Attachment_2_-_Appendix_A_TI16APB17_21Aug14.pdf

N00024-14-R-6203

APPENDIX A

TO

ATTACHMENT 2

TI-16/APB-17 Development, Integration, Testing and Delivery

[CLINs 0005, 0006, and 0007]

A-i

APPENDIX A

TO

ATTACHMENT 2

TABLE OF CONTENTS

1. SYSTEMS ENGINEERING 1

1.1 Systems Engineering Management Plan (SEMP) 1

1.2 Engineering Documentation Database 2

1.3 Studies and Analyses 2

1.4 Meetings, Integrated Product Teams (IPTs) and Working Groups (WGs) 2

1.5 System Requirements 2

1.5.1 Requirements Documentation 2

1.5.2 Interface Requirements Management 3

1.5.3 System Architecture and Design 3

1.5.4 Safety 5

1.5.5 Information Assurance (IA) 6

2. SYSTEM DEVELOPMENT 6

2.1 TI-16/APB-17 Software Development 6

2.2 Problem Reporting 7

2.3 System Integration Planning 8

2.4 Test Documentation 8

2.4.1 Test and Evaluation Program Plan 8

2.4.2 Test Procedures 8

3. TEST AND EVALUATION 8

3.1 Test Conduct 9

3.2 Testing Support to the Government 9

4. PLATFORM INTEGRATION 9

4.1 System Delivery 9

5. INTEGRATED LOGISTICS SUPPORT 9

5.1 Interactive Electronic Technical Manual (IETM) Source Data 9

5.2 Ready Reference Manual (RRM) 10

5.3 OD 44979 Redlines 10

6. FACILITIES 10

6.1 Hardware/Software Integration and Test (HSIT) Facilities 10

6.2 Licenses 11

A-1

APPENDIX A TO ATTACHMENT 2

STATEMENT OF WORK

FOR

TI-16/APB-17 DEVELOPMENT, INTEGRATION, TESTING AND DELIVERY

[CLINs 0005, 0006, and 0007]

The Contractor shall design, develop, test, integrate and deliver the AN/BYG-1 PCS TI-16/APB-17 PCS for variants

(V) 1, 6 and 9 and accomplish common efforts for (V)8 under CLIN 0005. The Contractor shall have facilities to support these variants. Paragraphs 1 through 6 of this Appendix A apply to CLINs 0005, 0006, and 0007.

The Contractor shall use the AN/BYG-1 TI-16/APB-15 WCS system as the baseline for developing the core TI- 16/APB-17 PCS and shall ensure the TI-16/APB-17 PCS performance is in accordance with the Performance Specification for the Payload Control System (PCS) PMS4253-PCS-001 dated 09 May 2014 (Attachment 6). All tasks defined herein shall be accomplished and delivered in accordance with the IMS.

The Contractor shall ensure the PCS variants interface with the TI-16/APB-17 Tactical Control System (TCS) and the Information Assurance (IA) software being developed in parallel under separate Navy contracts. The Contractor shall coordinate with Government and contractor facilities as needed to ensure that system integration testing and subsystem simulations requiring Government assets outside the Contractor’s facility are appropriately coordinated and scheduled.

1. SYSTEMS ENGINEERING

The Contractor shall provide a Systems Engineering Lead for the TI-16/APB-17 effort under this contract. The Systems Engineering Lead shall ensure the application of disciplined Systems Engineering processes and Integrated Process and Product Development (IPPD) principles toward the development of the TI-16/APB-17 PCS baseline supporting the final certified system configurations of the AN/BYG-1 SCCS.

1.1 Systems Engineering Management Plan (SEMP)

The Contractor shall provide a Systems Engineering Management Plan (SEMP) to describe the Contractor’s approach for planning, controlling and conducting a fully integrated engineering effort under this contract. The Contractor shall ensure the SEMP incorporates the principles, and effectively aligns with the processes, of the Submarine Combat and Weapon Control System SEP. The Contractor shall deliver the initial SEMP under CLIN 0005 for TI-16/APB-17; however, the SEMP shall apply to all efforts under this contract and shall be updated as required for subsequent TI/APB efforts. [CDRL A015]

The SEMP shall describe how the PCS development will progress from initial requirements definition through the build management and test and integration processes and how various technical inputs to the systems engineering effort will be integrated into a collaborative development environment. The SEMP process shall ensure the compatibility, interoperability, and integration of all functional and physical interfaces and shall ensure that the system definition and design reflect the requirements for all system elements: hardware, software, facilities, people, and data, as well as characterize and manage technical risks.

The SEMP shall also include a detailed description of the Contractor’s approach for ensuring that all system requirements are accounted for through a demonstrated ability to trace each requirement to the Specification Requirement Verification Matrix (SRVM) [CDRL A018], the Software Requirements Specifications (SRSs) [CDRL A020], System/Subsystem Specifications (SSSs) [CDRL A017] and Test Procedures [CDRL A027].

The SEMP shall define the full extent of internal and external AN/BYG-1 integration plans, identify the Contractor’s approach and support for overall AN/BYG-1 integration, and identify the necessary development and integration resources to conduct AN/BYG-1 system integration. The SEMP shall also identify the process to address all problems identified by the Government during interface testing.

A-2

The Contractor's System Engineering processes shall include efforts to support the Weapon Safety Program and those efforts to ensure the "design-in" of high reliability, maintainability, and availability requirements, including on-line and off-line diagnostics, maintenance documentation (e.g. built-in Interactive Electronic Technical Manual), and embedded training capabilities.

1.2 Engineering Documentation Database

The Contractor shall maintain the Contractor Integrated Digital Environment databases (i.e. Dynamic Object- Oriented Requirements System (DOORS)) to support the generation, traceability and configuration management of TI-16/APB-17 requirements, plans and procedures. At a minimum, the database shall trace all TI-16/APB-17 requirements to the SRVM, SRSs, SSSs, and Test Procedures. The database shall also allow for storage of these deliverables. The Contractor shall ensure the Government has full real-time access to the database. [CDRL A016]

The Contractor shall provide for the initial requirements database under CLIN 0005 for TI-16/APB-17; however, the database shall apply to all development efforts under this contract and shall be updated as required for subsequent TI/APB efforts.

1.3 Studies and Analyses

The Contractor shall assist the Government in developing strategies and studies, performing system engineering analysis, and developing implementation plans to ensure the PCS achieves the specified performance. [CDRLs A010 and A011]

1.4 Meetings, Integrated Product Teams (IPTs) and Working Groups (WGs)

The Contractor shall participate in and/or support the following Government-established Integrated Product Teams (IPTs) and working groups supporting the TI-16/APB-17 design, development, integration and installation:

a) AN/BYG-1 System Engineering Integrated Product Team (SEIPT)

b) AN/BYG-1 Requirements Architecture Design Working Group (RADWG)

c) AN/BYG-1 Integration and Test Working Group (ITWG)

d) AN/BYG-1 Integrated Logistics Support Working Group (ILSWG)

e) AN/BYG-1 Problem Trouble Report (PTR) Review Board

f) SWFTS Architecture Working Group (SAWG)

g) SWFTS Systems Engineering Working Group (SEWG)

h) Technology Insertion IPT (TI IPT)

i) Integration IPT (I&T IPT)

j) Installation IPT

k) VIRGINIA Class and OHIO Class new construction technical team meetings and Platform Integration

Teams (PITs)

l) Submarine Combat System Combined Safety Working Group; the Software System Safety Technical

Review Panel (SSSTRP); and the Weapons System Explosives Safety Review Board (WSESRB)

m) Design reviews and working groups for the design and development of the AN/BYG-1 TI hardware baselines

1.5 System Requirements

The Contractor shall assist the Government in defining and documenting the capabilities and requirements for the TI-16/APB-17 baseline. The Contractor shall maintain the PCS requirements in the Contractor Integrated Digital Environment database (i.e., Dynamic Object-Oriented Requirements System (DOORS)) with updates required for

TI-16/APB-17.

1.5.1 Requirements Documentation

The Contractor shall develop the following for the PCS TI-16/APB-17 configurations:

A-3

• System/Subsystem Specifications (SSS) [CDRL A017]

• Specification Requirement Verification Matrix (SRVM) [CDRL A018]

The Contractor shall document the specific weapon/payload tubes and launcher equipment provided as GFE (Attachment 4) that will be utilized for each test in the SRVM. To support development of the SRVM, the Contractor may elect to review the TI-14/APB-13 SSS and SRVM requirements documentation that is maintained on AIMTC.

1.5.2 Interface Requirements Management

As part of the Contractor’s SEMP [CDRL A015], the Contractor shall describe the processes to be used to manage system interfaces. At a minimum, the Contractor shall address the following:

a) The Contractor shall identify processes for specifying the lowest level (i.e., subsystem or component) at and below which it intends to control and define interfaces by proprietary, vendor-unique standards, as well as the impact of those standards upon the proposed modularity and logistics approach.

b) The Contractor shall describe how it will define and record all subsystem and CI level interfaces to provide fully functional specifications.

As part of the Contractor’s System/Subsystem Design Description (SSDD) [CDRL A019], the Contractor shall describe the PCS interfaces and interaction with SWFTS subsystems and weapons/payload/launcher systems. At a minimum, the Contractor shall address the following:

a) Interfaces described shall ensure compliance with applicable Interface Control Drawings (ICDs), Interface Requirements Documents (IRDs), and Interface Requirements Specifications (IRSs), including weapons and payloads, as defined in the PCS Performance Specification (provided as GFI, Attachment 3).

b) The Contractor shall address the interface and data exchange standards between the component, module or system and the interconnecting or underlying information exchange medium.

c) The Contractor shall state how these interfaces support an overall Information Assurance strategy that provides a defense in depth in accordance with NAVSEA Instruction 9400.2

The Contractor shall ensure the external interface integrity of the PCS and manage interface change activity.

a) The Contractor shall participate in the SWFTS Baseline Management System and notify the Program Office of any required Non-Propulsion Electronics System (NPES) Baseline Change Requests (NBCRs) required to support PCS external interface changes. The Contractor shall create NBCRs as directed by the Program Office. The Contractor shall evaluate NBCRs submitted by other SWFTS systems for impact to the PCS.

b) The Contractor shall initiate appropriate interface change requests for other interface specifications, including weapons and payload when updates are required.

1.5.3 System Architecture and Design

1.5.3.1 Modular Open Systems Architecture Approach

The Contractor shall establish and maintain a modular open systems architecture approach in accordance with the requirements of the DoD Open System Architecture Contract Guidebook, v1.1. The Contractor shall ensure the following system architecture characteristics are maintained for the TI-16/APB-17 PCS:

a) Open Architecture - The Contractor shall develop and maintain a PCS architecture that incorporates appropriate considerations for reconfigurability, portability, maintainability, technology insertion, vendor independence, reusability, scalability, interoperability, upgradeability, and long-term supportability.

A-4

b) Modular, Open Design – The Contractor shall develop and maintain a PCS architecture that is layered and modular and uses COTS/NDI hardware, operating systems, and middleware that utilizes non-proprietary or non-vendor-unique, key Application Programming Interfaces (APIs). The Contractor’s design approach shall be applied to all subsystems and components. The Contractor shall provide the Government (and/or Government support contractors) electronic access to its integrated development environment throughout the term of the contract.

c) Modular Open Systems Approach (MOSA) –The Contractor’s design approach shall produce a system that consists of hierarchical collections of software and hardware configuration items (components). These components shall be of a size that supports competitive acquisition as well as reuse. The Contractor’s design approach shall emphasize the selection of components that are available commercially or within the DOD, to avoid the need to redevelop products that already exist and that can be re-used.

In technical and design reviews, the Contractor shall provide the approach to be used relating to the overall Software Computer Software Configuration Item (CSCI) structure, functional flows, and interface requirements and shall describe how their approach supports Open Architecture goals while interfacing with the other SWFTS systems simultaneously under development. The Contractor shall disclose the approach to support the system’s collaborative development environment including the frequent and continuous design disclosure to Navy designated third-party developers throughout the development process. Additionally, as part of technical and design reviews, the Contractor shall, at a minimum:

a) Describe how the proposed system architecture meets the modular, open design goals, including the steps taken to use non-proprietary or non-vendor unique COTS or reusable NDI components wherever practicable.

b) Describe its rationale for the modularization choices made to generate the design.

c) Provide rationale that explicitly address any tradeoffs performed, particularly those that compromise the modular and open nature of the system.

d) Provide rationale for maintaining continued access to cutting edge technologies and products from multiple suppliers.

e) Describe how it will mitigate the risks associated with technology obsolescence.

f) Describe how it will avoid being locked into proprietary or vendor-unique technology and reliance on a single source of supply over the life of the system

1.5.3.2 System Design Documents

The Contractor shall provide the following TI-16/APB-17 documents to fully detail the PCS TI-16/APB-17 configurations:

• System/Subsystem Design Description (SSDD) [CDRL A019]

• Software Requirements Specifications (SRSs) [CDRL A020]

• Software Design Description (SDD) [CDRL A021]

The Contractor shall ensure the above documents fully describe the overall software Computer Software Configuration Item (CSCI) structure, functional flows and interface requirements, including external PCS interface requirements, if applicable. The Contractor shall include separate sections that detail any unique variant or platform requirements. To support development of this effort, the Contractor may elect to review the TI-14/APB-13 SSS and SRVM requirements documentation that is maintained on AIMTC.

The Contractor shall also generate SWFTS-level interface documentation including Group Requirements Lists (GRLs).

1.5.3.3 Technical and Design Reviews

Technical and design reviews shall be held at the Contractor’s facility to discuss and evaluate overall design progress and the status of entrance and exit criteria as defined in the PMS425 SEP. The structure and intervals shall

A-5 be defined in the IMS. However, the scope of the TI-16/APB-17 technical reviews shall be limited to the impact of the new TI-16/APB-17 CIs. The Contractor shall address all review action items within the scope of the TI- 16/APB-17 changes and document (but defer) any effort involving legacy issues.

The Contractor shall provide for the following TI-16/APB-17 technical and design reviews:

• System Requirements Review (SRR)

• Preliminary Design Review (PDR)

• Critical Design Review (CDR)

The Contractor shall provide Design Review Data Packages supporting these reviews two (2) weeks prior to the design review. [CDRL A022]

1.5.3.4 Hardware Design

The Contractor shall work with the Technology Insertion Hardware (TIH) contractor and other hardware contractors to ensure that the PCS TI-16 baseline design meets the requirements of the system performance specification and is not technologically obsolete when fielded. The Contractor shall provide engineering services to support TI-16 end-of-life hardware studies or form/fit/function replacement studies. The Contractor shall support any required replacement hardware prototyping; hardware requirements definition; Critical Item Test and product deselect; and product selection and validation.

If replacement production evaluation and selection is required, the Contractor shall ensure that the requirements of National Aerospace Standard (NAS 411) are considered to eliminate, or at least minimize to the highest possible extent, the following:

• Any usage of hazardous materials, including those on the Environmental Protection Agency (EPA) listing of 17 toxics,

• Any Class I or II Stratospheric Ozone depleting substances

• Any of the Department of Defense (DoD) Top Ten Toxic Release Inventory (TRI) Chemicals

The Contractor shall also consider electromagnetic requirements, specifically that candidate components must be electromagnetically self-compatible with all other onboard systems and equipment in the submarine’s below-deck operational electromagnetic environment.

1.5.4 Safety

1.5.4.1 Safety Program

The Contractor shall establish and maintain a system safety program in accordance with the requirements of MIL- STD-882 and the PMS425 System Safety Management Plan (SSMP) 425-SAFETY-SSMP-02. The Contractor shall develop a System Safety Program Plan (SSPP) [CDRL B001] that describes the system safety management and system safety engineering tasks and activities required to identify, evaluate, and eliminate/ control hazards, or reduce the associated risk to a level acceptable by PMS425. The Contractor shall provide addendums to the SSPP to address specific analyses and activities required to achieve the overall system safety objectives for all TI-16/APB-17 configurations. The Contractor shall deliver the initial SSPP under CLIN 0005 for TI-16/APB-17; however, the SSPP shall apply to all efforts under this contract and shall be updated as required for subsequent TI/APB efforts.

The Contractor is responsible and accountable for the PCS Safety Program. As such, the Contractor shall:

• Ensure the safety tasks are properly conducted and reported to the Program Office

• Resolve Program Office concerns regarding safety

• Provide support to the Software System Safety Technical Review Panel (SSSTRP) and Weapon System

Explosive Safety Review Board (WSESRB) reviews and resolve action items as they relate to the PCS

• Plan and conduct a weekly safety meeting via telcon with the PMS425 Principal for Safety

A-6

• Provide support to, and participate in, the quarterly PMS425 Combined Weapons System Safety Working Group with the system safety certification process

• Conduct safety analysis and develop associated reports

When safety impacts are identified, the Contractor shall notify PMS425 of a decrease in the level of safety on the system. The Contractor shall ensure safety is considered in test and evaluation activities and shall ensure that all test safety requirements are met prior to and during testing.

1.5.4.2 Safety Documents

The Contractor shall conduct, document and deliver the following safety analyses/reports for the TI-16/APB-17 configuration with supporting details for variant or platform differences:

• Preliminary Hazard Analysis (PHA)[CDRL B002]

• System Hazard Analysis (SHA) [CDRL B002]

• Subsystem Hazard Analysis (SSHA) [CDRL B002]

• Safety Requirements/Criticality Analysis (SR/CA) [CDRL B002]

• Inadvertent Launch Analysis (ILA) [CDRL B002]

• Operational & Safety Hazard Analysis (O&SHA) [CDRL B002]

The Contractor shall create Functional One-Line Diagrams (FOLDs) and Fault Tables for the TI-16/APB-17 configurations. The Contractor shall also perform a comprehensive safety assessment for the TI-16/APB-17 configuration and generate a Safety Assessment Report (SAR) to evaluate the mishap risk being assumed prior to the WSESRB. [CDRL B003]

1.5.5 Information Assurance (IA)

The Contractor shall maintain an IA program to support the customer's system security certification and accreditation of PCS. The Contractor shall implement IA in accordance with NAVSEAINST 9400.2, DoDD 8500.01, and COMNAVNETWARCOM Communications Tasking Order (CTO) 11-16. During the course of the contracting period, the Contractor shall ensure the system design and engineering processes employed in system design include IA considerations as delineated in the technical reference documents and the PCS Performance Specification, and that IA measures and design characteristics are correctly implemented in the PCS. Furthermore, the Contractor shall ensure that personnel are trained and appropriately certified in accordance with DoD 8570.01 for providing IA functional services.

The Government will periodically update the IA technical reference documents, as needed. If it is determined that a change in guidance will impact the system design, existing labor requirements, or other contract deliverables, the Contractor shall notify the Government within 30 calendar days.

The Contractor shall implement and apply safeguards such that information and resources maintain the appropriate level of confidentiality, integrity, availability, authentication, and non-repudiation based upon mission criticality, level of required information assurance and classification or sensitivity level of information entered, processed, stored, or transmitted for PCS. The Contractor shall safeguard information and information systems through the use of multi-disciplined defensive layers, as well as sound administrative and operational practices.

The Contractor shall analyze system security requirements, provide data inputs to support the Program Office in the development of System Security Authorization Agreements (SSAAs) and provide Information Assurance Vulnerability Messages (IAVM) support in accordance with the Information Assurance Vulnerability Management Policy for PMS425 (PMS425 ltr Ser 425/0161 dated 24 August 2007).

2. SYSTEM DEVELOPMENT

2.1 TI-16/APB-17 Software Development

A-7

The Contractor shall establish and maintain a software engineering process by tailoring the requirements of the ISO/IEC/IEEE 12207-2008 standard as applicable to the PCS program. The Contractor shall document the software engineering process in a Software Development Plan (SDP) and shall include the rationale for tailoring as part of the SDP. The Contractor shall manage, develop, update, test and deliver the PCS computer software in accordance with the SDP. The Contractor shall ensure the SDP contains appropriate procedures for the prevention of, and screening for, malware including the following:

• Identification of malware scanning procedures using the latest DoD-approved anti-malware product prior to release of each formal build

• Establishment of procedures to limit, to the maximum extent practical, and govern the use of removable media during software development

In lieu of a separate Open Systems Management Plan, the Contract shall incorporate the following into the SDP:

• Documentation of the of the Contractor's approach to using modular design, standards-based interfaces and widely-supported consensus-based standards throughout the PCS development effort

• Identify all Commercial-Off-the-Shelf (COTS) and Non-Developmental Item (NDI) components, their functionality in the system, and provide copies of license agreements related to these components

• Procedures for Government access to the integrated development environment (IDE) and the ability to download artifacts throughout the life of the contract

• Procedures to reuse pre-existing or common items and provide justification for any exceptions

The Contractor shall deliver the initial SDP under CLIN 0005 for TI-16/APB-17; however, the SDP shall apply to all efforts under this contract and shall be updated as required for subsequent TI/APBs. [CDRL A023]

The Contractor shall provide the following TI-16/APB-17 software development efforts:

• Execute Code and Unit Test (CUT)

• Perform code review

• Assess, adjudicate, and resolve Problem Trouble Reports (PTRs)

• Generate and deliver software builds as necessary to support software development and integration requirements [CDRL A024]

• Generate Software Version Description (SVD) documents for the generated software builds [CDRL A025]

• Generate software configuration build procedures

• Provide Information Assurance Vulnerability Messages (IAVM) support

The Contractor shall support integration of SWFTS Interface Data Language (IDL) versions.

2.2 Problem Reporting

The Contractor shall establish a single Problem Trouble Report (PTR) system for the identification, tracking and resolution of all TI-16/APB-17 hardware, software and baseline documentation problems identified during system development, integration and testing. In addition, the PTR system shall be used to track test documentation problems and technical manual errors. The Contractor shall ensure the Government has full real-time access to the database.

For planning purposes and guidance only, the following table provides the Government’s estimation on the number and classification of PTRs that may require Contractor analysis and software resolution during development, integration and testing of the TI-16/APB-17 baseline:

Total PTRs High Severity Medium Severity Low Severity Common 225 25 180 20 (V)9 Unique 75 15 50 10

A-8

The Contractor shall co-lead the AN/BYG-1 PTR Review Board (PTRB) with the government to assess, adjudicate, and provide recommendations to the Government. The Contractor shall use NAVSEAINST 9410.02 in providing PTR classification recommendations. The Government will designate and approve final classification of PTR severity. The Contractor shall provide support and conduct a technical assessment in adjudication of the PTR;

however, the Government will determine which PTRs to authorize for correction during the integration and test events including incorporation into software builds. A synopsis of all problems identified under this PTR system shall be included with the monthly IPMR. The PTR shall reference applicable requirements, system notes, any other applicable interface system PTR (Ex. Tactical Control PTR) and COATs Common Problem Reports (CPRs). For PTRs adjudicated by the Government as requiring a System Note, the Contractor shall provide data supporting Ready Reference Manual (RRM) preparation. For PTRs adjudicated as requiring a Hazard Analysis Report (HAR), the Contractor shall provide input to the PMS425 Principal for Safety for preparation of the HAR.

2.3 System Integration Planning

The Contractor shall support overall AN/BYG-1 integration throughout the design, development and test phases of the PCS and TCS components (including TacLAN and Information Assurance) as well as system-level integration of the variants and delivery of associated logistics products. The Contractor shall support all system integration requirements including integration with TCS, IA, the Tactical Tomahawk Weapon Control System (TTWCS) and all applicable Submarine Warfare Federated Tactical Systems (SWFTS) as required to support delivery of both TCS and PCS as a certified AN/BYG-1 (V) 1, 6 and 9 TI-16/APB-17 Combat Control System.

2.4 Test Documentation

The Contractor shall maintain a comprehensive test program and perform integrated test planning to ensure that all tests are properly time phased and that duplicative or redundant testing is minimized. The test program shall concentrate on ensuring the delivered PCS meets the performance requirements as intended for operational deployment. The test planning shall address pass/fail criteria and provisions for analyzing and correcting the cause of any failures.

2.4.1 Test and Evaluation Program Plan

The Contractor shall develop a Test and Evaluation Program Plan (TEPP) to describe the Contractor’s approach for a comprehensive test program. The TEPP shall include a description of all test procedures and planned test events for the PCS life cycle including, but not limited to, software verification, regression testing, validation testing, longevity testing and testing of associated payloads, launchers, shipboard subsystems and interfaces. The Contractor shall ensure the TEPP addresses the location for conduct of the specific test events as well as all required hardware, Simulation/Stimulation (SIM/STIM) equipment, and other test support. The Contractor shall deliver the initial TEPP under CLIN 0005 for TI-16/APB-17; however, the TEPP shall apply to all efforts under this contract and shall be updated for TI-18/APB-17 and TI-18/APB-19. [CDRL A026]

2.4.2 Test Procedures

Additionally, the Contractor shall develop and deliver new procedures in accordance with the Contractor’s TEPP to support TI-16/APB-17 requirements. To support this effort, the Contractor may elect to review the TI-16/APB-15 test procedures that are maintained on AIMTC. [CDRL A027]

3. TEST AND EVALUATION

The Contractor shall perform demonstrations and tests per the Contractor-prepared and Government-approved test plans and test procedures in accordance with the SOW and the PCS Performance Specification. [CDRL A026 and A027] Government acceptance of the final TI-16/APB-17 PCS software is contingent upon successful completion of these demonstrations and tests. The Contractor shall provide test lead support and test meeting support for all T&E efforts within this SOW.

A-9

3.1 Test Conduct

The Contractor shall document and conduct Test Readiness Reviews (TRRs) as scheduled in the IMS to ensure the system software is configuration managed, test documents and RFDs are approved, and test entrance requirements are satisfied prior to entering formal test events. [CDRL A022]

The Contractor shall deliver software builds and conduct testing as defined in the TEPP and SRVM.

The Contractor’s T&E services shall also include:

a) Conduct of integration as necessary to ready the product for formal testing

b) Software build installation

c) Execution of Build Quality Assessment (BQA)

d) PTR Verification and Validation (V&V)

e) System Integration Tests

f) Use of payload simulators and test tools (ex. Torpedo Mini-PV and Tomahawk GTS units)

g) Generation and delivery of Test/Inspection Reports [CDRL A028]

The Contractor shall conduct regression testing to determine adequacy of PTR fix solutions and to ensure that no new faults have been introduced. TRRs and TRR presentations shall be required for regression test events.

3.2 Testing Support to the Government

The Contractor shall provide access to the PCS and associated sensors in its development and test facilities for the Government to perform on-site independent tests or evaluations.

The Contractor shall provide support, as required, for Government-conducted SWFTS-level test events such as External Interface Tests (EITs), System Level Tests (SLTs), and System Integrated Tests (SITs).

4. PLATFORM INTEGRATION

4.1 System Delivery

The Contractor shall provide input and participate in the Government-led Software Delivery Verification Review (SDVR) supporting each variant of the TI-16/APB-17 baseline to ensure that the system has successfully completed verification with all discrepancies adequately documented and that all system support actions have been completed.

The Contractor shall also provide input and participate in the Government-led Delivery Readiness Review (DRR) to ensure the system is ready to be delivered to the Fleet.

5. INTEGRATED LOGISTICS SUPPORT

5.1 Interactive Electronic Technical Manual (IETM) Source Data

The Contractor shall develop, update, maintain, and deliver PCS TI-16/APB-17 Interactive Electronic Technical Manual (IETM) source data to support government or other contractor development of the AN/BYG-1 IETM for all applicable TI-16/APB-17 configurations. The Contractor shall use the TMCR NO. NDMS-090092-000 in providing the source date deliverable. [CDRL A029]. These updates shall include but are not limited to, functional descriptions, physical descriptions, operating procedures including power-up/down, display screen shots, display hot links and text hyper-links, which address all aspects of PCS operations and maintenance for each configuration consistent with similar PCS data contained within the AN/BYG-1 IETMs for TI-16 APB-15 provided as GFI (Attachment 3 GFI). The Contractor shall develop source data that is S1000D compliant in a government approved S1000D database environment. The Contractor shall provide subject matter expertise to support comment

A-10 incorporation, desktop lab validations and verifications and provide single point of contact for the government and other members of the ILS working group in all matters relating to PCS IETM delivery, development and schedules.

Delivery schedule of IETM source data shall be documented in the Contractor’s Integrated Master Schedule (IMS) and support the AN/BYG-1Integrated Master Plan (IMP). The Contractor shall participate in bi-weekly ILS working group forums.

5.2 Ready Reference Manual (RRM)

The Contractor shall provide data, including system notes, to support preparation of the ready reference manual [CDRL A010]. Format for the RRM and System Notes shall be provided in Attachment 3 GFI. The RRM data shall include:

a) Software Build Procedures. These build procedures shall include identification of all necessary required to build the PCS portion of the AN/BYG-1 system. Procedures shall be reviewed and validated and must include any warnings, cautions, danger, and notes as applicable including any prerequisites and all necessary default passwords.

b) Procedural Steps. Procedural steps for a post build verification shall be included into a larger post build checklist.

c) Information Assurance Information: List of all swappable/removable disks/media affected by PCS software, security level during various posture transitions and clearing methods for each. Validated posture transition procedures to support shipboard posture transitions.

The Contractor shall ensure that all system notes for are provided post internal review and verification to the System Notes Working Group (SNWG) for inclusion into the consolidated system notes RRM. The Contractor shall participate in the SNWG and update notes as required. Delivery of the RRM and system notes shall be as agreed to by ILS Working group schedules.

5.3 OD 44979 Redlines

The Contractor shall provide redlines to OD 44979 based on PCS TI-16/APB-17 software changes [CDRL A010].

Approved OD44979 documents will be provided as part of Attachment 3 GFI. Delivery schedule of the OD44979 redlines shall be documented in the contractors IMS and as agreed to in the approved ILSWG schedules. Delivery of the OD 44979 redlines shall be consistent with provided GFI.

6. FACILITIES

6.1 Hardware/Software Integration and Test (HSIT) Facilities

The Contractor shall maintain Defense Security Service (DSS) compliant Hardware/Software Integration and Test (HSIT) facilities that provide the resources and environment for development, integration and testing of PCS TI- 16/APB-17 functionality on submarine variants (V) 1, 6 and 9 and common efforts for (V)8. The Contractor shall define any new or replacement TI-16 developmental hardware required to execute all efforts defined within this SOW for all TI-16/APB-17 efforts and all TI-16/APB-17 variants. The Contractor shall procure, receive, assemble, integrate and install any replacement developmental hardware under CLIN 0007 and shall maintain the development hardware under CLIN 0005. The Contractor shall ensure that any tactical hardware or test resources required to support its T&E and Integration approaches are identified in the TEPP and SIP.

The Contractor shall provide hardware troubleshooting, repair, and regular upkeep for all AN/BYG-1 TI-16 project-related hardware. The Contractor shall ensure all equipment is working properly prior to the start of TRR for each AN/BYG-1 TI-16/APB-17 variant. The Contractor shall create and maintain an AN/BYG-1 facilities schedule.

The Contractor shall provide the status of the HSIT maintenance effort including labor cost and ODC (materials) in the IPMR. [CDRL A005]

A-11

6.2 Licenses

The Contractor shall procure software licenses supporting all configurations and deliveries of the TI-16/APB-17 baseline.

Non-Developmental Items (NDI). The Contractor shall be responsible for the procurement of all software licenses for non-GFE Non-Developmental Items (NDI) products delivered in this contract including both contractor developed and third party NDI If the Contractor needs to obtain a license for any NDI incorporated into a deliverable under this contract, the Contractor shall notify the Government immediately in writing. This notification shall specify whether the license(s) that need to be procured are transferable to the Government and/or any of its other contractors. These licenses shall be transferred to the Government in accordance with the technical data clauses in Section I of the contract. The license shall be of the appropriate scope to allow the Government to develop, maintain, use, release, disclose and support (including updates and modifications) the end item throughout the life cycle of the product.

Modified NDI. The Contractor shall provide to the Government all licenses and documentation required by the Government to support any NDI that is modified by the Contractor.