Attachment J-10_ETSNext Demonstration Scenariosdated 2023-11-09.docx

U.S. General Services Administration

47QMCB23R0011

Attachment J-10 ETSNext Demonstration Scenarios

November 9, 2023 *All changes are reflected in red*

Revision Log

Table of Contents

Overview This document outlines the demonstration scenarios and requirements/tasks to be completed in the nine required scenarios as part of Volume 6, Element 1 from Section L. The scenarios are intended to highlight requirements in Attachment J-3 Requirements Traceability Matrix (RTM) and business processes outlined in Attachment J-12.1-6 Service Blueprints. Only requirements designated “At Evaluation” are included as required tasks in the demonstration scenarios.

Configuration and Set-Up Guidance There will be a separate document provided as an amendment to the RFP that includes specific guidance and sample data needed to support the scenarios during the demonstration. The information required to set up the demonstration will be provided not later than November 9, 2023. This document will include the following information for a notional Federal agency:

1. Organizational information

2. Agency’s travel policy parameters

3. TMC guidance for services, GDS integration, and real-time availability

4. User profiles, attributes, and workflow settings

5. Lines of accounting

6. Payment types, including the use of CBA and IBA payments

7. Travel locations/cities* scenario demonstrations

8. A subset of pre-selected FedRoom properties for each designated test city

9. Other trip parameters including departure/return dates, car rental, airline, hotel, and per diem settings.

* A sampling of domestic and foreign cities will be provided in the forthcoming vendor configuration and set-up guidance for vendors to set up prior to the demonstrations. Solutions should be set up to support each of the travel locations. However, the specific travel locations for each scenario will be provided to the vendor on the day of demonstration.

Demonstration Requirements

1. Provide an overview of how the proposed travel and expense (T&E) solution was set up and configured for the demonstration.

2. Integrate with a Travel Management Company (TMC) and/or Global Distribution System (GDS) of the vendor’s choosing to demonstrate live transactions and data. The TMC will be expected to access GSA city-pair fares, government car rental rates, and government lodging rates. GSA will provide the selected FedRoom properties to load for the demonstration.

3. Provide output in CSV, XLS, JSON or XML format using data generated during the demonstration.

4. Compliance with Section 508 is included in the Requirement Traceability Matrix as an At Evaluation requirement (TE-04). During the demonstration, the government will observe how the solution ensures WCAG 2.1 Level A and Level AA success criteria including:

a. Color is not used as the only visual means of conveying information. (1.4.1-color-meaning)

b. The purpose of each link can be determined. (2.4.4-link-purpose)

c. Each visual form label is sufficiently descriptive. (2.4.6-label-descriptive)

d. A visible indication of focus is provided. (2.4.7-focus-visible)

e. Items in error are identified in text and sufficiently described to the user. (3.3.1-error-identification)

f. Visual labels or instructions are provided for form elements. (3.3.2-label-provided)

g. Suggestion for corrected input is provided about how to correct errors for form fields. (3.3.3-error-suggestion) Additional Considerations

1. Pace the demonstration to allow the government to take notes as each screen is presented. Be mindful of the timing for each scenario and the desire for government participants to assess the features being presented. The government will have the option to ask clarifying questions after each scenario.

2. During the demonstration, indicate what features are “out of the box”, customizations, or not possible with the solution.

3. Include comments on any best practice considerations related to this demonstration given ETSNext’s needs.

Demonstration Scenarios Demonstrate the proposed solution for ETSNext travel and expense for the following scenarios:

SCENARIO 1: DOMESTIC TRIP

User Roles: Traveler, Funds Certifier, Reviewer, Supervisor, Administrator

Objective: Demonstrate the proposed solution highlighting key requirements identified in the Service Blueprints and Requirements Traceability Matrix for completing a Domestic Trip.

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

The order of tasks may be modified from the order listed, if necessary. The government may ask clarification questions at the end of each phase of the demonstration.

PROFILE

Requirements to be Demonstrated:

PR-04, PR-07, PR-09, PR-10, PR-20, PR-21, PR-26

Demonstrate how your proposed solution will do the following:

1.1. Allow a traveler to see the information in their travel profile, including:

1.1.1. Unique ID

1.1.2. Personnel name, title, organization and contact info

1.1.3. Traveler type (e.g., regular, VIP, invitational, virtual, contractor)

1.1.4. Assigned travel arranger

1.1.5. Authorizing/approving official(s)

1.1.6. Certifying officer

1.1.7. Employee type

1.1.8. Charge card information (IBA)

1.1.9. Traveler loyalty programs

1.1.10. Lines of accounting

1.1.11. Traveler preferences (e.g., air, hotel, car)

1.2. Allow a traveler to edit their profile (e.g., add loyalty program info)

1.3. Allow an administrator to track the history of changes to the profile

Pause for any clarification questions from the government.

RESERVATION

Requirements to be Demonstrated:

RE-01, RE-02, RE-06 – RE-08, RE-13,

RE-19 – RE-22, RE-34, RE-36, RE-38,

RE-44 – RE-49, RE-51, RE-58, RE-65, RE-66, RE-72, RE-73, RE-83, RE-84, RE-86,

RE-89 – RE-96, RE-98 – RE-101, RE-103,

RE-113 – RE-116

Demonstrate how your proposed solution will do the following:

1.4. Allow a traveler to search for airline trip options and book a flight

1.4.1. Show how travelers would identify policy-compliant options in search results (e.g., CPP, discounted government fares)

1.4.2. Show how travelers would see whether a fare is refundable or non-refundable in search results

1.4.3. Show how search results appear to travelers when their agency has opted to:

1.4.3.1. Hide certain carriers, airports, or fare classes

1.4.3.2. Display CPP fares first

1.4.3.3. Hide YCA CPP fares when a _CA fare is available

1.4.3.4. Display discounted government (non-CPP) fares last

1.4.3.5. Define a threshold higher than the lowest available CPP fare

1.4.4. Show how travelers are alerted when they select a non-policy-compliant option

1.4.5. Show how travelers book a policy-compliant flight

1.5. Allow a traveler to search for lodging options and reserve a room

1.5.1. Show how travelers would identify policy-compliant options in search results

1.5.1.1. Identify FedRooms hotels

1.5.1.2. Identify FedRooms rates at FedRooms hotels

1.5.2. Show how search results appear to travelers when their agency has opted to:

1.5.2.1. Hide specific lodging properties

1.5.2.2. Hide non-FedRoom rates at FedRoom properties

1.5.2.3. Hide certain rate descriptions (GOV, MIL, AARP)

1.5.2.4. List FedRooms hotels first in the sort order

1.5.3. Show how travelers are alerted when they select a non-policy-compliant option

1.5.3.1. Select a non-FedRooms rate at a FedRooms property

1.5.3.2. Select a non-FedRooms property when a FedRooms rate is available at a FedRooms property

1.5.3.3. Select a rate above the per diem amount for that date/location

1.5.4. Show how travelers reserve a policy-compliant room

1.6. Allow a traveler to search for car rental options and reserve a car

1.6.1. Show how travelers would identify policy-compliant options in search results (e.g., the lowest-cost compact car)

1.6.2. Show how travelers are alerted when they select a non-policy-compliant option

1.6.3. Show how travelers reserve a non-policy-compliant rental car

1.7. Allow a traveler to review and submit the trip reservation

1.7.1. Show how the system evaluates the reservation for compliance and how the traveler is notified of any compliance issues

1.7.1.1. Show how the traveler would go back and select a policy-compliant rental car option to address the compliance issue

1.7.2. Show how the traveler would see cost per segment and total cost

1.7.3. Show how the traveler would see confirmation that travel has been reserved

1.8. Allow the traveler to review ticketing information and cancellation rule messaging

1.9. Export the final PNR and provide to the Contracting Officer for evaluator review

Pause for any clarification questions from the government.

AUTHORIZATION

Requirements to be Demonstrated:

AU-09, AU-10, AU-12, AU-13, AU-15, AU-27, AU-28, AU-35, AU-49, AU-50,

AU-55 – AU-60, AU-63 – AU-68, AU-99,

AU-200, AU-201

Demonstrate how your proposed solution will do the following:

1.10. Allow a traveler to create a travel authorization from a reservation

1.10.1. Show how the traveler would see per diem rates (lodging and M&IE) displayed for each day of travel

1.10.2. Show how the traveler would see their estimated expense amount for the trip (i.e., 15% gross-up of total air, car, hotel, M&IE)

1.10.3. Show how the traveler would see the privately owned vehicle (POV) mileage rate for the trip from home to airport and back

1.10.4. Show how the traveler would see estimated total costs

1.11. Allow a traveler to submit the travel authorization for review

1.11.1. Show how the travel authorization is displayed to the funds certifier

1.11.2. Show how the funds certifier would approve funds availability and line of accounting

1.12. Show the funds check sent to the financial management system; Export the data set in CSV, XLS, JSON or XML format. (Output will be used for Scenario 7.1)

1.13. Allow a supervisor to approve the travel authorization

1.13.1. Show how the supervisor views and approves the travel authorization/necessity of travel

1.14. Show the obligation request sent to the financial management system; Export the data set in CSV, XLS, JSON or XML format. (Output will be used for Scenario 7.2)

1.15. Show how the system sends the OK to ticket to the TMC

1.16. Provide a PDF of the travel authorization to the Contracting Officer for evaluator review

Pause for any clarification questions from the government.

VOUCHER

Requirements to be Demonstrated:

VO-01 – VO-03, VO-08, VO-13, VO-15, VO-16,

VO-47 – VO-54, VO-59 – VO-63, VO-66 – VO-70

VO-74 – VO-77,

VO-90 – VO-92, VO-95, VO-96,

VO-137 – VO-139, VO-215, VO-217

Demonstrate how your proposed solution will do the following:

1.17. Allow a traveler to create a voucher from an approved travel authorization

1.17.1. Show how the system populates the voucher with expenses from the IBA/CBA card

1.17.2. Show how the traveler would see all estimated expenses from the travel authorization

1.18. Allow a traveler to add expenses to the voucher

1.18.1. Show how a traveler would attach a receipt to an existing expense (e.g., PDF of a lodging receipt)

1.18.2. Show how a traveler would create a new expense

1.18.2.1. Traveler takes a picture of a receipt with a SmartPhone

1.18.2.2. Traveler uploads the image

1.18.2.3. System uses optical character recognition (OCR) to captures the expense type and amount

1.18.3. Show how the traveler would see an itemized list of expenses and total amount to be reimbursed

1.18.4. Show how the traveler would see total M&IE amounts for each day of travel

1.18.5. Show how the traveler would see which amounts are to be disbursed to a government card (IBA, CBA) vs. direct to traveler

1.19. Show how a traveler is alerted to errors in a voucher

1.19.1. Show how the system would identify an expense greater than $75 that does not have a receipt

1.19.2. Show how the traveler would indicate a lost receipt

1.20. Allow a traveler to sign and submit a voucher

1.21. Allow a traveler to track the status of a voucher approval and payment

1.22. Show the disbursement request sent to the financial management system; Export the data set in CSV, XLS, JSON or XML format. (Output will be used for Scenario 7.3)

1.23. Allow a traveler to view the complete voucher

1.24. Provide a PDF of the voucher to the Contracting Officer for evaluator review

Pause for any clarification questions from the government.

SCENARIO 2: DOMESTIC TRIP with DATE CHANGE

User Roles: Traveler, Supervisor

Objective: Demonstrate the proposed solution highlighting key requirements identified in the Service Blueprints and Requirements Traceability Matrix for changing the date for a Domestic Trip.

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

The order of tasks may be modified from the order listed, if necessary. The government may ask clarification questions at the end of each phase of the demonstration.

RESERVATION

Requirements to be Demonstrated:

RE-71,

RE-74 – RE-76

Demonstrate how your proposed solution will do the following:

2.1. Allow a traveler to change the dates of an existing travel reservation; In this case, move the departure date a day earlier

2.1.1. Show how the traveler updates the airfare selection

2.1.2. Show how the traveler updates the lodging selection

2.1.3. Show how the traveler updates the car rental selection

2.2. Provide a PDF of the updated PNR record to the Contracting Officer for evaluator review

Pause for any clarification questions from the government.

AUTHORIZATION

Requirements to be Demonstrated:

AU-61, AU-62, AU-69, AU-77, AU-78, AU-82

Demonstrate how your proposed solution will do the following:

2.3. Automatically update the travel authorization with new dates

2.4. Allow a supervisor to reject a travel authorization; in this case, because the traveler did not update the TMC fee

2.4.1. Allow the traveler to update the TMC fee and resubmit the travel authorization

2.4.2. Allow the supervisor to view the updated travel authorization and trip costs

2.5. Allow a supervisor to approve the updated travel authorization

2.6. Show the adjusting obligation request sent to the financial management system; Export the data set in CSV, XLS, JSON or XML format. (Output will be used for Scenario 7.1)

Pause for any clarification questions from the government.

SCENARIO 3: DOMESTIC TRIP with CANCELLATION

User Roles: Traveler

Objective: Demonstrate the proposed solution highlighting key requirements identified in the Service Blueprints and Requirements Traceability Matrix to cancel a Domestic Trip.

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

The order of tasks may be modified from the order listed, if necessary. The government may ask clarification questions at the end of each phase of the demonstration.

AUTHORIZATION

Requirements to be Demonstrated:

AU-69, AU-83, AU-84

Demonstrate how your proposed solution will do the following:

3.1. Allow a traveler to cancel a travel authorization before ticketing for a trip that uses a refundable fare

3.1.1. Show how the system automatically cancels the trip reservation

3.2. Allow a traveler to cancel a travel authorization after ticketing for a trip that uses a refundable fare

3.2.1. Show how the system automatically cancels the trip reservation

3.3. Allow a traveler to cancel a travel authorization for a trip that uses a non-refundable fare

3.3.1. Show how the system automatically cancels the trip reservation

Pause for any clarification questions from the government.

SCENARIO 4: FOREIGN TRIP

User Roles: Traveler, Traveler Arranger

Objective: Demonstrate the proposed solution highlighting key requirements identified in the Service Blueprints and Requirements Traceability Matrix for completing a Foreign Trip.

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

The order of tasks may be modified from the order listed, if necessary. The government may ask clarification questions at the end of each phase of the demonstration.

RESERVATION

Requirements to be Demonstrated:

RE-11

Demonstrate how your proposed solution will do the following:

4.1. Allow a traveler to search for foreign airline trip options and book a flight

4.1.1. Show exception information for required use of coach class

4.2. Allow a traveler to review and submit the trip reservation

4.3. Provide a PDF of the final PNR record to the Contracting Officer for evaluator review

Pause for any clarification questions from the government.

4.4. Allow a traveler to create a travel authorization from a reservation

4.5. Provide a PDF of the travel authorization to the Contracting Officer for evaluator review

Pause for any clarification questions from the government.

VOUCHER

Requirements to be Demonstrated:

VO-59 – VO-61,

VO-71 – VO-73

Demonstrate how your proposed solution will do the following:

4.6. Allow a travel arranger to create a voucher from an approved travel authorization

4.7. Convert foreign currency expenses to $US

4.8. Allow a traveler to approve a voucher submitted by the travel arranger

4.9. Provide a PDF of the voucher to the Contracting Officer for evaluator review.

SCENARIO 5: LOCAL TRIP / MISCELLANEOUS VOUCHER

Objective: Demonstrate the proposed solution highlighting key requirements identified in the Service Blueprints and Requirements Traceability Matrix for completing a Local Trip / Miscellaneous Voucher.

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

The order of tasks may be modified from the order listed, if necessary. The government may ask clarification questions at the end of each phase of the demonstration.

VOUCHER

Requirements to be Demonstrated:

VO-97 – VO-131

Demonstrate how your proposed solution will do the following:

5.1. Allow a traveler to create a local voucher

5.2. Allow a traveler to add expenses to the local voucher

5.2.1. Include payee info

5.2.2. Include a list of itemized expenses

5.2.3. Attach receipts for expenses

5.2.4. Include mileage and mileage rate for a POV

5.2.5. Calculate total expense amount

5.2.6. Show accounting classification information, amount and allocation percentage

5.3. Allow a traveler to sign and submit the local voucher

5.3.1. Show how the traveler would see a disallowed local voucher expense

5.3.2. Show how the traveler is notified of the appeals process for disallowed expenses

5.3.3. Allow the traveler to correct the disallowed expense and resubmit

5.4. Allow a traveler to track the status of a local voucher approval and payment

5.5. Allow a traveler to view the complete local voucher

5.6. Provide a PDF of the voucher to the Contracting Officer for evaluator review

SCENARIO 6: SHORT DISTANCE TRIP

Objective: Demonstrate the proposed solution highlighting key requirements identified in the Service Blueprints and Requirements Traceability Matrix for completing a Short-Distance Trip.

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

The order of tasks may be modified from the order listed, if necessary. The government may ask clarification questions at the end of each phase of the demonstration.

VOUCHER

Requirement to be Demonstrated:

VO-04

Demonstrate how your proposed solution will do the following:

6.1. Capture information when travel is more than 12 hours but not exceeding 24 hours

6.1.1. Show that the traveler qualifies for M&IE only (not lodging)

6.1.2. Show that M&IE becomes taxable income

6.2. Provide a PDF of the voucher to the Contracting Officer for evaluator review

SCENARIO 7: INTEGRATION GATEWAY API/SFTP

User Roles: SysAdmin

Demonstration Objectives: Financial Management (FM) Application Programming Interfaces (API) Specifications and mapping templates requirements have been provided in the RFP in Attachment 14. It is not expected that vendors will make any API connections during the demonstration phase, however GSA does expect to evaluate how the solution presented by the vendor maps to the published standards since Funds Management standards are a critical requirement with US Federal Government agencies. The overriding intent of these requirements will be to evaluate the ability of a vendor solution to export transactional data generated during Scenarios 1-3 in a manner that is compatible with the published APIs as these are critical to the government mission of reducing travel costs via decreased approval times. These API calls will simulate the following steps: 1) Verification request for funds availability, 2) Obligation of funds upon approval of the Travel Authorization and 3) Disbursement of funds upon processing of a Travel Voucher. While ETSNext will need to support sFTP for FM checks as part of its mission to ‘Do No Harm’, APIs are the preferred method of connectivity and the focus of this scenario.

System Integration Considerations:

· Vendors are not expected to build integrations to Financial Management (FM) systems for the demonstration. However, GSA will validate the solution integration capabilities by reviewing extract files. The vendor will provide a file export that has all Authorizations and Vouchers that would be sent for a FM check. (GSA will compare to a selected FM API to see compatibility of current state).

· Vendor shall demonstrate that their solution supports API gateway technology and can support using it for FM Integration as part of the ETSNext Integration layer as it serves as the entry point that will authenticate/authorize and send the request to the proper endpoint service in the standard integration layer. The APIs will crosswalk the (TRT standard data elements) as defined in the T&E Business Standards to the corresponding FM standard data elements. If API service exports cannot be demonstrated, please demonstrate via other compatible flat file exports as would be used with sFTP.

REST API or SFTP: /travelAuthorization/funds

AU-63, AU-64, AU-65

Demonstrate how your proposed solution will do the following:

7.1. Using the dataset from Scenarios 1, 2, and 3 to create a Travel Authorization Fund check request and export that data set as output in CSV, XLS, JSON or XML format to demonstrate input structure, key fields, success, or failure, etc. using the specified formatting options. Please provide a mapping of your output files to the API Standard Travel Authorization Check Fund Service as outlined in Attachment PDQ of the RFP.

Pause for any clarification questions from the government.

REST API or SFTP:

/travelAuthorization

AU-200

Demonstrate how your proposed solution will do the following:

7.2. Using the dataset from Scenarios 1, 2, and 3 to create a Travel Authorization funds obligation request and export that data set as output in CSV, XLS, JSON or XML format to demonstrate input structure, key fields, success, or failure, etc. using the specified formatting options. Please provide a mapping of your output file to the Travel Authorization API Standard Service as outlined in Attachment PDQ of the RFP.

Pause for any clarification questions from the government.

REST API or SFTP:

/travelVoucher/disbursements

VO-90, VO-91, VO-129, VO-130

Demonstrate how your proposed solution will do the following:

7.3. Using the dataset from Scenarios 1, 2, and 3 to create voucher/claim for reimbursement of expenses payment disbursement information consistent with FTR and OMB Cir as output and export that data set as output in CSV, XLS, JSON or XML format. Please provide a mapping of your output file to the API Standard Travel Voucher disbursements Service as outlined in Attachment PDQ of the RFP.

SCENARIO 8: TECHNICAL & SECURITY DEMONSTRATION

User Roles: Traveler, Travel Arranger, Approver

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

Demonstration Objective: Demonstrate general capabilities and features of the vendor’s solution as defined in the Requirements Traceability Matrix and related RFP documents as it relates to Non-Functional Requirements to include Technical and Security. The expected outcome of these scenarios are for a vendor to show how their system can meet the requirements.

TECHNICAL

Requirement to be Demonstrated:

TE-08, TE-09, TE-32, TE-03

Demonstrate how your proposed solution will do the following:

8.1. Show a sample of a system generated email notification

8.2. Allow a traveler, travel arranger or approver to complete a microsurvey and provide feedback after submission of an authorization or voucher

8.3. Show browser compatibility for Safari, Google Chrome, and Microsoft Edge

8.4. Provide a mobile user interface for Expense Entry, Travel Booking, Approvals

Pause for any clarification questions from the government.

ROLE-BASED AUTHORIZATION

Requirement to be Demonstrated:

SE-28, SE-64

Demonstrate how your proposed solution will do the following:

8.5. Assign users to specific roles within applications which define their authorizations and system views

8.6. Show how the vendor solution uses Active Directory group membership

8.6. Support separation of duties

Pause for any clarification questions from the government.

USER LOGIN & PASSWORDS

Requirement to be Demonstrated:

SE-24, SE-66, SE-45, SE-46

Demonstrate how your proposed solution will do the following:

8.7. Accommodate rules for password creation (e.g., specified minimum of numbers and letters, required mix of numbers and letters, prevents users from using the same password, and defined reuse cycle (number of times and period of time)).

8.8. Limit the number of unsuccessful password attempts, followed by a user lockout

8.8. Sign-on and validate credentials using dual / multi factor authentication

8.9. Generate alerts for security violations and deliver them to appropriate personnel via workflow (e.g., unsuccessful login, unauthorized login attempt, etc.)

8.10. Allow security and error messages to be customized for the GSA users

Pause for any clarification questions from the government.

SYSTEM ACCESS CONTROLS

Requirement to be Demonstrated:

SE-50, SE-61, SE-48

Demonstrate how your proposed solution will do the following:

8.11. Terminate active user sessions after periods of inactivity

8.12. Support controllable auto logoff intervals for inactive users by authorized users

8.13. Support multiple sessions within a given login ID

Pause for any clarification questions from the government.

DATA DISPLAY CONTROLS

Requirement to be Demonstrated:

SE-30, SE-57

Demonstrate how your proposed solution will do the following:

8.14. Allow fields with sensitive/private data the ability to be masked (e.g., tax numbers/ID, passwords, bank account information, credit card numbers, Social Security number, Drivers License number, etc.)

8.15. Mask sensitive/private data when viewing both on-screen and through reports and queries

Pause for any clarification questions from the government.

AUDIT TRAIL

Requirement to be Demonstrated:

SE-56

Demonstrate how your proposed solution will do the following:

8.8. Record transactions with user ID and time stamp and create a log for each transaction and each user that is viewable

8.9. Export audit logs to MS Office products

Pause for any clarification questions from the government.

ACCESSIBILITY

Requirement to be Demonstrated:

TE-04

Demonstrate how your proposed solution does the following:

8.8. Run an accessibility audit using Lighthouse on the following pages and provide a JSON file of each result to the Contracting Officer for evaluator review:

8.8.1. Index/home page

8.8.2. Search results page

8.8.3. Create voucher page

SCENARIO 9: REPORTING

User Roles: Supervisory Approver, Administrator

During the each demonstration phase, describe how the solution:

· Supports the user experience

· Follows general principles for user interface design as described in Nielsen's 10 Usability Heuristics (TE-44)

· Accommodates novice or expert users

Demonstration Objective: Demonstrate specific capabilities and features of the vendor’s solution related to Reporting and Analytics.

STANDARD REPORTING

Requirements to be Demonstrated:

RP-18

9.1. Demonstrate any pre-defined templates for standard reports such as Expense Summary, Travel Compliance, Approvals, etc.

9.2. Show how the system is able to schedule standard reports on a daily, weekly, or monthly basis and automatically deliver them to specified email addresses

Pause for any clarification questions from the government.

AD HOC REPORTING

Requirements to be Demonstrated:

RP-19

9.3. Demonstrate how the system enables users to select specific fields and filters to generate ad hoc reports tailored to the user's needs; Show how the system generates ad hoc reports in real-time, pulling the latest available data

9.4. Using the inputs generated during Scenarios 1, 2 and 3, generate a data extract of all transactional data in CSV, XLS, JSON or XML format

Pause for any clarification questions from the government.

ANALYTICS

Requirements to be Demonstrated:

RP-20

9.5. Show how the system provides various data visualization formats like charts, graphs, and heat maps to provide analytical insights for expense and travel data

11/9/2023 2 V. 1.1 image1.png