N65236-17-R-0002_8(a)_Incubator_Draft_PWS_dtd_14_June_2018.pdf

[Ver dtd 28 Dec 2017] 1 of 38

SECTION C – DESCRIPTION/SPECS/WORK STATEMENT

SPECIFICATIONS/STATEMENT OF WORK/PERFORMANCE WORK STATEMENT

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

SHORT TITLE: SPAWARSYSCEN ATLANTIC PROGRAMMATIC, ENGINEERING AND

LOGISTICS SUPPORT

1.0 PURPOSE

1.1 SCOPE

The scope of this contract covers the entire spectrum of non-inherently governmental services and solutions (equipment and services) associated with the full system lifecycle support including research, development, test, evaluation, maintenance, production and fielding of sustainable, secure, survivable, and interoperable Command, Control, Communications, Computers, Combat Systems, Intelligence, Surveillance, Reconnaissance (C5ISR), Information Operations, Enterprise Information Services (EIS) and Space capabilities. Additional support requires Program Management, Financial Management, and DoD Acquisition Life Cycle expertise and experience.

1.1.1 Multiple Funding

This contract will allow multiple appropriation on a single task order; funding specifics will be specified at the task order level

1.2 BACKGROUND

Space and Naval Warfare Systems Center Atlantic (SPAWARSYSCEN Atlantic) meets our nation's demands for uninterrupted vigilance, fail-safe cyber security, adaptive response and engineering excellence by delivering secure, integrated and innovative solutions to many naval, joint and national agencies. SPAWARSYSCEN Atlantic has requirements for C5ISR electronics and communications services and solutions in support of mission capabilities within its Portfolio mission areas.

2.0 PLACE(S) OF PERFORMANCE

2.1 GOVERNMENT FACILITIES

The Government will provide facilities (i.e., office space, computer hardware/software, or lab space) to those labor categories that would otherwise adversely affect the work performance if they were not available on-site. Labor categories and Government location of contractor personnel with supplied Government facilities will be identified at the task order level. Note: The burdened labor rate for those contractor personnel designated as "Government site" shall include overhead costs allocable to government site work, consistent with the contractor's established accounting practices.

2.1.1 Training Requirements

Contractor personnel working full-time or partially at a Government facility shall complete all applicable mandatory training requirements as specified under Security Training, PWS Para 8.0.

2.2 CONTRACTOR FACILITIES

The contractor shall have facilities (i.e., office space, laboratory space, staging and storage areas, with or without classified storage) in order to accomplish task order objectives. Depending on the type of support required at the task order level, contractor shall be required to possess or establish facilities at

[Ver dtd 28 Dec 2017] 2 of 38 specific locations. Any necessary contractor facilities requirements will be identified at the task order level.

3.0 PERFORMANCE REQUIREMENTS

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

3.1 TECHNICAL AND PROGRAM MANAGEMENT SUPPORT

The contractor shall assist the government project manager providing support at the program level, sponsor level, and at the contract level.

3.1.1 Program Support

The contractor shall apply business, financial management, and technical disciplines required to support planning, organizing, staffing, controlling, and leading team efforts in managing acquisition programs and projects such that the result places capable and supportable systems in the hands of the warfighter when and where needed, and at an affordable price. This functional area represents an integration of a complex system of differing but related functional disciplines that must work together to achieve program goals through development, production, deployment, operations, support, and disposal. Program support may require significant coordination and interface with various DoD and non-DoD activities located in and out of CONUS. The contractor is expected to include a mix of mature and innovative approaches to delivering foundational program management processes and practices. The contractor shall continually monitor and improve on these processes during execution of the contract. The contractor shall be able to provide program management support at the program level, sponsor level, and at the contract level.

3.1.2 Program Support Documentation

The contractor shall develop and draft various program management (PM) documents (CDRL A001).

At a minimum, the following documents are typical PM deliverables that the contractor shall have knowledge writing:

• Statement of Work or Performance Work Statement

• Cost Estimation

• Meeting Agenda and Minutes

• Plans of Action and Milestone

• Work Breakdown Structure (WBS)

• Various Program Acquisition related documents: Mission Needs Statement (MNS), Capability Production Documentation (CPD), Operational Requirements Document (ORD), etc.

3.2 DESIGN, DEVELOPMENT, INTEGRATION AND SYSTEMS ENGINEERING SUPPORT

The contractor shall perform engineering disciplines for the development of new and existing C5ISR and IT capabilities and systems, development of significant alterations to existing systems, integration and interface of existing equipment or software into different applications or platforms to support the warfighter, and evaluation of foreign or non-developmental systems, equipment, and technologies.

This shall include performance of scientific analytical and engineering efforts necessary to transform operational needs into unique system performance parameters for evolution into improved system capabilities. To the maximum extent practicable, open systems and standards shall be utilized in the design and implementation of systems and subsystems. This functional area also includes all support

[Ver dtd 28 Dec 2017] 3 of 38 required within the area of environmental engineering of C5ISR and IT systems and related infrastructure.

3.3 RESEARCH AND DEVELOPMENT SUPPORT

The contractor shall support the development and application of scientific and analytical disciplines to conduct fundamental research; scientific study and experimentation directed toward advancing the state-of-the-art or increasing knowledge or understanding; concept formulation; , and assessments of those studies and/or scans; assessment of system and subsystem requirements; development, analysis and evaluation of concepts and technologies (to include, but not limited to, trade studies, technological environmental scans) as well as systems and subsystems ; and development of operational concepts and tactics with the end goal being the application of results to developing new or improving existing C5ISR and IT capabilities. This effort may include manning, operating, and maintaining test support and experimental platforms to support tests.

3.4 PROTOTYPING, PRODUCTION, MODEL-MAKING, AND FABRICATION SUPPORT

The contractor shall support the building, production, fabrication, testing, evaluation, and operation of reduced and full-scale models, mock-ups, prototypes, production units, and research and development (R&D) test tools of electronic and electro-mechanical systems and system elements. Fabrication and manufacturing of replacement parts/equipment for fielded systems or platforms is included under this task. Additional support includes the development of hardware system/prototypes that demonstrate potential design solutions to operational and functional requirements for C5ISR and IT systems. Also included is the performance of systems hardware and software integration and testing to ensure total operational and functional compatibility with interfacing/interacting systems, subsystems, equipment, and computer programs. The use of traditional materials as well as new composite materials is considered applicable in this task.

3.5 TECHNOLOGICAL OPPORTUNITIES AND USER NEEDS ASSESSMENT SUPPORT

3.5.1 Independent Technical Studies

The contractor shall conduct independent technical studies (CDRL A001), evaluations, and assessments to determine the cost and feasibility of specified projects or processes. Conduct technical reviews, analyses, and studies to determine the availability and applicability of advanced technology and state-of-the-art systems or solutions. These studies would include technical capabilities as a comparison to cost analysis. The source for these technical reviews will include DoD acquisition programs as well as commercial off-the-shelf (COTS) systems, subsystems, and equipment.

Technical studies shall also include industrial engineering assessments of operations for the purpose of proposing improved processes, methods, standards, tools, and production enhancements.

3.5.2 Science and Technology

The contractor shall conduct technology assessments to determine the potential warfighting and/or commercial value of a laboratory and/or the intellectual property of a technical activity. Assessment includes identifying candidate products and processes, and evaluating potential to validate feasibility, suitability, and marketability. The contractor shall provide support in the development of technical portfolios of marketable technologies that that may be used to respond to inquiries and unanticipated application opportunities defined by potential clients. The contractor shall:

3.5.2.1 Obtain and review public, government, and privately held literature.

3.5.2.2 Obtain technical expertise and recommendations from experts, both inside and outside the government, including private industry, colleges and universities, and international experts.

3.5.2.3 Prove how the possible solutions fulfill the technical requirements and operational

[Ver dtd 28 Dec 2017] 4 of 38 mission requirements.

3.5.2.4 The contractor shall prepare a report (CDRL A002) that specifies the criteria used to select potential solutions. The contractor shall ensure the report will demonstrate the applicability and effectiveness of the criteria. The unacceptable solutions will be identified, and how and why each solution failed to satisfy the specified criteria will be discussed. The report will include a list of solutions that satisfied the criteria and a recommended course of action. The remainder of the report will clearly show the correlation between each solution and the technical requirements. Unless otherwise specified in each TO, the contractor’s format is acceptable.

3.6 INTEROPERABILITY, TEST AND EVALUATION, TRIALS AND INSTALLATION

CHECKOUT SUPPORT

The contractor shall perform and/or apply engineering, scientific, and analytical disciplines to the development of all necessary test documentation, plans, change requests, specifications, and reports to ensure that developed platforms, C5ISR and IT systems, and war-fighting capabilities have been properly tested and that joint interoperability requirements have been fully met at all levels of its life cycle, including the support of measurement facilities, ranges and instrumentation used for testing, evaluating, experimenting, and exercising platforms and systems. This includes Intra-DoD, Inter- Government, and International interoperability studies as well as multi-platform integration studies of various C5ISR and IT systems. Included in this task, the contractor shall perform Independent Verification and Validation (IV&V) Support services.

3.7 HARDWARE AND SOFTWARE SUPPORT

The contractor shall apply engineering, security, and scientific disciplines to perform technical analysis and technical support of new or existing hardware and software for systems, test facilities, or training facilities. This also includes technical support of software implementation in systems, sub-systems, and components. Supporting or delivering Commercial Off-The-Shelf (COTS) solutions and product modifications (e.g., software tools, licensing, and associated hardware) are considered within the scope of this functional area. At the task order level, compliance with and support of specific technical approaches and process management assessments may be required.

3.8 INSTALLATION AND IN-SERVICE ENGINEERING SUPPORT

The contractor shall apply engineering, analytical, and technical disciplines and skills to establish and maintain long term engineering, operation, and maintenance support for in-service C5ISR and IT capabilities as well as the capability to modernize or introduce transformational technologies into those capabilities. This includes the installation in accordance with paragraph 6.2.2 of this document for shipboard work and SPAWAR Shore Installation Process Handbook for shore work, and delivery of systems, including the development of installation and integration plans, drawings, technical change documentation and notices and procedures in support of these efforts. Included in this task is site/platform support liaison and help desk support as required.

3.9 TECHNICAL SUPPORT

3.9.1 Site Surveys and Studies

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

3.9.2 Maintenance

[Ver dtd 28 Dec 2017] 5 of 38

This type of work entails, at a minimum, the following: maintenance, overhaul, troubleshooting, and repair or a system and/or equipment, such as Video Teleconferencing systems. Maintenance support work may or may not involve traveling. Contractor personnel shall be highly experienced in electronic systems and familiar with the particular system, unless otherwise stated in the task order.

3.9.3 On-Site Technical Assist

The contractor shall provide technical assistance directly for CASREP resolution, fault analysis, testing, and/or repair of various SPAWARSYSCEN Atlantic installed systems and equipment, as specified by individual task orders, to restore the units to operational status. The contractor shall be prepared to commence travel for onsite assistance within 24 hours of notification. Contractor personnel shall be technically knowledgeable and capable of analyzing system problems and implementing corrective actions without direct assistance or support from SPAWARSYSCEN Atlantic personnel if and when required. Technical assistance may also involve collecting additional information for SPAWARSYSCEN Atlantic, such as design, operation and equipment conditions, training and skill levels of site operators, engineering change status, initial calibration, recalibration, and maintenance problems. The contractor shall report findings, analysis results and corrective action taken associated with technical assistance provided, using the Government provided database/format/workspace.

3.10 INTEGRATED LOGISTICS SUPPORT (ILS)

The contractor shall apply engineering and analytical disciplines required to implement ILS as a multi-functional technical management discipline associated with the design, development, test, production, fielding, sustainment, and improvement modifications of cost effective C5ISR and IT systems that achieve the warfighters' peacetime and wartime readiness requirements. The principal objectives of ILS are to ensure that support considerations are an integral part of the system's design requirements, that the system can be cost effectively supported through its lifecycle (from program initiation to system retirement), and that the infrastructure elements necessary to the initial fielding, operation and maintenance support of the system are identified, developed, acquired, and supported.

Utilizing MIL-M-85337A and MIL-DTL-24784 as guidance documents, the contractor shall provide technical manual support; however, the majority of ILS includes supply support and provisioning, maintenance planning, support equipment, technical data, training, facilities, packaging, handling, storage and transportation, manpower, and design interface, computer resources, Performance Based Logistics, Supply Chain Management, and depot management.

3.11 SYSTEM SAFETY ENGINEERING SUPPORT

The contractor shall apply engineering and analytical disciplines to ensure that safety is considered in all aspects of design, development, operation, maintenance, and modification of C5ISR and IT systems and platforms. This includes system health and hazard assessments and analysis and pollution prevention.

3.12 TRAINING SUPPORT

The contractor shall apply engineering, analytical, and applicable training disciplines required to ensure that the warfighter and technical support community is provided with adequate instruction including applied exercises resulting in the attainment and retention of knowledge, skills, and abilities regarding the warfighting capabilities, platforms, and the C5ISR and IT systems they operate and maintain. The contractor shall develop a presentation and provide all training course documentation (CDRL A003) required for each course.

[Ver dtd 28 Dec 2017] 6 of 38

3.13 OPERATIONS AND TRAINING EXERCISE SUPPORT

The contractor shall apply technical and administrative disciplines and skills to provide systems operation support services including support for standard/common/migration applications or systems.

Activities include application/system and network administration services, maintenance of documentation related to system and network operations, routine system problem identification and correction, LAN/WAN administration and any other operational duties and training exercises associated with the SPAWAR mission. Support may also include providing applications and systems modification, testing, installation and ongoing quality assurance activities.

3.14 CONFIGURATION MANAGEMENT (CM) SUPPORT

As outlined in MIL-HDBK-61A, the contractor shall apply engineering and analytical disciplines to identify, document, and verify the functional, performance, and physical characteristics of systems and associated interface systems, to control changes and nonconformance, and to track actual configurations of systems and platforms. The contractor shall provide support that includes all activities related to CM planning, baseline management, configuration identification, configuration audits, formal reviews, engineering changes, and configuration management records and reports; and the use of automated tools to perform these functions.

3.15 PROJECT QUALITY ASSURANCE (QA) SUPPORT

The contractor shall apply engineering and analytical disciplines to ensure that the processes and products used in the design, development, fabrication, manufacture, and installation result in quality products. This area also includes the development and adherence to quality management plans in accordance to best industry practices.

3.16 SOFTWARE ACQUISITION MANAGEMENT SUPPORT

The contractor shall support the PM with the program/project management of software development and maintenance of Enterprise Information Systems (EIS), software, and business applications throughout the acquisition life cycle including development, testing, production release, and sustainment. The contractor shall support TEAM SPAWAR Business Systems/EIS business development and provide programmatic support to Government overarching technical authority tasks and responsibilities.

3.17 FMS SUPPORT

3.17.1 FMS Program Planning Support

The contractor shall develop technical reports and rough order of magnitude (ROM’s) for hardware/software deliverables in accordance to Price and Availability (P&A) requests. The contractor shall review Letters of Request (LORs) to ensure conformance to FMS rules/regulations for case implementation, execution, and closure. The contractor shall support pre-case activities to include researching and preparing concept papers and technical reports; coordinate/attend technical and program meetings; develop agenda items/briefs; generate meeting minutes; develop/maintain an action tracking system; and maintain ready-reference library. Case support may require significant coordination and interface with various DoD and non-DoD activities located in and out of CONUS.

3.17.2 FMS Program Execution and Case Tracking

The contractor shall review Letters of Offer and Acceptance (LOAs) to ensure conformance to FMS rules/regulations and perform risk analysis based on cost, schedule, and technical status. The contractor shall conduct analyses and document LOA configuration variances and inter-operability issues; respond to FMS data calls; develop work breakdown structures; participate in program and technical reviews; analyze financial obligations, expenditures, and discrepancies; track procurement status; provide logistic and configuration management support; support training activities; and

[Ver dtd 28 Dec 2017] 7 of 38 develop management reports/tools to meet case requirements. The contractor shall also support case execution activities to include coordination/attendance of technical and program meetings, development of agenda items/briefs, generation of meeting minutes, and development/maintenance of action tracking systems. Case support may require significant coordination and interface with various DoD and non-DoD activities located in and out of CONUS.

3.17.3 FMS Case Closure / Termination

The contractor shall assist in maintaining case files for program termination and/or case closure. The contractor shall track and monitor the progress of case closure and terminated programs to completion. The contractor will assist in gathering documentation by conducting record searches and compiling, analyzing, and preparing documentation to support termination/closure processes. Case support may require significant coordination and interface with various DoD and non-DoD activities located in and out of CONUS.

3.18 PROCUREMENT MANAGEMENT SUPPORT FOR EQUIPMENT AND MATERIAL

PROCUREMENT

As specified on task orders, the contractor shall provide various equipment/material support that ranges from research, procurement, fabrication, integration, and delivery. The contractor shall collect information for requirements documentation, assemble procurement requirements package, submit requests to the procurement competencies, and confirm selected proposals/quotes satisfy the Government's needs and sufficient funds are available to proceed, then monitor and report on procurement status until award.

3.18.1 Procurement Support

The contractor shall research and procure specified equipment and material as either contractor-acquired property (CAP) (PWS Para 10.2) or contractor furnished property (CFP) requirements. To ensure fair and reasonable pricing under this, the contractor shall ensure acquisition selection factors include price, availability, reliability, and supportability within current supply system. The contractor shall keep source selection records and make it available for government review as needed. Prior to items being purchased, the contractor shall obtain COR concurrence. The contractor shall provide all support data and cost estimates necessary to justify a fair and reasonable price per item procured. The contractor shall have an adequate accounting system to track all items and the delivery status per task order and per item. After receipt, the contractor shall have an adequate property management system to track the item location per task order per item. All items procured by the contractor shall be utilized or staged at the contractor’s facility transported by the contractor to the installation, integrated or consumed in a system, or returned to the government at the completion of the task order. The contractor shall be responsible for identifying monthly and cumulative CAP procurements in the TOSR (CDRL A004). At any time outside the monthly reporting cycle, the contractor shall be capable of generating and providing a CAP inventory tracking report(s) (CDRL A005) of items procured, received, and delivered as applicable. Contractor shall recommend and procure items that conform to the following applicable product validation, identification, and tracking requirements.

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

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

[Ver dtd 28 Dec 2017] 8 of 38

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

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

3.18.2 Warranty Tracking & Management

3.18.2.1 Warranty Tracking of Serialized Items

In accordance with DFARS clause 252.246-7005/7006 and Instructions for Electronic Submission of Warranty Tracking and Administration Information for Serialized Items (see CDRL A006 Attachment 1 of Exhibit A), the contractor shall follow the requirements for any serialized item manufactured or acquired that come with a warranty:

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

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

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

(i) Utilizing the Wide Area WorkFlow (WAWF), the contractor shall ensure that the required warranty data is electronically submitted using the CDRL exhibit line item number (ELIN) functionality for the WAWF Materiel Inspection and Receiving Report or WAWF Reparable Receiving Report, as applicable.

(ii) If problems occur submitting warranty data electronically, the WTI and WSRI can be submitted manually (as a PDF file) with the COR concurrence. The contractor shall forward documents to COR for review and when approved, the Government will post forms to Electronic Data Access (EDA).

3.18.2.2 Warranty Management

The contractor shall serve as the warranty manager by tracking the applicable government acceptance dates/receipt dates against the serial number of equipment or the line replaceable unit (LRU) of a system. As warranty manager, the contractor shall, unless otherwise directed, submit warranty data on Warranty Tracking Information (WTI) form and Warranty Source of Repair Instructions (WSRI) as specified on the Warranty Tracking and Administration for Serialized Items (CDRL A006). The

[Ver dtd 28 Dec 2017] 9 of 38 contractor shall upload data to the WAWF Materiel Inspection and Receiving Report (or WAWF Reparable Receiving Report, if appropriate).

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

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

3.18.3 Hydrofluorocarbons

Pursuant with the Presidential Climate Action Plan, the contractor shall provide services, when feasible, that reduce the use, release, or emissions of high global warming potential (GWP) hydrofluorocarbons (HFCs) in accordance with FAR clauses 52.223-12.

3.19 ARCHITECTURE DEVELOPMENT SUPPORT

The contractor shall apply engineering, scientific, and analytical disciplines to assist in the identification and creation of analysis artifacts, support acquisition and engineering processes to identify key end-to-end performance requirements, derive measures of effectiveness, and measures of performance to be validated and verified by test procedures for C5ISR and IT systems. Analysis results shall be documented using applicable frameworks such as, Department of Defense Architecture Framework (DoDAF) viewpoints or Federal Enterprise Architecture viewpoints, as applicable.

3.20 ENTERPRISE ANALYSIS AND ASSESSMENTS SUPPORT

The contractor shall apply engineering, scientific, and analytical disciplines to identify, refine, and document operational and functional requirements; translate operational and functional requirements to Concepts of Operations (CONOPS), Functional Requirements, Functional Descriptions, and Operational Requirements Documentation such as Capability Development Documents (CDD), Capability Production Documents (CPD), etc.; develop system, subsystem, and component level design specifications and documents; and develop System performance documents, specifications, and interface requirements documents.

3.21 MODELING, SIMULATION, AND ANALYSIS SUPPORT

The contractor shall apply standardized, rigorous, structured methodology to create and validate a physical, mathematical, or otherwise logical representation of a system, entity, phenomenon, or process. The contractor shall be able to use models, including emulators, prototypes, simulators, and either statically or over time, to develop data as a basis for making managerial, technical, strategic, or tactical decisions.

[Ver dtd 28 Dec 2017] 10 of 38

3.22 HUMAN SYSTEMS INTEGRATION, PERFORMANCE, AND USABILITY ENGINEERING

SUPPORT

The contractor shall apply engineering, scientific, and analytical disciplines to ensure that design of interactive systems are safer, more secure and easier to use, thereby reducing accidents due to human error, increasing system integrity, and enabling more efficient process operations. This functional area also includes applying engineering, scientific, and analytical disciplines to ensure that the number, type, mix, knowledge, skills, and abilities (KSAs), aptitudes, and physical characteristics of operators, maintainers, and support personnel have been defined and documented early in the system design phase. This includes the preparation and maintenance of Human Engineering Program Plans and Human Engineering Detailed Equipment Performance Specifications and performance Human Factors Assessments for C5ISR and IT systems. In accordance with DFAR 235.072(e), the contractor shall comply with clause 252.235-7004, Protection of Human Subjects when performing research involving human subjects that is covered under 32 CFR Part 219.

3.23 CYBERSECURITY/INFORMATION ASSURANCE

Cybersecurity (also known as Information Assurance (IA)) includes tasks which the contractor shall protect and defend information and information systems by ensuring their availability, integrity, authentication, confidentiality, and non-repudiation. This includes providing for restoration of information systems by incorporating protection, detection, and reaction capabilities.

3.23.1 Cybersecurity Personnel

(a) In accordance with DFAR clause 252.239-7001, DoDD 8570.01 and SECNAV M-5239.2, contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-M prior to accessing DoD information systems.

(b) The contractor shall be responsible for tracking and reporting cybersecurity personnel, also known as Cybersecurity Workforce (CSWF). See PWS Para 4.4.3 for CSWF Report (CDRL A008) requirements. Although the minimum frequency of reporting is monthly, the task order can require additional updates at any time.

3.23.2 Design Changes

The contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI 8500.01.

3.24 SYSTEMS ENGINEERING MANAGEMENT SUPPORT

The contractor shall collect and analyze data and draft documentation in support of assigned programs. Topics include, but are not limited to, management methodology and tools, program requirements, acquisition planning, program milestones, integrated program summaries, program schedules, and other program related information. All contractor documentation shall be prepared in accordance with current Government Directives such as the DoD 5000 series.

3.25 PROJECT MANAGEMENT SUPPORT

The contractor shall support the PM with monitoring program execution by reviewing or developing integrated cost and schedule performance data. The contractor shall, based on these reviews, make recommendations to mitigate or minimize risk. The contractor will use internal management control systems that produce data that: (a) indicate work progress; (b) properly relate cost, schedule, and technical accomplishment; (c) are valid, timely, and able to be audited; and (d) provide PMs with information at a practical level of summarization.

[Ver dtd 28 Dec 2017] 11 of 38

3.26 PLAN DEVELOPMENT, PROGRAM PLAN EXECUTION, AND INTEGRATED CHANGE

CONTROL SUPPORT

3.26.1 Plan Development

The contractor shall support PMs in the Program Plan Development phase by creating consistent and coherent documents from information resulting from other planning processes.

3.26.2 Program Plan Execution

The contractor shall support PMs in the Program Plan Execution phase by implementing the plan and performing the activities included therein.

3.26.3 Integrated Change Control

The contractor shall support PMs in Integrated Change Control by coordinating changes across the entire project. The contractor shall prepare for, attend, provide inputs for, and participate in program related meetings and reviews. The contractor shall prepare draft agendas, financial/budget reports, minutes, trip reports, attendance lists, action item lists, program reviews, design reviews, photographs, and recommendations. The contractor shall maintain historical records of these meetings for ready retrieval and reference. The contractor shall compile reference information packages for ready access in support of meeting attendance and action item and deficiency resolution.

3.27 RISK MANAGEMENT SUPPORT

The contractor shall update and maintain a Government - Furnished Risk Enterprise web application;

maintain the database on the Government firewall protected network; schedule & attend periodic risk review meetings; provide presentation support for such meetings; and prepare minutes to include action item assignments.

3.28 MEASUREMENT AND ANALYSIS SUPPORT

3.28.1 Performance Management

The contractor shall support the PM with performance management and provide analysis and insight into operational performance for approved new projects. The contractor shall develop project metrics and coordinate with the appropriate personnel to track project metrics focusing on schedule, cost, and performance. The contractor shall identify which metrics are currently tracked and monitored with regard to customer projects and make recommendations for improving the project performance reporting.

4.0 INFORMATION TECHNOLOGY (IT) SERVICES REQUIREMENTS

4.1 INFORMATION TECHNOLOGY (IT) GENERAL REQUIREMENTS

The contractor shall adhere to the following requirements when the IT support services and/or supplies are applicable to the requirement:

4.1.1 Ensure that no production systems are operational on any research, development, test and evaluation (RDT&E) network.

4.1.2 Follow DoDI 8510.01 when deploying, integrating, and implementing IT capabilities.

4.1.3 Migrate all Navy Ashore production systems to the Navy, Marine Corps Intranet (NMCI) environment where available.

4.1.4 Work with Government personnel to ensure compliance with all current Navy IT & cybersecurity policies, including those pertaining to Cyber Asset Reduction and Security (CARS).

[Ver dtd 28 Dec 2017] 12 of 38

4.1.5 Follow SECNAVINST 5239.3C and DoDI 8510.01 prior to integration and implementation of IT solutions or systems.

4.1.6 Register any contractor-owned or contractor-maintained IT systems utilized on contract in the Department of Defense IT Portfolio Registry (DITPR)-DON.

4.1.7 Ensure all software recommended, procured, and/or developed is compliant with Section 508 of the Rehabilitation Act of 1973, 26 CFR Part 1194 and pursuant to SPAWARINST 5721.1B.

4.1.8 Only perform work specified within the limitations of the basic contract and task order, if applicable.

4.2 ACQUISITION OF COMMERCIAL SOFTWARE PRODUCTS, HARDWARE, AND

RELATED SERVICES

Contractors recommending or purchasing commercial software products, hardware, and related services that support Navy programs and projects shall ensure they recommend or procure items from approved sources in accordance with the latest DoN and DoD policies.

4.2.1 DoN Enterprise Licensing Agreement/DoD Enterprise Software Initiative Program Pursuant to DoN Memorandum – Mandatory use of DoN Enterprise Licensing Agreement (ELA), contractors that are authorized to use Government supply sources per FAR Subpart 51.101 shall verify if the product is attainable through DoN ELAs and if so, procure that item in accordance with appropriate ELA procedures. If an item is not attainable through the DoN ELA program, contractors shall then utilize DoD Enterprise Software Initiative (ESI) program as prescribed in DFARS Subpart

208.74 and Government-wide SmartBuy program (see DoD memo dtd 22 Dec 05). The contractor shall ensure any items purchased outside these programs have the required approved waivers as applicable to the program. Software and/or software licenses to be procured will be specified at the task order level.

4.2.2 DoN Application and Database Management System (DADMS)

The contractor shall ensure that no Functional Area Manager (FAM) disapproved applications are integrated, installed or operational on Navy networks. The contractor shall ensure that all databases that use database management systems (DBMS) designed, implemented, and/or hosted on servers and/or mainframes supporting Navy applications and systems be registered in DoN Application and Database Management System (DADMS) and are FAM approved. All integrated, installed, or operational applications hosted on Navy networks must also be registered in DADMS and approved by the FAM. No operational systems or applications will be integrated, installed, or operational on the RDT&E network.

4.2.3 DoD Cybersecurity/Computer Security Requirements

The contractor shall ensure that all products recommended and/or procured that impact cybersecurity shall be selected from the National Information Assurance Partnership (NIAP) Validated Products List. The contractor shall ensure the products chosen are based on the appropriate NIAP-approved Protection Profile (PP) for the network involved, and are utilized in accordance with latest Defense Information Systems Agency (DISA) policy at time of order. The contractor shall store all product information and have it available for government review at any time.

4.2.4 Supply Chain Risk Management

“Covered item of supply” (e.g., software, processor, etc.) is any information technology item that is purchased for inclusion in a “covered system” (i.e., national security systems). In accordance with DFARs clause 252.239-7018, the contractor shall have mechanisms in place to effectively monitor the supply chain for critical components, understands how supply chain risk can be introduced through those components, and shall have implemented or plans to implement countermeasures to mitigate the risk that an adversary may sabotage, maliciously introduce unwanted function, or

[Ver dtd 28 Dec 2017] 13 of 38 otherwise subvert the design, integrity, manufacturing, production, distribution, installation, operation, or maintenance or a system so as to surveil, deny, disrupt, or otherwise degrade the function, use, or operation of such system.

4.3 IT POSITION CATEGORIES

Pursuant to DoDM 5200.02, DoDI 8500.01, DoD 8570.01-M, SECNAVINST 5510.30B, SECNAV M-5239.2, SECNAV M-5510.30, and applicable to unclassified DoD information systems, a designator is assigned to certain individuals that indicates the level of IT access required to execute the responsibilities of the position based on the potential for an individual assigned to the position to adversely impact DoD missions or functions. As identified in SECNAV M-5510.30, two DoN IT levels/Position categories require personnel to meet specific security requirements:

(a) IT-I (Privileged access)

(b) IT-II (Limited Privileged, sensitive information)

The contractor PM shall assist the Government Project Manager or Contracting Officer’s representative (COR) in determining the appropriate IT Position Category assignment for all contractor personnel based on the level of IT access needed. Contractor personnel whose duties meet the criteria for IT-I or IT-II position designation shall have a successful Single-Source Scope Background Investigation (SSBI), Tier 5 (T5) or Tier 3 (T3), respectively, with 5 year reviews and shall have a U.S. citizenship unless a waiver request is approved by CNO (N09N2). All required SSBI, SSBI Periodic Reinvestigation (SSBI-PR), and National Agency Check (NAC) adjudication will be performed Pursuant to DoDI 8500.01 and SECNAVINST 5510.30B. Requests for investigation of contractor personnel for fitness determinations or IT eligibility without classified access are submitted by SPAWARSYSCEN Atlantic Security Office, processed by the Office of Personnel Management (OPM), and adjudicated by Department of Defense Consolidated Adjudications Facility (DoD CAF). Contractor personnel identified as needing privileged access shall complete a privileged user agreement, all privileged user training for their level, 8570 certification and a System Authorization Access Request – Navy (SAAR-N) form in accordance with the applicable IT position category. Investigative requirements for each category vary, depending on the role and whether the individual is a U.S. civilian contractor or a foreign national.

4.3.1-IT-I Level (Privileged) Personnel in this position support cybersecurity roles at command enclave infrastructure to include RDT&E, Data Centers and any other network and/or are responsible for the planning, direction, and implementation of a computer security program; major responsibility for the direction, planning and design of a computer system, including the hardware and software; or, can access a system during the operation or maintenance in such a way, and with a relatively high risk for causing grave damage, or realize a significant personal gain. Personnel whose duties meet the criteria for IT-I Position designation shall have a favorably adjudicated Tier 5 (T5) investigation (formerly a Single Scope Background Investigation (SSBI) or SSBI-PR). The T5 is updated a minimum of every 5 years.

Personnel assigned to designated IT-I positions shall have a U.S. citizenship unless a waiver request is approved by CNO. IT-1 roles include the following:

• Boundary Devices Management (proxies, firewalls, traffic analyzers, VPN Gateways)

• Intrusion Detection/Prevention Systems (IDS/IPS)

• Host Based Security Systems (HBSS)

• Network infrastructure (routers, switches, enterprise wireless)

• Domain and Authentication System Administrators (Active Directory, LDAP, Kerberos, etc.)

(enclave wide scope)

• Vulnerability Scanner Operators (Retina, ACAS, HP Web Inspect, etc.)

Virtualization Technology Administrators that host any of the above (ESX, Solaris Zones, etc.)

4.3.2 – IT-II Level (Limited Privileged) Personnel in this position support the-direction, planning, design, operation, or maintenance of a computer system, have privileged access to assets and systems that are tenants on SPAWARSYSCEN

[Ver dtd 28 Dec 2017] 14 of 38

Atlantic networks and/or similar system constructs, and has work that is technically reviewed by a higher authority at the IT-II Position level to insure the integrity of the system. Personnel whose duties meet the criteria for an IT-II Position shall have a favorably adjudicated Tier 3 (T3) investigation (formerly National Agency Check with Law and Credit (formerly ANACI/NACLC).

Personnel assigned to designated IT-II positions shall have a U.S. citizenship unless a waiver request is approved by CNO. Examples of IT-II roles include the following:

• Webserver Administrators

• Developers

• Testers

• Database Administrators

4.4 CYBERSECURITY SUPPORT

Cybersecurity (which replaced the term Information Assurance (IA)) is defined as prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. Contractor personnel shall perform tasks to ensure Navy applications, systems, and networks satisfy Federal/DoD/DON/Navy cybersecurity requirements.

4.4.1 Cyber IT and Cybersecurity Personnel

4.4.1.1 The Cyberspace workforce elements addressed include contractors performing functions in designated Cyber IT positions and Cybersecurity positions. In accordance with DFARS Subpart 5239.71, DoDD 8140.01, SECNAVINST 5239.20A, and SECNAV M-5239.2, contractor personnel performing cybersecurity functions shall meet all cybersecurity training, certification, and tracking requirements as cited in DoD 8570.01-M prior to accessing DoD information systems. Proposed contractor Cyber IT and cybersecurity personnel shall be appropriately qualified prior to the start of the contract performance period or before assignment to the contract during the course of the performance period.

4.4.1.2 Contractors that access Navy IT shall also follow guidelines and provisions documented in Navy Telecommunications Directive (NTD 10-11) and are required to complete a System Authorization Access Request (SAAR) – Navy form as documented in Para 8.2.2.4(b).

4.4.1.3 Contractor personnel with privileged access shall acknowledge special responsibilities with a Privileged Access Agreement (PAA) IAW SECNAVINST 5239.20A.

4.4.2 Design, Integration, Configuration or Installation of Hardware and Software The contractor shall ensure any equipment/system installed or integrated into Navy platform will meet the cybersecurity requirements as specified under DoDI…