1. 1 [insert briefing type here] [insert program name here] for [insert name and organization of person(s) to be briefed here] [insert “month day, year” of brief here] Briefed by: [insert briefer’s name here] [insert briefer’s organization code here] [insert briefer’s phone number here] [Insert briefer’s e-mail address here] Insert program logo in this area Distribution Statement

2. Program logo here 2 Key Stakeholders NameOrganization APM MDA DT Coordinator COMOPTEVFOR (OTD) COMOPTEVFOR (OTC) CNO (N912) CNO (N-sponsor) JITC DOT&E (if required) Others (as required) -PMW, SYSCOMS, Service

3. Program logo here 3 Purpose of Briefing

4. Program logo here 4 Briefing Outline

5. Program logo here 5 Program Overview ACAT Program Phase Milestone or Decision that this phase of test will support Mission Inventory Objective (quantities)

6. Program logo here 6 System Overview Component/System Description

7. Program logo here 7 Program Overview Accomplishments/History

8. Program logo here 8 Program Overview Previous Guidance (if Required)

9. Program logo here 9 Acquisition Coordination Team (ACT) The following (Program Name) ACT members have been briefed on the program status and concur with the fielding of (Program Name).

10. Program logo here 10 Program Information and Documentation Status R Required at this time, but does not exist B Requires development or updating w/in 12 months O Required at this time and under development/update G Current, with all required approvals Y In approval cycle. Expected Date in Comments NR Not required. Rationale in Comments

11. Program logo here 11 [insert program name] Program Overview Chart DATE OF REPORT: MM/DD/YYYY PM / SponsorCostSchedulePerformance Programmatic Compliance Logistics Contract Execution Contact Info here Description: Program Start Date: MM / YY [Insert program description here] Joint or International: [Insert joint or International details] Key Performance Parameters KPPObjectiveThresholdDemo OP Avail.90.90.98 S/W Reliability 200 hrs 200 hrs 1000 hrs S/W Mean 5 sec 5 sec 3.2 sec xxxx x x x Acquisition Objectives Quantity650 IOC12 / 99 Target Price (unit)$Various $M (FY XX)$610.12 Contractor Data ContractorLitton DSD Value / Type$NA / GSA Start / CompleteAPR97 / APR03 ContractorXXX Value / Type$XX / XXX Start / CompleteXXX / XXX Cost Data ($ in M)* CostObjectiveThresholdCurrent Est. R&D 0 0 0 Proc 300.3 300.3 380 O&S 250.5 250.5 276.1 xxxx x x x * Values from last approved APB (IT) ACAT Level: MDA: Budget Source: Overall Volatility Contract Execution Ratings: G= CPI/SPI.95 or > Y= CPI/SPI.85 -.94 R = CPI/SPI <.85 OSD T&E Oversight: Y/N

12. Program logo here 12 Acquisition Strategy (Program Structure) Concept Decision Milestone A RFP Development Milestone B Contract Award Development Test/OA Milestone C/LRIP Decision Operational Test IOC FRP Decision FY03 FY04 FY05 FY06 FY07 FY08FY09FY10

13. Program logo here 13 LOGISTICS SUPPORT (Compliance with DoD/SECNAV 5000 series and policy documents) Logistics RequirementCompliance Exception Notes Independent Logistics Assessment (ILA) GREEN/YELLOW/RED Rating? When completed? Navy Training System Plan (NTSP) NTSP completed? Sustainment Training in Place? YES/NO Diminishing Manufacturing Sources & Matl. Shortages (DMSMS) DMSMS Process/Tool used to ID Obsolescence challenges? YES/NO Unique Identification (UID) Policy implementation DFARS Clause 252.211-7003 in contract/contract mods? YES/NO Digital Product and Technical Data Manuals, Drawings, Illustrations available in approved digital formats? YES/NO Human Systems Integration (HSI) HSI factors addressed in AS, SEP, and NTSP? YES/NO Performance Based Logistics (PBL) implementation PBL strategy considered and decision documented in BCA? YES/NO

14. Program logo here 14 Program Assessment Installation Readiness Place the assessment rating icon here. Delete the remaining.

15. Program logo here 15 Software Maturity Software Trouble Reports (STRs) S/W Build Version x.xx # of STRs

16. Program logo here 16 Software Maturity Priority 1 STR’s

17. Program logo here 17 Software Maturity Priority 1 STR Status

18. Program logo here 18 [Combat capability] ThresholdObjective [C4I Interoperability, (Strategic, Theater, Force Coord.)] [Endurance] [Cost] [Manning] [Sustained Speed] KPP Compliance

19. Program logo here 19 COI Assessment (Based on DT Results)* COIRisk Effectiveness Capacity (example) Survivability (example) Joint Interoperability (Net Ready) Etc. Suitability Reliability Maintainability Operational Availability Logistic Supportability Compatibility Interoperability Training Human Factors Safety Documentation * For DRR, assess likelihood of achieving COI Thresholds

20. Program logo here 20 DT Recommendation

21. Program logo here 21 Developmental Testing & Evaluation (DT&E) Results ParameterThresholdObjectiveResult/Assessment KPP’s KPP 1 KPP 2 MOE’s/MOS’s MOE 1 MOE 2 MOS 1 MOS 2 CTP’s CTP 1 CTP 2

22. Program logo here 22 OT Scope of Test

23. Program logo here 23 T&E Exceptions Waivers Deferrals

24. Program logo here 24 Interoperability (Net Ready)

25. Program logo here 25 Program Manger’s OTRR Checklist Navy Criteria for Certification: The following criteria for certification of readiness applies to all OT&E for all Navy Programs (EOA, OA, IOT&E, FOT&E). The program manager with the concurrence of the OTA, may tailor criteria listed below ( with the exception of item #1). The MDA may add criteria as necessary to determine the readiness for OT. YesNoN/AApproval Date 1. The TEMP is current and approved. OT prior to Milestone B shall have an approved T&E Strategy (TES). 2. DT&E results indicate DT objectives and performance thresholds identified in the TEMP have been satisfied for the ORD/CDD/CPD, as appropriate. a. If no, are they projected to be at system maturity, and do the results indicate that the system will perform successfully in OT&E? b. In addition, will they meet the criteria for approval at the next program decision milestone (e.g., full rate production on completion of IOT&E)? 3. All significant areas of risk have been identified and corrected, or mitigation pans are in place. 4. DT&E data and reports have been provided to the OTA not less than 30 days prior to the commencement of OT, unless otherwise agreed to by the OTA. 5. Entrance criteria for OT identified in the TEMP have been satisfied.

26. Program logo here 26 Program Manger’s OTRR Checklist (con’t) YesNoN/AApproval Date 6. System operating, maintenance, and training documents have been provided to the OTA 30 days prior to the OTRR, unless otherwise agreed to by the OTA. 7. Logistic support, including spares, repair parts, and support/ground support equipment is available as documented. a. Is there any logistics support which will be used during OT&E, but will not be used with the system when fielded (e.g., contractor provided depot level maintenance)? 8. The OT&E manning of the system is adequate in numbers, rates, ratings, and experience level to simulate normal operating conditions. 9. Training has been completed and is representative of that planned for fleet units. 10. All resources required to execute OT including instrumentation, simulators, targets, and expendables have been identified and are available. 11. Models, simulators, and targets have been accredited for intended use.

27. Program logo here 27 Program Manger’s OTRR Checklist (con’t) YesNoN/AApproval Date 12. The system provided for OT&E, including software, is production representative. Differences between the system provided for test and production configuration shall be addressed at the OTRR. 13. Threat information (e.g., threat system characteristics and performance, electronic countermeasures, force levels, scenarios, and tactics), to include security classification, required for OT&E is available to satisfy OTA test planning. 14. The system is safe to use as planned in the concept of employment. Any restrictions to safe employment are stated. a. The environmental, safety, and occupational health (ESOH) program requirements have been satisfied. b. The system complies with Navy/Marine Corps environmental, safety, and occupational health/hazardous waste requirements, where applicable. c. Environmental, safety, and occupational health/hazardous waste reviews and reports have been provided to the OTA.

28. Program logo here 28 Program Manger’s OTRR Checklist (con’t) YesNoN/AApproval Date 15. All software is sufficiently mature and stable for fleet introduction. a. All software Trouble Reports are documented with appropriate impact analyses. There are no outstanding Trouble Reports that: 1) Prevent the accomplishment of an essential capability. 2) Jeopardize safety, security, or other requirement designated "critical“. 3) Adversely affect the accomplishment of an essential capability and no work-around solution is known, or 4) Adversely affect technical, cost, or schedule risks to the project or to life-cycle support of the system, and no work-around solution is known. 16. For software qualification testing (SQT), a Statement of Functionality that describes the software capability has been provided to the OTA and CNO (N091).

29. Program logo here 29 Program Manger’s OTRR Checklist (con’t) YesNoN/AApproval Date 17. For programs with interoperability requirements (e.g., NR-KPP ORD/CDD/CPD), appropriate authority has approved the ISP. a. JITC concurs that program interoperability demonstrated in development has progressed sufficiently for the phase of OT to be conducted. 18. Approval of spectrum certification compliance and spectrum supportability has been obtained. 19. For IT systems, including NSS, the system has been assigned a MAC and Confidentiality Level. a. System certification accreditation documents, including the SSAA and the Authority to Operate (ATO) or Interim Authority to Operate (IATO), has been provided to the OTA. 20. Other(s)…

30. Program logo here 30 Program Manger’s OTRR Checklist (con’t) YesNoN/AApproval Date 21. For aircraft programs, there are no unresolved NAVAIRSYSCOM deficiencies that affect: a. Airworthiness b. Capability to accomplish the primary or secondary mission(s) c. Safety of the aircrew/operator/maintainer d. Integrity of the system or an essential subsystem e. Effectiveness of the operator as an essential subsystem

31. Program logo here 31 e LIKELIHOOD e d c b a CONSEQUENCE dc b a HighMedium LowMedium Risk Advisory Board: [Mr. X, PMA xxx] [Ms. Y, XYZ Corp] [Ms. Z, DASN YY] A brief description of Issue # 4 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 4 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 3 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 3 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 2 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 2 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 1 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 1 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 5 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 5 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 6 and rationale for its rating. Approach to remedy/mitigation A brief description of Issue # 6 and rationale for its rating. Approach to remedy/mitigation Acronyms: [IMA= Intermediate Maintenance Activity] Program Risk Assessment

32. Program logo here 32 Key Issues No further action required Significant interest outside Program Cannot be solved within the Program Legend IssueDue DateResponseStatus

33. Program logo here 33 Other Decision Factors and Challenges [List as appropriate] Example: Acquisition Coordination Team, Chaired by [insert name] concurred that [insert program name] is ready for OT&E on [date] Example: Acquisition Coordination Team, Chaired by [insert name] concurred that [insert program name] is ready to enter SDD Phase

34. Program logo here 34 PM Assessment

35. Program logo here 35 Recommendations