Attachment 1-SOW for Airborne Laser Mine Detection Systems.docx

Attachment 1 Statement of Work (SOW) for Production of the AN/AES-1 Airborne Laser Mine Detection System (ALMDS)

N00024-13-R-6318

20 June 2013

Prepared By:

Program Executive Office, Littoral Combat Ships (PEO LCS) Mine Warfare Program Office (PMS495) Washington Navy Yard, D.C.

DISTRIBUTION STATEMENT D: DISTRIBUTION AUTHORIZED TO DOD AND U.S. DOD CONTRACTORS ONLY: ADMINISTRATIVE/OPERATIONAL USE. OTHER REQUESTS SHALL BE REFERRED TO PEO LCS (PMS 495).

DESTRUCTION NOTICE – For classified documents, follow the procedures in DOD 5220.22-M, National Industrial Security Program Operating Manual, Chapter 5, Section 7 or DOD 5200.1-R, Information Security Program Regulation. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction.

Table of Contents

Statement of Work (SOW) for the AN/AES-1 Program

FIXED PRICE AND COST PLUS EFFORTS:

1.0 GENERAL

The AN/AES-1 Airborne Laser Mine Detection System (ALMDS) consists of the hardware, software, material, data, and services required to rapidly detect and classify near surface Mine-Like Objects (MLOs).

The Contractor will fabricate, integrate, test and deliver the ALMDS Systems, Peculiar Support Equipment (PSE), and provisioned items, including any changes as a result of government approved Engineering Change Proposals (ECPs).

1.1 Scope

This Statement of Work (SOW) describes the effort required to produce the ALMDS Systems, ALMDS PSE, and provisioned items including the fabrication, integration, testing, and delivery in accordance with the Technical Data Package (TDP) provided as Government Furnished Information (GFI). This SOW also describes Engineering Services, Depot Services, and Software Support for the ALMDS Program.

1.2 Background

ALMDS is a laser-based electro-optic Airborne Mine Countermeasures (AMCM), high-area-coverage system that detects, classifies, and localizes floating and near surface moored MLOs. ALMDS will be deployed on the MH-60S helicopter.

1.3 Description

Each set of ALMDS fleet deliverable hardware consists of an ALMDS and PSE. The Contractor shall be responsible for the production of the ALMDS, the PSE, and Provisioned Items in accordance with the TDP.

2.0 APPLICABLE DOCUMENTS

The following documents form a part of this SOW as specified below. Military Standards and Specifications shall be used only when there is no Best Commercial Practice or Commercial Specification acceptable to the Government.

2.1 Military Standards

20 Jan 05

MIL-STD-461F

MIL-STD-464C

MIL-STD-810G

MIL-STD-882E

2.2 Commercial Specifications and Standards

2.3 Other Government Documentation

3.0 TECHNICAL REQUIREMENTS

FIXED PRICE EFFORTS:

3.1 Production Team

The ALMDS team members include Program Executive Office (PEO) Littoral Combat Ship (LCS), Mine Warfare Program Management Office (PMS495), Naval Surface Warfare Center Panama City Division (NSWC PCD), the Contractor, and other subject matter experts as required. PMS495 is the program manager for ALMDS and NSWC PCD is the Technical Design Agent (TDA).

Northrop Grumman is the Depot certified facility through FY2014. The Contractor shall perform Depot Services beginning in FY2015.

Northrop Grumman Aerospace Systems is the Software Support Agent (SSA) for the ALMDS program through FY2015. The Contractor shall perform SSA Services beginning in FY2016.

3.2 Government Furnished Property (GFP) or Information (GFI)

Property supplied by the Government for use on this contract is listed in the GFP List, Attachment 6. Information supplied by the Government for use on this contract is listed in the GFI List, Attachment 2.

3.3 Program Management

3.3.1 Program Management Planning and Management

The Contractor shall plan, control, coordinate, execute and oversee all its activities performed under this contract. The Contractor shall meet all technical performance, cost, schedule and delivery requirements of this contract. The Contractor shall develop and deliver a Program Management Plan (PMP), Integrated Master Schedule (IMS), and Work Breakdown Structure (WBS). The Contractor shall perform subcontract management to ensure performance and quality of all work performed under this contract. (CDRLs A001/A002/A003/B001)

3.3.2 Post Award Orientation

The Contractor shall participate in a Post Award Orientation conducted by the Contracting Officer. The purpose of the Post Award orientation will be to (1) achieve a clear and mutual understanding of all contract requirements, and (2) identify and resolve potential problems. See FAR 42.5 for information regarding the Post Award Orientation. (CDRLs A004, A005)

3.3.3 ALMDS PM Integrated Product Team

The Contractor shall participate in a Government led ALMDS Program Management (PM) Integrated Product Team (IPT). The Contractor’s Program Manager and Lead Engineer or Engineering Manager shall participate in the Program Management IPT. The IPT shall meet weekly via teleconference for the duration of the contract. (CDRLs A004, A005)

3.3.4 Program Management Reviews (PMRs)

The Contractor shall conduct monthly PMRs to brief the ALMDS PM on program status and to resolve any program issues and concerns. These meetings shall be at the Contractor’s facility or at some other mutually agreeable site. (CDRLs A004, A005)

3.3.5 Quarterly Program Reviews

The Contractor shall conduct Quarterly Program Reviews (QPRs) beginning three months after contract award. QPRs shall be at the Contractor’s facility or at some other mutually agreeable site. The QPRs shall provide the Government maximum visibility into the conduct and consequences of the Contractor’s efforts and decisions on the program. The Contractor shall present manufacturing, integration, schedule performance status, problem areas, results of trade studies and recommended corrective actions at each QPR. The Contractor shall ensure Configuration Management (CM), Quality Assurance (QA), manufacturing, logistics, system safety, system integration, and system testing topics are highlighted and addressed at each QPR. The Contractor shall generate audio-visual aids as necessary for use in conducting program status reviews and audits. (CDRLs A004, A005)

3.3.6 Program, Data, and Risk Reporting

The Contractor shall provide a progress, status and management report on a monthly basis to PMS 495. (CDRL A006) The Contractor shall generate a Data Accession List and update it monthly for the life of the contract. The Contractor shall include all data generated that was exclusively Government funded by this contract. The Contractor shall also include all data generated that was partially Government funded by this contract. The Contractor shall report the appropriate data rights for each data item. (CDRL A007) The Contractor shall use the PMS495 approved risk management template (Attachment 9) for introducing new risks or updating existing risks. The Contractor shall provide a risk management status report documenting all risks on a monthly basis for the life of the contract. The Contractor shall participate in one-hour risk management meetings once every two weeks for the duration of the contract. (CDRL A008)

3.4 Production Engineering

The Contractor shall provide production engineering to address issues or problems impacting all hardware produced under this contract. The Contractor shall provide production, integration and software uploading support for all hardware produced under this contract. (A006)

3.4.1 ALMDS Pod Subsystems

The Contractor shall procure, fabricate, integrate, test and deliver ALMDS Pod Subsystems (APS) in accordance with the Government furnished TDP. The APSs shall meet all functional, allocated, and product baseline requirements listed in Section 3.8.2. (CDRL A009)

3.4.2 Peculiar Support Equipment

The Contractor shall procure, fabricate, integrate, test and deliver the PSE specified in Attachment 5. (CDRL A009)

3.4.3 Tools

The Government will provide the GFP, which is listed in Attachment 6. The Contractor shall supply all other tools required to procure, fabricate, integrate, test and deliver ALMDS, PSE, and Provisioned Items. The Contractor shall perform processes for documenting and controlling all tools. The Contractor shall maintain calibration of all tooling, including GFP.

3.5 Component Selection

The assembly of the production system requires the procurement of subsystems and components by various vendors. The TDP, provided as GFI under Attachment 2, provides drawings and vendor information for the procurement of these parts.

The Contractor shall inform PMS495 of its intent to use vendors not identified in the TDP (Attachment 2). The Contractor shall provide a Qualification Plan for any system components procured from vendors other than those used during previous ALMDS LRIP contracts and provide rationale, certification and qualification evidence to the government. (CDRL A010) PMS495 will approve the use of non-certified/qualified vendors by reviewing qualification test plans and notifying the Contractor of acceptance or disapproval. PMS495 will approve the qualification of non-certified/qualified vendors by reviewing qualification test results and notify the Contractor of acceptance or disapproval. (CDRL A012)

3.5.1 Component Obsolescence Management

The Contractor shall track and report obsolescence status during the life of the contract and shall conduct Diminishing Manufacturing Sources and Diminishing Material Sources (DMSMS). When requesting quotes and when placing orders for parts and components, the Contractor shall request obsolescence information. The Contractor shall provide a quarterly report identifying end of life dates for parts. The Contractor shall provide recommendations and suitable replacement parts as part of the report. (CDRL A011)

3.6 Production Facilities

In accordance with the TDP, the Contractor shall provide production facilities to support the production, fabrication, integration, test, and shipment of all systems, subsystems and PSE that are part of ALMDS. The Contractor shall handle system components during assembly and test. The Contractor shall provide a laser facility to test the system as a fully integrated system in the far field (i.e. over lengths similar to normal operating altitude) as specified by the Ground Test Plan and Procedure for Outdoor Laser Transmission Testing of the Airborne Laser Mine Detection System (ALMDS) Low Rate Initial Production (LRIP) Pod Subsystem, provided as GFI, Attachment 2.

3.7 ALMDS Testing

For each production system, the Contractor shall verify all requirements identified in the functional baseline. Test of the APS, PSE, and Provisioned Items shall comply with the test procedures, which shall be based on GFI, tailored by the Contractor and approved by the Government. (A012) ALMDS testing shall consist of sub-assembly test and final system assembly Factory Acceptance Test (FAT) of each system provided by the Contractor at the Contractor’s facility. PSE and Provisioned Items testing may require only a single test procedure. (A012) The Government will provide GFP listed in Attachment 6. The Contractor shall obtain all other jigs, fixtures, and special test equipment. The Contractor shall perform processes for documenting and controlling all special test equipment. The Contractor shall maintain calibration of all test equipment, including GFP.

If there are deficiencies cited during the testing, the Contractor shall generate Deficiency Reports (DRs). The Contractor shall correct all deficiencies and retest to verify corrections have been made. The Contractor shall determine if the issue may have existed with previously tested or delivered units. If the Contractor determines that similar deficiencies may exist in delivered ALMDS units, the Contractor shall notify the Government of this potential lack of compliance with the requirement within seven (7) days of its determination. Any changes required to address these deficiencies to units delivered and/or in production shall be made at no additional cost to the Government. (CDRL A014) If directed by the Government through a contract modification in response to a formal Engineering Change Proposal (ECP), the Contractor shall upgrade the existing ALMDS units with the appropriate changes to bring the unit into compliance with the requirement.

The Government reserves the right to observe the processes, facilities, equipment, tooling, and/or testing at any point during performance under this contract.

3.7.1 Component Testing

The TDP identifies components that are certified with qualification tests. Qualification tests required may include tests such as Acceptance Test Procedures and Environmental Stress Screening, which are identified in the TDP. Qualification tests shall fully verify each component’s allocated requirements. The Contractor shall submit all component test procedures to PMS 495 for review and approval before being formally tested. The Contractor shall ensure that vendors complete the qualification test identified in the appropriate specification. The Contractor shall provide the schedule for qualification testing. (CDRL A013, A014)

3.7.2 Factory Acceptance Test (FAT) Plan, FAT Procedures, and Specification Requirements Verification Matrix (SRVM) Validation The Factory Acceptance Test (FAT) Plan and FAT Procedures generated and used by the prior ALMDS contractor are included as GFI (Attachment 2). Prior to the conduct of FAT, the Contractor shall tailor these documents and generate additional documents as necessary to verify that all ALMDS Detail Specification, Environmental Profile Plan (EPP), and Interface Requirements Specification requirements are satisfied. (A013) The ALMDS Specification Requirements Verification Matrix (SRVM) is provided as GFI in Attachment 2. The Contractor shall update the SRVM to clearly show traceability from each requirement of the ALMDS Detail Specification, Interface Requirements Document (IRD), and EPP to the specific test procedures that provides compliance with that requirement. (CDRL A013)

3.7.3 Factory Acceptance Test (FAT)

The Contractor shall perform FAT on each production unit in accordance with the approved FAT Plan and Procedures. The Contractor shall conduct FAT at the Contractor’s facility.

The Contractor shall prepare a FAT Report which shall include appendices, any/all notes produced by individuals during testing, test analyses, error analyses, confidence levels, all computerized data collection, and reduction results. (CDRL A014)

3.7.4 Verification Flight Tests

The Government will perform Verification Flight Test (VFT) on all Contract Line Item Number (CLIN) 0001 systems. The Contractor shall provide the selected system for the conduct of Verification Flight Testing to the TDA located at NSWC PCD. The Government will be responsible for all testing. The VFT shall verify the adequacy of the FAT to thoroughly test that the ALMDS conforms to the requirements of the contract while mounted to a MH-60S helicopter. The Government will provide results of the VFT by documenting the performance of the ALMDS and providing raw data, processed data, oceanographic data, and target ground truth. The Government reserves the right to perform VFT on any additional production deliveries. The Contractor may witness the verification flight testing. The Contractor shall be responsible for corrections to production deliveries if issues or failures occur during VFTs at no additional cost to the Government. The systems will be conditionally accepted until they pass VFT acceptance.

3.8 Configuration Management

The Contractor shall provide configuration management in accordance with the Configuration Management (CM) Plan for PMS 495 Systems and Equipment ,provided under Attachment 2 as GFI, and CONFIGURATION MANAGEMENT (NAVSEA) (APR 2004) (modified January 2013). In the event that the Statement of Work, CONFIGURATION MANAGEMENT (NAVSEA) (APR 2004)(modified 24 January 2013), and Configuration Management Plan for PMS 495 Systems and Equipment do not align, the Configuration Management Plan for PMS 495 Systems and Equipment shall take precedence.

3.8.1 Configuration Management Planning and Management

The Contractor shall develop a Configuration Management Plan (CMP). The Contractor shall follow this CMP for all configuration items. The Contractor shall submit proposed changes or proposed deviations from the CMP. (CDRL A015)

3.8.2 Configuration Identification

The functional baseline for the ALMDS consists of the following documents, which are provided in Attachment 2:

The allocated baseline is defined by the following specifications, which are provided in Attachment 2:

7/10/2008

7/10/2008

7/10/2008

7/10/2008

The product baseline is defined by the TDP and the following specifications, which are provided in Attachment 2:

The Contractor shall place all baselines under internal configuration control. The Contractor shall use the drawings and specifications referenced in the attached ALMDS TDP as the baseline upon which the system will be produced. The Contractor shall update and maintain the TDP through the production period. The Contractor shall deliver the final TDP after the FAT and PCA are complete. (CDRL A016)

3.8.3 Configuration Change Management

The Government is the configuration change authority for all baselined configuration items. The Contractor shall not deliver a component that deviates from the product, allocated, or functional baseline unless authorized by the Government. Each request for deviation from a baseline shall be submitted to the Government as a Request for Deviations (RFDs) as outlined in the PMS495 CM Plan. Previous versions of approved deviations are provided as GFI. (CDRL A017)

System changes shall be through the Engineering Change Proposal (ECP) process as outlined in the PMS495 CM Plan, provided as GFI (Attachment 2). Following approval of any Formal ECP, the Contractor shall document and update the TDP as a result of Government approved changes to the baseline. As part of the TDP, the Contractor shall maintain the GFI provided drawing tree to reflect approved ECP changes. (CDRLs A016, A018, A019, A020, A021)

The Contractor shall incorporate all approved ECPs into its schedule, processes, production, integration, and tests.

3.8.4 Configuration Status Accounting

The Contractor shall maintain Configuration Status Accounting (CSA) information for each Configuration Item (CI) in the product baseline. The Contractor shall submit a Configuration Status Accounting Report quarterly. (CDRL A020)

The CSAR shall include, at a minimum:

1. A record of approved configuration documentation and identification numbers.

2. Status of proposed ECPs, ECOs, and Deviations to the configuration.

3. Implementation status of approved changes.

4. Configuration of all hardware (units) and software of the CI in the operational inventory.

The Contractor shall flow down and control the CM requirements of the contract to suppliers and subcontractors.

3.8.5 Configuration Verification and Audit

The ALMDS TDP and any modifications to the TDP authorized by the government will be validated during the Physical Configuration Audit (PCA) and the Contractor shall update the TDP based on the PCA results. A moratorium on changes shall be imposed during the period of the audit. Any changes in the process of being incorporated shall be presented to the audit team as a list of outstanding changes.

The Contractor shall use an incremental approach for the conduct of each PCA event. The Contractor shall be responsible for establishing the time and place of the PCA, in accordance with the Integrated Master Schedule (IMS) and with the coordination of the Government. The PCA shall be conducted on one ALMDS unit selected jointly by the Government and the Contractor. PCA will not be conducted on the PSE. The PCA shall include the following:

a) Necessary hardware, facilities, personnel, documentation, and resources to support each incremental PCA.

b) Detail plans and procedures to conduct each incremental PCA (CDRL A022).

c) Applicable specifications, drawings, manuals, schedules, and design and test data.

d) Tools and inspection equipment necessary for evaluation and verification.

The PCA may require the disassembly of each item selected and the removal of modular/replaceable assemblies to make visible all assemblies/piece parts; and may require reassembly. Any difference between the item and the Contractor’s drawing package observed shall be recorded and considered a potential discrepancy. The PCA shall disclose and record all workmanship discrepancies. The Contractor shall generate a report to document findings, corrective actions, and completion dates for reported discrepancies. (CDRL A023)

Upon completion of the PCA and Government acceptance of the corrective actions for the discrepancies, the Product Baseline will be considered validated.

3.9 Safety Program

The Contactor and its Subcontractors shall log, identify, and report to the Government all hazards discovered during the performance of this contract. The Contractor and its Subcontractors shall enact and report enactment to the Government of all safety measures used to mitigate or reduce the safety risks discovered during the performance of this contract. (CDRL A006)

3.10 Hazardous Material

The Contractor shall evaluate all engineering changes or manufacturing process changes to identify if there is newly required hazardous material, newly produced hazardous material or hazardous material eliminated from the process by the incorporation of an ECP or a manufacturing process change.

3.11 Security

The Contractor shall comply with the provisions outlined in the Department of Defense Contract Security Classification Specification, DD Form 254 provided as Attachment 4.

3.12 Quality Assurance Program

The Contractor shall establish, implement, and maintain a Quality Control System in accordance with the International Organization for Standardization (ISO) 9001-2008.

The Contractor shall develop a Quality Assurance Plan (QAP). The Contractor shall follow this QAP at all times during the execution of this contract. The Contractor shall submit proposed changes to the QAP for Government approval. The Contractor shall submit proposed deviations from the QAP for Government approval. The Contractor shall make QA personnel available in accordance with the Contractor’s internal process to assist with performing conformance inspections. (CDRL A024) The Contractor shall use a Quality Management System (QMS) to review and monitor the test procedures and test data sheets throughout product testing. The Contractor shall ensure its Quality Department monitors, witnesses, and documents all testing.

3.12.1 Responsibility for Inspection

The Contractor shall perform all inspection requirements as specified in ISO-9001-2008. The Contractor shall flow down inspection requirements to their suppliers and subcontractors. Inspection and test records shall include, as a minimum, the nature of observation, number of observations made, and the number and type of deficiencies found. Inspection and test records shall be complete and accurate. The Contractor may use the Contractor’s and/or sub-supplier facilities to ensure supplies and services conform to ISO-9001-2008 prescribed inspection requirements. The Government reserves the right to perform inspections at any time. (A023)

3.12.2 Calibration System Requirements

The Contractor shall establish and maintain a calibration system for all measuring and test equipment in accordance with ISO-10012-1 and/or ANSI-Z540-1. For the purposes of control of test parameters, measurements, and recording of test data the Contractor shall use calibrated instruments and test equipment whose uncertainty is less than one-third of the maximum allowable tolerance for the measured or controlled parameters.

3.12.3 Environmental, Safety, and Occupational Health Requirements The Contractor shall verify that production complies with all applicable local, state, and federal environmental protection laws regulations, treaties, and agreements.

3.13 Parts Control and Standardization Program

The Contractor shall implement an internal parts management system in accordance with the Contractor’s internal methodology. The Contractor shall notify the Government in writing upon discovery of any defective conditions in military specifications, vendor qualified parts, components, materials, or processes that may adversely affect the execution of this program.

3.14 Item Unique Identification and Valuation of Items and Radio Frequency Identification Item Unique Identification (IUID) data plates shall be placed on each qualifying component using the IUID Implementation Plan supplied by the Government as GFI under Attachment 2.

3.15 Production Support

3.15.1 Reliability, Maintainability, and Availability Program The Contractor shall conduct closed loop Failure Reporting, Analysis, and Corrective Action System (FRACAS) for all ALMDS components supplied under this contract for all failures occurring during system debugging, checkout, test, and operational use. The Contractor shall use FRACAS to record, categorize, and analyze failures of the ALMDS system, PSE, and provisioned items during the production phase to identify any trends that may jeopardize the availability of the system. The Contractor shall retain failure reports to the lowest level of depot repair. (CDRL A025)

The Contractor shall measure supportability parameters such as Inherent Availability, Operational Availability, Mean Time between Operational Mission Failure (MTBOMF), Mean Time to Repair (MTTR), and Mean Logistics Delay Time (MLDT) on a monthly basis for analysis to improve baselines.

The Contractor shall assess corrective action effectiveness. The Contractor shall report reliability trends and shall provide recommendations to improve the reliability of the ALMDS using the ECP process. The Contractor shall institute an ALMDS reliability growth program.

3.15.2 Technical Publications

The Contractor shall supply source data as required to update the ALMDS publications provided as GFI based on approved engineering changes. The contractor shall supply source data for changes to existing operator and maintenance procedures or any required new procedure. (CDRL A026)

3.15.3 Packaging, Handling, Storage and Transportation

The Contractor shall package, handle, store, and transport with best commercial practices unless otherwise noted. The ALMDS shall be delivered within the specified ALMDS shipping container provided as GFP. The PSE shall be delivered in their respective GFP cases.

3.15.4 Human Systems Integration, Manpower and Training

The Contractor shall supply source material and technical data for approved changes to existing training or proposed new training resulting from approved ECPs.

3.15.5 Demilitarization and Disposal Support

The Contractor shall recommend updates to the existing Demilitarization and Disposal Plan provided as GFI under Attachment 2, in accordance with the latest guidance. For any lower level component, special demilitarization and disposal instructions shall be identified in the procedures. (CDRL A011)

3.15.6 Post Production Support

Prior to the closing of the production line, the Contractor shall provide a Post Production Support Plan. The Contractor shall also detail the life cycle support requirements of the ALMDS to ensure life cycle supportability. This analysis shall present mitigation options to projected problems due to inadequate sources of supply, support capabilities, or modification after shutdown of production lines; include subsystem vendor projections and recommended mitigating options; and use as its baseline the TDP and its approved changes. (CDRL A027)

3.16 Integrated Digital Environment (IDE) and Electronic Commerce/Electronic Data Interchange (EC/EDI) All of the processes and products of the contract must be readily visible and available to the Government for review to implement fully and effectively DoD Acquisition Reform initiatives for IDE and EC/EDI.

The Contractor shall establish an IDE and EC/EDI in accordance with MIL-PRF-28000B, MIL-PRF-28001C, MIL-PRF-28003B, and DoD 5000.2-R. The Contractor shall use MIL-STD-1840C and DoD 5000.2-R in establishing the IDE and EC/EDI systems used in executing the contract. The database must be compliant with the requirements of the Navy Marine Corps Internet (NMCI).

This contract may result in updates to technical and engineering data characterizing the design criteria and every process necessary for full disclosure of the fabrication and testing of the end item. In support of these efforts, analyses, and trade studies may be developed. The Contractor shall make this information accessible to the Government in real-time through the EC/EDI solution and tools. The Contractor shall use email, computer bulletin boards, Adobe (pdf), and other similar technologies for exchanging data. The Contractor shall also optimize the EC/EDI solution to provide direct access for initial and subsequent submittals of all contract data deliverables.

3.16.1 Data Rights

At a minimum, the Government shall have unlimited data rights and ownership of all data produced, developed or updated as a result of this contract. Data shall include but is not limited to system drawings, manufacturing fixtures, special tooling drawings, models, reports, and procedures. The Contractor shall immediately notify the government if the Contractor believes they are entitled to different rights.

COST PLUS EFFORTS:

3.17 Engineering Services

The Contractor shall provide engineering services to support the Government as required per issued Technical Instructions. The Engineering Services to be performed shall be in accordance with SECTION C of the contract. (CDRL B004)

3.17.1 Monthly Status Reports

The Contractor shall deliver a monthly status report to the Government that includes sections for labor hours expended by Resource Code (RC), meetings, work performed, accomplishments, and risk areas under the Engineering Services CLIN. Each Technical Instruction is required to be accounted for in each section of the monthly status report. The report shall be part of the coordinated monthly submission for the contract. (CDRL A006) Technical Instructions will be issued in accordance with the NAVSEA Technical Instruction Template (Attachment 7).

3.17.2 Travel

Travel requirements shall be documented within the individual TIs under the Support Services CLINs.

3.17.3 Material

The Contractor shall procure the materials required to perform engineering services. Material requirements shall be documented within the individual TIs under the Engineering Services CLINs.

3.18 Depot Support

The Depot shall be responsible for maintaining ALMDS production assets for the Navy. The Depot certified facility is Northrop Grumman through 30 November 2014 (FY15). The Contractor shall achieve Depot certification by 1 December 2014 (FY15).

The Contractor shall support maintenance of delivered hardware as required by the Government. This includes all preventative (scheduled) maintenance and required corrective maintenance (unscheduled) of the equipment during test events and during the period of performance of this contract. The Contractor shall maintain all ALMDS LRIP and FRP units under this contract. The Contractor shall develop maintenance procedures for the receipt, diagnosis, repair, re-verification, and shipment of all Configuration Items (CIs). (B005)

The Contractor shall provide repair estimates to the Contracting Officer and Contracting Officer Representative (COR) for a decision to repair or replace and shall quote repairs individually. The Contractor shall obtain Government approval of repair estimates before beginning a maintenance action. (CDRL B006)

The Contractor shall provide the Government with all actions performed on the hardware since the last time the hardware was declared Ready for Issue (RFI) and the cost to perform them. The Contractor shall provide the Government with all discrepancies between the TDP and the hardware at the time it was declared RFI. The Contractor shall provide the Government with all as-run test procedures executed to declare the pod RFI. (CDRL B007) The Depot shall conduct closed loop Failure Reporting, Analysis, and Corrective Action System (FRACAS) for all ALMDS components regardless of initial manufacturer for all failures occurring during system debugging, checkout, tests and operational use. The Contractor shall use FRACAS to record, categorize, and analyze failures of the ALMDS system, PSE, and provisioned items to identify any trends that may jeopardize the availability of the system. The Contractor shall retain failure reports to the lowest level of depot repair. The Contractor shall provide failure summaries monthly after depot certification. (CDRL B003) The Depot shall measure supportability parameters such as Inherent Availability, Operational Availability, Mean Time Between Operational Mission Failure (MTBOMF), Mean Time to Repair (MTTR), and Mean Logistics Delay Time (MLDT) on a monthly basis for analysis to improve baselines.

The Depot shall assess corrective action effectiveness. The Depot shall report reliability trends and shall provide recommendations to improve the reliability of the ALMDS. The Depot shall continue the ALMDS reliability growth program.

3.19 Software Support

The Contractor shall maintain a Software Support Activity (SSA) for all ALMDS. The SSA facility is Northrop Grumman through FY2015. The Contractor shall function as the SSA beginning in FY2016. The Contractor shall ramp up their ALMDS software capabilities to fully be capable of transition in FY2016. Until the Contractor becomes the SSA, the Contractor shall install the software delivered from the Government. All deliverables shall be compatible with the software delivered as part of the GFI (Attachment 2). Once the Contractor becomes the SSA, it will install the software. Any ECPs or hardware submitted prior to or during the transition period shall account for software compatibility with the latest Government approved software build. The Government will notify the Contractor of any changes to the software baseline delivered as part of the GFI. At the time of contract award, the current software build version provided as GFI is Software Version 5077.

The SSA shall maintain the APS Computer System Configuration Items (CSCIs) to add or remove functionality, to improve performance, or to correct deficiencies identified during testing or operations. The Contractor shall request Government approval for each software modification prior to incorporation into release builds through the ECP process defined in the ALMDS CM Plan. The Contractor shall conduct monthly software coordination meetings with the government. (B001/B002) The Contractor shall define a software development approach appropriate for the computer software effort to be performed under this Statement of Work. The Contractor shall document this approach in a Software Development Plan. The Contractor shall follow this SDP for all computer software to be developed or maintained under this effort. The Contractor shall submit proposed changes to the SDP for Government approval. The Contractor shall submit proposed deviations from the SDP for Government approval. (CDRL B008) The SDP shall define the Contractor's proposed life cycle model and the processes used as a part of that model. In this context, the term “life cycle model” is as defined in IEEE/EIA Std. 12207-2008 (See Section 2.2). The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of this contract. In accordance with the framework defined in IEEE/EIA Std. 12207-2008, the SDP shall define the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks. Because IEEE/EIA Std. 12207-2008 does not prescribe how to accomplish the task, the Contractor must provide this detailed information so the Navy can assess whether the Contractor's approach is viable. The SDP shall contain the information defined by ISO/IEC/IEEE 15289-2011, section 7 (generic content) and the Mapping of ISO/IEC 12207:2008 (IEEE Std 12207-2008) Clauses to Information Items for each Software Life Cycle Process in Table 2 of ISO/IEC/IEEE 15289-2011. In all cases, the level of detail shall be sufficient to define all software development processes, activities, and tasks to be conducted. Information provided must include specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification. The Contractor shall add all information products identified in the SDP and not identified as CDRLs to the Data Accession List. The SDP shall identify the approval authority and data rights for each information product generated during the execution of this contract. The Contractor shall post all DAL items on the Contractor’s IDE in a location accessible to the Government.

Previous software specifications, development plan, and software transition plan are included as GFI within Attachment 2.

image1.jpeg image2.jpeg