DRAFT Structured Data Modeling PWS.pdf

PERFORMANCE WORK STATEMENT

Contract: TBD

Title: Structured Data Modeling of Navy Systems

Date: 9/4/2018

1.0 SCOPE:

Space and Naval Warfare Systems Center (SPAWARSYSCEN) Pacific, Code 55370, has been tasked to provide structured data modeling of US Navy afloat and ashore platforms and associated cyber operations analysis. The effort requires the data capture, modeling, and analysis of Navy Integrated systems, network, data, activity and operations.

1.1 BACKGROUND:

SPAWARSYSCEN Pacific is part of the Model Based Systems Engineer (MBSE) team which was responsible for development of an integrated modeling environment that reduces costs and risks associated with developing and modernizing communications components, systems and system of systems. The model addressed one of the biggest challenges many Navy program offices face today and that is how to quickly integrate commercial off-the shelf technology and modernize the Navy's current technologies to work with already existing systems.

The MBSE team documented more than 18,000 components and interfaces within the submarine communications realm and entered the data into a computer based integrated modeling environment where they can analyze the effects of adding, taking away or changing a component or system.

2.0 APPLICABLE REFERENCE DOCUMENTS:

The following documents are for guidance only.

2.1 DoD Manual 8570.01-M Change 3 – Information Assurance Workforce Improvement Program.

2.2 DoD Directive 8570.01 – Information Assurance Training, Certification, and Workforce Management, 15 Aug 04

2.3 DoDI 8500.01 -Cybersecurity, 14 March 2014

2.4 DODI 8500.2 Information Assurance (IA) Implementation, 6 Feb 03

3.0 REQUIREMENTS:

The contractor shall perform the following tasks in accordance with this PWS issued by SSC Pacific.

3.1 SYSTEMS DATA CAPTURE AND LOGICAL DATA MODEL DEVELOPMENT:

3.1.1 Systems Data Capture and Logical Data Model Development (PEO Carriers)

3.1.1.1 The contractor shall work with stakeholders (Program Office personnel, US Fleet Cyber Command, National Security Agency, as well as NAVSEA and SPAWAR headquarters organizations) to define and decompose requirements for a logical data model for the capture of Navy afloat and ashore integrated systems.

3.1.1.2 The framework shall establish methodologies for capturing and managing data associated with complex integrated Hull, Mechanical, and Electrical (HM&E) and C4I systems.

3.1.1.3 The contractor shall establish a logical data model enabling and enforcing concordance and mapping between system, subsystem, interface, mission thread, process and other data sets.

3.1.1.4 The model shall generate outputs that support data call responses, information flow analyses, operations analyses, performance evaluations, mission thread analyses, cybersecurity assessments and engineering change evaluations.

3.1.1.5 The contractor shall work with stakeholders as required to conduct the systems and data research required to support model development and sustainment.

3.1.1.6 The contractor shall ensure the model supports engineering change and configuration management processes.

3.1.1.7 The contractor shall research the application of the MBSE to acquisition, engineering and logistics support applications and develop associated meta-data management and reporting capabilities.

3.1.2 Systems Data Capture and Logical Data Model Development (PEO IWS)

3.1.2.1 The contractor shall work with stakeholders (Program Office personnel, US Fleet Cyber Command, National Security Agency, as well as NAVSEA and SPAWAR headquarters organizations) to define and decompose requirements for a logical data model for the capture of Navy afloat and ashore integrated systems.

3.1.2.2 The framework shall establish methodologies for capturing and managing data associated with complex integrated Hull, Mechanical, and Electrical (HM&E) and C4I systems.

3.1.2.3 The contractor shall establish a logical data model enabling and enforcing concordance and mapping between system, subsystem, interface, mission thread, process and other data sets.

3.1.2.4 The model shall generate outputs that support data call responses, information flow analyses, operations analyses, performance evaluations, mission thread analyses, cybersecurity assessments and engineering change evaluations.

3.1.2.5 The contractor shall work with stakeholders as required to conduct the systems and data research required to support model development and sustainment.

3.1.2.6 The contractor shall ensure the model supports engineering change and configuration management processes.

3.1.2.7 The contractor shall research the application of the MBSE to acquisition, engineering and logistics support applications and develop associated meta-data management and reporting capabilities.

Task Status Reports: For each task the contractor shall provide monthly progress and status reports. (CDRL A001)

3.2 OPERATOR-MACHINE MODELING INTERFACE

3.2.1 Operator-Machine Modeling Interface (PEO Carriers)

3.2.1.1 The contractor shall research the requirements for and support the application of a collaborative data modeling environment for both stand-alone users, those without access to SIPR RDTE (SWAN), and remote/enterprise access users at multiple classifications.

3.2.1.2 The contractor shall research and generate graphical user interfaces that support access to and reporting from a data modeling environment. The interfaces shall support access from both local and remote sites (probable sites include but not limited to DC area, Norfolk and Philadelphia), and for users with both novice and advanced model interaction capabilities.

3.2.1.3 The contractor shall research and generate the data conditioning functionality necessary to push and pull data to/from network discovery applications, simulation tools, system vulnerability scanning tools and external databases.

3.2.2 Operator-Machine Modeling Interface (PEO IWS)

3.2.2.1 The contractor shall research the requirements for and support the application of a collaborative data modeling environment for both stand-alone users, those without access to SIPR RDTE (SWAN), and remote/enterprise access users at multiple classifications.

3.2.2.2 The contractor shall research and generate graphical user interfaces that support access to and reporting from a data modeling environment. The interfaces shall support access from both local and remote sites (probable sites include but not limited to DC area, Norfolk and Philadelphia), and for users with both novice and advanced model interaction capabilities.

3.2.2.3 The contractor shall research and generate the data conditioning functionality necessary to push and pull data to/from network discovery applications, simulation tools, system vulnerability scanning tools and external databases.

Task Status Reports: For each task the contractor shall provide monthly progress and status reports. (CDRL A001)

3.3 CYBER OPERATIONS ANALYSIS

3.3.1 Cyber Operations Analysis (PEO Carriers)

3.3.1.1 The contractor shall develop capabilities within a systems model to capture and inter-relate vulnerabilities and cyber operations (e.g. to evaluate mission impacts).

3.3.1.2 The contractor shall research and develop modeling operations that facilitate end-to-end cyber effects analysis, cyber compromise impact analysis and generate reports to support certification and other risk assessments.

3.3.1.3 The contractor shall research methods to condition data for export to cyber situational awareness tool suites.

3.3.2 Cyber Operations Analysis (PEO IWS)

3.3.2.1 The contractor shall develop capabilities within a systems model to capture and inter-relate vulnerabilities and cyber operations (e.g. to evaluate mission impacts).

3.3.2.2 The contractor shall research and develop modeling operations that facilitate end-to-end cyber effects analysis, cyber compromise impact analysis and generate reports to support certification and other risk assessments.

3.3.2.3 The contractor shall research methods to condition data for export to cyber situational awareness tool suites.

Task Status Reports: For each task the contractor shall provide monthly progress and status reports. (CDRL A001)

4.0 SECURITY:

The work performed by the contractor at SPAWARSYSCEN will include access to unclassified and up to SECRET data and information. Contractor personnel are required to have a minimum level of a Secret Clearance in accordance with the DD Form 254, Contract Security Classification specification for access to classified equipment and/or spaces. The contractor will be required to attend meetings classified up to Secret level.

The Contractor will require access to Communications Security and Secure Internet Protocol Router Network (SIPRNet).

As required by National Industrial Security Program Operating Manual (NISPOM) Chapter 1, Section 3, contractors are required to report certain events that have an impact on: 1) the status of the facility clearance (FCL); 2) the status of an employee’s personnel clearance (PCL); 3) the proper safeguarding of classified information; 4) or an indication that classified information has been lost or compromised. Contractors working under SPAWARSYSCEN Pacific contracts will ensure information pertaining to assigned contractor personnel are reported to the Contracting Officer’s Representative

(COR)/Technical Point of Contact (TPOC), the Contract Specialist, and Security Department in addition to notifying appropriate agencies such as Cognizant Security Agency (CSA), Cognizant Security Office (CSO), or Department of Defense Central Adjudication Facility (DODCAF) when that information relates to the denial, suspension, or revocation of a security clearance of any assigned personnel; any adverse information on an assigned employee’s continued suitability for continued access to classified access;

any instance of loss or compromise, or suspected loss or compromise, of classified information; actual, probable or possible espionage, sabotage, or subversive information;

or any other circumstances of a security nature that would affect the contractor’s operation while working under SPAWARSYSCEN Pacific contracts.

4.1 OPERATIONS SECURITY:

OPSEC is a five step analytical process (identify critical information; analyze the threat;

analyze vulnerabilities; assess risk; develop countermeasures) that is used as a means to identify, control, and protect unclassified and unclassified sensitive information associated with U.S. national security related programs and activities. All personnel working under this task may be required to handle, produce or process Critical Information or Critical Program Information, and therefore, all Contractor personnel must practice OPSEC. All work is to be performed in accordance with DoD OPSEC requirements, and in accordance with the OPSEC attachment to the DD254.

5.0 TRAVEL: 2-trips to Washington, DC and 2-trips to Newport News, VA annually

6.0 GOVERNMENT FURNISHED INFORMATION/PROPERTY: None

8.0 PLACE OF PERFORMANCE:

Contractor performance will be at SPAWARSYSCEN Pacific.

9.0 PERFORMANCE REQUIREMENTS SUMMARY:

Performance Objective Performance Standard

3.1 Systems Data Capture

and Logical Data Model Development Support

Systems Data Capture and Logical Data Model Development Support tasks are timely, accurate, and performed in accordance with the standards and references of the associated PWS. Services will be measured 98% compliant, at a minimum, with all PWS and CDRL requirements. The Government will evaluate (1) the quality of the services and deliverables in terms of the contractor’s compliance with the performance standard, (2) the contractor’s timeliness with respect to task order, milestones, and delivery schedules, (3) the contractor’s cost control in terms of effectiveness in forecasting, managing, and controlling cost, and (4) the contractor’s relations in terms of timeliness, completeness, quality of problem identification and corrective action, and reasonable and cooperative behavior.

3.2 Operator-Machine

Modeling Interface Support

Operator-Machine Modeling Interface Support tasks are timely, accurate, and performed in accordance with the standards and references of the associated PWS. Services will be measured 98% compliant, at a minimum, with all PWS and CDRL requirements.

The Government will evaluate (1) the quality of the services and deliverables in terms of the contractor’s compliance with the performance standard, (2) the contractor’s timeliness with respect to task order, milestones, and delivery schedules, (3) the contractor’s cost control in terms of effectiveness in forecasting, managing, and controlling cost, and (4) the contractor’s relations in terms of timeliness, completeness, quality of problem identification and corrective action, and reasonable and cooperative behavior.

3.3 Cyber Operations

Analysis Support

Cyber Operations Analysis Support tasks are timely, accurate, and performed in accordance with the standards and references of the associated PWS. Services will be measured 98% compliant, at a minimum, with all PWS and CDRL requirements. The Government will evaluate (1) the quality of the services and deliverables in terms of the contractor’s compliance with the performance standard, (2) the contractor’s timeliness with respect to task order, milestones, and delivery schedules, (3) the contractor’s cost control in terms of effectiveness in forecasting, managing, and controlling cost, and (4) the contractor’s relations in terms of timeliness, completeness, quality of problem identification and corrective action, and reasonable and cooperative behavior

9.0 PERFORMANCE REQUIREMENTS SUMMARY: