SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

Work under this performance-based task order will be performed in accordance with the following description/ specifications/ statement of work (SOW) which herein will be referred to as Performance Work Statement (PWS):

SHORT TITLE: SHORE SUBMARINE COMMUNICATIONS SYSTEM (SSCS) COMMAND, CONTROL, COMMUNICATIONS, COMPUTERS, & INTELLIGENCE (C4I) TECHNICAL SUPPORT

1.0 PURPOSE

1.1 SCOPE

This PWS covers systems engineering, technical, and management support services to the Program Manager Warfare (PMW) 770 Program Office for Naval Information Warfare Center Atlantic (NIWC Atlantic). This support encompasses engineering analysis and technical support services required to support the Shore Submarine Communications Systems (SSCS) identified in paragraph 3.0 by providing components through system level engineering, Subject Matter Expert (SME) technical and training support for the modernization, sustainment and on-site technical support.

NOTE: Website and e-mail addresses referenced within the PWS and Contract Data Requirements List (CDRL) forms are subject to change. For any website and e-mail address not working during time of performance, the contractor shall contact the Contracting Officer’s Representative (COR) or Contracting Officer for the latest website and e-mail address. An incorrect website or e-mail address does not alleviate a contractor from required reporting or access requirements.

1.2 BACKGROUND

The Undersea Communications & Integration Program Office (PMW 770) mission is to accomplish “Seamless, End-to-End Communications, Information Exchange System (IXS) to Internet Protocol (IP) Transition, and Higher Data Rates for the Submarine Force.” This effort has been focused on improving stealthy communications, continuing IXS to IP transition efforts, and increasing submarines’ worldwide communications capabilities. PMW 770 is the Echelon II Command providing funding and direction to NIWC Atlantic as the Echelon III for Submarine Operating Authority (SUBOPAUTH) programs .

The SUBOPAUTH program provides a consolidated shore infrastructure to support submarine communications and to ensure flexible and common operations within the four (4) SUBOPAUTH facilities worldwide, ten (10) Fixed Broadcast Transmitter Stations, three (3) Tack Charge and Move Out (TACAMO) units and the Expeditionary Very Low Frequency systems. The SUBOPAUTH program supports Continuity of Operations (COOP) and consistent Command and Control of Submarines from worldwide SUBOPAUTH facilities. The SUBOPAUTH network provides the only means to communicate with submarines at speed and depth. NIWC Atlantic is the designated In-Service Engineering Activity (ISEA) for all SUBOPAUTH systems and is responsible to ensure these architectures are always operational.

2.0 PLACE(S) OF PERFORMANCE

The contractor shall provide support at the following location:

a. NIWC Atlantic Charleston, SC

b. NIWC Atlantic Portsmouth, VA

c. Contractor Facility Comment by Aller, John Charles CIV USN NIWC ATLANTIC SC (USA): I thought we had the BCA sites listed since we had people pcs there

2.1 GOVERNMENT FACILITIES

Government facilities (i.e., office space or lab space) are provided to those contractor personnel that would otherwise adversely affect the work performance if they were not available on the Government site. Labor categories with supplied Government facilities shall be located at NIWC Atlantic in Charleston, SC and Portsmouth, VA.

2.1.1 Access to Government facilities

NIWC Atlantic and other Government installations have restricted access. Contractors are limited to access during certain days and times as specified in the workweek requirements of this PWS. If access to the assigned Government facility is restricted due to safety/security exercise, an Executive Order, or an administrative leave determination applying to the local activity (e.g., inclement weather), the contractor, in agreement with the COR, shall make alternative work arrangements. The contractor shall adjust the work schedule, work at an alternate location, or if alternate work arrangements cannot be accommodated, the contractor shall notify the COR of the inability to access the assigned facility prior to charging their time to the task order as direct cost provided such charges are consistent with the contractor’s accounting practices.

2.1.2 Training Requirements and Exercise Support

Contractor personnel working full-time or partially at a Government facility shall complete all applicable training requirements as specified under Mandatory Training, PWS Para 8.0. Contractor personnel may also be required to participate in safety, security (e.g., Anti-Terrorism Force Protection (AT/FP)), and operational training exercises (possibly two per year). Applicable contractor personnel shall support and participate in the training exercise which may include role-playing and reacting to exercise injections based on the situation or exercise objectives.

2.1.3 Emergency Management at Government Installations

During emergency situations including health (e.g., COVID-19 pandemic) and weather related circumstances, contractor personnel with scheduled access to a Government installation shall coordinate with the COR prior to reporting to their Government worksite. Access will be in accordance with the latest Government installation requirements and restrictions. The contractor shall identify with the COR if certain personnel are designated mission essential and determine the work expectations during the emergency period of performance. Depending on the type of support, working on an alternative worksite may or may not be allowed.

2.2 CONTRACTOR FACILITIES

A significant portion of work issued under this task order requires close liaison with the Government. The contractor shall be prepared to establish a local facility within a thirty (30)-mile radius of NIWC Atlantic Portsmouth, VA. The contractor shall be capable of quickly interfacing with the labs located at NIWC Atlantic Portsmouth, VA. The contractor’s facility is not necessarily for the exclusive use of this task order and can be utilized on a shared basis. The contractor shall meet all facility location and size requirements within 30 days after task order award. The contractor’s facility shall include physical security to protect Government property as identified in PWS Para10.0. The contractor shall ensure facility configuration includes space for offices, conference rooms, lab work, and a staging area for materials and equipment.

2.3 ALTERNATE WORK LOCATIONS

The ability to provide support from an alternate location (includes working from an employee’s residence or other non-Government facility) is dependent on the type of support required, the contractor employee’s ability and trustworthiness, and the company’s employment policy. Allowing work to be performed at an alternate location is not an option for all positions and personnel. The ultimate decision to allow work performed at an alternate work location will be determined by COR. If alternate work locations are allowed, the company shall have defined criteria addressing the minimum requirement to have continuous, secure internet connection. Each applicable contractor employee shall have an established signed telework agreement between the company and employee. For each contractor employee proposed to work at an alternate location, the contractor shall submit a written request and justification to the COR with a copy of the applicable employee’s signed telework agreement which becomes part of the COR files. If the requirements for teleworking and/or alternate work locations are not outlined/specified in the employee agreement documentation, the contractor shall include a copy of those requirements with the signed employee agreement. Working at an alternative location shall not adversely affect the response time required in support of the task order. The Government reserves the right to disallow any billable hours by contractor employees working at an alternative work location without obtaining prior Government approval. The Government reserves the right to discontinue the ability to work from an alternate location at any time without cause. The inability of a contractor to respond to the requirements of the task order due to telework conditions will be negatively reflected in the Contractor Performance Assessment Reporting System (CPARS). The contractor shall utilize the Government site or Client site (vice contractor site) overhead labor rate for personnel working from their residence unless their Accounting System requires a different billing structure.

3.0 PERFORMANCE REQUIREMENTS

The following paragraphs list non-personal services tasks that will be required throughout this task order. The contractor shall provide the necessary resources with knowledge and experience as cited in the personnel qualification requirement to support the listed tasks. The contractor shall fulfil requirements in accordance with the Federal Acquisition Regulation (FAR) and/or Defense Federal Acquisition Regulation Supplement (DFARS) that do not include performance of inherently Government functions. The contractor shall complete all required tasks while controlling and tracking performance and goals in terms of costs, schedules, and resources.

The following task is supporting PMW 770, Naval Information Forces (NAVIFOR), Foreign Military Services (FMS), and Submarine Learning Center (SLC) for SSCS Program operations and maintenance support. The tasking in this section crosses SUBOPAUTH, WTAC, Low Band Universal Communications System (LBUCS) and Expeditionary VLF funding CLINs.

In executing the work listed below the Contractor shall participate in the PMW 790 the Scaled Agile Framework (SAFe) methodology for the development of new capabilities and sustainment engineering efforts required under this PWS. The SAFe process shall be applied to tasks including, but not limited to, system engineering, cyber security, testing, technical and logistics document production, and the creation of installation documentation. The Contractor's implementation of this framework will be centered around quarterly Phased Implementation (PI) planning events, which are used to define and organize work for a 13-week increment. This work is then executed through a series of sprints within that PI. While SAFe is the current methodology, the Contractor shall be prepared to adapt to other agile methodologies that may be adopted in the future

3.1 Program Support

The contractor shall provide integrated program and project management support to coordinate the tasking described in the PWS.

3.1.1 SUBOPAUTH Program Support

Some programs shall require a Contractor to work closely with the Government COR and support the needs of the program at the sponsor level. As required, the Contractor shall assist with coordination of meetings, preparing budget drills, developing agenda items, attending high-level meetings, generating minutes, and tracking action items may be required. Program support may require significant coordination and interface with various Department of Defense (DoD) and non-DoD activities located in and out of Continental United States (CONUS/OCONUS).

3.1.1.1 The Contractor shall be responsible for the coordination and participate in reviews, meetings, conferences, boards, working groups, demonstrations, tests, audits, and surveys in the performance of the other tasking elements of this PWS. The Contractor shall propose and conduct periodic technical exchange meetings (TEMS) for collaborative development sessions, program reviews, and design reviews (formal and informal, telecom and face-to-face) with project stakeholders, delegates, or both; as well as coordinate Task Order quarterly program status and financial reviews with the COR/PM.

3.1.1.2 SUBOPAUTH Financial Management Support

The Contractor shall provide financial documentation required to support management decisions including funding status, cost estimate support for project/program efforts and cost impact of changes in project, and Program Management Documentation (production and delivery schedules) (CDRL A001).

3.1.1.3 SUBOPAUTH Program Plans/Documentation

The Contractor shall follow the defined Government provided risk management plan/process. The purpose of risk management is to define the course of action for identifying, evaluating, planning responses for, and monitoring risks and issues. Risk Management is an extended process across almost all phases of project management and technical execution. The Contractor shall identify, document and manage project risks both internally (NIWC Atlantic) and externally (SUBAUTH sites). For each project, the Contractor shall meet with the Government technical project leads monthly at a minimum and discuss existing and emergent risks (frequency shall be defined at the task order level). For each risk approved by the Government, the Contractor shall develop a Risk-Mitigation Plan (RMP) (CDRL A002). The Contractor shall develop, analyze, make recommendations, provide rationale for the recommendations and provide technical and administrative support in preparing workloads, program plans and/or project associated documentation (CDRL A001). These plans will be requested on a project basis, with the type of plan differing according to the project but being performed within the existing/required Level-of-Effort.

3.1.1.4 SUBOPAUTH Program/Project Reports

The Contractor shall be responsible for developing and maintaining a comprehensive integrated cost and milestones schedule plan (CDRL A003) including tasking, milestones, and deliverables associated with each SUBOPAUTH project. Monthly updates to the cost and milestones schedule shall be presented to the COR. The Contractor shall prepare and conduct program management reviews that is included in Program Management Documentation (CDRL A001) with the COR monthly. The program management reviews shall consist of providing an overview of system planning documents, which include but are not limited to Project Schedules, objectives, and status of coordination efforts prior to on-site or off-site work.

3.1.2 LBUCS Program Support

Some programs shall require a Contractor to work closely with the Government COR and support the needs of the program at the sponsor level. As required, the Contractor shall assist with coordination of meetings, preparing budget drills, developing agenda items, attending high-level meetings, generating minutes, and tracking action items may be required. Program support may require significant coordination and interface with various Department of Defense (DoD) and non-DoD activities located in and out of Continental United States (CONUS/OCONUS).

3.1.2.1 The Contractor shall be responsible for the coordination and participate in reviews, meetings, conferences, boards, working groups, demonstrations, tests, audits, and surveys in the performance of the other tasking elements of this PWS. The Contractor shall propose and conduct periodic technical exchange meetings (TEMS) for collaborative development sessions, program reviews, and design reviews (formal and informal, telecom and face-to-face) with project stakeholders, delegates, or both; as well as coordinate Task Order quarterly program status and financial reviews with the COR/PM.

3.1.2.2 LBUCS Financial Management Support

The Contractor shall provide financial documentation required to support management decisions including funding status, cost estimate support for project/program efforts and cost impact of changes in project, and Program Management Documentation (production and delivery schedules) (CDRL A001).

3.1.2.3 LBUCS Program Plans/Documentation

The Contractor shall follow the defined Government provided risk management plan/process. The purpose of risk management is to define the course of action for identifying, evaluating, planning responses for, and monitoring risks and issues. Risk Management is an extended process across almost all phases of project management and technical execution. The Contractor shall identify, document and manage project risks both internally (NIWC Atlantic) and externally (LBUCS sites). For each project, the Contractor shall meet with the Government technical project leads monthly at a minimum and discuss existing and emergent risks (frequency shall be defined at the task order level). For each risk approved by the Government, the Contractor shall develop a Risk-Mitigation Plan (RMP) (CDRL A002). The Contractor shall develop, analyze, make recommendations, provide rationale for the recommendations and provide technical and administrative support in preparing workloads, program plans and/or Program Management Documentation (CDRL A001). These plans will be requested on a project basis, with the type of plan differing according to the project but being performed within the existing/required Level-of-Effort.

3.1.2.4 LBUCS Program/Project Reports

The Contractor shall be responsible for developing and maintaining a comprehensive integrated cost and milestones schedule plan (CDRL A003) including tasking, milestones, and deliverables associated with each LBUCS project. Monthly updates to the cost and milestones schedule shall be presented to the COR. The Contractor shall prepare and conduct program management reviews that is included in Program Management Documentation (CDRL A001) with the COR monthly. The program management reviews shall consist of providing an overview of system planning documents, which include but are not limited to Project Schedules, objectives, and status of coordination efforts prior to on-site or off-site work.

3.2 SYSTEMS TECHNICAL SUPPORT

3.2.1 SUBOPAUTH/LBUCS Support

Project provides a consolidated shore infrastructure to support Shore Submarine Communications Systems. ISEA is designated for all SUBOPAUTH/LBUCS systems and is responsible for ensuring these architectures are always operational ensuring flexible and common operations within the SUBOPAUTH facilities worldwide. In the performance of these duties the Contractor shall be required to enter the Sensitive Compartmented Information (SCI) spaces when operations are taking place. The Contractor shall be required to enter the SCI spaces to specifically perform configuration management, cybersecurity support, enterprise modernization engineering, testing, and production, ISDS SME, trusted agent, and Information Assurance (IA) certification support.

3.2.1.1 Systems and Equipment

The Contractor shall provide functional and technical expertise supporting a wide range of Department of the Navy (DoN) and DoD Business IT systems. Systems will range from client-server applications, employing interactive and batch processes, to customized web-based solutions, operating in a distributed or standalone environment. Such systems include, at a minimum:

1. Shore Submarine Communications Systems, which include:

a. Submarine Message Gateway – Legacy (SMG-L) Computer System

b. Common Operational Toolset (SCOT) Servers

c. Submarine Wide Area Network (SWAN)

d. Submarine Message Gateway (SMG)

e. Very Low Frequency (VLF) Broadcast Builder (VBB)

f. Windows off the air monitor (Win OTAM)

g. Top Secret (TS) Utility Workstation

h. Cybersecurity Support Server (CSS)

i. Submarine Fleet Mail Server (Sub FMS)

j. LBUCS

k. Integrated Verdin Transmit Terminal (IVTT)

l. North Atlantic Treaty Organization (NATO) Interoperable Submarine Broadcast System (NISBS)

m. Information Screening and Delivery System (ISDS)

n. Broadcast Control Authority (BCA) Utility Workstation

o. Secure File Transfer Protocol (SFTP)/ Conversational Hypertext Access Technology (CHAT) server

p. Virtual Desktop Infrastructure (VDI)

q. Host Based Security System (HBSS)

r. Assured Compliance Assessment Solution (ACAS)

s. Submarine Operating Authority - Enterprise (SOA-E) Application Hosting

t. Environment (Computer Information System Company /Unified computing System/Network Applications/Storage Area Network (CISCO/UCS/NetApp/SAN))

u. Hyper Converged Infrastructure (HCI) NUTANIX, Inc. Hosting Platform.

v. Clarinet Merlin Receiver System (CMRS) network

w. Cross Domain Solution (CDS)

x. Nova information Exchange Terminal (NIXT) /Naval Message Handling System (NMHS)

y. Expeditionary VLF Transmission system SOA equipment

2. SUBOPAUTH operating systems include:

a. Virtual Machine Software (VMWARE)

b. CISCO Internet Operating System (IOS)

c. Microsoft Azure

d. Red Hat Linux Enterprise

e. Microsoft (MS)-Disk Operating System (DOS)

f. Microsoft Windows Workstation and Server

g. NETAPPS Data Open Network Technology for Appliance Products (ONTAP)

h. Docker Enterprise

i. Kubernettes

j. HYCU

3.2.1.2 The Contractor shall conduct site surveys (ND-1) to determine the optimum location and configuration for equipment/system modifications or upgrades. The Contractor shall gather all pertinent environmental, engineering, configuration and design information relevant to site conditions, analyzing the collected data, performing necessary calculations to make technical recommendations, and preparing technical reports and documentation (CDRL A004) for a specific engineering change proposal, modification, or system upgrade.

3.2.1.3 The Contractor shall assist Fleet personnel on Shore Submarine Communications Systems to include training, routine maintenance, troubleshooting, and repair of Internet Protocol (IP) based communications systems including systems that carry up to SCI information. The Contractor will notify NIWC Atlantic via telephone or email of any problems that cannot be rectified locally and shall be required to enter all problems/problem resolution into the NIWC Information Technology Service Management (ITSM) system as outlined in NIWC ATLANTIC RSOP-57700-00005. The Contractor shall document, report, and Shore Submarine Communications Systems and circuit outages via weekly status reports. This shall include the date and time of the outage, actions required to rectify the outage, and any recommendations or comments deemed of interest to ISEA Government personnel.

3.2.1.4 The Contractor shall provide technical support to system administration of designated Shore Submarine Communications Systems. This shall include such items as the administration of passwords, database backups, configuration management and other routine network administrative activities required to ensure the proper operation of the operating systems identified in section 3.2.1.1.

3.2.1.5 The Contractor shall provide technical representation at meetings for the purpose of reviewing Shore Submarine Communications related technical information and providing technical expertise. The Contractor shall provide a Technical Report (CDRL A004) outlining technical issues, problems and proposed solutions. This report shall also identify upcoming events such as training events, embedded site planned installations, scheduled outages, etc. (anything that may be of interest to the ISEA). The Contractor shall participate in a semi-annual Shore Submarine Communications Technical Review. This will require travel to the host site. Additional travel may be required to support meetings, testing, troubleshooting or training at various submarine communications sites as defined in section 11.0. The Contractor shall submit a single trip report (CDRL A005) outlining the results of the technical review.

3.2.1.6 The Contractor shall perform telephone, e-mail, and naval message technical assistance to the fleet to resolve equipment failures. The Contractor shall acknowledge all requests for technical assistance within sixty (60) minutes of receipt. The Contractor shall respond with the requisite assistance to all requests within one (1) business day. For all requests that cannot be resolved in this period, the Contractor shall provide the schedule for resolution of the issue (CDRL A001). All technical assistance will be recorded using NIWC ITSM Remedy trouble reporting system as outlined in NIWC ATLANTIC RSOP-57700-00005. The contractor shall utilize weekly and monthly ITS reports to conduct system readiness analysis.

3.2.1.7 The Contractor shall create hard disk images of all Shore Submarine Communications systems located within NIWC Atlantic equipment labs. These images shall contain the current level of Cybersecurity lockdowns for the system being imaged. These images shall be documented in a spreadsheet type format showing at a minimum the total number of images held, serial number of the image, system it was created from, date created, and location of where stored. The contractor shall conduct a monthly inventory of images stored.

3.2.1.8 The Contractor shall perform product troubleshooting, repairs and perform technical analysis on failed Shore Submarine Communications systems equipment by using the references in section 16.2 as guidance. It is estimated that there shall be a total of 200 pieces of equipment required to be repaired by the Contractor. Of the 200, it is estimated that 150 pieces of equipment shall be at the NIWC Atlantic equipment labs, and fifty (50) pieces of equipment will be required to be repaired on-site at travel locations specified in section 11.0. The Contractor shall submit a trip report (CDRL A005) for any onsite technical assistance visit made. The Contractor shall repair each item within ten (10) business days or provide a resolution schedule to include the type of equipment, type of failure, and reason for the delay in repair. The Contractor shall demonstrate that each item of equipment repaired is returned fully operational condition. Each repaired item shall be tested (in-lab or on-site) and signed off by Government personnel. The Contractor shall document all repair efforts using the NAVWAR Classified Network ITSM Remedy trouble reporting system and report this in a Technical Repair Report (CDRL A004).

3.2.2 Shore Submarine Communications System Technical Support The Contractor shall provide Shore Submarine Communications systems technical services for fleet support to include configuration, hardware/software troubleshooting and coordinate repair items for the Submarine BCA/WTAC BCA/ Broadcast Keying Stations (BKS)/ Broadcast Transmitter Station (BTS) installations. Provide analysis, recommendations, and network engineering support for ISDS system interconnections and integration networking solutions for all existing BCA systems. Provide system installation, configuration and groom support at the ISEA and at the Submarine BCA/BKS/BTS sites identified in section 11.0 of this PWS.

The Contractor shall provide technical services in support of the design and review of the Shore Submarine Communications Systems hardware/software configuration. The Contractor shall develop and provide test documentation (test and evaluation support for new concepts) (CDRL A006), lead site testing, System Operational Verification Testing (SOVT) or other test events that require SOA-E Hosting platform or network architecture experts. This development support shall include such items as data collection, network analysis, circuit operation, and troubleshooting and repair as necessary to support SOVT, as well as experiments such as Trident Warrior, or other tests requiring technical expertise at the SUBOPAUTH facilities.

The Contractor shall provide software qualification, validation and regression testing expertise to include writing of test plans, execution and providing completion test reports (CDRL A006). The Contractor shall provide status updates of this task in their inputs to the WSR (CDRL A007).

3.2.2.1 The Contractor shall work with the BCA and Special Intelligence Broadcast Facility (SIBF) Engineers for troubleshooting and repair of shore submarine IP based communications systems, shore submarine communications systems development support, submarine communications system testing and evaluation, submarine communications system sustainment, integration and Configuration Management (CM) of multiple submarine communications products and technical input into long term modernization planning and execution related to the shore infrastructure supporting submarine communications.

3.2.2.2 The Contractor shall provide BCA design technical services in support of the design and review of the Shore Submarine Communications systems hardware and network configurations. The Contractor shall review all design plans for the Shore Submarine Communications systems and make recommendations for the integration of this configuration into the existing BCA architecture.

3.2.2.3 The Contractor shall provide IP network technical services in support of the Shore Submarine Communications systems architecture modernization and fielding of new products/systems. The Contractor shall utilize current telecommunications protocols and network architectures and provide modification plans for changes required because of Shore Submarine Communications systems deployment and existing equipment modernization.

3.2.2.4 The Contractor shall provide engineering support/technical services to incorporate/integrate the following services/systems into one (1) program of record (POR) system under PMW 770. These services shall specifically include the following:

a. Microsoft Active Directory

b. SOA-E, CISCO FlexPod (CISCO UCS, NetApp FAS)

c. Virtual Desktop Infrastructure

d. SFTP / Chat server

e. SUBOPAUTH Software Tools

f. SUBOPAUTH Common Operational Toolset (SCOT) Servers

g. SUBOPAUTH Wide Area Network (SWAN)

h. Submarine Message Gateway (SMG) Computer System

i. SUBOPAUTH Control Console (KVM System)

j. Submarine Message Gateway – Legacy (SMG-L) Computer System

k. Automatic Digital Network System (ADNS) Increment III

l. Baseband RF Equipment (Extremely High Frequency (EHF) Terminal, Ultra High Frequency (UHF) Terminal, High Frequency (HF) Receivers)

m. Information Screening and Delivery Subsystem (ISDS)

n. Hyper Converged Infrastructure (HCI) NUTANIX Hosting Platform.

o. Clarinet Merlin Receiver System (CMRS) network

p. Cross Domain Solution (CDS)

q. Nova information Exchange Terminal (NIXT) /Naval Message Handling System (NMHS)

r. Crypto Host Control Interface (HCI)

3.2.2.5 The Contractor shall provide systems engineering, integration, testing and documentation of non PMW 770 POR systems with existing Shore Submarine Communications systems in NIWC Atlantic lab facilities. The Contractor shall develop testing plans and detailed test reports, (CDRL A006) execute testing and provide written technical/procedural recommendations for improvements in architecture.

3.2.2.6 The Contractor shall provide technical representation in the development and review of fleet Shore Submarine Communications systems operating procedures and concept of operations (CDRL A004) to support the best utilization of Shore Submarine Communications systems capabilities to support communications with the submarine force.

3.2.2.7 The Contractor shall provide technical services in support of the design and review of the Shore Submarine Communications systems hardware configuration. The Contractor shall review the hardware design plan for the specific systems and make recommendations for the integration of this configuration into the existing shore submarine architecture. The Contractor shall provide a technical report (CDRL A004) documenting the results of this analysis.

3.2.2.8 The Contractor shall provide system development technical support in the system development labs located at NIWC Atlantic (Virginia). The Contractor shall be responsible for troubleshooting and configuring the system as required during the development and testing of the Shore Submarine Communications systems. The Contractor shall provide inputs to weekly status report (CDRL A007) detailing all actions performed.

3.2.3 Very Small Aperture Satellite Terminals (VSAT) Support

The Contractor shall provide VSAT technical on-site and distance support as required at each Shore Submarine Communications site.

3.2.3.1 The Contractor shall perform an on-site inspection of the Digital Systems side of the Shore Submarine Communications Systems that is located at the Broadcast Transmit Sites (BTS). This inspection shall include an operational check of all equipment in the system and an analysis of its status. The Contractor shall provide on-site technical assistance for any items that can be repaired and for those items that can’t be repaired on-site, provide trouble ticket data for repairs to be completed in the Fleet Support Lab at NIWC Atlantic. All technical analysis will be performed using the specifications in section 16.2 as guidance. The equipment consists of MD-1316, MD-5062, and MD-3920, timing systems, MD-1310 modulators, NISBS formatters and LBUCS. It is estimated that there will be a total of fifty (50) pieces of equipment required to be repaired by the Contractor. It is estimated that twenty (20) pieces of equipment will be at the Fleet Support Lab at NIWC Atlantic to be repaired. The Contractor shall repair each item within ten (10) business days or provide a resolution schedule to include the type of equipment, type of failure, and reason for the delay in repair. The Contractor shall demonstrate that each item of equipment repaired is returned fully operational condition. Each repaired item shall be tested in-lab and signed off by Government personnel. The Contractor shall document all repair efforts using the NAVWAR Classified Network ITSM trouble reporting system.

3.2.3.2 The Contractor shall provide interface and technical support for VSAT supporting the Shore Submarine Communications Systems program. The Contractor shall coordinate with service providers to ensure the proper operation and maintenance of the VSAT ground and hub terminals. The Contractor shall develop, review and maintain VSAT connectivity design and implementation documentation (CDRL A004). The Contractor shall develop installation documentation (CDRL A003) and support installation and maintenance of VSAT last mile connectivity.

3.2.3.4 The Contractor shall perform a site visit to five (5) submarine broadcast transmitter sites to perform Shore Submarine Communications systems groom. The Contractor shall provide the engineering/technical expertise to operate, test, inspect, align, groom, repair and analyze/assess C4I system/equipment material condition during Sub Shore events or similar test and inspection programs. This includes identifying and correcting system/equipment discrepancies.

3.2.4 Foreign Military Support (FMS) Support

The Contractor shall support FMS tasking for submarine communications shore C4I and afloat communications systems under the SOA-E program umbrella. This includes the installation, testing, SOVT, training and support of U.S. Navy submarine related communications systems and software applications implemented within the OPNAV/PMW 740 FMS Program office at various allied countries. The Contractor will submit a completion report (CDRL A004) for each deployment made.

3.2.4.1 The Contractor shall provide technical support for Shore Submarine Communications Systems installed at shore and afloat units as directed by the Shore Submarine Communications Systems ISEA. This included development, deployment and integration of site/system specific systems. The Contractor shall provide documents for technical approval.

3.2.4.2 The Contractor shall provide remote support to allied nations for submarine related communications systems/software applications installed via email, telephone, chat and other secure communications links.

3.2.5 Submarine Learning Center (SLC) Training Support ND-2

The Contractor shall coordinate with each site to schedule and complete LBUCS system training semiannually at each site. The Contractor will maintain a yearly training schedule that will be provided to the COR whenever updates are implemented.

3.2.5.1 The Contractor shall provide training results, student rosters, and student critique sheets for all training sessions (CDRL A008).

3.2.5.2 The Contractor shall be responsible for the updating and maintenance of all training materials. All updates/changes will be routed through the designated technical representative for approval prior to use.

3.2.6 Circuit Management Support

The Contractor shall provide technical services for Shore Submarine Communications Systems to include documenting the configuration, providing usage and throughput analysis, circuit requirements validation, restoral priority justification, circuit testing and troubleshooting. The Contractor shall document all technical assistance in the NAVWAR Classified network ITSM ticketing system and provide WSR to the ISEA (CDRL A007).

3.2.6.1 The Contractor shall track and manage all Shore Submarine Communications systems related circuit connectivity between BCA, BTS, Clarinet Merlin Receiver Stations (CMRS), and TACAMO facilities. The Contractor shall provision, change and disestablish circuit connectivity using Defense Information Systems Agency (DISA) Storefront services and utilize Technical Control Operating Support System (TCOSS) and the DISAC 310 circulars.

3.3 SOFTWARE ENGINEERING

Software engineering includes the design, development, and documentation of software to support a specific government requirement. The contractor shall utilize certified software and computer personnel. The contractor (prime and/or subcontractor) that is responsible for leading software development efforts shall define a software development approach appropriate for the computer software effort to be performed under each task. The contractor shall document the approach in a Software Development Plan (SDP) (CDRL A009). The contractor shall follow this SDP for all computer software to be developed or maintained under this effort. The contractor shall develop one SDP to support the unique task order software requirements. At a minimum, the contractor shall ensure the SDP meets the criteria specified in the CDRL DD1423 using ISO/IEC/IEEE 12207:2017 and the PWS tasking.

3.4 EQUIPMENT AND MATERIAL SUPPORT

3.4.1 Procurement Support

The contractor shall research and procure/fabricate equipment and/or material in support of the performance requirements. Under this cost reimbursable contract line items, items purchased are known as contractor-acquired property (CAP) and are identified in PWS Para 10.2. To ensure fair and reasonable pricing under this cost reimbursable contract line item, the contractor shall ensure acquisition selection factors include price, availability, reliability, and supportability within the current supply system. The contractor shall keep source selection records and make it available for government review as needed. Prior to purchasing items, the contractor shall obtain COR concurrence. The contractor shall provide all support data and cost estimates necessary to justify a fair and reasonable price per item procured. As mandated in the FAR, the contractor shall have an adequate accounting system to track all items ordered and its associated delivery status. After receiving the receipt, the contractor shall have an adequate property management system to track each item’s location. All items procured by the contractor shall be utilized or staged at the contractor’s facility transported by the contractor to the installation, integrated or consumed in a system, or returned to the government at the completion of the task order. The contractor shall be responsible for managing Government property in accordance with PWS Para 10.3. The contractor shall recommend and procure items that conform to the following applicable product validation, identification, and tracking requirements.

3.4.1.1 Product Validation – The contractor shall certify that it purchases supplies from authorized resellers and/or distributers. The contractor shall warrant that the products are new, in their original box. The contractor shall obtain all manufacturer products submitted in task order offers from authentic manufacturers or through legal distribution channels only, in accordance with all applicable laws and policies at the time of purchase. The contractor shall provide the Government with a copy of the End User license agreement and shall warrant that all manufacturer software is licensed originally to Government as the original licensee authorized to use the manufacturer software. The contractor shall track the licensing information and have it available for government review.

3.4.1.2 IT Security Requirements – The contractor shall ensure that all products recommended and/or procured meet cybersecurity and computer requirements specified in PWS Para 4.0.

3.4.1.3 Electronic Parts – In order to mitigate use of counterfeit and/or defective electronic parts, the contractor shall ensure all acquired electronic parts comply with the notification, inspection, testing, and authentication requirements in accordance with DFARS 252.246-7007 and DFARS 252.246-7008 specific to electronic parts.

3.4.1.4 Item Unique Identification (IUID) – In accordance with SECNAVINST 4440.34, the contractor shall ensure that certain delivered items manufactured, integrated, or purchased (depending on if item meets a unit cost threshold, is serially managed, or if government specifies identification required) have an item unique identification or Unique Item Identifier (UII). If specified by the Government, prior to delivery, the contractor shall clearly mark and identify each applicable item based on the guidance provided in DoD MIL-STD-130N for those items not already marked. With Government concurrence, the contractor shall specify the construction, syntax, marking methodology, and quality methodology chosen to mark the required parts and any corresponding technical justification. All IUID information shall be recorded and shall be subject to Government review. The contractor shall track IUID items and maintain information being recorded. Prior to delivery of applicable CAP item, the contractor shall register items with Unique Item Identifier (UII) in the IUID Registry.

3.4.2 Warranty Tracking & Management

3.4.2.1 Warranty Tracking of Serialized Items

In accordance with DFARS 252.246-7005/7006 and the Warranty Tracking and Administration Information for Serialized Items (CDRL A010), the contractor shall follow the applicable requirements for submitting Warranty Tracking Information (WTI) form and Source of Repair Instruction (SORI) form if any serialized item manufactured or acquired is provided with a warranty:

(a) For Government specified warranty terms – the Government will complete certain fields on the WTI form (Attachment 2) and the SORI form (Attachment 3). The contractor shall complete the remaining sections of the WTI and forward the form as part of their task order proposal prior to the award. The contractor shall complete the remaining sections of the SORI and forward the form (CDRL A010) to the Contracting Officer and COR at the time of delivery of the warranted serialized item(s).

(b) For contractor/vendor specified warranty terms – the contractor shall complete all data elements for both the WTI (Attachment 2) and SORI (Attachment 3) and shall forward the completed forms (CDRL A009) to the Contracting Officer and COR no later than the date the warranted serialized items are presented for receipt and/or acceptance.

(c) For receipt and acceptance of items – the contractor shall comply with the following requirements:

3.4.2.2 Warranty Management

The contractor shall serve as the warranty manager by tracking the applicable government acceptance dates/receipt dates against the serial number of equipment or the lowest replaceable unit (LRU) of a system. As warranty manager, the contractor shall, unless otherwise directed, submit warranty data on Warranty Tracking Information (WTI) form and Source of Repair Instructions (SORI) form as specified on the Warranty Tracking and Administration for Serialized Items (CDRL A009). The contractor shall upload data to the WAWF Materiel Inspection and Receiving Report (or WAWF Reparable Receiving Report, if appropriate).

(a) If there is no compatible Government database to maintain and track warranty life spans for the GFP and/or CAP under task order, the contractor shall internally track items by task order, serial numbers, and the information shall be updated monthly to identify the time left on the original warranty. The contractor shall provide the government with a copy of the warranty information in an inventory tracking report (CDRL A009).

(b) When an item has failed, the contractor shall determine if the item is still under warranty. If the item is under warranty, the contractor shall obtain a Return for Maintenance Authorization (RMA) number and instructions on how to get the product repaired or replaced by the manufacturer or authorized distributor. A Warranty and Non-Warranty Failure Status Repair Report (CDRL A010) shall be submitted to the COR on all warranty and non-warranty actions taken during the preceding quarter and collected cumulatively. The contractor shall submit the report within fifteen (15) days of the completion of the quarter. The quarters will be based on the fiscal year beginning in the month of October.

3.5 LIFECYCLE LOGISTICS SUPPORT

The contractor shall assist in planning and conducting an Integrated Logistics Support (ILS) Program, which shall govern the management of the ILS effort. The Contractor shall apply engineering and analytical disciplines required to implement life cycle (acquisition) logistics as a multi-functional technical management discipline associated with the experimental development, design, development, test, production, fielding, sustainment, and improvement modifications of systems achieving the warfighter’s peacetime and wartime readiness requirements. The principal objective of lifecycle (acquisition) logistics is to ensure support considerations are an integral part of the system’s design requirements. The system shall be maintained through the life cycle, and the research and development facilities and infrastructure elements necessary to the design, development, initial fielding, and operation of the system are identified, developed, acquired, and supported.

3.5.1 Logistics Management Policy

The Contractor shall coordinate pending logistics actions with the Inventory Control Point (ICP). Any applicable issues that arise shall be consulted with ICP managers to ensure corrective actions are agreed upon by all parties. The Contractor shall notify ICP personnel of issues involving Material Support Date (MSD), Approved Parts List (APL) changes, delinquent or late parts deliveries, Y-coded items, or end of life of parts affecting any of the FSBS FVLF/LF shore antenna and transmitter systems. The Contractor shall provide NIWC Atlantic with the needed support to generate documentation or briefs to explain material actions, and coordinate responses.

3.5.1.1 Logistics Management Assessment

The Contractor shall populate the database with all pertinent logistics data for all impending hardware or software installations. Requirements for Integrated Logistics Support (ILS) Certification are contained in para 2.1, reference (g). ILS Certification information includes APL, Configuration Data Managers Database – Open Architecture (CDMD-OA), OPNAV_4790_CK information, Preventative / Planned Maintenance System (PMS), training, installation schedule, Software Allowance Parts List (XRIC), technical manuals and hazardous material (HAZMAT) information for the shore site or platform in question. The Contractor shall provide a status to the Logistics Lead concerning disposition of the effort. The Contractor shall provide acquisition related logistics function and establish and maintain Program Support Data and Material Support Date of the system.

3.5.2 Logistics Support

The Contractor shall prepare logistics documentation, package, prepare and stage materials for shipment, track all shipments to destination.

3.5.3 Material Shipping

The Contractor shall receive, ship, store, issue, and inventory assets for the Shore Submarine Communications systems projects. Receive includes performing physical receipt and inspection for quality, quantity and correctness. Shipping includes pulling assets from inventory, packaging material if required, preparing documentation, and taking material to shipping. Issuing includes filling out a material usage card or a hi-rise issue document and pulling material from location. The Contractor shall include the number of receipts, and the number of assets and equipment received in the Inventory Tracking Report (CDRL A009). The total number of receipts is not expected to exceed 1,900 during the anticipated period of performance.

3.5.3.1 Material Inventory

The Contractor shall conduct a tri-annual inventory as required and when directed by NIWC Atlantic. After the inventory, the Contractor shall compare it to the approved databases and reconcile any differences to ensure inventory accuracy and deliver a Material/Equipment Inventory Report (CDRL A009). The Contractor shall make recommendations on what assets can be excessed and present this data in their input to the Inventory Tracking Report (CDRL A009).