N66001-17-R-0154 Amendment 0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

The purpose of this amendment is to make the follow ing changes:

1) Update Softw are Development Plan (SDP) DID to DI-IPSC-81427B in Section 3.3.10 Softw are Engineering Approach of the PWS and in Section 3.1 Softw are Development Plan of the RFP.

2) Update Section 1.1 Background of the PWS to revise the project list title to "Radio Frequency Propagation and Performance Assessment Suite (RFPPAS)."

See summary of changes herein. All other terms and conditions remain unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 34

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 05-Feb-2018

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X N6600117R0154

X 9B. DATED (SEE ITEM 11)

23-Jan-2018

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

05-Feb-2018

CODE

SPAWAR SYSTEMS CENTER PACIFIC

SARAH MURR, CODE 22550

SARAH.MURR@NAVY.MIL

53560 HULL STREET

SAN DIEGO CA 92152-5001

N66001 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

N6600117R0154

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

The following have been modified:

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS):

NETWORK MANAGEMENT REFERENCE IMPLEMENTATION LABORATORY (NMRIL)

ENGINEERING SERVICES AND SUPPORT

1.0 SCOPE:

The scope of this Performance Work Statement (PWS) includes support to the Network Management Reference Implementation Laboratory (NM RIL) in its continuing effort to maintain the Joint Enterprise Network Manager (JENM) product for Product Lead (PL) JENM, where the PL JENM has overall responsibility for the deployment and sustainment of the JENM software. The effort also includes the procurement of incidental materials at the task order level as required.

The NM RIL supplies a full range of services for the following, but not limited to, areas:

Software Support Activities: Research, design and develop new products; create new baselines, implement and test enhancements to those baselines; update and maintain established baselines and support for all fielded software.

Systems Engineering: Evaluate, compile, and perform functional and verification testing of all JENM product builds, support generation of communication plans, and collaborate with the developers of software defined radios to ensure interoperability with JENM.

Logistics: Configure JENM to meet the specific needs of each customer, test to ensure JENM is functioning correctly, track configuration and disposition details, assist with troubleshooting communication plans, and assist users as a Tier-3 helpdesk, and provide training support and documentation.

Test Event Support: Support radio test events and field activities, such as the bi-annual Network Integration Evaluation (NIE). Act as liaison between radio vendors and the government sponsors for product development and test support.

Additionally, the scope of this PWS is to provide technical support to the Communications Division (Code 552) projects for the following, but not limited to, areas:

Management: Integrated product teams, analysis, planning documentation.

Engineering: System/network architecture design and evaluation, integration, system evaluation and trade study, design analysis and assessment, software analysis and development, technology review and design.

Test and Evaluation: Test and evaluation, site survey, help desk, implementation and integration, laboratory testing, modeling and simulation.

Integrated Logistics Support (ILS): ILS planning and life cycle support, configuration management, technical data archiving and retrieval, training, implementation, supply, Continuous Acquisition and Life Cycle System, human factors as a part of system design and computer resources

Facilities: Development, management, installation, operations, and maintenance of SPAWAR System Center (SSC) Pacific laboratory, test bed facilities, and project equipment.

Implementation/Integration: Installation support, replacement of RF, C4I, Information systems that could include procurement, integration, enhancements, fabrication and testing.

On Site Technical Assistance: On-site support including troubleshooting, integration and installation of proof of concept systems for experiments/exercises and development testing.

Security: System security engineering and certification support.

Any replacement, follow-on, or interrelated systems associated with Table 1-1 below will be covered by the scope of this PWS.

Other agencies/activities outside the United States Navy (USN), supported by Space and Naval Warfare Systems Center (SSC) Pacific, Code 55200, are NATO, the United States Air Force (USAF), US Army, Marine Corps (USMC), United States Transportation Command (USTRANSCOM), Special Operations Command (USSOCOM), STRATCOM HQ, the Defense Advanced Research Projects Agency (DARPA), National Security Agency (NSA), and the Department of Homeland Security (DHS).

1.1 BACKGROUND

The Space and Naval Warfare (SPAWAR) System Center, Pacific (SSC Pacific) Communications Division requires support for evaluation of both existing and developing communications technology. This contract will aid SSC Pacific in the goal of assisting the Department of Defense (DoD) and the Navy in identifying, implementing, developing, improving and enhancing the Command, Control, Communications, Computers, & Intelligence (C4I) and network centric warfare concept called Information Dominance.

Communications Division programs consist of communications systems covering the entire spectrum from very low frequency (VLF) through laser; wideband, narrowband and protected communications on afloat, ashore, airborne, submerged, and space based platforms.

This effort consists of support relating to the areas of management, engineering, technical assistance, integrated logistics, facilities, implementation/integration, discrete signal processing experience radar signal processing and detection/classification, instrumentation, radio frequency (RF) data acquisition, software development Information Assurance system hardening, graphical user interface (GUI) design, application interface definitions, onsite technical assistance, and security.

The Network Management Reference Implementation Laboratory produces the Joint Enterprise Network Manager (JENM) and provides support throughout the application’s life cycle.

JENM is a radio network communications planning and management application that can be configured as a stand-alone system, a virtual machine, or simply as an application. JENM offers four primary capabilities:

Communications Planning Network Instantiation and Configuration (includes loading of terminals with configuration parameters) Network Monitoring (includes network health, status, and position reporting) Network Management (includes fault management and security management)

Examples of potential support areas, related to NM RIL, under this PWS include the programs and projects listed in the table below:

Table 1-1: Project Listing

DIGITAL MODULAR RADIO (DMR) RESEARCH DEVELOPMENT TEST AND EVALUATION

(RDT&E)

LASER PROPAGATION

ENHANCED POLAR SYSTEM (EPS) GATEWAY

JOINT (UHF) MILSATCOM NETWORK INTEGRATED (JMINI) CONTROL SYSTEM

INTEGRATED WAVEFORM CONTROL SYSTEM

HIGH FREQUENCY PROPAGATION STUDIES

NETWORK MANAGEMENT REFERENCE IMPLEMENTATION LABORATORY (NM RIL)

PERISCOPE VULNERABILITY

NAVY MULTIBAND TERMINAL INTERNATIONAL PARTNER VARIANT

RADIO FREQUENCY PROPAGATION AND PERFORMANCE ASSESSMENT SUITE (RFPPAS)

2.0 APPLICABLE DOCUMENTS:

The following documents in this Performance Work Statement (PWS) may be incorporated for individual delivery/task orders. Nothing in the documents however, shall supersede applicable laws and regulations, unless a specific exemption has been obtained. The Contractor’s solution shall comply with current documentation, standards and guidance as outlined in each task order.

2.1 DoD 5000.01, “The Defense Acquisition System”, 12 May 2003

2.2 DoD 5000.02, “Operation of the Defense Acquisition System”, 10 August 2017

2.3 CL 810-H, “Guidebook for Performance-Based Services Acquisition (PBSA) in the Department of

Defense”, December 2000

2.4 SPAWAR “Shore Installation Process Handbook”, Version 3.0, 19 October 2009

2.5 EIA-632, Processes for Engineering a System, January 1999

2.6 SECNAVINST 5000.2E, Implementation and Operation of the Defense Acquisition System and the Joint

Capabilities Integration and Development System, 1 September 2011.

2.7 IEEE Standard for Software Project Management Plans (IEEE 1058-1998), 8 December 1998

2.8 DoD Architecture Framework (DoDAF), version 2.0, May 2009

2.9 Guidebook for Acquisition of Naval Software Intensive Systems, Ver 1.0, dtd September 2008

2.10 ISO/IEC 15288:2008(E) (IEEE Std 15288-2015) Systems and Software Engineering – System Life Cycle

Process dtd 01 May 2015

2.11 IEEE Std 829-2008 Standard for Software and System Test Documentation, 18 July 2008

2.12 ISO/IEC 12207:2008(E)/IEEE Std 12207-2008 System and Software Engineering – Software Life Cycle

Processes dtd 01 February 2008

2.13 Software Development Plan (Template), TM-SPP-02, V2.0, dtd 05 April 2005

2.14 Software Engineering Institute, Capability Maturity Model Integration (CMMI) Version 1.1 for System

Engineering, Software engineering, Integrated Product and Process Development, and Supplier Sourcing, CMU/SEI-2002-TR-012, dtd March 2002

2.15 Software Engineering Institute, Capability Maturity Model Integration (CMMI) for Services, Version 1.3, Improving Processes for Better Services, CMU/SEI-2010-TR-034, November 2010

2.16 EIA 748-B, “Earned Value Management Systems”, June 2007

2.17 ASN RD&A Memorandum, “DON Policy on Digital Product/Technical Data, 23 October 2004

2.18 DoD 8570.01M, IA Work Force Improvement Program Manual, with Change 3, 01/24/2012

2.19 SECNAV Manual 5510.30, Department of Navy Personnel Security Program, 3 January 2013

2.20 SECNAV Manual 5510.36, Department of Navy Information Security Program, June 2006

2.21 DOD M-5200.01 Volumes 1 through 4, DOD Security Program, 24 February 2012

2.22 DOD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), 28 February 2006 with

Change 2 188 May 2016

2.23 OPNAVINST F3300.53C, Navy Antiterrorism Program 25 May 2009

2.24 National Security Decision Directive 298, National Operations Security Program (NSDD) 298, 22 January

2.25 DOD 5205.02, DOD Operations Security (OPSEC) Program, 6 March, 2006

2.26 OPNAVINST 3432.1, DON Operations Security, 4 November 2011

2.27 SPAWARINST 3432.1 (Series), Operations Security Policy, 02 February 2005

2.28 DoD 8500.1 Cyber Security Program, 14 March 2014

2.29 Network Enterprise Domain Software In-Service Support (SwISS) Plan; Version 1.1, 06 August 2008

2.30 JPEO JTRS Software Standards; Version 1.4.1, 04 May 2010

2.31 JPEO JTRS Standards Standardization Plan; Version 2.0.1, 04 May 2010

2.32 JTRS Unified INFOSEC Criteria; Revision 2, 02 December 2005 (SECRET//NOFORN)

2.33 Joint Tactical Radio System (JTRS) Information Repository (IR) User Registration Guide; Version 1.7, 23 July

2.34 MIL-HDBK-61A, Configuration Management Guidance; dated 7 February 2001

2.35 MIL STD 31000A, Technical Data Packages; February 2013

2.36 United States Code, Title 10, Section 2399, "Operational Test and Evaluation of Defense Acquisition

Programs", January 2012.

2.37 JOINT TACTICAL RADIO SYSTEM (JTRS) Test and Evaluation Master Plan (TEMP) for the JTRS Network

Enterprise Domain (NED), Increment 1, October 2010.

2.38 MIL-STD-961E DEFENSE AND PROGRAM UNIQUE SPECIFICATIONS FORMAT AND CONTENT, 2

April 2008

2.39 MIL-DTL-31000C TECHINICAL DATA PACKAGES; 9 July 2004

2.40 MIL-HDBK-454A GENERAL GUIDELINES FOR ELECTRONIC EQUIPMENT, 3 November 2000

2.41 MIL-HDBK-831 PREPARATION OF TEST REPORTS 23 April 1999

2.42 DoD 5000.2-R Mandatory Procedures for Major Defense Acquisition Programs and Major Automated

Information System Acquisition Programs; 5 April 2002

2.43 Secretary of Navy Instruction (SECNAVINST) 5000.2B Implementation of Mandatory Procedures for Major and Non-Major Defense Acquisition Programs and Major and Non-Major Information Technology Acquisition Programs; 6 December 1996

2.44 American Society of Mechanical Engineers (ASME) Y14.100 Engineering Drawing Practices; 2013

2.45 ASME Y14.24, Types and Applications of Engineering Drawings; 5 April 2013

2.46 ASME Y14.34; Associated Lists 2013

2.47 ASME Y14.35M Revision of Engineering Drawings and Associated Documents 2014

2.48 12207-2008 ISO/IEC/IEEE Standard for Systems and Software Engineering — Software Life Cycle Processes

2.49 ISO/IEC standard 7498-1 Open Systems Interconnections Reference Model (OSI—RM) 1994

2.50 DoD 8570.01-M, Information Assurance Workforce Improvement Program; 10 November 2015

2.51 DoD 8510.01 "Risk Management Framework (RMF) for DoD Information Technology (IT), March 14 2014 with change 2 28 July 2017

3.0 TECHNICAL REQUIREMENTS:

The contractor shall perform the following tasks. Individual task orders will contain specific details.

3.1 SUSTAINMENT

The contractor shall perform systems engineering, design, code, test, and integration required to support sustainment of released product baseline versions; including the currently fielded and planned replacement versions.

3.1.1 Sustainment Planning

The contractor shall maintain the product planning and monitoring of waveform, radio, and network support deployed in product baseline releases.

The contractor shall provide support in definition of Information Assurance and Test strategies for baseline updates;

information Assurance (IA) engineering to maintain Authorization to Operate (ATO) and Certificate of Networthiness (CoN) approvals when product baselines are updated to resolve bugs or IA deficiencies; analysis of user complaints, bug reports, and Information Assurance deficiencies identified for released baseline products, including failure analysis and system engineering design of remediation actions or problem resolution; expanding non-developmental item (NDI) Radio Support for released baselines; assist in ensuring that the sustainment and development baselines remain in sync and shall ensure that common problems are documented and resolved in both;

improve the product usability, and support development of training packages; and provide product baseline support to other DoD organizations at the request of the Program Office.

3.1.2 Sustainment Systems Engineering

The contractor shall participate in the product Systems Engineering team providing sustainment support for problem analysis and impact working with the reporting organization to document the problem; working with the Program Office to establish baseline update priorities and release strategies; ensuring the solutions provided will not affect the product security posture; coordinating with external agencies to ensure availability of needed resources for test of product releases; working with development team to ensure good understanding of the PBIs and that solutions meet objective; and providing product User Experience cross checks to ensure solution maintains product usability and supports updates to training.

3.1.3 Sustainment Development

The contractor shall participate in the product Development team providing sustainment support for: addressing Product Improvements already identified in Sustainment backlog; updates to software and data model as required;

perform all unit and integration testing; support the resolution of any integration problems found in sustainment release testing; and ensure that all software meets the “definition of done” and all practices are maintained for the baseline.

3.1.4 Sustainment Integration, Test, and Training Support

The contractor shall provide technical support for sustainment integration and test; work with systems engineering in ensuring reproducibility of problems identified; work with systems engineering to develop the release strategy and securing Lab and radio assets required for system testing of the release; support definition of development and System Test strategies to test coverage of all release requirements; ensure all test strategy, test plans, test cases and test reports are archived; coordinate with the Development test team to ensure problems resolved in sustainment baseline are also resolved in the development baseline; and support the logistics team to ensure the System User Manual and training stays synchronized with the product.

3.1.5 Development

The contractor shall perform systems engineering, design, code, test, and integration to support development, enhancement, and product improvements to product software applications and services; design, build, modify, improve the product as determined by the basic idea or concept; support new requirements and additional capabilities that change a product not within the current performance envelope; and support the capability to improve the product within its current performance envelope.

3.1.6 Systems Engineering Support

The contractor shall participate in the product Systems Engineering team providing support to the Program Office Technical Management Directorate (TMD); support to the TMD in the definition and allocation requirements to produce components; support project management office (PMO) leadership in the release strategy definition;

participation in Program Executive Office Command Control Communications-Tactical (PEO C3T) wide Integrated Product Teams for the TMD; assist in the definition of Information Assurance and Test strategies; assist in the definition of Epics, Capabilities and Features to define development strategy; support development teams in their implementation of updates for the PBIs; product User Experience (UEx) design to simplify and improve the product usability; information Assurance (IA) engineering, support to Risk Management Framework (RMF) process to achieve authorization to operate (ATO) and Certification of Networthiness (CoN) for new product releases;

Interface Control Document updates for new or modified waveforms, services, radios, and external system applications; product support to other Department of Defense (DoD) organizations at the request of PMO; and generation of whitepapers at the request of PMO to evaluate, document, design, or assess capabilities.

3.1.7 Capability Development

The contractor shall provide technical support for the product improvements stemming from the analysis of the Product Backlog Items (PBIs) allocated to a product release that delivers the functionality defined. The contractor shall assist in decomposing Features into a set of detailed requirements for development teams in the form of Product Backlog Items (PBIs); address Product Improvements identified in the Development backlog; analyze the PBIs to establish executable assignment to the development teams; assist in devising Simplified Planning including the ability to plan networks in the absence of a Tactical Radio Report in-feed; work with product Stakeholders to capture UEx feedback to enhance the design; add graphic visualization and editing to make planning simpler and more intuitive; work with external agencies to ensure that the product correctly supports radio services such as Enterprise Over-the-Air Management (eOTAM) and new planned services; assist in updating and Implementation of Target ICD / Reference implementation and minimizing the work NDI vendors are required to do to use it; assist in the definition and implementation of product support for new features and capabilities as radios and radio services evolve; participate in the design and implementation of interfaces to other tools in use by service planners; and add support for alternative platforms used by the other services, such as Marines, Navy, and Air Force.

3.2 MANAGEMENT SUPPORT

3.2.1 Integrated Product Team (IPT) Support

The contractor shall work with IPT lead and members to identify and prioritize tasks for the team; review progress;

participate in meetings; review, track and process action items; and provide assessments of the capabilities and deficiencies of the systems and vendors under review.

3.2.2 Program and System Management Support

The contractor shall support program and development efforts including assessing current and future system and software project requirements, analyzing changes and situations, and developing and proposing or recommending tentative approaches and solutions using a variety of tools, techniques, or processes. The contractor shall provide milestone support for major project efforts, facilitate and document project team activities, and provide input for business process modeling and reengineering. Documentation produced or modified shall be maintained in the electronic folders resident on the local area network.

3.2.3 Technical and Management Reviews

The contractor shall attend technical and management support reviews and related meetings. Examples are design reviews, process and issues resolution meetings, reviews of program status, system/subsystem requirements and critical design, various plans (test description, test case, test results), test readiness, and meetings to define and update schedules and task estimates.

3.2.4 Project Planning and Oversight

The contractor shall provide project-related planning documents and perform oversight of the planned tasks subject to government review and approval.

3.2.5 Program Management Documents

The contractor shall provide program oversight documents, such as a management plan, plan of action and milestones, schedule and work breakdown structure. Participate in technical and programmatic reviews and meetings. Submit progress and status reports as required by the task order (TO).

3.2.6 Risk Management

The contractor shall provide technical, cost, and schedule risk assessment.

3.3 ENGINEERING

3.3.1 Engineering Support

The contractor shall provide engineering support in connection with the development, installation, integration, and configuration of the Global Information Grid (GIG) and the Communications programs and information network systems.

3.3.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 and improve operations. The contractor shall investigate and research new techniques and solutions meeting the requirements. The contractor shall assess program requirements, analyze problems and conditions, develop, propose and recommend approaches and solutions using a variety of tools, techniques, and processes. The types of analyses will be directed at specific engineering and program performance goals associated with the implementation and integration of supported systems on host platforms. Emphasis will be placed on achieving complete system capability with networking technologies, utilizing typical connections, wireless, satellite communications (SATCOM), or Tactical Common Data Link (TCDL) transmission paths.

3.3.3 Design Analysis and Assessment Support

The contractor shall provide design analysis or recommendations for the following: safety, human factors, reliability, maintainability, transportability, survivability, weight or weight distribution, heating/cooling, control of electrostatic discharge and mercury contamination, and power or power distribution. The contractor shall review proposed designs to assess compliance with software/system specifications. The contractor shall monitor the transition between functional, allocated, and product baselines.

3.3.4 Software Analysis

The contractor shall contribute to Integrated Product Teams by evaluating proposed software architecture, functional allocations and configuration items and assessing the fidelity of the vendor’s proposals in accordance with the system specifications and published interface control documents. The contractor shall make recommendations, when appropriate, for achieving economies-of-effort or improvement to the system architecture, including related hardware and software implementations.

3.3.5 Program Review Support

The contractor shall attend program reviews, Design Reviews, and Interface Control Document Reviews. The contractor shall evaluate key development areas and compare with expected/desired progress. The contractor shall identify risk areas and methods of mitigation.

3.3.6 Information Assurance, Network Management and Network Architecture

The contractor shall provide requirements analysis and design to provide and evaluate Information Assurance (IA).

This IA effort includes such areas as Communications Security (COMSEC) Material Systems (CMS), High Assurance Internet Protocol Encryptors (HAIPEs), firewalls and security accreditation. The contractor shall evaluate network architectures (Local Area Network (LAN)/Multi Area Network (MAN)/Wide Area Network (WAN)) provide design inputs and requirements documentation, including Network Management Systems and Network management topologies. The contractor shall measure evaluations and requirements against concepts of operations and GIG requirements documentation that includes, but is not limited to, the GIG Architecture, Net Centric Interface Documents (NCIDs) and Network Core Enterprise Services (NCES).

The contractor shall provide system security engineering and certification support as required for successful Type Accreditation prior to fielding and implementation of a system. The contractor shall ensure necessary network security accreditation and assurance issues are obtained and followed. The contractor shall determine network parameters and settings required to meet security requirements.

3.3.7 GIG Integration and Compliance

The contractor shall provide analyses of specifications, capabilities development documents, technical requirements documents and concepts of operations to ensure the system under development is fully compliant with the Open System Interconnection (OSI) levels 1 through 7. In addition, the contractor shall ensure compliance with all architectural and performance standards required for full interoperability with the GIG, including Internet Protocol version 6 (IPv6), packet communications protocols, Quality and Class of Service, dynamic resource allocation, mobile ad hoc networking, and line of sight and satellite RF communications links. The contractor shall participate in developing solutions to the Information Assurance problems of connecting weapons systems to Command, Control, Communications, Computers and Intelligence (C4I) networks.

3.3.8 User Application Engineering

The contractor shall evaluate existing systems and equipment, including production terminals and baseband/user applications. The contractor shall evaluate requirements for new systems and equipment that may include baseband/user applications and terminals. The evaluation shall include comparing specifications with proposed designs to determine feasibility, compliance, and cost effectiveness.

3.3.9 Engineering Changes

The contractor shall review documents and engineering change proposals, pertaining to communications systems design, and identify changes, possible improvements, or alternatives to the system design that could affect the Navy communication system development.

3.3.10 Software Engineering Approach

The contractor shall define a software development approach appropriate for the computer software effort to be performed under this contract. This approach shall be documented in a Software Development Plan (SDP) (see data item description (DID) No. DI-IPSC-81427B for required format and content). Once defined, the contractor shall follow this SDP for all computer software to be developed or maintained under this contract.

The SDP shall define the offeror's proposed life cycle model and the processes used as a part of that model. In this context, the term "life cycle model" is as defined in Institute of Electrical and Electronics Engineers / Electronic Industries Alliance (IEEE/EIA) Standard 12207.0. The SDP shall describe the overall life cycle and shall include primary, supporting, and organizational processes based on the work content of this contract. In accordance with the framework defined in IEEE/EIA Standard 12207.0, the SDP shall define the processes, the activities to be performed as a part of the processes, the tasks which support the activities, and the techniques and tools to be used to perform the tasks. Because IEEE/EIA Standard 12207.0 does not prescribe how to accomplish the task, the offeror must provide this detailed information so the Navy can assess whether the offeror's approach is viable.

The SDP shall contain the information defined by IEEE/EIA Standard 12207.1, section 5.2.1 (generic content) and the Plans or Procedures in Table 1 of IEEE/EIA Standard 12207.1. In all cases, the level of detail shall be sufficient to define all software development processes, activities and tasks to be conducted. Information provided must include, as minimum, specific standards, methods, tools, actions, strategies, and responsibilities associated with development and qualification.

The contractor’s software engineering approach shall afford opportunities for input and oversight by the Government.

3.3.11 Component Analysis and Design

The contractor shall perform analysis and design on new and existing system components to include evaluating their capability to meet technical, functional, and mission requirements. Analysis shall be at the system, subsystem, component, or sub-component level.

3.3.12 Component Specification

The contractor shall develop component specifications and interface requirements. The contractor shall assess the adequacy of components in terms of current and future requirements. Technical documentation in support of these designs shall be produced.

3.3.13 Integration, Test, and Training Support

The contractor shall provide technical support for the execution of the developmental testing; definition of development and System Test strategies; participation in test team activities to synergize test approaches; support for regression testing across product builds; support for monthly build integration or more often on an as needed basis at the SSC Pacific test laboratories, program of record labs, NDI vendor labs, and in the contractor’s own labs; and support System User Manual, User Guide, and training updates.

3.3.14 Technical Manuals

Appropriate software product specifications, design documents, and software listings shall be produced when specified in the individual task order.

3.3.15 System Implementation

The contractor shall provide hardware/software integration engineering and analysis, planning support, and mechanical support.

3.3.16 Integration Analysis

The contractor shall perform integration analyses on components and subsystems to integrate them into the complete system. These analyses shall address technical interface and physical limitations necessary to meet the system mission requirements. The contractor shall prepare installation criteria, drawings, and other appropriate documentation to support the design approach.

3.3.17 Interface Specifications

The contractor shall prepare integration plans describing the technical approach, interface requirements, electrical and physical layout, schedule, test, and other requirements necessary for the complete integration of the subsystem components.

3.3.18 Concept of Operations

The contractor shall develop and prepare operational concepts documentation detailing use, operation, architectures, configurations, topologies, and requirements.

3.3.19 Security Engineering

The contractor shall perform system security engineering in accordance with the process, task, and activity guidelines established in DoDI 8510.01 "Risk Management Framework (RMF) for DoD Information Technology (IT), dated March 14 2014 and its subsequent revisions.

3.4 TEST AND EVALUATION

3.4.1 Performance Analysis Evaluation

The contractor shall evaluate system performance analyses, functional decomposition approach, functional to physical allocation decisions, requirements verification planning, and hardware/software designs.

3.4.2 Site Survey Support

The contractor shall provide site survey support as required to determine the physical space, location, and details for equipment installation. For new or existing systems, conduct an evaluation of the requirements document and provide suggested candidate installation sights. The contractor shall participate in the development of Plan of Action & Milestones (POA&Ms), surveys to establish WAN and LAN interfaces involving commercial telecom and DoD networks, and local network infrastructure evaluations and security accreditations.

3.4.3 Help Desk Support

The contractor shall provide on-call and on-site technical services on equipment/systems to perform troubleshooting, checkout, repair, and testing.

3.4.4 System Operation and Verification Test (SOVT)

The contractor shall develop a SOVT Planning package and perform the SOVT to ensure satisfactory operation, availability and readiness and report on outcomes.

3.4.5 Waveform and Platform Systems Engineering

The contractor shall review and provide improvements to the waveform and platform test and evaluation plans and procedures. The contractor shall also review and provide improvements to the associated waveform and platform assessment tools. Reviews shall be conducted in accordance with the Peer Review Process. Problem Change Reports (PCR) and Lessons Learned from prior waveform assessments and platform assessments shall be used in the plan /procedures / tools improvement process. The contractor shall provide electronic versions of the document changes to the government point of contact (POC).

3.4.6 System Test Planning and Coordination

The contractor shall support preparations and planning for systems testing such as the system terminal’s factory performance tests, Inter-segment Engineering Tests, engineering tests, backward compatibility performance tests, satellite System-wide interoperability and performance tests, and Formal Qualification Testing (FQT). The contractor shall coordinate test planning meetings, system reviews, and problem resolution meetings. The contractor shall provide terminal test plans, test procedures, visual presentations, performance analyses, recommendations, and technical reports when appropriate. The contractor shall review system-level test plans, procedures, and reports, and provide comments.

3.4.7 System Test and Evaluation Master Plan (TEMP) Support and Coordination

The contractor shall provide input for planning for test and evaluation of the system terminals and existing baseband equipments to determine backward compatibility and compliance with the test and evaluation master plan (TEMP) and terminal specifications. The contractor shall attend coordination and planning meetings, system reviews, and problem resolution meetings. The contractor shall provide visual presentations, data reduction; performance analyses of TEMP specified parameters, recommendations, and technical reports when appropriate. The contractor shall review test plans and procedures for accuracy and completeness and provide comments. The contractor shall participate in operational test readiness assessments.

3.4.8 Waveform and Platform Test Assessments

The contractor shall provide support to the government team in conducting waveform and platform test assessments against existing standards as directed by the government program manager. The test assessments shall use the current versions of the approved test and evaluation plans, procedures and tools.

3.4.9 System Development Testing

The contractor shall perform analytical studies and tests in the areas of system performance and network operation to include the determination of adherence to specifications, interface control documents, operational requirements documents and test and evaluation master plans. The contractor shall perform testing data reduction, analysis and documentation of test data including writing of computer programs in support of development and operational tests.

The contractor shall develop and provide test plans and procedures for laboratory and field testing against specifications, interface control documents, operational requirements documents, test and evaluation master plans and other standards documents. The contractor shall prepare test reports to include the results of analysis of tests and which summarize the capabilities and deficiencies of the system under review. The contractor shall recommend new techniques, design changes, and other stratagems aimed toward system improvement.

3.4.10 RF Laboratory Testing

The contractor shall configure candidate test systems for evaluation with selected RF paths, then participate in the design and implementation of a laboratory test facility supporting the evaluation of candidate systems; develop engineering solutions that meets the requirements document; from initial drawings design laboratory test environment; coordinate with selected RF path's for laboratory setup, connectivity and system configuration; prepare program documents; develop configuration drawings/scheme for testing; configure selected RF paths for laboratory testing; configure network connections for laboratory testing; participate in design and plan of action and milestones for laboratory testing; conduct laboratory testing; participate and provide input for field testing of candidate systems selected via the laboratory testing process; provide configurations/settings developed during the laboratory testing;

develop reports on testing conducted in laboratory or during operational tests.

3.4.11 Network Laboratory Testing

The contractor shall develop configuration drawings/scheme for testing; configure networks for laboratory testing;

participate in design and plan of action milestones for laboratory testing; conduct laboratory testing; provide data capture and analysis; develop reports on testing conducted in laboratory, developmental, or operational tests.

3.4.12 Modeling and Simulation

The contractor shall design, develop, and conduct modeling and simulation of systems, RF paths, user applications interfaces, network connectivity, performance, and un-testable requirements/test parameters due to cost, scale or environment (e.g. nuclear effects).

3.4.13 Laboratory Test Bed Engineering Support

The contractor shall provide laboratory test bed support to include designing, developing, configuring or re-configuring, integrating, modifying and maintaining test beds/test facilities; installing rigid and flexible, rectangular and circular waveguide systems, including support items such as dry air systems; designing, fabricating and installing mechanical support brackets and fixtures required for electronic equipment installations; designing, redesigning, installing, terminating multi-conductor and coaxial cables; defining and installing power and ground requirements for both secure and non-secure (red/black) systems; providing updated drawings, schematics and wiring diagrams. The contractor shall provide network test bed support including designing, reconfiguring, installing and terminating network cabling and infrastructure, wired and optical; equipment rack installation, configuration and maintenance; installation and maintenance of uninterruptible power sources. This shall include test beds and facilities such as the GIG-EF, GIG-IC and portable/transportable test beds used in support of the 552 program activity.

3.4.14 Software Requirements Specification

The contractor shall analyze system and subsystem operational concepts. The contractor shall perform site surveys and conduct studies to gain a complete understanding of software requirements. The contractor shall conduct market surveys.

3.4.15 Software Design

The contractor shall provide a system software design that meets known system-wide performance requirements.

The contractor shall provide tailored software designs that meet site-specific installation requirements. The contractor shall design for testability and maintainability. The contractor shall conduct preliminary and interim design reviews, and a final design review. The contractor shall establish and document the software design baseline.

The contractor shall adhere to an established software configuration control process. The contractor shall update the software baseline and supporting documentation to ensure that they meet emerging performance requirements.

3.4.16 Software Test

The contractor shall provide performance test plans, including: effective and quantitative test requirements that are achievable, affordable and adequately support system operation and maintenance; and test resources. The contractor shall perform test dry runs to validate and verify the test plan and procedures. Update test plans/procedures.

3.4.17 Software Procurement Support

The contractor shall identify the tools and licenses required to implement the software design. The contractor shall establish and maintain accountability and reporting mechanism to facilitate tracking material purchases, inventory control, and material custody (receipts and issues).

3.4.18 Program exercises/demonstrations

The contractor shall support exercise activities to include data collection, performance analysis, results analysis and interpretation, as well as exercise close-out activities. Work involves diagnosing and resolving problems in response to exercise reported incidents, researching, evaluating, providing feedback on problematic trends and patterns, providing training, and ensuring the rigorous application of information security information assurance policies, principles, and practices during program supported/approved exercises such as Joint Warrior Interoperability Demonstration (JWID), Joint Rapid Architecture Experimentation (JRAE), Trident Warrior Risk Reduction Limited Objective Experiments (TWRR LOEs), and Global Information Grid Evaluation Facilities (GIG-EF).

3.4.19 Operational sites

The contractor shall integrate systems and components into operational sites. The contractor shall dispatch field engineering support as needed to install and maintain fielded systems; determine failure mode(s); affect repair or recovery of system components to bring system back to operational readiness; conduct systems engineering as necessary to assure adjoining systems are not affected by the repair; perform tasks necessary to instruct or offer troubleshooting guidelines to the crew; report missing or damaged equipment (operational or non-operational);

return removed system components to appropriate In Service Engineering Activity (ISEA) or repair facility; provide comment to all technical documentation as required; periodically report causal conditions found in the performance of the repair that could be used in upgrade planning (age of hardware, incompatibilities, etc.), making upgrade/repair/replacement recommendations as appropriate; document and maintain system, network and/or nodal system configuration, providing alternative improvement and setting parameters to optimize interoperability and connectivity for the system.

3.4.20 Network Support

The contractor shall provide on-site expertise in areas such as, but not limited to, routing, switching, configuration and management of IPv4, IPv6 and hybrid networks. The contractor shall perform troubleshooting, repair and testing of wired and optical networks, including optical fiber terminations. The contractor will refine tests and exercises for protocol capture and traffic generation.

3.5 INTEGRATED LOGISTICS SUPPORT (ILS)

3.5.1 Data Management

The contractor shall perform data management activities. Examples of data management activities are consolidating, merging, correcting, revising, updating, incorporating comments, formatting, and maintaining a project technical library.

3.5.2 Configuration Management

The contractor shall perform configuration management activities. Examples of configuration management activities are identification of entities to be placed under configuration control, and assignment of a project-unique identifier to a Computer Software Configuration Item (CSCI) and each additional entity to be placed under configuration control, including documentation.

3.5.3 Configuration Status Accounting

The contractor shall record, update, and report the configuration status of all entities. The contractor shall maintain configuration records and master copies of delivered software end items for the duration of the contract. The contractor shall include, as applicable, the current version/revision/release of each entity, a record of changes to the entity being placed under project-level or higher configuration control, and the status of problem/change reports affecting the entity.

3.5.3.1 Problem Resolution

The contractor shall perform problem resolution in accordance with the following requirements:

3.5.3.2 Problem/Change Reports

The contractor shall prepare a problem/change report to describe each problem detected in software products under project-level or higher configuration control and each problem in activities described in the software development plan.

3.5.3.3 Problem Resolution Process

The contractor shall provide and implement a problem resolution process for handling each problem detected in (a) software products under project-level or higher configuration control, and (b) related process and project management plans. The contractor shall evaluate system hardware and software for Fault, Configuration, Accounting, Performance, Security (FCAPS); replicate fault/root cause in lab as necessary to instruct crew or Field Engineering Support; requisition incidental repair parts/materials at best value for the activity and within the event deadlines; dispatch field engineering support as needed to test and maintain systems in a current operational state of readiness; and establish and maintain a network level configuration master matrix for the operational sites, sufficient to assure operational readiness of the system.

3.5.4 Logistics

The contractor shall perform Integrated Logistics Support (ILS) analyses and ILS planning efforts. Establish the infrastructure for supply support and maintenance of the system throughout its life cycle.

3.5.4.1 Logistics Analysis and Planning

The contractor shall analyze logistics support requirements. The contractor shall conduct trade off studies and tailored Logistics Support Analysis (LSA). The contractor shall conduct life cycle costing analyses.

3.5.4.2 Logistics Management

The contractor shall participate in logistics, technical and program review meetings. The contractor shall review program documents.

3.5.4.3 Reliability, Maintainability, Maintenance Planning and Support

The contractor shall identify define and document Reliability, Maintainability and Availability (RM&A) requirements.

3.5.5 Technical Manuals

The contractor shall analyze related system and/or equipment level operation and maintenance technical manuals.

The contractor shall provide organizational and depot level technical manuals and training materials.

3.5.6 Operator/User Manuals

The contractor shall develop and provide software, system, and equipment operations manuals.

3.5.7 Maintenance Manuals

The contractor shall develop and provide software system and equipment organizational level and depot level maintenance manuals.

3.5.8 Technical Manual Validation and Verification

The contractor shall provide technical manual…