DI-SESS-82168

Technical Review Presentation Package (TRPP)

Defines the format and content requirements for the presentation package used by the government to determine whether an emerging system has demonstrated sufficient maturity to enter the next development phase.

Approval DateNovember 17, 2017

AMSC NumberN9874

Preparing ActivityAS

Project NumberSESS-2017-025

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable Forms—

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantYes

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

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.

Preparation Instructions

1Reference documentsThe 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.1NAVAIRINST 4355.19E - Systems Engineering Technical Review (SETR) Process

2FormatThe TRPP shall be in contractor's format.

3ContentThe TRPP shall contain the following sections:

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

aSystem purpose

bExisting system shortfalls

cThreat/Targets

dOperational requirements status

eConOps

fOperational Mode Summary/Mission Profile

gSustainment Strategy

hRAM-C

iSystem architecture of each alternative concept

jKey technologies for each alternative concept

kTechnology risk and abatement approaches

lApproach to estimating performance aspect of the system concepts and their architectures

mKey metrics and how they were measured

nEstimates of performance for each system concept

oSystem and human performance estimates for the best overall system concept alternative

pOperational impacts to the selection of each concept alternative

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

rTechnical performance measures to assess Hardware (HW), Software (SW) and human performance

sRisk assessment measures to assess risk and the effectiveness of mitigation upon those risks

tAlternative selection decision approach

uPreferred concept selection and standing

vTechnical review team recommendation of the preferred concept

wStatus of the requirements documentation along with the development and approval schedule and document hierarchy scheme

xKey system technical and IA requirements and allocations to subsystems

yAn overview of the proposed system development, acquisition schedule, and test and operational evaluation

zDetailed schedule and costs associated with the next phase of development

aaOverall acquisition cost and plans for completion

bbTechnical review team recommendation on the system development plans

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

aSystem mission

bAgenda

cEntrance and Exit criteria

dIntegrated Master Schedule

eDraft Subsystem Specification

fTrade Study

gDesign Reference Mission (DRM)

hMission Threads

iReliability and Maintainability Program Plan, including Reliability Growth Plan

jPreliminary Reliability and Maintainability Allocations

kPreliminary Reliability and Maintainability Block Diagrams

lR&M Engineering

mAvailability/Readiness

nManufacturing

oQuality

pFunctional Definitions

qDraft Logistics Strategy

rSystem Safety Impacts

sRisks and Associated Mitigation Strategies

tOperational views and documentation of the operational requirements

uScenarios, 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

vDescription of the capability development document, system threat assessment report, and concept of operations

wDescription of the system architecture

xSystem boundaries describing the system apart from other systems and its environment

yInternal 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

zUnique states of the system and identification of all static and dynamic modes

aaSystem trades and analyses

bbKey performance parameters, technologies, system concept, anticipated human performance requirements, and the differences between the system concept used at the SRR and the ASR

ccResults of the system effectiveness and performance assessment

ddStatus of the development of the requirements documentation

eeIdentification of the required threat and the IA threat

ffSystem capability requirements

ggRequirements not related to mission capabilities

hhHow the system requirements will be qualified

iiDescription of the process of the allocation of requirements from the system-level to the subsystem level and major system requirements allocations to subsystems

jjRemaining schedule of the entire system development and acquisition

kkNear term schedule and costs plans for the next phase of development

llEstimation of cost and progress for the overall acquisition program

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

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

aAgenda

bEntrance and Exit criteria

cIntegrated Master Schedule

dDraft Subsystem Specification

eTrade Study

fMass Properties

gFunctional Definitions

hDraft Logistics Strategy

iDescription of Health Management functional requirements

jFinal R&M Allocations

kFinal R&M Block Diagrams

lProduct support functional requirements

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

nDesign Reference Mission

oSystem Safety Impacts

pRisks and Associated Mitigation Strategies

qDescription of the functional architecture

rPerformance specifications

sSystem Requirements Document (SRD)

tDraft prime item performance and prime item detail specifications

uDesign data defining the overall system

vRisk assessment results

wRisk mitigation plans

xTrade studies and analyses

yTechnical performance measurements

zDraft enabling product plans, Systems Engineering Plan (SEP) and a summary of comments

3.4Section 4 - Software Specification Review (SSR)The SSR section of the TRPP shall contain the following:

aDescription of the system architecture

bAn overview of the system requirements

cGrowths of requirements for each system build

dThe error/failure handling concept for the Software Development Plan (SDP)

eAllocation of system requirements to Software Configuration Items (SCIs)

fIdentification of security-critical and non-critical SCIs

gInterfaces between the Configuration Items (CIs), broken out into builds

hLayers of the architecture, if layers have been defined

iUser interfaces, including displays and the rational for their selection

jOperator job descriptions, based on functions allocated to humans

kPlanned locations for new and reused software, Commercial Off-The-Shelf (COTS), Non-Developmental Items (NDI), legacy equipment, and Government Furnished Information (GFI)

lPlans for how reused software will meet IA requirements

mAn overview of the SCI requirements, both functional and IA

nWhere the SCI fits into the system architecture and the system build plan

oDescription of how the system requirements are allocated to the various CIs

pA breakdown of how the requirements are allocated across builds

qReferences defining which Software Requirements Specification (SRS) requirements are allocated to which builds

rSystem requirements changes made since the SFR

sSafety critical requirements

tQuality requirements (including reliability, availability, maintainability)

uRequirements supporting test and analysis

vHuman Machine Interface (HMI) requirements

wHow the build plan for the SCI is consistent with the overall system build plan

xDates when technical agreements are needed on the content of the various requirements and design documentation artifacts

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

zExplanation 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

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

bbProgress made in SCI development compared to the plan defined in the system development landscape

ccRequirements and implementation constraints allocated to the SCI

ddPerformance requirements of the SCI

eeTest approaches planned for qualification of the requirements

ffSummary of the risk items and mitigation plans identified for the SCI that will impact successful completion of the SCI

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

aAgenda

bEntrance and Exit criteria

cIntegrated Master Schedule

dCDRL Status

eFinal Subsystem Specification

fDraft Assessment Plan

gTrade Study

hPreliminary Product Drawings/Models and Associated Lists

iMass Properties

jPreliminary Reliability and Maintainability Predictions

kPreliminary Testability Analysis

lParts Management Plan

mProducibility Impacts

nProducibility Plan

oManufacturing Technology Availability

pIndustrial Capabilities

qDraft Allocation Report

rDraft Failure Mode Effects and Criticality Analysis (FMECA)

sFailure Reporting, Analysis and Corrective Action System (FRACAS)

tDraft Reliability and Maintainability Test Plan

uDraft Maintainability and Testability Demonstration Plan

vDraft Logistics Strategy

wDraft Incorporation Plan

xSystem Safety Impacts

yRisks and Associated Mitigation Strategies

zDescription of the system architecture

aaAn overview of the total system requirements

bbAllocation of requirements to each of the hardware and software configuration items (HWCIs & SCIs)

ccAllocation of requirements to any SCI hosted by the HWCI

ddUser interfaces, including displays

eeGrowths of requirements for each system build

ffInterfaces between the CIs, broken out into builds

ggLayers of the architecture (if layers have been defined)

hhConnectivity among system HWCIs as defined in the Interface Design Specifications (IDSs)

iiIdentification of all NDIs, Government Furnished Equipment (GFE), and legacy equipment

jjIdentification of all Computer Software Components (CSCs)

kkOperator and maintainer job descriptions

llAn overview of the HWCI & SCI requirements and any associated SCI/firmware documentation

mmWhere the HWCIs & SCIs fit into the system architecture and system development schedule

nnHow the system requirements are allocated to the various HWCIs

ooA breakdown of how the requirements are allocated across builds

ppDocumentation defining which SRS requirements are allocated to which builds

qqDocumentation defining the SCI's architecture

rrRequirements applicable to the production equipment, but not the Engineering Development Model (EDM)

ssA breakdown of the requirements relative to SCI/firmware builds associated with the particular HWCI

ttRequirement changes made since the SSR

uuSafety critical requirements

vvQuality requirements (including reliability, availability and maintainability)

wwRequirements supporting test and analysis

xxDesign error budgets for meeting allocated requirements

yyShip integration requirements

zzSystem security/IA requirements

aaaEnvironmental requirements

bbbExplanation 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

cccHow the equipment and SCI/firmware build plans for the HWCI are consistent with the overall SDP

dddDates when technical agreements are needed on the content of the various requirements and design documentation

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

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

gggAn overview of the system architecture

hhhDescription of the processes and methodologies for assessing the ergonomics and operational suitability of the hardware configurations

iiiDescription of the intra-HCI & intra-SCI landscape

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

kkkLocations of new and reused software, including COTS, NDI, legacy, and GFI

lllHow reused components and CIs will meet IA requirements

mmmWhere industry and government standards are applied

nnnDescription of the maturity of the functional/subsystem design

oooDescription of the HWCI's/SCI's performance requirements, including design margins

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

qqqSummary of the risk items identified for the HWCI & SCI that impact successful completion of the HWCI

rrrTest approaches planned for the HWCI and SCI testing

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

tttDegree of functional and environmental coverage planned for the tests

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

aAgenda

bEntrance and Exit criteria

cIntegrated Master Schedule

dCDRL Status

eFinal Assessment Plan

fDraft Assessment Report

gFinal Product Drawings/Models and Associated Lists

hMass Properties

iOrganizational description of operators and maintainers associated with the system

jUpdate producibility plan

kFinal Reliability and Maintainability Predictions

lFinal Allocation Report

mFinal Failure Mode Effects and Criticality Analysis (FMECA)

nFailure Reporting, Analysis and Corrective Action System (FRACAS)

oFinal Reliability and Maintainability Test Plan

pFinal Maintainability and Testability Demonstration Plan

qDraft Manufacturing Plan

rDraft Producibility & Quality Plan

sDraft Subcontractor Management Plan

tDraft Logistics Strategy

uDraft Incorporation Plan

vFinal Testability Analysis

wFinal parts management Plan

xGrowth of requirements for each system build including any training required

ySystem Safety Impacts

zRisks and Associated Mitigation Strategies

aaDescription of the system architecture

bbAn overview of the total system requirements as defined in the system specifications

ccAllocation of system requirements to each of the CIs comprising the system

ddUser interfaces, including displays

eeInterfaces between the SCIs, broken out into builds

ffConnectivity among system HCIs

ggLayers of the architecture (if layers have been defined)

hhIdentification of all NDIs, GFE, and legacy equipment

iiAn overview of the HCI requirements and associated SCI and firmware documentation

jjWhere the HCI fits into the system architecture and the system development schedule

kkHow the system requirements are allocated to the various HCIs

llRequirements applicable to the production equipment, but not the EDM

mmAn overview of the SCI requirements

nnA breakdown of the requirements relative to SCI/Firmware builds associated with the particular HCI

ooA breakdown of how the requirements are allocated across builds

ppDocumentation defining which SRS requirements is allocated to which builds

qqWhere the SCI fits into the system architecture and system build plan

rrRequirements changes made since PDR

ssSafety critical requirements

ttQuality requirements (including reliability, availability and maintainability)

uuRequirements supporting test and analysis

vvDesign error budgets for meeting allocated requirements

wwShip integration requirements

xxSystem security/IA requirements

yyEnvironmental requirements

zzProcesses for assessing the ergonomics and suitability of hardware configurations

aaaHow the equipment and SCI/firmware build plans for the HCI is consistent with the overall SDP

bbbDates when technical agreements are needed on the content of the various requirements and design documentation

cccEquipment/Software development process/methods being followed and tools that are to be used, as documented in the SDP

dddDetailed 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

eeeDescription of the intra-HCI & intra-SCI landscape

fffAn overview of the HCI's configuration

gggDocumentation defining the SCI's architecture

hhhIdentification of all CSCs

iiiIdentification of HCIs

jjjWhere, within the architecture, development and reuse components will be located

kkkLocations of new and reused software, including COTS, NDI, legacy, and GFI

lllPlans for how reused components/software will meet IA requirements

mmmHow reused HCIs will meet IA requirements

nnnWhere industry and government standards are applied

oooDescription of the test plans and procedures that will be applied to the HCI

pppTest approaches planned for the CIs

qqqFQT descriptions

rrrLower-level tests to be performed on the CI components, modules and subsystems

sssMaturity of the functional/subsystem design

tttDescription of the performance requirements

uuuSoftware/Hardware metrics appropriate to the particular development

vvvSummary of the risk database items identified that impact successful completion of the HCI

wwwRisk items for the SCI that will impact successful completion of the SCI

3.7Section 7 - Production Readiness Review (PRR)The TRPP for the Production Readiness Review shall include no less than the following:

aAgenda

bEntrance and Exit criteria

cIntegrated Master Schedule

dProduction screens and tests

eFinal Reliability and Maintainability Test Report

fFinal Maintainability and Testability Demonstration Report

gFailure Reporting, Analysis and Corrective Action System (FRACAS)

hFinal manufacturing Plan

iFinal Producibility & Quality Plan

jFinal Subcontractor management Plan

kLogistics Strategy

lFinal Incorporation Plan

mSystem Safety Impacts

nRisks and Associated Mitigation Strategies

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

aDescription of the system architecture

bAn overview of the total system requirements

cTest Schedule

dFRACAS Plan

eOrganizational description of operators and maintainers associated with the system

fAllocation of system requirements to the CI

gUser interfaces, including displays

hConnectivity among system CIs as defined in the IDSs

iIdentification of all NDIs, GFE, and legacy equipment

jAn overview the CI functional and performance requirements

kAssociated SCI and firmware documentation

lHow the test and evaluation management plan are allocated to the various CIs

mRequirements changes made since the CDR

nSecurity requirements

oEnvironmental requirements

pSafety critical requirements

qQuality requirements (including reliability, availability and maintainability)

rRequirements supporting test and analysis

sSummary of risk items and mitigation plans that impact successful completion of the system

tTest approaches planned for the system

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

aDescription of the system architecture

bDescription of the system production process/methods and tools to be used

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

dTest approaches planned for the system

eA summary of the risk items and mitigation plans that will impact successful completion of the system mission

3.10Section 10 - Physical Configuration Audit (PCA)The PCA section of the TRPP shall contain the following:

aDescription of the system architecture

bAn overview of the total system requirements

cAllocation of system requirements to each of the CIs comprising the system

dUser interfaces, including displays

eConnectivity among system CIs as defined in the in IDSs

fIdentification of all NDIs, GFE, and legacy equipment

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

hExplanation 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

iDescription of the processes to be used in developing HMI and its usability

jAn overview of the CI's functional and performance requirements

kSpecifications of interfaces and protocols

lAdditions and changes made to COTS equipment, including market research and upgrade strategy

mWhere the CI fits into the system and system production and deployment schedules

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

oDates when technical agreements are needed on the content of the various requirements and design documentation

pSummary of the risk items and mitigation plans that impact successful completion of the SCI

qTest approaches planned for the system

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

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

bEntrance and Exit CriteriaThe 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.

cIntegrated Master ScheduleThe 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.

dSubsystem SpecificationThe 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.

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

fFunctional Block DiagramThe 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.

gFunctional DefinitionsThe 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.

hLogistics StrategyThe 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)

iRisks and Associated Mitigation StrategiesThe 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.

jProduct Drawings/Models and Associated ListsThe 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.

kAssessment PlanThe 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.

lAssessment ReportThe Assessment Report includes the results and success criteria from all the requirements validation activities.

mManufacturing PlanThe 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.

nProducibility & Quality PlanThe 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.

oSystem Safety ImpactsSystem 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.

pSubcontractor Management PlanThe 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.

qReliability and Maintainability Program PlanThe 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.

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

sAllocation ReportThe 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.

tFailure 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.

uFailure 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.

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

wReliability and Maintainability Test ReportThe Reliability and Maintainability Test Report describes the tasks, tasks, responsibilities, procedures and controls utilized during and the results of the specified tests from the

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

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

zBlock Diagrams and Math ModelsThe 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.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer