693KA8-24-DRAFTSIR-INVERSE_Attachment J-1 Specs.pdf

Draft

Federal Aviation Administration

Invoice Validation and Expense Reconciliation Services

(INVERSE)

INVERSE Functional and Performance Specification

(IFPS)

June 20, 2024

Federal Aviation Administration

800 Independence Avenue, SW

Washington, DC 20591

INVERSE DRAFT SIR 693KA8-24-R-XXXXX

Attachment J-1 Page 2

Table of Contents

1. Introduction

1.1. Purpose

1.2. Definitions

1.3. Overview of FAA Business Processes

1.4. Interpretation of Requirements

1.5. Document Overview

2. Applicable Documents

2.1. FAA Orders and Notices

2.2. Other FAA Documents

2.3. Other Government Documents

2.4. Non-Government Documents

3. INVERSE System Requirements

3.1. General System Requirements

3.2. Security

3.3. Data Inputs

3.4. Storage of Data

4. INVERSE Services

4.1. General Capability

4.2. Calculation Specifications

4.3. Discrepancy Thresholds

4.4. Discrepancy Calculations

4.5. Validation of Taxes

4.6. Expensing

4.7. Projections of Estimates

5. INVERSE User Portal

5.1. General Portal Requirements

5.2. Human Factors

5.3. User Sessions

5.4. Calculation Specifications

5.5. Security

5.6. Data Repository

5.7. User Function / Sign In

Attachment J-1 Page 3

5.8. Workflow

5.9. Report Generation

Attachment J-1 Page 4

Attachment J-1

INVERSE Functional and Performance Specification (IFPS)

1. Introduction

1.1. Purpose

This document defines the functional and performance specifications for services that the Federal

Aviation Administration (FAA) will acquire under the Invoice Validation and Expense

Reconciliation Services (INVERSE) contract as outlined in the INVERSE Section C Statement of Work.

1.2. Definitions

The following terms are used throughout this document to describe the FAA’s requirements. The terms are defined here to ensure a common understanding of the requirements.

Acronym Definition

ACC Accounting Classification Code

CINP Communications, Information, and Network Programs

EIS FAA Enterprise Infrastructure Solutions

F&E Facilities and Equipment

FAN Funding Agreement Number

FENS FAA Enterprise Services

IFPS Inverse Functional and Performance Spec

LOA Line of Accounting. This is a combination of fields that are used to code charges into the correct account and project

MRC Monthly Recurring Charge

MRC-NE Monthly Recuring Charge – Network Establishment

Note: This CLIN type is used to spread network establishment over multiple years.

NAS National Air Space

NRC Non-Recurring Charge

OPS Operations funding

TIS Telecommunications Integrated Services commercially available, electronic format

Possible formats include, but are not limited to, ASCII text, XML, Microsoft

Excel spreadsheets, Oracle database tables, and Microsoft Access database tables.

1.3. Overview of FAA Business Processes

The FAA’s TIS directorate is responsible for network services that support the FAAs

Administrative network and NAS network. These services are ordered primarily through the

FENS contract and EIS Task Orders contract.

Attachment J-1 Page 5

Each service ordered through one of these contracts is first quoted by the Vendor listing the contractual CLINs and associated contract prices. The FAA reviews the quotes and if ordered, the FAA allocates budget for the service and creates a service order. The first two years of a service are typically paid for with F&E funding and the remaining years are typically paid for with OPS funding. Upon delivery of the service and FAA acceptance, the FENS or EIS Vendor will invoice the FAA for the service based on the In-Service date.

Services are invoiced at the beginning of each month for all services in place during the prior month. For example, all services that were in service in the month of March would be on an

April dated invoice. The FAA is required to review and pay all approved charges 30 days from the invoice date. This will require the INVERSE contractor to conduct the invoice review, assign the appropriate expensing/budgeting codes and identify any discrepancies in time for the

FAA to review the findings and pay the invoice on time.

Detailed business rules regarding the ordering, invoicing, expensing and invoice payments can be found in Attachment J-4

1.4. Interpretation of Requirements

This document uses ‘must’ as the mandatory imperative in requirement statements. Use of ‘must’ as the mandatory imperative complies with Federal Plain Language Guidelines, March 2011

Revision 1, May 2011 and the FAA Plain Language Toolkit accessible from FAA Plain

Language Website: https://www.faa.gov/about/initiatives/plain_language

When the words “and” and “or” appear in in the statement of a requirement, they represent logical operators defined as follows:

• And – All the conditions of the requirement must be met.

• Or – At least one of the conditions of the requirement must be met.

When an element of a document is referenced such as a Subsection, Section, Paragraph, or

Chapter, all subordinate Subsections, Sections, Paragraphs, or Chapters to the referenced element are applicable.

1.5. Document Overview

Section 1 contains introductory information. Section 2 references the applicable documents that must be followed in execution of this contract. Section 3 provides specifications for the

INVERSE System, which refers to the automated capabilities required to meet the requirements of the contract. Section 4 provides specifications for the services provided under the contract.

Section 5 provides the specifications of the INVERSE User Portal.

2. Applicable Documents

The following documents are cited in other sections of the IFPS. They are the sources of additional requirements that apply to the INVERSE capabilities. The current version of each document is identified. If an applicable document is updated during the contract period of performance, the Contractor must adhere to the latest version of each document. When an https://www.faa.gov/about/initiatives/plain_language

Attachment J-1 Page 6 applicable document is updated, the Contractor must identify any impacts to the performance, cost, schedule, or other factors affecting the delivery of INVERSE Services and capabilities. The

Government will review the Contractor's impact assessment and determine if a contract modification is required. A limited number of copies of other applicable FAA documents may be obtained from the Contracting Officer. Requests should fully identify the material desired

(document identification number, title, date of issue, etc.) and should identify the RFP or contract involved.

2.1. FAA Orders and Notices

Order Number Title

1370.117 National Airspace System (NAS) Internet Protocol (IP) Addressing Policy

1370.121B FAA Information Security and Privacy Program & Policy

2.2. Other FAA Documents

Document Number Title

FAA-HF-STD-001B Human Factors Design Standard

RMA-HDBK-006C Reliability, Maintainability, and Availability (RMA) Handbook

N/A SWIM Governance Policies Version 3.1 (February 6, 2020)

2.3. Other Government Documents

Document Number Title

NIST Special Publication

800-53 Rev 5

Security and Privacy Controls for Information Systems and Organizations

DHS TIC Reference

Architecture v2.2

Trusted Internet Connections (TIC) Reference Architecture Document Version 2.2, Department of Homeland Security, June 19, 2017

X.509 Certificate Policy for the U.S. Federal PKI Common Policy Framework v1.31

NIST FIPS 180-4 Secure Hash Standard (SHS)

2.4. Non-Government Documents

Document Identifier Title

JMS 1.1 Java(TM) Message Service Specification Final Release 1.1

SAML 2.0 Security Assertion Markup Language Version 2.0

SOAP 1.2 Simple Object Access Protocol Version 1.2

Attachment J-1 Page 7

Document Identifier Title

SOAP MTOM SOAP Message Transmission Optimization Mechanism

TLS 1.2 Transport Layer Security Version 1.2

WS-Addressing 1.0 Web Services Addressing Version 1.0

WSDL 1.1 Web Services Description Language Version 1.1

WS-I Basic Security Profile 1.0 Web Services Interoperability Basic Security Profile Version 1.0

WS-Notification 1.3 Web Services Notification Version 1.3

WS-Policy 1.5 Web Services Policy Version 1.5

WS-Reliable Messaging 1.2 Web Services Reliable Messaging Version 1.2

WS-Security 1.1 Web Services Security Version 1.1

WS-Trust 1.4 Web Services Trust Version 1.4

XML Digital Signature 1.1 XML Signature Syntax and Processing Version 1.1

XML Encryption 1 XML Encryption Syntax and Processing Version 1

Verizon 811 Guide – v21.2 EDI Billing Implementation Guide, September 2021

ASC X12 Draft Version 4 Release 1 Standards

Telecommunications Industry Forum (TCIF) Telephone Billing Guideline Issue 9

3. INVERSE System Requirements

3.1. General System Requirements

[SPEC-SR001] The system clocks must be synchronized to UTC.

[SPEC-SR002] The system must support the business rules outlined in Attachment J-4

[SPEC-SR003] The system must be capable of storing INVERSE generated data, reports, and

CDRLS in a manner that allows the information to be reported by program (i.e. FENS and EIS).

3.2. Security

[SPEC-SR004] The INVERSE User Portal must comply with applicable tailored security controls in Attachment J-5.

[SPEC-SR005] The system must provide an encrypted (HTTPS TLS 1.3 or higher or HTTP

Strict Transport Security (HSTS)) session from the user to the INVERSE User Portal Functions defined in the IFPS.

[SPEC-SR006] The system must utilize a deny by default and permit by exception policy to restrict traffic to authorized ports and protocols only.

Attachment J-1 Page 8

[SPEC-SR007] The system must provide Denial of Service (DoS) and Distributed Denial of

Service (DDoS) protection for the defined INVERSE User Portal Functions.

[SPEC-SR008] The system must utilize multi-factor authentication to identify the user.

[SPEC-SR009] The system must be capable of detecting and reporting intrusions.

[SPEC-SR010] The system must be capable of identifying intrusions and actively countering them.

[SPEC-SR011] The system must be capable of detecting and removing Viruses.

[SPEC-SR012] The system must be capable of detecting and removing Malware.

[SPEC-SR013] The system must log sessions and security events.

[SPEC-SR014] The INVERSE Security Monitoring and Reporting Capability must have an availability of TBD.

[SPEC-SR015] The INVERSE Security Monitoring and Reporting Capability must have a reliability of TBD.

[SPEC-SR016] The system must provide an INVERSE Security Monitoring and Reporting

Capability that enables authorized users to obtain information and perform actions related to the

INVERSE System and INVERSE User Portal.

[SPEC-SR017] The INVERSE Security Monitoring and Reporting Capability must provide current, read-only access to information system security-related information from: (1) Intrusion detection and protection elements, (2) Boundary protection devices/services, including firewalls,

(3) INVERSE-dedicated infrastructure, (4) Security systems and services, (5) Security incident audit data and ticketing system data.

[SPEC-SR018] The INVERSE Security Monitoring and Reporting Capability must provide security incident notifications to FAA-designated security points-of-contact within 15 minutes of detection of a security incident.

[SPEC-SR019] The INVERSE Security Monitoring and Reporting Capability must enable authorized personnel to: (1) Create custom dashboards; (2) Write custom channels based on

SMRM data; (3) Define and apply channel filters based on user-specified criteria corresponding to one or more data fields (e.g., hostname and message type); and (4) Generate custom reports using criteria in multiple fields (e.g., Message and IP Address)."

[SPEC-SR020] The INVERSE Security Monitoring and Reporting Capability must provide user- customized views of the data based on payload contents of all packets inspected.

[SPEC-SR021] The INVERSE Security Monitoring and Reporting Capability must provide automated visual alerts based on defined event types received.

[SPEC-SR022] The INVERSE Security Monitoring and Reporting Capability must provide a drill-down capability for analyzing events.

3.3. Data Inputs

Attachment J-1 Page 9

[SPEC-SR023] The system must be capable of importing government-furnished data (both machine readable and electronic copies such as PDF and Microsoft office documents, from various FAA systems.

[SPEC-SR024] Where government-furnished data is only available in hardcopy format, the system must provide a means for entry of the data by INVERSE contractor personnel.

[SPEC-SR025] The system must be capable of importing the FENS CLIN structure and associated prices in a commercially available, electronic format.

[SPEC-SR026] The system must be capable of importing the EIS CLIN structure and associated prices in a commercially available, electronic format.

[SPEC-SR027] The system must be capable of importing FAA funds obligation data in a commercially available, electronic format to be specified by the FAA.

[SPEC-SR028] The system must be capable of importing FENS service order data including service acceptance dates and service discontinuation dates in a commercially available, electronic format.

[SPEC-SR029] The system must be capable of importing EIS service order data including service acceptance dates and service discontinuation dates in a commercially available, electronic format.

[SPEC-SR030] The system must be capable of importing FENS Usage data in a commercially available, electronic format.

[SPEC-SR031] The system must be capable of importing EIS Usage data in a commercially available, electronic format.

[SPEC-SR032] The system must be capable of importing FENS outage data in a commercially available, electronic format via the FENS User Portal.

[SPEC-SR033] The system must be capable of importing EIS outage data in a commercially available, electronic format via the TBD.

[SPEC-SR034] The system must be capable of importing FAA payment data by delivery order, delivery order modification number, and Accounting Classification Code (ACC) in a commercially available, electronic format to be specified by the FAA.

[SPEC-SR035] The system must be capable of importing FENS service level agreement data in a commercially available, electronic format.

[SPEC-SR036] The system must be capable of importing EIS service level agreement data in a commercially available, electronic format.

[SPEC-SR037] The system must be capable of importing FENS invoice data in a commercially available, electronic format.

[SPEC-SR038] The system must be capable of importing EIS invoice data in a commercially available, electronic format.

3.4. Storage of Data

Attachment J-1 Page 10

[SPEC-SR039] The system must store INVERSE GFI data. Each programs data (i.e. FENS and

EIS) must be stored in a manner that allows the information to be reported by program.

[SPEC-SR040] The system must store INVERSE Calculated data. Each programs data (i.e.

FENS and EIS) must be stored in a manner that allows the information to be reported by program.

4. INVERSE Services

4.1. General Capability

[SPEC-SR041] The system and INVERSE User Portal must provide an Invoice Review

Capability that enables authorized users to review the complete invoicing history of FENS and

EIS Invoices.

[SPEC-SR042] The system must store the following fields at a minimum:

1. CLIN,

2. Charge Type (e.g. NRC, MRC, MRC-NE),

3. Task Order-based charges,

4. Taxes and Surcharges,

5. Adjustments and credits,

6. Support Services charges,

7. Service order charges,

8. Type of Funds: F&E, Operations,

9. Timeframe: Month-Year, Government Fiscal Quarter, Government Fiscal Year,

10. Program (IE FENS and EIS),

11. Invoice Number,

12. Billing Start Date,

13. Billing End Date,

14. Delivery Order Number,

15. CLIN Number/Code

16. CLIN Unit Price,

17. CLIN Quantity Including pro-rated CLIN Quantity,

18. Unique FENS or EIS Service Identifier.

4.2. Calculation Specifications

[SPEC-SR043] The system must be capable of calculating prorated amounts based upon the fraction of the billing period for which a CLIN was in-service.

[SPEC-SR044] The system must be capable of calculating prorated amounts based upon FAA-specified allocation percentages.

4.3. Discrepancy Thresholds

[SPEC-SR045] The system must apply discrepancy thresholds to determine when amounts on monthly invoices are outside the discrepancy thresholds defined in the IFPS Section C.4.3.

[SPEC-SR046] The system must verify that Fixed Price CLINs are within 0.00% of actual

CLIN price - Threshold 0%.

Attachment J-1 Page 11

[SPEC-SR047] The system must verify that usage-based Invoice quantities are within +- 10% of calculated value - Threshold +-10%.

[SPEC-SR048] The system must verify that mileage-based Invoice quantities are within +- 10% of calculated value - Threshold +-10%.

[SPEC-SR049] The system must verify that service billing date billed equals the actual In-service date supplied by the FAA - Threshold 0%.

[SPEC-SR050] The system must verify that the actual invoice credit equals the actual credit calculated - Threshold 0%.

[SPEC-SR051] The system must verify that the actual invoice adjustment invoiced equals the actual adjustment calculated. - Threshold 0%.

4.4. Discrepancy Calculations

[SPEC-SR052] The system must calculate billing discrepancies due to the contractual fixed price being outside of discrepancy thresholds defined in IFPS Section C.4.3.

[SPEC-SR053] The system must calculate billing discrepancies due to the Usage based invoice quantity being outside of discrepancy thresholds.

[SPEC-SR054] The system must calculate billing discrepancies due to the Mileage based invoice quantity being outside of discrepancy thresholds.

[SPEC-SR055] The system must calculate billing discrepancies due to the service billing date being outside of discrepancy thresholds.

[SPEC-SR056] The system must calculate billing discrepancies due to the actual credit invoiced being outside of discrepancy thresholds.

[SPEC-SR057] The system must calculate billing discrepancies due to the actual adjustment invoiced being outside of discrepancy thresholds.

[SPEC-SR058] The system must calculate service credits due to the FAA as a result of Service outages in accordance applicable contract clauses.

[SPEC-SR059] The system must calculate LOA payment discrepancies.

[SPEC-SR060] The system must calculate billing adjustments amounts required due to billing discrepancies. The system must compute the amounts to be deducted and returned to each LOA involved in a discrepancy.

4.5. Validation of Taxes

[SPEC-SR061] The system must calculate the effective rate of Universal Service Fund (USF), Gross Receipts and all other applicable taxes.

[SPEC-SR062] The system must provide a 12-month trend of each USF, Gross Receipts or other Taxes Categories and provide analysis if tax rates are reasonable.

4.6. Expensing

Attachment J-1 Page 12

[SPEC-SR063] The system must be able to assign accounting codes based on the associated funding agreement provided by the FAA and must follow the business rules outlined in

Attachment J-4.

[SPEC-SR064] The system must be able to track amendments or change orders and the impact to supplemental funding sources and accounting codes based on FAA discretion.

[SPEC-SR065] The system must track funds by year.

[SPEC-SR066] The system must track F&E and OPS funds separately.

[SPEC-SR067] The system must track SLA-based credits against the appropriate funds as specified in the business rules outline in Attachment J-4.

4.7. Projections of Estimates

[SPEC-SR068] The system must be capable of projecting year-end totals based upon year-to-date amounts.

[SPEC-SR069] The system must be capable of projecting year-end totals based upon prior year totals for the same time period.

[SPEC-SR070] The system must enable the user to select whether the basis for projections should be based on prior-year data or year-to-date data.

[SPEC-SR071] The system must be capable of calculating the amount to be transitioned to the

CINP OPS Base Budget from other LOAs.

5. INVERSE User Portal

5.1. General Portal Requirements

[SPEC-SR072] The INVERSE User Portal must have an availability of 0.998 measured over a rolling 12-month period. Planned outages are excluded from the availability calculation.

[SPEC-SR073] The INVERSE User Portal must not have more than 9 unplanned outages per year and must not have more than 12 planned outages per year.

[SPEC-SR074] The INVERSE User Portal must be accessible via current versions of FAA-approved browsers.

[SPEC-SR075] The INVERSE User Portal must support connections using the IPv4 and IPv6 stacks.

5.2. Human Factors

[SPEC-SR076] The INVERSE User Portal must conform to the FAA-approved Human Factors as referenced in Section 2, applicable documents, of the IFPS.

5.3. User Sessions

[SPEC-SR077] The INVERSE User Portal must support at least 250 users accounts and 50 simultaneous user sessions.

5.4. Calculation Specifications

Attachment J-1 Page 13

[SPEC-SR078] The INVERSE User Portal must be capable of calculating subtotals based upon user-specified ranges, intervals, indices, and thresholds.

[SPEC-SR079] The INVERSE User Portal must calculate duration in terms of the number of calendar days.

5.5. Security

[SPEC-SR080] The INVERSE User Portal must comply with applicable tailored security controls in Attachment J-5.

[SPEC-SR081] The INVERSE User Portal must utilize a deny by default and permit by exception policy to restrict traffic to authorized ports and protocols only.

[SPEC-SR082] The INVERSE User Portal must utilize multi-factor authentication to identify the user.

[SPEC-SR083] The INVERSE User Portal must log sessions and security events.

[SPEC-SR084] The INVERSE User Portal must provide Denial of Service (DoS) and

Distributed Denial of Service (DDoS) protection for the defined INVERSE User Portal

Functions.

5.6. Data Repository

[SPEC-SR085] The INVERSE User Portal must provide a data repository for all related documents associated with INVERSE invoice processing.

[SPEC-SR086] The INVERSE User Portal must display folders that are organized by document type and date for ease of Users to find information.

[SPEC-SR087] The INVERSE User Portal Data Repository must support the establishment and enforcement of user access privileges at the library or folder level.

[SPEC-SR088] The INVERSE User Portal Data Repository must store at a minimum all the data fields listed within this IFPS Document.

5.7. User Function / Sign In

[SPEC-SR089] The INVERSE User Portal must provide a User Portal that supports the following Data Sets: (1) FAA Data (2) FENS Data (3) EIS Data (4) Other Agency Data

[SPEC-SR090] The INVERSE User Portal must provide a single sign-on authentication capability.

[SPEC-SR091] The INVERSE User Portal must implement role-based access privileges to the individual functions comprising the INVERSE User Portal.

[SPEC-SR092] The INVERSE User Portal must provide a help function to aid users with navigating the portal and using its functions.

[SPEC-SR093] The INVERSE User Portal must validate user inputs and reject erroneous inputs.

[SPEC-SR094] The INVERSE User Portal must prevent unauthorized access to user portal resources at the application level.

Attachment J-1 Page 14

[SPEC-SR095] The INVERSE User Portal must provide an Approver role for authorized FAA users to disposition account establishment requests.

[SPEC-SR096] To facilitate user-initiated searches, the INVERSE User Portal must provide drop-down menus that provide a list of valid values for the search criteria within each function as appropriate for each data type.

5.8. Workflow

[SPEC-SR097] The INVERSE User Portal must provide a workflow for CDRLs that allow the

FAA to review, approve or reject with edits.

5.9. Report Generation

[SPEC-SR098] The INVERSE User Portal must provide authorized users with the ability to review the history of identified billing discrepancies including but not limited to: (1) The associated invoice number and billing period (2) A description of the nature of the discrepancy, e.g., invoiced quantity does not match ordered quantity (3) The dollar value of the discrepancy

(4) The status of the discrepancy, e.g., open, resolved, adjustment applied to invoice, etc.

[SPEC-SR099] The INVERSE User Portal must provide authorized users with the ability to review the history of invoice adjustments and credits including but not limited to: (1) The associated invoice number and billing period (2) The reason for the adjustment or credit; and (3)

The dollar value of the adjustment or credit.

[SPEC-SR100] The INVERSE User Portal must allow users to enter a start date and/or an end date or no dates at all for queries on date-based information within each function.

[SPEC-SR101] When no dates are entered by the user, the INVERSE User Portal must default to basing the search on the most recent invoice month.

[SPEC-SR102] The INVERSE User Portal must provide users with the capability to filter the contents of an on-line report based upon a specific value or range of values for any field within the report.

[SPEC-SR103] The INVERSE User Portal on-line respiratory must be enable users to retrieve, view and report data by its related invoice period, invoice number and/or payment cycle.

[SPEC-SR104] The INVERSE User Portal must provide users with the capability to sort the contents of an on-line report based upon one or more key fields within the report.

[SPEC-SR105] The INVERSE User Portal must enable the user to specify whether the sorted order should be in ascending or descending order numerically or alphabetically.

[SPEC-SR106] The INVERSE User Portal must enable users to select the data fields to be included in the report.

[SPEC-SR107] The INVERSE User Portal must enable users to specify the database records to be included in the report based upon user-specified criteria.

[SPEC-SR108] The INVERSE User Portal must provide authorized users with the ability to query the following fields at a minimum:

Attachment J-1 Page 15

1. CLIN,

2. Charge Type (e.g. NRC, MRC, MRC-NE),

3. Task Order-based charges,

4. Taxes and Surcharges,

5. Adjustments and credits,

6. Support Services charges,

7. Service order charges,

8. Type of Funds: F&E, Operations,

9. Timeframe: Month-Year, Government Fiscal Quarter, Government Fiscal

Year,

10. Program (IE FENS and EIS),

11. Invoice Number,

12. Billing Start Date,

13. Billing End Date,

14. Delivery Order Number,

15. CLIN Number/Code

16. CLIN Unit Price,

17. CLIN Quantity Including pro-rated CLIN Quantity,

18. Unique FENS or EIS Service Identifier.

[SPEC-SR109] The INVERSE User Portal must provide subtotals per billing period and combined total for all reports.

[SPEC-SR110] The INVERSE User Portal reports must be capable of reporting subtotals based upon user-specified ranges, intervals, indices, and thresholds.

[SPEC-SR111] The INVERSE User Portal reports must be capable of reporting duration in terms of the number of calendar days.

[SPEC-SR112] The INVERSE User Portal must provide subtotals for the numeric data fields selected by the user within a custom report.

[SPEC-SR113] The INVERSE User Portal must provide subtotals per Delivery Order.

[SPEC-SR114] The INVERSE User Portal must provide subtotals per service identifier.

[SPEC-SR115] The INVERSE User Portal must provide capability for users to create and save customized reports in the INVERSE User Portal.

[SPEC-SR116] The INVERSE User Portal must provide users with the capability to create custom reports based upon the results of user-specified queries.

[SPEC-SR117] The INVERSE User Portal must provide users with the capability to store custom reports within the on-line repository and retrieve them for future use.

[SPEC-SR118] The INVERSE User Portal must provide authorized users with the ability to download a machine-readable version of each invoice for all prior billing periods.

Attachment J-1 Page 16

[SPEC-SR119] For all on-line reports, pre-defined formats and user-specified formats, the

INVERSE User Portal must enable users to download the reports on a local storage device in a

CSV file format and PDF format with the PDF Format formatted to print out utilizing repeating row headings, printable on 8 1/2 x 11 paper, and headers showing criteria used, report date, and report name.