RFP_MPSAAS_.pdf

FOR OFFICIAL USE ONLY

STATEMEMT OF Work (SOW)

FOR

Logistics Supply Chain Management System (LSCMS) Microsoft Project Server as a Service (MPSAAS)

This document contains source selection information related to the conduct of a Federal agency procurement, the disclosure of which is restricted by Section 27 of the Office of Federal Procurement Policy Act (41 U.S.C. 423). The unauthorized disclosure of such information may subject both the discloser and recipient of the information to contractual, civil, and/or criminal penalties as provided by law.

1 TITLE

FEMA Logistics Supply Chain Management System (LSCMS) Microsoft Project Server as a Service (MPSAAS)

2 BACKGROUND

LSCMS provides near real-time asset and commodity visibility tracking, and improves the speed, performance and accountability for the receipt, inventory management, transportation, deployment and distribution of critical disaster assets and commodities.

The intent of the LSCMS solution is to provide for coordination, control, and reporting of assets during emergency response activities and during regular non-emergency operations.

In an effort to consolidate similar technology needs, the FEMA Office of Logistics Systems (OLS) desires to have primary and secondary common operating environments established in the data centers to help gain efficiency and effectiveness in its operations. The Department has selected the SharePoint environment as the first common operating environment to be implemented. As a result, it is the desire of The Department of Homeland Security to 1) consolidate Component collaboration systems into the DHS Enterprise Data Centers (DC1 and DC2) with the standup of a unified SharePoint as a Service (SPTaaS) capability and 2) to utilize the new SharePoint COE for all future collaboration efforts. The requirements for this SPTaaS managed-service offering have been jointly agreed upon by representatives from the COE Team and select Component agency partners.Components. SPTaaS shall be hosted using a common architecture and infrstructure with primary capabilities at DC2 and disaster recovery capabilities at DC1.

The Enterprise System Development Office (ESDO), an organization under the DHS Chief Information Officer, is the Department’s executive sponsor of this program. The Components will leverage their existing licenses (or will obtain the licenses via a department-wide contract) to access SharePoint.

3 SCOPE

The scope of this Statement of Work is to award a Fixed Price Task Order provide the FEMA Office of Logistics Systems (OLS) timely and effective access to a secure Microsoft Project Server 2010 hosted service that includes tools and services to help OLS users manage information and collaborate effectively. The contractor shall provide provide users the ability to easily create and manage custom team-and-project-focused sites for collaboration and personal productivity. This service shall be provided for daily operations and support surge capabilities to OLS during National Emergency events (natural or otherwise).

4 ASSUMPTIONS

The following assumptions are applicable to this SOW:

The awardee of MPSAAS has immediate access to Microsoft Enterprise Services to support the software Licenses to support this requirement Stakeholders required.

The awardee of MPSAAS will leverage the latest and greatest Microsoft technology through direct access to the services required to ensure that this technology is deployed and maintained to maximize its technical and cost benefits.

The awardee can deliver Department of Homeland Security Certified and Accredited MPSAAS service no later than 30 days after award.

5 APPLICABLE DOCUMENTS

The following standards are applicable to this requirement:

EO12472, Assignment of National Security and Emergency Preparedness

Telecommunications Functions EO 13011 Federal Information Technology OMB Circular A-130, Management of Federal Information Resources PDD 63, Critical Infrastructure Protection PL 107-296, Homeland Security Act PL 104-106, Information Technology Management Reform Act PL 103-63, Government Performance and Results Act PL 107-347, Federal Information Security Management Act PL 100-235, Computer Security Act of 1987 PL 105-220, Rehabilitation Act

6 SPECIFIC TASKS

6.1 Task 1 – Microsoft Project Server as a Service

The contractor shall possess the business, technical and management skills to deliver MPSAAS. It is expected that the contractor shall have intimate knowledge of Department of Homeland Securities Data Center (DC) 2 system environment and architecture deliverables to ensure completeness, consistency, and quality. Tasks expected from the contractor are inclusive of the following:

• Provide direct access and storage through the Department of Homeland Securities Data Center 2 (DC) to the Project 2010 site collection

• Provide a dedicated SharePoint 2010 and Project Server 2010 farm environment.

• Enable users to create and maintain automated master project schedules for programs and lines of business

• Aggregate key project data into executive level dashboard view or storyboard to quickly identify risks and upcoming milestones

• Link events and resource dependencies across project portfolios to identify potential risks and allow for pro-active risk mitigation planning.

• Service option shall supports up to 65 users with a minimum of 225 GB initial storage data

6.2 Task 2 – Microsoft Project Server as a Service

• Provide up to 160 hours of on-demand technical services

7 DELIVERABLES AND DELIVERY SCHEDULE

The contractor shall provide the deliverables according to the following tables:

Deliverable Description Sow Reference Due Date Provision Project Server Completed

Provision OLS

MPSAAS

Task 1 No later than 30 Days after award

Provide on-demand Technical Support

Technical Support Task 2 As required 30 Days after award

Monthly Status Report Monthly Status Report of all Contract Tasks

Task 1 and 2 30 days after award;

monthly thereafter

8 GOVERNMENT-FURNISHED EQUIPMENT AND INFORMATION

No GFE will be provided to the contractor. GFI will be provided to the managed service provider as needed in order to continue OLS current MPSAAS service, or resolve service desk tickets.

9 PLACE OF PERFORMANCE

Data Center 2 (DC2) in Clarksville, VA.

10 PERIOD OF PERFORMANCE

The period of performance is from date of award through 6/26/2015.

11 Travel Costs:

NA

12 INFORMATION TECHOLOGY SECURITY CLEARANCE

The work to be conducted by the contractor will be UNCLASSIFIED. The individuals working on the Enterprise Data Center contract for DHS OCIO should already have the appropriate clearances. The clearances are required for the work they perform at DC2 and for the different components. DHS OCIO determines the level of clearance required.

When sensitive Government information is processed on Department telecommunications and automated information systems, the Contractor shall provide for the administrative control of sensitive data being processed. Contractor personnel must have favorably adjudicated background investigations commensurate with the defined sensitivity level.

Contractors who fail to comply with Department security policy are subject to having their access to Department IT systems and facilities terminated, whether or not the failure results in criminal prosecution. Any person who improperly discloses sensitive information is subject to criminal and civil penalties and sanctions under a variety of laws (e.g., Privacy Act).

Contractor access will be terminated for unauthorized use. The contractor agrees to hold and save DHS harmless from any unauthorized use and agrees not to request additional time or money under the contract for any delays resulting from unauthorized use or access.

13 INFORMATION TECHNOLOGY SECURITY TRAINING AND OVERSIGHT

Before receiving access to IT resources under this contract the individual must receive a security briefing, which the Contracting Officer’s Technical Representative (COR) will arrange, and complete any nondisclosure agreement furnished by DHS.

14 HSAR 3052.204-71 Contractor Employee Access Clause

CONTRACTOR EMPLOYEE ACCESS (JUN 2006)

(a) Sensitive Information, as used in this Chapter, means any information, the loss, misuse, disclosure, or unauthorized access to or modification of which could adversely affect the national or homeland security interest, or the conduct of Federal programs, or the privacy to which individuals are entitled under section 552a of title 5, United States Code (the Privacy Act), but which has not been specifically authorized under criteria established by an Executive Order or an Act of Congress to be kept secret in the interest of national defense, homeland security or foreign policy.

This definition includes the following categories of information:

(1) Protected Critical Infrastructure Information (PCII) as set out in the Critical Infrastructure Information Act of 2002 (Title II, Subtitle B, of the Homeland Security Act, Public Law 107-296, 196 Stat. 2135), as amended, the implementing regulations thereto (Title 6, Code of Federal Regulations, Part 29) as amended, the applicable PCII Procedures Manual, as amended, and any supplementary guidance officially communicated by an authorized official of the Department of Homeland Security (including the PCII Program Manager or his/her designee);

(2) Sensitive Security Information (SSI), as defined in Title 49, Code of Federal Regulations, Part 1520, as amended, “Policies and Procedures of Safeguarding and Control of SSI,” as amended, and any supplementary guidance officially communicated by an authorized official of the Department of Homeland Security (including the Assistant Secretary for the Transportation Security Administration or his/her designee);

(3) Information designated as “For Official Use Only,” which is unclassified information of a sensitive nature and the unauthorized disclosure of which could adversely impact a person’s privacy or welfare, the conduct of Federal programs, or other programs or operations essential to the national or homeland security interest; and

(4) Any information that is designated “sensitive” or subject to other controls, safeguards or protections in accordance with subsequently adopted homeland security information handling procedures.

(b) “Information Technology Resources” include, but are not limited to, computer equipment, networking equipment, telecommunications equipment, cabling, network drives, computer drives, network software, computer software, software programs, intranet sites, and internet sites.

(c) Contractor employees working on this contract must complete such forms as may be necessary for security or other reasons, including the conduct of background investigations to determine suitability. Completed forms shall be submitted as directed by the Contracting Officer. Upon the Contracting Officer's request, the Contractor's employees shall be fingerprinted, or subject to other investigations as required. All contractor employees requiring recurring access to Government facilities or access to sensitive information or IT resources are required to have a favorably adjudicated background investigation prior to commencing work on this contract unless this requirement is waived under Departmental procedures.

(d) The Contracting Officer may require the contractor to prohibit individuals from working on the contract if the government deems their initial or continued employment contrary to the public interest for any reason, including, but not limited to, carelessness, insubordination, incompetence, or security concerns.

(e) Work under this contract may involve access to sensitive information. Therefore, the Contractor shall not disclose, orally or in writing, any sensitive information to any person unless authorized in writing by the Contracting Officer. For those contractor employees authorized access to sensitive information, the contractor shall ensure that these persons receive training concerning the protection and disclosure of sensitive information both during and after contract performance.

(f) The Contractor shall include the substance of this clause in all subcontracts at any tier where the subcontractor may have access to Government facilities, sensitive information, or resources.

(g) Before receiving access to IT resources under this contract the individual must receive a security briefing, which the Contracting Officer’s Technical Representative (COR) will arrange, and complete any nondisclosure agreement furnished by DHS.

(h) The contractor shall have access only to those areas of DHS information technology resources explicitly stated in this contract or approved by the COR in writing as necessary for performance of the work under this contract. Any attempts by contractor personnel to gain access to any information technology resources not expressly authorized by the statement of work, other terms and conditions in this contract, or as approved in writing by the COR, is strictly prohibited. In the event of violation of this provision, DHS will take appropriate actions with regard to the contract and the individual(s) involved.

(i) Contractor access to DHS networks from a remote location is a temporary privilege for mutual convenience while the contractor performs business for the DHS Component.

It is not a right, a guarantee of access, a condition of the contract, or Government Furnished Equipment (GFE).

(j) Contractor access will be terminated for unauthorized use. The contractor agrees to hold and save DHS harmless from any unauthorized use and agrees not to request additional time or money under the contract for any delays resulting from unauthorized use or access.

(k) Non-U.S. citizens shall not be authorized to access or assist in the development, operation, management or maintenance of Department IT systems under the contract, unless a waiver has been granted by the Head of the Component or designee, with the concurrence of both the Department’s Chief Security Officer (CSO) and the Chief Information Officer (CIO) or their designees. Within DHS Headquarters, the waiver may be granted only with the approval of both the CSO and the CIO or their designees. In order for a waiver to be granted:

(1) The individual must be a legal permanent resident of the U.S. or a citizen of Ireland, Israel, the Republic of the Philippines, or any nation on the Allied Nations List maintained by the Department of State;

(2) There must be a compelling reason for using this individual as opposed to a U.S.

citizen; and

(3) The waiver must be in the best interest of the Government.

(l) Contractors shall identify in their proposals the names and citizenship of all non-U.S.

citizens proposed to work under the contract. Any additions or deletions of non-U.S.

citizens after contract award shall also be reported to the contracting officer.