跳到正文
cccskills
免费在 GitHub 公开

mil-hdbk-338

Knowledge base from MIL-HDBK-338B (Electronic Reliability Design Handbook). Use for electronic reliability engineering: R/M/A theory, reliability specification/allocation/prediction, parts management and derating, reliable circuit and fault-tolerant design, environmental and human performance reliability, FMEA/FMECA/FTA/sneak circuit analysis, design reviews and testability, FRACAS, reliability demonstration and growth testing, and systems-level R&M parameters. Covers selected Part 2 design-guidance topics only; skips large annex/part-stress tables. Guidance handbook — not a contractual requirement text. Does not replace MIL-HDBK-217 prediction libraries, service-specific reliability regs, or safety standards (see mil-std-882).

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(15)

  • SKILL.md6.5 KB
  • chapters/ch01-rma-theory-foundations.md2.4 KB
  • chapters/ch02-specification-allocation-prediction.md2.2 KB
  • chapters/ch03-parts-management-and-derating.md2.0 KB
  • chapters/ch04-circuit-design-and-fault-tolerance.md2.0 KB
  • chapters/ch05-environmental-and-human-reliability.md2.0 KB
  • chapters/ch06-fmea-fta-and-sneak-circuits.md2.0 KB
  • chapters/ch07-design-reviews-testability-safety.md2.1 KB
  • chapters/ch08-data-fracas-demonstration-growth.md2.1 KB
  • chapters/ch09-systems-reliability-engineering.md2.1 KB
  • cheatsheet.md1.6 KB
  • glossary.md1.8 KB
  • LICENSE1.2 KB
  • PACK.yaml1.6 KB
  • patterns.md2.2 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

<!-- argument-hint: [reliability topic, MTBF/MTTR, derating, FMEA/FTA, growth test, testability, or chapter number] -->

MIL-HDBK-338B — Electronic Reliability Design

Source: DoD MIL-HDBK-338B (US Government work, public domain; Distribution Statement A) | Chapters: 9

When to use

Reach for this pack when designing or reviewing electronic/hardware reliability programs grounded in MIL-HDBK-338B — especially reliability requirements and allocation, parts derating, prediction caveats, FMEA/FTA, testability, FRACAS, and reliability growth/demonstration strategy. Use it to brief design teams on inherent reliability levers and to structure analytical and test feedback loops.

Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.

How to Use This Skill

  • Without arguments — load the core frameworks below.
  • With a topic — ask about MTBF/availability, allocation/prediction, derating, fault tolerance, FMEA/FTA, growth testing, FRACAS, or testability.
  • With a chapter — ask for ch01 through ch09.

Supporting files: glossary.md, patterns.md, cheatsheet.md.

Guidance only. 338B states it is not to be cited as a requirement. Synthesize practices; do not paste annex reliability tables or third-party standard text.

Core Frameworks & Mental Models

Inherent reliability is a design output

Once the design (parts, stresses, architecture) is approved, inherent reliability is largely fixed. Parts, derating, circuit design, and fault tolerance set that ceiling before test.

Spec, allocate, model, predict

Quantitative requirements with environment; allocation tree; reliability model matching architecture; prediction with explicit method/assumptions; refresh when design changes.

R/M/A and system effectiveness

Reliability, maintainability, and availability metrics (including MTBF/MTTR-class measures) feed system effectiveness. Know whether you discuss inherent or operational measures.

Analysis pair: FMEA/FMECA + FTA (+ SCA when needed)

Inductive failure mode analysis for breadth; deductive fault trees for critical top events; sneak circuit analysis for latent paths without part failure.

Empirical loop: FRACAS + demonstration/growth

Data collection and closed-loop corrective action; choose growth (design still plastic) vs demonstration (frozen design decision test); accelerated tests need physics-aware reading.

Testability as a reliability property

Detection/isolation provisions and design-review gates make predicted reliability verifiable in integration and field use.

Chapter Index

#SectionKey content
ch01R/M/A Theory FoundationsDistributions, failure modeling, MTBF/MTTR/availability, Bayesian notes
ch02Spec, Allocation, PredictionRequirements, apportionment, models, prediction methods
ch03Parts Management & DeratingParts control, electronic/mechanical derating
ch04Circuit Design & Fault ToleranceRobust circuits, redundancy, fault-tolerant design
ch05Environment & Human ReliabilityEnvironmental design, human performance reliability
ch06FMEA/FTA/SCAFMEA/FMECA, fault trees, sneak circuits
ch07Reviews, Testability, Safety LinkDesign reviews, DFT/BIT, safety program interface
ch08Data, FRACAS, Demo & GrowthData uses, FRACAS, demonstration, growth, accelerated test
ch09Systems Reliability EngineeringEffectiveness, system R&M parameters, COTS/NDI

Topic Index

  • Allocation / apportionment → ch02
  • Availability (inherent vs operational) → ch01, ch09
  • BIT / diagnostics → ch07
  • COTS / NDI reliability → ch09
  • Derating → ch03
  • Environmental stress design → ch05
  • Failure distributions / Weibull / exponential → ch01
  • Fault tolerance / redundancy → ch04
  • Fault tree analysis (FTA) → ch06
  • FMEA / FMECA → ch06
  • FRACAS → ch08
  • Human performance reliability → ch05
  • MTBF / MTTR → ch01, ch02
  • Parts management → ch03
  • Physics-of-failure / stress drivers → ch05, ch03
  • Reliability demonstration → ch08
  • Reliability growth testing → ch08
  • Reliability prediction → ch02
  • Sneak circuit analysis → ch06
  • System effectiveness → ch09
  • Testability / DFT → ch07

Supporting Files

  • glossary.md — R&M terms used across selected 338B topics
  • patterns.md — implementation patterns with When/How/Trade-offs
  • cheatsheet.md — decision rules, maps, tells & smells

Scope & Limits

This pack covers selected design-guidance material from MIL-HDBK-338B (1 Oct 1998; Notice 2 keeps active) — R/M/A theory, specification/allocation/prediction, core Section 7 design guidelines (parts through safety interface), reliability data/FRACAS/demonstration/growth, and systems reliability engineering. Extraction metadata reports 1046 PDF pages for the nde-ed.org mirror copy (DLA catalog often cites ~716 content pages; PDF page objects can differ). It does not reproduce large annex part-stress/reliability tables, full worked numerical appendices, or third-party standards quoted inside 338B. Guidance only — not contractual requirements text. US Government public domain work (Distribution Statement A). No source-material download link is published.

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Signpost (not a knowledge pack) for the automotive standards landscape: ISO 26262, ASPICE, SAE J3016, UNECE R155, UNECE R156, and the NHTSA vehicle set. Contains NO source content: designation, edition, owner, status, and an official catalogue URL only. Use when you need to identify or locate an automotive standard. Most are paywalled or carry no redistribution grant and cannot be packaged; the one open path is the nhtsa-vehicle pack.

中文简介正在准备中。当前显示原文说明。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月15日 更新

Signpost (not a knowledge pack) for the avionics development assurance standards landscape: RTCA DO-178C / EUROCAE ED-12C and its supplements (DO-330/ED-215, DO-331/ED-218, DO-332/ED-217, DO-333/ED-216); RTCA DO-254 / EUROCAE ED-80; SAE ARP4754B and ARP4761A; and the free regulator documents that recognise them (FAA AC 20-115D, AC 20-152A, Order 8110.49A; EASA AMC 20-115D and AMC 20-152A). Contains no source content: each row carries only the designation, title, edition, owner, redistributability status, and the owner's URL. Use when you need to identify, cite, or locate an avionics standard; paywalled rows point to the owner, free rows point to the regulator text, and the FAA rows also name the in-repo faa-8110-49 pack.

中文简介正在准备中。当前显示原文说明。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月15日 更新

cisa-cpg

免费

Knowledge base from CISA Cross-Sector Cybersecurity Performance Goals 2.0. Use for prioritized IT/OT baseline cyber goals aligned to NIST CSF 2.0 (including GOVERN), critical-infrastructure hygiene, MSP/supply-chain expectations, and board-friendly outcome language. Covers CPG 2.0 goals only; does not replace full CSF programs, sector-specific goals (SSGs), or CSET tooling detail.

中文简介正在准备中。当前显示原文说明。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月15日 更新

Knowledge base from DAFMAN 63-119 (15 April 2021), Mission-Oriented Test Readiness Certification. Use for continuous MOTRC replacing single-point OTRR thinking: framework/applicability, Certification Official vs PM roles, review cycle and exit criteria, certification memo/decertify gates, DT&E/contractor evidence, ITT integration and cyber resiliency, and the 31-template matrix. DAF T&E readiness process only—does not replace DoDI 5000.89, AFI 99-103, or multi-service lead policies.

中文简介正在准备中。当前显示原文说明。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月15日 更新

Knowledge base from the DoD Systems Engineering Guidebook (OUSD R&E, February 2022). Use for the DoD SE process model — the 16 SE processes (8 technical management + 8 technical) mapped to ISO/IEC/IEEE 15288, the event-driven technical reviews and audits across the Major Capability Acquisition life cycle (ASR, SRR, SFR, PDR, CDR, SVR/FCA, PRR, PCA), the Systems Engineering Plan (SEP), risk/issue/opportunity management, TPMs and leading indicators, system-of-systems and digital engineering, and the 24 design considerations (RAM, system safety, HSI, system security engineering, MOSA, supportability, etc.). Acquisition-program oriented: thin on detailed cost estimating, contracting law, and non-DoD or commercial life cycles.

中文简介正在准备中。当前显示原文说明。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月15日 更新

Knowledge pack from 'Towards Digital Engineering: The Advent of Digital Systems Engineering' (Huang et al., Old Dominion University, arXiv:2002.11672, 2020). Use when reasoning about digital engineering, 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) DSE research framework. Covers the conceptual/vision layer of the field. SCOPE LIMITS: this is a single ~28-page vision paper, not a methods handbook — it is thin on step-by-step procedures, tooling, case studies, and quantitative evaluation, and it predates 2020 so it does not cover later digital-engineering standards or recent AI/LLM advances. Use the sebok pack for established SE canon and MBSE depth.

中文简介正在准备中。当前显示原文说明。

jgsystemsconsulting/jgs-se-knowledge-packs82026年10月15日 更新

查看 jgsystemsconsulting 的全部技能

报告此技能的问题