Amendment_0004_m2P1_Atch_J-6_Transition_Support_Tasks.pdf

Amendment 0004, dated August 22, 2016

Attachment J-6

Transition support tasks Tasks 1 and 2 are sample tasks of potential workloads for migration to allow the Contractor to propose a technical solution. Tasks 3 through 6 are existing milCloud workloads scheduled to be transitioned to milCloud 2.0 as part of the

Initial Operating Capability (IOC). The Contractor will provide a technical solution for each task (Tasks 1-6) with estimated level of effort including the proposed number of labor hours by labor category required to perform a successful transition for each task from the current state to the proposed cloud environment. Definitions of the Labor

Categories are included in Attachment J-5. Technical solution format may be determined by the Contractor, but Labor

Category Lists shall be in a Microsoft Excel spreadsheet. Actual task orders for transition of IOC workloads will be negotiated with the successful Contractor after contract award. No pricing data will be included in the response to section J-6.

Travel to the Consumer location will be performed using cost-reimbursable ODCs in accordance with standards identified in FAR Part 31 and the Joint Travel Regulations (JTR). Contractors will not be evaluated for travel costs. If the

Contractor feels that some or all of the labor should be performed at the Consumer’s current location, they will define the hours for the tasks which must be performed at the Consumer’s location, and the hours that should be performed at the Contractor’s location or the DISA Cloud Hosting location. .

The Contractor will also include in each solution all compute, storage and services necessary to meet the IaaS capacity required to support the systems in each task. The Contractor will also include capacity required by the Contractor’s solution to meet any COOP and elasticity requirements included in the task description. Original Consumer input for tasks 3-6 were collected on System Requirement Forms (SRF). The Government has extracted the information relevant to the Contractor from the Consumer provided requirements documents including the SRF, and provided assumed answers for data that was not included in the original documents. All Contractors will be able to respond to the same baseline data. The original SRF documents are included in this document (pages 14-61) for background.

The Transition Support solution for each task will provide a description of the work to be performed and the tools and methodology to be used, plus a Labor estimate to perform the following tasks:

A. Technical Analysis - Analyze the current environment to include network connectivity, server performance, virtualization requirements and application design.

B. Transition Program Plan - Develop plan to transition to cloud environment including resource capacity, funding assessment, architectural support, mitigation of workload or data portability issues, testing, risk planning, recommended server sizes, OS and application changes related to the target environment.

C. Virtualize - Transition all physical and virtual servers to images suitable for the target virtual format.

D. Extract, Transform and Load (ETL) of data stores, for migration to the infrastructure services, when applicable.

E. Migrate - Transport all images and data to the infrastructure services.

F. Import - Import or Export images and data into the Consumer’s purchased infrastructure services.

G. Turn-over - Ensure connectivity for Consumer management personnel to target servers.

H. Testing of DoD Consumer mission capabilities after migration.

I. Aid consumer in understanding the use of service APIs, CLIs, and infrastructure service management consoles.

J. Support in using operational features such as machine image snapshotting and image libraries.

K. Support in Consumer IA accreditation efforts for their transitioned workloads.

L. Additional tasks as defined by the offeror.

Each task description below will define the current environment including any CSP relevant data needed for the solution.

Task 1 Legacy application with physical servers

Task 1 CSP Relevant Requirements

Item Data Comment

Project Name Legacy Application with Physical servers

Description

This is an example of an existing DoD legacy project with staff with low level technical knowledge. They will require Transition support for all phases of the transition. The application has a Private (.mil only) facing web tier containing two small Red Hat 6.x servers. The application must be available 24/7/365, and is not designed for elasticity. There are two application servers running Windows Server 2008 R2, and two clustered database servers running Red Hat 6.x and using a shared database. All servers are currently rack mounted physical servers operating at the Consumer location.

The application operates at a single site, with no COOP or failover to an external site. Standard backup is required to provide 24 Hour RTO, and 24 Hour RPO for all storage. Privileged administrative users are at a combination of .mil DoD and .com contractor sites.

MAC Level III

Confidentiality Level Private

Network NIPR

Current Accreditation ATO

PPSM Registered Yes

Tools Required ACAS, HBSS

CND Alignment DISA

Special Data Reqt None

Required Backup Type Standard

COOP (Y/N) Yes

RTO 24 hour

RPO 24 hour

Local HA Required Yes, app is clustered

Remote HA Required No

Automated Patch Management

Yes

Non Standard Requirements

None

Task 1 Existing Servers

Server CPU Cores Mem

GB

OS and App

Storage Disk -

(Usable

GB)

Additional Tier 1 Data

Storage (Usable

GB)

Object Store

(Usable

GB)

Web 01 - Red Hat 1 2 75 0

Web 02 - Red Hat 1 2 75 0

App 01 - Windows 2 12 75 100

App 02 - Windows 2 12 75 100

DB 01 - Red Hat 8 32 75 1000

DB 02 - Red Hat 8 32 75 0

Object Storage 1000

Task 1 Support Labor

Year 1 Labor Category List Function Contractor

Location

DISA

Cloud

Hosting Site

Consumer Location

Trips Travel Days

Required

Travel

Windows SA

Linux SA

DBA

Network Engineer

Virtualization Specialist

Cloud Specialist

Project Manager

Cybersecurity Analyst

Task 2 Virtualized Legacy System

Task 2 CSP Relevant Requirements

Project Name Virtualized Legacy System

Description

Task 2 is an Air Force legacy system operating on Microsoft Hyper-V. It is in a small center on an Air Force base. The personnel are knowledgeable about virtualization and their application. They will require some support on all aspects of the transition. The application must be available 24/7. The developers want to add the ability to horizontally expand the Web and App tiers which is a capability of the application. This is to meet expected increased demand for the application during business hours, and to allow for surge processing in the event of a deployment. The Consumer wants to manage their own backup of the database. Failing servers will be restored from existing templates for OS and Application software. The Consumer plans to provide their own services including logging, VPN, CND and scanning from their existing datacenter via a lobe extension. The lobe extension will exist in the COLO (co-located network devices) at the site of the milCloud 2.0 instance. The COLO will be DISA designed and managed.

Privileged administrative users are at .mil DoD sites. The application is impact level 5, and requires internal failover, and RPO and RTO of no more than 8 hours.

MAC Level II

Confidentiality Level Private

Network NIPR

Current Accreditation ATO

PPSM Registered Yes

Tools Required None - Self provided

CND Alignment Air Force

Special Data Reqt No

Required Backup Type Self managed

COOP (Y/N) No - self provided

RTO

RPO

Local HA Required Yes

Remote HA Required No

Automated Patch Management

No

Non Standard

Lobe extension, DISA will design

Task 2 Virtualized Legacy System

GB

OS and App

Storag e Disk - (Usable

GB)

Additiona l Tier 1 Data

Storage (Usable

GB)

Tier 2 Storag e (Usable

GB)

Tier 3 Storag e (Usable

GB)

Object Store (Usabl e GB)

Web 01 - Windows 1 4 75 0

Web 02 - Windows 1 4 75

App 01 - Windows 2 10 75 100

App 02 - Windows 2 10 75 100

DB 01 - Windows 8 32 75 1000

DB 02 - Windows 8 32 75 0

Task 2 Support Labor

Location

DISA

Cloud

Hosting Site

Consumer Location

Trips Travel Days

Required

Travel

Windows SA

Linux SA

DBA

Network Engineer

Virtualization

Specialist

Cloud Specialist

Cybersecurity

Analyst

Task 3 IRIS Test System in RACE

Task 3 CSP Relevant Requirements

Project Name IRIS Legacy T&D

Description T&D application that migrated from DISA RACE to DISA milCloud 1.0. Development system for DITCO

Confidentiality Level Public

Network NIPR

Current Accreditation IATT DISA AO

PPSM Registered Yes

Tools Required HBSS, ACAS

CND Alignment DISA

Special Data Reqt No

Required Backup Type Standard

COOP (Y/N) No

RTO

RPO

Local HA Required No

Remote HA Required No

Automated Patch Management

No

Non Standard

No

Task 3 Servers

GB

OS and App

Storage Disk -

(Usable

GB)

Additiona l Tier 1 Data

Storage (Usable

GB)

Tier 2 Storag e (Usable

GB)

Tier 3 Storag e (Usable

GB)

Object Store (Usabl e GB)

N_RUJ03R_70_131 - Windows

1 2 100

N_RUJ03R_70_163 - Windows

1 2 100

Task 3 Support Labor

Year 1 Labor Category List

Function Contractor Location

DISA

Cloud

Hosting Site

Consumer Location

Trips Travel Days

Required

Travel

Windows SA

Linux SA

DBA

Network Engineer

Virtualization Specialist

Cloud Specialist

Cybersecurity Analyst

Task 4 PSD Development and Test Systems

Task 4 CSP Relevant Requirements

Project Name PSD Development and Test Systems

Description

PSD is two environments, Development and Test, that have recently transitioned from RACE to two separate VDCs in milCloud 1.0. The data below has been extracted from their transition requests. There are separate support teams for each environment, and they are billed separately. Transition may be billed on a single Task Order. The Mission Partner requested an estimate to detail the total cost of support services provided with the milCloud Plus service offering rate for the PSD Legacy Applications. Seven (7) milCloud Central

Processing Units (CPUs), 18 gigabytes (GB) of Random Access Memory (RAM) and 1220 GBs of usable storage. The PSD

Legacy Applications Development environment consists of three (3) development Virtual Operating Environments

(VOEs). To meet the requirements of this request, the Service Provider would provide the services outlined in Enclosure 1 with the milCloud Plus service rate to three (3) development VOEs milCloud Plus service offering rate for the PSD Legacy Test RACE/milCloud environment. 12 milCloud Central Processing

Units (CPUs), 26 gigabytes (GB) of Random Access Memory (RAM) and 2,600 GBs of usable storage. The PSD Legacy Test environment consists of five (5) test and development Virtual

Operating Environments (VOEs).

Logically separated Development and Test enclaves

MAC Level III

Confidentiality Level Public

Network NIPR

Current Accreditation IATO For Test only

PPSM Registered Yes Test only

Tools Required HBSS, ACAS

CND Alignment DISA

Special Data Reqt No

Required Backup Type Standard

COOP (Y/N) N

RTO

RPO

Local HA Required No

Remote HA Required No

Automated Patch Management

Yes

Non Standard

None

Task 4 Servers

GB

OS and App

Storag e Disk

(Usabl e GB)

Addition al Tier 1

Data Storage (Usable

GB)

Tier 2 Storag e (Usabl e GB)

Tier 3 Storag e (Usabl e GB)

Object Store (Usabl e GB)

Development

N_DIT01R_65_131 Windows 2008 2 8 120

N_DIT01R_65_165 Windows 2008 1 2 100

N_DIT01R_65_196 Windows 2008 4 8 1000

Test:

N_DIT02R_78_195 Windows 2008 2 4 300

N_DIT02R_78_227 Windows 2008 2 4 1200

N_DIT02R_78_162 Windows 2008 2 4 300

N_DIT02R_78_194 Windows 2008 2 6 300

N_DIT02R_78_226 Windows 2008 2 8 500

Task 4 Support Labor

Location

DISA

Cloud

Hosting Site

Consumer Location

Trips Travel Days

Required

Travel

Windows SA

Linux SA

Task 5 CMIS

Task 5 CSP Relevant Requirements

Project Name CMIS

Description

Task 5 is for the CMIS program Development and Test systems that were recently implemented in milCloud 1.0.

Development and Test systems are in a single VDC in milCloud, but are logically separated except as noted in the following SRF document.

Confidentiality Level Sensitive

Network NIPR

Current Accreditation ATO

PPSM Registered Yes

Tools Required HBSS, ACAS

CND Alignment DISA

Special Data Reqt PII, HIPAA

Required Backup Type Standard

COOP (Y/N) No

RTO

RPO

Local HA Required No

Remote HA Required No

Automated Patch Management

Yes

Non Standard

DISA provides IA/SA support - Will require OOB access

Task 5 Servers

GB

OS and App

Storag e Disk

(Usabl e GB)

Addition al Tier 1

Data Storage (Usable

GB)

Tier 2 Storag e (Usabl e GB)

Tier 3 Storag e (Usabl e GB)

Object Store (Usabl e GB)

Test Web Windows 2012 R2 4 12 60

Test DB Windows 2012 R2 8 16 60 40

Dev Web Windows 2012 R2 4 12 60

Dev DB Windows 2012 R2 8 16 60 40

Test DC Windows 2012 R2 4 32 60

Dev DC Windows 2012 R2 4 32 60

Task 5 Support Labor

Location

DISA

Cloud

Hosting Site

Consumer Location

Trips Travel Days

Required

Travel

Windows SA

Linux SA

Task 6 VAA Scanning Systems

Task 6 CSP Relevant Requirements

Project Name VAA Scanning System

Description

Task 6 is for the VAA Scanners that currently operate in milCloud. These are Nessus ACAS scanners that are used by the DISA IA personnel to scan all DISA DECCs for security risks. They are configured as noted in the following SRF document. Red Hat OE VM to host Nessus Scanners for the purpose of scanning DISA DoD CNDSP

Customers

Production ACAS Scanners

MAC Level III

Confidentiality Level Sensitive

Network NIPR

Current Accreditation ATO

PPSM Registered Yes

Tools Required HBSS

CND Alignment DISA

Special Data Reqt None

Required Backup Type Standard

COOP (Y/N) N

RTO

RPO

Local HA Required None

Remote HA Required None

Automated Patch Management

None

Non Standard

Task 6 Servers

GB

OS and App

Storag e Disk - (Usabl e GB)

Additiona l Tier 1 Data

Storage (Usable

GB)

Tier 2 Storag e (Usabl e GB)

Tier 3 Storag e (Usabl e GB)

Object Store (Usabl e GB)

VAA1 2 4 60

VAA2 2 4 60

VAA3 2 4 60

VAA4 2 4 60

VAA5 2 4 60

VAA6 2 4 60

VAA7 2 4 60

VAA8 2 4 60

VAA9 2 4 60

VAA10 2 4 60

VAA11 2 4 60

VAA12 2 4 60

VAA13 2 4 60

VAA14 2 4 60

NSSC 2 4 60

Task 6 Support Labor

Location

DISA

Cloud

Hosting Site

Consumer Location

Trips Travel Days

Required

Travel

Windows SA

Linux SA

SRF Forms below included for background information

ONLY (14-61 pages):

Task 3IRIS Test System in RACE IRIS is a DISA Test system that recently transitioned from DISA’s RACE environment to milCloud 1.0. The following is a

System Requirements Form (SRF) that was extracted from their transition request. IRIS has two servers.

Part 1 - Project Overview

Project Identification

1. System/Application

Name

2. Mission

Partner

3. Project Title 4. Service Provider

Tracking Number

5. Priority

IRIS Legacy RACE Dev

DISA IRIS 3914 Normal

6. Designated Hosting Site tbd 7. Managing Site Tbd

8. Project Description – Describe project details, dependencies, and constraints below. Attach any relevant design specifications or documentation to this section.

The Mission Partner requested an estimate to detail the total cost support services provided with the milCloud

Plus service offering rate for the legacy RACE PLD environment. The Mission Partner would order through the milCloud portal two (2) milCloud Central Processing Units (CPUs), 4 gigabytes (GB) of Random Access

Memory (RAM) and 200 GBs of usable storage. The IRIS environment consists of two (2) development Virtual

Operating Environments (VOEs)

9. System/Application Description

Test systems for DITCO

10. Operational Impact

Development System

11. CIC/ASC/BAN 12. MAC Level 13. Confidentiality Level 14. DoD Network

III

Public

Classified

Sensitive

NIPRNet

SIPRNet

Mission Partner DAA Accredited Enclave

(CDAE)

15. System DAA (Name, Title, Org, Email, Phone) DISA AO

16. Accreditation Status

17. If System/Application is NOT accredited, what is Mission Partner’s plan for achieving accreditation?

IATT

IATO

ATO

Not Accredited

18. Accrediting Agency 19. Accreditation Expiration 20. System DITPR Number

DISA

21. Accreditation

Repository

22. Residual Risk 23. VMS Registration eMASS Other Yes No Yes No Program Name:

24. PPSM ID Number 25. PPS Utilized 26. Application Development Environment

TBD Standard Non-Standard STIG’d Non-STIG’d

27. Critical Plans (select all that exist) 28. Reviews/Assessments (select all that exist)

Configuration Management Plan

Risk Management Plan

Vulnerability Management Plan

Patch Management Plan

Incident Response Plan

Continuity of Operations Plan

Disaster Recovery Plan

DoD 8500.2 IA Control Review

Location of Review:

Application Security and Development Review

Location of Review: AFNIC

Privacy Impact Assessment

Location of Assessment: AFMC/A6 XI

29. Tool Compatibility

HBSS Yes No Unknown

ESM Software Yes No Unknown

30. Open Source Software Yes No Unknown

CDSP - DoDD O-8530.01 and in support of CJCSI 6510.01F and CJCSI 6211.02D, require all DoD information systems and networks that process, store, transmit, display, or receive DoD information to be aligned in writing to an accredited Tier II CDSP.

The Mission Partner is required to obtain/maintain compliance with this requirement. DISA is able to provide this service or another provider can be used. In the case that another CDSP provider is chosen, a copy of the current SLA must be provided so that DISA analysts are able to provide TIPPER notifications the chosen CDSP.

31. Will the information system/application/network process, store, transmit, display, receive or disseminate DoD information

Yes No

32. Will the Mission Partner system connect to a DECC infrastructure?

Yes No

33. Does the Mission Partner intend to leverage the DISA

DECC Network Infrastructure?

Yes No

34. Does the Mission Partner intend to align to DISA for

CDSP services?

Yes No

35. If not aligned to DISA CDSP, provide name of other

CDSP. Please also provide SLA to <insert applicable

DISA office here> AND letterkenny.re.list.cdsp-requests@mail.mil

Mission Partner CDSP

CDSP POC

CDSP Email

Special Compliance Information (select all that apply)

36. PII 37. HIPAA 38. Financial System/ Application 39. Nuclear Information

Yes No Yes No Yes No Yes No

40. Data Access 41. CAC Enabled (Restricted/Private)

Unrestricted (unauthenticated)

Restricted (authenticated .com)

Private (access from .mil only)

Yes

No

42. Cyber Compliance

Yes No

Special Audits, Inspections, Assessments, and Tests (select all that apply)

43. SSAE 16 44. FISCAM 45. PCI 46. C&A

Yes No Yes No Yes No Yes No

47. Incident Response 48. Penetration Testing

Yes No Yes No

49. Points of Contact Name

Office and

Physical

Address Phone Email

Mission Partner Program POC Barbara Biebl

Mission Partner Technical POC

Mission Partner Financial POC

Mission Partner IA POC

Service Provider Team Lead

Service Provider Project Manager

Service Provider Technical Lead

Service Provider Customer Account

Rep (CAR)

Service Provider IA Technical

Advisor

Service Provider Network Lead

Service Provider Software Engineer

Target Dates

Initial Operation Environment (IOE) Date – date that Operating Environments (OEs) are turned over to the application administrators for application load

Initial Operating Capability (IOC) Date – date that OEs are configured for production users

50. Target Letter Estimate Date 51. Target Funding Date 52. Target IOE Date 53. Target IOC Date

Risk Assessment

Note: IA risk can only be determined by the IA Technical Advisor

54. Technical 55. Schedule 56. IA

High

Medium

Low

High

Medium

Low

High

Medium

Low

57. Enter Details of Any “High” or ‘Medium” Risks Noted:

N/A

Part 2 - Implementation and Cutover Support Requirements

1. Implementation Contacts

Role Name and Contact Information

Mission Partner Lead Technical POC

Mission Partner Lead Management POC

(Authority to approve changes)

Vendor or Integrator SME

Other Implementation POC (specify)

2. Migration Requirements

OE/File System Name Size of File(s) or

Image Being

Migrated

(usable storage in GB)

Type

(e.g., DB Export, Flat

File, OVA Image)

File Transmission Method

(Offline Copy, Online Copy

(SFTP), Array-to-Array

Replication, Application

Replication)

Migration Method

(Import, Overlay, Mirror, OVA)

N_RUJ03R_70_131 100

N_RUJ03R_70_163 100

3. Cutover Requirements

Describe the cutover window in terms of length and timing constraints:

Describe the Mission Partner, integrator, and vendor resources necessary to support cutover:

Describe any system-specific post-cutover acceptance criteria:

Describe any post-cutover parallel processing requirements:

4. Performance Metrics

Provide any performance metrics that must be attained for systems migrating to the Service

Provider:

5. Global Service Desk Level 1 Support Information

Approximate number of concurrent end-users:

Approximate Service Desk contact volume and frequency:

Part 3 - Technical Requirements

1. Mission Partner Disposition – Which of these statements best describes the Partner’s view of their technical requirements?

The Mission Partner is providing a detailed specification for computing infrastructure that they expect to deliver without modification.

The Mission Partner is providing detailed technical requirements based on an existing environment but acknowledges the design may not be optimal for Cloud hosting and is willing to engage the Cloud Service Provider to explore design alternatives.

The Mission Partner is providing general technical description and requires the Cloud Service Provider technical assistance to define technical requirements.

Other (fill in here):

Server Name

(hostname or unique identifier if not known)

Server

Function

(e.g., web, database, app)

Environment

(Production, Test, COOP)

Estimated

Availability

Requirement

(Metered

Billing)

OS OS

Version

32-bit or 64-bit

# of vCPUR eq

Req RAM

(GB)

N_RUJ03R_7

0_131

DEV 24/7/365

Windo ws 2008 64 1 2

N_RUJ03R_7

0_163

DEV 24/7/365

Windo ws 2008 64 1 2

2. OE Storage Requirements – Specify the storage that is required by each OE (usable storage in GB)

Server Name and

Function

Allocation for

Application

Allocation for

Database

Allocation for

Logs

Allocation for

Flat Files

Desired Storage

Tier Or performance

Level

Total (GB)

N_RUJ03R_70_131 100 Tier 1 100

N_RUJ03R_70_163 100 Tier 1 100

Object Storage – Not tied to specific server

Total Usable Storage Required (in GBs): 200

3. Web Interfaces – Identify URLs required and their attributes

Public – Any service intended to provide unclassified and non-sensitive information accessible from outside the NIPRNet, to include anonymous access.

Restricted – Any service intended to be accessible from the Internet and serves sensitive information to a limited set of users.

Access controls are in place to limit the user set who can access the service.

Private – Any service meant to be accessed only from the NIPRNet or SIPRNet, respectively (.mil only).

URL Name Application Public/Restricted/Private

(see definitions above)

Load-balanced to Multiple

Web Servers (Yes/No)

4. External System Communication Requirements – List the OEs that require communication with any external system.

Specify the ports and protocols used by each. This does not include external access for administration by privileged users.

Internal Server or

Enclave Name

Function External Server or System

Name and Domain

Party Initiating

Communication

Ports Protocols Notes

NA

5. Internal System Communication Requirements – List the OEs that require communication with other OEs within the enclave. Specify the ports and protocols used by each.

Internal Server Function Target Internal

Server

Party Initiating

Communication

Ports Protocols Workload

Characterization tbd

6. Software Requirements – List all application software, tools and accessories. Do not include Cloud Service Provider-provided Enterprise Systems Management (ESM) software.

Server Name Software

Vendor

Software

Name

Detail Version

Information

Software License

Provided/Procured by

Licensing or Acquisition

Notes

7. Open Source Software Requirements – List all open source software used. For open source, indicate whether or not the software has been DAA-approved. List additional information (i.e. licensing, vendor support, etc.) in the Notes column.

Software

Vendor

Software

Name

Version

Information

DAA-Approved Licensing, Acquisition, Support Notes

Yes No

Yes No

Yes No

8. User Authentication Requirements

Does user authentication / authorization require access to a remote resource (e.g., LDAP, AD)? Yes No

If Yes, who will manage the authentication / authorization database? .

9. Networking & Security

Describe any specific data protection requirements (e.g., data at rest) specified by the data owner.

N/A

Describe any interconnection requirements among DoD applications operating at different classification levels

(e.g., SIPRNet to NIPRNet or vice versa).

Describe any system-to-system interfaces with government agencies, commercial companies, foreign countries, etc.

N/A

Are any network VPNs required to secure system-to-system interfaces? Yes No

If Yes, network VPNs required, remote sites are: .com .mil .gov

Characterize anticipated aggregate bandwidth requirements (data center inbound/outbound).

Load Balancing: Describe any local or global application and/or server load balancing requirements.

10. Local High Availability Requirements – Does the system require any specific local high availability feature for any specific OEs or functions (e.g., clustering, Oracle RAC)?

If Yes, please elaborate on the requirement (if possible identify the OEs to be clustered and the type of clustering required, e.g., active, passive, RAC) below:

11. Remote or Second Site High Availability Requirements – Does the system require remote or second site high availability feature for any specific OEs or functions (e.g., remote failover, clustering, Oracle RAC)?

Yes No

If Yes, please elaborate on the requirement (if possible identify the OEs to be clustered and the type of clustering required, e.g., synchronous, asynchronous, RAC) below:

Part 4 - Standard and Optional Rate-Based Services

1. Core Services – Every workload hosted in milCloud 2.0 is based on the amount of Compute capacity.

Compute Compute is the basic Infrastructure as a Service capability provided by the CSP. This include virtual CPU, Memory and storage at the rates identified by the CSP. This also includes a Client OS license for a supported OS.

Describe any requested deviations from these core services:

2. Optional CSP Services –The below services may be acquired from the CSP These may have prerequisites in terms of connectivity and root control of the OS. Review and check any requested optional services:

Automated Patch Management – Automated Patch Management provides an automated patching service for supported client OS’s. This service may be limited to security and system patching and may include prerequisite levels of system access and scheduling.

3. Optional Value Add Services –The below services may be acquired from DISA. These may have prerequisites in terms of connectivity and root control of the OS. These may include any of the “Optional” service shown below. Review and check any requested optional services:

milCloud Plus – milCloud Plus includes System Administration (on-site support during normal business hours (8x5) with two-hour on-call response outside of normal hours), Security, Facilities Support, Standard OE (SOE) core software, Power, and Communications (local infrastructure/shared communications), and Level II Service Desk services. Level 1 and Level 3 services are not provided in Basic Services. Basic Services is assessed by OE.

Application Support – Tier 2 Service Desk support of a dedicated application. Examples include running special jobs on behalf of users, re-running aborted jobs, loading new releases of functional-user software, etc. If application support is selected, it will be applied to all OEs associated with a Mission Partner’s workload except for Service

Provider-provided or Web Administration OEs.

Database Administration – Includes the labor to provide Database Administration support and to ensure databases comply with security guidelines. It only applies to Database servers.

Oracle Grid Control – Provides the Service Provider standard web based database monitoring and management interface to Mission Partner DBAs. It is included if the Mission Partner is paying for Database Administration, but can be selected as an option by those Mission Partners who elect to perform their own DBA support. It is billed at 10 percent of the Database administration rate.

Database Software Maintenance – Maintenance of Oracle database software. Costs associated with this include the software maintenance and not the license itself. Note: DB Software Maintenance is a required service if the Service

Provider provides Oracle licenses.

24 x 7 System Administration – Provides seven days a week, 24 hours a day (24x7), full system administration support. Standard system administration support is part of Basic Services.

24 x 7 Application Support –Provides seven days a week, 24 hours a day (24x7), full application support. Select this option if the standard 8x5 with two hour after-hours response time is insufficient.

24 x 7 Database Administration – Provides seven days a week, 24 hours a day (24x7) full database administration support. Select this option if the standard 8x5 with two-hour after-hours response time is insufficient.

Include any comments or relevant information related to the selected optional services above:

4. Conditional Services – Conditional services may be required depending upon the optional services selected. Review and check any applicable conditional services that apply:

Web Administration – Web Administration is another type of application support and it utilizes the Application

Support rate. This service supports the labor to administer a web server and its associated software. If a web server uses Microsoft's Internet Information Services (IIS), the Service Provider will install the feature and support static content at no additional charge, as this is included in the standard Basic Services rate.

Database Security –Includes the labor associated with ensuring database servers comply with security guidelines (e.g., consultative services on the STIG, handling STIG findings, database scans, and VMS entry and validation) and applies to those database servers for which the Mission Partner retains the DBA function themselves. It is billed at 10 percent of the optional Database Administration rate. Database security is included for those database servers that the Mission Partner selects Database Administration.

Capacity Planning Reporting – Mission Partners who maintain their own hardware and do not pay the Hardware

Services rate may elect to receive capacity planning reports billed at 10 percent of the Hardware Services rate.

Include any comments or relevant information related to the selected conditional services

5. Service Continuity – If remote site COOP support is required, please select one of the options below. Descriptions are based on DISA service levels for reference. These services may be application dependent depending on the level of automation required:

Shared COOP – Referred to as “Remote Recovery Combination 1” in the DISA Service Catalog

(RTO = 5 days, RPO = 7 days) – MAC III applications only

Shared COOP w/Replication Option – Referred to as “Remote Recovery Combination 1.2” in the DISA Service Catalog

(RTO = 5 days, RPO = 8 hours) – MAC III applications only

Dedicated COOP – Referred to as “Remote Recovery Combination 2” in the DISA Service Catalog

(RTO = 24 hours, RPO = 8 hours)

Dedicated COOP – Referred to as “Remote Recovery Combination 3” in the DISA Service Catalog

(RTO and RPO = 8 hours)

High-Availability COOP – Referred to as “Remote Recovery Combination 4” in the DISA Service Catalog

(RTO = 30 minutes, RPO = 1 Sec)

Custom – (Failover, T&D, Mission Partner-managed COOP, etc.)

No Service Provider-provided COOP

Note any special considerations related to your Service Continuity requirement here and provide more detailed specifications in the Non-Standard Requirements section, if applicable:

Is the detailing of production and COOP locations in the same documentation authorized? Yes No

Part 5 - Non-Standard Requirements

Fulfillment of non-standard requirements are generally not included in the Service Provider’s published server and storage rates and entail additional design and integration efforts, special considerations/approvals (waivers), and/or long procurement lead times.

1. Non-Standard Configurations or Mission Partner-Provided Items – Specify non-standard or Mission-Partner-provided hardware that must be deployed at a DECC in support of this system.

Item Name or

Description

Item Type

(Server, storage, network, software, other)

Purpose Justification

(explain why standard components will not work)

Source Acquired by

Maintenance

Arrangement if

Mission-Partner

Provided (contract number, vendor, expiration date)

Will the

Service

Provider

Pick Up

Maintenance

Upon Current

Contract

Expiration?

Yes

No

Yes

No

Yes

No

Yes

No

Yes

No

Yes milCloud 2.0 SRF Template Version FY16.0 – Jun 2016

2. Non-Standard Support Requirements – Explain any non-standard operations or support requirements. (e.g., any SME labor or non-standard support functions.

3. Non-Standard Communications or Network Requirements – Explain any non-standard network or communications requirements. (e.g., any deviation from the Service Provider enclave designs, exceptional bandwidth, latency or access requirements, etc. Include diagrams if available.)

4. Non-Standard Other – Explain any non-standard unusual, unique or exceptional requirements that do not fit into the previous categories.

5. Additional Documentation – Attach and identify in the space below any documents that support the specification of non-standard requirement(s) noted in this section:

Task 4 PSD Development and Test Systems PSD is two environments, Development and Test, that have recently transitioned from RACE to two separate VDCs in milCloud 1.0. The data below has been extracted from their transition requests. There are separate support teams for each environment, and they are billed separately. Transition may be billed on a single Task Order.

Part 1 - Project Overview

Project Identification

58. System/Application

Name

59. Mission

Partner

60. Project Title 61. Service Provider

62. Priority

PSD Legacy RACE Dev and Test

DITCO PSD 3912 and 3913 Normal

63. Designated Hosting Site tbd 64. Managing Site Tbd

65. Project Description – Describe project details, dependencies, and constraints below. Attach any relevant design specifications or documentation to this section.

The Mission Partner requested an estimate to detail the total cost of support services provided with the milCloud

Plus service offering rate for the PSD Legacy Applications. The Mission Partner would order through the milCloud portal seven (7) milCloud Central Processing Units (CPUs), 18 gigabytes (GB) of Random Access

Memory (RAM) and 1220 GBs of usable storage. The PSD Legacy Applications Development environment consists of three (3) development Virtual Operating Environments (VOEs). To meet the requirements of this request, the Service Provider would provide the services outlined in Enclosure 1 with the milCloud Plus service rate to three (3) development VOEs

The Mission Partner requested an estimate to detail the total cost support services provided with the milCloud

Plus service offering rate for the PSD Legacy Test RACE/milCloud environment. The Mission Partner would order through the milCloud portal 12 milCloud Central Processing Units (CPUs), 26 gigabytes (GB) of Random

Access Memory (RAM) and 2,600 GBs of usable storage. The PSD Legacy Test environment consists of five (5) test and development Virtual Operating Environments (VOEs). To meet the requirements of this request, the

Service Provider would provide the services outlined in Enclosure 1 with the milCloud Plus service rate to five

(5) test and development VOEs

66. System/Application Description

Development and Test enclaves

67. Operational Impact

Development and Test Systems

68. CIC/ASC/BAN 69. MAC Level 70. Confidentiality Level 71. DoD Network

III

Public

Classified

Sensitive

NIPRNet

SIPRNet

Mission Partner DAA Accredited Enclave

(CDAE)

72. System DAA (Name, Title, Org, Email, Phone) DISA AO

73. Accreditation Status

74. If System/Application is NOT accredited, what is Mission Partner’s plan for achieving accreditation?

IATT

IATO

ATO

Not Accredited

Development system – VPN access only

75. Accrediting Agency 76. Accreditation Expiration 77. System DITPR Number

78. Accreditation

Repository

79. Residual Risk 80. VMS Registration eMASS Other Yes No Yes No Program Name:

81. PPSM ID Number 82. PPS Utilized 83. Application Development Environment

TBD Standard Non-Standard STIG’d Non-STIG’d

84. Critical Plans (select all that exist) 85. Reviews/Assessments (select all that exist)

Configuration Management Plan

Risk Management Plan

Vulnerability Management Plan

Patch Management Plan

Incident Response Plan

DoD 8500.2 IA Control Review

Location of Review:

Application Security and Development Review

Location of Review: AFNIC

Privacy Impact Assessment

Continuity of Operations Plan

Disaster Recovery Plan

Location of Assessment: AFMC/A6 XI

86. Tool Compatibility

HBSS Yes No Unknown

ESM Software Yes No Unknown

87. Open Source Software Yes No Unknown

CDSP - DoDD O-8530.01 and in support of CJCSI 6510.01F and CJCSI 6211.02D, require all DoD information systems and networks that process, store, transmit, display, or receive DoD information to be aligned in writing to an accredited Tier II CDSP.

The Mission Partner is required to obtain/maintain compliance with this requirement. DISA is able to provide this service or another provider can be used. In the case that another CDSP provider is chosen, a copy of the current SLA must be provided so that DISA analysts are able to provide TIPPER notifications the chosen CDSP.

88. Will the information system/application/network process, store, transmit, display, receive or disseminate DoD information

Yes No

89. Will the Mission Partner system connect to a DECC infrastructure?

Yes No

90. Does the Mission Partner intend to leverage the DISA

DECC Network Infrastructure?

Yes No

91. Does the Mission Partner intend to align to DISA for

CDSP services?

Yes No

92. If not aligned to DISA CDSP, provide name of other

CDSP. Please also provide SLA to <insert applicable

DISA office here> AND letterkenny.re.list.cdsp-requests@mail.mil

Mission Partner CDSP

93. PII 94. HIPAA 95. Financial System/ Application 96. Nuclear Information

Yes No Yes No Yes No Yes No

97. Data Access 98. CAC Enabled (Restricted/Private)

Unrestricted (unauthenticated)

Restricted (authenticated .com)

Private (access from .mil only)

Yes

No

99. Cyber Compliance

100. SSAE 16 101. FISCAM 102. PCI 103. C&A

Yes No Yes No Yes No Yes No

104. Incident Response 105. Penetration Testing

106. Points of Contact Name

Physical

Address Phone Email

Mission Partner Program POC Cora Benriquez

Mission Partner Technical POC

Mission Partner Financial POC

Mission Partner IA POC

Service Provider Team Lead

Service Provider Project Manager

Service Provider Technical Lead

Service Provider Customer Account

Rep (CAR)

Initial Operation Environment (IOE) Date – date that Operating Environments (OEs) are turned over to the application administrators for application load

Initial Operating Capability (IOC) Date – date that OEs are configured for production users

107. Target Letter Estimate

Date

108. Target Funding

Date

109. Target IOE

Date 110. Target IOC Date

111. Technical 112. Schedule 113. IA

High

Medium

Low

High

Medium

Low

High

Medium

Low

114. Enter Details of Any “High” or ‘Medium” Risks Noted:

N/A

Part 2 - Implementation and Cutover Support Requirements

6. Implementation Contacts

Role Name and Contact Information

Mission Partner Lead Technical POC

Mission Partner Lead Management POC

(Authority to approve changes)

7. Migration Requirements

Image Being

Migrated

(usable storage in GB)

Type

(e.g., DB Export, Flat

File, OVA Image)

File Transmission Method

(Offline Copy, Online Copy

(SFTP), Array-to-Array

Replication, Application

Replication)

Migration Method

(Import, Overlay, Mirror, OVA)

N_DIT01R_65_131 120

N_DIT01R_65_165 100

N_DIT01R_65_196

1,000

N_DIT02R_78_195 300

N_DIT02R_78_227 1200

N_DIT02R_78_162 300

N_DIT02R_78_194 300

N_DIT02R_78_226 500

8. Cutover Requirements

9. Performance Metrics

10. Global Service Desk Level 1 Support Information

12. Mission Partner Disposition – Which of these statements best describes the Partner’s view of their technical requirements?

The Mission Partner is providing a detailed specification for computing infrastructure that they expect to deliver

The Mission Partner is providing detailed technical requirements based on an existing environment but acknowledges the design may not be optimal for Cloud hosting and is willing to engage the Cloud Service Provider

The Mission Partner is providing general technical description and requires the Cloud Service Provider technical unique identifier if not known)

Server

Function

(e.g., web, database, app)

Environment

(Production, Test, COOP)

Estimated

Availability

Requirement

(Metered

Billing)

OS OS

Version

32-bit or 64-bit

# of vCPUR eq

Req RAM

(GB)

N_DIT01R_6

5_131 Dev 24/7/365

Windo ws 2008 64 2 8

N_DIT01R_6

5_165 Dev 24/7/365

Windo ws 2008 64 1 2

N_dit01r_65

_196 Dev 24/7/365

Windo

2008 64 4 8

N_DIT02R_78

_195 Test 24/7/365

Windo ws 2008 64 2 4

N_DIT02R_78

_227 Test 24/7/365

Windo ws 2008 64 2 4

N_DIT02R_78

_162 Test 24/7/365

Windo

2008 64 2 4

N_DIT02R_78

_194 Test 24/7/365

Windo ws 2008 64 2 6

N_DIT02R_78

_226 Test 24/7/365

Windo

2008 64 4 8

13. OE Storage Requirements – Specify the storage that is required by each OE (usable storage in GB)

Function

Allocation for

Application

Allocation for

Database

Allocation for

Logs

Allocation for

Flat Files

Desired Storage

Tier Or performance

Level

Total (GB)

N_DIT01R_65_131 120 Tier 1 120

N_DIT01R_65_165 100 Tier 1 100

N_dit01r_65_196 1000 Tier 1 1,000

N_DIT02R_78_195 300 Tier 1 300

N_DIT02R_78_227 1200 Tier 1 1200

N_DIT02R_78_162 300 Tier 1 300

N_DIT02R_78_194 300 Tier 1 300

N_DIT02R_78_226 500 Tier 1 500

Total Usable Storage Required (in GBs):

14. Web Interfaces – Identify URLs required and their attributes

Public – Any service intended to provide unclassified and non-sensitive information accessible from outside the NIPRNet, to include anonymous access.

Restricted – Any service intended to be accessible from the Internet and serves sensitive information to a limited set of users.

Access controls are in place to limit the user set who can access the service.

Private – Any service meant to be accessed only from the NIPRNet or SIPRNet, respectively (.mil only).

URL Name Application Public/Restricted/Private

(see definitions above)

Load-balanced to Multiple

15. External System Communication Requirements – List the OEs that require communication with any external system.

Specify the ports and protocols used by each. This does not include external access for administration by privileged users.

Internal Server or

Enclave Name

Function External Server or System

Name and Domain

Party Initiating

Communication

16. Internal System Communication Requirements – List the OEs that require communication with other OEs within the

Internal Server Function Target Internal

Server

Party Initiating

Communication

Ports Protocols Workload

17. Software Requirements – List all application software, tools and accessories. Do not include Cloud Service Provider-

Server Name Software

Vendor

Software

Name

Detail Version

Information

Software License

Provided/Procured by

Licensing or Acquisition

Notes

18. Open Source Software Requirements – List all open source software used. For open source, indicate whether or not the software has been DAA-approved. List additional information (i.e. licensing, vendor support, etc.) in the Notes column.

Software

Vendor

Software

Name

Version

Information

DAA-Approved Licensing, Acquisition, Support Notes

Yes No

Yes No

Yes No

19. User Authentication Requirements

Does user authentication / authorization require access to a remote resource (e.g., LDAP, AD)? Yes No

If Yes, who will manage the authentication / authorization database? .

20. Networking & Security

N/A

Describe any interconnection requirements among DoD applications operating at different classification levels

(e.g., SIPRNet to NIPRNet or vice versa).

Describe any system-to-system interfaces with government agencies, commercial companies, foreign countries, etc.

N/A

Are any network VPNs required to secure system-to-system interfaces? Yes No

If Yes, network VPNs required, remote sites are: .com .mil .gov

Characterize anticipated aggregate bandwidth requirements (data center inbound/outbound).

Load Balancing: Describe any local or global application and/or server load balancing requirements.

21. Local High Availability Requirements – Does the system require any specific local high availability feature for any specific

Yes No

If Yes, please elaborate on the requirement (if possible identify the OEs to be clustered and the type of clustering required,

22. Remote or Second Site High Availability Requirements – Does the system require remote or second site high availability

Yes No

If Yes, please elaborate on the requirement (if possible identify the OEs to be clustered and the type of clustering required,

6. Core Services – Every workload hosted in milCloud 2.0 is based on the amount of Compute capacity.

Compute Compute is the basic Infrastructure as a Service capability provided by the CSP. This include virtual CPU, Memory and storage at the rates identified by the CSP. This also includes a Client OS license for a supported OS.

7. Optional CSP Services –The below services may be acquired from the CSP These may have prerequisites in terms of

Automated Patch Management – Automated Patch Management provides an automated patching service for supported client OS’s. This service may be limited to security and system patching and may include prerequisite

8. Optional Value Add Services –The below services may be acquired from DISA. These may have prerequisites in terms of connectivity and root control of the OS. These may include any of the “Optional” service shown below. Review and check any requested optional services:

milCloud Plus – milCloud Plus includes System Administration (on-site support during normal business hours (8x5) with two-hour on-call response outside of normal hours), Security, Facilities Support, Standard OE (SOE) core software, Power, and Communications (local infrastructure/shared communications), and Level II Service Desk services. Level 1 and Level 3 services are not provided in Basic Services. Basic Services is assessed by OE.

Application Support – Tier 2 Service Desk support of a dedicated application. Examples include running special jobs on behalf of users, re-running aborted jobs, loading new releases of functional-user software, etc. If application support is selected, it will be applied to all OEs associated with a Mission Partner’s workload except for Service

Provider-provided or Web Administration OEs.

Database Administration – Includes the labor to provide Database Administration support and to ensure databases comply with security guidelines. It only applies to Database servers.

Oracle Grid Control – Provides the Service Provider standard web based database monitoring and management interface to Mission Partner DBAs. It is included if the Mission Partner is paying for Database Administration, but can be selected as an option by those Mission Partners who elect to perform their own DBA support. It is billed at 10 percent of the Database administration rate.

Database Software Maintenance – Maintenance of Oracle database software. Costs associated with this include the software maintenance and not the license itself. Note: DB Software Maintenance is a required service if the Service

Provider provides Oracle licenses.

24 x 7 System Administration – Provides seven days a week, 24 hours a day (24x7), full system administration support. Standard system administration support is part of Basic Services.

24 x 7 Application Support –Provides seven days a week, 24 hours a day (24x7), full application support. Select this option if the standard 8x5 with two hour after-hours response time is insufficient.

24 x 7 Database Administration – Provides seven days a week, 24 hours a day (24x7) full database administration support. Select this option if the standard 8x5 with two-hour after-hours response time is insufficient.

9. Conditional Services – Conditional services may be required depending upon the optional services selected. Review and

Web Administration – Web Administration is another type of application support and it utilizes the Application

Support rate. This service supports the labor to administer a web server and its associated software. If a web server uses Microsoft's Internet Information Services (IIS), the Service Provider will install the feature and support static content at no additional charge, as this is included in the standard Basic Services rate.

Database Security –Includes the labor associated with ensuring database servers comply with security guidelines (e.g., consultative services on the STIG, handling STIG findings, database scans, and VMS entry and validation) and applies to those database servers for which the Mission Partner retains the DBA function themselves. It is billed at 10 percent of the optional Database Administration rate. Database security is included for those database servers that the Mission Partner selects Database Administration.

Capacity Planning Reporting – Mission Partners who maintain their own hardware and do not pay the Hardware

Services rate may elect to receive capacity planning reports billed at 10 percent of the Hardware Services rate.

10. Service Continuity – If remote site COOP support is required, please select one of the options below. Descriptions are based on DISA service levels for reference. These services may be application dependent depending on the level of automation required:

Shared COOP – Referred to as “Remote Recovery Combination 1” in the DISA Service Catalog

(RTO = 5 days, RPO = 7 days) – MAC III applications only

Shared COOP w/Replication Option – Referred to as “Remote Recovery Combination 1.2” in the DISA Service Catalog

(RTO = 5 days, RPO = 8 hours) – MAC III applications only

Dedicated COOP – Referred to as “Remote Recovery Combination 2” in the DISA Service Catalog

(RTO = 24 hours, RPO = 8 hours)

Dedicated COOP – Referred to as “Remote Recovery Combination 3” in the DISA Service Catalog

(RTO and RPO = 8 hours)

High-Availability COOP – Referred to as “Remote Recovery Combination 4” in the DISA Service Catalog

(RTO = 30 minutes, RPO = 1 Sec)

Custom – (Failover, T&D, Mission Partner-managed COOP, etc.)

No Service Provider-provided COOP

Note any special considerations related to your Service Continuity requirement here and provide more detailed specifications in

Fulfillment of non-standard requirements are generally not…