本文へ移動
cccskills
無料GitHub で公開

faa-std-025

Knowledge base from FAA-STD-025f (Preparation of Interface Documentation). Use for IRD/ICD family definitions, common format and content, IRD shall-requirements, ICD design characteristics, verification/VRTM, and CM/revision/approval of FAA Enterprise Subsystem interfaces. Covers rev F preparation rules only; does not replace FAA-STD-005 drawing/spec prep, Order 1800.66 full CM procedures, or non-FAA interface standards.

インストール方法を見る

含まれるファイル(12)

  • SKILL.md5.5 KB
  • chapters/ch01-scope-and-document-family.md3.6 KB
  • chapters/ch02-general-format-and-common-content.md3.6 KB
  • chapters/ch03-ird-content-requirements.md4.2 KB
  • chapters/ch04-icd-content-requirements.md3.5 KB
  • chapters/ch05-verification-and-traceability.md3.4 KB
  • chapters/ch06-revisions-cm-and-approval.md3.4 KB
  • cheatsheet.md1.9 KB
  • glossary.md2.5 KB
  • LICENSE1.1 KB
  • PACK.yaml1.6 KB
  • patterns.md2.5 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

<!-- argument-hint: [topic, document type, or chapter number] -->

FAA-STD-025f — Preparation of Interface Documentation

Source: FAA-STD-025f (US Government work, public domain) | Chapters: 6

When to use

Reach for this pack when authoring or reviewing Interface Requirements Documents (IRD) or Interface Control Documents (ICD) for FAA Enterprise Subsystems / NAS interfaces — including choosing IRD vs ICD, filling required outlines, specifying security/physical/power interface shalls, building a VRTM, or routing revisions under configuration management.

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 IRD vs ICD, TBS, facility IRDs, VRTM, security shalls, power factors, or approval roles.
  • With a chapter — ask for ch01 through ch06.

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

Core Frameworks & Mental Models

IRD / ICD pair

ArtifactAnswersVerbBaseline role
IRDWhat must the interface satisfy?shallFAA-controlled requirements baseline
ICDHow is it implemented / as-built?is/areDeveloper deliverable design record

Facility interfaces: IRD only (no ICD). Orphan ICDs (no parent IRD) must carry both shall and is/are — discouraged.

Interface-type outlines

Use the standard decision tree, then the matching TOC:

  • Facility / analog / discrete family
  • General service / web service family

Shared rules: front matter, explicit N/A, incorporation by reference, TBS only where allowed.

Common technical spine

  1. Scope template + responsibility lists
  2. Referenced documents (versioned, accessible, tailored)
  3. Functions / demarcation / security / physical / power
  4. Type-specific protocol or facility slots
  5. Verification responsibility + VRTM (1:1 with shalls)

Verification levels

Subsystem/Service (Development) → Integration → Site. SEM T&E guidance tailored into the VRTM; special conformance/interoperability for ATN/IPS.

CM and timing

  • Start IRD early; before SOW finalization when used in procurement.
  • Approve IRD before ICD when both required.
  • Revise by superseding full document under FAA Order 1800.66 (no legacy side "Interface Revision" form).
  • Facility IRD maturity: Initial → Primary → Intermediate → Final.

Chapter Index

#SectionKey content
ch01Scope and Document FamilyFESS applicability, IRD vs ICD, TBS, baselining
ch02General Format and Common ContentOutlines, front matter, scope templates, references
ch03IRD Content RequirementsFunctional/security/physical/power and typed IRDs
ch04ICD Content RequirementsDesign characteristics, as-built, orphan ICD rule
ch05Verification and TraceabilityVRTM, levels, methods, ATN/IPS special tests
ch06Revisions, CM, and Approval1800.66 revisions, roles, facility iterations

Topic Index

  • Analog / discrete interfaces → ch01, ch03, ch04
  • Application process / protocols → ch03, ch04
  • As-built / form-fit-function → ch01, ch04
  • Configuration Management / Order 1800.66 → ch02, ch06
  • Demarcation point → ch03
  • Facility IRD (no ICD) → ch01, ch03, ch06
  • Front matter / TOC outlines → ch02
  • Interface Control Document (ICD) → ch01, ch04
  • Interface Management → ch01, ch06
  • Interface Requirements Document (IRD) → ch01, ch03
  • Interface Working Group roles → ch06
  • N/A and TBS language → ch01, ch02
  • Power / connectors / grounding / EMC → ch03, ch04
  • Requirements Traceability / VRTM → ch05
  • Security requirements at interfaces → ch03, ch04
  • Service / web service interfaces → ch03, ch04
  • Verification levels (dev/integration/site) → ch05
  • Verb discipline (shall vs is/are) → ch01, ch04

Supporting Files


Scope & Limits

This pack covers FAA-STD-025f (November 30, 2007) — Preparation of Interface Documentation — as synthesized reference notes from the everyspec mirror of Rev F (64 pages per extraction metadata). It does not cover: full text of FAA-STD-005 / FAA-STD-002 / FAA-G-2100; the complete FAA Order 1800.66 CM procedure set; non-FAA interface control standards (e.g., generic MIL ICD practices beyond this FAA standard); or program-specific IRD/ICD instances. US Government public domain work. No source-material download link is published.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

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月9日 更新

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月9日 更新

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月9日 更新

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月9日 更新

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月9日 更新

Knowledge base from the DoD Digital Engineering Strategy (2018, OUSD/ODASD(SE)). Use for the Department of Defense's five digital engineering goals — (1) formalize the development, integration, and use of models; (2) provide an enduring authoritative source of truth; (3) incorporate technological innovation; (4) establish supporting infrastructure and environments; (5) transform the culture and workforce — plus 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. Does NOT provide a how-to method, tool tutorials, MBSE/SysML mechanics, or implementation-plan content; thin on metrics, acquisition-policy detail, and step-by-step procedure. Excludes the CAC-gated Digital Engineering Body of Knowledge (DEBoK).

日本語の概要は準備中です。原文の説明を表示しています。

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

jgsystemsconsulting のスキルをすべて見る

このスキルの問題を報告する