|
[Insert Your Department Name
|
| bet | 4/4 | | Sana | 22.07.2021 | | Hajmi | 42,49 Kb. | | #15524 |
Provide a detailed description of the proposed environment using the same criteria as in the Current Environment and include an architectural diagram for reference
IaaS / PaaS Requirements Infrastructure as a Service (IaaS) Technical Requirements
Use the tables below to provide the technical requirements and specifications of the proposed IaaS environment. Insert rows if additional space is needed.
Servers
|
Production
|
Development
|
Test
|
Application
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
Database
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
Web Hosting
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
Communications (ie, SFT)
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
Server XX – CPU’s, RAM, Storage
|
|
|
|
|
Storage Systems
|
Production
|
Development
|
Test
|
SAN (GB or TB)
|
|
|
|
NAS (GB or TB)
|
|
|
|
Back-up (GB or TB)
|
|
|
|
Archive (GB or TB)
|
|
|
|
|
|
|
|
Network
|
|
|
|
Transport (ie, Dedicated, Internet, TIC, or None)
|
|
|
|
Bandwidth (MB or GB)
|
|
|
|
Redundancy
|
|
|
|
Firewall
|
|
|
|
Internet Gateway
|
|
|
|
Layer 3 Switching
|
|
|
|
Secure File Transfer
|
|
|
|
Security
|
|
|
|
Platform as a Service (PaaS) Technical Requirements
In addition to the IaaS technical requirements, please use the tables below to provide the technical requirements and specifications for the proposed PaaS environment. Insert rows if additional space is needed.
Virtual Network
|
Specification
|
|
VPN
|
|
|
VLAN
|
|
|
Virtual Desktop
|
|
|
|
|
|
Operating System
|
Linux
|
Windows
|
Server 1
|
|
|
Server 2
|
|
|
|
|
|
Middleware
|
|
|
|
|
|
|
|
| Other Requirements
In addition to the IaaS and PaaS technical requirements, include requirements for the following functions and professional services.
Software License
Clarify in this section who will be responsible for licensing, including but not limited to operating systems, servers, databases and applications.
Backup Systems and Capability
Backup capability refers to the ability to recover and restore the system and data from a failure or loss situation. This would include:
Backup Contents
Applications – (i.e., 45 GB full, 1GB daily incremental)
Data – (i.e., 100 TB full, 50 GB daily incremental) (if running multiple applications, may want to list Data by application)
Other – (i.e., web pages, 100 GB full, 1GB daily incremental)
Backup Retention Period and Archiving
Recovery Time Objective (RTO)
The required length of time for backup restoration (for example):
24 hours for production environment
72 hours for development and test environments
Recovery Point Objective (RPO)
The maximum length of time between backups
Snapshot Capability
Identify whether or not snapshot capability is required. This refers to the customer having the ability to make an on-demand copy of the system / data, such as before doing a system upgrade or data migration.
Scalable Resources
Provide the ability to increase/decrease resources, as needed, to support any periods of unpredictable high/low usage. Scalable resources include but are not limited to:
Servers
Storage
Database instances
Other
System Usage
For the target throughput of the system, include users and anticipated users from all groups in the numbers. If the system has multiple applications, create a table for each application.
Description
|
Current
|
Growth
|
Growth Timeframe
|
Number of Users: Peak Time
|
|
|
|
Number of Users: Average Time
|
|
|
|
Amount of Bandwidth: Peak Time
|
|
|
|
Amount of Bandwidth: Average Time
|
|
|
|
Number of Transactions: Peak Time
|
|
|
|
Number of Transactions: Average Time
|
|
|
| System Availability
The Contractor will design an environment configured to support the system availability of xx.xx% or greater per month.
Service Level Agreements (SLAs)
This subsection specifies SLAs the Contractor is required to meet. The Contractor shall provide a financially-backed penalty schedule for not meeting each of the SLA targets.
Help Desk Support
State requirements for Help Desk support
The help desk shall be available and provide the following levels of support:
Security Security Classification
State the FISMA rating according to its FIPS199 classification.
Vulnerability Scanning and Patching
The Contractor must comply with Continuous Monitoring requirements and conduct standards per FedRAMPI policy. The Contractor shall submit monthly continuous monitoring reports to the applicable Government System Owner and Authorizing Official, to include a monthly Plan of Action and Milestones (POA&M) report documenting risk mitigation strategies.
Trusted Internet Connection (TIC) Compliance
This section applies when there will be a transfer of restricted data between government systems and external systems, information is going to be transmitted between the hosted environment and another environment (including transferring data for the initial loading), or if information is to be transmitted from a web app onto the cloud over the internet.
Compliance with federally mandated IPv6 requirements for public-facing services. See http://www.whitehouse.gov/sites/default/files/omb/assets/egov_docs/transition-to-ipv6.pdf for more information.
Professional Services
This section is applicable on a case-by-case basis depending on the customer’s need for any of the services. These could include one-time services, such as implementation assistance, or monthly recurring services that are needed to support the project.
Description
|
One-Time Hours
|
Monthly Hours
|
Architecture and Design
|
|
|
Migration and Implementation
|
|
|
Application Development
|
|
|
Testing
|
|
|
Training
|
|
|
Database Administration
|
|
|
System Administration
|
|
|
Security Assessment & Authorization
|
|
|
Monitoring and Compliance
|
|
|
Directory Services
|
|
|
Authentication Services
|
|
| Period of Performance
Please indicate the length of the task order i.e. start date and end date.
State if the task order is to be awarded with a base period and options. If the task order is to be awarded and funded incrementally, state the base obligation period and incremental funding periods.
Points of Contact
Contracting Officer (CO)
Name:
Address:
Email:
Phone Number:
Contracting Officer’s Representative (COR)
Name:
Address:
Email:
Phone Number:
[Optional]
[Include list of reference documents]
OCIO IaaS-PaaS SOW Template
|
| |
