693KA8-23-RFI-INVERSE-01_ATTACHMENT 1.pdf

Contents C. Statement of Work

C.1 Introduction

C.2 INVERSE Program Management

C.3 Establish and Maintain Data Repository and Report Generation Capability

C.4 Invoice Review and Reconciliation

C.5 Payment Reconciliation

C.6 Budget Tracking and Analysis

C.7 Data Tracking and Analysis

C.8 Financial Analysis

C.9 Report Generation

C.10 Security Management

C.11 Other Programmatic and Technical Support

C. STATEMENT OF WORK

C.1 INTRODUCTION

C.1.1 BACKGROUND

The Federal Aviation Administration (FAA) acquires telecommunications services and equipment to support the nation’s air traffic control system, known as the National Airspace

System (NAS), as well as to support administrative and other non-NAS functions. The FAA has established the FAA Enterprise Network Services (FENS) program to ensure that the FAA’s needs for telecommunications services will continue to be met in a cost-effective manner through

2038. In addition, the FAA purchases administrative services from the GSA/EIS contract.

Although the FAA is currently processing GSA/EIS bills, the FENS schedule currently assumes the first telecommunications invoice will need to be processed by November 2024.

The FENS contract will be the primary vehicle through which the FAA acquires a broad range of telecommunications services and telecommunications support services. The FENS vendor will submit invoices for the services on a monthly basis and charges must be reviewed and validated prior to final payment. The GSA/EIS contract will be a secondary vehicle for which the FAA procures. The FAA intends to procure the required invoice review validation, and reconciliation services under a new contract vehicle for the above mentioned services. The contractor will be responsible for verifying that all invoiced charges have been ordered, priced, billed, and expensed correctly. The objectives of this effort are to improve control and oversight of telecommunications costs, facilitate budgeting and planning, and support the implementation of a fee-for-service program to allocate telecommunications costs to users.

C.1.2 SCOPE

C.1.2.1 Overview

This Statement of Work (SOW) describes the functions and services to be provided by the

INvoice Validation and Expense Reconciliation SErvices (INVERSE) contractor to assist the

FAA in the financial management of the FENS and GSA/EIS program.

The following paragraphs identify the required work elements to be performed by the INVERSE contractor.

I. Invoice Review and Reconciliation – Review all invoices submitted by the FENS and

GSA/EIS vendors to ensure that invoiced items and the associated charges are consistent with the current active service orders and quantities, contractual prices, and service credits due. Identify and notify the FAA of any discrepancies. Coordinate the resolution of discrepancies with the FENS and GSA/EIS vendors and notify the FAA of the outcome of the discrepancy resolution process.

II. Payment Reconciliation – Based on government provided business rules, provide government with detailed payment record of accounting codes used for each invoice and review government accounting reports to ensure that specific charges were expensed to the appropriate accounting and appropriation accounts. Identify discrepancies and required account adjustments.

III. Budget Forecasting, Tracking, and Analysis – Track all FENS and GSA/EIS charges by accounting and appropriation code, type of funds, and fiscal year of funds. Compare the actual expenses to the amount of funds budgeted and obligated for the associated services. Develop projections of future costs and advise the FAA of potential variances between obligations and projected costs.

IV. Establish and Maintain Data Repository – Maintain an on-line repository of all order, invoice, and financial data received as inputs and generated as outputs in the performance of the INVERSE contract. Provide the FAA with access to the database and the ability to browse and query the database and obtain pre-defined and ad hoc reports.

V. Data Tracking and Analysis – Conduct analyses of the FENS invoice data, associated funding and usage data to identify trends and cost drivers. Prepare cost forecasts and advise the FAA of potential issues.

VI. Report Generation – Provide the FAA with the capability to obtain pre-formatted and tailored reports via a portal maintained by INVERSE contractor.

VII. Security Management – Provide the requisite security measures to interface with FAA systems, ensure data integrity, and protect FAA data from unauthorized access.

VIII. Other Programmatic and Technical Support – Provide other programmatic and technical support to the FAA as specifically tasked. Support may include such items as participation in program reviews, service improvement meetings, and technical interchange meetings.

IX. INVERSE Program Management – Manage the INVERSE Program to ensure that all required functions are performed according to the program schedule and within the allocated cost. Conduct program status reviews and participate in technical interchange meetings related to the INVERSE.

Sections C.2 through C.11 of this SOW elaborate upon the required functions to be performed by the INVERSE contractor within each work element.

C.1.3 LEVEL OF EFFORT

The level of effort on the INVERSE contract will be a function of the number of services ordered, the number of CLINs per order, the number of discrepancies identified, and other factors. Approximate projection of services are 30,000 services per month on FENS and 24,000 services per month on GSA/EIS. All projections represent order-of-magnitude estimates, the actual values experienced under the FENS and GSA/EIS contract will vary.

C.1.4 GOVERNMENT-FURNISHED DATA

To enable the INVERSE contractor to perform the required functions, the government or its designee will provide the following data:

(1) Service order data, service acceptance dates, and service discontinuation dates;

(2) FENS and GSA/EIS CLIN structure and pricing;

(3) Thresholds for usage-based CLINs;

(4) Funds obligation data by delivery order modification number, including the accounting and appropriation codes

(5) FENS monthly invoices including call detail records and other supporting information.

(6) Invoice discrepancies resolved by the FAA;

(7) FENS and GSA/EIS service level agreement (SLA);

(8) Outage data (for determining when credits are due);

(9) FAA payment data;

The FAA will provide the INVERSE contractor with a secure electronic interface to the vendor’s

Online Portal. The INVERSE contractor will be granted the appropriate privileges to obtain read-only access to service order data and monthly invoices.

If apparent errors are detected within input data for which the government is the source, the

INVERSE contractor shall notify the Contracting Officer via e-mail. Multiple errors may be compiled in a single e-mail message and the notification shall be made within one business day when errors are detected. At a minimum, the e-mail notification shall list:

(1) source of the data, e.g., the FENS Program Office, GSA/EIS Program office

(2) category of source data as defined in future attachment J.

(3) date the source data was received by the INVERSE contractor;

(4) description of the source data error; and

(5) correct value(s) if identifiable.

The interval at which the data will be updated varies among the items. Service order information and funds obligation data may be updated as often as once per week. The invoice data, outage data, and payment data will be provided on a monthly basis. The usage thresholds, SLA, and reference cost data should be relatively static; updates will be provided as necessary. The CLIN pricing will change periodically, and it may be updated due to:

(1) start of an option year;

(2) introduction of a new service type; or

(3) modification of an existing service type.

C.2 INVERSE PROGRAM MANAGEMENT

C.2.1 PROGRAM MANAGEMENT ORGANIZATION

The INVERSE contractor shall establish a program management office at their own premises to support and manage the delivery of INVERSE services throughout the life of the contract. The

INVERSE contractor shall ensure that sufficient resources are available to provide the INVERSE services required by the FAA. The INVERSE contractor shall coordinate with the FAA on the plans and schedule to resolve any programmatic issues that may arise. In the course of resolving issues, the INVERSE contractor shall adhere to the schedule agreed upon by FAA and shall advise the FAA on the status of the issue resolution.

The INVERSE contractor shall maintain clear and effective lines of authority, coordination, communication, and accountability between their INVERSE contract team organization and the

FAA. To facilitate communication and coordination, the INVERSE contractor shall provide a

Program Manager to interface with the FAA. The INVERSE contractor’s Program Manager or his or her designated alternate shall be available for consultation with the Government on weekdays from 8:00am to 5:00pm in the Eastern time zone (except for Federal holidays).

Contractor may be required to attend meetings at the FAA Program Office site located in

Washington, DC.

C.2.2 PROGRAM MANAGEMENT FUNCTIONS

To ensure compliance with all requirements of the contract, the INVERSE contractor shall be responsible for the management and control of all personnel assigned to the INVERSE contract including subcontractors/team members. The INVERSE contractor shall provide a Program

Management briefing within 30 days of contract award in accordance with CDRL TBD.

In performing the INVERSE program management functions, the INVERSE contractor shall provide a program schedule that addresses the first year of the contract in accordance with

CDRL TBD. To ensure the FAA’s awareness of all activities and progress, the INVERSE contractor shall report the status of the INVERSE program in a Monthly Status Report as described in CDRL TBD.

To supplement the written CDRLs, the INVERSE contractor shall conduct quarterly Program

Management Reviews (PMRs) as prescribed in CDRL TBD until on-line data repository is completed. As required, the INVERSE contractor shall conduct Technical Interchange Meetings related to the performance of the INVERSE contract. The INVERSE contractor shall prepare an agenda in accordance with CDRL TBD for all meetings, conferences, and comparable forums that they conduct. The INVERSE contractor shall also prepare minutes in accordance with

CDRL TBD from all meetings, conferences, and comparable forums that they conduct.

In conjunction with performance-based incentives that may be defined under the INVERSE contract for a period of time, most likely in the beginning of the contract, the INVERSE contractor shall report the progress of the dispute resolution process to the FAA on monthly basis as prescribed in CDRL TBD. The purpose of the INVERSE Performance report is to document the INVERSE contractor’s performance in identifying discrepancies and resolving them.

C.3 ESTABLISH AND MAINTAIN DATA REPOSITORY AND REPORT GENERATION CAPABILITY

C.3.1 ESTABLISH REPOSITORY FOR INVERSE DATA AND REPORT GENERATION CAPABILITY

The INVERSE contractor shall establish a repository of all order, invoice, and financial data received from the government (or its designee) to support the performance of the work elements described in this Statement of Work. The INVERSE contractor also shall store within the repository all data produced to satisfy the reporting requirements specified in this SOW (referred to as INVERSE-generated data).

The INVERSE contractor shall establish the capability for the automated generation all CDRLs that are designated to be delivered on-line.

The INVERSE contractor shall provide authorized users with on-line access to the data repository so that data stored within repository is available to users per the specifications contained in the INVERSE Functional Specification (Future Attachment). The INVERSE contractor shall provide authorized users with the ability to browse and query the data repository and obtain pre-defined and ad hoc reports.

Users accessing the data repository will be geographically dispersed and will include both FAA employees and its support contractors. If any software other than a web page browser and

Microsoft Office applications is required on users’ computers for accessing and using the on-line data repository, the INVERSE contractor shall provide an installation utility to enable FAA designees to install the software on user workstations. The INVERSE contractor shall maintain any associated licenses required by the developer of software used by the INVERSE contractor in providing the on-line data repository and any software provided to users of the on-line data repository by the INVERSE contractor.

The INVERSE contractor shall control access to the data stored in the repository and protect its integrity in accordance with the security requirements defined in the INVERSE Specification and provide monthly a recurring list of users, both new and removed via CDRL.

The efforts to customize existing tools to establish the data repository and meet the FAA’s requirements for on-line data access, report generation, and data analysis capabilities are covered under CLIN 0001. The combination of tools provided for Government use and tools used solely on an internal basis by the INVERSE contractor is referred to as the INVERSE tool suite.

The INVERSE contractor shall conduct one or more system-level reviews of the INVERSE tool suite so that the FAA may assess:

(1) whether input data are interpreted and manipulated properly,

(2) readability of data and report presentation formats,

(3) user-friendliness of tools provided for Government use, and

(4) overall compliance with requirements.

The INVERSE contractor shall provide a System-Level Review Data Package to the FAA in accordance with CDRL TBD. The number of reviews and the timeframe for the review(s) relative to the INVERSE Contract Award date are to be proposed (TBP). The INVERSE contractor shall test the tool suite to demonstrate its compliance with the requirements defined in the INVERSE Functional Specification (Future Attachment). The testing of the tool suite may be witnessed by the Government. Test results shall be supplied to the Government in CDRL

TBD (regardless of whether the tests are witnessed by the government). The tool suite will be deemed ready for use upon approval of the final submission of CDRL TBD.

C.3.2 MAINTAIN INVERSE DATA REPOSITORY

C.3.2.1 Data Storage

The INVERSE contractor shall maintain within the repository all order, invoice, and financial data received from the government (or its designee) to support the performance of the work elements described in this Statement of Work. In addition, the INVERSE contractor shall maintain all INVERSE generated data produced to satisfy the reporting requirements specified in this SOW. The INVERSE contractor shall maintain the complete FENS and GSA/EIS program history of all service orders, invoice charges, discrepancies, and payment information per the data storage requirements listed in the INVERSE Functional Specification. FENS and GSA/EIS data must be segregated in a manner that allows separate or combined access to the data based on government direction.

C.3.2.2 Data Accessibility

The INVERSE Functional Specification in Future J attachment allows for the data repository to be partitioned into an on-line portion and an off-line archive. The INVERSE contractor shall make all INVERSE data accessible to authorized users in accordance the timeliness of data requirements defined in the INVERSE Functional Specification and based on users access to

FENS, GSA/EIS or both. The INVERSE contractor also shall establish a back-up data repository that can be accessed by users within 2 business days of the unavailability of the primary data repository.

The INVERSE contractor shall provide the facilities where the on-line data repository, the off-line archive, and the back-up data repository reside.

C.3.2.3 Maintenance of User Accounts

The INVERSE contractor shall manage user accounts for the duration of the contract. The

INVERSE contractor shall establish accounts for new users within one week of receiving a request for a new user account. The INVERSE contractor shall maintain user passwords and notify users when passwords are due to be updated to meet the security requirements specified in future J attachment. The INVERSE contractor shall close user accounts within 2 business days of receiving a request to close an account.

C.3.2.4 Upgrade the INVERSE Data Repository and Report Generation Capability

As ordered, the INVERSE contractor shall upgrade the INVERSE data repository and report generation capability in the event that it becomes necessary to modify existing capabilities, add new capabilities, accommodate additions and changes to the data stored within the repository, or make other upgrades as defined by the FAA. When changes are made to the INVERSE data repository and report generation capability, the INVERSE contractor shall perform regression testing and document the results in a revised delivery of CDRL TBD.

C.3.3 USER INSTRUCTION FOR ON-LINE ACCESS TO THE DATA REPOSITORY

As ordered by the FAA, the INVERSE contractor shall provide instruction on how to access the on-line portion of the data repository, define and submit queries, view data and reports, tailor output formats, and download data. Each instruction session shall be no longer than 4 hours in length and shall be conducted at a Government-specified facility. Each instruction session will have a maximum of 12 students. The contractor shall provide, in contractor format, an instruction manual (CDRL TBD) for each student in each instruction session.

If this is a capability that you currently provide or have provided in the past, please identify the specific systems, tools, or applications for which user instruction has been provided and indicate the methods of delivery, e.g., “live” instructor-led courses (either in-person or via videoconference), interactive computer-based learning, prerecorded videos (non-interactive), etc.

C.4 INVOICE REVIEW AND RECONCILIATION

The INVERSE contractor shall review all invoices submitted by the FENS and GSA/EIS vendor for accuracy and consistency with the ordered services. The FENS and GSA/EIS invoice data will be made available to the INVERSE contractor in a commercially available electronic format.

The INVERSE contractor shall obtain the FENS invoice data from the associated online portals of FENS and GSA/EIS. All service order information required to perform the invoice review will be made available to the INVERSE contractor by the FAA. In performing the invoice review and reconciliation process, the INVERSE contractor shall follow the business rules defined by the FAA.

The following subsections further elaborate upon the actions required on the part of the

INVERSE contractor when reviewing and reconciling invoices.

C.4.1 CONSISTENCY WITH CLIN LIST AND PRICING DATA

Invoices will be submitted by the FENS and GSA/EIS vendors monthly for all delivered services. The INVERSE contractor shall review each invoice to ensure that it matches the

FAA’s order for each service in terms of the quantities and types of CLINs. Multiple service order numbers (SONs) may be associated with a particular service based on revisions of that service. The INVERSE contractor shall confirm that all invoiced CLINs reflect the cumulative effect of all associated SONs.

The INVERSE contractor’s review shall focus upon CLINs for telecommunications services.

The INVERSE contractor shall compute subtotals for all other CLINs priced on fixed price

Support Services, Time and Materials (T&M) basis and cost-plus fixed fee (CPFF) basis, but no determination by the INVERSE contractor as to the validity of the charges is required.

For CLINs defined as within scope, the INVERSE contractor shall review each invoice to ensure that the charges on an invoice are consistent with the prices in effect when the service was rendered. CLINs for FENS and GSA/EIS telecommunications services may be firm fixed price

(FFP), usage sensitive, or mileage based. For usage sensitive CLINs, the FAA will define thresholds so that the INVERSE Contractor can identify when usage was not within the expected range.

C.4.2 REVIEW OF NON-CLIN ITEMS

The INVERSE contractor shall review items listed on invoices for which there are no CLINs.

These items may include, but are not necessarily limited to:

(1) taxes;

(2) surcharges;

(3) pre-subscribed interexchange carrier charges (PICCs); and

(4) universal service fees (USFs);

The INVERSE Contractor shall identify any instances where the amounts are inappropriate or not properly applied.

C.4.3 CONFIRMATION OF SERVICE CREDITS AND BILLING ADJUSTMENTS

Under the FENS and GSA/EIS contract, the FAA may receive credits from the vendors as a result of service outages. The outages and credits will be associated with an individual service.

The FAA will provide the INVERSE contractor with the information required to determine when a credit is due.

In addition to service outage credits, the FAA may be due billing adjustments as a result of the invoice review and discrepancy resolution process. As part of the invoice review process, the

INVERSE contractor shall determine whether the proper credits and billing adjustments were received. If not, the INVERSE contractor shall reconcile the discrepancy in the same manner as other billing errors.

The FENS and GSA/EIS vendors are required to provide the FAA with credits as a function of the applicable monthly recurring charges if the service due date is missed. The FENS vendor is deemed to have missed the service due date if the service acceptance occurs after the service due date cited in the service order. The GSA/EIS Vendor credit schedule has not yet been determined but may be implemented in the future. The INVERSE contractor shall identify these instances based upon the service due dates and actual service acceptance dates provided by the

FAA, calculate the amount of the credit due to the FAA, and confirm that it is properly reflected on the FENS or GSA/EIS invoice for all affected CLINs.

C.4.4 ACCURACY OF BILLING PERIOD

The INVERSE contractor shall also review each invoice to ensure that any prorating of costs for any individual service order was done in an accurate manner in accordance with the business rules defined in future J attachment. For new service orders with recurring costs, the INVERSE contractor shall ensure that the billing of the monthly recurring charges did not start prior to the

FAA’s acceptance date for the service. In the same manner, when a service is being discontinued, the INVERSE contractor shall confirm that billing did not continue beyond the date that the service was directed to be discontinued.

C.4.5 IDENTIFICATION OF INVOICE DISCREPANCIES

The INVERSE contractor shall identify all invoice discrepancies outside the range of the thresholds listed in Table C.4-1. The thresholds are to be applied to the difference of the invoiced price and the CLIN price.

Table C.4-1 Potential Thresholds for What Constitutes an Invoice Discrepancy

Invoice Item THRESHOLD

Fixed price CLIN’s 0%

Usage-based CLIN’s + 10%

Mileage-based CLINs + 10%

Service Billing Date 0%

Credits, i.e. appropriate credits not shown, incorrect credit value or no credit when credit was due

0%

Adjustments 0%

Taxes, USFs, and PICCs + 15%

CLINs are billed up to an accuracy of $0.000001 depending on the CLIN. A threshold of 0% implies that dollar amount at the unit level on the invoice must identically match the CLIN price.

The INVERSE contractor shall categorize all invoice discrepancies based upon whether they appear to be administrative errors or whether further investigation with the vendor is required.

Categories of discrepancies may include (but are not necessarily limited to) those listed in Table

C.4-2.

Table C.4-2 Categories of Invoice Discrepancies

Administrative Resolve with Vendor

Computational error Usage not within projected range

Incorrect fixed unit cost applied Service order number not recognized

Incorrect quantity CLIN not listed on service order

Incorrect mileage Credit not received

Billing started before service acceptance date

Billing continued after service discontinuance date

The INVERSE contractor shall assign a unique identification number to each invoice discrepancy and a code indicating the type of discrepancy. The INVERSE contractor shall provide an itemized listing of all discrepancies to the FAA and the FENS or GSA/EIS vendor.

When computing the net amount of an invoice to be paid, the INVERSE vendor shall deduct the total value of discrepancies categorized as administrative and discrepancies resolved with the vendor since the previous invoice. The net amount to be paid shall be identified in the Invoice

Certification Document in accordance with CDRL TBD. The INVERSE contractor shall identify all items in the “Resolve with Vendor” category as Disputed Payment (DP) and when the dispute is resolved, the INVERSE contractor shall reflect the associated adjustments in the next delivery of the Invoice Certification Document.

To support the payment provisions of the FENS and GSA/EIS contracts, the INVERSE contractor shall provide the Invoice Certification Document to the FAA no later than 20 days after the date that the invoice is made available to the INVERSE contractor.

The requirements associated with the discrepancy resolution process are described in the next section.

C.4.6 DISCREPANCY RESOLUTION

Along with notifying the FAA, the INVERSE contractor shall be responsible for notifying the

FENS and GSA/EIS vendors of all billing discrepancies identified during the invoice review process. The INVERSE contractor shall be responsible for coordinating with the vendor and working to resolve all discrepancies. The INVERSE contractor shall provide an itemized listing of all discrepancies in accordance with CDRL TBD. The INVERSE contractor shall provide the

FAA with a list of all discrepancies, regardless of type, that are not resolved within two billing cycles. The FAA will take final action to resolve discrepancies that remain in dispute after three billing cycles. The FAA will notify the INVERSE contractor of the outcome of discrepancies resolved by the FAA.

C.5 PAYMENT RECONCILIATION

On a monthly basis, the FAA will provide the INVERSE contractor with the detailed payment record of ACCs used on each invoice. The payment record will be in hardcopy format delivered via PDF. The INVERSE contractor shall compare the payment record with the data compiled in the Invoice Certification Document (CDRL TBD) to ensure that charges were expensed to the appropriate ACCs. The INVERSE contractor shall verify that the proper delivery order and delivery order modification numbers were cited on the service order and the invoice. The

INVERSE contractor shall identify all discrepancies to the FAA and shall provide the FAA with the supporting data required to reconcile the accounts in accordance with CDRL TBD. The

INVERSE contractor also shall conduct a follow-up review of ACCs to ensure that any required adjustments have been made based upon previously identified discrepancies. The INVERSE shall include its findings of the follow-up review in its monthly delivery of CDRL TBD.

When there are multiple ACCs associated with a particular service order, the FAA will provide the INVERSE contractor with the payment rules for distributing the costs among the ACCs. As part of the account review, the INVERSE contractor shall identify all instances where the payment rules were not followed.

If an ACC is used to pay non-Vendor related expenses as well as Vendor charges, the FAA may elect to provide that information to the INVERSE contractor. In those instances, the INVERSE contractor shall provide the FAA with a roll-up of the total expenses and a breakdown of the portion that were Vendor-related and non-Vendor related. The INVERSE contractor will not be responsible for validating non-Vendor related expenses.

C.6 BUDGET TRACKING AND ANALYSIS

The INVERSE contractor shall provide the FAA with the capability to track actual Vendor costs against the amounts budgeted. To facilitate this process, the FAA will provide the INVERSE contractor with funding source data associated with individual Vendor service orders. The information may include (and is not necessarily limited to), delivery order modifications, organization codes, ACCs and their components (CAF, CCC, JON), types of funds (R,E, & D, F&E, and OPS). The INVERSE contractor shall provide the FAA the ability to view cost itemizations and roll-ups for each of these designations.

For each service order, the INVERSE contractor shall track the actual expensed charges against the amount of funds obligated by ACC. Upon the first indication of the potential for a shortfall of funds, the INVERSE contractor shall notify the FAA. The INVERSE contractor shall provide a summary report of actual versus obligated costs in accordance with CDRL TBD. The report shall reflect the most recent invoice data that has been reconciled.

The FAA has a requirement to project its OPS Funding requirements for up to two fiscal years in advance based upon the transition of costs from F&E funding accounts. This budgeting process is referred to as the “NAS Plan Hand-off.” The INVERSE contractor shall support the NAS Plan

Hand-off process by identifying all OPS funding requirements down to the level of an individual service order. In accordance with CDRL TBD, the INVERSE contractor shall identify funding requirements by service and service order number along with the date that the NAS Plan hand-off will occur. In addition, the INVERSE contractor shall aggregate the OPS funding requirements for a fiscal year by program, Line of Business (LOB), Service Area, PDC/SVC, Location Identifier (LID), Facility Code (FAC), and Availability level within CDRL TBD.

C.7 DATA TRACKING AND ANALYSIS

The INVERSE contractor shall analyze all data within the INVERSE database to identify trends, cost drivers, and future budget requirements. The INVERSE contractor shall provide the FAA with the ability to view, sort, and filter the data as described in CDRL TBD for Data Tracking and Analysis Reports.

The INVERSE contractor shall provide cost tracking reports based upon the actual amounts paid on invoices taking into account any credits or adjustments that have been applied. For all tracking reports on cost and usage data, the INVERSE contractor shall provide the FAA with capability to designate:

(1) the resolution of the data analysis indicating whether statistics should be compiled on a daily, monthly, or yearly basis; for individual services or specific categories of services;

and other subsets and groupings that may be suggested by the INVERSE contractor.

(2) the interval for the summary, i.e., monthly, by fiscal year, from inception of billing, the most recent user-specified number of months, and other intervals that may be suggested by the INVERSE contractor.

The INVERSE contractor also shall provide the FAA with the capability to project costs and usage for future time periods.

For usage-based CLINs that have been in-service for more than three months, the INVERSE contractor shall provide the FAA with the capability to specify a percentage threshold (e.g., +15%) and identify instances where usage in a given month exceeds the previous month’s level by an amount outside the threshold range.

C.8 FINANCIAL ANALYSIS

Using cost reference data supplied by the FAA, the INVERSE contractor shall assist the FAA in analyzing the Return on Investment provided by the FENS and GSA/EIS Programs. The Return on Investment calculation will consider all charges associated with implementing a service requirement on the FENS and GSA/EIS network and the differences between the recurring charges from the Vendor and the current service provider at the time of the transition. In the case where a requirement did not exist prior to the transition, the reference cost data will represent a projection of what the cost would have been under predecessor program. The

INVERSE contractor shall document the comparison of FTI actual costs to the reference cost data according to CDRL TBD.

C.9 REPORT GENERATION

The INVERSE contractor shall provide the FAA with on-line access to all report generation capabilities. Reports that are to follow a prescribed format are identified in future J attachment and the associated Data Item Descriptions (DIDs) are provided in future J attachment. With respect to reports described in this SOW for which there is no CDRL, the INVERSE contractor shall provide the FAA with an on-line capability to define the format of a report and to generate the report on an as needed basis. The INVERSE contractor shall ensure that the data contained in on-line reports reflect the most current invoice and accounting data available.

The INVERSE contractor shall ensure that all reports are viewable on-line and capable of being printed on 8½ X 11 inch paper in a font no less than 8 points in size. In addition, the INVERSE contractor shall provide the FAA with the ability to download any report.

C.10 SECURITY MANAGEMENT

The Contractor is responsible for managing and conducting all activities necessary to obtain the security authorization of Contractor-provided infrastructure and services as required by FAA

Order 1370.121, FAA Information Security and Privacy Program & Policy, Chapter 2, Section

5.4. The Government will authorize Contractor-provided services and capabilities prior to operation in the NAS. The Government will conduct independent security assessments and report on the security posture through testing and evaluating compliance with security requirements to secure the NAS and meeting Federal Information Security Management Act

(FISMA) security authorization reporting requirements.

C.11 OTHER PROGRAMMATIC AND TECHNICAL SUPPORT

The INVERSE contractor shall provide program management and technical personnel at meetings and conferences when ordered by the Government. The types of meetings and conferences may include: The Contractor is asked to propose a single FP CLIN per person per trip that will be ordered up Government request to travel.

(1) Program reviews;

(2) Technical Interchange Meetings related to the FENS and GSA/EIS Programs and other

FAA Programs as deemed appropriate by the FAA.

When ordered by the government, the INVERSE contractor shall document the results of each

Technical Interchange Meeting in accordance with (CDRL TBD).

In addition, the INVERSE contractor shall provide personnel to support other tasks that will be defined on an as-needed basis.