본문으로 건너뛰기
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.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고