Attachment_2_-_Appendix_D_Eng_Svcs_21Aug14.pdf

N00024-14-R-6203

APPENDIX D

TO

ATTACHMENT 2

Engineering Support Services and Studies

[CLINs 0001-0004, 0101-0104, 0201-0204, 0301-0304, and 0401-0404]

D-i

APPENDIX D

TO

ATTACHMENT 2

TABLE OF CONTENTS

1. SYSTEMS ENGINEERING 1

1.1 Systems Engineering Management Plan (SEMP) 1

1.2 Engineering Documentation Database 1

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 4

1.5.5 Information Assurance (IA) 5

2. SYSTEM DEVELOPMENT 6

2.1 PCS Software Development 6

2.2 Problem Reporting 6

2.3 System Integration Planning 7

2.4 Test Documentation 7

2.4.1 Test and Evaluation Program Plan 7

2.4.2 Test Procedures 7

3. TEST AND EVALUATION 7

3.1 Test Conduct 7

3.2 Testing Support to the Government 8

4. PLATFORM INTEGRATION 8

4.1 System Delivery 8

4.2 Installation Support 8

5. INTEGRATED LOGISTICS SUPPORT 8

5.1 Interactive Electronic Technical Manual (IETM) Source Data 8

5.2 Ready Reference Manual (RRM) 9

5.3 OD 44979 Redlines 9

6. FACILITIES 9

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

6.2 Licenses 10

D-1

APPENDIX D TO ATTACHMENT 2

STATEMENT OF WORK

FOR

ENGINEERING SUPPORT SERVICES AND STUDIES

[CLINs 0001-0004, 0101-0104, 0201-0204, 0301-0304, and 0401-0404]

The Contractor shall provide a level of engineering and technical services supporting the development, sustainment, and maintenance of on-going Technology Insertion efforts as well as other engineering and analysis tasks as requested by the Government and authorized under Technical Instructions. The level of engineering and technical services shall support United States Navy variants, common efforts for Royal Australian Navy (RAN), and RAN-unique requirements. The efforts shall include approved Capability Improvements, Fleet and new construction problem assessment and adjudication; configuration control; software, hardware and logistics troubleshooting; and End of Life issue assessment. Efforts shall also include engineering support for other unique studies and analysis, not associated with the specific TI/APB development efforts defined in Appendices A though C and Appendix E, which may be required during the Period of Performance (PoP) of this contract.

The following Statement of Work (SOW) provides the summation of the three elements efforts:

1) The Contractor shall conduct the engineering effort for TI-16/APB-17, TI-18/APB-17, and TI-18/APB-19 approved Capability Improvements (CIs) through Test Readiness Review (TRR). The engineering for United States Navy variants and common RAN approved CIs shall be conducted under the applicable Engineering Support Services and Studies CLINs 0001, 0101, 0201, 0301, and 0401.

The Contractor shall conduct the systems engineering, logistics, management efforts, test, delivery, and other tasks under the applicable TI/APB CLINs 0005, 0006, 0007, 0105, 0106, 0107, 0205, and 0206.

(2) The Contractor shall provide support to the TI-16/APB-17, TI-18/APB-17 and TI-18/APB-19 configurations after completion of the initial variant Delivery Readiness Review (Legacy Support) for USN/RAN Shared under CLINs 0001, 0101, 0201, 0301, and 0401 and RAN Unique CLINs 0003, 0103, 0203, 0303, and 0403.

(3) The Contractor shall support all RAN Unique requirements including engineering, systems engineering, logistics, management efforts, test, delivery, and facilities, including the approved CIs, under the RAN Unique CLINs 0003, 0103, 0203, 0303, and 0403.

1. SYSTEMS ENGINEERING

The Contractor shall provide a Systems Engineering Lead for the engineering efforts 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 all legacy and other efforts as authorized under Technical Instruction.

1.1 Systems Engineering Management Plan (SEMP)

The Contractor shall update the Systems Engineering Management Plan (SEMP) as required to accommodate modifications in processes driven by, or additional processes required to support, legacy configuration changes.

[CDRL A015]

1.2 Engineering Documentation Database

The Contractor shall update and maintain the Contractor Integrated Digital Environment databases (i.e. Dynamic Object-Oriented Requirements System (DOORS) in support of effort through TRR for authorized CIs and post-DRR

D-2

(Legacy) changes to the TI-16/APB-17, TI-18/APB-17 and TI-18/APB-19 requirements, plans and procedures

[CDRL A016]

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 legacy PCS configurations meet and/or sustain 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 design, legacy configuration updates, integration, installation and performance assessment:

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, assessing and documenting capability and requirements changes for the TI-16/APB-17, TI-18/APB-17 and TI-18/APB-19 configurations. Capability changes to these configurations shall be adjudicated and authorized by the Government via Technical Instruction. 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 the TI-16/APB-17, TI-18/APB-17 and TI-18/APB-19 configurations.

The Contractor shall develop and deliver the TI-16/APB-17, TI-18/APB-17 and TI-18/APB-19 PCS capabilities as approved and authorized by the Government.

The Contractor shall assist in coordinating efforts between modernization and new construction VIRGINIA Class programs to target and support a common (to the extent practicable) TI-16/APB-17 baseline for installation during new construction. This shall include efforts for functional requirements determination and interface definition. The Contractor shall assist in reviewing and providing PCS inputs for all applicable VIRGINIA Class Block IV TI-16 new construction ship specifications and Functional Requirements Documents (FRDs).

1.5.1 Requirements Documentation

The Contractor shall develop and provide updates of the following requirements documentation for legacy PCS configurations based on changes adjudicated and authorized by the Government:

D-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

For legacy changes, the Contractor shall continue to manage interface requirements and ensure PCS interface integrity, based on changes adjudicated and authorized by the Government, in accordance with the processes established by the Government-approved Contractor SEMP [CDRL A015] and System/Subsystem Design Description (SSDD) [CDRL A019] originally provided for TI-16/APB-17 development.

The Contractor shall interact with the SWFTS subsystems and weapons/payload/launcher systems to ensure continued compliance with the 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).

The Contractor shall manage interface change activity and participate in the SWFTS Baseline Management System.

The Contractor shall 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. The Contractor shall also 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 legacy PCS configurations:

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.

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.

For any changes to legacy PCS baselines, the Contractor shall ensure frequent and continuous design disclosure to Navy designated third-party developers throughout the development/upgrade process.

D-4

1.5.3.2 System Design Documents

The Contractor shall provide for the update and delivery of the following design documentation for legacy PCS configurations based on changes adjudicated and authorized by the Government:

• 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 changes, if any, to the overall software Computer Software Configuration Item (CSCI) structure, functional flows and interface requirements, including external PCS interface requirements. The Contractor shall update the separate variant or platform sections as required due to unique variant or platform requirements changes.

The Contractor shall also generate SWFTS-level interface documentation changes, including Group Requirements Lists (GRLs), as required to support legacy PCS configuration changes.

1.5.3.3 Technical and Design Reviews

Technical and design reviews shall be for TI-16/APB-17, TI-18/APB-17, and TI-18/APB-19 PCS legacy configurations support and shall address only the impact of required, approved changes. Reviews shall be held at the Contractor’s facility or via teleconferencing, to discuss and evaluate overall progress and the status of the approved fixes or updates.

1.5.3.4 Hardware Design

The Contractor shall work with the Technology Insertion Hardware (TIH) contractor and other hardware contractors to ensure that any form/fit/function hardware replacements prompted by End of Life (EOL) issues meets the requirements of the system performance specification. The Contractor shall provide engineering services to support EOL hardware studies or form/fit/function replacement studies. The Contractor shall support 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 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 update the Contractor’s System Safety Program Plan (SSPP) as required to describe the system safety management and system safety engineering tasks and activities required to identify, evaluate, and eliminate/ control hazards, or reduce the

D-5 associated risk to a level acceptable by PMS425. [CDRL B001] The Contractor shall provide updates to the SSPP to address specific analyses and activities required to achieve overall system safety objectives for legacy PCS configurations.

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 chair AN/BYG-1 Safety Working Groups to be held quarterly at the contractors facility

• Provide support to 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 updates for the following safety analyses/reports for the legacy 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), the SSHA shall consist of two parts hardware and firmware/software which may be separate deliverables [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 DoDD 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, D-6 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 PCS Software Development

The Contractor shall maintain its software engineering process in support of the PCS capability items and legacy configurations.

The Contractor shall provide updates to the Software Development Plan (SDP) as required to accommodate modifications in processes driven by, or additional processes required to support, the legacy configuration changes.

The Contractor shall manage, develop, update, test and deliver the authorized PCS computer software updates in accordance with the SDP. [CDRL A023]

The Contractor shall provide the following software development services for the Capability Improvements changes and for new legacy builds driven by changes authorized by the Government:

• 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

2.2 Problem Reporting

The Contractor shall maintain a single Problem Trouble Report (PTR) system for the identification, tracking and resolution of all PCS software and baseline documentation problems identified prior to and post-RTF. 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.

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.

D-7

The Contractor shall support the VIRGINIA Class CPR Adjudication Board (CAB) for new construction TI/APB configurations.

2.3 System Integration Planning

The Contractor shall support overall AN/BYG-1 integration as well as system-level integration of the variants and delivery of associated logistics products for new builds driven by changes authorized by the Government. 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 the updated software to the PCS configurations.

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 any updated PCS legacy software 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 update the Test and Evaluation Program Plan (TEPP) as required to accommodate modifications in processes driven by, or additional processes required to support, legacy configuration changes.

[CDRL A026]

2.4.2 Test Procedures

The Contractor shall review the applicable PCS legacy configuration Test Procedures and update and deliver new procedures as required to support legacy configuration changes. [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 updated legacy 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. The Contractor shall provide test lead support and test meeting support for all T&E efforts within this SOW.

3.1 Test Conduct

The Contractor shall document and conduct Test Readiness Reviews (TRRs) as required for PCS legacy configuration changes to ensure the system software is baselined, 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 authorized by the Government.

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

D-8

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

g) Generation and delivery of Test/Inspection Reports including Test Completion 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 System Level Tests (SLTs), System Integrated Tests (SITs), and dockside or at-sea tests as required to support the final verification of requirements. The Contractor shall also provide PCS support, as required, for follow-on Developmental Test/Operational Test (DT/OT) and Technical Evaluation (TECHEVAL) including the potential to provide riders during at-sea testing.

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 new legacy software build final delivery 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.

The Contractor shall generate and deliver the software media executable data files and Software Version Description (SVD) document to support software installation on the individual platforms as directed by the Government. The SVD shall include separate sections for any unique platform requirements. [CDRLs A024, A025]

4.2 Installation Support

The Contractor shall provide source data supporting Engineering Change Instruction (ECI) development for platform modernization.

5. INTEGRATED LOGISTICS SUPPORT

5.1 Interactive Electronic Technical Manual (IETM) Source Data

The Contractor shall provide updates to PCS legacy baseline Interactive Electronic Technical Manual (IETM) source data to support Government or other Contractor modifications to the AN/BYG-1 IETM. [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-14 APB-13 provided as GFI (Attachment 3 GFI). The contractor shall develop source data that is S1000D compliant in a government approved S1000D database environment. TMCR NO. NDMS- 090092-000 shall be used as a reference. The contractor shall provide subject matter expertise to support comment 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.

D-9

Delivery schedule of IETM source data shall be documented in the contractor’s Integrated Master Schedule (IMS) and support the AN/BYG-1 Integrated 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 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 to support maintaining the TI-16 and TI-18 configurations upon their transfer from the development CLINs. The Contractor shall define any new or replacement TI-16 or TI-18 hardware required to execute all efforts authorized by Technical Instructions. The Contractor shall procure, receive, assemble, integrate, install, and maintain the new hardware under authorized Technical Instruction(s).

The Contractor shall define any unique RAN TI-16 and/or TI-18 hardware required to execute (V)8 efforts authorized by Technical Instructions. The Contractor shall procure, receive, assemble, integrate, install, and maintain the new (V)8 hardware under authorized Technical Instruction(s).

The Contractor shall provide hardware troubleshooting, repair, and regular upkeep for all transitioned AN/BYG-1 hardware. The Contractor shall ensure requirements for the use of legacy PCS hardware are included in the overall 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]

D-10

6.2 Licenses

The Contractor shall procure software licenses supporting all configurations including any licenses required for delivery of updated legacy baselines.