Atch_1_-_IDIQ_PWS.pdf

RFP HTC711-18-R-D005 Attachment 1

PERFORMANCE WORK STATEMENT

Third Party Payment System ID/IQ

25 May 2018

1.0. DESCRIPTION OF SERVICES

The Third Party Payment System (TPPS) requirement is to provide an Electronic Transportation Bill Payment Environment (ETBPE) for the Department of Defense (DoD) and other federal agencies. For purposes of this requirement, TPPS is synonymous with ETBPE.

1.1. OBJECTIVE

The objective of this contract is to provide a commercially available web-based service that automates and integrates the entire audit, approval and payment cycle for transportation related expenses. This service will allow federal agencies and their Transportation Service Providers (TSPs) to conduct business through a single portal, creating a full audit trail that ensures compliance with policies and regulatory requirements, as well as timely and accurate payments.

1.2. SCOPE

1.2.1. This Performance Work Statement (PWS) defines the general tasks to be performed under the TPPS Indefinite Delivery/Indefinite Quantity (ID/IQ) contract.

1.2.2. The contractor shall have a fundamental understanding of DoD and other federal agency transportation and distribution management processes, as well as related regulations and procedures. The contractor shall have an understanding of the various federal agency distribution process missions, policies and procedures, regulations, documentation, and associated lifecycle support requirements.

1.2.3. The TPPS requirement is Covered Defense Information (CDI) as defined in DFARS 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident. CDI means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category-list.html that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Government-wide policies. The TPPS requirement CUI Registry identifies Electronic Funds Transfer pursuant to 48 CFR 32.1104.

1.2.4. The TPPS ID/IQ contract will serve as a vehicle to provide support for the DoD and other federal agencies.

1.2.5. General Description. The contractor shall provide TPPS services for the DoD and any other federal agencies that issue a task order under this ID/IQ contract. The following Task Areas define the required contractor services.

Task Area 1: Contract Level Management Task Area 2: Automated Transportation Third Party Payment System Task Area 3: Interfaces Task Area 4: Payment Reports Task Area 5: Bank Payments to Transportation Service Providers Task Area 6: Self-Service Data Analysis Capabilities and Help Desk Task Area 7: Training Task Area 8: System Downtime/Scheduled Maintenance Task Area 9: Data Storage Task Area 10: System Management Change Requests and Testing Task Area 11: Disaster Recovery Plan Task Area 12: Monthly Processing Fee Percentage Task Area 13: Early Payment Incentive Task Area 14: Audit Readiness http://www.archives.gov/cui/registry/category-list.html

1.3. SPECIFIC TASKS

Throughout this PWS all references to Contracting Officer Representative, (COR) are applicable to both the Primary and Alternate COR.

1.3.1. Task Area 1: - Contract Level Management

1.3.1.1. The contractor shall provide program management for all contractor tasks, personnel resources and costs, and ensure all deliverables meet schedule constraints under this PWS. The contractor shall designate a principle point of contact for technical/engineering issues. The contractor shall provide a Contact Manager and Alternate(s) who will be responsible for the overall effort. The name of the Contract Manager and Alternate(s), who will act for the contractor when the Contract Manager is absent, shall be designated in writing to the COR for each task order no later than (NLT) three business days prior to the planned absence.

1.3.1.2. No contractor personnel will perform any work on this contract that meets the definition of inherently governmental according to FAR Subpart 7.503(c). Contractor personnel will be performing tasks under FAR Subpart 7.503(d); however, contract personnel will be in a supporting role to the Government task lead and will not be in a decision-making role. The Government will be the sole authority for decisions regarding Government requirements and actions. The Government seeks commercial best practices. The contractor may submit recommendations to the Contracting Officer’s Representative (COR) identified on the task order for further action.

1.3.2. Task Area 2: Automated Transportation Third Party Payment System

1.3.2.1. The contractor shall provide an automated transportation TPPS with the following abilities:

• to electronically receive and utilize batch data from Government order, shipment, contract, and accounting management systems based upon standard/commercial electronic format.

• to electronically accept and utilize invoices with event status from Government Approved Freight

Carriers/TSPs based upon a commercial industry standard data set and transmission method.

• to electronically accept and utilize verification and data changes from Government order, shipment, contract, and accounting management systems directly and systematically.

• to reconcile and pay TSPs the amount verified by Government shippers or buyers directly or systematically.

• for Government personnel to access the TPPS via direct system-to-system interface and the Internet for purposes of establishing valid Carrier or TSP relationships and originating, processing and approving electronic payment related transactions.

• for authorized users to enter, edit, and save all bill of lading (BOL) information including, but not limited to, carrier/TSP to be paid, amount to be paid, delivery information, origin, destination, line item detail, appropriation sub-head code, line of accounting (LOA), appropriation code(s), Transportation Account Codes (TAC), and Transportation Control Number (TCN).

• to provide an on-line mechanism to facilitate control and monitor post-payment adjustments that automatically links the adjustment to the original shipment and provides for a detailed record of the reason(s) for adjustment. The TPPS shall automatically link payment information with the underlying shipment or order information to present the user with a single combined view of the transaction and eliminate the need for an additional reconciliation process.

• to capture all appropriation code information relevant to a shipment or order provided by Government order, shipment, contract, and accounting management systems, to be visible and linked to said activity and retained in the TPPS for posting, reporting and analysis purposes.

• to create and submit supplemental payment requests or billing disputes that can be used for any purpose, including, but not limited to, the recovery or adjustment of money associated with transportation over/under payments, interest penalties associated with delayed transaction approvals, and administrative offsets services and supplemental billing and or adjustment to all the afore mentioned categories. These Supplemental Transactions shall be linked in an auditable manner to the original transaction. Unlinked Supplemental Transactions will be allowed in limited, but specified, situations that shall be identified in writing by the COR. The party requesting funds has the obligation of creating and submitting the supplemental payment requests or billing disputes to the receiving party. As an example of acceptable action or activity, upon approval by the receiving party, the contractor shall process the supplemental payment requests or billing disputes by crediting or paying the requesting party and debiting the receiving party. All supplemental transactions, debit or credit, require bilateral approval (approval by the requesting and receiving party) prior to processing by the contractor. In the event that the contractor cannot collect the amount of the approved supplemental payment requests or billing disputes from the receiving party within 60 days, the contractor has the option of reversing the supplemental payment requests or billing disputes transaction.

• for the Government to unilaterally adjust and/or stop payments to the TSP to offset debts. The contractor shall develop with the Government a standard commercial process for redirecting credits resulting from adjusted and/or stopped payments no later than (NLT) 12 months of contract award. The Government will adjust and/or stop payments to the contractor to satisfy any TSP offsets, if the contractor fails to provide the Government with the ability to offset TSP debts within 12 months of contract award.

• to pay carriers/TSP in any foreign currency as requested by the Government and under the terms provided by the Government. Currently, the Government accepts only two foreign currencies, Euros and British Pounds and has no immediate plans to accept additional foreign currencies. However, should the need arise, the contractor shall establish the settlement conversion rate for each transaction, and bill the Government in U.S. Dollars (USD).

• interface with carrier or TSP invoice management systems to receive data with regards to performance and sending payment for successful performance of service. The system shall have the capability to tie cargo movements and costs to a contract number. Carrier or TSP invoice shall include a contract number. The data shall be accurate, timely, reside in a searchable field for reporting purposes, and reflect all transactions history (i.e. price adjustments, offsets) to final cost.

• system shall provide the Government with the capability to grant data access rights

• automatically links payment information with the underlying shipment and or service or order information to present the user with a single combined view of the transaction and eliminate the need for an additional reconciliation process. The contractor shall retain all appropriation code and TAC information relevant to a shipment or order provided by Government order, shipment, contract, and accounting management systems in the TPPS for audit, posting, reporting and analysis purposes.

• capable of supporting the Government processes for audit, transportation payment, reconciliation, working capital/appropriated/non-appropriated funds management interface and that, at a minimum, provides all capabilities and abilities listed in this PWS.

1.3.2.2. In order to comply with regulatory guidance or requirements for the Government, the contractor shall, at the request of the Government, provide applicable reports or data.

1.3.3. Task Area 3: Interfaces

1.3.3.1. The capability must exist to interface with federal agency systems to electronically transmit and receive data with Government TAC, order, shipment, contract, In Transit Visibility (ITV), audit, billing, data analysis, and accounting management systems based upon commercial/industry standard electronic format. The contractor shall maintain specific information delineated in Interface Requirements Specification (IRS) document(s). Each Government Program Management Office (PMO) will maintain detailed file layouts specifying type of data, length of data element, periodicity of transmission, and other appropriate information related to the creation of an efficient interface.

1.3.3.2. The DoD interfaces will utilize the Global Exchange (GEX) maintained by the Defense Automatic Addressing System (DAAS) (or other interfacing exchange system(s) as designated by DoD). GEX is a Value- Added Network (VAN), which is a staging area for sharing files between trading partners. GEX has the capability to transfer data via Secure File Transfer Protocol (sFTP) and HyperText Transfer Protocol-Secure (HTTPS). The transport mechanism used to send and receive information (EDI/XML/UDF data) between the contractor system and the designated Government system is sFTP. The EDI/XML/UDF data, whether it is in the form of EDI/XML 810, 814, 820, 821, 859, 858, 824 or 997 transactions, is encoded in the Request Body as a standard octet-stream.

Other designated Federal Agencies will retain their current interface specifications, specified within their individual task order. Contractor shall provide EDI/XML data to FACTS/Tracker Lite that shows the BOLs received from GFM/CMOS were accepted and processed/posted to the TPPS system as a valid BOL/Order transaction.

1.3.3.3. The communications connectivity for the interface between the contractor system and designated Government system is based on Internet Protocol (IP) Sockets using the public Internet for the packet delivery.

sFTP application layer protocols are used for the transport of the EDI/XML data and the encryption of the data payload(s).

1.3.3.4. Modifications to this interface will be required if any of the following components supporting the interface are changed: (a) Software, (b) Hardware, (c) Communications Infrastructure, (d) Interface Procedures, and (e) Changes to the Format/Content of the Data Transferred. Because modifications to this interface may require extensive changes to the hardware and/or software of the Contractor or Government systems, any modifications must be thoroughly analyzed and coordinated with the Government.

1.3.3.5. Testing and familiarization, the contractor shall allow the Government access to all applicable test environments for 30 days prior to deployment of Government-specific TPPS upgrades. The test region shall have the capability of sending and receiving test data from the GEX test region and the test regions of the Government.

The contractor shall submit an implementation plan for rollout of any future TPPS upgrades with its technical proposal.

1.3.4. Task Area 4: Payment Reports

1.3.4.1. The contractor shall provide a summary account balance report for all accounts as specified on each task order. At a minimum, the report shall display the following fields:

• Account Number

• Account Name

• Statement Closing Date

• Total Debits

• Total Credits

• Total Payments

• Current Balance

• Past Due Balance

1.3.4.2. The contractor shall provide a daily report each business day on the status of account certifications for the Household Goods (HHG), Non-temporary Storage (NTS) and Freight (FRT) platforms. The report shall identify the uncertified accounts by name and number, the cycle date and the uncertified days. The report shall annotate if any charges are in the manual charges section of the monthly summary invoice.

1.3.4.3. The contractor shall submit to the ID/IQ contracting officer, each quarter starting on 01 April 2019, a Quarterly Report providing the following information for each task order:

1) Contract/Task Order Number

2) Agency/Sub-Agency Name

3) Total number of transactions

4) Total dollar value of transactions paid to shipper:

5) Total reimbursable amount, based on processing fee

1.3.5. Task Area 5: Bank Payments to Transportation Service Providers

1.3.5.1. The contractor shall make payment to TSPs within three Government business days upon receipt of a Government approved invoice. Any failure by the contractor to make payment of approved transactions under the terms specified in the TSP agreement shall be resolved between the contractor and the TSP.

1.3.5.2. All payment information shall be automatically linked with the underlying TAC, shipment or order information to present the user with a single combined view of the transaction and eliminate the need for additional reconciliation processing. All appropriation code information relevant to a shipment or order provided by the Government’s shipment or order management systems shall be retained in the TPPS for audit, posting, reporting, billing, and analysis purposes.

1.3.5.3. The contractor shall deliver all summary invoices and reports electronically to each authorized user's desktop via the TPPS. To further streamline the payment accounting process, summary invoices shall summarize charges by LOA and TAC, when provided, and appropriation code. The accounting information displayed in the monthly statement record relies upon Customer input. If the LOA or TAC is not present, then the default LOA shall be summarized in the summary invoice.

1.3.5.4. The contractor shall provide the Government with the capability to grant data access rights, including an automated interface with federal agency accounting systems, to the Government – and their authorized users so that oversight, audit, accounting, and compliance groups can perform their functions within the TPPS – including an automated interface with Government systems.

1.3.6. Task Area 6: Self-Service Data Analysis Capabilities and Help Desk

1.3.6.1. The contractor shall provide users with the capability to conduct a variety of Web-based analysis and reporting tasks. This includes ad-hoc query and reporting with which users can construct and execute custom, line-item detail and summary database queries and reports; and Online Analytical Processing (OLAP, e.g., “information cubes”), which allows users to perform summary-level, multi-dimensional analysis. Users need to be able to save and share reports they have developed on the contractor’s website. They also need a scheduling capability to run a report at recurring dates and times, and the ability to save reports down to their client system as a Microsoft Excel 2013 workbook (.xlsx), Adobe Acrobat Portable Document File (.pdf), delimited text files, XML files, and HTML (e.g., Web report).

1.3.6.2. The contractor shall provide a help desk and functioning toll-free help desk phone number, and web address for same, all to be available from the effective date of the contract, seven days per week, twenty-four hours a day.

1.3.6.3. The contractor shall analyze customer (e.g. the Government, carriers/TSP, etc.) problems and systemic problems within its system and develop solutions to these problems.

1.3.7. Task Area 7: Training

1.3.7.1. The contractor shall provide customized training tools and materials for TSPs and federal agency users.

This task is scoped to include a contractor developed Training Plan. The Training Plan does not constitute the Government’s approval or commitment to hosting a conference/site visit in support of the PWS. The intent of the Training Plan is to identify new opportunities for relaying system training and new system functionality to all users.

The contractor shall conduct training either in-person or virtually. In addition, the contractor shall provide web-based training to Certifying Officers, Service Representatives and Pay Technicians. The training shall include reference guides, system setup, on-site consulting, and project management meetings.

1.3.7.2. Contractor shall not conduct customer site visits outside the purpose of user training in support of any federal agency task order without written coordination and written approval as specified in the task order.

1.3.8. Task Area 8: System Downtime/Scheduled Maintenance

1.3.8.1. System downtime shall not exceed 5% in a given month. The Contractor shall provide a system with at least 98 percent or better reliability. Reliability is defined, as the amount of time the system and or process is available for use by DoD and other designated federal agency users worldwide. The contractor shall report all system downtime to the Government point of contact in accordance with each task order.

1.3.8.2. The contractor shall announce scheduled system maintenance affecting Government users worldwide, at least one week in advance via the most efficient media available. Scheduled downtime shall occur between 0200 hours Eastern Time (ET) on Saturday and 2400 hours ET on Sunday. The contractor shall not schedule downtime outside the aforementioned parameters. Scheduled downtime will not count against the system/process reliability calculation.

1.3.9. Task Area 9: Data Storage

1.3.9.1. The contractor shall be the Government's agent for document repository as it relates to all transactions under the payment system at no cost to the government. A transaction is defined as any record documenting the movement of goods and persons and related payments for the Government. Final payment is defined, as the last payment made on a transaction. Linked eBills must be used for the purpose of determining final payment for related transactions. The contractor shall maintain electronic records of all transactions after final payment in accordance with the disposition schedules in DFAS 5015.2-M, approved by the U.S. National Archives and Records Administration and DoD. Foreign Military Sales (FMS) transactions are subject to alternative retention requirements in accordance with the aforementioned disposition schedules. FMS transactions are identified by Lines of Accounting with a Basic Symbol of 8242. Basic Symbol is the data element, A4 (or A3 in SFIS). The disposition schedules dictate the storage of non-FMS and FMS transactions for 6 years and 10 years, respectively. The COR is responsible for notifying the contractor of any modifications to the disposition schedules. The contractor shall provide online access to data for a minimum of 36 months after the final payment. Archived data shall be available upon request from the COR and shall be provided electronically within five (5) business days of a request unless requested as a result of an audit engagement. Archived data is defined as transactions stored offline based on the final payment after 36 months. The contractor shall store all transaction data for open, closed or inactive accounts at no cost to the Government. See the Audit Readiness section in this document for the audit-related request timeframe.

1.3.9.2. The contractor shall provide all requested information, which includes any transactions housed in its systems that support the contract during the period of performance in an electronic format, at no additional cost to the Government. The contractor shall propose a commercial/standard file format for electronic data delivery. Data shall be delivered in the approved standard format to multiple locations as required by the federal agency. The Government may request non-standard file formats on an annual basis that shall be provided by the contractor at no cost.

1.3.9.3. Additionally, the contractor shall provide a daily feed(s), as specified by the federal agency, containing a copy of all records that make up each transaction, to include linked eBills.

1.3.10. Task Area 10: System Change Management Requests and Testing

1.3.10.1. System Change Management Requests (SCMRs) merely document changes the Government would find beneficial. Implementation of these changes is solely up to the discretion of the contractor and all costs will be borne by the contractor with no guarantee of future Government work if the change(s) are implemented. An SCMR, in part or in whole, does not modify the terms and conditions of the contract/task order and cannot be used as a basis for any claim or other assertion for money or monetary damages by the contractor now or in the future.

1.3.10.2. All SCMRs shall be submitted to the ID/IQ Contracting Officer. The TPPS Council will review the Transportation TPPS SCMRs at the semi-annual TPPS council meetings and submit to the contractor the approved and prioritized SCMRs. The contractor shall then provide a feasibility assessment form according to the Priorities listed below. In addition to the feasibility of the SCMR, the form shall include a description of the proposed contractor solution and an estimated length of completion.

• Priority 1 SCMR within 30 days of receipt.

• Priority 2 SCMR within 60 days of receipt.

• Priority 3 SCMR within 90 days of receipt

• Priority 4 SCMR within 90 days of receipt

• Priority 5 SCMR within 90 days of receipt

1.3.10.3. The contractor shall provide TPPS information needed to process the recommended upgrades through the DoD Services Intranet Environments review, packaging, and certification process. The contractor shall notify the COR prior to making any changes or upgrades to the processes that would affect the customer and require training or updating user documentation. Additionally, notification is required when making changes that affect the technology required to operate the product, such as operating systems or web browser functionality. This notification shall be made through the contractor’s system homepage, by email to PMO offices, and other media as necessary.

1.3.10.4. For the purposes of testing and familiarization, the contractor shall allow DoD access to all applicable test environments for 30 days prior to deployment of Government-specific TPPS upgrades. The test region shall have the capability of sending and receiving test data from the GEX test region and the test regions of DoD. The contractor shall submit an implementation plan for rollout of any future TPPS upgrades with its technical proposal.

1.3.10.5. If there are any changes to the system or interface(s) that will result in a need for additional training or testing, notification and coordination with the COR and Stakeholders is required at least nine months prior to intended deployment. This advanced notice is required to reduce impact to fiscal year cycle planning and to support application integration into DoD Services Intranet Environment.

1.3.11. Task Area 11: Disaster Recovery Plan

The Contractor shall provide a commercial/standard Continuity of Operations Plan.

1.3.12. Task Area 12: Processing Fee

The processing fee for the each task order shall cover all expenses associated with processing a transportation provider’s invoice and shall not exceed the fee established on the ID/IQ contract.

1.3.13. Task Area 13: Early Payment Incentive

1.3.13.1. Each quarter the contractor shall calculate an early payment incentive (EPI) based on the File Turn Rebate Rate on all eligible Net Quarterly Charges Volume to each organization. The calculation will be based on each Organization’s Individual Account Number’s payment performance.

1.3.13.2. The following definitions are only applicable to the Early Payment Incentive addressed within this paragraph.

Term Definition File Turn Equal to the Sum of Daily Balances divided by Sum of

Daily Sales Individual Account Number The specific account to which the Transportation

Service Provider payment will be charged and billed to the government

Net Quarterly Charge Volume Sum of all sales less returns

Organization Federal Agency/Ordering Agency, e.g. DoD Sum of Daily Balances Sum of the outstanding balance for each day of the quarter Sum of Daily Sales Sum of the Net Quarterly Charge Volume for each day of the quarter

1.3.13.3. Determination of File Turn and File Turn Rebate Rate. Each period the contractor shall calculate the EPI.

First, the contractor shall calculate the File Turn for each period, which will then be used to determine the File Turn Rebate Rate for the same period consistent with the grid below.

File Turn File Turn Rebate Rate File Turn File Turn Rebate Rate 30 or greater 0.00000 14 0.00064

29 0.00004 13 0.00068 28 0.00008 12 0.00072 27 0.00012 11 0.00076 26 0.00016 10 0.00080 25 0.00020 9 0.00084 24 0.00024 8 0.00088 23 0.00028 7 0.00092 22 0.00032 6 0.00096 21 0.00036 5 0.00100 20 0.00040 4 0.00104 19 0.00044 3 0.00108 18 0.00048 2 0.00112 17 0.00052 1 0.00116 16 0.00056 0 0.00120 15 0.00060

1.3.13.4. If the File Turn for an Individual Account Number is less than thirty (30) for the period, the Contractor will calculate the EPI Amount. The EPI Amount will equal the File Turn Rebate Rate multiplied by the Individual Account Number Net Quarterly Charge Volume. If the File Turn for the Individual Account Number is equal to thirty (30) or greater, the Individual Account Number will not be eligible for an EPI.

1.3.13.5. EPI Amount = File Turn Basis Points X Individual Account Number Net Quarterly Charge Volume

1.3.13.6. The Contractor shall create and submit to the COR a File Turn Summary report 30 days after the end of each calendar year quarter. The report shall detail each Organization’s qualifying Individual EPI Amount by Account Number. The report shall also include the quarterly File Turn calculation as well as the EPI calculation at the individual account level. The Government will distribute to each Organization a copy of all reports. The Government will review the submitted report and either reject the report or ask for corrections. The Contractor shall submit a Final Report within five business days of receipt of the Government comments.

1.3.13.7. A quarter is defined as:

Q1 – 1 Jan through 31 March Q2 – 1 April through 30 June Q3 – 1 July through 30 September Q4 – 1 October through 31 December

1.3.13.8. The sum of all EPI Amounts for an Organization’s Individual Account Numbers will be disbursed as one single payment to the Organization via ACH or EFT. Each federal agency earned EPI will be sent via Wire Transfer to the federal agencies disbursing office for distribution.

1.3.13.9. The sum of all EPI Amounts will be disbursed to a mutually agreed upon single account. If at any time during the corresponding calendar year an agency, such as DoD, earns an EPI Amount, the COR must fill out an EPI disbursement form for distribution of earnings. The COR will indicate to the contractor on the EPI disbursement form the amount to be disbursed to the federal agency and provide information for the Wire Transfer Addenda to include the Service/Agency Line of Accounting which earnings are being distributed to and the amount be distributed. The COR on the task order must submit the signed disbursement form to the contractor within 90 days of receipt of the EPI Report for transfer from the contractor General Ledger (GL) account to the EPI holding account. EPI Earnings are held in the EPI Account one quarter in arrears to cover the Offsets/Payment of unliquidated, aged invoices.

1.3.13.10. The contractor shall open a ticket within 48 hours of receipt of request to perform transfers from the contractor GL account to the federal agency EPI holding account or disbursements from the federal agency EPI holding account to Federal Agency Disbursing. The contractor shall then have seven (7) calendar days to perform the internal transfer of funds. For requests for disbursements from the federal agency EPI holding account, the contractor shall have 14 calendar days to perform the disbursement.

1.3.13.11. Rounding for purposes of EPI shall use the following methodology: for any calculation, the midpoint of .50 shall determine the direction of rounding. If the derived decimal amount is .50 or less, the number of days shall round down to the nearest whole number. If the decimal is .51 or greater, the amount shall round up to the nearest whole number.

1.3.14. Task Area 14: Audit Readiness

1.3.14.1. The contractor shall cooperate in any data mining, Lean Six Sigma or other audit techniques initiated by the Government.

1.3.14.2. Upon Government request, the contractor shall provide all data, documentation, or evidentiary matter in support of any audits involving the Government within Auditor established timeframes for the request. The contractor shall comply with data/document feeds to Government repositories when requested by the COR.

1.3.14.3. The contractor shall support Standard Financial Information Structure (SFIS), as specified in the task order, by enforcing data integrity validation for appropriated funds in the contractor’s system. The contractor shall support the Government by incorporating the Standard Line of Accounting (SLOA) data set format as part of the SFIS in its systems. The Government shall provide requirements for SFIS and SLOA compliance.

1.3.14.4. The contractor and its system shall comply with the FFMIA as set forth in the Office of Management and Budget (OMB) Circular A-123.

1.3.14.5. The contractor shall conduct a Statement on Standards for Attestation Engagements No. 18 (SSAE), or the current American Institute of CPAs (AICPA) equivalent, on its system with the reporting period and report issuance dates aligned with federal agency audits. The contractor shall conduct meetings with its SSAE No. 18 auditor and the federal agency to provide pertinent information regarding the ongoing annual SSAE No. 18 to include, but not limited to, all additions/modifications/deletions to the Complementary User Entity Controls and Complementary Subservice Organization Controls.

1.3.14.6. The contractor shall implement SCMRs and/or CAPs identified by the Government as a result of any deficiencies with the contractor and its system that could negatively impact a federal agency audit.

1.4. DELIVERABLES

1.4.1. Deliverables will be defined in each task order

1.4.2. ID/IQ Quarterly Report. Starting with Q1 2019, the contractor shall submit, within 14 calendar days after the end of each quarter, a report to the ID/IQ contracting officer providing the following information for each task order:

1) Contract/Task Order Number

2) Agency/Sub-Agency Name

3) Total number of transactions

4) Total dollar value of transactions paid to shipper:

5) Total reimbursable amount, based on processing fee

2.0. SERVICE DELIVERY SUMMARY

A Service Delivery Summary (SDS) will be included in the individual task order.

2.1. Quality Assurance. The Government will evaluate performance of the services listed in the individual task order SDS to determine whether the contractor has met the performance thresholds.

2.2. Performance Deficiency Notification. The Government will employ three types of notification. First Notice, Second Notice, and Corrective Action Request.

2.2.1. First Notification. First notification is used for minor tasks that can be re-performed. It will state “First Notice”.

2.2.2. Second Notification. Second notification is used when the first notice fails to resolve the issue. It will state “Second Notice”.

2.2.3. Corrective Action Request (CAR). A CAR is used when the contractor fails to meet the performance threshold for an SDS item or the First and Second notifications failed to result in corrective action.

2.3. Performance Deficiency Resolution. Contractor shall take immediate action to correct all Government reported deficiencies, and to prevent recurrence of the deficiency.

3.0. GOVERNMENT FURNISHED EQUIPMENT (GFE)/GOVERNMENT FURNISHED INFORMATION

(GFI)

GFE/GFI, if any, will be specified in each individual task order.

4.0. GENERAL INFORMATION

4.1. Ordering Period

This contract will include a six year ordering period: 1 January 2019 through 31 December 2024.

4.2. Place of Performance

Performance will be at the contractor’s site.

4.3. Work Hours

There are no specific work hours. Requirements regarding contractor availability for meetings will be established in the individual task order.

4.4. Processing Fee

The processing fee for each task order shall match the processing fee established in the ID/IQ award.

4.5. Recovery Rate Adjustments

The Recovery Rate percentage addressed in paragraph 6.0. will be re-calculated every fiscal year and may be adjusted by the Government on an annual basis, utilizing guidance published by USTRANSCOM/J8.

4.6. Intellectual Property

The contractor shall own all Intellectual Property rights in the name, system, software, documentation, and related material. Nothing in this PWS shall cause or be construed as a transfer of any Intellectual Property rights to the DoD and other designated Federal Agencies, nor shall it constitute a license to Intellectual Property of the contractor. The DoD and other designated Federal Agencies may not modify, reverse assemble, or decompile the Intellectual Property, nor make derivative works thereof. Data captured through TPPS, however, is proprietary and the exclusive sovereign property of the U.S. Government. The terms of this Section shall survive the termination of this PWS.

4.7. Government-Wide Shut Down

Each year, Congress must pass appropriation bills that provide legal authority to spend or obligate U.S. Treasury Funds. The bills must then be signed into law by the President or become law through a Congressional override of a Presidential veto. It is possible that all of the appropriation bills will not be completed in time for the start of any given fiscal year. A continuing resolution is usually passed to allow the Government to continue to function;

however, in recent years, the Government has been required to “shut down” non-essential functions. In the event of a government-wide shut down, payment to the contractor may be late; however, all billed accounts will be paid with Prompt Payment Act interest upon a budget passing. The contractor shall not deactivate any account in this situation unless otherwise notified in writing by the Contracting Officer or COR for the individual task order.

4.8. Non-Disclosure Agreement (NDA) for Contractor Employees

NDA’s will be identified and addressed on each individual task order.

4.9. Implementation and End of Contract Transition

Cooperative, orderly, and seamless transitions are crucial to the Government’s mission requirements. All Contractor costs associated with implementation shall be borne by the Contractor. Specific tasks related to Implementation and End of Contract Transition will be identified on each individual task order.

5.0. Security

Security items may be further defined in each task order.

6.0. Recovery Rate

6.1. A Recovery Rate shall be applied to revenue of all contract services.

6.2. The contractor shall pay USTRANSCOM a 2.3% Recovery Rate for services performed under this ID/IQ. The contractor shall remit the Recovery Rate in U.S. dollars within 60 calendar days after the end of each semi-annual period. The Recovery Rate equals 2.3% of total revenues received during the period.

6.2.1. The contractor shall provide an email to the contracting officer identifying the semi-annual dollar value (rounded to the nearest whole dollar) of all revenue received under this contract every six months by the end of the month following the end of the previous six months of activity. The dollar value of a sale is the price billed/invoiced to each customer for products and services requested under this contract, and the revenue is the money received by the contractor for payment of those services. If no revenue is received, the contractor shall notify the Contracting Officer.

6.2.2. The contractor shall submit one payment for the semi-annual period within 60 calendar days after the end of the semi-annual period. To ensure that the payment is credited properly, the contractor shall identify the check or electronic transmission as a USTRANSCOM GHS STSS COST Recovery Rate, EEIC 45418, LOA: 97X4930.FD50 6F7 70EA 1000000132 G023Q0 45418 SC84A 387700 F87700" and include the following information: contract number; payment amount(s); and associated period of performance. If the contractor makes payment by check, they shall provide this information on either the check; check stub, or other remittance material.

6.2.3. If paying the Cost Recovery Rate by check, the contractor shall forward the check to the following address:

TWCF DFAS-3877 JAMJA/LI DISB OPS DIRECTORATE

8899 E 56TH STREET

ATTN: 3801 LIMESTONE FIELD SITE INDIANAPOLIS, IN 46249

6.2.4. If paying the Cost Recovery Rate by EFT, Online payment in US dollars at Pay.Gov is available using DFAS Contractor Debt Payment 3801 form as follows:

1. Go to https://www.pay.gov

2. Click 'Find an Agency'

3. Click the letter 'D' for DFAS

4. Click 'Defense (DOD) Defense Finance and Accounting Service (DFAS)

5. Click DFAS Limestone Public Vendor Payment 3801/3877

6. Continue to form

7. Click on form

8. Fill in information

9. Fill in contract number in "TWCF Invoice" field

10. Continue to next page for payment