Attachment 1 - Draft SOW.pdf

STATEMENT OF WORK (SOW)

TACTICAL NETWORKS (TACNET) IN-SERVICE ENGINEERING AGENT (ISEA)

30 April 2026

1.0 SCOPE:

The effort provides support to execute In-Service Engineering Agent (ISEA) functions for Afloat and Ashore Tactical Networks and Command, Control, Communications, Computers and Intelligence (C4I) Systems as defined through the issuance of individual task orders for Naval Information Warfare Center (NIWC) Pacific.

1.1 INTRODUCTION AND BACKGROUND:

The SOW primarily covers ISEA support for Afloat and Ashore Tactical Networks (TACNET) for NIWC Pacific Tactical Networks Branch (Code 41250). The support will include, at a minimum, the following areas: Management, Engineering, Technical, Integrated Logistics Support (ILS), and Configuration Management. Specific tasking for all work will be generated by individual Task Orders (TOs). The effort requires the procurement and usage of Commercial- Off-the-Shelf (COTS) and Non-Developmental Items (NDI), including hardware and software for each of the programs.

TACNET ISEA is responsible for the sustainment of fielded systems through End-of-Life (EOL) replacement, system upgrades, follow-on, or interrelated systems, distance support, on-site repair, installations, and system analysis to ensure networks are performing within designed specifications. The TACNET ISEA also provides engineering reviews of documents in support of production and installation of Program-of-Record (POR) systems. The POR systems will consist of Automated Digital Network System (ADNS), Consolidated Afloat Networks Enterprise Service (CANES), Combined Enterprise Regional Information Exchange (CENTRIXS-M), Communications as a Service (CaaS), Integrated Shipboard Networking System (ISNS), Sensitive Compartmented Information Networks (SCI Networks), Agile Core Services (ACS), Software Defined Networks (SDN), Tactical Afloat Next Generation Networks (TNGN) and C4I interrelated systems and applications listed below.

• CND - Computer Network Defense

• GCCS-M - Global Command and Control System - Maritime

• DCGS-N - Distributed Command Ground System - Navy

• EPF - Expeditionary Fast Transport

• FSW – Flank Speed Wireless

• NXP - Naval Exchange Points

• JTT-M - Joint Tactical Terminal - Maritime

• JDMS - Joint Delivery Management Service

• JTDI - Joint Technical Data Integration

• NAVMACS - Navy Modular Automated Communications Subsystem

• NIAPS - Navy Information Application Product Suite

• NMCI - Navy and Marine Corps Intranet

• NTCSS - Naval Tactical Command Support System

• SCIP-IWF - Secured Communications Interoperability Protocol Inter-Working Function

• TAC VTC - Tactical Video Tele-Conferencing

• TBMCS - Theater Battle Management Core System Teleport

• TMIP-M - Theater Medical Information Program - Maritime

• TSS - Tactical Switching System

• TVS - Tactical Video Switch

• VDS - Video Display Systems

• VIXS - Video Information Exchange System

• VOIP - Voice Over IP

• WRBS - Wireless Reach Back System

• WLAN - Wireless Local Area Network

2.0 APPLICABLE DOCUMENTS:

• 5000, NAVWAR Configuration Management Policy Implementaiton

• ANSI/EIA-649 Configuration Management Standard

• COMUSFLTFORCOMINST 4790.3, Joint Fleet Maintenance Manual (JFMM)

• DODM 5200.01, Volume 1, DoD Information Security Program: Overview, Classification, And Declassification, Ch-2 28 July 2020

• DODM 5200.01, Volume 2, DoD Information Security Program: Marking Of Classified

Information, Ch-4 28 July 2020

• DODM 5200.01, Volume 3, DoD Information Security Program: Protection Of Classified

Information, Ch-3 28 July 2020

• DODI 5200.48, Controlled Unclassified Information (CUI), 6 March 2020

• DOD 5400.7-R, DOD Freedom of Information Act Program, dated September 1998

• DoDM 5200.02 – Procedures for the DoD Personnel Security Program (PSP) dtd Ch-1 29

October 2020

• DOD 5205.02-M, DOD Operations Security (OPSEC) Program, Ch-1 26 April 2018

• DoDM 5220.32, Volumes 1, National Industrial Security Program: Industrial Security

Procedures for Government Activities, 1 August 2018, Ch-2 10 December 2021

• DoDM 5220.32, Volumes 2, National Industrial Security Program: Procedures For

Government Activities Relating To Foreign Ownership, Control, Or Influence (FOCI), 17 April 2014, Ch-2 10 December 2021

• DoDI 5220.22, National Industrial Security Program (NISP) Mar 18 2011, Ch-2 September 24, 2020

• 32 CFR Part 117, National Industrial Security Program, Operating Manual (NISPOM), 24 February 2021

• DoDD 5205.02E, DoD Operations Security (OPSEC) Program, 20 June 2012, Ch-2 20 August 2020DoD 8570.01-M, DoD Information Assurance Workforce Improvement Program

• DoDI 5200.01, DoD Information Security Program and Protection of Sensitive Compartmented Information (SCI)

• GU-CFM-1000584 Naval Information Warfare Systems Command Configuration Management Guidebook

• National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298, 22 January 1988

• NAVWARINST 3084.1 System Operational Verification Test (SOVT) Preparation and execution Guide (SPEG) for Ship, Shore, and Submarine Installations

• NAVWARINST 3432.1 (Series), Operations Security Policy

• NNIAES-CDMP-0207 – Afloat Networks, Information Assurance, and Enterprise Services

Program Office Configuration Data PMW-160 Configuration Data Management Plan

(CDMP)

• OPNAV 4790.4D 3-M Manual, Ships’ Maintenance and Material Management (3-M) System Policy

• OPNAVINST 3432.1, DON Operations Security, 4 November 2011

• OPNAVINST F3300.53D (Series), Navy Antiterrorism Program, 2 August 2021

• SECNAVINST 5510.30C, Department of Navy Personnel Security Program, 24 January

• SECNAVINST 5510.36B, DON Information Security Program, 12 July 2019

• SECNAVINST 5239.20A, DON Cyberspace IT and Cybersecurity

• NAVWARINST 4790.1 Series – NAVWAR POLICY and Process for Afloat Casualty

Reports (CASREPS) and Incident Response Coordination

• Tactical Networks Program Office Life Cycle Configuration Management Plan (CMP)

• NIWCPACINST 5500.1C Security Manual, Ch-1 15 August 2023

3.0 REQUIREMENTS:

The contractor shall perform the following tasks in accordance with this SOW and each individual TO issued by NIWC Pacific.

3.1 MANAGEMENT SUPPORT:

3.1.1 Task Status Reports: The contractor shall provide monthly progress and status reports. This report shall include reconcilable expenditure reports that shall reflect the TO/DO original quote and final invoices.

3.1.2 Program Requirements: The contractor shall respond timely to task order requirements and shall implement and manage task orders and contract administration requirements of this contract. The contractor shall ensure that all task order work is performed in accordance with the applicable task order, the task order PWS, and the delivery schedule. The contractor Program Manager shall be on-site as required and coordinate with the tech code leads.

3.1.3 Management Reviews: The contractor shall provide management support and provide recommendations for program reviews. This shall include tracking outstanding actions. The contractor shall assist in the development of cost estimates, cost comparison analysis, project briefs, and whitepapers.

3.1.4 Transition Activities: At the conclusion of the period of performance, the contractor in place shall assist in the event of a transition to a new contractor. At a minimum this includes:

• Transferring knowledge and documentation

• Providing access to data and systems

• Supporting continuity of operations during the handover

3.1.5 Best Practices: The contractor shall support and consult for the adoption, implementation and sustainment of information technology and network best practices to include but not limited to: Development Operations Information Technology Infrastructure Library (DevOps ITIL), Agile Capability Maturity Model Integration (Agile CMMI), International Standards Operations, Documentation (ISO), AGILE Methodical Framework, and applicable documents listed in Section 2.0. Collect, analyze, and report metrics from ISEA functional areas in accordance with applicable task orders to support root cause reliability, quality assurance, and best practices.

3.1.6 General Housekeeping: The contractor shall abide by Government on-site policies for maintaining daily cleanliness of workspaces utilized by contractor personnel within a Government facility. Any non-conformances as determined by the onsite Government contract program manager shall be resolved within 2 weeks of identification. The Government will provide access to Government workspaces.

3.1.7 Safety: The contractor shall be cognizant and follow all safety regulations as set forth by the Occupational Safety and Health Administration (OSHA) and NIWC Pacific/Atlantic at the Government facility. This includes the use of Personal Protective Equipment (PPE) as required in designated areas. The contractor shall also establish and provide at minimum annual safety refresher training for their employees tailored to working in a Government facility (i.e.

Hazardous Materials (HAZMAT) handling procedures, use of PPE, safe use of tools, electrical safety, etc.). Additionally, the contractor shall ensure active licensing and certification of their employees assigned to operate warehouse handling and maintenance equipment (Forklift, Cranes, Lifting Slings, etc.). The contractor will be subject to unannounced Government safety inspections.

3.1.8 Quality Assurance (QA) Program: The contractor shall provide and maintain a quality/inspection system that adheres to the requirements imposed by this contract. The quality system shall be documented and contain procedures, plans, and all other documentation and data necessary to provide an efficient and effective quality system based on the contractor’s internal auditing system. The quality system shall be made available to the Government for review at both the program and worksite services level during predetermined visits. Existing quality assurance documents that meet the requirements listed in Section 2.0 of this SOW may continue to be used to administer and manage the QA Program. The contractor shall maintain a QA Alteration Installation Technical (AIT) workbook for each on-site visit in support of AIT Support. The Contractor shall also require that all subcontractors possess a quality assurance and control program commensurate with the services and supplies to be provided as determined by the Prime Contractor QA Program Coordinator or designated personnel. The Government reserves the right to witness any inspection, installation, demonstration, test, validation and verification. The Government reserves the right to disapprove the contractor’s and or subcontractor’s quality system or portions thereof when the quality system(s) fails to meet contractual requirements at either the program or worksite services level. The Government will evaluate the contractor’s performance under this contract in accordance with established quality assurance policies and processes as described in applicable documents listed in Section 2.0. The Government’s quality assurance oversight is not a substitute for quality control by the contractor.

3.2 ENGINEERING SUPPORT:

3.2.1 Technical Support: The contractor shall participate in technical reviews. The contractor shall assist in the development and/or revision of specification(s), Specification Change Notices (SCN), Ship Change Documents (SCD), Request for Changes (RFC), Engineering Change Notices (ECN), Fleet Readiness Certification Boards (FRCB), Field Changes (FCs) or modifications, technical repair standards. The contractor shall coordinate, attend and participate in on-site surveys, installations, technical assistance visits, schedule afloat inspections and test events, meetings and conferences, and exchange information with program managers, engineers and users for the primary systems listed in Section 1.1. The contractor shall provide global support to customers worldwide.

3.2.2 System Evaluations and Trade Study Support: The contractor shall perform system and technical evaluations, investigations, requirement reviews or trade studies to determine where changes might be recommended to correct deficiencies, achieve cost savings or improve operations and maintenance.

3.2.3 Design Analysis Support: The contractor shall provide plans, design analysis and recommendations for the primary systems listed in Section 1.1 and as newer systems are designed for replacement/upgrade.

3.2.4 Mockup Support: The contractor shall maintain and validate engineering mockup of systems listed in Section 1.1, and newer systems as they are designed for replacement/upgrade.

3.2.5 Engineering Information Bulletins/Article(s) Support: The contractor shall submit technical and engineering information for inclusion into Fleet Advisory Messages (FAMs); Fleet information Bulletins (FIBs), Mandatory Security Update (MSUs); and other Engineering Information Bulletin(s), and/or messages.

3.2.6 Engineering Sustainment Support: The contractor shall provide sustainment support in identifying, reviewing, assessing, and resolving deficiencies of systems listed in Section 1.1 throughout the system’s life cycle. The contractor shall assist in the development of engineering solutions and recommendations that support maintaining baseline configuration and capability and identifies opportunities for performance and capability enhancement for systems listed in Section 1.1. The solutions and recommendations shall include the measurement, identification and verification of a system’s technical and supportability deficiencies; associated root cause analyses; evaluation of the potential for deficiency correction; and the development of a range of corrective action options. The contractor shall assist in the development and implementation of selected corrective actions to include configuration or maintenance processes, and monitoring of key sustainment health metrics as defined by the Government representative. This includes root cause analysis of in-service problems, operational hazards, deficiency reports, parts obsolescence, and engineering reliability degradation analysis and reports. The above work requires that the contractors hold U.S. Government security clearance/access approvals commensurate with the highest level of information processed by the respective system. For example, if access to the SCI Networks or ADNS INC III SI/SCI enclaves is required, the contractor must be cleared at the SI/SCI level. The access requirements for CANES, SCI Networks and ADNS INC III systems on surface units and submarines are SI/TK/HCS/GG/ as specified by ONI and CNO (CNO N2/N6F21).

3.2.7 Network Engineering: The contractor shall provide engineering support in the form of technical insertions and solutions for primary systems listed in Section 1.1. This support shall include: development and review of 400 series documents (such as high level architecture, detailed design, requirements and configuration settings, Engineering Change Orders (ECOs), Bill of Materials (BoMs), operations guidelines, operations procedures, Enterprise Change Requests (ECRs), Enterprise Problem Reports (EPRs), and Service Request Forms (SRFs));

development and review design; technical reports; cost estimates for end of life software and hardware replacement and recommended engineering and design changes; correspondence including letters and messages to the Government sponsor as dictated within each contract task order; preparation and review of design proposals security documents; and verification of Installation Design Plans (IDPs), network architecture diagrams, and drawings to ensure specifications and design meet performance requirements.

3.2.8 Network Security Support: The contractor shall provide technical and engineering guidance for Information Assurance (IA) integration into tactical systems listed in Section 1.1 to include development, installation, enhancement and implementation of those systems. This includes network security support for mitigating network security vulnerabilities, network intrusion attempts, and virus activity, reporting and documentation, and patching of the tactical networks to mitigate vulnerabilities.

3.2.9 Proactive Sustainment Engineering Support: The contractor shall assist in the development, implementation, and sustainment of an automated report collection that supports afloat network predictive modeling. This includes identifying indicators that could lead to, or exacerbate, a network casualty that can be mitigated if proactively addressed; with potentially many more indicators that could be identified through the analysis of network performance and metrics. The engineering solutions and recommendations shall include the capturing of near-real-time afloat network configuration data, critical log files, and system-state metrics to deliver advanced critical troubleshooting information that assist in mitigating afloat network outages throughout the network life cycle. The contractor shall provide DevSecOps engineering support that addresses the requirement for proactive sustainment support, customer-focused security that supports monitoring of network health and anticipation of network degradation, and feedback loop on impacts/results of software releases for evaluation of system effects and performance.

3.2.10 System Operation and Verification Test (SOVT): The contractor shall develop, execute and maintain a SOVT Planning and Execution Guide (SPEG) Compliant SOVT package, perform the SOVT testing, and provide documentation to the Government of the results. The SOVT shall ensure satisfactory operation, availability and readiness after integration or installation. This includes development and execution of SOVT utilizing PEO C4I and TACNET

ISEA digitized Testing Procedures. The contractor shall employ the following SOVT strategy:

(1) system integration (in the laboratory environment) and equipment acceptance testing; (2) baseline testing to assure the proper operating condition and the system integrity of all existing interfaces prior to any pre-installation activity and prior to dismantling or removal of existing connections or equipment; (3) component in-place testing to verify that each component installed operates as demonstrated in the initial acceptance testing; (4) bypass testing after equipment/system installation to demonstrate that the shore is performing its designed function;

(5) test data interface exchange testing after installation of equipment/system to ensure that elemental test data can be exchanged between the components of the system; (6) initial integration testing with operational programs loaded and program functions validated; and (7) interoperability testing. The specific requirements for SOVT execution will be identified at the task order level. All portions of the SOVT shall be witnessed by the Government representative.

The SOVT package shall contain a list of hardware and software installed.

3.3 TECHNICAL SUPPORT:

3.3.1 Site Survey Support: The contractor shall provide site survey support globally to determine the physical space, equipment location, and installation details in support systems listed in Section 1.1.

3.3.2 TACNET ISEA Help Desk Analyst Support: The contractor shall provide 24x7 on-call and on-site Afloat Networks ISEA Help Desk (via telephone, chat or email) support. The contractor shall perform first-level diagnosis and troubleshooting support to end-users and customers for systems listed Section 1.1. The specific priorities will be identified at the task order level. The contractor assigned duties to the Technical Sustainment Support Help Desk shall follow the practices and standards in the current NIWC Pacific TACNET ISEA Technical Sustainment Support and C4I Help Desk Standard Operating Procedures (SOP), and other established processes. The contractor shall document all work performed in support of Help Desk Support in HELIX and other Program Executive Office (PEO) C4I approved remedy databases, systems and applications. The contractor shall provide message traffic support that includes message traffic review, routing, drafting, and releasing.

3.3.3 Technical Assistance Support: The contractor shall provide on-site and remote/virtual technical assistance, to include Tactical Networks Remote Access (TNRA), for the systems listed in Section 1.1. This includes support for Casualty Reports (CASREPS), on-site technical assistance and fleet schedule test events such as Inspection Survey Deployed Group System Integration Testing Technical System Readiness Assessment, Combat Systems, Command, Control, Communications and Computer Readiness Assessment and other on-site technical assist events worldwide. This assistance shall include the capability to diagnose and repair the complete network, end-to-end globally, leveraging chat, telephone, email, remote monitoring, and accessing ship’s network remotely from ashore. This assistance shall also include, at a minimum, the computer networks, Radio Frequency (RF), fiber optics, baseband, and all interconnection of the system network. The contractor shall document all work performed in support of Technical Assistance in the HELIX and other PEO C4I approved remedy databases, systems and application. The contractor shall support emergent fleet needs for Afloat and Ashore Tactical Networks system CASREP’s and significant incidents with C4I casualties. The contractor shall provide rapid response in support of CASREPs as required by the JFMM, COMUSFLTFORCOMINST 4790.3 series and NAVWARINST 4790.1 series and applicable Memorandums of Agreement (MOAs) between Naval Information Warfare Systems Command (NAVWAR), Regional Maintenance Centers (RMCs), and Fleet Type Commanders (TYCOMs).

The contractor shall implement processes to ensure effective tracking, reporting, data collection (using the HELIX and other PEO C4I approved remedy databases, systems and applications) and coordination of corrective actions to address and resolve C4I degradations and limitations that undermine the overall war fighting readiness of the Fleet.

3.3.4 Testing Support: The contractor shall investigate, design, code, implement and test enhancements to afloat networks software and hardware, emphasizing automation. Test support shall include development, quality assurance, production, and postproduction testing of hardware/software to determine operational readiness, compliance with requirements, security posture, and effectiveness. The contractor shall document, test, and analyze results. The contractor shall submit the results of all tests and inspections using the applicable guidelines and reporting procedures as indicated within each contract task order’s listed reference documents.

3.3.5 System Operability Testing (SOT): The contractor shall provide technical expertise to provide recommendations for coordinating, scheduling, and implementing C4I System Operability Testing. The contractor shall perform configuration validation for systems operation and gather current configurations. The contractor shall document and identify the deltas between the baseline configuration and current configuration.

3.3.6 Network System Validation and Configuration-Groom: The contractor shall provide technical expertise to perform the network validation and configuration check-out (Network Validation and Checkout (VC)), and system grooms for systems listed in Section 1.1. The Network VC and System Grooms shall validate, resolve and restore network deficiencies in accordance with baseline documentation. The contractor shall submit technical recommendations for system problems, assist with troubleshooting, and maintain configuration records.

3.3.7 Alteration Installation Technical (AIT) Support: The contractor shall provide software load, installation support and alterations for primary systems listed in Section 1.1, afloat and ashore.

This includes approved Engineering Changes, software pre-loads executed in C4I Pre- Installation Check Out (PITCO) facilities, shipboard alterations, and other approved upgrades for services as specified at the task order level for systems listed in Section 1.1. The installation support includes integration, testing, training, system activation, operational transition, and repair of installation disparities found during installation and SOVT, minor disassembly/removal and assembly/replacement of units or components to facilitate test requirements and/or inspection with target completion before ship’s end of availability. The contractor shall provide engineering, redlines, and technical feedback as necessary to enhance future system operations for systems listed in Section 1.1. The contractor shall utilize the approved installation documentation and configuration guides as indicated and referenced at the task order level. The contractor shall ensure satisfactory operation, availability and readiness after integration or installation. This includes execution of SOVT utilizing PEO C4I and TACNET ISEA digitized and automated work-flows Modern Digital Tactical Software for Testing (MDTST). The contractor shall utilize MDTST to support test development, test execution, data collection, test status, problem reporting, and test data validation. SOVT checks that cannot be completed during ship availability due to unavailability of shipboard and ashore dependencies shall be listed in SPEG SOVT Appendix B and a Plan of Action and Milestones (POAM) will be developed and tracked to completion. The SOVT shall not be considered complete until final signoff as witnessed by the respective Government representative. The contractor shall only use Government-approved portable storage/network devices In Accordance With (IAW) SECNAVINST 5239.20 in support of alterations services. The contractor shall conduct Systems Pre-installation Check Out (PICO) for primary systems listed in Section 1.1. The contractor shall support installations in accordance with the Surface Ship and Carrier modernization schedule in Navy Data Environment-Navy Modernization (NDE-NM)-SPIDER, PMW-160 and other sponsors fielding/installation plans.

3.3.8 Verification and Validation (V&V) Support: The contractor shall provide V&V support.

The contractor shall develop V&V test documentation (test plan procedures and reports or assessments) and qualified personnel to support testing in accordance with the specific requirements for each task order. Other support shall include providing a report of findings, identifying, recommending and correcting issues prior to and post-test execution, and/or validating test results.

3.3.9 Network User Pre-Migration and Migration Support: The contractor shall develop and maintain network user pre-migration data and data migration support plans and procedures. The contractor shall provide pre-integration and post-integration planning to include verifying integration documents to insure the latest redlines and changes are incorporated and up to date, implement strategies to reduce downtime, and ensure that lessons learned are captured and followed until documents can be updated. The procedures and processes shall support the execution of network user data migration between shipboard systems listed in Section 1.1 and temporary networks identified at the task order level. This includes shipboard user data, shared data, user email boxes data, workstations and approved software that will be identified at the task order level.

3.10 Tactical Networks Operations Management: The contractor shall have the capability to provide data metrics, resource management, schedule management, cost management, and analysis for systems listed in Section 1.1. Contractor personnel will support CB-ISEA service executions platforms to develop and maintain a measurable service performance framework across all functional area services to enable data analysis and produce proactive and predictive support capabilities. The contractor will develop integrated reporting tools, business logic and common service execution workflows to extract the key performance indicators. The contractor shall maintain resource capability/qualification management and monitoring system(s) to capture historical service performance, measure service quality, and maintain service resolution outcomes. The contractor will advise on resource capability and capacity management allocations through in-depth metrics analysis and data visualizations of the current workforce against future technical skills and demand requirements. The contractor will provide actionable resource performance information to the program to include trending length of support events (e.g. installation times, CASREP support frequency), skillset requirements, and actual resource performance/allocation against spend plan parameters. The solutions and recommendations shall include dashboards displaying trouble tickets and CASREPs trend analysis, past/present/future events scheduling and staffing, individual Subject Matter Expert (SME) capabilities and utilization, and data driven optimization to capture TACNET workflow optimization and processes. Data collected shall be able to project future SME demands, and the team’s ability to meet them, to highlight upcoming demand challenges and support requirements development.

3.4 Integrated Logistic Support (ILS):

3.4.1 ILS Planning and Life Cycle Support:

3.4.1.1 Integrated Logistics Support (ILS) Planning: The contractor shall develop and assist the Government in the validation of Type II equipment technical manuals, Type III system technical manuals, and technical manual supplements to support operations and maintenance at the Organizational Level and Depot Level. When required, the contractor shall procure commercial manuals for fleet and training support. Technical Manual (Military and Commercial) requirements and deficiencies shall be identified as part of the Logistics Support Analysis (LSA) supportability evaluation. The contractor shall develop, for Government review and approval, and support the validation of the Illustrated Parts Breakdowns and Maintenance Standards Books The contractor shall provide trained S1000D technical documentation to Subject Matter Experts.

The contractor shall prepare an Interactive Electronic Technical Publication (IETP) IAW DoD / DON / NAVWAR guidelines and Version 4.0.1 of the S1000D Specification for primary systems listed in Section 1.1. The contractor shall develop an expanded Technical Manual Organization Plan (TMOP) which includes the use of S1000D, and software applications such as Contenta (content management), XPP (publishing) and Live Content. The S1000D supports the management and distribution of technical manual documents for primary systems listed in Section 1.1. and all application documents as assigned by the ISEA/ILS Function Area Manager.

The contractor ILS report and documentation shall include the following ILS elements: (1) Technical Data; (2) Training and Training Support; (3) Maintenance; (4) Supply Support; (5) Configuration Management; (6) Support Equipment; (7) Manpower and Personnel; (8) Packaging, Handling, Storage and Transportation; (9) Computer Resources Support; (10) Facilities; and (11) Design Interface.

3.4.1.2 ILS Development and Sustainment: The contractor shall develop and sustain Program Support Data (PSD) sheets utilizing approved system BOMs, system equipment reliability data, and fleet criticality code assignments. The contractor shall update the Parts Reporting and Tracking System (PARTS) Database with the PSD sheet data and prepare data packages to support the annual BAM N412 PSD reviews.

3.4.1.3 ILS Technical Documentation Development and Support: The contractor shall develop, validate, and update to the User’s Logistics Support Summary (ULSS), Interactive Electronic Technical Manual (IETM) Software Operations Manuals (SOM) in accordance with Program-approved system baseline changes documented in SRF, ECP, ECR, ECO, and FC. The contractor shall draft and submit Technical Manual Identification Numbering System (TMINS) requests and provide required documentation for Advanced Technical Information Support (ATIS) Certification/Horizontal Integrated Data Environment (HIDE). The contractor shall update the SYSCOM Acquisition Integrated Logistic Online Repository (SAILOR) Website with an electronic copy of all new and newly revised technical documentation developed to include the

ULSS, IETM, SOM and technical guides within five (5) business days of Government approval.

The contractor shall conduct technical and quality reviews with technical and program stakeholders to ensure completeness and accuracy of the IETM/SOM. The contractor shall link system documentation and technical content to specific shore sites and/or platforms, removing, adding, and updating versions to reflect current configurations. The contractor shall provide support and technical guidance to all staging environments for integration and operational testing for SAILOR revisions; and shall attend technical meetings and conferences in support of the SAILOR website.

3.4.1.4 ILS Obsolescence Management and Documentation Support: The contractor shall provide obsolescence management and documentation support by forecasting for and managing spares of End of Life (EOL) items included in approved system BOMs. The contractor shall populate and update approved obsolescence management databases to monitor and proactively manage system obsolescence issues. The contractor shall provide documentation support, such as tracking, diminishing manufacturing sources and material shortages tracking for EOL tracking;

and notify the sustainment engineering Functional Manager (FM) of support obsolescence for TACNET support via a quarterly written report.

3.4.1.5 ILS Tracking Support: The Contactor shall update and document spare parts procurement requirements for primary systems listed in Section 1.1 and participate in technical and logistics reviews. The contractor shall update spares lists based on PSD sheet requirements, utilizing historical failure data, fielding plans, as well as range and depth analysis. The contractor shall analyze and recommend updates to reliability based sparing models, as well as provide written analysis and recommendations for failure trends.

3.4.1.6 ILS Engineering and Review: The contractor shall support ILS reviews of ECR, (SRF, and associated ILS checklists in support of the Configuration Management (CM) tool. The contractor shall provide logistics impacts assessments for all ECRs and SRFs submitted within 10 business days of request, to include Level of Repair Analysis (LORA) and level of effort impact estimates for required updates to logistics products. The contractor shall provide technical subject matter experts to participate in and support Physical Configuration Audits (PCA) to reconcile preliminary configurations with final configurations. The contractor shall provide requested ILS data and artifacts to support independent Government validation and verification in support of ILS products impacted by ECRs and SFRs. The contractor shall provide technical analyses and recommendations to support the Government’s review of third-party vendor ILS deliverables.

3.4.1.7 ILS Data Management: The contractor shall administer and maintain the Government’s data management system, including providing user training as required IAW each contract task order. The contractor shall ensure data integrity by complying with all Government directives concerning the dissemination of information.

3.4.1.8 ILS Package Delivery: The contractor shall collect, organize, copy to appropriate media, package and deliver ILS packages to the Government. The contractor shall obtain final delivery confirmation and acknowledgement of receipt from the Government, as well as update Naval

Networks website with the completed delivery signature data within two (2) business days of receipt.

3.4.1.9 Hardware Planned Maintenance System (PMS) Development/Support: The contractor shall assist in the development of Hardware PMS documentation to support maintenance requirements, analyses of the system/equipment, and preventive maintenance in accordance with the Reliability Centered Maintenance (RCM) Process. The contractor shall maintain records of the PMS documentation process. Existing RCM data, and other related data shall be obtained from existing databases to preclude any duplication of development efforts. The contractor shall analyze all assigned Technical Feedback Reports (TFBRs) and provide a written technical recommendation for resolution to the Government within 15 business days of assignment.

Reviews will include a written report validating the end users’ feedback received via TFBR’s, HELIX and other PEO C4I approved remedy databases, systems and applications. The contractor shall validate the information/feedback contained in the TFBR’s, PMSMIS, and REMEDY, and provide recommendations as necessary for technical resolution.

3.4.1.10 Network Planned Maintenance System (N-PMS) Development: The contractor shall provide assistance in the development of Networks Administrative Preventative Maintenance to include the review of technical feedback reports from end users. Reviews shall include a written report validating the end users’ feedback or provide logical reasoning as to why the feedback is not valid. The contractor shall provide assistance in the development of the Network PMS (N- PMS) in accordance with Administrative Networks Software Procedures to the Navy’s Planned Maintenance System (PMS) Letter Date 8 DEC 2009, Ser 04RM/4258.

3.4.1.11 Supply Support: The contractor shall develop specific Provisioning Technical Documentation (PTD). Provisioning information shall be developed and delivered using the Interactive Computer-Aided Provisioning System (ICAPS) or other Government-approved Automated Data Processing (ADP) capability. The contractor shall submit Design Change Notices (DCN) to identify changes to Provisioning Technical Documentation (PTD).

Provisioning screening and technical information coding (including replacement factors; mission essentiality; and source, maintenance and recoverability codes) shall be provided for each item listed on the Provisioning Parts List (PPL). The contractor shall identify Original Equipment Manufacturer (OEM) part data and the cage code as well as the up-to-date unit cost. The contractor shall develop, compute and document PSD on forms NAVSUP 1390 Hull, Mechanical, & Electrical Support Cost (HSC End Item Program Support Data), and NAVSUP 1390/1 (Equipment Installation Data, and NAVSUP 1392 (HSC Secondary Item Funding Requirements) using the Navy's authorized ADP capability called PARTS. The contractor shall request/confirm Government nomenclature; request assignment of serial numbers; request assignment of national stock numbers; and provide identification plates.

3.4.1.12 Logistic Support Analysis (LSA): The contractor shall perform LSA supportability analyses of systems/equipment. The LSA process is iterative and may be continued through the life cycle of the systems/equipment to address engineering changes. These analyses shall include at a minimum: (1) identification of hardware or software for which the Government will not or may not receive full rights due to constraints imposed by regulations or laws limiting the information that must be furnished because of proprietary or other source control considerations;

(2) development of supportability, cost, and readiness objectives including risk assessment; and

(3) development of supportability and supportability related design constraints for inclusion in specification(s) and other requirement documents.

3.4.1.13 Warehouse and Inventory Control Support: The contractor shall establish and maintain a Government site warehousing and inventory control process using Government-approved computer-based application software programs for the systems listed in Section 1.1. This control process shall include Installation and Checkout (INCO) and On-Board Repair Parts (OBRP) program material and equipment. Upon Government request, the contractor shall provide storage space and an inventory management system to warehouse INCO and OBRP program material and equipment. The contractor shall maintain inventory records keeping of INCO’s and OBRP’s material segregated by their respective category and report to the Government representative ILS Functional Area Manager in accordance with NAWAR Instruction 4410.12 (Management of Operating Materials and Supplies (OM&S), Government Furnished Property (GFP), Contractor Acquired Property (CAP), Property, Plant and Equipment (PP&E), and Inventory.

The contractor shall ensure all inventory issued to fill fleet requisitions has been properly tested and meets all operational standards before it is used.

3.4.2 Training Support:

3.4.2.1 Formal Training: The contractor shall develop formal training for both the organizational level and maintenance level. All course material required for instruction (i.e. curriculum, training audiovisual aids, outlines and guides) for any course shall be developed and validated by the contractor. At a minimum, the course content shall provide the following: uses; interfaces; theory of operation; synopsis of the equipment and equipment checkout; startup procedures; operation and shutdown safety procedures; procedures for alignment, inspections, and maintenance;

assembly/disassembly; troubleshooting; use of tools and test equipment; and replacement of parts and repair in accordance with the maintenance concept of the equipment/system.

Developed courses shall provide recommended pre-requisite training and experience with the equipment/system, to include preventive and corrective maintenance procedures. As will be specified at the task order level, training shall be conducted ashore and afloat, defining the number of sessions, duration, locations, and maximum number of students per class.

3.4.2.2 On-the-Job Training (OJT) and Handbook Development: The contractor shall develop and conduct a 4-hour OJT session focused on the deltas between existing and upgraded system configurations for system/equipment upon completion of Afloat Networks system or equipment upgrades. The training shall provide personnel with a summary of what the formal training as discussed in Section 3.4.2.1 above.

3.4.2.3 Configuration Management (CM) Support: The contractor shall support the Governments’ CM program to include the development, implementation and maintenance of CMP; Configuration Identification (CI); Configuration Control, Configuration Status Accounting; Configuration Verification and Audit; and Data Management. Contractor shall assist in administering TACNET ISEA COTS Product Lifecycle Management (PLM) web-based solution CMPRO secure database.

3.4.2.4 Configuration Management Planning: The contractor shall develop, implement and maintain a CMP which complies with ANSI/EIA-649 and NAVWAR CM Policies. The CMP shall include processes for CI, Configuration Control, Configuration Status Accounting, Configuration Verification and Audit, and Data Management.

3.4.2.5 Configuration Management Identification: The contractor shall develop, implement and sustain processes that verify and sustain a complete and accurate configuration identification of CI/Computer Software Configuration Item (CSCI.) The contractor shall establish and maintain Government approved functional, allocated, product and as-installed baselines for equipment/systems. The contractor shall maintain baseline documents that include specifications, drawings and associated lists, manufacturing process and procedures, test and inspection plans/procedures, quality assurance provisions, inspection and test equipment requirements, packaging requirements, tooling/jigs/fixture requirements, software documentation, technical manuals, maintenance and supply support documentation, and training/training support documentation. The contractor shall ensure only approved changes via an EPR, Service Request Deviation Form (SRD), or deviation request for waivers are reflected in the baseline documents listed above.

3.4.2.6 Configuration Control: The contractor shall develop, implement and sustain configuration control processes that regulate life cycle cost and allow optimum design and development latitude with the appropriate degree, and depth of configuration change control procedures during the life cycle of the System/CI. The contractor shall provide efficient processing and implementation of configuration changes that maintain or enhance operational readiness, supportability, interchangeability and operability. The contractor shall ensure complete, accurate and timely changes to configuration documentation maintained under appropriate configuration control authority. The contractor shall eliminate unnecessary change proliferation.

3.4.2.7 Configuration Control Board (CCB): The contractor shall support and participate in the Government’s Configuration Control Board (CCB), Platform Technical Review Board (PTRB) and Change Implementation Board (CIB) processes and shall submit any proposed changes using the Government’s Configuration Management System and associated tools.

3.4.2.8 Configuration Status Accounting (CSA): The contractor shall provide configuration status accounting, which shall delineate the status of changes from the baseline; the status of proposed changes; and the status of implementation of approved changes. The contractor shall use the Government’s configuration management system for configuration status accounting reporting.

3.4.2.9 Configuration Verifications and Audits: The contractor shall support and participate in Functional Configuration Audits (FCA) and Physical Configuration Audits (PCA). The contractor shall also support and participate in “Self-Assessment Audits” whose function is to verify that approved configuration management process and procedures are being complied with.

The contractor shall use the Government’s configuration management system and associated tools for reporting discrepancies.

4.0 DATA DELIVERABLES:

Data deliverables shall be reviewed IAW “DON Policy on Digital Product/Technical Data, ASN RD&A Memo dated 23 OCT 2004.” Technical data and computer software delivery requirements will be specified through use of a Contract Data Requirements List, DD Form 1423 at the individual delivery/task order level.

5.0 SECURITY:

The work performed by the contractor will include access to unclassified and up to Top Secret/Sensitive Compartmented Information (TS/SCI) data, information, and spaces. The contractor will be required to provide individuals with security clearances at the appropriate classification levels, as specified in individual task orders. The contractor will be required to attend meetings classified up to Top Secret/SCI. The contractor will require access to Communications Security (COMSEC), the Secure Internet Protocol Router Network (SIPRNet) and some contractor personnel will require access to the Joint Worldwide Intelligence Communications System (JWICS), National Security Agency Network (NSANET) and CANES Although there is no requirement for the contractor to access NATO on this contract per Naval Intelligence Security Policy Directive 17-008 those contractors that have SCI access and those cleared SCI with JWICS or SIPRnet accounts shall be North Atlantic Treaty Organization (NATO) read-on and complete the derivative classification training prior to being granted access to JWICS/SIPRnet; training is provided by the facility security officer. Specific requirements provided in the Department of Defense Contract Security Classification Specification, DD Form 254.

Contractors performing tasks at the TS or below level without SCI access shall only receive the North Atlantic Treaty Organization (NATO) awareness brief and complete the derivative classification training prior to being granted access to SIPRnet; training is provided by the facility security officer. Specific requirements provided in the Department of Defense Contract Security Classification Specification, DD Form 254.

Contractor personnel shall be required to perform duties that require a background security investigation. The type of investigation required will be determined by the position risk level designation for all duties, functions, and/or tasks performed.

Contractor personnel assigned to this effort who require access to SCI data and spaces must possess a current SSBI with ICD 704 eligibility (which replaced DCID 6/4 eligibility).

Some of the work performed by the contractor will be located in Sensitive Compartmented Information (SCI) spaces, and attendance of SCI level meetings and possibly exposure to SCI data will be required. All deliverables will be unclassified, but access to SCI spaces is required to work on SCI Networks and SCI CANES. The SCI cleared contractors shall interface with the COR to enter into SCI discussions for system problems and testing events related to Top/Secret (TS)/Sensitive Compartmented Information Network while onboard ships providing technical assistance. The access requirement for SCI Networks, ADNS INC III and SCI CANES systems on surface units and submarines shall be indoctrinated in SI/TK/HCS/GG compartments as specified by ONI and CNO (CNO N2/N6F21). Contractors should be U.S. citizens for systems requiring US only access. Only US Citizens are authorized access to SCI Networks, ADNS INC

III SI/SCI enclave and SCI CANES. The contractor shall be Information Assurance (IA) trained and certified in compliance with DoD 8570.01-M and DIA Directive (DIAD) 8500.400 requirements, and provide a copy of required certifications for designated positions. Contractors shall have a working knowledge of operational system functions, security policies, technical security safeguards, and operational security measures. In addition to meeting the above stated requirements, the following guidelines, defined by ONI/Naval Intelligence Information

The National Industrial Security Program Operating…