LCS SOW DRAFT.pdf
PDF 333 KB Posted
- Solicitation number
- N6339426R0TBD
About this file
This is a Statement of Work (SOW) for the Naval Surface Warfare Center, Port Hueneme Division (NSWC PHD), focusing on providing engineering and technical support for Littoral Combat Ship (LCS) and related maritime systems. The contract requires comprehensive support across multiple domains, including engineering, integration, test and evaluation, software development, cyber security, logistics, training, and design interface support for various naval systems such as combat management systems, communication networks, radar, navigation equipment, and training devices.
Key technical requirements include performing system studies, analyzing performance metrics, conducting reliability engineering, developing software updates, managing configuration changes, supporting platform certifications, updating training materials, and providing subject matter expertise. The contractor will work with both Independence and Freedom variant LCS, as well as other naval platforms like Landing Ship Medium and Expeditionary Sea Base. The scope encompasses activities such as troubleshooting, modernization, testing, maintenance, and addressing emerging technical requirements across CONUS and OCONUS locations, with an emphasis on improving warfighter readiness and supporting naval operational capabilities.
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
CUI
1 BACKGROUND
The Naval Surface Warfare Center, Port Hueneme Division (NSWC PHD) is part of the larger Naval Sea Systems Command. The NSWC PHD mission is to provide research, development, test and evaluation, and in-service engineering and logistics support to the U.S. Navy, other military services, and government agencies. Its focus areas include combat systems, unmanned systems, surface ship systems, and information systems.
General Dynamics Mission Systems is the sole Design Agent of the Independence variant of the Littoral Combat Ship (LCS) and other related surface ship and maritime systems. The Independence variant combat system consists of Integrated Combat Management System (ICMS), which interfaces with Command, Control, Communications, Computers, Combat Systems, and Intelligence (C5I) elements, software applications, and the networking environment hardware.
2 SCOPE
The general scope of this Statement of Work (SOW) is to provide quality systems engineering and technical expertise to aggressively improve Warfighter readiness, as well as to improve and modernize the delivery, quality, and cost of products and services. It encompasses a wide range of activities and resources tailored to meet the specific needs of engineering projects. This involves providing expertise on technical matters related to engineering design, analysis, troubleshooting, and implementation. This engineering support will help to develop and maintain strong relationships with Program Sponsors and the Navy Fleet, and to pursue new technologies to better support them.
This contract is to provide support integration, modernization, test, troubleshooting and sustainment of the following systems with respect to Combat System, encompassing the systems and equipment within their scope of responsibility, and/or program offices. It is important to note that this is not an all-inclusive list. Throughout the duration of the task order, additional programs, program offices, platforms, and sites may require support. Specific details regarding these requirements will be outlined in the Technical Instruction (TI) form.
Littoral Combat Ship (LCS) Independence and Freedom variant Landing Ship Medium (LSM) ship class Expeditionary Sea Base (ESB) ship class Integrated Combat Management System (ICMS) hardware and software LCS Combat Management Systems Hardware and Mission Package Console LCS Total Ship Computing Environment (TSCE) Video Distribution System and Above Deck Cameras; Closed Circuit Television (CCTV
System) Sea Giraffe AN/SPS-77; Air Search Radar Bridgemaster X&S Band; Navigation Radar
Sea Star Safire (SSS) III MK 110 Mod 0; 57MM Gun Mount MK 15 Mod 31 SEA RAM; Self Defense Missile ES-3601 AN/SLD-4(V)1; Electronic Warfare (EW) ALEX SRBOC MK 137 MOD 1; Decoy Launching System Multi-Data Link Management System (MDLMS) AN/USQ-242; Link Management Commercial Mobile Radio Service (CMRS); Communications Automation Software MD-1324 AN/PSC-5D (RT-1672D); Ultra High Frequency (UHF) Satellite
Communications (SATCOM)
AN/PSC-5D (RT-1672D), AN/ARC-210 (RT-1747D); VHF/UHF LOS
Global Command and Control System – Maritime (GCCS-M) High Frequency Radio System (HFRS) (Thales); High Frequency (HF) AN/USQ-219(V); Tactical Common Data Link (TCDL) AN/USQ-155(V); Tactical Variant Switch (TVS) SAAB R4/R5; Automatic Identification System (AIS) MK 39 Inertial Navigation System (INS); Gyro NAVIGAT; Digital Gyro Compass Echosounder; Fathometer Precise Time Management (PTM) Magnetic Compass Cryptography Equipment (KWR-46; KIV-19A; KIV-7 HSB; KGV-68B; KG-40A (P);
MT- 4417; HNF-1 (KWR-46 ENCLOSURE); KSV-21; CV-3591; AN/ USC-43 (V)1
(ANDVT); KVY-5; STE CABLE SET; STE; Mounting Bracket; Office STE; KSV-21;
AN/CYZ-10(v)3; KYK-13; KOT-18-1; KIT-1C; KIR-1C; KG-175-E-100 CRYPTO
GEAR)
AN/ USQ-144(V); Automated Digital Network System (ADNS) Inmarsat C SOLAS; Commercial Satellite Communications AN/SSR-1; Fleet Broadcast Communications Satellite Transmitter (BCST) AN/URC-141C (Low Power) Multifunctional Information Distribution System (MIDS) On Ship (MOS) (Link 16) AN/SYQ-26(V)3; Naval Modular Automated Communications System (NAVMACS) Sperry Integrated Bridge System (IBS); Navigation Sensor System Interface (NAVSSI);
WSN-7 GDU
Navy Integrated Tactical Environment System (NITES) Navy Tactical Command Support System (NTCSS) AN/WSC-6(V)9; Wide Band SATCOM (WBS) Super High Frequency (SHF) Engineering Control System (ECS) Voyage Management System (VMS) Machinery Plant Control Management System (MPCMS) MK 48 Gun Weapon System (GWS) Surface Electronic Warfare Improvement Program (SEWIP) – Lite – Electronic Warfare
System NULKA Decoy Launching System C2P (Command and Control Processor) Naval Strike Missile (NSM) LCS Surface Warfare and Mine Countermeasures Integrated Tactical Trainer (ITT) located at the Littoral Combat Ship Training Facilities
(LTFs) or other facilities and on-board training capability Common Data Link Management System (CDLMS) AN/UQN-10 Navigation system AN/UPX-46 (Mode 5/S) Identification Friend or Foe (IFF) System Atalanta Weapon System (AtWS) integration with Independence weapon and sensor systems MK20 Mod1 Electro Optic Sensor System Mission Package Consoles (MPC) and Mission Package Computing Environment
(MPCE)
Multiple Vehicle Communications System (MVCS) Maintenance, Training, Asset Management, Integrated, Navy Supported (MainTAIN) Advanced System Integration Structure (ASSIST)
VISION
Communication Systems Interface Adapter (CSIA) WSN‐7/WSN‐9 Inertial Navigation Systems Command and Control Processor (C2P) External Network Track Receiver (ENTR) Tactical Cross Domain Solutions (TACDS) Central Navigation Provider (CNP) Navigation Critical Distribution System (NCDS) GPS‐based Positioning, Navigation, and Timing Service (GPNTS) Condition Based Maintenance (CBM) interface with combat systems elements and TSCE Digital Modular Radios (DMR)
3 APPLICABLE DOCUMENTS
Attachment X, Government Furnished Information, provides a list of applicable documents required for fulfilling the contract. All applicable tasking, process, performance, execution, and documentation within this contract shall be in accordance with the most current revision of the documents as of the date of award. The Government will provide direction by way of a TI should there be a conflict between the required documents and guidance.
4 REQUIREMENTS
4.1 Program Manager (Key Position)
4.1.1 The Program Manager, a Key Position, shall be responsible for providing technical expertise in the overall planning, direction, and successful execution of all requirements outlined in this SOW. The Program Manager shall ensure that all project goals and objectives are achieved within the specified time frame, budget, and to the satisfaction of all stakeholders.
4.1.2 The Program Manager shall provide program and project management services including, but not limited to:
• Program Planning and Control
• Resource management
• Risk management
• Rough Order of Magnitude (ROM) development
• Financial management, Earned Value Management (EVM), trend analysis, expenditures and forecasting
• Budgeting and Cost Management
• Schedule management
• Performance monitoring and reporting
• Documentation preparation and transmittal
• Quality control
4.1.3 The Program Manager shall establish effective communication channels with the Procuring Contracting Officer (PCO), Contract Specialist, and Contracting Officer’s Representative (COR) and shall conduct biweekly contract status meetings covering contract execution, identified performance risks and issues, and the contractor’s mitigation/corrective actions.
(CDRL A001) CONTRACT STATUS MEETING REPORT
4.2 TASK ORDER MANAGEMENT AND ADMINISTRATION
4.2.1 Administrative Requirements/Guidelines
The contractor must efficiently manage the task order by streamlining communication, establishing processes, and ensuring quality assurance. This involves overseeing communication 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. Tasks outlined in Section 4.2 fall within the purview of 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.1 The contractor may be required to participate in an annual program review, typically lasting about an hour. This review can occur at either the Naval Base Ventura County campus, through telecommunication, or a combination of both. The purpose of the program review is to review the status of contract execution and discuss any issues/challenges. The Government will provide briefing material and format via email to the Program Manager for review and feedback.
4.2.1.2 Contract performance shall take place at NSWC PHD locations within the Continental United States (CONUS), including but not limited to Port Hueneme, California; San Diego, California; Seal Beach, California; White Sands Missile Range, New Mexico; Virginia Beach, Virginia; Norfolk, Virgina; Wallops Island, Virginia; Moorestown, New Jersey; Mayport, Florida; Pearl Harbor, Hawaii; and Kauai, Hawaii, and other Outside the Continental United States (OCONUS) or remote sites including Japan, Singapore and Bahrain.
4.2.1.3 Normal hours of operation at NSWC PHD, Port Hueneme, CA are from 0730-1700 Pacific 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. 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.
4.2.1.4 The contractor shall obtain the PCO’s approval in advance of any work performed on weekends, holidays, and during facility shut down. It is important to note that during facility shutdowns, certain offices will remain operational, and contractor personnel might be needed to maintain support services during this time.
4.2.1.5 Alternate work schedules used by the contractor must not negatively impact SOW deliverables, project schedules, and tasks.
4.2.1.6 The Government will neither supervise contractor personnel, train contractor personnel, nor control the method by which contractor personnel perform tasks. The Government will not assign tasks to, or prepare work schedules for, individual contractor personnel. The contractor shall manage its employees and 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, CS, and COR via email within one (1) business day.
4.2.1.7 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.2.1.8 Shipboard training is mandatory for anyone embarking on a Navy vessel. Tier 1/2/3 cards must be obtained for this purpose. The government will facilitate and provide the necessary training to fulfil this mandate. The contractor shall ensure that its employees assigned to support tasks on Navy vessels complete this training within 30 days to comply with the specified criteria.
4.2.1.9 The contractor shall have qualified personnel capable of responding to emergent events within 48 hours. These personnel shall be capable of carrying out tasks in locations both CONUS and OCONUS. This readiness ensures that the contractor can quickly deploy resources to address emergent events, regardless of their geographical location.
4.2.1.10 The 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, etc.), Adobe Acrobat, Google Suite, email management tools, Navy Enterprise Resource Planning (N-ERP), Model Based Product Support (MBPS), Windchill, internet/intranet navigation and research skills, and familiarity with Jira, Industrial Logistics Support Management Information System (ILSMIS), One Touch, Configuration Data Managers Database-Open Architecture (CDMD-OA), and the Interactive Computer Aided Provisioning System (ICAPS).
Please note that the Navy is currently transitioning to MBPS, a new Product Lifecycle Management (PLM) approach to managing logistics data and processes. It is important that the contractor personnel have the knowledge and ability to work with both the current Navy/Department of Defense (DOD) logistics tools and the new MBPS systems as they are implemented. contractor personnel must be able to adapt to these changes, using both existing and emerging tools. Contractor personnel shall manage their time effectively, prioritize tasks, and work efficiently to ensure that work is completed on schedule and deadlines are met.
4.2.1.11 Contractor personnel must possess the necessary skills to communicate effectively with colleagues, clients, and stakeholders, utilizing both written and verbal methods.
They shall be capable of articulating information clearly and concisely, as well as responding promptly to inquiries.
4.2.1.12 The contractor personnel shall manage their time effectively, prioritize tasks, and work efficiently to ensure that work is completed on schedule and deadlines are met.
4.2.1.13 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.2.1.14 The contractor shall develop and submit a monthly Contracting Officer’s Management report by the 10th day of each month. The final report for each contract period
(base, option year 1, etc.) is due no later than 60 calendar days after the end of each period of performance.
(CDRL A002) CONTRACTING OFFICER’S MANAGEMENT REPORT
4.2.1.15 The contractor shall prepare a monthly personnel roster of individuals performing work on behalf of the Government and submit it by the 10th of every month, as well as within two (2) business days of any personnel changes. The COR shall be notified via email no later than two (2) business days after becoming aware that a contractor employee is separating from the company and the personnel roster shall be updated. During shipboard support, the On Site Installation Coordinator OSIC and/or Combat Systems Project Engineer (CSPE) shall be immediately notified via email of any shift or personnel change, providing certifications of new personnel.
(CDRL A003) CONTRACTOR’S PERSONNEL ROSTER
4.2.1.15.1 Performance under this contract requires that contractor personnel complete mandatory training requirements accessible via Total Workforce Management Services (TWMS) or Waypoints. It’s the contractor’s responsibility to ensure that their employees and subcontractor personnel, assigned to tasks under this task order, complete the mandatory training. The contractor shall maintain a roster of personnel who have completed the training.
4.2.1.16 Emergency Muster: Upon request from the COR or PCO, the contractor shall, within one (1) business day of receiving the request, provide the names, geographical locations, and physical status of the contractor personnel assigned to this requirement via email. Physical condition shall be described as “Mustered – unharmed,” “Mustered – injured,” “Missing,” “Deceased,” or “Unknown”. Follow-on update reports may be requested as the emergency develops.
(CDRL A004) REVISIONS TO EXISTING GOVERNMENT DOCUMENTS
4.2.1.17 The contractor shall ensure that each contractor employee who requires (or has been issued) a Common Access Card (CAC) completes all initial required training and annually as required thereafter. 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.2.2 Security
4.2.2.1 This contract is unclassified, however, the classification of the work to be performed under this task order requires access to secure areas or classified information up to and including SECRET security classification guidance and security requirements will be identified per Contract Security Classification Specification, DD Form 254 (Attachment X). In the event a contract requires revisions, updates or changes to security requirements, the DD Form 254 (Attachment X) will be revised.
4.2.2.2 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 and which is still in scope is acceptable.
4.2.2.3 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.
4.2.2.4 The Contractor may require intentional access to Foreign Government Information in support of tasks delineated in Technical Instructions in support of this contract.
4.2.2.5 NSWC PHD Command Security Manager (CSM) 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.2.2.6 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.2.2.7 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.2.2.8 The contractor will be developing, producing, analyzing, maintaining, transporting, storing, testing, or using critical information or indicators for this contract. This work requires Communication Security (COMSEC), access to Foreign Government Information, use of the Secure Communication Network (SIPRNET), to successfully receive, store, and generate Classified Information or Material, as well as fabricate, modify, or store classified hardware in support of the tasking outlined in the TI.
4.2.2.9 The Contractor shall develop an Operations Security (OPSEC) Plan. The Contractor is required to protect critical information associated with the contract to prevent unauthorized disclosure and shall observe OPSEC Requirements. See block 14 of the Department of Defense (DD) Form 254.
(CDRL A005) OPERATIONS SECURITY (OPSEC) PLAN
4.2.2.10 The contractor shall comply with the Government Contracting Activity (GCA) or facilities OPSEC program instructions, guidance and contribute to organization-level OPSEC training and awareness programs while performing aboard designated government sites and facilities. Ensure you read NSWCPHDINST 3070.1A for OPSEC requirements.
4.2.2.11 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.2.3 Deliverables
4.2.3.1 The contractor shall ensure all deliverables provided against this contract contain the appropriate classification marking and distribution statement. The contractor shall adhere to applicable laws, regulations, and government-wide policies when managing all Controlled Unclassified Information (CUI).
4.2.3.2 The Government reserves the right to reject deliverables without the appropriate marking and distribution statement and for errors. The contractor shall correct the deliverable and resubmit to the Government within three (3) workings days after receipt of rejection.
4.2.3.3 Mark CUI according to the DoDI 5200.48, March 6, 2020, and apply Distribution Statements according to DoDI 5230.24, August 23, 2012.
4.2.3.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.2.3.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.2.3.6 Use of Government documentation for commercial purposes is forbidden.
4.2.4 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 by the 10th day of each of each month.
(CDRL A004) REVISIONS TO EXISTING GOVERNMENT DOCUMENTS
4.2.5 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 by the 10th day of each month.
(CDRL A006) GOVERNMENT PROPERTY INVENTORY REPORT
4.2.6 Travel Requirements
The contractor may be required to travel in performance of this contract to CONUS and 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.
4.2.6.1 The contractor shall have personnel ready to support emergent events within 48 hours to perform tasking to CONUS and OCONUS locations.
4.2.6.2 All travel shall be coordinated with the COR, prior to travel. The contractor shall complete and provide the COR with a trip information form (Attachment X) for each trip. The COR will review the request and provide a response within two (2) business days. For urgent travel requirements, the COR will respond with one (1) business day.
4.2.6.3 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 (JTR). It is anticipated that travel will be required primarily within the CONUS but could be required OCONUS.
4.2.6.4 The total number of trips per option period is estimated to be between eleven (11) to one hundred ninety-six (196) trips and the duration of each trip is estimated to be between five
(5) to thirty (30) days. The contractor shall provide a trip report for each trip performed within seven (7) calendar days of trip completion.
(CDRL A007) Trip/Travel Report
4.2.7 Technical Instruction (TI) Form
The issuance of technical tasks required under SOW Section 5.0 Technical Requirements may be provided by the COR via the 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.
5 TECHNICAL REQUIREMENTS
To avoid redundancy, each requirement in this SOW is detailed in a single section, even if it applies to multiple areas. The contractor shall collaborate closely with various programs across different departments to ensure effective execution and alignment with overall objectives.
During performance of tasks, the Contractor shall complete and deliver a Condition Found Report (CFR) for deficiencies found, repairs required and recommend corrective action(s) within three (3) business days of discovery. For conditions found to impact the critical path(s)/controlling item(s), the Contractor shall notify the COR via email within 24 hours of discovery. This initial notification need not include all content required for a CFR but must include a description of the condition/deficiency and the Contractor's professional recommendation for resolution. Review of the CFR and/or initial notification will be completed by the Government’s technical team, COR and PCO. The Government will notify the Contractor on how to proceed via email. If a change to the contract is required, contract modification will be issued.
(CDRL A008) Condition Found Report
5.1 Contingency Environment
NSWC PHD may be required to operate in unpredictable environments, where engineering support is essential for sustaining operational sufficiency, assuring safety, and attaining mission objectives. These environments may present challenges that require innovative and customizable solutions. The objective is to obtain engineering support capable of addressing the unique challenges posed by contingent environment. The contractor support will enable NSWC PHD to respond effectively to evolving situations, implement timely solutions, and mitigate risk associated with operating in such environments.
5.2 Material Procurement
5.2.1 The Contractor shall procure material necessary to perform the tasking described in this SOW and the Government issued TIs. The procurement of any material which is not directly related to and necessary for contract performance may be determined to be unallowable costs pursuant to FAR Part 31. The term “material” includes supplies, parts, equipment, hardware and Information Technology (IT) resources including hardware, services and software.
5.2.2 The Contractor shall provide all consumable materials required for task performance as identified by TI. Consumable material includes but is not limited to; bolts, screws, welding consumables, paint, cable hangers, straps, or other materials not otherwise listed. Consumable materials are required to complete a quality installation according to the TI and its reference documents.
5.2.3 The Contractor shall ship, receive, and manage materials for all CONUS and OCOUNUS locations. The Contractor shall ensure that the installation and removal team receives all materials delivered to foreign ports 30 days prior to the availability or window of opportunity start date.
5.2.4 The Contractor shall provide (fabricate or procure) all material items not provided as Government Furnished Property (GFP) required to perform installation of system units and components per the SIDs. This includes all systems and components identified as Installation Activity Furnished (IAF) items on the List of Materials pages of the SIDs. The Contractor shall have all material at the work site prior to the start of the installation and shall confirm delivery receipt by submittal of the Contractor Furnished Material (CFM) Report.
(CDRL A009) Contractor Furnished Material (CFM) Report
5.2.5 The Contractor shall provide equipment and material transportation and staging areas, which includes Government Furnished Equipment and Material (GFE/GFM) and contractor acquired Equipment and Material, and removed material/equipment identified in the TI to be returned to the Government. The Contractor shall protect, and store removed material/equipment IAW best commercial practices. The Contractor shall ship removed material/equipment back to In-Service Engineering Agent (ISEA) per the TI. The Contractor shall be responsible for covering equipment in the industrial area as part of protection from dust and contaminants associated with work in an industrial environment.
5.2.6 The Contractor shall provide a Final Inventory Report where an installation/modernization effort results in excess government property outside of the Naval Base San Diego (NBSD) area. All items purchased by the contractor to directly support the task that do not meet the FAR Part 45 definition for material are considered Contractor Acquired Property (CAP). CAP and GFP provided on a TI shall be consumed, installed, or returned to the Government as "excess government property." The Contractor shall incorporate information and receipts obtained from the Contractor Furnished Material List (CDRL A009). The Government will notify the Contractor of any GFP or CAP requiring shipment to NBSD for future use.
Consumable items shall be utilized to the maximum extent possible.
(CDRL A00A) Final Inventory Report
5.2.7 The Contractor shall remove all excess material and equipment from the work site, prior to completion of installation. The Contractor shall dispose of the excess material and equipment, unless otherwise identified in the TI, IAW federal, state, and local regulations.
5.3 Engineering, Integration and Test and Evaluation (T&E) Support
5.3.1 The Contractor shall conduct LCS and related surface ships and maritime system studies, analyses, design, fabrication and testing. This includes but is not limited to the following:
assessing engineering and production problems; analyzing program and system costs; human systems integration (HSI) issues; designing, engineering, fabricating, procuring and testing new technologies; designing system and platform improvements; managing and resolving obsolescence issues; and managing schedule risks resulting from ship design changes.
(CDRL A00B) Technical Status Report (CDRL A00C) Subsystem Design Analysis Report
(CDRL A00D) Technical Report Studies (CDRL A00E) Welding Procedures
5.3.2 The Contractor shall provide reports documenting Failure Reporting, Analysis and Corrective Action (FRACAS) reporting to support the Program Office's overall metrics and readiness reporting including:
Tracking and documenting ship operational and performance metrics, to include Mean Time Between Failure (MTBF), Mean Time to Repair (MTTR), Mean Logistics Delay Time (MLDT), and Operational Availability (AO).
Identifying and documenting recurring failures, conducting root cause analysis, and drafting and submitting failure analysis reports.
Participating in Failure Review Boards and working groups established to perform the analysis. Implementing tasks and consistently monitoring and reporting the effectiveness of Failure Review Board/working group recommendations.
Providing support for events that emerge under special circumstances and failure analysis requests in technical support to the U.S. Navy to analyze reported problems to support Condition Based Maintenance (CBM) plus and Reliability, Availability, Maintainability, and Cost (RAM-C) not addressed by existing Data Collection, Analysis, and Corrective Action reports or metrics, including generating customized metrics and documentation required to support any assigned analysis work.
Provide engineering and root cause investigations to support RAM-C improvements;
readiness improvements and obsolescence risk mitigation; and design improvement planning.
(CDRL A00F) Failure Modes, Effects, and Criticality Analysis (CDRL A00G) Failure Analysis and Corrective Action Report (CDRL A00H) Failure Summary and Analysis Report (CDRL A00J) Reliability and Maintainability Prediction Report (CDRL A00K) Reliability-Centered Maintenance Failure Modes and Effects Analysis Report
5.3.3 The Contractor shall provide engineering and test support for assessing system and human performance in order to resolve technical issues during post repair trials, Combat System Ship Qualification Trials (CSSQTs), design improvement upgrades, and system grooms. The Contractor shall provide resources for test events, support emergent requirements, and support working groups, meetings, and Integrated Product Teams (IPTs).
(CDRL A00L) Meeting Minutes
5.3.4 The Contractor shall provide a CONUS/OCONUS subject matter expert team to assist in the event of an emergent requirement where specific technical expertise from the Original Equipment Manufacturing (OEM) is required.
5.3.5 The Contractor shall support emergent requirements, analyze Casualty Reports (CASREPs), and Technical Observation Reports (TORs). If it is determined that there is a problem, the Contractor shall develop and deliver a problem report, provide an initial assessment of the cause and identify which configuration item caused the problem, and conduct further analysis and data collection as required to address the problem.
(CDRL A00B) Technical Status Report
5.3.6 The Contractor shall support Platform Certification requirements in accordance with NAVSEA Command Instruction 9410, including but not limited to: Risk 1 issues; Safety;
Weapon System Explosive Safety Review Board; Navy Certification; Aviation Certification;
Electro Magnetic Interference Certification; Radiation Hazard Certification; C5I) Element Certification; and Training Certification.
5.4 Software Development and Test
5.4.1 The Contractor shall perform Integrated Tactical Trainer (ITT) configuration management. The Contractor shall update and integrate the ITT software to match the shipboard configuration when changes or upgrades are made to the ships’ operating software.
5.4.1.1 Up to two (2) major tactical software updates will be delivered and installed annually to each ITT.
5.4.2 The Contractor shall identify software changes and update ITT software as a result of approved configuration changes, student critiques or shipboard experienced lessons learned.
(CDRL A00M) Software Firmware Change Request
5.4.3 The Contractor shall provide emergent updates that address critical C5I elements that will be supported under ITT Maintenance.
5.4.4 The Contractor shall support software design, development, testing and deployment, including maintaining software testing facilities.
5.4.4.1 Support computer program and software baseline management and provide disaster recovery software; maintain software configurations and files; identify and develop software integration fixes as needed; and integrate with other computer programs including applicable Government furnished programs to form the new computer program sets.
5.4.4.2 Develop computer program engineering changes to support maintenance and modernization and support the development and execution of system-oriented test plans and procedures to ensure compatibility, usability, interoperability, and cross-element functionality integration of updated software.
(CDRL A00N) Producibility Analysis Report
5.4.4.3 Manage developmental and life-cycle software licenses for all shore and ship-based software and hardware requirements.
5.4.4.4 Identify and develop software obsolescence and predictions health charts for predicting end of life and end of procurement in support of technical baseline refresh planning and execution.
(CDRL A00P) Bill of Materials for Logistics and Supply Risk Management
5.4.4.5 Perform the required analysis and conduct the required engineering to establish a definition and approach for the baseline upgrades or critical experiments; analyze software requirement specifications to develop cost/benefit analysis once requirements are defined;
analyze and refine user requirements into system and software requirement; and participate in design reviews.
(CDRL A00Q) Software Requirements Specification
5.5 Cyber Security/Information Assurance
5.5.1 The Contractor shall assess, patch and mitigate vulnerabilities in accordance with Department of Navy Information Assurance (IA) Vulnerability Management policy.
5.5.2 The Contractor shall design, develop, test, and provide software updates and patches to address information assurance related vulnerabilities and system weaknesses.
(CDRL A00R) Information Assurance Test Report (CDRL A00S) Security Evaluation Document
5.5.3 The Contractor shall provide security safeguards in accordance with military standards and requirements. The Contractor shall configure the system in accordance with the Defense Information Systems Agency’s Security Technical Implementation and Security Requirement Guides. The Contractor shall resolve system weaknesses or mitigate the weakness to an acceptable risk level if it cannot be fully resolved.
5.5.4 The Contractor shall provide engineering support services to ensure compliance with new Fleet Advisory Messages; Communication Tasking Orders and/or Fragmentary Orders related to cyber security.
5.5.5 The Contractor shall support updates to LCS adaptation data (i.e. War Diaries, World Maps, etc.) to include development and testing of adaptation data and development of the associated Ship Change Control Board package.
5.5.6 The Contractor shall prepare and submit documentation in accordance with the Risk Management Framework (RMF, DoD Instruction 8510.01) to the U.S. Navy Authorizing Official in order to be granted an Authority to Operate.
(CDRL A00T) DOD Risk Management Framework Package Deliveries
5.6 Planning, Installation and Modernization
5.6.1 The Contractor shall provide design engineering and test support for assessing system and human performance in order to resolve technical issues during post repair trials, CSSQTs and modernization upgrades; support system grooms; analyze data from test events and HSI assessments; provide recommendations for resolution of issues found; support working groups, meetings and IPTs; provide resources for test events; and support emergent requirements.
(CDRL A00L) Meeting Minutes (CDRL A00B) Technical Status Report (CDRL A00U) Human Engineering Systems Analysis Report (CDRL A008) Condition Found Report (CDRL A00V) Key Events Schedule
5.6.2 The Contractor shall support ship checks; documentation development; installation efforts; resources; and services for installation execution.
(CDRL A00D) Technical Report Studies
5.6.3 The Contractor shall support documentation development and revisions and provide installation drawings and documentation in a format compatible with Government technical data information systems, Model Based Product Support (MBPS).
5.6.4 The Contractor shall review and provide comments on installation drawings in accordance with NAVSEA technical specification TS9090-600A; initiate or provide input for initiation of Ship Change Documents (SCDs) or Engineering Change Proposals (ECPs) pertaining to the C5I elements; review Support Service Requests for accuracy prior to submission; provide SCDs in accordance with NAVSEA technical specification document titled
TS9090-400C.
(CDRL A004) Revisions to Existing Government Documents (CDRL A00B) Technical Status Report
(CDRL A00D) Technical Report Studies (CDRL A00W) Alteration Installation Team Quality Assurance Workbook (CDRL A00X) Engineering Documentation Product Drawings, Modified (Maintenance) (CDRL A00Y) Emergent Work Item Specification (CDRL A032) Test Inspection Plan (CDRL A00Z) Test Inspection Plan (CDRL A010) Parts Lists (CDRL A011) Liaison Action Records (CDRL A012) Repair/Modification/Overhaul Status Report (CDRL A013) Installation Specification (CDRL A014) Installation Control Drawings
5.6.5 The Contractor shall quantify the impact of each design change on each applicable system covered by the hull applicability of the change. The impact shall be quantified in terms of the effect on all or any of the following activities: design, engineering, production planning, procurement, ship construction, equipment installations, systems manuals, equipment manuals, associated planning and execution documentation, testing, schedule, and logistics.
(CDRL A015) Logistics Management Information (LMI)
5.6.6 The Contractor shall provide cost estimates to assist with cost benefit analysis development for SCDs.
(CDRL A016) Man-hour Estimate, Technical Cost Proposals
5.6.7 The Contractor shall provide revised Ship Installation Drawings (SIDs), other drawings and Technical Data Packages (TDPs) to meet Planning Yard (PY) requirements.
(CDRL A004) Revisions to Existing Government Documents
5.7 Logistics Support
5.7.1 The Contractor shall analyze the impact that engineering design changes and obsolescence replacements have on provisioning, technical documentation, maintenance procedures, test specifications, and HSI elements.
5.7.2 The Contractor shall maintain and provide updates to all technical data that requires design changes and revisions resulting from form, fit, and function changes or added during the service life of systems identified in this SOW. Technical data includes but is not limited to technical manuals; specifications; standards; engineering drawings; photographs; sketches and descriptions; necessary assembly and general arrangement drawings; schematic drawings;
schematic diagrams; wiring diagrams; cable diagrams. This technical data may be associated with the design, production, operation of, and maintenance of equipment, machines, processes or systems.
(CDRL A017) Contractor Evaluation of Technical Publications and Recommended Changes
5.7.3 The Contractor shall support and develop technical data packages including product drawings and associated lists for Contractor and Government produced logistics product updates.
A TDP shall include all product drawings associated lists, process descriptions, and other documents that define characteristics including physical geometry, material composition and performance as well as manufacture, assembly and acceptance test procedures.
(CDRL A018) Technical Data Package (TDP)
5.7.3.1 The Contractor shall update and maintain technical accuracy of engineering drawings, product models, and associated indentured lists for assigned equipment.
(CDRL A019) Product Engineering Design Data and Associated List
5.7.4 The Contractor shall ensure engineering drawings, product models, and associated indentured lists definitively identify dimensional, material, mechanical, electrical and other characteristics necessary for provisioning and maintenance of the equipment. Drawings and product models shall include but not be limited to cabinet, element, system, ship, interface drawings, and ship space location drawings and models.
5.7.5 The Contractor shall review military essentiality codes, Sources, Maintenance and Recoverability (SM&R) codes, and onboard allowance tables and recommend improvements.
5.7.6 The Contractor shall ensure that provisioning reflects proper maintenance and support requirements of installed equipment configurations; ensure systems and equipment are correctly supported with available and accurate parts; and recommend Allowance Parts List (APL) changes to reflect spares allowancing and efficient supply support. Provisioning shall be delivered IAW the NAVSEA Provisioning and Allowance Procedures Manual NAVSEA M- 4423.1The Contractor shall perform support services in the area of inventory control, interim spares management, and APL management. Develop and maintain provisioning data to include long lead/end of life items, interim spares list, and Installation and Checkout (INCO) spare list.
(CDRL A01A) Installation and Checkout Spares Listing
5.7.7 The Contractor shall perform parts support services by coordinating the receiving, inspecting, repairing, packaging, and shipping of items returned to condition A. Determine correct spares requirements based on a review of the Provisioning Technical Documentation, Planned Maintenance System (PMS) cards, and Reliability-Centered Maintenance (RMC) analysis. Develop and update Preliminary Allowance Lists (PALs), Preliminary Equipage Lists, On Board Repair Parts List, Inventory Control Plan, Interim Spares Plan, Interim Supply Support Plans, and Supply Support Plans.
(CDRL A010) Parts List (CDRL A012) Repair/Modification/Overhaul Status Report (CDRL A01B) Report of Receipts, Inventory, Adjustments, and Shipments of Government Property (CDRL A01C) Government Furnished Property Inventory and Forecasting Report
5.7.8 The Contractor shall identify, resolve, and document Diminished Manufacturing Source Material Shortage (DMSMS) issues, hardware changes, and compatibility issues. This entails conducting research to determine or validate the system Bill of Materials (BOM), finding alternate compatible parts, mitigating the impact of unavailable parts, updating logistics documentation and databases, and preparing reports as outlined in the Defense Standardization Program Office Diminishing Manufacturing Sources and Material Shortages Guidebook (SD- 22).
5.7.8.1 The Contractor shall conduct vendor surveys for parts identified as mission critical and ascertain configuration and continued production availability; document results of these surveys and problems encountered; and maintain a critical parts list.
5.7.9 The Contractor shall maintain a standardized configuration management program and configuration status accounting files that effectively controls the hardware, middleware, technical documentation, and computer program configuration baselines. The Configuration Status Accounting (CSA) files for the ship configurations include applicable data for technical manuals, PMS, SIDs, approved changes, alterations, and SCDs.
5.7.10 As part of Local Change Control Board (LCCB) process, the Contractor shall review and provide comments for change reviews and attend LCCB as required.
5.7.11 The Contractor shall update configuration data for all design changes, including alterations and modernization.
5.7.12 The Contractor shall record, and report information needed to manage configuration items effectively, including the status of proposed changes and implementation status of approved changes.
(CDRL A00B) Technical Status Report
5.7.13 The Contractor shall develop support plans, recommendations, modifications or improvements to Government logistics support requirements; the logistics support plan/program, and associated logistics support elements.
5.7.14 The Contractor shall support Coordinated Shipboard Allowance List (COSAL) maintenance efforts and coordinate necessary APL changes to reflect optimum COSAL and supply support.
5.7.15 The Contractor shall support Readiness Based Sparing analysis and provide output reports.
5.8 Training Support
5.8.1 The Contractor shall identify new training devices, software, equipment, and updates to existing training devices such as the ITT including associated Common Mission Package…
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .