PWS_NGMS_5_3_19_posted_with_synopsis.docx

Performance Work Statement (PWS) for ECDIS-N/Navigation/Steering & Propulsion/Machinery Control Systems

1.0 INTRODUCTION

1.0.1 The Naval Surface Warfare Center Philadelphia Division (NSWCPD) is a Department of Defense entity responsible for research and development, test and evaluation, engineering and fleet support organization for the Navy’s ships, submarines, military watercraft and unmanned vehicles. This requirement is for NSWCPD Code 50, which is responsible for surface vessels’ navigation systems, piloting support systems, steering/propulsion control systems, Machinery Control Systems (MCS) and Electronic Charting Display and Information Systems (ECDIS).

1.0.2 This contract is for non-personal services. It does not create employment rights with the U.S. Government whether actual, inherent, or implied

1.0.3 Government / Contractor Relationship

(a) The services to be delivered under this Delivery Order/Task Order are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the Delivery Order/Task Order between the Government and the Contractor's personnel. Therefore, it is in the best interest of the Government to provide both parties a full understanding of their respective obligations.

(b) The Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishable badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence

(c) Contractor personnel under this Contract/Task Order shall not engage in any of the inherently Governmental functions listed at FAR Subpart 7.5 or DFARS Subpart 207.5.

(d) Employee Relationship:

1) The services to be performed under this Contract/ Task Order do not require the Contractor or its personnel to exercise personal judgment and discretion on behalf of the Government. Rather the Contractor's personnel will act and exercise personal judgment and discretion on behalf of the Contractor.

2) Rules, regulations, directives, and requirements that are issued by the U. S. Navy and NSWCPD under its responsibility for good order, administration, and security are applicable to all personnel who enter a Government installation or who travel on Government transportation. This is not to be construed or interpreted to establish any degree of Government control that is inconsistent with a non-personal services contract.

(e) Inapplicability of Employee Benefits: This Contract/ Task Order does not create an employer-employee relationship. Accordingly, entitlements and benefits applicable to such relationships do not apply.

(f) Notice. It is the Contractor's, as well as the Government's, responsibility to monitor Contract/ Task Order activities and notify the Contracting Officer if the Contractor believes that the intent of this Section has been or may be violated.

(1) The Contractor should notify the Contracting Officer in writing within three (3) calendar days from the date of any incident that the Contractor considers to constitute a violation of this Section. The notice should include the date, nature, and circumstances of the conduct; the name, function, and activity of each Government employee or Contractor official or employee involved or knowledgeable about such conduct; identify any documents or substance of any oral communication involved in the conduct; and the estimate in time by which the Government must respond to this notice to minimize cost, delay, or disruption of performance.

(2) The Contracting Officer will, within five (5) calendar days after receipt of notice, respond to the notice in writing. In responding, the Contracting Officer will either:

i. Confirm the conduct is in violation and when necessary direct the mode of further performance,

ii. Countermand any communication regarded as a violation,

iii. Deny that the conduct constitutes a violation and when necessary direct the mode of further performance, or

iv. In the event the notice is inadequate to make a decision, advise the Contractor what additional information is required, and establish the date by which it should be furnished by the Contractor.

1.1 BACKGROUND

NSWCPD provides surface vessel navigation system, steering/propulsion control system, machinery control system and electronic charting, display and information system (ECDIS) subject matter expert (SME) and in-service engineering agent (ISEA) services for the Department of Defense (DoD). These services span all phases of ships’ lifecycles including capability-based assessments, material solutions analysis, technology maturation/risk reduction, engineering manufacturing/design, production/deployment, and operations/support. These services include trade studies, verification and validation (V&V), installation/installation oversight, technical documentation development, fleet technical support, and operator/maintainer training.

Specific systems under NSWCPD cognizance include, but are not limited to, Navy ECDIS, legacy Voyage Management System (VMS), Scalable Integrated Bridge System (SIBS), DDG-51 class Integrated Bridge and Navigation System (IBNS)/Integrated Bridge System (IBS), DDG 1000 class Integrated Bridge System, CG-47 class Integrated Ship Control (ISC), LHD Automated Bridge System (ABS), LHD MCS, LHA MCS, Navigation Data Distribution System (NAVDDS), Voyage Data Recorder (VDR), and LCS echo-sounder.

1.2 SCOPE OF WORK

Contractor shall provide engineering, training, technical publication development, program management, technical services, and other services relating to surface vessel navigation systems, steering/propulsion control systems, MCS and ECDIS as tasked by the NSWCPD Contract Officer (KO) or Contractor Officer Representative (COR) on behalf of NSWCPD Department 50.

Contractor shall maintain and provide subject matter expertise for Navy ECDIS, legacy VMS, SIBS, DDG-51 class IBNS/ IBS, DDG 1000, CG-47 class ISC, LHD ABS, LHD MCS, LHA MCS, NAVDDS, VDR, and LCS Fathometer/Echo-Sounder.

Contractor’s engineering services shall include remote technical support (relating to system troubleshooting), onsite technical support (relating to system troubleshooting), onsite ship checks supporting ship installation drawing development, V&V test execution, and installation oversite support. Contractor’s engineering services to NSWCPD Department 50 also include support for, or direct development of, trade studies, system requirements, system designs, V&V test plans, V&V test execution, operations technical manual development, maintenance technical manual development, and technical data package development (preliminary ship installation drawings, installation wire connection lists, system interconnect diagrams, system signal flow diagrams and other items supporting system deployment on Navy’s surface vessels).

Contractor’s training services shall include operational, maintenance, and ISEA-support evolutions for systems supported by Contractor. Contractor shall conduct these evolutions at the Contactor’s facility, in Government facilities (to include Government’s other contracted facilities), and on surface vessels to train NSWCPD Department 50 personnel, regional maintenance center personnel, and fleet personnel to operate, maintain and support systems supported by Contractor.

Contractor’s technical publication development shall include creation and or update of technical publications directing the operation, maintenance or support systems supported by Contractor.

Contractor’s program management services shall include oversite, direction, and coordination of Contractor’s personnel in support of above tasking. Contractor’s program management services will also include emergent technology demonstrations, system change proposal preparations, estimate generation, meeting preparation, hosting program reviews, and coordinate resolution of resulting follow-up actions.

Contractor’s technical services shall include other mechanical, production, and electrical work associated with prototype development, onsite system troubleshooting, installation oversite support, and post-installation testing.

Contractor shall procure incidental materials and components as needed to support emergent troubleshooting efforts. Contractor’s other services will include administrational and other overhead tasks necessary to support NSWCPD task execution.

2.0 APPLICABLE DOCUMENTS

2.1 Configuration Management Standard EIA649B –[http://standards.sae.org/eia649b/]

2.2 MIL-HDBK-502, DEPARTMENT OF DEFENSE HANDBOOK: ACQUISITION LOGISTICS (30 MAY 1997) – [http://everyspec.com/MIL-HDBK/MIL-HDBK-0500-0599/MIL_HDBK_502_235/]

2.3 MIL-DTL-81927C, DETAIL SPECIFICATION: MANUALS, TECHNICAL: WORK PACKAGE STYLE, FORMAT, AND COMMON TECHNICAL CONTENT REQUIREMENTS; GENERAL SPECIFICATION (NOV 1997) -[http://everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-81927C_14024/]

2.4 MIL-STD-38784A (W/ CHANGE-1), DEPARTMENT OF DEFENSE STANDARD PRACTICE: GENERAL STYLE AND FORMAT REQUIREMENTS FOR TECHNICAL MANUALS (11-JUL-2016) -[http://everyspec.com/MIL-STD/MIL-STD-10000-and-Up/MIL-STD-38784A_CHG-1_55081/]

2.5 MIL-DTL-87269D, DETAIL SPECIFICATION: DATA BASE, REVISABLE – INTERACTIVE ELECTRONIC TECHNICAL MANUALS, FOR THE SUPPORT OF (30-JAN-2014) - [http://everyspec.com/MIL-SPECS/MIL-SPECS-MIL-DTL/MIL-DTL-87269D_49349/]

2.6 NAVSEA Technical Specification 9090-310G -[http://www.navsea.navy.mil/Portals/103/Documents/NSWC_Dahlgren/FiberOptics/Appendix_H_TS9090-310G_Approved_2015-2-12.pdf]

The Contractor shall reference and utilize the latest version available when performing tasks within this PWS.

3.0. REQUIREMENTS

3.1 Planning and Program Management Support

3.1.1 The contractor shall provide engineering and technical support to perform the following planning and execution functions for shipboard systems on US Navy Ships and Land Based Test Facilities (LBTF):

(a) Assist in the preparation of and participation in program reviews and Configuration Control Board (CCB) meetings conducted by program activities, sponsors and contractors. (CDRL A012, A042)

(b) Provide engineering and maintenance technical support services in support of the installation and validation of shipboard systems and methodologies. (CDRL A003, A019)

(c) Provide on-site administrative support to Naval Surface Warfare Center Philadelphia Division. Tasks include travel arrangements, meeting minutes, records management, financial management, and presentation development. (CDRL A001, A002, A008, A012, A018)

3.2 System Design and Integration Engineering

3.2.1 The contractor shall assist the Government with the assessment, design, and installation of shipboard systems on US Navy Ships and Land Based Test Facilities (LBTF) by supporting system modernization and new concept development which will include: Engineering algorithms, Logic trees (as they pertain to systems diagnostics and prognostics), Failure Mode, Effects and Criticality Analysis (FMECA), Expert systems, Verification and validation of software developed to support these new concepts. (CDRL A004, A005, A006,A007 A015, A016, A022, A025, A026, A027, A028, A029, A030, A031, A032, A033, A034, A035, A036, A037, A038, A041)

3.2.2 The contractor shall perform analysis and technical studies and provide technical services in the area of shipboard systems engineering support. The contractor shall provide support to NSWCPD Software Support Activity (SSA) for developing, installing and functionally testing software for shipboard systems, including system Simulators, On Board Trainers (OBT) and Land Based Test Facilities (LBTF). Areas of particular involvement shall include:

a) Performing investigations and analysis of data, modernization of shipboard systems necessary to develop alteration packages to include SCDs, ECPs, SHIPALTs, and others, as appropriate. (CDRL A026)

b) Providing OEM engineering support to develop, update, and maintain shipboard system equipment specifications and design documents, and analyzing operational requirements. (CDRL A007, A009, A010, A011, A013, A014, A020)

c) Engineering support to develop Item Control Drawings (ICD) and Ship Installation Drawing (SID) packages to support ECP and SCDs providing system and equipment reliability, maintainability and availability data, and evaluating failure trending and analysis including Failure Mode, Effects and Criticality Analysis (FMECA) and Reliability and Maintainability studies for system components. (CDRL A022, A025, A026, A039, A040, A041)

d) Reviewing proposed engineering changes for impact on configuration, performance, reliability, maintainability, logistics support, safety, and life cycle costs. (CDRL A022, A025, A026, A039, A040, A041, A043, A045)

e) Recommending and performing/supporting redesign, modification, or alteration of hardware and software for system integration and improvements. (CDRL A022, A025, A026, A039, A040, A041)

f) Conducting systems engineering studies for shipboard systems. (CDRL A003)

g) Provide OEM engineering services and technical support to design, develop, and integrate technological improvements to shipboard systems. (CDRL A022, A025, A026, A039, A040, A041)

h) Provide OEM engineering support to develop, update, and maintain shipboard systems software specifications, design and requirements documentation, including concept papers, interface reviews, preliminary designs, detailed designs, design review board for system and interface requirements, system and software requirements analysis. (CDRL A022, A025, A026, A039, A040, A041)

i) Provide OEM engineering support to accomplish shipboard systems software deliveries and installations shipboard and at land based test or training sites, including software/hardware delivery, audit preparation, and configuration management. (CDRL A022, A025, A026, A039, A040, A041, A042)

3.3 Test and Evaluation Engineering

3.3.1 The contractor shall provide integration test support for verification of shipboard systems integration requirements. In addition, the contractor shall provide installation/validation support for installing and functionally testing shipboard systems alterations. (CDRL A004, A005, A006, A007 A015, A016, A019, A022, A025, A026, A027, A028, A029, A030, A031, A032, A033, A034, A035, A036, A037, A038, A041, A044, A047, A048, A049, A050, A051, A052)

3.3.2 The contractor shall provide test and evaluation support to investigate Shipboard systems problems and isolate root cause. (CDRL A004, A005, A006, A007 A015, A016, A019, A022, A025, A026, A027, A028, A029, A030, A031, A032, A033, A034, A035, A036, A037, A038, A041, A044, A047, A048, A049, A050, A051, A052)

This shall include:

a. Develop test and evaluation plans including:

i. Network integration plans

ii. Systems installation validation

iii. Verification plans

iv. Environmental testing plans

b. Formulate testing methodology and develop test procedures for shipboard systems.

c. Conduct system integration testing locally and support testing at various integration labs.

d. Develop and perform configuration audits for shipboard, land based test and training facilities.

e. Coordinate testing as required for the ISEA with outside activities, commands and commercial labs as required.

f. Assist the ISEA to provide engineering services for the correction of shipboard systems discrepancies onboard US Navy ships and Land Based Test facilities.

3.4 Integrated Logistics Support

3.4.1 The contractor shall provide assistance in the development and updating of ILS packages, including, but not limiting to, technical manuals/electronic technical manuals in accordance with reference 2.6. (CDRL A007, A020, A021 A023, A025, A010, A011, A013)

3.4.2 Contractor shall maintain material for installation and shipboard support as part of contractor maintained supply system support. (CDRL A020)

3.4.3 Contractor shall provide obsolescence management support for OEM material. (CDRL A009)

3.5 System Installation Support

3.5.1 The contractor shall provide resources to ISEA in support of equipment installation, training, test, and evaluation of shipboard systems. (CDRL A002, A003)

This support includes:

a) Assist in the development of installation test procedures, including system operability tests as well as the development and review of installation standards and practices.

b) Making ship visits to design prototype layout plans for ECP / SCD installation, mark up existing installation drawings / documents and capture information for development of new documents.

c) Provide incidental materials such as foundations/ mounting brackets/ cabling/ connectors, and similar type items to support the prototype shipboard systems installation or other shipboard systems installations, receipt and stowage of these parts as Government Furnished Equipment (GFE) as required.

d) Provide SCD/SHIPALT/ECD kits (including all hardware and associated documentation) for shipboard systems.

i. Conduct shipboard integration testing, verification and validation of signals and troubleshooting of systems.

ii. Support development of both operator and maintainer training curriculum.

iii. Conduct shipboard and classroom training for operators and maintainers

iv. Provide required drawing updates and associated documentation to reflect as built solution and insert as found conditions in the approved System Problem Improvement Report (SPIR) database.

v. Provide on-site support and coordination with item/program managers to ensure material being received and delivered meets program requirements.

vi. Provide on-site support to maintain records and controls over material in stock, due in, and planned to ensure accuracy is maintained and material is entered into the government owned database.

vii. Provide on-site support to assist or perform yearly audits on 100% of all material in stock to ensure material control is maintained.

4. DATA REQUIREMENTS

1.1. Contract Status Report (CDRL A001)

1.1.1. This report shall reflect both prime and Subcontractor data if applicable at the same level of detail.

1.1.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR.

1.2. Travel Report (CDRL A002)

1.2.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.2.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR.

1.3. Technical Report –Study Services (CDRL A003)

1.3.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.4. Computer Software End Product Items (CDRL A004)

1.4.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.5. Test Plans (CDRL A005)

1.5.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.6. Test Procedures (CDRL A006)

1.6.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.7. Product Drawings/Models and Associated Lists (CDRL A007)

1.7.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.8. Meeting Minutes (CDRL A008)

1.8.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.9. Diminishing manufacturing sources and material shortages (DMSMS) (CDRL A009)

1.9.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.9.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.10. Repairable Item Inspection Report (CDRL A010)

1.10.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.10.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.11. Repair Procedure (CDRL A011)

1.11.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.11.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.12. Weekly Meeting/Program Review Briefs (CDRL A012)

1.12.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.13. Material Status Report (CDRL A013)

1.13.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.13.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.14. Government Furnished Equipment Repair Status Report (CDRL A014)

1.14.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.14.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.15. Software Documentation (CDRL A015)

1.15.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.16. Software Development Summary Report (CDRL A016)

1.16.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.17. System / Subsystem Specification (SSS) (CDRL A017)

1.17.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.17.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.18. Key Events Schedule/ Plan Of Action And Milestones (POAM) (CDRL A018)

1.18.1. POA&Ms will be developed and maintained in Microsoft Project software. POA&Ms shall include Calculations, Specifications, Test Data/Reports, and Metrics as required for tasks identified by the TPOC. POA&M’s shall be prepared and delivered within 5 working days of identification.

1.18.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.19. Test/Inspection Report (CDRL A019)

1.19.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.19.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.20. Parts Management Plan (CDRL A020)

1.20.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.20.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.21. Technical Manuals (Equipment/Components) – Commercial Off the Shelf (COTS)/Non-Commercial Off the Shelf (NON-COTS) (CDRL A021)

1.21.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.21.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.22. Failure Mode, Effects, And Criticality Analysis (FMECA) Report (CDRL A022)

1.22.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.22.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.23. Training Materials (CDRL A023)

1.23.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.24. Installation and Checkout (Inco) Spares List (CDRL A024)

1.24.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.24.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.25. Commercial Drawings and Associated Lists (CDRL A025)

1.25.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.25.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.26. Technical Information Report (CDRL A026)

1.26.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.26.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.27. Interface Design Description (IDD) (CDRL A027)

1.27.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.27.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.28. Software Requirements Specification (SRS) (CDRL A028)

1.28.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.28.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.29. Software Version Description (SVD) (CDRL A029)

1.29.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.29.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.30. Software Test Report (STR) (CDRL A030)

1.30.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.30.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.31. System Deficiency Report Data (SDR) (CDRL A031)

1.31.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.31.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.32. Software Product Specification (SPS) (CDRL A032)

1.32.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.32.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.33. Software Transition Plan (STRP) (CDRL A033)

1.33.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.33.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.34. Software User Manual (SUM) (CDRL A034)

1.34.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.34.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.35. Software Installation Plan (SIP) (CDRL A035)

1.35.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.35.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.36. Software Programmer’s Guide (SPG) (CDRL A036)

1.36.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.36.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.37. Software Design Description (SDD) (CDRL A037)

1.37.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.37.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.38. Software Development Plan (SDP) (CDRL A038)

1.38.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.38.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.39. Factory Acceptance Test Plan and Procedures (CDRL A039)

1.39.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.39.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.40. Safety Assessment Report (SAR) (CDRL A040)

1.40.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.40.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.41. Interface Control Document (ICD) (CDRL A041)

1.41.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.41.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.42. Contractor's Configuration Management Plan (CMP) (CDRL 042)

1.42.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.42.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.43. Engineering Change Proposal (ECP) (CDRL A043)

1.43.1. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.44. Hardware Design Document (HDD) (CDRL A044)

1.44.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.44.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.45. Technical & Management Work Plan (CDRL A045)

1.45.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.45.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.46. Management Plan (CDRL A046)

1.46.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.46.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.47. Electromagnetic Interference Test Report (EMITR) (CDRL A047)

1.47.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.47.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.48. Shock Test Extension Request (CDRL A048)

1.48.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.48.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.49. Shock Test Report (CDRL A049)

1.49.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.49.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.50. Hardware Requirements Document (HRD) (CDRL A050)

1.50.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.50.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.51. Software Requirements Document (SRD) (CDRL A051)

1.51.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.51.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.52. System Requirements Document (SRD) (CDRL A052)

1.52.1. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

1.52.2. The CDRL shall be delivered electronically, unless otherwise stated, and while Contractor’s format is acceptable, Government’s approval is required from the COR. This report shall reflect both prime and subcontractor data if applicable at the same level of detail.

Note: Draft technical reports and conclusions reflecting the work accomplished under each task set forth will be prepared and delivered to the Government two (2) weeks before final submittal date and in the form required by the COR. The final report shall not be prepared without approval of the COR. All draft and final reports submitted by the contractor should have computer media attached. All software Programs and databases shall be compatible with government software programs and databases as defined by NMCI.

5.0 SECURITY REQUIREMENTS

5.1 An active SECRET Facility Clearance (FLC) is required for performance on this contract. There is no safeguarding requirement required. All personnel must have a current SECRET or higher clearance, or the ability to obtain one.

5.2 The Contractor is responsible for completing all required Government-mandated training to maintain security and network access to government-sites and IT systems.

5.3 The contract company shall ensure each employee has completed the 10-hour OSHA Maritime Shipyard Employment Course #7615. The contract company shall ensure that each employee maintains a current Course #7615 certification based on the course's certification expiration period and the requirement for retraining and recertification. REF: NAVSEA SI 009-74

5.4 Security Classification Guidance is as follows of portions of the tasking on this contract when invoked in the task order statement of work:

5.4.1 All contractor personnel accessing classified information or classified material associated with the performance work relative to the resultant contract must be United States citizens no foreign nationals and shall have and maintain at a minimum SECRET security clearance.

5.4.2 The Contractor is responsible for completing all required government mandated training to maintain security and network access to government sites and IT systems, as necessary to support.

6. PLACE OF PERFORMANCE

Place of performance will be at Northrop Grumman facilities in Charlottesville, VA.

7. TRAVEL

The Contractor may be required to travel from the primary performance location when supporting this requirement. The estimated number of trips is approximately 348 trips. Travel in support of this requirement is anticipated to include, but may not be limited to, the following alternate performance locations:

Pittsfield, MA Philadelphia, PA Norfolk, VA San Diego, CA Bremerton, WA Washington, D.C.

Pearl Harbor, HI Mayport, FL Yokosuka, JA Portland, ME Sasebo, JA Bahrain, BAH

The number of times the Contractor may be required to travel to each location cited above may vary as program requirements dictate, provided that the total estimated travel cost is not exceeded. The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. All travel shall be approved by the COR and Contracting Officer before travel occurs. Approval may be via the Technical Instruction (TI). Before initiating any travel, the Contractor(s) shall submit a detailed and fully-burdened estimate that includes the number of employees traveling, their expected travel costs for airfare, lodging, per diem, rental car, taxi/mileage and any other costs or actions requiring approval. The travel estimate shall be submitted to the Contracting Officer's Representative (COR) and Contract Specialist. Actuals cost, resulting from the performance of travel requirements, shall be reported as part of the Contractor's monthly status report. The reportable cost shall also be traceable to the Contractor's invoice

All travel shall be conducted in accordance with FAR 31.205-46, Travel Costs, and HQ B-2-0020 Travel Cost – Alt I (NAVSEA) and shall be pre-approved by the COR. The Contractor shall submit travel reports in accordance with DI-MGMT-81943 (CDRL A002).

Travel Costs

The Government shall reimburse the contractor (and its subcontractors) at a reduced reimbursement rate from the current “maximum per diem” rates for lodging, meals, and incidentals, referenced in FAR 31.205-46(a)(2), for any employees, purchased labor, consultants, etc. assigned to a temporary duty station (TDY) in excess of 30 days in one location. This applies to both CONUS and OCONUS travel. The current “maximum per diem” rates are set forth in the (i) Federal Travel Regulations for travel in the Continental United States; (ii) Joint Travel Regulations for Overseas Non-Foreign areas (e.g., Alaska, Hawaii, Guam, Puerto Rico, etc.); and (ii) Department of State (DOS) prescribed rates for foreign overseas locations.

When proposed travel is in excess of 30 consecutive days, but less than 180 consecutive days, the Government shall limit reimbursement of contractor (and subcontractor) travel costs, on a flat rate basis, to 75 percent of the per diem rate for the TDY locality at the time of travel (lodging, meals, and incidentals) for each full day, long-term TDY of 31 to 180 days. For travel lasting in excess of 180 days, the Government shall limit reimbursement of contractor (and subcontractor) travel costs, on a flat rate basis, to 55 percent of the per diem rates of the TDY locality at the time of travel for each full day.

8.0 GOVERNMENT FURNISHED PROPERTY.

8.1 Government Furnished Material (GFM) will be issued as needed and indicated on each Task Order (TO).

9.0 GOVERNMENT FURNISHED INFORMATION

9.1 Government Furnished Information (GFI) will be issued as needed and indicated on each Task Order (TO). GFI The government will provide the contractor with all pertinent information, including deadlines and government propriety data within fourteen (14) working days of request. This government furnished information (GFI) shall be returned to the government within thirty (30) days after completion of this task or with submission of the final report, unless the SME directs that it be destroyed.

10. PURCHASES

Only items directly used and incidental to the services for this Contract/Task Order and for work within the scope of the Performance Work Statement, shall be purchased under the Other Direct Cost (ODC) line items. Individual purchases above $3,500 shall be approved by the Contracting Officer prior to purchase by the Contractor. The purchase request and supporting documentation shall have submitted via email to the Contracting Officer and the Contracting Officer's Representative (COR) it shall be itemized and contain the cost or price analysis performed by the Contractor to determine the reasonableness of the pricing. (Include the following language where negotiated subcontracts are expected: Provide copies of price estimates from at least 2 vendors.)

Information Technology (IT) equipment, or services must be approved by the proper approval authority. All IT requirements, regardless of dollar amount, submitted under this Contract/Task Order shall be submitted to the PCO for review and approval prior to purchase. The definition of information technology is identical to that of the Clinger-Cohen Act, that is, any equipment or interconnected system or subsystem of equipment that is used in the automatic acquisition, storage, manipulation, management, movement, control, display, switching, interchange, transmission, or reception of data or information. Information technology includes computers, ancillary equipment, software, firmware and similar procedures, services (including support services), and related resources.

11. PERSONNEL

12.1 Personnel Requirements. All persons proposed in key and non-key labor categories shall be U.S. citizens holding at least a current SECRET clearance, or ability to obtain one.

Clause 52.222-2 "Payment for Overtime Premiums" will provide for the total dollar approved amount of overtime or will state “zero” if not approved. If overtime premium has not been approved under this contract in accordance with Clause 52.222-2, overtime effort to be performed shall be requested from the Contracting Officer prior to performance of the overtime. For overtime premium costs to be allowable costs; the Contracting Officer is required to approved the performance of overtime prior to the actual performance of overtime.

The level of effort for the performance of the resultant Contract/Task Order is based on the following labor categories and hours total:

12.1.1 Key Personnel

There are no Key Personnel required for this SOW.

12.1.2 Non-Key Personnel

Although resumes for "Non-Key Personnel" are not required, offerors must fully demonstrate their ability to provide the non-key personnel listed below who meet the requirements that follow. The Contractor shall certify in their proposal that they have these non-key personnel and provide a statement as to their ability to supply the personnel with the experience required to perform the efforts specified in the performance work statement. The Contractor shall provide individuals to fill the non-key positions identified below:

Program/Project Manager I:

Minimum Education: Bachelor's degree in Engineering or Business from an accredited college or university.

Minimum Experience:

· Five (5) years professional experience in program/project management

· Overall planning, direction and success of major programs, systems development efforts, and research or technology initiatives which have great significance to the activity's and agency's needs

· Establishment and control of technical milestones, schedules, budgets and costs are also essential tasks for the Program Manager

· Working knowledge of the Naval Sea System Command, Naval Surface Warfare Center and Fleet organizations is desired

Program/Project Manager II:

Minimum Education: Bachelor's degree in Engineering or Business from an accredited college or university.

Minimum Experience:

· Ten (10) years professional experience in program/project management

· Overall planning, direction and success of major programs, systems development efforts, and research or technology initiatives which have great significance to the activity's and agency's needs

· Establishment and control of technical milestones, schedules, budgets and costs are also essential tasks for the Program Manager

· Working knowledge of the Naval Sea System Command, Naval Surface Warfare Center and…