|11 Design Analyses and Updates|
Required analyses: Stress/Strength, Worst Case Tolerance, Sneak
Circuit, FMECA/FMEA, Thermal, Logistics Support Analysis (LSA), System
Safety, Integrated Diagnostics & Testability (ID/T). Others
(e.g. Fault Tree, mass properties, etc.) performed as needed. All
results are documented and maintained throughout program's life.
Results are checked against program's Design Manual criteria to ensure
compliance with program requirements. Analyses are scheduled and
performed to support design effort and agenda of design reviews.
Computer-Aided Design/Computer-Aided Engineering tools are used to perform
analyses whenever possible. Design updates will be documented using
CAD/CAE when possible.
|12 Specifications Tree|
Based on PIDS, a complete set of specifications including
hardware/software interfaces, testing, and functional requirements is
developed down to the Shop-Replaceable Assembly (SRA) level. BIT
allocations/requirments defined at each level.
|13 Integrated Test Plan (ITP)|
A complete ITP is developed and maintained, addressing, for example,
all development, qualification and acceptance testing to be performed by
the company, subcontractors and the government, Development Test and
Evaluation (DT&E) and Operational Test and Evaluation (OT&E);
support equipment/special test equipment evaluation, acceptance testing
etc. The ITP also identifies critical test resources and schedule
constraints, missing and redundant test efforts, and documented use of
similarity of design to justify lack of testing. Requires government
approval; calls for as much government participation in testing as is
|14 Program Plans|
Plans (e.g. safety, reliability, testability, human factors, etc.)
address performance parameters which are proven during System
Qualification Testing. Items on the list address specific system
needs and may show up as deliverable data items. Project management
decides which plans will be developed and maintains written justification
for excluding any plan. Plans are released, included, and
government-approved as part of the Transition Plan.
|15 Level Breakdowns for Hardware and
Software (HW/SW) |
Various HW/SW level breakdowns aredeveloped at different stages in the
design process to give project management personnel top-down and bottom-up
perspectives on how the system physically comes together. Each level
breakdown must reflect agreement among design, production and
manufacturing, software, and logistics disciplines and reflect contact
requirements and specifications as they are understood by the contractor
and the government at that time. Component level breakdowns serve as
the basis for writing critical item development specs. Functional,
allocated, and product baselines are generated to provide inputs to the
life cycle cost analysis and configuration control mechanism.
|16 Life Cycle Cost (LCC)
Analysis tool used to incorporate design, operation, and support cost
impacts into the design process. All modernization activities will
be checked with LCC. LCC tradeoffs traceable back to customer
requirements via interplay between specifications tree,
level breakdown, and LCC analyses.
Internal and governement required reviews are scheduled for hardware
and software; Government required reviews are conducted per MIL-STD
1521. Agendas include all company and government concerns. A
review should not be scheduled before activities supporting its objectives
have been conducted. Technical issues are presented in a manner that
matches the audience's technical expertise and fosters
understanding. All disciplines that play a role in the transition to
production should have input to the reviews.
|18 Post Award Conferences|
There are two types of post award conferences:
- Government conference follows proposed system review. Purpose
is to discuss technical and funding/provisioning issues, schedule field
visits, and agree on program schedule.
- Supplier (subcontractor) conference follows detail design
review. Purpose is to verify all appropriate contract
requirements, inform/remind suppliers of incoming inspections policy,
introduce suppliers to individual points of contact in the company, and
discuss quick reaction capabilities.
|19 Technical Database|
A technical database is established at the time of contract award and
maintained by configuration and data management personnel. It
contains such information as MIL-SPECS, PIDS and Spec Tree (and related
profiles), data deliverables, program memos/reports, information for
design reviews and PRR, etc. All relevant tiems are included in the
database when available and updated when appropriate. Database
information should all be current prior to each internal and government
required design review.
|20 Critical Items List|
A critical items list is developed and continuously maintained.
The list must include any item of high technical tisk with no work around,
any item with a schedule/delivery risk --- sole source, all
high-failure-rate items (connectors and cables automatically on list), and
all Safety-of-Flight material. Trade studies and lessons learned are
incorporated to ensure all critical items are identified at appropriate
stages for consideration by program