1__Performance_Work_Statement_for_IDIQ.pdf

PERFORMANCE WORK STATEMENT (PWS)

As of 14 May 2019

Defense Collaboration Services (DCS)

Solicitation Number HC1047-19-R-4005

1. Contracting Officer’s Representative (COR)

See section H1 of contract “Points of Contact”

2. Contract or Title. Defense Collaboration Services (DCS) Engineering and Sustainment

Support.

3. Background. Defense Information Systems Agency is an information technology services provider and delivers information sharing capabilities to the DoD warfighters and mission partners via a globally accessible enterprise information infrastructure. As part of this mission, DISA provides Defense Collaboration Services (DCS) as an unified real time enterprise collaboration capability that delivers secure web conferencing and instant messaging services on

Secret Internet Protocol Router Network (SIPRNet), Sensitive but Unclassified Internet Protocol

Network (NIPRNet), and internet (via NIPRNet). This critical enterprise service regularly serves

150K monthly web conference users and 19K concurrent daily chat users on NIPRnet. With

DCS, DISA promotes and fosters a Joint information collaborative environment with a high quality and cost effective services to improve workflow productivity. DCS capabilities are built on open source solution and provides:

o Collaboration Portal: Social Media and collaboration features, links and training info, and real time communications via messages o Web Conferencing: Slide Show Presentations, Integrated Voice, Web Conference

Recordings, Desktop Sharing, Multi-user Whiteboarding, closed captioning, Text

Chat, Polling and Voting, o Instant Messaging (Desktop and Mobile Apps): Persistent chat rooms, Group Chat, One on One chat, Presence, Search, Chat Log access, and administration functions

The hosting infrastructure is located in MilCloud 1.0 in two Defense Enterprise Computing

Centers with Multi-site deployment arrangement. DCS is dependent on enterprise shared services and infrastructure for reliability and availability. The DCS service is designed to integrate with other DoD enterprise services including F5, OCSP, DNS, EASF, NTP and other services. Any individual with a Common Access Card (CAC) or Public Key Infrastructure (PKI) hard token can start a meeting and registration is not required. The moderator can allow guest user access for those without CACs to enter web conference meetings.

DCS has achieved Full Operational Capability (FOC) and is in sustainment. The DCS PMO will continue to utilize DevOps methodologies to deliver infrastructure, tech refreshes, and customer requirements to ensure DCS viability, reduce costs and optimize services.

4. Objectives: The objective of this contract is to provide DCS engineering and sustainment support to improve and maintain the service. DCS support contract includes managing and maintaining the applications, servers and supporting infrastructure on both the DISA NIPRNet and SIPRNet. The contract personnel should have requisite knowledge of DoD enterprise architectures, networks, frameworks, systems, process, and data requirements. Additionally, the technical contractual personnel should have expert knowledge of Web services, Open source components and trends, DoD integration and networks, DoD engineering and sustainment procedures and processes to deliver a real time enterprise collaborative service to a large customer base.

This includes continuously assessing the DCS security posture leading to and maintaining a current security authorization that meets the criteria of the DoD Risk Management Framework

(RMF). This PWS delineates Contractor support in assuring the DCS information system, technology and components are secured according to the applicable security requirements, directives, and regulations and meet all applicable DoD and Non-DoD Information Assurance

(IA) security requirements in accordance with (IAW) the DoDD 8140, DoD 8510 (RMF), and

DoD 8570.01-M. Because of the complexity of DCS engineering and sustainment functions, Capability Maturity Model Integration (CMMI) Services (CMMI-SVC) Level 3 (or better) and

Capability Maturity Model Integration (CMMI) Development (CMMI-DEV) Level 3 (or better) are required.

With rapidly evolving technologies, budget uncertainty, constant customer requirements, and fierce competition, DISA needs to manage these areas closely and continuously seek new, innovative, and effective ways to optimize and improve the DCS service. To better serve DOD and its Mission Partner customers, DCS program office has to continue DevOps methodologies to manage infrastructure deployments, technology refreshes, and customer requirements.

5. Scope: The scope of this contract includes engineering, development, integration, testing, cybersecurity, implementation, customer engagement, training, marketing, and sustainment functions to deliver DCS to our customer base. The contract support requires architecting, engineering, developing, integrating, enhancing, testing, implementing and sustainment functions.

Additionally, contractor support requires infrastructure deployments, technology refreshes, and customer requirements. The contractor has to support transition to latest cloud infrastructures to obtain IT efficiencies and cost savings. Within infrastructure, there are numerous opportunities for improvement with shared services, open source component/server optimizations, containerization, and cross-site interactions. The contract support must anticipate and deliver technology refreshes to ensure DCS usability and viability in the future with HTML5, Core

Updates (portal, WC, Chat), and Open source components. In addition, DCS PMO must manage customer expectations and deliver requirements for the customers including unified capabilities, Mobility, Enterprise chat federation, Disconnected Intermittent Low Bandwidth, and Regional

DCS.

DCS is a collection of multiple components and management tools utilized to develop, manage, and optimize the performance of DCS. Below are a list of the components, protocols, standards, tools, and technologies used for DCS:

Open Source Software Components

BigBlueButton MySQL

Swift Redis

Openfire Server Red5

Elasticsearch, Logstash, Kibana (ELK Stack) NGINX

FreeSWITCH Apache Tomcat

LibreOffice Java

Tigase Messenger (iOS & Android) AG Projects (SylkServer) etc.)

SSH, SFTP Clients (e.g. PuTTY)

Commercial Components

RedHat Enterprise Linux (RHEL 7 or higher) Nagios XI

F5 Load Balancers Firewalls (e.g. Juniper, Cisco)

VMWare (Virtual Data Centers) Active Directory / Domain Controllers

Remedy Management System

Ribbon (Sonus) Session Border Controller

(SBC) Software Edition (SWe)

Microsoft Visio Microsoft Project

Microfocus Fortify

Protocols, Standards, Infrastructure and Other Technologies

Digital Server Certificates Commercial Cloud Services (e.g. Amazon

Web Services, etc.)

Enterprise Chat Federation HTML5

Advanced knowledge of DoD authentication and authorization infrastructures (i.e. PKI)

Active Directory / Domain Controllers

6. Performance Requirements.

6.1 Task Area 1 - Contract Oversight Reporting Requirements

Contractor shall provide a weekly status report for the tasks and subtasks by monitoring for quality assurance, progress/status reporting and program reviews applied to the task order. The contractor shall update the Contract Management Plan provided at time of proposal submission, describing the technical approach, organizational resources and management controls to be employed in each task order to meet performance and schedule requirements when a new task order is placed. The contractor shall be able to deliver an Integrated Master Schedule (IMS) to define the work projections throughout to the contract execution updated monthly.

Deliverable(s):

PWS

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.1 Weekly Status

Report

The report shall include

Assigned projects of each staff member and the sections described as follows:

1. Tasks for projects detailing the task name, accomplishments description, and the responsible team members assigned to complete the task and projected start and end dates.

2. Issues and action items detailing task name, description of issue/action

3. Upcoming Activities

MS Project or as specified by government

Standard

Distribution*

Every Friday

6.1 Updates to the

contracts

Management

Plan

Update the Contract

Management Plan to include new Task

Order management.

Contractor-

Determined

Format

Standard

Distribution*

Draft 15 days after task order award.

Final 30 days after task order award, updated annually.

6.1 Integrated

Master

Schedule

(IMS)

Prepare an Integrated

Master Schedule (IMS) to define the work projections throughout

Task Order (TO) execution

MS Project Standard

Distribution*

Weekly: COB

Friday

** Note ** For contractor’s planning purposes these deliverables are being used as example.

The deliverables will be task order specific. The Government reserves the right to add or delete deliverables based on task order need.

6.2 Task Area 2 - DCS Engineering Support

The task area is for DCS Engineering and architecture support for current and proposed technical changes to include infrastructure, tech refresh, customer requirements, and sustainment functions. The contractor support engineers and architects transition to latest cloud infrastructures. Additionally, the support optimizes infrastructure with shared services, open source component/server optimizations, containerization, and cross-site interactions. The contract support delivers technology refreshes Core Updates (portal, WC, Chat), and Open source components. The contract support delivers customer requirements for unified capabilities. Additionally, this task area will involve engineer and architect sustainment tasks and its impacts to DCS infrastructure and application.

This task area includes engineering support for prototyping, open source technology evaluations, government consultation, and advanced troubleshooting of the existing DCS application environment. The capabilities must be delivered on specific timelines to meet the program requirements to provide cutting edge collaboration capabilities to DoD and mission partners. For sustainment, the requirements can include:

The contractor shall provide engineering troubleshooting for DCS Virtual Server issues, DCS application issues, Infrastructure as a Service (IaaS) issues, IA /security issues, and supporting infrastructure and enterprise-level NIPRNet/SIPRNet issues. Support prototyping and testing for upgrades released as well as new open source software. Shall test upgrades, updates, or break fixes. Evaluating future systems requirements or enhancements. Develop & update DCS architecture documentation. Document procedures and maintain repository for DCS Engineering documentation. Deploy an engineering team to the servicing DECC for coordination, and engineering TEMs.

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.2 Weekly

Activity

Reports

Provide a weekly activity report documenting open work issues, current work efforts, and future work efforts.

Contractor-

Determined

Format

Standard

Distribution*

Weekly

6.2 DCS

Architecture

Documentation

Develop & Update

DCS Architecture documentation.

MS Word and

MS Visio and

PDF

Standard

Distribution*

Monthly

6.2 DCS

Engineering

Document

Repository

Maintain and Update for DCS Engineering documentation

DEPS

Document

Repository &

DCS System

Wiki (DEPS)

Standard

Distribution*

Weekly

6.2 DCS System

Engineering

Testing and

Validation

Testing and Validation

Process & Plan for

DCS Systems

Contractor-

Determined

Format

Standard

Distribution*

Draft 15 days prior to each architecture change and final 30 days

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date after each architecture change

6.2 System OV-1

and SV 1

Operational View (OV-

1) and System View

(SV-1) of DCS System

Architecture

MS Visio and

PDF

Standard

Distribution*

Draft 15 days prior to each architecture change and final 30 days after each architecture change

6.2 Software Forge

Usage Plan

Plan to leverage

Software Forge (or equivalent as designated by the

Government) to maintain requirements, defects, task, software, playbooks, and executables and fully leverage all capabilities provided by Software

Forge

Contractor-

Determined

Format

Standard

Distribution*

Thirty (30) days after task order start and updated annually.

6.2 Software Forge

Updates

Software Forge

Software

Forge

Artifacts, Software

Code, Executables, Playbooks

Per Software

Forge Format

Standard

Distribution*

Weekly

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.3 Task Area 3 - DCS Tier 3 Support

This task area provides Tier 3 support for the DCS application. The contractor shall be responsible for defined Tier 3 support in task orders. The contractor shall interface with the supporting Tiers (2 and 4) in an effort to assess the infrastructure and resolve the respective incident or problem tickets. The annual historical average of incident tickets is 380 incident tickets with a monthly closure of on average of 20 tickets per month. To support this task area the contractor shall attain and maintain IT-1 qualification. The contractor shall utilize the DISA

Global Ticket Management System (GTMS) on the SIPRNet, and IT Service Management

(ITSM) on the NIPRNet. The contractor shall be responsible for accessing, reviewing, updating, and annotating all Tier 3 Incident Tickets and Problem Tickets within the defined ITSM/GTMS metrics for incident priority. The contractor shall ensure Tier 3 tickets are either closed, escalated to Tier 4, or de-escalated to Tier 2.

Task#

Deliverable

Title

Minimum

Requirements

Format Distributio n/ Copies

Submission

Due Date

6.3 Weekly

Tier 3

Ticket

Report

Provide the

Government a Weekly

Tier 3 Ticket Report that identifies the:

Total Incident

Tickets in the Tier 3

Queue

Total Problem

Management

Tickets in the Tier 3

Queue and the number of associate incident Tickets.

Total Number of

Incidents Tickets

Opened

Total Incident

Tickets that are older than 10 working days old

Total Number of

Incidents Tickets

Updated

Total Number of

Incidents Tickets

Escalated to Tier 4

Total Number of

Incidents Tickets deescalated to Tier

Total Number of

Incidents Tickets

Closed

Contractor-

Determined

Format

Standard

Distribution

Weekly

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.4 Task Area 4 - DCS Training

This task area provides live and recorded training to the DCS community. Training is conducted primarily on NIPRNet using DCS. The training sessions average 40 participants for DCS Basic

Training, 25 for DCS Advanced, and 60 for Swift and Transverse Chat Client training. The contractor shall develop, present, and update the DCS live training and the DCS recorded video presentations and maintain training scripts to develop DCS Training Videos. The contractor shall record and make available DCS Basic, Advances, and Chat Client training videos in the

Government-designated Visual Information facilities.

Deliverables(s):

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.4 Training

presentations in MS

PowerPoint

(Basic and

Advanced

Training) for all DCS capabilities.

Develop, update, and maintain currency of all DCS Training

Presentations.

MS

PowerPoint

Standard

Distribution* updated quarterly; as requested

6.4 Presentation

scripts for

Audio/Video recordings of

Basic, Advanced, and

Chat Client

Training

Develop, update, and maintain training scripts to develop DCS

Training Videos

MS Word Standard

Distribution* updated quarterly; as requested

6.3 Weekly

Service

Operational

Report

Detailed summary of new and ongoing troubleshooting status report (customer, issue, resolution)

Contractor-

Determined

Format

Standard

Distribution

Weekly

6.3 Software

Incidents, technical issues, and updates via

Format

Standard

Distribution

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.4 DCS Training

Videos

Record DCS Basic, Advances, and Chat

Client training videos in the Government-designated Visual

Information facilities updated quarterly.

MP4 or MOV formats

Standard

Distribution* updated quarterly; as requested

6.4 DCS

Information

Portal updated monthly

Provide content management of the information on the

DEPS DCS

Information Portal on the NIPRNet and

SIPRNet.

Contractor-

Determined

Format

Standard

Distribution*

Weekly

6.4 DCS FAQ, Did

you know articles, Best

Practices, Lessons

Learned, quick start guides

Provide a review and update FAQ, Did you know articles, Best

Practices, Lessons

Learned, quick start guides

Contractor-

Determined

Format

Standard

Distribution* updated quarterly; as requested

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.5 Task Area 5 - Enterprise Collaboration Open Services Support Development

The task area provides open source solution development to include BigBlueButton and components for DCS Conferencing and Chat. The contractor shall develop the open source solution for integration into the DoD environment. To function in the developmental and operational environments, the software developed must be Integrated in accordance with (IAW) the Agile Model of the Software Developmental Life Cycle (SDLC) and tested within the government SDLC.

The contractor shall provide documentation detailing each of the software development efforts.

The contractor shall deliver each of the System (Application) Software executable and source code in designated format (e.g. rpms). The contractor shall conduct, document and deliver test plans and testing results to the Government with each quarterly software (SW) build or release, to include: unit test, integration/system test, volume/stress test, and user test. The contractor shall provide the Government a level-of effort (LOE) assessment on any modifications, fixes, and enhancement to the open source tool sets used by DCS. The contractor shall deliver solutions for HTML5, Core Updates (portal, WC, Chat), and Open source components. The contractor shall deliver customer requirements such as unified capabilities, voice integration, and

Mobility.

Task#

Deliverable

Title

Minimum

Requirements

Format Distributi on/ Copies

Submission Due

Date

6.5 Software

Release

Documentat ion documentation outlining features and functions of each software deliverable.

Designated format

(e.g. MS

Word )

Standard

Distributio n*

Draft 10 days before each deliverable.

Final 10 days after each deliverable

6.5 Test Plans

and Results

Conduct, document and deliver test plans and testing results to the Government with each software

(SW) build or release. To include:

• Unit Test

Integration/Syst em Test

• Volume/Stress

Test

• User Test

Contractor-

Determine d Format

Standard

Distributio n*

Draft 10 days before each deliverable.

Final 10 days after each deliverable

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.6 Task Area 6 - DCS Integration and Operational Support

This task are has two subtasks areas: DCS Integration Support and DCS Operational Support.

6.6.1 Subtask Area 6.1. DCS Integration Support

This subtask area integrates DCS software solution to ensure products delivered by the developer meet or exceed the Cybersecurity and infrastructure requirements for the production network.

The development environment is the responsibility of the contractor.

The contractor shall perform functions like the ones bellow or others within scope of Task Area

6.6.1 that are specified at the Task Order level.

a. Deliver and integrate software in accordance with the Agile Model of the Software

Developmental Life Cycle (SDLC).

b. Ensure the deliverables identified meet 100% delivery.

c. Ensure the deliverables are fully tested in the DISA staging environment prior to delivery to the Government.

d. Ensure any deliverables not accepted by the Government are corrected within 30 calendar days.

e. Ensure any Plan of Action and Mitigation (POA&M) are resolved on or before the date of the Government approved Plan of Action & Milestones.

f. Apply full SDLC processes to the development effort.

g. Apply Capability Maturity Model Integration (CMMI) Level 3 development effort.

h. Ensure modifications to support Information Assurance Vulnerability Management

(IAVM) are corrected on or before the designated suspense date.

i. Maintain, document, and update annually the requirements management processes to ensure the integrity of approved baseline requirements.

j. Collect validate, and document new requirements in Rational Dynamic Object Oriented

Requirements System (DOORS) monthly.

k. Establish and document formal software development, code control and build processes for major and minor (patches) releases and fully integrate with Forge.mil, MilCloud, DISA DECC, and DECC infrastructure environments.

l. Document and update architecture for integration of the DCS Platform for each upgrade.

m. Develop and design the software modules for integration of the DCS Platform.

n. Provide an Integrated Development and Test environment that can be accessed by all

DCS developers and DCS Government Personnel

o. Update Software Forge artifacts and submit software code and deliverables via designated software development management platform (e.g. Software Forge)

Integrate, test the software modules, and field DCS for use by the DoD user community.

Deliverable(s):

PWS

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.6.1 Formal

Software

Development

Processes

Establish and document formal software development, code control and build processes for major and minor (patches) releases and fully integrate with

Forge.mil, Milcloud, DISA DECC, and

DECC infrastructure environments.

Contractor-

Determined

Format

Standard

Distribution*

Draft 30 days after task award

Final 60 days after task award and updated annually.

6.6.1 Baseline

Requirements

Management

Maintain, document, and update annually the requirements

Contractor-

Determined

Format

Standard

Distribution*

6 months from task award, Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date processes

(updated annually) management processes to ensure the integrity of approved baseline requirements.

updated annually

6.6.1 DOORS New

Requirements

Documentation

(updated monthly)

Collect, validate, and document new requirements in

Rational Dynamic

Object Oriented

Requirements System

(DOORS) monthly.

Contractor-

Determined

Format

Standard

Distribution*

Monthly

6.6.1 Updated DCS

Platform

Architectural

Documentation

Document and develop update architecture for integration of the DCS

Platform for each upgrade.

MS Word or

MS Visio as directed.

Standard

Distribution*

Draft 10 days before each upgrade

Final 10 days after each upgrade

6.6.1 DCS

Integrated

Software modules (in rmps format)

Develop and design the software modules for integration of the DCS

Platform (24 upgrades and 60 updates per year)

RPMs or

Ansible

Playbooks as directed.

Standard

Distribution*

Weekly

6.6.1 Test Plans and

Results

Integrate, test the software modules, and field DCS for use by the DoD user community. Provide the Test Plans and results to include:

Unit Test

Integration/System

Test

Volume/Stress Test

User Test

Regression Test

Contractor-

Determined

Format

Standard

Distribution*

Draft 10 days before each upgrade

Final 10 days after each upgrade

6.6.1 Software

Development /

Integration

Updates via

Software Forge

Software Forge updates Software

Forge

Artifacts, Software

Code, Software

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

Executables, Playbooks

Per Software

Forge Format

6.6.1 Request For

Change

(RFCs)

Request For Change

(RFCs) to be reviewed by the DCS Technical

Review Board (TRB)

Meeting

As Directed Standard

Distribution*

Weekly

6.6.1 Static Code

Analysis

Reports

Static Code Analysis

Format

Standard

Distribution*

With each software deliverable

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.6.2 Subtask Area 6.2. DCS Operational Support

This subtask area provides dedicated operational support (Tier 4) for DCS and ensure that the

DCS application(s) and Virtual Operating Environments (VOEs) are managed, configured, sustained, and monitored during the lifecycle of the DCS program to ensure service availability

& optimal performance for DCS. DCS VOE’s include Staging, Pre-Production, and Production

VDCs on NIPRNet and SIPRNet. The average escalations of incident tickets from Tier 3 to Tier

4 are 10 per month.

The contractor shall perform functions like the ones bellow or others within scope of Task 6.6.2 that are specified at the Task Order level.

a. Provide dedicated Tier 4 support the other Tiers.

b. Manage, configure, and monitor the DCS Virtual Operating Environments (VOEs) associated with the DCS Staging, Pre-Production, and Production VDCs on NIPRNet and

SIPRNet.

c. Manage, configure, and monitor the DISA Milcloud Virtual Data Center (VDC) configured for DCS on the NIPRNet and SIPRNet.

d. Coordinate with DCS Tier 2 to apply the necessary Cybersecurity controls, Enterprise

Systems Management (ESM) tools, and Security Technical Implementation Guidance

(STIG) controls.

e. Hand-off the validated Pre-Production application to the production deployment via the

TRB process.

f. Ensure every change to an application component has a document location for immediate roll-back.

g. Upgrade or update, receive, deploy, and test the deliverable code from the development stage into the Milcloud staging enclave. Upon successful testing, move the code to the

Milcloud pre-production VDCs for Cybersecurity hardening. Provide test and hardening results to the PM prior to production delivery.

h. Document and provide meeting minutes of the weekly Technical Review Board (TRB) to the TRB facilitator.

i. Update Software Forge artifacts and submit software code and deliverables via designated software development management platform (e.g. Software Forge)

j. Provide a monthly Status, Health and Configuration report on environments currently being worked

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.6.2 Pre-

Deployment

Testing Results

For each developmental upgrade or update, receive, deploy, and test the deliverable code from the development stage into the Milcloud

Staging and pre-production VDCs for DCS. Provide test results to the

PM prior to production delivery.

Contractor-

Determined

Format

Standard

Distribution*

Draft 5 Days after each testing event.

Final 15 Days after each testing event.

6.6.2 Weekly

Change

Management

Tracking and

Status report

Provide a weekly

Change Management tracking and status report that documents any changes to any of the deployed application components and the status of the roll-back capability.

Format

Standard

Distribution*

Weekly

6.6.2 Software Forge

Updates

Updates to Software

Forge Artifacts, Task, and repositories

Software

Forge format

N/A Weekly

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.7 Task Area 7 - DCS Service Analysis and Situational Awareness Capability

This task area evaluates, develops, and delivers Service Analysis and Situational Awareness tools that can be used by operational support elements to assess the visibility, health and stability of the DCS application environment and the support infrastructure and to provide near real-time

Situational Awareness of their DCS Conference, Chat Session, or infrastructure stability. There are two subtask areas: Integration and Sustainment:.

6.7.1 Subtask Area 7.1 DCS Service Analysis integration

The focus of this subtask area is to develop and maintain the DCS Service Analysis capabilities.

The development environment is the responsibility of the contractor. DCS uses the following tools and applications to manage the development portion of the Service Analysis and Situational

Awareness Development effort:

Nagios XI

Elasticsearch, Logstash, & Kibana (ELK Stack)

Simple Network Management Protocol (SNMP)

Rsyslog

To support the integration of Service Analysis and Situational Awareness tools, the following elements are considered to be key components.

Internet Protocol (IP) networks (IPV4 and IPV6)

Firewalls, Routers, and Switches

Virtual Infrastructures (VMWare)

Network Attached Storage

Storage Area Networks

Active Directory / Domain Controllers

Virtual Private Networks

F5 Load Balancers

6.7.1 that will be specified at the Task Order level.

a. Develop level-of effort (LOE) assessments on development efforts to support each of the developmental tasks.

b. Update Software Forge artifacts and submit software code and deliverables via designated software development management platform (e.g. Software Forge)

c. Develop and/or integrate the DCS Service Analysis tools with changes in infrastructure, tech refresh, customer requirements, and other modifications. Update DCS Service

Analysis tools on a semi-annual basis and modify tools to ensure that tools monitor the current DCS architecture on an as needed basis.

d. Develop documentation to support the developmental tasks.

Deliverable(s)

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.7.1 Developmental

Tasks Level of

Effort (LOE)

Develop a level-of effort (LOE) assessments on development efforts to support each of the developmental tasks.

Contractor-

Determined

Format

Standard

Distribution*

Draft 15 days after each requirement decision

Final 30 days after each upgrade requirement decision

6.7.1 System OV-1

and SV 1

Operational View (OV-

1) and System View

(SV-1) of DCS System

Architecture

MS Visio and

PDF

Standard

Distribution*

Draft 15 days prior to each architecture change and final 30 days after each architecture change

6.7.1 Test Plans and

results

For each deliverable develop Test plans and deliver results designed to validate and support the tool deployment to include technical testing, and regression testing when appropriate.

Contractor-

Determined

Format

Standard

Distribution*

Draft 10 Days after each deliverable

Final 20 Days after each deliverable

6.7.1 LUT and

Results

Conduct Limited User

Testing (LUT) and provide the results of each LUT to the

Government to validate wider testing and implementation.

Contractor-

Determined

Format

Standard

Distribution*

Draft 10 Days after each LUT event

Final 20 Days after each LUT event

6.7.1 Formal

Software

Development

Processes

Formal Software

Development Processes documentation

Format

Standard

Distribution*

Annually

6.7.1 Baseline

Requirements

Management processes

Baseline Requirements

Management processes

Format

Standard

Distribution*

Annually

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.7.1 DOORS New

Requirements

Documentation

DOORS New

Format

Standard

Distribution*

As requested

6.7.1 Updated DCS

Platform

Architectural

Updated DCS Platform

Architectural

MS Visio, MS

Word, and

PDF as directed.

Standard

Distribution*

Monthly

6.7.1 DCS

Integrated

Software modules [24 upgrades and

60 updates per year]

DCS Integrated

Software modules (e.g.

rpms, Ansible

Playbooks) [24 upgrades and 60

Rpms, Ansible

Playbooks

Software

Forge and as otherwise directed.

Twice Monthly

6.7.1 Test Plans and

Results

Test Plans and Results

Format

Standard

Distribution*

With each software deliverable

6.7.1 Request For

Change

(RFCs)

Request For Change

(RFCs) to be reviewed by the DCS Technical

Review Board (TRB)

Meeting

As Directed Standard

Distribution*

Weekly

6.7.1 Updates via

Updates via Software

Forge Format

Standard

Distribution*

Weekly

6.7.1 Static Code

Format

Standard

Distribution*

With each deliverable as directed.

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.7.2 Subtask Area 7.2 DCS Service Analysis - Sustainment

The focus of this subtask area is DCS service analysis sustainment. DCS uses the following tools and applications to manage the development portion of the Service Analysis and Situational

Awareness Development effort:

Nagios XI

Elasticsearch, Logstash, & Kibana (ELK Stack)

Simple Network Management Protocol (SNMP)

Rsyslog

The contractor shall perform functions like the ones bellow or others within scope of Task 6.7.2

a. Monitor DCS servers and associated IaaS components on the NIPRNet and SIPRNet using the Nagios and ELK tools.

b. Maintain & configure DCS Service Situational Awareness/NetOps tools per direction of

DCS NetOps Development.

c. Maintain close communication with DCS Tier 2, Tier 3, and Tier 4, and DCS NetOps

Development.

d. Provide direct support to DCS Tier 2 and Tier 3, the DISA NetOPs and the DISA

Command Center (DCC).

e. Utilize government provided monitoring tools to maintain the visibility, health, and security of all DCS servers, infrastructure components, and application stability.

f. Participate in DISA Operations Meetings weekly to provide status and health of DCS to

DISA NetOPs.

g. Provide a weekly Performance Analysis Report.

Readiness of secondary DCS site to fail over if needed

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.7.2 Metrics Report DCS Metrics Report on

System Metrics as determined by DCS

PMO

As directed Standard

Distribution*

Weekly, Monthly, and as requested

6.7.2 DCS Status, Health, and

Configuration

Report

(updated

Monthly)

DCS Status, Health, and Configuration

Report (updated

Monthly)

Format

Standard

Distribution*

Weekly and monthly

6.7.2 Weekly

Performance

Analysis

Reports for

DCS on

NIPRNet and

SIPRNet

Provide a weekly

Performance Analysis

Report that addresses the following:

Health and stability of the network routers and firewalls

Contractor-

Determined

Format

Standard

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date supporting the DCS infrastructure

Health and stability of the F5

Application Load

Balancers supporting the DCS infrastructure

Health and stability of the Milcloud

Virtual Data Centers

(VDCs) supporting the DCS infrastructure

Health and stability of the Staging, Pre-

Production, and

Production VDCs supporting the DCS infrastructure

Health and stability of all of the Virtual

Operating

Environments

(VOEs) is each of the Milcloud VDC

Validation of the mirroring of the primary DCS site to the failover site

Readiness of secondary DCS site to fail over if needed

6.8 Task Area 8 - DCS Compliance Test Support

This task area is to ensure that any application component, patch, fix, or update to the DCS or a

DCS component is fully tested functionally, technically, and in accordance with Cybersecurity requirements. The contract support will plan the test process, create test plans, perform the test, and deliver the results to ensure reliable quality assurance deliveries.

6.8 that are specified at the Task Order level.

a. Utilize the DCS Pre-Production Environment on the NIPRNet or SIPRNet to support evaluations of Information Assurance (IA) and functional capabilities of DCS products.

b. Support the testing of the code delivery in the DCS Pre-Production environment.

c. Conduct tests and provide the results of the following tests to support the development and pre-deployment of all DCS developed components, patches, fixes, and/or upgrades:

Software Code Scanning to ensure compliance with Information Assurance requirements

Unit Test

Integration/System Test

Volume/Stress Test

User Test

Regression Test

d. Provide the Government a go/no assessment for each Testing event.

e. Provide the Government a quarterly testing status in the form of an In Progress Review

(IPR).

f. Develop a Software Test Plan (STP) designed to document the process, procedures, and mitigations related to the application testing and validation processes.

g. Provide quality assurance for all deliverable testing.

Task

Deliverabl e Title

Minimum

Requirements

Format Distributi on/

Copies

Submission

Due Date

6.8 Static Code

Static Code

Analysis Reports

Contractor

Determine d Format

Standard

Distributi on*

With each software deliverable.

6.8 Deploymen

t and Pre-

Deploymen t Testing

Results

Deployment and

Pre- Deployment

Testing Results

Contractor

Determine d Format

Standard

Distributi on*

As requested

6.8 Software

Test Plan

(STP)

For each software solution, develop a

Software Test Plan

(STP) designed to

Contractor

Determine d Format

Standard

Distributi on*

Draft 10 days prior to each

Deliverabl e Title

Minimum

Requirements

Format Distributi on/

Copies

Submission

Due Date document the process, procedures, and mitigations related to the application testing and validation processes.

software deliverable

Final 5 days prior to each software deliverable.

6.8 Quarterly

Testing

IPR

Provide the

Government a quarterly testing status in the form of an In Progress

Review (IPR).

Contractor

Determine d Format

Standard

Distributi on*

90 days after award, updated

Quarterly

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.9 Task Area 9 – Cybersecurity Support

This task area is to provide support to the DCS Program to ensure all Cybersecurity requirements are met and required security controls are selected and implemented to maintain compliance with the DoD RMF. This is a support task and any deliverables are government generated artifacts that require input and completion on the part of the contractor. The performance of this task requires Cybersecurity expertise to advise and support the Government Information System

Security Manager (ISSM) with required RMF tasks.

The contractor shall perform functions like the ones bellow or others within scope of Task 6.9

a. Ensure all contractors supporting this task are DoDD 8140-IAM Level 2 Certified

Professionals.

b. Research and validate compliance with applicable DoD/DISA Cybersecurity requirements, directives, regulations, and US Laws.

c. Be required to function on both the classified and unclassified networks.

d. Support the utilization of the automated validation capabilities of the Enterprise Mission

Assurance Support Service (eMASS) for preparation of the RMF Package.

e. Develop and maintain the RMF package quarterly which includes:

Maintaining the DCS system artifacts.

Assigning security controls based on the DCS system categorization as required by

DoDI 8500.01 and DoDI 8510.01, CNSS 1253 and NIST SP 800-60, Volume II.

Ensuring the DCS system is properly registered in eMASS

Initiating and maintaining the RMF System Security Plan (SSP).

f. Implement and validate assigned security controls which include:

Execution of the SSP.

Conducting RMF validation activities.

Compile the status of the validation results in the RMF Scorecard.

g. Develop and maintain the supporting Assessment and Authorization (A&A) which include:

Risk Assessments

Contingency Plan

Plan of Actions and Milestones (POA&M)

Other artifacts associated with implementing security controls, etc. as required for the

RMF.

h. Draft a POA&M for any authorization decision that requires corrective action.

i. Develop and maintain the System Security Plan (SSP).

j. Provide security engineering to the Government and support assessment and authorization (A&A activities related to the DCS System).

k. Update any Cybersecurity databases as required or directed by DoD/DISA policies.

l. Submit and update IA related artifacts in software Forge.

m. Manage and maintain the DCS Assessment and Authorization (A&A) process monthly required to sustain DoD/DISA compliance standards IAW the DoD RMF and in compliance with DoD 8500 series publications.

n. Manage the DCS IAVM (Information Assurance Vulnerability Alert (IAVAs)/

Information Assurance Vulnerability Bulletin (IAVBs)) management process as determined by the Government.

o. Support the preparation and documentation of Cybersecurity assessments of the DCS system and assets for all security and/or certification visits in the Command Cyber

Readiness Inspection (CCRI) Federal Information Security Modernization Act (FISMA) discrepancies. Assessment tasks include:

Auditing and reporting of the DCS system

Documentation

Security control compliance

DoD 8570.1-M compliance requirements

IAVM which include IAVAs/IAVBs), and STIG/SRG compliance.

p. Coordinate and provide Cybersecurity input on matters related to

STIG compliance

IAVA Testing and compliance

Assured Compliance Assessment Solution (ACAS) and Fortify Scans, and

Penetration Test results

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.9 DCS RMF

Package

Quarterly

Updates

Develop and maintain the RMF package quarterly which includes:

• Maintaining the

DCS system artifacts.

• Assigning security controls based on the

DCS system categorization as required by DoDI

8500.01 and DoDI

8510.01, CNSS

1253 and NIST SP

800-60, Volume II.

• Ensuring the DCS system is properly registered in eMass

• Initiating and maintaining the RMF

System Security Plan

(SSP).

Contractor-

Determined

Format

Standard

Distribution*

Draft 60 days after task order award

Final 90 days after task order award, updated quarterly

6.9 DCS System

Security Plan

Annual

Updates

Develop and maintain the System Security

Plan (SSP) annually that provides a systematic approach and techniques for protecting the application environment from being used by unauthorized users, guards against worms and viruses as well as any other incident/event/proce ss that can jeopardize the underlying system’s security.

Contractor-

Determined

Format

Standard

Distribution*

11 months from award, updated annually

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission

Due Date

6.9 A&A Process

Monthly

Updates

Manage and maintain the DCS Assessment and Authorization

(A&A) process monthly required to sustain DoD/DISA compliance standards

IAW the DoD RMF and in compliance with

DoD 8500 series publications.

Contractor-

Determined

Format

Standard

Distribution*

30 days from task order award, updated

Monthly

6.9 Weekly IAVM

report

Weekly IAVM report Contractor-

Determined

Format

Standard

Distribution* weekly

6.9 DCS change

requests

DCS change requests for new capabilities

Contractor-

Determined

Format

Standard

Distribution*

As requested

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.10 Task Area 10 – New Infrastructure Migration and Integration Support

This task area is to provide technical and integration support to complete new hosting infrastructure migrations. DCS will transition to another cloud hosted infrastructure as Mil 1.0 environment will no longer be available. The major tasks for this infrastructure deployment consists of obtaining servers, creating and configuring virtual private clouds (Configure firewalls to comply with STIG requests), Infrastructure Creation (VM and server creation, configure ports), supporting cybersecurity requirements and approvals, VPC VM Creation, VDSS

Configuration (F5, URL, CERTs), VDMS (HBSS and ACAS scans for CR2), End to End

Testing (functional, IA, load, COOP), CSSP and SCCA creation, and deployment.

In addition, the task area is to optimize and improve infrastructure performance with shared services, open source component/server optimizations, containerization, and cross-site interactions. By optimizing the DCS application, servers, and infrastructure, there will be cost savings, IT efficiencies and customer service and quality improvements for the program.

6.10 that are specified at the Task Order level.

a. Provide technical and integration support to the latest cloud hosting infrastructure.

b. Measure the performance and optimize infrastructure and performance within shared services, open source component/server optimizations, containerization, and cross-site interactions.

c. Submit and update development / engineering related artifacts in Software Forge

Deliverables:

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission Due

Date

6.1

Technical documenta tion

1. Prepare technical documentati on SV1 and

OV1

diagrams, engineering specification s, presentation s

Contractor-

Determined

Format

Standard Distribution*

As requested

6.10 Performan

ce testing document ation

Prepare a performance measurements documentation

Contractor-

Determined

Format

Standard Distribution*

As required

6.10 Weekly

status updates

Provide a weekly activity report documenting open work issues, current work efforts, and future work efforts.

Contractor-

Determined

Format

Standard

Distribution*

Weekly after contract award

6.10 Test

Results

Test results Contractor-

Determined

Format

Standard

Distribution*

NLT 5 days after the testing

6.11 Task Area 11 – Tech Refresh Integration Support

This task area is to provide integration support for DCS tech refreshes. The contractor shall provide technical support engineer, integrate, test, and deliver technology refresh updates. For instance, DCS application is based on Adobe Flash. However, browsers will cease Flash support by year 2020. In order to ensure DCS viability for our customers, the team must develop a fully capable HTML5 prior to year 2020. Additionally, tech refreshes for web conference and chat components that must be delivered to ensure DCS service and availability.

The DCS tech refresh support will involve HTML5, Core Updates (portal, WC, Chat), and

Open source component upgrades.

6.11 that are specified at the Task Order level.

a. Deliver tech refresh to be integrated and deployed into DCS application.

b. Provide integration support for HTML5 capable DCS. This required tech refresh will replace Flash with a fully HTML5 capable DCS. The browser support for Flash ends in 2020 and DCS will not be accessible after 2020.

c. Provide integration support for DCS Core Updates with the portal, Web conference, and Chat.

d. Provide integration support for DCS Open source components.

e. Submit and update development / engineering related artifacts in Software Forge

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission Due Date

6.11 Technical

documentation white papers, presentations, SV1 and

OV-1 Architecture

Updates

Contractor-

Determined

Format

Standard

Distribution*

As requested, weekly

6.11 Weekly status

report

Weekly Tech refresh status report

Contractor-

Determined

Format

Standard

Distribution*

Weekly

6.11 Test

results and resolution plans

Test results and resolution plans

Standard format

Standard distro

As requested

6.11 Tech

Refresh

RFC

Tech Refresh RFC Requested format

Standard distro

As requested

6.12 Task 12 Area – Customer Requirement Integration Support

This task area is to provide integration support for customer requirements. There are constant customer requirements that the DCS PMO must analyze and deliver for their customers. The contract support delivers customer requirements for unified capabilities, voice integration, FVEY CE chat, Mobility, Enterprise chat federation, Disconnected Intermittent Low

Bandwidth, and Regional DCS.

The contractor shall perform functions like the ones bellow or others within scope of Task 6.12

a. Provide integration support for unified capabilities.

b. Provide integration support for unified capabilities FVEY CE chat.

c. Provide integration support for Mobility web conference and XMPP chat capabilities.

d. Provide integration support for Enterprise chat federation and Cross Domain Enterprise services solution.

e. Provide integration support for Disconnected Intermittent Low Bandwidth, and Regional

DCS.

f. Provide integration support for additional capabilities and functions to DCS.

g. Submit and update development / engineering related artifacts in Software Forge

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission Due

Date

6.12 Technical

documentati on to include white papers, presentation s, SV1 and

OV-1

Architecture

Updates

White papers, presentations, SV1 and OV-1

Contractor- Determined Format

Standard Distribution* weekly

6.12 Weekly Status

Weekly Status

Format

Standard Distribution* weekly

6.12 Formal

Software

Formal Software

Format

Standard Distribution* weekly

6.12 Baseline

Requiremen ts

Managemen t processes

Baseline

Requirements

Management processes

Contractor- Determined Format

Standard Distribution* weekly

6.12 DOORS New

Requirements

Documentatio n

DOORS New

Format

Standard weekly

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission Due

Date

6.12 Updated DCS

Platform

Architectural

Documentatio n

Updated DCS

Platform Architectural

Format

Standard Distribution* weekly

6.12 DCS

Integrated

Software modules (in rmps format)

[24 upgrades and 60 updates per year]

DCS Integrated

Software modules (in rmps format) [24 upgrades and 60 updates per year]

Format

Standard Distribution* weekly

6.12 Test Plans

and Results

Test Plans and Results

Format

Standard Distribution* weekly

6.12 Infrastructure

Deployment

(Mil 2.0, AWS, other cloud hosted infrastructures

Infrastructure

Deployment (Mil 2.0, AWS, other cloud hosted infrastructures)

Format

Standard Distribution* weekly

6.12 Infrastructure

RFCs to implement changes to supporting infrastructure

Infrastructure RFCs to implement changes to supporting infrastructure

Format

Standard Distribution* weekly

6.12 Customer

Requirements

(unified capabilities, voice

Customer

Requirements (unified capabilities, voice integration, and

Mobility)

Contractor- Determined Format

Standard

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission Due

Date integration, and Mobility)

Customer

Requirements

RFC –

Customer

Requirements

(unified capabilities, voice integration, and Mobility)

Customer

Requirements RFC –

Customer

Requirements (unified capabilities, voice integration, and

Mobility)

6.12 Updates via

Updates via Software

Forge format

N/A* weekly

6.12 Request For

Change

(RFCs) to be reviewed by the DCS

Technical

Review Board

(TRB)

Meetings

Request For Change

(RFCs) to be reviewed by the DCS Technical

Review Board (TRB)

Meetings

Format

Standard

6.13 Task Area 13 – Implementation Support

Implementation (Implementation Weekly Status Report)

The task is to lead the implementation for the deliverables through the DCS SDLC and into production. The contract support understands the deliverables and schedules and manages the implementation process.

6.13 that are specified at the Task Order level.

a. Manage the deliverable implementation from staging, pre-prod, and production.

b. Plan, deliver, and manage the deliverable implementation by working in concert with government, DECC, and DISA personnel to deliver the capability.

c. Submit and update development / engineering related artifacts in Software Forge

Task#

Deliverable

Title

Minimum

Requirements

Format Distribution/

Copies

Submission Due

Date

6.13 Technical

documentation and diagrams on deliverables

Technical documentation and diagrams on deliverables

Format

Standard Distribution* weekly

6.13 Implementatio

n Weekly

Status Report

Implementation

Weekly Status Report

Format

Standard Distribution* weekly

** Note ** For contractor’s planning purposes these deliverables are being used as example.

6.14 Task Area 14 - Customer Engagement Support

This task area is to provide support for DCS…