Amendment No. 00003_Attachment 3.1 - Statement of Work.pdf

Request for Proposal No. 693JJ321R000013

Attachment No. 3.1 ‐ eDelivery Statement of Work

Amendment No. 00003

Date: July 9, 2021

C.1 INTRODUCTION

This statement of work describes the software requirements and non‐personal services necessary to deliver a comprehensive web‐based and mobile eDelivery construction management system that fully integrates all aspects of Federal Highway Administration (FHWA), Office of Federal Lands Highway (FLH)

Division’s program construction activities, including: cost estimating (engineer’s estimate), procurement, electronic bidding (ebidding), construction management, construction document management, and

Contractor payments and acceptance of the project.

C.2 BACKGROUND

The Office of Federal Lands Highway (FLH) is a part of the Federal Highway Administration (FHWA), an agency within the U.S. Department of Transportation. FLH provides transportation expertise and engineering including delivering projects that support more than 500,000 miles of roadway, comprising over 8500 bridges, over 35,000 trails, and over 400 transit systems for federally owned transportation facilities open to the public which serve Federal lands. FLH is distinctive in FHWA as we directly deliver projects similar to the State DOTs and Local Public Agencies.

FLH provides planning, design, procurement, and construction engineering services primarily to Federal

Land Managing Agencies (FLMA) such as the National Park Service (NPS); USDA Forest Service (Forest

Service); U.S. Fish and Wildlife Service (USFWS); Bureau of Indian Affairs (BIA) and Tribal Governments;

Bureau of Land Management (BLM); Department of Defense (DOD); U.S. Army Corps of Engineers

(USACE); and the Bureau of Reclamation (BOR). FLH’s project delivery work also includes managing and contracting professional services and construction services. In FY19 our National project delivery resulted in approximately:

$341M advertised construction contracts value

$353M awarded construction contract value

$1.195B active construction contract value

255 active construction contracts

103 completed construction contracts

131 construction projects advertised

FLH is headquartered in Washington, DC, with Division offices in Lakewood, Colorado; Ashburn, Virginia;

and Vancouver, Washington.

Each Division has numerous field offices responsible for the administration of highway construction projects. These small, temporary offices can be located in remote parts of the U. S. and its territories.

FLH is comprised of approximately 700 employees of whom 96% are located in the Division offices.

Annually FLH had approximately 500 active projects across all three Divisions within the Design, Acquisition, and Construction phases. The projects are similar to projects delivered by State

Departments of Transportation. The projects can be categorized as heavy civil transportation construction contracts that are primarily comprised of roadway and bridge construction.

Additional information about the Federal Lands Division can be found at https://highways.dot.gov/federal‐lands

C.3 OBJECTIVES

The primary objective of this contract is to replace FLH’s existing construction management systems, and add additional capabilities, with a single comprehensive web‐based and mobile eDelivery system.

FLH’s objectives for this contract include:

1. Enable FLH project staff to make offline mobile updates at project locations;

2. Improve the capability and efficiency for FLH staff to capture project documentation in the design, procurement and management phases of construction projects;

3. Replace the existing roadway cost estimating system;

4. Add eBidding capabilities; and

5. Add construction document management including managed workflows.

C.4 SCOPE OF REQUIREMENT

The Contractor shall provide all the necessary products and services to deliver a single comprehensive web‐based and mobile eDelivery construction management system. The Contractor’s eDelivery solution must fully integrate with all aspects of FLH’s program construction activities, including cost estimating

(engineer’s estimate), procurement, electronic bidding (ebidding), construction management, construction document management, and final Contractor payment and acceptance of projects. The

Contractor shall implement and configure its eDelivery system to meet all the necessary requirements outlined in SOW Attachment No. 1 – eDelivery System Requirements.

The Contractor shall provide all the necessary operations and maintenance services to ensure that its eDelivery system is continually available, secure and has all the necessary functionality to meet the objectives and requirements of this contract. The Contractor shall provide all of the necessary professional services to manage and oversee the requirements for the entire life of the contract.

C.5 SYSTEM REQUIREMENTS

The eDelivery system shall consistently and efficiently track project activities through the design, acquisition and construction phases of the project lifecycle, and provide document management during the construction phase. The system must at least contain four (4) modules that include a design module, acquisition and eBidding module, construction module, and a document management module.

The system will also include other requirements that are overarching or ancillary to those requirements in the four (4) primary eDelivery modules. The high‐level needs and detailed system requirements for

FHWA’s eDelivery system are provided in SOW Attachment No. 1 – eDelivery System Requirements.

C.6 SYSTEM USERS

Users of the eDelivery system are further described in the C.6.1 sub‐sections below.

C.6.1 INTERNAL SYSTEM USERS

Federal employees (approximately 500 active users) o System Administrators that manage administrative functions of the system and access to the program and data.

o Module Administrators that have elevated rights in a specific module of the system.

o Design Engineers and Technical Specialists that create estimates for roadway projects.

o Acquisition personnel that produce contract and e‐bidding documents and facilitate the e‐ bidding process.

o Construction personnel that track roadway projects, Contractor progress, and progress payments during construction.

o Data Administrators that will access data for specific reporting purposes.

Contract employees (approximately 50 users) o Service Desk Employees that control access to the program and data.

o Procurement personnel that produce contract documents and enter bid data received from

Contractor bidders.

o Construction personnel that track roadway projects, Contractor progress, and progress payments.

C.6.2 EXTERNAL SYSTEM USERS

Architecture and Engineering (A/E) Consultants (approximately 200 active users) o Design engineers that create estimates for roadway projects during the preliminary engineering phase prior to construction.

o Contract Inspectors and Contract Project Engineers that track roadway projects, contractor progress, and progress payments during construction.

Prospective Bidders (approximately 250) o Review Solicitation and prepare/submit electronic bids

Construction Contractors (approximately 350 users) o For preparation of pay notes, invoices, submittals, Requests for Information (RFIs), and tracking work during construction.

Approximately 600 maximum concurrent logins are anticipated. Typical concurrent logins are expected to be 100 to 400. Additional users are expected to use the mobile construction module offline.

C.7 STATEMENT OF WORK TASK AREAS

C.7.1 PROJECT MANAGEMENT

The Contractor shall provide all the necessary project management services to meet the requirements of this contract and to ensure the successful implementation, operation and maintenance of the eDelivery system. Project management services are required throughout the duration of this contract.

In addition, the Contractor shall provide the following project management services delineated by the sub‐tasks below.

C.7.1.1 COORDINATE A PROJECT KICK‐OFF MEETING

The Contractor shall schedule, coordinate, and host a Project kick‐off meeting at the location approved by the Government. The meeting will provide an introduction between the Contractor’s personnel and

Government’s personnel who will be involved with the contract. At a minimum, the attendees shall include Key Contractor Personnel, representatives from the FLH, other relevant Government personnel, and the FHWA COR.

At least three business days prior to the Kick‐Off Meeting, the Contractor shall provide a kick‐off meeting agenda for review and approval by the FHWA COR prior to finalizing. The agenda shall include, at a minimum, the following topics/deliverables:

a. Points of Contact (POCs) for all parties;

b. Personnel discussion (i.e., roles and responsibilities and lines of communication between

Contractor and Government);

c. Draft Project Management Plan (PMP), including draft implementation and configuration schedule, tasks, etc.;

d. Security discussion and requirements (i.e., FEDRAMP and/or ATO status, Government issued badges, PIV Cards, and mobile devices, if necessary); and

e. Invoicing considerations.

The Government will provide the Contractor with the number of Government participants for the Kick‐

Off Meeting and the Contractor shall provide sufficient copies of the presentation for all present.

The Contractor shall draft and provide a kick‐off meeting minutes report documenting the Kick‐Off

Meeting discussion and capturing any action items.

C.7.1.2 PROJECT MANAGEMENT PLAN (PMP)

The Contractor shall document and prepare a PMP covering all facets of its implementation and configuration of the eDelivery system. The Contractor shall provide the Government with a draft PMP for Government review and comments. The final PMP shall incorporate the Government’s comments.

The PMP shall include, but is not limited to the following elements:

a. Describe the proposed management approach.

b. Include milestones, tasks, and subtasks required in this TO.

c. Describe in detail the Contractor’s approach to risk management under this TO.

d. Describe in detail the Contractor’s approach to enterprise communications, including processes, procedures, communication approach, and other rules of engagement between the

Contractor, FHWA COR and other FHWA personnel. The PMP is an evolutionary document that shall be updated annually at a minimum.

The PMP is considered a living document, and periodic updates and revisions to the PMP may be requested by the Government during the implementation of the eDelivery system.

C.7.1.3 PREPARE A MONTHLY STATUS REPORT (MSR)

The Contractor shall develop and provide an MSR. The MSR shall include the following:

a. Activities during reporting period, by task (include on‐going activities, new activities, and activities completed, and progress to date on all above‐mentioned activities). Each section shall start with a brief description of the task.

b. Problems and corrective actions taken. Also, include issues or concerns and proposed resolutions to address them.

c. Government actions required for the Contractor to execute specific tasks. Net results of Government action or inaction.

d. Schedule (show major tasks and projects, milestones, and deliverables; planned and actual start and completion dates for each).

C.7.1.4 BI‐WEEKLY IMPLEMENTATION MEETINGS

The Contractor Project Manager shall convene a bi‐weekly (every two weeks) or more frequent eDelivery implementation technical status meeting with the FHWA COR and other FHWA stakeholders.

The purpose of this meeting is to ensure all stakeholders are informed of the current activities and provide opportunities to identify other activities and establish priorities, and coordinate resolution of identified problems or opportunities. The Contractor PM shall provide a pre‐meeting agenda and post‐ meeting minutes, including: attendance, issues discussed, decisions made, and action items assigned, to the FHWA COR within five workdays following the meeting.

C.7.2 SYSTEM IMPLEMENTATION AND CONFIGURATION

C.7.2.1 SYSTEM CONFIGURATION

The Contractor will be responsible for initial software configuration based upon the Government’s requirements in preparation for initial user testing. The Contractor will apply the documented and approved configuration changes to the eDelivery solution. The configuration activities will include, but are not be limited to, the following:

a. Creating and configuring user and role permissions;

b. Configuring business rules/workflows;

c. Configuring the additional fields required by the Government;

d. Ensuring mobile app compatibility and offline accessibility;

e. Configuring the PIV card login and PIV exemption for ‘.GOV’ users;

f. Configuring the access requirements for external, Contractor, or ‘non‐.GOV’ users;

g. Configuring reports and creating additional reports, as needed;

h. Drafting /creating screen layouts and menu designs;

i. Testing of the software for functionality;

j. Assisting the Government with other aspects of software testing; and

k. Providing a system architecture document.

C.7.2.2 DATA MIGRATION

The Government will work with the Contractor to identify data migration requirements and the methods to be used to extract all the necessary data from existing systems and the process for migrating the data to the new system. The Contractor shall map all data to software’s data structure. The Contractor will produce data migration requirements in a data migration plan. The data migration plan shall be reviewed and approved by the FHWA COR. The Contractor will work with the Government to map historical information to the software’s data structure without damaging the integrity or stability of the software or data. Details on the data that needs to be imported are provided in SOW Attachment No. 1, Section 7. Most types of data will need to be imported multiple times. The type of data migration content will include, but is not limited to:

a. Master Pay Item Lists;

b. FLH Bid History and General Project Information; and

c. Construction Project Status from three different systems.

C.7.2.3 DATA GAP ANALYSIS

The Contractor will conduct a fit‐gap analysis to determine what configuration functionality best meets the Government’s requirements and define the gaps/conflicts between the Government’s requirements and the standard eDelivery solution capabilities. Each identified gap will have a Contractor recommendation to mitigate or enhance its standard eDelivery solution. The Contractor will provide a full data gap analysis report including their recommendations to the Government. For each configuration area identified in the data gap analysis report, the Contractor will highlight the existing configuration(s), potential conflicts, and recommended configuration changes/additions. The

Government will review proposed baseline configurations.

C.7.2.4 PRODUCTION

The Contractor will initiate the production support process. The Contractor will provide hosting and operational support services including setup, database administration, systems administration, customer training and help desk support of the eDelivery solution. The Contractor shall provide support services that include but are not limited to: new versions and service packs, technical and release bulletins, access to customer support and issue management services (registration, e‐mail, chat, phone, FAQs, documentation, and customer portal websites). A sign off document on the final acceptance will be agreed upon by the government. The cutover to the Go Live release date will be based on successful implementation of the system in the agreed environments and upon successful user acceptance testing of the system and all interfaces. The system Go Live Successful testing entails that the system performs as per the agreed requirements. The final Go Live Date will be mutually set by the Contractor and the

FHWA COR; however, the Go Live Date must happen by no later than 18‐months from the date of contract award. The Contractor will provide two instances of the system, one will be a Testing/Sandbox instance and the other will be the Production instance.

C.7.3 OPERATIONS AND MAINTENANCE

The Contractor shall maintain the hosting equipment, keep the system current, and maintain system integrity, functionality, and provide high quality service to the users. At a minimum, the Contractor shall perform the following system updates and installation activities:

a. Update system software as revisions are due or new software is required;

b. Update physical layout diagrams using agency approved modeling tool(s) detailing equipment and location;

c. Update system documentation, including installation configurations for each host location; and

d. Update Installation documentation for each location;

e. Allow system scanning as required by the Government.

The Contractor shall respond to identified vulnerabilities and apply appropriate protection. The

Contractor shall monitor the global incidence of malicious software and promptly respond to any incidents with the potential to impact systems.

C.7.4 TRAINING

The Contractor shall provide all the necessary training to ensure that the users of the eDelivery system have all the necessary knowledge and materials to properly use the system. Live course session dates and times will be coordinated with the Government's COR, and may be recorded and used for

Government training activities in the future.

The Government retains the right to copy, modify, and distribute the electronic and paper copies of all documents or portions thereof created for or delivered with the system for the training of internal users, external partners, or any other use the Government deems appropriate. The Government will be posting the training documents on their public web site for internal and external users to download. For live virtual instructor led trainings, the Contractor shall provide a virtual training platform such as:

GoToMeeting, WebEx, Teams, or another meeting platform as approved by the FHWA COR. The

Contractor shall provide onsite training if the Government determines that it is necessary.

Additional details regarding training requirements under this contract are delineated in the sub‐sections below.

C.7.4.1 TRAINING PLAN

The Contractor shall develop a training plan that details the Contractor’s approach and strategy for ensuring that all users are properly trained. The training plan shall include, but is not limited to, the following elements:

a. Provide a training plan that incorporates training options for each course identified in SOW

Section C.7.4.2 – C.7.4.5;

b. Provide a training schedule that aligns with the eDelivery implementation schedule;

c. Provide detailed information on how companies submitting a bid for a project listed in the eBidding module will be trained;

d. Provide training user guides that incorporate the specific system customizations and configurations developed for FLH. The Contractor shall provide draft and final training and user guide documents for the Government’s review, comment, and approval; and

e. Provide draft and final outlines for On Demand Video Training for the COR’s review, comment, and approval.

C.7.4.2 TRAINING FOR USER ACCEPTABILITY TESTERS

During the system implementation and testing, the Contractor shall provide training for Government users who will be testing the system. The Contractor shall provide the training in Testing/Sandbox eDelivery instance. The Contractor shall conduct training for FLH user acceptability testers when each module or section becomes available for testing. Additional Testers shall be trained, as determined by the Government. Testers will represent all the different disciplines that will use the system. The number of testers needed will be determined by the Government. Most of the Government Testers will attend the training for all the modules or sections. Some of the Testers may only need to attend one or two of the courses. Part of the Government implementation testing will include testing the web based and on demand training options and reviewing the training materials provided by the vendor. Before general training begins, the Government will determine if all, part, or none of the initial training data is to remain in the Training/Sandbox instance of the system.

Table C.7.4.2 – Training for User Acceptability Testers

Training Topic Delivery Format Number of Classes

Administrator Training Live/Virtual ‐ Instructor Led 2

Design Module Training Live/Virtual ‐ Instructor Led 2 to 4

Acquisitions and eBidding Module Live/Virtual ‐ Instructor Led 2

Construction Module ‐ Main Live/Virtual ‐ Instructor Led 2 to 4

Construction Module ‐ Mobile Live/Virtual ‐ Instructor 2 to 4

Construction Document Management Module Live/Virtual ‐ Instructor Led 2 to 4

Report Development Live/Virtual ‐ Instructor Led 1 to 3

Database Administrator download or access Live/Virtual ‐ Instructor Led 1

C.7.4.3 TRAINING SPECIFIC TO EACH SYSTEM MODULE

The Contractor shall provide user training for each module in the system. The timing of the training will be coordinated between the Contractor and the FHWA COR. Also, the Contractor shall provide FLH specific On Demand Video training for each of the modules listed below. In addition, the following information is provided regarding training sessions:

Table C.7.4.3 – Module Specific Trainings

Design Module ‐ 200+ Students Live/Virtual ‐ Instructor Led 4 to 8

Construction Main and Document Management Module – 300+ Students

Live/Virtual ‐ Instructor Led 5 to 10

Construction – Mobile 250+ Students Live/Virtual ‐ Instructor 5 to 10

Acquisition and eBidding Module 15 to 30 Students Live/Virtual ‐ Instructor Led 2

On Demand Video Training for Each Module List above

Pre‐recorded Video N/A

C.7.4.4 BIDDER TRAINING

In addition to the training listed for the other modules the contractor must provide training to bidders on how to use the eBidding portion of the system.

C.7.4.5 SPECIALIZED TRAINING

The Contractor shall provide the following specialized live instructor led specific trainings:

Table C.7.4.5 – Specialized Trainings

FLH Help Desk (creating and maintaining User accounts)

Live ‐ Instructor Led 2 to 3

System Administrator Users Training Live ‐ Instructor Led 2 to 4

Customized Reporting Training Live ‐ Instructor Led 2 to 4

FLH Database Administrator Training Live ‐ Instructor Led 2

C.8 SCHEDULE OF DELIVERABLES

The Contractor shall submit electronic copies of document deliverables to the CO and COR (and others as specified by the CO or COR) via e‐mail. All document deliverables shall be made by close of business (COB) 4:30pm EST Monday through Friday, unless stated otherwise. Deliverables are due the next Government workday if the due date falls on a holiday or weekend.

Table C.8 – Schedule of Deliverables

SOW

Reference Contract

Deliverable Due Date Format 508 Compliance

C.4 Fully functional eDelivery system in accordance with the requirements of this SOW

Up to 18 months after contract award

Web based system with an offline mobile component

Yes

C.7.1.1 Draft Kick‐Off Meeting Agenda Due 3 business days before

Kick‐Off Meeting

Electronic 2010 or higher MS

Word, Excel, PP, or PDF.

Yes

C.7.1.1 Final Kick‐Off Meeting Agenda Due on the Scheduled date of the kick‐off meeting MS Word Yes

C.7.1.2 Draft PMP 30‐calendar days after contract award

MS Word

Yes

C.7.1.2 Final PMP 5‐business days after receipt of final Government comments

C.7.1.3 Monthly Status Report 15th day of every month

C.7.1.4 Bi‐weekly Implementation Meetings

Every other Wednesday or on a day and time agreed to by the

Government and contractor.

Virtual Meeting

C.7.2.2 Data Migration Plan 60‐calendar days after contract

C.7.2.3 Data Gap Analysis Report 30‐business days from initiation

C.7.2.4 Sign Off Form for Final Acceptance of Production

Offers proposed schedule, but not to exceed 18 months from the date of contract award

PDF Signed Form N/A

C.7.4.1 Draft Training Plan 90‐calendar days after contract

C.7.4.1 Final Training Plan 5‐business days after receipt of final Government comments

C.10 List of FedRAMP Security Certification for proposed hosting environment

Submit with proposal

MS Word, Acrobat, or other as approved

No

C.9 REQUIREMENTS FOR IMPLEMENTING SECTION 508

STANDARDS

NOTE: The following applies to all FHWA contracts and assistance agreements containing Information and Communication Technology (ICT) as a deliverable.

In addition to the work requirements specified in this statement of work, the Contractor shall ensure that all ICT deliverables meet the requirements of Section 508 of the Rehabilitation Act and the ICT Final

Standards and Guidelines (508 Refresh) at 36 CFR Part 1194.

As defined in the 508 Refresh, at 36 CFR Part 1194, Appendix A, E103.4, ICT is “Information technology and other equipment, systems, technologies, or processes, for which the principal function is the creation, manipulation, storage, display, receipt, or transmission of electronic data and information, as well as any associated content. Examples of ICT include, but are not limited to: computers and peripheral equipment; information kiosks and transaction machines; telecommunications equipment;

customer premises equipment; multifunction office machines; software; applications; Web sites; videos;

and, electronic documents.”

Section 508 requires that all electronic products prepared for the Federal Government be accessible to persons with disabilities, including those with vision, hearing, cognitive, and mobility impairments.

Applicable Standards:

Appendix A to Part 1194 – Section 508 of the Rehabilitation Act: Application and Scoping Requirements

Appendix B to Part 1194 – Section 255 of the Communications Act: Application and Scoping Requirements

Appendix C to Part 1194 – Functional Performance Criteria and Technical Requirements

Section 508 Refresh standards are available at https://www.access‐board.gov/guidelines‐and‐ standards/communications‐and‐it/about‐the‐ict‐refresh.

The Contractor shall adhere to the terms and requirements in FHWA Form 4260 Section 508 Information and Communication Technology (ICT) Conformance Criteria for Section 508 conformance. The

Conformance Criteria document does not need to be completed when submitting a deliverable.

C.10 FEDRAMP APPROVAL AND AUTHORITY TO OPERATE

The system shall obtain a Federal Authority to Operate before it can be accepted. The contractor shall meet all requirements found in FEDERAL INFORMATION TECHNOLOGY SYSTEMS SECURITY

REQUIREMENT (FedRAMP) FOR UNCLASSIFIED CLOUD CONTRACT (SEP 2016).

C.11 SECURITY REQUIREMENTS

The Contractor shall be responsible for the following privacy and security safeguards:

a. If new or unanticipated threats or hazards are discovered by either the Government or the

Contractor, or if existing safeguards have ceased to function, the discoverer shall immediately bring the situation to the attention of the other party.

b. The Government has the right to perform manual or automated audits, scans, reviews, or other inspections of the vendor's IT environment being used to provide or facilitate services for the

Government.

c. The Contractor shall not publish or disclose in any manner, without the Contracting Officer's written consent, the details of any safeguards either designed or developed by the Contractor under this Order or otherwise provided by the Government. Exception – Disclosure to a

Consumer Agency for purposes of C&A verification. Contractor under this Order or otherwise provided by the Government. Exception – Disclosure to a Consumer Agency for purposes of C&A verification.

d. To the extent required to carry out a program of inspection to safeguard against threats and hazards to the security, integrity, and confidentiality of Government data, the Order shall afford the Government access to the Contractor's facilities, installations, technical capabilities, operations, documentation, records, and databases within 72 hours.

e. The program of inspection shall include, but is not limited to:

i. Authenticated and unauthenticated operating system/network vulnerability scans;

ii. Authenticated and unauthenticated web application vulnerability scans;

iii. Authenticated and unauthenticated database application vulnerability scans;

iv. Automated scans can be performed by Government personnel, or agents acting on behalf of the Government, using Government operated equipment; and

v. Government specified tools.

f. If new or unanticipated threats or hazards are discovered by either the Government or the

Contractor, or if existing safeguards have ceased to function, the discoverer shall immediately bring the situation to the attention of the other party. If the Contractor chooses to run its own automated scans or audits, results from these scans may, at the Government's discretion, be accepted in lieu of Government performed vulnerability scans. In these cases, scanning tools and their configuration shall be approved by the Government. In addition, the results of

Contractor conducted scans shall be provided, in full, to the Government.

C.12 SENSITIVE INFORMATION STORAGE

Controlled Unclassified Information (CUI), data, and/or equipment shall only be disclosed to authorize personnel on a Need‐To‐Know basis. The Contractor shall ensure that appropriate administrative, technical, and physical safeguards are established to ensure the security and confidentiality of this information, data, and/or equipment is properly protected. When no longer required, this information, data, and/or equipment shall be returned to Government control, destroyed, or held until otherwise directed. Destruction of items shall be accomplished by following NIST Special Publication 800‐88, Guidelines for Media Sanitization.

The disposition of all data shall be at the written direction of the COR, this may include documents returned to Government control; destroyed; or held as specified until otherwise directed.

C.13 PROTECTION OF INFORMATION

The Government shall retain unrestricted rights to Government data. The ordering activity retains ownership of any user created/loaded data and applications hosted on vendor's infrastructure, as well as maintains the right to request full copies of these at any time.

Government data loaded into or processed by the cloud services shall be protected against unauthorized access, disclosure or modification, theft, or destruction.

The data must be available to the Government upon request within one business day or within the timeframe specified otherwise and shall not be used for any other purpose other than that specified herein. The Contractor shall provide requested data at no additional cost to the Government.

No data shall be released by the Contractor without the consent of the Government in writing.

All requests for release must be submitted in writing to the COR/CO.

C.14 DISCLOSURE OF INFORMATION

Any information made available to the Contractor by the Government shall be used only for the purpose of carrying out the terms and conditions of this contract and shall not be divulged or made known in any manner to any persons except as may be necessary in the performance of the contract. In performance of this Order, the Contractor assumes responsibility for protection of the confidentiality of Government records and shall ensure that all work performed by its Subcontractors shall be under the supervision of‐ the Contractor or the Contractor's responsible employees. Each officer or employee of the Contractor or any of its subcontractors to whom any Government record may be made available or disclosed shall be notified in writing by the Contractor that information disclosed to such officer or employee can be used only for that purpose and to the extent authorized herein. Further disclosure of any such information, by any means, for a purpose or to an extent unauthorized herein, may subject the offender to criminal sanctions imposed by 18 U.S.C. §§ 1030.

C.15 AUDIT, INSPECTION, AND ACCESS

The Contractor shall respond to Government requests for documentation and/or access to the

Contractor facilities for any lawful government purpose to include oversight, audit, and inspection within a reasonable period of notification from the Government not less than two (2) business days unless otherwise negotiated as specific terms within the governing contract. The Contractor shall provide access and documentation without requirement for separate or additional non‐disclosure. The

Government commits to the Contractor that information provided by the Contractor shall be retained no longer than required by law or applicable Department/ Agency policy, shall be appropriately protected while within the Government's possession, and shall be destroyed in accordance with Federal requirements for the destruction of sensitive information and media when no longer required.

C.16 PERIODS OF PERFORMANCE

The total period of performance, inclusive of all option periods, is ten years. The contract periods are further broken‐down below:

‐ Base Period: 24‐months

‐ Option Period I: 24‐months

‐ Option Period II: 24‐months

‐ Option Period III: 24‐months

‐ Option Period IV: 24‐months

C.17 PLACE OF PERFORMANCE

The primary place of performance is the Contractor’s own facilities.

C.18 GOVERNMENT FURNISHED EQUIPMENT

The Government will not provide any furnished equipment for the performance of the requirements in this SOW.

C.19 GOVERNMENT FURNISHED INFORMATION

The Government furnished information provided for the performance of the requirements in this SOW are detailed in SOW Exhibit No. 1 ‐ Workflow Diagrams, Example Reports, System‐wide Queries, Progress Payment Summary Dashboard View, and Account Data Tracked.

C.20 ATTACHMENTS/EXHIBITS LIST

The following list of attachments and exhibits are provided with the SOW:

a. SOW Attachment No. 1 – eDelivery System Requirements; and

b. SOW Exhibit No. 1 – Workflow Diagrams, Example Reports, System‐wide Queries, Progress

Payment Summary Dashboard View, and Account Data Tracked.