A1.SOW _DRAFT.pdf

Contract #N00173-??-?-????

Attachment 1

Statement of Work

Command, Control, Communications, Computers, Intelligence, Surveillance and

Reconnaissance (C4ISR) Systems Design and Development

(DRAFT)

1.0 Introduction

1.1 Mission

1.2 Background

1.3 Scope

2.0 Applicable Documents

2.1 Military/Department of Defense Specifications and Standards

2.2 Non-Government Documents

3.0 Requirements

4.0 Special Requirements

4.1 Security

Statement of Work (SOW)

Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) Systems Design and Development

1.0 Introduction

The Space Systems Development Department (SSDD) is the space and ground support systems research and development (R&D) organization of the Naval Center for Space Technology (NCST), an organization within the U.S. Naval Research Laboratory (NRL) in Washington, DC, which is the designated lead for Navy Space Program technology development and acquisition of space, aerospace and Command, Control, Communications, Computers, Intelligence, Surveillance and Reconnaissance (C4ISR) systems to assist Naval Missions.

1.1 Mission

The mission of SSDD is to derive system requirements from mission requirements, develop architectures in response to the systems requirements, and design and develop systems, subsystems, equipment, and implementation technologies to achieve optimized, integrated operational space and ground systems.

1.2 Background

SSDD is currently involved in the concept definition and design phases on various advanced concepts studies and projects, which will evolve into future space, aerospace and tactical C4ISR systems. Development responsibilities extend across the entire space/ground spectrum of hardware, software and advanced technologies including digital processing, as well as systems engineering.

1.3 Scope

The purpose of this contract is to provide personnel to perform Systems Engineering Research and Development for the Space Systems Development Department Code 8100.

2.0 Applicable Documents

The Contractor shall comply with the following specifications, standards, and publications as they apply to each task. Where specified, the exact revision level of the reference listed should be used. In some circumstances there may be additional documents required not listed below. In those circumstances, the government will inform the contractor and provide one copy as necessary. Where a revision level is not included, the latest reference to the document from the Department of Defense Index of Specifications and Standards (DODISS) apply. Nothing in this document, however, supersedes applicable laws or regulations unless a specific exemption has been obtained. In the event of conflict between the referenced documents and this SOW, the requirements of this SOW apply.

2.1 Military/Department of Defense Specifications and Standards

Document Number Description

Document Number Description

AFMC Handbook Analysis of Alternatives (AoA), July 2010 http://www.prim.osd.mil/Documents/AoA_Handbook.pdf

DI-MGMT-81467 Cost/Schedule Status Report http://www.everyspec.com/DATA-ITEM-DESC-DIDs/DIMGMT/DI-

MGMT-81467_2556/

DI-MGMT-81468 Cost Financial Status Report http://www.everyspec.com/DATA-ITEM-DESC-DIDs/DIMGMT/DI-

MGMT-81468_11999/

DI-MGMT-81808 Contractor's Risk Management Plan http://www.everyspec.com/DATA-ITEM-DESC-DIDs/DIMGMT/DI-

MGMT-81808_20435/

NIST Special Publication 800- 37, Revision 2

Risk Management Framework (RMF)

SMC -STD-S-21 Technical Reviews and Audits for Systems Equipment and Computer Software, Vol. 1 and Vol. 2, 15 September 2009 http://www.everyspec.com/USAF/USAFSMC/download.php?spec=SMC-

S021_15SEP2009.021534.PDF

2.2 Non-Government Documents

2.2.1 American National Standards Institute (ANSI)/Electronic Industries Association (EIA)

Document Number Description

EIA/IS-632 Systems Engineering

EIA/IS-649 Configuration Management

(Applications for copies should be addressed to the American National Standards Institute, http://www.ansi.org, 1430 Broadway, New York, NY 10018.) and/or (Application for copies should be addressed to Electronic Industries Association, http://www.eia.gov, 2001 Pennsylvania Ave., NW, Washington, DC 20006.)

3.0 Requirements 1234 (See footnote definitions on the last page)

The following subsections specify the specific engineering tasks, objectives, and elements required for this contract.

3.1 Maritime Domain Awareness (MDA)

3.1.1 Program Management

3.1.1.1 Program Management – requires Top Secret with SCI eligibility personnel

3.1.1.1.1 The Contractor shall develop and implement a program management plan to provide systems engineering, integration, test and evaluation, and operations research and development for proof-of-concept, engineering development, and operational based systems defined in the following sub-tasks. [A002] 1,3,4

3.1.1.1.2 The contractor shall assist in the technical direction and management of the existing and future Research & Development (R&D) programs. Duties will include, but are not limited to, contractor technical direction, systems engineering, monthly status meeting support, budget development and recommendations, and presentations. 1,4

3.1.1.1.3 The contractor shall perform hardware and software configuration item updates, configuration change management, configuration status accounting, configuration audits and verification, and Configuration Management (CM )planning and management. 1,2,3,4

3.1.1.1.4 The contractor shall provide financial monitoring of the programs subcontracts to include recommendations for funding allocations, financial oversight and overall project financial management. 1,3,4

3.1.1.1.5 The Contractor shall provide a monthly Contract/Schedule Status Report (C/SSR) for all programs/projects. [A001] 1,2,3,4

3.1.1.1.6 The Contractor shall provide a quarterly Contract Funds Status Report (CFSR) for all programs/projects. [A003] 1,2,3,4

1 RDTE Funded Tasks 2 Other Procurement Funded Tasks 3 Operations & Maintenance, Navy Funded Tasks 4 Navy Working Capital Funded Tasks

3.1.1.1.7 The Contractor shall develop and submit a Contract Work Breakdown Structure

(CWBS). [A004] 1,3,4

3.1.2 Systems Engineering - requires Top Secret with SCI eligibility personnel

3.1.2.1 The Contractor shall conduct technical reviews and audits for systems assigned. [A002] 1,3,4

3.1.2.2 The Contractor shall manage configuration control of classified and unclassified documents for programs/projects. [A002] 1,3,4

3.1.2.3 The Contractor shall assist in developing and documenting systems architecture concept, plans, implementations, and operational analyses for current and planned programs/projects.

[A002] 1,3,4

3.1.2.4 The contractor shall develop and maintain concept plans, white papers, and Concept of Operations (CONOPS) documentation. 1,4

3.1.2.5 The Contractor shall perform and report the results of Analysis of Alternatives (AoA) assessments for programs/projects. [A002] 1,3,4

3.1.2.6 The Contractor shall generate program and technical review briefing slides for use in program/project reviews. [A002] 1,3,4

3.1.2.7 The Contractor shall generate and provide updates to program plans and documentation for programs/projects. [A002] 1,3,4

3.1.2.8 The Contractor shall participate in Program Requirements and Technical Reviews. The specific reviews that occur depend on the phase of development the program or project is in e.g.

concept development, engineering development, or test and evaluation. Representative reviews include: 1,3,4

• Systems Requirement Review (SRR)

• System Design Review (SDR)

• Software Specification Review (SSR)

• Preliminary Design Review (PDR)

• Critical Design Review (CDR)

• Technical Interchange Meetings (TIM)

• Test Readiness Review (TRR)

• Technical Interchange Meetings (TIM)

3.1.2.9 The Contractor shall conduct analyses of technical data packages for completeness and compliance in accordance with established program technical review readiness criteria. These data packages may include technical reports, schedules, analysis reports, design specifications, briefings, design review data packages, drawing packages, design review minutes and action item responses, test plans and procedures, and test reports. [A002] 1,3,4

3.1.2.10 The Contractor shall analyze test and evaluation planning efforts and provide recommendations for conducting test and evaluation of systems. [A002] 1,3,4

3.1.3 MULTI-INT TRACKING AND FUSION – requires Top Secret with SCI eligibilitypersonnel

3.1.3.1 The contractor shall provide technical direction for software development tasks, including the review of work products for correctness, adherence to the design concept, and for progress in accordance with established schedules. 1,3,4

3.1.3.2 The contractor shall support algorithm review, analysis, maintenance and upgrades, including engineering efforts, data analysis and maintenance efforts, and performance measurements and analysis. Long-term trending shall be performed while data remains available for processing. Anomalies detected during performance measurements and analysis review shall be reported to the government lead. 1,3,4

3.1.3.3 The contractor shall design software tools and subsystems to support software reuse and domain analyses, and shall manage software development and support use of formal specifications, data flow diagrams and other accepted design techniques and Computer Aided Software Engineering (CASE) tools. 1,3,4

3.1.3.4 The contractor shall implement and manage Oracle Enterprise Edition Relational Database Management System (RDBMS) along with Oracle label security, Oracle real application cluster and Oracle partitioning options (i.e., Structured Query Language (SQL) programming). 1,3,4

3.1.3.5 The contract shall support the following operating systems: Red Hat Linux 6.5/6.6/7.x and OEL 6.5/6.6, Community ENTerprise Operating System (CENT OS), and beyond. 1,3,4

3.1.3.6 The Contractor shall develop data fusion and geographic tracking algorithms for multiple situation awareness data types. [A002] 1,3,4

3.1.3.7 The Contractor shall develop new code/algorithms and modify current code/algorithms to increase quality of data fusion and accuracy of geolocation tracking. 1,4

3.1.3.8 The contractor shall support the development and tuning of track correlation algorithms, tracker algorithms enhancements, database tuning modifications, enhancements to current alarming capabilities, and performance reports. 1,4

3.1.3.9 The contractor shall provide support the evaluation of mission thread effectiveness via detailed systems engineering and signals analysis, support the development of new mission threads and perform analysis of alternate detection algorithms. 1,4

3.1.3.10 The contractor shall develop and maintain software baselines developed in Java, C and other programming languages. 1,2,3,4

3.1.3.11 This effort will include system capability reviews, engineering, software support, developing processing and fusion algorithms, modifying existing code, and storing all code changes in a CM data base. 1,4

3.1.3.12 The contractor shall develop and maintain the architecture, maritime data feeds, maritime schedule information, and web extractor software that will be hosted on NRL provided hardware suite, (Intelligence Community (IC) or Department of Defense (DoD) Cloud, or commercially provided Government Cloud such as Amazon Web Services (AWS). 1,3,4

3.1.3.13 The contractor shall also provide Operations and Maintenance (O&M) support (echelon

2) for existing data feeds. 3,4

3.1.3.14 The contractor shall analyze the output data accuracy and correct any issues that arise.

The contractor shall implement a long-term online data archive. The archive shall be able to respond to queries for items that may include, but are not limited to, maritime, airborne, land, and space domain positions, schedule information, and metadata. 3,4

3.1.3.15 The contractor shall provide a web service to enable users to query for historical data from the data archive. 3,4

3.1.3.16 The contractor shall integrate Open Source Schedule data. 1,3,4

3.1.4 DATA TAGGING AND CHARACTERIZATION– requires Top Secret with SCI eligibility personnel

3.1.4.1 The Contractor shall research and develop automated electronic emission pattern data tagging algorithms for detection and modeling of selected electronic emission patterns. [A002] 1,3,4

3.1.4.2 The contractor shall provide algorithm and software development, integration, migration and fielding to meet the objectives. 1,3,4

3.1.4.3 The contractor shall analyze the system development and design, define the problem, and develop system requirements and program specifications. 1,3,4

3.1.4.4 The contractor shall design software tools and subsystems to support software reuse and domain analyses, and manage software development and support using formal specifications, data flow diagrams and other accepted design techniques and Computer Aided Software Engineering (CASE) tools. 1,3,4

3.1.5 DATA ANALYSIS – GEOINT, SIGINT, OSINT

3.1.5.1 DATA ANALYSIS - requires Top Secret with SCI eligibility personnel

3.1.5.1.1 The Contractor shall perform data analysis of system functionality and performance using technical assessments and engineering analyses to identify, recommend, and implement solutions for critical design or performance deficiencies. 1,3,4

3.1.5.1.2 The contractor shall identify and report deficiencies identified as part of analyzing system functionality and performance. 3,4

3.1.5.1.3 The contractor shall perform short-term engineering analyses and quick reaction studies to support data analysis efforts. 3,4

3.1.5.1.4 The contractor shall assess data analysis products and functionality; prepare training documentation, train operators, and support ongoing program deliveries, demonstrations and customer presentations. 1,3,4

3.1.5.1.5 The contractor shall identify, analyze or develop decision support, simulation or modeling activities to support data analysis of system performance. 1,3,4

3.1.5.1.6 The contractor shall perform data analysis of system survivability analyses. 1,3,4

3.1.6 CLOUD TECHNOLOGY

3.1.6.1 CLOUD TECHNOLOGY - requires Top Secret with SCI eligibility personnel

3.1.6.1.1 The contractor shall coordinate with various Government agencies to develop, test, integrate and deploy these capabilities. 1,2,3,4

3.1.6.1.2 The contractor shall provide systems engineering, design, and planning support for the transition of capabilities into the IC and DoD Cloud Architecture. 1,3,4

3.1.6.1.3 The contractor shall conduct technical exchange meetings as required to define system requirements and architectural changes necessary to align systems with the IC and DoD Cloud Architecture. 1,3,4

3.1.6.1.4 The contractor shall research and engineer potential techniques for transitioning Oracle RDBMS based data stores to the IC and DoD Cloud data layer. 1,4

3.1.6.1.5 The contractor shall provide data engineering support for the definition and implementation of the Object Models (such as Unified Object Model, Generalized Entity Model and others) within the IC and DoD Cloud architecture. 1,4

3.1.6.1.6 The contractor shall support ongoing engagement with evolving Cloud Architectures and technology and establish the transition path for existing capabilities into those architectures.

These Cloud Architectures will be hosted on hardware suite, IC or DoD Cloud (Cloud Computing Services (C2S)), or commercially provided Government Cloud such as Amazon Web Services (AWS). 1,2,4

3.1.6.1.7 The contractor shall develop the design, system scope, interaction and layout of the Widget Suite and underlying data access web services to design analysis capabilities within the Ozone Widget Framework or other presentation frame works. 1,4

Contract #N00173-xx-x-xxxx

3.1.6.1.8 The contractor shall design and engineer a working user interface prototype of the Widget Suite that leverages existing legacy web services and RDBMS systems. 1,4

3.1.7 SOFTWARE DEVELOPMENT

3.1.7.1 SOFTWARE DEVELOPMENT- requires Top Secret with SCI eligibility personnel

3.1.7.1.1 The contractor shall provide system level integration test plans and procedures. 1,4

3.1.7.1.2 The contractor shall review and document both technical approaches as well as Level of Effort (LOE) required for submitted Discrepancy Reports (DR). 3,4

3.1.7.1.3 The contractor shall modify existing source code or generate new source code to implement desired changes upon approval by the Government Configuration Control Board

(CCB). 3,4

3.1.7.1.4 The contractor shall participate in unit level testing to demonstrate changes resulted in the desired operationally relevant functionality necessary to perform a cadre of maritime related missions. 3,4

3.1.7.1.5 The contractor shall conduct hardware and software design reviews. 1,3,4

3.1.7.1.6 The contractor shall establish and execute the overall software test and verification planning, execution, and reporting efforts. The testing will include Integration & Test (I&T), Unit Testing, and System Testing. 1,4

3.1.7.1.7 The contractor will follow the intentions of the software development processes called out in ISO IEC 12207-2008(E), Standard for Information Technology - Software life cycle processes, which provides guidance on performing life cycle for software that is part of a larger systems, as well as stand-alone software products and services; however, compliance to this standard is not mandatory. 1,3,4

3.1.7.1.8 The Contractor shall generate and update subsystem software development specifications for programs/projects. [A002] 1,3,4

3.1.7.2 SOFTWARE DEVELOPMENT- does not require Top Secret with SCI eligibility personnel

3.1.7.2.1 The contractor shall review and document both technical approaches as well as Level of Effort (LOE) required for submitted Discrepancy Reports (DR). 3,4

3.1.7.2.2 The contractor shall modify existing source code or generate new source code to implement desired changes upon approval by the Government Configuration Control Board

(CCB). 3,4

3.1.7.2.3 The contractor shall participate in unit level testing to demonstrate changes resulted in the desired operationally relevant functionality necessary to perform a cadre of maritime related missions. 3,4

3.1.7.2.4 The contractor shall develop and maintain existing software baselines in Java, C and other programming languages. 1,3,4

3.1.7.2.5 The contractor shall perform engineering and software support for ongoing and enhanced Web Tier capabilities. 1,3,4

3.1.8 INFRASTRUCTURE - requires Top Secret with SCI eligibility personnel

3.1.8.1 The contractor shall support manage and enhance computer system and network technology implementations. 2,4

3.1.8.2 The contractor shall perform routine maintenance of installed equipment; manage access through account creation scripts; and maintain access for various Wide Area Networks and Local Area Networks. Access to the Infrastructure is done via thin clients (no individual workstations or personal computers (PCs). 1,2,3,4

3.1.8.3 The contractor shall implement and manage Oracle Database products including Oracle 12c, SQL developer and 12c cloud console and specifically in the installation of: Oracle Enterprise Linux on bare metal servers; Oracle 12c software on bare metal, and Real Application Clusters (RAC) and Exadata servers. 1,3,4

3.1.8.4 The contractor shall support a suite of hardware comprised of LINUX, Oracle Enterprise Linux and Windows (Limited) operating systems. The network infrastructure consists of virtualized systems and bare metal servers. 1,3,4

3.1.8.5 The contractor shall analyze/resolve Local Area Networks (LAN) / Wide Area Networks (WAN) network protocol issues. 1,3,4

3.1.8.6 The contractor shall support a variety of projects that range from development environments to high availability environments. 1,3,4

3.1.8.7 The contractor shall administer and configure servers using LINUX, VMWARE and/or RHEV, Enterprise Identity Management tools (LDAP, IPA, Active Directory (AD), etc.). 1,3

3.1.8.8 The contractor shall communicate with a variety of hardware and software vendors to receive quotes and resolve infrastructure challenges. 2,4

3.1.8.9 The contractor shall provide hands-on support, maintenance, performance monitoring, and optimization of 50 plus servers in a thin client environment. 1,3,4

3.1.8.10 The contractor shall perform system administration, system hardening and network administration on computer systems at NRL. This will include maintaining accounts, updating operating systems, installing patches, and operations and maintenance of all server-based and thin client networks. 1,3,4

3.1.9 Information Assurance - requires Top Secret with SCI eligibility personnel

3.1.9.1 The contractor shall support the DoD information assurance certification and accreditation process in accordance with NISP SP 800-37 Rev. 2, Risk Management Framework

(RMF). 1,3,4

3.1.9.2 The Contractor shall prepare for and conduct information assurance certification testing.

[A002] 1,3,4

3.1.9.3 The contractor shall apply Information Systems Security Engineering (ISSE) and Information Assurance (IA) principles, in accordance with current DoD and Intelligence Community Security directives, regulations, standards guidance security technical implementation guides and industry security best practices, into the Software / System Development Life Cycle (SSLC) process. 1,3,4

3.1.10 Common Operating Picture (COP) / Common Intelligence Picture (CIP) - requires Top Secret with SCI eligibility personnel

3.1.10.1 The contractor shall develop COP applications to generate a single identical display of relevant (operational) information (e.g. position of own troops and enemy troops, position and status of important infrastructure such as bridges, roads, etc.) shared by more than one Command. The COP applications will facilitate collaborative planning and assists all echelons, incident responders to achieve situational awareness. 1,3,4

3.1.10.2 The contractor shall develop Web Applications, visualization tools, Human Machine Interface analysis and data latency metrics to display the COP. 1,4

3.1.10.3 The contractor shall design and develop CIP applications to generate a single display of relevant Intelligence information that can be shared by more than one group, agency, command or organization. The CIP will bring together a variety of multi-INT capabilities, data and displays to provide a short and long term intelligence view of an Area of Responsibility (AOR) or Situation. 1,4

3.1.11 Object Management as a Service (OMAAS) / Object Based Production (OBP) -requires Top Secret with SCI eligibility personnel

3.1.11.1 The contractor shall implement an object based production approach that delivers consumers’ aggregated information reflecting a real world object such as a vessel, airplane, facility, entity, etc. The contractor shall ensure the Object Management approach aggregates objects in a service framework to allow for collaboration at a regional/worldwide level. 1,4

3.1.11.2 The contactor shall develop an object aggregation algorithm (with or without relational database technology) to support NRL’s research and development into these new concepts. 1,4

3.1.11.3 The contractor shall develop Web applications for display and operator interaction. 1,4

4.0 Special Requirements

This section describes the special requirements for this effort. The following sub-sections provide details of various considerations on this effort.

4.1 Security

4.1.1 The Contractor shall comply with the NRL Occupational Safety and Health Manual, 5100.13C, and the NRL Security Manual, 5510.40E with respect to all Contractor and subcontractor employees located at NRL.

4.1.2 The Contractor shall assist SSDD in its on-going safety program, which entails taking a proactive approach towards providing a safe and healthy workplace. The Contractor shall provide expertise and support with respect to: compliance with Government safety provisions, on-site identification and elimination of safety and environmental hazards, facilitating the correction of safety and environmental deficiencies reported by building monitors and/or identified during the annual NRL Safety and Environmental Inspection(s), and to otherwise provide supplementary safety training and educational support, as needed.

4.1.3 Contractor personnel shall possess a favorably completed DoD investigation and a final DoD granted Top Secret security clearance with the eligibility of SCI at time of proposal submission for all tasks that require personnel with Top Secret with SCI eligibility, and maintain that level of classified access for the life of the contract. Detailed security requirements are delineated in the issued DD 254s relevant to this contract. The Contractor shall ensure that all classified material is handled in accordance with the issued DD 254, the National Industrial Security Program Operating Manual (NISPOM) (DoD 5220.22M and all NRL and applicable Security Program Guides/Directives.

4.1.4 Contractors issued a DoD interim secret security clearance may ONLY work on unclassified tasks in accordance with this contract SOW. No classified access will be authorized.

Unclassified Information Assurance (IA) or Information Technology (IT) positions are NOT authorized with a DoD issued interim secret clearance.