RFP Attachment 1 - Statement of Work Rev2.docx

Federal Aviation Administration (FAA)

Strategic Sourcing for the Acquisition of Various Equipment and Supplies (SAVES) and Simplified Purchase Team (SPT)

AAQ-5B0

STATEMENT OF WORK

For Robotic Process Automation May 13, 2021

CHANGE CONTROL LOG

1. Introduction/Background The FAA has a requirement for a Blanket Purchase Agreement (BPA) that will provide Robotic Process Automation (RPA) services to all FAA lines of business, staff offices, regions, and centers across the continental United States.

The contractor will work with FAA Business Units (clients) to develop and implement a Robotic Process Automation (RPA) solution. The solution will consist of “bots” that reduce or replace the need for employees to perform mundane, error-prone tasks such as copy-and-pasting data, analyzing large volumes of data and/or data aggregation. The “bots” will be either “Attended” requiring human intervention and/or “Unattended” without human intervention. The solutions will leverage industry leading, FEDRAMP compliant (or FAA Federal Cloud System (FCS) hosted), software (technology) approved by FAA Information Technology (AIT) and hosted in FCS.

2. Scope of Work RPA services will be required nationwide, on an as-needed basis, in support of specific RPA requirements for all FAA Regional Offices. The BPA will include predetermined pricing for regions to utilize for acquisition procurement. Firm fixed price call orders will be issued under the respective BPA(s). The individual call orders will specify the services to be provided and not every BPA call will require every service listed in this Statement of Work. Although process automation can vary by complexity, the table below should be used as a guideline to estimate the RPA cost per complexity level.

RPA Project Size and Time Frame Estimator Table

3. Requirements

The FAA has implemented a framework for robotic automation that consist of five phases:

1. Select the Process

2. Diagram the Process

3. Diagram the Automation

4. Select a Tool

5. Develop the Automation This framework is based on industry-standard practice and is right-sized for RPA engagements; however, it is also general enough to enable innovative solutions. Each phase has specific goals, deliverables, and expectations. The following sections of this SOW specify which phases the FAA desires to solicit.

Process Selection Task The Contractor shall assist the FAA with evaluating the suitability of process(es) for robotic automation. The Contractor shall define an appropriate evaluation methodology that allows the FAA to determine good candidates for automation, included factors such as, but not limited to, complexity, stability, relative level-of-effort, and potential cost for automation.

The Contractor shall be required, at minimum, to describe the methodology and how it meets the evaluation goals. The Contractor may use some, all, or none of the FAA “RPA Candidate Evaluation Checklist” as part of the evaluation methodology. Access to the Checklist will be made available upon request to the Contracting Officer.

Diagram the Process Task The Contractor shall conduct requirements elicitation to gain a detailed understanding of the “as-is” process(es) that have been selected for automation. The Contractor shall consult any existing process documentation that may be available, as well as any policies or orders that apply to the process.

The Contractor shall model the as-is process using an industry-standard format. The Contractor must use Business Process Modeling Notation (BPMN), unless there is a specific and justifiable reason to use an alternative. The Contractor must get prior approval from the COR before adopting an alternative notation.

The Contractor shall ascertain and document, for each step in the process(es), the name, description, inputs and outputs, potential exceptions, and the data elements that are stored, copied, or referenced by each step.

The Contractor may use the FAA “Process Definition Document” (PDD) Template to meet the documentation requirements of this section, or use another preferred document. However, the chosen document must capture at least the same level of detail or more than the FAA’s Template. The template is available in the RPA Toolkit found at https://my.faa.gov.

Diagram the Automation Task The Contractor shall conduct requirements elicitation to gain a detailed understanding of the FAA’s desired “to-be” state of the entire or subset of process(es) it wishes to automate.

The Contractor shall model the “to-be” process using an industry-standard format. The Contractor shall use Business Process Modeling Notation (BPMN), unless there is a specific and justifiable reason to use an alternative. The Contractor must get prior approval from the COR before adopting an alternative notation.

The Contractor shall ensure that steps to be automated are clearly delineated from those that will be excluded from automation, if any. The reasons for these exclusions and impacts of those exclusions must be documented.

The Contractor shall document known exceptions that may occur during the automation, along with the recommended steps for recovery.

The Contractor shall recommend metrics to the FAA to ensure any automation(s) are performing as expected and that will contribute to demonstrating the value of the automation over time.

The Contractor may use the FAA “Process Definition Document” (PDD) Template to meet the documentation requirements of this section, or another preferred document. However, the chosen document must capture at least the same level of detail or more than the FAA’s Template. The template is available in the RPA Toolkit found at https://my.faa.gov/go/rpa (FAA Network Only).

Select a Tool Task The Contractor shall consult with the FAA to select an RPA product that will meet the automation needs identified in the scope of this initiative. The Contractor shall define an appropriate evaluation methodology that allows the FAA to determine which product should be used; included factors such as, but not limited to, fitness, ease-of-use, and cost.

The products for consideration shall be limited to those previously approved by the FAA and included in the Technology Products List (TPL), which are Blue Prism, UiPath, and Pega Robotics (formerly OpenSpan). The FAA will procure the licenses and provide to the contractor as Government Furnished Equipment.

The Contractor shall ensure that product selection is conducted in accordance with the FAA’s roadmap for implementation of specific product versions. Any deployment to an FAA-hosted environment will be subject to the version installed in that environment as of the planned deployment date.

Develop the Automation The Contractor shall deliver automation(s) that comply with the requirements approved by the FAA. The Contractor shall utilize an iterative development methodology that allows the FAA to examine the validity and accuracy of the requirements, and to respond to the usability and performance of introduced functionality, at regular intervals.

The Contractor shall be aware of and comply with the RPA governance policies and procedures established by the FAA, in addition to the relevant security and privacy policies. Links to the relevant documents can be found in the RPA Toolkit found at https://my.faa.gov.

The Contractor is strongly encouraged to use an FAA-provided development environment. However, the Contractor may use their own development environment with prior approval from the COR, if there is a compelling need to do so.

Regardless of the development environment, the Contractor shall ensure that any Releases are tested and deployed into the FAA-managed test and production environments. The Contractor shall, as early as feasible, advise the FAA of any potential license costs required to execute the automation(s), such as, but not limited to, developer tools, bot runtimes, or Virtual Machine (VM) usage.

The Contractor shall coordinate User Acceptance Testing (UAT) for each Release, and shall support FAA users during UAT. UAT must confirm that the automation is properly installed, configured, and remains in compliance with contractual and functional requirements.

The Contractor shall provide adequate training to ensure end users are adequately prepared to use the automation(s). This training may be in written form, delivered via screen-sharing, or other appropriate means. The Contractor shall ensure that the RPA Platform Administrator is aware of any specific administration requirements related to the delivered automation(s).

The Contractor shall ensure that any automation(s) delivered under this Task are registered in the FAA Bot Registry upon release to Production. In addition, the Contractor shall provide a briefing that specifies any specific runtime requirements or other relevant information necessary for production usage. The Contractor shall ensure the FAA has access to the un-compiled automation before release to Production.

4. Deliverables This section describes 1) the products and tangible end results that are expected from each task contained in the previous section, 2) the date each deliverable is due, and 3) the government acceptance criteria.

All days are business days unless otherwise specified.

Process Definition Document (PDD)

· Video: .mp4 (H.264 encoding)

· Audio: .mp3

· The resolution should be 640 x 360px. The file size should be 60mb or less, with a run time of less than 10 minutes. Less important sequences may be removed to reduce the run time.

image1.png image2.emf