(Insert Your Department Name) (Insert Your Agency Name)
(Insert Your Department Name) (Insert Your Agency Name)
(Insert Your Department Name) (Insert Your Agency Name)
XX 2012
SAMPLE
Version 0.2
This sample Email as a Service (EaaS) Blanket Purchase Agreement (BPA) Statement of Work
(SOW) template is informational only and the use of this template is not required.
This template can simply be used as a reference document for purposes of outlining your own
SOW and for ensuring that the information listed in this template is provided in your own SOW.
Note: Guidance in this template is presented in italics within square brackets [guidance], while
example content is presented in normal font.
All sections should be reviewed for relevance to the cloud-based objectives of the ordering
activity and modified accordingly.
This sample is not all inclusive, therefore the reader is cautioned to use professional judgment
and include agency specific references to their own SOW.
If you have questions regarding the EaaS BPA please reach out to the EaaS Service Line
Manager listed below.
Tom Kireilis
10304 Eaton Place
Fairfax, Virginia 22030
Phone: (703) 589-2925
Email: Thomas.kireilis@gsa.gov
http://www.gsa.gov/eaas
Document Overview.................................................................................................................... 2
1. Task Order Title....................................................................................................................5
2. Introduction........................................................................................................................... 5
3. Background.......................................................................................................................... 5
4. Current Environment............................................................................................................ 6
5. Objectives............................................................................................................................. 7
5.1. Business Objectives......................................................................................................7
5.2. Technical Objectives.....................................................................................................8
5.3. Service Objectives.........................................................................................................8
5.4. Security Objectives........................................................................................................8
5.5. Management & Administrative Objectives.....................................................................8
5.6. Migration Objectives......................................................................................................8
5.7. Integration Objectives....................................................................................................8
5.8. Solution-specific Objectives...........................................................................................8
6. Scope................................................................................................................................... 8
7. Specific Requirements..........................................................................................................9
7.1. Task Description............................................................................................................ 9
7.2. Key Deliverables, Milestones and Schedule................................................................12
7.3. Government Furnished Equipment/Information (GFE/GFI)..........................................12
7.4. Other Pertinent Information/Special Considerations....................................................13
8. Constraints......................................................................................................................... 13
8.1. Access Control............................................................................................................ 13
8.2. Authentication.............................................................................................................. 13
8.3. Personnel Security Clearances...................................................................................14
8.4. Non-Disclosure Agreements (NDAs)...........................................................................14
8.5. Accessibility................................................................................................................. 14
8.6. Data............................................................................................................................. 14
8.7. Confidentiality, Security, and Privacy...........................................................................14
8.8. Privacy Act.................................................................................................................. 14
Table of Tables
2. Introduction
[Provide a short description of the requirements without including the specific requirements.]
The new email and collaboration system will meet industry performance standards, offer the
necessary redundancy and contingency features to meet [Department/Agency] needs, and
provide state-of-the-art technology enhancements to improve user experience and minimize
service disruption.
This Statement of Work (SOW) issued by [Department/Agency] describes the goals expected to
be achieved with regard to executing the transition of enterprise email applications to the cloud
and operation of the new email service via a cloud Email as a Service (EaaS) solution.
3. Background
[Consider the following: Include high–level Agency/Department specific background, how the
requirement evolved; relationship to other projects; why work is needed, the outcomes of any
market research conducted by your organization to determine the viability and cost of different
options for an email solution. Summarize information which is essential for understanding the
work and ensure technical information is understandable to potential readers of different
disciplines.]
Produced by the Office of Management & Budget (OMB), the February 2011 Federal Cloud
Strategy outlines the impetus and benefits of migrating to cloud services, including acceleration
of data center consolidation and better utilization of existing infrastructure assets. Based on the
December 2010 25 Point Plan to reform Federal Information Technology Management, also
from OMB, each Federal agency CIO has been directed to leverage this strategy to begin
planning the migration of their IT services to cloud solutions. [Department/Agency] recognizes
the importance of harnessing these fundamental shifts in IT investment patterns to increase IT
efficiencies and cut IT costs.
4. Current Environment
[Provide a brief, high-level description of your organization’s current environment. Examples of
current environment factors are listed below]:
[Related programs that could impact cloud migration (e.g. refresh schedules, large
acquisitions)]
The existing email and collaboration infrastructures at [Department/Agency] are not adequate
for the future.
[Identify any high level descriptors of the issues that current email and collaboration solutions
are causing].
The main drivers of this effort for [Department/Agency] to utilize a cloud solution for enterprise
email applications are:
[Department/Agency] current uses [current email system/solution], across [X] users and [X]
locations.
outlines the user base across [locations, components, or other criteria] and identifies other
existing parameters for the current email environment.
[Identify any user base growth patterns/projections, such as total expected mailboxes over a
given growth period].
Environment [Agency/Department]
User Base
[Component 1] # of Users for Component
[Component 2] # of Users for Component
[Component 3] # of Users for Component
Total Number of Users # of Users (Total)
Mailbox Type
5. Objectives
[Provide a concise overview of your Agency/Department goals and expectations as a result of
this task order. It does not need to include a description of deliverables or requirements since
these will be included in the “Specific Requirements” section below. Include the desired end
result and your expectations or goals of the contractor.]
The objective of this SOW is to acquire the EaaS solution [specify the desired EaaS lots
(service offerings) and sub-lots (deployment models)] via the GSA EaaS BPA.
In line with the requirements in the EaaS BPA, [Department/Agency] has outlined objectives that
the proposed EaaS solution will achieve, including business, technical, security,
management/administrative, migration, and integration objectives.
5.1.Business Objectives
[Department/Agency] is seeking an integrated suite of cloud-based email and collaboration
services that improves business performance, increases employee productivity, achieves
5.2.Technical Objectives
The EaaS solution shall achieve the technical objectives to achieve a high degree of
confidentiality, integrity, reliability and availability in accordance with the GSA EaaS BPA.
5.3.Service Objectives
The EaaS solution shall offer the necessary redundancy, resiliency, and contingency
capabilities to ensure service availability that meets [Department/Agency’s] current and
future needs in accordance with the GSA EaaS BPA.
5.4.Security Objectives
The EaaS solution shall meet the requisite FedRAMP security controls and requirements in
accordance with the GSA EaaS BPA.
5.6.Migration Objectives
The EaaS solution shall enable the [Department/Agency] to conduct a seamless and
expedited transition from the current email and collaboration environment to the cloud email
and collaboration services with minimal disruption to business operations while insuring data
integrity.
5.7.Integration Objectives
The EaaS solution shall provide necessary integration services to extend the EaaS solution
to related applications, in accordance with the EaaS BPA.
5.8.Solution-specific Objectives
The following objectives apply to the solution identified by [Department/Agency] as ideally
fitting the requirements of the organization:
[Include any objectives that are solely applicable to the solution desired to be implemented
(e.g. which commercial software product desired to be used) that are not addressed
elsewhere in this document]
6. Scope
[Describe general scope of work. Include a brief description of: Size of the anticipated effort;
summary of actions to be performed; results expected; and/or special areas of interest.]
The EaaS Blanket Purchase Agreement (BPA), numbered QTA011GNB0010, issued by the
General Services Administration (GSA) for Email as a Service (EaaS) from Schedule 70 in
accordance with SmartBUY is hereby incorporated by reference.
outlines the scope of services across the service offerings, delivery models, and pricing options
for the EaaS solution.
[Information provided in Table 2 should align to the information outlined in Table 1 in this
document. For example, if Integration Services will be part of the scope, identify the
applications and defining characteristics that will be integrated with the target Email solution.]
The scope of the EaaS Solution will apply to the following components of [Agency/Department]:
[Component 1]
[Component 2]
[If applicable, identify which service offerings are not included in the scope of this SOW. If any
Agency/Department component(s) require EaaS services under the BPA that vary from the core
service listed above, identify the component(s) and the additional services required, including
the Service Offering, Delivery Model, and Type of Pricing. For those services or requirements
that may exceed the baseline service offerings available under the EaaS BPA, identify any
services or requirements that will need to be provided through supplemental Schedule 70
services.]
7. Specific Requirements
[Provide a performance-based narrative of the specific tasks, services and/or deliverables
that make up the SOW. Number the tasks sequentially, e.g. Task 1 and narrative, Task 2
and narrative, etc.]
7.1.Task Description
[Include deployment model/Lot number. The sample tasks below were split into one task
per service offering simply for clarity of presentation. Multiple service offerings may be
combined into a single task as appropriate resulting in one task per component or other
logical grouping suitable to the ordering activity.]
[Provide a total aggregate of [xxx – as derived from Table 1] GB of mailbox storage for
those mailboxes. Although the BPA specified a minimum of 5 GB storage per mailbox,
some vendors provide additional amounts of base storage per mailbox. Vendors
therefore may or may not need to provide costs against the additional storage CLIN
based on your overall requirements.]
[Provide email archiving services for a total of [xxx – As derived from Table 1]
mailboxes].
[Provide Blackberry Enterprise Server services for a total of [xxx – As derived from
Table 1] mailboxes.]
[Provide the following functional capabilities that are identified in the BPA as optional
requirements:]
o [Provide integration to the vendor trouble ticket system through web service
supported Application Program Interface (API).]
o [Allow the end-user(s) designated as the group mailbox owner to manage the
end-users with access to the group mailbox.]
o [Provide the end user with the option to create and edit email in a pop-up
window.]
o [Allow the end-user to designate contacts as shared with other end users.]
o [Provide additional support for other mobile device integration through dedicated
mobile web site. Specify the functionality required.]
o [Creation of intranet websites including the ability to create user content, serve
as document repository and track document history, and create wiki pages.]
[Provide the following Office Automation functional capabilities that are identified in the
BPA as optional requirements:]
o [Provide ability for end-users to transmit and receive faxes from the messaging
system.]
o [Any other office automation tasks beyond those provided as required or optional
within the BPA.]
[Provide a total aggregate of [xxx] GB of storage for office automation purposes for
those users.]
[Provide email migration services for [xxx] users at the Standard Migration Service level
for the deployment model and pricing type indicated above.]
The contractor shall be furnished current task pertinent information, and other
documentation or materials as required for conducting the tasks described hereunder.
For the purposes of migrating existing systems to the contractor provided systems and
as necessary for the implementation of requested implementations, the contractor shall
have full access to GFE and software to perform the duties on the project while
performing duties in government space.
All Government Furnished Property referred to in this clause will remain the property of
the Government, or its contractor, and under that entity’s control at all times. The
Contractor Travel - Describe any local or long distance travel the contractor will have to
perform to execute the task order. Identify the “to/from” locations of the travel, numbers
and duration of the trip.]
8. Constraints
[This section lists laws, rules, regulations, standards, technology limitations and other
constraints that the service and/or service provider must adhere to or work under.
Include any constraints not previously mentioned in other sections of this document, potentially
to include:]
The e-mail system shall allow the [Agency/Department] administrators remote administration
of end-user account provisioning, de-provisioning and access privileges through a web browser
interface.
The e-mail system shall allow the [Agency/Department] administrators to allow end-user access
through the use of username and password if an administrator determines that the end user cannot
utilize the Agency’s multi-factor identification.
The e-mail system shall provide the end users the ability reset their own passwords.
8.2. Authentication
[E.g. identification of specific authentication requirements NOT identified in the Technical
Objectives]
The e-mail system shall support integration with [Agency/Department’s] directory services
supporting an integrated authentication and authorization model (single sign on) utilizing the e-
Government profile for Security Assertion Markup Language 2.0 (SAML 2.0).
The e-mail system shall support dual factor authentication including support for PKI certificates
from a smartcard/CAC. It is envisioned that in the future all users will authenticate with the
PKI and use the Identity, Credentials, and Access Management (ICAM) access card; for
the present some users will continue to be authenticated by user name and password,
8.5. Accessibility
[Constraints for accessibility in alignment with the 508 Compliance requirements outlined in the
EaaS BPA]
8.6. Data
[Any constraints on the use and/or ownership of data, potentially including the identification of
data that will remain the property of the government]
Responder personnel shall adhere to the Privacy Act, Title 5 of the U.S. Code, Section 552a
and applicable agency rules and regulations as specified in the EaaS BPA.
9. Contract Type
[The ordering Agency/Department may acquire deliverables and services on a firm-fixed unit
price basis in the individual task orders.]
The term for each Order placed under the BPA shall be specified by the ordering
Agency/Department in the individual Order.
Under no circumstances may an Order be placed under the BPA if the BPA has expired,
or has been terminated or cancelled by the Government.
Notwithstanding anything to the contrary above, a multi-year Order placed under the
BPA must be consistent with FAR Subpart 17.1 and any applicable funding restrictions.]
All hosted email, collaboration and related services will be provided at the vendor’s locations
[either U.S. Based or Worldwide], and all Migration and Integration efforts [will be performed on
site at the Agency/Department location].