1__Performance_Work_Statement_for_IDIQ.docx

PERFORMANCE WORK STATEMENT (PWS)

As of 06 June 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 (DISA) is an information technology services provider and delivers information sharing capabilities to the Department of Defense (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:

· Collaboration Portal: Social Media and collaboration features, links and training info, and real time communications via messages

· Web Conferencing: Slide Show Presentations, Integrated Voice, Web Conference Recordings, Desktop Sharing, Multi-user Whiteboarding, closed captioning, Text Chat, Polling and Voting,

· 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 Application Delivery Controller (e.g. F5 VIPRION Platform), Online Certificate Status Protocol (OCSP), Domain Name System (DNS), Active Directory Enterprise Application and Services Forest (AD EASF), Network Time Protocol (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 Program Management Office (PMO) will continue to utilize Development / Security / Operations (DevSecOps) 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 Department of Defense Directive (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

SSH, SFTP Clients (e.g. PuTTY)

Commercial Components

Remedy Management System

Ribbon (Sonus) Session Border Controller (SBC) Software Edition (SWe)

Microfocus Fortify

Protocols, Standards, Infrastructure and Other Technologies

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):

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

Final 30 days after task order award, updated annually.

** 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, Information Assurance (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 Defense Enterprise Computing Center (DECC) for coordination, and engineering Technical Exchange Meetings (TEMs).

Deliverable(s):

Software Forge Updates

Software Forge Artifacts, Software Code, Executables, Playbooks Per Software Forge Format

** 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.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.

Deliverable(s):

· 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 2 Total Number of Incidents Tickets Closed

Incidents, technical issues, and updates via Software Forge

Software Forge Format

** 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.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):

** 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.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.

Deliverable(s):

Final 10 days after each deliverable

Final 10 days after each deliverable

** 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.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.

1. Deliver and integrate software in accordance with the Agile Model of the Software Developmental Life Cycle (SDLC).

1. Ensure the deliverables identified meet 100% delivery.

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

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

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

1. Apply full SDLC processes to the development effort.

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

1. Ensure modifications to support Information Assurance Vulnerability Management (IAVM) are corrected on or before the designated suspense date.

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

1. Collect validate, and document new requirements in Rational Dynamic Object Oriented Requirements System (DOORS) monthly.

1. 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.

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

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

1. Provide an Integrated Development and Test environment that can be accessed by all DCS developers and DCS Government Personnel

1. 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):

Final 60 days after task award and updated annually.

Final 10 days after each upgrade

· Unit Test

· Integration/System Test

· Volume/Stress Test

· User Test Regression Test

Final 10 days after each upgrade

Per Software Forge Format

Static Code Analysis Reports

** 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.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.

1. Provide dedicated Tier 4 support the other Tiers.

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

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

1. Coordinate with DCS Tier 2 to apply the necessary Cybersecurity controls, Enterprise Systems Management (ESM) tools, and Security Technical Implementation Guidance (STIG) controls.

1. Hand-off the validated Pre-Production application to the production deployment via the TRB process.

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

1. 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.

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

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

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

Deliverable(s):

Final 15 Days after each testing event.

Forge format

** 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.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:

0. Nagios XI

0. Elasticsearch, Logstash, & Kibana (ELK Stack)

0. Simple Network Management Protocol (SNMP)

0. Rsyslog

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

0. Internet Protocol (IP) networks (IPV4 and IPV6)

0. Firewalls, Routers, and Switches

0. Virtual Infrastructures (VMWare)

0. Network Attached Storage

0. Storage Area Networks

0. Active Directory / Domain Controllers

0. Virtual Private Networks

0. F5 Load Balancers

The contractor shall perform functions like the ones bellow or others within scope of Task Area 6.7.1 that will be specified at the Task Order level.

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

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

1. 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.

1. Develop documentation to support the developmental tasks.

Deliverable(s)

Final 30 days after each upgrade requirement decision

Final 20 Days after each deliverable

Final 20 Days after each LUT event

Formal Software Development Processes documentation

Baseline Requirements Management processes

DOORS New Requirements Documentation

Updated DCS Platform Architectural Documentation

Test Plans and Results

Updates via Software Forge

Software Forge Format

Static Code Analysis Reports

** 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.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:

0. Nagios XI

0. Elasticsearch, Logstash, & Kibana (ELK Stack)

0. Simple Network Management Protocol (SNMP)

0. Rsyslog

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

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

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

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

1. Provide direct support to DCS Tier 2 and Tier 3, the DISA NetOPs and the DISA Command Center (DCC).

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

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

1. Provide a weekly Performance Analysis Report.

1. Readiness of secondary DCS site to fail over if needed

Deliverable(s):

DCS Status, Health, and Configuration Report (updated Monthly)

1. Health and stability of the network routers and firewalls supporting the DCS infrastructure

1. Health and stability of the F5 Application Load Balancers supporting the DCS infrastructure

1. Health and stability of the Milcloud Virtual Data Centers (VDCs) supporting the DCS infrastructure

1. Health and stability of the Staging, Pre-Production, and Production VDCs supporting the DCS infrastructure

1. Health and stability of all of the Virtual Operating Environments (VOEs) is each of the Milcloud VDC

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

1. Readiness of secondary DCS site to fail over if needed

** 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.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.

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

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

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

1. 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

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

1. Provide the Government a quarterly testing status in the form of an In Progress Review (IPR).

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

1. Provide quality assurance for all deliverable testing.

Deliverable(s):

Static Code Analysis Reports

Deployment and Pre- Deployment Testing Results

Final 5 days prior to each software deliverable.

** 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.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 that are specified at the Task Order level.

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.

1. Ensuring the DCS system is properly registered in eMASS

1. 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(s):

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

Final 90 days after task order award, updated quarterly

** 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.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.

The contractor shall perform functions like the ones bellow or others within scope of Task Area 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:

** 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.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.

The contractor shall perform functions like the ones bellow or others within scope of Task Area 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

Deliverables:

** 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.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 that are specified at the Task Order level.

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

Deliverables: