Amendment 47HAA021R0001_0002.pdf

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

E. IMPORTANT: Contractor is not is required to sign this document and return copies to the issuing office.

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. CONTRACT ID CODE

2. AMENDMENT/MODIFICATION NUMBER 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQUISITION NUMBER 5. PROJECT NUMBER (If applicable)

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

STANDARD FORM 30 (REV. 11/2016)

Prescribed by GSA FAR (48 CFR) 53.243

FACILITY CODE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers is extended. is not extended.

12. ACCOUNTING AND APPROPRIATION DATA (If required) copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NUMBER AS DESCRIBED IN ITEM 14.

CHECK ONE A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER

NUMBER IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation data, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15C. DATE SIGNED

15A. NAME AND TITLE OF SIGNER (Type or print)

16C. DATE SIGNED

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

PAGE OF PAGES

6. ISSUED BY CODE

8. NAME AND ADDRESS OF CONTRACTOR (Number, street, county, State and ZIP Code) (X)

CODE

15B. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

16B. UNITED STATES OF AMERICA

(Signature of Contracting Officer)

Previous edition unusable

H1AW

Sharmel Lane, Contract Specialist/Contracting Officer

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

The purpose of this amendment is to provide the Government's answers to additional questions posed, revise the pricing template and revise Sections C, E, L and M of the solicitation.

ALL OTHER TERMS AND CONDITIONS REMAIN UNCHANGED.

H1AA

OAS, Office of Internal Acquisition, Acquisition Services Division (H1AW)

1800 F ST NW

Washington, DC 20405 USA

OAS, Office of Internal Acquisition, Acquisition Operations Division 1800 F ST NW., 7th Floor Washington, DC 20405 USA

GQIPOA-21-0009

47HAA021R0001

1 93

8/18/2021

7/20/2021

PART I – THE SCHEDULE

SECTION B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 SCHEDULE OF SERVICES

This is a fixed-price contract; however, some CLINs will be labor hour. The contractor’s proposal shall include the necessary disciplines/labor categories, hourly rates and estimated level of effort to perform the services in Section C of the solicitation.

Contractor’s shall prepare their price quotations for this solicitation using the attached Price Schedule template in MS Excel format. Contractors must ensure that their price quotations include proposed pricing for all tasks, CLINs, and deliverables.

Price quotations that do not conform to the format in the attached Price Schedule template may be rejected and receive no further consideration for award purposes.

Contractors are to complete Attachment 6, Pricing Template, Tabs 1 -7 Tab 1 - Total Evaluated Price Tab 2 - Licensing Hosting Data Tab 3 - ATO & Security Tab 4 - Operations and Maintenance (O&M) Tab 5 - Configuration Tab 6 - Implementation Tab 7 - Hardware & Software

B.2 HOURLY RATES FOR CONTRACT WORK

The contractor shall submit hourly rates and estimated level of effort for all labor categories proposed under this contract. Hourly rates are to include all associated costs, excluding travel.

B.3 TRAVEL COSTS

The costs for travel will be reimbursed to the contractor in accordance with the Federal Travel Regulation (FTR) as defined in FAR Part 31.205-46, Travel Costs.

SECTION C – PERFORMANCE-BASED STATEMENT OF OBJECTIVES

(SOO)

C.1 INTRODUCTION

The General Services Administration’s (GSA) Office of the Chief Information Officer – Office of Public Buildings Information Technology Services (PB-ITS) in support of the PBS Office of Facilities Management (OFM) and Office of Financial Management (OCFO), 1800 F Street, NW, Washington, DC, seeks to acquire a new Cloud-based, commercial-off-the-shelf (COTS) enterprise-wide solution that includes hosting, licensing, configuration, data architecture, integration, and support services for an advanced metering, utility and waste data tracking, and utility invoice processing system. The Government intends to award a single-award contract to replace existing applications and services: Energy Usage Analysis System (EUAS), Advanced Metering System (ION EEM), the solid waste module of the GSA’s Sustainable Operations and Maintenance (SOM), and the service for processing of utility invoices for payment. The solution will provide a single integrated environment to be managed by a single Offeror.

C.2 BACKGROUND

The PBS OFM Energy and Utility Management Division, serves as the agency-wide center of expertise for all utility related functions, including advanced metering, energy and water usage intensity reporting, utility contracting, utility rate intervention, demand response, and more.

The Energy Division is required to track energy intensity, water intensity, greenhouse gas emission, and other energy related data to comply with federal mandates. The existing energy and water tracking solution, EUAS, supports the mission of GSA by housing both current and historic energy and water use and cost data for GSA-operated buildings, and providing a variety of preset reports to internal and external stakeholders. The system houses monthly historical energy data back to 1985 and water data back to 1997. Currently it tracks approximately 5,000 accounts for approximately 1,500 leased and GSA owned buildings. The system is a portlet within the Minor Applications Rationalization and Consolidated (MARC) framework which is housed within the PBS Portal. The platform is expected to reach end-of-life in the next two to three years. Appendix D Site- Generation Tracking gives examples of the types of reports desired.

The PBS OFM Facility Risk Management Division (FRMD) is responsible for national environmental programs, including solid waste and recycling. Waste diversion is a criterion for determining sustainable federal building status. In accordance with current executive orders and federal sustainability requirements, GSA is required to assess progress on waste management and instructed to track the disposition of non-hazardous solid waste (not including construction and demolition waste and debris) and report waste generated and percentage going to treatment and disposal facilities (e.g., landfills or incinerators without energy recovery) in annual Sustainability Plans. GSA tracks waste from buildings 10,000 https://www.sustainability.gov/pdfs/gsa-2019-sustainability-plan.pdf

GSF or greater, where GSA is directly responsible for waste disposal services for the building (e.g., through a waste management service contract), but GSA’s Regional Offices may include waste from smaller facilities at their discretion. The publicly available national metrics that GSA needs to report are: metric tons of non-hazardous waste generated; percentage (by weight) of non-hazardous waste diverted from landfills/incinerators; and percentage (by weight) of non-hazardous waste sent to landfills/incinerators. Sections C.10 (Solid Waste/Trash/Recycling Management), C.11 (Environmental Reporting), and Exhibit 6 (Recycling and Solid Waste and Recycling Report) of PBS OFM’s National Custodial Specification requires GSA’s custodial service contractors to provide monthly reports of solid waste and recycling data to GSA’s Contracting Officers (COs) and Contracting Officer Representatives (CORs).

From fiscal year 2015 to the present, the FRMD has used the Sustainable Operations Maintenance (SOM) Tool to track sustainability performance data on the disposal and management of solid waste generated at GSA-owned buildings.

The attached documents, Appendix A Sample Waste Import File, Appendix B Sample Waste Reports and Conversion Factors, and Appendix C Solid Waste Management SOM Tool Instruction, provide an overview of the current data tracking tool. The solid waste data is entered in the SOM Tool at the individual building and campus (i.e., more than one building) level. There are 1,664 federally owned buildings and 136 campuses (comprising buildings). Each building and campus has a unique ID, and the campus ID is mapped to unique building IDs. The SOM Tool contains solid waste data, reported quarterly by building or campus, to include: quantity of waste (in tons); material type (seven waste categories); waste disposal cost ($); and recycling revenue ($). Historical data back to 2011 is available to view and download in the tool. PBS does not intend to continue the use of the SOM Tool for solid waste data management in the near future.

The PBS OFM Energy Division is also responsible for the management of GSA’s Advanced Metering Infrastructure. Throughout GSA’s inventory, advanced meters, data aggregators and gateways have been installed to achieve compliance with Section 103 of the Energy Policy Act of 2005 (EPACT), EISA 2007 and other Federal energy Executive Orders. GSA’s advanced metering inventory currently consists of 40 unique devices, over 700 IP enabled devices with 6,643 enabled sources and over 40,000 source measurement pairs. The typical communication protocol is ION and Modbus TCP/IP. Currently, ten (10) regional PME servers collect this data on a 15-minute interval basis, which then rolls up to a National ION EEM application. ION EEM will no longer be supported by Schneider Electric after September 30, 2021. This solution will need to be able to poll metering data for all 40,000+ source/measurement pairs on a 15-minute interval basis.

The building interval data provided by GSA’s advanced metering system, directly supports several PBS strategic initiatives and GSA priorities. Data currently https://www.gsa.gov/cdnstatic/National_Custodial_Spec_Final_121912_version_1.13.pdf exported from the current system is used for many things including virtual building audits, which identifies energy conservation measures and if implemented will improve the load profile of GSA’s owned facilities. Tools like this directly support PBS Productivity priority and most of its initiatives.

Administrative Tools within the current metering platform are currently used to edit metering data, manage inventory, configure hardware, monitor power quality, etc. It is currently an ongoing effort to manage offline meters, repair/replace meters and correct erroneous data. GSA’s metering support team is dependent on tools that can provide meter information at a portfolio level.

In 2015, GSA entered into a financial management shared services agreement with the U.S. Department of Agriculture/Pegasys Financial Services (USDA/PFS) and transferred the Pegasys financial management system, an instance of Momentum Financials®, which serves OCFO and approximately 46 other external customers. USDA/PFS is responsible for processing and paying utility invoices for GSA through a third-party utility bill paying service. Utilities used by GSA customers include water (potable and non-potable), electricity, renewable electricity, geo-thermal, natural gas, Ethanol 85 (E85), propane (LPG), steam, chilled water, #2 and #6 fuel oil, diesel, biodiesel, kerosene, coal, sewer, and trash collections services.

Utility invoices are submitted by each utility vendor electronically and/or in paper form for processing of invoice charges and payments. The current utility invoice processing systems contain data for approximately 800 vendors and 3,700 active utility accounts. The Government estimates it receives approximately 44,400 utility invoices per year. Utility invoices may represent multiple utility meters from multiple locations. Invoices are received daily based on monthly, quarterly, semi-annual and annual services scheduled via email, mail, or fax. The cost and operational management of current utility invoice processing systems continues to increase each year.

C.3 SCOPE

The Contractor will provide a cloud-based or government site-hosted (on premise) COTS enterprise-wide utility management solution and all support for the configuration, implementation, operation, maintenance and performance of the solution. The Contractor will coordinate all technical implementation tasks with Government-designated support teams including server, application, network and/or security teams. This task includes the technical support, changes and architectural expertise to maintain the application in compliance with all existing GSA policies and guidelines. Issues that may be discovered through scan, reviews and audits shall be resolved in the timeframes defined by GSA Policy. The scope of the resulting contract shall include all products and support services required to deploy, host, license, configure, integrate, and support enterprise as well as train end-users.

The Government envisions three (3) stages for this contract:

1) Configuration - covers all activities proposed to deliver an operational solution within the proposed timeline;

2) Implementation - covers deployment of the solution to all users and migration of active projects and data and;

3) Execution - covers operation, maintenance, support, and enhancements of the solution.

At a minimum, “operational” is defined as implementation/configuration of all user stories (Attachment 2), compliance with Federal IT Security requirements, readiness to migrate active data/projects, and readiness to deploy solutions to all users.

C.4 CONTRACTOR SPECIFIC TASKS

C.4.1 ACCEPTABILITY STANDARDS

The solution shall adhere to the following business goals/objectives, technical requirements and execution phase requirements:

C.4.1.1 BUSINESS GOALS/OBJECTIVES

The Government’s primary goal is to acquire and implement an enterprise-wide utility tracking solution that provides for advanced metering, energy and water usage intensity reporting, utility contracting, utility rate intervention, demand response, waste diversion performance, utility billing, processing and account management, and more for all GSA-operated buildings.

General Goals/Objectives

1. Goal: Provide ability to gather, analyze and export Advanced Metering data.

Objectives:

a. Ability to poll metering data for 40,000+ source/measurement pairs on a fifteen (15) minute interval basis.

i. Provide a tool that delivers meter information at a portfolio level.

1. Highly Customizable Load Profile Templates

2. Power Quality Template

3. Data Quality, Data Management, Data Import Function by

End-User

4. Source Node Hierarchies with near real-time meter communication status

5. Access to System Log which should include administration of users

6. Reporting capabilities available for download or scheduled and sent via email. Needed for both internal and external end-users

7. Alarming Capabilities.

8. Tool shall provide the ability to edit meter information, manage inventory, etc.

2. Goal: Provide an administrative tool for end users

a. Objectives:

i. Ability for end users to edit data, manage inventory, and configure hardware.

ii. Ability to access system logs.

iii. Ability to add and delete users, copy dashboards and templates to users, reset passwords, set user permissions for sources and trends, and monitor user activity.

iv. User information should be easy to filter and sort, with the ability to export user reports.

3. Goal: Provide reporting capability

a. Objectives:

i. Scheduled or ad hoc capability.

ii. Ability to download or email reports at regularly scheduled intervals.

iii. Ability to configure reports.

iv. Multiple hierarchies, time period options, comparisons.

v. Ability to handle conversion factors and calculations

4. Goal: Event alarm capability.

a. Objectives:

i. Ability to set alarms for setpoints determined by the end user.

5. Goal: Data Gathering Ability

a. Objectives:

i. Interfaces for end user building, account, and usage/cost data input, editing, and deletion.

ii. Ability to extract data from a variety of different systems and file types, including but not limited to API, text files, Microsoft Excel, Google documents.

iii. Ability to export iframe or other HTML enabled interactive content for external websites.

6. Goal: Energy, Water, Waste Dashboarding

a. Objectives:

i. Strategic dashboard to monitor key performance indicators (KPIs)

ii. Analytical dashboards with drill-downs

iii. Operational dashboards to monitor business processes

7. Goal: Data Sharing

a. Integration with other internal and external IT systems

i. GSA systems, i.e., REXUS, ABP, GBuild, Business Intelligence (BI), GSA Link etc.

ii. Environmental Protection Agency (EPA) Energy Star Portfolio Manager III. Third party vendors via direct integration or open API support (i.e., MetTel)

iv. Weather data (heating and cooling degree days, humidity, ambient temperatures) from National Oceanic and Atmospheric Administration (NOAA) or other similar sources.

8. Goal: Invoice Processing

a. Objectives:

i. Integrated utility invoice processing solution to support OCFO. The solution should provide an invoice file that the government will use to disburse to utility vendors.

ii. Provide utility invoice receipt, processing, storing, and account management services for all customers regardless of invoice formats (i.e., paper, electronic) or mode of receipt (i.e., e-mail, mail, fax). This includes resolving and reconciling billing errors within the same billing cycle.

iii. Provide a monthly accrual file which shall interface with the government’s accounting system for each utility account based on the proration of the last payment amount and account’s performance periods.

C.4.1.2 STAGE GOALS/OBJECTIVES

● Configuration Stage

○ Configure solution to meet all user stories in Attachment 2 and achieve all goals described in this SOO.

○ Configure a solution that provides an outstanding user experience supporting all types of project delivery teams, using agile principles and reliance on GSA subject matter experts (SMEs).

○ Provide hosting, licensing, integration, functionality and support for up to 50 users to allow the configured solution to be fully tested with GSA users and SMEs.

○ Provide initial training and training resources (e.g. videos, tip sheets, user guides)on the core product for GSA team members and up to 50 GSA designated testers. Training shall be provided at GSA Headquarters in Washington, DC and virtually via online meeting software.

○ Deliver user training as needed to GSA team members, SMEs, users, and end user support contractors.

○ Deliver a fully operational solution, defined as delivery of agreed-to user stories, compliance with Federal IT Security requirements, readiness to migrate active data / projects, and readiness to deploy solutions to all end users.

○ Provide ongoing demos, training, and support throughout the agile configuration process to enable the GSA team members and designated testers to fully test the system and configurations. All are expected to be virtual via online meeting software.

● Implementation Stage

○ Successfully deploy the operational solution based on the Government accepted Implementation Plan.

○ Seamlessly migrate active data and/or projects from the legacy systems to the new system.

○ After GSA acceptance of an operational system, the Contractor shall begin live rollout beyond the initial 50 end users.

■ Contractor shall create and maintain an implementation plan.

■ Contractor shall provide a communication plan in their quote to demonstrate how they will communicate with all stakeholders, including the core and extended project team and GSA leadership. Elements to include in the plan: type, form, frequency of communication. In the case of service interruptions, the plan shall indicate response times and update frequencies until resolution.

■ Contractor shall provide a seamless transition of data / projects from the existing solutions to the new solution.

○ Contractor shall provide a training plan and shall develop and provide training materials and technology for internal and external users.

● The Government’s timeline for implementation is:

○ Vendor delivers a FedRAMP Readiness Assessment Review completed by a FedRAMP 3PAO following the FedRAMP Readiness Assessment Guidelines 90 days after award.

○ Vendor complies with security policy to achieve a Limited Authorization to Operate (L-ATO) SaaS for Moderate Impact systems prior to using GSA production data or prior to go live rollout, whichever occurs first. (See Attachment 1a, Section 4, Attachment 1b, Attachment 1d, and Attachment 1e identifying contractor or government responsibilities which are incorporated by reference herein)

○ Vendor obtains all security approvals, including but not limited to FedRAMP authorizations and Agency ATO(s), 12 months after award (See Attachment 1a, Section 5 identifying contractor or government responsibilities which are incorporated by reference herein, and Attachment 1e).

○ Without a FedRAMP authorization within 1 year of contract award;

GSA will not be able to use the product for the option years and will not proceed with exercising the remaining option years (See Attachment 1a, Sections 4 and 5).

● Execution Stage

○ Operate and maintain a high-quality enterprise solution that is responsive to end user feedback and aligns with GSA’s evolving requirements.

○ Contractor shall maintain a fully configured and compliant system throughout the execution phase, including but not limited to hosting, licensing, integration, functionality, and support at full scale.

Contractor shall maintain FedRAMP authorization and GSA ATO.

○ The Contractor shall maintain and update all artifacts created in earlier phases of the contract including but not limited to:

■ Data architecture plan

■ Project plan

■ Technology roadmap

■ Agile artifacts as proposed by the Contractor and approved by GSA.

○ Contractor shall maintain all GSA configurations and integrations through all updates and releases of the underlying solution.

○ Contractor shall provide technical support for GSA IT Service Desk support personnel.

○ Provide Tier 3 help desk support or its equivalent, in collaboration with the existing GSA IT Service Desk.(7:30AM – 7:30PM ET Monday through Friday)

○ Provide the means and metrics to be used to measure the quality and responsiveness of user support and how that data will inform appropriate adaptations in the user support model.

○ The Contractor shall include scripts, support and training to GSA IT Service Desk support personnel. The Contractor shall include resources and training delivery methods made available to GSA and external users to help themselves. These can take the form of user forums, web pages, video instruction, chat sessions and other interactions.

○ The Contractor shall include how the solution will deliver information to GSA users and core team members about new features, upcoming releases, product line changes to the proposed solution, maintenance periods, and outages and other events that will affect GSA users.

C.4.1.3 USER STORIES

The solution shall meet the capabilities identified in Attachment 2 User Stories.

User Stories are organized into the following categories:

● Administration

● Data Management

● Data Inputs

● Reporting/Dashboarding

User stories are prioritized as follows:

● “Mandatory”- the highest priority, critical to the operation of the solution.

● “Highly Desirable” - second highest priority, non-essential to the operation of the solution, but a desired feature to enhance the user experience.

● “Desirable” - lowest priority, optional components that are nice features to have.

The Government has identified evaluation criteria for each user story and will utilize it to define the boundaries of a user story and to confirm when a story is completed and working as intended. Upon award, the Government will work alongside the vendor to fully define the backlog of user stories and the acceptance criteria for user story configuration.

C.4.1.4 TECHNICAL REQUIREMENTS

○ On premise

○ Cloud at their location (FEDRAMP)

● The Contractor shall meet GSA’s security requirements (see Attachments 1a, 1b, 1c, 1d, and 1e):

○ FedRAMP authorization for a moderate system (Cloud)

○ GSA ATO for a moderate system

● The Contractor shall provide a Service Level Agreement (SLA) which shall contain backup, disaster recovery and business continuity services; monitoring and performance processes; metrics to demonstrate compliance such as availability, reliability, responsiveness, and user experience; and reporting mechanisms including issue tracking and reporting processes and resolution timeframes.

○ Available 24 hours a day, 7 days a week, 365 days a year, with tolerances outlined in the SLA and approved by GSA.

○ Provide performance and functionality metrics, specifically, web page views and load times.

○ In the case of service interruptions, the SLA shall indicate response times and update frequencies until resolution.

○ SLAs are metrics that are important to the business line – could be up time, etc

● The Contractor shall conform to GSA IT’s enterprise architecture (see Attachment 1c) as follows:

○ Integrate with GSA’s electronic collaboration solution (currently Google Suite Enterprise)

○ Include a system architecture diagram.

○ Use modern integration solutions so that the proposed solution can easily integrate with other enterprise document management solutions, digital signature solutions, and applications as GSA architecture evolves.

● The Contractor shall provide and maintain a technology roadmap for operating and maintaining the solution throughout the duration of the contract.

○ The Contractor shall propose configurations and solutions that lie within the technology roadmap.

○ The Contractor shall propose and implement configurations and solutions that are operable and maintainable within COTS releases, upgrades, patches, platform updates, bug fixes, and other industry standard software modifications.

○ The Contractor shall propose and implement configurations and solutions that enhance and do not degrade operability, including all integrations.

○ The Contractor shall ensure development technology stack, components, software or frameworks used in solution are up to date. The Contractor shall update, troubleshoot, and correct issues in solution deriving from third party components, frameworks, GSA infrastructure or security updates. The Contractor shall provide a 'software bill of materials' or scan results of the source code to ensure compliance with known component end-of-life dates as requested by the government.

○ The Contractor shall propose and implement configurations and solutions that follow industry best practices and comply with all GSA IT Security Policies and all applicable GSA and NIST standards and guidelines, and other government-wide laws and regulations.

● The Contractor shall be able to exchange data according to industry best practices and in compliance with all Federal guidelines.

● The Contractor shall be able to exchange data with GSA legacy infrastructure (see Attachment 1) and data transfer protocols, including Extract Transform Load (ETL) tools and Application Program Interfaces (APIs).

● The Contractor shall create a data architecture plan based on technical discovery and scope for GSA approval. The Contractor shall maintain and update the data architecture plan throughout the duration of the contract.

○ The Contractor shall include a description of the database technology to be used and the processes employed to manipulate data.

○ The Contractor shall describe security boundaries and interconnects in data architecture plan.

○ The Contractor shall include an expected data model, entity relationship diagram and a data dictionary or equivalent information to permit GSA to maintain GSA's enterprise data model.

○ The data architecture plan shall describe interfaces for sharing structured data with other IT systems.

○ The Contractor shall provide a data schema for data downloads and transfers so GSA can inventory the type, quantity, structure, and relationships of data housed in the solution.

○ The Contractor shall incorporate infrastructure in the data architecture plan that supports common data operations

(e.g., emergency procedures, data imports, data backups, external transfers of data).

● The Contractor shall create and maintain a project plan and schedule. Contractor shall update and submit these deliverables to GSA on a regular schedule, to be approved by GSA.

C.4.1.5 TIMELINE

The Government’s milestones include:

● The Contractor delivers a FedRAMP Readiness Assessment Review completed by a FedRAMP 3PAO following the FedRAMP Readiness Assessment Guidelines no later than 90 days after award.

● The Contractor complies with security policy to achieve a Limited Authorization to Operate (L-ATO) SaaS for Moderate Impact systems prior to using GSA production data or prior to go live rollout, whichever occurs first. (See Attachments 1a, 1b, 1c, 1d and 1e).

● The Contractor obtains all security approvals, including but not limited to L-ATO, FedRAMP authorizations, and Agency ATO(s). If the solution does not hold a FedRAMP authorization, GSA will sponsor the selected vendor/solution through the Agency Authorization process within the FedRAMP framework.

● The Contractor delivers a fully operational solution as defined in Section 3 concurrent with a L-ATO or ATO or within 12 months of award, whichever occurs first.

● The Contractor implements a fully operational solution including roll-out and standup of active projects per the proposed schedule in their performance work statement.

C.4.1.6 EXECUTION REQUIREMENTS

● The Contractor shall maintain a fully configured and compliant system throughout the execution phase, including but not limited to hosting, licensing, integration, functionality, and support at full scale.

● The Contractor shall maintain a FedRAMP authorization and GSA

ATO.

● The Contractor shall maintain and update all artifacts created in earlier phases of the contract including but not limited to:

○ Data architecture plan

○ Project plan

○ Technology roadmap

○ Agile artifacts as proposed by the Contractor and approved by GSA.

● The Contractor shall maintain all GSA configurations and integrations through all updates and releases of the underlying solution.

● The Contractor shall provide technical support for GSA IT Service Desk contractor support personnel.

○ Provide Tier 3 help desk support or its equivalent, in collaboration with the existing GSA IT Service Desk.

(7:30AM – 7:30PM ET Monday through Friday)

● Provide the means and metrics to be used to measure the quality and responsiveness of user support and how that data will inform appropriate adaptations in the user support model.

○ Contractor shall include scripts, support and training to GSA IT Service Desk support personnel. Include resources and training delivery methods made available to GSA and external users to help themselves. These can take the form of user forums, web pages, video instruction, chat sessions and other interactions.

○ Contractor shall include how the solution will deliver information to GSA users and core team members about new features, upcoming releases, product line changes to the proposed solution, maintenance periods, and outages and other events that will affect GSA users.

● Contractor support for this solution shall include the production environment and may include other technical environments required by the Government such as user acceptance testing, training.

C.4.2 AGILE PROGRAM/PROJECT MANAGEMENT METHODOLOGIES

● Contractor shall propose an Agile approach to development and use Agile methods to the extent feasible to deliver an operational solution.

Contractor shall propose methods to monitor the delivery of work using Agile artifacts such as product backlog, iteration backlog, release backlog, iteration planning and review, iteration team meetings, velocity, error detection and management, and reports on earned value and burndown rates. Contractor shall provide a list of proposed artifacts and the frequency of their submission to GSA as part of their Agile Approach narrative in their Performance Work Statement.

● Contractor shall use a Government-designated electronic repository to capture all artifacts and deliver the solution in the agreed-upon timeframe, and per the agreed-to criteria for acceptance. GSA currently uses JIRA.

C.4.3 OPERATIONS AND MAINTENANCE

The Contractor shall fully support GSA’s implementation of the solution, including GSA or GSA-designated power users, trainers, and end users.

C.4.4 FUTURE ENHANCEMENTS

The Contractor shall support potential future enhancements as identified by the Government.

SECTION D – PACKAGING AND MARKING

D.1 PACKAGING

The contractor is responsible for properly protecting all submissions transmitted to the Government.

D.2 MARKING

D.2.1 DELIVERY OR DATA ITEMS

All documentation, reports and other deliverables shall be clearly marked with the project title, the sender, and contract number.

Unless otherwise specified by the Government, the Contractor shall submit all deliverables electronically.

SECTION E – INSPECTION AND ACCEPTANCE

E.1 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB

1998) This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): https://www.acquisition.gov/far/

Clause Number Clause Title Date

52.246-2 Inspection of Supplies (Fixed Price) Aug 1996

52.246-4 Inspection of Services (Fixed-Price) Aug 1996

52.246-6 Inspection of Services May 2001

(Time and Material and Labor Hour)

E.2 INSPECTION AND ACCEPTANCE OF SERVICES

The contractor is expected to ensure proper control and coordination of all deliverables to ensure timely delivery. The Government will review and comment on all deliverables within fifteen (15) business days of receipt, unless otherwise specified. Acceptance or rejection of deliverables shall be made by the COR (after consultation with the PM) in writing, giving the specific reason(s) for the rejection. The Contractor shall correct the rejected deliverable within five (5) business days unless another date is specified by the COR/PM. The Government shall review any resubmissions within ten (10) business days of receipt and accept or reject the resubmission.

Notwithstanding the foregoing, any deliverable requiring acceptance by the Government shall be deemed to be accepted by the Government if no written notice of nonconformity has been received by the Contractor within the acceptance period.

Both the contractor and the Government have responsibilities for providing and ensuring quality services, respectively.

E.3 CONTRACTOR QUALITY MANAGEMENT

The contractor shall identify and implement its approach for providing and ensuring quality by developing a Quality Management Plan (QMP). The QMP shall describe the application of the appropriate methodology (i.e., quality control and/or quality assurance) for accomplishing performance requirements. The QMP shall describe how the appropriate methodology integrates with the Government’s requirements. The contractor shall submit the QMP as part of its technical quote. The contractor shall make appropriate modifications to the QMP (at no additional cost to the Government). The Government has the right to require revisions of the QMP (at no cost to the Government) should the QMP fail to deliver the quality of the services required at any time during performance.

E.4 PERFORMANCE MEASURES

The Contractor is expected to develop Performance measures and metrics that directly correlate to the SOO. The Government will develop and utilize a Quality Assurance Surveillance Plan (QASP) throughout the life of the contract to ensure that the contractor is performing the required services in an acceptable manner.

The Government reserves the right to alter or change the surveillance methods in the QASP at its own discretion. A Performance Based Service Assessment Survey will be used in combination with the QASP to assist the Government in determining acceptable performance levels.

E.5 GOVERNMENT QUALITY ASSURANCE

The Government will perform periodic reviews of the contractor’s performance in accordance with the Government’s QASP. The QASP will be finalized after the award. The Government reserves the right to review services to be provided, including those developed or performed at the contractor's facilities, to determine conformity with performance and technical requirements.

SECTION F – DELIVERIES OR PERFORMANCE

F.1 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): https://www.acquisition.gov/far/

Clause Number Clause Title Date

52.242-15 Stop-Work Order Aug 1989

52.242-17 Government Delay of Work Apr 1984

F.2. PHASE-IN/PHASE-OUT

The Phase-In/Phase-Out process is defined as a smooth transition from one Contractor to another to maintain the program’s integrity required under this and previous agreements. The Contractor shall take all actions necessary to achieve a successful transition from the incumbent Contractors/GSA Staff and to the follow-on Contractors/GSA Staff.

F.2.1. PHASE-IN

This is a new requirement; therefore, phase-in is not required.

F.2.2 PHASE-OUT

The Contractor shall remain fully compliant during the period of time leading up to the contract expiration or termination. The Contractor shall submit to the Government a phase-out plan sixty (60) calendar days before the contract’s completion or termination. The phase-out plan shall address not less than the following:

● Procedures for retaining the staffing levels necessary to maintain required services through the day of the contract’s expiration or termination

● Procedures and responsibilities for performing physical inventory and reconciling and certifying of all Government Furnished Equipment (GFE) and Government Furnished Information (GFI)

● Procedures for reconciling and certifying material and equipment on-hand levels and accuracy.

● Document and define the procedures and responsibilities for turning over all account access to the follow on contractor required to manage and maintain the cloud environment

● Document and define the plan for providing on-the-job, application specific, training for the incoming Contractor personnel

● Provide detailed documentation sufficient to allow the follow-on Contractor to effectively transition into the contract. The following illustrates the types of documentation required. The Government will specify any other types of documentation that may be needed at the start of the phase-out period:

● System operating procedures

● Customized user guides and manuals

● Detailed data mapping

● All business logic and where it resides within the system

(presentation layer, database, etc.)

● All workflow and business process configurations

● All outstanding / in-progress issues

● All underdeveloped requirements

● Latest version of the System Security Plan, if applicable

● Any additional documents developed related to the system

● Providing application and configuration walkthroughs with the incoming Contractor.

● Provide all code for any customizations or add-ons to the underlying solution. Provide code walkthroughs as applicable.

● Providing the hardware/software inventory.

● Facilitating the transition of the cloud environment to incoming Contractor and/or GSA, as determined by the Government.

The Contractor shall coordinate phase-out activities with the incoming Contractor to affect a smooth and orderly transition at the end of the contract period of performance. Specific details regarding the number of days that will be required for Phase-Out activities will be determined by the Government. The Contractors shall provide on-the-job training for the incoming personnel, as needed, except for any mandated training provided by the Government. The Contractors shall remove all Contractor-owned property from the Government spaces or facilities by close of business on the last day of the contract.

F.3 PERIOD OF PERFORMANCE

This is a performance-based contract. The contract consists of a Base Year with provisions for 4 consecutive one year options. The option years will be exercised based on the contractor’s performance. Acceptance of the contractor’s performance will result in a modification to the contract issued by the Contracting Officer.

The resulting contract will consist of one (1) twelve-month base year and four (4) one-year options. The estimated period of performance is as follows:

Base Year: October 15, 2021 – October 14, 2022 Option Year 1: October 15, 2022 – October 14, 2023 Option Year 2: October 15, 2023 – October 14, 2024 Option Year 3: October 15, 2024 – October 14, 2025 Option Year 4: October 15, 2025 – October 14, 2026

F.4 CONTRACT EFFECTIVE PERIOD

The contract is effective from the date of award for a period of one full year from the date of contract award. The effective period can be extended for an additional four (4) years by exercising each of the 4 one year options making the potential total duration of the project a maximum of 5 years.

F.5 CONTRACT DELIVERABLES

The Contractor will produce numerous working deliverables to facilitate the agile project management approach; such deliverables shall be proposed in the Contractor’s Performance Work Statement and amended, as required, over the life of the contract. The Government will participate collaboratively in the creation and revision of these deliverables and will have ultimate approval of these deliverables. The contractor developed PWS shall include all deliverables identified in the table below. All deliverables shall be produced in accordance with PB-ITS software standards as well as GSA security standards (See Attachment 1a).

The contractor developed PWS shall include proposed due dates and update frequency for all required deliverables, leveraging the values and principles of an Agile framework to the maximum extent practicable. In addition to the deliverables listed below, the contractor shall comply with all deliverable requirements mandated by Attachment 1a - GSA IT Security Requirements.

At a minimum, the Contractor developed PWS shall address:

Deliverable Frequency

Test plans Start of each agile sprint

Test reports End of each agile sprint

Service Level Agreement including Hosting and Licensing Agreement, Backup, Business Continuity and Disaster Recovery Plans

Included in contractor developed PWS

Project Plan and Project Schedule Included in contractor developed PWS.

Weekly Status Updates (including Agile artifacts) in a form acceptable to the Government

Weekly

Monthly Status Updates (including Agile artifacts) in a form acceptable to the Government due on the 10th day of each Month

Implementation Plan Included in contractor developed PWS.

Data Architecture plan. Options for integrating contractor system with non-solution IT systems (See Attachment 5 - Data Report shows current, short term and target architecture environment.)

Included in contractor developed PWS

Data Dictionary (or approved substitute) Included in contractor developed PWS

Proof of FedRAMP Authorization Within 12 months of award of the contract

User Support Plan Included in contractor developed PWS

Training Plan Included in contractor developed PWS

Training Materials Included in contractor developed PWS

Quality Management Plan Included in contractor developed PWS

Communication Plan Included in contractor developed PWS

Contractor self-evaluation of performance Annually

Migration Plan Included in contractor developed PWS

Phase-out Plan 60 days prior to contract expiration

The Contractor shall deliver the deliverables specified in the table above (and any additional deliverables that the Contracting Officer may require in writing) on dates specified therein, or on such revised dates as the Contracting Officer may specify. All deliverables expected to be included in the contractor developed PWS (as indicated in the table above) shall also be revised throughout the duration of this contract, as applicable.

All documentation, including, but not limited to, documented processes, procedures, software tools and applications, test materials, text, notes, electronic files, data, new capabilities or modification of existing applications, source code and records generated, modified, acquired or produced by the Contractor under this contract shall become the property of the Government. In accordance with the FAR 52.227-14(b), the Government shall have unlimited rights to all produced materials, including the right to modify, distribute and publish. The Contractor shall deliver electronic copies of all produced materials to the Government quarterly (or as requested) and upon expiration or termination of this contract. The Contractor may mark the deliverables to indicate its authorship, provided, however, that it shall not include any markings inconsistent with the Government’s unlimited rights. The Contractor agrees that the Government may release any deliverable in response to a Freedom of Information Act (FOIA) request, subject to any right to object or to request redactions that the Contractor may otherwise have under the Act or under applicable agency regulations.

All deliverables in printed or other media forms containing personally identifiable information (PII) and/or sensitive but unclassified (SBU) information shall follow applicable policies including General Services Administration Document security for Sensitive But Unclassified Building Information (PBS P 3490.2). The Contractor shall ensure and deliver the application is designed to function in accordance with applicable Federal Information Processing Standards Publication (FIPS PUB) 140-2 and all applicable annexes or subsequently approved federally recognized policy for the protection, operation and/or delivery of Federal information technology systems

F.5 TERM OF CONTRACT

Upon contract award of the base year, the contractor shall perform the services of the contract in accordance with the performance periods stated in F.3 of this section. Deliverables will be in accordance with Section F.5.

F.6 PLACE OF PERFORMANCE

The primary place of performance for this requirement will be at the contractor’s site. Normal business hours are between 7:00am - 5:00pm ET, Monday through Friday, excluding Federal holidays.

SECTION G – CONTRACT ADMINISTRATION DATA

G.1 GENERAL

The Contracting Officer (CO) is the Contractor’s primary point of contact during the performance of the contract. Upon award, the CO may delegate certain functions to the Contracting Officer’s Representative (COR).

G.2 CONTRACT ADMINISTRATION

The administration of this contract will require the maximum coordination between the U.S. General Services Administration (GSA), Office of Public Buildings Information Technology Services (PB-ITS) and the contractor. All contract administration will be affected by the Contracting Officer except as may be re-delegated. In no event will any understanding or agreement, contract modification, change order, or other matter in deviation from the terms of this contract between the contractor and a person other than the Contracting Officer be effective or binding upon the GSA. All such actions shall be formalized by a proper contractual document executed by the Contracting Officer.

G.2.1 CONTRACTING OFFICER (CO)

The CO has the overall responsibility for the administration of this contract. The CO alone, without delegation, is authorized to take actions on behalf of the Government to amend, modify, or deviate from the contract terms, conditions, requirements, specifications, details and/or schedules; make final decisions on disputed deductions from contract payments for nonperformance; terminate the contract for convenience or default; issue final decisions regarding contract questions or matters under dispute. However, the CO may delegate certain other responsibilities to his/her authorized representatives.

The Contracting Officer is Ms. Sharmel Lane unless otherwise stated in writing.

Communications pertaining to contract administration matters will be addressed to the Contracting Officer. Written communications from the contractor shall make reference to the contract number and shall be emailed to the address provided below:

Ms. Sharmel Lane Contracting Officer (CO) Email: sharmel.lane@gsa.gov Telephone: (202) 208-7005

G.2…