Attachment_B_Draft_DEOS_Statement_of_Objectives.docx

ATTACHMENT B

DRAFT

STATEMENT OF OBJECTIVES (SOO)

1. Background The Department of Defense (DoD) requires an integrated enterprise cloud service offering (CSO) that provides common communication, collaboration, and productivity capabilities that are mission-effective, efficient, more widely accessible, and 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 productivity suite.

2. Objectives DEOS will support the Department’s vision to move towards an integrated/interoperable communication, collaboration, and productivity service, by facilitating trusted information sharing between Combatant Commands, Services and Agencies (CC/S/As), and through the consolidation of multiple DoD enterprise services into a single environment. In addition, 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 DoD-wide legacy capabilities.

The DEOS CSO will be acquired by DISA using an unrestricted, competitively awarded, single-award Firm-Fixed Price (FFP) Blanket Purchase Agreement (BPA) with a contractor who will provide a widely used/widely available, and non-developmental and fully integrated collaboration solution. [footnoteRef:1]The BPAperiod of performance will be a 5-year base ordering period and two 2 year option periods and one 1 year option period.. The BPA 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. [1: The final Request for Quote is expected to be accompanied by an Individual Deviation to Federal Acquisition Regulation (FAR) 8.405-3(d) to increase the period of performance from a one year base period to 5 year base period and two 2 year options and one 1 year option period (i.e for a maximum total of ten years). ]

3. Scope The DEOS CSO may scale to an anticipated 3.15 million DoD consumers, and over 4 million directory objects, which includes supporting DoD CC/S/As across many locations to include local base/post/camp/station (B/P/C/S), 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, and 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 the key DoD supporting infrastructure, services, and major integration points that will reside primarily on-premises as part of the Government’s responsibility. The Cloud Service Provider (CSP) will be responsible for ensuring interoperability and integration with these major service support functions and integration points. Additional requirements are outlined in section 6, and section 7 of the Functional Requirements Document (FRD) Attachment A.

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 NIPRNet and SIPRNet implementations in United States territories and possessions, the Government expects to leverage DoD approved commercially hosted facilities to meet the DEOS requirements. However, due to DoD data sovereignty requirements, the contractor must implement their NIPRNet and SIPRNet CSO within DoD data centers (e.g., Stuttgart, Wiesbaden, Capodichino) for locations outside of the United States territories and possessions.

For locations outside of the United States territories and possessions, the contractor must provide a standalone environment within a DoD data center. The solution must be self-contained and must include the required infrastructure, hardware, software, and auxiliary components required to implement, management, and maintain the CSO environment within the DoD data center. The Government expects the contractor to describe the details of their solution to include physical requirements (e.g., 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 (e.g., 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.

4. Performance Requirements The contractor shall propose performance tasks that fully adhere to the requirements of the solicitation and the DEOS FRD (Attachment A) so that DEOS is available to end users. The contractor will perform all necessary activities as well as provide the required documentation association to achieve and maintain the necessary DEOS Authorization to Operate (ATO) decisions as a national security system on the DoDIN, utilizing the Performance Work Statement (PWS) format (Attachment C) provided as part of this solicitation.

4.1 Task 1 – NIPRNet Environment

The contractor shall deliver a CSO that enables collaboration across the DoD enterprise. The NIPRNet CSO shall include System Wide, Core Services (i.e., email, IM/chat, web conferencing, native audio, native video, content management, and productivity suite), and DoD Information Network (DoDIN) Protection requirements in accordance with (IAW) the FRD sections 1, 2, and 3 having a network category of “Both” or “NIPR”.

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

4.1.1 Subtask 1 – United States Territories and Possessions

Provide a geographically dispersed off-premises CSO within a DoD private/community hybrid cloud that meets Impact Level 5 requirements IAW the DoD CCSRG and the FRD.

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

4.2 Task 2 – SIPRNet Environment

The contractor shall deliver a CSO that enables collaboration across the DoD enterprise. The SIPRNet CSO shall include System Wide, Core Services (i.e., email, IM/chat, web conferencing, native audio, native video, content management, and productivity suite), and DoDIN Protection requirements IAW the FRD sections 1, 2, and 3, having a network category of “Both” or “SIPR”. Furthermore, the contractor shall be required to interface the CSO to the core integration points identified in the FRD section 6. Lastly, the contractor shall adhere to the performance objectives identified in the FRD section 8, and shall be required to perform testing activities/events (i.e., integration, acceptance, operational) IAW the FRD section 9, to verify the proper interoperability between the CSO and core integration points (FRD section 6).

4.2.1 Subtask 1 – United States Territories and Possessions

Provide geographically dispersed off-premises CSO within a DoD private/community cloud that meets Impact Level 6 requirements in accordance with the DoD CC SRG and the FRD.

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

4.3 Task 3 – Denied, Disconnected, Intermittent, Limited Bandwidth (D-DIL) Environment The contractor shall provide a solution able to operate when disconnected from the main CSO that allows for continuity of operations while experiencing a Denied, Disconnected, Intermittent or Limited Bandwidth condition IAW section 5 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.) that may be the primary provider of the service for an extended period of time. The contractor shall plan for these variations in D-DIL service based on a per tenancy or standalone environments that are implemented.

4.3.1 Subtask 1 – D-DIL Prototype

Engineer, configure, and deploy a prototype for the D-DIL use cases in appendix A of the FRD for NIPRNet and SIPRNet environments. The prototype shall demonstrate the functionality and provide the ability to validate the technical feasibility for the D-DIL use cases. The prototype shall have all the functionality of the D-DIL product/solution and capable of supporting real-world scenarios.

4.3.2 Subtask 2 – NIPRNet D-DIL Environment

Engineer, configure and deploy a standalone, independently operable D-DIL solution that communicates with the NIPRNet CSO when connectivity is regained to synchronize data. D-DIL deployments may experience lower cloud service availability.

4.3.3 Subtask 3 – SIPRNet D-DIL Environment

Engineer, configure and deploy a standalone, independently operable D-DIL solution that communicates with the SIPRNet CSO when connectivity is regained to synchronize data. D-DIL deployments may experience lower cloud service availability.

4.3.4 Subtask 4 – D-DIL Software/Subscription Licenses

The contractor shall offer annual subscription licenses using a fixed fee for small, medium, and large user populations.

4.3.5 Subtask 5 – Infrastructure

The contractor shall offer a pricing model for the software, hardware and virtual infrastructure required to enable D-DIL instances for the following three scalability models: small D-DIL deployments consisting of less than 300 personnel; medium D-DIL deployments consisting of 300 -1,500 personnel; and large D-DIL deployments consisting of 1,500 - 6,000 personnel.

4.4 Task 4 – User Tenancy Structure

The Government will allow flexibility and expects the contractor to propose a tenancy[footnoteRef:2] structure. As a result, the contractor shall propose an architecture, which meets the requirements of the FRD, and allows each Combatant Commands, Services and Agencies (CC/S/As)[footnoteRef:3] the ability to apply controls and restrictions, records disposition schedules for their users and data, site configuration, as well as user, feature, and functionality management to meet their mission needs. This includes the ability to grant/remove administrative privileges, user roles, and the ability to control license assignment within the solution. The solution needs to address the specific complexities and practices of the DoD (e.g., permanent change of stations, Service members also members of COCOM’s) and enable DoD wide collaboration. The Government requires a tenancy structure to support approximately 3.15 million subscriber’s part of the DoD enterprise. [2: A tenant is defined as a client or organization that owns and manages a specific instance of a cloud service. Each tenant is distinct and separate from other tenants in that it isolates customer data, prevents identity information from co-mingling (e.g., users and administrators of one tenant cannot accidentally or maliciously access data in another tenant) and has an account that provides unrestricted administrative access to features and functions of the instance.

] [3: Additional Tenancy considerations and legacy population breakdown are located in Appendix D, F, and G of the Functional Requirement Document (FRD).]

4.5 Task 5 – Subscription Licenses

The contractor shall propose a per-seat subscription-based pricing, and a corresponding licensing model in accordance with Table 9 – Notional Core Service User Tiers, which allows the Government to purchase or subscribe to the contractor CSO for a specific period and for a set price.

4.5.1 Subtask 1 – Core Services

The contractor shall provide a per subscription based licensing structure for the functionality outlined in Figure 1. The exact number of users within each licensing tier will be specified at the task order-level upon task order execution. In addition to Figure 1, the contractor shall reference the information presented in Table 9 – Notional Core Service User Tiers, to propose a licensing structure that maps to the CSO’s commercial licensing structure. Table 9 should be used as a reference only for the licensing structure the Government is requesting.

Table 9 – Notional Core Service User Tiers

· Mobile App(s)

· Virtual Desktop

· Web Browser

· Mobile App (s)

· Virtual Desktop

· Web Browser

4.5.2 Subtask 2 – Drafting and Diagraming

The contractor shall provide a per user license for Drafting and Diagramming services that assist with the creation of diagrams, flow and organizational charts.

4.5.3 Subtask 3 – Project Management

The contractor shall provide a per user license for Project Management services that assist with assigning resources to tasks and tracking project progress.

4.5.4 Subtask 4 – Other Services/Add-Ons/Plug-Ins

In addition to the tiered user licensing structure identified for sub-task(s) 4.5.1, 4.5.2, and 4.5.3 the contractor shall independently indicate in Attachment F any additional service add-ons, plugins, licenses (e.g., Geographic information system) that can be purchased with the proposed CSO.

4.6 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 at the task order-level upon task order execution:

4.6.1 Subtask 1 – Enterprise Voice Over Internet Protocol (EVoIP)

The contractor shall leverage the SS backbone to interface the NIPRNet CSO to the DISA Enterprise Voice over IP (EVoIP) infrastructure, IAW the FRD section 7.1.3 and SOO section 4.6.7, Subtask 7 – Softswitch (SS) Backbone.

4.6.2 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 7.1.4.

4.6.3 Subtask 3 – Mass Warning Notification

The contractor shall provide integration or interoperability with Service or Component mass warning notification systems IAW the FRD section 7.6.

4.6.4 Subtask 4 – Local Voice Survivability

The contractor shall provide continuity of voice services and local voice survivability when the B/P/C/S is severed from the DISN, IAW the FRD section 7.1.6

4.6.5 Subtask 5 – E-911

The contractor shall ensure E-911 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 7.1.5.

Note: Specific E-911 services, such as national Private Switch-Automatic Location Information (PS ALI), local PS ALI (when offered), and location discovery capabilities, are expected to be provided through already established contract vehicles (e.g., Networx contract) outside of the DEOS contract.

4.6.6 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 7.1.7.

4.6.7 Subtask 7 – Softswitch (SS) Backbone

The contractor shall interoperate the NIPRNet CSO to the SS backbone by using one of the following methods:

· Configure a SIP Trunk to the Government provided SBCs, if the Government provided APL certified SBCs could translate DEOS CSO signaling traffic to AS-SIP.

· Provide an AS-SIP Gateway, to translate DEOS CSO proprietary based signaling traffic to AS-SIP.

In addition, the contractor shall support E.164 number routing, the DoD’s World-Wide Numbering & Dial Plan, and shall assign Defense Switched Network (DSN) and commercial phone numbers to subscribers/end instruments in accordance with the FRD section 7.1.1.

4.6.8 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), which provides Public Switched Telephone Network (PSTN) access to DoD IAW the FRD section 7.1.2 and SOO section 4.6.7 Subtask 7 – Softswitch (SS) Backbone.

4.6.9 Subtask 9 – Local Base/Post/Camp/Station Session Controllers The contractor shall interoperate the NIPRNet CSO to individual Local Session Controllers (LSCs) on an as needed basis per CC/S/A by establishing SIP trunks IAW the DEOS FRD section 7.1.8.

4.6.10 Subtask 10 – Unclassified Video Interoperability

The contractor shall interoperate the NIPRNet CSO to the SS backbone to enable video communications IAW the FRD section 7.2.1.

4.6.11 Subtask 11 – Classified Video Interoperability

The contractor shall interoperate the SIPRNet CSO to DISA ECVoIP Session Managers to enable video communications IAW the FRD section 7.2.2.

4.6.12 Subtask 12 – NIPR Local B/P/C/S Provided VTC Systems

The contractor shall interoperate the NIPRNet CSO to local base/post/camp/station provided VTC systems IAW the FRD section 7.2.3.

4.6.13 Subtask 13 – SIPR Local B/P/C/S Provided VTC Systems

The contractor shall interoperate the SIPRNet CSO to local base/post/camp/station provided VTC systems IAW the FRD section 7.2.3.

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

4.6.15 Subtask 15 – 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 7.4.

4.6.16 Subtask 16 – 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 7.5.

4.6.17 Subtask 17 – 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 7.5.

4.6.18 Subtask 18 – Records Management

Configure the CSO to support NARA requirements IAW DoDI 5015.02, and the FRD section 4.

4.6.19 Subtask 19 – Workflow

Configure the CSO to support declassification review, legal-related reviews, and approval processes IAW the FRD section 4.1.

4.6.20 Subtask 20 – Redaction

Configure the CSO to support Document Redaction IAW the FRD section 4.2.

4.6.21 Subtask 21 – Freedom of Information Act (FOIA)

Provide enhanced FOIA functionality as part of the enhanced Records Management capability provided by the CSO IAW the FRD section 4.3.

4.6.22 Subtask 22 – eDiscovery

Configure the CSO to support documentation-marking, redactions, and deduplication of files IAW the FRD section 4.4.

4.6.23 Subtask 23 – Voicemail

Provide industry standard voicemail for DEOS subscribers IAW the FRD section 7.1.10.

4.6.24 Subtask 24 – Unified Messaging

Integrate the DEOS provided voicemail with the DEOS provided email to provide unified messaging. Both voicemail and email services must be provided by the same CSO. Otherwise, at the customer request, integrate the DEOS provided email with non-DEOS provided voicemail systems to provide unified messaging IAW the FRD section 7.1.11.

4.7 Task 7 – Data Migration & Readiness Assessments

The contractor shall perform a comprehensive evaluation of CC/S/A data, to prepare the environment for migration to DEOS. Evaluations shall clearly outline migration traffic flows, involved system components, applications, and integration dependencies.

4.7.1 Subtask 1 – Directory Service

The contractor shall analyze the existing enterprise directory, and as needed, customer specific directories, to outline the necessary execution activities, migration strategy, implementation plan, and configuration changes required to optimize the existing directory environment and support the successful migration of directory data into the new DEOS service. Examples include directory object normalization, non-person entity (NPE) 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 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.

4.7.2 Subtask 2 – Email

The contractor shall assess existing email environments and data to ensure an optimal migration. Examples of activities include, but are not limited to, evaluating email profiles, email data volume, PST data volume, and cleanup of mailboxes, distribution lists and delegations clearly identified by the Government.

4.7.3 Subtask 3 – Content Management

The contractor shall analyze existing content management environments and data to ensure an optimal migration. Examples of activities include, but are not limited to, site structure/content analysis, site content volume, identification and cleanup of folder hierarchies, determining user permissions, evaluate existing workflows, and identification of lost functionality with suggestions as to how to replace it.

4.8 Task 8 – User & Data Migration

The contractor shall develop a data migration plan that minimizes the business impact to day-to-day operations such as downtime, data integrity issues, and costs. The contractor shall provide the manpower, tools, and hardware needed to migrate existing services, operations, and customer data necessary to deliver the CSO to approximately 3.15 million DoD subscribers. During migration, the contractor shall support dual operations, ensuring that users migrated to the CSO are able to collaborate with those that have not been migrated. In addition, the contractor shall ensure that customer profiles and data stored on the legacy systems are 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.

4.8.1 Subtask 1 – Directory Service

The contractor shall 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 Service (EDS) for provision/de-provisioning of user accounts. The contractor shall provide Government authentication using a Government specified identity provider (IdP). The contractor shall ensure that FRD requirements are being met during migration.

4.8.2 Subtask 2 – Email

The contractor shall migrate user email data, mailboxes, non-person entity (NPE) mailboxes (e.g., conference rooms), group mailboxes, calendars, contact lists and distribution lists from legacy systems. The contractor shall also migrate journaled messages as well as files needed for legal or regulatory compliance. During migration, the contractor shall ensure coexistence of the legacy email systems with the proposed CSO, shall establish dual delivery of messages during the transition period, and shall support calendar visibility with legacy email systems.

4.8.3 Subtask 3 – Content Management

The contractor shall migrate content management sites, to include structure, content, workflows, and permissions from 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 during migration. The contractor shall apply metadata tagging to migrated documents for RM purposes.

4.8.4 Subtask 4 – Business Voice

The contractor shall migrate legacy DSN and PSTN telephone numbers in E.164 format to subscriber profiles.

4.8.5 Subtask 5 – Business Video

The contractor shall migrate legacy DSN and PSTN telephone numbers in E.164 format to DEOS subscriber profiles.

4.9 Task 9 – Training

The contractor shall develop training materials to prepare DEOS subscribers, privileged users, and instructors on the CSO features and functions in preparation for migration, deployments and day-to-day operations. The contractor shall develop training artifacts to include Standard Operating Procedures (SOPs), Tactics, Techniques and Procedures (TTPs), and online documentation to train users and administrators on the service.

4.9.1 Subtask 1 – Subscriber - Classroom/Instructor Led

Provide in-person, classroom/instructor led training to subscribers. Training content shall include explaining software features, functions, and common tasks associated with DEOS services and capabilities.

4.9.2 Subtask 2 – Subscriber - Individual Hands-On

Provide individual hands-on training to subscribers. Training content shall include explaining software features, functions, and common tasks associated with DEOS services and capabilities.

4.9.3 Subtask 3 – Subscriber - Online Instructor Led Training Provide live online instructor led training to subscribers. Training content shall include explaining software features, functions, and common tasks associated with DEOS services and capabilities.

4.9.4 Subtask 4 – Subscriber - Computer Based Training (CBT)

Provide the Government with training materials in digital format (e.g., recorded webinars, factsheets) that can be distributed and published to a web portal, established and maintained by the Government. Provided CBT material shall allow users to troubleshoot and perform common tasks on the service without the need for direct instructor interaction.

4.9.5 Subtask 5 – Privileged User- Classroom/Instructor Led

Provide in-person, classroom/instructor led training to Government designated privileged users to explain advanced concepts, software features, and common administrative functions associated with the configuration and management of DEOS services and capabilities (e.g., content management administrators, records management officers, FOIA officers, etc).

4.9.6 Subtask 6 –Privileged User- Individual Hands-On

Provide individual hands-on training to Government designated privileged users to explain advanced concepts, software features, and common administrative functions associated with the configuration and management of DEOS services and capabilities (e.g., content management administrators, records management officers, FOIA officers, etc).

4.9.7 Subtask 7 – Privileged User- Online Instructor Led Training Provide live online instructor led training to Government designated privileged users to explain advanced concepts, software features, and common administrative functions associated with the configuration and management of DEOS services and capabilities (e.g., content management administrators, records management officers, FOIA officers, etc).

4.9.8 Subtask 8 – Privileged User- Computer Based Training (CBT) Provide the Government with training materials in digital format (e.g., recorded webinars, factsheets) that can be distributed and published to a web portal, established and maintained by the Government. Provided CBT material shall allow Government designated privileged users to troubleshoot and perform common tasks on the service without the need for direct instructor interaction (e.g., content management administrators, records management officers, FOIA officers, etc).

4.9.9 Subtask 9 – Trainer - Classroom/Instructor Led

Provide in-person, classroom/instructor led training to Government designated trainers to enable them to explain and train other DEOS subscribers and privileged users on software features, and common functions associated with DEOS services and capabilities.

4.9.10 Subtask 10 – Trainer - Individual Hands-On

Provide individual hands-on training to Government designated trainers to enable them to explain and train other DEOS subscribers and privileged users on software features, and common functions associated with DEOS services and capabilities.

4.9.11 Subtask 11 – Trainer - Online Instructor Led Training

Provide live online instructor led training to Government designated trainers to enable them to explain and train other DEOS subscribers and privileged users on software features, and common functions associated with DEOS services and capabilities.

4.9.12 Subtask 12 – Trainer - Computer Based Training (CBT)

Provide the Government with training materials in digital format (e.g., recorded webinars, factsheets) that can be distributed and published to a web portal, established and maintained by the Government. Provided CBT material shall allow Government designated trainers to learn software features, and common functions associated with DEOS service, without the need for direct instructor interaction.

4.10 Task 10 – Engineering Support

This section outlines requirements for technical/engineering support services. Support services may be provided to the DEOS Program Management Office (PMO) directly, or to DEOS customers. The contractor shall provide the full range of engineering support necessary to incorporate new/future technologies into the DEOS service/baseline after initial deployment and must have expertise in both traditional IT infrastructure and cloud computing. The contractor shall provide comprehensive technical/engineering support services to include design, implementation, modification, and sustainment of DEOS projects and work activities. The scope includes any future work efforts for both United States Territories and Possessions, as well as locations outside of the United States Territories and Possessions, NIPRNet and SIPRNet environments

SIGNIFICANCE OF SYSTEMS ENGINEERING TECHNICAL REVIEWS REQUIRED UNDER THIS CONTRACT

The effort to be performed under this contract includes a series of technical reviews in accordance with IEEE Standard 15288.2 for Technical Reviews and Audits on Defense Programs as part of Post Award Task Order Meetings/Conferences. The parties agree that the fundamental purpose of these systems engineering technical reviews (SETRs) is to review the design/development to date of the DEOS system and in so doing to assess the progress to date towards meeting the technical and/or performance requirements set forth in this contract. As such, each review will be tailored to ensure that the emerging design/development of the DEOS system is ready to enter the next phase towards completion of this contract. The parties further agree that Government approval of any particular technical review does not eliminate nor modify the Contractor’s responsibility to perform in accordance with the terms and conditions of this contract. In that regard, unless expressly directed in writing by the Procuring Contracting Officer, the Contractor is free to adopt or reject any recommendations or advice offered by the Government during the conduct of any of the required SETRs. Moreover, in the event the Contractor is expressly directed in writing by the Contracting Officer to implement a change(s) to the design/development of the DEOS system, this clause shall remain in full force and effect unless the Contractor provides written notice to the Contracting Officer requesting relief from the requirements of this clause. Such written request shall provide detailed rationale to support and justify the Contractor’s request for relief. In addition, such written request shall be made not later than five (5) days after being directed in writing by the Contracting Officer to implement said change and the Contractor waives any and all entitlements to relief from the requirements of this clause by failing to make a timely written request to the Contracting Officer.

4.10.1. Subtask 1 – Systems Engineering

The contractor shall employ disciplined systems engineering processes including, but not limited to, requirements development, technical management and control, systems engineering technical reviews, and system/software design and architecture. In addition, the contractor shall implement system engineering best practices associated with risk management, configuration management, data management, test and evaluation (T&E), and verification and validation (V&V) throughout the period of performance of the task orders.

4.10.2. Subtask 2 – Architecture and Service/System Design Engineering The contractor shall support the design and development of systems and applications and their integration into the overarching enterprise DoD architecture. The contractor shall provide all required design and development documents and supporting architectural documentation in compliance with Department of Defense Architectural Framework (DoDAF) Enterprise Architecture guidance, or other frameworks as identified in the task orders.

4.10.3. Subtask 3 – Network Engineering

The contractor shall support routing and switching analysis of enterprise-wide and large-scale networking infrastructure (CAN, MAN, WAN), to include, but not limited to, analyzing circuits, troubleshooting routing protocol configurations, making route optimization recommendations, highlighting traffic congestion points, and ensuring quality of service policies are properly configured. The contractor shall ensure network components are running the required hardware and software approved by the government, and validates network systems and transport layers are in compliance with industry standards and protocols. The contractor shall evaluate network problems, workflows, usage and trends to make organizational and planning recommendations, while developing appropriate corrective action.

4.10.4. Subtask 4 – Configuration Management Engineering

The contractor shall accomplish Configuration Management (CM) activities in accordance with DESMF best practices. CM activities include baseline identification, change control, status accounting, and auditing.

4.10.5. Subtask 5 – Test Engineering

The contractor shall develop dynamic provide a testing environment that will be used to validate the CSO satisfies the government’s technical and operational requirements. The contractor shall establish and maintain an integrated test lab that is capable of supporting a full range of integration test activities for both the currently fielded system in as well as maintenance/modernization releases. The contractor shall support of the following test activities which include, but are not limited to: product testing (i.e., regression testing and new capability testing/evergreen); , operational scenarios testing (e.g., real world production environment simulation testing) considering system topology, and concept of operations, disaster recovery, clustering, and load balancing; ), stress and longevity testing (e.g., load and throughput, speed of service, and duration); , interoperability testing (e.g., protocol translation, discrete systems communication); , security testing (e.g., VPN, Firewall, security configuration)

4.10.6. Subtask 6 – Cybersecurity

The contractor shall assess the entire cybersecurity posture of the DEOS service and shall make recommendations to reduce support costs and shall expose and remediate configuration and operational security issues before they affect the DEOS service. The contractor shall monitor the environment for security events and operational health. The contractor shall prevent the compromise of privileged account credentials from cyberattacks, promote credential hygiene and cybersecurity best practices, while ensuring systems/services comply with DoD cybersecurity requirements. The contractor shall coordinate with designated government personnel to ensure the DEOS services are available and optimized through security gateways.

4.10.7. Subtask 7 – Mobility Engineering

The contractor shall support the integration of the DEOS CSO and delivery of DEOS services to DoD approved mobile devices. The contractor shall support troubleshooting the DoD's Mobility Infrastructure (e.g., Mobile Device Management (MDMs), Gateways, security services and specific mobile PKI solutions) that are in direct support of DEOS services. The contractor shall ensure that all systems/services (e.g., email, web conferencing, file storage) are available via approved DoD mobile devices and that required DEOS mobile applications, tools, framework, and MAS are available for use across DoD.

4.11 Task 11 – Contract and Task Order Management

Provide all services necessary to manage and oversee all aspects of the contract and task order(s). Use key performance parameters to monitor work performance, measure results, and ensure delivery of contracted product deliverables and solutions support management and decision-making and facilitate communications. Identify risks, resolve problems and verify effectiveness of corrective actions. Institute and maintain a process that ensures problems and action items discussed with the Government are tracked through resolution and shall provide timely status reporting. Results of contractor actions taken to improve performance shall be tracked, and lessons learned incorporated into applicable processes. Establish and maintain a documented set of disciplined, mature, and continuously improving processes for administering all contract and task order efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness, and consistently high-quality delivery. The contractor shall provide a Monthly Service Utilization, Capacity, Outage and Upgrade Status and Forecast Report and resources (i.e., personnel) required for closeout operations prior to contract completion.

5. Performance Standards Performance Standards will be identified at the Task Order Level. Routine inspections by the Government will be performed with or without notice. Each TO will cite the specific performance standards that apply to the requirements of that TO.

6. Incentives The identification of incentives (both positive and negative) will be addressed in each task order and reported in the Contractor Performance Assessment Reporting System (CPARS). In general, positive incentives may be used to reward significantly outstanding performance on a task order. Significantly, outstanding performance may include employing process improvements and increased efficiencies, which result in significant cost savings for the Government, without compromising the quality of services or products provided. Adversely, negative incentives may be utilized to penalize substandard or unacceptable quality of services or products in performance of the task order. The contractor is incentivized to earn favorable Government reviews to support continuation of DISA requirements and support contract awards with other Government agencies seeking DISA’s input on the contractor’s past performance.

7. Place of Performance Specific work location will be determined at the TO level. Work may be performed on-site, at all United States territories and possessions and Non-United States territories and possessions Government facilities or at the contractor’s facility, sub-contractor facility, supplier, or other designated locations (e.g., corporate, 3rd party, or subcontractor). The Government will, if required, further specify the Periodic Progress Meetings at the task order level. On-site spaces at Government facilities may be revoked at any time per Government requirements.

Places of Performance shall include the following, at a minimum and subject to change based on TO requirements: Ft. Meade (DISA HQ), Scott AFB, Stuttgart, GE, Honolulu, HI, and Ogden. Performance may be required at any Department of Defense location, worldwide.

For any contractor/sub-contractor facility, supplier, or other designated locations (e.g., corporate, 3rd party, or subcontractor) that are used to performance or meet TO requirements, the contractor shall provide the Government with the following detailed information:

· Facility Name

· Point of Contact

· Description of Services/Data Provide at the location

· Geographic Location and Address

Travel in and around the primary place of performance may be required throughout the period of performance. Additional travel within the United States territories and possessions and Locations outside of the United States territories and possessions may be required to support the requirements of this SOO.

7.1 Alternate Place of Performance (Contingency Only)

As determined by the Contracting Officer’s Representative (COR), contractor employees may be required to work at an alternate place of performance (e.g., home, the contractor's facility, or another approved activity within the local travel area) in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, Government closure due to inclement weather, etc.). Non-emergency/non-essential contractors should not report to a closed Government facility. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in this SOO. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer (CO) or the contractor may request an equitable adjustment pursuant to the Changes clause of the contract.

8. Period of Performance The period of performance for the BPA will be a 5-year base ordering period and two 2 year option periods and one 1 year option period (i.e. for a maximum total of ten years) and the 6-month extension of services IAW FAR 52.217-8. Period of Performance for each TO will be specified at the TO level. TOs that are awarded prior to the ordering period expiration can continue performance for a period not to exceed one year following the expiration of the ordering period. As directed by the COR, the contractor shall continue performance in emergency or mission essential conditions. Additionally, the contractor may be required to account for the whereabouts of their personnel should this information be requested by the COR.

9. Security Requirements This section shall be considered a supplement to Block 13 of the Government provided DD Form 254, Contract Classification Specification. The following security requirements shall apply to this effort. All contractor personnel shall possess, obtain, and maintain during the life of the BPAthe required security clearance over the life of the BPA IAW DD Form 254, Contract Security Classification Specification. Contractor personnel shall comply with all applicable security and safety regulations, guidance, and procedures, including local, referenced in the requirement and in effect at the work sites.

Per the FedRAMP supplemental guidance for PS-3, found in the FedRAMP Control Specific Contract Clauses v2, June 6, 2014 document 71, an agency must stipulate, “IAW OPM and OMB requirements”, the type of background investigation required for CSP personnel having access to or who can gain access to information. For DoD, the minimum designations are defined by level as follows:

Impact Levels 5: CSP personnel supporting Level 5 cloud service offerings will meet the personnel security requirements and undergo background checks as defined in OPM policy IAW the FedRAMP Moderate baseline, the FedRAMP+ CEs related to personnel security, and DoD personnel security policies. As such the minimum background investigation required for CSP personnel having access to Level 4 and 5 information based on a “critical-sensitive” (e.g., DoD’s ADP-1) position designation, is a Single Scope Background Investigation (SSBI) or a Background Investigation (BI) for a “high risk” position designation. The minimum background investigation required for CSP personnel having access to Level 4 and 5 information based on a “noncritical-sensitive” (e.g., DoD’s ADP-2) is a National Agency Check with Law and Credit (NACLC) (for “noncritical-sensitive” contractors), or a Moderate Risk Background Investigation (MBI) for a “moderate risk” position designation.

Impact Level 6: In accordance with PS-3(1), invoked by the CNSSI 1253 Classified Information Overlay, personnel having access to a secure room, the infrastructure supporting classified processing, or handling classified information, in addition to meeting the public trust position suitability/investigation requirements (e.g., a favorably adjudicated SSBI for a system administrator in a DoD ADP-1 position) must have a security clearance at the appropriate level. Systems and network administrators (i.e., privileged users), while typically not approved to handle classified information for need-to-know reasons, are considered to have access to classified information through their duties. Therefore these individuals require a clearance at the appropriate level for the classified information stored, processed, or transmitted.

References

a. DISA Form 786, DISA Statement of Information System Use and Acknowledgement of User Responsibilities

b. DISA Policy Letter, Unauthorized Connections to Network Devices, 11 September 2013

c. DISAI 240-110-8, Information Security

d. DISAI 240-110-36, Personnel Security

e. DISAI 240-110-38, Industrial Security

f. DISA Instruction 630-230-19, Cybersecurity

g. DoDM 5200.01, Vol 1-4 Information Security Program, 24 February 2012

h. DOD 5200.2-R, DoD Personnel Security Program

i. DOD 5220.22-M, National Industrial Security Program Operating Manual, February 2006 Incorporating Change 02 May 2016

j. DOD 5220.22-R, Industrial Security Regulation

k. DoDM 5105.21 Sensitive Compartmented Information (SCI) Administrative Security Manual:

Administration of Information and Information Systems Security

9.1 Facility Security Clearance

The work to be performed under this contract/order is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility for some personnel. Therefore, the company must have an interim or final Top Secret Facility Clearance from the Defense Security Service Facility Clearance Branch.

9.2 Security Clearance and Information Technology (IT) Level

All personnel performing on or supporting the DEOS contract in any way must be U.S. citizens. The personnel security requirements for this contract cover the individuals supporting the Task Areas delineated in the table below. Contractor personnel must possess the interim or final security clearance and interim or final IT-level eligibility delineated in the table below when performance starts. In addition, if the Government sponsors a position at a certain clearance level, the Contractor is expected to maintain that position at the same clearance level.