1300389284_-_SOW_SP2.docx
DOCX document 47 KB Posted
- Solicitation number
- N66604-14-R-0597
About this file
Statement of Work
View the file
Other files
| File | Type | Posted |
|---|---|---|
| 1300389284_-_JA_(approved)_SP2_Redacted.pdf | ||
| N66604-15-R-0132_with_exhibits.pdf | ||
| 1300389284_-_SOW_3.18.14.docx | DOCX document |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
STATEMENT OF WORK
1. BACKGROUND
The Naval Undersea Warfare Center (NUWC) Division, Newport (NUWCDIVNPT) Code 2522 is responsible for the direction, control, and decisions inherent in the planning, budgeting, design, development, acquisition, engineering, and implementation throughout the life cycle of the Ohio Class Submarine Data Processing Subsystem (DPS) Program and Command and Control System (CCS) and Non-Propulsion Electronics System (NPES) System Engineering as mandated by the Department of Defense (DOD). The DPS is a mission critical legacy subsystem that directly supports the United States national security and both the strategic deterrent mission of the OHIO Class SSBN submarines and the strike mission of the OHIO Class SSGN submarines. To achieve these goals, Code 2522 must provide the unique resources and full-spectrum facilities to meet the specific needs of the fleet and to support the technologies for the current and future programs success and progress for the Navy.
Specifically, this role includes maintenance, refurbishment, design, development, integration, future planning and engineering, prototyping, and providing technical management during the life cycle of the Ohio Class Submarine Data Processing Subsystem Program.
The Contractor shall provide technical services in support of Code 252. Project customers include the Naval Sea Systems Commands PMS392, PMS 397, IWS6, 07L, Strategic Systems Programs (SP24) and SPAWAR .
2. SCOPE
The Contractor shall provide operational maintenance and technical engineering services and life cycle maintenance of the Ohio Class Submarine CCS/NPES DPS shipboard and non-shipboard system and subsystem and related elements. The operational maintenance tasks will encompass operational Ohio Class submarines and shore sites performing training, refit, and maintenance activities extending from preventative and emergency maintenance to equipment refurbishment to laboratory layout planning and implementation. The technical engineering tasks will encompass Ohio Class submarines and consist of: design concepts and engineering proposals, development, integration and installation, test and evaluation plans, test data results, future alteration planning, validation and verification, and conduct of various analyses and studies of engineering requirements, for hardware and software.
Tasking and deliverables shall be in accordance with requirements defined in Section 4.
3. APPLICABLE DOCUMENTS
Government Specifications, Standards, and Documents
| 3.1 |
| MIL-STD-1397B |
| Input/Output Interfaces, Standard Digital Data, Navy Systems |
| 3.2 |
| MIL-STD-52779A |
| Software Quality Assurance Program Requirement |
| 3.3 |
| IEEE/EIA/ISO 12207 |
| Software Life Cycle |
| 3.4 |
| ISO 9001 |
| Quality Management Systems - Requirements |
| 3.5 |
| NAVSEA 0900-074-4010 |
| Interface Design Specification for the TRIDENT Submarine Ohio Class Command and Control System Common Requirements for Intersubsystem Computer Program Interfaces CCS Specification |
| 3.6 |
| NAVSEA T9410-D1-SPN-010 |
| System Specification for the TRIDENT Submarine Ohio Class Command and Control System Functional & Allocated Requirements Specification |
| 3.7 |
| NAVSEA TE687-TC-PPS-F10 |
| Submarine Ohio Class Command and Control System TRIDENT Common Program/TRIDENT Service Program Computer Program Performance Specification |
| 3.8 |
| NAVSEA TE687-TF-PPS-N10 |
| Trident Submarine Ohio Class Command and Control System Naval Undersea Warfare Center Utility Package Computer Program Performance Specification |
| 3.9 |
| NAVSEA TE687-BK-PPS-G10 |
| Trident Submarine Ohio Class Command and Control System Data Processing Subsystem Workstation Software Requirements Specification |
| 3.10 |
| NAVSEA TE687-AX-PPS-G10 |
| Ohio Class Guided Missile Submarine Non-Propulsion Electronics System Data Processing Subsystem Mission Critical Workstation Software Requirements Specification |
| 3.11 |
| NAVSEA T9410-GB-PLN-010 |
| Ohio Class (SSBN/SSGN) Command and Control System and Non-Propulsion Electronics System Configuration Management Plan |
| 3.12 |
| TE687-BY-SCM-010/SW DEL REQ |
| TRIDENT Submarine Ohio Class Command and Control System Software Delivery Requirements |
| 3.13 |
| NAVSEA T9410-AB-PRO-010/020 |
| Trident CCS Problem Reporting System (TCPRS) Procedures and Program Plan, Volumes 1 and 2 |
| 3.14 |
| NAVSEA T9401-BU-PRO-010 |
| Trident CCS Modification (TCMOD) System Procedures and Plan |
| 3.15 |
| NAVSEA S8200-BE-TRN-010 |
| Trident CCS Temporary Engineering Change (TEC) Standard Operation Procedure (SOP) |
| 3.16 |
| NAVSEA T9410-BK-PRO-010 |
| Trident CCS Engineering Change (EC) Development SOP |
| 3.17 |
| NAVSEA T9410-AX-CCD-010 |
| SSBN 726 Class Submarine CCS Boundary Definition Document |
| 3.18 |
| TE687-BX-PRO-010/CMPA |
| TRIDENT Submarine Ohio Class Command and Control System (CCS) Computer Program Configuration Management / Product Assurance (CM/PA) Procedures |
| 3.19 |
| NAVSEA T9410-GB-PRO-010 |
| OHIO Class (SSBN/SSGN) Command and Control System (CCS) and Non-Propulsion Electronics System (NPES) Modification Development Standard Operating Procedure |
| 3.20 |
| N/A |
| DON Information Security Program Regulation SECNAVINST 5510.36 |
| 3.21 |
| TE687-BN-PLN-K10 |
| Submarine OHIO Class Command and Control System, Software Development Plan (SDP) For The Data Processing Subsystem (DPS) Workstation (DPWS) |
| 3.22 |
| TE687-BN-PLN-M10 |
| OHIO Class Guided Missile Submarine (SSGN) Non-Propulsion Electronics System (NPES) Software Development Plan for the Data Processing Subsystem (DPS) Mission Critical Workstation (MCW) |
| 3.23 |
| SE610-NV-MMO-A10 |
| Technical Manual Operation and Maintenance Instructions for Computer Set AN/UYK-43(V) |
| 3.24 |
| TE687-EZ-MMO-010 |
| Technical Manual for Submarine Workstation (OL-651(P)) Description, Operation, and Maintenance |
| 3.25 |
| TE687-C9-OMI-D10 |
| Interactive Electronic Technical Manual For AN/UYQ-70(V) Data Processing System (DPS) Multi-Function Server (MFS) Description, Operation, And Maintenance |
| 3.26 |
| N/A |
| Information Assurance Vulnerability Technical Advisory (IAVA) Assessment Process |
4. REQUIREMENTS
Specific tasks shall be defined by TOs to be placed against the contract by the Contracting Officer. The tasks shall be accomplished in accordance with the specifications/standards and within the scope of the Tasks specified below. These tasks shall be performed in accordance with the Applicable Documents Section 3.0 and other documentation/guidance as identified in individual TOs.
4.1 Operational Life Cycle Support Maintenance (Hardware, Software & Documentation)
· In accordance with Applicable Documents 3.2, 3.3 and 3.7 through 3.11, 3.13, 3.21, 3.22 and using GFI 6.7, 6.8 and 6.9, the Contractor shall respond to and resolve DPS priority (1) problems within 24 hours of notification, and DPS priority (2) problems within 72 hours of notification. The contractor shall achieve full functional capabilities of the DPS. The Contractor shall deliver a technical report that identifies the problem resolution and repair.
· In accordance with Applicable Documents 3.1, 3.23-3.25 and using GFI 6.1, 6.2 and 6.4, the Contractor shall conduct DPS hardware configuration/inspection audits and grooms and deliver a technical report that details the inspection’s findings.
· In accordance with Applicable Documents 3.7 through 3.10, 3.21 through 3.25 and using GFI 6.1 and 6.2, the Contractor shall develop change packages for DPS documentation and individual Manual Change Requests (MCRs) associated with Ship Systems Manual (SSM) deficiencies and program anomalies identified by the Fleet.
· In accordance with Applicable Documents 3.5 through 3.10 and using GFI 6.4, the Contractor shall attend Life Cycle Support Facility (LCSF) Planning Group meeting and develop a technical report of the DPS recommended LCSF implementation plans and schedules, and deliver these to the government.
· In accordance with Applicable Documents 3.1, 3.2, 3.23, 3.24, and 3.25 and using GFI 6.8 and 6.13, the Contractor shall conduct inspections and overhaul of equipment located at TRIDENT Trainer Facilities located at Kings Bay, Georgia and Bangor, Washington and deliver a technical report of the findings of the inspection/overhaul.
· In accordance with Applicable Documents 3.14, 3.15, 3.16, and 3.19 and using GFI 6.1 and 6.2, the Contractor shall prepare and/or review and comment on Ohio Submarine Class CCS/NPES DPS Revision Temporary Modification (TCMOD) series’ to support DPS installations and provide associated Temporary Engineering Changes (TEC), Engineering Changes (EC), Engineering Change Instruction (ECI), and Configuration Change Requests (CCR).
· In accordance with Applicable Documents 3.12, 3.18, and 3.19 and using GFI 6.1, the Contractor shall prepare and deliver DPS Subsystem Software Updates (SUs) related to DPS software products installed on the SSGN and/or SSBN platforms.
· In accordance with Applicable Documents 3.20 and 3.26 and using GFI 6.1 and 6.2, the Contractor shall monitor Information Assurance Vulnerability Technical Advisory (IAVA) bulletins for impacts to those DPS software products installed on the SSGN platform and assess and resolve those IAVAs impacting DPS Revision products in accordance with guidelines outlined by the advisory for inclusion in commissioned SUs onboard the SSGN.
· In accordance with Applicable Documents 3.11, 3.18 and 3.19 and using GFI 6.1, the Contractor shall integrate DPS, Monitoring Subsystem (MS), and Ship Control Application Program (SCAP) Participating Manager (PARM) Revision Software for the Ohio Class Submarine CCS/NPES revisions and build integrated legacy UYK-43 Computer software builds via Machine Transferrable Software Support (MTASS) system tools for integration and certification.
· Using GFI 6.3 through 6.4 and 6.10, the contractor shall attend CCS/NPES System Engineering and Test Group meetings, CCS/NPES program reviews, technical design reviews and working group meetings. The contractor shall deliver a meeting minutes report which documents the topics of discussion, action items assigned, and participating organizations and individuals.
· In accordance with Applicable Documents 3.5 through 3.10 and 3.21 and 3.22 and using GFI 6.1, 6.2 and 6.3, the Contractor shall prepare and deliver DPS presentations and briefing packages which address cost, technical content, schedule, and problem status.
Deliverable(s):
Technical Report CDRL A001, Computer Software Product End Items CDRL A002, Record of Meeting Minutes CDRL A003, Presentation Material CDRL A004.
4.2 Revision Development and Advanced Planning
· In accordance with Applicable Documents 3.3, 3.5 through 3.10, 3.21, and 3.22 and using GFI 6.1, 6.2, 6.5, 6.6 and 6.8, the Contractor shall review and assess potential DPS shipboard and shore-based hardware and/or software impacts associated with proposed CCS/NPES upgrades and prepare and provide an implementation approach white paper and associated Rough Order of Magnitude (ROM) estimates for those alterations impacting DPS shipboard and shore-based software or hardware products for government planning.
· In accordance with Applicable Documents 3.3, 3.5 through 3.10, 3.21, and 3.22 and using GFI 6.5 and 6.6, the Contractor shall prepare and deliver technical presentations and briefing materials for the DPS Preliminary Design Review and Critical Design Review (PDR/CDR) for proposed CCS/NPES alterations. The PDR/CDR presentations shall identify DPS Engineering Change Proposal (ECP) content and any DPS hardware and/or software required to support the proposed CCS/NPES revision development.
· In accordance with Applicable Documents 3.14, 3.16 and 3.19 and using GFI 6.1, 6.2. 6.5 and 6.6, the Contractor shall prepare and deliver Engineering Change Instruction(s) (ECI) and Engineering Change Proposal(s) (ECP) for proposed CCS/NPES alteration content.
· In accordance with Applicable Documents 3.2, 3.3, 3.7 through 3.10, 3.21 and 3.22 and using GFI 6.1 and 6.2, the Contractor shall prepare and deliver DPS test plans and procedures in support of proposed CCS/NPES revision(s). Upon approval by the Government, the contractor shall prepare and deliver a preliminary and final DPS test procedure.
· In accordance with Applicable Documents 3.3, 3.21 and 3.22 and using GFI 6.1 and 6.2, the Contractor shall conduct formal DPS assessment testing for a proposed CCS/NPES revision(s). The contractor shall prepare and deliver formal daily test reports, and a final DPS Verification Testing (DVT) Report.
· In accordance with Applicable Documents 3.2, 3.3, 3.11, 3.12, 3.18, 3.21 and 3.22 and using GFI 6.1 and 6.2, the Contractor shall prepare and deliver a preliminary DPS software build(s) and final DPS Computer Program Package(s) (CPP) build in support of a CCS/NPES revision.
· In accordance with Applicable Documents 3.2, 3.3, 3.5 through 3.11, 3.21 and 3.22 and using GFI 6.1, 6.2, 6.5 and 6.6, the Contractor shall prepare documentation changes for DPS sections of the Ships Systems Manuals (SSM), including individual Manual Change Requests (MCRs) associated with SSM deficiencies and program anomalies, as well as complete revision change packages in support of a CCS/NPES revision.
· In accordance with Applicable Documents 3.16, 3.18 and 3.19 and using GFI 6.1, 6.2, 6.4 and 6.8, the Contractor shall install the government approved DPS product(s) on SSBN/SSGN hulls and at the TRIDENT Training Facility (TTF) in Bangor, WA and King’s Bay, GA and the TRIDENT Life Cycle Support Facility at Newport, RI. Installation shall include a technical test report that details the efforts associated with hardware and software interface troubleshooting and any problem resolutions.
· In accordance with Applicable Documents 3.16 and 3.18 and using GFI 6.1,6.2, 6.4 and 6.8, the Contractor shall conduct testing of the government approved DPS product(s) on SSBN/SSGN hulls and the TRIDENT Training Facility (TTF) in Bangor, WA and King’s Bay, GA and the TRIDENT Life Cycle Support Facility at Newport, RI. Testing shall include a technical test report that details all associated activities.
· In accordance with Applicable Documents 3.3, 3.7 through 3.11, 3.14, 3.15, 3.16, 3.21 and 3.22 and using GFI 6.1, 6.2, 6.5 and 6.6, the Contractor shall review Ohio Submarine Class CCS/NPES TCMOD series’ documentation, and deliver associated technical reports in the form of DPS Temporary Engineering Changes (TEC), Engineering Change/Engineering Change Instructions (EC/ECI), and Configuration Change Requests (CCR) materials. The contractor shall review, update, and provide technical reports for the Configuration Item Listings (CILs), Product Baselines (PBLs), Reallocation Plans, Maintenance Assist Module (MAM) and Installation & Checkout (I&C) Spare Parts Requirement Lists and Allowance Parts List.
· In accordance with Applicable Documents 3.2 through 3.3 and using GFI 6.1 through 6.6, the Contractor shall prepare and maintain a project Plan of Action and Milestones (POA&M) which includes schedule dates for all DPS CDRLs related to DPS design and advanced planning development activities. The contractor shall update schedules included in the POA&M and deliver monthly to reflect current progress. The contractor shall update, identify and explain schedule changes and potential impacts in each monthly update.
· Using GFI 6.1 and 6.10 through 6.12, the Contractor shall participate in Ohio Class Modernization Platform Integration Team (PIT) meetings; technical briefings and coordination briefing; and working group meetings representing the DPS.
· In accordance with Applicable Documents 3.5 through 3.6 and using GFI 6.1, 6.2 and 6.10 through 6.12, the Contractor shall develop system engineering studies and design alternatives, review planning documentation and coordination drawings to ensure that documentation/drawings meet government specifications, and perform technical evaluation and special studies on the potential application of emerging technology all in support of Ohio Class Submarine SSBN CCS Modernization planning activities. In addition, the Contractor shall perform feasibility and design concept, operational concept, and trade-off analysis in support of these planning activities.
Deliverable(s):
Technical Report CDRL A001, Computer Software Product End Items CDRL A002, Record of Meeting Minutes CDRL A003, CDR/PDR Presentation Material CDRL A004, Engineering Change Proposal CDRL A005, Test Plan CDRL A006, Test Procedure CDRL A007 , Test Report CDRL A0008.
5. PROGRESS REPORTS
The contractor shall submit Monthly Progress and Financial Reports in accordance with Clause C16. These reports shall document the technical and financial status, and may be submitted in the contractor’s format.
6. GOVERNMENT FURNISHED INFORMATION (GFI)
| 6.1 |
| Ohio Class CCS Two Year Plan Alteration Locator |
| 6.2 |
| Ohio Class NPES Modernization Schedule |
| 6.3 |
| TRIDENT SSBN/SSGN System Engineering Calendar |
| 6.4 |
| TRIDENT Life Cycle Support Facility 12-Month Planning Schedule |
| 6.5 |
| CCS/NPES Alteration Documentation (e.g. TEMPALT, SHIPALT) |
| 6.6 |
| CCS/NPES Change Documentation (e.g., ECI, TECI, EC, BCR) |
| 6.7 |
| Patrol reports & naval messages |
| 6.8 |
| Letters/e-mails from the sites |
| 6.9 |
| LCSF test reports |
| 6.10 |
| Meeting announcements/emails |
| 6.11 |
| SSBN CCS Modernization PIT Charter |
| 6.12 |
| SSBN CCS Modernization POM15 Issue Paper |
| 6.13 |
| NUWC Fiscal Year (FY) DPS Overhaul Individual Task Planning Sheet (ITPS) |
7. QUALITY SURVEILLANCE & PERFORMANCE STANDARDS
The government will conduct quality surveillance via various methods including formal and informal meetings, review of technical reports, review of monthly progress reports, and review of deliverables.
Contractor performance will be evaluated in the areas of technical quality, responsiveness, timeliness and cost. Technical quality will be evaluated against the performance standards defined in Attachment A. Responsiveness will be evaluated based upon the Government’s experience interacting with the contractor during performance. Timeliness will be evaluated based on the contractor’s ability to meet CDRL schedules with minimal negative impact and cost will be evaluated based upon the contactor’s ability to manage costs.
File details come from the government source that posted it. Updated .