Systems Integration Dependency Mapper
Map aerospace subsystem dependencies and identify integration risks
What You Can Do
You can systematically map dependencies between dozens of subsystems, visualize integration relationships through structured dependency matrices, quantify integration risk exposure, and generate optimal integration sequences that minimize schedule risk. This skill understands aerospace-specific challenges like avionics coupling, power distribution constraints, thermal interdependencies, and certification requirements—transforming interface specifications into actionable integration plans before hardware arrives.
Features
Creates structured matrices showing subsystem-to-subsystem relationships, interface types, and coupling strength to expose hidden dependencies
Assesses technical risk, schedule risk, and interface conflict probability to prioritize mitigation efforts
Generates integration build sequences that reduce critical path and minimize rework by ordering subsystem integration based on dependencies
Identifies power, thermal, mechanical, and data bus conflicts between specifications to catch integration issues at PDR/CDR stage
Accounts for avionics coupling, power distribution constraints, thermal interdependencies, and certification documentation requirements
Analyzes interface control documents to identify missing specifications, ambiguous requirements, and vendor compatibility issues
Generates test sequence recommendations based on dependency hierarchy to validate subsystems in logical integration order
Maps how specification changes ripple across dependent subsystems to quantify downstream integration risk
Example Output
Example 1: Dependency Matrix Output
Subsystem A (Flight Control) → Subsystem B (Avionics Bus): Power, Data, Mechanical
Coupling Strength: HIGH | Risk Score: 8/10 | Critical Interface: CAN Bus 1
Subsystem C (Power Dist) → Subsystem D (Thermal Mgmt): Power, Thermal
Coupling Strength: MEDIUM | Risk Score: 6/10 | Bottleneck: 28V DC Line
Example 2: Integration Sequence
Phase 1 (Week 1-2): Power Distribution System + Structure
Phase 2 (Week 3-4): Thermal Management + Power Dist
Phase 3 (Week 5-6): Avionics Bus + Power/Thermal
Phase 4 (Week 7-8): Flight Control + Avionics/Power
Risk Reduction: 35% | Critical Path Compression: 2 weeks
Example 3: Interface Conflict Report
- ⚠️ HIGH: Flight Control expects 28V±2V, Power Dist spec shows 28V±3V
- ⚠️ MEDIUM: Thermal margin overlap between Avionics (60°C limit) and Power Dist (65°C output)
✓ RESOLVED: CAN Bus timeout parameters aligned across 4 subsystems
What's Included
- SKILL.md: Complete integration analysis workflow and methodology
- Dependency Matrix Template: Structured Excel/CSV template for subsystem-to-subsystem mapping with risk scoring
- Integration Risk Assessment Framework: Checklist for technical, schedule, and interface conflict evaluation
- Interface Conflict Detection Checklist: Aerospace-specific verification list (power, thermal, mechanical, data, certification)
- Integration Sequence Optimization Worksheet: Dependency-based sequencing logic with critical path analysis
Who It's For
- Systems Integration Engineers — Planning and executing aerospace platform integration with multiple vendors and subsystems
- Program Integration Managers — Coordinating integration risks, schedules, and interface changes across project phases
- Chief Engineers & Technical Leads — Assessing integration complexity at PDR/CDR and identifying potential rework risks
- Interface Management Teams — Developing and validating interface control documents and managing specification changes
- Test Engineers — Planning optimal integration test sequences based on subsystem dependencies
Best For
- Phase Integration Planning — PDR/CDR stage dependency mapping and risk assessment before hardware integration
- Integration Conflict Resolution — Identifying root causes of test failures involving multiple subsystems and mapping impacts
- Change Impact Assessment — Quantifying downstream effects of specification changes across dependent subsystems
- Vendor Onboarding — Analyzing compatibility of new subsystems with existing platform interfaces and dependencies
- Integration Test Sequencing — Generating build sequences that validate subsystems in logical order and reduce critical path
You might also like
You can rapidly validate FEA model inputs, boundary conditions, and mesh strategies before expensive simulations run. Claude analyzes your model documentation, interprets stress concentrations and failure predictions against design criteria, maps results to certification requirements (FAA Part 23/25, DO-254, MIL-STD-1916), and identifies root causes for convergence issues or anomalous results. This compresses the 20-30% of analysis time typically spent on verification and documentation.
by a7garden
You can rapidly examine thousands of instrumentation parameters across multiple test points to isolate unexpected behaviors and their origins. Claude structures the detective work: asking conditional questions about parameter relationships, flagging impossible states, isolating anomaly emergence moments, and building logical chains connecting symptoms to root causes. The output produces defensible technical justifications suitable for FAA or military certification packages and flight test reports.
by a7garden
You can analyze static and fatigue test data from aerospace components, distinguish between real failure modes and test artifacts, establish statistical confidence in results, and generate certification-ready engineering reports. The skill helps you interpret physical behavior under load, determine root causes of structural failures, and validate finite element predictions against test evidence—enabling design review boards and certification authorities to make informed decisions.
by a7garden
You can conduct rapid fatigue life assessments, apply damage tolerance principles per AC 25.571-1D methodology, and predict residual strength of aircraft structures under cyclic loading. This skill organizes fatigue data interpretation, applies appropriate failure theories, calculates safety margins, and documents analysis assumptions for certification compliance—reducing analysis time while maintaining the rigor required for structural certification and service life determination.
by a7garden
You can master professional podcast audio editing, mixing, and mastering workflows using Audacity with Claude-guided processes that transform raw recordings into broadcast-quality episodes. Claude provides step-by-step instructions for noise reduction, multi-track mixing, dynamic range control, and mastering optimization tailored to your podcast's mic setup and distribution requirements. Automate repetitive editing tasks and achieve consistent audio quality across entire episode catalogs.
by a7garden
You can systematically diagnose avionics system failures by organizing failure symptoms into decision frameworks that consider hardware, software, and environmental factors simultaneously. The skill generates failure logic trees, maps cross-system dependencies, and produces defensible root cause analysis reports that meet FAA/EASA certification requirements. This transforms ad-hoc troubleshooting into a repeatable, auditable methodology that accelerates fault isolation and supports occurrence reporting.
by a7garden
You can rapidly review FEA stress, strain, and displacement results to spot unrealistic outputs, correlate simulation predictions with test measurements, and identify when design changes or additional testing are warranted. This skill helps you build defensible evidence packages for certification authorities (FAA/EASA/NADCAP) by documenting the correlation between analysis and physical validation, reducing certification delays and safety risks.
by a7garden
You can analyze complex avionics test failures by feeding Claude multiple data streams—oscilloscope traces, BITE logs, CAN/ARINC 429 transcripts, and environmental parameters—to build diagnostic decision trees that prioritize root causes based on failure signatures. Claude helps you cross-reference specifications against observed behavior, identify design-versus-implementation gaps, and generate testable hypotheses with step-by-step verification procedures that accelerate failure resolution across multi-LRU (Line Replaceable Unit) systems.
by a7garden