PWS N66001-16-R-0118 DRAFT.doc

N66001-16-R-0118

PERFORMANCE WORK STATEMENT (PWS)

TACTICAL NETWORKS IN-SERVICE ENGINEERING AGENT (ISEA)

08 March 2016

1.0 SCOPE:

The effort provides support to execute In-Service Engineering Agent (ISEA) functions for Afloat and Ashore Tactical Networks and C4I Systems as defined through the issuance of individual task orders for Space and Naval Warfare Systems Center Pacific (SSC) (Pacific).

1.1 INTRODUCTION AND BACKGROUND:

The Performance Work Statement (PWS) covers primarily ISEA support for Afloat and Ashore Tactical Networks (TACNET) for Space and Naval Warfare Systems Center, Pacific’s (SSC PAC) 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 Delivery/Task Orders (DO/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 system, distant support, on-site repair, installations, and system analysis to ensure networks are performing within designed specifications. The TACNET ISEA also provides engineering review 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), Integrated Shipboard Networking System (ISNS), Sensitive Compartmented Information Networks (SCI Networks) and C4I interrelated systems and applications listed below.

CND - Computer Network Defense

CSRR - GCCS-M - Global Command and Control System- Maritime DCGS-N Distributed Command Ground System - Navy

EPF- Expeditionary Fast Transport JHSV - Joint High Speed Vessel

JTT-M - Joint Tactical Terminal- Maritime

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

SubLAN - Submarine Local Area Net SWAN - Shipboard Wide Area Network

SHIP PLATFORM Networks

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

VIXS- Video Information Exchange System

Voice over IP

WRBS-Wireless Reach Back System

WLAN – Wireless Local Area Network 2.0

APPLICABLE DOCUMENTS:

2.1

OPTIONAL MILITARY SPECIFICATIONS:

MIL-D-23140D Drawings, Installation Control, for Electronic Equipment

MIL-DTL-17H

Cables, Radio Frequency, Flexible and Semi rigid, General Specification MIL-DTL-15024F Plate, Tags and Bands for Identification of Equipment, General Specification MIL-DTL-24640B Cables, Light Weight, Electric, Low Smoke for Shipboard Use

MIL-DTL-31000C Technical Data Packages, Inspection System Requirements

MIL-DTL-24784B Manuals, Technical: General Acquisition and Development Requirements

MIL-E-17555H Electronic and Electrical Equipment, Accessories, and Provisioned Items (Repair Parts): Packaging of

MIL-M-85337A Manuals, Technical: Quality Assurance Program Requirements for MIL-STD-3034 Reliability-Centered Maintenance (RCM) Process

Admitting Networks Software Procedures to the Navy’s Planned Maintenance System (PMS) Letter Date 8 Dec 2009 Ser 04RM/4258

MIL-P-24534A Planned Maintenance System Development of Maintenance Requirement Cards, Maintenance Index Pages and Associated Documentation

MIL-PRF-16552F Filters, Air Environmental Control System, Cleanable, Impingement (High Velocity Type)

MIL-PRF-29612 Training Data Products

MIL-PRF-49506 Logistics Management Information Quality Assurance Surveillance Plan – FAR Section 46.401 DFARS Subpart 237.1-Service Contract – General (DFARS 237.172) 2.2

OPTIONAL MILITARY STANDARDS:

MIL-STD-129P Standard Practice for Military Marking

MIL-STD-130M Identification Marking of U.S. Military Property

IL-STD-202G Test Method Standard Electronic and Electrical Component Parts

MIL-STD-461E Requirements for the Control of Electromagnetic Interference Emission and Susceptibility MIL-STD-789C Contractor Technical Information Coding of Replenishment Parts MIL-STD-810F Environmental Test Methods and Engineering Guidelines

MIL-STD-882D Standard Practice for System Safety

MIL-STD-883F Test Method Standard Microcircuits

MIL-STD-961E Department of Defense Standard Practice Defense Specifications

MIL-STD-1472F Human Engineering MIL-STD-1474D Department of Defense Design Criteria Standard- Noise Limits MIL-STD-1686C Electrostatic Discharge Control Program for Protection of

Electrical and Electronic Parts, Assemblies, and Equipment

MIL-STD-1840C Automated Interchange of Technical Information

MIL-STD-2073-1D Standard Practice for Military Packaging

MIL-STD-2110 Restoration, Overhaul, and Repair of Electronic Equipment

Defense System Software Quality Program

MIL-STD-38784 Standard Practice for Manuals, Technical: General Style and

Format Requirements

2.3

OPTIONAL MILITARY HANDBOOKS:

MIL-HDBK-61A Configuration Management Guide

MIL-HDBK-217F Reliability Prediction of Electronic Equipment

MIL-HDBK-237D Electromagnetic Environmental Effects and Spectrum Supportability guidance for the Acquisition Process

MIL-HDBK-347 Mission Critical Computer Resources Software Support

MIL-HDBK-419A Grounding and Shielding for Electronic Equipment and Facilities Basic Theory

MIL-HDBK-454A General Guidelines for Electronic Equipment

MIL-HDBK-470A Designing and Developing Maintainable Products and Systems Volume I & II, Appendix C: Design Guidelines

MIL-HDBK-502 Acquisition Logistics

MIL-HDBK-781A Reliability Test Methods, Plans, and Environments for Engineering, Development Qualification, and Production

MIL-HDBK-831 Preparation of Test Reports

MIL-HDBK-1221 Evaluation of Commercial Off the Shelf (COTS) Manuals

MIL-HDBK-2036 Preparation of Electronic Equipment Specifications

MIL-HDBK-2097A Acquisition of Support Equipment and Associated Integrated Logistics Support

MIL-HDBK 2155 Handbook for Failure Reporting, Analysis and Corrective Action System

MIL-HDBK 2165 Testability Handbook for Systems and Equipment

MIL-HDBK-29612A/4A Glossary for Training

MIL-HDBK-46855A Human Engineering Guidelines for Military Systems, Equipment and Facilities

2.4

OTHER DOCUMENTS:

AMERICAN SOCIETY OF MECHANICAL ENGINEERS (ASME) ASME Y14.100M Engineering Drawing Practices AMERICAN SOCIETY FOR TESTING AND MATERIALS (ASTM) ASTM D 3951 Packaging, Commercial American National Standards Institute (ANSI)

ANSI Quality Systems- Model for Quality Assurance in Design/Development, Production, Installation, and Servicing

ANSI/ASQC Quality and Quality Systems Elements, Guidelines Q9004-1, Sq-4 1987 ANSI/EIA-690 National Consensus Standard for Configuration Management ANSI X3.131 Small Computer System Interface (SCSI), 1986

Electronic Industries Association (EIA) EIA 310-D Racks, Panels, and Associated Equipment

Institute of Electrical and Electronic Engineers (IEEE) IEEE 100 Standard Dictionary of Electrical and Electronic Terms

IEEE 200 Reference Designations for Electrical and Electronic Parts and Equipment ANSI Y32.16, DoD adopted

IEEE 260.1 IEEE Standard Letter Symbols for Units Measurement (SI Units, Customary Inch-Pound Units, and Certain Other Units)

IEEE 280 Standard Letter Symbols for Quantities Used in Electrical Science and

Electrical Engineering (DoD adopted)

IEEE 315A Graphic Symbols for Electrical and Electronics Diagrams (Including

Reference Designation Class Designation Letters) (ANSI Y32.2)

2.5

OTHER NAVY DOCUMENTS

8570.01-M DoD Information Assurance Workforce Improvement Program

Automated Digital Network System (ADNS) Obsolescence Management Process (OMP) dated 12/10/2012 Version 0.09

COMFLTFORCOMINST 4990.3 Commander Joint Fleet Maintenance Manual

COMUSFLTFORCOMINST 4790.3 Joint Fleet Maintenance Manual (JFMM)

DOD 5205.02 (Series), DOD Operations Security (OPSEC) Program

DOD 5220.22-M (Series), National Industrial Security Program Operating Manual (NISPOM)

Memorandum of Agreement between Commander Navy Regional Maintenance

Centers and Deputy Commander, Space and Naval Warfare Systems Command, Fleet Readiness Directorate, Subject: (MOA) for Support of C4I Fleet Technical

Assistance (FTA) Requirements

National Security Decision Directive 298 (Series), National Operations Security Program (NSDD) 298

NAVICP 4441.170A COSAL Use and Maintenance Handbook

NAVSEA 9090-1600 PTD Requirements for Development TS Items Procure as Government Furnished Equipment NAVSEA Program Support Data (PSD) Information Guide and Automated

Reporting and Tracking System (PARTS) Users Manual NAVSEA SL720-AA-MAN-010 Fleet Modernization Program (FMP) Management and Operations Manual NAVSEA Standard Items, FY-15 NAVSEA Technical Specification 9090-700 CDMD-OA

NAVSEA Technical Specification 9090-310G Ships Alteration by AIT NAVSEA T8501-AF-PLN-010 Engineering and Operations Training Material Management Plan NAVSUP P-437 MILSTRIP/MILSTRAP Manual NAVSUP P-485 Supply Support

NAVSUP P-545 DLR Manual Depot Level Repairable Requisition Turn-In and Carcass Tracking Guide

NNIAES-CDMP-0207 – Afloat Networks, Information Assurance, and Enterprise Services Program Office Configuration Data PMW-160 Configuration Data Management Plan (CDMP) OPNAVINST F3300.53C (Series), Navy Antiterrorism Program OPNAVINST 3432.1 (Series), DON Operations Security

OPNAV 4790.4D 3-M Manual, Ships’ Maintenance and Material Management

(3-M) System Policy

QASP – Quality Assurance Surveillance Plan – FAR Section 46.401 DFARS Subpart 237.1 – Service Contract General (DFARS 237.172)

SAILOR 2.1 2.0 Project Charter, dated 10 March 2010

SECNAVM-5000.2 DON Acquisition and Capabilities Guidebook (2May 2012)

SECNAVINST 5100.10H Safety Mishap Prevention Occupational Health and Fire

SD-2 Buying NDI - Defense Standardization Program DoD Acquisition Buying Commercial Item and Non-Developmental Items SD-5 Locating Off the Shelf Items

SPAWARINST 3432.1 (Series), Operations Security Policy

SPAWARINST 3084.1 System Operational Verification Test (SOVT) Preparation and Execution Guide (SPEG) for Ship, Shore, and Submarine Installations

SPAWARINST 4130.3 SPAWAR Life Cycle Configuration Management Policy, 28MAR2013

SPAWARINST 4160.38 SPAWAR PEO C4I Policy, Procedures and Responsibilities for Technical Manual Operations and Product/Technical Data Lifecycle Support

SPAWARINST 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

SPAWARINST 4440.2A Policy for Establishment of Fleet Support Teams (FST)

SPAWARINST 4790.1 Series - SPAWAR POLICY and Process for

Afloat Casualty Reports (CASREPS) and Incident Response Coordination

SPAWARINST 4130.3 SPAWAR Life Cycle Configuration Management Policy 28MAR2013

SPAWAR INST 4160.3B SPAWAR PEO C4I POLICY, Procedures and Responsibilities for Technical Manual Operations and Product/Technical Data Lifecycle Support

SPAWARINST 5400.4B (ISEA) Designation and Certification Policy

SPAWAR Business Framework (SBF) Global Work Breakdown Structure (GWBS)/Enterprise Cost Management Framework (ECMF) Function Tactical Networks User’s Logistic Support Summary (ULSS) as listed per each system Technical Manual Identification Numbering System (TMINS) 3.0

REQUIREMENTS:

The contractor shall perform the following tasks in accordance with this PWS and each individual DO/TOs issued by SSC 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 shall provide an on-site person who shall be responsible for the performance of this contract. The identified person shall be a Program Manager (PM) with full authority to make decisions, and designated in writing to the COR Support Manager (CSM) at the start of the contract and as changes occur.

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 Intranet/Web Page: The contractor shall establish an Intranet Web page to facilitate real time procurement actions and status tracking with a minimum of the following: (1) Basic contract and contract modifications, (2) Task Statements of Work, (3) Task Contract Data Requirements List (CDRL) DD Form 1423-1, (4) Task Status Reports, (5) Task Electronic Deliverables. The contractor shall maintain a secure access to this Web page and provide 128-bit encrypted, password-protected or PKI aware access to designated government representatives.

3.1.5 Wide Area Work Flow WAWF/Invoices: The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided. The contractor shall go to the WAWF web address https://doncmra.nmci.navy.mil and completely fill in required data fields.

3.1.6 Transition Activities: At the conclusion of any performance period, including option periods or extensions, the services provided under this PWS may be awarded to another contractor. The contractor in place shall be required to assist in the transition.

3.1.7 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: Information Technology Infrastructure Library (ITIL), Capability Maturity Model Integration (CMMI), International Standards Operations, Documentation (ISO) and applicable documents listed in

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.8 Quality Assurance Surveillance Plan (QASP): The documented QASP shall be used to ensure that the end product/service of each task conforms to contract requirements whether produced by the Contractor or provided by approved subcontractors or vendors. The QASP shall provide the overall performance objectives to reflect (1) Quality of Product/Services, (2) Schedule, (3) Cost Control, (4) Business Relations, and (5) Management of Key Personnel. All services shall be performed according to the documented quality assurance surveillance plan and directly monitored by the COR.

3.1.9 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. The contractor shall perform monthly inspections to ensure cleanliness of workspaces. Any non-conformances as determined by the on-site government contract program manager shall be resolved within 2 weeks of identification. The Government will provide access to Government workspaces, but any special equipment requests (such as ergonomic chairs) shall be the responsibility of the contractor to provide.

3.1.10 Safety: The contractor shall be cognizant and follow all safety regulations as set forth by OSHA and SSC-PAC/LANT 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. 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.11 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 contract may continue to be used to administer and manage the QA Program. The contractor shall maintain a QA AIT workbook for each on-site visit in support if 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 Contractors 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 section 2.0. The Government’s quality assurance oversight is not a substitute for quality control by the contractor.

3.1.12 Quality Control: Unless otherwise directed, the Contractor is responsible for all quality control inspections necessary in the performance of the various tasks as assigned and identified by the respective Work Breakdown Structure (WBS), POA&M or procedural quality system document. The Government reserves the right to perform any inspection deemed necessary to assure that the Contractor provides services, documents, and material that meet the prescribed requirements. The Government also reserves the right to reject any or all services, documents, and material when nonconformance is determined using reference documents listed section 2.0.

3.1.13 Contractor Manpower Reporting Application (CMRA): The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Space and Naval Warfare Systems Command (SPAWAR) via a secure data collection site. The contractor is required to completely fill in all required data fields using the following web address https://doncmra.nmci.navy.mil.

Reporting inputs (from contractors) will be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. Contractors may direct questions to the help desk, linked at https://doncmra.nmci.navy.mil.”

For purposes of CMRA reporting, the Federal Supply Code /Product Service Code applicable to the contract/order is J059.

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 evaluations, 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 system 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); 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 contractor shall perform the role of Trusted Agents for the Government to full-fill requirements established by the Office of Naval Intelligence (ONI) and the Chief of Naval Operation (CNO) N2/N62. 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/HSL/EL 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 to supported systems 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 Order (ECO), Bill of Materials (BoM), Operations Guidelines, Operations Procedures, Enterprise Change Request (ECR), Enterprise Problem Report (EPR), and Service Request Form (SRF)]; 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 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, and patching of the tactical networks to mitigate vulnerabilities. The contractor shall provide IA technical support to the System Security Authorization Agreement (SSAA), Trusted Facility Manual (TFM), Security Features User Guide (SFUG), Security Requirement Traceability Matrix, (SRTM), Trusted Facility Manual (TFM), and Security Features User Guide (SFUG). Conduct IA technical integration and support to strategic planning and analysis that will ensure appropriate technologies, desired functionality, and required implementation activities are developed, monitored, and initiated throughout a network-centric environment. The contractor shall perform the role of Trusted Agents for the Government to full-fill the requirements established by the Office of Naval Intelligence (ONI) and the Chief of Naval Operation (CNO) N2/N62. 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. If access to the CANES, SCI Networks or ADNS INC III SI/SCI enclaves is required, the contractor must be cleared to 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/HSL/EL as specified by ONI and CNO (CNO N2/N6F21).

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 C4I Help Desk Support: The contractor shall provide 24x7 on-call C4I Help Desk (via telephone, chat or e-mail) support. The contractor shall preform 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 Fleet Services Help Desk shall follow the practices and standards in the current SSC Pacific TACNET Help Desk SOP 41260 and other established processes. The Subject Matter Experts assigned duties in Fleet Service shall utilize the Approved Tactical Networks ISEA Tier II/III SOP. 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 technical assistance for the systems listed in section 1.1. This includes support for CASREPs, on-site technical assistance and fleet schedule test events (INSURV, DGSIT, TSRA, C5RA, and other on-site technical assist events) worldwide. This assistance shall include the capability to diagnose and repair the complete network, end-to-end. This assistance shall also include, at a minimum, the computer networks, 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 Remedy Database. 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 Joint Fleet Maintenance Manual (JFMM), COMUSFLTFORCOMINST 4790.3 series and SPAWARINST 4790.1 series and applicable Memorandums of Agreement (MOAs) with between SPAWAR, Regional Maintenance Centers (RMCs), and Fleet Type Commanders (TYCOMs). The contractor shall implement processes to ensure effective tracking, reporting, data collection (using the Remedy Database) 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 develop test procedures, perform tests, and provide documentation to the government of the results. The test procedures shall describe the proposed tests and inspections in sufficient depth to prove that equipment/system are thoroughly evaluated for conformance to the requirements of equipment/system specification(s). The testing shall consider partitioning to enhance fault isolation, initialization of circuitry under test control, module interface for test access and control, circuit controllability and examination, test point placements, and Built in Test (BIT) fault isolation approach. 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 listed reference documents. The contractor shall perform the required calibration of any test equipment prior to commencing any tests.

3.3.5 System Operability Testing (SOT): The contractor shall provide technical expertise to provide recommendations for coordinating, scheduling, and implementing of 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 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. 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.7 Alteration Installation Technical (AIT) Support: The contractor shall provide installation support and alterations for primary systems listed in section 1.1. The installation support includes integration, testing, training, system activation, operational transition, and repair of installation discrepancies found during installation and SOVT, minor disassembly/removal and assembly/replacement of units or components to facilitate test requirements and/or inspection. 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).

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 procedure 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 posttest 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 procedures and process shall support the execution of network user data migration between shipboard systems listed Section 1.1 and temporary network 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.4

ILS SUPPORT:

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 LSA supportability evaluation. The contractor shall develop and assist the Government in the validation of the Illustrated Parts Breakdowns and Maintenance Standards Books. The contractor shall provide trained S1000D technical documentation Subject Matter Experts. The contractor shall prepare an AN/USQ-208 Interactive Electronic Technical Publication (IETP) In Accordance With (IAW) DoD / DON / SPAWAR guidelines and Version 4.0.1 of the S1000D Specification. 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 the CANES AN/USQ-208 Variants), and all application documents as assigned by the ISEA/ILS Function Area Manager for CANES. The contractor ILS report and documentation as required per CDRL A016 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 Bill of Materials (BOM), 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 support the annual BAM N412 PSD reviews.

3.4.1.3 ILS Technical Documentation Development and Support: The contractor shall develop, support, 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 support the development of Technical Manual Identification Numbering System (TMINS) requests, and Advanced Technical Information Support (ATIS) Certification /Horizontal Integrated Data Environment (HIDE). The contractor shall update the SPAWAR Acquisition Integrated Logistic Online Repository (SAILOR) Website with an electronic copy of the ULSS. The contractor shall conduct technical and quality reviews with technical and program stakeholders to ensure completeness and accuracy of the IETM/SOM.

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.

3.4.1.5 ILS Tracking Support: The Contactor shall update and document spare parts procurement requirements for primary systems listed in para 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 solutions for failure trends.

3.4.1.6 ILS Engineering and Review: The contractor shall support ILS reviews of Enterprise Change Requests (ECR), Service Request Forms (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, to include Level of Repair Analysis (LORA) and level of effort impact estimates for required updates to Logistics products. The contractor shall support Physical Configuration Audits (PCA) to reconcile preliminary configuration with final configuration. The contractor shall support independent government validation and verification in support of ILS products impacted by ECRs and SFRs. The contractor shall support the Government’sreview 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, includes 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 SAILOR: The contractor shall provide and design the graphics user interface (UI), user experience (UX), and architectural specification to the SAILOR database and framework for SAILOR website on UNCLASS and CLASSIFIED Networks. This includes functional flow designs, relationship tables, graphic files, color specifications, and font specifications in accordance with Program Sponsor input. The contractor shall work with responsible developers to specify, implement, test and deploy provided web packages. The contractor shall provide support and technical guidance to all staging environments for integration and operational testing for SAILOR revisions; and all shall attend technical meetings and conferences in support of the SAILOR website.

3.4.1.9 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 updating Naval Networks website with the completed delivery signature data.

3.4.1.10 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 assist in resolution of Technical Feedback Reports (TFBRs). Reviews will include a written report validating the end user feedback that are recieved via TFBR’s or REMEDY. The contractor shall validate the information/feedback contained in the TFBR’s and REMEDY, and provide recommendations to the as necessary for technical resolution

3.4.1.11 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 user 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.12 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 part data and the cage code as well as the up to date unit cost. The contractor shall develop, compute and document Program Support Data (PSD) on Forms NAVSUP 1390 (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 Reporting and Tracking System (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.13 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.14 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. Uponm 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 SPAWAR 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. Training shall be conducted ashore and afloat.

3.4.2.2 On-the-Job Training (OJT) and Handbook Development. The contractor shall develop and conduct job skills-type training (at both the organization and maintenance levels) for system/equipment upon completion of Afloat Networks system or equipments upgrades. . The training shall provide personnel with a summary of what the formal training, as discussed in 3.4.3.1 above, covers.

3.4.3 Configuration Management (CM) Support: The contractor shall support the governments’ Configuration Management (CM) program to include the development, implementation and maintenance of Configuration Management Plans (CMP); Configuration Identification (CI); Configuration Control, Configuration Status Accounting; Configuration Verification and Audit; and Data Management.

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

3.4.5 Configuration Management Identification: The contractor shall develop, implement and sustain processes that verify and sustain a complete and accurate configuration identification of each CCI/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 Enterprise Problem Report (EPR), Service Request Deviation Form (SRD), or Deviation Request for Waiver are reflected in the baseline documents listed above.

3.4.6 Configuration Control: The contractor shall develop, implement and sustain configuration control process 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.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.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.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”.