45N_CDRL_A006.doc

CONTRACT DATA REQUIREMENTS LIST

FORM APPROVED

OMB No.0704-0188

Public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instruction, searching existing data sources, gathering and maintaining the data needed and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden to, Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington, VA 22202-4302, and to the Office of Management and Budget, Paperwork Reduction Project (0704-0188), Washington, DC 20503. Please DO NOT RETURN your form to either of these addresses. Send completed form to the Government Issuing Contract Office for the Contract/PR No. listed in Block E.

TBD

1. DATA ITEM NO.

A006

2. TITLE OF DATA ITEM

Technical Review Presentation Package (TRPP)

3. SUBTITLE

System Engineer Products

4. AUTHORITY (DATA ACQUISITION DOCUMENT NO.)

DI-SESS-82168

5. CONTRACT REFERENCE

See BLK 16

6. REQUIRING OFFICE

AD4.5.14

7. DD 250 REQ

LT

9. DIST STATEMENT REQUIRED

10. FREQUENCY

ONE/R

12 DATE OF FIRST

See BLK 16

14. DISTRIBUTION

b. COPIES

8. APP CODE

A

13. DATE OF SUBSEQUENT See BLK 16

Reg Repro

16. REMARKS

BLOCK 4: Contractor format acceptable. Data Item Description cited as a guide only.

BLOCK 5: SOW Para 3.3.1.3, 3.3.1.3.1, 3.3.1.3.2, 3.3.1.4 - 3.3.1.7, 3.3.2.4 BLOCK 8: and 13: The Government has 45 working days for review and acceptance or rejection. Contractor has 30 days for re-submittal if accepted with comments or rejected.

BLOCK 9: DISTRIBUTION STATEMENT D, Department of Defense and U.S. DoD contractors only (Critical Technology) (Date). Other requests shall be referred to (Cognizant Program Office assigned at time of award).

BLOCK 12: Report to be submitted NLT 45 days after completing studies, research, development, test and evaluation.

BLOCK 14: One (1) soft copy (Reg). Soft copy shall be delivered in the original and modifiable application (e.g., Microsoft Office, AutoCAD, etc.) to:

Building 2185 RM 1130

22347 Cedar Point Road

Patuxent River, MD 20670

DESTRUCTION NOTICE: Follow the procedures in DoD 5220.22-M, NISPOM, Section 5-705.

4.5.14 (See Block 16)

15.TOTAL

G. PREPARED BY

H. DATE

14 September 2018

I. APPROVED BY

J. DATE

DD FORM 1423, JUN 90 Previous editions are obsolete Page of Pages

17. PRICE GROUP

18. ESTIMATED

TOTAL PRICE

_1598688464.pdf

DATA ITEM DESCRIPTION

Title: TECHNICAL REVIEW PRESENTATION PACKAGE (TRPP)

Number: DI-SESS-82168 Approval Date: 20171117

AMSC Number: N9874 Limitation: N/A

DTIC Applicable: N/A GIPDEP Applicable: N/A

Preparing Activity: AS Project Number: SESS-2017-025

Applicable Forms: N/A

Use/Relationship: The Technical Review Presentation Package (TRPP) is used by the government to determine and ensure that the emerging system has demonstrated sufficient maturity to enter the next phase of development.

This Data Item Description (DID) contains the format and content preparation instructions for the data product resulting from the discrete task requirements as delineated in the contract. This DID covers all presentation material for Systems Engineering Technical Review Processes (SETRs) and all other technical reviews.

Requirements:

1. Reference documents. The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.

1.1 NAVAIRINST 4355.19E - Systems Engineering Technical Review (SETR) Process.

2. Format. The TRPP shall be in contractor’s format.

3. Content. The TRPP shall contain the following sections:

3.1. Section 1 – Alternative System Review (ASR). The ASR section of the TRPP shall contain the following:

a. System purpose.

b. Existing system shortfalls.

c. Threat/Targets.

d. Operational requirements status.

e. ConOps.

f. Operational Mode Summary/Mission Profile.

g. Sustainment Strategy.

h. RAM-C.

i. System architecture of each alternative concept.

j. Key technologies for each alternative concept.

k. Technology risk and abatement approaches.

l. Approach to estimating performance aspect of the system concepts and their architectures.

m. Key metrics and how they were measured.

Source: https://assist.dla.mil -- Downloaded: 2018-09-17T15:19Z Check the source to verify that this is the current version before use.

DI-SESS-82168

n. Estimates of performance for each system concept.

o. System and human performance estimates for the best overall system concept alternative.

p. Operational impacts to the selection of each concept alternative.

q. Key Information Assurance (IA) considerations that impact the certification and accreditation risks for concept alternatives.

r. Technical performance measures to assess Hardware (HW), Software (SW) and human performance.

s. Risk assessment measures to assess risk and the effectiveness of mitigation upon those risks.

t. Alternative selection decision approach.

u. Preferred concept selection and standing.

v. Technical review team recommendation of the preferred concept.

w. Status of the requirements documentation along with the development and approval schedule and document hierarchy scheme.

x. Key system technical and IA requirements and allocations to subsystems.

y. An overview of the proposed system development, acquisition schedule, and test and operational evaluation.

z. Detailed schedule and costs associated with the next phase of development.

aa. Overall acquisition cost and plans for completion.

bb. Technical review team recommendation on the system development plans.

3.2. Section 2 – System Requirements Review (SRR). The SRR section of the TRPP shall contain the following:

a. System mission.

b. Agenda.

c. Entrance and Exit criteria.

d. Integrated Master Schedule.

e. Draft Subsystem Specification.

f. Trade Study.

g. Design Reference Mission (DRM).

h. Mission Threads.

i. Reliability and Maintainability Program Plan, including Reliability Growth Plan.

j. Preliminary Reliability and Maintainability Allocations.

k. Preliminary Reliability and Maintainability Block Diagrams.

l. R&M Engineering.

m. Availability/Readiness.

n. Manufacturing.

o. Quality.

p. Functional Definitions.

q. Draft Logistics Strategy.

r. System Safety Impacts.

s. Risks and Associated Mitigation Strategies.

t. Operational views and documentation of the operational requirements.

u. Scenarios, campaigns, and threats that comprise the DRM for the system, the manner in which the DRM shall be utilized in subsequent system development, and development status.

v. Description of the capability development document, system threat assessment report, and concept of operations.

w. Description of the system architecture.

x. System boundaries describing the system apart from other systems and its environment.

y. Internal system structure describing the division of the systems into subsystems, major foreseen interface relationships between the major divisions, and boundaries between security-critical and non-critical functions.

z. Unique states of the system and identification of all static and dynamic modes.

aa. System trades and analyses.

bb. Key performance parameters, technologies, system concept, anticipated human performance requirements, and the differences between the system concept used at the

SRR and the ASR.

cc. Results of the system effectiveness and performance assessment.

dd. Status of the development of the requirements documentation.

ee. Identification of the required threat and the IA threat.

ff. System capability requirements.

gg. Requirements not related to mission capabilities.

hh. How the system requirements will be qualified.

ii. Description of the process of the allocation of requirements from the system-level to the subsystem level and major system requirements allocations to subsystems.

jj. Remaining schedule of the entire system development and acquisition.

kk. Near term schedule and costs plans for the next phase of development.

ll. Estimation of cost and progress for the overall acquisition program.

mm. Description of the approach to management of the system requirements, architecture, design, and the special configuration management requirements of security-critical elements.

3.3. Section 3 – System Functional Review (SFR). The SFR is the functional baseline and this section of the TRPP shall contain the following:

a. Agenda.

b. Entrance and Exit criteria.

c. Integrated Master Schedule.

d. Draft Subsystem Specification.

e. Trade Study.

f. Mass Properties.

g. Functional Definitions.

h. Draft Logistics Strategy.

i. Description of Health Management functional requirements.

j. Final R&M Allocations.

k. Final R&M Block Diagrams.

l. Product support functional requirements.

m. Use Cases (e.g. Day in the life of the maintainer, etc.).

n. Design Reference Mission.

o. System Safety Impacts.

p. Risks and Associated Mitigation Strategies

q. Description of the functional architecture.

r. Performance specifications.

s. System Requirements Document (SRD).

t. Draft prime item performance and prime item detail specifications.

u. Design data defining the overall system.

v. Risk assessment results.

w. Risk mitigation plans.

x. Trade studies and analyses.

y. Technical performance measurements.

z. Draft enabling product plans, Systems Engineering Plan (SEP) and a summary of comments.

3.4. Section 4 – Software Specification Review (SSR). The SSR section of the TRPP shall contain

a. Description of the system architecture.

b. An overview of the system requirements.

c. Growths of requirements for each system build.

d. The error/failure handling concept for the Software Development Plan (SDP).

e. Allocation of system requirements to Software Configuration Items (SCIs).

f. Identification of security-critical and non-critical SCIs.

g. Interfaces between the Configuration Items (CIs), broken out into builds.

h. Layers of the architecture, if layers have been defined.

i. User interfaces, including displays and the rational for their selection.

j. Operator job descriptions, based on functions allocated to humans.

k. Planned locations for new and reused software, Commercial Off-The-Shelf (COTS), Non-Developmental Items (NDI), legacy equipment, and Government Furnished

Information (GFI).

l. Plans for how reused software will meet IA requirements.

m. An overview of the SCI requirements, both functional and IA.

n. Where the SCI fits into the system architecture and the system build plan.

o. Description of how the system requirements are allocated to the various CIs.

p. A breakdown of how the requirements are allocated across builds.

q. References defining which Software Requirements Specification (SRS) requirements are allocated to which builds.

r. System requirements changes made since the SFR.

s. Safety critical requirements.

t. Quality requirements (including reliability, availability, maintainability).

u. Requirements supporting test and analysis.

v. Human Machine Interface (HMI) requirements.

w. How the build plan for the SCI is consistent with the overall system build plan.

x. Dates when technical agreements are needed on the content of the various requirements and design documentation artifacts.

y. Description of the software development processes/methods and tools that will be used, as documented in the Software Development Plan (SDP).

z. Explanation of any process and tool changes made since the SDP was released, why the changes were made, and an assessment of the impact of these changes on the SDP.

aa. Processes and measures to be used in developing the HMI and evaluating its usability and impact on operator performance and workload.

bb. Progress made in SCI development compared to the plan defined in the system development landscape.

cc. Requirements and implementation constraints allocated to the SCI.

dd. Performance requirements of the SCI.

ee. Test approaches planned for qualification of the requirements

ff. Summary of the risk items and mitigation plans identified for the SCI that will impact successful completion of the SCI.

3.5. Section 5 –Preliminary Design Review (PDR). The PDR is the allocated baseline and this section of the TRPP shall contain the following:

d. CDRL Status.

e. Final Subsystem Specification.

f. Draft Assessment Plan.

g. Trade Study.

h. Preliminary Product Drawings/Models and Associated Lists.

i. Mass Properties.

j. Preliminary Reliability and Maintainability Predictions.

k. Preliminary Testability Analysis.

l. Parts Management Plan.

m. Producibility Impacts

n. Producibility Plan

o. Manufacturing Technology Availability.

p. Industrial Capabilities.

q. Draft Allocation Report.

r. Draft Failure Mode Effects and Criticality Analysis (FMECA).

s. Failure Reporting, Analysis and Corrective Action System (FRACAS).

t. Draft Reliability and Maintainability Test Plan.

u. Draft Maintainability and Testability Demonstration Plan.

v. Draft Logistics Strategy.

w. Draft Incorporation Plan.

x. System Safety Impacts.

y. Risks and Associated Mitigation Strategies.

z. Description of the system architecture.

aa. An overview of the total system requirements.

bb. Allocation of requirements to each of the hardware and software configuration items

(HWCIs & SCIs).

cc. Allocation of requirements to any SCI hosted by the HWCI.

dd. User interfaces, including displays.

ee. Growths of requirements for each system build.

ff. Interfaces between the CIs, broken out into builds.

gg. Layers of the architecture (if layers have been defined).

hh. Connectivity among system HWCIs as defined in the Interface Design Specifications

(IDSs).

ii. Identification of all NDIs, Government Furnished Equipment (GFE), and legacy equipment.

jj. Identification of all Computer Software Components (CSCs).

kk. Operator and maintainer job descriptions.

ll. An overview of the HWCI & SCI requirements and any associated SCI/firmware documentation.

mm. Where the HWCIs & SCIs fit into the system architecture and system development schedule.

nn. How the system requirements are allocated to the various HWCIs.

oo. A breakdown of how the requirements are allocated across builds.

pp. Documentation defining which SRS requirements are allocated to which builds.

qq. Documentation defining the SCI’s architecture.

rr. Requirements applicable to the production equipment, but not the Engineering

Development Model (EDM).

ss. A breakdown of the requirements relative to SCI/firmware builds associated with the particular HWCI.

tt. Requirement changes made since the SSR.

uu. Safety critical requirements.

vv. Quality requirements (including reliability, availability and maintainability).

ww. Requirements supporting test and analysis.

xx. Design error budgets for meeting allocated requirements.

yy. Ship integration requirements.

zz. System security/IA requirements.

aaa. Environmental requirements.

bbb. Explanation of any process and tool changes that have been made since the SSR, why the changes were made, and an assessment of the impact of these changes on the SDP.

ccc. How the equipment and SCI/firmware build plans for the HWCI are consistent with the overall SDP.

ddd. Dates when technical agreements are needed on the content of the various requirements and design documentation.

eee. Description of the equipment and software development process/methods and tools that are to be used, as documented in the SDP.

fff. Description of the measures to be used in assessing human performance and operator workload (cognitive/temporal/physical).

ggg. An overview of the system architecture.

hhh. Description of the processes and methodologies for assessing the ergonomics and operational suitability of the hardware configurations.

iii. Description of the intra-HCI & intra-SCI landscape.

jjj. Where, within the architecture, development/new and reuse components will be located, including NAVSEA Data Environment, NDI, COTS, legacy equipment and GFE.

kkk. Locations of new and reused software, including COTS, NDI, legacy, and GFI.

lll. How reused components and CIs will meet IA requirements.

mmm. Where industry and government standards are applied.

nnn. Description of the maturity of the functional/subsystem design.

ooo. Description of the HWCI’s/SCI’s performance requirements, including design margins.

ppp. Metrics to include plan vs. specified parameters, Earned Value Metrics (EVMs), and the programs’ Work Breakdown Structure (WBS).

qqq. Summary of the risk items identified for the HWCI & SCI that impact successful completion of the HWCI.

rrr. Test approaches planned for the HWCI and SCI testing.

sss. Lower-level tests to be performed on the HWCI and SCI components, modules and subsystems from unit-level to top-level.

ttt. Degree of functional and environmental coverage planned for the tests.

3.6. Section 6 – Hardware Critical Design Review (HCDR). The HCDR is the product baseline and this section of the TRPP shall contain the following:

d. CDRL Status.

e. Final Assessment Plan.

f. Draft Assessment Report.

g. Final Product Drawings/Models and Associated Lists.

h. Mass Properties.

i. Organizational description of operators and maintainers associated with the system.

j. Update producibility plan

k. Final Reliability and Maintainability Predictions.

l. Final Allocation Report.

m. Final Failure Mode Effects and Criticality Analysis (FMECA).

n. Failure Reporting, Analysis and Corrective Action System (FRACAS).

o. Final Reliability and Maintainability Test Plan.

p. Final Maintainability and Testability Demonstration Plan.

q. Draft Manufacturing Plan.

r. Draft Producibility & Quality Plan.

s. Draft Subcontractor Management Plan.

t. Draft Logistics Strategy.

u. Draft Incorporation Plan.

v. Final Testability Analysis.

w. Final parts management Plan.

x. Growth of requirements for each system build including any training required.

y. System Safety Impacts.

z. Risks and Associated Mitigation Strategies.

aa. Description of the system architecture.

bb. An overview of the total system requirements as defined in the system specifications.

cc. Allocation of system requirements to each of the CIs comprising the system.

dd. User interfaces, including displays.

ee. Interfaces between the SCIs, broken out into builds.

ff. Connectivity among system HCIs.

gg. Layers of the architecture (if layers have been defined).

hh. Identification of all NDIs, GFE, and legacy equipment.

ii. An overview of the HCI requirements and associated SCI and firmware documentation.

jj. Where the HCI fits into the system architecture and the system development schedule.

kk. How the system requirements are allocated to the various HCIs.

ll. Requirements applicable to the production equipment, but not the EDM.

mm. An overview of the SCI requirements.

nn. A breakdown of the requirements relative to SCI/Firmware builds associated with the particular HCI.

oo. A breakdown of how the requirements are allocated across builds.

pp. Documentation defining which SRS requirements is allocated to which builds.

qq. Where the SCI fits into the system architecture and system build plan.

rr. Requirements changes made since PDR.

ss. Safety critical requirements.

tt. Quality requirements (including reliability, availability and maintainability).

uu. Requirements supporting test and analysis.

vv. Design error budgets for meeting allocated requirements.

ww. Ship integration requirements.

xx. System security/IA requirements.

yy. Environmental requirements.

zz. Processes for assessing the ergonomics and suitability of hardware configurations.

aaa. How the equipment and SCI/firmware build plans for the HCI is consistent with the overall SDP.

bbb. Dates when technical agreements are needed on the content of the various requirements ccc. Equipment/Software development process/methods being followed and tools that are to be used, as documented in the SDP.

ddd. Detailed explanation of any process and tool changes that have been made since the

PDR, including rationale on why the changes are made and an assessment of the impact of these changes on the development plan.

eee. Description of the intra-HCI & intra-SCI landscape.

fff. An overview of the HCI's configuration.

ggg. Documentation defining the SCI’s architecture.

hhh. Identification of all CSCs.

iii. Identification of HCIs.

jjj. Where, within the architecture, development and reuse components will be located.

kkk. Locations of new and reused software, including COTS, NDI, legacy, and GFI.

lll. Plans for how reused components/software will meet IA requirements.

mmm. How reused HCIs will meet IA requirements.

nnn. Where industry and government standards are applied.

ooo. Description of the test plans and procedures that will be applied to the HCI.

ppp. Test approaches planned for the CIs.

qqq. FQT descriptions.

rrr. Lower-level tests to be performed on the CI components, modules and subsystems.

sss. Maturity of the functional/subsystem design.

ttt. Description of the performance requirements.

uuu. Software/Hardware metrics appropriate to the particular development.

vvv. Summary of the risk database items identified that impact successful completion of the

HCI.

www. Risk items for the SCI that will impact successful completion of the SCI.

3.7. Section 7 – Production Readiness Review (PRR). The TRPP for the Production Readiness

Review shall include no less than the following:

d. Production screens and tests.

e. Final Reliability and Maintainability Test Report.

f. Final Maintainability and Testability Demonstration Report.

g. Failure Reporting, Analysis and Corrective Action System (FRACAS).

h. Final manufacturing Plan.

i. Final Producibility & Quality Plan.

j. Final Subcontractor management Plan.

k. Logistics Strategy.

l. Final Incorporation Plan.

m. System Safety Impacts.

n. Risks and Associated Mitigation Strategies.

3.8. Section 8 – Test Readiness Review (TRR). The TRR section of the TRPP shall contain the following:

b. An overview of the total system requirements.

c. Test Schedule.

d. FRACAS Plan.

e. Organizational description of operators and maintainers associated with the system.

f. Allocation of system requirements to the CI.

g. User interfaces, including displays.

h. Connectivity among system CIs as defined in the IDSs.

i. Identification of all NDIs, GFE, and legacy equipment.

j. An overview the CI functional and performance requirements.

k. Associated SCI and firmware documentation.

l. How the test and evaluation management plan are allocated to the various CIs.

m. Requirements changes made since the CDR.

n. Security requirements.

o. Environmental requirements.

p. Safety critical requirements.

q. Quality requirements (including reliability, availability and maintainability).

r. Requirements supporting test and analysis.

s. Summary of risk items and mitigation plans that impact successful completion of the system.

t. Test approaches planned for the system.

3.9. Section 9 – Functional Configuration Audit (FCA). The FCA section of the TRPP shall contain the following:

b. Description of the system production process/methods and tools to be used.

c. Explanation of process and tool changes since the SDP was released, why the changes were made, and an assessment of the impact of these changes.

d. Test approaches planned for the system.

e. A summary of the risk items and mitigation plans that will impact successful completion of the system mission.

3.10. Section 10 – Physical Configuration Audit (PCA). The PCA section of the TRPP shall contain

b. An overview of the total system requirements.

c. Allocation of system requirements to each of the CIs comprising the system.

d. User interfaces, including displays.

e. Connectivity among system CIs as defined in the in IDSs.

f. Identification of all NDIs, GFE, and legacy equipment.

g. Description of the system production and deployment process/methods and tools to be used, as documented in the SDP.

h. Explanation of process and tool changes that have been made since the SDP was released, why the changes were made, and an assessment of the impact of these changes on the SDP.

i. Description of the processes to be used in developing HMI and its usability.

j. An overview of the CI’s functional and performance requirements.

k. Specifications of interfaces and protocols.

l. Additions and changes made to COTS equipment, including market research and upgrade strategy.

m. Where the CI fits into the system and system production and deployment schedules.

n. How the equipment and SCI/firmware build plans for the CI are consistent with the overall system production plan.

o. Dates when technical agreements are needed on the content of the various requirements

p. Summary of the risk items and mitigation plans that impact successful completion of the

SCI.

q. Test approaches planned for the system.

3.11. Section 11 - Content Definitions shall contain the following:

a. Agenda. The Agenda includes topics of discussion for the design review/technical interchange meeting and proposed lengths of discussion.

b. Entrance and Exit Criteria. The Entrance and Exit Criteria includes the criteria for entrance and exit from any event, milestone, or task necessary for the development of the design change to proceed in accordance with the Systems Engineering Strategy.

c. Integrated Master Schedule. The Integrated Master Schedule includes all scheduled tasks, at the corresponding level, and milestones, with predecessors and successors assigned, necessary for the development of the design and the critical path of those tasks to meet desired maturity in accordance with the proposed schedule.

d. Subsystem Specification. The Subsystem Specification includes all of the requirements for the design change, the methods to verify and validate those requirements, and how the requirements trace back to higher level specifications, the Government provided component specification, and standards that define the requirements.

e. Trade Study Status. The Trade Study Status includes the trade-offs being considered, the method of conducting the trade study, and the results of the trade study.

f. Functional Block Diagram. The Functional Block Diagram includes all of the functions required of the design change and how those functions trace back to the functions of the overall system.

g. Functional Definitions. The Functional Definitions includes all of the functions to be performed by the design change and a description of that function in relation to the overall function of the system.

h. Logistics Strategy. The Logistics Strategy provides the current status of all 12 ILS

Elements (Maintenance Planning, Supply Support, Packaging, Handling, Storage &

Transportation, Production Support Management, Sustainment Engineering, Computer

Resources, Tech Data, Design Interface, Facilities, Manpower & Personnel, Support

Equipment, and Training & Training Support)

i. Risks and Associated Mitigation Strategies. The Risks and Associated Mitigation

Strategies includes all technical, cost, and schedule risks associated with the program, including probability and consequence, the mitigation plan/method(s) of reducing the risk to an acceptable level, and the mitigated risk level.

j. Product Drawings/Models and Associated Lists. The Product Drawings/Models and

Associated Lists includes all drawings and/or models of the design and lists associated with those drawings that are required to be able to produce and qualify the new component(s)/system.

k. Assessment Plan. The Assessment Plan includes all planned requirement validation activities, the procedures or methods to perform those activities, and the artifacts that will contain the results from the assessment activities.

l. Assessment Report. The Assessment Report includes the results and success criteria from all the requirements validation activities.

m. Manufacturing Plan. The Manufacturing Plan identifies the contractor's overall manufacturing system and detailed factors necessary to achieve an effective and efficient manufacturing program. The Plan includes the sequence and schedule of events that define availability/use of materials, fabrication flow, test equipment, tools, facilities, and personnel.

n. Producibility & Quality Plan. The Producibility & Quality Plan includes methods to ensure the end product is designed in such a manner that fabrication and manufacturing methods and processes have necessary flexibility in producing the product at a reasonable cost while maintaining the required functionality, performance, quality, and reliability. The plan also identifies and document key characteristics, if any, of the design.

o. System Safety Impacts. System Safety Impact: is characterizes as system's hazards, potential mishaps resulting from hazard and their causal factors. MIL-STD-882E outlines the System Safety practice (hardware and software), the respective hazard analyses that can be performed depending upon the system, its architecture (hardware or software), and the hazards incumbent in that system. These analyses are leveraged in the Systems Engineering (SE) process to mitigate or eliminate hazards and facilitate the characterizing of the resultant risk from hazards remaining as a result of the SE process.

p. Subcontractor Management Plan. The Subcontractor Management Plan includes the

Contractor’s plan to manage all subcontractor’s quality and manufacturing capabilities in accordance with the Contractor’s quality and manufacturing plans.

q. Reliability and Maintainability Program Plan. The Reliability and Maintainability

Program Plan defines the roles, responsibilities and systems engineering approach associated with the development and growth of reliability and implementation of maintainability.

r. Reliability and Maintainability Predictions. The Reliability and Maintainability

Predictions evaluates the reliability and maintainability of the design by assigning probabilities and resulting effects on the system.

s. Allocation Report. The Allocation Report documents the methods and results of the allocation of the reliability, maintainability and testability requirements. End item quantitative requirements must be broken down to appropriate system/subsystem/unit levels necessary to establish requirements for designers and subcontractors.

t. Failure Mode Effects and Criticality Analysis (FMECA). The Failure Mode Effects and

Criticality Analysis (FMECA) identifies potential failure modes for a system to assess the risk associated with those failure modes, rank the failure modes in terms of criticality and to identify and carry out corrective actions to address the most serious concerns.

u. Failure Reporting, Analysis and Corrective Action System (FRACAS). The Failure

Reporting, Analysis and Corrective Action identifies the process for reporting, classifying and analyzing failures and planning corrective actions in response to those failures.

v. Reliability and Maintainability Test Plan. The Reliability and Maintainability Test Plan describes the necessary tasks, responsibilities, procedures and controls that should be implemented for the specified test.

w. Reliability and Maintainability Test Report. The Reliability and Maintainability Test

Report describes the tasks, tasks, responsibilities, procedures and controls utilized during and the results of the specified tests from the

x. Maintainability and Testability Demonstration Plan. The Maintainability and Testability

Demonstration Plan describes the necessary tasks, responsibilities, procedures and controls that should be implemented for the specified demonstration.

y. Maintainability and Testability Demonstration Report. The Maintainability and

Testability Demonstration Report describes the tasks, responsibilities, procedures and controls that were utilized during and the results of the specified demonstration.

z. Block Diagrams and Math Models. The Block Diagrams and Math Models Modeling models the system by decomposing the overall system into individual subsystems to demonstrate how individual component reliability contributes to the success or failure of the system.

End of DI-SESS-82168