RFP D12PS00041 - Final.docx

SOLICITATION, OFFER AND AWARD

1. This Contract will not be a rated order

2. CONTRACT NUMBER:

3. SOLICITATION NUMBER: D12PS00041

6. REQUISITION/PURCHASE NUMBER:

7. ISSUED BY CODE

8. ADDRESS OFFER TO (If other than Item 7)

US Dept of Interior / NBC / Acquisition Services Directorate / Attn: Gregory Ruderman, Contracting Officer 381 Elden Street, Suite 4000 Herndon, VA 20170

NOTE: In sealed bid solicitations “offer” and “offeror” mean “bid” and “bidder”

SOLICITATION

9. Sealed offers in electronic copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 10C, or if handcarried, in the depository located in Reference Section L until 10:00 a.m. Eastern Standard local time February 29, 2012.

CAUTION LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

NUMBER

EXT.

Greg.Ruderman@aqd.nbc.gov

11. TABLE OF CONTENTS

AND OTHER STATEMENTS OF OFFERORS

OFFER (Must be fully completed by offeror)

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

12. In compliance with the above, the undersigned agrees, if this offer is accepted within 75 days (60 calendar days unless a different period is inserted by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the designated point(s), within the time specified in the schedule.

30 CALENDAR DAYS %

___ CALENDAR DAYS %

(The offeror acknowledges receipt of amendments to the

SOLICITATION for offerors and related documents numbered and dated):

FACILITY

16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER

AND

ADDRESS

OF

OFFEROR

EXT.

ADDRESS IS DIFFERENT FROM ABOVE - ENTER SUCH ADDRESS IN SCHEDULE.

AWARD (To be completed by Government)

19. ACCEPTED AS TO ITEMS NUMBERED

Reference Section B – Schedule of Prices

20. AMOUNT

21. ACCOUNTING AND APPROPRIATION

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

See Section G

ITEM

24. ADMINISTERED BY (If other than Item 7) CODE

25. PAYMENT WILL BE MADE BY CODE

See Section G

26. NAME OF CONTRACTING OFFICER (Type or print)

27. UNITED STATES OF AMERICA

Signature of Contracting officer

28. AWARD DATE

IMPORTANT -- Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 GENERAL

This solicitation is issued under FAR Part 12 (“Acquisition of Commercial Items”) and FAR Part 15 (“Contracting by Negotiation”) and various other FAR Parts as applicable.

This is a solicitation for commercial items prepared in accordance with the Uniform Contract format in FAR 15.204-1, as supplemented with additional information included in this section.

The following North American Industry Classification Code (NAICS Codes) is the primary code applicable to this acquisition: 541519 (Other Computer Related Services), business size standard of $25 Million. This is a Full and Open Competition and not set-aside for small business.

If you are interested in this acquisition, you may participate by submitting your response in accordance with the instructions included herein. See Section L of this document for “Instructions, Conditions, and Notices to Offerors or Respondents.”

B.2 CCR REGISTRATION

All Offerors must be registered with the Central Contractor Registration (www.ccr.gov). Offerors who have already completed their Representations & Certifications through the ORCA website (https://orca.bpn.gov/) do not need to provide hard copies of representations and certifications with their proposal as required in Section K of this Solicitation.

B.3 CONTRACTING OFFICER AND CONTACT INFORMATION FOR INQUIRIES

The Contracting Officer (CO) for this requirement is Gregory Ruderman. All questions regarding this Award must be submitted via e-mail to Mr. Ruderman (Greg.Ruderman@aqd.nbc.gov ) with a copy to Contract Specialist Brian Baker (Brian.Baker@aqd.nbc.gov ). Identify the RFP number in your subject line. Questions are due no later than 10:00 am EST on February 14, 2012. All questions must be submitted in a format other than “.PDF” that is compatible with Microsoft Office 2007 and the “.doc” or “.docx” standard. Do not put questions in the body of the e-mail. All questions should be delivered within an attached file. The Contracting Officer must be provided unlocked documents, or if password protected, each document’s password.

B.5 OTHER DIRECT COSTS (ODCS)

ODCs will not be authorized as part of the anticipated contract.

B.6 TRAVEL

Travel reimbursement is not authorized as part of the anticipated contract. Neither local nor Long Distance Travel is anticipated during the performance of this requirement

B.7 OVERTIME

Not Applicable – Overtime reimbursement is not authorized as part of the anticipated contract.

B.8 HOLIDAYS

The contractor shall establish a standard holiday schedule that exactly coincides with the Government’s schedule. Holidays and other non-work days peculiar to or dynamically declared by the Government shall be considered as holidays for contractor personnel. The Government does not anticipate work being conducted on holidays but will reserve the right to request contractor performance on these days. The following is a list of Government holidays:

B.9 OPTIONAL CLINS

Optional CLINS are designed to accommodate additional Governmental needs which cannot be fully anticipated at the time of award. Optional CLINS may be activated as often as necessary, but will not exceed the total quantity as specified within the CLIN structure. Any quantities not exercised in any performance period may be carried forth to any subsequent exercised option period. If additional capacity is required after the exhaustion of all optional quantities in the current period of performance, optional quantities from future option periods may be transferred to the current period. Any quantities carried from other than the current period of performance shall be exercised at the rate(s) for the current performance period.

B.10 REQUEST FOR DISCOUNT & INVERSE OR NO PRICE ESCALATION

In the spirit of Federal Information Technology Transformation, cost transparency, cost savings to the taxpayer, and to the Federal Government, please consider eliminating price escalation within your price submission for this project. We ask all firms to highly consider joining the President, Congress, and the Federal Government Workforce in removing automatic price increases from price proposals. Although each offeror’s solution will vary, with all else being equal, the Government expects competitive pricing for the cloud hosting portion of this project to be priced using an inverse escalation in the project’s option years. Please remember that price is an important factor for determining the awardee for this procurement.

B.11 CLIN DETAILS ( SCHEDULE OF PRICES - ATTACHMENT 1 )

All firms SHALL complete the attached schedule of prices spreadsheet as is and submit it with their proposal (as an “.xls” or “.xlsx” file or equal). Deviations or substitutions will not be accepted. Failure to comply may result in a non-responsive offer that is not considered for evaluation.

RFP D12PS00041

Section B

SCHEDULE OF PRICES

(USE ATTACHMENT 1 –Schedule of Prices Spreadsheet to enter data for official submission)

Use Attachment 1 for Official Submission

SECTION C - DESCRIPTIONS AND SPECIFICATIONS

STATEMENT OF OBJECTIVES

1. Purpose

The Department of the Interior (DOI) is pursuing the acquisition of cloud-based “Software as a Service” (SaaS) email and collaboration services from a commercial provider of Cloud Computing services. Interior’s goal is to transition its current email and collaboration services from disparate, on-premise systems to a highly integrated, innovative, creative, cost-effective, and evolving cloud-based environment. The ideal solution is an integrated suite of tools and capabilities that allows the government to transform the way business is conducted today, while also having the ability to manage and monitor service performance, quality, and delivery, through clearly defined roles and business rules, rather than through physical control of assets and direct software licensing.

Interior seeks a cloud-based solution that increases employee productivity and collaboration and improves its service to the American people. The objective of the cloud-based email and collaboration services acquisition is to reduce DOI’s service delivery costs, as well as equip and empower DOI employees with secure, modern, reliable communication. The resulting capabilities should act as a catalyst to accelerate and improve the delivery of mission goals and services in the future.

This Statement of Objectives (SOO) describes the outcomes DOI expects to achieve with regard to:

a. Modernizing its e-mail system

b. Provisioning of services in a government community or private cloud solution that include email, calendaring, cloud-based email archiving/journaling, instant messaging, desktop video conferencing, web-based collaboration systems and support for connecting mobile devices

c. Reducing the government’s in-house system maintenance burden and associated spending

d. Ensuring appropriate security and privacy safeguards

The cloud-based solution should:

a. Provide features, functionality and capabilities that meet industry performance and interoperability standards and utilize best practices

b. Offer the necessary redundancy, resiliency, and contingency capabilities to ensure service availability that meets DOI’s current and future needs.

c. Improve user experience and productivity

d. Provide a secure information system environment that complies with all required federal regulations and DOI specific security requirements

e. Leverage standard commercial service offerings that will require minimum software and/or service development work on behalf of DOI staff to meet DOI requirements

f. Ensure data portability to another cloud platform upon contract completion/termination

2. Background

The Federal CIO’s “25 Point Implementation Plan to Reform Federal Information Technology” published by OMB in December 2010 requires Federal agencies to implement a “Cloud First policy” in their acquisition of IT services and applications. Agencies are required to “default to cloud-based solutions whenever secure, reliable, cost-effective cloud options exist.”

In February 2011, the Federal CIO issued a “Federal Cloud Computing Strategy” that defines the executive branch’s approach to safely and securely move IT infrastructure services to a cloud-computing environment.

In the February 2011 Federal Cloud Strategy and the December 2010 25 point plan to reform Federal Information Technology Management, both from the Office of Management and Budget, each Federal agency’s CIO has been directed to leverage this strategy to begin planning the migration of their IT services to cloud solutions. Obtaining cloud-based email and collaboration services are cornerstone initiatives in DOI’s implementation of these directives.

Traditional outsourcing and system integration support is insufficiently adaptive and costly for Interior’s needs. Market research supports the replacement of the outsourced model with agile and cost effective commodity SaaS Cloud Computing services. DOI requires the rapid implementation of transformative, secure, cloud-based email and collaboration services across all bureaus and offices in order to reduce migration costs and engineering risk, improve levels of service, and provide a predictable cost model for ongoing operations.

2.1 Current Environment

The Department's implementation of email is comprised of seven distinct implementations of Lotus Domino and Microsoft Exchange owned and operated by bureaus and offices. These systems support approximately 92,000 users. Microsoft Office, which includes Microsoft Outlook, is deployed throughout the organization as Interior’s standard office automation suite. Roughly half of the Department’s total mailboxes are hosted on Lotus Domino and use the Lotus Notes client. Of Interior’s remaining Domino/Notes installations, half are not under current maintenance contracts, and may be several revisions behind, leaving them unable to leverage advances in collaboration capabilities.

Each of the seven email systems employed throughout the Department maintains its own email directory and, as a result, only Interior’s Enterprise Active Directory can be considered an authoritative source for building an enterprise address book. End user support for email is inconsistent as well. For example, weekend and after hours support may be provided on a "best effort" basis in some cases and 24/7/365 in others.

The nature of the mission of the Department and its bureaus is reflected in its highly distributed infrastructure, with more than 2,400 offices in the United States and its territories. Many are geographically isolated and challenged with poor network connectivity. Moreover, a growing number of employees work remotely and do not regularly utilize DOI facilities. Interior’s myriad automated systems and email capable devices employ POP3, IMAP, and SMTP internally to manage and distribute mail. Some of these systems generate automated, critical life and limb email notifications during emergencies such as earthquake and tsunami events. In addition to the critically time-sensitive nature of these communications, the volume of mail generated during such events can well exceed 10,000 additional messages each minute inbound and out.

The diversity in the implementation of email across the Department has created an excessively complex operational environment that is extremely fragile and regularly subject to issues such as undelivered mail, inconsistent entries in directories used for address book creation, and the delivery of multiple copies of single messages. These issues are most common when sending emails between bureaus or between bureaus and the Office of the Secretary, directly affecting the ability to support the overall mission of the Department. In addition, simple capabilities enjoyed by organizations leveraging a single email system, such as sending messages to all employees, are difficult to implement in the current environment.

Email journaling is currently implemented inconsistently, is difficult to use, and does not meet information retrieval (e-discovery) requirements. Additionally, the storage associated with e-mail journal archiving continues to grow and is costly to manage. Federal regulations for handling e-mail litigation hold and discovery demand that DOI implement a more efficient and cost effective process.

DOI will maintain customer (user) support to receive Tier 1 trouble calls or requests for assistance and interface with the appropriate technical support. No direct customer support is required from this solicitation. Only technical, system administration, and contract acquisition staff will interface directly with the Offeror.

Figure 1 - DOI Bureau and Office As-Is State

3. Scope

The scope of the resulting contract will include all Cloud Computing and support services required to transition, deploy, operate, maintain, safeguard and manage an enterprise-wide e-mail and collaboration environment as previously defined. Offerors shall provide a comprehensive management approach for managing software licenses for the development/production environments, end-user licenses, and fielded application configurations.

The cloud computing environment must consist of a government community cloud (including United States federal, state, local and tribal entities), or private cloud. For legal jurisdiction implications regarding ensuring the adequate safeguarding of Government sensitive information, including Personally Identifiable Information (PII), all the constituent assets of this cloud computing environment must reside within the continental United States, Hawaii, Alaska, Puerto Rico, Guam, and/or the Virgin Islands.

Regardless of teaming arrangements, the Offeror and its subcontractors shall comply with all required laws, rules, regulations, and standards, and these laws, rules, regulations, and standards shall apply equally to all parties involved in any aspect of managing, hosting, delivering, maintaining and/or supporting the Cloud Services.

3.1 Period of Performance

The base period of performance is for one year from contract award with six, one-year options.

4. Objectives

Interior seeks an integrated suite of cloud-based email and collaboration services that increases employee productivity, fosters greater collaboration, and improves the Agency’s service to the American people.

4.1 Business Objectives

Replace the current email and collaboration environment with cloud-based email and collaboration services that are integrated as seamlessly as possible via a single sign-on and that improve business performance by providing DOI users with expanded and new capabilities reflecting current industry offerings including, but not limited to, the following:

· Email, including calendar, task management, mobile device and webmail support

· Support for journaling to the Agency’s chosen third party provider

· Personal email archiving

· Robust and rapid search (full text) capability to enable forensics and e-discovery across all data, including active and archived files

· Instant Messaging

· Desktop video conferencing

· Collaboration Services, including web-based tools and services that enable employees to share documents and other information using collaborative team sites

· Compliance with security and regulatory requirements defined by OMB mandate, the Federal Information Security Management Act (FISMA), and enhanced DOI-specific security requirements among others

4.1.1 Mobile Device Support

The use of mobile devices to access email and collaboration services is a fundamental enhancement to employee productivity. DOI currently has an installed base of approximately 12,500 Blackberry devices that must be supported. DOI’s objectives in obtaining cloud-based email and collaboration services include continued support for BlackBerry and other mobile devices that use ActiveSync (or similar) “push” technology, such as the Apple iPad. Support for other devices is desirable but support for Blackberry and iPhone/iPad are primary objectives. Interior employs FiberLink’s cloud-based MaaS360 Mobile Device Management solution for managing devices other than the BlackBerry. As is the case for email services generally, Interior’s objective is to obtain mobile device connectivity solutions from the Offeror, replacing on-premise systems.

4.1.2 Collaborative Tools

Interior’s objectives include obtaining robust web-based, cloud-based collaborative services and capabilities (such as instant messaging, soft phone integration, on-line meetings, shared workspace, social media, video chat, groupware, workgroup support systems, etc.) to replace, augment, or compliment DOI’s current capabilities and enhance DOI staff productivity.

4.1.3 Email Journaling Services

DOI long-term objectives include obtaining a systematic archiving service that reduces storage costs as well as saves and protects the data contained in email messages in a separate immutable data store, with both messages and metadata indexed based upon keywords and message attributes for a deterministic period of time (potentially indefinitely) so that it can be retrieved quickly at a later date by an e-Discovery Service. Such services are not in scope of the CECS procurement. However, the government’s objectives do include obtaining cloud-based email services that support journaling to such a solution. Such journaling is typically performed using standard SMTP services, for instance.

4.1.4 Email Hygiene

Interior requires the ability to manage spam, phishing scams, viruses, malware, and other nuisances associated with modern email delivery. An objective of this solicitation is to obtain cloud-based services that allow individual users to define and manage both blacklists and whitelists in addition to enforcing globally-applied restrictions according to the Government’s needs. Due to the time-sensitive nature of email delivery in support of Interior’s mission, each of the organization’s mailbox consumers need real-time, on-demand access to email quarantined by the system in addition to automated daily (or customizable at intervals no greater than once daily) quarantine alerts.

4.1.5 DOI Active Directory Integration

DOI uses Microsoft’s Active Directory to create a single DOI-Wide directory of all users. This directory is known as the Enterprise Active Directory (EAD). The messaging and collaboration system must recognize the EAD as the authoritative source for authentication and as the source of information for populating bureau and office address books as well as a consolidated “All DOI” email address list.

4.2 Transition Objectives

Conduct a seamless and expedited transition from current legacy email and collaboration services to cloud-based services with minimal service disruption to day-to-day business operations, while ensuring data security and integrity:

· Plan and conduct an expedited transition from the current legacy environment to the new environment preserving data integrity and with minimal disruption to the users

· Migrate all DOI identified e-mail (server-side data migration) to the new Cloud Services environment by December 2012

· Achieve a high degree of user acceptance and adoption of the Cloud Services

· Establish an efficient and feasible data migration plan for existing online e-mail message stores

· Improve workforce efficiency and effectiveness and reduce costs by standardizing on the Cloud Services, and enabling user adoption of expanded functions and new capabilities.

· Deliver a training plan and associated end user and administrator training materials to support proficiency with service offerings and service management capabilities

· Include an executable exit strategy that would allow data portability to another solution or cloud platform upon contract completion/termination and that demonstrates transition readiness

4.3 Technical and Service Integrity Objectives

Obtain Cloud Services with proven high degree of confidentiality, integrity, reliability and availability which should, at a minimum:

· Provide 99.9% availability, or higher, to all DOI users with an acceptable applied penalty schedule

· Prevent the loss of DOI data, service degradation, and/or service disruption to DOI users in the event of planned or unplanned outage

· Provides the capability - including necessary capacity and availability - that ensures immediate and uninterrupted delivery of critical email notifications as described in SOO Section 2.1

· Provide 24 hours per day, seven days a week, 365 days per year troubleshooting service and support for inquiries, outages, and issue resolutions

· Provide a Trusted Internet Connection 2.0 (TIC 2.0, see http://www.dhs.gov/files/programs/gc_1268754123028.shtm ) compliant interconnection architecture

· Comply with federally mandated IPv6 requirements for public facing services (see http://www.cio.gov/documents/IPv6memofinal.pdf )

4.4 Security and Compliance Objectives

Obtain Cloud Services with the requisite Security, Confidentiality, Integrity, Availability, and Privacy levels and controls that are compliant with regulations, including:

· Federal government regulatory compliance requirements (i.e. Privacy Act, FISMA, CIPSEA, Federal Records Act, Freedom of Information Act, Trade Secrets Act, Health Insurance Portability and Accountability Act (HIPAA), Privacy Rules, etc.)

· Security standards and security control requirements for a Moderate Impact system as described in NIST Special Publications (SP) for cloud computing (SP 800-144, SP800-145, and SP 800-146) as well as NIST SP 800-53 with an accepted Certification and Accreditation (C&A) or Security Authorization

· Privacy Act, Title 5 of the United States Code (U.S.C.) § 552a and applicable agency rules and regulations Prior to approval for DOI operational readiness, the contractor shall be required to provide (for Government review and acceptance) the complete set of Security Assessment and Authorization artifacts, as required by FISMA for the information system having a Moderate security categorization. The deliverables are required to support system certification and DOI authorization to operate (ATO).

4.5 Management Objectives

Obtain Cloud Services from a provider that delivers cost effective, responsive, and efficient management and customer support that:

· Maintains ongoing high levels of user satisfaction with the Cloud Services

· Measures, and reports on, customer satisfaction with the delivery and use of Cloud Services

· Reduces the government’s burden related to the management of Cloud Services capabilities

· Allows for controlled, real-time, on-demand, government-initiated provisioning of mailbox and other collaboration suite services

· Provides DOI service level managers a web-based “dashboard” that enables 24x7x365 near real-time monitoring and visibility of:

· Cloud Services performance, service status, and key performance indicators of the system against the established SLAs and operational parameters; and

· Meaningful reporting and analytics that provide DOI with up-to-date and comprehensive information regarding technical and management performance (summarizing projected vs. actual measures), pricing and other related issues by bureau and office

· Offers comprehensive, meaningful, timely and self-explanatory invoices for managed services

5. Project Phases (all dates are expressed in calendar days)

5.1 Task 1: Government’s Operational Readiness and Acceptance Testing (GORAT - Phase I) The Government expects GORAT to be completed within 45 days of award. At the close of Phase 1, the vendor will deliver to the government for review and acceptance draft Assessment and Authorization (A&A) documentation, proposed solutions architecture, migration plans, prototypes, and test results necessary to demonstrate a high likelihood of success for delivery of the services described in this statement of objectives. The Government will have 7 days to review and submit to the vendor a report identifying any deficiencies evidenced in GORAT documentation and as a result of service testing. The vendor shall have 7 days to respond to the government’s report with a corrective action plan. The Government will have 7 days for final review and acceptance of the vendor’s proposed service solution.

5.2 Optional Task 2: Migration (Phase II)

Within 30 days of notification by the government of GORAT acceptance, the vendor shall begin migration and implementation for all of the DOI and work to ensure a full implementation no later than 12/31/2012.

5.3 Optional Task 3: Steady-State Phase (Phase III)

Phase III will be the full implementation and steady-state operations of the cloud-based email and collaboration services.

6. Constraints This SOO and accompanying attachments identifies laws, rules, regulations, standards, technology limitations and other constraints that the service and/or the Offeror must adhere to or work under.

If compliance with any one of the Constraints listed in this section is not included in the Offeror’s base offering and pricing, the Offeror must document this fact in the response, and the Offeror shall provide detail on the impact of the Constraint(s) on the Cloud Services pricing in proposal response. Offerors are encouraged to provide additional CLINs, with the appropriate description and documentation, for achieving compliance as appropriate.

6.1 Access Control

Seamlessly integrate with the DOI Identity, Authorization and Access Management (IdAAM) solution that consists of the Microsoft Active Directory (AD) and Public Key Infrastructure (PKI) architecture and associated Certificate Authority and DOI HSPD-12 PIV SmartCard-based credentials and enable logical authentication utilizing those credentials without requiring additional Contractor solution credentials; digital and electronic signing and signatures of emails and documents/content within the collaboration suite; and encryption of emails and documents/content using those capabilities.

6.2 Authentication

DOI currently utilizes name and password authentication, however the Department is transitioning to Entrust PKI for authentication. The email system shall support authentication using DOI’s Entrust PKI. It is envisioned that in the future all users will authenticate with the Entrust PKI and use the HSPD-12 PIV Smart Card; for the present some users will continue to be authenticated by user name and password, and this method must also be supported. Furthermore email encryption and signing shall use the existing Interior Entrust PKI and PIV Smart Card.

6.3 HSPD-12 Personnel Security Clearances

Acquired services shall comply with the following regulations and requirements:

Homeland Security Presidential Directive-12 requires that all federal entities ensure that all contractors have current and approved security background investigations that are equivalent to investigations performed on federal employees. The Contractor shall comply with DOI policy relating to HSPD-12. Background investigations will be performed by the Office of Personnel Management (OPM) (See DIAPR 2010-04, Implementation of Homeland Security Presidential Directive-12 (HSPD-12) Part 2, DOI Access Program Implementation at http://www.doi.gov/pam/DIAPR%202010-04.pdf).

DOI separates the risk levels for personnel working on federal computer systems into three categories: Low Risk, Moderate Risk, and High Risk. The level/complexity of background investigations must be the same as for a Federal employee holding a similar position. Criteria for determining which risk level a particular contract employee falls into are shown in Illustration 1 of DOI’s Departmental Manual (DM) 441, Chapter 3 (available at: http://elips.doi.gov/app_dm/act_getfiles.cfm?relnum=3860). The DM Chapter provides guidance for the appropriate background investigations based on types of access. The Contractor shall ensure that only appropriately cleared personnel are assigned to positions that meet these criteria.

Those contract personnel determined to be in a Low Risk position will require a National Agency Check with Written Inquiries (NACI) or equivalent investigation.

Those Applicants determined to be in a Moderate Risk position will require either a Limited Background Investigation (LBI) or a Minimum Background Investigation (MBI) based on the Contracting Officer’s (CO) determination. Those Applicants determined to be in a High Risk position will require a Background Investigation (BI). The Contracting Officer, through the Contracting Officer’s Technical Representative or Program Manager will ensure that a completed Contractor Information Worksheet (CIW) for each Applicant is forwarded to the Federal Protective Service (FPS) in accordance with the DOI//FPS Contractor Suitability and Adjudication Program Implementation Plan dated 20 February 2007. FPS will then contact each Applicant with instructions for completing required forms and releases for the particular type of personnel investigation requested.

Applicants will not be reinvestigated if a prior favorable adjudication is on file with FPS or DOI, there has been no break in service, and the position is identified at the same or lower risk level.

After the required background investigations have been initiated, the Contractor may request authorization for employees whose investigations are pending to access systems supporting DOI email and collaboration applications. The DOI Chief Information Officer may grant this authorization based on determination of risk to the government and operational need for the support of these applications.

Contractor shall comply and cause Provider to agree to comply with the United States Government and the DOI regulations as outlined in DM441, Chapter 3, in reference to background checks, position risk and sensitivity. The Provider is responsible for maintaining an up to date list of all personnel that have access to DOI data. This list shall be provided by the service provider at any time during the life of the contract when requested by the CO or COR via email. The vendor shall provide the list within three business days of the request.

6.4 Non-Disclosure Agreements

The Offeror shall require each employee that interfaces with the DOI cloud services data, its management, hosting, and delivery to sign non-disclosure agreements prior to beginning work on the DOI contract. Standard non-disclosure statements shall be provided as required for system administration personnel who may have access to government data in the course of their duties.

6.5 Accessibility

Requirements for accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) are determined to be relevant. Information about the Section 508 Electronic and Information Technology (EIT) Accessibility Standards may be obtained via the Web at the following URL: www.Section508.gov. The Government Product/Service Accessibility Template (GPAT) is found within Attachment 4 of this solicitation. Generally accepted inspection and test methods corresponding to the identified Section 508 standards are reflected in the EIT Acceptance Guide found within Attachment 4.

6.6 Data Ownership

· All data (e-mail traffic, contact information, calendar contents, etc) is and shall remain the exclusive property of the government. The scope and pricing of the agreement must ensure that the government may have access and download capability of all data for research, investigation, transfer, or migration to other systems in a readable format.

· The Offeror shall provide notice immediately of any third-party request for DOI data and the request cannot be serviced without DOI’s prior approval.

6.7 Sensitive and Embargoed Data

In accordance with the Federal Acquisitions Regulations (FAR) clause 52.239-1 in meeting the scope and objectives of this SOO, the Offeror shall:

Protect the confidentiality of confidential information by adhering to safeguard principles, including:

· emphasizing to their officers, employees, contractors, and agents the importance of protecting the confidentiality of information in cases where the identity of respondents can reasonably be inferred by either direct or indirect means;

· training their officers, employees, contractors, and agents in their legal obligations to protect the confidentiality of respondent identifiable information, and in the procedures that must be followed to provide access to such information;

· implementing appropriate measures to assure the physical and electronic security of confidential data;

· establishing a system of records that identifies individuals accessing confidential data and the project for which the data was required;

· being prepared to document their compliance with safeguard principles to other agencies authorized by law to monitor such compliance;

· not publishing or disclosing in any manner, without the Contracting Officer’s written consent, the details of any safeguards used by the Offeror under the resulting contract or otherwise provided by or for the government.

The Offeror shall refer to the SOO attachments in this solicitation for further guidance and clarification related to rules and regulations in meeting the scope and objectives of this RFP.

7. Definitions For the purposes of this solicitation package, the Offeror shall refer and use the following definitions.

Private Cloud: Following the NIST definition, a private cloud is one in which “the cloud infrastructure is provisioned for exclusive use by a single organization comprising multiple consumers (e.g., business units). It may be owned, managed, and operated by the organization, a third party, or some combination of them, and it may exist on or off premises. A private cloud is one in which the infrastructure and computational resources are operated exclusively for an organization.”

Government Community Cloud: Following the NIST definition, a Community Cloud is one in which “the cloud infrastructure is provisioned for exclusive use by a specific community of consumers from organizations that have shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be owned, managed, and operated by one or more of the organizations in the community, a third party, or some combination of them, and it may exist on or off premises.” A Government Community Cloud is a multi-tenant cloud environment that is specifically limited to Government clients (United States federal, state, local, and tribal) with an appropriate Government issued domain name.

Software-as-a-Service (SaaS): Defined by NIST as “the capability provided to the consumer to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web- based email), or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.”

Cloud Services: For the purposes of this solicitation, Cloud services refers to the provision of a secure SaaS offering that DOL is requesting as part of this solicitation to meet its requirements. These secure services are: email, calendar, tasks, archive, eDiscovery, office automation, collaboration, and electronic records management. These services, heretofore referred to as “Cloud Services”, are further defined in Attachment 1, Features and Function Matrix.

Email: Email will be used throughout this solicitation, except where expressly stated, as shorthand for the following applications: email, calendar, contacts, and tasks Offeror or Quoter: For the purposes of this solicitation “Offeror” or “Quoter” will be used interchangeably to refer to any combination of teaming arrangements that may include: Cloud Service Provider (CSP), an Integrator, and any other Third party involved in any aspect of managing, hosting, delivering, maintaining and/or supporting the Cloud Services.

SECTION D – PACKAGING AND MARKINGS

This section is intentionally left blank.

SECTION E - INSPECTION AND ACCEPTANCE

E.1 CLAUSES INCORPORATED BY REFERENCE

The following contract clauses pertinent to this section are hereby incorporated by reference in accordance with the clauses at FAR “52.252-2 Clauses Incorporated by Reference” in Section I of this contract. This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. The full text of a clause may be accessed electronically at this address: http://farsite.hill.af.mil/vffar1.htm or https://www.acquisition.gov/far/

E.2 CLAUSES INCORPORATED BY FULL TEXT

Inspection and Acceptance - Services Inspection, acceptance, and rejection will be based upon compliance with the requirements. Inspection of services to be furnished hereunder shall be performed by the Contracting Officer’s Representative (COR) in accordance with Clause 52.246-4 above. The Government reserves the right to conduct any inspection and tests it deems reasonably necessary to assure that the services provided conform to all aspects of the contract requirements. Final acceptance of the deliverables and the Progress Reports shall be made by the COR.

Inspection and Acceptance Criteria Final inspection and acceptance of all work performed, reports and other deliverables will be performed by the COR at the place of delivery. The basis for acceptance shall be compliance with the requirements and other terms and conditions of the contract. Deliverable items that are rejected shall be corrected in accordance with applicable clauses.

General quality measures as set forth below will be applied to each work product received from the contractor under the SOO:

· Work products shall be clear and concise. Any/all diagrams shall be easy to understand and be relevant to the supporting narrative.

· All text and diagrammatic files shall be editable by the Government.

· Work products shall be submitted on or before the due date specified in the SOO/deliverables table or submitted in accordance with a later scheduled date determined by the Government.

SECTION F - DELIVERIES OR PERFORMANCE

CLAUSES INCORPORATED BY REFERENCE

The following contract clauses pertinent to this section are hereby incorporated by reference in accordance with the clauses at FAR “52.252-2 Clauses Incorporated by Reference” in Section I of this contract. This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. The full text of a clause may be accessed electronically at this address: http://farsite.hill.af.mil/vffar1.htm or https://www.acquisition.gov/far/

See Section B12

F.2 PLACE OF PERFORMANCE

All service provider information system components that access, store, transmit and/or process DOI information must be located within the sole jurisdiction of the United States Federal Government (i.e., within the continental United States, Hawaii, Alaska, Puerto Rico, Guam, and/or the Virgin Islands).

F.3 52.242-15 -- STOP-WORK ORDER (AUG 1989)

(a) The Contracting Officer may, at any time, by written order to the Contractor, require the Contractor to stop all, or any part, of the work called for by this contract for a period of 90 days after the order is delivered to the Contractor, and for any further period to which the parties may agree. The order shall be specifically identified as a stop-work order issued under this clause. Upon receipt of the order, the Contractor shall immediately comply with its terms and take all reasonable steps to minimize the incurrence of costs allocable to the work covered by the order during the period of work stoppage. Within a period of 90 days after a stop-work is delivered to the Contractor, or within any extension of that period to which the parties shall have agreed, the Contracting Officer shall either-

(1) Cancel the stop-work order; or

(2) Terminate the work covered by the order as provided in the Default, or the Termination for Convenience of the Government, clause of this contract.

(b) If a stop-work order issued under this clause is canceled or the period of the order or any extension thereof expires, the Contractor shall resume work. The Contracting Officer shall make an equitable adjustment in the delivery schedule or contract price, or both, and the contract shall be modified, in writing, accordingly, if-

(1) The stop-work order results in an increase in the time required for, or in the Contractor's cost properly allocable to, the performance of any part of this contract; and

(2) The Contractor asserts its right to the adjustment within 30 days after the end of the period of work stoppage; provided that, if the Contracting Officer decides the facts justify the action, the Contracting Officer may receive and act upon the claim submitted at any time before final payment under this contract.

(c) If a stop-work order is not canceled and the work covered by the order is terminated for the convenience of the Government, the Contracting Officer shall allow reasonable costs resulting from the stop-work order in arriving at the termination settlement.

(d) If a stop-work order is not canceled and the work covered by the order is terminated for default, the Contracting Officer shall allow, by equitable adjustment or otherwise, reasonable costs resulting from the stop-work order.

F4. NOTICE TO THE GOVERNMENT OF DELAYS

In the event the Contractor encounters difficulty in meeting performance requirements, or when it anticipates difficulty in complying with the contract delivery schedule or date, or whenever the Contractor has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this contract, the Contractor shall immediately notify the CO and the COR, in writing, giving pertinent details, provided however, that this data shall be informational only in character and that this provision shall not be construed as a waiver by the Government of any delivery schedule or date or of any rights or remedies provided by law or under this contract.

F.5 DELIVERABLES

Deliverable - Subcontracting Plan IAW 52.219-9 within 30 days after contract award

See Attachment 5 for the Schedule of Deliverables

SECTION G -- CONTRACT ADMINISTRATION DATA

G.1 CONTRACTING OFFICER’S REPRESENTATIVE (COR)

The COR for this effort is as follows:

To be Named at Award

The COR is the individual within the Program Management function who has overall technical responsibility for this effort. The COR supports the Contracting Officer (CO) during administration of this effort by:

1. Making final decisions regarding any recommended rejection of deliverables;

1. Providing technical clarification relative to overall workload matters;

1. Providing advice and guidance to the Contractor in the preparation of deliverables and services;

1. Providing acceptance of deliverable products to assure compliance with requirements.

The COR also provides technical direction to the Contractor, i.e., shifting work emphasis between areas of work; fills in details, or otherwise serves to accomplish the purpose of this effort. Technical direction shall be within the requirement documents and award for this effort, including the contractor’s proposal documents. The COR, nor any other federal employee except the Contracting Officer, does NOT have the authority to- and may NOT - issue any technical direction which:

1. Constitutes an assignment of work outside the general scope of this effort;

1. Constitutes a change as defined in the “Changes” clause;

1. In any way causes an increase or decrease in price or the time required for performance;

1. Changes any of the terms, conditions, or other requirements of this effort; and

1. Suspends or terminates any portion of this effort.

All technical direction shall be issued in writing by the COR or will be confirmed by the COR in writing within 10 calendar days after verbal issuance. A copy of the written direction shall be furnished to the CO.

In addition to providing technical direction, the COR will:

1. Monitor the Contractor’s technical progress, including surveillance and assessment of performance, and recommend to the CO, any changes in the requirement;

1. Assist the Contractor in the resolution of technical problems encountered during performance; and

1. Perform inspection and acceptance or recommendation for rejection of Contractor deliverables and identify deficiencies in delivered items. This does not replace any other quality assurance inspection requirements that are specified elsewhere within this SOW.

If in the opinion of the Contractor, any instruction or direction issued by the COR is outside of their specific authority, the Contractor shall not proceed but shall notify the CO in writing within 5 working days after receipt of any instruction or direction.

G.2 CONTRACTING OFFICER AUTHORITY (CO)

The contracting officer is:

Gregory Ruderman US Department of the Interior Acquisition Services Directorate 381 Elden St., Suite 4000

Greg.Ruderman@aqd.nbc.gov

In no event shall any understanding or agreement between the Contractor and any Government employee other than the Contracting Officer on any contract, modification, change…