TI16 MAC_SOW(N63394-24-RFPREQ-NSWCPHD-0005)_20260127.docx
DOCX document 137 KB Posted
- Solicitation number
- N6339426R4001
About this file
This is a Statement of Work (SOW) for the Technical Insertion 16 (TI16) Multiple Award Contract (MAC) Indefinite-Delivery-Indefinite-Quantity (IDIQ) follow-on procurement. The SOW defines lifecycle sustainment requirements for TI16 equipment at Naval Surface Warfare Center, Port Hueneme Division (NSWC PHD), including limited manufacture, assembly, testing of equipment spares, engineering services, obsolescence management, procurement, and installation of Ordnance Alteration (ORDALT) Kits. The TI16 program supports multiple naval platforms including Aegis systems, Guided Missile Destroyers (DDGs), Aircraft Carriers (CVNs), Amphibious Assault Ships (LHAs), Landing Ship Docks (LSDs), Littoral Combat Ships (LCS), Frigates (FFGs), and Ship Self-Defense System (SSDS) platforms, with potential expansion to additional programs throughout the contract duration.
The contractor must provide comprehensive engineering services including configuration management, change management, reliability engineering, failure analysis, test and evaluation, physical configuration audits, and risk management. Key deliverables include over 40 Contract Data Requirements Lists (CDRLs) covering technical documentation, software development, test procedures, ORDALT instructions, and various engineering analyses. The contractor must also manage diminishing manufacturing sources and material shortages (DMSMS), perform packaging and handling services, provide in-service engineering support with onsite field services and installation teams, and conduct equipment refurbishment and repair. Administrative requirements include designation of a Program Manager, monthly contracting officer reports, quarterly program reviews, security clearances up to SECRET classification, cybersecurity workforce certifications, OPSEC compliance, and labor hour reporting through the ECMRA system. Contract performance occurs at NSWC PHD facilities in Port Hueneme, California, with travel requirements throughout CONUS and OCONUS locations including deployed naval vessels.
View the file
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
UNCLASSIFIED
UNCLASSIFIED
1.0 BACKGROUND
The Technical Insertion (TI) program has its origins in 2004 under the management of Program Executive Office Integrated Warfare Systems (PEO IWS) 6.0 as an enterprise approach across surface Navy combat systems to introduce powerful display, processing, and storage as part of a general thrust to achieve a modular and open architecture design. In 2012, management of the Technical Insertion 12 (TI12) initiative transitioned to PEO IWS 1.0, where it became an integral part of the Aegis Modernization (AMOD) and new construction Guided Missile Destroyer (DDG) programs and continued to serve other surface ship combat system requirements as well. In 2015, the enterprise approach continued with Technical Insertion 16 (TI16) in order to introduce the latest commercial-off-the-shelf (COTS) and open architecture design for Navy Combat Systems in the 2018 timeframe.
2.0 SCOPE
This Statement of Work (SOW) defines the efforts required for lifecycle sustainment of the TI16 equipment. This includes the limited manufacture, assembly, and testing of TI16 equipment spares; associated engineering services, obsolescence management, procurement, and installation of Ordnance Alteration (ORDALT) Kits and related products for the Naval Surface Warfare Center, Port Hueneme Division (NSWC PHD), Port Hueneme California. NSWC PHD is a field activity of Naval Sea Systems Command (NAVSEA) and is the In-Service Engineering Agent (ISEA) for the TI16 suite of equipment.
The TI16 program has expanded from a modernization effort for Aegis in-service platforms to DDGs, including new construction, modernization, and Foreign Military Sales (FMS); Ship Self Defense System (SSDS) platforms, including Aircraft Carriers (Nuclear-Propulsion) (CVNs), Amphibious Assault Ships (LHAs), and Landing Ship Docks (LSDs); Aircraft Carrier Tactical Support System (CV-TSC), Surface Electronic Warfare Improvement Program (SEWIP), Littoral Combat Ship (LCS), and Frigate (FFG). It is important to note that this is not an all-inclusive list. Throughout the duration of the contract, additional programs, program offices, platforms, and sites may require support.
3.0 APPLICABLE DOCUMENTS
The following documents are applicable to the tasks described herein and are for use by the contractor in the fulfillment of those tasks. The exact revisions of the documents are not cited in the text of this SOW for the convenience of reference. All of the documents listed herein are assumed to be the latest revision as of the date of award. The Government will provide direction by way of a Technical Instruction (TI) should there be a conflict between the required documents and guidance documents.
| 3.1 | Government Documents |
| Document # | |
| Title |
| SL720-AA-MAN-030 |
| Navy Modernization Process Management and Operational Manual |
| MIL-STD-1662D |
| Preparation of ORDALT Instructions |
| SECNAV M-5510.30C |
| Navy Personnel Security Program Manual |
| Executive Order 13467 |
| Executive Order 13467 |
| HSPD-12 |
| Homeland Security Presidential Directive 12 |
| NAVSEA 4130.6C |
| ORDALT Instruction Control Procedures |
| NAVSEA 4130.9 |
| Configuration Control Procedures for Preparation and Implementation of ORDALTs |
| NAVSEA 4720.11C |
| Shipboard Installations and Modifications Performed by Alteration Installation Teams (AITs) |
| NAVSEA Technical Specification 9090.310 |
| Alterations to Ships Accomplished by AITs |
| NAVSEAINST 4790.8C (Series) |
| Ships’ Maintenance and Material Management (3-M) |
| MIL-HDBK Technical Review Manual |
| PEO IWS – Deputy Commander, Naval Sea Systems Command Warfare Systems Engineering Directorate (NAVSEA 05H) Technical Review Manual (TRM) |
| PEO IWS Program Plan |
| Diminishing Manufacturing Sources and Material Shortages (DMSMS) Plan |
| PEOIWSINST 4130.1C |
| PEO IWS Enterprise Configuration Control Process |
| NAVSEAINST 5000.8 |
| Naval Systems Command (SYSCOM) Risk Management Policy |
| PEO IWS 1.0 TI CMP 3063214 |
| Technical Insertion Configuration Management Plan (CMP) (CMP to release updated version to include not only TI12, but TI16 and follow-on) |
| NAVESEAINST 4130.12B |
| Configuration Management (CM) Policy and Guidance |
| S0005-AA-GYD-030 |
| Technical Manual Management Program (TMMP) |
| NSWCPHD INSTRUCTION 5510.4C |
| Cyberspace Information Technology and Cybersecurity Workforce Qualification Program |
| SECNAV M-5510.30C |
| Navy Personnel Security Program Manual (Chapter 6, Section 6-6, Paragraphs 2b and 2c |
| DoD Instruction 8510.01 |
| Risk Management Framework (RMF) for Department of Defense (DoD) Information Technology (IT) |
| S0005-AA-PRO-010/TMMP |
| NAVSEA Technical Manual Management Program |
| S0300-A7-AEG-010, 020, 030 |
| Aegis Style Guide for Development and Publication of Combat/Weapon System Technical Manuals |
| 3.2 | Joint Chiefs of Staff, Department of Defense, and DoD Services Documents |
| Document # | |
| Title |
| Defense Acquisition Guidebook 4.3.3.4.7 |
| Production Readiness Reviews (PRR) - https://dag.dau.mil |
| DoD 5220.22M |
| Defense Security Service (DSS) National Industrial Security Program Operating manual (NISPOM) |
| DoDI 4140.67 |
| Department of Defense Instruction (DoDI) 4140.67 DoD Counterfeit Prevention Policy |
| 3.3 | Military Standards (MIL-STD) |
| Document # | |
| Title |
| MIL-STD-129P |
| DoD Standard Practice, Military marking for Shipment and Storage |
| MIL-STD 130N |
| DoD Standard Practice Identification Marking of U.S. Military Property |
| MIL-STD-882E |
| System Safety |
| MIL-STD-2073-1E |
| DoD Standard Practice for Military Packing |
| MIL-STD-40051E |
| Preparation of Digital Technical Information for Technical Manuals (TMs) |
| 3.4 | Other Military Documents |
| Document # | |
| Title |
| MIL-D-23140D |
| Drawings, Installation Control, for Shipboard Electronic Equipment |
| MIL-DTL-31000C |
| Technical Data Packages, Detail Specification |
| MIL-STD-3034 |
| Planned Maintenance System: Development Of Maintenance Requirement Cards, Maintenance Index Pages, and Associated Documentation |
| MIL-PRF-29612B |
| Training Data Products |
| 3.5 | Handbooks |
| Document # | |
| Title |
| MIL-HDBK-61B |
| Configuration Management (CM) Guidance |
| MIL-HDBK-881C |
| Work Breakdown Structures for Defense Materiel Items |
| 3.6 | Non-Government/Commercial Standards |
| Document # | |
| Title |
| ISO 9001:2015 |
| Quality management systems - Requirements |
| ASME Y14.24-2020 |
| Types and Applications of Engineering Drawings |
| ASTM 1166-07 (2017) |
| Standard Practice for Human Engineering Design for Marine Systems, Equipment, and Facilities |
| ASTM F1337-10 (2015) |
| Standard Practice for Human Systems Integration Program Requirements for Ships and Marine Systems, Equipment, And Facilities |
| IEEE/EIA 12207-2017 |
| Software Life Cycle Processes |
| ISO/DIS 9001 |
| Quality Management Systems - Requirements |
| ISO 10007:2017 |
| Quality management — Guidelines for configuration management |
| IEEE/EIA-649-1 |
| Institute of Electrical and Electronics Engineers (IEEE) National Consensus Standard for CM |
4.0 GENERAL REQUIREMENTS AND INFORMATION
4.1 Administrative Guidelines
4.1.1 The overall effort required for lifecycle sustainment of the TI16 equipment takes place at NSWC PHD, other PHD sites, remote sites, and other locations within CONUS and OCONUS. Contract performance shall take place at the contractors' facility as well as travel to NSWC PHD, other PHD sites, remote sites, and other locations within CONUS and OCONUS. Execution of tasks under this contract requires frequent interface with the personnel at NSWC PHD. Normal hours of operation at NSWC PHD, Port Hueneme, CA are from 0730-1700 Pacific Standard Time, Monday through Friday, except Federal holidays. The standard hours of operation for other NSWC PHD sites, remote sites, and travel destination workplaces are determined locally and may vary.
| 4.1.2 | Contractor personnel are authorized to work independently within government facilities without the presence of a government representative on site, provided the nature of the work allows for independent execution without compromising safety, security, or the integrity of government property. Pending prior approval by local installation. |
| 4.1.3 | The Contractor shall obtain Procuring Contracting Officer (PCO) approval in advance of any work performed on weekends, holidays, and during facility shut down. Alternate work schedules used by the contractor must not negatively affect SOW deliverables, project schedules, and tasks. |
| 4.1.4 | The Contractor is expected to maintain an adequate workforce for the uninterrupted performance of all tasks defined within this SOW. The Contractor shall accomplish all work by employing and utilizing qualified personnel with appropriate combinations of education, training, certifications, if required, and experience (Ref. Attachment X Staffing Plan) to provide quality workmanship, maintain schedule, and minimize rework. |
| 4.1.5 | Contractor personnel shall be proficient in utilizing up-to-date software tools and technologies employed by both the Government and Industry. This includes, but is not limited to, Microsoft Office Suite (Word, Excel, Outlook, PowerPoint, Project, Planner, Teams, Power BI, SharePoint, etc.), Adobe Acrobat, Google Suite, email management tools, Navy Enterprise Resource Planning (N-ERP), internet/intranet navigation and research skills, and familiarity with Model Based Product Support. |
| 4.1.6 | Contractor personnel must possess the necessary skills to communicate effectively with colleagues, clients, and stakeholders, utilizing both written and verbal methods. Contractor personnel shall be capable of articulating information clearly and concisely, as well as responding promptly to inquiries from the Government. |
| 4.1.7 | The Government will neither supervise contractor personnel, train contractor personnel, nor control the method by which contractor personnel perform tasks. Contractor personnel shall manage their time effectively, prioritize tasks, and work efficiently to ensure that work is completed on schedule and deadlines are met. The Government will not assign tasks to, or prepare work schedules for, individual contractor personnel. |
| 4.1.8 | The Contractor is required to effectively manage multiple tasks simultaneously, adjust to changing priorities, and address emergent tasks effectively. The nature of the work may require contractor personnel to respond promptly to tight deadlines. |
| 4.1.9 | The issuance of technical tasks may be provided by the COR via the Technical Instruction (TI) form. The TI will outline specific task requirements within the scope of the task order, including details such as performance location, task sequence, any necessary drawings or specifications. It is important to note that the TIs do not obligate funds and cannot be used for financial management purposes. They serve as a means to provide clarification or additional information related to the existing SOW or contract terms. The contractor is responsible for reviewing TIs to ensure tasks are within scope and if any out-of-scope tasks are identified, the Contractor shall promptly notify the PCO. After confirming that the TI aligns with the SOW, the contractor must sign it and return it to the COR. Revisions to the TI are only required if there are changes or updates to the original task requirements, but these revisions must remain within the task order scope and do not require formal contract modification. |
4.1.10 Performance may require that contractor personnel complete mandatory training requirements. The Government will notify the Contractor, via email, of any contractor employees required to complete training requirements. The Contractor shall ensure that all contractor employees, if required, complete the training requirements on time.
4.2 Program Management and Administration
Tasks outlined in Section 4.2 fall within the purview of Program Management and Administrative Requirements/Guidelines. These tasks are operational rather than technical and are critical for ensuring the seamless execution of tasks and achieving task order objectives.
4.2.1 The Contractor shall designate a Program Manager who will serve as the primary point of contact and be responsible for the overall planning, direction, and successful execution of all requirements outlined in this SOW. The Program Manager is responsible for ensuring project goals and objectives are achieved within the specified time frame, budget, and to the satisfaction of the Government. This includes:
· Program Planning and Control
· Resource Management
· Risk Management
· Budgeting and Rough Order of Magnitude (ROM) Development
· Cost Management and Control
· Schedule Management
· Performance Monitoring and Reporting
· Documentation Preparation and Transmittal
· Quality Control
| 4.2.2 | The Program Manager shall guard against any actions that are, or perceived as, personal services. If the Contractor believes that any actions constitute, or perceived to constitute, personal services, the Contractor shall notify the PCO, Contract Specialist (CS), and Contracting Officer’s Representative (COR) via email within one (1) business day. |
| 4.2.3 | The Program Manager shall establish effective communication channels with the PCO, CS, COR, Technical Requirement Lead, and other government stakeholders. The Contractor must efficiently manage task orders by streamlining communication, establishing processes, and ensuring quality assurance. This involves overseeing communications and coordination among stakeholders, managing risk, allocating resources optimally, monitoring performance, and maintaining specified quality standards. Through diligent execution of these tasks, the contractor ensures seamless tasks execution and delivers high-quality outcomes while adhering to budgetary and scheduling limitations. |
| 4.2.4 | The Program Manager shall conduct periodic contract status meetings for all active Task Orders covering contract execution, identified performance risks and issues, and the contractor’s mitigation/corrective actions. The Program Manager shall maintain an Action Item List to enable tracking the closure of generated action items. |
| 4.2.5 | The Program Manager shall develop and submit a monthly Contracting Officer’s Management Report in accordance with CDRL A001. |
| 4.2.6 | The Contractor shall conduct periodic program reviews with government stakeholders to assess the Contractor’s progress and status of contract execution and discuss any issues/challenges. This review can occur at either the Naval Base Ventura County campus, through telecommunication or virtual, or a combination of both. The Contractor shall provide, at a minimum, an overview of engineering and ORDALT development status, review of program DMSMS status, including disclosure of any and all known DMSMS items, the planned action to mitigate its engineering and Integrated Logistic Support (ILS) impacts, and a report on small business utilization. Vendor/Subcontractor status and problems shall also be addressed in program review. In addition, a separate review may be conducted to cover a special set of circumstances or troublesome area(s), but the reviews shall be considered part of and conducted with the quarterly production review. The Contractor shall provide the briefing material in accordance with CDRL A002. |
| 4.2.7 | The Contractor shall prepare and submit an end of contract transition plan, in accordance with CDRL A003, detailing the transfer of full assumption of duties to the follow-on contractor. |
4.3 General Security Requirements
| 4.3.1 | Classification: This contract is unclassified, however, the work to be performed under this contract may require access to secure areas or classified information up to and including SECRET security classification. Security guidance and requirements will be identified per Contract Security Classification Specification, DD Form 254 (Attachment X). In the event of revisions, updates or changes to security requirements, the DD Form 254 (Attachment X) will be revised. |
| 4.3.2 | Background Investigations: In accordance with SECNAV M-5510.30, the Navy Personnel Security Program Manual (Chapter 6, Section 6-6, Paragraphs 2b and 2c), Executive Order 13467 of 30 June 2008, as well as Homeland Security Presidential Directive 12 (HSPD -12) and United States Office of Personnel Management Memorandum, Final Credentialing Standards for Issuing Personal Identity Verification Cards under HSPD-12 dated 31 July 2008, the Contractor shall ensure that all individuals performing work on behalf of the Government have a current, favorably adjudicated background investigation of the appropriate type to determine fitness to perform work on behalf of the Government as a contractor employee, perform sensitive national security duties, or have access to classified information. A background investigation equivalent to the current Tier requirement which is equivalent to secret which is still in scope is acceptable. |
| 4.3.3 | The Contractor shall maintain a roster which includes the security clearance status of all personnel assigned to this contract. The Contractor Roster shall be delivered in accordance with CDRL A004. |
4.3.4 Personnel Security Processing: Contractor Employees who require access to Classified Information will be processed under the terms of the National Industrial Security Program (NISP) in alignment with the work requirements of the contract and Security Requirements on the applicable DD Form 254 (Attachment X). Those contractor employees who do not require access to classified information in performance of this contract, but are assigned to sensitive national security duties, require access to sensitive information, or for other reasons require a fitness or trustworthiness determination, shall be processed for the appropriate background investigation through the NSWC PHD Personnel Security Office for a Non-NISP investigation. Point of contact is the Personnel Security Specialist, (805) 228-7196. The contractor shall provide the required form(s) (i.e., Application for Identification Card/Deers Enrollment (DD Form 1172-2)) for each contractor employee requiring a CAC.
| 4.3.5 | Security Incident Reporting: NSWC PHD Command Security Manager shall be made aware of any contractor personnel who have an investigation with an action pending, eligibility has been administratively withdrawn or pending, withdrawal of interim clearance eligibility, eligibility of no determination made, or final denial or revocation of security clearance eligibility. |
| 4.3.6 | Electronic Spillages: Electronic Spillages are unacceptable and pose a risk to national security. An electronic spillage is defined as classified data placed on an information system, media or hardcopy document possessing insufficient security controls to protect the data at the required classification level. If the Contractor is determined to be responsible for an Electronic Spillage, the Contractor shall be responsible for all direct and indirect costs incurred by the Government. |
| 4.3.7 | Spillage Corrective Actions: NSWC PHD Security will continue to be responsible for the corrective action plan in accordance with the security guidance reflected on the DD Form 254 (Attachment X). NSWC PHD Security will identify the Contractor and contract number associated with all electronic spillages during the investigation that involve Contractor support. NSWC PHD Security will notify the PCO with the Contractor name and contract number, incident specifics and associated costs for clean-up. The PCO will be responsible to work with the Contractor to capture the costs incurred during the spillage clean up. The Contractor is also responsible for taking Information Security Awareness training annually, via its Facility Security Officer (FSO), as part of the mandatory training requirements. If a spillage occurs additional training will be required to prevent recurrence. |
| 4.3.8 | Critical Information Protection: The Contractor will be developing, producing, analyzing, maintaining, transporting, storing, testing, or using critical information or indicators for this contract. |
4.3.9 Operations Security (OPSEC) Compliance: The Contractor is required to protect critical information associated with the contract to prevent unauthorized disclosure and shall observe OPSEC Requirements. The Contractor shall develop an Operations Security (OPSEC) Plan. See block 14 of the Department of Defense (DD) Form 254. The Contractor shall comply with the Government Contracting Activity or facilities OPSEC program instructions and guidance and contribute to organization-level OPSEC training and awareness programs while performing aboard designated government sites and facilities. Ensure you read NSWCPHDINST 3070.1 for OPSEC requirements.
4.3.10 OPSEC Training: The Contractor shall include OPSEC as part of its ongoing training and awareness program and take all required activity OPSEC training. The contractor shall protect identified critical information, sensitive unclassified information and activities, which, if divulged, could further compromise classified or sensitive information or operations, or degrade the planning and execution of operations performed in support of the mission. Specific OPSEC requirements will be delineated on the DD Form 254.
4.3.11 Cybersecurity and IT Requirements: The Contractor shall possess and maintain Cybersecurity Workforce Operating System/Computing Environment certifications required by Department of Navy (DoN) and report in accordance with (CDRL A005) Cybersecurity Workforce (CSWF) Report.
4.3.12 IT Systems Access: Individuals who require IT-I level access to sensitive DoD and DoN IT systems require a favorably adjudicated Tier 5 investigation, and individuals who require IT-II level access to such systems require a Tier 3 investigation. All access to DoN IT systems is, at minimum, IT-II.
4.3.13 The Navy adopted IEEE/Electronic Industries Alliance (EIA) Standard 12207, Standard for IT, in May 1998, as its basis for software development planning and acquisition. This standard defines a framework within which specific software development life cycles can be defined and provides a standard set of terminology to be used when describing these activities. This standard does not define any specific approach; it allows a wide variation of system life cycles and facilitating the customization of approaches to accommodate the needs of individual systems. The Contractor shall ensure compliance with the most recent IEEE/EIA Standard 12207. The Contractor shall demonstrate a level of competency with established processes commensurate with Capability Maturity Model Integration (CMMI) Q Level 3.
4.4 Safety, Environmental Protection and Compliance
4.4.1 The Contractor shall prepare an Emergency Action Plan (EAP) associated to the services performed in this SOW. Contractors storing classified documentation and classified equipment at their facilities in accordance with tasking in this requirement shall develop and maintain an EAP and provide a report in accordance with CDRL A006.
4.4.2 The Contractor shall prepare a HAZMAT/HAZWASTE report associated with the services performed in this SOW in accordance with CDRL A007.
4.5 Government Furnished Property and Information
4.5.1 Government Furnished Property: The contractor shall provide all property necessary to perform this contract. In the event Government Furnish Property (GFP) is required and provided, the contractor shall maintain (real-time) a tracking system to track and manage GFP and contractor acquired property. The contractor shall deliver a report for all GFP, and contractor acquired property in the custody of the contractor in accordance with CDRL A008.
4.5.2 Government Furnished Information: The contractor shall manage Government Furnished Information (GFI) and complete the GFI form (Attachment X) for all GFI received and/or in the custody of the contractor in accordance with CDRL A009.
4.6 Data Deliverables
| 4.6.1 | All deliverables shall be completed and submitted in accordance with the requirements of this SOW and as specified on the approved Contract Data Requirements List (CDRLs), DD Form 1423. |
| 4.6.2 | The Contractor shall ensure all deliverables provided against this contract contain the appropriate classification marking and distribution statement and adhere to applicable laws, regulations, and government-wide policies when managing all Controlled Unclassified Information (CUI). |
| 4.6.3 | The Government reserves the right to reject deliverables without the appropriate marking and distribution statement and for errors. |
| 4.6.4 | Deliverables provided under this requirement may contain technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C., Sec 2751, et. seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401 et seq. Violations of these export laws are subject to severe criminal penalties. Disseminate in accordance with provisions of DoD Directive 5230.25. |
| 4.6.5 | Destruction Notice for classified documents, follow the procedures in DoD 5220.22-M, Industrial Security Manual, Section 11 - 19 or DoD 5200.1-R, Information Security Program Regulation, Chapter IX. For unclassified, limited documents, destroy by any method that will prevent disclosure of contents or reconstruction of the document. |
| 4.6.6 | Use of Government documentation for commercial purposes is forbidden. |
4.7 Travel Requirements
4.7.1 The contractor may be required to travel in performance of this contract throughout the Continental United States (CONUS) and Outside Continental United States (OCONUS) locations. When required to obtain access to a Government facility, ship, aircraft, or other duty station, the contractor shall complete all forms required and provide the request and forms to the COR for appropriate action. The contractor shall maintain a working knowledge of the Foreign Clearance Guide for OCONUS travel. It is anticipated that travel will be required primarily within the CONUS but may be required OCONUS. CONUS and OCONUS travel requirements will be directed by task order and/or TI. Although not all inclusive, the Contractor may be required travel to the following locations: Washington D.C., Honolulu, HI, Kauai, HI, San Diego, CA, Norfolk, VA, Moorestown, NJ, Yokosuka, Japan, Mayport, FL, Rota, Spain/Romania/Poland/Other European Union, Everett, WA, Port Hueneme, CA (NSWC PHD), Persian Gulf Theater, Dahlgren, VA, Virginia Beach, VA, Wallops Island, VA, Pascagoula/Gulf Coast, MS, Aboard Aegis ships, both in homeport and worldwide.
4.7.2: All travel shall be coordinated with the COR, prior to travel. The contractor shall complete and provide to the COR a trip information form (Attachment X) for each trip. The COR will review the request and provide a travel authorization within two (2) business days. For urgent travel requirements, the COR will respond with one (1) business day.
4.7.3 The Contractor shall prepare a trip report at the conclusion of any travel associated with this contract in accordance with CDRL A010.
| 4.7.4 | Travel Limitations: The numbers of trips and types of personnel traveling shall be limited to the minimum required to accomplish work requirements. All travel shall be conducted in accordance with FAR Part 31.205-46 Travel Costs and the Joint Travel Regulations. |
| 5.0 | TECHNICAL REQUIREMENTS |
| 5.1 | Engineering Services |
5.1.1 The Contractor shall provide engineering and field services to include distance support, informal instruction to users, shipboard fleet technical assistance and supply support for parts and technical services, all in conjunction with and in support of ISEA sustainment actions.
5.1.2 The Contractor shall participate in various technical meetings, integrated product teams, and working groups including Hardware Engineering Review Board (HERB), Local Configuration Control Board (LCCB), Enterprise Configuration Control Board (ECCB), Failure/Problem Review Boards, Fleet Issues Working Groups (FIWG), Engineering Working Groups, User Working Groups, and Risk Assessments and various other collaborative engagements. The Contractor shall provide technical support and inputs during these events to ensure integrated and coordinated work across all elements of the Sustainment Program.
5.1.3 The Contractor shall develop, maintain, and deliver the following engineering support and planning documents supplementing services performed and in accordance with the applicable CDRL:
· Configuration Management Plan, CDRL A011
· Provisioning Technical Documentation (PTD) Report, CDRL A012
· Instructional Media Design Package, CDRL A013
· Computer Based Training (CBT), CDRL A014
· Software Version Description (SVD), CDRL A015 (needs tailoring)
· Software User Manual (SUM), CDRL A016 (needs tailoring)
· Firmware Support Manual (FSM), CDRL A017
· Interface Control Document, CDRL A018task analysis
· Installation Control Drawings, CDRL A019
· Interface Design Description (IDD) Application Program Interface, CDRL A020
· Software Requirements Specification (SRS), CDRL A021
· Software Development Plan (SDP), CDRL A022
· Software Design Description (SDD), CDRL A023
· INCO Spares Listing, CDRL A024
· Lowest Replaceable Units (LRU) Cross- Reference List, CDRL A025
· Notice of Revision (NOR), CDRL A026
· Engineering Change Proposal, CDRL A027
· Technical Data Package, CDRL A028
· Technical Manual (TM) Data, CDRL A029
· Maintenance Task Analysis, CDRL A030
· Computer Software Configuration Items, CDRL A031
· Life Cycle Cost (LCC) And Independent Schedule, CDRL A032
· Inventory/Utilization Data Report, CDRL A033
· Failure Reporting, Analysis and Corrective Action Technical Report, CDRL A034
· Reliability, Prediction, and Documentation of Supporting Data, CDRL A035
· Engineering Analysis Report, CDRL A036
· Test Plans/Test Procedures - Environmental Qualification Test (EQT) Report, CDRL A037
· Production Acceptance Test (PAT) Procedures, CDRL A038
· Software Compatibility Test Report, CDRL A039
· Test and Evaluation Reports (Test Procedures, Systems Level), CDRL A040
· Technical Report Repair/Replacement, CDRL A041
· Risk Management Plan, A042
· Diminishing Manufacturing Sources & Material Shortages Implementation Plan, CDRL A043
· Source Data Health Analysis & Forecasting for DMSMS Surveillance Report, CDRL A044
· DMSMS and Life Cycle Management Report, CDRL A045
· DMSMS Health Assessment Report, CDRL A046
· As Built Configuration List - Common (ABCL-C), CDRL A047
· Material Procurement & Screening Plan, CDRL A048
· Procurement Reports, CDRL A049
· Packing, Handling, Storage and Transportation (PHS&T) Plan, CDRL A050
5.1.4 Change Management
5.1.4.1 The Contractor shall provide configuration management services.
5.1.4.2 The Contractor shall provide Equipment Changes and ORDALT Implementation Support, Engineering and Integrated Product Support (IPS), updates and maintenance to Government Documents as specified by Technical Instruction.
| 5.1.4.3 | The Contractor shall provide scheduling, production, and project management services for major upgrades, COTS Equipment Refresh, and Configuration Database Support. |
| 5.1.4.4 | The purpose of the preliminary and formal ECP is to provide advance notification of a proposed change, assign a recommended ECP classification (Class I or II), and obtain Government concurrence after configuration control boards have approved the change to expend resources to fully document the proposed change. If a Class I ECP is proposed, the Contractor shall include rationale explaining why the proposed change cannot be accomplished by a Class II ECP. The Contractor shall describe in all ECPs the logistics impact(s), including form/fit/function interchangeability, applicability, reliability and maintainability requirements. The Contractor shall generate formal ECPs and provide updates when directed by the Government and/or following Government approval of a preliminary ECP. |
| 5.1.5 | TDP Maintenance: The Contractor shall update the existing TDP provided as GFI in accordance with CDRL A021 to reflect all products. The Contractor shall perform update and provide updates to the Government for the maintenance of the existing TDP in an incremental fashion as equipment changes are made. The TDP shall contain all data sufficient to provide life cycle support for all products and changes thereto. |
| 5.1.6 | PAT Environment and Software Toolset Maintenance |
5.1.6.1 The Contractor shall provide Production Acceptance Test (PAT) Environment and Software Toolset Maintenance and upgrade services to TI16. This shall include all software, middleware, and the licenses (e.g., updates, maintenance, patches, helpdesk support, and other software or middleware products) delivered under the previous Production contracts that are necessary for basic system operations (e.g., diagnostics, Built in Test, boot loader, performance monitoring, operating environment, plus the operating system kernel necessary to run the aforementioned software) as defined within the System Requirements Document (SRD).
5.1.6.2 All software procured or developed under this contract shall not require license renewal in order to continue uninterrupted operation and contractor shall claim no data rights to any of the software, firmware, middleware developed or maintained under this contract. Service Agreements for all software procured or developed under this contract shall at a minimum cover a period of two years from the date of delivery.
5.1.6.3 A report shall be generated to identify inventory and utilization of Software, Middleware, Firmware and Licenses.
5.1.6.4 The Contractor shall follow Shipboard and Land Based Test Site Cyber security requirements.
5.1.7 Reliability Engineering, Failure Analysis, Monitoring, And Redesign
5.1.7.1 The Contractor shall provide services required to plan, implement, conduct, and support a tailored Reliability and Maintainability (R&M) program.
5.1.7.2 The Contractor shall have a system for collecting and recording all failures (both critical and non-critical) which occur during all tests, inspection procedures, and installations. Individual failure records shall include, at a minimum, the failure record number, part number, name, and manufacturer, date of failure, operating hours, problem description, investigation procedures, corrective action status and corresponding ECP number when applicable.
5.1.7.3 The Contractor shall review field failure data from sites, shipyards and the fleet to identify problems impacting R&M characteristics and to determine adverse trends. All failures shall be analyzed and corrective action implemented to preclude recurrence of the failure. The effectiveness of the corrective action shall be evaluated by the continued review of Failure Records.
5.1.7.4 The Contractor shall provide services to conduct root cause analysis and recommend corrective actions. Investigations shall be performed to establish root cause of failure and corrective action for R&M problems and failure trends and failure analysis reports shall be provided detailing root cause of failure trend.
5.1.7.5 The Contractor shall monitor and report all testing failures.
5.1.7.6 The Contractor shall participate in Hardware Engineering Review Boards with the government, if needed, to review all user failures and production failures to identify reliability or quality problems and failure trends, and to discuss the investigation and corrective action status for those items. The board monitors trends at Combat System integration sites/ ships and production facilities.
5.1.7.7 The Contractor shall provide design improvement recommendations in technical reports, with findings and methodology used for recommendations and solutions.
5.1.7.8 The Contractor shall provide services to test and evaluate the findings to ensure the recommended technical solution has been fully evaluated and tested in the baseline operating environment at land-based test sites or aboard US or Foreign Navy Ships as directed by the Government.
5.1.8 Physical Configuration Audit
5.1.8.1 The Contractor shall provide engineering services, equipment and facilities in support of Physical Configuration Audit (PCA) and Functional Configuration Audit (FCA) for first ORDALT Kits and major cabinet level redesigns and as required for lower level units and assemblies. PCA and/or FCA will be conducted at the designated production site. Government will provide Test Plans and Procedures prior to PCA or FCA as specified by the Government.
5.1.8.2 The Contractor shall perform testing and analysis to ensure compatibility and interoperability of products and equipment produced under this contract with systems delivered under previous production contracts. The Contractor shall identify discrepancies or shortfalls.
5.1.9 Test and Evaluation
5.1.9.1 The Contractor shall provide services to test, evaluate, and qualify parts and assemblies. The Contractor shall also evaluate parts and assemblies prior to delivery of ORDALT Kits and INCO Spares or concurrent with installation at sites or aboard ships to ensure that delivered items meet all requirements for installation as specified in Systems Requirement Document (SRD). Tests include Functional Bench Testing, First Article Testing, Environmental Qualification Testing (EQT), Integration Testing, Software Compatibility Testing, and any necessary regression testing.
5.1.9.2 The Contractor shall provide onsite engineering and technical support during test and evaluation events during ORDALT kit installs.
5.1.10 Risk Assessment and Management: The Contractor shall create and maintain a Risk Management Plan .
5.1.11 Equipment Refurbishment and Assembly/Component Repair
5.1.11.1 The Contractor shall provide equipment refurbishment services. Refurbishment services shall be required for equipment harvested from active ships as well as Navy land based test laboratories. All equipment, parts, diagnostics, and repair services required to ensure refurbished equipment meets original operational requirements and packaging shall be included.
5.1.11.2 The Contractor shall provide assembly/component repair services required by the Government. The Contractor shall perform an assessment and estimation for repair for items received. Assessment shall include Contractor recommendation regarding repair feasibility.
5.2 Obsolescence Management
5.2.1 The Contractor shall monitor, identify, plan for and resolve DMSMS and obsolescence issues and submit a DMSMS Implementation Plan.
5.2.2 The Contractor shall respond to DMSMS Alerts provided by the Government that may include product upgrade, technology refresh, lifetime buys, bridge buys and/or a redesign to meet the requirements of the contract. DMSMS solutions accepted by government shall be implemented in accordance with the NAVSEA 4130.12B CM Policy and Guidance.
5.2.3 The Contractor shall select products for production whose projected obsolescence date is not less than one year past the end of production. The product lifetime equals the timeframe that the product can be purchased from the Original Equipment Manufacturer (OEM). Any products that do not meet this criterion must be approved by the Government ISEA prior to final product selection. For the purposes of this contract, hardware, software, and/or firmware shall be considered obsolete when the item can no longer be procured as new from the OEM.
5.2.4 DMSMS Forecasting Source Data
5.2.4.1 The contractor shall perform DMSMS obsolescence surveillance which includes but not limited to ongoing process of monitoring parts, components, software and technologies used to identify and mitigate the risks associated with DMSMS parts. The contractor shall prepare a DMSMS Health Analysis and Forecasting bill of materials report for all configurations to support production and/or changes to the system implemented during production.
5.2.4.2 The Contractor shall submit Product Recall, DMSMS, and Obsolescence Identification & Vendor Change Notices and DMSMS Health Analysis Reports.
5.3 Material Procurement
| 5.3.1 | The Contractor shall procure production equipment, piece parts, ORDALT Kits, Installation Check-Out (INCO) Spares, spare parts, and firmware required to provide Life Cycle Support for equipment and to produce sustainment ORDALT Kits as specified in Section B. |
| 5.3.2 | The Contractor shall procure parts, materials and replacements for items that become obsolete. |
| 5.3.2 | The Contractor shall procure parts, materials and replacements for items that become obsolete. The Government will specify requirement Technical Instruction. |
| 5.3.3 | The Contractor shall accurately document, track materials and purchased parts, provide As Built Configuration Lists (ABCL) for all kits. |
| 5.3.4 | The Contractor shall provide a material procurement plan which includes effective procedures to determine material needs, lead times, and delivery schedule. |
5.3.5 The Contractor shall submit Procurement Reports.
| 5.4 | Packaging, Handling, Storage and Transportation (PHS&T) Support |
| 5.4.1 | The Contractor shall adhere to the existing and approved PHS&T plan to be provided as Government Furnished-Information (GFI). The Contractor shall update the existing and approved PHS&T plan as necessary due to new design changes. |
5.4.2 The Contractor shall provide certificates of compliance for material procured and ensure International Traffic in Arms Regulations (ITAR) compliant products adhere to the procurement screening process.
5.4.3 The Contractor shall provide packaging, shipping and tracking of procured material, ORDALT Kits, and Lowest Replaceable Units (LRUs) for delivery as specified by the Government.
5.4.4 The Contractor shall apply DoD Item Unique Identification (IUID) markings to the equipment at the unit level assemblies and associated LRUs in accordance with the TDP and MIL-STD-130. The Contractor shall adhere to approved Marking Plans and update as necessary due to new design changes.
5.5 In-service Engineering, Installations, and Field Services
5.5.1 The Contractor shall perform onsite equipment assessments in support of ORDALT installations as indicated in the non-exclusive list below.
Assessment Type
Purpose of Assessment
| Pre-Availability Assessment |
| Test /Assess material condition of legacy systems/sensors: determine long lead type work candidates for upcoming availabilities (Ship Check) |
Pre/Post Installation and Check Out
System check before installation of software and/or components to confirm proper operation of the system. System health of each component is documented and reported. For harvesting efforts each piece of equipment would need to be tagged with its health status and material condition. System Operational Verification Test is the after installation check to ensure proper operation of the system.
Equipment Light Off Assessment Ensure delivery to Fleet of Materially ready ship at end of Chief of Naval Operations availabilities
| Readiness Assessment and Verification |
| Ensure Combat System-ready ships for pre-deployment exercises and workups |
Pre/Post-Deployment Assessment To baseline Equipment prior to and upon ship’s return from deployment and to review Combat System Master Plan jobs for Light Off risk mitigation
| IPS Assessment |
| Identify and correct supportability deficiencies to support ship's current configuration |
| Operational and maintenance Training |
| Provide refresher/supplemental training on operations & maintenance of Equipment. |
| Reutilization & Harvesting |
| Conduct equipment assessments prior to removal (Shipboard and/or Land Based sites). Identify LRU/Non-LRU candidates for possible harvesting and reutilization. |
5.5.2 The Contractor shall provide ORDALT Alteration Installation Teams (AIT) installation services.
5.5.2.1 The Contractor shall develop, maintain, and deliver the following ORDALT installation data products supplementing services performed and in accordance with the applicable CDRL. Additional data deliverables outlined in SOW Paragraph 5.1.3 may also be required in performance of requirements within SOW paragraph 5.5.
· Ordnance Alteration (ORDALT) Instructions, CDRL A051
· Alteration Installation Item (AIT) Workbook , CDRL A052
· Planned Maintenance System (PMS) Maintenance Requirement Card (MRC), A053
· Planned Maintenance System (PMS) Maintenance Index Page (MIP), CDRL A054
· Technical Manual Validation Plan, CDRL A55
5.5.2.2 The Contractor shall provide supply support for parts and technical services for ORDALT Kits in conjunction with Naval Supply Weapon Systems Support and Government in-service support actions.
5.5.2.3 The Contractor shall perform ORDALTs and installation support for Pre-Installation and Checkout and document discrepancies on all cabinets and consoles impacted by installation of ORDALT Kits.
5.5.2.4 The Contractor shall develop Pre-Installation AIT Workbooks and support Post-Installation Closeout and delivery of AIT Workbooks.
5.5.2.5 The Contractor shall conduct required post installation test procedures and identify and correct any faults generated by installation of ORDALT Kits. The Contractor shall document results and corrective actions.
5.5.2.6 The Contractor shall provide harvesting, staging and shipping services for components and associated parts removed during ORDALT installations.
5.5.2.7 The Contractor shall monitor and report all installation failures and provide recommendations for equipment correction, repair, and replacement supporting Government effective decisions on material readiness issues.
5.5.2.8 The Contractor shall monitor and correct any deficiencies of installed equipment's’ Technical Feedback Reports (TFR)s for the equipment just installed in order to close out AIT workbooks.
5.5.2.9 In support of ORDALT installations, the Contractor shall participate in Waterfront Reviews and related production (daily de-conflict) and installation status meetings held with the Government installation teams. These meeting are performed while the shipboard ORDALT installation is ongoing.
5.5.3 The Contractor shall develop, build, and test ORDALT kits and provide services including harvesting, qualification, production, installation, and coordination of integrated product support (IPS) product change development and product delivery.
5.5.3.1 The Contractor shall successfully complete a Production Readiness Review 30 days prior to production of ORDALT Kits or LRUs.
5.5.3.2 The Contractor shall identify existing and projected manufacturing problems and areas of risk on the ORDALT Kits or LRUs. The Contractor shall assess the progress of installation readiness in the Contractor's planning to achieve production rates required under the delivery schedule which will be provided by the Government.
X Enterprise-wide Contractor Manpower Reporting Application (ECMRA) The Contractor shall report contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the NSWC PHD CMRA Tool via a secure data collection site. Contracted services excluded from reporting are based on Product Service Codes (PSCs). The excluded PSCs are:
W, Lease/Rental of Equipment;
X, Lease/Rental of Facilities;
Y, Construction of Structures and Facilities;
D, Automatic Data Processing and Telecommunications, IT and Telecom- Telecommunications Transmission (D304) and Internet (D322) only;
S, Utilities only;
V, Freight and Shipping only.
The Contractor is required to upload, enter, and complete all required data fields using the following web address: https://www.ecmra.mil.
Reporting inputs will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://www.ecmra.mil.
UNCLASSIFIED
UNCLASSIFIED
File details come from the government source that posted it. Updated .