Attachment___1_SOO.DOCX

STATEMENT OF OBJECTIVES (SOO)

as of 16 April 2018

Contract Title: Defense Enterprise Office Solutions (DEOS)

Background The Department of Defense (DoD) requires an integrated enterprise cloud service offering (CSO) for common communication, collaboration, and productivity capabilities that are mission-effective, efficient, more widely accessible, to facilitate DoD operations worldwide. The Defense Information Systems Agency (DISA), in support of the DoD Deputy Secretary of Defense’s direction to accelerate the DoD’s adoption of cloud computing technology, plans to acquire and implement a seamlessly integrated, enterprise CSO as a replacement for disparate DoD legacy enterprise information technology (IT) services, such as voice, video, collaboration, email, content management, records management, and office productivity.

Objectives DEOS is a new procurement of a CSO that will support the Department’s move towards implementing capabilities for the Joint Information Environment (JIE) vision, improving trusted information sharing, and integration of virtual enterprise services into DoD strategic environments. DEOS will unify and modernize legacy DISA IT enterprise services such as DoD Enterprise Email (DEE), DoD Enterprise Portal Service (DEPS), Defense Collaboration Services (DCS), and other disparate DoD-wide legacy enterprise collaboration, voice/video, and productivity capabilities.

The DEOS CSO will be acquired by DISA through an unrestricted, competitively awarded single-award Indefinite Delivery/Indefinite Quantity (ID/IQ) Firm-Fixed Price (FFP) contract with a contractor who will provide a non-developmental, seamlessly integrated CSO. The contract period of performance will be a 5-year base ordering period and five 1-year options ordering period. The contract also will include the 6-month extension of services authorized by FAR 52.217-8. The 10-year period of performance will provide the Department with the flexibility to transition users based on user demand, migration schedules, and legacy contracts or service end-of-life terms. The anticipated initial task order issued against this ID/IQ could potentially include the current 1.8 million legacy United States territories and possession NIPRNet DEE user population.

Scope DEOS will provide the DoD with an integrated, interoperable, enterprise CSO to support approximately 3.15 million DoD consumers, standardize adoption, and enable cross-Department collaboration at local base/post/camp/station (B/P/C/S) levels to include deployed and afloat organizations. DEOS is intended to be deployed on the Sensitive but Unclassified Internet Protocol (SBU IP) Data Network, also known as NIPRNet, the Secret Internet Protocol (IP) Data, also known as SIPRNet, to include Denied, Disconnected, Intermittent, and Limited Bandwidth (D-DIL) environments.

The capabilities within the scope of the DEOS service are highlighted in Figure 1. The green boxes highlight some of the existing DoD supporting infrastructure, services, and major integration points that will reside primarily on-premises as part of the Government’s responsibility and which the Cloud Service Provider (CSP) must integrate with. These specific supporting infrastructure and services outline the DoD required integration points that the CSP will be responsible for ensuring interoperability and integration with. Additional, information related to the DoD supporting infrastructure and service requirements are outlined within section 4 of the Functional Requirements Document (FRD).

Figure 1 – DEOS Service Requirements

The Government requires a multifaceted implementation and deployment approach for United States territories and possessions and locations outside of the United States territories and possessions for NIPRNet, SIPRNet, and D-DIL environments.

For the United States territories and possessions NIPRNet and SIPRNet implementations, the Government will leverage commercially hosted facilities to meet the DEOS requirements. However, due to DoD data sovereignty requirements, locations outside of the United States territories and possessions the contractor will be required to implement a NIPRNet and SIPRNet CSO within a DoD data centers (e.g. Stuttgart, Wiesbaden, Capodichino).

For all implementation locations outside of the United States territories and possessions the contractor will be required to provide a stand-alone environment within a DoD data center that includes, the required infrastructure, hardware, software, and any other additional components required to implement, management, and maintain the CSO environments. The Government will provide and identify the DoD data center facilities based on the contractor proposed number of distributed DoD data centers, heating, ventilation, air condition (HVAC), per-rack power (e.g. single phase, 3-phase, amperage, voltage, etc.), floor space (rack and total square footage), bandwidth (in total Mbps/Gbps), physical security/separation, physical access, remote management, and networking (e.g. IP addressing, subnets, routing) requirements.

Performance Objectives The contractor shall propose performance tasks that fully adhere to the requirements of the solicitation and the DEOS FRD (Attachment 01), DoD Cloud Computing Security Requirements Guide (CC SRG), and DoD security control requirements to achieve and maintain Authorization to Operate (ATO), Provisional Authorization (PA) at Impact Level (IL) 5 (Controlled Unclassified Information) and IL 6 (Classified Information up to Secret) utilizing the Performance Work Statement (PWS) format (Attachment 4) provided as part of this solicitation.

The deliverables and performance standards based the proposed technical and management solution, shall incorporate the mandatory contract deliverables, the performance standards (section 6), Cyber Threat Security Plan (section 16), Supply Chain Risk Management (SCRM) requirements (section 19), and Section 508 Accessibility Standards (section 20) in the proposed PWS.

Task 1 – NIPRNet Environment The contractor shall deliver a cloud architecture and corresponding environment that supports a multiple tenant. The NIPRNet CSO shall include System Wide, Core Services (i.e. Email, IM/Chat, Web Conferencing, Native Audio, Native Video, Content Management, and Office Productivity), Record Management, and DoD Information Network (DoDIN) Protection requirements in accordance with (IAW) the FRD sections 2, 3, and 4.

Furthermore, the contractor shall be required to interface the CSO to the core integration points identified in the FRD section 7. Lastly, the contractor shall adhere to the performance objectives identified in the FRD section 9, and shall be required to perform testing activities/events (i.e. integration, acceptance, operational) IAW the FRD section 10, to verify the proper interoperability between the CSO and core integration points (FRD section 7).

Subtask 1 – United States Territories and Possessions Provide a geographically dispersed off-premises CSO within a DoD private/community hybrid cloud that meets IL 5 requirements IAW the DoD CCSRG and the FRD.

Subtask 2 – Locations outside of the United States Territories and Possessions Provide a geographically dispersed DoD private/community hybrid Cloud Service Offering (CSO) that is deployed in an DoD facility using an on-premises deployment model that meets Impact Level 6 in accordance with the DoD CC SRG and FRD.

Deliverables:

The Government shall require the following documents as the deliverables for this task and sub-tasks. The contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Determined Format

Distribution* One Time Update annually as required

Determined Format

Distribution* Monthly, as Required

Determined Format 90 Calendar Days after TO Execution Standard Distribution* Monthly, as required

Architecture, DoDAF Artifacts/Diagrams (i.e. AV, OV, SV, StdV, CV) Contractor Determined Format 90 Calendar Days after TO Execution Standard Distribution* One Time Update annually as required

Determined Format 90 Calendar Days after TO Execution Standard Distribution* One Time Update annually as required

Service Support Functions and Integration Plan Contractor Determined Format

Distribution* One Time;

Updated annually as required

Records Management Architecture/ Integration Plan Contractor Determined Format 30 Calendar Days after TO Execution Standard Distribution* One Time Update annually as required

Cybersecurity Monitoring Strategy Contractor Determined Format

Distribution* One Time;

Updated annually as required

Transition/ Decommission Plan Contractor Determined Format

Distribution* One Time Updated annually as required

Requirements Management Plan / Traceability Matrix Contractor Determined Format 30 Calendar Days after TO Execution Standard Distribution* Weekly, as required

Customer Communication Plan Contractor Determined Format 30 Calendar Days after TO Execution Standard Distribution* One Time;

Updated annually as required

White Papers, Information Papers and Decision Papers Contractor Determined Format 30 Calendar Days after TO Execution Standard Distribution* Monthly, as required

Determined Format 30 Calendar Days after TO Execution Standard Distribution* Weekly, as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository.

Task 2 – SIPRNet Environment The contractor shall deliver a cloud instance architecture and corresponding environment that supports multiple tenants. The SIPRNet CSO shall include System Wide, Core Services (i.e. Email, IM/Chat, Web Conferencing, Native Audio, Native Video, Content Management, and Office Productivity), and DoD DoDIN Protection requirements IAW the FRD sections 2, 3, and 4. Furthermore, the contractor shall be required to interface the CSO to the core integration points identified in the FRD section 7. Lastly, the contractor shall adhere to the performance objectives identified in the FRD section 9, and shall be required to perform testing activities/events (i.e. integration, acceptance, operational) IAW the FRD section 10, to verify the proper interoperability between the CSO and core integration points (FRD section 7).

Subtask 1 – United States Territories and Possessions Provide a geographically dispersed off-premises CSO within a DoD private/community hybrid cloud that meets IL 5 requirements in accordance with the DoD CC SRG and the FRD.

Subtask 2 – Locations outside of the United States Territories and Possessions Provide a geographically dispersed DoD private/community hybrid CSO that is deployed in an DoD facility using an on-premises deployment model that meets Impact Level 6 in accordance with the DoD CC SRG and FRD.

Deliverables:

The Government shall require the following documents as the deliverables for this task and sub-tasks. The contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Distribution* One Time;

Updated annually as required

Distribution* Monthly, as required

Distribution* Monthly, as required

Architecture, DoDAF Artifacts/Diagrams (AV, OV, SV, StdV, CV)

Distribution* One Time;

Updated annually as required

Distribution* One Time;

Updated annually as required

Service Support Functions and Integration Plan

Distribution* One Time;

Updated annually as required

Records Management Architecture/ Integration Plan

Distribution* One Time;

Updated annually as required

Cybersecurity Monitoring Strategy

Distribution* One Time;

Updated annually as required

Transition/ Decommission Plan

Distribution* One Time;

Updated annually as required

Requirements Management Plan / Traceability Matrix

Distribution* Weekly, as required

Customer Communication Plan

Distribution* One Time;

Updated annually as required

White Papers, Information Papers and Decision Papers

Distribution* Monthly, as required

Distribution* Weekly, as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository.

Task 3 – Denied, Disconnected, Intermittent, Limited Bandwidth (D-DIL) Environment The contractor shall provide an independently-operable system (i.e. able to operate when disconnected from the main cloud service) that allows for continuity of operations while experiencing a Denied, Disconnected, Intermittent or Limited Bandwidth condition IAW section 6 and appendix A of the FRD.

In many cases, the full suite of DEOS services may not be required and in some cases the requirements may consist of a single function deployed as a standalone service (i.e. black-box, hardware, software, etc.). The contractor shall plan for these variations in D-DIL service based on a per tenancy or stand-alone environments that are implemented.

Subtask 1 – NIPRNet Environment Engineer, configure and deploy a standalone, independently operable suite that operates from the NIPRNet cloud instance when connected. The D-DIL solution shall communicate with the cloud to receive updates. It is understood that in some cases, D-DIL deployments may experience lower cloud service availability rates. However, the contractor shall ensure that standalone equipment is engineered and configured to have the same availability and survivability Service Level Agreement (SLA) as that of the cloud.

Subtask 2 – SIPRNet Environment Engineer, configure and deploy a standalone, independently operable suite that operates from the SIPRNet cloud instance when connected. The D-DIL solution shall communicate with the cloud to receive updates. It is understood that in some cases, D-DIL deployments may experience lower cloud service availability rates. However, the contractor shall ensure that standalone equipment is engineered and configured to have the same availability and survivability SLA as that of the cloud.

Deliverables The Government shall require the following documents as the deliverables for this task and sub-tasks. The contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Distribution* One Time Update annually as required

after TO Execution Standard Distribution* Monthly, as required

Distribution* Monthly, as required

Distribution* One Time;

Updated annually as required

Architecture, DoDAF Artifacts/Diagrams (AV, OV, SV, StdV, CV)

Distribution* One Time;

Updated annually as required

Distribution* One Time;

Updated annually as required

Cybersecurity Monitoring Strategy

Distribution* One Time;

Updated annually as required

Transition/ Decommission Plan

Distribution* One Time;

Updated annually as required

Requirements Management Plan / Traceability Matrix

Distribution* Weekly, as required

White Papers, Information Papers and Decision Papers

Distribution* Monthly, as required

Distribution* Weekly, as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository

Task 4 – User Tenancy Stand-Up The Government will allow flexibility and expects the contractor to propose a tenancy structure. As a result, the contractor shall propose a single tenancy or multitenancy architecture, which meets the requirements of the FRD, and allows each Combatant Commands, Services and Agencies (CC/S/As) the ability to control their own environment from an administrative and operations perspective, while providing logical groupings of users who share common access, attributes and work relationships.

Tenants should be expected to have control of their own instance, including their data, configuration, as well as user, feature, and functionality management. This includes the ability to grant/remove administrative privileges, user roles, and the ability to control license assignment within the solution.

The following table provides a summary of potential DoD subscribers per region. The contractor tenancy structure must address the concerns listed above, as well as an approach for customers that may be part of a CC/S/As at the same time (i.e. “dual hatting”).

Locations outside of the United States Territories and Possessions 290,984*

*DMDC Active Duty, Reserve, and Civilians data as of September 30, 2017; excludes contractors

If offering a multitenant environment, the contractor at a minimum must support the establishment of the following tenants: Army, Navy, Marine Corps, Air Force, Coast Guard, Intel Community (IC) (National Security Agency (NSA), National Geospatial-Intelligence (NGA), Defense Intelligence Agency (DIA)) 4th Estate (Defense Health Agency (DHA), DISA, Defense Logistics Agency (DLA), Joint Service Provider (JSP)), COCOMs (Northern Command (NORTHCOM), Transportation Command (TRANSCOM), Strategic Command (STRATCOM)).

Additional tenants may be required by the Government based on future demand and mission requirements. The contractor shall propose the stand-up costs for the notional summary provided above per tenant, to include establishing the new tenancy, as well as the sustainment costs for supporting a maximum of 20 tenants for the proposed CSO.

Deliverables:

The Government shall require the following documents as the deliverables for this task and sub-tasks. The contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Tenancy Architecture

Distribution* One Time;

Updated annually as required

Cloud Service Administration Portal Plan

Distribution* One Time;

Updated annually as required

Directory Services Synchronization Plan

Distribution* One Time;

Updated annually as required

Distribution* One Time;

Updated annually as required

Distribution* One Time;

Updated annually as required

Distribution* One Time;

Updated annually as required

Distribution* One Time;

Updated annually as required

Multiple Domain Management Approach

Distribution* One Time;

Updated annually as required

Distribution* Weekly, as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository.

** Preliminary Design Review (PDR):

a) Deliverable will not be required until the PDR milestone has been reached as indicated within the Contractors proposed Integrated Master Schedule (IMS).

Task 5 – Subscription Licenses The contractor shall propose per-seat subscription-based pricing, and corresponding licensing model, which allows the Government to purchase or subscribe to the contractor CSO, a la carte, for a specific period and for a set price. In addition, the contractor shall provide a licensing strategy (i.e. process/procedures, mechanism) describing the contractor approach to license management, process for tracking licenses consumed by tenants, and how subscribers can transition from one user tier to another, to give the government the ability to track who has subscribed to the CSO, and has been granted access to a specific function, service or product.

Subtask 1 – Core Services The contractor shall provide a user tiered subscription based licensing structure that provides services for the functionality outlined in Figure 1. The number of users within each licensing tier will be specified at the task order-level based upon the DoD consumer’s mission requirements. In addition to Figure 1, the following table below provides an example licensing structure that maps different types of users to features and client types. Table 1 is to be used as a reference only for the licensing structure the Government is requesting. The contractors shall propose a tiered user licensing structure utilizing Attachment 6 based on the current market place offering for the proposed CSO.

Table 1 – Notional Core Service User Tiers

· Mobile

· Virtual Desktop

· Web Browser

· Mobile

· Virtual Desktop

· Web Browser

· Mobile

· Virtual Desktop

· Web Browser

Subtask 2 – Drafting and Diagraming The contractor shall identify the per user license for Drafting and Diagramming services IAW the FRD requirements PS-020 and PS-021.

Subtask 3 – Project Management The contractor shall identify the per user license for Project Management services, IAW the FRD requirements PS-022, and PS-023.

Subtask 4 – Other Services/Add-Ons/Plug-Ins In addition to the tiered user licensing structure identified for sub-task(s) 5.5.1, 5.5.2, and 5.5.3 the contractor shall independently indicate utilizing Attachment 6 any additional service/add-ons/plug-ins user licenses (i.e. Geographic Information Science) that can be utilized/purchased with the proposed CSO.

Deliverables The Government shall require the following documents as the deliverables for this task and sub-tasks. The contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Distribution* One Time;

Updated annually as required

Software License Reports

after TO Execution Standard Distribution* Monthly, as required

Licensing & Subscription Structure

Distribution* One Time;

Updated annually as required

Distribution* Weekly, as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository.

Task 6 – Additional Supporting Infrastructure, Integration Points, and Services The contractor shall be required to interoperate the proposed CSO with the following supporting infrastructure, integration points, and services based on user demand on a per-tenant basis:

Subtask 1 – Enterprise Voice Over Internet Protocol (EVoIP) The contractor shall interoperate the NIPRNet CSO to the Softswitch (SS) backbone by establishing an Assured Service (AS) Session Initiation Protocol (SIP) trunk from the DEOS edge via a contractor provided AS-SIP Gateway to the Government provided Session Border Controller (SBC). Otherwise, the contractor shall configure a SIP trunk to the Government provided SBC to enable interoperability with DISA’s NIPRNet SS backbone IAW the DEOS FRD section 8.1.3.

Subtask 2 – Enterprise Classified Voice over IP (ECVoIP) The contractor shall interoperate the SIPRNet CSO to ECVoIP Session Managers by establishing SIP trunks IAW the FRD section 8.1.4.

Subtask 3 – Mass Warning Notification The contractor shall provide integration or interoperability with Service or Component mass warning notification systems IAW the FRD section 8.6.

Subtask 4 – Local Voice Survivability The contractor shall provide local voice survivability during wide-area networks (WAN) failures that prevent end instruments/clients from registering and signaling to the centralized voice session managers, IAW the FRD section 8.1.6

Subtask 5 – E-911 The contractor shall ensure E911 calls originated from soft clients, can be routed to the Public Safety Answering Point (PSAP), or local B/P/C/S Emergency Response Centers (ERCs) IAW the FRD section 8.1.5.

Subtask 6 – Voice Over Secure IP (VoSIP) The contractor shall interoperate the SIPRNet CSO to VoSIP Session Managers by establishing SIP trunks IAW the FRD section 8.1.7.

Subtask 7 – Softswitch (SS) Backbone The contractor shall interoperate the NIPRNet CSO to the SS backbone by establishing an AS SIP trunk from the DEOS CSO edge via a contractor provided AS-SIP Gateway to the Government provided SBC. Otherwise, the contractor shall configure a SIP trunk to the Government provided SBC to enable interoperability with DISA’s NIPRNet SS backbone. In addition, the contractor shall support E.164 number routing, the DoD’s World-Wide Numbering & Dial Plan, as well as assign Defense Switched Network (DSN) and commercial phone numbers to subscribers/end instruments in accordance with the FRD section 8.1.1.

Subtask 8 – Voice Internet Service Provider (VISP) / Commercial Voice Networks (PSTN) The contractor shall leverage the SS backbone to interface the NIPRNet CSO to the DISA Voice Internet Service Provider (VISP) network, which provides Public Switched Telephone Network (PSTN) access to DoD IAW the FRD section 8.1.2.

Subtask 9 – Local Base/Post/Camp/Station Session Controllers The contractor shall interoperate the NIPRNet CSO to individual Local Session Controllers on a tenant-per-tenant basis, by establishing SIP trunks IAW the DEOS FRD section 8.1.8.

Subtask 10 – SS Backbone – Video The contractor shall interoperate the NIPRNet CSO to the SS backbone to enable video communications IAW the FRD section 8.2.1.

Subtask 11 – Unclassified Global Video Service (GVS-U) The contractor shall interoperate the NIPRNet CSO to unclassified DISA Global Video Service (GVS) using SIP or H.323 trunks IAW the FRD section 8.2.2.

Subtask 12 – Classified Global Video Service (GVS-C) The contractor shall interoperate the SIPRNet CSO to classified DISA GVS using SIP or H.323 trunks IAW the FRD section 8.2.3.

Subtask 13 – EVoIP – Video The contractor shall interoperate the NIPRNet CSO to the SS backbone to enable video communications IAW the FRD section 8.2.4.

Subtask 14 – ECVoIP – Video The contractor shall interoperate the SIPRNet CSO to DISA ECVoIP Session Managers to enable video communications IAW the FRD section 8.2.5.

Subtask 15 – Cross Domain Enterprise Services The contractor shall interface the NIPRNet CSO to existing Cross Domain Services (CDSs) to transfer data between security domains, based on user demand and on a per-tenant basis IAW the FRD section 8.3.1.

Subtask 16 – SIPR Cross Domain Enterprise Services The contractor shall interface the SIPRNet cloud service offering to existing CDSs to transfer data between security domains, based on user demand and on a per-tenant basis IAW the FRD section 8.3.1.

Subtask 17 – NIPR Global Content Directory Services (GCDS) The contractor shall leverage the Global Content Delivery Service (GCDS) to accelerate the delivery of NIPRNet CSO content and applications across the DoDIN IAW the FRD section 8.4.

Subtask 18 – SIPR Global Content Directory Services (GCDS) The contractor shall leverage the GCDS to accelerate the delivery of SIPRNet CSO content and applications across the DoDIN IAW the FRD section 8.4.

Subtask 19 – NIPR IM, Chat & Presence Federation The contractor shall facilitate IM, Chat & Presence Federation of the NIPRNet CSO with external NIPR chat systems IAW the FRD section 8.5.

Subtask 20 – SIPR IM, Chat & Presence Federation The contractor shall facilitate IM, Chat & Presence Federation of the SIPRNet CSO with external SIPRNet chat systems IAW the FRD section 8.5.

Subtask 21 – Records Management Provide integration or interoperability with the CSO to support the National Archives and Records Administration (NARA) and comply with DoDI 5015.02, and the FRD section 5.

Subtask 22 – Workflow Provide integration or interoperability with the CSO to support declassification review, legal-related reviews, and approval processes IAW the FRD section 5.1.

Subtask 23 – Redaction Provide integration or interoperability with the CSO to support Document Redaction IAW the FRD section 5.2.

Subtask 24 – Freedom of Information Act (FOIA) Provide integration or interoperability with the CSO to support create and preserve records IAW the FRD section 5.3.

Subtask 25 – eDiscovery Provide integration or interoperability with the CSO to support documentation marking, redactions, and deduplication of files IAW the FRD section 5.4.

Deliverables:

The Government shall require the following documents as the deliverables for this task and sub-tasks. The contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Format

Distribution* One Time;

Updated annually as required

Infrastructure Review Checklist Contractor Determined Format

Distribution* One Time;

Updated annually as required

Infrastructure Analysis/Evaluation Report Contractor Determined Format

Distribution* One Time;

Updated annually as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository.

** Critical Design Review (CDR):

a) Deliverable will not be required until the CDR milestone has been reached as indicated within the Contractors proposed Integrated Master Schedule (IMS).

Task 7 – Data and Readiness Assessments The contractor shall perform a comprehensive evaluation of DoD customers legacy infrastructure and data that will be migrated to the DEOS service. Evaluations shall clearly detail traffic flow, system components, applications, and integration dependencies, at a minimum, and shall retain customer profiles and customer data stored on the legacy systems.

Subtask 1 – Directory Service The contractor shall analyze the existing enterprise directory, and other customer directories, identity services, and domains, to identify the necessary execution activities, migration plan, and implementation required to optimize the existing directory environments in support of migrating directory data into the new DEOS service. Examples include directory object normalization, non-person entity standardization, and attributes cleanup/mapping to allow synchronization with the new DEOS service.

The contractor shall configure the DEOS service to authenticate users IAW the DEOS FRD requirements (e.g. PIV certificate, alternate DoD approved persona-specific authenticator or persona-specific assertion, DoD approved multifactor authentication, or username/password) as directed by the Government IAW DoDI 8500.1 and DoDI 8520.03.

DEOS directories and authentication methods shall support the use of current DoD approved Public Key Infrastructure (PKI) mechanisms (e.g. PKI, Common Access Cards (CACs), SIPR Tokens and derived credentials) for authentication on virtual desktops, web browsers, thick clients, and DoD approved mobile platforms, and shall check for certificate expiration, against a DoD Certificate Authority (CA) that issued the certificate, confirming the certificate has not been revoked. Revocation status shall be determined by looking up the user-provided certificate in a locally stored Certification Revocation List (CRL) or via an Online Certificate Status Protocol (OCSP) call across the network to the Robust Certificate Validation Service (RCVS).

Subtask 2 – Email The contractor shall assess existing email environments and data to ensure an optimum migration. Examples of activities include, but are not limited to the evaluating email profiles, email data volume, PST data volume, POD architecture/locations, identification and cleanup of defunct mailboxes, distribution lists and delegations, and upgrades of legacy hardware (i.e. servers).

Subtask 3 – Content Management The contractor shall analyze existing content management environments and data to ensure an optimum migration. Examples of activities include site structure/content analysis, site content volume, identification and cleanup of folder hierarchies, determining user permissions, and ensuring workflows compliance.

Subtask 4 – Instant Messaging (IM), Chat, & Presence The contractor shall assess existing IM/chat environments and data to ensure an optimum migration. Examples include IM/chat profiles, IM/chat contact lists, persistent chat group migration, analysis of messages stored in persistent chat groups, and on a case by cases basis analysis of chat federation with other systems.

Subtask 5 – Productivity Suite The contractor shall evaluate the productivity suite environment and data to ensure an optimum migration. Examples include updating thick applications prior to migration, cleaning and reducing duplicate files, and normalizing document versions before starting the migration.

Subtask 6 – Web Conferencing The contractor shall analyze the existing web conferencing environment and data to ensure an optimum migration. Examples include evaluating persistent conferences, access control and delegation of users to persistent web conferences, persistent web conference content volume, analyzing local network configuration, bandwidth availability and overall readiness, and identification and cleanup of folder hierarchies.

Subtask 7 – File Storage The contractor shall assess existing local user data environments to ensure an optimum migration. Examples include analyzing content and volume of files located in local device stores (e.g. desktops, hard drives), as well as network drives.

Subtask 8 – Native Audio The contractor shall evaluate existing native audio environments to ensure optimum migration. Examples include migrating contact lists, call logs, analyzing local network configuration, bandwidth availability and overall readiness for native audio traffic.

Subtask 9 – Native Video The contractor shall evaluate existing native video environments to ensure optimum migration. Examples include migrating contact lists, call logs, analyzing local network configuration, bandwidth availability and overall readiness for native video traffic.

Deliverables:

The Government shall require the following documents as the deliverables for this task and sub-tasks. The contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Distribution* One Time;

Updated annually as required

Core Capability Data Readiness Review Checklist

Standard Distribution* One Time;

Updated monthly as required

Standard Distribution* One Time;

Updated monthly as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository.

Task 8 – User & Data Migration The Government must minimize the business impacts of data migration downtime, data integrity issues, costs, and control problems. The Service Provider will be required to develop a data migration process model and utilize robust methodology (i.e. data profiling) and tools for migrations. The contractor will provide the manpower, tools, and hardware needed to migrate existing services (e.g. DEPS, DEE), as well as the customer data and support operations necessary to deliver the CSO to approximately 3.12 million DoD subscribers. During migration, the contractor shall support dual operations, ensuring that users migrated to the cloud offering are able to collaborate with those that have not been migrated to the cloud. The contractor shall ensure that customer profiles and data stored on the legacy systems are completely migrated to the CSO as agreed upon with the Government and to the customer’s satisfaction. The CSO must support the collection, management, and publishing of information in digital format using a web interface. User/organizational content may take the form of text (such as electronic documents), multimedia files (such as audio or video files), or any other file type that requires content lifecycle management.

Subtask 1 – Directory Service The contractor shall establish a link to Identity Synchronization Services (IdSS) via Security Assertion Markup Language (SAML) interface to synchronize user directory data, attributes, certificates, and database objects that support the authentication and authorization required by the CSO. Once synchronization is established, the contractor shall leverage the Enterprise Directory for provision/de-provisioning of user accounts. The contractor shall provide government authentication using SAML 2.0 integration with a Government specified identity provider utilizing DoD approved multi-factor authentication mechanisms or username and password according to agency policy. The contractor shall ensure that FRD requirements are being met during migration.

Subtask 2 – Email The contractor shall migrate user email data, mailboxes, non-person entity mailboxes (e.g. conference rooms), group mailboxes, calendars, contact lists and distribution lists from their legacy systems. The contractor shall also migrate journaled messages as well as files needed for legal or regulatory compliance. The contractor shall ensure coexistence of the legacy email systems with the proposed CSO. The contractor shall migrate mailbox data from production source system to include message store, calendar, and contacts. The contractor shall provide integration between the CSO and Government mobile devices. The contractor shall establish dual delivery of messages during the transition period. After migration, the service shall provide access to historical data that is subject to records management provisions, as well as access to legacy email server archives.

Subtask 3 – Content Management The contractor shall migrate content management sites, to include structure, content, workflows, and permissions from their legacy systems. The contractor shall also migrate files needed for legal or regulatory compliance. The contractor shall ensure coexistence of the legacy content management system with the proposed CSO. The contractor shall provide integration between the cloud content management offering and Government mobile devices. After migration the service shall provide access to historical data that is subject to records management provisions, as well as access to legacy content management archives.

Subtask 4 – Instant Messaging (IM), Chat, & Presence The contractor shall enable IM/Chat & Presence capabilities for all users’ part of the CSO, regardless of tenancy association if using a multitenancy environment. In addition, the contractor shall migrate IM/chat profiles, IM/chat contact lists, persistent chat groups, and messages stored in persistent chat groups from the legacy IM/chat systems to the cloud IM/chat offering. The contractor shall ensure that chat federation with other systems is maintained with the legacy IM/chat system and the CSO IM/chat offering during migration.

Subtask 5 – Productivity Suite The contractor shall migrate legacy word processing, spreadsheet, presentation, database management, and diagramming and project management files from on premise repositories to the CSO. The contractor shall ensure legacy files can be opened and seen in the CSO. During migration, the contractor shall ensure users that have not been migrated can access files/data stores that have been migrated to the CSO.

Subtask 6 – Web Conferencing The contractor shall migrate persistent web conference and prerecorded conferencing sessions from the legacy web conferencing system to the cloud web conferencing offering. The contractor shall ensure access control and delegation of users to persistent web conferences is maintained once migrated. During migration, the Contractor shall ensure users that have not been migrated can access persistent web conferences that have been migrated to the CSO.

Subtask 7 – File Storage The contractor shall migrate individual user data stored in local user data environments (e.g. desktops, hard drives) as well as network drives, into each user’s file storage partition in the cloud offering. The contractor shall ensure access control is maintained once migrated to the cloud offering. During migration, the contractor shall ensure users can access files that have been migrated to the CSO.

Subtask 8 – Native Audio The contractor shall enable native audio calling capabilities for all users’ part of the CSO, regardless of tenancy association if using a multitenancy environment. In addition, the contractor shall migrate legacy DSN and PSTN telephone numbers in E.164 format to subscriber profiles, as well as any voicemail messages required for legal compliance.

Subtask 9 – Native Video The contractor shall enable native video calling capabilities for all users’ part of the CSO, regardless of tenancy association if using a multitenancy environment. In addition, the contractor shall migrate legacy DSN and PSTN telephone numbers in E.164 format to DEOS subscriber profiles, move personal video teleconferences (VTCs) to native video conferences.

Deliverables:

The Government shall require the following documents as the deliverables for this task and sub-tasks. The Contractor shall incorporate these deliverables into the proposed PWS. In addition, the contractor shall propose any additional deliverables based upon their technical and management approach that collectively provide sufficient evidence of satisfactory performance of activities required for this task and sub-tasks as applicable.

Distribution* One Time;

Updated annually as required

Monthly User Migration Reports

after TO Execution Standard Distribution* Monthly, as required

Distribution* One Time;

Updated annually as required

after TO Execution Standard Distribution* Monthly, as required

* Standard Distribution:

a) 1 copy of the transmittal letter without the deliverable to the Contracting Officer shall be uploaded to https://www.ditco.disa.mil/dcop/Public/ASP/dcop.asp.

b) 1 copy of the transmittal letter with the deliverable to the Primary COR or Government designated repository.

Task 9 – Training Conduct technical reviews and develop appropriate materials to train system users and instructors in preparation of operational deployments. Assess training requirements based on system and functional baseline. Develop training artifacts in support of operations including but not limited to Standard Operating Procedures (SOPs), and Tactics, Techniques and Procedures (TTPs). Provide online documentation to train users and administrators on the service being provided to include access, troubleshooting guides, features, (i.e. NetOPS) provisions, and capabilities. Documentation and support shall include user groups such as but not limited to Senior Executive Service (SES), Government administrators, and types of end users that will be impacted by consuming the new service Subtask 1 – Classroom/Instructor Led Provide in-person, classroom/instructor led training to government designated personnel to explain software features, functions, and common tasks associated with DEOS services and capabilities.

Subtask 2 – Individual Hands-On Provide individual hands-on training to Government designated…