CLASSIFICATION: PUBLIC LICENCE: MIT (TOOLING) DOC-ID: JGS-SE-KP/REF REV: 1.16.3
JG Systems Consulting Ltd. · Pack reference

The full catalogue, 48 skills

Every knowledge pack in the release, with its source licence and what it covers. Each pack is an Agent Skill you invoke by its slug. Type to filter by name, publisher, licence, or topic. Click a slug to open its SKILL.md on GitHub.

PackSource licenceWhat it covers
sebokCC BY-NC-SA 3.0Knowledge base from the Guide to the Systems Engineering Body of Knowledge (SEBoK) v2.14. Reference the established SE canon, lifecycle models, ISO/IEC/IEEE 15288 processes, system definition and architecture, V&V, MBSE, systems thinking, traceability, standards alignment, and SoS/enterprise/service SE.
nasa-se-handbookPublic Domain (US Gov)Knowledge base from the NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2). NASA's SE process model, the SE Engine and 17 common technical processes, project life cycle (Pre-Phase A–F), Key Decision Points and technical reviews, system design, product verification and validation, and crosscutting technical management.
nasa-se-expandedPublic Domain (US Gov)Knowledge base from the Expanded Guidance for NASA Systems Engineering (NASA/SP-2016-6105-SUPPL Vol 1), the practitioner-depth supplement to the NASA SE Handbook. The load-bearing mechanics the handbook compresses: the SE Engine's per-phase cadence and iterative-vs-recursive distinction, life-cycle tailoring vs. customization, the recursive system-design consistency loop (ConOps, requirement flow/type/ownership), product realization (verify/qualify/accept/certify cardinality, protoflight, 'test the way we fly'), and crosscutting technical management (six-step scheduling, cost estimating, JCL, the interface document family, RIDM/CRM, CM baselines, EVM, MOE/MOP/KPP/TPM, leading indicators, decision-analysis methods). The DEPTH layer, pair it with the nasa-se-handbook pack.
nist-ai-rmfPublic Domain (US Gov)AI risk management, the four functions (Govern, Map, Measure, Manage), trustworthiness characteristics, harmful-bias management, and AI RMF profiles.
nist-ssdfPublic Domain (US Gov)Secure software development practices grouped as Prepare the Organization, Protect the Software, Produce Well-Secured Software, and Respond to Vulnerabilities.
nist-csfPublic Domain (US Gov)The six CSF functions (Govern, Identify, Protect, Detect, Respond, Recover) plus organizational profiles and tiers for managing cybersecurity risk.
nist-ssePublic Domain (US Gov)Systems security engineering (NIST SP 800-160 Vol 1 + Vol 2), the three SSE framework contexts (problem/solution/trustworthiness), 30+ design principles for trustworthy secure design, trustworthiness & assurance cases, security across the life-cycle process groups, and the cyber-resiliency engineering framework (4 goals, objectives, 14 techniques, design principles) for the APT threat model.
nist-800-37Public Domain (US Gov)Risk Management Framework (NIST SP 800-160's governance overlay, NIST SP 800-37 Rev 2), the seven RMF steps (Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor) and their tasks, the three-tier organization-wide risk model, authorization boundaries, the requirements-to-controls relationship, security categorization (FIPS 199/200 high-water mark) and control selection/tailoring (SP 800-53/53B baselines, named not reproduced), the authorization decision and risk acceptance, continuous monitoring and ongoing authorization, the security/privacy distinction, and supply chain risk management.
nist-cpsPublic Domain (US Gov)NIST Framework for Cyber-Physical Systems (SP 1500-201/202/203, v1.0), the CPS Framework's aspect × facet grid (nine aspects examined through conceptualization, realization, and assurance facets), cross-property trustworthiness risk management (safety/security/privacy/reliability/resilience together), data interoperability (syntactical/semantic/contextual, canonical models, identifiers, provenance), the timing aspect (time-interval classes, time domains, time-aware networking) and secure/resilient time (GNSS jamming/spoofing, PTP/NTP attacks, holdover, the clock-error model and Allan/MTIE metrics), plus the use-case requirements method. Bridges IT and OT under a clock.
digital-systems-engineeringCC BY 4.0Towards Digital Engineering (Huang et al., Old Dominion University, arXiv:2002.11672, 2020), digital engineering and the DoD Digital Engineering Strategy and its five goals, the Authoritative Source of Truth, digitalization vs. digitization, digital augmentation, digitalized models, provenance, unique identification, and the four-level (vision/strategy/action/foundation) Digital Systems Engineering research framework. The conceptual/vision layer of the field; a single ~28-page vision paper, thin on methods and tooling.
nasa-npr-7123Public Domain (US Gov)NASA's SE process requirements, the 17 common technical processes as 'shall' requirements, life-cycle phases and technical reviews (entrance/success criteria), the SEMP, and Technology Readiness Levels.
nasa-riskPublic Domain (US Gov)NASA's integrated risk management, Risk-Informed Decision Making (RIDM) and Continuous Risk Management (CRM: Identify, Analyze, Plan, Track, Control, Communicate & Document).
nasa-system-safetyPublic Domain (US Gov)NASA system safety, the Risk-Informed Safety Case (RISC), the claim-evidence-argument structure, safety objectives and requirements, and RISC development and evaluation.
nasa-praPublic Domain (US Gov)Knowledge base from the NASA Probabilistic Risk Assessment Procedures Guide (NASA/SP-2011-3421, 2nd ed.), quantitative PRA of aerospace and safety-critical systems: the risk triplet and scenario logic stack (MLD, ESD, event trees, fault trees, minimal cut sets), Bayesian data collection and parameter estimation, aleatory/epistemic uncertainty and common-cause failure (Alpha Factor, beta-factor, CCBE), human reliability analysis (THERP, CREAM, NARA, SPAR-H), context-based software risk (CSRM), physics-based/structural models (stress-strength, FORM/SORM, NASGRO), uncertainty propagation and importance measures (F-V, RAW, Birnbaum, DIM), and launch-abort modeling with worked examples. The QUANTITATIVE engine beneath NASA's risk doctrine, for the qualitative RIDM/CRM framework use the nasa-risk pack.
nasa-hsiPublic Domain (US Gov)NASA Human Systems Integration, the six HSI domains, the HSI process across the life cycle, technical authorities, and HSI planning, scaling, and tailoring.
mil-std-882Public Domain (US Gov)DoD System Safety, the system safety process, hazard analysis tasks (PHA/SSHA/SHA/O&SHA), the severity x probability risk assessment matrix, software safety criticality, and risk acceptance.
requirements-writingCC BY 4.0 (original)Writing high-quality requirements, the quality characteristics and EARS patterns (When/While/Where/If-Then) for unambiguous, verifiable requirements, plus defect review and verification & traceability.
gao-traPublic Domain (US Gov)GAO Technology Readiness Assessment Guide (GAO-20-48G), evaluating technology maturity in acquisition programs: Technology Readiness Levels (TRL 1–9) and related scales (MRL, IRL), Critical Technology Elements (CTEs), the five-step TRA process, the four characteristics of a reliable TRA (comprehensive, well-documented, credible, defensible), Technology Maturation Plans (TMPs), and knowledge-based milestone decisions.
dau-se-guidebookPublic Domain (US Gov)DoD Systems Engineering Guidebook (OUSD R&E), the DoD SE process model (16 processes: 8 technical management + 8 technical, mapped to ISO/IEC/IEEE 15288), event-driven technical reviews and audits (ASR/SRR/SFR/PDR/CDR/SVR-FCA/PRR/PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs, system-of-systems and digital engineering, and the 24 design considerations.
dodafPublic Domain (US Gov)DoD Architecture Framework Vol II, the eight DoDAF viewpoints (All / Capability / Data & Information / Operational / Project / Services / Standards / Systems), the DM2 meta-model, and fit-for-purpose model selection.
eu-ai-actEU OJ (reproducible)EU Artificial Intelligence Act (Reg 2024/1689), prohibited practices, high-risk classification & requirements (risk management, data governance, human oversight), operator obligations, conformity assessment, GPAI models, transparency, and governance.
faa-semPublic Domain (US Gov)FAA Systems Engineering Manual (SEM) v1.0.1, civil-agency SE as the FAA practices it inside the Acquisition Management System (AMS) and the National Airspace System: the five-phase AMS lifecycle and its decision points, operational concept development and implementation-free functional analysis (ConOps, FFBD/N², CMLs), requirements and architecture synthesis (PRS→MRS, the pPRD→iPRD→fPRD ratchet, RAM, CPRs), the seven technical management disciplines (Integrated Technical Management/SEMP, Interface Management/IRD-ICD, Risk-Issue-Opportunity, Configuration Management, SE Information Management, Decision Analysis, V&V), and the specialty disciplines (RMA via Service Threads, Life Cycle Engineering, E3/Spectrum, Human Factors, Information Security via the NIST RMF, System Safety via the SMS, environmental/EOSH).
nasa-schedulePublic Domain (US Gov)NASA Schedule Management Handbook (2024 ed., Rev 2), program/project schedule management of aerospace and large engineering efforts: the five sub-functions (Planning, Development, Assessment & Analysis, Maintenance & Control, Documentation & Communication), the Integrated Master Schedule (IMS) and WBS/OBS/CBS, the Schedule Management Plan (SMP) and Basis of Estimate, Critical Path Method, float and margin, tiered schedule assessment (the Shock Test, Dimensions of Schedule Reliability), Schedule Risk Analysis (SRA), Integrated Cost-Schedule Risk Analysis (ICSRA), Monte Carlo and the Joint Confidence Level (JCL), baselining vs. replan vs. rebaseline, and EVM schedule metrics (SPI, BEI, CEI, Earned Schedule, CPLI).
dod-mosaPublic Domain (US Gov)DoD MOSA, *Implementing a Modular Open Systems Approach in DoD Programs* (OUSD R&E, Feb 2025), MOSA as a DoD acquisition + design discipline: the statutory/regulatory basis (10 U.S.C. 4401–4403, FY2017/FY2021 NDAA, DFARS), the five OUSD(R&E) pillars, the plan→modularize→identify→define→standardize interface lifecycle, technical levers (WBS/MIL-STD-881F taxonomy, standards profiling, API-first software, COTS/cybersecurity), MOSA assessment metrics and tools (PART/OAAT/KOSS/SEAM/MAUT), technology-change and DMSMS management, roadmaps, MOSA across the six AAF pathways, and contracting/IP/data-rights mechanics.
nasa-rm-standardPublic Domain (US Gov)NASA Reliability and Maintainability Standard (NASA-STD-8729.1A, Rev A), NASA's objectives-driven R&M framework: the R&M objectives hierarchy (one Top Objective decomposed into four sub-objectives, paired with tailorable strategies), how R&M requirements are set inside the SMA Plan required by NPR 7120.5, SMA Technical Authority concurrence/independent-evaluation governance, milestone vs. readiness review gates, the reliability/maintainability/availability vocabulary (Ai vs. Ao, the failure causal chain, risk as a triplet), and the R&M Evidentiary Methods catalogue (FMEA/FMECA, FTA, RBDA, RCM, LORA, plus space-environment and parts-pedigree analyses). An objectives-and-strategies standard, defers step-by-step procedures to the NASA Preferred Reliability Practices.
dod-rioPublic Domain (US Gov)DoD Risk, Issue, and Opportunity (RIO) Management Guide for Defense Acquisition Programs (OUSD R&E, Sep 2023 incl. Change 2.2), the defense-acquisition mechanics of program risk management: the RIO definitions, the five-step risk process (plan-identify-analyze-mitigate-monitor), 1–5 likelihood/consequence scoring and the 5×5 matrix, the four mitigation options (accept/avoid/transfer/control), burn-down plans, issue management (probability=1), opportunity management toward should-cost, cross-program/interface risk, tailoring RIO to the six AAF pathways (UCA/MTA/MCA/Software/DBS/Services), specialized methods (RMF, MBCRA/Cyber Table Top, Agile metrics, FMECA, ITRA/DTRAM), and institutionalizing RIO via the PRMP, boards (RMB/JRMB/ROMB/RWG), tiered roles, and WBS/IMP/IMS/EVM/TPM integration. The DoD-acquisition complement to `nasa-risk` and `dau-se-guidebook`.
dod-digital-engineeringPublic Domain (US Gov)DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)), the Department of Defense's five digital engineering goals (formalize models; provide an enduring authoritative source of truth; incorporate technological innovation; establish supporting infrastructure and environments; transform the culture and workforce), their focus areas, the document-to-model and design-build-test→model-analyze-build shifts, model formalisms/provenance, governance and access control of the authoritative source of truth, and the coordinate→plan→pilot→sustain rollout. A vision-and-policy strategy, deliberately non-prescriptive, no how-to method or MBSE/SysML mechanics; excludes the CAC-gated DEBoK.
nasa-de-acquisitionPublic Domain (US Gov)NASA Digital Engineering Acquisition Framework Handbook (NASA-HDBK-1004), acquiring digital/model-based data under contract: the Data Requirements Description (DRD) instrument and the Appendix A DRD suite (TDP, MBx, CDMP, CSA, CR, FCA/PCA, SDT, EMDAL, REF, MRI), the Data Type 1–5 control scale, SOW/RFP/Cost-Volume contract language and data rights (FAR/DFARS, Table 3 license categories), the Requirements Exchange Format (REF/ReqIF, UUID schema) and Master Records Index, model-based data definition (MBSE, CAD/PMI, M&S credibility, BOM, release-state mapping, PLM), digital data collaboration, the four owned architectures, interoperability standards (MIL-STD-31000, STEP/ISO 10303, ASME Y14), the four MBE interoperability use cases, and MBE Plan development. The acquisition-and-contracting side of digital engineering.
nasa-fault-managementPublic Domain (US Gov)NASA Fault Management Handbook (NASA-HDBK-1002, Draft 2, April 2012), designing what a system does when it fails: the fault/failure/anomaly vocabulary, the five FM strategies (fault avoidance, failure avoidance, failure masking, failure recovery, goal change), the six FM process activities across NASA mission phases Pre-A to E, response-latency-versus-time-to-criticality (TTC) design trades, fault/failure containment regions and FEPPs, the four redundancy approaches, top-down FM requirements development, FM verification vs. validation, the seven dedicated FM milestone reviews (FMCR/FMARR/FMPDR/FMCDR/FMTRR/FMLRR/FMCERR), FM organizational structure, and mined NASA Lessons Learned. **Built from an UNAPPROVED DRAFT**, informational guidance, not a controlling standard; several sections are thin source placeholders.
faa-system-safetyPublic Domain (US Gov)FAA System Safety Handbook (Dec 30, 2000), system safety as a specialty within systems engineering: the five-step safety risk management process (mandated by FAA Order 8040.4 and the AMS), the severity-by-likelihood risk matrix and acceptance bands, the Safety Order of Precedence, system-description models (5M, SHEL(L)), the hazard-analysis activities (PHL/PHA/RHA/SSHA/SHA/O&SHA/HHA), integrated system hazard analysis, the analysis techniques (FTA, FMEA/FMECA, Fault Hazard, Common Cause, Sneak Circuit, Energy Trace), closed-loop hazard tracking (Safety Action Record), and the specialty domains, acquisition-lifecycle safety and contracting, software safety (DO-178B), test & evaluation safety, facilities safety, commercial launch safety, training, and Operational Risk Management (ORM). A year-2000 FAA how-to that predates the modern FAA/ICAO SMS frameworks.
faa-hf-stdPublic Domain (US Gov)Knowledge base from the FAA Human Factors Design Standard (HF-STD-001B, 2016), the FAA's consolidated human-factors / human-systems-integration design criteria for systems it manages, operates, or maintains. Use for requirement-level design rules on: general human-factors design principles; automation and function allocation; designing equipment for maintenance; displays, controls, and visual indicators; alarms, audio, and voice communications; the computer-human interface (information presentation, coding, interaction styles, windows, dialogue); keyboards, input devices, and workstation/workplace ergonomics; system security, personnel safety, environment, anthropometry, and user documentation; plus intended-use and tailoring guidance. It is a quantified, source-attributed synthesis (heavily citing MIL-STD-1472G, MIL-HDBK-759C, DOD-HFDG-ATCCS, NUREG-0700, NASA-STD-3000, ANSI, OSHA, ISO 9241). Complements nasa-hsi as a parallel HSI tradition from the civil-aviation domain. Scope limits: it is design criteria, NOT an HSI lifecycle/process model (use nasa-hsi, nasa-npr-7123, or dau-se-guidebook for process); it does NOT reproduce the third-party standards it cites; it is FAA-acquisition-oriented (ATC, towers, TRACONs, airway facilities), not a general consumer-UX guide; and it is thin on modern touchscreen/mobile, web, and AI-driven interface patterns and on quantitative human-reliability analysis.
dod-mq-bokPublic Domain (US Gov)Knowledge base from the DoD M&Q BoK (the Manufacturing and Quality Engineering Body of Knowledge), v3.0 of July 2025, published by OUSD(R&E). Use for the manufacturing-and-quality view of the defense acquisition life cycle: what M&Q engineers do across the Adaptive Acquisition Framework phases (Pre-MDD, Materiel Solution Analysis, Technology Maturation and Risk Reduction, Engineering and Manufacturing Development, Production and Deployment, Operations and Support); the twelve M&Q threads (A–L) built on the '5 Ms'; manufacturing feasibility and producibility; Manufacturing Readiness Levels and assessments; Key/Critical Characteristics and process capability (Cp/Cpk, SPC); the standards stack (AS6500, AS9100/ISO 9001, AS9103, AS9145); technical reviews (ASR/PDR/CDR/PRR) and milestone gates; DCMA surveillance; industrial base and supply chain; and sustainment (LCSP, IPS, ILA, ISR). Scope is DoD acquisition M&Q practice on the Major Capability Acquisition path, it is a best-practice compilation, not policy, and is thin on detailed shop-floor process engineering, contract law, and the full text of the cited industry standards (which it names but does not reproduce).
gao-costPublic Domain (US Gov)Knowledge base from the GAO Cost Estimating and Assessment Guide (GAO-20-195G). Use for program cost estimating: the four characteristics of a reliable estimate (comprehensive, well documented, accurate, credible) and the 18 best practices, the 12-step cost estimating process, estimating methods (analogy, parametric/CER, engineering build-up, learning curves), Monte Carlo risk/uncertainty analysis with confidence levels and contingency, auditing and validating an estimate against the four characteristics, earned value management (EIA-748, BCWS/BCWP/ACWP, CPI/SPI/TCPI, EAC, PMB, IBR), and specialized techniques (software cost estimating, Analysis of Alternatives, WBS templates, the Green Book internal-control framework). The cost-estimating companion to `gao-schedule` and `gao-tra`; names referenced standards (EIA-748, MIL-STD-881D, the Green Book) without reproducing them.
gao-schedulePublic Domain (US Gov)Knowledge base from the GAO Schedule Assessment Guide (GAO-16-89G, 2015). Use for building, assessing, or auditing a program's integrated master schedule (IMS): the ten best practices of a reliable schedule (capture, sequence, resource, duration, traceability, valid critical path, reasonable total float, schedule risk analysis, updating, baseline), the four characteristics (comprehensive, well-constructed, credible, controlled), critical path method arithmetic (forward/backward pass, total float), schedule risk analysis (Monte Carlo, contingency), statusing and baseline control, and the Appendix II audit triad. The time-domain authority on schedule reliability, NOT a cost-estimating guide, full SE process model, agile guide, or risk-management framework (see `gao-cost`, `dau-se-guidebook`, `nasa-schedule`, `nasa-risk`).
nasa-cehPublic Domain (US Gov)Knowledge base from the NASA Cost Estimating Handbook (CEH) v4.0. Use for NASA's 12-step, three-part cost estimating process (Project Definition, Cost Methodology, Cost Estimate), the WBS/CADRe/ONCE data backbone, estimating methodologies (analogy, parametric/CER, engineering build-up, EVM, Delphi), ground rules and assumptions, data normalization and inflation (BY/CY/RY), the point-estimate-to-S-curve cost-risk chain and Unallocated Future Expense (UFE) reserves, Joint Cost and Schedule Confidence Level (JCL) analysis via probabilistic cost-loaded schedules, decision-support analyses (sensitivity, trade studies, make/lease-vs-buy, affordability, CAIV), and economic analysis (discounting, NPV, OMB Circular A-94). The cost-estimating complement to NASA's SE and risk packs and to the GAO cost canon; names third-party tools/standards (ACEIT, SEER, OMB A-94, GAO-09-3SP) without reproducing them.
nasa-systems-modelingPublic Domain (US Gov)Knowledge base from the NASA Systems Modeling Handbook for Systems Engineering (NASA-HDBK-1009A Rev A, 2025), model-based systems engineering (MBSE) wired into NASA's NPR 7123.1 SE processes: the three aspects of MBSE (language / methodology / framework), the NASA SE Engine and its two OOSEM-derived steps (Model Planning, Setting Up the Model), the Modeling Plan as a SEMP subset, the tool-agnostic NASA SE metamodel of elements and relationships across the four SysML pillars (structure / behavior / requirements / parametrics), worked SysML diagrams and tables for stakeholders/requirements/structure/V&V, generating SE work products (ConOps, MOE, MOP, TPM, V&V), the MBSE Grid framework, alternative modeling approaches (PBR, Scenario, System Specification, Verification), and the ConOps model-content template. Bounded to four common technical processes (Stakeholder Expectation Definition, Technical Requirements Definition, Product Verification, Product Validation); does NOT teach SysML itself, mandate a tool, define NPR 7123.1 processes, cover technical-management processes 10–17, or reproduce the OMG SysML specification.
dod-te-guidebookPublic Domain (US Gov)Knowledge base from the DoD Test & Evaluation Enterprise Guidebook (OUSD R&E, August 2022), DoD test and evaluation (T&E) across the Adaptive Acquisition Framework: the four test communities (contractor testing, developmental DT&E, operational OT&E, live-fire LFT&E); the five operational events (Operational Demonstration, EOA, OA, IOT&E, FOT&E) and the OTRR gate; the T&E Strategy / TEMP and its IDSK, with the upstream documents that feed it and the test plans that decompose it; the T&E organizations and oversight roles (USD(R&E), DOT&E, TRMC, the Service Executives and OTAs, the T&E WIPT, CDT); and pathway-specific T&E for all six acquisition pathways. Statutory anchors include 10 U.S.C. §4171 (IOT&E) and §4172 (LFT&E/FUSL). Guidance, not policy, it points outward to DoDI 5000.89 and the DoDI 5000-series for binding detail, and is thin on detailed test statistics/design-of-experiments, cost estimating, the Acquisition of Services pathway, and CUI/CAC-gated companion guides.
faa-ams-vvPublic Domain (US Gov)Knowledge base from the FAA AMS Lifecycle V&V Guidelines (verification and validation), Version 3.0 (April 2017), applying V&V across the FAA Acquisition Management System (AMS) lifecycle: the verify-vs-validate distinction (built right vs. right thing), the work-product/component/product tiers, the nine V&V planning elements, the four method catalogs (Appendix C), decision-point-gated V&V (SASP, CRD, Investment Analysis, Solution Implementation, In-Service Management), the Appendix B document checklists (PRD/APB/ISPD/PMP), and the DT/OT/IOA test triad. An FAA acquisition-V&V doctrine, NOT a general SE process model, requirements-engineering manual, or test-design textbook; borrows its core V&V definitions from CMMI v1.2 (SEI, paraphrased) and presumes the surrounding AMS lifecycle (see the `faa-sem` pack). Phase tables are April-2017 policy snapshots; thin on detailed test methods, tool specifics, and anything outside FAA acquisition governance.
gao-agilePublic Domain (US Gov)Knowledge base from the GAO Agile Assessment Guide (GAO-24-105506, 2023). Use for assessing and managing Agile software development in federal programs: the Agile Manifesto and framework family (Scrum, Kanban, XP, SAFe, DA, DSDM, Lean, DevOps); the three adoption perspectives (team dynamics, program operations, organization environment); requirements decomposition (epics, features, user stories, INVEST, MoSCoW, definition of done); Agile-aware federal contracting (FAR, modular contracting, SOO/PWS/SOW, product owner vs. COR); program monitoring and control (WBS, cost, schedule, EVM at the feature level); Agile metrics (velocity, lead/cycle time, CFD, burn charts); and the auditor's key-question bank. Oversight- and acquisition-oriented: it tells you how to *assess and govern* Agile programs, not how to code. Thin on hands-on engineering practice, deep cost/schedule checklists (see `gao-cost`, `gao-schedule`), and any non-US-federal context.
mil-hdbk-61Public Domain (US Gov)Knowledge base from MIL-HDBK-61B, the DoD Configuration Management (CM) guidance handbook (7 April 2020, cataloged with Change 1, 2025). Use for defense CM across the acquisition and sustainment life cycle: the five CM functions (planning, identification, control/change management, status accounting, verification & audit), the three configuration baselines (FBL/ABL/PBL) and FCD→ACD→PCD documentation, configuration items (CIs/HWCI/CSCI), change instruments (ECP/NOR/RFV), the CCB and Class I/II classification, CDCA/AA authority, FCA/PCA audits, data management and data rights (CDRL/DID, DFARS rights ladder, master/authoritative source), and tailoring CM by phase (EIA-649-1 R/T/NR matrix, Appendix C templates), plus digital-era CM (digital twin, viewpoints, MOSA). NOTE: 61B is advisory guidance that adopts and points to the SAE EIA-649 / EIA-649-1 / GEIA-HB-649 suite for the authoritative CM requirements, this pack names and describes that suite but does not reproduce its copyrighted requirement text. Thin on: the EIA-649 requirement clauses themselves, form-level detail (DD-form field instructions, full DID content), and non-DoD/commercial CM frameworks.
mrl-deskbookPublic Domain (US Gov)Knowledge base from the DoD Manufacturing Readiness Level (MRL) Deskbook (Version 2022, OSD ManTech / Joint Service–Industry MRL Working Group). Use for assessing and managing manufacturing maturity and producibility risk in defense acquisition: the 10-level MRL scale and its non-linear, target-not-grade nature; the five demonstration environments (laboratory → production-relevant → production-representative → pilot line → production line); the nine manufacturing-risk threads and sub-threads; how MRL targets map onto Adaptive Acquisition Framework milestones (MRL 4/6/7/8/9); conducting an MRL Assessment; building a Manufacturing Maturation Plan; putting MRL maturity into contract language (Section L/M, SOW, AS6500A, DIDs); tailoring criteria for S&T, single-system, ship, sustainment, and industry contexts; and screening operational-technology cybersecurity. Manufacturing-readiness focused, it measures producibility risk and frames mitigation; it is NOT a technology-readiness (TRL) guide, a full systems-engineering process model, a cost-estimating or schedule guide, or a deep cybersecurity audit method (see sibling packs for those).
faa-req-handbookPublic Domain (US Gov)Knowledge base from the FAA Requirements Engineering Management Handbook (DOT/FAA/AR-08/32). Use for writing requirements for real-time, embedded control systems, the avionics/medical slant, via the Handbook's eleven recommended practices: system overview and boundary (monitored/controlled variables), operational concepts (use cases), environmental assumptions, change-tolerant functional architecture (dependency diagrams), safety-driven architecture revision (FHA/PSSA/fault tree), system modes, detailed behavior and performance requirements (ideal value + tolerance + latency), the four-variable model bridge to software requirements (MON/CON/NAT/REQ, IN'/REQ'/OUT', DO-178B mapping), subsystem allocation, and rationale. Carries the Isolette Thermostat and Flight Control System worked examples. Slanted toward control systems with sensors and actuators; thin on information-system / enterprise / agile requirements, on requirements-management tooling, and on the formal-methods internals of SCR/RSML/SpecTRM (it names them, does not re-teach them). Does not reproduce the IEEE/DO-178B/ARP standards it cites.
sd-22-dmsmsPublic Domain (US Gov)Knowledge base from the SD-22 DMSMS Guidebook (DSPO, FY24 working draft). Use for managing Diminished Manufacturing Sources and Material Shortages (DMSMS) and obsolescence across a long-lived system's life cycle: the five-step process (Prepare, Identify, Assess, Analyze, Implement) plus the Strategize overlay; standing up a DMSMS Management Team (DMT) and Management Plan (DMP); risk-based monitoring and surveillance (the risk cube, predictive tools, vendor surveys, GIDEP/DLA PDNs, critical-materials analysis); health assessments and resolution timing; costing and selecting resolutions (life-of-need buys, substitutes, redesign, technology refreshment) by AoA/BCA; and budgeting/executing resolutions through modification funding and the ECP process. Defense-sustainment / DoD-acquisition framing throughout. Does NOT teach general systems engineering, parts-management standards, or contracting law in depth, and does not reproduce DoD policy text or the source's tables and figures.
nasa-npr-7150Public Domain (US Gov)Knowledge base from NASA NPR 7150.2D, NASA Software Engineering Requirements. Use for NASA's Agency-wide software-engineering requirements: the software classification scheme (Classes A–F), the Requirements Mapping Matrix and class-driven applicability, tailoring and Technical Authority governance, the SWE-### 'shall' requirements across software management (Ch 3) and the engineering life cycle (Ch 4), the supporting disciplines (configuration management, risk, peer reviews/inspections, measurement, non-conformance, Ch 5), safety-critical and cybersecurity requirements, IV&V applicability, traceability, and the Appendix A definitions. Does not cover detailed software-assurance/safety procedures (see NASA-STD-8739.8), implementation how-to and document content (see NASA-HDBK-2203), the systems-engineering process framework (see NPR 7123.1), or program/project management (see NPR 7120.5). The software-requirements complement to `nasa-npr-7123`.
nist-stat-handbookPublic Domain (US Gov)Knowledge base from the NIST/SEMATECH e-Handbook of Statistical Methods (NIST HB 151), the practical statistics reference for engineering, metrology, and quality. Use for: exploratory data analysis and the four univariate assumptions (4-plot); measurement process characterization including bias/precision, calibration designs, gauge R&R, and ISO/GUM uncertainty budgets; production process characterization (stability vs. capability); process modeling and regression (LS/WLS/NLS/LOESS); design of experiments (screening, fractional/factorial, response-surface, Taguchi); statistical process control (Shewhart/CUSUM/EWMA charts, capability indices, acceptance sampling); product/process comparisons (hypothesis tests and confidence intervals for 1/2/3+ groups, ANOVA, multiple comparisons); and reliability (lifetime & repair-rate models, accelerated testing, reliability growth). Applied frequentist statistics for measurement and quality, does NOT reproduce the per-distribution formula galleries, worked case studies, datasets, plot images, or Dataplot/R code of the original web Handbook (described, not copied); thin on modern machine learning, Bayesian methods beyond conjugate reliability priors, time-series/forecasting, and Bayesian experimental design.
faa-rmaPublic Domain (US Gov)Knowledge base from FAA-HDBK-006D (2020), the FAA's System Reliability, Maintainability, and Availability (RMA) Handbook for National Airspace System (NAS) hardware and software. Use for RMA figures of merit (MTBF, MTBO, MTTR, the availability variants), the bathtub curve and probability distributions, the four-stage RMA lifecycle mapped to the FAA Acquisition Management System (AMS), the six-task RMA technical-management/acquisition process, service-thread criticality and the NAS-RD severity-to-target table, the RMA analysis toolbox (RBD, FMEA/FMECA, FTA, Ishikawa, Monte Carlo, Bayesian, FRACAS, ALT, reliability-growth/recovery tests), software reliability (early prediction + reliability growth), and tailorable example RMA requirements for a Program Requirements Document. Scope limits: FAA/NAS-specific guidance (not a requirement, by its own statement), centred on hardware-plus-software availability, brackets out human/service/facility/communications availability, names but does not reproduce the math derivations or external standards (MIL-STDs, IEEE 1633, RTCA DO-178C/DO-278A, SAE JA1011), and is thin on detailed worked numerical examples and on safety-case method.
omg-signpostMIT (signpost)**Signpost, not a pack**, points to the official OMG specs (UML, SysML, BPMN, UAF…) at omg.org with zero reproduced content. OMG specs can't be packaged (licence forbids it), so this cites where to get them.
se-standards-signpostMIT (signpost)**Signpost, not a pack**, the full SE standards landscape (ISO/IEC/IEEE 15288/24748/29148/42010, INCOSE SE Handbook & Vision 2035, SAE/EIA, ECSS, NATO AAP-48, CMMI, NIST SP 800-160…) with each standard's owner, redistributability status, and where to get it. Zero reproduced content; most are paywalled/all-rights-reserved and point to the owner, the open ones point to the real pack.
No packs match that filter.