# COVER PAGE

## CP.1 NOTICE TO OFFERORS OF SUBCONTRACTING PLAN REQUIREMENTS: 552.219-72 (DEC 1995) 519.708(a)

The General Services Administration (GSA) is committed to assuring that
maximum practicable opportunity is provided to small, small
disadvantaged, and women-owned small business concerns to participate in
the performance of this contract consistent with its efficient
performance. GSA expects any subcontracting plan submitted pursuant to
FAR 52.219-9, Small, Small Disadvantaged and Women Owned Small Business
Subcontracting Plan, to reflect this commitment. Consequently, an
offeror, other than a small business concern, before being awarded a
contract exceeding \$500,000 (\$1,000,000 for construction) will be
required to demonstrate that its subcontracting plan represents a
creative and innovative program for involving small, small
disadvantaged, and women-owned small business concerns as subcontractors
in the performance of this contract.

NOTE: See Exhibit 1 for a sample subcontracting plan.

## CP.2 CP-FSS-1-C (APR 1993)

Solicitation No. \*\_\_\_\_\_\_\*

FEDERAL SUPPLY SCHEDULE CONTRACT FOR FLEET, TRAVEL AND PURCHASE CARD
SERVICES

FSC GROUP 7389, 6099 and 6153

PERIOD: November 30, 1998 THROUGH November 29, 2003\
with 5 One-Year Options

ANY INFORMATION THAT MAY BE DESIRED ON THIS PARTICULAR SOLICITATION

CAN BE OBTAINED FROM THE ISSUING OFFICE ADDRESS SHOWN HEREIN.

## CP.3 SIGNIFICANT CHANGES: CP-FSS-2 (OCT 1988)

The attention of the offeror is invited to the following change(s) made
since the issuance of the last solicitation for the supplies/services
covered herein:

1\. This solicitation is for commercial items in accordance with FAR
12.6.

2\. The location of the bid room has changed. The new address is:
General Services Administration, FSS Bid Room, Crystal Mall #4 Room
C-39, 1941 Jefferson Davis Highway, Arlington, VA 22202.

3\. The type of contract has changed. This is no longer a requirements
contract. The Government contemplates awarding an Indefinite
Delivery/Indefinite Quantity (ID/IQ) task order contract under a master
contract approach.

4\. The Fleet Card business line has been added.

5\. Significant program wide changes in the Government's requirements.
Please review this document thoroughly and carefully.

6\. The length of the contract period has dramatically changed.

7\. The scope of work has been expanded.

8\. The GSA travel card will be the only form of card payment required
to be accepted under GSA's City-Pair Program.

## CP.4 NOTICE: REQUESTS FOR EXPLANATION OR INFORMATION: CP‑FSS‑3 (MAR 1996)

Oral or written requests for explanation or information regarding this
solicitation should be directed to:

GSA/FSS/Service Acquisition Center

Support Services Division (FCXC)\
ATTN: Darlena Bikowski or Rebecca Koses

1941 Jefferson Davis Highway, Room 507\
Arlington, VA 22202

Tel: (703) 305-5592 (Ms. Bikowski) or (703) 305-6681 (Ms. Koses)

E-Mail: darlena.bikowski@gsa.gov or rebecca.koses@gsa.gov

IMPORTANT: DO NOT ADDRESS OFFERS, MODIFICATIONS OR WITHDRAWALS TO THE
ABOVE ADDRESS. THE ADDRESS DESIGNATED FOR RECEIPT OF OFFERS IS CONTAINED
ELSEWHERE IN THIS SOLICITATION.

## CP.5 SOLICITATION COPIES: CP-FSS-4-A (MAR 1996)

\(a\) To reduce Government costs, only one copy (either paper copy or
diskette) of this solicitation is provided to addressees on our
bidders\' mailing list. If additional paper copies are required (see
52.212-1, Instructions to Offerors---Commercial Items and its addendum
for number of copies to be submitted), you may reproduce them yourself,
provided they are complete in every respect\*, or you may obtain them
from the address specified below:

GSA/FSS/Service Acquisition Center, Support Services Division\
1941 Jefferson Davis Highway, Room 507\
Arlington, VA 22202

Tel: (703) 305-6681

\(b\) Offerors are strongly urged to use two-sided copying of offers for
submission to GSA.

\* EXCEPTION: Oversized blueprints, drawings, or similar documents which
are incorporated by reference in and attached (folded) to the
solicitation are not required to be duplicated for the purpose of
submitting a duplicate copy of the offer to GSA.

## CP.6 ELECTRONIC DATA INTERCHANGE (EDI) ORDERING: CP-FSS-6 (JAN 1994)514.201‑70(a)

Offerors are advised that the Federal Supply Service is expanding use of
electronic communications to exchange business documents. The Placement
of Orders clause contained in this contract provides that orders may be
placed using Electronic Data Interchange (EDI) procedures.

## CP.7 PAST PERFORMANCE EVALUATION FACTOR: CP‑FSS‑FCXB‑010 (MAR 1996) FSS A/L FC-95-7

Federal Acquisition Regulation (FAR) 15.6 requires that past performance
be an evaluation factor in competitively negotiated contracts over
\$1,000,000. This threshold will decline to \$100,000 by July 1999. Past
performance may be used as a factor in solicitations under \$100,000 at
the discretion the Contracting Officer. Offerors are advised that the
quality of an offeror's past performance, on contracts similar to that
solicited, will be a factor in the award decision for this solicitation.
Further, the Contractor's performance under any contract(s) resulting
from this solicitation may directly impact future contract awards. The
Evaluation of Commercial Items section provides instruction on past
performance information that may be provided by offerors. The methods to
be used in evaluating past performance, as a part of the award
decision(s), are described in the Evaluation of Commercial Items,
paragraph 2, Method of Award (M-FSS-FCXC-\_\_\_) (MAY 1997)).

## CP.8 REMOVAL OF COVER PAGE NOTICE: CP-FSS-30 (APR 1993)

**PLEASE REMOVE THIS COVER PAGE(S) BEFORE SUBMITTING OFFER TO GSA.**

# Standard Form 1449 

**Continuation of Standard Form (SF) 1449:**

Block 10: This acquisition is not set aside for small business.

Block 19: Contract Line Item Numbers (Section B)

**TABLE OF CONTENTS**

COVER PAGE

CP.1 NOTICE TO OFFERORS OF SUBCONTRACTING PLAN REQUIREMENTS: 552.219-72
(DEC 1995)

CP.2 CP-FSS-1-C (APR 1993)

CP.3 SIGNIFICANT CHANGES: CP-FSS-2 (OCT 1988)

CP.4 NOTICE: REQUESTS FOR EXPLANATION OR INFORMATION:
CP‑FSS‑3 (MAR 1996)

CP.5 SOLICITATION COPIES: CP-FSS-4-A (MAR 1996)

CP.6 ELECTRONIC DATA INTERCHANGE (EDI) ORDERING: CP-FSS-6 (JAN 1994)

CP.7 PAST PERFORMANCE EVALUATION FACTOR: CP‑FSS‑FCXB‑010 (MAR 1996)

CP.8 REMOVAL OF COVER PAGE NOTICE: CP-FSS-30 (APR 1993)

Standard Form 1449

*Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued*

B.1 MASTER CONTRACT: B-FSS-FCXC-\_\_\_ (AUG 1996)

B.2 MENU-DRIVEN OPTIONS: B-FSS-FCXC-\_\_\_ (AUG 1996)

B.3 ESTIMATED QUANTITIES: B-FSS-FCXC-\_\_\_ (AUG 1996)

B.4 GUARANTEED MINIMUM: B-FSS-FCXC-\_\_\_ (AUG 1996)

B.5 DEFINITIONS: B-FSS-FCXC-\_\_\_ (MAY 1997)

B.6 FINANCIAL CONSIDERATION TO AGENCIES/ORGANIZATIONS: B-FSS-FCXC-\_\_\_
(MAY 1997)

B.7 PRICING INSTRUCTIONS: B-FSS-FCXC-\_\_\_ (MAY 1997)

B.8 BENCHMARK TASKS: B-FSS-FCXC-\_\_\_ (MAY 1997)

*Schedule of Services, Performance Work Statement (Section C)*

C.1 SCHEDULE OF SERVICES:

C.2 DEFINITIONS:

C.3 SCOPE OF WORK

C.4 AGENCY/ORGANIZATION ELIGIBILITY DETERMINATIONS

C.5 OBJECTIVES

C.6 ELECTRONIC COMMERCE/ELECTRONIC DATA INTERCHANGE (EC/EDI)

C.7 CARD PROGRAM(S) REQUIREMENTS

C.8 MERCHANT ACCEPTANCE

C.9 PROGRAM VOLUME GROWTH AND TECHNOLOGICAL ADVANCES

C.10 QUALITY ASSURANCE

C.11 REPORTING OF CENTRALLY BILLED ACCOUNTS TO CREDIT BUREAUS

C.12 DELINQUENCY CONTROL FOR CENTRALLY BILLED ACCOUNTS

C.13 SECURITY REQUIREMENTS

C.14 SYSTEM BACKUP

C.15 INVESTIGATION ASSISTANCE

C.16 AUDIT ASSISTANCE

C.17 MARKETING AND ADVERTISING

C.18 MASTER CONTRACT NEWSLETTER

C.19 STATEMENT INSERTS

C.20 STATEMENT MESSAGING

C.21 MASTER CONTRACT TRAINING CONFERENCE

C.22 RELEASE OF PROGRAM INFORMATION

C.23 CARD DESIGN AND EMBOSSING

C.24 ACCOUNT NUMBER

C.25 TRAINING REQUIREMENTS

C.26 PERSONNEL:

C.27 START-UP IMPLEMENTATION REQUIREMENTS

C.28 YEAR 2000 COMPLIANCE

C.29 TRANSACTION AUTHORIZATIONS

C.30 AUTHORIZATION CONTROLS

C.31 POSTING OF TRANSACTIONS

C.32 TAX EXEMPT STATUS

C.33 FOREIGN CURRENCY CONVERSION

C.34 PROGRAM AND TRANSACTION DATA

C.35 CENTRALLY BILLED CARD PROGRAM ACCOUNTS:

C.36 SUSPENSION PROCEDURES FOR CENTRALLY BILLED ACCOUNTS

C.37 CANCELLATION PROCEDURES FOR CENTRALLY BILLED ACCOUNTS

C.38 AGENCY REPORTING REQUIREMENTS

C.39 GSA CONTRACTING OFFICE REPORTS

C.40 CUSTOMIZED SERVICES:

C.41 TRANSITION REQUIREMENTS:

C.42 RECORD RETENTION AND RETRIEVAL

C.43 POST CONTRACT REQUIREMENTS

C.44 CARD FEES

C.45 GOVERNMENT-WIDE SHUT DOWN

C.46 LIABILITY FOR CENTRALLY BILLED ACCOUNTS

C.47 VALUE-ADDED PRODUCTS AND SERVICES

*SECTION CA - REQUIREMENTS SPECIFIC TO THE FLEET CARD PROGRAM*

CA.1 BACKGROUND FOR FLEET CARD SERVICES

CA.2 DEFINITIONS:

CA.3 FLEET CARD PROGRAM REQUIREMENTS

CA.4 MERCHANT ACCEPTANCE FOR THE FLEET CARD PROGRAM

CA.5 CARD DESIGN AND EMBOSSING FOR THE FLEET CARD PROGRAM

CA.6 TRAINING REQUIREMENTS FOR THE FLEET CARD PROGRAM

CA.7 AUTHORIZATION CONTROLS FOR THE FLEET CARD PROGRAM

CA.8 TAX EXEMPT STATUS FOR THE FLEET CARD PROGRAM

CA.9 PROGRAM AND TRANSACTION DATA FOR THE FLEET CARD PROGRAM

CA.10 FLEET CARD PROGRAM ACCOUNTS

CA.11 FLEET CARD PROGRAM REPORTING REQUIREMENTS

*SECTION CB - REQUIREMENTS SPECIFIC TO THE TRAVEL CARD PROGRAM*

CB.1 BACKGROUND FOR TRAVEL CARD SERVICES

CB.2 DEFINITIONS:

CB.3 TRAVEL CARD PROGRAM REQUIREMENTS

CB.4 MERCHANT ACCEPTANCE FOR THE TRAVEL CARD PROGRAM

CB.5 CARD DESIGN AND EMBOSSING FOR THE TRAVEL CARD PROGRAM

CB.6 ACCOUNT NUMBER FOR THE TRAVEL CARD PROGRAM

CB.7 TRAINING REQUIREMENTS FOR THE TRAVEL CARD PROGRAM

CB.8 ADDITIONAL START-UP IMPLEMENTATION REQUIREMENTS FOR THE TRAVEL CARD
PROGRAM

CB.9 AUTHORIZATION CONTROLS FOR THE TRAVEL CARD PROGRAM

CB.10 TRAVEL CARD PROGRAM AND TRANSACTION DATA FOR CENTRALLY BILLED
ACCOUNTS

CB.11 TRAVEL CARD PROGRAM CENTRALLY BILLED ACCOUNTS

CB.12 TRAVELERS CHECKS

CB.13 TRAVEL CARD PROGRAM REPORTING REQUIREMENTS

CB.14 TRAVEL CARD PROGRAM AND TRANSACTION DATA FOR INDIVIDUALLY BILLED
ACCOUNTS

CB.15 TRAVEL CARD PROGRAM INDIVIDUALLY BILLED ACCOUNTS

CB.16 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS AND CREDIT BUREAUS

CB.17 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS AND DELINQUENCY CONTROL

CB.18 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNT SUSPENSION PROCEDURES

CB.19 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNT CANCELLATION PROCEDURES

CB.20 LIABILITY FOR INDIVIDUALLY BILLED ACCOUNTS ON THE TRAVEL CARD
PROGRAM

CB.21 LATE FEES ON INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS

CB.22 REINSTATEMENT FEES ON CANCELED INDIVIDUALLY BILLED TRAVEL CARD
ACCOUNTS

CB.23 PER CARD ANNUAL FEES OR PRE-FUNDED CARDS FOR INDIVIDUALLY BILLED
TRAVEL CARD ACCOUNTS

*SECTION CC - REQUIREMENTS SPECIFIC TO THE PURCHASE CARD PROGRAM*

CC.1 BACKGROUND FOR PURCHASE CARD SERVICES

CC.2 DEFINITIONS:

CC.3 PURCHASE CARD PROGRAM REQUIREMENTS

CC.4 MERCHANT ACCEPTANCE FOR THE PURCHASE CARD PROGRAM

CC.5 CARD DESIGN AND EMBOSSING FOR THE PURCHASE CARD PROGRAM

CC.6 TRAINING REQUIREMENTS FOR THE PURCHASE CARD PROGRAM

CC.7 ADDITIONAL START-UP IMPLEMENTATION REQUIREMENTS FOR THE PURCHASE
CARD PROGRAM

CC.8 AUTHORIZATION CONTROLS FOR THE PURCHASE CARD PROGRAM

CC.9 PURCHASE CARD PROGRAM AND TRANSACTION DATA

CC.10 PURCHASE CARD PROGRAM ACCOUNTS

CC.11 BANK CHECKS

CC.12 PURCHASE CARD PROGRAM REPORTING REQUIREMENTS

CONTRACT TERMS AND CONDITIONS\-- COMMERCIAL ITEMS (MAY 1997) 52.212-4

ADDENDUM TO CLAUSE 52.212-4

1\. WOMEN OWNED BUSINESS: 52.204-5 (OCT 1995)

2\. PLACE OF PERFORMANCE: 52.215-20 (APR 1984)

3\. SMALL BUSINESS PROGRAM REPRESENTATION: 52.219-1 (JAN 1997)

4\. OPTION TO EXTEND THE TERM OF THE CONTRACT: 52.217-9 (MAR 1989)

5\. AVAILABILITY OF FUNDS FOR TASK ORDERS: CITC-FCXC-\_\_\_ (MAY 1997)

6\. BANKRUPTCY: (DEVIATION) 52.242-13 (JUL 1995)

7\. AUTHORIZED DEVIATIONS OR VARIATIONS IN CLAUSES: 552.252-6 (DEVIATION
FAR 52.252-6) (JUL 1985)

8\. REQUIREMENTS FOR COST OR PRICING DATA OR INFORMATION OTHER THAN COST
OR PRICING DATA: 52.215-41 (MAR 1997) ALTERNATE IV (OCT 1995)

9\. REQUIREMENTS FOR COST OR PRICING DATA OR INFORMATION OTHER THAN COST
OR PRICING DATA---MODIFICATIONS: 52.215-42 (JAN 1997)
(ALTERNATE IV---JAN 1997)

10\. TYPE OF CONTRACT: 52.216-1 (APR 1984)

11\. INDEFINITE QUANTITY: 52.216-22 (OCT 1995) (VARIATION---OCT 1995)

12\. SINGLE OR MULTIPLE AWARDS: 52.216-27 (OCT 1995)

13\. NOTICE TO THE GOVERNMENT OF LABOR DISPUTES: 52.222-1 (FEB 1997)

14\. INTEREST: 52.232-17 (JUN 1996)

15\. F.O.B. DESTINATION: FSS-FCXB-100 (MAR 1997)

16\. CONTRACT TERMS AND CONDITIONS APPLICABLE TO GSA ACQUISITION OF
COMMERCIAL ITEMS: 552.212-71 (FEB 1996)

17\. CONTRACTOR'S REPORT OF SALES: 552.238-72 (APR 1995)

18\. INDUSTRIAL FUNDING FEE (IFF): CITC-FCXC-\_\_\_ (MAY 1997)

19\. PRICE REDUCTIONS: 552.238-76 (OCT 1994)

20\. MODIFICATIONS (MASTER CONTRACTS): CITC-FCXC-\_\_\_ (MAY 1997)

21\. ORDER LIMITATIONS: CITC-FCXC-\_\_\_ (MAY 1997)

22\. CHANGES---FIXED-PRICE: 52.243-1 (AUG 1987)

23\. SCOPE OF CONTRACT FOR THE FLEET CARD: CITC-FCXC-\_\_\_ (MAY 1997)

24\. SCOPE OF CONTRACT FOR TRAVEL CARD: CITC-FCXC-\_\_\_ (MAY 1997)

24\. SCOPE OF CONTRACT FOR PURCHASE CARD: CITC-FCXC-\_\_\_ (MAY 1997)

26\. DEFAULT TASK ORDERS: CITC-FCXC-\_\_\_ (MAY 1997)

27\. ELECTRONIC COMMERCE\--FACNET: I-FSS-599 (SEP 1995)

28\. INTERPRETATION OF CONTRACT REQUIREMENTS: I-FSS-965 (APR 1984)

29\. ORGANIZATIONAL CONFLICT OF INTEREST: CITC-FCXC-\_\_\_ (MAY 1997)

30\. AUTHORIZED NEGOTIATORS: CITC-FCXC-\_\_\_ (MAY 1997)

31\. CONTRACT ADMINISTRATION PLAN: CITC-FCXC-\_\_\_ (MAY 1997)

32\. GOVERNMENT POINTS OF CONTACT: CITC‑FCXC‑\_\_\_ (MAY 1997)

33\. CONTRACTING OFFICER\'S AUTHORITY: CITC-FCXC-\_\_\_ (MAY 1997)

34\. AGENCY/ORGANIZATION PROGRAM COORDINATOR (A/OPC): CITC‑FCXC-\_\_\_
(MAY 1997)

35\. DESIGNATED BILLING OFFICE (DBO): CITC‑FCXC-\_\_\_ (MAY 1997)

36\. TRANSACTION DISPUTE OFFICE (TDO): CITC‑FCXC-\_\_\_ (MAY 1997)

37\. EC/EDI OFFICE (EO): CITC‑FCXC-\_\_\_ (MAY 1997)

38\. ORDERING: CITC-FCXC-\_\_\_ (MAY 1997)

39\. CARD ACTION TEAMS (CATS): CITC-FCXC-\_\_\_ (MAY 1997)

40\. KICK OFF MEETING: CITC-FCXC-\_\_\_ (MAY 1997)

41\. KEY PERSONNEL: CITC-FCXC-\_\_\_ (MAY 1997)

42\. SERVICE IMPROVEMENTS: H-FSS-FCXC-\_\_\_ (MAY 1997)

43\. MASTER CONTRACT DELIVERABLES REQUIRED: F‑FSS‑FCXC‑\_\_\_ (MAY 1997)

44\. TASK ORDER CONTRACT DELIVERABLES REQUIRED:
F‑FSS‑FCXC‑\_\_\_ (MAY 1997)

45\. CONTRACT PERFORMANCE STANDARDS: F-FSS-FCXC-\_\_\_ (MAY 1997)

46\. TASK ORDER EVALUATION: CITC-FCXC-\_\_\_ (MAY 1997)

47\. MASTER CONTRACT EVALUATION: CITC-FCXC-\_\_\_ (MAY 1997)

48\. PRIVACY ACT NOTIFICATION: 52.224-1 (APR 1984)

49\. PRIVACY ACT: 52.224-2 (APR 1984)

50\. CONTRACTOR REQUEST FOR PAYMENT OF THE GUARANTEED MINIMUM:
CITC-FCXC-\_\_\_ (MAY 1997)

52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR
EXECUTIVE ORDERS---COMMERCIAL ITEMS (AUG 1996) (DEVIATION\--MAY 1996)

INSTRUCTIONS TO OFFERORS SECTION

1\. 52.212-1 INSTRUCTIONS TO OFFERORS\--COMMERCIAL ITEMS (OCT 1995)

2\. INSTRUCTIONS TO OFFERORS: L-FSS-FCXC-\_\_\_ (MAY 1997)

3\. SUBMISSION OF OFFERS IN THE ENGLISH LANGUAGE: 52.214-34 (APR 1991)

4\. SUBMISSION OF OFFERS IN U.S. CURRENCY: 52.214-35 (APR 1991)

5\. PREAWARD ON-SITE EQUAL OPPORTUNITY COMPLIANCE REVIEW: 52.222-24
(APR 1984)

6\. SERVICE OF PROTEST: 52.233-2 (AUG 1996)

7\. PREPROPOSAL CONFERENCE: L-FSS-FCXC-\_\_\_ (MAY 1997)

8\. PERIOD FOR ACCEPTANCE OF OFFERS: L-FSS-FCXC-\_\_\_ (MAY 1997)

9\. INFORMATION COLLECTION REQUIREMENTS: A-FSS-40 (OCT 1988)

10\. AWARD: L-FSS-59 (APR 1984)

10\. BEST AND FINAL OFFERS: L-FSS-FCXC-\_\_\_ (MAY 1997)

11\. CLARIFICATIONS OR AMENDMENTS TO THE SOLICITATION: L‑FSS‑FCXC-\_\_\_
(MAY 1997)

12\. DISPOSITION OF PROPOSALS: L-FSS-FCXC-\_\_\_ (MAY 1997)

13\. ANNOUNCEMENT OF AWARD(S): L-FSS-FCXC-\_\_\_ (MAY 1997)

14\. SUBMISSION OF PROPOSALS: L-FSS-FCXC-\_\_\_ (MAY 1997)

15\. BENCHMARK TASK INSTRUCTIONS: L-FSS-FCXC-\_\_\_ (MAY 1997)

EVALUATION OF COMMERCIAL ITEMS

1\. 52.212-2 EVALUATION\--COMMERCIAL ITEMS

2\. METHOD OF AWARD: M-FSS-FCXC-\_\_\_ (MAY 1997)

3\. EVALUATION CRITERIA: M-FSS-FCXC-\_\_\_ (MAY 1997)

4\. EVALUATION OF TECHNICAL CRITERIA: M‑FSS‑FCXC‑\_\_\_ (MAY 1997)

5\. EVALUATION OF PRICE FOR EACH BUSINESS LINE: M‑FSS‑FCXC‑\_\_\_ (MAY
1997)

6\. PRODUCTIVITY REFUND: M‑FSS‑FCXC‑\_\_\_ (MAY 1997)

7\. BENCHMARK TASK EVALUATION: M‑FSS‑FCXC‑\_\_\_ (MAY 1997)

52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS---COMMERCIAL ITEMS
(JAN 1997) (DEVIATION\--MAY 1996)

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 1 - FLEET CARD SERVICES**

TIER 1 REQUIREMENTS - BASE PERIOD (5-YEARS)

+----------+-------------+---------+----------+-----------+-----------+
| **       | **De        | **Eval  | **Unit   | **Basis   | **E       |
| Contract | scription** | uated** | of**     | Points/** | xtended** |
| Line**   |             |         |          |           |           |
|          |             | **Qua   | *        | **Price** | **Total** |
| **Item** |             | ntity** | *Issue** |           |           |
|          |             |         |          |           |           |
| **       |             | **(Base |          |           |           |
| Number** |             | Pe      |          |           |           |
|          |             | riod)** |          |           |           |
| **       |             |         |          |           |           |
| (CLIN)** |             |         |          |           |           |
+----------+-------------+---------+----------+-----------+-----------+
| BA.0001  | Fleet Card  | \$      | Charge   | Basis     | \$        |
|          |             | 500,000 | Volume   | Points    |           |
+----------+-------------+---------+----------+-----------+-----------+
| \(a\)    | Integrated  | \$125,  | Charge   | Basis     | \$        |
|          | Solution    | 000,000 | Volume   | Points    |           |
+----------+-------------+---------+----------+-----------+-----------+
| \(b\)    | Customized  | 10,400  | Per hour | \$        | \$        |
|          | Services    |         |          |           |           |
|          |             |         |          |           |           |
|          | Programmer  |         |          |           |           |
+----------+-------------+---------+----------+-----------+-----------+

**TABLE 1A - FLEET CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION ONE (1 YEAR PERIOD)

+----------+-------------+--------+----------+-----------+-----------+
| **       | **De        | *      | **Unit   | **Basis   | **E       |
| Contract | scription** | *Evalu | of**     | Points/** | xtended** |
| Line**   |             | ated** |          |           |           |
|          |             |        | *        | **Price** | **Total** |
| **Item** |             | **Quan | *Issue** |           |           |
|          |             | tity** |          |           |           |
| **       |             |        |          |           |           |
| Number** |             | **(Per |          |           |           |
|          |             | Y      |          |           |           |
| **       |             | ear)** |          |           |           |
| (CLIN)** |             |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+
| BA.1001  | Fleet Card  | \$1    | Charge   | Basis     | \$        |
|          |             | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(a\)    | Integrated  | \$25,0 | Charge   | Basis     | \$        |
|          | Solution    | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(b\)    | Customized  | 2,080  | Per hour | \$        | \$        |
|          | Services    |        |          |           |           |
|          |             |        |          |           |           |
|          | Programmer  |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+

**TABLE 1B - FLEET CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION TWO (1 YEAR PERIOD)

+----------+-------------+--------+----------+-----------+-----------+
| **       | **De        | *      | **Unit   | **Basis   | **E       |
| Contract | scription** | *Evalu | of**     | Points/** | xtended** |
| Line**   |             | ated** |          |           |           |
|          |             |        | *        | **Price** | **Total** |
| **Item** |             | **Quan | *Issue** |           |           |
|          |             | tity** |          |           |           |
| **       |             |        |          |           |           |
| Number** |             | **(Per |          |           |           |
|          |             | Y      |          |           |           |
| **       |             | ear)** |          |           |           |
| (CLIN)** |             |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+
| BA.2001  | Fleet Card  | \$1    | Charge   | Basis     | \$        |
|          |             | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(a\)    | Integrated  | \$25,0 | Charge   | Basis     | \$        |
|          | Solution    | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(b\)    | Customized  | 2,080  | Per hour | \$        | \$        |
|          | Services    |        |          |           |           |
|          |             |        |          |           |           |
|          | Programmer  |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 1C - FLEET CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION THREE (1 YEAR PERIOD)

+----------+-------------+--------+----------+-----------+-----------+
| **       | **De        | *      | **Unit   | **Basis   | **E       |
| Contract | scription** | *Evalu | of**     | Points/** | xtended** |
| Line**   |             | ated** |          |           |           |
|          |             |        | *        | **Price** | **Total** |
| **Item** |             | **Quan | *Issue** |           |           |
|          |             | tity** |          |           |           |
| **       |             |        |          |           |           |
| Number** |             | **(Per |          |           |           |
|          |             | Y      |          |           |           |
| **       |             | ear)** |          |           |           |
| (CLIN)** |             |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+
| BA.3001  | Fleet Card  | \$1    | Charge   | Basis     | \$        |
|          |             | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(a\)    | Integrated  | \$25,0 | Charge   | Basis     | \$        |
|          | Solution    | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(b\)    | Customized  | 2,080  | Per hour | \$        | \$        |
|          | Services    |        |          |           |           |
|          |             |        |          |           |           |
|          | Programmer  |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+

**TABLE 1D - FLEET CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION FOUR (1 YEAR PERIOD)

+----------+-------------+--------+----------+-----------+-----------+
| **       | **De        | *      | **Unit   | **Basis   | **E       |
| Contract | scription** | *Evalu | of**     | Points/** | xtended** |
| Line**   |             | ated** |          |           |           |
|          |             |        | *        | **Price** | **Total** |
| **Item** |             | **Quan | *Issue** |           |           |
|          |             | tity** |          |           |           |
| **       |             |        |          |           |           |
| Number** |             | **(Per |          |           |           |
|          |             | Y      |          |           |           |
| **       |             | ear)** |          |           |           |
| (CLIN)** |             |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+
| BA.4001  | Fleet Card  | \$1    | Charge   | Basis     | \$        |
|          |             | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(a\)    | Integrated  | \$25,0 | Charge   | Basis     | \$        |
|          | Solution    | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(b\)    | Customized  | 2,080  | Per hour | \$        | \$        |
|          | Services    |        |          |           |           |
|          |             |        |          |           |           |
|          | Programmer  |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+

**TABLE 1E - FLEET CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION FIVE (1 YEAR PERIOD)

+----------+-------------+--------+----------+-----------+-----------+
| **       | **De        | *      | **Unit   | **Basis   | **E       |
| Contract | scription** | *Evalu | of**     | Points/** | xtended** |
| Line**   |             | ated** |          |           |           |
|          |             |        | *        | **Price** | **Total** |
| **Item** |             | **Quan | *Issue** |           |           |
|          |             | tity** |          |           |           |
| **       |             |        |          |           |           |
| Number** |             | **(Per |          |           |           |
|          |             | Y      |          |           |           |
| **       |             | ear)** |          |           |           |
| (CLIN)** |             |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+
| BA.5001  | Fleet Card  | \$1    | Charge   | Basis     | \$        |
|          |             | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(a\)    | Integrated  | \$25,0 | Charge   | Basis     | \$        |
|          | Solution    | 00,000 | Volume   | Points    |           |
+----------+-------------+--------+----------+-----------+-----------+
| \(b\)    | Customized  | 2,080  | Per hour | \$        | \$        |
|          | Services    |        |          |           |           |
|          |             |        |          |           |           |
|          | Programmer  |        |          |           |           |
+----------+-------------+--------+----------+-----------+-----------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 1F - FLEET CARD SERVICES**

PRODUCTIVITY REFUND OFFERED (as defined in B.5.2)? \[ \] YES \[ \] NO

  --------------------- -------------------------------------------------
  **Amount**            **Terms**

                        
  --------------------- -------------------------------------------------

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 2 - FLEET CARD SERVICES**

TIER 2 REQUIREMENTS - BASE PERIOD (5-YEARS)

+-------+---------------------------+-------------+------------------+
| **Con | **Description**           | **Unit of** | **Price**        |
| tract |                           |             |                  |
| L     |                           | **Issue**   |                  |
| ine** |                           |             |                  |
|       |                           |             |                  |
| **I   |                           |             |                  |
| tem** |                           |             |                  |
|       |                           |             |                  |
| **Num |                           |             |                  |
| ber** |                           |             |                  |
|       |                           |             |                  |
| **(CL |                           |             |                  |
| IN)** |                           |             |                  |
+-------+---------------------------+-------------+------------------+
| BA    | Value-Added               |             |                  |
| .0002 | Products/Services         |             |                  |
+-------+---------------------------+-------------+------------------+
| \(a\) | Additional authorization  | Per         | \$               |
|       | controls                  | service,    |                  |
|       |                           | per card    |                  |
+-------+---------------------------+-------------+------------------+
| \(b\) | Software                  | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(c\) | Stored-Value Card         | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(d\) | Debit Card                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(e\) | ATM Access                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(f\) | Bank Check                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(g\) | Inter/Intra-Agency        | Per         | \$               |
|       | Service                   | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(h\) | Electronic bill payment   | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(i\) | Hybrid Card               | Per card    | \$               |
|       |                           |             |                  |
|       | ROM[^1]                   | Per card    | \$               |
|       |                           |             |                  |
|       | Low (1K)                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (4K)               | Per card    | \$               |
|       |                           |             |                  |
|       | High (12K)                | Per card    | \$               |
|       |                           |             |                  |
|       | RAM[^2]                   | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (128 bytes)        | Per card    | \$               |
|       |                           |             |                  |
|       | High (800 bytes)          | Per card    | \$               |
|       |                           |             |                  |
|       | EPROM[^3]                 | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
|       |                           |             |                  |
|       | EEPROM[^4]                |             |                  |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(j\) | Electronic Purchasing     | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(k\) | Photo ID                  | Per card    | \$               |
+-------+---------------------------+-------------+------------------+
| \(l\) | Convenience services      | Per service | \$               |
|       | (please list)             |             |                  |
+-------+---------------------------+-------------+------------------+
| \(m\) | Card sleeves              | Per sleeve  | \$               |
+-------+---------------------------+-------------+------------------+
| \(n\) | Activation/Deactivation   | Per card    | \$               |
|       | on Demand                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(o\) | Emerging Technology       |             | Determined by    |
|       |                           |             | Task Order       |
+-------+---------------------------+-------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 2A - FLEET CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION ONE (1-YEAR PERIOD)

+-------+---------------------------+-------------+------------------+
| **Con | **Description**           | **Unit of** | **Price**        |
| tract |                           |             |                  |
| L     |                           | **Issue**   |                  |
| ine** |                           |             |                  |
|       |                           |             |                  |
| **I   |                           |             |                  |
| tem** |                           |             |                  |
|       |                           |             |                  |
| **Num |                           |             |                  |
| ber** |                           |             |                  |
|       |                           |             |                  |
| **(CL |                           |             |                  |
| IN)** |                           |             |                  |
+-------+---------------------------+-------------+------------------+
| BA    | Value-Added               |             |                  |
| .1002 | Products/Services         |             |                  |
+-------+---------------------------+-------------+------------------+
| \(a\) | Additional authorization  | Per         | \$               |
|       | controls                  | service,    |                  |
|       |                           | per card    |                  |
+-------+---------------------------+-------------+------------------+
| \(b\) | Software                  | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(c\) | Stored-Value Card         | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(d\) | Debit Card                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(e\) | ATM Access                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(f\) | Bank Check                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(g\) | Inter/Intra-Agency        | Per         | \$               |
|       | Service                   | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(h\) | Electronic bill payment   | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(i\) | Hybrid Card               | Per card    | \$               |
|       |                           |             |                  |
|       | ROM[^5]                   | Per card    | \$               |
|       |                           |             |                  |
|       | Low (1K)                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (4K)               | Per card    | \$               |
|       |                           |             |                  |
|       | High (12K)                | Per card    | \$               |
|       |                           |             |                  |
|       | RAM[^6]                   | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (128 bytes)        | Per card    | \$               |
|       |                           |             |                  |
|       | High (800 bytes)          | Per card    | \$               |
|       |                           |             |                  |
|       | EPROM[^7]                 | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
|       |                           |             |                  |
|       | EEPROM[^8]                |             |                  |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(j\) | Electronic Purchasing     | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(k\) | Photo ID                  | Per card    | \$               |
+-------+---------------------------+-------------+------------------+
| \(l\) | Convenience services      | Per service | \$               |
|       | (please list)             |             |                  |
+-------+---------------------------+-------------+------------------+
| \(m\) | Card sleeves              | Per sleeve  | \$               |
+-------+---------------------------+-------------+------------------+
| \(n\) | Activation/Deactivation   | Per card    | \$               |
|       | on Demand                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(o\) | Emerging Technology       |             | Determined by    |
|       |                           |             | Task Order       |
+-------+---------------------------+-------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 2B - FLEET CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION TWO (1-YEAR PERIOD)

+-------+---------------------------+-------------+------------------+
| **Con | **Description**           | **Unit of** | **Price**        |
| tract |                           |             |                  |
| L     |                           | **Issue**   |                  |
| ine** |                           |             |                  |
|       |                           |             |                  |
| **I   |                           |             |                  |
| tem** |                           |             |                  |
|       |                           |             |                  |
| **Num |                           |             |                  |
| ber** |                           |             |                  |
|       |                           |             |                  |
| **(CL |                           |             |                  |
| IN)** |                           |             |                  |
+-------+---------------------------+-------------+------------------+
| BA    | Value-Added               |             |                  |
| .2002 | Products/Services         |             |                  |
+-------+---------------------------+-------------+------------------+
| \(a\) | Additional authorization  | Per         | \$               |
|       | controls                  | service,    |                  |
|       |                           | per card    |                  |
+-------+---------------------------+-------------+------------------+
| \(b\) | Software                  | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(c\) | Stored-Value Card         | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(d\) | Debit Card                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(e\) | ATM Access                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(f\) | Bank Check                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(g\) | Inter/Intra-Agency        | Per         | \$               |
|       | Service                   | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(h\) | Electronic bill payment   | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(i\) | Hybrid Card               | Per card    | \$               |
|       |                           |             |                  |
|       | ROM[^9]                   | Per card    | \$               |
|       |                           |             |                  |
|       | Low (1K)                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (4K)               | Per card    | \$               |
|       |                           |             |                  |
|       | High (12K)                | Per card    | \$               |
|       |                           |             |                  |
|       | RAM[^10]                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (128 bytes)        | Per card    | \$               |
|       |                           |             |                  |
|       | High (800 bytes)          | Per card    | \$               |
|       |                           |             |                  |
|       | EPROM[^11]                | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
|       |                           |             |                  |
|       | EEPROM[^12]               |             |                  |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(j\) | Electronic Purchasing     | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(k\) | Photo ID                  | Per card    | \$               |
+-------+---------------------------+-------------+------------------+
| \(l\) | Convenience services      | Per service | \$               |
|       | (please list)             |             |                  |
+-------+---------------------------+-------------+------------------+
| \(m\) | Card sleeves              | Per sleeve  | \$               |
+-------+---------------------------+-------------+------------------+
| \(n\) | Activation/Deactivation   | Per card    | \$               |
|       | on Demand                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(o\) | Emerging Technology       |             | Determined by    |
|       |                           |             | Task Order       |
+-------+---------------------------+-------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 2C - FLEET CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION THREE (1-YEAR PERIOD)

+-------+---------------------------+-------------+------------------+
| **Con | **Description**           | **Unit of** | **Price**        |
| tract |                           |             |                  |
| L     |                           | **Issue**   |                  |
| ine** |                           |             |                  |
|       |                           |             |                  |
| **I   |                           |             |                  |
| tem** |                           |             |                  |
|       |                           |             |                  |
| **Num |                           |             |                  |
| ber** |                           |             |                  |
|       |                           |             |                  |
| **(CL |                           |             |                  |
| IN)** |                           |             |                  |
+-------+---------------------------+-------------+------------------+
| BA    | Value-Added               |             |                  |
| .3002 | Products/Services         |             |                  |
+-------+---------------------------+-------------+------------------+
| \(a\) | Additional authorization  | Per         | \$               |
|       | controls                  | service,    |                  |
|       |                           | per card    |                  |
+-------+---------------------------+-------------+------------------+
| \(b\) | Software                  | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(c\) | Stored-Value Card         | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(d\) | Debit Card                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(e\) | ATM Access                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(f\) | Bank Check                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(g\) | Inter/Intra-Agency        | Per         | \$               |
|       | Service                   | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(h\) | Electronic bill payment   | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(i\) | Hybrid Card               | Per card    | \$               |
|       |                           |             |                  |
|       | ROM[^13]                  | Per card    | \$               |
|       |                           |             |                  |
|       | Low (1K)                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (4K)               | Per card    | \$               |
|       |                           |             |                  |
|       | High (12K)                | Per card    | \$               |
|       |                           |             |                  |
|       | RAM[^14]                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (128 bytes)        | Per card    | \$               |
|       |                           |             |                  |
|       | High (800 bytes)          | Per card    | \$               |
|       |                           |             |                  |
|       | EPROM[^15]                | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
|       |                           |             |                  |
|       | EEPROM[^16]               |             |                  |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(j\) | Electronic Purchasing     | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(k\) | Photo ID                  | Per card    | \$               |
+-------+---------------------------+-------------+------------------+
| \(l\) | Convenience services      | Per service | \$               |
|       | (please list)             |             |                  |
+-------+---------------------------+-------------+------------------+
| \(m\) | Card sleeves              | Per sleeve  | \$               |
+-------+---------------------------+-------------+------------------+
| \(n\) | Activation/Deactivation   | Per card    | \$               |
|       | on Demand                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(o\) | Emerging Technology       |             | Determined by    |
|       |                           |             | Task Order       |
+-------+---------------------------+-------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 2D - FLEET CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION FOUR (1-YEAR PERIOD)

+-------+---------------------------+-------------+------------------+
| **Con | **Description**           | **Unit of** | **Price**        |
| tract |                           |             |                  |
| L     |                           | **Issue**   |                  |
| ine** |                           |             |                  |
|       |                           |             |                  |
| **I   |                           |             |                  |
| tem** |                           |             |                  |
|       |                           |             |                  |
| **Num |                           |             |                  |
| ber** |                           |             |                  |
|       |                           |             |                  |
| **(CL |                           |             |                  |
| IN)** |                           |             |                  |
+-------+---------------------------+-------------+------------------+
| BA    | Value-Added               |             |                  |
| .4002 | Products/Services         |             |                  |
+-------+---------------------------+-------------+------------------+
| \(a\) | Additional authorization  | Per         | \$               |
|       | controls                  | service,    |                  |
|       |                           | per card    |                  |
+-------+---------------------------+-------------+------------------+
| \(b\) | Software                  | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(c\) | Stored-Value Card         | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(d\) | Debit Card                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(e\) | ATM Access                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(f\) | Bank Check                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(g\) | Inter/Intra-Agency        | Per         | \$               |
|       | Service                   | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(h\) | Electronic bill payment   | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(i\) | Hybrid Card               | Per card    | \$               |
|       |                           |             |                  |
|       | ROM[^17]                  | Per card    | \$               |
|       |                           |             |                  |
|       | Low (1K)                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (4K)               | Per card    | \$               |
|       |                           |             |                  |
|       | High (12K)                | Per card    | \$               |
|       |                           |             |                  |
|       | RAM[^18]                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (128 bytes)        | Per card    | \$               |
|       |                           |             |                  |
|       | High (800 bytes)          | Per card    | \$               |
|       |                           |             |                  |
|       | EPROM[^19]                | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
|       |                           |             |                  |
|       | EEPROM[^20]               |             |                  |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(j\) | Electronic Purchasing     | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(k\) | Photo ID                  | Per card    | \$               |
+-------+---------------------------+-------------+------------------+
| \(l\) | Convenience services      | Per service | \$               |
|       | (please list)             |             |                  |
+-------+---------------------------+-------------+------------------+
| \(m\) | Card sleeves              | Per sleeve  | \$               |
+-------+---------------------------+-------------+------------------+
| \(n\) | Activation/Deactivation   | Per card    | \$               |
|       | on Demand                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(o\) | Emerging Technology       |             | Determined by    |
|       |                           |             | Task Order       |
+-------+---------------------------+-------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 2E - FLEET CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION FIVE (1-YEAR PERIOD)

+-------+---------------------------+-------------+------------------+
| **Con | **Description**           | **Unit of** | **Price**        |
| tract |                           |             |                  |
| L     |                           | **Issue**   |                  |
| ine** |                           |             |                  |
|       |                           |             |                  |
| **I   |                           |             |                  |
| tem** |                           |             |                  |
|       |                           |             |                  |
| **Num |                           |             |                  |
| ber** |                           |             |                  |
|       |                           |             |                  |
| **(CL |                           |             |                  |
| IN)** |                           |             |                  |
+-------+---------------------------+-------------+------------------+
| BA    | Value-Added               |             |                  |
| .5002 | Products/Services         |             |                  |
+-------+---------------------------+-------------+------------------+
| \(a\) | Additional authorization  | Per         | \$               |
|       | controls                  | service,    |                  |
|       |                           | per card    |                  |
+-------+---------------------------+-------------+------------------+
| \(b\) | Software                  | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(c\) | Stored-Value Card         | Each        | \$               |
+-------+---------------------------+-------------+------------------+
| \(d\) | Debit Card                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(e\) | ATM Access                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(f\) | Bank Check                | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(g\) | Inter/Intra-Agency        | Per         | \$               |
|       | Service                   | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(h\) | Electronic bill payment   | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(i\) | Hybrid Card               | Per card    | \$               |
|       |                           |             |                  |
|       | ROM[^21]                  | Per card    | \$               |
|       |                           |             |                  |
|       | Low (1K)                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (4K)               | Per card    | \$               |
|       |                           |             |                  |
|       | High (12K)                | Per card    | \$               |
|       |                           |             |                  |
|       | RAM[^22]                  | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (128 bytes)        | Per card    | \$               |
|       |                           |             |                  |
|       | High (800 bytes)          | Per card    | \$               |
|       |                           |             |                  |
|       | EPROM[^23]                | Per card    | \$               |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
|       |                           |             |                  |
|       | EEPROM[^24]               |             |                  |
|       |                           |             |                  |
|       | Medium (1K)               |             |                  |
|       |                           |             |                  |
|       | High (8K)                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(j\) | Electronic Purchasing     | Per         | \$               |
|       |                           | transaction |                  |
+-------+---------------------------+-------------+------------------+
| \(k\) | Photo ID                  | Per card    | \$               |
+-------+---------------------------+-------------+------------------+
| \(l\) | Convenience services      | Per service | \$               |
|       | (please list)             |             |                  |
+-------+---------------------------+-------------+------------------+
| \(m\) | Card sleeves              | Per sleeve  | \$               |
+-------+---------------------------+-------------+------------------+
| \(n\) | Activation/Deactivation   | Per card    | \$               |
|       | on Demand                 |             |                  |
+-------+---------------------------+-------------+------------------+
| \(o\) | Emerging Technology       |             | Determined by    |
|       |                           |             | Task Order       |
+-------+---------------------------+-------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 2F - FLEET CARD SERVICES**

QUANTITY DISCOUNT OFFERED ON TIER 2 REQUIREMENTS? \[ \] YES \[ \] NO

  --------------------- -------------------------------------------------
  **Amount**            **Terms**

                        
  --------------------- -------------------------------------------------

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 3 - FLEET CARD SERVICES**

BENCHMARK TASK 2 - BASE PERIOD (5-YEARS) (see Exhibit 3)

+------------------------+------------+---------+---------+----------+
| **Contract Line Item   | **Des      | **Eval  | **Unit  | *        |
| Number (CLIN)**        | cription** | uated** | of**    | *Price** |
|                        |            |         |         |          |
|                        |            | **Qua   | **      |          |
|                        |            | ntity** | Issue** |          |
|                        |            |         |         |          |
|                        |            | **(Base |         |          |
|                        |            | Pe      |         |          |
|                        |            | riod)** |         |          |
+------------------------+------------+---------+---------+----------+
| BA.0003                | Benchmark  |         |         | \$       |
|                        | Task 2     |         |         |          |
+------------------------+------------+---------+---------+----------+

**TABLE 3A - FLEET CARD SERVICES**

BENCHMARK TASK 2 - OPTION ONE (1-YEAR PERIOD) (see Exhibit 3)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BA.1003                | Benchmark  |        |          | \$       |
|                        | Task 2     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 3B - FLEET CARD SERVICES**

BENCHMARK TASK 2 - OPTION TWO (1-YEAR PERIOD) (see Exhibit 3)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BA.2003                | Benchmark  |        |          | \$       |
|                        | Task 2     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 3C - FLEET CARD SERVICES**

BENCHMARK TASK 2 - OPTION THREE (1-YEAR PERIOD) (see Exhibit 3)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BA.3003                | Benchmark  |        |          | \$       |
|                        | Task 2     |        |          |          |
+------------------------+------------+--------+----------+----------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 3D - FLEET CARD SERVICES**

BENCHMARK TASK 2 - OPTION FOUR (1-YEAR PERIOD) (see Exhibit 3)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BA.4003                | Benchmark  |        |          | \$       |
|                        | Task 2     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 3E - FLEET CARD SERVICES**

BENCHMARK TASK 2 - OPTION FOUR (1-YEAR PERIOD) (see Exhibit 3)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BA.5003                | Benchmark  |        |          | \$       |
|                        | Task 2     |        |          |          |
+------------------------+------------+--------+----------+----------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 4 - TRAVEL CARD SERVICES**

TIER 1 REQUIREMENTS - BASE PERIOD (5-YEAR PERIOD)

+--------+-------------+---------+----------+-----------+-----------+
| **Cont | **De        | **Eval  | **Unit   | **Basis   | **E       |
| ract** | scription** | uated** | of**     | Points/** | xtended** |
|        |             |         |          |           |           |
| **Line |             | **Qua   | *        | **Price** | **Total** |
| Item** |             | ntity** | *Issue** |           |           |
|        |             |         |          |           |           |
| **Nu   |             | **(Base |          |           |           |
| mber** |             | Pe      |          |           |           |
|        |             | riod)** |          |           |           |
| **(C   |             |         |          |           |           |
| LIN)** |             |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| B      | Travel Card | \$125,  | Charge   | Basis     | \$        |
| B.0001 |             | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(a\)  | Integrated  | \$125,  | Charge   | Basis     | \$        |
|        | Solution    | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(b\)  | Travelers   | 5,      | Per      | \$        | \$        |
|        | Check       | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(c\)  | ATM Access  | 5,      | Per      | \$        | \$        |
|        |             | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(d\)  | Customized  | 10,400  | Per hour | \$        | \$        |
|        | Services    |         |          |           |           |
|        |             |         |          |           |           |
|        | Programmer  |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+

Per Card Annual Fee for Individually Billed Travel Card Accounts as
described in paragraph CB.23: \$\_\_\_\_\_\_

**TABLE 4A - TRAVEL CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION ONE (1-YEAR PERIOD)

+--------+-------------+---------+----------+-----------+-----------+
| **Cont | **De        | **Eval  | **Unit   | **Basis   | **E       |
| ract** | scription** | uated** | of**     | Points/** | xtended** |
|        |             |         |          |           |           |
| **Line |             | **Qua   | *        | **Price** | **Total** |
| Item** |             | ntity** | *Issue** |           |           |
|        |             |         |          |           |           |
| **Nu   |             | **(Per  |          |           |           |
| mber** |             | Year)** |          |           |           |
|        |             |         |          |           |           |
| **(C   |             |         |          |           |           |
| LIN)** |             |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| B      | Travel Card | \$25,   | Charge   | Basis     | \$        |
| B.1001 |             | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(a\)  | Integrated  | \$25,   | Charge   | Basis     | \$        |
|        | Solution    | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(b\)  | Travelers   | 1,      | Per      | \$        | \$        |
|        | Check       | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(c\)  | ATM Access  | 1,      | Per      | \$        | \$        |
|        |             | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(d\)  | Customized  | 2,080   | Per hour | \$        | \$        |
|        | Services    |         |          |           |           |
|        |             |         |          |           |           |
|        | Programmer  |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+

Per Card Annual Fee for Individually Billed Travel Card Accounts as
described in paragraph CB.23: \$\_\_\_\_\_\_

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 4B - TRAVEL CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION TWO (1-YEAR PERIOD)

+--------+-------------+---------+----------+-----------+-----------+
| **Cont | **De        | **Eval  | **Unit   | **Basis   | **E       |
| ract** | scription** | uated** | of**     | Points/** | xtended** |
|        |             |         |          |           |           |
| **Line |             | **Qua   | *        | **Price** | **Total** |
| Item** |             | ntity** | *Issue** |           |           |
|        |             |         |          |           |           |
| **Nu   |             | **(Per  |          |           |           |
| mber** |             | Year)** |          |           |           |
|        |             |         |          |           |           |
| **(C   |             |         |          |           |           |
| LIN)** |             |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| B      | Travel Card | \$25,   | Charge   | Basis     | \$        |
| B.2001 |             | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(a\)  | Integrated  | \$25,   | Charge   | Basis     | \$        |
|        | Solution    | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(b\)  | Travelers   | 1,      | Per      | \$        | \$        |
|        | Check       | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(c\)  | ATM Access  | 1,      | Per      | \$        | \$        |
|        |             | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(d\)  | Customized  | 2,080   | Per hour | \$        | \$        |
|        | Services    |         |          |           |           |
|        |             |         |          |           |           |
|        | Programmer  |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+

Per Card Annual Fee for Individually Billed Travel Card Accounts as
described in paragraph CB.23: \$\_\_\_\_\_\_

**TABLE 4C - TRAVEL CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION THREE (1-YEAR PERIOD)

+--------+-------------+---------+----------+-----------+-----------+
| **Cont | **De        | **Eval  | **Unit   | **Basis   | **E       |
| ract** | scription** | uated** | of**     | Points/** | xtended** |
|        |             |         |          |           |           |
| **Line |             | **Qua   | *        | **Price** | **Total** |
| Item** |             | ntity** | *Issue** |           |           |
|        |             |         |          |           |           |
| **Nu   |             | **(Per  |          |           |           |
| mber** |             | Year)** |          |           |           |
|        |             |         |          |           |           |
| **(C   |             |         |          |           |           |
| LIN)** |             |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| B      | Travel Card | \$25,   | Charge   | Basis     | \$        |
| B.3001 |             | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(a\)  | Integrated  | \$25,   | Charge   | Basis     | \$        |
|        | Solution    | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(b\)  | Travelers   | 1,      | Per      | \$        | \$        |
|        | Check       | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(c\)  | ATM Access  | 1,      | Per      | \$        | \$        |
|        |             | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(d\)  | Customized  | 2,080   | Per hour | \$        | \$        |
|        | Services    |         |          |           |           |
|        |             |         |          |           |           |
|        | Programmer  |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+

Per Card Annual Fee for Individually Billed Travel Card Accounts as
described in paragraph CB.23: \$\_\_\_\_\_\_

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 4D - TRAVEL CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION FOUR (1-YEAR PERIOD)

+--------+-------------+---------+----------+-----------+-----------+
| **Cont | **De        | **Eval  | **Unit   | **Basis   | **E       |
| ract** | scription** | uated** | of**     | Points/** | xtended** |
|        |             |         |          |           |           |
| **Line |             | **Qua   | *        | **Price** | **Total** |
| Item** |             | ntity** | *Issue** |           |           |
|        |             |         |          |           |           |
| **Nu   |             | **(Per  |          |           |           |
| mber** |             | Year)** |          |           |           |
|        |             |         |          |           |           |
| **(C   |             |         |          |           |           |
| LIN)** |             |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| B      | Travel Card | \$25,   | Charge   | Basis     | \$        |
| B.4001 |             | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(a\)  | Integrated  | \$25,   | Charge   | Basis     | \$        |
|        | Solution    | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(b\)  | Travelers   | 1,      | Per      | \$        | \$        |
|        | Check       | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(c\)  | ATM Access  | 1,      | Per      | \$        | \$        |
|        |             | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(d\)  | Customized  | 2,080   | Per hour | \$        | \$        |
|        | Services    |         |          |           |           |
|        |             |         |          |           |           |
|        | Programmer  |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+

Per Card Annual Fee for Individually Billed Travel Card Accounts as
described in paragraph CB.23: \$\_\_\_\_\_\_

**TABLE 4E - TRAVEL CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION FIVE (1-YEAR PERIOD)

+--------+-------------+---------+----------+-----------+-----------+
| **Cont | **De        | **Eval  | **Unit   | **Basis   | **E       |
| ract** | scription** | uated** | of**     | Points/** | xtended** |
|        |             |         |          |           |           |
| **Line |             | **Qua   | *        | **Price** | **Total** |
| Item** |             | ntity** | *Issue** |           |           |
|        |             |         |          |           |           |
| **Nu   |             | **(Per  |          |           |           |
| mber** |             | Year)** |          |           |           |
|        |             |         |          |           |           |
| **(C   |             |         |          |           |           |
| LIN)** |             |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| B      | Travel Card | \$25,   | Charge   | Basis     | \$        |
| B.5001 |             | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(a\)  | Integrated  | \$25,   | Charge   | Basis     | \$        |
|        | Solution    | 000,000 | Volume   | Points    |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(b\)  | Travelers   | 1,      | Per      | \$        | \$        |
|        | Check       | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(c\)  | ATM Access  | 1,      | Per      | \$        | \$        |
|        |             | 000,000 | tra      |           |           |
|        |             |         | nsaction |           |           |
+--------+-------------+---------+----------+-----------+-----------+
| \(d\)  | Customized  | 2,080   | Per hour | \$        | \$        |
|        | Services    |         |          |           |           |
|        |             |         |          |           |           |
|        | Programmer  |         |          |           |           |
+--------+-------------+---------+----------+-----------+-----------+

Per Card Annual Fee for Individually Billed Travel Card Accounts as
described in paragraph CB.23: \$\_\_\_\_\_\_

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 4F - TRAVEL CARD SERVICES**

PRODUCTIVITY REFUND OFFERED as described in B.5.2? \[ \] YES \[ \] NO

  --------------------- -------------------------------------------------
  **Amount**            **Terms**

                        
  --------------------- -------------------------------------------------

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 5 - TRAVEL CARD SERVICES**

TIER 2 REQUIREMENTS - BASE PERIOD (5-YEARS)

+-------+-------------------------+----------------+------------------+
| **    | **Description**         | **Unit of**    | **Price**        |
| Contr |                         |                |                  |
| act** |                         | **Issue**      |                  |
|       |                         |                |                  |
| *     |                         |                |                  |
| *Line |                         |                |                  |
| I     |                         |                |                  |
| tem** |                         |                |                  |
|       |                         |                |                  |
| **Num |                         |                |                  |
| ber** |                         |                |                  |
|       |                         |                |                  |
| **(CL |                         |                |                  |
| IN)** |                         |                |                  |
+-------+-------------------------+----------------+------------------+
| BB    | Value-Added             |                |                  |
| .0002 | Products/Services       |                |                  |
+-------+-------------------------+----------------+------------------+
| \(a\) | Additional              | Per service,   | \$               |
|       | authorization controls  | per card       |                  |
+-------+-------------------------+----------------+------------------+
| \(b\) | Software                | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(c\) | Stored-Value Card       | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(d\) | Debit Card              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(f\) | Bank Check              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(g\) | Inter/Intra-Agency      | Per            | \$               |
|       | Service                 | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(h\) | Telephone Card Access   | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(i\) | Electronic bill payment | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(j\) | Hybrid Card             | Per card       | \$               |
|       |                         |                |                  |
|       | ROM[^25]                | Per card       | \$               |
|       |                         |                |                  |
|       | Low (1K)                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (4K)             | Per card       | \$               |
|       |                         |                |                  |
|       | High (12K)              | Per card       | \$               |
|       |                         |                |                  |
|       | RAM[^26]                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (128 bytes)      | Per card       | \$               |
|       |                         |                |                  |
|       | High (800 bytes)        | Per card       | \$               |
|       |                         |                |                  |
|       | EPROM[^27]              | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
|       |                         |                |                  |
|       | EEPROM[^28]             |                |                  |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(k\) | Electronic Purchasing   | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(l\) | Photo ID                | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(m\) | Convenience services    | Per service    | \$               |
|       | (please list)           |                |                  |
+-------+-------------------------+----------------+------------------+
| \(n\) | Net Billing             | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(o\) | Card sleeves            | Per sleeve     | \$               |
+-------+-------------------------+----------------+------------------+
| \(p\) | Activation/Deactivation | Per card       | \$               |
|       | on Demand               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(q\) | Emerging Technology     |                | Determined by    |
|       |                         |                | Task Order       |
+-------+-------------------------+----------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 5A - TRAVEL CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION ONE (1-YEAR PERIOD)

+-------+-------------------------+----------------+------------------+
| **    | **Description**         | **Unit of**    | **Price**        |
| Contr |                         |                |                  |
| act** |                         | **Issue**      |                  |
|       |                         |                |                  |
| *     |                         |                |                  |
| *Line |                         |                |                  |
| I     |                         |                |                  |
| tem** |                         |                |                  |
|       |                         |                |                  |
| **Num |                         |                |                  |
| ber** |                         |                |                  |
|       |                         |                |                  |
| **(CL |                         |                |                  |
| IN)** |                         |                |                  |
+-------+-------------------------+----------------+------------------+
| BB    | Value-Added             |                |                  |
| .1002 | Products/Services       |                |                  |
+-------+-------------------------+----------------+------------------+
| \(a\) | Additional              | Per service,   | \$               |
|       | authorization controls  | per card       |                  |
+-------+-------------------------+----------------+------------------+
| \(b\) | Software                | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(c\) | Stored-Value Card       | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(d\) | Debit Card              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(f\) | Bank Check              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(g\) | Inter/Intra-Agency      | Per            | \$               |
|       | Service                 | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(h\) | Telephone Card Access   | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(i\) | Electronic bill payment | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(j\) | Hybrid Card             | Per card       | \$               |
|       |                         |                |                  |
|       | ROM[^29]                | Per card       | \$               |
|       |                         |                |                  |
|       | Low (1K)                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (4K)             | Per card       | \$               |
|       |                         |                |                  |
|       | High (12K)              | Per card       | \$               |
|       |                         |                |                  |
|       | RAM[^30]                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (128 bytes)      | Per card       | \$               |
|       |                         |                |                  |
|       | High (800 bytes)        | Per card       | \$               |
|       |                         |                |                  |
|       | EPROM[^31]              | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
|       |                         |                |                  |
|       | EEPROM[^32]             |                |                  |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(k\) | Electronic Purchasing   | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(l\) | Photo ID                | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(m\) | Convenience services    | Per service    | \$               |
|       | (please list)           |                |                  |
+-------+-------------------------+----------------+------------------+
| \(n\) | Net Billing             | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(o\) | Card sleeves            | Per sleeve     | \$               |
+-------+-------------------------+----------------+------------------+
| \(p\) | Activation/Deactivation | Per card       | \$               |
|       | on Demand               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(q\) | Emerging Technology     |                | Determined by    |
|       |                         |                | Task Order       |
+-------+-------------------------+----------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 5B - TRAVEL CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION TWO (1-YEAR PERIOD)

+-------+-------------------------+----------------+------------------+
| **    | **Description**         | **Unit of**    | **Price**        |
| Contr |                         |                |                  |
| act** |                         | **Issue**      |                  |
|       |                         |                |                  |
| *     |                         |                |                  |
| *Line |                         |                |                  |
| I     |                         |                |                  |
| tem** |                         |                |                  |
|       |                         |                |                  |
| **Num |                         |                |                  |
| ber** |                         |                |                  |
|       |                         |                |                  |
| **(CL |                         |                |                  |
| IN)** |                         |                |                  |
+-------+-------------------------+----------------+------------------+
| BB    | Value-Added             |                |                  |
| .2002 | Products/Services       |                |                  |
+-------+-------------------------+----------------+------------------+
| \(a\) | Additional              | Per service,   | \$               |
|       | authorization controls  | per card       |                  |
+-------+-------------------------+----------------+------------------+
| \(b\) | Software                | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(c\) | Stored-Value Card       | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(d\) | Debit Card              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(f\) | Bank Check              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(g\) | Inter/Intra-Agency      | Per            | \$               |
|       | Service                 | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(h\) | Telephone Card Access   | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(i\) | Electronic bill payment | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(j\) | Hybrid Card             | Per card       | \$               |
|       |                         |                |                  |
|       | ROM[^33]                | Per card       | \$               |
|       |                         |                |                  |
|       | Low (1K)                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (4K)             | Per card       | \$               |
|       |                         |                |                  |
|       | High (12K)              | Per card       | \$               |
|       |                         |                |                  |
|       | RAM[^34]                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (128 bytes)      | Per card       | \$               |
|       |                         |                |                  |
|       | High (800 bytes)        | Per card       | \$               |
|       |                         |                |                  |
|       | EPROM[^35]              | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
|       |                         |                |                  |
|       | EEPROM[^36]             |                |                  |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(k\) | Electronic Purchasing   | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(l\) | Photo ID                | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(m\) | Convenience services    | Per service    | \$               |
|       | (please list)           |                |                  |
+-------+-------------------------+----------------+------------------+
| \(n\) | Net Billing             | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(o\) | Card sleeves            | Per sleeve     | \$               |
+-------+-------------------------+----------------+------------------+
| \(p\) | Activation/Deactivation | Per card       | \$               |
|       | on Demand               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(q\) | Emerging Technology     |                | Determined by    |
|       |                         |                | Task Order       |
+-------+-------------------------+----------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 5C - TRAVEL CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION THREE (1-YEAR PERIOD)

+-------+-------------------------+----------------+------------------+
| **    | **Description**         | **Unit of**    | **Price**        |
| Contr |                         |                |                  |
| act** |                         | **Issue**      |                  |
|       |                         |                |                  |
| *     |                         |                |                  |
| *Line |                         |                |                  |
| I     |                         |                |                  |
| tem** |                         |                |                  |
|       |                         |                |                  |
| **Num |                         |                |                  |
| ber** |                         |                |                  |
|       |                         |                |                  |
| **(CL |                         |                |                  |
| IN)** |                         |                |                  |
+-------+-------------------------+----------------+------------------+
| BB    | Value-Added             |                |                  |
| .3002 | Products/Services       |                |                  |
+-------+-------------------------+----------------+------------------+
| \(a\) | Additional              | Per service,   | \$               |
|       | authorization controls  | per card       |                  |
+-------+-------------------------+----------------+------------------+
| \(b\) | Software                | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(c\) | Stored-Value Card       | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(d\) | Debit Card              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(f\) | Bank Check              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(g\) | Inter/Intra-Agency      | Per            | \$               |
|       | Service                 | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(h\) | Telephone Card Access   | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(i\) | Electronic bill payment | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(j\) | Hybrid Card             | Per card       | \$               |
|       |                         |                |                  |
|       | ROM[^37]                | Per card       | \$               |
|       |                         |                |                  |
|       | Low (1K)                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (4K)             | Per card       | \$               |
|       |                         |                |                  |
|       | High (12K)              | Per card       | \$               |
|       |                         |                |                  |
|       | RAM[^38]                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (128 bytes)      | Per card       | \$               |
|       |                         |                |                  |
|       | High (800 bytes)        | Per card       | \$               |
|       |                         |                |                  |
|       | EPROM[^39]              | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
|       |                         |                |                  |
|       | EEPROM[^40]             |                |                  |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(k\) | Electronic Purchasing   | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(l\) | Photo ID                | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(m\) | Convenience services    | Per service    | \$               |
|       | (please list)           |                |                  |
+-------+-------------------------+----------------+------------------+
| \(n\) | Net Billing             | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(o\) | Card sleeves            | Per sleeve     | \$               |
+-------+-------------------------+----------------+------------------+
| \(p\) | Activation/Deactivation | Per card       | \$               |
|       | on Demand               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(q\) | Emerging Technology     |                | Determined by    |
|       |                         |                | Task Order       |
+-------+-------------------------+----------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 5D - TRAVEL CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION FOUR (1-YEAR PERIOD)

+-------+-------------------------+----------------+------------------+
| **    | **Description**         | **Unit of**    | **Price**        |
| Contr |                         |                |                  |
| act** |                         | **Issue**      |                  |
|       |                         |                |                  |
| *     |                         |                |                  |
| *Line |                         |                |                  |
| I     |                         |                |                  |
| tem** |                         |                |                  |
|       |                         |                |                  |
| **Num |                         |                |                  |
| ber** |                         |                |                  |
|       |                         |                |                  |
| **(CL |                         |                |                  |
| IN)** |                         |                |                  |
+-------+-------------------------+----------------+------------------+
| BB    | Value-Added             |                |                  |
| .4002 | Products/Services       |                |                  |
+-------+-------------------------+----------------+------------------+
| \(a\) | Additional              | Per service,   | \$               |
|       | authorization controls  | per card       |                  |
+-------+-------------------------+----------------+------------------+
| \(b\) | Software                | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(c\) | Stored-Value Card       | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(d\) | Debit Card              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(f\) | Bank Check              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(g\) | Inter/Intra-Agency      | Per            | \$               |
|       | Service                 | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(h\) | Telephone Card Access   | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(i\) | Electronic bill payment | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(j\) | Hybrid Card             | Per card       | \$               |
|       |                         |                |                  |
|       | ROM[^41]                | Per card       | \$               |
|       |                         |                |                  |
|       | Low (1K)                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (4K)             | Per card       | \$               |
|       |                         |                |                  |
|       | High (12K)              | Per card       | \$               |
|       |                         |                |                  |
|       | RAM[^42]                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (128 bytes)      | Per card       | \$               |
|       |                         |                |                  |
|       | High (800 bytes)        | Per card       | \$               |
|       |                         |                |                  |
|       | EPROM[^43]              | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
|       |                         |                |                  |
|       | EEPROM[^44]             |                |                  |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(k\) | Electronic Purchasing   | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(l\) | Photo ID                | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(m\) | Convenience services    | Per service    | \$               |
|       | (please list)           |                |                  |
+-------+-------------------------+----------------+------------------+
| \(n\) | Net Billing             | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(o\) | Card sleeves            | Per sleeve     | \$               |
+-------+-------------------------+----------------+------------------+
| \(p\) | Activation/Deactivation | Per card       | \$               |
|       | on Demand               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(q\) | Emerging Technology     |                | Determined by    |
|       |                         |                | Task Order       |
+-------+-------------------------+----------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 5E - TRAVEL CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION FIVE (1-YEAR PERIOD)

+-------+-------------------------+----------------+------------------+
| **    | **Description**         | **Unit of**    | **Price**        |
| Contr |                         |                |                  |
| act** |                         | **Issue**      |                  |
|       |                         |                |                  |
| *     |                         |                |                  |
| *Line |                         |                |                  |
| I     |                         |                |                  |
| tem** |                         |                |                  |
|       |                         |                |                  |
| **Num |                         |                |                  |
| ber** |                         |                |                  |
|       |                         |                |                  |
| **(CL |                         |                |                  |
| IN)** |                         |                |                  |
+-------+-------------------------+----------------+------------------+
| BB    | Value-Added             |                |                  |
| .5002 | Products/Services       |                |                  |
+-------+-------------------------+----------------+------------------+
| \(a\) | Additional              | Per service,   | \$               |
|       | authorization controls  | per card       |                  |
+-------+-------------------------+----------------+------------------+
| \(b\) | Software                | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(c\) | Stored-Value Card       | Each           | \$               |
+-------+-------------------------+----------------+------------------+
| \(d\) | Debit Card              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(f\) | Bank Check              | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(g\) | Inter/Intra-Agency      | Per            | \$               |
|       | Service                 | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(h\) | Telephone Card Access   | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(i\) | Electronic bill payment | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(j\) | Hybrid Card             | Per card       | \$               |
|       |                         |                |                  |
|       | ROM[^45]                | Per card       | \$               |
|       |                         |                |                  |
|       | Low (1K)                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (4K)             | Per card       | \$               |
|       |                         |                |                  |
|       | High (12K)              | Per card       | \$               |
|       |                         |                |                  |
|       | RAM[^46]                | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (128 bytes)      | Per card       | \$               |
|       |                         |                |                  |
|       | High (800 bytes)        | Per card       | \$               |
|       |                         |                |                  |
|       | EPROM[^47]              | Per card       | \$               |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
|       |                         |                |                  |
|       | EEPROM[^48]             |                |                  |
|       |                         |                |                  |
|       | Medium (1K)             |                |                  |
|       |                         |                |                  |
|       | High (8K)               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(k\) | Electronic Purchasing   | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(l\) | Photo ID                | Per card       | \$               |
+-------+-------------------------+----------------+------------------+
| \(m\) | Convenience services    | Per service    | \$               |
|       | (please list)           |                |                  |
+-------+-------------------------+----------------+------------------+
| \(n\) | Net Billing             | Per            | \$               |
|       |                         | transaction    |                  |
+-------+-------------------------+----------------+------------------+
| \(o\) | Card sleeves            | Per sleeve     | \$               |
+-------+-------------------------+----------------+------------------+
| \(p\) | Activation/Deactivation | Per card       | \$               |
|       | on Demand               |                |                  |
+-------+-------------------------+----------------+------------------+
| \(q\) | Emerging Technology     |                | Determined by    |
|       |                         |                | Task Order       |
+-------+-------------------------+----------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 5F - TRAVEL CARD SERVICES**

QUANTITY DISCOUNT OFFERED ON TIER 2 REQUIREMENTS? \[ \] YES \[ \] NO

  --------------------- -------------------------------------------------
  **Amount**            **Terms**

                        
  --------------------- -------------------------------------------------

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 6 - TRAVEL CARD SERVICES**

BENCHMARK TASK 3 - BASE PERIOD (5-YEARS) (see Exhibit 4)

+----------------------+------------+----------+----------+----------+
| **Contract Line Item | **Des      | **Eva    | **Unit   | *        |
| Number (CLIN)**      | cription** | luated** | of**     | *Price** |
|                      |            |          |          |          |
|                      |            | **Qu     | *        |          |
|                      |            | antity** | *Issue** |          |
|                      |            |          |          |          |
|                      |            | **(Base  |          |          |
|                      |            | P        |          |          |
|                      |            | eriod)** |          |          |
+----------------------+------------+----------+----------+----------+
| BB.0003              | Benchmark  |          |          | \$       |
|                      | Task 3     |          |          |          |
+----------------------+------------+----------+----------+----------+

**TABLE 6A - TRAVEL CARD SERVICES**

BENCHMARK TASK 3 - OPTION ONE (1-YEAR PERIOD) (see Exhibit 4)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BB.1003                | Benchmark  |        |          | \$       |
|                        | Task 3     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 6B - TRAVEL CARD SERVICES**

BENCHMARK TASK 3 - OPTION TWO (1-YEAR PERIOD) (see Exhibit 4)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BB.2003                | Benchmark  |        |          | \$       |
|                        | Task 3     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 6C - TRAVEL CARD SERVICES**

BENCHMARK TASK 3 - OPTION THREE (1-YEAR PERIOD) (see Exhibit 4)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BB.3003                | Benchmark  |        |          | \$       |
|                        | Task 3     |        |          |          |
+------------------------+------------+--------+----------+----------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 6D - TRAVEL CARD SERVICES**

BENCHMARK TASK 3 - OPTION FOUR (1-YEAR PERIOD) (see Exhibit 4)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BB.4003                | Benchmark  |        |          | \$       |
|                        | Task 3     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 6E - TRAVEL CARD SERVICES**

BENCHMARK TASK 3 - OPTION FIVE (1-YEAR PERIOD) (see Exhibit 4)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BB.5003                | Benchmark  |        |          | \$       |
|                        | Task 3     |        |          |          |
+------------------------+------------+--------+----------+----------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 7 - PURCHASE CARD SERVICES**

TIER 1 REQUIREMENTS - BASE PERIOD (5-YEARS)

+-------+-------------+---------+----------+------------+------------+
| **    | **De        | **Eval  | **Unit   | **Basis    | **         |
| Contr | scription** | uated** | of**     | Points/**  | Extended** |
| act** |             |         |          |            |            |
|       |             | **Qua   | *        | **Price**  | **Total**  |
| *     |             | ntity** | *Issue** |            |            |
| *Line |             |         |          |            |            |
| I     |             | **(Base |          |            |            |
| tem** |             | Pe      |          |            |            |
|       |             | riod)** |          |            |            |
| **Num |             |         |          |            |            |
| ber** |             |         |          |            |            |
|       |             |         |          |            |            |
| **(CL |             |         |          |            |            |
| IN)** |             |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+
| BC    | Purchase    | \$125,  | Charge   | Basis      | \$         |
| .0001 | Card        | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(a\) | Integrated  | \$125,  | Charge   | Basis      | \$         |
|       | Solution    | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(b\) | Bank Check  | 5,      | Per      | \$         | \$         |
|       |             | 000,000 | tra      |            |            |
|       |             |         | nsaction |            |            |
+-------+-------------+---------+----------+------------+------------+
| \(c\) | Customized  | 10,400  | Per hour | \$         | \$         |
|       | Services    |         |          |            |            |
|       |             |         |          |            |            |
|       | Programmer  |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+

**TABLE 7A - PURCHASE CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION ONE (1-YEAR PERIOD)

+-------+-------------+---------+----------+------------+------------+
| **    | **De        | **Eval  | **Unit   | **Basis    | **         |
| Contr | scription** | uated** | of**     | Points/**  | Extended** |
| act** |             |         |          |            |            |
|       |             | **Qua   | *        | **Price**  | **Total**  |
| *     |             | ntity** | *Issue** |            |            |
| *Line |             |         |          |            |            |
| I     |             | **(Per  |          |            |            |
| tem** |             | Year)** |          |            |            |
|       |             |         |          |            |            |
| **Num |             |         |          |            |            |
| ber** |             |         |          |            |            |
|       |             |         |          |            |            |
| **(CL |             |         |          |            |            |
| IN)** |             |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+
| BC    | Purchase    | \$25,   | Charge   | Basis      | \$         |
| .1001 | Card        | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(a\) | Integrated  | \$25,   | Charge   | Basis      | \$         |
|       | Solution    | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(b\) | Bank Check  | 1,      | Per      | \$         | \$         |
|       |             | 000,000 | tra      |            |            |
|       |             |         | nsaction |            |            |
+-------+-------------+---------+----------+------------+------------+
| \(c\) | Customized  | 2,080   | Per hour | \$         | \$         |
|       | Services    |         |          |            |            |
|       |             |         |          |            |            |
|       | Programmer  |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+

**TABLE 7B - PURCHASE CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION TWO (1-YEAR PERIOD)

+-------+-------------+---------+----------+------------+------------+
| **    | **De        | **Eval  | **Unit   | **Basis    | **         |
| Contr | scription** | uated** | of**     | Points/**  | Extended** |
| act** |             |         |          |            |            |
|       |             | **Qua   | *        | **Price**  | **Total**  |
| *     |             | ntity** | *Issue** |            |            |
| *Line |             |         |          |            |            |
| I     |             | **(Per  |          |            |            |
| tem** |             | Year)** |          |            |            |
|       |             |         |          |            |            |
| **Num |             |         |          |            |            |
| ber** |             |         |          |            |            |
|       |             |         |          |            |            |
| **(CL |             |         |          |            |            |
| IN)** |             |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+
| BC    | Purchase    | \$25,   | Charge   | Basis      | \$         |
| .2001 | Card        | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(a\) | Integrated  | \$25,   | Charge   | Basis      | \$         |
|       | Solution    | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(b\) | Bank Check  | 1,      | Per      | \$         | \$         |
|       |             | 000,000 | tra      |            |            |
|       |             |         | nsaction |            |            |
+-------+-------------+---------+----------+------------+------------+
| \(c\) | Customized  | 2,080   | Per hour | \$         | \$         |
|       | Services    |         |          |            |            |
|       |             |         |          |            |            |
|       | Programmer  |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 7C - PURCHASE CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION THREE (1-YEAR PERIOD)

+-------+-------------+---------+----------+------------+------------+
| **    | **De        | **Eval  | **Unit   | **Basis    | **         |
| Contr | scription** | uated** | of**     | Points/**  | Extended** |
| act** |             |         |          |            |            |
|       |             | **Qua   | *        | **Price**  | **Total**  |
| *     |             | ntity** | *Issue** |            |            |
| *Line |             |         |          |            |            |
| I     |             | **(Per  |          |            |            |
| tem** |             | Year)** |          |            |            |
|       |             |         |          |            |            |
| **Num |             |         |          |            |            |
| ber** |             |         |          |            |            |
|       |             |         |          |            |            |
| **(CL |             |         |          |            |            |
| IN)** |             |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+
| BC    | Purchase    | \$25,   | Charge   | Basis      | \$         |
| .3001 | Card        | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(a\) | Integrated  | \$25,   | Charge   | Basis      | \$         |
|       | Solution    | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(b\) | Bank Check  | 1,      | Per      | \$         | \$         |
|       |             | 000,000 | tra      |            |            |
|       |             |         | nsaction |            |            |
+-------+-------------+---------+----------+------------+------------+
| \(c\) | Customized  | 2,080   | Per hour | \$         | \$         |
|       | Services    |         |          |            |            |
|       |             |         |          |            |            |
|       | Programmer  |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+

**TABLE 7D - PURCHASE CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION FOUR (1-YEAR PERIOD)

+-------+-------------+---------+----------+------------+------------+
| **    | **De        | **Eval  | **Unit   | **Basis    | **         |
| Contr | scription** | uated** | of**     | Points/**  | Extended** |
| act** |             |         |          |            |            |
|       |             | **Qua   | *        | **Price**  | **Total**  |
| *     |             | ntity** | *Issue** |            |            |
| *Line |             |         |          |            |            |
| I     |             | **(Per  |          |            |            |
| tem** |             | Year)** |          |            |            |
|       |             |         |          |            |            |
| **Num |             |         |          |            |            |
| ber** |             |         |          |            |            |
|       |             |         |          |            |            |
| **(CL |             |         |          |            |            |
| IN)** |             |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+
| BC    | Purchase    | \$25,   | Charge   | Basis      | \$         |
| .4001 | Card        | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(a\) | Integrated  | \$25,   | Charge   | Basis      | \$         |
|       | Solution    | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(b\) | Bank Check  | 1,      | Per      | \$         | \$         |
|       |             | 000,000 | tra      |            |            |
|       |             |         | nsaction |            |            |
+-------+-------------+---------+----------+------------+------------+
| \(c\) | Customized  | 2,080   | Per hour | \$         | \$         |
|       | Services    |         |          |            |            |
|       |             |         |          |            |            |
|       | Programmer  |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+

**TABLE 7E - PURCHASE CARD SERVICES**

TIER 1 REQUIREMENTS - OPTION FIVE (1-YEAR PERIOD)

+-------+-------------+---------+----------+------------+------------+
| **    | **De        | **Eval  | **Unit   | **Basis    | **         |
| Contr | scription** | uated** | of**     | Points/**  | Extended** |
| act** |             |         |          |            |            |
|       |             | **Qua   | *        | **Price**  | **Total**  |
| *     |             | ntity** | *Issue** |            |            |
| *Line |             |         |          |            |            |
| I     |             | **(Per  |          |            |            |
| tem** |             | Year)** |          |            |            |
|       |             |         |          |            |            |
| **Num |             |         |          |            |            |
| ber** |             |         |          |            |            |
|       |             |         |          |            |            |
| **(CL |             |         |          |            |            |
| IN)** |             |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+
| BC    | Purchase    | \$25,   | Charge   | Basis      | \$         |
| .5001 | Card        | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(a\) | Integrated  | \$25,   | Charge   | Basis      | \$         |
|       | Solution    | 000,000 | Volume   | Points     |            |
+-------+-------------+---------+----------+------------+------------+
| \(b\) | Bank Check  | 1,      | Per      | \$         | \$         |
|       |             | 000,000 | tra      |            |            |
|       |             |         | nsaction |            |            |
+-------+-------------+---------+----------+------------+------------+
| \(c\) | Customized  | 2,080   | Per hour | \$         | \$         |
|       | Services    |         |          |            |            |
|       |             |         |          |            |            |
|       | Programmer  |         |          |            |            |
+-------+-------------+---------+----------+------------+------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 7F - PURCHASE CARD SERVICES**

PRODUCTIVITY REFUND OFFERED as described in B.5.2? \[ \] YES \[ \] NO

  --------------------- -------------------------------------------------
  **Amount**            **Terms**

                        
  --------------------- -------------------------------------------------

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 8 - PURCHASE CARD SERVICES**

TIER 2 REQUIREMENTS - BASE PERIOD (5-YEARS)

+-------+-------------------------+---------------+--------------------+
| **    | **Description**         | **Unit of**   | **Price**          |
| Contr |                         |               |                    |
| act** |                         | **Issue**     |                    |
|       |                         |               |                    |
| *     |                         |               |                    |
| *Line |                         |               |                    |
| I     |                         |               |                    |
| tem** |                         |               |                    |
|       |                         |               |                    |
| **Num |                         |               |                    |
| ber** |                         |               |                    |
|       |                         |               |                    |
| **(CL |                         |               |                    |
| IN)** |                         |               |                    |
+-------+-------------------------+---------------+--------------------+
| BC    | Value-Added             |               |                    |
| .0002 | Products/Services       |               |                    |
+-------+-------------------------+---------------+--------------------+
| \(a\) | Additional              | Per service,  | \$                 |
|       | authorization controls  | per card      |                    |
+-------+-------------------------+---------------+--------------------+
| \(b\) | Software                | Each          | \$                 |
+-------+-------------------------+---------------+--------------------+
| \(c\) | Stored-Value Card       | Each          | \$                 |
+-------+-------------------------+---------------+--------------------+
| \(d\) | Debit Card              | Per           | \$                 |
|       |                         | transaction   |                    |
+-------+-------------------------+---------------+--------------------+
| \(e\) | ATM Access              | Per           | \$                 |
|       |                         | transaction   |                    |
+-------+-------------------------+---------------+--------------------+
| \(f\) | Inter/Intra-Agency      | Per           | \$                 |
|       | Service                 | transaction   |                    |
+-------+-------------------------+---------------+--------------------+
| \(g\) | Electronic bill payment | Per           | \$                 |
|       |                         | transaction   |                    |
+-------+-------------------------+---------------+--------------------+
| \(h\) | Hybrid Card             | Per card      | \$                 |
|       |                         |               |                    |
|       | ROM[^49]                | Per card      | \$                 |
|       |                         |               |                    |
|       | Low (1K)                | Per card      | \$                 |
|       |                         |               |                    |
|       | Medium (4K)             | Per card      | \$                 |
|       |                         |               |                    |
|       | High (12K)              | Per card      | \$                 |
|       |                         |               |                    |
|       | RAM[^50]                | Per card      | \$                 |
|       |                         |               |                    |
|       | Medium (128 bytes)      | Per card      | \$                 |
|       |                         |               |                    |
|       | High (800 bytes)        | Per card      | \$                 |
|       |                         |               |                    |
|       | EPROM[^51]              | Per card      | \$                 |
|       |                         |               |                    |
|       | Medium (1K)             |               |                    |
|       |                         |               |                    |
|       | High (8K)               |               |                    |
|       |                         |               |                    |
|       | EEPROM[^52]             |               |                    |
|       |                         |               |                    |
|       | Medium (1K)             |               |                    |
|       |                         |               |                    |
|       | High (8K)               |               |                    |
+-------+-------------------------+---------------+--------------------+
| \(i\) | Electronic Purchasing   | Per           | \$                 |
|       |                         | transaction   |                    |
+-------+-------------------------+---------------+--------------------+
| \(j\) | Photo ID                | Per card      | \$                 |
+-------+-------------------------+---------------+--------------------+
| \(k\) | Convenience services    | Per service   | \$                 |
|       | (please list)           |               |                    |
+-------+-------------------------+---------------+--------------------+
| \(l\) | Net Billing             | Per           | \$                 |
|       |                         | transaction   |                    |
+-------+-------------------------+---------------+--------------------+
| \(m\) | Card sleeves            | Per sleeve    | \$                 |
+-------+-------------------------+---------------+--------------------+
| \(n\) | Activation/Deactivation | Per card      | \$                 |
|       | on Demand               |               |                    |
+-------+-------------------------+---------------+--------------------+
| \(o\) | Emerging Technology     |               | Determined by Task |
|       |                         |               | Order              |
+-------+-------------------------+---------------+--------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 8A - PURCHASE CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION ONE (1-YEAR PERIOD)

+--------+--------------------------+--------------+-------------------+
| **Cont | **Description**          | **Unit of**  | **Price**         |
| ract** |                          |              |                   |
|        |                          | **Issue**    |                   |
| **Line |                          |              |                   |
| Item** |                          |              |                   |
|        |                          |              |                   |
| **Nu   |                          |              |                   |
| mber** |                          |              |                   |
|        |                          |              |                   |
| **(C   |                          |              |                   |
| LIN)** |                          |              |                   |
+--------+--------------------------+--------------+-------------------+
| B      | Value-Added              |              |                   |
| C.1002 | Products/Services        |              |                   |
+--------+--------------------------+--------------+-------------------+
| \(a\)  | Additional authorization | Per service, | \$                |
|        | controls                 | per card     |                   |
+--------+--------------------------+--------------+-------------------+
| \(b\)  | Software                 | Each         | \$                |
+--------+--------------------------+--------------+-------------------+
| \(c\)  | Stored-Value Card        | Each         | \$                |
+--------+--------------------------+--------------+-------------------+
| \(d\)  | Debit Card               | Per          | \$                |
|        |                          | transaction  |                   |
+--------+--------------------------+--------------+-------------------+
| \(e\)  | ATM Access               | Per          | \$                |
|        |                          | transaction  |                   |
+--------+--------------------------+--------------+-------------------+
| \(f\)  | Inter/Intra-Agency       | Per          | \$                |
|        | Service                  | transaction  |                   |
+--------+--------------------------+--------------+-------------------+
| \(g\)  | Electronic bill payment  | Per          | \$                |
|        |                          | transaction  |                   |
+--------+--------------------------+--------------+-------------------+
| \(h\)  | Hybrid Card              | Per card     | \$                |
|        |                          |              |                   |
|        | ROM[^53]                 | Per card     | \$                |
|        |                          |              |                   |
|        | Low (1K)                 | Per card     | \$                |
|        |                          |              |                   |
|        | Medium (4K)              | Per card     | \$                |
|        |                          |              |                   |
|        | High (12K)               | Per card     | \$                |
|        |                          |              |                   |
|        | RAM[^54]                 | Per card     | \$                |
|        |                          |              |                   |
|        | Medium (128 bytes)       | Per card     | \$                |
|        |                          |              |                   |
|        | High (800 bytes)         | Per card     | \$                |
|        |                          |              |                   |
|        | EPROM[^55]               | Per card     | \$                |
|        |                          |              |                   |
|        | Medium (1K)              |              |                   |
|        |                          |              |                   |
|        | High (8K)                |              |                   |
|        |                          |              |                   |
|        | EEPROM[^56]              |              |                   |
|        |                          |              |                   |
|        | Medium (1K)              |              |                   |
|        |                          |              |                   |
|        | High (8K)                |              |                   |
+--------+--------------------------+--------------+-------------------+
| \(i\)  | Electronic Purchasing    | Per          | \$                |
|        |                          | transaction  |                   |
+--------+--------------------------+--------------+-------------------+
| \(j\)  | Photo ID                 | Per card     | \$                |
+--------+--------------------------+--------------+-------------------+
| \(k\)  | Convenience services     | Per service  | \$                |
|        | (please list)            |              |                   |
+--------+--------------------------+--------------+-------------------+
| \(l\)  | Net Billing              | Per          | \$                |
|        |                          | transaction  |                   |
+--------+--------------------------+--------------+-------------------+
| \(m\)  | Card sleeves             | Per sleeve   | \$                |
+--------+--------------------------+--------------+-------------------+
| \(n\)  | Activation/Deactivation  | Per card     | \$                |
|        | on Demand                |              |                   |
+--------+--------------------------+--------------+-------------------+
| \(o\)  | Emerging Technology      |              | Determined by     |
|        |                          |              | Task Order        |
+--------+--------------------------+--------------+-------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 8B - PURCHASE CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION TWO (1-YEAR PERIOD)

+-------+-------------------------+---------------+-------------------+
| **    | **Description**         | **Unit of**   | **Price**         |
| Contr |                         |               |                   |
| act** |                         | **Issue**     |                   |
|       |                         |               |                   |
| *     |                         |               |                   |
| *Line |                         |               |                   |
| I     |                         |               |                   |
| tem** |                         |               |                   |
|       |                         |               |                   |
| **Num |                         |               |                   |
| ber** |                         |               |                   |
|       |                         |               |                   |
| **(CL |                         |               |                   |
| IN)** |                         |               |                   |
+-------+-------------------------+---------------+-------------------+
| BC    | Value-Added             |               |                   |
| .2002 | Products/Services       |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(a\) | Additional              | Per service,  | \$                |
|       | authorization controls  | per card      |                   |
+-------+-------------------------+---------------+-------------------+
| \(b\) | Software                | Each          | \$                |
+-------+-------------------------+---------------+-------------------+
| \(c\) | Stored-Value Card       | Each          | \$                |
+-------+-------------------------+---------------+-------------------+
| \(d\) | Debit Card              | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(e\) | ATM Access              | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(f\) | Inter/Intra-Agency      | Per           | \$                |
|       | Service                 | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(g\) | Electronic bill payment | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(h\) | Hybrid Card             | Per card      | \$                |
|       |                         |               |                   |
|       | ROM[^57]                | Per card      | \$                |
|       |                         |               |                   |
|       | Low (1K)                | Per card      | \$                |
|       |                         |               |                   |
|       | Medium (4K)             | Per card      | \$                |
|       |                         |               |                   |
|       | High (12K)              | Per card      | \$                |
|       |                         |               |                   |
|       | RAM[^58]                | Per card      | \$                |
|       |                         |               |                   |
|       | Medium (128 bytes)      | Per card      | \$                |
|       |                         |               |                   |
|       | High (800 bytes)        | Per card      | \$                |
|       |                         |               |                   |
|       | EPROM[^59]              | Per card      | \$                |
|       |                         |               |                   |
|       | Medium (1K)             |               |                   |
|       |                         |               |                   |
|       | High (8K)               |               |                   |
|       |                         |               |                   |
|       | EEPROM[^60]             |               |                   |
|       |                         |               |                   |
|       | Medium (1K)             |               |                   |
|       |                         |               |                   |
|       | High (8K)               |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(i\) | Electronic Purchasing   | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(j\) | Photo ID                | Per card      | \$                |
+-------+-------------------------+---------------+-------------------+
| \(k\) | Convenience services    | Per service   | \$                |
|       | (please list)           |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(l\) | Net Billing             | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(m\) | Card sleeves            | Per sleeve    | \$                |
+-------+-------------------------+---------------+-------------------+
| \(n\) | Activation/Deactivation | Per card      | \$                |
|       | on Demand               |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(o\) | Emerging Technology     |               | Determined by     |
|       |                         |               | Task Order        |
+-------+-------------------------+---------------+-------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 8C - PURCHASE CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION THREE (1-YEAR PERIOD)

+--------+------------------------+---------------+-------------------+
| **Cont | **Description**        | **Unit of**   | **Price**         |
| ract** |                        |               |                   |
|        |                        | **Issue**     |                   |
| **Line |                        |               |                   |
| Item** |                        |               |                   |
|        |                        |               |                   |
| **Nu   |                        |               |                   |
| mber** |                        |               |                   |
|        |                        |               |                   |
| **(C   |                        |               |                   |
| LIN)** |                        |               |                   |
+--------+------------------------+---------------+-------------------+
| B      | Value-Added            |               |                   |
| C.3002 | Products/Services      |               |                   |
+--------+------------------------+---------------+-------------------+
| \(a\)  | Additional             | Per service,  | \$                |
|        | authorization controls | per card      |                   |
+--------+------------------------+---------------+-------------------+
| \(b\)  | Software               | Each          | \$                |
+--------+------------------------+---------------+-------------------+
| \(c\)  | Stored-Value Card      | Each          | \$                |
+--------+------------------------+---------------+-------------------+
| \(d\)  | Debit Card             | Per           | \$                |
|        |                        | transaction   |                   |
+--------+------------------------+---------------+-------------------+
| \(e\)  | ATM Access             | Per           | \$                |
|        |                        | transaction   |                   |
+--------+------------------------+---------------+-------------------+
| \(f\)  | Inter/Intra-Agency     | Per           | \$                |
|        | Service                | transaction   |                   |
+--------+------------------------+---------------+-------------------+
| \(g\)  | Electronic bill        | Per           | \$                |
|        | payment                | transaction   |                   |
+--------+------------------------+---------------+-------------------+
| \(h\)  | Hybrid Card            | Per card      | \$                |
|        |                        |               |                   |
|        | ROM[^61]               | Per card      | \$                |
|        |                        |               |                   |
|        | Low (1K)               | Per card      | \$                |
|        |                        |               |                   |
|        | Medium (4K)            | Per card      | \$                |
|        |                        |               |                   |
|        | High (12K)             | Per card      | \$                |
|        |                        |               |                   |
|        | RAM[^62]               | Per card      | \$                |
|        |                        |               |                   |
|        | Medium (128 bytes)     | Per card      | \$                |
|        |                        |               |                   |
|        | High (800 bytes)       | Per card      | \$                |
|        |                        |               |                   |
|        | EPROM[^63]             | Per card      | \$                |
|        |                        |               |                   |
|        | Medium (1K)            |               |                   |
|        |                        |               |                   |
|        | High (8K)              |               |                   |
|        |                        |               |                   |
|        | EEPROM[^64]            |               |                   |
|        |                        |               |                   |
|        | Medium (1K)            |               |                   |
|        |                        |               |                   |
|        | High (8K)              |               |                   |
+--------+------------------------+---------------+-------------------+
| \(i\)  | Electronic Purchasing  | Per           | \$                |
|        |                        | transaction   |                   |
+--------+------------------------+---------------+-------------------+
| \(j\)  | Photo ID               | Per card      | \$                |
+--------+------------------------+---------------+-------------------+
| \(k\)  | Convenience services   | Per service   | \$                |
|        | (please list)          |               |                   |
+--------+------------------------+---------------+-------------------+
| \(l\)  | Net Billing            | Per           | \$                |
|        |                        | transaction   |                   |
+--------+------------------------+---------------+-------------------+
| \(m\)  | Card sleeves           | Per sleeve    | \$                |
+--------+------------------------+---------------+-------------------+
| \(n\)  | A                      | Per card      | \$                |
|        | ctivation/Deactivation |               |                   |
|        | on Demand              |               |                   |
+--------+------------------------+---------------+-------------------+
| \(o\)  | Emerging Technology    |               | Determined by     |
|        |                        |               | Task Order        |
+--------+------------------------+---------------+-------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 8D - PURCHASE CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION FOUR(1-YEAR PERIOD)

+-------+-------------------------+---------------+-------------------+
| **    | **Description**         | **Unit of**   | **Price**         |
| Contr |                         |               |                   |
| act** |                         | **Issue**     |                   |
|       |                         |               |                   |
| *     |                         |               |                   |
| *Line |                         |               |                   |
| I     |                         |               |                   |
| tem** |                         |               |                   |
|       |                         |               |                   |
| **Num |                         |               |                   |
| ber** |                         |               |                   |
|       |                         |               |                   |
| **(CL |                         |               |                   |
| IN)** |                         |               |                   |
+-------+-------------------------+---------------+-------------------+
| BC    | Value-Added             |               |                   |
| .4002 | Products/Services       |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(a\) | Additional              | Per service,  | \$                |
|       | authorization controls  | per card      |                   |
+-------+-------------------------+---------------+-------------------+
| \(b\) | Software                | Each          | \$                |
+-------+-------------------------+---------------+-------------------+
| \(c\) | Stored-Value Card       | Each          | \$                |
+-------+-------------------------+---------------+-------------------+
| \(d\) | Debit Card              | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(e\) | ATM Access              | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(f\) | Inter/Intra-Agency      | Per           | \$                |
|       | Service                 | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(g\) | Electronic bill payment | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(h\) | Hybrid Card             | Per card      | \$                |
|       |                         |               |                   |
|       | ROM[^65]                | Per card      | \$                |
|       |                         |               |                   |
|       | Low (1K)                | Per card      | \$                |
|       |                         |               |                   |
|       | Medium (4K)             | Per card      | \$                |
|       |                         |               |                   |
|       | High (12K)              | Per card      | \$                |
|       |                         |               |                   |
|       | RAM[^66]                | Per card      | \$                |
|       |                         |               |                   |
|       | Medium (128 bytes)      | Per card      | \$                |
|       |                         |               |                   |
|       | High (800 bytes)        | Per card      | \$                |
|       |                         |               |                   |
|       | EPROM[^67]              | Per card      | \$                |
|       |                         |               |                   |
|       | Medium (1K)             |               |                   |
|       |                         |               |                   |
|       | High (8K)               |               |                   |
|       |                         |               |                   |
|       | EEPROM[^68]             |               |                   |
|       |                         |               |                   |
|       | Medium (1K)             |               |                   |
|       |                         |               |                   |
|       | High (8K)               |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(i\) | Electronic Purchasing   | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(j\) | Photo ID                | Per card      | \$                |
+-------+-------------------------+---------------+-------------------+
| \(k\) | Convenience services    | Per service   | \$                |
|       | (please list)           |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(l\) | Net Billing             | Per           | \$                |
|       |                         | transaction   |                   |
+-------+-------------------------+---------------+-------------------+
| \(m\) | Card sleeves            | Per sleeve    | \$                |
+-------+-------------------------+---------------+-------------------+
| \(n\) | Activation/Deactivation | Per card      | \$                |
|       | on Demand               |               |                   |
+-------+-------------------------+---------------+-------------------+
| \(o\) | Emerging Technology     |               | Determined by     |
|       |                         |               | Task Order        |
+-------+-------------------------+---------------+-------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 8E - PURCHASE CARD SERVICES**

TIER 2 REQUIREMENTS - OPTION FIVE (1-YEAR PERIOD)

+-------+---------------------------+--------------+------------------+
| **    | **Description**           | **Unit of**  | **Price**        |
| Contr |                           |              |                  |
| act** |                           | **Issue**    |                  |
|       |                           |              |                  |
| *     |                           |              |                  |
| *Line |                           |              |                  |
| I     |                           |              |                  |
| tem** |                           |              |                  |
|       |                           |              |                  |
| **Num |                           |              |                  |
| ber** |                           |              |                  |
|       |                           |              |                  |
| **(CL |                           |              |                  |
| IN)** |                           |              |                  |
+-------+---------------------------+--------------+------------------+
| BC    | Value-Added               |              |                  |
| .5002 | Products/Services         |              |                  |
+-------+---------------------------+--------------+------------------+
| \(a\) | Additional authorization  | Per service, | \$               |
|       | controls                  | per card     |                  |
+-------+---------------------------+--------------+------------------+
| \(b\) | Software                  | Each         | \$               |
+-------+---------------------------+--------------+------------------+
| \(c\) | Stored-Value Card         | Each         | \$               |
+-------+---------------------------+--------------+------------------+
| \(d\) | Debit Card                | Per          | \$               |
|       |                           | transaction  |                  |
+-------+---------------------------+--------------+------------------+
| \(e\) | ATM Access                | Per          | \$               |
|       |                           | transaction  |                  |
+-------+---------------------------+--------------+------------------+
| \(f\) | Inter/Intra-Agency        | Per          | \$               |
|       | Service                   | transaction  |                  |
+-------+---------------------------+--------------+------------------+
| \(g\) | Electronic bill payment   | Per          | \$               |
|       |                           | transaction  |                  |
+-------+---------------------------+--------------+------------------+
| \(h\) | Hybrid Card               | Per card     | \$               |
|       |                           |              |                  |
|       | ROM[^69]                  | Per card     | \$               |
|       |                           |              |                  |
|       | Low (1K)                  | Per card     | \$               |
|       |                           |              |                  |
|       | Medium (4K)               | Per card     | \$               |
|       |                           |              |                  |
|       | High (12K)                | Per card     | \$               |
|       |                           |              |                  |
|       | RAM[^70]                  | Per card     | \$               |
|       |                           |              |                  |
|       | Medium (128 bytes)        | Per card     | \$               |
|       |                           |              |                  |
|       | High (800 bytes)          | Per card     | \$               |
|       |                           |              |                  |
|       | EPROM[^71]                | Per card     | \$               |
|       |                           |              |                  |
|       | Medium (1K)               |              |                  |
|       |                           |              |                  |
|       | High (8K)                 |              |                  |
|       |                           |              |                  |
|       | EEPROM[^72]               |              |                  |
|       |                           |              |                  |
|       | Medium (1K)               |              |                  |
|       |                           |              |                  |
|       | High (8K)                 |              |                  |
+-------+---------------------------+--------------+------------------+
| \(i\) | Electronic Purchasing     | Per          | \$               |
|       |                           | transaction  |                  |
+-------+---------------------------+--------------+------------------+
| \(j\) | Photo ID                  | Per card     | \$               |
+-------+---------------------------+--------------+------------------+
| \(k\) | Convenience services      | Per service  | \$               |
|       | (please list)             |              |                  |
+-------+---------------------------+--------------+------------------+
| \(l\) | Net Billing               | Per          | \$               |
|       |                           | transaction  |                  |
+-------+---------------------------+--------------+------------------+
| \(m\) | Card sleeves              | Per sleeve   | \$               |
+-------+---------------------------+--------------+------------------+
| \(n\) | Activation/Deactivation   | Per card     | \$               |
|       | on Demand                 |              |                  |
+-------+---------------------------+--------------+------------------+
| \(o\) | Emerging Technology       |              | Determined by    |
|       |                           |              | Task Order       |
+-------+---------------------------+--------------+------------------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 8F - PURCHASE CARD SERVICES**

QUANTITY DISCOUNT OFFERED ON TIER 2 REQUIREMENTS? \[ \] YES \[ \] NO

  --------------------- -------------------------------------------------
  **Amount**            **Terms**

                        
  --------------------- -------------------------------------------------

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 9 - PURCHASE CARD SERVICES**

BENCHMARK TASK 4 - BASE PERIOD (5-YEARS) (see Exhibit 5)

+----------------------+------------+----------+----------+----------+
| **Contract Line Item | **Des      | **Eva    | **Unit   | *        |
| Number (CLIN)**      | cription** | luated** | of**     | *Price** |
|                      |            |          |          |          |
|                      |            | **Qu     | *        |          |
|                      |            | antity** | *Issue** |          |
|                      |            |          |          |          |
|                      |            | **(Base  |          |          |
|                      |            | P        |          |          |
|                      |            | eriod)** |          |          |
+----------------------+------------+----------+----------+----------+
| BC.0003              | Benchmark  |          |          | \$       |
|                      | Task 4     |          |          |          |
+----------------------+------------+----------+----------+----------+

**TABLE 9A - PURCHASE CARD SERVICES**

BENCHMARK TASK 4 - OPTION ONE (1-YEAR PERIOD) (see Exhibit 5)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BC.1003                | Benchmark  |        |          | \$       |
|                        | Task 4     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 9B - PURCHASE CARD SERVICES**

BENCHMARK TASK 4 - OPTION TWO (1-YEAR PERIOD) (see Exhibit 5)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BC.2003                | Benchmark  |        |          | \$       |
|                        | Task 4     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 9C - PURCHASE CARD SERVICES**

BENCHMARK TASK 4 - OPTION THREE (1-YEAR PERIOD) (see Exhibit 5)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BC.3003                | Benchmark  |        |          | \$       |
|                        | Task 4     |        |          |          |
+------------------------+------------+--------+----------+----------+

***Block 19 of SF 1449:***

***Contract Line Item Numbers (Section B)\--Continued***

**TABLE 9D - PURCHASE CARD SERVICES**

BENCHMARK TASK 4 - OPTION FOUR (1-YEAR PERIOD) (see Exhibit 5)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BC.4003                | Benchmark  |        |          | \$       |
|                        | Task 4     |        |          |          |
+------------------------+------------+--------+----------+----------+

**TABLE 9E - PURCHASE CARD SERVICES**

BENCHMARK TASK 4 - OPTION FIVE (1-YEAR PERIOD) (see Exhibit 5)

+------------------------+------------+--------+----------+----------+
| **Contract Line Item   | **Des      | *      | **Unit   | *        |
| Number (CLIN)**        | cription** | *Evalu | of**     | *Price** |
|                        |            | ated** |          |          |
|                        |            |        | *        |          |
|                        |            | **Quan | *Issue** |          |
|                        |            | tity** |          |          |
|                        |            |        |          |          |
|                        |            | **(Per |          |          |
|                        |            | Y      |          |          |
|                        |            | ear)** |          |          |
+------------------------+------------+--------+----------+----------+
| BC.5003                | Benchmark  |        |          | \$       |
|                        | Task 4     |        |          |          |
+------------------------+------------+--------+----------+----------+

# *Block 19 of SF 1449: Contract Line Item Numbers (Section B)\--Continued*

## B.1 MASTER CONTRACT: B-FSS-FCXC-\_\_\_ (AUG 1996)

The General Services Administration (GSA) plans to award long-term task
order master contracts to multiple vendors offering a wide variety of
products and services. Each qualifying offeror is eligible for award for
each independent business line (fleet, travel, or purchase) and for an
integrated solution. Vendors must meet requirements of the business
line(s) in order to be considered for an integrated solution.

Offerors must offer all of core requirements for a business line to be
considered for value-added products and services in the particular
business line(s) offered. Value-added products and services may not be
offered separately from the core requirement. This is to ensure that an
ordering agency/organization need only utilize one system for
product/service requirements and payment. This also enables
interoperability between products and services required and the systems
they must be generated through.

Offerors are encouraged to utilize small businesses, small disadvantaged
businesses, and women-owned businesses where possible. Contractor team
arrangements are encouraged (e.g., to provide consulting services on
re-engineering efforts (reference GSA's Management Organization Business
Improvement Services (MOBIS) Schedule No. 874; to enhance the
Government's desire to integrate business lines as addressed in the
Schedule of Services; to provide smart card readers, peripheral
equipment and systems integration (reference GSA's Schedule No.
\_\_\_\_, etc.). Reference Federal Acquisition Regulation (FAR) 9.6,
Contractor Team Arrangements for additional information on contractor
team arrangements.

## B.2 MENU-DRIVEN OPTIONS: B-FSS-FCXC-\_\_\_ (AUG 1996)

In order to ease the administrative burden to ordering
agencies/organizations and contractors, the GSA has devised menu-driven
options of various products and services. These menu-driven options
allow agencies/organizations to review contractor capabilities based on
requirements stated herein and place an order with the contractor that
best meets the agency's/organization's needs at the price stipulated in
Block 19 of the SF 1449, Contract Line Item Numbers (CLINs).

## B.3 ESTIMATED QUANTITIES: B-FSS-FCXC-\_\_\_ (AUG 1996)

While historical figures are provided in Exhibit 6 (Fleet Card Program,
Exhibit 7, Travel Card Program, and Exhibit 8 (Purchase Card Program),
it is not possible to determine any estimated quantities of orders that
may be received under the master contract approach. Therefore, OFFERORS
ARE CAUTIONED THAT THERE ARE NO GUARANTEES GIVEN THAT ANY ORDERS WILL BE
PLACED (however, reference B.4, Guaranteed Minimum). THE QUANTITIES
SHOWN IN THE PRICING TABLES ARE FOR EVALUATION PURPOSES ONLY AND DO NOT
REPRESENT ESTIMATED QUANTITIES.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

## B.4 GUARANTEED MINIMUM: B-FSS-FCXC-\_\_\_ (AUG 1996)

GSA guarantees a minimum on each fleet, travel and purchase card master
contract (not each task order) as indicated in the subparagraphs below.
Payment of the guaranteed minimum is contingent upon good contract
performance. In order to determine whether contract performance has been
good, the Government will continually evaluate the contractor's
performance by utilizing:

1.  Annual contractor quality survey results (referenced in C.10,
    Quality Assurance); and

2.  Contract performance standards as described in the addendum to
    52.212-4, paragraph 45, Contract Performance Standards.

Contractors not responding to every task request/order received, either
with a proposal to the task order or a no offer response, will not be
eligible to receive the guaranteed minimum.

Payment of the guaranteed minimum (as detailed below) will occur at the
conclusion of the initial 5-year base period with demonstrated
satisfactory performance. Contracts terminated for cause are not
entitled to any guaranteed minimum. Contractors must request payment in
accordance with paragraph 50 of the Addendum to 52.212-4.

No guaranteed minimum amounts will be offered by the Government beyond
the initial 5-year base period.

B.4.1 *Guaranteed Minimum for the Fleet Card Program:* The guaranteed
minimum for the fleet card program is \$5,000, to be calculated as
follows: GSA guarantees a minimum charge volume of \$100,000 flowing
through each fleet card master contract for the initial 5-year base
period, provided that the Contractor demonstrates satisfactory contract
performance as described in B.4. Charge volume is defined as all revenue
producing transactions/volumes. If a Contractor does not realize the
minimum charge volume of \$100,000, GSA will pay an amount equal to 5%
of the amount required to bring the volume up to the \$100,000 charge
volume guarantee, not to exceed \$5,000.

B.4.2 *Guaranteed Minimum for the Travel Card Program:* The guaranteed
minimum for the travel card program is \$25,000, to be calculated as
follows: GSA guarantees a minimum charge volume of \$25 million flowing
through each travel card master contract for the initial 5-year base
period, provided that the Contractor demonstrates satisfactory contract
performance as described in B.4. Charge volume is defined as all revenue
producing transactions/volumes. If a Contractor does not realize the
minimum charge volume of \$25 million, GSA will pay an amount equal to
00.1% of the amount required to bring the volume up to the \$25 million
charge volume guarantee, not to exceed \$25,000.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

B.4.3 *Guaranteed Minimum for the Purchase Card Program:* The guaranteed
minimum for the purchase card program is \$25,000, to be calculated as
follows: GSA guarantees a minimum charge volume of \$25 million flowing
through each purchase card master contract for the initial 5-year base
period, provided that the Contractor demonstrates satisfactory contract
performance as described in B.4. Charge volume is defined as all revenue
producing transactions/volumes. If a Contractor does not realize the
minimum charge volume of \$25 million, GSA will pay an amount equal to
00.1% of the amount required to bring the volume up to the \$25 million
charge volume guarantee, not to exceed \$25,000.

B.4.4 *Examples of How the Guaranteed Minimum Will Work:* Several
examples of how the guaranteed minimum will work are provided below:

> Example 1: Contractor "x" has one travel card contract and no other
> contracts. Contractor "x" had \$20 million of charge volume and
> satisfactory performance for the travel card business line during the
> initial 5-year base period, a shortfall of \$5 million. GSA will pay
> 00.1% on the \$5 million shortfall in charge volume, or \$5,000.
>
> Example 2: Contractor "y" has one purchase card contract and one
> travel card contract. Contractor "y" had \$30 million of charge volume
> for the purchase card business line and \$20 million of charge volume
> for the travel card business line during the initial 5-year base
> period and satisfactory performance. This results in a shortfall of
> \$5 million on the travel card business line only, and no shortfall on
> the purchase card business line. GSA will pay 00.1% on the \$5 million
> shortfall in charge volume for the travel card business line, or
> \$5,000. As the minimum has been exceeded for the purchase card
> business line, no payment will be made.
>
> Example 3: Contractor "a" has one purchase card contract and no other
> contracts. Contractor "a" had \$0 of charge volume and met the
> contract performance standard requirements for the purchase card
> business line. This results in a shortfall of \$25 million on the
> purchase card business line. GSA will pay 00.1% on the \$25 million
> shortfall in charge volume, or \$25,000, the maximum amount allowed to
> be paid.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

> Example 4: Contractor "b" has one fleet card contract, one purchase
> card contract, and one travel card contract. Contractor "b" had
> \$50,000 of charge volume for the fleet card business line, \$25
> million each of charge volume for both the travel and purchase card
> business lines during the initial 5-year base period and satisfactory
> performance. This results in a shortfall of \$50,000 on the fleet card
> business line only, and no shortfall on the travel and purchase card
> business lines. GSA will pay 5% on the \$50,000 shortfall in charge
> volume for the fleet card business line, or \$2,500. As the minimum
> has been exceed for the travel and purchase card business lines, no
> payment will be made.
>
> Example 5: Contractor "c" has one fleet card contract, one purchase
> card contract, and one travel card contract. Contractor "c" had
> \$50,000 of charge volume for the fleet card business line, \$25
> million of charge volume for the travel card business line, \$0 for
> the purchase card business line during the initial 5-year base period
> and satisfactory performance. This results in a shortfall of \$50,000
> on the fleet card business line, no shortfall on the travel card
> business line, and a shortfall of \$25 million for the purchase card
> business line. The total guaranteed minimum GSA will pay in this
> scenario is \$30,500 broken out as follows: \$2,500 for the shortfall
> in the fleet card business line (5% on the \$50,000 shortfall in
> charge volume), and \$25,000 for the shortfall in the purchase card
> business line (00.1% of the \$25 million shortfall in charge volume).
>
> Example 6: Contractor "d" has one fleet card contract, one purchase
> card contract, and one travel card contract. Contractor "d" had
> \$100,000 of charge volume for the fleet card business line, and \$25
> million each of charge volume for the travel and purchase card
> business lines during the initial 5-year base period and satisfactory
> performance. This results in no shortfall and GSA will pay nothing.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

> Example 7: Contractor "e" has one fleet card contract, one purchase
> card contract, and one travel card contract. Contractor "e" had \$0 of
> charge volume for each business line during the initial 5-year base
> period. This results in a shortfall of \$100,000 on the fleet card
> business line, and a shortfall of \$25 million each on the travel and
> purchase card business lines. The total guaranteed minimum GSA would
> have paid in this scenario is \$55,000 broken out as follows: \$5,000
> for the shortfall in the fleet card business line (5% on the \$100,000
> shortfall in charge volume), \$25,000 for the shortfall in the travel
> card business line (00.1% of the \$25 million shortfall in charge
> volume), and \$25,000 for the shortfall in the purchase card business
> line (00.1% of the \$25 million shortfall in charge volume). However,
> contractor "e" failed to respond to every task request/order received,
> therefore, not meeting a minimum requirement for obtaining the
> guaranteed minimum. No payment will be made.

## B.5 DEFINITIONS: B-FSS-FCXC-\_\_\_ (MAY 1997)

**Agency Gross Refund:** The calculated amount of the
agency/organization refund in dollars including GSA's Industrial Funding
Fee (IFF).

**Agency Net Refund:** The calculated amount of the agency/organization
refund in dollars less GSA's IFF in dollars.

**Basis Point:** One hundredth of one percent.

**Gross Basis Points:** The number of Contractor-offered basis points
including GSA's IFF.

**Net Charge Volume:** All revenue producing transactions/volumes in
both core and value-added products and services and excludes credits and
adjustments.

**Revenue Producing Transactions/Volumes:** Income received by the
Contractor via card fees, ATM/Cash, merchant fees, discount rates and
interchange rates.

## B.6 FINANCIAL CONSIDERATION TO AGENCIES/ORGANIZATIONS: B-FSS-FCXC-\_\_\_ (MAY 1997)

B.6.1 *Sales Refund:* The Contractor shall provide a proposal which will
provide each agency/organization level a financial refund, in basis
points, based on net charge volume, paid directly to the
agency/organization level.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

The proposal offered must include GSA's Industrial Funding Fee (IFF) as
described in the Addendum to 52.212-4, paragraph 18.

B.6.1.1 *Calculation of Sales Refund:* For the purposes of sales
refunds, refunds shall be calculated as follows:

a)  Identify the refund payout volume (net charge volume identified
    above);

b)  Determine the dollar balances in suspended and canceled accounts;
    and

c)  Subtract the dollar amount determined in subparagraph b) from
    subparagraph a) to begin refund computations.

Thus, the calculations shall follow this series of formulas:

**1. A (Net Charge Volume) - B (Dollar Balances in Suspended/Canceled
Accounts) =**

**C (Dollar Basis to Determine Sales Refund)**

**2. C (Dollar Basis to Determine Sales Refund) x X (Gross Basis Points)
=**

**W (Agency Gross Refund)**

**3. C (Dollar Basis to Determine Sales Refund) x Y (GSA Industrial
Funding Fee) =**

**Q (Dollars to GSA)**

**4. W (Agency Gross Refund) - Q (Dollars to GSA) = Z (Agency Net
Refund)**

For example, Agency A has \$1,000,000 in net charge volume (A) and
\$5,000 in dollar balances in suspended/canceled accounts (B). Gross
basis points offered in this example is 10 basis points, 4 of which is
GSA's Industrial Funding Fee. The sales refund would be calculated as
follows:

1\. A (\$1,000,000\--Net Charge Volume) - B (\$5,000\--Dollar Balances
in Suspended/Canceled Accounts) = C (\$995,000\--Dollar Basis to
Determine Sales Refund).

2\. C (\$995,000\--Dollar Basis to Determine Sales Refund) x X (10 basis
points\--Gross Basis Points) = \$W (995.00\--Agency Gross Refund)

3\. C (\$995,000\--Dollar Basis to Determine Sales Refund) x Y (4 basis
points\--GSA Industrial Funding Fee) = Q (\$398\--GSA IFF)

4\. W (Agency Gross Refund) - Q (GSA IFF) = Z (\$597\--Agency Net
Refund)

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

Once payment is received and suspension/cancellation is lifted, those
dollar balances in subparagraph b), above, shall be included in
subparagraph a), above for the next refund payout date.

B.6.1.2 *Sales Refund Proposals:* Sales refunds are based on net charge
volume as described in B.6.1.1, Calculation of Sales Refund. The
following historical information is provided to assist offerors:

a)  Historic programmatic data for the fleet card program on sales,
    transactions, cardholders and delinquencies are shown in Exhibit 6.

b)  Historic programmatic data for the travel card program on sales,
    transactions, cardholders and delinquencies are shown in Exhibit 7.

c)  Historic programmatic data for the purchase card program on sales,
    transactions, cardholders and delinquencies are shown in Exhibit 8.

B.6.1.3 Varying Assumptions: Offerors are strongly encouraged to provide
alternate pricing proposals.

B.6.2 *Productivity Refund:* The Contractor is encouraged to provide a
separate proposal to agency/organization levels which will afford an
opportunity for agencies/organizations to receive a productivity refund
based on agency/organization level's improved payment performance (e.g.,
faster pay, reduced delinquencies, electronic receipt of
invoice/reports, reduced write-offs, etc.). The productivity refund
should encourage and motivate agency/organization levels to improve and
streamline operations and payments. The Contractor shall remit any
productivity refund directly to the agency/organization level.

B.6.3 *Frequency of Remittance:* Agency net refunds and productivity
refunds shall, at a minimum, be remitted to the agency/organization
level by the **10th of each fiscal year quarter**, unless otherwise
specified by the agency/organization level. The Contractor shall remit
refunds electronically, as directed, unless otherwise specified by the
agency/organization level. Agency/organization levels may require more
frequent refund remittance schedules (e.g., daily, weekly, monthly) and
will specify and request pricing for their requirements in their task
order.

The Government operates on a fiscal year basis that spans from October 1
through September 30. In order for agencies/organizations to take
advantage of refunds, the timing of such refunds must account for the
Government's year end processing. The proposal shall address how the
Contractor proposes to time the refund(s) so that agencies/organizations
may take advantage of the financial consideration prior to fiscal year
end.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

B.6.4 *Application of Refunds:* Each agency/organization level may
choose to apply their refund in a variety of ways to include, but not be
limited to, offset against subsequent invoices, direct electronic
payment, payment against value-added products and services ordered,
payment against contract-related expenses (e.g., GSA registration fees
for conferences), and/or any combination thereof. Each
agency/organization level will specify the refund mechanism desired in
their task order.

## B.7 PRICING INSTRUCTIONS: B-FSS-FCXC-\_\_\_ (MAY 1997)

a)  Offerors are instructed to submit their pricing in the format
    specified in Tables 1 through 9 for the base year and each option
    year period.

b)  If offerors adopt a volume-based approach to pricing, the pricing
    proposed must not adversely affect agencies/organizations that place
    their orders first. As individual agencies/organizations will place
    separate orders with contractors, it would not be prudent to create
    an incentive to wait for other agencies/organizations to place
    orders to obtain a volume based discount.

c)  If quantity discounts are offered on the value-added products and
    services, please indicate what the quantity discounts are.

d)  If an integrated solution discount is offered, please indicate what
    the discount is.

e)  Where additional space is necessary, use plain bond paper and
    clearly mark the contract line item number for which the pricing is
    being offered.

B.7.1 *Ceiling/Floor Prices:* All prices offered, except the
agency/organization sales and productivity refund and GSA's industrial
funding fee, are to be ceiling prices (i.e., the maximum price of the
product/service). Because agencies/organizations may simply place a
standard task order after reviewing all master contractor(s)
presentation packages or the Federal Supply Schedule Information Package
(FSSIP) without further contact with the master contractor(s) and
because the ceiling prices will be evaluated for evaluation purposes of
the master contract, offerors are encouraged to aggressively price
contract line items offered at the outset.

Agency/organization sales refund, productivity refund and GSA's IFF are
floor prices (i.e., the minimum amount of the refund/IFF).

B.7.2 *No Charge:* If there is no charge for a contract line item,
please indicate "N/C."

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

B.7.3 *Core Requirements:* Core requirements are defined in the Schedule
of Services, Section C, and associated sections distinct to each
business line. Pricing for financial refunds are described in B.6,
Financial Consideration to Agencies/Organizations.

a)  Specific to Travel Card: Offerors shall include core pricing for
    Travelers Checks and ATM Access.

b)  Specific to Purchase Card: Offerors shall include core pricing for
    Bank Checks.

B.7.4 *Value-Added Products and Services:* Please note that offerors may
not offer value-added products and services unless they offer the core
requirements. Pricing, if any, shall be inclusive of products/services
as described in C.47, Value-Added Products and Services, unless
otherwise specified. All pricing offered shall be in accordance with
standard commercial pricing. All terms and conditions proposed shall be
in accordance with commercial terms and conditions, unless otherwise
specified herein.

a\) Additional Authorization Controls: These are specified in C.47,
Value-Added Products and Services, subparagraph C.47.1. Offerors shall
identify what additional controls are provided and the associated
processes.

b\) Software: This is specified in C.47, Value-Added Products and
Services, subparagraph C.47.2. Offerors shall identify and describe what
software is offered, specifications and operating systems required, etc.

c\) Stored-Value Card or E-Purse Products and Services: These are
specified in C.47, Value-Added Products and Services, subparagraph
C.47.3. Offerors shall identify and describe chip sizes offered.
Pricing, if any, shall only include the cost of the physical card
product based on chip size. Applications will be priced using the labor
rates specified in the Pricing Schedule. The actual stored value of the
card will be determined by the agency/organization.

d\) Debit Card Products and Services: These are specified in C.47,
Value-Added Products and Services, subparagraph C.47.4. Offerors shall
identify terms and conditions of debit cards offered. Pricing, if any,
shall only include the cost of the physical card product.

e\) Optional ATM Products and Services (Purchase and Fleet Cards): These
are specified in C.47, Value-Added Products and Services, subparagraph
C.47.5.

f\) Optional Bank Check Products and Services (Fleet and Travel Cards):
These are specified in C.47, Value-Added Products and Services,
subparagraph C.47.6.

g\) Inter/Intra-Governmental Services: This is specified in C.47,
Value-Added Products and Services, subparagraph C.47.7.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

h\) Telephone Card Access (for the Travel Card only): This is specified
in C.47, Value-Added Products and Services, subparagraph C.47.8.
Pricing, if any, shall only include the actual inclusion of the long
distance carrier access code and calling number on the back of the card.
Effort required to facilitate this with the Government's long distance
carrier contractor(s) will be priced using the labor rates specified in
the Pricing Schedule.

i\) Electronic Bill Payment: This is specified in C.47, Value-Added
Products and Services, subparagraph C.47.9.

j\) Hybrid Card: These are specified in C.47, Value-Added Products and
Services, subparagraph C.47.10. Offerors shall identify and describe
chip sizes offered. Pricing shall only include the cost of the physical
card product based on chip size. Housing of applications will be priced
using the labor rates specified in the Pricing Schedule.

k\) Electronic Purchasing: This is specified in C.47, Value-Added
Products and Services, subparagraph C.47.11.

l\) Photo ID: This is specified in C.47, Value-Added Products and
Services, subparagraph C.47.12. Offerors shall identify and describe
processes required for placing a photo on the card product.

m\) Commercially Offered Convenience Services: These are described in
C.47, Value-Added Products and Services, subparagraph C.47.13. Offerors
shall identify and describe offered products and services as well as
terms and conditions, as applicable.

n\) Net Billing (Travel and Purchase Card Programs Only): These are
described in C.47, Value-Added Products and Services, subparagraph
C.47.14.

o\) Card Sleeves: This is described in C.47, Value-Added Products and
Services, subparagraph C.47.15.

p\) Activation/Deactivation on Demand: This is described in C.47,
Value-Added Products and Services, subparagraph C.47.16.

q\) Emerging Technology: These are described in C.47, Value-Added
Products and Services, subparagraph C.47.17. Offerors shall describe any
emerging technology that may add value to the Card Program(s). No
pricing should be included, unless pricing is known and inclusive.

***Block 19 of SF 1449: Contract Line Item Numbers (Section
B)\--Continued***

## B.8 BENCHMARK TASKS: B-FSS-FCXC-\_\_\_ (MAY 1997)

See the following exhibits for the benchmark tasks:

-   Exhibit 2, Benchmark Task for an Integrated Solution

-   Exhibit 3, Benchmark Task for Fleet Card Services

-   Exhibit 4, Benchmark Task for Travel Card Services

-   Exhibit 5, Benchmark Task for Purchase Card Services

#  *Schedule of Services, Performance Work Statement (Section C)*

***SCHEDULE OF SERVICES***

The Government is increasing its reliance on card-based systems as it
continues to seek new and innovative methods to streamline financial and
administrative operations. The Government believes that card services
and technologies currently available and under development for
commercial purposes offer great potential to the Federal Government for
business process improvement. Over the last two decades, the public and
private sectors have been steadily migrating from paper-based systems to
card-based delivery systems to support financial transactions and
associated business processes. The nation\'s commercial infrastructure
for credit and debit card services currently supports magnetic-stripe
based card transactions and technologies. However, the nation\'s
commercial card industry has demonstrated much interest and investment
in improving and expanding services through the increased memory and
computational capabilities of integrated circuit card (ICC) or smart
card systems. Whether supporting a purchase transaction, cash
withdrawal, or electronic network access, commercial industry has
demonstrated the business case and vision for the migration to smart
card systems and technology for the future. The Government shares this
vision with the commercial sector as demonstrated in The President's
Budget for Fiscal Year 1998 which states: "*The Administration wants to
adopt 'smart card' technology so that, ultimately, every employee will
be able to use one card for a wide range of purposes, including travel,
small purchases, and building access.*"

Full realization of this vision will require the creation of standard
platforms to support multi-application card systems for both Government
and commercial purposes. This will require resolution of issues related
to liability, ownership of data, and security of applications and data.
The Government looks to commercial industry to develop the necessary
operating rules and standards and to incorporate them into the services
and products offered to the Government. The Government will proceed to
incorporate such standards into its service requirements and
applications. A partnership of public and private stakeholders is
essential.

The need for business process change is not the only driving force for
the Government's movement to card-based systems and electronic business
processes. Public policy mandates have created deadlines for significant
electronic commerce activity, such as the Debt Collection Improvement
Act of 1996, which requires all federal payments to be made
electronically by 1999. Not only will such mandates increase electronic
commerce activity in the Government, but will also have the subsidiary
effect of stimulating the re-engineering of business processes using all
electronic data. In addition, public policy mandates such as the
Government Performance and Results Act, the Government Management Reform
Act, and the Federal Financial Management Improvement Act all have
called for increased and more accurate performance reporting in the
Government. This increased emphasis on performance reporting and the
consolidated government-wide financial statements required by the
Government Management Reform Act will lead to greater public interest
and demand for accountability and performance. Further, the President's
Budget directs the Government to use electronic means to improve
purchasing and the capture of financial data for easier accounting.
Accurate entry of low level transaction data into the government's
financial systems is key to accomplishing more timely and improved
financial and performance reporting. In addition, this richer
transaction and financial data can be stored in repositories, such as
data warehouses, and aggregated for decision-support analysis.
Electronic commerce and smart or hybrid card system support can provide
the detailed transaction data needed for these purposes.

Many commercial entities currently use third party processors to act as
"brokers" and represent them in electronic commerce. These "brokers"
take much of the risk of technology development and spread it across
multiple entities. The Federal Government seeks to share with commercial
industry such reduced investment and time for systems development by
using such " brokers" to provide some or all of a suite of electronic
commerce services supported by the government's card programs. Rather
than support separate electronic commerce overhead structures across the
government, commercial industry electronic commerce service providers
are solicited to consolidate infrastructure across organizational lines.
The Federal Government is seeking service providers to provide a full
suite of electronic commerce services as needed across the government
based on the government's Card Programs.

The Government envisions the use of card-based systems as essential
tools in its migration from paper-based to electronic systems. Federal
agencies/organizations are looking to automate their business processes,
replacing paper-based processes with electronic transactions and
document flows.

This master contract requests respondents to offer an integrated
solution across two or more of the core Card Programs for fleet, travel,
and purchase. Although this RFP presents each core Card Program as
separate and distinct for contract purposes, there is much similarity
inherent in the three programs that should lead to an integrated
approach for a single or a team of offering card service providers.
Through integration the Government seeks to establish uniform and
complementary processes to support the front-end processes of account
set up and maintenance, card initialization and personalization, card
design and issuance, and cardholder services, newsletter services, and
the "backroom" processes of transaction processing and reporting,
accounting, invoicing, reconciliation, and billing. Through a
consolidated approach to these card services programs, the Government
expects:

a)  to gain efficiencies in Contractor services and prices;

b)  to leverage the costs of investment for new systems and technology;

c)  to coordinate and improve service delivery;

d)  to promote agency/organization expansion of card services available
    through the integrated solution card platform;

e)  to consolidate overhead and other support functions for these Card
    Programs;

f)  to consolidate accounting and reporting data and systems for
    improved financial management;

g)  to reduce information and processing redundancy;

h)  to provide greater convenience and flexibility to cardholders; and,

i)  to reduce the proliferation of single-purpose card systems across
    the government.

These integrated services will be supported by commercial solutions
offered by the contractor that enable the fleet, travel and purchase
card programs to operate in a uniform, streamlined environment. Through
such integration, the Government intends to ultimately use one system or
platform for multiple applications, to consolidate the processes for
card issuance, procurement, payment, reporting and accounting across the
three core business lines to streamline the Government's business
processes. While integration across these services does not necessarily
mean a single card for all purposes, the Government does anticipate that
integrated card systems will be able to support consolidation of
functions, improved and consistent accounting and reporting, and
improved business efficiencies for a wide range of Government business
and administrative functions.

Respondents are encouraged to offer integrated solutions for the master
contract. The Government views the master contract as key to the future
of government business processes by serving as the platform for a wide
range of services supported through card technology.

The master contract not only offers the opportunity for vendors to
propose an integrated solution to the Government\'s business process
needs for the fleet, travel and purchase card programs, but to propose a
broad range of value added services for multi-application card systems
to improve the Government\'s financial and administrative business
processes for these programs**.** The majority of Federal business
process needs can be addressed by the card systems, electronic commerce
products and services that exist in the commercial marketplace today.
Respondents are encouraged to offer a wide range of commercial products
and services for integrated card solutions and value-added services that
can realize the vision of electronic and streamlined government business
processes.

***SCHEDULE OF SERVICES***

## C.1 SCHEDULE OF SERVICES:

The schedule of services is divided into sections as follows:

Performance Work Statement (Section C) - contains general terms and
conditions that are applicable to all business lines. Section C is
further specifically defined for each business line noted below:

a)  Specific to Fleet Card (Section CA)

b)  Specific to Travel Card (Section CB)

c)  Specific to Purchase Card (Section CC);

***DEFINITIONS***

## C.2 DEFINITIONS:

**Account Setup Information:** Specific information required for each
card/account so that an active card/account can be established. This
information is supplied by each ordering agency/organization to the
Contractor. Reference C.34.5, Master File.

**Agency:** The highest level of responsibility for an entity authorized
to use the card/account. This may be an Administration, Agency, Board,
Commission, Corporation, Department, Foundation, Institute, etc. The
agency is then further broken down to include sub-elements of the agency
(e.g., bureau, service, activity, component, division, office, etc.).

**Agency Location Code (ALC):** An ALC is a 3, 4, or 8-digit symbol that
uniquely identifies each agency that reports payments and collections to
the Financial Management Service of the Department of Treasury. It is
similar to a bank account number. An 8 digit numerical ALC is used for
agencies that use the Treasury for disbursing of funds. The first two
digits refer to the agency, the next two digits refer to the Bureau, and
the last four digits refer to the particular agency accounting station.
A 4 digit numerical code is used for agencies which have their own
disbursing authority, i.e. DOD. A 3 digit ALC is used to identify
Treasury Financial Centers.

**Agency/Organization Accounts:** A card/account issued in the
agency/organization name.

**Agency/Organization Identifying Number:** Known as Federal Information
Processing Standards (FIPS), Publication 95-1, these are codes for the
identification of Federal and Federally-Assisted Organizations. This
standard provides a four-character identifier for each organization. The
set of identifiers defines a standard data element. The two leftmost
characters form a component data element which is identical with the
two-digit numerical code used in the Federal budgetary process to
identify major Federal organizations. Agency/Organization Identifying
Numbers may be downloaded from the Internet at:

**http://www.nist.gov/itl/csl/fips/fips95-1.txt**

**Agency/Organization Level:** Any hierarchy level established by the
agency/organization.

**Agency/Organization Program Coordinator (A/OPC):** An individual
designated by the ordering agency/organization to perform task order
contract administration within the limits of delegated authority and to
manage the card program for the agency/organization. This individual
shall have overall responsibility for the card program(s) within their
agency/organization, and may determine who participates in the card
program(s). Specific A/OPC responsibilities are addressed in the
Addendum to Clause 52.212-4, paragraph 34, Agency/Organization Program
Coordinator (A/OPC). Multiple levels of program coordinators are
anticipated within different hierarchies or at different hierarchical
levels within the program for each agency/organization.

**American National Standards Institute (ANSI) Accredited Standards
Committee (ASC):** Any references to ASC X12 standards found herein
pertain to those provided under these Federal conventions. Information
on EC/EDI and how to obtain the Federal Implementation Conventions can
be obtained via the Internet at:

**www.arnet.gov/ecapmo**

**Authorization:** The process of verifying that a purchase being made
is within the authorization controls at the point of sale.

**Automated Clearing House (ACH):** A type of electronic funds transfer.
The ACH is a central distribution point for transferring funds
electronically for participating depository financial institutions.
Rather than each payment being sent separately, ACH transactions are
accumulated and sorted by destination for transmission during a
predetermined period. It includes small dollar payments in large
transaction volume.

**Automated Teller Machine (ATM) Services:** Contractor provided ATM
services which allow cash withdrawals within established dollar limits
from participating ATM\'s to be charged to a contractor-issued
card/account.

**Bank Check:** Contractor-provided product and service which allow
checks to be written on a card/account within established dollar limits.

**Billing Cycle:** A specific recurring time period between the time
statements of account and invoices are processed.

**Business Day:** Monday through Friday except Federal holidays.

**Cardless Account:** An established account without a physical card.

**Centrally Billed Account:** A card/account established by the
Contractor at the request of the agency/organization. These may be
card/cardless accounts. Payments are made directly to the Contractor by
the agency/organization. All fleet and purchase cards are centrally
billed cards/accounts. Agencies/organizations will specify which travel
and integrated solution cards should be centrally billed cards/accounts
in their task orders.

**Closing Date:** The closing date is the close of the billing cycle
date assigned to the account. Also referred to as the billing cycle
date.

**Core Requirements:** Minimum Government-wide requirements specified in
detail. All contractors must provide core requirements and the vast
majority of customers will utilize core requirements. Core requirements
are referred to as "Tier 1."

**Customization:** The standard commercial practice of creating reports,
invoices, and services to meet unique needs or to a specific customer.

**Debit Card:** Contractor-provided product and service that debits an
account/fund within established dollar limits. May be on-line or
off-line. When the debit card is presented for authorized payment, funds
are debited directly from an established financial account/fund.

**Declined Transactions:** Those transactions where authorization has
been refused by the card Contractor\'s transaction authorization system.

**Designated Billing Office (DBO):** The office designated by the
ordering agency/organization to receive the official invoice and, in
some instances, make payments against the official invoice. Specific DBO
responsibilities are addressed in the Addendum to Clause 52.212-4,
paragraph 35, Designated Billing Office (DBO).

**Domestic:** All 50 states, the District of Columbia and US Territories
and Possessions.

**E-Purse:** A product and service that contains an established block of
dollars that are stored on the card or network. These can be off-line
accountable systems or on-line systems. They may be rechargeable or
disposable. Also called stored value card.

**Electronic:** A method of communication whereby information is
disseminated by floppy disk, optically stored media, magnetic tape,
computer disks, microfiche, microfilm, computer to computer
communications via modem, Networks (value added), facsimile, or other
electronic method of dissemination.

**Electronic Commerce:** The use of documents in electronic form, rather
than paper, for carrying out functions of business or government (such
as finance, logistics, procurement, and transportation) that require
interchanges of information, obligations, or monetary value between
organizations.

**Electronic Commerce/Electronic Data Interchange Office (EO):** The
office designated by the ordering agency/organization for EC/EDI
functions and support. Specific EO responsibilities are addressed in the
Addendum to Clause 52.212-4, paragraph 37, EC/EDI Office (EO).

**Electronic Data Interchange (EDI):** EDI is the computer-to-computer
transmission of strictly formatted messages that represent documents.

**Electronic Funds Transfer (EFT):** A term which identifies delivery
systems used to transfer payments of funds electronically. These systems
transfer funds faster and more securely than transfers authorized by
paper check.

**Fedwire:** One of the major wire transfer systems directly connected
to the Federal Reserve Bank. Wire transfer of funds are executed through
the Fedwire network, which is tied to all federal reserve branches,
depository financial institutions, the Financial Management Service and
other government agencies/organizations. It is a method of electronic
funds transfer. These payments usually involve large dollar amounts
associated with small transaction volume.

**Fiscal Year:** October 1 through September 30.

**Format(s):** Arrangement of information for a particular purpose.

**Inter/Intra-Governmental Service:** Merchant acquiring services which
involves setting up merchant agencies. This service is used for
inter/intra-agency operations and payments in conjunction with the
fleet, travel and purchase cards.

**International:** Locations not domestic.

**Internet:** An electronic public forum for information and commerce.

**Intranet:** An electronic private forum for information and commerce.

**Level I Data:** Standard commercial transaction data which includes
the total purchase amount, the date of purchase, the merchant category
code and the merchant's name.

**Level II Data:** Adds additional data to Level I data about each
purchase which includes sales tax amount, accounting code, merchant TIN,
minority/women owned business codes, 1099 status and merchant city,
state and zip code.

**Level III Data:** Full line-item detail in addition to the data in
Level II which includes unit cost, quantities, unit of measure, product
codes, product descriptions, ship to/from zip codes, freight amount,
duty amount, order date, discount amount, and order number.

**Mandatory User:** Agencies/organizations that have agreed to be
mandatory users of one or more of the business line(s) under the GSA
contract and one or more component(s) of a particular business line
(e.g., ATM, travelers checks, bank checks). These agencies/organizations
are precluded from purchasing similar fleet, travel and/or purchase card
products and services outside of this master contract. Contractors shall
accept all orders from mandatory users.

**Master File:** This file is maintained by the contractor. It contains
all essential account information described herein (see C.34.5, Master
File).

**Media:** A broad spectrum of methods used to provide a permanent
record of communications (e.g., paper, EDI, electronic, floppy disk,
optically stored media, computer disks, microfiche, microfilm, computer
to computer communications via modem, Networks (value added), facsimile,
or any other acceptable methods of available communication).

**Merchant Category Code:** A Contractor-assigned categorization of the
type of business the merchant is engaged in and the kinds of goods and
services provided. These codes are used as an authorized transaction
type code on a card/account to identify those types of businesses who
provide goods and/or services that are authorized.

**Non-Mandatory User:** Agencies/organizations that have not agreed to
be mandatory users of one or more of the business line(s) under the GSA
contract and one or more component(s) of a particular business line
(e.g., ATM, travelers checks, bank checks). These agencies/organizations
may use the GSA contract for their fleet, travel and/or purchase card
products and services, but are not under any obligation to do so.
Contractors may accept orders from non-mandatory users.

**Official Invoice:** A proper invoice, containing the data required by,
and formatted in accordance with contract specifications requesting
payment be made to the Contractor.

**Official Notification:** Written or electronic notification to the
Contractor by either the GSA Contracting Officer regarding contractual
issues, or by a Customer regarding their cards/accounts or reports.

**Organization:** Individuals or entities authorized to use GSA sources
of supply as specified by the GSA Contracting Officer.

**On-Line:** Direct access to computer-based data files and operations
systems via computer terminals.

**Personal Identification Number (PIN):** Code the card/account holder
possesses for verification of identity when using a card.

**Quarterly:** The Federal fiscal year divided into quarters is as
follows: First quarter, October 1 through December 31; second quarter,
January 1 through March 31; third quarter, April 1 through June 30; and
fourth quarter, July 1 through September 30.

**Roll-Up Section:** Aggregated reporting/access to program and
transaction data at the level specified by the agency/organization.

**Signature:** Discrete, verifiable symbol of an individual affixed to a
document, with the knowledge and consent of the individual.

**Stored Value Card:** A product and service that contains an
established block of dollars that are stored on the card or network.
These can be off-line accountable systems or on-line systems. They may
be rechargeable or disposable. Also called E-Purse.

**Sub-Accounts:** Agencies/Organizations may require that sub-accounts
be set up under their account to identify and separate charges for
specific components within agencies/organizations. Each of these
agencies/organizations may require their own sub-accounts for electronic
access, reporting and/or billing.

**Suspension:** The process in which an ordering office is prohibited
from making purchases with the card program due to delinquency or
multiple pre-suspension actions.

**Task Order:** A document that specifies and authorizes products and
services required and the negotiated price at which they will be
provided.

**Task Order Ombudsman:** The GSA individual that reviews Contractor
complaints and ensures that all Contractors receive a fair opportunity
to be considered, consistent with the contract procedures (as required
under Section 303J(e) of the Federal Property and Administrative
Services Act of 1949, as amended).

**Taxpayer Identification Number (TIN):** A TIN is the number required
by the Internal Revenue Service (IRS) to be used in reporting income tax
and on other returns. This may be either a Social Security Number (SSN)
or Employer Identification Number (EIN).

**Tier 1:** Core government-wide requirements.

**Tier 2:** Value-added products and services.

**Transaction Dispute:** A disagreement between the cardholder or
account holder and the merchant with respect to a transaction.

**Transaction Dispute Office (TDO):** The office designated by the
ordering agency/organization that assists the agency/organization and
the Contractor in tracking and resolving disputed purchases or
transactions. Specific TDO responsibilities are addressed in the
Addendum to Clause 52.212-4, paragraph 36, Transaction Dispute Office
(TDO).

**User Friendly:** Ease of use geared towards those with a rudimentary
or limited knowledge of computer systems and operations. The typical
knowledge base includes how to log on and off the system, simple
menu-based functions (e.g., point and click functions such as file,
open, close, etc.), simple one-step commands (e.g., search, print, save,
etc.).

**Value-Added Products and Services:** A set of selected products and
services available to agencies/organizations and separately priced.
Value-added products and services are referred to as "Tier 2." (See
C.47, Value-Added Products and Services.)

**Value Added Tax (VAT):** A broad-based sales tax levied on business
services purchased in the European community.

***SCOPE OF WORK***

## C.3 SCOPE OF WORK 

The purpose of the master contracts is to provide a worldwide
procurement, payment and functional data storage mechanism to support
authorized purchases, expenses, and/or streamline purchase and payment
systems for the Fleet, Travel, Purchase and Integrated Solution Card
Programs. All financial, management and administrative products and
services, current and emerging, which assist in the support of
authorized purchases, expenses and/or streamline purchase and payment
systems falls within the scope of this contract. The Contractor shall
provide the necessary products and services to accomplish all of the
requirements stated herein.

***ELIGIBILITY***

## C.4 AGENCY/ORGANIZATION ELIGIBILITY DETERMINATIONS 

Mandatory agencies/organizations (see Exhibits 10, 11 and 12) wishing to
participate in the program shall issue a task order against the GSA
contract directly to the Contractor. Non-mandatory users shall send a
task request/order to the General Services Administration, Federal
Supply Service, Services Acquisition Center (FCX) ATTN: Rebecca Koses,
Washington DC 20406. The GSA Contracting Officer and/or his/her designee
will forward all approved task requests/orders from non-mandatory
eligible participants to the Contractor with the name and point of
contact for each agency/organization deemed eligible to participate in
this contract. The services for which the participant has been approved
shall be identified on the task request/order. (See the Addendum to
Clause 52.212-4, paragraph 23, Scope of Contract for the Fleet Card;
paragraph 24, Scope of Contract for the Travel Card; and paragraph 25,
Scope of Contract for the Purchase Card.)

***PROGRAM OBJECTIVES***

## C.5 OBJECTIVES

The objectives of the Government's Card Program(s) are to:

-   Gain cost efficiencies;

-   Simplify financial processes;

-   Provide efficiency and convenience through single-card capability;

-   Improve Government operations, particularly accountability and
    performance reporting;

-   Provide procedural checks and feedback to improve security and
    management control on financial transactions and processes;

-   Create the platform for a wide range of Government functions and
    services to be accessed through a single card or system;

-   Improve Government cash management practices;

-   Consolidate payments where possible;

-   Reduce/eliminate imprest funds;

-   Streamline procurement, payment and administrative procedures;

-   Obtain detailed and tailored management reports;

-   Follow commercial rules, procedures and best practices;

-   Provide convenience to Government employees; and

-   Take advantage of state-of-art technology and technological
    advances.

The Government's requirements seek consistency with the best commercial
practices.

***EC/EDI REQUIREMENTS***

## C.6 ELECTRONIC COMMERCE/ELECTRONIC DATA INTERCHANGE (EC/EDI) 

The goal of the Federal EC/EDI program is to present a consistent face
to industry in EC/EDI applications. Government activities will conduct
EC using EDI in accordance with American National Standards Institute
(ANSI) Accredited Standards Committee (ASC) X12 standards, common
implementation conventions, a common communications infrastructure, a
common set of business practices, and commercial off-the-shelf hardware
and software. Thus, all electronic business transactions will be
exchanged with trading partners in a similar manner, regardless of the
agency/organization. Different automated information systems, using
different technologies, are able to transmit through various
communication systems to arrive at a common point where the transactions
are exchanged in similar manner to our customers. Many Government
activities have existing systems with some level of EDI capability that
make use of ANSI ASC X12 standards, but many of these systems currently
stand alone. Over time, the Federal Government will migrate to a common
standard for EC.

The Contractor shall have the capability to successfully perform EC/EDI
under this contract within **60 calendar days** of the
agency's/organization's ability to come on line to Federal EC/EDI
standards. The Contractor's EDI capability shall adhere to the
Electronic Commerce Federal Implementation Conventions (IC), as provided
through the National Institute of Standards and Technology. These
conventions are based on the ANSI ASC X12.

The Contractor's system for receiving and retransmitting electronic
forms shall, at a minimum, meet the data requirements of ASC X12 release
current with the Federal Implementation Conventions and the implementing
guidelines specific to the system with which the contractor will be
exchanging information. The Contractor shall also be capable of
performing EC/EDI that is compliant with the UN/EDIFACT standards used
for international commerce.

The Contractor's system shall, at a minimum, be able to retrieve, store,
transmit, and process the following electronic transaction sets: ANSI
810 - Invoice; ANSI 811 - Consolidated Service Invoice/statement; ANSI
812 - Debit/Credit Adjustment; ANSI 820 - Payment Order/Remittance
Advice; ANSI 821 - Financial Reporting; ANSI 824 - Application Advice;
and ANSI 997 - Functional Acknowledgment; and other transaction sets as
IC's are developed and published.

The Contractor shall also assist in developing processes, guidance and
as appropriate, implementation support for agencies/organizations to
implement EC/EDI for card processes. Further, the Contractor shall work
with agencies/organizations to ensure that appropriate systems guidance
includes complete systems documentation, test transactions and
procedural guidance for each document type. The Contractor shall be able
to perform tests on the system at no cost to the Government.

***SUMMARY OF PROGRAM REQUIREMENTS***

## C.7 CARD PROGRAM(S) REQUIREMENTS

The Contractor shall provide a program(s) that provides for:

-   Widespread domestic and international merchant acceptance;

-   Centrally billed accounts (including agency/organization or
    vehicle/equipment accounts);

-   Commercial billing and payment terms to the maximum extent
    practicable;

-   Automated systems;

-   Operational support;

-   Training support;

-   Implementation support;

-   Transaction dispute support; and

-   Transition support.

For additional Card Program(s) requirements, reference CA.3, Fleet Card
Program Requirements, CB.3, Travel Card Program Requirements, and CC.3,
Purchase Card Program Requirements.

***MERCHANT ACCEPTANCE***

## C.8 MERCHANT ACCEPTANCE

The Contractor shall have a mechanism in place to add new merchants and
merchant types to their network as needed by agencies/organizations. The
Contractor shall assist, as requested, in promoting the benefits of
accepting the card and recruiting merchants that do not currently accept
the card. These actions can include preparation of vendor brochures that
discuss benefits of acceptance, enrollment information, contact with the
merchant, etc. The Government will identify merchants for recruitment,
where necessary.

For additional merchant acceptance requirements, reference CA.4,
Merchant Acceptance for the Fleet Card Program, CB.4, Merchant
Acceptance for the Travel Card Program and CC.4, Merchant Acceptance for
the Purchase Card Program.

C.8.1 *Point of Sale Discounts:* Any merchant product or service
discount negotiated by the Government on its own behalf directly with
the merchant shall be identified where the discount information is
provided to the Contractor by the merchant through the transaction
process. For example, the Government negotiated 10% off all supplies
purchased at an office supply store. The Government would be responsible
for providing the merchant with the appropriate account number ranges or
other identifying process. This type of discount is not one which the
Contractor would guarantee; however, the Contractor shall pass on the
discount information provided by the merchant. The discount would be
taken off by the merchant prior to the occurrence of the financial
transaction between the merchant and card service provider. The card
service provider's transaction fee/merchant discount would be based on
the NET price (less the discount offered to the Government by the
merchant). The discount information passed with the transaction would be
informational only. Contractors may offer net billing services as
described in C.47.14, Net Billing.

***GROWTH AND TECHNOLOGY***

## C.9 PROGRAM VOLUME GROWTH AND TECHNOLOGICAL ADVANCES

The Contractor shall demonstrate the ability to successfully accommodate
program volume growth (see Exhibit 6 (Fleet Card Program), Exhibit 7
(Travel Card Program) and Exhibit 8 (Purchase Card Program)) with
minimal disruption to the card program(s). All upgrades or replacement
equipment and software required by the Contractor to accommodate program
volume growth are the Contractor's responsibility. The Contractor shall
ensure that any change brought about by program volume growth is
effectuated in a smooth, seamless manner, with minimal disruption to the
card program(s). The Contractor shall coordinate any such change with
the participating users and the GSA Contracting Officer at least **90
calendar days** in advance, unless otherwise directed by the GSA
Contracting Officer.

The Contractor shall utilize its best efforts to ensure that the
products and services offered are current with commercial practice and
assist in maximizing efficiencies to the Government. Products and
services offered should be state-of-the-art and provide the
technological advances that are consistent with the commercial
marketplace, unless otherwise directed by the GSA Contracting Officer.

***QUALITY***

## C.10 QUALITY ASSURANCE

The Contractor shall maintain a quality assurance program that shall:

a)  Ensure the quality of the card products and card services provided
    under this contract;

b)  Ensure that the information captured for reports in accordance with
    this contract is complete, accurate, and timely;

c)  Ensure timely delivery of cards;

d)  Ensure that customer service assistance is available in accordance
    with the terms and conditions of this contract and is prompt,
    cooperative and courteous;

e)  Ensure that payments received on all accounts are posted in
    accordance with the terms and conditions of this contract;

f)  Ensure that transitions are seamless and in accordance with C.41,
    Transition Requirements;

g)  Annually assess A/OPC, DBO, TDO and EO, agency/organization and user
    satisfaction with the card program(s) and contractor performance.
    This can be accomplished through satisfaction surveys or other
    approved tools that provide comprehensive feedback on all aspects of
    the card program(s) and contractor performance. The Contractor shall
    submit the results of the survey or other approved tools, as well as
    the methodology and participants utilized, to the GSA Contracting
    Officer no later than the **30th calendar day** following each 12
    month contract period. For example, if award of the contract was
    made on 10/01/98, the results of the survey would be due no later
    than 10/30/99.) GSA reserves the right to verify survey results; and

h)  Continually monitor the quality of services provided by the
    contractor.

In addition, some agencies/organizations may require additional quality
assurance measures in their task order that may include specific
requirements and request pricing for feedback and evaluation.

***CREDIT BUREAUS***

## C.11 REPORTING OF CENTRALLY BILLED ACCOUNTS TO CREDIT BUREAUS

The Contractor shall not provide any information regarding a Federal
Government centrally billed account(s) to credit bureaus.

***DELINQUENCY CONTROL***

## C.12 DELINQUENCY CONTROL FOR CENTRALLY BILLED ACCOUNTS

The Contractor shall not utilize a collection agency for delinquency
control on Federal Government centrally billed accounts. The Contractor
may request the GSA Contracting Officer's assistance in resolving
delinquent centrally billed accounts.

If any in-house collection effort results in a final settlement action,
all Contractor records and reports shall so reflect the settlement
action and debt shall be considered discharged.

***SECURITY, BACKUP, AND INVESTIGATIVE/AUDIT ASSISTANCE***

## C.13 SECURITY REQUIREMENTS

The Contractor shall, at a minimum, meet the security requirements of
any Bank or Credit Card Association to which it belongs or the
Contractor's own security procedures and submit such
requirements/procedures for Government review as well as any subsequent
updates throughout the contract period. In addition, the Contractor's
own security procedures shall be incorporated into any resultant
contract. The Contractor's systems security procedures and measures
shall protect the integrity, security and proper functioning of all
databases and systems involved in the operation of the Card Program(s).
The databases and information processing systems containing Government
information shall have security measures to protect against deliberate
or inadvertent loss, degradation, alteration, or damage of information
from unauthorized access.

In addition, some agencies/organizations require a higher level of
security to include personnel and physical security requirements (e.g.,
if the Contractor has access to government sensitive systems, there
should be some level of background checks or investigation conducted for
those with access). If additional security is required, the
agency/organization will specify further requirements and request
pricing in its task order.

## C.14 SYSTEM BACKUP

The Contractor shall have a backup system in place and procedures to
ensure that services are not interrupted during system failures or
normal system maintenance procedures such as database updates. The
backup system shall secure and protect all information and data in the
Government Card Program(s) against deliberate or inadvertent loss,
degradation, alteration, or damage of information. The backup system
shall be seamless and ensure continuity of the Government's Card
Program(s).

## C.15 INVESTIGATION ASSISTANCE

The Contractor shall assist any authorized investigative unit (e.g., The
Office of Inspector General or authorized representative, or the
ordering or GSA Contracting Officer or authorized representative) of the
US Government concerning alleged wrongdoing or suspected fraud, waste or
abuse by agency/organization employees or those entities doing business
with the US Government using the Card Program(s). If Government records
are required to assist in the authorized investigative unit's
investigation efforts, the Contractor shall provide any data requested
within the timeframes mutually-agreed to by the Contractor and the
authorized investigative unit, unless otherwise specified by the
ordering or GSA Contracting Officer.

## C.16 AUDIT ASSISTANCE

The Contractor shall assist any authorized audit unit (the ordering or
GSA Contracting Officer, or an authorized representative, or the
Comptroller General of the United States, or an authorized
representative) of the US Government by providing reasonable access to
all card program(s) administrative, financial and management data. If
Government records are required to assist in the authorized audit unit's
investigation efforts, the Contractor shall provide any data requested
within the timeframes mutually-agreed to by the Contractor and the
authorized audit unit, unless otherwise specified by the ordering or GSA
Contracting Officer.

***COMMUNICATION OF PROGRAM INFORMATION***

## C.17 MARKETING AND ADVERTISING

All marketing and advertising of its products and services under the
Government's Card Program(s) shall be the responsibility of the
Contractor. Marketing and advertising materials relative to the
Government's Card Program(s) shall be precluded from (1) implying
Government endorsement of the product/service or of one contractor over
another; (2) interpreting contract terms or conditions; or (3) using
Government official seals and logos, excluding the Government-provided
card design(s). All marketing and advertising materials relative to the
Card Program(s) shall be submitted to the GSA Contracting Officer for
written approval prior to initial dissemination. The GSA Contracting
Officer will review materials for content and provide written
approval/disapproval within 14 calendar days of receipt of the
Contractor's materials. Revisions must be submitted to allow sufficient
time for re-review without delaying distribution.

Transmittal letters and other form-type letters may be granted blanket
approval using the process described above.

All travel costs associated with marketing and advertising shall be
borne by the Contractor. Using approved materials, the Contractor may
direct-market agencies/organizations after the master ceremony of the
kick-off conference (reference C.27.3, Kick-Off Conference), contract
start-up, annual conferences, newsletters, or upon request from an
agency/organization.

## C.18 MASTER CONTRACT NEWSLETTER

The Contractor shall develop and electronically distribute a quarterly
master contract newsletter to all A/OPC program participants. Each
newsletter shall include, at a minimum, program information, news,
issues relative to the business line and card program, and a disclaimer
as follows: "This newsletter is not a legal document. The information
provided is for general use only. Contact the GSA Contracting Officer
with any questions related to proper use of the master contract." Prior
to distribution, the Contractor shall obtain the GSA Contracting
Officer's written approval of the content of the newsletter. The GSA
Contracting Officer will review materials for content and provide
written approval/disapproval within 14 calendar days of receipt of the
Contractor's materials. Revisions must be submitted to allow sufficient
time for re-review without delaying distribution. The GSA Contracting
Officer reserves the right to require publication of specific
information and also reserves the right to edit the newsletter. The
newsletter shall be available to A/OPC program participants
electronically, at the discretion of the agency/organization, through
the Internet or through an agency's/organization's Intranet, using any
specifications or requirements that are designated by the
agency's/organization's Intranet.

## C.19 STATEMENT INSERTS

Statement inserts provide a method in which the Government and the
Contractor can disseminate information about the Card Program(s) and
program-related matters. The Contractor shall provide the GSA
Contracting Office, GSA Program Office, and agencies/organizations the
ability to include electronic or paper statement inserts into cardholder
statements of account to reach selected or entire government audiences
(e.g., only to GSA employees, all participating agencies/organizations,
etc.).

If the Contractor uses the statement insert feature relative to the Card
Program(s), the Contractor shall be precluded from the prohibitions
described in C.17, Marketing and Advertising. Further, all
Contractor-requested statement inserts relative to the Card Program(s)
shall be submitted to the GSA Contracting Officer for written approval
prior to dissemination. The GSA Contracting Officer will review
materials for content and provide written approval/disapproval within 14
calendar days of receipt of the Contractor's materials. Revisions must
be submitted to allow sufficient time for re-review without delaying
distribution. The GSA Contracting Officer reserves the right to edit
statement inserts.

If an agency/organization uses the statement insert feature relative to
the Card Program(s), the Contractor shall ensure that
agency/organization-requested insert does not:

-   Imply Government endorsement of the product/service or of one
    contractor over another; or

-   Interpret master contract terms or conditions.

If the Contractor is in doubt as to the content of the insert, it shall
contact the GSA Contracting Officer for direction. Further, all
agency/organization-requested statement inserts relative to the Card
Program(s) shall be submitted directly to the Contractor, using any
Contractor-stated specifications (e.g., size, quantities, frequency,
other parameters) required for the electronic or paper statement insert.
The Contractor may suggest editing revisions to the content of the
agency's/organization's statement insert. In the event of significant
program issues (e.g., agency/organization gross misstatement of fact,
possible release of proprietary information, etc.) that the Contractor
may be concerned with regarding an agency's/organization's statement
insert, it shall contact the GSA Contracting Officer for assistance.

The Contractor shall process statement inserts on a first-come,
first-serve basis; however, if multiple inserts are requested
concurrently for the same audience, the GSA Contracting Officer will
determine the priority of the inserts. The GSA Contracting Officer has
the right to override the Contractor's or agency's/organization's
designation of the priority of the inserts.

The Contractor shall not allow any third-party to utilize the statement
insert feature, unless approved in writing by the GSA Contracting
Officer.

## C.20 STATEMENT MESSAGING

Statement messaging provides a method in which the Government and the
Contractor can disseminate information about the Card Program(s) and
program-related matters. The Contractor shall provide the GSA
Contracting Office, GSA Program Office, and agencies/organizations the
ability to include electronic statement messaging with the cardholder
statements of account to reach selected or entire government audiences
(e.g., only to GSA employees, all participating agencies/organizations,
etc.).

If the Contractor uses the statement messaging feature relative to the
Card Program(s), the Contractor shall be precluded from the prohibitions
described in C.17, Marketing and Advertising. Further, all
Contractor-requested statement messaging relative to the Card Program(s)
shall be submitted to the GSA Contracting Officer for written approval
prior to dissemination. The GSA Contracting Officer will review
materials for content and provide written approval/disapproval within 14
calendar days of receipt of the Contractor's materials. Revisions must
be submitted to allow sufficient time for re-review without delaying
distribution. The GSA Contracting Officer reserves the right to edit
statement messaging.

If an agency/organization uses the statement messaging feature relative
to the Card Program(s), the Contractor shall ensure that
agency/organization-requested messaging does not:

-   Imply Government endorsement of the product/service or of one
    contractor over another; or

-   Interpret master contract terms or conditions.

If the Contractor is in doubt as to the content of the messaging, it
shall contact the GSA Contracting Officer for direction. Further, all
agency-/organization-requested statement messaging relative to the Card
Program(s) shall be submitted directly to the Contractor, using any
Contractor-stated specifications (e.g., word limits, frequency, other
parameters) required for the electronic statement messaging. The
Contractor may suggest editing revisions to the content of the
agency's/organization's statement messaging. In the event of significant
program issues (e.g., agency/organization gross misstatement of fact,
possible release of proprietary information, etc.) that the Contractor
may be concerned with regarding an agency's/organization's statement
messaging, it shall contact the GSA Contracting Officer for assistance.

The Contractor shall process statement messaging on a first-come,
first-serve basis; however, if multiple messaging is requested
concurrently for the same audience, the GSA Contracting Officer will
determine the priority of the messagings. The GSA Contracting Officer
has the right to override the Contractor's or agency's/organization's
designation of the priority of the messagings.

The Contractor shall not allow any third-party to utilize the statement
messaging feature, unless approved in writing by the GSA Contracting
Officer.

## C.21 MASTER CONTRACT TRAINING CONFERENCE

As directed by the GSA Contracting Officer, the Contractor shall
participate in one annual A/OPC master contract training conference at
different geographic locations each year (e.g., the first conference may
be in Washington, DC; the second conference may be on the West coast,
the third may be on the East coast, the fourth may be in the Midwest,
etc.). The annual master contract training conference is anticipated to
be a duration of 4 to 5 days and generally comprised of an opening
master ceremony and break outs to individual training classes that
repeat throughout the length of the conference.

All contractors under the master contract shall concurrently participate
in this conference at the request of the GSA Contracting Officer;
however, the GSA Contracting Officer reserves the right to require
separate training conferences for each business line. This conference
shall cover a variety of topics of interest to the Card Program(s) and
include training on the various aspects of the Card Program(s). Examples
of such topics include policies, regulations, frequently asked
questions, agency/organization best practices, etc. Examples of such
training include electronic access, reconciliation, account set-up, etc.
The content of the training conference will be directed by the GSA
Contracting Officer.

The GSA Contracting Officer will be responsible for selecting the
training location, contracting for the facility, arranging for
presenters/speakers, and assuming primary responsibility for logistics.
The Contractor shall be responsible for identifying agency/organization
best practices and points of contact, all Contractor training materials
and instructors, the individual cost of any audio-visual equipment and
set up specifically required for their training classes, all
Contractor's travel, per diem, and personnel costs.

The GSA Contracting Officer reserves the right to require the Contractor
to assist in the logistics of the training conference by providing
personnel resources to assist in preparing/mailing invitations;
compiling and reporting registration; preparing name badges; collecting
and remitting training fees, if any. on GSA's behalf, including setting
up the GSA Contracting Office as a merchant specific for these
conferences to accept card payments where the Contractor has merchant
acquiring abilities commercially available; providing confirmation;
preparing training and/or welcome packets; and manning registration
tables, at no additional cost to the Government. If the GSA Contracting
Officer exercises this right, Contractor assistance will be limited to
his/her business line and further limited to his/her participating
government clients (e.g., the Contractor will help prepare/mail
invitations to his/her A/OPC base, but not to the entire master contract
Card Program A/OPC base).

The Contractor may use this forum to introduce new products and services
as approved by the GSA Contracting Officer, or to market and advertise
their products and services as approved by the GSA Contracting Officer
to potential agency/organization customers. This may include setting up
a booth that is similar to those found in standard commercial trade
fairs. The Contractor shall be responsible for all costs associated with
marketing and advertising, including any booth rent, audio-visual
equipment and set up, etc. However, the primary focus of this conference
shall be training on the Card Program(s), products and services. The GSA
Contracting Office fully intends to participate in and/or present
program information during the conference.

In the event of cancellation of the annual training conference, the
Contractor shall bear all Contractor costs associated with the
cancellation. The GSA Contracting Officer reserves the right to not have
an annual training conference.

## C.22 RELEASE OF PROGRAM INFORMATION

The Contractor shall not use names, addresses, or any other account or
card information for any purpose other than that specified in this
contract. The Contractor shall not release, sell, or make available any
information to any third party except as otherwise specifically provided
in the contract.

***CARD DESIGN***

## C.23 CARD DESIGN AND EMBOSSING

The Government will provide background card designs (see Exhibit 12
(Integrated Solution), Exhibit 13 (Fleet Card Program), Exhibit 14
(Travel Card Program) and Exhibit 15 (Purchase Card Program)) for
non-generic cards for each business line to be utilized on all
non-generic cards issued under this contract. Non-generic cards are
defined as all tier 1 cards except those cards discussed in C.23.2,
Generic Card Requirements, and CB.5.4, Quasi-Generic Card Requirements.
The Government may utilize more than one background design for control
purposes. The Contractor shall be responsible for the embossing/printing
of the cards. The final card model shall be submitted to the GSA
Contracting Officer **2 weeks** after contract award for written
approval. The Contractor shall immediately correct and replace any cards
issued that contain Contractor-caused errors at its expense. Additional
requirements appear in each business line (reference CA.5, Card Design
and Embossing for the Fleet Card Program, CB.5, Card Design and
Embossing for the Travel Card Program and CC.5, Card Design and
Embossing for the Purchase Card Program).

The Government reserves the right to add other card designs during the
contract period.

C.23.1 *Back Side of Cards:* The Contractor's customer service toll-free
or collect telephone number shall appear on the back side of the card.

C.23.2 *Generic Card Requirements:* If requested by a participating
agency/organization, the Contractor shall also provide a generic card,
using the Contractor's commercial design, showing no association with
the Government. This shall include, when requested by a participating
agency/organization, an account number which is indistinguishable from
nongovernment personal cards. Generic cards issued under this contract
shall be subject to the terms and conditions of this contract, except
C.32, Tax Exempt Status. Each generic card shall be embossed with the
following:

a)  Account name;

b)  Account number; and

c)  Expiration date.

C.23.3 *Sample/Test Card Requirements:* From time to time, the GSA
Contracting Office, GSA Program Office, or A/OPCs may request "sample"
cards for demonstration or quality testing purposes only. Sample cards
shall have the appearance of the final card model as described in C.23,
with the embossing and printing required for each business line
(reference CA.5, Card Design and Embossing for the Fleet Card Program,
CB.5, Card Design and Embossing for the Travel Card Program and CC.5,
Card Design and Embossing for the Purchase Card Program), but have no
charge capability. Sample cards shall have prominently printed or
embossed on the face of the card "SAMPLE CARD." Test cards may be blank,
have a unique test card appearance, or may appear the same as the cards
described herein. Test cards will have limited charge capability. These
cards may be used to test card quality, inter-agency payment systems,
and other emerging processing capabilities as they become available
under this contract. Test cards shall have prominently printed or
embossed on the face of the card "TEST CARD."

C.23.4 *Camera Ready Art:* The Contractor shall provide to A/OPCs or the
GSA Contracting Office camera ready art of the final finished card
model, as requested.

***ACCOUNT NUMBER***

## C.24 ACCOUNT NUMBER

The Contractor shall have adequate numbers of prefixes unique to the
Government for fleet, travel and purchase card accounts. The Contractor
shall, within a common numbering system, assign a Government-unique
account number to each card issued under the master contract, except for
situations covered by C.23.2, Generic Card Requirements. The numbering
system shall be dedicated solely to the Federal Government.

The Contractor shall not utilize the same numbering system or sequence
for other business purposes, including other Federal Government
contracts.

It is imperative that the numbering system be unique to the Federal
Government and to the master contract, as it serves as an important
control mechanism to access Government-only products and services. The
Government reserves the right to require multiple prefixes, separate
numbering systems or sequence for control purposes.

For additional requirements specific to the travel card, reference CB.6,
Account Number for the Travel Card Program.

***TRAINING***

## C.25 TRAINING REQUIREMENTS

NOTE: THE TIMEFRAMES STATED BELOW ARE EFFECTIVE NOVEMBER 30, 1998.
INITIAL CONTRACT START-UP TIMEFRAMES ARE STATED IN C.27, START-UP
IMPLEMENTATION REQUIREMENTS.

The Contractor, at its expense, shall provide training materials as
specified below. The Contractor shall:

1)  At the agency's/organization's discretion, provide training
    materials through the Internet or through the
    agency's/organization's Intranet, using any specifications required
    by the agency's/organization's Intranet at Contractor expense;

2)  Provide a limited number of hard copies of each training material to
    the A/OPC and GSA Contracting Office as requested;

3)  Provide on-site training to groups of 25 or more A/OPCs, Designated
    Billing Office and Transaction Disputes Office points of contact or
    any combination thereof, at the request of the agency/organization.
    All Contractor travel and travel-related costs associated with
    on-site training shall be borne by the Contractor;

4)  Assist in training agencies/organizations on all aspects of the Card
    Program(s), products and services;

5)  Develop and distribute training materials as described in each
    business line;

6)  Periodically revise training materials as required by the GSA
    Contracting Officer or as desired by the Contractor and
    communicating any approved revisions to all participants; and

7)  Educate program users on vendor responsibilities under their
    merchant agreements that are pertinent to the Card Program(s).

In addition to the requirements stated in this section, each business
line contains additional requirements as referenced in CA.6, Training
Requirements for the Fleet Card Program, CB.7, Training Requirements for
the Travel Card Program and CC.6, Training Requirements for the Purchase
Card Program. Contractor training materials shall be precluded from:

a)  Implying Government endorsement of the product/service or of one
    contractor over another;

b)  Interpreting contract terms or conditions;

c)  Being promotional in nature; or

d)  Using Government official seals and logos, excluding the card
    design(s).

Further, all Contractor training materials, and subsequent modifications
thereto, relative to the Card Program(s) shall be submitted to the GSA
Contracting Officer for written approval prior to initial dissemination.
The GSA Contracting Officer will review materials for content and
provide written approval/disapproval within 14 calendar days of receipt
of the Contractor's materials. Revisions must be submitted to allow
sufficient time to re-review without delaying distribution. The GSA
Contracting Officer reserves the right to edit training materials.

C.25.1 *Cardholder Guide:* The Contractor shall develop a guide to be
issued with each card for use by individual cardholders. This guide
shall be sufficiently detailed to serve as a stand-alone reference for
the cardholder. At a minimum this guide shall include:

a)  Procedures for reporting lost or stolen cards;

b)  Replacement card ordering procedures;

c)  Explanation of electronic access screens, necessary key sequences
    and functions for reviewing purchases and disputing a transaction
    electronically;

d)  Account suspension and cancellation procedures;

e)  Payment requirements;

f)  Authorized uses of the card;

g)  Foreign currency conversion procedures;

h)  List of cardholder responsibilities; and

i)  Toll-free or collect customer service telephone number.

The Contractor shall distribute a copy of the Cardholder Guide to each
participating A/OPC within **ten (10) calendar days** of the
Contractor\'s receipt of a task order issued in accordance with the
terms and conditions of this contract. A copy of this guide shall also
be provided to each cardholder in conjunction with the issuance of the
card. Additional copies shall be made available to the A/OPC as
requested.

C.25.2 *Agency/Organization Program Coordinator Guide:* The Contractor
shall develop a guide for use by each participating A/OPC. This guide
shall be sufficiently detailed to serve as a stand-alone reference for
the A/OPC to operate the card program. At a minimum it shall include:

a)  Account set-up and maintenance procedures;

b)  Transaction dispute procedures;

c)  Reconciliation procedures;

d)  Account suspension and cancellation procedures;

e)  Payment requirements;

f)  Authorized uses;

g)  A list of cardholder, designated billing office, transaction dispute
    office and A/OPC responsibilities;

h)  A list, samples and explanation of contract reports and how to read
    them;

i)  Explanation of electronic access screens, necessary key sequences
    and functions for performing the requirements of C.34, Program and
    Transaction Data; and

j)  Toll-free or collect task order manager telephone number.

At the agency's/organization's discretion, the Contractor shall
distribute the Internet/Intranet address or a hard copy of the
Agency/Organization Program Coordinator Guide to each participating
A/OPC within **ten (10) calendar days** of the Contractor\'s receipt of
a task order issued in accordance with the terms and conditions of this
contract. Additional hard copies shall be made available to the A/OPC as
requested.

C.25.3 *Designated Billing Office Guide:* The Contractor shall develop a
guide for use by each participating billing office. This guide shall be
sufficiently detailed to serve as a stand-alone reference for the
designated billing office to operate the card program. At a minimum it
shall include:

a)  Explanation of billing cycles;

b)  Transaction dispute procedures;

c)  Reconciliation procedures;

d)  Account suspension and cancellation procedures;

e)  Payment requirements;

f)  Authorized uses;

g)  A list, samples and explanation of forms relating to invoices,
    transaction data and transaction disputes and how to read them,
    required timeframes for submittal, etc.;

h)  Explanation of electronic access screens, necessary key sequences
    and functions for performing the requirements of C.34, Program and
    Transaction Data relative to Designated Billing Office duties; and

i)  Toll-free or collect task order manager and customer service
    telephone numbers.

At the agency's/organization's discretion, the Contractor shall
distribute the Internet/Intranet address or a hard copy of the
Designated Billing Office Guide to each participating A/OPC and each
agency/organization designated billing office within **ten (10) calendar
days** of the Contractor\'s receipt of a task order issued in accordance
with the terms and conditions of this contract. Additional hard copies
shall be made available to the A/OPC and Designated Billing Office as
requested.

C.25.4 *Transaction Dispute Office Guide:* The Contractor shall develop
a guide for use by each participating transaction dispute office. This
guide shall be sufficiently detailed to serve as a stand-alone reference
for the transaction dispute office to operate the card program. At a
minimum it shall include:

a)  Transaction dispute procedures;

b)  Transaction dispute office responsibilities;

c)  Contractor responsibilities;

d)  Required timeframes;

e)  Chargeback provisions;

f)  A list, samples and explanation of forms relating to transaction
    disputes and how to read and complete them;

g)  Explanation of electronic access screens, necessary key sequences
    and functions for performing the requirements of C.34, Program and
    Transaction Data relative to Transaction Dispute Office duties; and

h)  Toll-free or collect account manager and customer service telephone
    numbers.

At the agency's/organization's discretion, the Contractor shall
distribute the Internet/Intranet address or a hard copy of the
Transaction Dispute Office Guide to each participating A/OPC and each
agency/organization transaction dispute office within **ten (10)
calendar days** of the Contractor\'s receipt of a task order issued in
accordance with the terms and conditions of this contract. Additional
hard copies shall be made available to the A/OPC and the Transaction
Dispute Office as requested.

***PERSONNEL***

## C.26 PERSONNEL:

The Contractor shall provide skilled personnel together with the
supervisory, management and administrative services necessary to
successfully meet the Government requirements.

C.26.1 *Key Personnel Definition:* Personnel identified in the proposal
as key individuals to be assigned for participation in the performance
of the master contract and individuals which are designated as key
personnel by agreement of the Government and the Contractor during
negotiations. Key personnel shall not be subcontracted personnel.

a)  Additions to Key Personnel: If at any point, the Contractor
    concludes additional key personnel are required, it shall advise the
    GSA Contracting Officer at least **15 calendar days** in advance.
    The Contractor shall demonstrate that the qualifications of the
    prospective additional key personnel are equal to or better than the
    qualifications of personnel approved under the master contract. The
    Contractor shall submit the same type of information to demonstrate
    qualifications of additions as was submitted with the proposal for
    the original key personnel. The GSA Contracting Officer will respond
    to any proposed additions of key personnel within 10 calendar days.
    Additions to key personnel shall only be made via a modification to
    the master contract.

b)  Replacement of Key Personnel: Key personnel shall not be removed,
    replaced or reassigned either permanently or temporarily, without
    **15-calendar day** advance notification to the GSA Contracting
    Officer, where possible. If one or more of the key personnel are
    unavailable for work under this contract for a continuous period
    exceeding 30 calendar days, the Contractor shall immediately notify
    the GSA Contracting Officer and provide a temporary replacement. Any
    key personnel lost must be replaced within **30 calendar days** from
    the date of the vacancy. The Contractor shall demonstrate that the
    qualifications of the prospective replacement key personnel are
    equal to or better than the qualifications of personnel approved
    under the master contract. The Contractor shall submit the same type
    of information to demonstrate qualifications of replacements as was
    submitted with the proposal for the original key personnel. The GSA
    Contracting Officer will respond to any proposed replacements of key
    personnel within 10 calendar days. Replacements to key personnel
    shall only be made via a modification to the master contract. The
    Contractor shall provide a temporary replacement as an interim
    measure until key personnel are replaced

C.26.2 *Key Personnel Categories:* The skill categories listed below are
essential for successful Contractor performance. The Contractor shall
assign dedicated personnel to the noted positions below. Dedicated
personnel are defined as personnel that solely manages and administers
Federal Government accounts under the Master Contract.

a)  Project Manager;

b)  Task Order Manager; and

c)  Any other individual designated as key personnel by agreement
    between the Contractor and the Government.

C.26.3 *Key Personnel Responsibilities:*

> a\) Project Manager: The Contractor shall designate a dedicated
> Project Manager for the GSA Contracting Office for:

1)  Day-to-day and special support activities;

2)  Implementation;

3)  Billing;

4)  Reconciliation;

5)  Suspension;

6)  Cancellation;

7)  Transaction overrides;

8)  Transaction disputes;

9)  Contract administration;

10) Supervision;

11) Coordination; and

12) Customer service support.

> This individual shall be well versed in all aspects of the Card
> Program(s), readily accessible, and be an overall point of contact for
> the GSA Contracting Officer and contracting support staff. The
> Contractor shall also designate an alternate in the event of the
> absence of the primary dedicated point of contact. The Contractor
> shall provide dedicated project management staff for the GSA
> Contracting Office from 8:00 a.m. Eastern Time until 5:00 p.m. Eastern
> Time.
>
> b\) Task Order Manager: For mandatory users of the Card Program(s) (as
> shown in Exhibit 9 (Fleet Card Program), Exhibit 10 (Travel Card
> Program) and Exhibit 11 (Purchase Card Program)), the Contractor shall
> designate dedicated task order managers for agencies/organizations and
> A/OPCs for:

1)  Program implementation (e.g., account set-up, account maintenance,
    account suspension or cancellation, training, etc.);

2)  Program management (e.g., task order administration, day-to-day and
    special support management activities, problem solving, pilot
    programs, customized services, investigations, audits, etc.); and

3)  Program operation (e.g., transaction overrides, individually and
    centrally billed account inquiries, reporting lost/stolen cards,
    billing, disputes, reconciliation, customer service, etc.);

> This individual shall be well versed in all aspects of the Card
> Program(s), readily accessible, and be an overall point of contact for
> A/OPCs. The Contractor shall also designate an alternate in the event
> of the absence of the primary dedicated point of contact. The
> Contractor shall provide dedicated, full-time staff to both domestic
> and international A/OPCs through toll-free or collect telephone
> numbers, from 7:00 a.m., Eastern Time until 9:00 p.m. Eastern Time
> each business day.
>
> Non-mandatory users of the Card Program(s) need not have dedicated
> staff; however, the staff must be available within the timeframes
> specified.

C.26.4 *Support Personnel:* The Contractor shall provide the required
personnel to successfully accomplish the Government's requirements. The
following support personnel categories are anticipated:

a)  Account Coordinators/Customer Service Representatives: The
    Contractor shall provide dedicated customer service personnel to
    both mandatory and non-mandatory users of the Card Program(s),
    accessible to both domestic and international cardholders through
    toll-free or collect telephone numbers, 24 hours a day, every day of
    the year. These services shall include, at a minimum, transaction
    authorization and verification, reporting of lost or stolen cards,
    cardholder account inquiries, etc. Account Coordinators/Customer
    Service Representatives shall be well versed in the Card
    Program(s).\
    \
    The Contractor may utilize a two-tier approach in providing customer
    service to cardholders. The first approach may utilize an
    interactive voice response unit for customer service that can
    readily accommodate routine requests for action or information. For
    example, a cardholder can request balances, last payment(s), last
    transaction(s), etc., through an interactive voice response unit
    that is in accordance with commercial practice. The second approach
    may then elevate the cardholder to contractor personnel for direct
    response.\
    \
    Personnel shall be well versed in all aspects of the Card
    Program(s), readily accessible, and be an overall point of contact
    for cardholders.

b)  EC/EDI Coordinators: The Contractor shall designate EC/EDI
    Coordinators for agencies/organizations and Government EC/EDI
    Offices (EO) for electronic systems implementation and integration
    (e.g., development of EC/EDI processes, guidance, implementation
    support, mapping, trouble-shooting, systems documentation, testing,
    etc.);\
    \
    This individual shall be well versed in all EC/EDI aspects of the
    Card Program(s), readily accessible, and be an overall point of
    contact for the Government. The Contractor shall also designate an
    alternate in the event of the absence of the primary point of
    contact. The Contractor shall provide dedicated, full-time staff
    through toll-free or collect telephone numbers, from 8:00 a.m.,
    Eastern Time until 5:00 p.m. Eastern Time each business day.

c)  Any other skill category designated as support personnel by
    agreement between the Contractor and the Government.

C.26.5 Other Considerations: All key Contractor personnel who work in
the performance of this contract shall be acceptable to the Government
in terms of professional conduct. Employment and staffing difficulties
will not be justification for failure to meet established schedules, and
if such impairs performance, the Contractor may be subject to
termination for cause.

***INITIAL CONTRACT START-UP REQUIREMENTS:***

***NOTE: The timeframes referenced in C.27 are specific to initial
contract start-up ONLY (Date of award through November 29, 1998).***

## C.27 START-UP IMPLEMENTATION REQUIREMENTS

All Contractor costs associated with implementation shall be borne by
the Contractor. In addition to the requirements specified in this
section, the travel and purchase business lines have additional
requirements for start-up implementation (reference CB.8, Additional
Start-Up Requirements for the Travel Card Program and CC.7, Additional
Start-Up Requirements for the Purchase Card Program). The Contractor may
perform all actions necessary, subject to marketing restrictions below,
to implement card programs except that **no charges shall be made or
processed prior to November 30, 1998**.

C.27.1 *Account Information:* Submission of new program forms (as
specified in C.34.4) are required for the master contract.

C.27.2 *Presentation Packages:* The Contractor shall develop a
presentation package. The presentation package will be used by
agencies/organizations to assist in their selection of their vendor of
choice and introduce agencies/organizations to the Contractor and the
products and services offered under contract. The presentation package
shall be available electronically and in hard copy, and include such
items as pricing, products, services, points of contact and Internet Web
Site. It should be comprehensive enough for agencies/organizations to
make an informed choice; however, keep in mind that this document will
be in the public domain, and thus should not divulge trade secrets or
information that a Contractor may consider proprietary. The presentation
package should not be overly long as lengthy presentation packages are
time-consuming for agencies/organizations to thoroughly review. The
presentation package should not exceed 10 pages in length. The
Contractor shall be responsible for the design, publication and
distribution of these presentation packages. As requested by the
agency/organization **and** after the Kick-Off Conference (C.27.3,
below), the presentation package shall be available electronically,
through the Internet or the agency's/organization's Intranet, using any
agency/organization-Intranet specifications.

Within **2 weeks of contract award**, the Contractor shall submit its
final presentation package to the GSA Contracting Officer for written
approval (the draft presentation package will be submitted with the
offer\--see Instructions to Offerors Section, paragraph 14.3,
subparagraph b) 2) a) (vii)). Contractors are prohibited from marketing
their card programs to the Government until the conclusion of the master
ceremony at GSA's Kick-Off Conference (see C.27.3).

C.27.3 *Kick-Off Conference:* The GSA Contracting Office will conduct a
kick-off conference in the Washington, DC metropolitan area for all
awarded master contractors and the government currently scheduled for
the January-February 1998 timeframe. The GSA Contracting Office will
kick-off the new contracts with a master ceremony to welcome everyone,
explain the master contract, ordering procedures, etc., and formally
introduce master contract awardees to the government. After the master
ceremony, Contractors may begin marketing to agencies/organizations.
Contractors are expected to set up a booth, similar to those in
commercial trade shows, where customer agencies/organizations may talk
to master contractors, review materials, see demonstrations, etc. All
Contractor travel and travel-related costs shall be borne by the
Contractor as well as any audio-visual needs, including
telephone/voice/data lines for personal computers. The GSA Contracting
Office will provide conference and booth space.

C.27.4 *Start-Up Implementation Schedule:*

> a\) Task Order Placement Schedule: The placement of task orders is
> anticipated to follow the schedule below. The following schedule is an
> example of a task order placement schedule. An accurate schedule will
> follow as soon as mandatory/non-mandatory usage is known. NOTE: GSA
> Pool is described in the Addendum to 52.212-4, paragraph 38.9 b) 2).

**DATE SCHEDULE**

01/21/98 - 01/24/98 KICK-OFF CONFERENCE

02/23/98 - 03/30/98 1st window for mandatory user submission of
**tailored** task requests/orders:

DOE NASA HHS DOJ

GSA Pool GSA DOL State

03/09/98 - 04/30/98 1st window for mandatory user submission of
**tailored** task requests/orders:

DoD Postal Svc VA DOI

GSA Pool Agriculture Commerce Treasury

03/30/98 - 05/11/98 1st window for mandatory user submission of
**tailored** task requests/orders:

GSA Pool All other mandatory agencies/organizations

04/13/98 - 05/18/98 2nd window for mandatory user submission of
**tailored** task requests/orders:

DOE NASA HHS DOJ

GSA Pool GSA DOL State

05/04/98 - 06/15/98 2nd window for mandatory user submission of
**tailored** task requests/orders:

DoD Postal Svc VA DOI

GSA Pool Agriculture Commerce Treasury

05/18/98 - 06/22/98 2nd window for mandatory user submission of
**tailored** task requests/orders:

GSA Pool All other mandatory agencies/organizations

06/08/98 - 07/02/98 Window for mandatory user submission of **standard**
task requests/orders:

DOE NASA HHS DOJ

GSA Pool GSA DOL State

06/22/98 - 07/20/98 Window for mandatory user submission of **standard**
task requests/orders:

DoD Postal Svc VA DOI

GSA Pool Agriculture Commerce Treasury

07/13/98 - 08/10/98 Window for mandatory user submission of **standard**
task requests/orders:

GSA Pool All other mandatory agencies/organizations

07/27/98 - 09/30/98 Window for non-mandatory user submission of
**standard and tailored**

task requests/orders:

GSA Pool All other non-mandatory agencies/organizations

10/01/98 - 11/09/98 Window for non-mandatory user submission of
**standard and tailored**

task requests/orders:

GSA Pool All other non-mandatory agencies/organizations

It is anticipated that agencies/organizations may take close to ten (10)
months to effectuate a seamless transition. Within **10 calendar days**
of receipt of a task order from a mandatory user of this contract and
receipt of the task order is in accordance with the schedule above, the
Contractor shall contact the A/OPC to develop an implementation
schedule. The implementation schedule shall include a time line for the
various steps required to implement a program to include, but not be
limited to, a detailed listing of necessary agency/organization actions
(e.g., submittal of program forms, operating system specifications,
etc.) as well as the required timeframes to ensure implementation stays
on schedule and a detailed listing of necessary actions on the
Contractor's part (e.g., program forms, customer training, account
set-up, card production and distribution schedules, electronic access
set-up and testing, EC/EDI set-up and testing, etc.). The Contractor
shall provide implementation and training to all agencies/organizations
in the areas of finance, administration and management of Card Program
requirements. This includes all action necessary to implement the Card
Program(s) (e.g., on-site visits, program education/explanation,
reviewing specific user requirements, assisting in account set up,
etc.). All travel costs associated with start-up implementation shall be
borne by the Contractor. [The timeframes specified below apply to
mandatory users of this contract]{.underline}. NOTE: CARD/ACCOUNT
EFFECTIVE DATES SHALL NOT BE PRIOR TO THE EFFECTIVE DATE OF THE MASTER
CONTRACT.

If a mandatory user of the Card Program submits its task order outside
the phase-in schedule noted above, the Contractor shall use its best
efforts to develop an implementation schedule within **10 calendar
days** of receipt of the task order, but in no case shall the
establishment of the implementation schedule exceed **30 calendar
days**.

It is anticipated that a number of agencies/organizations designated as
non-mandatory users may wish to participate in this contract. For
non-mandatory users of this contract, the Contractor shall put forth its
best efforts to implement the Card Program(s) prior to November 30,
1998.

> a\) Program Forms: During start-up implementation, the Contractor
> shall promptly provide hard copy program forms to
> agencies/organizations as requested.
>
> b\) Card/Account Delivery: Cards shall not be delivered any earlier
> than **November 15, 1998,** unless otherwise mutually agreed to by the
> agency/organization and the Contractor.
>
> c\) Card/Account Activation: Cards/accounts shall not be activated
> under any circumstance any earlier than **November 30, 1998**. The
> Contractor shall ensure that activation procedures for the card are
> provided with card issuance, unless otherwise specified in the
> agency/organization task order.
>
> d\) Training Materials: The Internet/Intranet address or hard copy
> training materials (materials are described in C.25, Training
> Requirements), shall be provided to A/OPCs, DBOs, TDOs and EOs in
> accordance with the implementation schedule**,** unless otherwise
> mutually agreed to by the agency/organization and the Contractor.
>
> e\) Electronic Access: Agency's/organization's electronic access
> systems shall be fully operational by **November 30, 1998**, unless
> otherwise mutually agreed to by the agency/organization and the
> Contractor.
>
> f\) No charges shall be made or processed prior to **November 30,
> 1998**.

**END OF INITIAL CONTRACT-START UP REQUIREMENTS**

***YEAR 2000 COMPLIANCE***

## C.28 YEAR 2000 COMPLIANCE

The Contract warrants that any product offered or electronic and
authorization system delivered under this contract shall be Year 2000
compliant. Year 2000 compliant means accurately processing date/time
data (including, but not limited to, calculating, comparing, and
sequencing) from, into, and between the twentieth and twenty-first
centuries, and the years 1999 and 2000 and leap year calculations, when
used in accordance with the product documentation provided by the
Contractor, provided that all products used in combination with the
Contractor's product properly exchange date data with it. If the
contract requires that specific listed products must perform as a system
in accordance with the foregoing warranty, then that warranty shall
apply to those listed products as a system. The duration of this
warranty and the remedies available to the Government for breach of this
warranty shall be as defined in, and subject to, the terms and
limitations of the Contractor's standard commercial warranty or
warranties contained in this contract, provided that notwithstanding any
provision to the contrary in such commercial warranty or warranties, the
remedies available to the Government under this warranty shall include
repair or replacement of any listed product whose non-compliance is
discovered and made known to the Contractor within 90 calendar days
after acceptance. Nothing in this warranty shall be construed to limit
any rights or remedies the Government may otherwise have under this
contract with respect to defects other than Year 2000 performance.

***TRANSACTION AUTHORIZATIONS***

## C.29 TRANSACTION AUTHORIZATIONS

The Contractor shall have a system which provides domestic and
international transaction authorization support, 24 hours a day, every
day of the year. In addition, the Contractor shall adhere to the
authorization procedures established by the Contractor or the
Contractor's Bank or Credit Card Association. Transactions that violate
the restrictions established by the authorization controls shall be
denied authorization at the point-of-sale. The authorization system
shall have a backup system in place should the Contractor\'s normal
authorization system malfunction or become otherwise inoperable.
Immediate override capabilities shall be provided to allow the
authorized A/OPC or the GSA Contracting Office to direct the contractor
to authorize specific transactions that may otherwise be prohibited. The
Contractor shall have a method in which to ensure that the request to
override a transaction is from an authorized individual. The Contractor
shall monitor account transactions to identify any unusual spending
patterns or frequencies (e.g., identifying multiple purchases having the
characteristics of a "split purchasing" pattern (a purchase split
between two or more purchase orders); alerting to attempted purchases at
excluded merchants; flagging purchases that are made on dates and times
that are outside of normal cardholder spending patterns) and promptly
notify the A/OPC of any unusual spending patterns or frequencies as well
as provide this information on the agency's/organization's exception
report specified in C.38.2, subparagraph e).

***AUTHORIZATION CONTROLS***

## C.30 AUTHORIZATION CONTROLS

The Contractor shall provide a means during the transaction
authorization process to provide the controls for each account as
specified below and in each business line (reference CA.7, Authorization
Controls for the Fleet Card Program, CB.9, Authorization Controls for
the Travel Card Program, CC.8, Authorization Controls for the Purchase
Card Program), unless otherwise specified. The Contractor shall also
provide an automatic control that flags and declines invalid cards
(lost/stolen, suspended, canceled, etc.) and has the ability to void
cards at the request of the agency/organization or GSA Contracting
Officer.

a)  Default limit: The Contractor may suggest standard commercial
    default limits during card/account set-up that may be changed by an
    agency/organization;

b)  Dollars per transaction limit: Each account may be assigned a dollar
    per transaction limit by the A/OPC;

c)  Dollars per month limit: Each account may be assigned a dollar per
    month limit by the A/OPC. Any whole dollar limit may be assigned.
    This dollar limit shall apply to the cardholder's billing cycle;

d)  Transactions per day limit: Each account may be assigned a
    transaction per day limit by the A/OPC;

e)  Transactions per month limit: Each account may be assigned a
    transaction per month limit by the A/OPC. This transaction limit
    shall apply to the cardholder's billing cycle; and

f)  Merchant category code: Each account may be restricted from making
    certain types of purchases as set by the A/OPC. Purchases may be
    restricted depending on the type of merchant (identified by the
    merchant category code).

***TRANSACTION POSTING***

## C.31 POSTING OF TRANSACTIONS

All electronic transactions (both credits and debits) shall be posted to
the account within **two (2) business days** from the date of the
Contractor's receipt of the posted and settled transaction. Posted
credit transactions shall include the reference number assigned at the
time of the original charge or another identifier that will enable the
cardholder to match the original charge with the credit.

Manual transactions must be posted within **two (2) business days** from
the date of the Contractor's receipt of the posted and settled
transaction. The Contractor shall ensure that there are adequate
tracking controls for manually processed transactions. This may mean
requiring merchants to maintain receipt records long enough to allow for
signature identification on disputed transactions.

***TAX EXEMPTION***

## C.32 TAX EXEMPT STATUS

Transactions against Federal Government accounts that are directly paid
by the Government are exempt from state and local taxes. The Contractor
shall work cooperatively with the Government to ensure that merchants
and states do not tax these transactions. The Contractor shall work with
the Government to assist in resolution of any other tax exemption issues
that may arise. For additional tax exemption requirements applicable to
the Fleet Card Program, reference CA.8, Tax Exempt Status for the Fleet
Card Program.

***FOREIGN CURRENCY CONVERSION***

## C.33 FOREIGN CURRENCY CONVERSION

The Contractor shall ensure that charges made in a foreign currency are
converted into US Dollars on the statement of account, invoice, and
related reports using a favorable conversion rate established by an
interbank rate or where required by law, an official rate. This rate
shall be the one in existence at the time the transaction is processed.
The Contractor shall identify the conversion rate used on the statement
of account, invoice and related reports. The Contractor shall not charge
a fee for the conversion.

***PROGRAM AND TRANSACTION DATA***

## C.34 PROGRAM AND TRANSACTION DATA

The Contractor shall provide, at a minimum, its Level III platform for
program and transaction data and forward all data received from
merchants and obtained by the Contractor to the Government.

The Contractor shall restrict access to the program and transaction data
and the ability to request changes to the information therein. The
Contractor shall limit access only to authorized individuals designated
by the A/OPC, in writing. Information shall be restricted to inquiring
agency/organization and subsequent level (e.g., Department of the
Interior shall only have access to Interior information, National Park
Service shall only have access to National Park Service information,
Yellowstone National Park shall only have access to Yellowstone National
Park information). The GSA Contracting Officer shall have access to all
program and transaction data. The Contractor shall provide higher levels
of security for reviewing detailed transaction data or making changes
and lower levels of security for obtaining program forms, training
materials, etc.

C.34.1 *Electronic Access to Program and Transaction Data:* The
Contractor shall provide an electronic access system that allows two-way
communications between the agency/organization and perform the functions
as described below, or their commercially equivalent product that meets
the Government's requirements. The Contractor, at its expense, shall
also provide any associated software and communication access required
to each requesting agency/organization. The electronic method must be
compatible with a variety of computer systems (including personal
computers and mainframes) and be provided at the Contractor's expense,
to each requesting agency/organization level. This does not include
providing any underlying operating system (e.g., UNIX, OS/2, Macintosh,
DOS, or Windows) or computer hardware. For access through modem, the
Contractor shall provide each requesting agency/organization the
appropriate communications parameter information and any necessary
procedural information (e.g., baud rate, function keys, screen
sequences).

All program and transaction data shall be available on-line. At a
minimum, the electronic access system shall:

a)  Provide the ability to perform the functions specified in C.34.2,
    Agency/Organization Program Information; C.34.3, Program
    Implementation and Program Management; C.34.4, Program Forms;
    C.34.5, Master File; and C.34.6, Transaction Data;

b)  Provide the ability to sort data by any field chosen, as well
    roll-up, review and manipulate the data by agency/organization and
    subsequent level;

c)  Be user-friendly;

d)  Ensure that all program and transaction data on the Government Card
    Program(s) is secured, at a minimum, according to standard
    commercial practices;

e)  Provide the ability to generate ad hoc reports;

f)  Accommodate multiple users concurrently;

g)  Provide the ability to dispute transactions electronically as well
    as track transactions from the time of charge through final
    resolution of the charge;

h)  Provide the data in a database/table format or an ASCII file format
    or other agency/organization agreed-upon format that can be
    downloaded via electronic means based on the following select
    criteria: account number, type of account, name, billing address,
    type of charge, date of charge, amount of charge, and date of
    payment. The associated record layout shall be provided to the
    agencies/organizations upon their request;

i)  Allow the agency/organization to download data from the system and
    batch upload into the system without having to manually enter the
    data;

j)  Be available 24 hours a day, every day of the year; and

k)  Provide automation of traveler and/or bank check system (reference
    CB.12, Travelers Checks and CC.11, Bank Checks).

C.34.2 *Agency/Organization Program Information:* Based on the
information provided on program forms (see C.34.4, Program Forms) by
agencies/organizations at each hierarchy level, as well as subsequent
agency/organization changes to program information, the Contractor shall
develop, maintain, regularly update and report an electronic list of
names, work addresses, work telephone/facsimile numbers, and work e-mail
addresses (if available) for:

-   Agency/Organization Program Coordinators;

-   Designated Billing Office points of contact (for centrally billed
    accounts only);

-   Transaction Disputes Office points of contact (for centrally billed
    accounts only); and

-   EC/EDI Coordinators.

C.34.3 *Program Implementation and Program Management:* The Contractor
shall provide electronic access to each participating A/OPC to enable
program implementation and program management to include, but not be
limited to:

a)  Sending in program forms;

b)  Account set-up;

c)  Account maintenance;

d)  Activating/deactivating a card;

e)  Renewing a card;

f)  Updating required authorization controls;

g)  Disputing a transaction;

h)  Sorting, reviewing and manipulating transaction data;

i)  Downloading reports, statements of accounts or invoices; and

j)  Generating ad hoc reports.

C.34.4 *Program Forms:* The Contractor shall:

a)  Develop all program forms;

b)  Date and number all program forms;

c)  Ensure that the program forms capture the data required in C.30,
    Authorization Controls; C.34.2, Agency/Organization Program
    Information; C.34.3, Program Implementation and Program Management;
    and C.34.5, Master File;

d)  Provide a copy of any proposed additions/revisions/deletions to the
    GSA Contracting Officer at least **7 calendar days** prior to the
    Contractor's notification to the agencies/organizations of any
    change in forms. The GSA Contracting Officer reserves the right to
    disapprove any proposed change to the form(s). New or updated forms
    and explanation of such shall be electronically provided to each
    participating A/OPC, at no expense to the Government, at all levels,
    at least **14 calendar days** prior to the effective date of the
    addition/change;

e)  Accept all forms completed by a participating agency/organization
    and approved by the A/OPC, via electronic means, fax, and/or mail;
    and

f)  Assist participating agencies/organizations in completing forms, as
    requested.

.

The Contractor shall also provide hard copies of each program form as
requested by the GSA Contracting Office or the A/OPC and process such
forms within the timeframes specified.

C.34.5 *Master File:* The Contractor shall develop, maintain and update
a master file for each cardholder, A/OPC, Designated Billing Office,
Transaction Dispute Office, EC/EDI Office, and Report Office, on-line.
The master file shall be electronically accessible to the A/OPC and
provide the ability to request the Contractor to make changes to the
master file, both on-line and in batch electronic uploads.

Required changes to the master file resulting from program requirements,
internal reorganizations, personnel movements, or other
agency/organization changes, shall be completed within **three (3)
business days** after receipt of such changes by the Contractor.
Appropriate forms for such changes shall be provided by the Contractor,
as referenced in C.34.4, Program Forms, and accessible electronically by
agencies/organizations. A change to the master file shall result in
automatic system-wide changes for all program data.

The Contractor shall have the ability to transfer cardholders and
accounts within an agency/organization level without reissuing a new
card, if requested by the participating agency/organization.

Upon request of the GSA Contracting Officer, the Contractor shall
provide a current, complete and accurate master file of all program
participants in a mutually agreeable medium, within **30 calendar days**
of the request. Upon request of the A/OPC, the Contractor shall provide
a current, complete and accurate master file of the requesting
agency/organization level's participants in a mutually agreeable medium,
within **30 calendar days** of the request.

The master file shall be capable of recording the following information
as well as the specific data elements for each business line required in
CA.9, Program and Transaction Data for the Fleet Card Program, CB.10,
Travel Card Program and Transaction Data for Centrally Billed Accounts,
CB.14, Travel Card Program and Transaction Data for Individually Billed
Accounts and CC.9 Purchase Card Program and Transaction Data.

C.34.5.1 *[Card Specific Information]{.underline}:*

a)  Cardholder name;

b)  Account number;

c)  Cardholder address (minimum 30 digit alphanumeric field per line,
    five (5) line work address);

d)  Cardholder area code and telephone number, including fax number;

e)  Cardholder electronic address (if available);

f)  Agency/organization name and address;

g)  Authorization controls (reference C.30, Authorization Controls);

h)  Account status; and

i)  Master accounting code (up to 64 alpha-numeric character length).

C.34.5.2 *[Agency/Organization Program Coordinator (A/OPC) Specific
Information]{.underline}:*

a)  A/OPC name;

b)  Agency/organization identifying number;

c)  Agency/organization name and address;

d)  Minimum 30 digit alphanumeric field per line, five (5) line work
    address;

e)  A/OPC electronic address (if available);

f)  Area code and telephone number, including fax number; and

g)  Task order number.

C.34.5.3 *[Designated Billing Office (DBO) Specific
Information]{.underline}:* \[NOTE\--the address provided here is
considered the official invoice address for purposes of meeting the
deadlines of the Prompt Payment Act, even though the actual address from
which payment is rendered may be different.\]

a)  DBO name;

b)  Agency/organization identifying number;

c)  Agency/organization name and address;

d)  Minimum 30 digit alphanumeric field per line, five (5) line work
    address;

e)  DBO electronic address (if available); and

f)  Area code and telephone number, including fax number.

C.34.5.4 *[Transaction Dispute Office (TDO) Specific
Information]{.underline}:*

a)  TDO name;

b)  Agency/organization identifying number;

c)  Agency/organization name and address;

d)  Minimum 30 digit alphanumeric field per line, five (5) line work
    address;

e)  TDO electronic address (if available); and

f)  Area code and telephone number, including fax number.

C.34.5.5 *[EC/EDI Office (EO) Specific Information]{.underline}:*

a)  EO name;

b)  Agency/organization identifying number;

c)  Agency/organization name and address;

d)  Minimum 30 digit alphanumeric field per line, five (5) line work
    address;

e)  EO electronic address (if available); and

f)  Area code and telephone number, including fax number.

C.34.5.6 *[Report Specific Information]{.underline}:* \[NOTE\--This is
the record of address(es) to which reports is to be distributed for each
card.\]

a)  Contact name;

b)  Report title/number;

c)  Report address; and

d)  Area code and telephone number, including fax number.

C.34.6 *Transaction Data:* The Contractor shall make electronically
available all recorded and obtained transaction data to the
agency/organization and the GSA Contracting Office. The A/OPC and GSA
Contracting Office must be able to sort the data by any field, review
and manipulate the data by agency/organization level, as well as
generate ad hoc reports. If requested by the agency/organization, the
Contractor must provide copies of the transaction data on a single hard
copy report or as part of a single flat file/EDI database transmission.

C.34.6.1 Transaction Data Elements: The following transaction data for
each purchase is required. Level II and Level III data elements that are
asterisked (\*) indicate submission of such data where the data is
passed by the merchant and obtained by the Contractor, unless otherwise
specified in the specific data elements required for each business line
(reference CA.9.2, Fleet Card Program Transaction Data Elements and
CB.10.2, Travel Card Program Transaction Data for Centrally Billed
Accounts).

a)  Account name;

b)  Account number;

c)  Agency/organization name;

d)  Agency/organization identifying number;

e)  Merchant category code;

f)  Carrier/Merchant/Establishment name;

g)  Carrier/Merchant/Establishment address (city and state);

h)  Debit or credit indicator (i.e., identify whether it was a charge or
    a credit);

i)  Date of charge/credit (and identify ATM, travelers check or bank
    check transaction);

j)  Amount of charge/credit (and identify ATM, travelers check or bank
    check transaction);

k)  Date charge/credit was processed by the Contractor;

l)  Contractor processing/transaction reference number for each
    charge/credit;

m)  Accounting code\*;

n)  Minority/women owned business codes (1057 information)\*;

o)  1099 status\*;

p)  Sales tax amount\*;

q)  Merchant zip code\*;

r)  Merchant's taxpayer identification number\*;

s)  Merchant's area code and telephone number\*;

t)  Unit cost\*;

u)  Quantities\*;

v)  Unit of measure\*;

w)  Product codes\*;

x)  Product descriptions (line item detail)\*;

y)  Ship to/from zip codes\*;

z)  Freight amount\*;

a)  Duty amount\*;

b)  Order date\*;

c)  Discount amount\*;

d)  Order number\*; and

e)  Merchant DUNS number\*.

As additional or enhanced data elements are available from the merchant
and obtained by the Contractor, the Contractor shall pass the data to
the Government.

***CENTRALLY BILLED ACCOUNTS***

## C.35 CENTRALLY BILLED CARD PROGRAM ACCOUNTS:

The Contractor shall issue cards/cardless accounts to the address and
individual/agency/orga-nization designated by the A/OPC after receipt of
completed program forms. If requested by the A/OPC, the Contractor shall
meet with agency/organization representatives to discuss implementation
procedures. All travel costs associated with this meeting shall be borne
by the Contractor. Additional requirements specific to each business
line are addressed in CA.10, Fleet Card Program Accounts, CB.11, Travel
Card Program Centrally Billed Accounts, CB.15, Travel Card Program
Individually Billed Accounts and CC.10, Purchase Card Program Accounts.

C.35.1 *Account Set Up:* Each agency/organization will provide master
file information specified in C.34.5, Master File on Contractor-provided
program forms. The Contractor shall:

a)  Assist agencies/organizations in setting up accounts, as requested;

b)  Provide the required authorization controls referenced in C.30,
    Authorization Controls, at the request of a participating
    agency/organization, and unless otherwise specified;

c)  Establish centrally billed cards/accounts without prior credit
    worthiness checks or personal information required of the cardholder
    other than the cardholder's name and work address;

d)  Provide single account numbers with multiple sub-accounts, if
    requested by participating agencies/organizations; and

e)  Make cards/accounts valid for a specific time period as agreed upon
    by the Contractor and the A/OPC, not to exceed the master contract
    base period or any options exercised, unless otherwise specified by
    the GSA Contracting Officer.

For purposes of opening centrally billed cards/accounts, the Contractor
shall accept program forms via fax, mail and/or electronic means.

C.35.2 *Card/Cardless Issuance and Delivery for Centrally Billed
Accounts:* The Contractor shall:

a)  Establish new centrally billed accounts as approved by the A/OPC
    upon receipt of completed program forms via fax, mail or electronic
    means;

b)  Process program forms and issue cards/cardless accounts to the
    designated address within **three (3) business days** of receipt of
    the completed program forms;

c)  Provide standard commercial card activation procedures;

d)  Domestically, replace lost, stolen, broken or otherwise unusable
    cards within **24 hours** of the agency/organization request; and

e)  Internationally, replace lost, stolen, broken or otherwise unusable
    cards within **48 hours** of the agency/organization request.

C.35.3 *Emergency Account Set-Up and Card Delivery:* The Contractor
shall process and ship cards within **24 hours** at the request of the
A/OPC or GSA Contracting Officer. These requests are generally in
response to natural disasters (e.g., hurricane, earthquake) or military
mobilization, but may be requested for any emergency as defined by the
A/OPC or GSA Contracting Officer. Upon request of the A/OPC or GSA
Contracting Officer, the Contractor shall ship emergency cards overnight
delivery at Contractor expense.

Where the Government provides oral instruction to set up an account
and/or issue a card, confirmation will follow within three (3) business
days of the oral authorization. The agency/organization may use
electronic means to forward program forms to the Contractor.

C.35.4 *Short Term Account Set-Up and Card Delivery:* The Contractor
shall issue short-term cards/accounts as requested by the A/OPC or GSA
Contracting Officer. These requests are generally in response to special
events (Olympic Games, Economic Summits, Anniversaries of Historic
Events) or in response to emergencies as described in C.35.3. The
Contractor shall have a method of deactivating these short term
cards/accounts at the end of the specified period through short-term
expiration dates, card/account cancellation, or other methods.

C.35.5 *Card Renewal:* At least **90 calendar days** prior to the
expiration of each account or card, the Contractor shall submit a report
to the A/OPC listing each expiring account or card. The report shall
contain all information necessary for the agency/organization to renew
the account or card. Cards shall automatically renew unless otherwise
directed by the A/OPC. If accounts or cards are not to be renewed, the
A/OPC will notify the Contractor, in writing, 45 calendar days prior to
account or card expiration. Renewed cards shall be sent no earlier than
40 calendar days before the expiration date of the existing card and no
later than 20 calendar days before the expiration date of the existing
card.

C.35.6 *Verification of Card Receipt:* The Contractor, at its expense,
shall have a means of verifying receipt of any card issued under the
program(s).

C.35.7 *Invoicing:* The Contractor shall send an itemized official
invoice to the designated billing office for each centrally billed
account promptly after the end of each billing cycle.
Agency/or-ganization receipt of the official invoice shall allow ample
time from each billing cycle for reconciliation and payment.

C.35.7.1 *[Frequency of Invoicing]{.underline}:* Invoicing shall occur
on a monthly billing cycle unless otherwise specified by the
agency/organization. The Contractor shall provide shorter billing cycles
(e.g., daily, weekly), alternate billing cycles, and/or alternate levels
of billing as requested by the agency/organization and priced in their
task order.

C.35.7.2 *[Medium(a) of Invoicing]{.underline}:* The invoice shall be
submitted in a medium(a) requested by the Designated Billing Office,
e.g., accessed and downloaded through the electronic access system
described in C.34.1, hard copy, 3.5" or 5.25" floppy disk, 9-track
magnetic tape, non-EDI based electronic invoicing, or through EDI.

C.35.7.3 *[Invoices]{.underline}:* There are two types of invoices that
an agency/organization may choose from. Agencies/organizations may
choose one or both invoices.

> a\) Itemized Invoice: For each transaction, the invoice shall, at a
> minimum, contain the information required in C.34.6, Transaction Data
> and C.34.6.1, Transaction Data Elements and the following:

1)  Invoice date;

2)  Master file accounting code;

3)  Foreign conversion rate and methodology;

4)  Debit/credit indicator;

5)  Itemized and total charges/credits (including ATM/Travelers Checks
    and Bank Check, customized services, value-added products and
    services and any miscellaneous fees as a separate item, where
    applicable);

6)  Prompt Payment Act interest charges as a separate item, as
    applicable; and

7)  Amount carried over from previous invoice.

> b\) EC/EDI Invoice: This type of invoice is structured and formatted
> in accordance with C.6, Electronic Commerce/Electronic Data
> Interchange.

The invoice shall include all transactions, debits and charges posted to
the account during the billing cycle. The invoice shall match the
transaction data referenced in C.34.6, Transaction Data and C.34.6.1,
Transaction Data Elements and shall balance at all times.

C.35.8 *Billing Discrepancies:* The invoice will be manually or
electronically reconciled by the cardholder, agency/organization or
designee. It is the agency/organization's responsibility to notify the
Contractor of any items in dispute within 60 calendar days of receipt of
the invoice. This notification of transaction dispute may occur via the
electronic access system described in C.34.1, telephone or other means
(e.g., facsimile, mail, etc.). In the event of a transaction dispute,
the Contractor shall:

a)  Provide immediate temporary credit to the account;

b)  Provide sufficient transaction data to identify the charge;

c)  Promptly investigate disputed items and use best efforts to resolve
    transaction disputes, including working with merchants and the
    transaction dispute office;

d)  Provide a copy of the charge in dispute, if requested;

e)  Provide a copy of all Contractor correspondence regarding disputed
    items, if requested;

f)  Chargeback the merchant where appropriate;

g)  Detail the disputed charge on the Invoice Status Report (see C.38.1,
    Essential Reports, subparagraph b)); and

h)  Rebill proper charges in the subsequent billing period with any
    applicable Prompt Payment Act interest charge itemized separately
    and include complete transaction data for the rebilled charge.

If a disputed item is resolved before the payment due date, the
resolution shall appear on the agency's/organization's following
official invoice.

C.35.9 *Reconciliation Assistance:* The Contractor shall assist
agencies/organizations and/or their designee in the electronic
reconciliation of centrally billed accounts, as requested. This includes
ensuring that the official invoice is sent as a proper invoice as well
as assisting agencies/organizations and/or their designee with
downloading or transferring and/or reading the transaction data and
supporting documentation.

C.35.10 *Payment Processing:* Any payment received by the Contractor for
a past-due invoice shall be applied first to the principal amount, with
any remaining amount being applied to the Prompt Payment Act interest.
In case of a discrepancy of any payment received, the Contractor shall
promptly notify the Designated Billing Office.

C.35.11 *Settlement for Centrally Billed Accounts:* Settlements for
centrally billed accounts are made directly by the agency/organization
or designee. The Contractor shall accept payment from multiple sources
electronically and post such payments within **two (2) business days**
of receipt of payment. The Contractor shall ensure that their accounting
system enables the accurate and timely posting of account payments. If
the agency/organization specifies instructions for applying payment, the
Contractor shall comply with those instructions. The Contractor shall
develop procedures to ensure proper distribution of payment in
accordance with agency/organization instructions. The Contractor shall
be paid in accordance with the Prompt Payment Act, as amended, and the
provisions of OMB Circular A‑125, incorporated herein by reference, for
all centrally billed accounts. OMB Circular A-125 may be viewed at the
following Internet site:

**www.whitehouse.gov/WH/EOP/OMB/html/circular.html**

Only an undisputed amount for which payment has not been made shall be
considered delinquent. Agencies/organizations are responsible for
calculating interest under the Prompt Payment Act.

## C.36 SUSPENSION PROCEDURES FOR CENTRALLY BILLED ACCOUNTS

\[NOTE: SUSPENSION PROCEDURES FOR INDIVIDUALLY BILLED TRAVEL CARD
ACCOUNTS ARE SPECIFIED IN CB.18\]

For suspension purposes, an account is considered past due if payment
for undisputed principal amounts has not been received 45 calendar days
from the closing date on the invoice in which the charges appeared. The
Contractor shall either send a letter to the A/OPC and Designated
Billing Office or make a documented telephone call to the A/OPC and
Designated Billing Office requesting payment on past due accounts for
the undisputed principal amount.

The Contractor shall provide the Pre-Suspension/Pre-Cancellation Report
(reference C.38.1, subparagraph d) to the A/OPC to identify undisputed
amounts that are overdue on centrally billed accounts. If the Contractor
chooses to begin the suspension process, it shall follow the procedures
listed below if payment for the undisputed principal amount has not been
received 55 calendar days from the closing date on the invoice in which
the charges appeared. The Contractor shall:

1)  Notify the A/OPC and Designated Billing Office electronically or in
    writing of suspension if payment for the principal amount is not
    received by the close of business on the fifth (5th) calendar day
    after notification; and

2)  Notify the A/OPC and Designated Billing Office of the Contractor's
    point of contact to assist in resolving the past due account(s).

Suspension actions must be documented and, if requested, such
documentation must be provided to the GSA Contracting Officer. If
payment for the undisputed principal amount has not been received 61
calendar days from the closing date on the invoice in which the charges
appeared, the Contractor may suspend the account.

C.36.1 *Disputed Items:* The Contractor shall not suspend any account
for amounts in dispute.

C.36.2 *Reinstatement of Centrally Billed Suspended Accounts:* The
Contractor shall automatically reinstate suspended accounts upon payment
of the undisputed principal amount and Prompt Payment Act interest.

C.36.3 *Suspension/Reinstatement Record:* The Contractor shall maintain
a suspension/reinstate-ment file on accounts to include, at a minimum,
the agency/organization office name, the agency/organization identifying
number, the account number, the A/OPC and Designated Billing Office and
telephone numbers, invoice numbers, principal and estimated interest
penalty for each invoice, the number of days past due for each invoice,
documentation described in C.36, the date of suspension and the date of
reinstatement. This file shall be made available to the A/OPC,
Designated Billing Office and the GSA Contracting Officer immediately
upon request.

C.36.4 *Government Requested Suspension:* The A/OPC reserves the right
to suspend a centrally billed account under his/her purview and document
the reasons for the suspension. The GSA Contracting Officer reserves the
right to suspend a centrally billed account and document the reasons for
suspension. In accordance with the requirements specified in C.30,
Authorization Controls, the Contractor shall have the ability to void
cards at the request of the A/OPC or GSA Contracting Officer.

## C.37 CANCELLATION PROCEDURES FOR CENTRALLY BILLED ACCOUNTS

\[NOTE: CANCELLATION PROCEDURES FOR INDIVIDUALLY BILLED TRAVEL CARD
ACCOUNTS ARE SPECIFIED IN CB.19\]

The Contractor shall provide the Pre-Suspension/Pre-Cancellation Report
(reference C.38.1, subparagraph d) to the A/OPC to identify the
undisputed amount that is overdue on centrally billed accounts.

There are two reasons for which the Contractor may initiate cancellation
of a centrally billed account for non-payment of undisputed amounts:

1\. The account has been suspended two (2) times during a 12-month
period for undisputed amounts and is past due again as outlined in C.36
(e.g., an account is suspended in January and in December of any given
year and is past due again in March of the following year would be
eligible for cancellation); OR

2\. The account is past due for undisputed amounts, i.e., 120 calendar
days past the closing date on the invoice in which the charges appeared,
and the requirements of C.36, Suspension Procedures have been met.

If the Contractor chooses to begin cancellation procedures, it shall
follow the procedures listed below if payment for the undisputed
principal amount has not been received 120 calendar days from the
closing date on the invoice in which the charges appeared. The
Contractor shall either send a letter to the A/OPC and Designated
Billing Office or make a documented telephone call to the A/OPC and
Designated Billing Office requesting payment on past due accounts for
the undisputed principal amount. The Contractor shall:

1)  Notify the A/OPC and Designated Billing Office of cancellation if
    payment for the principal amount is not received by the close of
    business on the fifth (5th) calendar day after notification; and

2)  Notify the A/OPC and Designated Billing Office of the Contractor's
    point of contact to assist in resolving the past due account(s).

Cancellation actions must be documented and, if requested, such
documentation made available to the GSA Contracting Officer. If payment
for the undisputed principal amount has not been received 126 calendar
days from the closing date on the invoice in which the charges appeared,
the Contractor may cancel the account.

C.37.1 *Disputed Items:* The Contractor shall not cancel any account for
amounts in dispute.

C.37.2 *Reinstatement of Centrally Billed Canceled Accounts:* The
Contractor may reinstate canceled accounts upon payment of the
undisputed principal amount and Prompt Payment Act interest.

C.37.3 *Cancellation/Reinstatement Record:* The Contractor shall
maintain a cancellation/rein-statement file on accounts to include, at a
minimum, the agency/organization office name, the agency/organization
identifying number, the account number, the A/OPC and Designated Billing
Office and telephone numbers, invoice numbers, principal and estimated
interest penalty for each invoice, the number of days past due for each
invoice, documentation described in C.37, the date of suspension, the
date of reinstatement from suspension, the date of cancellation and the
date of reinstatement from cancellation. This file shall be made
available to the A/OPC, Designated Billing Office and the GSA
Contracting Officer immediately upon request.

C.37.4 *Government Requested Cancellation:* The A/OPC reserves the right
to cancel a centrally billed account under his/her purview and document
the reasons for the cancellation. The GSA Contracting Officer reserves
the right to cancel a centrally billed account and document the reasons
for suspension. In accordance with the requirements specified in C.30,
Authorization Controls, the Contractor shall have the ability to void
cards at the request of the A/OPC or GSA Contracting Officer.

***AGENCY REPORTING REQUIREMENTS***

## C.38 AGENCY REPORTING REQUIREMENTS

As specified in C.34, Program and Transaction Data, the Contractor shall
provide, at a minimum, its Level 3 platform for program and transaction
data and pass all data provided by merchants and obtained by the
Contractor.

Electronic reports shall provide the full functionality described in
C.34.1, Electronic Access to Program and Transaction Data, including the
ability to roll-up or break down the reports by agency/organization
levels within an agency/organization (e.g., department, major components
within a department, offices within major components, subelements within
offices, etc.). Although electronic transmission of program and
transaction data through the electronic access system is the preferred
mechanism for reporting, agencies/organizations may request other media
to include paper copy, disk, and magnetic tape reports. Reports shall
correspond with the agency/organization billing cycle (i.e., daily cycle
means daily reports, weekly cycle means weekly reports, monthly cycle
means monthly reports, etc.), unless otherwise specified by the
agency/organization. Additionally, the ability for the Government to
create ad-hoc reports based on all program and transaction data elements
is required.

Agencies/organizations may choose to receive some or all of these
reports unless noted below. Agencies/organizations shall determine
frequency (daily, weekly, monthly, quarterly, annually), distribution
points and method of transmission in their delivery or task order.

Unless otherwise specified, the Contractor shall provide their
commercial reports as indicated below. In addition to the requirements
below, there are additional data elements required in each business line
(reference CA.11, Fleet Card Program Reporting Requirements, CB.13,
Travel Card Program Reporting Requirements and CC.12, Purchase Card
Program Reporting Requirements). All reports shall be titled, dated,
numbered and paginated. Report information must coincide with invoice
information and transaction data information.

Release of program and transaction data is governed by 5 U.S.C. 552,
Freedom of Information Act.

C.38.1 *Essential Reports:* The following reports may or may not be
commercially standard reports, but are required for all
agencies/organizations. (NOTE\--If the Contractor has a commercial
report that will meet the stated specific need, it may propose that
report in lieu of the one specified.)

a)  Invoice: This is the official invoice. Required data elements are
    stated in C.35.7.3, Invoices, CA.10.1, Invoices for the Fleet Card
    Program and CB.11.3, Invoices for Centrally Billed Travel Card
    Accounts;

b)  Invoice Status Report: This report lists payment status on each
    invoice and includes all transaction data including original invoice
    number and other references required to identify the charge. This
    report is generally used by Designated Billing Offices to manage
    payments and disputes;

c)  Transaction Dispute Report: This report lists all outstanding and
    resolved transaction disputes and includes all information necessary
    to identify, track, balance and obtain status on the dispute from
    the original charge through resolution. This report is generally
    used by the Transaction Dispute Office to manage disputes. NOTE: The
    Travel Card Program requires this information segregated by
    individually and centrally billed accounts;

d)  Pre-Suspension/Pre-Cancellation Report: This report lists accounts
    eligible for suspension or cancellation and identifies account name,
    account number, status, balance past due, number of days past due
    and interest penalty. This report is generally used by the A/OPC to
    flag cardholders and accounts for A/OPC action and delinquency
    control. NOTE: The Travel Card Program requires this information
    segregated by individually and centrally billed accounts;

e)  Suspension/Cancellation Report: This report lists accounts that have
    been suspended or canceled and identifies account name, account
    number, status (suspended or canceled), date of status, balance past
    due, number of days past due and interest penalty. This report is
    generally used by the A/OPC for delinquency management. NOTE: The
    Travel Card Program requires this information segregated by
    individually and centrally billed accounts;

f)  Renewal Report: This report lists cards/accounts due to expire and
    identifies account name, account number, expiration date, and any
    other information required to determine renewal status. This report
    is generally used by the A/OPC to flag expiring cards; and

g)  Delinquency Report: This report lists account status for each
    30-120+ day time frame (i.e., 30 days, 60 days, 90 days, 120 days,
    120+ days). This report is generally used by the Designated Billing
    Office and the Chief Financial Officer to identify and manage
    delinquencies. NOTE: The Travel Card Program requires this
    information segregated by individually and centrally billed
    accounts.

C.38.2 *Other Agency Reports:* The Contractor(s) must offer all these
reports or their commercial equivalent to these reports.
Agencies/Organizations may choose to receive some or all of the
following reports:

a)  Account Activity Report: This report consists of summary totals for
    the reporting period, the fiscal year-to-date, by card and
    agency/organization. This report is generally used at all levels to
    obtain and manipulate program data. See CA.11.1, Account Activity
    Report for the Fleet Card Program, CB.13.1, Account Activity Report
    for the Travel Card Program, and CC.12.1, Account Activity Report
    for the Purchase Card Program for specific data elements;

b)  Master File Report: This report consists of master file information
    specified in C.34.5, Master File. It shall indicate whether the
    account is new. This report is generally used by the A/OPC to manage
    programmatic data;

c)  Statistical Summary Report: This report shall provide program
    summary information. This report is generally used at all levels to
    obtain and manipulate summary data. See CA.11.2, Statistical Summary
    Report for the Fleet Card Program, CB.13.2, Statistical Summary
    Report for the Travel Card Program and CC.12.2, Statistical Summary
    Report for the Purchase Card Program for specific data elements;

d)  Account Change Report: This report lists any changes made to the
    master file information specified in C.34.5, Master File, and
    identifies what, when and why elements(s) were changed. This report
    is generally used by A/OPCs to manage programmatic data as well as
    to flag/verify changes;

e)  Exception Report: This report identifies lost, stolen, invalid or
    canceled cards, declined transactions and unusual spending activity,
    and details such transaction activity. It includes current and past
    balances. This report is generally used by A/OPCs and Designated
    Billing Offices to monitor cardholder activity, track misuse and/or
    identify training needs of a cardholder;

f)  Current Accounts Report: This report lists all accounts in
    alphabetical order and includes all information necessary to
    identify and contact the account holder. This report is generally
    used by A/OPCs as an easy reference to cardholder identification.
    NOTE: The Travel Card Program requires this information segregated
    by individually and centrally billed accounts;

g)  1099 Report: This report lists summary payments made to merchants on
    a quarterly and cumulative calendar year basis. It shall be in
    merchant TIN ascending numeric order and include amount of purchase,
    merchant name, corporate status, identify doing business as (DBA) if
    applicable, and merchant address. This report is generally used by
    the agency/organization in fulfilling the requirements of 26 U.S.C.
    6050M;

h)  1057 Report: This report lists summary merchant demographic
    information (minority, women-owned business) on a quarterly and
    cumulative fiscal year basis. It shall be in merchant TIN ascending
    numeric order and include amount of purchase, merchant name,
    merchant address, merchant demographic information, standard
    industrialization classification (SIC) code or replacement (SIC is
    in the process of being replaced by the North American
    Classification System (NAICS), and size standard. This report is
    generally used by the agency/organization in fulfilling its small
    business and small disadvantaged business goals;

i)  Payment Performance and Refund Report: This report lists the payment
    performance (average payment time) and any refunds paid to the
    agency/organization level. It includes total net charge volume,
    payment performance, refund amount and type of refund. This report
    is generally used by the agency/organization to analyze payment
    performance and refunds as well as audit purposes;

j)  Detailed Transaction File: This file lists each cardholder's
    detailed transactions for the reporting period and contains all
    transaction data. This file is generally used by the
    agency/organization in processing transactions through their
    financial systems and for reporting purposes;

k)  Write-Off Report: This report lists the amounts written-off and the
    reasons for the write-offs. This report is generally used by the
    agency/organization to identify problem areas to better manage
    delinquencies in the future, to analyze and project programmatic
    data for the future, and to verify and balance delinquent data in
    contract reports;

l)  Summary Quarterly Merchant Report: This report lists, by fiscal year
    quarter, summary spending information by merchant category code and
    includes merchant category code description, number of transactions
    per merchant category code, total dollar amount per merchant
    category code, and average dollar amount per merchant category code.
    This report is generally used by the agency/organization to
    summarize supplier categories where the agency/organization dollars
    are spent, trend analysis, etc.;

m)  Summary Quarterly Vendor Analysis Report: This report lists, by
    fiscal year, a detailed quarterly and cumulative summary of the top
    100 merchants/vendors, by individual merchant/vendor, city, state,
    and service type, in total dollars and total number of transactions.
    This report is generally used by the agency/organization to
    negotiate better discounts with merchants, trend analysis, etc.;

n)  Summary Quarterly Vendor Ranking Report: This report lists, by
    fiscal year, a quarterly and comparative summary by name and type of
    vendor, ranking the major vendors and their dollar charges, along
    with a percentage breakdown of totals and changes from the previous
    quarter and the same quarter a year ago, if applicable. This report
    is generally used by the agency/organization for market and trend
    analysis, etc.

***GSA CONTRACTING OFFICE REPORTING REQUIREMENTS***

## C.39 GSA CONTRACTING OFFICE REPORTS

It is not feasible for the GSA Contracting Office to gather program
information at the master contract level if multiple systems are used.
Thus, the GSA Contracting Office has specified particular formats and
particular data elements required in its oversight and management of the
Card Program(s). The electronic format specified may change during the
contract period. GSA reserves the right to contract separately for data
warehousing services in order to compile data from multiple databases,
on different operating systems, or on various platforms. Should GSA
exercise this right, the Contractor shall provide the data to the data
warehouser in a format to be mutually agreed upon by the Contractor and
the GSA Contracting Officer.

The following reports shall be provided in the format specified below
and in agency/organization identifying number order to the GSA
Contracting Officer, ATTN: Rebecca Koses, Support Services Division
(FCXC), Services Acquisition Center, Washington, DC 20406. Reports shall
be provided at the frequencies stated in each report. One electronic
copy of each report shall be delivered in a commercial database (e.g.,
Dbase IV, Paradox 4.0, FoxPro, Microsoft Access). Hard copies or other
electronic medium may be required for some reports as specified, at no
additional cost.

a)  Agency/Organization Program Information Report: This report shall
    provide a list of all participating agencies/organizations, bureaus,
    divisions, offices or other organizational elements at each
    hierarchy level as specified in C.34.2, Agency/Organization Program
    Information. Updates/revisions shall also be included. This report
    shall be sent no later than the **5th calendar day** of each month
    to the GSA Contracting Officer. Unless otherwise specified by the
    GSA Contracting Officer, the Contractor shall provide a 3.5"
    diskette to the GSA Contracting Officer, containing four (4)
    separate files. File 1 shall contain the A/OPCs; file 2 shall
    contain the Designated Billing Office point of contact; file 3 shall
    contain the Transaction Dispute Office point of contact; and file 4
    shall contain the EC/EDI Office point of contact. The Contractor
    shall send, by the **5th calendar day of each subsequent month**,
    either a full-file replacement of the agency/organization program
    information, or a 3.5" diskette with only the updates/revisions in
    the format specified above to the GSA Contracting Officer. If the
    Contractor elects to only provide an updated diskette, it must
    clearly segregate A/OPC, Designated Billing Office, Transaction
    Dispute Office and EC/EDI Office points of contact. The data shall
    be in the following format:\
    \
    Field 1 Agency/organization name

    Field 2 Agency/organization identifying number

    Field 3 First Name

    Field 4 Last Name

    Field 5 Address 1

    Field 6 Address 2

    Field 7 City

    Field 8 State

    Field 9 Zip + 4

    Field 10 Area Code and Telephone Number

    Field 11 Area Code and Facsimile Number

    Field 12 E-mail address

b)  Program Report: This report shall list, on a monthly and cumulative
    basis, activity on the Card Program(s) as indicated below. This
    report shall include a roll-up section of each hierarchy level for
    each ordering agency/organization. This report shall be sent by the
    **10th calendar day** of each month to the GSA Contracting Officer.

    Field 1 Agency/organization name;

    Field 2 Agency/organization identifying numbers;

    Field 3 Monthly dollar charge volume;

    Field 4 Monthly dollar credits;

    Field 5 Monthly net dollar charge volume (Field 3 minus Field 4);

    Field 6 Monthly number of charge transactions;

    Field 7 Number of active cardholders for the month;

    Field 8 Total number of cardholders for the month;

    Field 9 Miscellaneous fees and identification of fee (e.g., \$x for
    customized

    services, \$x for annual card fee for individually billed travel
    card accounts, \$x for value-added products and services, etc.)

    Field 10 Cumulative month-to-date program dollar charge volume;

    Field 11 Cumulative month-to-date credits;

    Field 12 Cumulative month-to-date net program dollar charge volume

    (Field 10 minus Field 11);

    Field 13 Cumulative month-to-date charge transaction volume;

    Field 14 Cumulative program cardholders; and

    Field 15 Cumulative miscellaneous fees.

c)  Government-Wide Aging Analysis Report: This report lists summary
    account status and ranking for 30-120+ day time frame on a
    government-wide basis for each agency/organization and each business
    line. It shall segregate account status by 30, 60, 90, 120, and 120+
    days, by agency/organization. It shall include both individually and
    centrally billed accounts. This report shall be sent by the **tenth
    (10th) calendar day** of each month to the GSA Contracting Officer.

    Field 1 Agency/organization name;

    Field 2 Agency/organization identifying number;

    Field 3 Amount 30 days past due;

    Field 4 Number of accounts 30 days past due;

    Field 5 Amount 60 days past due;

    Field 6 Number of accounts 60 days past due;

    Field 7 Amount 90 days past due;

    Field 8 Number of accounts 90 days past due;

    Field 9 Amount 120 days past due;

    Field 10 Number of accounts 120 days past due;

    Field 11 Amount 120+ days past due;

    Field 12 Number of accounts 120+ days past due;

    Field 13 Status (suspended/canceled);

    Field 14 Ranking by amount among agencies/organizations; and\
    Field 15 Ranking by number of accounts among agencies/organizations.

d)  Agency/Organization Refund Report: This report lists sales and
    productivity refunds at the summary level to the agency/organization
    for each business line. This report shall be sent by the **fifteenth
    (15th) calendar day** of each fiscal year quarter.

    Field 1 Agency/organization name;

    Field 2 Agency/organization identifying number;

    Field 3 Agency/organization net charge volume;

    Field 4 Agency/organization refund amount on charge volume;

    Field 5 Agency/organization productivity refund amount; and

    Field 6 Total refund amount.

e)  Task Order Copies*:* The Contractor shall provide an electronic copy
    in a commercially standard word processing program (e.g., Word,
    WordPerfect) of each awarded task order for the reporting month for
    each business line. If an electronic copy is not provided by the
    agency/organization, the Contractor shall forward a hard copy. The
    Contractor shall include the agency/organization task order and the
    awarded technical and price proposal. Complete copies shall be sent
    by the **tenth (10th) calendar day** of each month to the GSA
    Contracting Officer.

f)  Miscellaneous Expense Report: This report provides, by
    agency/organization, summary miscellaneous expenses such as
    customized services, value-added products/services or individually
    billed travel card account per card fees on a quarterly basis. It
    shall include a detailed identification of the expense, amount and
    date. This report shall be sent by the **15th calendar day** after
    the end of each fiscal year quarter to the GSA Contracting Officer
    and shall be in the following format:\
    \
    Field 1 Agency/organization name;\
    Field 2 Date of expense;\
    Field 3 Description of expense; and\
    Field 4 Amount of expense.

g)  Summary Quarterly Merchant Report*:* This report provides, by fiscal
    year quarter, agency/organization summary spending information by
    merchant category code for each business line. This report shall be
    sent by the **15th calendar day** after the end of each fiscal year
    quarter to the GSA Contracting Officer and shall be in the following
    format:

    Field 1 Agency/organization name;

    Field 2 Merchant category code;

    Field 3 Merchant category code description;

    Field 4 Number of transactions per merchant category code;

    Field 5 Total dollar amount per merchant category code; and

    Field 6 Average dollar amount per merchant category code.

h)  Summary Quarterly Vendor Analysis Report*:* This report provides, by
    fiscal year, a detailed quarterly and cumulative summary of the top
    100 merchants/vendors for each business line, by individual
    merchant/vendor, in total dollars and total number of transactions.
    This report shall be sent by the **fifteenth (15) calendar day**
    after the end of each fiscal year quarter.

    Field 1 Fiscal year;

    Field 2 Merchant;

    Field 3 Quarter 1 total transactions;

    Field 4 Quarter 1 total dollars;

    Field 5 Quarter 2 total transactions;

    Field 6 Quarter 2 total dollars;

    Field 7 Quarter 3 total transactions;

    Field 8 Quarter 3 total dollars;

    Field 9 Quarter 4 total transactions;

    Field 10 Quarter 4 total dollars;

    Field 11 Cumulative transactions; and

    Field 12 Cumulative dollars.

i)  Summary Quarterly Vendor Ranking Report: This report provides, by
    fiscal year, a quarterly and cumulative summary by type of vendor
    (e.g., gasoline station, airline, computer merchant, etc.) for each
    business line, ranking the major vendors and their dollar charges,
    along with a percentage breakdown of totals and changes from the
    previous quarter and the same quarter a year ago, if applicable.
    This report shall be sent by the **fifteenth (15) calendar day**
    after the end of each fiscal year quarter.

    Field 1 Fiscal year;

    Field 2 Type of vendor;

    Field 3 Name of vendor;

    Field 4 Dollars;

    Field 5 Percentage breakdown of total dollars per type of vendor;

    Field 6 Change from preceding quarter; and

    Field 7 Change from same quarter a year ago.

j)  Summary Transaction Data Report: This report provides a summary of
    agency/organization purchases for each business line. This report
    shall be sent by the **10th calendar day** of each month to the GSA
    Contracting Officer:

> Field 1 Agency/organization name;
>
> Field 2 Agency/organization identifying number (FIPS 55);
>
> Field 3 Amount of purchase;
>
> Field 4 Merchant category code;
>
> Field 5 Merchant's name;
>
> Field 6 Merchant's address (city and state);
>
> Field 7 Merchant's TIN;
>
> Field 8 Merchant's DUNs;
>
> Field 9 Corporate status (from agency/organization 1099 report);
>
> Field 10 Socio-economic status (from agency/organization 1057 report);
>
> Field 11 Standard industrial classification code (from the
>
> agency/organization 1057 report); and
>
> Field 12 Size standard (from the agency/organization 1057 report).
>
> k\) Ad-Hoc Reports: These reports will be identified on as-needed
> basis.

C.39.1 *GSA Contracting Officer Reports Specific to the Travel Card
Business Line:* In addition to the reports specified in C.39, Reporting
Requirements, the following required reports are specific to the travel
card business line. The reports shall be submitted in the format and
medium specified, by the timeframes specified below.

a)  Monthly Audit Report: The Contractor shall provide a complete
    electronic report of all common carrier transactions, including
    refunds and adjustments, for the travel card business line. Hard
    copies may be required. This data shall be sent by the **5th
    calendar day** of each month, to GSA, Federal Supply Service, Office
    of Transportation Audits (FW), Washington DC 20405. The audit
    reporting information shall include the following:

    Item Characters Name Description

    1 5 Account Number Credit card number

    2 4 Issuing Carrier (SCAC) NMFC reference

    3 20 Passenger Name Name of passenger

    4 6 Issue Date Date ticket issued

    5 6 Travel Date Date travel commences

    (each leg)

    6 13 Ticket Number Airline control number

    7 13 Conjunction Ticket Additional tickets

    8 13 Exchange Ticket Reissued ticket

    9 2 ARC Carrier Code Airline Reporting Corp. Code

    10 1 Coupon Number 1, 2, 3, 4

    11 2 Class Service Class designator

    12 3 Origin City For each leg

    13 1 Stopover (X or O) each leg

    14 3 Destination City For each leg

    15 8 Fare Basis YCA, BDG, etc.

    16 4 Flight Number Flight number

    17 4 Departure Time Time leaving origin

    18 4 Arrival Time Time arriving destination

    19 8 Total Fare Total fare for all legs

    20 5 Fee Applicable fee/surcharge

    21 5 Taxes Domestic/international taxes

    22 8 Total Cost Total fare + fees + taxes

    23 20 Endorsement/Restrictions Checkage Invitational

    Travel Order, Prisoner, etc.

    Refund information shall include the following:

    1\. Last Name

    2\. First Name

    3\. Account number (means the complete travel card number)

    4\. Transaction Date

    5\. Credit Amount

    6\. Airline carrier

    7\. Original ticket number

    8\. Credit ticket number

    9\. Date credit issued (not the date of request for refund)

    For audit reporting, the transaction information may be the actual
    documentation and a magnetic tape, or a clear photocopy of the
    documentation and a magnetic tape. For refund reporting, the
    transaction information shall be furnished on magnetic tape.

b)  Airline City-Pair Reports: The Contractor shall provide the
    following data in the format specified to GSA, Federal Supply
    Service, Services Acquisition Center (FCXB), ATTN: Contracting
    Officer, City Pair Program, Washington DC 20406, for the travel card
    business line.

    Each city pair is awarded individually. Within 30 days of award of
    the city pair contracts, GSA will provide the contractor(s) on
    diskette, a listing of city pair awardees and a listing of all
    applicable contract fare basis codes. Fare basis codes will have
    three to eight characters. Currently, all domestic contract fares
    begin with the characters YCA. In cities with multiple airports, the
    airport designators are added, e.g., in Houston, YCAIAH and YCAHOU.
    For travel between two city pairs with multiple airports, the fare
    basis code will be YCA, first airport code, first two characters of
    second airport code, e.g., YCALGADC. Currently, international fares
    begin with any alpha followed by CA. Business class fare basis codes
    begin with \_\_CB. In the future, additional fare basis codes may be
    added and existing ones may be changed.

    In all reports where airports are required fields, the two airports
    shall be separate fields. Domestically, city pairs are to be
    **reported** by airport code and are to be in alphabetical order,
    first by city, then by state. For example, Columbus, GA is before
    Columbus, OH. Atlanta, GA/Denver, CO and Denver, CO/Atlanta, GA is
    to be reported as ATL/DEN, regardless of the direction of the
    travel. Internationally, city pairs are to be **reported** by city
    code and alphabetized by US city, then US state, then by
    international country and city. They are to be reported in this
    order, regardless of direction. For example, travel between
    Washington and London is to be reported as WAS/LON regardless of
    what combination of BWI, Dulles, Heathrow or Gatwick airports are
    used and regardless of direction of travel.

    All reports are to be in the following formats:

    One electronic copy shall be delivered in a commercial database,
    e.g., Dbase IV, Paradox 4.0, Microsoft Access, FoxPro. The format
    shall be agreed to by the GSA Contracting Officer for the City Pair
    Program, Air Transportation Service, Service Contracts Division
    (FCXB), Services Acquisition Center, Washington DC 20406. The
    electronic format may change during the contract period.

    One hard copy of all quarterly and annual reports. Monthly reports
    shall be furnished in hard copy when requested by the City Pair
    Contracting Officer.

    The following reports are required on a monthly or quarterly basis,
    as indicated below:

    1\. Contract City Pair Travel Report: This report lists number of
    trips and dollars, by

    airline and fare basis code, of all city pairs. This report shall be
    sent by the **10th calendar day** of each month.

    Field 1 Carrier

    Field 2 Airport/city pair code (first airport)

    Field 3 Airport/city pair code (second airport)

    Field 4 Number of trips

    Field 5 Fare basis code; and

    Field 6 Total dollars;

    2\. Contract Fare Comparison Report: This report provides a
    comparative analysis of\
    travel charged. This report shall be sent by the **10th calendar
    day** of each

    month.

    Field 1 Carrier;

    Field 2 First airport/city pair code;

    Field 3 Second airport/city pair code;

    Field 4 Number of trips with any unrestricted contract fare basis
    code (codes beginning with Y);

    Field 5 Total unrestricted contract dollars;

    Field 6 Average unrestricted contract price per trip;

    Field 7 Number of trips with any restricted contract fare basis code

    (codes beginning with other than Y);

    Field 8 Total restricted contract dollars;

    Field 9 Average restricted contract price per trip;

    Field 10 Number of trips with any contract business fare basis code;

    Field 11 Total business fare basis contract dollars;

    Field 12 Average business fare basis contract dollars;

    Field 13 Number of trips with any non-contract fare basis code;

    Field 14 Total non-contract dollars;

    Field 15 Average non-contract price per trip;

> 3\. Top 100 Markets by City Pair Report: This report identifies the
> top 100 markets\
> by city pair. This report shall be sent by the **10th calendar day**
> of each month.
>
> Field 1 Carrier;
>
> Field 2 First airport/city pair code;
>
> Field 3 Second airport/city pair code;
>
> Field 4 Total trips with contract fare basis code;
>
> Field 5 Total contract dollars;
>
> Field 6 Total other fare basis code trips;
>
> Field 7 Total other fare basis dollars; and
>
> Field 8 Grand total dollars.
>
> 4\. Airport/City Pair with \$0 Contract Fare Basis Code Sales Report:
> This report lists\
> the city pairs with \$0. This report shall be sent by the **10th
> calendar day** of\
> each month.
>
> Field 1 First airport/city pair code with \$0 sales; and
>
> Field 2 Second airport/city pair code with \$0 sales.
>
> 5\. Top 100 Markets with No Contract Fare Basis Codes Report: This
> report\
> provides information on the top 100 domestic city pairs with no
> contract fare basis\
> codes. This report shall be sent by the **10th calendar day** of each
> fiscal year
>
> quarter:
>
> Field 1 First airport/city pair code;
>
> Field 2 Second airport/city pair code;
>
> Field 3 Number of trips per market; and
>
> Field 4 Number of dollars per market.
>
> 6\. Total Travel Report: This report provides a summary of Government
> travel. This\
> report shall be sent by the **10th calendar day** of the end of the
> fiscal year.
>
> Field 1 First airport/city pair code;
>
> Field 2 Second airport/city pair code;
>
> Field 3 Total number of trips by airport/city pair cumulative; and
>
> Field 4 Total number of dollars by airport/city pair cumulative.
>
> 7\. Total Dollars Spent on Air Travel, by Carrier: This report
> provides a summary of\
> Government travel by carrier. This report shall be sent by the **10th
> calendar\
> day** of the end of the month.
>
> Field 1 Carrier;
>
> Field 2 Total dollars, all contract fare basis codes; and
>
> Field 3 Total dollars, all other fare basis codes; and
>
> Field 4 Dollars cumulative.
>
> c\) GSA Contracting Office Reports for the Travel Card Program:\
> \
> 1. Summary ATM/Travelers Checks Report: This report provides a summary
> of
>
> total ATM/travelers checks dollars and number of transactions by each
>
> participating agency/organization, by month and cumulative. This
> report shall be
>
> sent by the **10th calendar day** of the end of the month.
>
> Field 1 Agency/organization name;
>
> Field 2 Agency/organization identifying numbers;
>
> Field 3 Monthly ATM/travelers check volume;
>
> Field 4 Monthly ATM/travelers check transactions;
>
> Field 5 Monthly ATM/travelers check fees;
>
> Field 6 Cumulative month-to-date ATM/travelers check volume;
>
> Field 7 Cumulative month-to-date ATM/travelers check
>
> transactions; and
>
> Field 8 Cumulative month-to-date ATM/travelers check fees.

C.39.2 *GSA Contracting Officer Reports Specific to the Purchase Card
Business Line:* In addition to the requirements specified in C.39,
Reporting Requirements, the following required reports are specific to
the purchase card business line. The reports shall be submitted in the
format and medium specified, by the timeframes specified below.

a)  *Summary Purchase Report:* This report provides a summary of
    agency/organization purchases under and over \$2,500. This report
    shall be sent by the **15th calendar day** of the end of the fiscal
    year quarter to the GSA Contracting Officer:

Field 1 Agency/organization name;

Field 2 Agency/organization identifying number;

Field 3 Number of transactions under \$2,500;

Field 4 Total dollar value of transactions under \$2,500;

Field 5 Number of transactions over \$2,500;

Field 6 Total dollar value of transactions over \$2,500;

Field 7 Percentage of total dollars under \$2,500; and

Field 8 Percentage of total dollars over \$2,500.

> b\) Summary Bank Checks Report: This report provides a summary of
>
> total bank check dollars and number of transactions by each
> participating\
> agency/organization, by month and cumulative. This report shall be
> sent by the\
> **10th calendar day** of the end of the month.
>
> Field 1 Agency/organization name;
>
> Field 2 Agency/organization identifying numbers;
>
> Field 3 Monthly bank check volume;
>
> Field 4 Monthly bank check transactions;
>
> Field 5 Monthly bank check fees;
>
> Field 6 Cumulative month-to-date bank check volume;
>
> Field 7 Cumulative month-to-date bank check transactions; and
>
> Field 8 Cumulative month-to-date bank check fees.

***CUSTOMIZED SERVICES***

## C.40 CUSTOMIZED SERVICES:

C.40.1 *Customized Services for the GSA Contracting Office:* These
customized services are services that are a substantial modification or
change to the master contract within the scope of the master contract
(e.g., pilot programs initiated by the GSA Contracting Office with
government-wide applicability, customized training materials for the
Card Programs (e.g., creation of a CD-ROM, video, computer software), a
pilot or demonstration of new processes, or contractor- or
government-suggested service improvements in accordance with the
Addendum to Clause 52.212-4, paragraph 42, Service Improvements).
Customized services may run for a period of time shorter than the master
contract and may have requirements for evaluation, feedback and
reporting. Customized services will be negotiated and priced separately
between the GSA Contracting Officer and the Contractor(s), and paid for
by the GSA Contracting Office.

The Contractor shall provide a detailed proposal within **15 calendar
days** of the GSA Contracting Officer's request for customized services,
unless otherwise directed. The proposal shall include, at a minimum, the
technical and management approach, an identification of the CLIN(s),
skill category(ies), number of hours, hourly rate, extended total, total
price, and milestone schedule.

C.40.2 *Customized Services for the Agencies/Organizations:* These
customized services are services that are a substantial modification or
change to an agency's/organization's task order within the scope of the
agency's/organization's task order (e.g., customized
agency/organization-specific training materials (e.g., on CD-ROM, video,
computer software), production and submittal of agency/organization 1099
information to the Internal Revenue Service, etc.), a pilot or
demonstration of new processes, or contractor- or government-suggested
service improvements in accordance with the Addendum to Clause 52.212-4,
paragraph 42, Service Improvements). Customized services may run for a
period of time shorter than the agency/organization task order length
and may have requirements for evaluation, feedback and reporting.
Customized services will be negotiated and priced separately between the
agency/organization and the Contractor and paid for by the requesting
agency/organization. An agency/organization may not modify or change the
terms and conditions of the master contract. Because agency/organization
customized services may have wide-spread government applicability, the
Contractor shall keep the GSA Contracting Officer apprised on a monthly
basis (no later than the **15th calendar day** of each month) of
agency/organization customized services to include, but not be limited
to, services performed, price, evaluation and feedback, etc.

The Contractor shall provide a detailed proposal within **15 calendar
days** of the agency's/organization's request for customized services,
unless otherwise directed. The proposal shall include, at a minimum, the
technical and management approach, an identification of the CLIN(s),
skill category(ies), number of hours, hourly rate, extended total, total
price, and milestone schedule.

***TRANSITION***

## C.41 Transition Requirements:

There are four types of transition requirements. The first type is
contract start-up transition discussed in C.27, Start-Up Implementation
Requirements. The second type is agency/organization transition in which
an agency/organization, throughout the life of the master contract, may
choose to switch vendors. The third type is a master contract transition
resulting from a change in the master contractor as a consequence of a
resolicitation. The fourth type is a technological advance transition.
During each transition type described, the Contractor shall maintain an
adequate knowledge base of the Government's Card Program(s) to
effectuate the transition with minimal disruption.

Cooperative, orderly, and seamless transitions are crucial to the
Government's mission requirements.

C.41.1 *Contract Start-Up Transition:* The Contractor shall furnish
phase-in training to agencies/organizations transitioning to the master
contract and exercise its best efforts to effect a cooperative, orderly,
and seamless transition from current GSA contracts (GS-22F-97501 (fleet
card), GS-00F-34139 (travel card), GS-23F-94031 (purchase card)). This
shall include a cooperative and professional arrangement with the
incumbent as well as agencies/organizations. The GSA anticipates that
agencies/organizations may take approximately ten (10) months to
effectuate their transition to the master contract. Reference C.27,
Start-Up Implementation Requirements, for specific contract start-up
requirements.

C.41.2 *Agency/Organization Transition:* The Contractor shall furnish
phase-in training with a successor contractor and exercise its best
efforts to effect a cooperative, orderly, and seamless transition should
an agency/organization decide to change contractors. The Contractor
shall, upon the A/OPC\'s written notice, furnish phase-in, phase-out
services for up to **180 working days** prior to the expiration date of
the task order. The Contractor shall provide sufficient, experienced
personnel during the phase-in, phase-out period to ensure that there is
no diminution in the quality of services provided under its task order.
The Contractor shall provide to the A/OPC a complete, non-proprietary,
current and accurate master file of individually billed and centrally
billed accounts, in hard copy, magnetic tape, or other agreed-upon
medium(a) at least **90 calendar days** prior to the end of the task
order, in a format to be approved by the Government. The master file
shall also include accurate information regarding suspended or canceled
accounts. At its discretion, the Government may reduce the transition
period.

The Contractor and the Government shall utilize their best efforts to
reconcile each account balance and settle each transaction dispute
within 180 calendar days of the completed agency/organization
transition.

C.41.3 *Master Contract Transition:* The Contractor shall furnish
phase-in training with a successor contractor and exercise its best
efforts to effect a cooperative, orderly, and seamless transition to a
successor. The Contractor shall, upon the GSA Contracting Officer\'s
written notice, furnish phase-in, phase-out services for up to **365
calendar days** prior to the expiration date of this contract. The
Contractor shall provide sufficient, experienced personnel during the
phase-in, phase-out period to ensure that there is no diminution in the
quality of services provided under the master contract and
agency/organization task orders. The Contractor shall provide to the GSA
Contracting Officer a complete, non-proprietary, current and accurate
master file of all accounts, in hard copy, magnetic tape or other
agreed-upon medium(a) at least **90 calendar days** prior to the end of
the contract, in a format to be approved by the Government. The master
file shall also include accurate information regarding suspended or
canceled accounts. At its discretion, the Government may reduce the
transition period.

The Contractor and the Government shall utilize its best efforts to
reconcile each account balance and settle each transaction dispute
within 180 calendar days of the completed transition.

C.41.4 *Technological Advance Transition:* The Contractor shall ensure
that any change brought about by technological advance is effectuated in
a smooth, seamless manner, with minimal disruption to the card program.
The Contractor shall coordinate any technological transition with the
participating users and the GSA Contracting Officer at least **90
calendar days** prior to transition.

***RECORD RETENTION AND RETRIEVAL***

## C.42 RECORD RETENTION AND RETRIEVAL

The Contractor shall agree to be the Government's agent for document
repository as it relates to transactions under the Card Program(s). The
Contractor shall maintain electronic records of all transactions for a
period of three (3) years after the contract expires. Upon written
request of the GSA Contracting Officer, the ordering Contracting
Officer, the A/OPC, or the Internal Revenue Service with A/OPC knowledge
and approval, the Contractor shall provide the requested information in
a widely available commercial format selected by the Government within
**30 calendar days**, unless otherwise specified.

***POST CONTRACT REQUIREMENTS***

## C.43 POST CONTRACT REQUIREMENTS

On the final expiration date of the master contract or
agency/organization task order, all accounts must be deactivated;
however, all transactions dated prior to the expiration date shall be
processed.

The Contractor shall continue to generate and distribute all records,
reports and copies of documents and refunds as was originally required
under the expired master contract or agency/organization task order,
with respect to all transactions dated prior to the expiration date and
all disputed transactions, until all activity under the master contract
or agency/organization task order is completed.

However, the requirement for the Contractor to perform work after the
expiration date of the master contract or delivery or task order shall
not exceed 90 calendar days, or until final conclusion of the activity,
whichever is sooner. The Contractor and the Government shall utilize
their best efforts to reconcile each account balance and settle each
transaction dispute within the 90-calendar day period. The Government is
not liable for any activity under individually billed accounts (i.e.,
travel card program). If no resolution occurs at the end of the
90-calendar day period following the expiration of the master contract
or agency/organization task order, the GSA or ordering Contracting
Officer, respectively, will make a final determination with respect to
the matter in need of resolution. The ordering Contracting Officer will
close out his/her task order and the GSA Contracting Officer will close
out the master contract.

***PER CARD FEES***

## C.44 CARD FEES

Card fees (e.g., annual card fees, card issuance fees, etc.) for core
requirements are prohibited, unless otherwise specified herein.

***GOVERNMENT-WIDE SHUT DOWN***

## C.45 GOVERNMENT-WIDE SHUT DOWN

Each year, Congress must pass appropriation bills authorizing funds for
Government agencies/organizations. 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 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 would be late for most accounts;
however, all centrally billed accounts would be paid with Prompt Payment
Act interest upon a budget passing. The Contractor shall not deactivate
any account unless otherwise notified.

***CENTRALLY BILLED ACCOUNT LIABILITY***

## C.46 LIABILITY FOR CENTRALLY BILLED ACCOUNTS

NOTE: For individually billed account liability on the Travel Card
Program, see CB.20, Liability for Individually Billed Accounts on the
Travel Card Program.

C.46.1 *Government Liability:* The Government accepts liability only for
those proper charges made by an authorized Federal government cardholder
using the Card Program(s). Unauthorized use means the use of a credit
card by a person, other than the cardholder, who does not have actual,
implied or apparent authority for such use and from which the cardholder
receives no benefit. The Government shall not be liable for any
unauthorized use.

C.46.1.1 *[Government Liability for Lost or Stolen Cards]{.underline}:*
The Government shall not be liable for cards reported lost or stolen.

Subject to the above, the Government will make reasonable efforts to
notify the Contractor promptly when it becomes evident that a card is
lost, stolen or being used improperly by a cardholder.

> **VALUE-ADDED PRODUCTS AND SERVICES - TIER 2**

***VALUE-ADDED PRODUCTS AND SERVICES***

## C.47 VALUE-ADDED PRODUCTS AND SERVICES

There are several commercially available products and services that add
significant value to an agency's/organization's Card Program(s).
However, due to an agency's/organization's individual composition,
technology status, and other factors, the agency's/organization's
ability to take advantage of these products and services vary
significantly. Agencies/organizations may require value-added products
and services in their core Card Program and will so state in their task
order.

Contractors are not required to offer the following list of products and
services for award of the master contract; however, if such products and
services are offered, they must be offered at the master contract level
in order to make them available at the agency/organization task order
level. The Contractor can distinguish themselves in the task order
process by offering these and other types of products and services.
Agencies/organizations may examine the Contractor's capability to
provide these and other types of products and services to assist in
their task order award decision.

The Contractor may provide a variety of Tier 2 products and services
that enhance or facilitate the Card Program(s) for each business line.
The following is a sample list of the types of products and services
that may be offered under this contract. While the types of products and
services are NOT limited to those shown below; they are limited to the
scope of the master contract.

The design, format, timing, medium(a), delivery, price, or
agency/organization specifics of Tier 2 products and services shall be
specified and negotiated at the time of the task order, or any
modification thereto.

C.47.1 *Additional Authorization Controls:* If offered, the Contractor
may provide additional authorization controls specified in C.30,
Authorization Controls, such as preferred supplier listing (a feature to
allow the agency/organization to compile and restrict approved
suppliers), preferred supplier listing threshold (a feature to allow the
agency/organization to compile and restrict approved suppliers for
transactions of a dollar amount greater than an amount designated by the
agency/organization), or other methods to code unauthorized
transactions. Specific to the fleet card program, and if offered by the
Contractor, additional controls such as maintenance pre-authorization
integration with the customer's authorization system or maintenance
pre-authorization service based on vehicle-type history or specific
vehicle history (does not include directing users to particular
merchants) would be value-added to the fleet card program.

C.47.2 *Software:* Not including the electronic access system required
in C.34.1, and if offered, the Contractor may provide and support other
commercial off-the-shelf or customized software that assists
agencies/organizations in their Card Program(s). Customizing of software
must be consistent with customizing of standard commercial software
normally performed for commercial customers. This includes, but is not
limited to, streamlining Government backroom processes (e.g.,
vouchering, accounts payable, etc.). Specific to the Fleet Card Program,
and if offered, the Contractor may provide integration with on-site fuel
systems (e.g., military bases, national parks, ports) and integration
with private alternative fuel systems (e.g., state governments,
utilities, etc.).

C.47.3 *Stored-value card or E-purse products and services:* If offered,
the Contractor may provide stored-value card or E-purse products and
services for the Card Program(s). This service provides the cardholder a
reloadable purse to be used for small dollar purchases. The reload
function will always be PIN protected, and the purse may be PIN
protected or not PIN protected at the agency's/organization's option.
The purse may be loaded from the cardholder's account/fund, or from a
government account/fund for a cash advance. The stored value system will
be a fully auditable governmental open system with purchases typically
made in cafeterias, vending machines or other sites.

Data contained in the card should include, but is not limited to Basic
ID (reference subparagraph C.47.10.2, subparagraph m) 1., plus:

> 1\. Private key encryption keys;
>
> 2\. Purse limitations;
>
> 3\. Transaction file; and
>
> 4\. Purse balance.

Each stored value transaction should contain the following information
which will be captured and forwarded to the host computer for processing
and settlement. The card's transaction file containing the last thirty
transactions will not exceed twenty bytes per transaction.

> 1\. Merchant number;
>
> 2\. Terminal number;
>
> 3\. Date, time, transaction amount;
>
> 4\. Card serial number; and
>
> 5\. Product code.

Each card used for stored value will store a transaction file in the
card containing the last thirty transactions. This file is for the
convenience of the cardholder, and is not intended to replace the
permanent host file.

Open system stored value transactions will be captured by each device
accepting the stored value purse, and will be batched and transmitted to
the appropriate host on a daily basis. Reconciliation and settlement
will also take place on a daily basis.

Value may be "loaded" to the stored value component of the card directly
from an account/fund maintained by the government or cardholder to
augment or replace cash advances.

C.47.4 *Debit Card Products and Services:* If offered, the Contractor
may provide debit card products and services for the Card Program(s).
The debit cards may be on-line or off-line.

C.47.5 *Optional ATM Products and Services for the Purchase and Fleet
Cards:* If offered, the Contractor may provide ATM access for the
purchase and fleet card program. If offered, the Contractor shall adhere
to the limits, timeframes and requirements specified in the Travel Card
portion (reference CB.11) of the statement of work for ATM access.

C.47.6 *Optional bank check products and services for the Fleet and
Travel Cards:* If offered, the Contractor may provide bank check
products and services for the fleet and travel card programs. If
offered, the Contractor shall adhere to the limits, timeframes and
requirements specified in the Purchase Card portion of the statement of
work for bank check products and services. The checks shall be
guaranteed by the Contractor against theft or loss, thus affording the
agency/organization protection against financial loss when using the
Contractor\'s product.

C.47.7 *Inter/Intra-Governmental Services:* If offered, the Contractor
may provide merchant bank services for inter/intra-governmental
transactions, payments and operations. Inter/intra-governmental
transactions shall adhere to the following requirements: (1) Funds will
not leave the Government (i.e., no transfer of Federal funds, however
momentary, into or outside of the Federal Government); (2) Fees may only
be priced on an agreed-upon tiered flat transaction price (i.e., the
higher the transaction volume, the lower the tiered flat transaction
price), substantially reduced or zero fee structure associated with
accomplishing the requirement (fees may not be transaction value based
(no discount or basis point fees) and will provide for the
authorization, processing and settlement of the inter/intra-governmental
card transactions; (3) transactions shall be identified as
inter/intra-governmental. Required transaction data will be transmitted
to the Government, either to the merchant agency or to Treasury's
Financial Management Service (FMS), to effect transaction accounting and
settlement between the purchasing and merchant agencies. The Contractor
shall address and include what operating rules are proposed for this
service for approval as multiple card issuers, potentially representing
more than one card association, may be offering this service.

The Contractor may propose a system that:

> a\) Provides sufficient functionality to support a wide range of
> inter/intra-governmental business activity as follows:
>
> 1\) Spontaneous transactions: One-time transfers of value for
> relatively small quantities of goods or services at a known price.
> These purchases may not involve the transfer of detail purchase and
> financial information prior to the transaction;
>
> 2\) Prenegotiated transactions: Non-scheduled transfers of value for
> goods or services under prenegotiated terms. These transactions may
> involve indefinite quantity and variable price terms and represent
> actions under signed agreements;
>
> 3\) Recurring transactions: Transfers of value for goods or services
> or to and from trust funds (or central accounts) which are made on a
> regular, scheduled basis. These transactions typically are made in
> large numbers and batch;
>
> 4\) Other transactions: Transfers not in exchange for goods and
> services but to support other legal and public policy purposes.
>
> b\) Provides sufficient information for audited financial systems and
> information needs of a variety of users. Transactions must be
> supported by proper backup documentation and provide information about
> business activity in a fully auditable manner. The information
> available must be at a level to support attestations about the
> management integrity of system operations (a crucial part of the
> accounting process involves the independent audit of agency
> activities). The system must support paying office needs (e.g.,
> documentation which positively matches an invoice to an appropriation
> account and includes attestations of available appropriations and a
> mechanism to receive invoices and reconcile them against goods and
> services received); collecting office needs (e.g., documentation that
> matches the payment to an invoice or other measure of service
> provided, billing systems that age receivables and a mechanism for
> billing); paying and collecting agency needs (information about
> completed and in-transit transactions to account for funds spent to
> measure program performance and to make resource allocation
> decisions); and needs of other consumers of information (e.g., central
> agencies, interagency councils, Congress and the public).
>
> c\) Support doing business in a distributed processing environment and
> support differing end-to-end processes. Roles, responsibilities,
> warranties and liabilities needed to do business must be well-defined
> in areas of purchase, authorization, settlement, dispute resolution
> and reporting;
>
> d\) Uses commercial technology whenever possible;
>
> e\) Manages change, monitors risk and be flexible. The system should
> include a structured process for change management that is based in
> agencies' system and information architectures and includes user
> feedback;
>
> f\) Be cost effective.
>
> g\) Provide merchant acquiring services. Each agency that accepts this
> card will need to be established as a merchant with the Contractor.
> The Contractor shall submit a merchant agreement for
> agency/organization review and negotiation and upon completion, will
> be executed by an authorized agency/organization official.
> Alternately, if the Contractor is not a merchant acquirer but would
> like to provide this service, the Contractor may work with the
> merchant acquirer to provide inter/intra-agency operations at an
> agreed-upon tiered flat transaction price (i.e., the higher the
> transaction volume, the lower the tiered flat transaction price),
> substantially reduced or zero fee structure associated with
> accomplishing the requirement. The Contractor shall provide each
> Government agency set up as a merchant point-of-sale terminals that
> captures and delivers, at a minimum, Level III data.

The Government may provide a standard settlement mechanism for effecting
transactions between agencies to meet the requirement that funds not
leave the Government for this service. Contractors offering this service
will be notified of such standard settlement mechanism before task
orders may be awarded for this service.

C.47.7.1 *[Reports]{.underline}:* The following reports will be
required:

**Agency Reports**

-   Daily Settlement Report. This report shall include data for each
    transaction issued against the agency's account. This report shall
    be transmitted electronically in a flat file which can be read in a
    commercially available database to be agreed to by the
    agency/organization and contractor. This report shall be issued
    daily to the agency for each merchant account. The Contractor shall
    provide access to transaction data and reports via an on-line
    system. The flat file will be downloaded once per day. The agency
    reference number, if required, will be input prior to transmittal of
    the sales draft. This report shall include the following fields:

1.  Merchant Account Number

2.  Agency Name

3.  Transaction Number (Acquirer Bank)

4.  Transaction Code

5.  Dollar Amount of Transaction

6.  Transaction Date

7.  Transaction Reference

8.  Agency Reference Number (assigned by agency)

9.  Authorization Code

10. Cumulative by merchant number

11. Number of Adjustments

12. Dollar Amount of Adjustment

-   Daily Chargeback Report. This report shall include data for each
    chargeback issued against the agency's account. This report shall be
    issued electronically. This report shall be issued to the agency
    upon the occurrence of each chargeback. This report shall include
    the following fields:

1.  Merchant Account Number

2.  Agency Name

3.  Transaction Number (Acquirer Bank)

4.  Transaction Code

5.  Dollar Amount of Transaction

6.  Transaction Date

7.  Transaction Reference

8.  Agency Reference Number (assigned by agency)

9.  Cumulative by merchant number

-   Monthly Agency Report to the agency contact for each merchant
    account. The Contractor shall provide access to transaction data and
    reports via an on-line system. The Contractor shall download this
    information in a flat file. The flat file will be downloaded once
    per month. This report shall contain at a minimum the dollar amount
    of agency wide activity.

1.  Merchant ID

2.  Agency Name

3.  Monthly Sales Total

4.  Number of Transactions

5.  Monthly Transaction Total

6.  Monthly Authorization Activity by Type

7.  Misc. Fees by category

8.  Total misc. fees

9.  Transaction fees

10. Cumulative total for all agency accounts

11. Number of account inquires

**GSA Contracting Office Reports**

-   Summary Report to the GSA Contracting Officer for intra-governmental
    transactions, government-wide. This report shall be issued
    electronically, in a commercially available data to be agreed upon
    by the GSA Contracting Officer and the Contractor. This report shall
    contain at a minimum, by agency:

1.  Cumulative Monthly Sales

2.  Cumulative Monthly Sales Total

3.  Cumulative Monthly Authorization Activity by Type

4.  Cumulative misc. fees

5.  Cumulative number of transactions

6.  Number of transactions

7.  Dollar Amount of transactions

8.  Cumulative Monthly Transaction Total

9.  Number of account inquires

C.47.8 *Telephone Card Access (for the Travel Card Only):* If offered,
the Contractor may include the agency/organization long distance carrier
access code and calling number on the back side of the travel card,
physically and electronically, as coordinated with the Government and
the Government's long distance carrier contractor(s). The travel card is
the preferred telephone access device. The travel card is not currently
intended to be the vehicle in which telephone billing or payments are
processed.

C.47.9 *Electronic Bill Payment:* If offered, the Contractor may provide
other non-EDI electronic bill payment products and services. This
includes paying merchants who traditionally don't accept card-based
payments on behalf of the Government such as utility companies.

C.47.10 *Hybrid Card:* If offered, the Contractor may provide hybrid
card products and services. The Government intends to take advantage of
the enhanced functionality provided through ICC technology. The
Government envisions card-based systems supported through a distributed
ICC card base that will perform a broad range of functions to support
the Government\'s business processes and needs. For the near term, the
Government envisions that hybrid cards, combining magnetic stripe and
ICC technologies, will be an enabling tool in re-engineering the current
business processes. The following are key goals for such services:

a\) The card systems must be built on an open system configuration,
consistent with commercial industry rules and standards;

b\) The card systems must be inter-operable for commercial and
Government access;

c\) The card systems must support multiple applications, both financial
and administrative;

d\) Where possible, the Government will use commercial card products and
infrastructure, particularly for electronic commerce, to deliver
services to share the systems development costs over a wider base.

To accomplish these goals in the migration from paper to electronic
processes, security is essential. Electronic systems must be able to
authenticate the user and other business partners so that only
authorized personnel may gain access to restricted information,
functions, and resources. Electronic systems must provide for the
confidentiality and integrity of information to ensure that the contents
of a message or transaction are not tampered with and that sensitive
data is properly protected. Electronic systems must also support the
property of non-repudiation to prevent any party from denying that a
transaction, message, or function occurred after it was, in fact,
performed. The Government is seeking integrated services to support
authentication, data integrity and confidentiality, and non-repudiation
for its business processes requiring enhanced security. To this end, the
Government anticipates that the card services offered through this
vehicle will support a secure operating environment for electronic
commerce, communications, and documents flow based on digital signatures
and a commercially functional public key infrastructure. To ensure a
uniform and consistent security infrastructure with the private sector,
the Government is seeking an extended identification (ID) authentication
function to support multiple applications based on the standard X.509
digital certificates and authentication framework as an operating model.

In addition, the Government is seeking solutions for secure networked
communications to support internal and external information exchange and
transactions and on-line access to distributed goods and services as
value-added services for the Government's Card Programs. The Government
anticipates that use of cards employing integrated circuit technology
(i.e., smart cards, hybrid cards) will provide the greatest support for
integrated solutions to control access to services and information and
provide for secure transactions and communications over the Internet and
other unsecured networks.

If offered, the Contractor may provide a hybrid card that can be
accepted domestically and internationally by merchant establishments and
financial institutions and assist the Government in streamlining the
Card Program(s). The hybrid card shall be an integral part of the
Government's Card Program(s). The Contractor shall have the ability to
store and manage data on the hybrid card as provided to the Contractor
by the agency/organization. The Government will specify application size
and parameters of the application data and provide such data in an
agreed-upon format to the Contractor.

C.47.10.1 *[Definitions:]{.underline}*

**Application:** A commercial use or purpose for using a device, e.g.,
an integrated circuit card used for transfers, inquiries, credits, etc.

**Biometrics:** Method of validating the user by electronically
measuring a unique characteristic such as fingerprint, voice print,
retina scan, or signature dynamics.

**Cardholder**: The person or entity with whom an account relationship
is established and to whom a card is issued.

**Card Initialization:** The process of transferring data to a card that
is common to all cards in a batch. Initialization can involve printing
on the surface of the card and writing to the chip. Basic application
data such as card logo, chip file structure, and data security keys are
added to the card during initialization.

**Card Issuance:** The process of moving a card from the point of
personalization to the cardholder.

**Card Personalization:** The process of writing data to the card that
is specific to the cardholder. A cardholder's name, account number, PIN
and authority levels are examples of data added to the card during
personalization.

**Chip:** A small square of thin, semiconductor material, such as
silicon, that has been chemically processed to have a specific set of
electrical characteristics such as circuits, storage, and/or logic
elements. Also known as an Integrated Circuit (IC).

**Contact:** An electrical connecting surface on an integrated circuit
card and/or interfacing device that permits a flow of energy current
between the two.

**Contactless Card:** An integrated circuit card that enables energy to
flow between the card and the interfacing device without the use of
contact. Instead, induction or high-frequency transmission techniques
are used through a radio-frequency (RF) interface.

**Digital Certificate:** A document digitally signed by a trusted third
party which serves to bind an individual to his/her public cryptographic
key. It is used as a means of verifying the ownership of the public key.

**Digital Signature:** A technique used to ensure the integrity of
electronic messages or transactions and to unambiguously identify the
individual who is responsible for its content. It serves as a means for
implementing non-repudiation (binding an individual to the contents of
the message). The digital signature is generated using an individual's
private cryptographic key and is validated using his/her public
cryptographic key.

**Digital Signature Certification:** An electronic proxy for a card,
issued by the contractor to a cardholder following approved
authentication policies of the government agency/organization, and
certifying that the enclosed public key is the true public key of the
identified cardholder. The Digital Signature Certificate is presented to
an on-line Internet merchant by the cardholder's desktop software in
making purchases, along with a message signed by the cardholder's
private key, and is used to authenticate the identity of the cardholder
to both the merchant and to the contractor for charge authorization.

**EMV Specifications:** Europay, Master Card and Visa joint project to
define global specifications for financial transactions using smart
cards.

**Encryption:** The use of cryptographic algorithm(s) to encode clear
text data (e.g., PINs) in order to protect the confidentiality of that
data.

**Hybrid Card:** A plastic card that has both magnetic stripe and
integrated chip capabilities. The magnetic stripe portion shall comply
with all American National Standards Institute (ANSI) and International
Standards Organization (ISO) standards.

**Integrated Circuit:** Electronic components designed to perform
processing and/or memory functions. Abbreviated as IC.

**Integrated Circuit Card (ICC):** A card into which one or more
integrated circuits are inserted. Includes both memory and smart cards.

**Manufacturer Key:** Security device to prevent access to IC card
functions for cards pending initialization.

**Microprocessor:** A microcomputer with all of its processing
facilities on a single chip. A microprocessor is a computer processor on
a chip including registers and possible cache memory. A microcomputer or
microcontroller also has data and program memory on the same chip.

**Off-Line:** Computer based data files and operations reside on the
ICC.

**Personalization:** The process of initializing a card with data that
ties it uniquely to a given cardholder and account.

**PIN:** Code the customer possesses for verification of identity when
using a card

**Private Key:** In asymmetric cryptography, the key which is held only
by the user, either in hardware or software authentication and
encryption.

**Public Key System:** Cryptographic method using pairs of cryptographic
keys, one of which is secret and one is public. If encipherment is done
using the public key, decipherment requires application of the
corresponding secret key and vice versa.

**Smart Card:** An integrated circuit card with a microprocessor, i.e.,
capable of calculation.

**User Identification:** A method of identifying the person using the
card to make a particular purchase (card presenter). This may take the
form of a signature, Personal Identification Number, or other auditable
method.

**Vendor Key:** Security device to prevent access to IC card data and
functions for cards pending issuance.

C.47.10.2 *[Hybrid Card]{.underline}:* The Contractor shall, at a
minimum, supply cards that comply with the card design requirements as
stated in C.23, Card Design and Embossing.

a\) Physical Characteristics of the Card: The Contractor shall provide a
hybrid card with both magnetic stripe and integrated circuit chip
capabilities. The card physical characteristics, magnetic stripe, and
magnetic stripe encoding of the card shall comply with American National
Standards Institute (ANSI) and International Standard Organization (ISO)
standard 7813 Identification Cards - Financial Transaction Cards. The
integrated circuit chip aspects of the card shall comply with ANSI/ISO
standard 7816 Identification Cards - Integrated Circuit Cards with
Contacts and with the EMV ICC Card Specifications for Payment Systems
and all standards incorporated in that specification. All cards shall
additionally comply with updates to these specifications and relevant
standards as they are adopted to conform to commercial operating
guidelines.

b\) Functions of the Hybrid Card: The size and capabilities of the
integrated circuit chip contained within the hybrid card will depend
upon the applications for which the card will be used. At a minimum, it
is expected that an integrated microprocessor and memory chip will be
required. Some applications may require more advanced technologies that
may be prevalent at the time of implementation such as emerging
combination chips with both contact and contactless read/write
capability.

There are four basic functional capabilities for the hybrid card that
will need to be performed to support the Government's integrated Card
Program(s):

1)  The ability to store information \-- the hybrid card will require
    the level of functionality to support the applications that need
    information necessary for the application stored on the card;

2)  The ability to manage data on the card \-- the hybrid card will
    require processing capabilities to enable the manipulation of data
    contents independently of processing capability at the point of
    interface or at a central host;

3)  The ability to authenticate the card and user \-- card functionality
    requires processing capability to determine if signal input matches
    authentication profile data on the card and functionality to provide
    different levels of authentication to access different parts of the
    chip; and,

4)  The ability to provide encryption and digital signature features \--
    the card will require functionality to support cryptographic
    applications.

The specific requirements for these functions will be determined by the
particular administrative or business process(es) identified to utilize
the card.

c\) Data Management: The hybrid card shall perform two basic access
functions in supporting the Government's Card Program(s). First, it is
an access key to facilitate secure access to physical and logical
functions. Second, it provides a portable database to facilitate access
to services, reporting and reconciliation for Government employees.
Thus, two sets of data shall be carried within the card. The first shall
be required data elements, when appropriate, to perform travel, small
purchase or fleet functions. Card personalization data may also be used
by agencies/organizations to perform related functions such as building
access, computer access and electronic commerce. The second set of data
shall be composed mainly of transaction files. Ultimately, these
transaction files will be used to automatically prepare reimbursement
requests, reconcile invoices, input fleet, travel or small purchase data
directly into agency/organization accounting systems and other such
functions.

d\) Card Data Management: As discussed above, all initialization and
personalization data shall be written to the card prior to issuance. All
transaction data shall be written to the card as the card is used.
Initialization and personalization data shall be permanently written to
the card although some data, such as agency/organization location or
phone numbers, may be updated. Transaction data shall be considered
volatile using a first-in first-out update methodology. The number of
transactions maintained on the card will be a function of the types of
transactions that the individual cardholder is entitled to perform and
the size of the memory on the chip. While general guidelines are
presented later in this section, agencies/organizations may request
alternate transaction storage requirements.

e\) Systems Data Management Support: All initialization and
personalization data shall be duplicated in the Contractor's central
card issuance information system. The Contractor shall also maintain a
detailed record of transactions performed by each cardholder for a
period of at least one (1) year with capability to retrieve transaction
information off-line for at least three (3) years after the expiration
of the master contract. Agencies/organizations may elect to maintain a
duplicate record of cardholder files. This duplicate will be created by
the agency/organization by periodically reading the transaction records
on the card and updating a local database. This record of cardholder
files will allow the agency/organization or cardholder to recreate the
transaction record locally if the card is lost, stolen or in the event
the chip cannot be read. Maintenance of local cardholder files shall not
relieve the Contractor of the responsibility to maintain cardholder and
transaction records at a central location.

The Contractor may offer systems data management support to
agencies/organizations so that the fleet, travel and purchase card
transaction files, data reporting and financial reconciliation and
accounting processes are fully integrated into the
agency's/organization's financial and information processing systems.
Such data management support may represent design and development
activities for network interfaces to systems, interoperability with
other governmental transaction data and systems and other systems for
integrated systems data reporting, formatting and outputs.

f\) Card Transaction Recording: Card file structures shall be
established to allow for recording of separate transaction files for
different applications. For example, a transaction file shall be
maintained for small purchase transactions performed by the cardholder
separate from a transaction file maintained for stored value
transactions. The transaction file shall maintain all types of
transactions such as purchases, credits, voids, as well as invalid PIN
attempts or other error messages. \[NOTE: Respondents are invited to
discuss alternative transaction storage approaches such as establishment
of a common transaction storage file in which each transaction record
would include a transaction type code. Overwriting of "old" transactions
could be performed on a first-in first-out basis or according to a
prescribed protocol that "saves" more critical transaction data first.
Any such protocol must be approved by the requesting agency/organization
and will not relieve the issuer from maintaining separate transaction
records.\]

g\) Key Management: The card initialization and personalization process
will include a key management system that will allow the secure
generation and storage of encryption keys. The keys may be used at a
card center, or could be transmitted to a remote (agency/organization)
personalization center. Provisions should be made for the management of
a public key system (electronic commerce) and a private key system
(stored value).

h\) Cardholder PIN Authentication: Each card will initially contain a
four to six digit PIN provided by the card issuer to the cardholder
under separate cover. The cardholder will be required to use the
issuer-assigned PIN the first time a card is used. The first time the
card is used, the cardholder may select a new PIN, or continue to use
the issuer assigned PIN. The cardholder may elect to use an alpha or
numeric PIN.

Agencies/organizations may elect to request the capability to use
multiple PINs. For example, one PIN could be used to perform travel
functions in a commercial environment while a separate PIN would be
required to perform electronic commerce functions.
Agencies/organizations may require that one PIN be used to gain access
to electronic commerce functions within an agency/organization system
while a separate may be required to initiate a purchase or payment.
Payments or purchases over a certain amount may require input of a
separate PIN as well.

Input of three consecutive invalid PINs shall automatically and
immediately lock the card and prevent any further usage.
Agencies/organizations may elect to select an alternative number of PIN
attempts that results in a locked card. Agencies/organizations may elect
to require alternative PIN attempt counters for each PIN. For example,
three attempts may be permitted for stored value transactions while
fewer attempts may be allowed for electronic commerce purchases.

i\) Cardholder Biometrics Authentication: Agencies/organizations may
elect to have the Contractor house a biometrics template for additional
security on the card. Actual specifications for biometrics will be
developed separately by the agency/organization. The biometric
applications will then be supplied to the Contractor by the requesting
agency/organization to house on the card.

j\) Digital Signatures: The card will have the capability of creating a
digital signature using a public key algorithm. The digital signature
will incorporate several transaction variables (e.g., date, time,
amount, transaction number) into the digital signature calculation.
Contractors offering this service shall provide digital certificates
that incorporate a X.509 structure as a means of binding a user's
identity to their public key. The digital signatures generated by the
card's ICC will meet the following requirements:

> 1\. Digital signatures must be unforgeable. The signature must
> uniquely be the result of authorized use of the private key which is
> securely maintained on the hybrid card's ICC.
>
> 2\. Digital signatures must be authentic. The signature must reflect
> the fact that the authorized cardholder is the only individual that
> can generate his/her digital signature.
>
> 3\. Digital signatures must not be reusable. The digital signature
> must be uniquely associated with the contents of one and only one
> message, transaction or other type of digital file and it must
> incorporate a time/date stamp.
>
> 4\. Digital signatures must provide the ability to detect any
> alteration of a message, transaction, or other type of digital file.
>
> 5\. Digital signatures cannot be repudiated. After digitally signing a
> message, transaction, or other type of digital file, the procedures
> and policies associated with the use of the private key must ensure
> that the signer cannot disavow his/her intent to be bound to or to be
> responsible for the signed message, transaction or other type of
> digital file.

The X.509 certificate contains the distinguished name of the user, the
user's public key, and other user attributes in a standard data format
and structure, and is digitally signed by an authorized Certification
authority. The Contractor(s) offering this service shall comply with
X.509 version 3, and shall provide for compliance with future versions
as issued.

The distribution of public keys will be performed by an authorized
Certification Authority through the generation and distribution of
public key certificates. The Contractor may also offer services as a
trusted third-party to the Government's electronic business processes
requiring authentication through digital signatures. As an authorized
Certification Authority for the Federal Government, the Contractor shall
be responsible for the secure distribution of public keys through the
creation, distribution and management of public key or digital
certificates. The Certification Authority shall generate and digitally
sign certificates to bind a public key value to the identity of the
specific user holding the corresponding private key, using the user's
distinguished name and public key. The Certification Authority shall be
responsible for the following functions in support of the government's
card services programs:

> 1\. Certification and digital signing of public keys and certificates;
>
> 2\. Maintenance of certificates;
>
> 3\. Distribution of certificates to public directories;
>
> 4\. Revocation of certificates and issuance and maintenance of
> associated revocation lists.

The hybrid card shall have the capability to maintain public key
certificates consistent with the X.509 version 3 standard structure. To
support applications requiring higher levels of security and functions
requiring the transport of sensitive information over unsecured
networks, the card must have the internal capability to:

> 1\. Authenticate the cardholder as the legitimate card user;
>
> 2\. Store the user's cryptographic key pairs (i.e., public and private
> keys) and public key certificate; and
>
> 3\. Perform the digital signature and verification functions.

k\) Card Replacement and Loss Management: The Contractor shall provide a
toll free telephone number to be called if the card is lost or stolen.
Any card reported lost or stolen shall be placed on a "hot card" list.
All on-line transactions shall be blocked for any card on this list. Any
on-line transaction initiated from a chip capable terminal by a card on
the hot card list shall result in a message sent to the terminal to
immediately "lock" the card. \[NOTE: Vendors are invited to offer
methodologies to ensure security and block transactions performed by
cards on the hot card file. Some alternatives may include requiring
periodic on-line inquiries based upon a pre-determined number of days of
activity, downloading of "hot card" files to local terminals, and
managing spending limits in which purchases or payments over a certain
threshold require on-line authorization or in which the dollar threshold
decreases based upon velocity parameters.

l\) Hybrid Card System Requirements: The basic system must provide the
capability to perform the following functions:

> 1\. Card Initialization: Card initialization is the process of
> transferring data to a card that is common to all cards in a batch.
> Initialization can involve printing on the surface of the card and
> writing to the chip. Basic application data such as card logo, chip
> file structure, and data security keys are added to the card during
> initialization.

The Contractor must provide for the collection of the data necessary to
initialize all cards at a centralized card center. All cards will be
initialized prior to issuance. All cards provided to the Contractor by
the card manufacturer shall be "locked" using a manufacturer key. The
manufacturer key shall be provided to the Contractor under separate
cover. The manufacturer key shall be required to unlock cards prior to
initialization. Initialization should include functions such as printing
of agency/organization specific information such as Agency/Organization
name or logo, establishing common chip file structures, and, writing
common keys to the secure area of the chip.

> 2\. Card Personalization: Card personalization is the process of
> writing data to the card that is specific to the cardholder. A
> cardholder's name, account number, PIN and authority levels are
> examples of data added to the card during personalization. Card
> issuance is the process of moving a card from the point of
> personalization to the cardholder.

Card personalization and issuance may be provided by the vendor or by
the local agency/organization at their discretion. Card personalization
shall include functions such as printing of cardholder name and account
number, placement of a photographic image of the cardholder on the face
of the card, and "loading" of personal data on the chip such as
cardholder name and account number and other information as described in
the following sections. Cards shall have the capability to store and
utilize multiple PINs to access multiple applications.\
\
If an agency/organization elects to have cards personalized by the
vendor, all personalization data will be provided to the vendor in a
standard agreed-upon electronic format. Cards maintained by the vendor
prior to issuance shall be held in secure areas and controlled as
valuable documents with adequate inventory controls.\
\
Agencies/organizations that elect to perform "in-house" personalization
shall be provided batches of cards under secure control. All cards shall
be locked using a vendor key. The vendor key shall be specific to each
batch and will be provided to the issuing agency/organization under
separate cover. Agencies/organizations that perform in-house
personalization shall provide the personalization records indicating the
serial number of each card issued, to whom it was issued, and a copy of
all personalization data to the vendor in electronic format at the close
of each issuance cycle (presumed daily). The vendor shall have the
capability to promptly update their cardholder database to reflect this
information. Vendors should specify the preferred method and frequency
of data transmission

m\) Possible Applications:

> 1\. Basic Identification: This service will enable the cardholder to
> be identified by the exterior of the card (i.e., a photograph) or
> through information stored in the ICC or magnetic stripe. The
> information in the card may be used for multiple purposes such as to
> gain access to a building or log on to a PC. Data on the card may
> include, but not be limited to:
>
> Name, work address and telephone number;\
> Agency/organization name and address;\
> Accounting office name and telephone number;\
> Account number;\
> Government ID number;\
> Social security number; and\
> Security access code (e.g., PIN)
>
> 2\. Extended Identification: This service will provide additional
> levels of identification and authentication necessary to perform
> extended services (e.g., higher levels of security and user
> authentication). The information in the card may be used for multiple
> purposes to support applications needing greater security or
> information support. Data on the card may include, but not be limited
> to:
>
> Name, work address and telephone number;
>
> Agency/organization name and address;
>
> Accounting office name and telephone number;
>
> Account number;
>
> Government identification number;
>
> Social security number;
>
> Security access code;
>
> Biometric template (not to exceed 500 bytes); and
>
> X509 Certificate and Certificate Structure.
>
> 3\. Other Applications: Agencies/organizations may choose to provide
> other standard data to support the Federal employee cardholder
> identification functions or to support other information and
> functional needs. Such additional data contained in the chip may
> include, but is not limited to:

-   Access authentication data to provide for varying levels of access
    and authentication to different applications supported by the chip;
    and

-   Agency/organization-specific data.

C.47.11 *Electronic Purchasing:* This service will allow the cardholder
to securely purchase goods or services electronically over the Internet,
or through a private network. The system functionality should provide
for the following features:

a\) Enhanced security, transaction integrity, transaction
confidentiality, user and seller authentication, and non-repudiation of
the transaction through the use of the users digital signature and
public key certificate-based authentication;

b\) Enhanced accountability through individualized authorization
controls;

c\) Improved efficiency by allowing authorized purchasing agents or
other authorized personnel to access electronic purchasing functions
from alternate sites while maintaining full security and functionality;
and

d\) Improved reconciliation by providing the capability to record
executed transactions to the card maintained by the cardholder.

C.47.12 *Photo ID:* This service will enable the cardholder to be
identified by the exterior of the card (i.e. a photograph).

C.47.13 *Commercially Offered Convenience Services:* If offered, the
Contractor may provide its commercial convenience services such as
extended warranty programs, ATM/travelers check vending machines at the
work-site, etc.

C.47.14 *Net Billing (Travel and Purchase Card Programs Only):* If
offered, the Contractor may provide net billing to
agencies/organizations. Net billing is ensuring merchant discounts or
rebates offered are deducted at the point of sale and guaranteeing such
discount arrangements. For example, an airline ticket costs \$100. The
travel agency rebates \$4.00 of the cost of that airline ticket to the
agency/organization based on existing agreements. The Contractor would
only bill the agency/organization \$96 for that airline ticket. The
Contractor shall ensure that discount information is identified and
passed to the agency/organization at the time of invoice. The Government
would be responsible for identifying to the Contractor any negotiated
discount arrangements and terms.

C.47.15 *Card Sleeves:* If offered, the Contractor may offer card
sleeves to protect cards.

C.47.16 *Activation/Deactivation on Demand:* These functions are
deactivated cards and may be in an individual's name or in the
agency's/organization's name. If offered, the Contractor may
electronically activate/deactivate the cards (not necessarily ICC cards)
on demand by the agency/organization. For example, in keeping with the
vision of one multi-function card, ABC Agency orders a hybrid fleet,
travel or purchase card and houses an identification application on the
card. This identification application is developed under a separate
contract, and simply housed on the fleet, travel or purchase card. As
fleet, travel or purchase functions are needed, ABC Agency wants the
ability to activate these functions on demand. As the functions are no
longer required, ABC Agency then wants the ability to deactivate fleet,
travel and purchase functions on demand.

C.47.17 *Emerging technology:* As available to the commercial market,
the Contractor may provide emerging technology that facilitates or
enhances the Card Program(s).

# *SECTION CA - REQUIREMENTS SPECIFIC TO THE FLEET CARD PROGRAM*

## CA.1 BACKGROUND FOR FLEET CARD SERVICES

*Program History:* The Defense Fuel Supply Center (DFSC) is responsible
for purchasing fuel for the Federal Government. Prior to 1979, the DFSC
contracts allowed each agency/organization to issue their own cards to
be used as payment mechanisms. This caused general confusion, with some
agencies/organizations duplicating each others account numbers, and no
central database for billing office address information.

In 1979, the General Services Administration (GSA) began procuring
plastic card services which included inventory management. Each
agency/organization was assigned specific account ranges within the
overall account numbering scheme assigned by the American Petroleum
Institute to the Federal Government. The card contractor maintained a
list of billing office addresses for each account (obtained when the
cards were ordered). This information was distributed to all fuel
vendors under the DFSC contracts. The fuel vendors then invoiced each
account individually. The DFSC contracted with the fuel vendors to
ensure taxes were deducted and that the GSA card was accepted as a
payment mechanism. GSA contracted for the issuance and distribution of
the cards. Each agency/organization was responsible for payment from
each fuel vendor at which the card was used. Both the current DFSC fuel
contract program and the GSA plastic card program expired in May 1997.

In October of 1996, GSA issued a solicitation for a commercial fleet
card service. Detailed fuel data from the fuel vendors was required;
however, only pricing data was required for maintenance purchases. That
contract was awarded on \_\_\_\_\_; however, it is unlikely that
consolidated invoice data will be available in time to include the
information in this solicitation.

**NOTE TO INTERAGENCY FLEET MANAGEMENT SYSTEM (IFMS) USERS: FOR THOSE
AGENCIES/ORGANIZATIONS THAT USE THE IFMS, GSA WILL CONTINUE TO PROVIDE
THE SERVICES AS IT CURRENTLY DOES. FOR THOSE AGENCIES/ORGANIZATIONS THAT
DO NOT UTILIZE THE IFMS, THEY WILL BE RESPONSIBLE FOR IMPLEMENTING,
CONTROLLING AND PAYING FOR THEIR OWN FUEL/MAINTENANCE PRODUCTS AND
SERVICES UNDER THIS MASTER CONTRACT.**

***DEFINITIONS***

## CA.2 DEFINITIONS:

**Billing Date:** The billing date is the date the invoice is received
by the agency/organization designated billing office in accordance with
the Prompt Payment Act.

**Cardholder:** Any individual, or agency/organization designated by the
agency/organization to be issued a card. Most cards will be issued to a
piece or group of motor equipment rather than to a person. More than one
person may be authorized to use a card assigned to equipment. The card
may bear the equipment identification (e.g., license plate),
individual\'s name, or agency's/organization's name and can be used to
pay for official purchases in compliance with the Federal Acquisition
Regulation and agency/organization internal procedures.

**Card Account Number:** An external means of identifying a specific
customer unit or specific card. This is embossed/encoded/encrypted on
the card itself.

**Card Identifier:** Unique identification for each piece of plastic
(card) issued to an account (Customer Unit).

**Customer:** (1) A user of this card; or (2) Any representative of the
Customer Unit, Service, or Department/Agency to which the card has been
issued.

**Customer Account:** A Contractor's internal means of identifying a
specific customer unit. This identification may be separate from the
Card Account Number, may appear on invoices or reports, and may be
required by the Contractor to properly post payments received.

**Customer Unit:** The smallest unit of reporting and invoicing. Each
Customer Unit is a distinct Account. More than one card may be assigned
to each account.

**Official Purchase:** Supplies or services procured at the direction of
an agency/organization under official purchase authorization.

> **CORE REQUIREMENTS - TIER 1**

***SUMMARY OF PROGRAM REQUIREMENTS***

## CA.3 FLEET CARD PROGRAM REQUIREMENTS

In addition to the requirements specified in C.7, Card Program(s)
Requirements, the Contractor shall provide a program that provides for:

-   Acquisition of fuel and maintenance/repair in an economical and
    effective manner;

-   Cards assigned to an individual piece or group of equipment; and

-   Cards assigned to an individual person or Customer Unit.

***MERCHANT ACCEPTANCE***

## CA.4 MERCHANT ACCEPTANCE FOR THE FLEET CARD PROGRAM

In addition to the requirements specified in C.8, Merchant Acceptance,
the Contractor shall provide a product which is accepted by fuel
merchants (including vehicle, marine and aviation) and by automotive
service, parts, and repair merchants.

CA.4.1 *Merchant Discounts:* Any merchant product or service discount
offered to the Contractor's non-Federal customers shall be passed on to
the Federal Government. In addition, the Government may independently
seek discounts directly from merchants. The Contractor shall have a
mechanism which enables merchants to identify which
agencies/organizations are eligible for the discounts. This may
necessitate separate account ranges for service/bureaus and
agencies/organizations/departments.

In addition to the point-of-sale discount identified in C.8, Merchant
Acceptance, another type of discount falls into this category:

-   Discounts offered by the card contractor to their customers. These
    are discounts the card company has negotiated with the merchant
    based on guaranteed or implied business volume. For example, 1% off
    all fuel purchases or 10% off glass (parts).

***CARD DESIGN***

## CA.5 CARD DESIGN AND EMBOSSING FOR THE FLEET CARD PROGRAM

The requirements stated in this section are in addition to the
requirements specified in C.23, Card Design and Embossing.

CA.5.1 *Face Side of Fleet Cards:* The Contractor shall be able to
emboss each card with the following:

a)  Account Number/Card Number (OCR[^73])

b)  Customer Agency/Organization Identification (alpha/numeric)

c)  Equipment Identification (alpha/numeric). This should allow
    [easy]{.underline} distinction between multiple cards issued to the
    same Customer Unit. (See C.34.5, Master File and CA.9.1.1)

d)  Expiration Date

In addition, the following information is recommended to be on the card:

-   Authorized Product Type

***TRAINING***

## CA.6 TRAINING REQUIREMENTS FOR THE FLEET CARD PROGRAM

In addition to the requirements stated in C.25, Training Requirements,
the Contractor shall develop and distribute the following training
materials:

CA.6.1 *Contractor's Merchant Network Guide:* The Contractor shall
provide a list of authorized merchants that will accept the card. At the
agency's discretion, this list shall be made electronically available
through the Internet or the agency's/organization's Intranet. This list
shall be updated and distributed to all Customer Units, A/OPCs and the
GSA Contracting Officer on a regular basis. Copies for each valid card
are required. Updates may take the form of a regular newsletter, be part
of the monthly reports, or any other form used by the Contractor to
update their commercial customers.

Each individual station need not be listed separately if all stations of
that brand in a geographic area accept the card. The list need only
state the brand and the geographic area in which the card is accepted.

Any discounts offered by the merchants should be noted in the Merchant
Network Guide. If the discount is taken at the point of sale (not passed
through on the invoice), this should also be noted, so customers can
ensure the appropriate discount is applied.

The Contractor shall distribute a copy of the Contractor's Merchant
Network Guide to each participating A/OPC within **ten (10) calendar
days** of the Contractor\'s receipt of a task order issued in accordance
with the terms and conditions of this contract. A copy of this guide
shall also be provided to each customer unit in conjunction with the
issuance of their card. Additional copies shall be provided to the A/OPC
and/or the GSA Contracting Officer upon request.

CA.6.2 *Card Use Instructions:* The Contractor shall provide
instructions for the use of each card issued. These instructions shall
cover information such as: use of card activated terminals on the fuel
pump, use of numeric keypads at the cash register, entering required
data, and description of receipts the card user should receive. These
instructions may be included as part of the cardholder guide or
contractor's merchant network guide and shall be distributed to each
participating A/OPC within **ten (10) calendar days** of the
Contractor\'s receipt of a task order issued in accordance with the
terms and conditions of this contract. A copy of this guide shall also
be provided to each customer unit in conjunction with the issuance of
their card. Additional copies shall be provided to the A/OPC and/or GSA
Contracting Officer upon request.

***AUTHORIZATION CONTROLS***

## CA.7 AUTHORIZATION CONTROLS FOR THE FLEET CARD PROGRAM

In addition to the requirements of C.30, Authorization Controls, the
Contractor shall have a method of limiting card use to items covered by
this contract even if the merchant sells other items. (For example, at a
department store with an automotive center, the Contractor should not
allow clothing or other items sold by the store to be purchased on this
card.) This can be done through the authorization process, through
merchant training, through exception reporting, combinations of these
three, or any other means utilized by the Contractor for their other
non-Federal customers.

For charges made at merchants not on the Contractor's merchant network,
the Contractor shall provide the merchant with the appropriate
designated Customer Unit billing office address so the merchant can
invoice the Government directly. This service shall be provided at no
cost to the merchant.

***TAX EXEMPTION***

## CA.8 TAX EXEMPT STATUS FOR THE FLEET CARD PROGRAM

In addition to the requirements in C.32, Tax Exempt Status, the Fleet
Card Program requires the identification of all taxes\--exempted
(invoiced net of taxes) or non-exempt (invoiced gross of taxes). This
includes, at a minimum, Federal Excise Tax (FET) on fuel, state motor
fuel tax, and state sales tax for fuel or non-fuel purchases. The
Contractor may provide additional tax details (e.g., local taxes, FET on
non-fuel items). The Contractor shall maintain accurate tax information.

Taxes must be deducted prior to invoicing when applicable. Regardless of
whether the Government is invoiced net taxes, all taxes shall be
itemized on the invoice (exempt and non-exempt).

***PROGRAM AND TRANSACTION DATA***

## CA.9 PROGRAM AND TRANSACTION DATA FOR THE FLEET CARD PROGRAM

CA.9.1 *Master File for the Fleet Card Program:* In addition to the
requirements specified in C.34.5, Master File, the Contractor shall have
the ability to record the following information:

CA.9.1.1 *[Card Specific Information]{.underline}:* In addition to the
requirements specified in C.34.5.1, Card Specific Information, the
Contractor shall also maintain the following information:

a)  Customer identification (to be embossed on card if requested)

b)  Equipment type \-- vehicle type if requested

c)  Equipment identification \-- (e.g., license number, tail number,
    name)[^74]

d)  Equipment fuel type (e.g., gasoline, CNG, ethanol)

CA.9.1.2 *Customer Unit Information (Card Assignment):* The Contractor
shall also maintain a master file for each account that includes the
following information:

a)  Customer Account (Contractor\'s internal accounting control method
    for identifying the Customer Unit. May or may not be the same as the
    Card Account Number);

b)  Federal Excise Tax (FET) Exempt Status (Necessary to determine if
    Federal Excise Tax should be deducted from the Customer Unit\'s
    invoice or merely identified. The Contractor may devise any method
    they choose to perform this function);

c)  Shipping Address (the Contractor shall maintain a record of the
    address to which each card [was]{.underline} shipped as well as a
    contact name and phone number); and

d)  Authorized Order Placement (the Contractor shall maintain a record
    of the office or persons authorized to place further card orders
    against the task order or make changes to card information as well
    as a contact name and phone number).

CA.9.2 *Fleet Card Program Transaction Data Elements:* In addition to
the requirements of C.34.6, Transaction Data and C.34.6.1, Transaction
Data Elements, the following fleet industry information must be
available for each purchase transaction in addition to the card
identification (reference C.34.5, Master File and CA.9.1, Master File
for Fleet Card Program) and tax exemption information (reference C.32,
Tax Exempt Status and CA.8, Tax Exempt Status for the Fleet Card
Program) necessary for invoices and reports.

a)  Time of purchase;

b)  User identification (identification of person using the card (card
    presenter));

c)  Location name or number (individual station/facility or store where
    purchase took place);

d)  Location address (address of individual station/facility or store
    including city, state and zip code);

e)  Type of purchase (fuel, non-fuel, both);

f)  Type of fuel (gasoline, diesel, gasohol, CNG, E85, M85, etc.);

g)  Grade of fuel (for gasoline - regular, mid-grade, premium);

h)  Type of unit (gallon, liter (foreign purchases only), gasoline
    gallon equivalent, alternative fuel);

i)  Units of fuel purchased;

j)  Price per fuel unit (carried out to same decimal places as pump
    price);

k)  Total fuel price (gross\--price per unit multiplied by number of
    units and carried out to two decimal places);

l)  Federal excise tax total;

m)  State motor fuel tax total;

n)  State sales tax total for fuel;

o)  Local motor fuel tax total;

p)  Local sales tax total for fuel;

q)  Total net fuel price (gross price minus applicable taxes and
    discounts);

r)  Mileage/odometer reading, where available;

s)  Non-fuel product type (maintenance, TBA, oil, car wash, repair,
    miscellaneous);

t)  Non-fuel product codes (e.g., repair codes), where available;

u)  Non-fuel price gross;

v)  State sales tax total for non-fuel item;

w)  Local sales tax total for non-fuel item;

x)  Net non-fuel price (non-fuel gross minus applicable taxes and
    discounts).

***ACCOUNTS***

## CA.10 FLEET CARD PROGRAM ACCOUNTS

In addition to the requirements specified in C.35, Centrally Billed Card
Program Accounts, the Contractor shall also provide the following:

CA.10.1 *Invoices for the Fleet Card Program:* In addition to the
requirements specified in C.35.7.3, Invoices and C.34.6, Transaction
Data, C.34.6.1, Transaction Data Elements, and CA.9.2, Transaction Data
Elements for the Fleet Card Program, the itemized invoice shall also
contain the Government purchase authorization. This is the user
identification (signature or PIN) for each transaction included for each
transaction unless otherwise requested by the agency/organization.
Customers may request this information on a separate report or may waive
this requirement if an alternate certification method is used (e.g.,
certification of the Statement of Account).

CA.10.2 *Statement of Account:* The Statement of Account shall be
submitted to the Designated Billing Office on the same cycle as the
invoice unless otherwise requested by the using agency/organization.
Information on the Statement of Account will be the same as on the
invoice except for the following additional data items:

a)  Merchant Type (based on contractor\'s own designation or SIC);

b)  Merchant Name (national, regional, or local [corporate]{.underline}
    name);

c)  Merchant Location or Number (individual station or shop); and

d)  Identification of purchases outside of normal parameters.

***AGENCY REPORTING REQUIREMENTS***

## CA.11 FLEET CARD PROGRAM REPORTING REQUIREMENTS

In addition to the requirements stated in C.38, Agency Reporting
Requirements, the Contractor shall also provide the data listed in this
section.

CA.11.1 *Account Activity Report for the Fleet Card Program:* Data
elements required for the reporting period are:

a)  Total Transactions;

b)  Total Units for the Reporting Period for each Fuel Type by Unit
    Type;

c)  Total Taxes for each state by tax category;

d)  Total Gross Fuel Charges for each Fuel Type;

e)  Total Gross Non-Fuel Charges for Non-Fuel Category;

f)  Total Net Fuel Charges for each Fuel Type;

g)  Total Net Non-Fuel Charges for Non-Fuel Category;

h)  Grand Total Gross Fuel Charges;

i)  Grand Total Gross Non-Fuel Charges;

j)  Grand Total Taxes Deducted;

k)  Grand Total Net Fuel Charges; and

l)  Grand Total Net Non-Fuel Charges.

CA.11.2 *Statistical Summary Report for the Fleet Card Program:* Data
elements required for the reporting period are:

a)  Agency/Organization;

b)  Customer Account;

c)  Task Order Number;

d)  Fuel Sales (Purchases made using card);

e)  Non-Fuel Sales (Purchases made using card);

f)  Fuel Transactions;

g)  Non-Fuel Transactions;

h)  Miscellaneous Charges (line item description)[^75];

i)  Current Active Cardholders;

j)  New Cards Issued;

k)  Replacement Cards Issued;

l)  Cards Removed from Inventory;

m)  Cards Reported Lost;

n)  Cards Reported Stolen;

o)  Total Customer Units (Accounts); and

p)  Total New Customer Units.

**END OF REQUIREMENTS SPECIFIC TO THE FLEET CARD PROGRAM**

# *SECTION CB - REQUIREMENTS SPECIFIC TO THE TRAVEL CARD PROGRAM*

## CB.1 BACKGROUND FOR TRAVEL CARD SERVICES

*Regulatory:* Under Federal Regulations, agencies/organizations may pay
for Government travel with Government Transportation Requests (GTR\'s),
charge instruments under contract to the Government and, in rare
instances, cash.

*General:* Individually billed account charge cards are used to pay for
official travel and other official travel-related expenses. The
Government only reimburses employees for authorized and allowable
expenses. Any amounts charged in excess of the allowable reimbursement
are paid to the contractor out of the employee\'s personal funds.

Centrally billed accounts are established by some agencies/organizations
to pay for official travel charges and for other official travel-related
expenses under special circumstances (e.g., conferences). Normally
charge cards are not issued in conjunction with centrally billed
accounts, however, from time to time, cards may be issued against a
centrally billed account.

The majority of Federal agencies and their employees, including
uniformed members of the armed services, normally purchase common
carrier transportation tickets for official travel through third-party
arrangements, with Travel Management Centers (TMC\'s) and Commercial
Travel Offices (CTO\'s) under Government contracts.

*Program History:* Since 1983, the General Services Administration (GSA)
has contracted for a Travel and Transportation Payment and Expense
Control System for official travel expenses. The system consists of
individually billed employee accounts with and without automated teller
machine (ATM) access, centrally billed accounts (CBA) and travelers
checks for use in connection with official Government travel and
travel-related expenses on a domestic and international basis. Prior to
the inception of this system, non-commercial payment practices were
utilized by agencies/organizations who implemented their own separate
travel programs. Most agencies/organizations used GTR's which were a
cumbersome technique and required significant control mechanisms. This
approach led to excessive costs and inconsistencies in implementation
and management of the travel programs. Furthermore, there was no payment
mechanism, other than the GTR, in place for airlines to ensure
eligibility for negotiated airfares.

To illustrate the growth of this program in terms of sales,
participating agencies/organizations, and cardholders, see Exhibit 7.

***DEFINITIONS***

## CB.2 DEFINITIONS:

**Billing Cycle Date (Applicable to Individually Billed Accounts
only):** For individually billed accounts, the closing date is the close
of the billing cycle date assigned to the account and indicated on the
cardholder statement of account. Also referred to as the billing cycle
date.

**Cardholder:** Any Federal employee designated by the
agency/organization to be issued a card. The card bears the employee\'s
name and can be used by the employee to pay for official travel and
travel-related expenses in compliance with the applicable regulations.

**Cardholder Agreement:** A written agreement between the Contractor and
a Federal employee stating both the employee\'s and Contractor\'s
responsibilities.

**Cardholder Application:** An application, designed by the Contractor
and used by Federal employees, to apply for individually billed
accounts.

**City Pair Program:** GSA's procurement program for air passenger
transportation services.

**City Pair Program Identifier:** A code that identifies an authorized
user of GSA's City-Pair Program.

**Closing Date (Applicable to Individually Billed Accounts only):** For
individually billed accounts, the closing date is the close of the
billing cycle date assigned to the account and indicated on the
cardholder statement of account. Also referred to as the billing cycle
date.

**Commercial Travel Office (CTO):** A Department of Defense (DOD) travel
arranger. This office provides a full range of travel services for the
DOD traveler. The CTO may be staffed with DOD personnel or may be a
commercial travel agency.

**Government Travel Regulation:** Rules governing the travel and
relocation allowances and entitlement of Federal employees performing
official travel or relocating for the Government. For Federal civilian
employees, see the Federal Travel Regulation (FTR) (41 CFR Chapters
301-304). For members of the Uniformed Services, see volume 1 of the
Joint Federal Travel Regulations (JFTR). The FTR and the JFTR are
available from the Superintendent of Documents, Government Printing
Office, Washington, DC 20402. For members of the Foreign Service of the
United States, see Chapter 100 of Volume 6 of the Foreign Affairs Manual
(6 FAM 100). 6 FAM 100 is available from the Department of State,
Publishing Services, Washington, DC 20520-0854.

**Individually Billed Account:** A Contractor issued card used by
travelers of a participating agency/organization to pay for passenger
transportation services, subsistence expenses, and other travel expenses
incurred in connection with official travel.

**Leg-by-Leg Itinerary:** Each segment of the trip shown separately on
the air/rail carrier\'s ticket.

**Official Travel:** Travel performed at the direction of a Federal
agency under an official travel authorization.

**Split Disbursement:** Purchases paid directly by the Government and
generally include large ticket items such as common carrier, hotel and
rental car charges. Part of the payment goes to the Contractor and the
other part goes to the employee. Payment is generally made using the
Social Security Number as the unique identifier.

**Travel Management Center (TMC):** A commercial travel firm authorized
by or under contract to civilian agencies to provide reservations,
ticketing and related travel management services for official travelers.

**Travelers Check:** A Contractor issued check, issued for a preset
amount, that may be cashed by countersigning in the presence of a payee
and accepted domestically and internationally by financial and
commercial firms. The checks shall be guaranteed by the Contractor
against theft or loss, thus affording agency/organization purchasers of
the check's protection against financial loss when using the
Contractor\'s product.

> **CORE REQUIREMENTS - TIER 1**

***SUMMARY OF PROGRAM REQUIREMENTS***

## CB.3 TRAVEL CARD PROGRAM REQUIREMENTS

In addition to the requirements stated in C.7, Card Program(s)
Requirements, the Contractor shall provide a program that provides for:

-   Individually billed accounts;

-   Automated teller machine access (ATM); and

-   Travelers checks.

***MERCHANT ACCEPTANCE***

## CB.4 MERCHANT ACCEPTANCE FOR THE TRAVEL CARD PROGRAM

In addition to the requirements specified in C.8, Merchant Acceptance,
the Contractor shall provide a product with widespread domestic and
international merchant acceptance by:

-   Domestic (US flag) passenger common carriers;

-   International/foreign passenger common carriers;

-   Airports;

-   Bus services and stations;

-   Train services and stations;

-   Taxi services;

-   Car rental agencies;

-   Hotel and lodging establishments (plus reservation, confirmations
    and payment);

-   DoD installations services (BOQ's, exchanges and clubs)

-   Restaurants;

-   Gas stations; and

-   ATM networks/banks.

***CARD DESIGN***

## CB.5 CARD DESIGN AND EMBOSSING FOR THE TRAVEL CARD PROGRAM

In addition to the requirements specified in C.23, Card Design and
Embossing, the Contractor shall provide for the following:

CB.5.1 *Face Side of Travel Cards:* The Contractor shall be able to
emboss/print each card with the following:

EMBOSSED:

a)  Account name;

b)  Account number;

c)  Expiration date; and

d)  A 20 character alphanumeric field for agency/organization use (may
    be used for the agency's tax exempt number).

PRINTED:

a)  Individual department, agency or organization name; and

b)  A minimum 15 digit alphanumeric discretionary field.

CB.5.2 *City Pair Program Identifier:* The GSA annually awards contracts
for air transportation for Federal employees on official Government
travel under the City Pair Program. One of the background card designs
provided will include a City Pair Program identifier. Based on the
information provided by agencies/organizations in the master file, the
Contractor shall ensure that only authorized users of the City Pair
Program have the card design that denotes authorized use of the City
Pair Program.

For those entities that are not authorized users of the City Pair
Program, the Contractor shall provide a separate card design that meet
commercial industry standards for card design and use the account
numbering requirements specified in CB.6, Account Number for the Travel
Card Program. Based on the information provided by
agencies/organizations in the master file, the Contractor shall ensure
that non-authorized users of the City Pair Program have the separate
card design that denotes the user does not have access to the City Pair
Program.

CB.5.3 *Quasi-Generic Card Requirements:* As requested by the A/OPC, the
Contractor shall provide a quasi-generic card, using the Contractor's
commercial design AND using the numbering system that identifies it as a
Government account. Quasi-generic cards issued under this contract shall
be subject to the terms and conditions of this contract. Quasi-generic
cards shall be embossed with:

a)  Account name;

b)  Account number; and

c)  Expiration date.

***ACCOUNT NUMBER***

## CB.6 ACCOUNT NUMBER FOR THE TRAVEL CARD PROGRAM

In addition to the requirements specified in C.24, Account Number, the
prefixes and numbering system utilized must distinguish between
individually and centrally billed accounts. The Contractor shall have
separate prefixes for individually billed accounts and centrally billed
accounts as identified below. The Contractor shall not utilize the same
prefixes and numbering system or sequence for non-Federal government
accounts, except as directed by the GSA Contracting Officer for
authorized entities using the City Pair Program on a mandatory basis,
such as designated Indian Tribes and the National Sector of the American
Red Cross. The following categories require separate account numbering
systems:

a)  Individually billed travel card accounts with City Pair Program
    access (separate prefixes and numbering system);

b)  Federal government centrally billed accounts with City Pair Program
    access (separate prefixes and numbering system) (with separate
    prefixes and numbering system for authorized Native Americans and
    the national sector of the American Red Cross);

c)  Other centrally billed accounts without City Pair Program access
    (separate prefixes and numbering system and a different card
    design);

d)  The Government reserves the right to require additional separate
    prefixes and numbering system.

***TRAINING***

## CB.7 TRAINING REQUIREMENTS FOR THE TRAVEL CARD PROGRAM

In addition to the requirements stated in C.25, Training Requirements,
the Contractor shall also provide the following:

CB.7.1 *Cardholder Guide for the Travel Card Program:* In addition to
the requirements specified in C.25.1, Cardholder Guide, the guide shall
also include:

a)  Statement of individual liability and cardholder responsibilities;

b)  Automated teller machine (ATM) procedures and locations (or Internet
    address/toll-free telephone number to locate convenient locations),
    where authorized;

c)  Travelers checks procedures and locations (or Internet
    address/toll-free telephone number to locate convenient locations);
    and

d)  Sample statement of account and how to read the statement of
    account.

CB.7.2 *Agency/Organization Program Coordinator Guide for the Travel
Card Program:* In addition to the requirements specified in C.25.2,
Agency/Organization Program Coordinator Guide, the guide shall also
include:

a)  Individually billed accounts requirements;

b)  Split disbursements;

c)  ATM procedures and locations (or Internet address/toll-free
    telephone number to locate convenient locations); and

d)  Travelers check procedures and locations (or Internet
    address/toll-free telephone number to locate convenient locations).

CB.7.3 *Designated Billing Office Guide:* In addition to the
requirements specified in C.25.3, Designated Billing Office Guide, the
guide shall also include split disbursement procedures.

***ADDITIONAL CONTRACT START-UP REQUIREMENTS***

## CB.8 ADDITIONAL START-UP IMPLEMENTATION REQUIREMENTS FOR THE TRAVEL CARD PROGRAM

In addition to the requirements stated in C.27, Start-Up Implementation
Requirements, the Contractor shall ensure that travelers checks and
associated equipment are issued no earlier than **November 15, 1998**,
unless otherwise directed by the agency/organization.

***AUTHORIZATION CONTROLS***

## CB.9 AUTHORIZATION CONTROLS FOR THE TRAVEL CARD PROGRAM

In addition to the requirements specified in C.30, Authorization
Controls, the Contractor shall provide the ability to limit access to
the ATM option. Each account may be assigned a daily, weekly or billing
cycle ATM limit by the A/OPC.

***PROGRAM AND TRANSACTION DATA (CENTRALLY BILLED ACCOUNTS)***

## CB.10 TRAVEL CARD PROGRAM AND TRANSACTION DATA FOR CENTRALLY BILLED ACCOUNTS

In addition to the requirements specified in C.34, Program and
Transaction Data, the Contractor shall provide the following:

CB.10.1 *Travel Card Program Master File for Centrally Billed Accounts:*
In addition to the requirements stated in C.34.5, Master File, the
Contractor shall also have the ability to record the following
information for each centrally billed account as set-up by the
agency/organization under Card Specific Information (reference
C.34.5.1):

a)  ATM data;

b)  Travelers check data; and

c)  City Pair Program Identifier.

Agencies/organizations may require additional master file elements to be
recorded and will so state specific requirements and request pricing in
their task order.

CB.10.2 *Travel Card Program Transaction Data for Centrally Billed
Accounts:* In addition to the requirements stated in C.34.6, Transaction
Data and C.34.6.1, Transaction Data Elements, the following transaction
data for each purchase shall also be recorded or obtained by the
Contractor:

a)  Hotel/Motel Fire Safety Act (FSA) statistics (on each lodging
    transaction, provide the number of room nights and a yes/no
    indicator as to whether the lodging establishment is FSA certified);

b)  Airline ticket numbers for common carrier transactions;

c)  Class of travel identifier (carrier\'s fare/class of service code);
    and

d)  Maximum available leg-by-leg itinerary (minimum of 4 legs) data for
    common air/rail carrier transactions.

***ACCOUNTS***

## CB.11 TRAVEL CARD PROGRAM CENTRALLY BILLED ACCOUNTS

Centrally billed accounts will be used primarily for common carrier
transportation purchases to meet the needs of individual
agencies/organizations. These accounts may be used by
agencies/organizations for lodging associated with mass movements and
other special functions of an individual agency/organization. There may
also be instances where an agency/organization requires charge cards to
be issued under a centrally billed account and may request ATM access
for these cards. In this case, the card shall be issued in an
employee\'s name, however, the billing statement shall be sent directly
to the agency/organization for payment. If requested by the
agency/organization, the Contractor shall meet with agency/organization
representatives to discuss implementation procedures. All Contractor
travel costs associated with this meeting shall be borne by the
Contractor.

In addition to the requirements specified in C.35, Centrally Billed Card
Program Accounts, the Contractor shall provide the following:

CB.11.1 *Account Set-Up for Centrally Billed Travel Card Accounts:* In
addition to the requirements stated in C.35.1, Account Set Up, the
Contractor shall:

a)  Provide a product with no preset expenditure limits for travel and
    subsistence;

b)  Provide an ATM option as requested; and

c)  Provide travelers checks as requested.

CB.11.2 *Card Issuance and Delivery for Centrally Billed Travel Card
Accounts:* In addition to the requirements stated in C.35.2,
Card/Cardless Issuance and Delivery for Centrally Billed Accounts, the
Contractor shall send PIN numbers associated with the ATM option
separately from the card within **three (3) business days** after
electronic or written notification by the A/OPC. Cards without initial
ATM authorization may be authorized at a later date by the A/OPC. The
Contractor shall allow the agency/organization the later option to
personalize a PIN number after initial issuance;

CB.11.3 *Invoices for Centrally Billed Travel Card Accounts:* In
addition to the requirements specified in C.35.7.3, Invoices, and
subsequent subparagraphs, the Contractor shall concurrently provide a
copy of the invoice and transaction data as specified in C.34.6,
Transaction Data and C.34.6.1, Transaction Data Elements, to the
agency's/organization's TMC or CTO in a medium(a) to be agreed upon by
the Contractor and the agency/organization.

A proper invoice consists of the invoice and the transaction data. Both
must be received in a readable format as agreed to in advance by both
parties, and must include complete transaction data as defined by this
contract. Prompt Payment timeframes apply only when these conditions are
met.

CB.11.4 *Billing Discrepancies for Centrally Billed Travel Card
Accounts:* Items which are not reconciled are considered to be disputed
charges. It is the agency's/organization's responsibility to notify the
Contractor of any items in dispute within 60 calendar days of receipt of
the invoice. In addition to the requirements specified in C.35.8,
Billing Discrepancies, the Contractor shall:

a)  Accept billing discrepancy reports which list unmatched items (both
    credits and debits) that have been manually or electronically
    reconciled against transaction records maintained by the TMC/CTO;
    and

b)  Subtract from the payments the dollar differences shown on the
    billing discrepancy reports pending receipt of additional
    information to be provided by the Contractor, vendor, or both.

CB.11.5 *Advance Credit:* The Contractor shall adhere to the
Government\'s advance credit policy. This policy allows refunds for
unused tickets to be deducted from the current bill if the refund due
has been processed by the TMC/CTO, providing the corresponding charge
has been paid or is on the current bill, and credit is not included in
the current bill.

CB.11.6 *Tracking Centrally Billed Account Payment:* The Contractor
shall be able to identify and track payment made by
agencies/organizations and have the ability to cross reference payment
to ticket numbers included under payment received.

***TRAVELERS CHECK REQUIREMENTS***

## CB.12 TRAVELERS CHECKS

As requested by the agency/organization, the Contractor shall be able to
provide travelers checks that can be issued and accepted domestically
and internationally by merchant establishments and financial
institutions. The travelers checks shall be an integrated part of the
travel card program. Travelers checks are priced separately in the
pricing schedule. The Contractor shall:

a)  Assist agencies/organizations in the implementation of their
    travelers check program;

b)  Furnish all equipment (e.g., card reader, software) necessary to
    implement and manage the travelers check program, at no cost to the
    Government, and if requested by the agency/organization;

c)  Provide, at a minimum, prepackaged sets of travelers checks in the
    following denominations: \$20; \$50; and \$100;

d)  Provide, at a minimum, individual travelers checks in the above
    stated denominations at the request of participating
    agencies/organizations;

e)  Provide holding envelopes with travelers checks to enable
    agencies/organizations to distribute checks in a packaged envelope;

f)  Provide dial-up/electronic access or Contractor-provided software to
    enable agencies/organizations to automate their travelers check
    system. The system shall, at a minimum, provide the ability to
    track, add, tally, report and reorder travelers checks;

g)  Issue travelers checks to both individually and centrally billed
    accounts, as directed by the A/OPC;

h)  Issue foreign currency travelers checks to participating domestic
    and international users, as requested by the A/OPC;

i)  Refund lost or stolen travelers checks domestically and
    internationally within **24 hours**, as requested by the A/OPC; and

j)  Establish payment procedures for agency-/organization-issued
    travelers checks. Payment for face-value of these checks shall not
    occur prior to issuance by the agency/organization.

CB.12.1 *Travelers Check Account Establishment:* Within **10 calendar
days** after receipt of a task order issued in accordance with the terms
and conditions of this contract, the Contractor shall contact the A/OPC
to discuss implementation procedures and, if requested by the
agency/organization, meet with agency/organization representatives to
review specific requirements. All Contractor travel costs associated
with this meeting shall be borne by the Contractor.

CB.12.2 *Inventory Replenishment:* The Contractor shall provide the
following inventory replenishment options:

a)  Automatic replenishment to pre-established dollar limits, by
    location; and

b)  Toll free or collect telephone line reorder capability; and 24 hour
    replenishment when requested by the A/OPC.

CB.12.3 *Trust Agreements:* Trust agreements, if any, must fully
describe the Government\'s liability for travelers checks held in
inventory by the Government.

***AGENCY REPORTING REQUIREMENTS***

## CB.13 TRAVEL CARD PROGRAM REPORTING REQUIREMENTS

In addition to the requirements specified in C.38, Agency Reporting
Requirements, the Contractor shall also provide the data listed in this
section.

CB.13.1 *Account Activity Report for the Travel Card Program:* This
report includes complete account activity, both active and inactive, and
includes a roll-up section. It includes ATM and travelers check
transactions. It reports current and fiscal year account activity. It
segregates all charges and credits by individually or centrally billed
accounts, with current period totals of the data elements identified. It
includes merchant information such as name, address, TIN, merchant
category code, etc.

CB.13.2 *Statistical Summary Report:* This report lists dollar volume,
ATM volume, travelers check volume, number of transactions, active
cardholders, total accounts, new accounts, miscellaneous fees and
identification of fees (e.g., fees for customized services, fees for
annual per card fees, fees for value-added products and services) on a
current and fiscal year basis.

CB.13.3 *Airline Credit/Refund Report:* This report lists all credits,
including refunds, by individually billed accounts and centrally billed
accounts. It includes merchant name, credit amount and credit date.

CB.13.4 *Write-off Report:* In addition to the requirements of C.38.2,
subparagraph k), this report shall also list the amounts written-off and
the reasons for the write-offs for individually billed accounts.

CB.13.5 *Invoice Status Report:* In addition to the requirements of
C.38.1, subparagraph b), this report shall also list ticket numbers.

CB.13.6 *Hotel/Motel Fire Safety Act (FSA) Report:* This report lists
FSA data and gives a percentage compliance to the FSA for each
agency/organization.

CB.13.7 *Per Card Fees/Pre-Funded Cards on Individually Billed
Accounts:* This report lists, by name and account number, all per card
fees assessed for the agency/organization and provides the number of
pre-funded cards provided and associated dollar value of the pre-funded
cards.

***PROGRAM AND TRANSACTION DATA (INDIVIDUALLY BILLED ACCOUNTS)***

## CB.14 TRAVEL CARD PROGRAM AND TRANSACTION DATA FOR INDIVIDUALLY BILLED ACCOUNTS

In addition to the requirements specified in C.34, Program and
Transaction Data, and CB.10, Travel Card Program and Transaction Data
for Centrally Billed Accounts, the Contractor shall provide the
following:

CB.14.1 *Travel Card Program Master File for Individually Billed
Accounts:* In addition to the requirements stated in C.34.5, Master
File, and CB.10.1, Travel Card Program Master File for Centrally Billed
Accounts, the Contractor shall also record:

> a\) A 12-digit alphanumeric identification number (this number may be
> used at the option of the Government as a cross-check with personnel
> records to verify cardholder employment); and
>
> b\) City Pair Program Identifier.

Agencies/organizations may require additional master file elements to be
recorded and will so state specific requirements and request pricing in
their task order.

***INDIVIDUALLY BILLED ACCOUNTS***

## CB.15 TRAVEL CARD PROGRAM INDIVIDUALLY BILLED ACCOUNTS

In addition to the requirements specified in C.35, Centrally Billed Card
Program Accounts and CB.11, Travel Card Program Centrally Billed
Accounts, the Contractor shall issue individually billed cards to
Government employees and only after receipt of a task order issued and
authorized by the A/OPC in accordance with the terms and conditions of
this contract. If requested by the A/OPC, the Contractor shall meet with
agency/organization representatives to discuss implementation
procedures. All Contractor travel costs associated with this meeting
shall be borne by the Contractor. Except during the implementation
schedule referred to in C.27, Start-Up Implementation Requirements and
CB.8, Additional Start-Up Implementation Requirements for the Travel
Card Program, cardholder agreements must be signed by the employee and
approved by the A/OPC prior to establishing an individually billed
account. Although the Government authorizes individually billed accounts
to be established, the Government accepts no liability for charges made
against the individually billed accounts.

CB.15.1 *Program Requirements for Individually Billed Accounts:*

CB.15.1.1 *[Cardholder Agreement]{.underline}:* The Contractor shall
develop a cardholder agreement for individually billed accounts. The
cardholder agreement shall include, at a minimum, the following:

a)  Purpose of the card and the account;

b)  Procedures for renewal and replacement of cards;

c)  Restrictions on use of the card;

d)  Individual liability for charges;

e)  Payment schedule;

f)  Non-payment actions and debt recovery fees (debt recovery fees are
    those fees charged for formal debt collection action);

g)  Delinquency and suspension/cancellation procedures;

h)  Automated Teller Machine Program procedures, where authorized;

i)  Travelers check procedures, where authorized;

j)  Procedures for reporting lost or stolen cards;

k)  Method of foreign currency conversions; and

l)  Toll-free or collect telephone number for billing inquiries, billing
    disputes, reporting lost or stolen cards, and problems with goods
    and services.

CB.15.1.2 *[Account Set-Up for Individually Billed
Accounts]{.underline}:* The Contractor shall:

a)  Assist A/OPCs in setting up accounts, as requested;

b)  Provide a 25-30 calendar day billing cycle;

c)  Provide a product with no preset authorization controls for travel
    and subsistence, unless otherwise specified by the A/OPC;

d)  Provide an ATM option if requested by the A/OPC;

e)  Have the capability to provide required authorization controls as
    stated in C.30, Authorization Controls and CB.9, Authorization
    Controls for the Travel Card Program at the request of the A/OPC;

f)  Establish individually billed accounts as requested by the A/OPC,
    without prior credit worthiness checks; and

g)  Make accounts valid for a specific time period as agreed upon by the
    Contractor and the A/OPC, not to exceed the master contract base
    period or any options exercised, unless otherwise specified by the
    GSA Contracting Officer.

For purposes of opening accounts, cardholder agreements shall be
accepted by the Contractor via electronic medium, fax and/or mail. The
original cardholder agreement will be forwarded by the A/OPC within
three (3) business days of the request to open the account.

CB.15.1.3 *[Card Issuance and Delivery for Individually Billed Travel
Card Accounts]{.underline}:* The Contractor shall:

a)  Establish new individually billed accounts upon receipt of a
    completed application that was approved by the A/OPC. A completed
    application is defined as account-set up information and signed
    cardholder agreement via fax, mail or electronic means;

b)  Process cardholder agreements and send cards within **three (3)
    business days** of receipt of the completed application;

c)  Send PIN numbers associated with the ATM option separately from the
    card within **three (3) business days** after written notification
    by the A/OPC. Cards without initial ATM authorization may be
    authorized at a later date by the A/OPC. The Contractor shall allow
    the cardholder the later option to personalize a PIN number after
    initial issuance;

d)  Make cards valid for a specific time period as agreed upon by the
    Contractor and the A/OPC, not to exceed the master contract base
    period or any options exercised, unless otherwise directed by the
    GSA Contracting Officer;

e)  Mail cards to the individual cardholder's stated address, or as
    directed by the A/OPC;

f)  Domestically, replace lost, stolen, broken or otherwise unusable
    cards within **24 hours** after the loss is reported to the
    Contractor; and

g)  Internationally, replace lost, stolen, broken or otherwise unusable
    cards within **48 hours** after the loss is reported to the
    Contractor.

CB.15.1.4 *[Emergency Account Set-Up and Card Delivery]{.underline}:*
The Contractor shall process and send cards within **24 hours** at the
request of the A/OPC. Where the Government provides oral instruction to
set up an account and issue a card, written confirmation will follow
within three (3) working days of the oral authorization. The
agency/organization may use electronic means to forward program forms to
the Contractor.

CB.15.1.5 *[Card Renewal for Individually Billed Accounts]{.underline}:*
At least **90 calendar days** prior to the expiration of each account or
card, the Contractor shall submit a report to the A/OPC listing each
expiring card. The report shall contain all information necessary for
the agency/organization to renew the card. Cards shall automatically
renew unless otherwise directed by the A/OPC. If cards are not to be
renewed, the A/OPC will notify the Contractor, in writing, 45 calendar
days prior to account or card expiration.

CB.15.1.6 *[Verification of Card Receipt]{.underline}:* The Contractor,
at its expense, shall have a means of verifying that the cardholder has
received the travel card.

CB.15.1.7 *[Statement of Account]{.underline}:* The Contractor shall
send the itemized statement of account to each cardholder within **five
(5) business days** after the end of each billing cycle. This document
is the official invoice for the individually billed account cardholder.
The statement shall include all transactions (debits and credits) posted
during the billing cycle. The statement of account shall include all
transaction data referenced in C.34.6.1, Transaction Data Elements and
CB.10, Travel Card Program and Transaction Data for Centrally Billed
Accounts, and also include the billing cycle date.

CB.15.1.8 *[Split Disbursement]{.underline}:* The Contractor shall
process split disbursements by an agency/organization as received. This
may include, but not be limited to, segregating and billing transactions
at the employee and the agency/organization level. Transactions
typically split include, but are not limited to, common carrier
transportation charges, hotel/motel charges, and car rental charges. The
Contractor shall have the ability to record in any split disbursement
the traveler's name and identifying number and identify the charges for
split disbursement (e.g., ticket number, etc.).

CB.15.1.9 *[Billing Discrepancies]{.underline}:* It is intended that
cardholders will reconcile their itemized official invoice and make
payment for those items not in dispute. It is the cardholder's
responsibility to notify the Contractor of any items in dispute within
60 calendar days of the receipt of the official invoice. The Contractor
shall:

a)  Provide immediate temporary credit to the account;

b)  Provide sufficient transaction data to identify the charge;

c)  Promptly investigate disputed items and use best efforts to resolve
    transaction disputes, including working with merchants and the
    transaction dispute office;

d)  Provide a copy of the charge in dispute, if requested;

e)  Provide a copy of all Contractor correspondence regarding disputed
    items, if requested;

f)  Chargeback the merchant where appropriate;

g)  Detail the disputed charge on the Invoice Status Report (see C.38.1,
    subparagraph b)); and

h)  Rebill proper charges in the subsequent billing period and include
    complete transaction data for the rebilled charge.

If a disputed item is resolved before the payment due date, the
resolution shall appear on the cardholder's following official invoice.

CB.15.1.10 *[Reconciliation Assistance]{.underline}:* The Contractor
shall assist cardholders in the reconciliation of individually billed
accounts, as requested.

CB.15.1.11 *[Processing Payments]{.underline}:* The Contractor shall
provide dedicated personnel to operationally support invoicing,
transaction disputes, and payments under this contract.

CB.15.1.12 *[Tracking Individually Billed Account Payment]{.underline}:*
The Contractor shall be able to identify and track payment by the
cardholder\'s social security number and account number at the
agency's/organization's discretion. The Contractor shall have the
ability to accept individually billed account payment electronically.
The Contractor shall ensure that their accounting system enables the
accurate and timely posting of account payments, to include matching of
payment by account number and social security number made to an
individually billed account by both the individual cardholder and the
Government via split disbursements.

CB.15.1.13 *[Payment for Individually Billed Accounts]{.underline}:*
Payments for individually billed accounts are the cardholder's
responsibility. The Government assumes no liability for individually
billed accounts.

***CREDIT BUREAUS AND INDIVIDUALLY BILLED ACCOUNTS***

## CB.16 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS AND CREDIT BUREAUS

\(a\) Generally, credit checks as a condition of initial card issuance
is not allowed. However, at the agency's/organization's discretion,
credit checks for the purpose of identifying alternate payment
mechanisms may be included in the agency/organization task
requests/orders for individually billed travel card accounts. If chosen
by the agency/organization, criteria for credit check screenings shall
be mutually agreed to by the agency/organization and Contractor. The
Contractor shall not deny card issuance to any individual on the basis
of the credit check nor report any of the account history or performance
to a credit bureau (but see paragraph (b), below). Credit checks would
not be conducted to deny an individual a card; rather, to provide the
agency/organization limited information (i.e., pass/fail credit check)
so that the agency/organization can provide the individual an
alternative card payment mechanism (i.e., pre-funded card) as determined
by the agency/organization. If this option is chosen by the
agency/organization, the agency/organization will be responsible for
negotiating any changes to its union agreements. The individual
cardholder must provide written consent to the card service provider
(e.g., through their cardholder agreement) prior to any credit check
being performed and the individual cardholder retains the right to
revoke his/her consent to the credit check at any time in accordance
with the Right To Financial Privacy Act (12 U.S.C. 3401 et seq.) and
will notify the Contractor if consent to the credit check is revoked.
**\[NOTE: THE DEPARTMENT OF DEFENSE HAS INDICATED THAT FOR DOD
INDIVIDUALLY BILLED ACCOUNT TRAVEL CARD PROGRAMS, CREDIT CHECKS ARE A
MANDATORY ELEMENT IN THEIR TASK ORDER. THIS MANDATORY ELEMENT OF DOD'S
TASK ORDER IS CONTINGENT UPON PENDING SUCCESSFUL GOVERNMENT NEGOTIATIONS
WITH THE APPROPRIATE UNION OFFICIALS. FOR ALL OTHER AGENCIES, CREDIT
CHECKS ARE NOT MANDATORY\]**

\(b\) For all individually billed travel card accounts, the Contractor
may provide credit information to credit bureaus in cases where the
individually billed account has been canceled in accordance with CB.19,
Individually Billed Travel Card Account Cancellation Procedures AND the
Suspension/Cancellation Report (C.38.1., subparagraph e)) has been
provided to the A/OPC in accordance with the terms and conditions of the
contract. Federal Government centrally billed accounts shall not be
referred to credit bureaus.

***DELINQUENCY CONTROL FOR INDIVIDUALLY BILLED ACCOUNTS***

## CB.17 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS AND DELINQUENCY CONTROL

The Contractor may elect to utilize a collection agency for delinquency
control on individually billed accounts after the requirements of CB.19,
Individually Billed Travel Card Account Cancellation Procedures, have
been met AND the Suspension/Cancellation Report (C.38.1., subparagraph
e)) has been provided to the A/OPC in accordance with the terms and
conditions of the contract. If the Contractor elects to use a collection
agency for delinquency control on individually billed accounts, the
Contractor shall require the collection agency in its contract or other
agreement with the collection agency to abide by the terms and
conditions of this contract covering release of information. The
Contractor shall ensure that the collection agency adheres to the Fair
Debt Collection Practices Act.

If any collection effort results in a final settlement action, all
Contractor records and reports shall so reflect the settlement action
and debt shall be considered discharged.

***SUSPENSION PROCEDURES FOR INDIVIDUALLY BILLED ACCOUNTS***

## CB.18 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNT SUSPENSION PROCEDURES

For suspension purposes, an account is considered past due if payment
for undisputed principal amounts has not been received 45 calendar days
from the closing date on the statement of account in which the charges
appeared. The Contractor shall either send a letter to the individual
cardholder or make a documented telephone call to the individual
cardholder requesting payment on past due accounts for the undisputed
principal amount.

The Contractor shall provide the Pre-Suspension/Pre-Cancellation Report
(reference C.38.1, subparagraph d)) to the A/OPC to identify undisputed
amounts that are overdue on individually billed accounts. If the
Contractor chooses to begin the suspension process, it shall follow the
procedures listed below if payment for the undisputed principal amount
has not been received 55 calendar days from the closing date on the
statement of account in which the charges appeared. The Contractor
shall:

1)  Notify the cardholder and A/OPC of suspension if payment for the
    principal amount is not received by the close of business on the
    fifth (5th) calendar day after notification;

2)  Notify the cardholder and A/OPC of the Contractor's point of contact
    to assist in resolving the past due account(s).

Suspension actions must be documented and, if requested, such
documentation must be provided to the A/OPC. If payment for the
undisputed principal amount has not been received 61 calendar days from
the closing date on the statement of account in which the charges
appeared, the Contractor may suspend the account, unless otherwise
directed by the A/OPC due to extenuating circumstances. The Government
accepts no liability for charges made against the individually billed
account.

CB.18.1 *Disputed Items:* The Contractor shall not suspend any account
for amounts in dispute.

CB.18.2 *Reinstatement of Suspended Individually Billed Accounts:* The
Contractor shall automatically reinstate suspended accounts upon payment
of the undisputed principal amount, unless otherwise specified by the
A/OPC.

CB.18.3 *Credit Bureaus:* The Contractor shall not provide credit
information on suspended individually billed accounts.

CB.18.4 *Referral of Individually Billed Accounts to Debt Collection:*
Suspended individually billed accounts shall not be referred to outside
collection entities until the requirements of CB.17 have been met.

CB.18.5 *Suspension/Reinstatement Record:* The Contractor shall maintain
a suspension/reinstatement file on individually billed accounts to
include, at a minimum, the cardholder name, the agency/organization
office name, the agency/organization identifying number, the account
number, the A/OPC and A/OPC's telephone number, invoice numbers, the
amount for each invoice, the number of days past due for each invoice,
documentation described in CB.18, the date of suspension and the date of
reinstatement. This file shall be made available to the A/OPC and the
GSA Contracting Officer immediately upon request.

CB.18.6 *Repeated Suspensions:* If an individually billed account has
been suspended two times during a 12-month period for undisputed amounts
and is past due again as outlined in CB.18, the Contractor may cancel
the account in accordance with the requirements of CB.19, Individually
Billed Travel Card Account Cancellation Procedures.

CB.18.7 *Government Requested Suspension:* The A/OPC reserves the right
to suspend an individually billed account under his/her purview and
document the reasons for the suspension. The GSA Contracting Officer
reserves the right to suspend an individually billed account and
document the reasons for suspension. In accordance with the requirements
specified in C.30, Authorization Controls, the Contractor shall have the
ability to void cards at the request of the A/OPC or GSA Contracting
Officer.

***CANCELLATION PROCEDURES FOR***

***INDIVIDUALLY BILLED ACCOUNTS***

## CB.19 INDIVIDUALLY BILLED TRAVEL CARD ACCOUNT CANCELLATION PROCEDURES

The Contractor shall provide the Pre-Suspension/Pre-Cancellation Report
(reference C.38.1 d)) to the A/OPC to identify the undisputed amount
that is overdue on individually billed accounts.

There are three reasons for which the Contractor may initiate
cancellation of an individually billed account:

1\. The account has been suspended two times during a 12-month period
for undisputed amounts and is past due again as outlined in CB.18,
Individually Billed Travel Card Account Suspension Procedures (e.g., an
account was suspended in January and in December of any given year and
is past due again in March of the following year would be eligible for
cancellation); or

2\. The account is past due for undisputed amounts, i.e., 120 calendar
days past the closing date on the statement of account in which the
charges appeared, and the requirements of CB.18, Individually Billed
Travel Card Account Suspension Procedures have been met; or

3\. Use of the card for other than authorized purchases and suspension
is approved by the A/OPC.

If the Contractor chooses to begin cancellation procedures, it shall
follow the procedures listed below if payment for the undisputed
principal amount has not been received 120 calendar days from the
closing date on the statement of account in which the charges appeared.
The Contractor shall either send a letter to the cardholder and A/OPC or
make a documented telephone call to the cardholder and A/OPC requesting
payment on past due accounts for the undisputed principal amount. The
Contractor shall:

1)  Notify the cardholder and A/OPC of cancellation if payment for the
    principal amount is not received by the close of business on the
    fifth (5th) calendar day after notification;

2)  Notify the cardholder and A/OPC of the Contractor's point of contact
    to assist in resolving the past due account(s).

Cancellation actions must be documented and, if requested, such
documentation must be provided to the A/OPC. If payment for the
undisputed principal amount has not been received 126 calendar days from
the closing date on the statement of account in which the charges
appeared, the Contractor may cancel the account, unless otherwise
directed by the A/OPC due to extenuating circumstances. The Government
accepts no liability for charges made against the individually billed
account.

CB.19.1 *Disputed Items:* The Contractor shall not cancel any account
for amounts in dispute.

CB.19.2 *Reinstatement of Canceled Individually Billed Accounts:* The
Contractor may reinstate canceled individually billed accounts upon
payment of the principal amount and late fee. The Contractor may conduct
a credit worthiness check prior to reinstatement of canceled
individually billed accounts. The Government accepts no liability for
charges made against the individually billed account.

CB.19.3 *Credit Bureaus:* Canceled individually billed accounts may be
referred to credit bureaus in accordance with CB.16, Individually Billed
Travel Card Accounts and Credit Bureaus.

CB.19.4 *Referral to Debt Collection:* Canceled individually billed
accounts may be referred to outside collection entities in accordance
with CB.17, Individually Billed Travel Card Accounts and Delinquency
Control.

CB.19.5 *Cancellation/Reinstatement Record:* The Contractor shall
maintain a cancellation/rein-statement file on individually billed
accounts to include, at a minimum, the cardholder name, the
agency/organization office name, the agency/organization identifying
number, the account number, the A/OPC and A/OPC's telephone number,
invoice number, the amount for each invoice, the number of days past due
for each invoice, documentation described in CB.19, the date of
suspension, the date of reinstatement from suspension, the date of
cancellation and the date of reinstatement from cancellation. This file
shall be made available to the A/OPC and the GSA Contracting Officer
immediately upon request.

CB.19.6 *Government Requested Cancellation:* The A/OPC reserves the
right to cancel an individually billed account under his/her purview and
document the reasons for the cancellation. The GSA Contracting Officer
reserves the right to cancel an individually billed account and document
the reasons for cancellation. In accordance with the requirements
specified in C.30, Authorization Controls, the Contractor shall have the
ability to void cards at the request of the A/OPC or GSA Contracting
Officer.

***LIABILITY FOR INDIVIDUALLY BILLED ACCOUNTS***

## CB.20 LIABILITY FOR INDIVIDUALLY BILLED ACCOUNTS ON THE TRAVEL CARD PROGRAM

Full liability for all charges and late fees rests with the individual
cardholder. The Government shall not be liable for individually billed
accounts.

CB.20.1 *Lost or Stolen Cards:* Cardholders must promptly report lost or
stolen cards to the Contractor(s). The cardholder shall not be liable
for purchases made on cards reported lost or stolen. The Government
shall not be liable for individually billed accounts.

***LATE FEES FOR INDIVIDUALLY BILLED ACCOUNTS***

## CB.21 LATE FEES ON INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS

The Contractor may charge their standard commercial late fee on the
undisputed charge made on individually billed accounts that are 120
calendar days past the closing date on the statement of account in which
the charges appeared and have been canceled in accordance with CB.19,
Individually Billed Travel Card Account Cancellation Procedures. Solely
at the agency's/organization's discretion, late fees may be assessed in
accordance with standard commercial practice and contingent upon the
agency's/organization's successful negotiations with the appropriate
union officials. Late fees are the responsibility of the individual
cardholder. The Government shall not be liable for late fees on
individually billed accounts. If an agency/organization allows late fees
in accordance with standard commercial practice, the agency shall so
state in their task request/order and request pricing.

***REINSTATEMENT FEES ON CANCELED INDIVIDUALLY BILLED ACCOUNTS***

## CB.22 REINSTATEMENT FEES ON CANCELED INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS

The Contractor may not charge a reinstatement fee; however, the
Government reserves the right to allow reinstatement fees during the
contract period on individually billed travel card accounts.

***RISK MEASURES***

## CB.23 PER CARD ANNUAL FEES OR PRE-FUNDED CARDS FOR INDIVIDUALLY BILLED TRAVEL CARD ACCOUNTS

GSA recognizes that in some cases, participation in the travel card
program may require allowance of risk mitigation measures to vendors.
Thus, GSA contemplates allowing (but not requiring) a variety or risk
mitigation measures for agencies to choose from if so desired.

The following are just two samples of risk mitigation measures
contemplated. GSA asks for detailed industry input on other risk
mitigation measures (excluding late fees) as well.

The Contractor may offer both per card annual fees and pre-funded cards
for individually billed travel card accounts. For those individually
billed travel card accounts that demonstrate poor payment performance,
the agency/organization may choose a per card annual fee or a pre-funded
card to mitigate contractor risk. Poor payment performance is defined
as:

-   Those individually billed travel card accounts in which payment for
    undisputed amounts are outstanding 60 days or more past the closing
    date on the statement of account in which the charges appeared for
    any 3-month period; or

-   Those individually billed travel card accounts that have been
    suspended two times during a 12-month period for undisputed amounts
    and is past due again (as outlined in CB.18); or

-   Those accounts which have been canceled in accordance with CB.19,
    Individually Billed Travel Card Account Cancellation Procedures and
    are reinstated.

a\) Per Card Annual Fees: The Contractor may charge an annual per card
fee for those individually billed travel card accounts meeting the poor
payment performance definition described above. The agency/organization
will be responsible for payment of this annual per card fee; however,
will not be liable for any charges made by the individually billed
account. The annual per card fee shall be limited to those individually
billed accounts that meet the poor payment performance definition as
specified above, for that specific agency/organization level. For
example, ABC Agency has 1,000 individually billed travel card accounts.
75 of those individually billed accounts meet the definition of poor
payment performance. ABC Agency chooses the annual per card fee option
to mitigate Contractor risk. The Contractor may then charge a per card
fee for those 75 accounts (e.g., \$X times 75 = \$Y). The Contractor may
retain this fee for the full 1-year timeframe from fee institution
regardless of payment performance improvement.

If payment performance improves during the 1-year timeframe from fee
institution and individually billed accounts no longer meet the poor
payment performance definition, the Contractor shall eliminate the
annual per card fee. Should individually billed accounts once again meet
the poor payment performance definition, the Contract may reinstate the
annual per card fee, as described above.

The Contractor shall track and report these fees on agency/organization
reports.

b\) Pre-Funded Card: These are cards funded by the Government in advance
of an individual's travel (i.e., a travel advance on a card product).
Agencies/Organizations may request that authorization controls are
placed on a pre-funded card in accordance with C.30, Authorization
Controls. Contractor-provided pre-funded cards will allow individuals to
incur travel expenses up to a pre-determined spending limitation as
designated by the agency/organization. The Government will pre-fund the
card. The Contractor may not charge a fee for the pre-funded card. The
Contractor may offer a pre-funded card. If pre-funded cards are chosen
by the agency/organization, the Contractor may provide a pre-funded card
for those individually billed travel card accounts meeting the poor
payment performance definition described above. The pre-funded card
option shall be limited to those individually billed accounts that meet
the poor payment performance definition as specified above, for that
specific agency/organization level. The Contractor may not charge a fee
for pre-funded cards. For example, XYZ Agency has 1,000 individually
billed travel card accounts. 75 of those individually billed accounts
meet the definition of poor payment performance. XYZ Agency chooses the
pre-funded card option to mitigate Contractor risk.

If the individually billed account cardholder demonstrates proper use of
the pre-funded card as determined by the A/OPC (e.g., internal
procedures are followed, charges are within authorization controls)
during the 1-year timeframe from pre-funded card institution, the
Contractor shall restore normal charge functions (i.e., eliminate the
pre-funding requirement) and remove authorization controls, at the
request of the A/OPC. Should individually billed accounts once again
meet the poor payment performance definition after restoration of normal
charge functions and/or removal of authorization controls, the
Contractor may reinstate the pre-funded card for that particular
individually billed account cardholder.

Pre-funded cards may also be offered as a standard risk mitigation
measure regardless of payment performance. Agencies/organizations may,
at their discretion, include a requirement for pre-funded cards in their
task order and request pricing.

The Contractor shall track and report the dollar volume and number of
pre-funded cards on agency/organization reports.

**END OF REQUIREMENTS SPECIFIC TO THE TRAVEL CARD PROGRAM**

# *SECTION CC - REQUIREMENTS SPECIFIC TO THE PURCHASE CARD PROGRAM*

## CC.1 BACKGROUND FOR PURCHASE CARD SERVICES

*Regulatory:* The Federal Acquisition Regulation and agency supplements
thereto directs how the Government acquires supplies and services.

*Program History:* The National Performance Review (NPR) established a
goal to create a Government that works better and costs less.
Government-wide procurement reform was identified as one avenue to
accomplish this objective. One of the principal NPR procurement reform
recommendations was to expand the use of the Government purchase card.
With the passage of the Federal Acquisition Streamlining Act (FASA) of
1994, came sweeping acquisition reform. The Act created or improved the
processes for contract formation, contract administration, acquisition
management, items, and other procurement matters. FASA also had a direct
impact on the exponential growth of purchase card usage.

Piloted in 1986, the purchase card program began with 24 Federal
agencies. The pilot program was so successful, the Office of Management
and Budget (OMB) requested that the General Services Administration
acquire purchase card services on a government-wide basis. The first
contract was competitively awarded by GSA in 1989, and the second
contract was competitively awarded in 1994. To illustrate the growth of
this program in terms of dollars, transactions, and cardholders, see
Exhibit 8.

***DEFINITIONS***

## CC.2 DEFINITIONS:

**Billing Date:** The billing date is the date the invoice is received
by the agency/organization designated billing office in accordance with
the Prompt Payment Act.

**Cardholder:** Any individual or agency/organization component
designated by the agency/organization issued a card. The card bears the
individual\'s or agency's/organization's component name and can be used
to pay for official expenses in compliance with the applicable
regulations.

**Delegation of Authority:** A document, issued by authorized
agency/organization personnel, that establishes the individual as an
authorized cardholder. This delegation of authority shall specify
spending and usage limitations unique to the cardholder. Each
agency/organization, in their internal procedures, must designate who
shall be responsible for issuance of these delegations.

**Micro Purchase:** As defined in FAR 2.101, an acquisition of supplies
or services (except construction), the aggregate amount of which does
not exceed \$2,500, except that in the case of construction, the limit
is \$2,000.

**Official Purchase:** Supplies or services procured at the direction of
a Federal agency/organization under official purchase authorization.

**Simplified Acquisition Threshold:** As described in FAR 2.101, means
\$100,000, except that in the case of any contract to be awarded and
performed, or purchase to be made, outside the United States in support
of a contingency operation as defined in 10 U.S.C. 101(a)(13), the term
means \$200,000.

> **CORE REQUIREMENTS - TIER 1**

***SUMMARY OF PROGRAM REQUIREMENTS***

## CC.3 PURCHASE CARD PROGRAM REQUIREMENTS

In addition to the requirements stated in C.7, Card Program(s)
Requirements, the Contractor shall provide a program that provides for
Bank Checks,

***MERCHANT ACCEPTANCE***

## CC.4 MERCHANT ACCEPTANCE FOR THE PURCHASE CARD PROGRAM

In addition to the requirements specified in C.8, Merchant Acceptance,
the Contractor shall provide a product with widespread domestic and
international merchant acceptance by a variety of merchants that supply
products and services.

***CARD DESIGN***

## CC.5 CARD DESIGN AND EMBOSSING FOR THE PURCHASE CARD PROGRAM

The requirements stated in this section are in addition to the
requirements specified in C.23, Card Design and Embossing.

CC.5.1 *Face Side of Purchase Cards:* The Contractor shall be able to
emboss/print each card with the following:

EMBOSSED:

a)  Account name;

b)  Account number;

c)  Expiration date; and

d)  A 20 character alphanumeric field for agency/organization use (may
    be used for the agency's tax exempt number).

PRINTED:

a)  Individual department, agency or organization name; and

b)  A minimum 15 digit alphanumeric discretionary field.

***TRAINING***

## CC.6 TRAINING REQUIREMENTS FOR THE PURCHASE CARD PROGRAM

In addition to the requirements stated in C.25, Training Requirements,
the Contractor shall also provide the following:

CC.6.1 *Cardholder Guide for Purchase Card Program:* In addition to the
requirements stated in C.25.1, Cardholder Guide, this guide shall also
include bank check procedures (as defined in CC.11), where authorized,
and a sample statement of account with instructions how to read the
statement of account.

CC.6.2 *Agency/Organization Program Coordinator Guide for the Purchase
Card Program:* In addition to the requirements of C.25.2,
Agency/Organization Program Coordinator Guide, this guide shall also
include bank check procedures.

***ADDITIONAL CONTRACT START-UP REQUIREMENTS***

## CC.7 ADDITIONAL START-UP IMPLEMENTATION REQUIREMENTS FOR THE PURCHASE CARD PROGRAM

In addition to the requirements stated in C.27, Start-Up Implementation
Requirements, the Contractor shall ensure that bank checks and
associated equipment are issued no earlier than **November 15, 1998,**
unless otherwise directed by the agency/organization.

***AUTHORIZATION CONTROLS***

## CC.8 AUTHORIZATION CONTROLS FOR THE PURCHASE CARD PROGRAM

In addition to the requirements specified in C.30, Authorization
Controls, the Contractor shall provide a billing cycle office limit. The
billing cycle office limit is used by agencies/organizations primarily
for budget control purposes. Each office shall be assigned a billing
cycle office dollar limit set by the A/OPC. Any office limit may be
assigned; however, the Contractor shall provide, at a minimum, an office
limit that can accommodate 7 digits in length.

The purchase card shall further be restricted as follows:

-   The card shall not be used for the long-term rental or lease of land
    or buildings;

-   Major telecommunications (telephone) services (i.e., FTS2000 or
    DSN). However, telephone equipment may be purchased unless
    restricted by an agency/organization;

-   Travel or travel-related purposes. All authorizations for merchants
    that are classified as travel and subsistence types of business
    shall be denied, unless specifically authorized. The types of
    business denied will include airlines, restaurants, bars, hotels,
    travel agencies and car rental agencies. However, it may be used for
    travel purposes where the GSA travel card is not accepted or an
    integrated solution card which includes the travel card program;

-   Fuel, oil, services, maintenance and repairs for those users of IFMS
    and the GSA Fleet Management Program. However, it may be used for
    fuel and fleet-related purposes under an integrated solution card
    which includes the fleet card program; and

-   Cash advances (unless permitted by agency/organization selected
    value-added option or an integrated solution card which includes the
    travel card program).

***PROGRAM AND TRANSACTION DATA***

## CC.9 PURCHASE CARD PROGRAM AND TRANSACTION DATA

In addition to the requirements specified in C.34, Program and
Transaction Data, the Contractor shall provide the following:

CC.9.1 Purchase Card Program Master File: In addition to the
requirements stated in C.34.5, Master File, the Contractor shall also
record the following information as set-up by the agency/organization
under Card Specific Information (reference C.34.5.1):

a)  12 digit alphanumeric identification number (This number may be used
    at the option of the Government as a cross check with personnel
    records to verify cardholder employment); and

b)  Bank check data.

Agencies/organizations may require additional master file elements to be
recorded and will so state specific requirements and request pricing in
their task order.

***ACCOUNTS***

## CC.10 PURCHASE CARD PROGRAM ACCOUNTS

In addition to the requirements specified in C.35, Centrally Billed Card
Program Accounts, the Contractor shall also provide the following:

CC.10.1 *Statement of Account:* The Contractor shall send an itemized
statement of account to each cardholder within **five (5) business
days** after the end of each billing cycle. The statement of account is
NOT the official invoice. The statement shall include all transactions
(debits and credits) posted during the billing cycle. The statement of
account shall include all transaction data referenced in C.34.6.1,
Transaction Data Elements and also include:

a)  Statement date;

b)  Cardholder address;

c)  Designated Billing Office identifier;

d)  Foreign conversion rate and methodology, as applicable;

e)  Total dollar amount of the statement of account;

f)  Instructions for handling transaction disputes and any commercial
    regulations concerning disputed items;

g)  Toll-free or collect telephone number for statement inquiries;

h)  Cardholder's monthly limit and single purchase limit;

i)  64 digit alphanumeric master accounting code;

j)  15 digit alphanumeric code; and

k)  20 digit alphanumeric agency/organization tax exempt number field.

***BANK CHECK REQUIREMENTS***

## CC.11 BANK CHECKS

As requested by the agency/organization, the Contractor shall be able to
provide bank checks that can be issued and accepted domestically and
internationally by merchant establishments and financial institutions.
The bank checks shall be an integrated part of the purchase card
program. The checks shall be guaranteed by the Contractor against theft
or loss, thus affording the agency/organization protection against
financial loss when using the Contractor\'s product. Bank checks are
priced separately in the pricing schedule. The Contractor shall:

a)  Assist agencies/organizations in the implementation of their bank
    check program;

b)  Provide a supply of checks to a designated cardholder drawn on the
    cardholder's purchase card account;

c)  Process the checks as they are presented for payment;

d)  Provide a listing of the checks cleared on the cardholder's
    statement of account and official invoice as a separate line item;

e)  Provide bank checks that vary in maximum payment amounts as
    designated by the agency/organization;

f)  Ensure that bank checks are multi-copied (one copy for the
    cardholder's records, the original for the merchant);

g)  Store cleared bank checks in accordance with C.42, Record Retention
    and Retrieval;

h)  Provide copies of cleared bank checks within **14 calendar days** of
    the agency's/organization's request;

i)  Issue foreign currency bank checks to participating domestic and
    international users, as requested by the A/OPC;

j)  Refund lost or stolen bank checks domestically and internationally
    within **24 hours**, as requested by the A/OPC;

k)  Provide electronic access or Contractor-provided software to enable
    agencies/organizations to automate their bank check system. The
    system shall, at a minimum, provide the ability to track, add,
    tally, report and reorder bank checks;

l)  Provide an audit trail which permits tracing of all transactions;

m)  Have the capability to stop payment on the bank check; and

n)  Establish payment procedures for agency-/organization-issued bank
    checks. Payment for these checks shall not occur prior to issuance
    by the agency/organization.

CC.11.1 *Bank Check Account Establishment:* Within **10 calendar days**
after receipt of a task order issued in accordance with the terms and
conditions of this contract, the Contractor shall contact the A/OPC to
discuss implementation procedures and, if requested by the
agency/organization, meet with agency/organization representatives to
review specific requirements. All Contractor travel costs associated
with this meeting shall be borne by the Contractor.

CC.11.2 *Inventory Replenishment:* The Contractor shall provide the
following inventory replenishment options:

a)  Automatic replenishment; and

b)  Toll free or collect telephone line reorder capability; and 24 hour
    replenishment when requested by the A/OPC.

CC.11.3 *Bank Check Design:* The Government will provide a background
bank check design(s) to be used under this contract. The Government may
utilize more than one background design for control purposes. The
Contractor shall be responsible for the encoding and printing of the
checks. The final bank check model(s) shall be submitted to the GSA
Contracting Officer within **2 weeks** of contract award for written
approval. The Contractor, at its expense, shall immediately correct and
replace any bank checks issued that contain Contractor-errors. The
Contractor shall ensure that checks are sequentially pre-numbered with
the following standard pre-printed information:

-   United States Government;

-   Name of agency/organization, as directed by the ordering agency,
    including appropriate agency/organization component;

-   For Official Use Only; and

-   US Government Tax Exempt.

***AGENCY REPORTING REQUIREMENTS***

## CC.12 PURCHASE CARD PROGRAM REPORTING REQUIREMENTS

In addition to the requirements specified in C.38, Agency Reporting
Requirements, the Contractor shall also provide the data listed in this
section.

CC.12.1 *Account Activity Report for the Purchase Card Program:* This
report includes complete account activity, both active and inactive, and
includes a roll-up section. It includes bank check transactions. It
reports current and fiscal year account activity. It segregates charges
and credits by individual or agency/organization accounts with current
period totals of the data elements identified. It includes merchant
information such as name, address, TIN, merchant category code, etc.

CC.12.2 *Statistical Summary Report for the Purchase Card Program:* This
report lists dollar volume, bank check volume, number of transactions,
active cardholders, total number of accounts, new accounts,
miscellaneous fees and identification of fees (e.g., fees for customized
services, fees for bank checks, fees for value-added products and
services, etc.) on a current and fiscal year basis.

CC.12.3 *Summary Quarterly Purchase Report:* This report provides a
summary of purchases under and over \$2,500. It includes number of
transactions and the dollar volume for the reporting period of purchases
under and over \$2,500 and comparative percentages.

**END OF REQUIREMENTS SPECIFIC TO THE PURCHASE CARD PROGRAM**

**CONCLUSION OF PERFORMANCE WORK STATEMENT (SECTION C)**

# CONTRACT TERMS AND CONDITIONS\-- COMMERCIAL ITEMS (MAY 1997) 52.212-4

a)  Inspection/Acceptance. The Contractor shall only tender for
    acceptance those items that conform to the requirements of this
    contract. The Government reserves the right to inspect or test any
    supplies or services that have been tendered for acceptance. The
    Government may require repair or replacement of nonconforming
    supplies or reperformance of nonconforming services at no increase
    in contract price. The Government must exercise its post-acceptance
    rights (1) within a reasonable time after the defect was discovered
    or should have been discovered; and (2) before any substantial
    change occurs in the condition of the item, unless the change is due
    to the defect in the item.

b)  ~~Assignment. The Contractor or its assignee\'s rights to be paid
    amounts due as a result of performance of this contract, may be
    assigned to a bank, trust company, or other financing institution,
    including any Federal lending agency in accordance with the
    Assignment of Claims Act (31 U.S.C. 3727).~~ **Assignments will not
    be permitted.\
    **

c)  ~~Changes. Changes in the terms and conditions of this contract may
    be made only by written agreement of the parties.~~

d)  Disputes. This contract is subject to the Contract Disputes Act of
    1978, as amended (41 U.S.C. 601-613). Failure of the parties to this
    contract to reach agreement on any request for equitable adjustment,
    claim, appeal or action arising under or relating to this contract
    shall be a dispute to be resolved in accordance with the clause at
    FAR 52.233-1, Disputes, which is incorporated herein by reference.
    The Contractor shall proceed diligently with performance of this
    contract, pending final resolution of any dispute arising under the
    contract.

e)  Definitions. The clause at FAR 52.202-1, Definitions, is
    incorporated herein by reference.

f)  Excusable delays. The Contractor shall be liable for default unless
    nonperformance is caused by an occurrence beyond the reasonable
    control of the Contractor and without its fault or negligence such
    as, acts of God or the public enemy, acts of the Government in
    either its sovereign or contractual capacity, fires, floods,
    epidemics, quarantine restrictions, strikes, unusually severe
    weather, and delays of common carriers. The Contractor shall notify
    the Contracting Officer in writing as soon as it is reasonably
    possible after the commencement of any excusable delay, setting
    forth the full particulars in connection therewith, shall remedy
    such occurrence with all reasonable dispatch, and shall promptly
    give written notice to the Contracting Officer of the cessation of
    such occurrence.

g)  ~~Invoice. The Contractor shall submit an original invoice and three
    copies (or electronic invoice, if authorized,) to the address
    designated in the contract to receive invoices. An invoice must
    include---\
    \
    (1) Name and address of the Contractor;\
    \
    (2) Invoice date;\
    \
    (3) Contract number, contract line item number and, if applicable,
    the order number;\
    \
    (4) Description, quantity, unit of measure, unit price and extended
    price of the items delivered;\
    \
    (5) Shipping number and date of shipment including the bill of
    lading number and weight of shipment if shipped on Government bill
    of lading;\
    \
    (6) Terms of any prompt payment discount offered;\
    \
    (7) Name and address of official to whom payment is to be sent;
    and~~\
    \
    ~~(8) Name, title, and phone number of person to be notified in
    event of defective invoice. Invoices will be handled in accordance
    with the Prompt Payment Act (31 U.S.C. 3903) and Office of
    Management and Budget (OMB) Circular A-125, Prompt Payment.
    Contractors are encouraged to assign an identification number to
    each invoice~~. **Invoice requirements are specified in C.35.7.3,
    Invoices; CA.10.1, Invoices for the Fleet Card Program and CB.11.3,
    Invoices for Centrally Billed Travel Card Accounts.**

h)  Patent indemnity. The Contractor shall indemnify the Government and
    its officers, employees and agents against liability, including
    costs, for actual or alleged direct or contributory infringement of,
    or inducement to infringe, any United States or foreign patent,
    trademark or copyright, arising out of the performance of this
    contract, provided the Contractor is reasonably notified of such
    claims and proceedings.

i)  Payment. Payment shall be made for items accepted by the Government
    that have been delivered to the delivery destinations set forth in
    this contract. The Government will make payment in accordance with
    the Prompt Payment Act (31 U.S.C. 3903) and Office of Management and
    Budget (OMB) Circular A-125, Prompt Payment. Unless otherwise
    provided by an addendum to this contract, the Government shall make
    payment in accordance with the clause at FAR 52.232-33, Mandatory
    Information for Electronic Funds Transfer Payment, which is
    incorporated herein by reference. In connection with any discount
    offered for early payment, time shall be computed from the date of
    the invoice. For the purpose of computing the discount earned,
    payment shall be considered to have been made on the date which
    appears on the payment check or the specified payment date if an
    electronic funds transfer payment is made.

j)  Risk of loss. Unless the contract specifically provides otherwise,
    risk of loss or damage to the supplies provided under this contract
    shall remain with the Contractor until, and shall pass to the
    Government upon:

    ~~(1) Delivery of the supplies to a carrier, if transportation is
    f.o.b. origin; or~~

    ~~(2) Delivery of the supplies to the Government at the destination
    specified in the contract, if transportation is f.o.b.
    destination~~.

k)  Taxes. The contract price includes all applicable Federal, State,
    and local taxes and duties.

l)  Termination for the Government\'s convenience. The Government
    reserves the right to terminate this contract, or any part hereof,
    for its sole convenience. In the event of such termination, the
    Contractor shall immediately stop all work hereunder and shall
    immediately cause any and all of its suppliers and subcontractors to
    cease work. Subject to the terms of this contract, the Contractor
    shall be paid a percentage of the contract price reflecting the
    percentage of the work performed prior to the notice of termination,
    plus reasonable charges the Contractor can demonstrate to the
    satisfaction of the Government using its standard record keeping
    system, have resulted from the termination. The Contractor shall not
    be required to comply with the cost accounting standards or contract
    cost principles for this purpose. This paragraph does not give the
    Government any right to audit the Contractor\'s records. The
    Contractor shall not be paid for any work performed or costs
    incurred which reasonably could have been avoided.

m)  Termination for cause. The Government may terminate this contract,
    or any part hereof, for cause in the event of any default by the
    Contractor, or if the Contractor fails to comply with any contract
    terms and conditions, or fails to provide the Government, upon
    request, with adequate assurances of future performance. In the
    event of termination for cause, the Government shall not be liable
    to the Contractor for any amount for supplies or services not
    accepted, and the Contractor shall be liable to the Government for
    any and all rights and remedies provided by law. If it is determined
    that the Government improperly terminated this contract for default,
    such termination shall be deemed a termination for convenience.

n)  ~~Title. Unless specified elsewhere in this contract, title to items
    furnished under this contract shall pass to the Government upon
    acceptance, regardless of when or where the Government takes
    physical possession.~~ ~~\
    ~~

o)  Warranty. The Contractor warrants and implies that the items
    delivered hereunder are merchantable and fit for use for the
    particular purpose described in this contract.

p)  ~~Limitation of liability. Except as otherwise provided by an
    express or implied warranty, the Contractor will not be liable to
    the Government for consequential damages resulting from any defect
    or deficiencies in accepted items.\
    ~~

q)  Other compliances. The Contractor shall comply with all applicable
    Federal, State and local laws, executive orders, rules and
    regulations applicable to its performance under this contract.

r)  Compliance with laws unique to Government contracts. The Contractor
    agrees to comply with 31 U.S.C. 1352 relating to limitations on the
    use of appropriated funds to influence certain Federal contracts; 18
    U.S.C. 431 relating to officials not to benefit; 40 U.S.C 327, et
    seq., Contract Work Hours and Safety Standards Act; 41 U.S.C. 51-58,
    Anti-Kickback Act of 1986; 41 U.S.C. 251 related to whistle blower
    protections; and 49 U.S.C 40118, Fly America.

s)  Order of precedence. Any inconsistencies in this solicitation or
    contract shall be resolved by giving precedence in the following
    order: (1) the schedule of supplies/services; (2) the
    ~~Assignments,~~ Disputes, Payments, ~~Invoice,~~ Other Compliances,
    and Compliance with Laws Unique to Government Contracts paragraphs
    of this clause; (3) the clause at 52.212-5; (4) addenda to this
    solicitation or contract, including any license agreements for
    computer software; (5) solicitation provisions if this is a
    solicitation; (6) other paragraphs of this clause; (7) the Standard
    Form 1449; (8) other documents, exhibits, and attachments; and (9)
    the specification.

# ADDENDUM TO CLAUSE 52.212-4

**ADDITIONAL COMMERCIAL ITEM CONTRACT TERMS AND CONDITIONS**

## 1. WOMEN OWNED BUSINESS: 52.204-5 (OCT 1995) 

## 

\(a\) Representation. The offer represents that it \[\_\_\_\] is,
\[\_\_\_\] is not a women-owned business concern.

\(b\) Definition. "Women-owned business concern," as used in this
provision, means a concern which is at least 51 percent owned by one or
more women; or in the case of any publicly owned business, at least 51
percent of the stock which is owned by one or more women; and whose
management and daily business operations are controlled by one or more
women.

## 2. PLACE OF PERFORMANCE: 52.215-20 (APR 1984)

\(a\) The offeror or quoter, in the performance of any contract
resulting from this solicitation, \[\_\_\_\] intends,

\(b\) \[\_\_\_\] does not intend (check applicable block) to use one or
more plants or facilities located at a different address from the
address of the offeror or quoter as indicated in this proposal or
quotation.

\(c\) If the offeror or quoter checks \"intends\" in paragraph (a)
above, it shall insert in the spaces provided below the required
information:

Place of Performance and Operator of the Plan or Facility

Name and Address of Owner if Other than Offeror or Quoter

(Street, Address, City, County, State, Zip Code)

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

## 3. SMALL BUSINESS PROGRAM REPRESENTATION: 52.219-1 (JAN 1997) 

## 

(a)(1) The standard industrial classification (SIC) code for this
acquisition is 7389 and 6099 for the Travel Card Program, and 6153 for
the Fleet and Purchase Card Programs.

\(2\) The small business size standard is \$3.5 million for SIC Codes
7389 and 6099, and \$100 million for SIC Code 6153.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\(3\) The small business size standard for a concern which submits an
offer in its own name, other than on a construction or service contract,
but which proposes to furnish a product which it did not itself
manufacture, is 500 employees.

\(b\) Representations.

\(1\) The offeror represents as part of its offer that it \[\_\_\_\] is,
\[\_\_\_\] is not a small business concern.

\(2\) (Complete only if offeror represented itself as a small business
concern in block (b)(1) of this section.) The offeror represents as part
of its offer that it \[\_\_\_\] is, \[\_\_\_\] is not a small
disadvantaged business concern.

\(3\) (Complete only if offeror represented itself as a small business
concern in block (b)(1) of this section.) The offeror represents as part
of its offer that it \[\_\_\_\] is, \[\_\_\_\] is not a women-owned
small business concern.

\(c\) Definitions. \"Joint venture,\" for purposes of a small
disadvantaged business (SDB) set-aside or price evaluation preference
(as prescribed at 13 CFR 124.321), is a concern that is owned and
controlled by one or more socially and economically disadvantaged
individuals entering into a joint venture agreement with one or more
business concerns and is considered to be affiliated for size purposes
with such other concern(s). The combined annual receipts or employees of
the concerns entering into the joint venture must meet the applicable
size standard corresponding to the SIC code designated for the contract.
The majority of the venture\'s earnings must accrue directly to the
socially and economically disadvantaged individuals in the SDB
concern(s) in the joint venture. The percentage of the ownership
involvement in a joint venture by disadvantaged individuals must be at
least 51 percent.

> \"Small business concern,\" as used in this provision, means a
> concern, including its affiliates, that is independently owned and
> operated, not dominant in the field of operation in which it is
> bidding on Government contracts, and qualified as a small business
> under the criteria in 13 CFR Part 121 and the size standard in
> paragraph (a) of this provision.
>
> \"Small disadvantaged business concern,\" as used in this provision,
> means a small business concern that (1) is at least 51 percent
> unconditionally owned by one or more individuals who are both socially
> and economically disadvantaged, or a publicly owned business having at
> least 51 percent of its stock unconditionally owned by one or more
> socially and economically disadvantaged individuals, and (2) has its
> management and daily business controlled by one or more such
> individuals. This term also means a small business concern that is at
> least 51 percent unconditionally owned by an economically
> disadvantaged Indian tribe or Native Hawaiian Organization, or a
> publicly owned business having at least 51 percent of its stock
> unconditionally owned by one or more of these entities, which has its
> management and daily business controlled by members of an economically
> disadvantaged

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> Indian tribe or Native Hawaiian Organization, and which meets the
> requirements of 13 CFR Part 124.
>
> \"Woman-owned small business concern,\" as used in this provision,
> means a small business concern\--
>
> \(1\) Which is at least 51 percent owned by one or more women or, in
> the case of any publicly owned business, at least 51 percent of the
> stock of which is owned by one or more women; and
>
> \(2\) Whose management and daily business operations are controlled by
> one or more women.

\(d\) Notice.

\(1\) If this solicitation is for supplies and has been set aside, in
whole or in part, for small business concerns, then the clause in this
solicitation providing notice of the set-aside contains restrictions on
the source of the end items to be furnished.

\(2\) Under 15 U.S.C. 645(d), any person who misrepresents a firm\'s
status as a small or small disadvantaged business concern in order to
obtain a contract to be awarded under the preference programs
established pursuant to sections 8(a), 8(d), 9, or 15 of the Small
Business Act or any other provision of Federal law that specifically
references section 8(d) for a definition of program eligibility,
shall\--

> \(I\) Be punished by imposition of fine, imprisonment, or both;
>
> \(ii\) Be subject to administrative remedies, including suspension and
> debarment; and
>
> \(iii\) Be ineligible for participation in programs conducted under
> the authority of the Act.

## 4. OPTION TO EXTEND THE TERM OF THE CONTRACT: 52.217-9 (MAR 1989) Deviation

## 

\(a\) The Government may extend the term of this contract by written
notice to the Contractor within 30 days prior to expiration of the
contract; *provided,* that the Government shall give the Contractor a
preliminary written notice of the intent to extend at least 60 days
before the contract expires. The preliminary notice does not commit the
Government to an extension.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\(b\) If the Government exercises this option, the extended contract
shall be considered to include this option provision.

\(c\) The total duration of this contract, including any options under
this clause, shall not exceed 10 years. This clause may be exercised
repeatedly for periods of two months to two years, provided that the
total contract period does not exceed 10 years.

## 5. AVAILABILITY OF FUNDS FOR TASK ORDERS: CITC-FCXC-\_\_\_ (MAY 1997)42.903

Funds are not presently available for any task orders placed under this
contract. The Government's obligation under this contract is contingent
upon the availability of appropriated funds from which payment for task
order purposes can be made. No legal liability on the part of the
Government for any payment may arise until funds are available to the
ordering Contracting Officer for the agency/organization task order and
until the Contractor receives notice of such availability, to be
confirmed in writing by the ordering Contracting Officer.

## 6. BANKRUPTCY: (DEVIATION) 52.242-13 (JUL 1995)42.903

In the event the Contractor enters into proceedings relating to
bankruptcy, whether voluntary or involuntary, the Contractor agrees to
furnish, by certified mail or electronic commerce method authorized by
the contract, written notification of the bankruptcy to the Contracting
Officer responsible for administering the contract. This notification
shall be furnished immediately upon the initiation of the proceedings
relating to bankruptcy filing. This notification shall include the date
on which the bankruptcy petition was filed, the identity of the court in
which the bankruptcy petition was filed, and a listing of Government
contract numbers and contracting offices for all Government contracts
against which final payment has not been made. This obligation remains
in effect until final payment under this contract.

## 7. AUTHORIZED DEVIATIONS OR VARIATIONS IN CLAUSES: 552.252-6 (DEVIATION FAR 52.252-6) (JUL 1985) 

## 

\(a\) The use in this solicitation or contract of any Federal
Acquisition Regulation (48 CFR Chapter 1) clause with an authorized
deviation or variation is indicated by the addition of \"(DEVIATION)\"
or \"(VARIATION)\" after the date of the clause, if the clause is not
published in the General Services Administration Acquisition Regulation
(48 CFR Chapter 5). The use in this solicitation of any Federal
Acquisition Regulation (FAR) clause with an authorized deviation or
variation that is published in the General Services Administration
Acquisition Regulation is indicated by the addition of \"(DEVIATION (FAR
clause no.))\" or \"(VARIATION (FAR clause no.))\" after the date of the
clause.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\(b\) The use is this solicitation of any General Services
Administration Acquisition Regulation clause with an authorized
deviation or variation is indicated by the addition of \"(DEVIATION) or
\"(VARIATION)\" after the date of the clause.

\(c\) Changes in wording of clauses that are prescribed for use on a
\"substantially the same as\" basis are not considered deviations.
Therefore, when such clauses are not worded exactly the same as the FAR
or GSAR clause, they are identified by the word \"(VARIATION)\" after
the date of the clause.

##  8. REQUIREMENTS FOR COST OR PRICING DATA OR INFORMATION OTHER THAN COST OR PRICING DATA: 52.215-41 (MAR 1997) ALTERNATE IV (OCT 1995)

\(a\) Submission of cost or pricing data is not required.

\(b\) Provide information described below:

\(1\) An offer prepared and submitted in accordance with the provision
at the Instructions to Offerors section, paragraph 14, Submission of
Proposals;

\(2\) Information regarding the offeror's commercial pricing practices
submitted in the format provided in this solicitation in accordance with
the instructions in the solicitation; and

\(3\) Any additional supporting information requested by the Contracting
Officer to determine whether the price(s) offered is fair and
reasonable.

\(4\) By submission of an offer in response to this solicitation or a
request for modification, the offeror grants the Contracting Officer or
an authorized representative the right to examine, at any time before
award, books, records, documents, papers, and other directly pertinent
records to verify any request for and exception to the requirement for
cost or pricing data, and the reasonableness of price(s) to verify that
the information submitted was complete, current and accurate. Access
does not extend to cost or profit information or other data relevant
solely to the offeror\'s determination of the prices to be offered in
the catalog or marketplace.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 9. REQUIREMENTS FOR COST OR PRICING DATA OR INFORMATION OTHER THAN COST OR PRICING DATA---MODIFICATIONS: 52.215-42 (JAN 1997) (ALTERNATE IV---JAN 1997) 

\(a\) Submission of cost or pricing data is not required.

\(b\) Provide information described below.

> Information required shall be in accordance with the provisions of
> clause REQUIREMENTS FOR COST OR PRICING DATA OR INFORMATION OTHER THAN
> COST OR PRICING DATA clause found elsewhere in this solicitation.

## 10. TYPE OF CONTRACT: 52.216-1 (APR 1984) 

The Government contemplates award of a Fixed Price Indefinite Delivery,
Indefinite Quantity (IDIQ) contracts resulting from this solicitation.

## 11. INDEFINITE QUANTITY: 52.216-22 (OCT 1995) (VARIATION---OCT 1995)

\(a\) This is an indefinite-quantity contract for the supplies or
services specified, and effective for the period stated. The quantities
of supplies and services specified in the contract are estimates only
and are not purchased by this contract.

\(b\) Delivery or performance shall be made only as authorized by orders
issued in accordance with the Ordering clause. The Contractor shall
furnish to the Government, when and if ordered, the supplies or services
specified in the contract. The Government shall order at least the
quantity of supplies or services designated in the contract as the
\"minimum.\"

\(c\) Except for any limitations on quantities in the Guaranteed Minimum
clause or Order Limitations clause, there is no limit on the number of
orders that may be issued. The Government may issue orders requiring
delivery to multiple destinations or performance at multiple locations.

\(d\) Any order issued during the effective period of this contract and
not completed within that period shall be completed by the Contractor
within the time specified in the order. The contract shall govern the
Contractor\'s and Government\'s rights and obligations with respect to
that order to the same extent as if the order were completed during the
contract\'s effective period.

## 12. SINGLE OR MULTIPLE AWARDS: 52.216-27 (OCT 1995) 16.506(f)

The Government may elect to award a single delivery order contract or
task order contract or to award multiple delivery order contracts or
task order contracts for the same or similar supplies or services to two
or more sources under this solicitation.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 13. NOTICE TO THE GOVERNMENT OF LABOR DISPUTES: 52.222-1 (FEB 1997) 

If the Contractor has knowledge that any actual or potential labor
dispute is delaying or threatens to delay the timely performance of this
contract, the Contractor shall immediately give notice, including all
relevant information, to the Contracting Officer.

## 14. INTEREST: 52.232-17 (JUN 1996) 

\(a\) Except as otherwise provided in this contract under a Price for
Defective Cost or Pricing Data clause or a Cost Accounting Standards
clause, all amounts that become payable by the Contractor to the
Government under this contract (net of any applicable tax credit under
the Internal Revenue Code (26 U.S.C. 1481)) shall bear simple interest
from the date due until paid unless paid within 30 days of becoming due.
The interest rate shall be the interest rate established by the
Secretary of the Treasury as provided in Section 12 of the Contract
Disputes Act of 1978 (Public Law 95‑563), which is applicable to the
period in which the amount becomes due, as provided in paragraph (b) of
this clause, and then at the rate applicable for each six‑month period
as fixed by the Secretary until the amount is paid.

\(b\) Amounts shall be due at the earliest of the following dates:

\(1\) The date fixed under this contract.

\(2\) The date of the first written demand for payment consistent with
this contract, including any demand resulting from a default
termination.

\(3\) The date the Government transmits to the Contractor a proposed
supplemental agreement to confirm completed negotiations establishing
the amount of debt.

\(4\) If this contract provides for revision of prices, the date of
written notice to the Contractor stating the amount of refund payable in
connection with a pricing proposal or a negotiated pricing agreement not
confirmed by contract modification.

\(c\) The interest charge made under this clause may be reduced under
the procedures prescribed in 32.614‑2 of the Federal Acquisition
Regulation in effect on the date of this contract.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 15. F.O.B. DESTINATION: FSS-FCXB-100 (MAR 1997)

\(a\) The term \"f.o.b. destination,\" means---Free of expense to the
Government delivered and laid down within the doors of the consignee's
premises, including delivery to specific rooms within a building if so
specified.

\(b\) The Contractor shall:

> 1\. Prepare the shipment in conformance with standard commercial
> practice;
>
> 2\. Deliver the shipment in good order and condition to the point of
> delivery specified in the task order or master contract;
>
> 3\. Be responsible for any loss of and/or damage to the goods
> occurring before receipt of the shipment by the consignee at the
> delivery point specified in the task order or master contract;
>
> 4\. Pay and bear all charges to the specified point of delivery.

\(c\) The Contractor shall be responsible for mailing and shipping costs
including costs for overnight or express mail deliveries.

## 16. CONTRACT TERMS AND CONDITIONS APPLICABLE TO GSA ACQUISITION OF COMMERCIAL ITEMS: 552.212-71 (FEB 1996)

The Contractor agrees to comply with any provision or clause that is
incorporated herein by reference to implement agency policy applicable
to acquisition of commercial items or components. The provision or
clause in effect based on the applicable regulation cited on the date
the solicitation is issued applies unless otherwise stated herein. The
following provisions and clauses are incorporated by reference:

\*[   X   ]{.underline}\* 552.203-70 Restriction on Advertising

\*\_\_\_\_\_\* 552.211-73 Marking

\*[   X   ]{.underline}\* 552.215-70 Examination of Records by GSA

\*\_\_\_\_\_\* 552.215-71 Examination of Records by GSA (Multiple Award
Schedule)

\*[   X   ]{.underline}\* 552.215-72 Price Adjustment for Incomplete,
Not Current or Inaccurate

Information Other Than Cost or Pricing Data

\*\_\_\_\_\_\* 552.219-71 Allocation of Orders---Partially Set-Aside
Items

\*\_\_\_\_\_\* 552.228-75 Workmen\'s Compensation

\*[   X   ]{.underline}\* 552.229-70 Federal, State, and Local Taxes

\*[   X   ]{.underline}\* 552.232-8 Discounts for Prompt Payment

\*\_\_\_\_\_\* 552.232-23 Assignment of Claims

\*[   X   ]{.underline}\* 552.232-70 Payments by Electronic Funds
Transfer

\*[   X   ]{.underline}\* 552.232-77 Availability of Funds

\*\_\_\_\_\_\* 552.232-78 Adjusting Payments

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\*\_\_\_\_\_\* 552.232-79 Final Payment

\*\_\_\_\_\_\* 552.237-70 Qualifications of Offerors

\*\_\_\_\_\_\* 552.237-71 Qualifications of Employees

\*\_\_\_\_\_\* 552.238-72 Contractor\'s Report of Sales

\*\_\_\_\_\_\* 552.238-74 Submission and Distribution of Authorized FSS
Schedule

Price List

\*\_\_\_\_\_\* 552.238-76 Price Reductions

\*\_\_\_\_\_\* 552.242-70 Status Report of Orders and Shipments

\*\_\_\_\_\_\* 552.243-72 Modifications (Multiple Award Schedule)

\*\_\_\_\_\_\* 552.246-73 Warranty---Multiple Award Schedule

\*\_\_\_\_\_\* 552.246-76 Warranty of Pesticides

## 17. CONTRACTOR'S REPORT OF SALES: 552.238-72 (APR 1995)

> \(a\) Contractors shall furnish program data as specified in C.39, GSA
> Contracting Office Reports, subparagraph b), Program Report, to
> satisfy this requirement for report of sales.
>
> \(b\) The Government reserves the right to inspect without further
> notice, such records of the Contractor as pertain to sales under any
> contract resulting from this solicitation. Willful failure or refusal
> to furnish the required reports, or falsification thereof, shall
> constitute sufficient cause for terminating the contract for default
> under FAR 52.212‑4, subparagraph m) Termination for Cause.

## 18. INDUSTRIAL FUNDING FEE (IFF): CITC-FCXC-\_\_\_ (MAY 1997)

The Contractor shall provide a proposal which will provide each entity
in the agency/organization a financial refund, in basis points, based on
net charge volume (net charge volume is defined as all revenue producing
transactions/volumes and excludes credits and adjustments), and paid
directly to the agency/organization level, except as described below.
The Contractor shall ensure that the financial refund offered to each
agency/organization level fully covers GSA's IFF, for each business line
offered.

The Contractor shall withhold four (4) basis points of the
agency/organization level's financial refund under each business line
ordered and shall remit the four (4) basis points of the
agency's/organization's and level's net charge volume to GSA by the
**10th of each fiscal year quarter** to industrially fund the program.
This is GSA's Industrial Funding Fee (IFF) and serves to cover GSA's
costs in administering the program(s). GSA reserves the right to revise
up or down the industrial funding fee during the contract period not to
exceed 6 basis points of an

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

agency's/organization's and level's net charge volume for each business
line. Any such revision to the IFF will be based upon GSA's review of
program volume growth, expense in administering the program,
agency/organization participation, etc. This review is done twice each
fiscal year. The Contractor shall have the ability to revise the IFF
accordingly. The Contractor shall remit GSA's IFF electronically, as
directed.

## 19. PRICE REDUCTIONS: 552.238-76 (OCT 1994)

On or after the effective date of this contract, the Contractor may at
any time reduce the contract price for any or all of the service(s) to
the Government either temporarily or permanently. Any price reduction
offered by a contractor shall be for a minimum of 30 days. Any such
reduction in the contract price shall be effective upon execution of a
bilateral contract modification specifying the price and the period the
price is in effect.

## 20. MODIFICATIONS (MASTER CONTRACTS): CITC-FCXC-\_\_\_ (MAY 1997)

\(a\) General. The Contractor may request a contract modification by
submitting a request to the GSA Contracting Officer for approval, except
as noted in paragraph (e) of this clause. A separate request should be
submitted for each type of proposed modification. At a minimum, every
request shall describe the proposed change(s) and provide the rationale
for the requested change(s).

\(b\) Types of Modifications:

> \(1\) Additional items or services within a business line:
>
> \(i\) A request for an exemption from the requirement to submit cost
> and pricing data shall be provided. To add items or services, submit
> the request to the GSA Contracting Officer.
>
> \(ii\) Price information for the new item(s) or new services must be
> provided. Specifically, submit the following information: Name of
> item/service, evidence of commercial selling price, and price offered
> to the Government.
>
> \(iii\) A full description of the new items or services must be
> provided.
>
> \(2\) Additional Business Line. The contractor may not offer any new
> business lines.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> \(3\) Deletions. The Contractor(s) may delete a product or service
> under a Contract Line Item Number with GSA Contracting Officer
> approval. The Contractor(s) shall provide an explanation for the
> deletion (e.g., obsolete technology, etc.). The Government reserves
> the right to reject any subsequent offer of the same item or a
> substantially equal item at a higher price during the same contract
> period, if the GSA Contracting Officer finds the higher price to be
> unreasonable when compared with the deleted item.

\(c\) Effective dates. The effective date of any modification is the
date specified in the modification, except as otherwise provided in the
Price Reduction clause at 552.238‑76.

\(d\) Electronic file updates. The Contractor shall update electronic
file submissions to reflect all modifications. Except for price
reductions and corrections, the Contractor shall obtain the GSA
Contracting Officer\'s approval before transmitting changes. Contract
modifications will not be made effective until updates to electronic
files are received. Price reductions and corrections may be transmitted
after a modification to the master contract is issued in accordance with
the Price Reduction Clause at 552.238-76.

\(e\) Notification of Master Contract Modification to
Agencies/Organizations: The Contractor shall distribute a notification
to participating agencies/organizations that reflects accepted changes
within 15 days after the effective date of the modification. At a
minimum, distribution shall be made to these ordering activities
utilizing the service which changed. In addition, five copies of the
supplemental information publication shall be submitted to the ordering
contracting officer.

## 21. ORDER LIMITATIONS: CITC-FCXC-\_\_\_ (MAY 1997) 

\(a\) Minimum order. When the Government requires supplies or services
covered by this contract in an amount of less than that specified in the
addendum to 52.212-4, paragraph 38, Ordering, subparagraphs 38.4 and
38.5, the Government is not obligated to purchase, nor is the Contractor
obligated to furnish, those supplies or services under the contract.
However, offerors may, if willing to accept smaller orders, specify a
smaller amount in their offers. If a smaller amount is offered, it is
mutually agreed that the Contractor will accept such orders and specify
the smaller minimum order limitation in the applicable contractor
publications. If the offeror fails to specify a smaller amount, the
Government may place orders for a smaller amount. Such orders shall be
deemed to be accepted by the Contractor, unless returned to the ordering
office within 5 workdays after receipt by the Contractor.

\(b\) Maximum transaction order. The maximum order per transaction will
be negotiated individually for each master contract. The Contractor may,
but is not obligated to honor any single transaction when the dollar
value exceeds \$500,000 per single transaction.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\(c\) Total orders placed against all master contracts shall not exceed
\$20 trillion dollars over ten (10) years (5-year base period and five
(5) 1-year option periods).

## 22. CHANGES---FIXED-PRICE: 52.243-1 (AUG 1987) 43.205(a)(1)

\(a\) The Contracting Officer may at any time, by written order, and
without notice to the sureties, if any, make changes within the general
scope of this contract in any one or more of the following:

\(1\) Description of services to be performed.

\(2\) Time of performance (i.e., hours of the day, days of the week,
etc.).

\(3\) Place of performance of the services.

\(4\) Drawings, designs, or specifications when the supplies to be
furnished are to be specially manufactured for the Government in
accordance with the drawings, designs, or specifications.

\(5\) Method of shipment or packing.

\(6\) Place of delivery.

\(b\) If any such change causes an increase or decrease in the cost of,
or the time required for, performance of any part of the work under this
contract, whether or not changed by the order, the Contracting Officer
shall make an equitable adjustment in the contract price, the delivery
schedule, or both, and shall modify the contract.

\(c\) The Contractor must assert its right to an adjustment under this
clause within 30 days from the date of receipt of the written order.
However, if the Contracting Officer decides that the facts justify it,
the Contracting Officer may receive and act upon a proposal submitted
before final payment of the contract.

\(d\) If the Contractor\'s proposal includes the cost of property made
obsolete or excess by the change, the Contracting Officer shall have the
right to prescribe the manner of the disposition of the property.

\(e\) Failure to agree to any adjustment shall be a dispute under the
Disputes clause. However, nothing in this clause shall excuse the
Contractor from proceeding with the contract as changed.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 23. SCOPE OF CONTRACT FOR THE FLEET CARD: CITC-FCXC-\_\_\_ (MAY 1997)

This contract is to provide a fuel/maintenance fleet card and associated
services.

a\) Mandatory Users: The entities listed in Exhibit 9 have committed to
be mandatory users of the fleet card contract.

b\) Non-Mandatory Users: The following activities are authorized to use
this contract on a non-mandatory basis:

1\) Any executive agency (as defined in 40 U.S.C. 472 (executive
departments or independent establishments in the executive branch of the
Government, including wholly owned Government corporations)) not listed
in Exhibit 9, and except those entities specified in subparagraph 9);

2\) The United States Postal Service;

3\) The Tennessee Valley Authority;

4\) Federal agencies, as defined in 40 U.S.C. 472, not specified in a)
above;

5\) Non-appropriated fund instrumentalities;

6\) Government cost-reimbursable contractors when authorized in writing
by a federal agency pursuant to 48 CFR 51.102;

7\) Mixed-ownership Government corporations as defined in 31 U.S.C.
9101;

8\) The Government of the District of Columbia; and

9\) Organizational units of executive agencies located outside the 50
states and the District of Columbia.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 24. SCOPE OF CONTRACT FOR TRAVEL CARD: CITC-FCXC-\_\_\_ (MAY 1997)

## 

This contract is to provide a travel payment card and associated
services.

a\) Mandatory Users: There are two categories of mandatory users as
described below:

1\) Category 1: The mandatory users in this category may request and are
eligible for any combination of individually billed cards and centrally
billed accounts and are permitted to participate in the City Pair
Program and receive city pair rates. Except as otherwise provided in
Category 2 below, mandatory users for the master contract are listed in
Exhibit 10.

2\) Category 2: The mandatory users in this category are eligible for
centrally billed accounts but are not eligible for individual cards:
Employees of a tribal organization when performing travel necessary to
carry out a contract, grant, or cooperative agreement under the Indian
Self-Determination and Economic Assistance Act when such tribal
organization has been added to the master contract as a mandatory user
by the GSA Contracting Officer pursuant to this clause. Each eligible
tribal organizations will be added individually as a mandatory user by
the GSA Contracting Officer (in writing to the Master contractors) at
the sole discretion of the Government and at no additional cost to the
Government.

\(a\) Prior to the GSA Contracting Officer adding a tribal organization
as a mandatory user, the tribal organization will be required to provide
an adequate guarantee of payment in one of the following manners:

> \(i\) A limited waiver of sovereign immunity providing the contractor
> the right to sue for payment;
>
> \(ii\) A payment bond equal to 100% of the estimated monthly usage;
>
> \(iii\) Prepayment of the estimated first three months invoices; or
>
> \(iv\) Another guarantee acceptable to the tribal organization and the
> contractor.

\(b\) If, at any time during the contract, the tribal organization
ceases having a contract, grant, or cooperative agreement under the
Indian Self-Determination Act, such a tribal organization shall cease
being eligible to use the Master Contract. If the tribal organization
subsequently enters into a new contract, grant, or cooperative agreement
under the Indian Self Determination Act, the GSA Contracting Officer may
again authorize the tribal organization as a mandatory user.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

b\) Non-Mandatory Users: There are two categories of non-mandatory users
as described below:

1\) Category 1: The non-mandatory users in this category may request and
are eligible for any combination of individually billed cards and
centrally billed accounts are permitted to participate in the City Pair
Program and receive city pair rates:

> \(i\) All uniformed personnel and civilian employees of the Department
> of Defense except as listed under subparagraph a)1) above;
>
> \(ii\) Civilian employees of agencies of the U.S. Government as
> defined in 5 U.S.C. 5701 except as listed in subparagraph a)1) above;
> For purposes of this provision, an agency of the U.S. Government as
> defined in 5 U.S.C. 5701 means:
>
> [1]{.underline}. An executive agency (executive department, Government
> corporation owned by the Government of the United States, or an
> independent establishment);
>
> [2]{.underline}. A military department (Department of the Army,
> Department of the Navy, and Department of the Air Force);
>
> [3]{.underline}. An office, agency, or other establishment in the
> legislative branch;
>
> but does not include a Government controlled corporation
> (mixed-ownership Government corporation); a member of Congress; or an
> office or committee of either House of Congress or of the two Houses.
>
> \(iii\) Uniformed members of the U.S. Coast Guard, the Public Health
> Service and the National Oceanic and Atmospheric Administration;
>
> \(iv\) All members and employees of the U.S. Congress; employees of
> the Judicial Branch of the Government; employees of the U.S. Postal
> Service; U.S. Foreign Service Officers; and employees of any agencies
> who are not subject to the provisions of 5 U.S.C. 5701‑09;
>
> \(v\) DOD recruits traveling from Military Entrance Processing
> Stations (MEPS). DOD groups of 21 or more passengers;

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> \(vi\) Employees of the Farm Credit Administration..

2\) Category 2: Non-mandatory users in this category may request a
centrally billed account but are not eligible for individual cards.
Users in this category **ARE** anticipated to generally be permitted to
participate in the City Pair Program and receive the city pair rates.

> \(i\) Persons traveling on behalf of the American Red Cross National
> Sector (except independent contractors and cost reimbursable
> contractors working for the American Red Cross);
>
> \(ii\) Employees of the Government of the Commonwealth of the Northern
> Mariana Islands on official travel;
>
> \(iii\) Employees of the Legal Services Corporation (except grantees);
>
> \(iv\) Employees of the Neighborhood Reinvestment Corporation;
>
> \(v\) Employees of the U.S. Air Force, U.S. Marine Corps, U.S. Navy
> and the U.S. Army non-appropriated fund instrumentalities;*\
> *
>
> \(vi\) Other entities listed as mandatory or non-mandatory users of
> the City Pair Program.

## 24. SCOPE OF CONTRACT FOR PURCHASE CARD: CITC-FCXC-\_\_\_ (MAY 1997)

## 

This contract is to provide a purchase card and associated services.

a\) Mandatory users: The entities listed in Exhibit 11 have committed to
be mandatory users of the purchase card contract.

b\) Non-Mandatory Users: The following activities are authorized to use
this contract on a non-mandatory basis:

1\) Any executive agency (as defined in 40 U.S.C. 472 (executive
departments or independent establishments in the executive branch of the
Government, including wholly owned Government corporations)) not listed
in Exhibit 11;

2\) The United States Postal Service;

3\) The Tennessee Valley Authority;

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

4\) Federal agencies, as defined in 40 U.S.C. 472, not specified in a)
above;

5\) Non-appropriated fund instrumentalities;

6\) Government cost-reimbursable contractors when authorized in writing
by a federal agency pursuant to 48 CFR 51.102;

7\) Mixed-ownership Government corporations as defined in 31 U.S.C.
9101;

8\) The Government of the District of Columbia; and

9\) Organizational units of executive agencies located outside the 50
states and the District of Columbia.

## 26. DEFAULT TASK ORDERS: CITC-FCXC-\_\_\_ (MAY 1997) 

In addition to FAR clause 52.212-4, subparagraph m) Termination for
Cause, the following is applicable to orders placed under this Master
Contract.

Any ordering office may, in respect to any one or more task orders
placed by it under the contract, exercise the same right of termination,
acceptance of inferior articles or services, and assessment of excess
costs as might the GSA Contracting Officer, except that when failure to
deliver articles or services is alleged by the Contractor to be
excusable, the determination of whether the failure is excusable shall
be made only by the GSA Contracting Officer, to whom such allegation
shall be referred by the ordering office and from whose determination
appeal may be taken as provided in the clause of this contract entitled
\"Disputes.\"

## 27. ELECTRONIC COMMERCE\--FACNET: I-FSS-599 (SEP 1995)

> \(a\) [General Background]{.underline}.
>
> The Federal Acquisition Streamlining Act (FASA) of 1994 establishes
> the Federal Acquisition Network (FACNET) requiring the Government to
> evolve its acquisition process from one driven by paperwork into an
> expedited process based on electronic commerce/electronic data
> interchange (EC/EDI). FASA increased the Simplified Acquisition
> Threshold (SAT---formerly is known as \"small purchases\") to
> \$100,000 if an ordering activity is FACNET compliant. The interim
> rules on FACNET were published in the Federal Register on July 3,
> 1995.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> EC/EDI means more than merely automating manual processes and
> eliminating paper transactions. It can and will help to move business
> processes (e.g., procurement, finance, logistics, etc.) into a fully
> electronic environment and fundamentally change the way organizations
> operate.
>
> \(b\) [Trading Partners and Value-Added Networks (VAN's)]{.underline}.
>
> Within the FACNET architecture, electronic documents (e.g., orders,
> invoices, etc.) are carried between the Federal Government\'s
> procuring office and contractors (now known as \"trading partners\").
> These transactions are carried by commercial telecommunications
> companies called Value-Added Networks (VAN's). Federal Government
> transactions are provided only to those VAN's that have been certified
> by DOD and connected to FACNET.
>
> EDI can be done using standard office automation hardware and
> telecommunications. The selection of a VAN is a business decision
> contractors must make. There are many different VAN's which provide a
> variety of electronic services and different pricing strategies. If
> your VAN only provides communications services, you may also need a
> software translation package.
>
> \(c\) [Registration Instructions]{.underline}.
>
> To do EDI with the Government, contractors must register as a trading
> partner with a VAN. contractors will register using an American
> National Standards Institute (ANSI) ANSI X12 838 transaction set,
> called a \"Trading Partner Profile.\" A transaction set is a standard
> method of moving electronic data. VAN's will be able to assist
> contractors with registration. Contractors will provide regular
> business information, banking information, and EDI capabilities to all
> agencies in this single registration. A central repository of all
> trading partners has been developed. All Government procuring offices
> and other interested parties will have access to this central
> repository. The database is structured to identify the types of data
> elements which are public information and those which are confidential
> and not releasable.
>
> A list of certified VAN's and software providers will be available
> from the Department of Defense (DOD) by calling 1(800)EDI-3414, or
> from world wide web at **www.itsi.disa.mil/ctf.**

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> To register, contractors must provide their Dun and Bradstreet (DUNS)
> number. The DUNS number is available by calling 1(800)333-0505. It is
> provided and maintained free of charge and only takes a few minutes to
> obtain. Contractors will need to provide their Tax Identification
> Number (TIN). The TIN is assigned by the Internal Revenue Service by
> calling 1(800)829-1040. Contractors will also be required to provide
> information about company bank or financial institution for electronic
> funds transfer (EFT).
>
> \(d\) [Implementation Conventions]{.underline}.
>
> All EDI transactions must comply with the Federal Implementation
> Conventions (IC's). Many VAN's and software providers have already
> built the IC requirements into their products. If you need to see the
> IC's, they are available on a registry maintained by the National
> Institute of Standards and Technology (NIST). It is accessible via the
> Internet at
>
> **http://snad.ncsl.nist.gov/dartg/edi/fededi.html**.
>
> IC's are available for common business documents such as Purchase
> Order, Price Sales Catalog, Invoice, Request for Quotes, etc.
>
> \(e\) [Additional Information]{.underline}.
>
> For additional information on FACNET, contact the following Government
> Agency:
>
> Federal Electronic Commerce Acquisition\
> Program Management Office (ECA-PMO)\
> 5113 Leesburg Pike, Suite 400\
> Falls Church, VA 22041\
> 703/681-0364 or 0369\
> FAX 703/681-0362 or 0363\
> Electronic Mail: useop@ncr.disa.mil\
> Internet World Wide Web Home Page: http://www.gsa.gov
>
> \(f\) [**GSA** Advantage!]{.underline}.
>
> \(1\) **GSA** *Advantage!* will use this FACNET system to receive
> price lists and send purchase orders. **GSA** *Advantage!* enables
> customers to:
>
> \(i\) Perform database searches across all contracts by Manufacturer,
> Manufacturer's Model/Part Number, and generic Product Categories.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> \(ii\) Generate their own EDI delivery orders to contractors, generate
> EDI delivery orders from the Federal Supply Service to contractors*,*
> or download files to create their own delivery orders.
>
> \(2\) **GSA** *Advantage!* may be accessed via the INTERNET. The
> INTERNET address is: **http://www.gsa.gov.**

## 28. INTERPRETATION OF CONTRACT REQUIREMENTS: I-FSS-965 (APR 1984)

No interpretation of any provision of this contract, including
applicable specifications, shall be binding on the Government unless
furnished or agreed to in writing by the GSA Contracting Officer or his
designated representative.

## 29. ORGANIZATIONAL CONFLICT OF INTEREST: CITC-FCXC-\_\_\_ (MAY 1997)

\(a\) Definitions:

\(1\) "Marketing Consultant" means any independent contractor who
furnishes advice, information, direction, or assistance to an offeror or
any other contractor in support of the preparation or submission of an
offer for a Government contract by that offeror. An independent
Contractor is not a marketing consultant when rendering\--

\(i\) Services excluded in FAR 37.204;

\(ii\) Routine engineering and technical services (such as installation,
operation, or maintenance of systems, equipment, software, components,
or facilities);

\(iii\) Routine legal, actuarial, auditing, and accounting services; or

\(iv\) Training services.

\(2\) Organizational conflict of interest means that because of other
activities ore relationships with other persons, a person is unable or
potentially unable to render impartial assistance or advice to the
Government, or the person's objectivity in performing the contract work
is or might be otherwise impaired, or a person has an unfair competitive
advantage.

\(b\) An individual or firm that employs, retains, or engages
contractually one or more marketing consultants in connection with a
contract, shall submit to the Contracting Officer, with respect to each
marketing consultant, the verifications described below, if the
individual or firm is notified that it is the apparent successful
offeror.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\(c\) The verification must contain the following:

\(1\) The name of the agency and the number of the solicitation in
question.

\(2\) The name, address, telephone number, and federal taxpayer
identification number of the marketing consultant.

\(3\) The name, address, and telephone number of a responsible officer
or employee of the marketing consultant who has personal knowledge of
the marketing consultant's involvement in the contract.

\(4\) A description of the nature of the services rendered by or to be
rendered by the marketing consultant.

\(5\) The name, address, and telephone number of the client or clients,
and the name of a responsible officer or employee of the marketing
consultant who is knowledgeable about the services provided to such
client(s), and a description of the nature of the services rendered to
such client(s), if, based on information provided to the Contractor by
the marketing consultant, any marketing consultant is rendering or, in
the 12 months preceding the date of the verification, has rendered
services respecting the same subject matter of the instant solicitation,
or directly relating to such subject matter, to the Government or any
other client (including any foreign government or person).

\(6\) A statement that the person who signs the verification for the
prime Contractor has informed the marketing consultant of the existence
of Subpart 9.5 and Office of Federal Procurement Policy Letter 89-1
(Exhibit 26).

\(7\) The signature, name, title, employer's name, address and telephone
number of the persons who signed the verifications for both the apparent
successful offeror and the marketing consultant.

\(d\) In addition, the apparent successful offer shall forward to the
Contracting Officer a verification signed by the marketing consultant
that the marketing consultant has been told of the existence of Subpart
9.5 and Office of Federal Procurement Policy Letter 89-1, and the
marketing consultant has made inquiry, and to the best of the
consultant's knowledge and belief, the consultant has provided no unfair
competitive advantage to the prime Contractor with respect to the
services rendered to be rendered in connection with the solicitation, or
that any unfair competitive advantage that, to the best of the
consultant's knowledge and belief, does or may exist, has been disclosed
to the offeror.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\(e\) Failure of the offeror to provide the verifications may result in
the offeror being determined ineligible for award. Misrepresentation of
any fact may result in the assessment of penalties associated with false
verifications or such other provisions provided for by law or
regulation.

\(f\) The terms of this clause and the application of this subpart to
the contract are not subject to negotiation.

## 30. AUTHORIZED NEGOTIATORS: CITC-FCXC-\_\_\_ (MAY 1997) 

The offeror represents that the following persons are authorized to
negotiate on its behalf with the Government in connection with this
request for proposals **FOR THE MASTER CONTRACT** (list names, titles,
and telephone numbers and electronic mail address of the authorized
negotiators).

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

The offeror represents that the following persons are authorized to
negotiate on its behalf with the Government in connection with
**INDIVIDUAL TASK ORDERS UNDER THE MASTER CONTRACT** (list names,
titles, and telephone numbers and electronic mail address of the
authorized negotiators).

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

## 31. CONTRACT ADMINISTRATION PLAN: CITC-FCXC-\_\_\_ (MAY 1997)

Offerors are required to submit with their proposal, a description of
their contract administration plan. This shall include, at a minimum,
who will administer the contract, who has signature authority to
financially commit and contractually bind the company for contract
modifications, along with names, titles, addresses, telephone and
facsimile numbers, and e-mail addresses.

Administration of Contract:

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

Signature Authority:

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

NOTE: A contract modification is required to change the contact for
contract administration.

## 32. GOVERNMENT POINTS OF CONTACT: CITC‑FCXC‑\_\_\_ (MAY 1997)

Designated Points of Contact are:

**Contracting Officer** TBD

**for Fleet Card:** GSA/FSS/FCXC

Washington, DC 20406

Tel: (703) 305-7564

**Contracting Officer** Ms. Darlena Bikowski

**for Travel Card:** GSA/FSS/FCXC

Washington, DC 20406

Tel: (703) 305-5592

Fax: (703) 305-6268

e-mail: darlena.bikowski@gsa.gov

**Contracting Officer** Ms. Rebecca Koses

**for Purchase Card &** GSA/FSS/FCXC

**Integrated Solutions** Washington, DC 20406

Tel: (703) 305-6681

Fax: (703) 305-6268

e-mail: rebecca.koses@gsa.gov

**Contract Specialist:** TBD

GSA/FSS/FCXC

Washington, DC 20406

Tel: (703)

**A/OPC:** As Determined on Each Task Order

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 33. CONTRACTING OFFICER\'S AUTHORITY: CITC-FCXC-\_\_\_ (MAY 1997)

The GSA Contracting Officer is the only person authorized to make any
changes in any of the requirements of the master contract, and
notwithstanding any provisions contained elsewhere in this contract,
said authority remains solely in the GSA Contracting Officer. In the
event the Contractor makes any changes to the master contract at the
direction of any person other than the GSA Contracting Officer, the
change will be considered to have been made without authority and no
adjustment will be made in the master contract price to cover any
increase in costs incurred as a result thereof.

The GSA Contracting Officer is the only individual who can legally
commit or obligate the Government to the expenditure of public funds for
the master contract. No cost chargeable to the proposed master contract
can be incurred before awarded of the contract or specific authorization
from the GSA Contracting Officer.

## 34. AGENCY/ORGANIZATION PROGRAM COORDINATOR (A/OPC): CITC‑FCXC-\_\_\_ (MAY 1997)

The Agency/Organization Program Coordinator (A/OPC) serves as the focal
point for coordination of the applications, issuance and destruction of
cards, establishment and review of reports, and administrative training.
Only the A/OPC or the GSA Contracting Officer is authorized to request
the Contractor to establish new accounts. This individual also serves as
the liaison between the agency/organization, Contractor and the GSA
Contracting Officer. The A/OPC oversees the card program(s) for his/her
agency/organization and establishes guidelines. Changes to required
authorization controls must be submitted to the Contractor by the A/OPC.
Responsibilities includes general administration of the
agency's/organization's task order which are limited to the following:

> \(1\) Maintaining an up-to-date list of account names, account
> numbers, addresses, e-mail addresses, telephone numbers, etc., of all
> current cardholders and accounts;
>
> \(2\) Maintaining an up-to-date list of agency/organization points of
> contact for Designated Billing Offices (DBO), Transaction Dispute
> Offices (TDO) and EC/EDI Offices (EO), as applicable, a list of each
> travelers check/bank check distribution point, point of contact for
> each site and telephone number of contact;
>
> \(3\) Providing to the contractor(s) any changes in their
> agency's/organization's organizational structure that affect
> invoice/report distribution;

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> \(4\) Reviewing and evaluating, on a quarterly basis, the
> contractor\'s technical and administrative task order performance and
> compliance, including conformance with price and schedule provisions
> of the work effort, and accepting deliverables. The A/OPC will ensure
> that DBO, TDO and EO Offices provide feedback to the A/OPC. The A/OPC
> will consolidate feedback on the task order evaluation forms;
>
> \(5\) Resolving technical and operational problems between the
> contractor and the user as required;
>
> \(6\) As applicable, assisting the GSA Contracting Officer in
> authorizing unique contract support changes;
>
> \(7\) Taking appropriate action regarding delinquent accounts or
> non-compliance with task order performance, notifying the contractor
> and GSA Contracting Officer as appropriate, and reporting to the GSA
> Contracting Officer any observed violations of applicable executive
> orders, laws or regulations;
>
> \(8\) As necessary, conduct site visits of the Contractor's facility;
>
> \(9\) Ensuring that task orders and changes orders to the task orders
> are within the maximum dollar volume limit, and include:
>
> \(a\) Clearly defined requirements, acceptance plan and criteria, and
> an appropriate management and technical approach; and
>
> \(b\) Defined milestones and deliverable products, schedules and
> prices.
>
> \(10\) Developing an independent Government estimate for each task
> order and/or change orders to the task order, for use in negotiating
> price;
>
> \(11\) Participating in annual training conferences and disseminating
> to agency/organization basic information learned during conference
> proceedings;
>
> \(12\) Ensuring cardholders use the card program correctly;
>
> \(13\) Monitoring account activity and managing delinquencies; and
>
> \(14\) Ensuring that appropriate steps are taken to mitigate
> suspension or cancellation actions.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

The A/OPC will not provide supervisory or instructional assistance to
the contractor\'s personnel. The A/OPC is not authorized to change any
of the terms and conditions of the master contract. Master contract
changes can only be authorized by the GSA Contracting Officer.

## 35. DESIGNATED BILLING OFFICE (DBO): CITC‑FCXC-\_\_\_ (MAY 1997)

The Designated Billing Office (DBO) serves as the focal point for
receipt of official centrally billed invoices. This individual also
serves as the liaison between the agency/organization, A/OPC and the
centrally billed account. The DBO oversees the proper processing of
invoices and ensures invoices are paid within the Prompt Payment Act
timeframes. Responsibilities include the following:

> \(1\) Ensuring that changes to DBO are provided to the A/OPC in a
> timely fashion;
>
> \(2\) Reconciling invoices;
>
> \(3\) Providing quarterly feedback to the A/OPC on contractor
> performance;
>
> \(4\) Identifying billing discrepancies to the Transaction Dispute
> Office (TDO);
>
> \(5\) Identifying and analyzing whether faster payment of official
> invoices in order to take advantage of productivity refunds are in the
> best interests of the Government, and if so, effectuate payment on the
> proper date;
>
> \(6\) Ensuring that payment for items is made within the Prompt
> Payment Act timeframes;
>
> \(7\) Ensuring that if payment exceeds Prompt Payment Act timeframes
> that the proper interest penalty is also provided;
>
> \(8\) Analyzing and monitoring contractor reports on invoices, invoice
> status, payment performance, and delinquencies;
>
> \(9\) As necessary, conduct site visits of the Contractor's facility.
>
> \(10\) Ensuring the agency/organization task order is adequately
> funded, if applicable;
>
> \(11\) Authorizing and effectuating split disbursements (travel card
> only);
>
> \(12\) Participating in annual training conferences and disseminate to
> agency/organization basic information learned during conference
> proceedings;

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> \(13\) Ensuring that appropriate steps are taken to mitigate
> suspension or cancellation actions; and
>
> \(14\) Process agency/organization refunds as designated by the
> agency/organization.

The DBO will not provide supervisory or instructional assistance to the
contractor\'s personnel. The DBO is not authorized to change any of the
terms and conditions of the master contract. Master contract changes can
only be authorized by the GSA Contracting Officer.

## 36. TRANSACTION DISPUTE OFFICE (TDO): CITC‑FCXC-\_\_\_ (MAY 1997)

The Transaction Dispute Office (TDO) serves as the focal point for
disputing transactions on centrally billed invoices. This individual
also serves as the liaison between the DBO, A/OPC and the centrally
billed account. The TDO oversees the proper processing of transaction
disputes and works with the Contractor to resolve transaction dispute.
Responsibilities include the following:

> \(1\) Ensuring that changes to TDO are provided to the A/OPC in a
> timely fashion;
>
> \(2\) Reporting disputed transactions to the Contractor in a timely
> fashion;
>
> \(3\) Tracking disputed transactions;
>
> \(4\) Providing quarterly feedback to the A/OPC on contractor
> performance;
>
> \(5\) Analyzing and monitoring contractor reports on transaction
> disputes;
>
> \(6\) As necessary, conduct site visits of the Contractor's facility;
> and
>
> \(7\) Participating in annual training conferences and disseminate to
> agency/organization basic information learned during conference
> proceedings.

## 37. EC/EDI OFFICE (EO): CITC‑FCXC-\_\_\_ (MAY 1997)

The EC/EDI Office (EO) serves as the focal point for electronic
commerce/electronic data interchange for the agency/organization. This
individual also serves as the liaison between the A/OPC, EC/EDI systems
staff and the Contractor. The EO oversees the proper implementation of
the agency/organization EC/EDI capabilities and processes.
Responsibilities include the following:

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> \(1\) Ensuring that changes to EO are provided to the A/OPC in a
> timely fashion;
>
> \(2\) Determining agency/organization EC/EDI processes and platforms;
>
> \(3\) Working with the Contractor to receive and transmit data
> electronically;
>
> \(4\) Providing quarterly feedback to the A/OPC on contractor
> performance;
>
> \(5\) As necessary, conduct site visits of the Contractor's facility;
> and
>
> \(6\) Participating in annual training conferences and disseminate to
> agency/organization basic information learned during conference
> proceedings.

## 38. ORDERING: CITC-FCXC-\_\_\_ (MAY 1997)

38.1 *Definitions:* The following definitions are provided:

**Fair Consideration Exceptions:** The requirement for fair
consideration does not apply to orders under \$2,500 or to orders above
\$2,500 where the ordering Contracting Officer determines that: (1) the
need for the services or property ordered is of such unusual urgency
that

providing such opportunity to all such contractors would result in
unacceptable delays in fulfilling that need; (2) only one such
contractor is capable of providing the services or property required at
the level of quality required because the services or property ordered
are unique or highly specialized; (3) the task order should be issued on
a sole-source basis in the interest of economy

and efficiency because it is a logical follow-on to a task order already
issued on a competitive basis; or (4) it is necessary to place the order
with a particular contractor in order to satisfy a minimum guarantee.
**\
**

**FSSIP:** Federal Supply Schedule Information Publication. A
Government-designed and issued publication that summarizes master
contract terms and conditions and summarizes awarded contracts. Includes
a matrix of Contractor(s) offerings in the areas of contract line item
numbers; value-added products and services, type of electronic access
and specifications; an indication of how current program and transaction
data is; past performance rating; price; etc.

**Mandatory User:** Agencies/organizations that have agreed to be
mandatory users of one or more of the business line(s) under the GSA
contract and one or more component(s) of a particular business line
(e.g., ATM, travelers checks, bank checks). These agencies/organizations
are precluded from purchasing similar fleet, travel and/or purchase card
products and services outside of this master contract. Contractors shall
accept all orders from mandatory users.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

**Non-Mandatory User:** Agencies/organizations that have not agreed to
be mandatory users of one or more of the business line(s) under the GSA
contract and one or more component(s) of a particular business line
(e.g., ATM, travelers checks, bank checks). These agencies/organizations
may use the GSA contract for their fleet, travel and/or purchase card
products and services, but are not under any obligation to do so.
Contractors may accept orders from non-mandatory users.

**Qualified Contractor:** Those master contract awardees that meet
agency/organization requirements. See example 1 of 38.21, Examples of
Task Order Award Process.

**Standard Task Request/Order:** An agency's/organization's written or
electronic order for the products and services as described
(off-the-shelf) in the Federal Supply Service information publication
(FSSIP) or the contractor's presentation package. The terms standard
task request and standard task order are used interchangeably and mean
the same thing. The standard task request will include, at a minimum,
the statement "THIS IS A STANDARD TASK REQUEST/ORDER," the names of the
activity or activities authorized to issue orders against the task order
(e.g., for DoD it may be Navy, Air Force, etc.), date of order, GSA
contract number, task order number, the Contract Line Item Number (CLIN)
ordered, price, period of performance, place of delivery or performance
and accounting and appropriation data. Agencies/organizations should
also be prepared to provide to the contractor its purchasing history
(e.g., dollars, transactions, cardholders, payment performance, etc.).
The standard task request/order is the document that starts the
implementation timeframes described in Section C. Agencies/organizations
will only issue a standard task request/order when they have selected
the awardee. The standard task request/order is NOT a request for
additional information from the Contractors. If an agency/organization
is still in the process of reviewing master contractors, they may
contact the contractors for additional information, as desired. See
Exhibit 16 for a sample standard task request/order.

**Tailored Task Request:** An agency/organization written or electronic
task request for a proposal to provide the products and services similar
to those described in the FSSIP or the contractor's presentation
package, but tailored to the agency's/organization's requirement. The
tailored task request will include, at a minimum, the statement "THIS IS
A TAILORED TASK REQUEST," a performance work statement for a particular
requirement or project from an ordering agency/organization that clearly
specifies all tasks to be performed and products to be delivered under
the task order; evaluation factors, relative importance of evaluation
factors, methodology for award of the task order, and a request for
written or oral proposals from master contract awardees.
Agencies/organizations should also be prepared to provide to the
contractors its purchasing history (e.g., dollars, transactions,
cardholders, payment performance, etc.). Agencies/organizations will
only issue a tailored task request when they have developed their
performance work statement, evaluation factors, relative importance of
evaluation factors and methodology for award of the task order. The
tailored task request is NOT an actual task order\--it is the
agency's/organization's request for proposal from master contract
awardees. See Exhibit 17 for a sample tailored task request.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

**Tailored Task Order Proposal:** The contractor's bona-fide proposal
describing how it intends to accomplish the agency's/organization's
requirements stated in the tailored task request and at what price.

**Tailored Task Order**: An agency's/organization's written or
electronic order for the tailored products and services at the
negotiated price. The tailored task order will include, at a minimum,
the statement "THIS IS A TAILORED TASK ORDER," the tailored task
request, the awardee's initial and best and final proposal(s), the names
of the activity or activities authorized to issue orders against the
task order (e.g., for DoD it may be Navy, Air Force, etc.), date of
order, GSA contract number, task order number, CLINs, price, period of
performance, place of delivery or performance and accounting and
appropriation data. See Exhibit 18 for a sample tailored task order.

38.2 *Task Orders:* It is not possible to accurately estimate the number
or volume of task orders that will be provided during the contract term.
All costs associated with the marketing, development, proposal
preparation, presentation, submission and negotiation in response to any
task request or task order shall be at the Contractor's expense. All
travel costs associated with task order process shall be borne by the
Contractor.

38.3 *Order Placement:* Each agency's/organization's Chief Financial
Officer (CFO), Chief Administrative Officer (CAO) and Procurement
Executive (PE), or designees of each, will be responsible for making the
decision on how the agency/organization will place a task order for
his/her agency/organization. The CFO, CAO and PE, or designees, may
allow various organizational elements to place their task order directly
with the contractor or may ask GSA to do so on their behalf. For orders
more than \$2,500, agencies/organizations are required to review

all qualified contractors using either the FSSIP or contractor
presentation packages prior to placing their task order.

38.4 *Minimum Task Order Size for Standard Task Requests/Orders:* There
is no minimum task order size for standard task requests/orders. The
Contractor shall accept all standard task requests/orders from mandatory
users.

38.5 *Minimum Task Order Size for Tailored Task Requests and Orders:*
The minimum task order size for tailored task requests and orders is as
follows:

a)  Fleet Card: \$300,000 annual charge volume;

b)  Travel Card: \$3,000,000 annual charge volume;

c)  Purchase Card: \$3,000,000 annual charge volume; and

d)  Integrated Solution Card: \$5,000,000 annual charge volume.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

*The Contractor may accept tailored task orders that are less than the
minimum charge volume specified*. Should the Contractor elect not to
accept a task order less than the minimum charge volume, the Contractor
shall submit a "no offer" response including a brief statement as to the
reason why they chose not to respond.

38.6 *Minimum Length of Initial Task Orders (both standard and
tailored):* For the agency's/organization's [initial]{.underline} task
order placed against the master contract, the minimum task order length
for both standard and tailored task orders is two (2) years OR duration
of the master contract, whichever is sooner, unless otherwise specified.
Agency/organization task orders may contain options to renew the initial
task order; however, the task order shall not exceed the period of the
master contract.

Subsequent agency/organization task orders are not required to have any
minimum length, but must not exceed the period of the master contract.

For example, the master contract is for a base period of 5 years. XYZ
Agency places its initial task order with ABC Contractor for two years
and contains 3 one-year options to renew. After the initial two-year
minimum length, XYZ Agency does not exercise any option to renew.
Instead, XYZ Agency issues a new statement of work to all master
contractors, gives fair consideration to all, and selects a new awardee,
DEF Contractor. XYZ Agency places a one-year task order with DEF
contractor. Because XYZ Agency met the contract requirement to have its
initial task order be a minimum 2-year length, subsequent task orders
are not required to have the same minimum length, even if XYZ Agency
changed contractors. The minimum task order length is tied to the
start-up of the master contract\--not to a task order with an individual
contractor.

As another example, the master contract is for a base period of 5 years.
BBB Agency places its initial task order with XYZ Contractor for two
years and contains 3 one-year options to renew. After the first year,
the GSA Contracting Officer terminates XYZ's contract for cause. Because
the duration of the master contract was shorter than the task order, the
minimum length of the task order becomes directly tied to the length of
the master contract, i.e., one year instead of the two year minimum.

The Contractor may accept initial task orders placed against the master
contract that are less than the minimum length specified. Should the
Contractor elect not to accept a task order less than the minimum
length, the Contractor shall submit a "no offer" response including a
brief statement as to the reason why they chose not to respond.

38.7 *Maximum Length of Task Orders (both standard and tailored):*
Agency/organization task orders may not exceed the master contract
length. The maximum agency/organization task order for the initial order
placement may be a maximum of 5 years with 5 one-year options to renew,
or duration of master contract length, whichever is sooner.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

For example, the master contract is for a base period of 5 years. EEE
Agency places its initial task order with ABC Contractor for five years
and contains 5 one-year options to renew. After the initial 5-year base
period, EEE Agency exercises its option to renew its task order for a
year, to correspond with the master contract one-year option to renew
which is exercised by the GSA Contracting Officer. Subsequent master
contract options are renewed each year thereafter, and EEE Agency also
exercises its task order option to renew each year thereafter, to
correspond with the master contract.

38.8 *Task Request/Order Development Assistance:* GSA offers all
agencies/organizations standard and tailored task order development
assistance, upon request, at no additional cost to the
agency/organization. Mandatory agencies receive first priority for task
request/order development assistance.

> a\) Standard Task Order Development: For agencies/organizations that
> want to place a standard task order but require assistance in
> determining which Contractor will best meet its needs, GSA will
> provide such assistance upon request. This includes educating the
> agency/organization on program offerings.
>
> b\) Tailored Task Order Development: For agencies/organizations that
> want to place a tailored task order but require assistance in
> determining agency/organization requirements or contractor selection,
> GSA will provide such assistance upon request. This will include
> educating the agency/organization on program offerings, facilitating
> internal agency/organization discussions, identifying appropriate
> categories of personnel to be included in the discussions, reviewing
> agency/organization requirements, suggesting changes/clarifications to
> requirements, providing procedural assistance, etc.

38.9 *Task Request/Order Placement Assistance:*

> a\) Contractor Provided Order Placement Assistance:
> Agencies/organizations are encouraged to pool their standard and
> tailored task orders together to obtain maximum benefits. The
> Contractor shall, upon request, facilitate agencies/organizations to
> pool orders together. This includes comparing agency requirements it
> receives to find
>
> similarities in requirements and suggesting a match, providing points
> of contact and telephone numbers.
>
> b\) GSA Provided Order Placement Assistance: At the
> agency's/organization's request and as described below, GSA will
> facilitate any pooling effort desired for both standard and tailored
> task orders by making a list of interested pooling parties and/or
> agency task orders available on an electronic bulletin board for
> agencies to review and obtain ideas from, including it into the GSA's
> Pool; or including the

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> agency/organization in GSA's task order. The Contractor shall accept
> all GSA-pooled orders. GSA WILL NOT SUBMIT ORDERS TO ANY PARTICULAR
> CONTRACTOR TO SATISFY A GUARANTEED MINIMUM. GSA will provide order
> assistance without regard to the guaranteed minimum. For example, if
> the agencies/organizations requesting order assistance all require
> current transaction data and ABC Contractor does not meet that
> requirement, but has no orders from anyone, GSA will not direct work
> or task orders to the ABC Contractor in order to satisfy the
> guaranteed minimum. In this example, ABC Contractor does not meet the
> requesting pooling agency/organization needs, thus the pooled task
> request would be offered to only those master contractors that meet
> the requirement for their proposal.
>
> 1\) Order Facilitation: For agencies/organizations that want to pool
> their task orders together without GSA or Contractor assistance, the
> GSA will make available an electronic bulletin board that lists
> agencies/organizations interested in pooling along with points of
> contact and telephone numbers. Agencies/organizations may arrange
> their own pooling efforts in this manner. GSA may also make available
> agency/organization awarded task orders (see paragraph 38.20) for
> agencies to review and obtain ideas from. It is important for
> agencies/organizations to submit their task requests electronically to
> facilitate this process.
>
> 2\) GSA Pool: For agencies/organizations that want to pool their task
> order together with GSA's assistance, GSA will facilitate this process
> upon request. Agencies/organizations may submit their requirements to
> GSA and GSA will compare agency/organization requirements to find a
> match and provide the agency/organization a point of contact and
> telephone number. GSA will consolidate agency/organization
> requirements and either provide the consolidated requirements to the
> ordering agency/organization or place the order on the
> agency's/organization's behalf. Contractors must accept all GSA-pooled
> orders, regardless of mandatory/non-mandatory status or task order
> size.
>
> 3\) GSA Task Order: Upon request, agencies/organization may pool their
> task order with GSA's task order. Contractors must accept all GSA task
> orders.

38.10 *Mandatory Users of the GSA Contract:* Agencies/organizations that
have agreed to be mandatory users of one or more business line(s) and
one or more component(s) of the particular business line under the GSA
contract may place their standard or tailored task request directly with
the Contractor or may have GSA place the order on their behalf.
Contractors must respond in good faith to all task requests received
from a mandatory user of the particular business line. For tailored task
requests received from a mandatory user of the particular business line,
the Contractor shall submit a bona fide proposal directly to the
agency/organization (or to GSA if GSA is placing the order on behalf of
the agency/organization) within **fifteen (15) calendar days** of
receipt, unless otherwise directed.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

38.11 *Non-Mandatory Users of the GSA Contract:* Agencies/organizations
that are non-mandatory users of one or more business line(s) and one or
more component(s) of the particular business line under the GSA contract
shall forward their standard or tailored task request directly to the
GSA Contracting Officer for that particular business line. GSA will make
an eligibility determination and approve all standard and tailored task
requests from eligible users, in writing, for the business line(s)
required. Specific to the Travel Card Program, GSA will verify a
non-mandatory user's eligibility for GSA's City Pair Program. Approved
non-mandatory agencies/organizations may then place their standard or
tailored task request, with a copy of the GSA Contracting Officer's
approval letter, directly with the Contractor or may have GSA place the
order on their behalf.

Contractors are encouraged to respond to all standard and tailored task
requests received from non-mandatory users; however, in the event the
contractor declines to accept a standard task order or submit a proposal
in response to a non-mandatory user's tailored task request, it must do
so within **seven (7) business days** after receipt of the task request
from the agency/organiza-tion. The Contractor shall then immediately
forward a copy of all task requests it declines and the reason for the
declination to the GSA Contracting Officer.

If the Contractor elects to accept a standard task order from a
non-mandatory user, it must perform the work in accordance with the
terms and conditions of the contract. If the Contractor elects to submit
a proposal in response to a tailored task request from a non-mandatory
user, it must exercise its best efforts to do so within **thirty (30)
calendar days** of receipt. If selected for award, the Contractor shall
perform in accordance with the awarded proposal and terms and conditions
of the master contract.

38.12 *Ordering Process:* In accordance with paragraph 38.10, Mandatory
Users of the GSA Contract and paragraph 38.11, Non-Mandatory Users of
the GSA Contract, orders will be placed as follows:

38.12.1 Standard Task Request/Order Process: For orders under \$2,500,
agencies/organizations can order these services simply by placing an
order with the contractor of the agency's/organization's choice. For
orders over \$2,500:

a\) The agency/organization must review the FSSIP or contractor
presentation package and determine which contractor best meets its
requirements. The agency/organization may contact the master contractors
for additional information, as desired, so long as they give fair
consideration to all contractors under the master contract;

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

b\) Once the agency/organization has made their selection, the
agency/organization then submits a written order for the products and
services. The order shall include, at a minimum: the statement "THIS IS
A STANDARD TASK REQUEST/ ORDER," the names of the activity or activities
authorized to issue orders against the task order (e.g., for DoD it may
be Navy, Air Force, etc.), date of order, GSA contract number, task
order number, CLINs, price, period of performance, place of delivery or
performance and accounting and appropriation data. The written order may
be on an official government order form (DD1155, GSA300, etc.), on
agency/organization letterhead, or electronic, but must be in writing.
Agencies/organizations do not submit a separate work statement with
their standard task request/order.

c\) The Contractor acknowledges the standard task order and begins
implementation within the timeframes specified in the Schedule of
Services. A separate technical and price proposal is not required for
the standard task request/order.

d\) When issuing standard task requests/orders, agencies/organizations
are not required to formally or informally compete the requirement or
negotiate with contractors.

38.12.2 Tailored Task Request/Order Process: For orders under \$2,500,
agencies/organizations can order these services simply by placing an
order with the contractor of the agency's/organization's choice. For
orders over \$2,500:

a\) The agency/organization must review the FSSIP or contractor
presentation packages and determine which contractors may meet it
requirements. The agency/organization may contact qualified master
contractors for additional information, as desired, so long as they give
fair consideration to all qualified contractors under the master
contract;

b\) The agency/organization may post their tailored task request on the
Internet in a separate area reserved for access by qualified master
contractors or utilize another medium (e.g., mail, fax, e-mail, or other
electronic means). NOTE: Electronic submission is preferred as GSA may
post final task orders on an electronic bulletin board (see paragraph
38.20);

c\) The procedures and selection criteria that will be used to provide
multiple awardees a fair opportunity to be considered for each tailored
task order are as follows: Agencies/organizations shall furnish
identical information concerning a proposed acquisition to all qualified
contractors. Agencies/organizations will treat all prospective awardees
fairly. The agency/organization will submit a tailored task request to
all qualified contractors. The tailored task request must be in writing
(e.g., mail, fax, etc.) or electronic (NOTE: Electronic submission is
preferred as GSA may post final task orders on an electronic bulletin
board\--see paragraph 38.20). The tailored task request shall include,
at a minimum: the performance work statement for a particular
requirement or project that clearly specifies all tasks to be performed
and

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

products to be delivered under the task order, period of performance,
evaluation factors[^76], relative importance of evaluation factors[^77],
methodology for award of the task order[^78], and a request for
proposals from qualified contractors. Agencies/organizations are
encouraged to request oral proposals from qualified contractors where
practicable. Agencies/organizations are encouraged to utilize
streamlined procedures (e.g., electronic submission of proposals, page
restrictions on proposals, etc.).

d\) As designated by the agency/organization, qualified Contractors
shall be allowed a short period of time to submit requests for
clarification and receive answers over the Internet or other medium. The
questions and answers shall be made available simultaneously to all
qualified contractors.

e\) Within the timeframes specified in paragraph 38.10 or 38.11, as
applicable, the Contractor(s) shall submit their tailored task order
proposal. The tailored task order proposal shall consist of two parts:
Technical and Price. Unless otherwise directed in writing, the technical
portion shall, at a minimum:

-   Demonstrate the contractor's understanding of the requirements;

-   Describe the contractor's accomplishments and experience in
    performing the work required under the performance statement of
    work;

-   Describe its technical approach to accomplishing the requirements
    within the required timeframes or budget, if provided by the
    agency/organization;

-   Identify the milestones or work break down structures;

-   Describe the skill categories/CLINs to be utilized;

-   Describe which portions of the effort will be subcontracted, if any;

-   Describe the number of hours/units required to accomplish the work
    effort for each CLIN, milestone or work break down structure; and

-   Identify the deliverables.

    Pricing shall be firm fixed price unless otherwise specified by the
    agency/organization. It shall identify all costs and/or the
    reduction or increase in refunds offered. Unless otherwise directed
    in writing, the price portion shall, at a minimum:

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

-   Identify all milestones or work break down structures and associated
    hours/units and price for each milestone or work break down
    structure;

-   Identify the CLINs and skill categories;

-   Identify the number of hours/units, hourly rate/unit price, extended
    price, and rebates offered; and

-   Identify the total price and include a summary of all CLINs
    proposed.

f\) The agency/organization will review and evaluate each proposal
received against established evaluation criteria and methodology. The
agency/organization may then do one of the following:

-   Select the awardee without further discussions; or

-   Conduct negotiations.

g\) If negotiations are conducted, they will occur at the time and place
designated by the ordering Contracting Officer and/or his/her designated
representative. Following the completion of negotiations and as
directed, the Contractor(s) shall submit a finalized tailored task order
proposal, as directed by the agency/organization, which reflects the
best and final offer, technical and price, and include a firm milestone
schedule.

h\) Based on the information provided by the qualified master
contractors, the agency/or-ganization will evaluate the offers received
in accordance with the established evaluation criteria and methodology.
Once completed, the agency/organization should document the process in
an "Award Recommendation Document" (ARD). The ARD will include the
contractor recommended for award, the evaluation criteria and
methodology employed, and the agency's/organization's rationale in
support of the recommendation. Furthermore, if a fair opportunity
exemption is applicable (see paragraph 38.1, Definitions), the exemption
will be cited and justified in the ARD. The ARD is intended to be brief
and succinct and will be part of the agency's/organization's task order
file. The ordering agency/organization will notify the other
participating contractors of which awardee will be issued the task
order. Agencies/organizations are not required to develop formal
negotiation or evaluation plans or scoring schemes for task orders.

38.12.3 Task Order Issuance:

a\) A tailored task order may be issued by the ordering Contracting
Officer after receipt and review of all of the qualified contractors'
initial, subsequent and best and final task order proposals in
accordance with the established evaluation criteria and methodology.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

b\) The tailored task order will include, at a minimum, the statement
"THIS IS A TAILORED TASK ORDER," the names of the activity or activities
authorized to issue orders against the task order (e.g., for DoD it may
be Navy, Air Force, etc.) , date of order, GSA contract number, task
order number, the tailored task request, the awarded contractor's
initial, subsequent, and best and final proposal(s), CLINs, hours/units,
price, period of performance, place of delivery or performance and
accounting and appropriation data.

c\) A completed tailored task order will result in the performance of a
specified unit of work in a definable service or applications area
having one or more related deliverable products. No work will be
performed except as authorized by a tailored task order and no payment
will be made except upon satisfactory performance accepted and approved
by the ordering Contracting Officer. The completion dates may be
extended in the event performance is delayed due to causes beyond the
control and without the fault or negligence of the contractor as set
forth in Clause 52.212-4, Contract Terms and Conditions\--Commercial
Items, and as determined by the ordering Contracting Officer.

38.13 *Schedule:* Each task order will establish a milestone or work
break down schedule for submissions (deliverables, testing, etc.).
Failure by the Contractor to perform in accordance with the schedule
will be sufficient grounds for the ordering Contracting Officer to
terminate the task order. It may also be sufficient grounds for the GSA
Contracting Officer to terminate the contractor's contract under the
master contract pursuant to the termination for cause clause of the
master contract.

38.14 *Changes:* Any changes to a standard or tailored task order will
be issued in writing by the ordering or GSA Contracting Officer on the
agency's/organization's behalf. Only the ordering or GSA Contracting
Officer on the agency's/organization's behalf may modify the terms and
conditions of the standard or tailored task order. The ordering
Contracting Officer does not have the authority to modify the terms and
conditions of the master contract.

38.15 *Restrictions:* A standard or tailored task order may not increase
the scope, period or maximum value of the master contract under which
the task order is issued. Unique to the Travel Card Program, a standard
or tailored task order may not split agency requirements between
individually and centrally billed accounts (i.e., if an agency places a
task order, it must include both individually and centrally billed
accounts (if applicable) in the task order. The agency may not issue one
task order for individually billed accounts with one contractor and
another task order for centrally billed accounts with a different
contractor).

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

38.16 *Submission of Task Orders by the Contractor:* The Contractor
shall provide one complete copy of each awarded standard and tailored
task order (technical and price) for that month, and any modifications
there, to the GSA Contracting Officer no later than the **10th calendar
day** of each subsequent month. Electronic copies are preferred. For
example, task orders awarded during the month of January would be
forwarded to the GSA Contracting Officer no later than February 10.

38.17 *Limitations:* Except for the maximum order per task order, if
any, there is no limit on the number of orders that may be placed, so
long as it does not exceed the maximum value for the master contract as
a whole.

38.18 *Protests:* A protest is not authorized in connection with the
issuance or proposed issuance of a task order except for a protest on
the ground that the task order increases the scope, period, or maximum
value of the contract under which the order is issued.

38.19 *Task Order Ombudsman:* A GSA task order ombudsman has been
appointed to hear concerns from offerors, potential offerors and
contractors for the master contract. The purpose of the ombudsman is not
to diminish the authority of the ordering or GSA Contracting Officer,
but to be responsible for reviewing complaints from the contractors and
ensure that all of the contractors are afforded a fair opportunity to be
considered for task orders. The task order ombudsman is a senior GSA
official who is independent of the GSA Contracting Officer for this
contract and can be reached at:

Mr. Nicholas Economou, Director

FSS Acquisition Management Center

1941 Jefferson Davis Highway

Crystal Mall 4, Room 716

Arlington, VA 22202

\(703\) 305-6936

e-mail: nicholas.economou@gsa.gov.

The task order ombudsman does not have the authority to overturn award
decisions or adjudicate formal contract disputes.

38.20 *Bulletin Board:* All standard and tailored task orders and price,
as well as any modifications thereto, may be posted on a public
electronic bulletin board created and maintained by GSA. It is critical
that agencies/organizations submit all task orders electronically to
facilitate this process.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

38.21 *Examples of the Task Order Award Process:* The following examples
are provided to demonstrate fair consideration and how the task orders
may be awarded:

> Example 1: This is an example of giving all contractors fair
> consideration. ABC Agency/Organization requires, at a minimum, current
> transaction data. DEF Contractor can provide real time data, GHI and
> JKL Contractors can provide current transaction data, and MNO and PQR
> Contractors can only provide transaction data that is 30-days old.
> Because MNO and PQR Contractors do not meet the minimum requirement,
> they are not considered qualified contractors. ABC Agency/Organization
> excludes them from further consideration.
>
> Example 2: This is an example of a standard task request/order. ABC
> Agency/Organ-ization only requires the core requirements for the
> purchase card. It reviews each contractor's presentation package or
> the FSSIP for that particular business line. Based on the information
> contained in the presentation packages, XYZ Contractor is selected.
> ABC Agency/Organ-ization places a standard task request/order to XYZ
> Contractor.
>
> Example 3: This is an example of a tailored task request. BBB
> Agency/Organization requires value-added products and services in
> addition to the core requirements for the travel and fleet card. BBB
> requires value-added services "x," "y" and "z" on both travel and
> fleet business lines. Based on its review of all master contractors'
> presentation package or the FSSIP for those business lines, only DDD
> and EEE Contractors can do the work required (they are the only
> contractors on contract that has "x," "y," and "z" on both business
> lines). BBB submits its tailored task request to DDD and EEE
> Contractors. Proposals are received by both contractors. Based on the
> evaluation criteria and methodology stated in its task request, BBB
> Agency/Organization determines that DDD Contractor is the awardee for
> both business lines. BBB places a tailored task order to DDD
> Contractor.
>
> Example 4: This is an example of a tailored task request. 222
> Agency/Organization requires value-added products and services in
> addition to the core requirements for the fleet, travel and purchase
> card. The 222 Agency/Organization requires "a," "b," and "c" on the
> fleet card; "a" and "b" on the travel card; and "a" on the purchase
> card. While 222 Agency/Organization will look at each business line
> separately, it states that it prefers an integrated solution and the
> evaluation criteria reflects the importance of an integrated solution.
> 222 Agency/Organization reviews

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

> the presentation packages or the FSSIP. It determines that LLL, MMM
> and NNN Contractors can do the independent business lines and OOO
> Contractor can do the integrated solution. 222 Agency/Organization
> submits its tailored task request to all four contractors. Based on
> the evaluation criteria and methodology stated in its task request,
> and after negotiations, 222 Agency/Organization determines that while
> OOO Contractor can do the integrated solution, the cost and technical
> tradeoffs do not merit the price proposed by OOO Contractor. 222
> Agency/Organ-ization determines that it is in its best interest to
> award independent business lines to LLL, MMM and NNN Contractors,
> respectively, and places three separate tailored task orders.

38.22 *Refinement of Ordering Process:* GSA reserves the right to refine
the ordering procedures throughout the term of the contract (see
paragraph 39, Card Action Teams).

## 39. CARD ACTION TEAMS (CATS): CITC-FCXC-\_\_\_ (MAY 1997) 

The GSA may establish Card Action Teams (CATS) consisting of high-level
Government personnel, GSA Contracting Office, and the CEO, President or
Vice-President, or designee, from each awardee. CATS may meet
periodically to discuss ordering procedures, planned requirements,
program status, etc., to facilitate open communications in all areas.
The meetings are intended to be informative, open and candid and will
serve to continuously seek contractor input to further improve the
Government's card programs. All contractor travel costs associated with
participating in CATS shall be borne by the Contractor.

[                                                                         ]{.underline}
[                                                 ]{.underline}

Name Title

[                                                                         ]{.underline}
[                                                 ]{.underline}

Name Title

## 40. KICK OFF MEETING: CITC-FCXC-\_\_\_ (MAY 1997) 

The Contracting Officer intends to conduct a kick-off meeting shortly
after award. Government attendees may include the GSA Contracting
Officer, agency/organization representatives, and other pertinent
Government personnel. Contractor attendees shall include the Project
Manager and any other personnel as needed. All Contractor-travel costs
associated with this kick off meeting shall be borne by the Contractor.
The objective of the meeting is to:

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

-   Discuss kick-off conference;

-   Identify responsibilities and roles;

-   Address reports needed/regular meetings/schedules;

-   Address acceptance criteria/nonconforming supplies;

-   Discussion of task order process; and

-   Review other issues as required.

## 41. KEY PERSONNEL: CITC-FCXC-\_\_\_ (MAY 1997)

\(a\) [Key Personnel]{.underline}: The Contractor shall include in its
proposal, by name and labor category, the key personnel to be assigned
to perform and carry out all phases of work under the master contract.
The Contractor shall include key personnel resumes. Key personnel
include those individuals who are designated as key personnel by
agreement of the Government and the contractor during negotiations and
those individuals listed below:

[LABOR CATEGORY]{.underline} [NAME]{.underline}

Project Manager
[                                               ]{.underline}

Alternate Project Manager
[                                               ]{.underline}

Task Order Manager(s)
[                                               ]{.underline}

[                                               ]{.underline}

[                                               ]{.underline}

Alternate Task Order Manager(s)
[                                               ]{.underline}

[                                               ]{.underline}

[                                               ]{.underline}

EC/EDI Coordinator
[                                               ]{.underline}

Alternate EC/EDI Coordinator
[                                               ]{.underline}

Other (identify name/title)
[                                               ]{.underline}

[                                               ]{.underline}

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

[                                               ]{.underline}

\[If additional space is required, please use plain bond paper and
indicate the clause number and key personnel category\]

The persons named above are considered by the Government to be key
personnel and essential for the successful completion of all work
assigned under this contract. During the first ninety (90) days of the
contract performance period, no personnel substitutions will be
permitted unless substitutions are necessitated by an individual's
sudden illness, death, or termination of employment. In any of these
events, the Contractor shall promptly notify the GSA Contracting Officer
and provide a detailed explanation of the circumstances necessitating
the proposed substitution, a complete resume for the proposed
substitute, and any other information requested by the GSA Contracting
Officer needed to approve the proposed substitution. After the initial
ninety (90) day period, all proposed substitutions must be submitted, in
writing, at least 15 calendar days in advance of the proposed
substitutions to the GSA Contracting Officer, and provide the
information required as stated above. Any key personnel lost from an
active project must be replaced within 30 calendar days from the date of
the vacancy and replaced with personnel of equal or greater
qualifications to the personnel being replaced. All proposed substitutes
shall have qualifications that are equal to or higher than the
qualifications of the person immediately being replaced. The Contractor
shall provide a temporary replacement as an interim measure until key
personnel are replaced.

\(b\) [Support Personnel]{.underline}: Personnel other than key
personnel are considered support personnel. Resumes for specified
support personnel positions may be required at the time of order
placement or task order proposal submission, as directed by the ordering
Contracting Officer.

The Contractor shall notify the ordering Contracting Officer, in
writing, at least 15 calendar days prior to making any replacements in
support personnel, if requested. All proposed substitutes shall have
qualifications that are equal to or higher than the qualifications of
the person to be replaced. Any support personnel lost from an active
project must be replaced within 30 calendar days from the date of the
vacancy and replaced with personnel of equal or greater qualifications
to the personnel being replaced. The Contractor shall provide a
temporary replacement as an interim measure until support personnel is
replaced.

## 42. SERVICE IMPROVEMENTS: H-FSS-FCXC-\_\_\_ (MAY 1997)

\(a\) After contract award, the Government may solicit, and the
Contractor is encouraged to propose independently, improvements to the
services, features, or other requirements of the master contract. These
improvements may be proposed to save money, to improve performance, or
for any other purpose which presents a service advantage to the
Government. As

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

part of the proposed changes, the Contractor must submit a price
proposal to the GSA Contracting Officer for evaluation. Those proposed
service improvements that are acceptable to the Government will be
processed as modifications to the master contract.

\(b\) At a minimum, the following information shall be submitted by the
contractor with each proposal:

\(1\) A description of the difference between the existing contract
requirements and the proposed change, and the comparative advantages and
disadvantages of each;

\(2\) Itemized requirements of the contract which must be changed if the
proposal is adopted, and the proposed revisions to the contract for each
such change;

\(3\) An estimate of the changes in performance and cost/price, if any,
that will result from adoption of the proposal;

\(4\) An evaluation of the effects that the proposed changes would have
on collateral costs to the Government (e.g., Government-furnished
property costs, costs of related items, and costs of maintenance,
operation and conversion (including Government premise equipment);

\(5\) A statement of the time by which the contract modification
adopting the proposal must be issued so as to obtain the maximum
benefits of the changes during the remainder of this contract including
supporting rationale; and

\(6\) A description of the impact of the proposed change on the contract
completion time or delivery schedule.

\(c\) The Government will not be liable for proposal preparation costs
or any delay in acting upon any proposal submitted pursuant to this
clause. The Contractor has the right to withdraw, in whole or in part,
any proposal not accepted by the Government within the period specified
in the proposal. The decision of the GSA Contracting Officer as to the
acceptance of any such proposal under this contract is final and not
subject to the "Disputes" clause of this contract.

\(d\) The GSA Contracting Officer may accept any proposal submitted
pursuant to this clause by giving the contractor written notice thereof.
This written notice will be given by issuance of a modification to the
master contract. Unless a modification is executed to incorporate a
proposal under this contract, the Contractor shall remain obligated to
perform in accordance with the requirements, terms and conditions of the
existing contract.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 43. MASTER CONTRACT DELIVERABLES REQUIRED: F‑FSS‑FCXC‑\_\_\_ (MAY 1997)

The deliverables listed below are provided as a summary checklist of the
deliverables that may be required in the master contract and delivered
to the GSA Contracting Officer. Specific details of the deliverable(s)
can be found in the referenced section (and the subparagraphs of such
sections). The following deliverables may be required:

**See next page**

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

Card Program(s)

  ------------------------- ------------------------- --------------------
  **DELIVERABLE**           **REFERENCE**             **DUE**

  Vendor brochures,         C.8, Merchant Acceptance  As ordered
  enrollment                                          

  Satisfaction survey       C.10, Quality Assurance   30th calendar day
                                                      following each 12
                                                      month contract
                                                      period

  Security                  C.13, Security            With offer and as
  requirements/procedures   Requirements              updated

  Marketing/advertising     C.17, Marketing and       As described
  materials                 Advertising               

  Newsletter                C.18, Master Contract     Quarterly
                            Newsletter                

  Statement inserts         C.19, Statement Inserts   As described

  Statement messaging       C.20, Statement Messaging As described

  Conference fees           C.21, Master Contract     As described
                            Training Conference       

  Final card product,       C.23, Card Design and     4 weeks after
  sample/test cards and     Embossing                 contract award and
  camera ready art                                    as described

  Training materials        C.25, Training            As described
                            Requirements              

  Demonstration of          C.26, Personnel           As described
  qualifications                                      

  Implementation materials  C.27, Start-Up            As described
                            Implementation            
                            Requirements              

  Certification             C.28, Year 2000           With offer
                            Compliance                

  Program and transaction   C.34, Program and         As described
  data                      Transaction Data          

  Cards/accounts            C.35, Centrally Billed    As described
                            Card Program Accounts     

  Suspension documentation  C.36, Suspension          As described
                            Procedures for Centrally  
                            Billed Accounts           

  Cancellation              C.37, Cancellation        As described
  documentation             Procedures for Centrally  
                            Billed Accounts           

  GSA Contracting Office    C.39, GSA Contracting     As described
  reports                   Office Reports            

  As ordered                C.40, Customized Services As ordered

  Transition documentation  C.41, Transition          As described
                            Requirements              

  Transaction records       C.42, Record Retention    Within 30 calendar
                            and Retrieval             days

  Post contract             C.43, Post Contract       As described
  documentation             Requirements              

  Copies of orders          Addendum to 52.212-4,     As described
                            paragraph 38, Ordering    

  Performance evaluations   Addendum to 52.212-4,     Quarterly
                            paragraph 45, Contract    
                            Performance Standards     
  ------------------------- ------------------------- --------------------

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 44. TASK ORDER CONTRACT DELIVERABLES REQUIRED: F‑FSS‑FCXC‑\_\_\_ (MAY 1997)

The deliverables listed below are provided as a summary checklist of the
deliverables that may be required in task orders and delivered to the
agency/organization as directed. Specific details of the deliverable(s)
can be found in the referenced section (and the subparagraphs of such
sections). The following deliverables may be required:

**See next page**

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

Task Order Deliverable(s)

  ------------------------- ------------------------- --------------------
  **DELIVERABLE**           **REFERENCE**             **DUE**

  Vendor brochures,         C.8, Merchant Acceptance  As ordered
  enrollment                                          

  Additional quality        C.10, Quality Assurance   As ordered
  assurance measures                                  

  Higher levels of security C.13, Security            As ordered
                            Requirements              

  Newsletter                C.18, Master Contract     Quarterly
                            Newsletter                

  Statement inserts         C.19, Statement Inserts   As described

  Statement messaging       C.20, Statement Messaging As described

  Sample/test cards and     C.23, Card Design and     As ordered
  camera ready art          Embossing                 

  Training materials        C.25, Training            As described
                            Requirements              

  Implementation materials  C.27, Start-Up            As described
                            Implementation            
                            Requirements              

  Receipts                  C.31, Posting of          As needed
                            Transactions              

  Foreign currency          C.33, Foreign Currency    On reports
  conversion rate           Conversion                

  Program and transaction   C.34, Program and         As described
  data and electronic       Transaction Data          
  access                                              

  Cards/accounts            C.35, Centrally Billed    As described
                            Card Program Accounts     

  Suspension documentation  C.36, Suspension          As described
                            Procedures for Centrally  
                            Billed Accounts           

  Cancellation              C.37, Cancellation        As described
  documentation             Procedures for Centrally  
                            Billed Accounts           

  Agency reports            C.38, Agency Reporting    As described
                            Requirements              

  As ordered                C.40, Customized Services As ordered

  Transition documentation  C.41, Transition          As described
                            Requirements              

  Transaction records       C.42, Record Retention    Within 30 calendar
                            and Retrieval             days

  Post contract             C.43, Post Contract       As described
  documentation             Requirements              

  Value-added products and  C.47, Value-Added         As ordered
  services                  Products and Services     

  Program and transaction   CB.14, Travel Card        As described
  data                      Program and Transaction   
                            Data for Individually     
                            Billed Accounts           

  Individually billed       CB.15, Travel Card        As described
  accounts                  Program Individually      
                            Billed Accounts           

  Suspension documentation  CB.18, Individually       As described
                            Billed Travel Card        
                            Account Suspension        
                            Procedures                

  Cancellation              CB.19, Individually       As described
  documentation             Billed Travel Card        
                            Account Cancellation      
                            Procedures                

  Reports on annual per     CB.23, Per Card Annual    As described
  card fees and pre-funded  Fees or Pre-Funded Cards  
  accounts                  for Individually Billed   
                            Travel Card Accounts      
  ------------------------- ------------------------- --------------------

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 45. CONTRACT PERFORMANCE STANDARDS: F-FSS-FCXC-\_\_\_ (MAY 1997)

The Government will evaluate the Contractor's performance based on
successful performance of a combination of the following:

1.  Meeting the requirements as stated in the master contract within the
    timeframes specified with a typical rating of "good" or higher. The
    GSA Contracting Office will utilize quarterly master contract
    evaluations as shown in the "Master Contract Evaluation" table in
    paragraph 48 of this section.

2.  Customer satisfaction as demonstrated through the satisfactory
    annual contractor quality survey results (referenced in C.10,
    Quality Assurance) with a typical rating of "good" or higher.

3.  Customer satisfaction as demonstrated by agency/organization input
    with a typical rating of "good" or higher. The GSA Contracting
    Office will utilize quarterly task order evaluations as shown in the
    "Task Order Evaluation" table in paragraph 47 of this section.

The Government will evaluate technical and management performance, as
well as customer satisfaction with the contractor. The Contractor will
be afforded the opportunity to comment on both the completed master
contract and task order evaluations. The following evaluation process
schedule shall be followed:

a\) The A/OPC will electronically complete and submit (or mail, fax) the
task order evaluation form to the Contractor within 14 calendar days
after the quarter end.

b\) The Contractor shall make no changes to the agency's/organization
task order evaluation. The Contractor may provide comments in the space
provided. If additional space is necessary, use plain bond paper. If the
Contractor has no comments, it shall so indicate in the comment area.
The Contractor shall return the completed task order evaluation form to
the A/OPC and provide a copy to the GSA Contracting Officer within **10
calendar days** of receipt of the evaluation. GSA reserves the right to
verify task order evaluations with the A/OPC.

c\) The A/OPC will attach the completed task order evaluation into the
agency's/organization's task order file. This documentation must be
maintained by the A/OPC in accordance with applicable record management
procedures.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

d\) The GSA Contracting Office will consolidate and tabulate all
completed agency/organization task order evaluations, review the
Contractor's performance under the master contract, and complete the
master contract evaluation form each quarter. Once complete, the GSA
Contracting Office will forward the completed master contract evaluation
form to the Contractor for comments. The Contractor shall make no
changes to the master contract evaluation. The Contractor may provide
comments in the space provided. If additional space is necessary, use
plain bond paper. If the Contractor has no comments, it shall so
indicate in the comment area. The Contractor shall return the completed
master contract evaluation form to the GSA Contracting Office within
**10 calendar days** of receipt of the evaluation.

e\) At the conclusion of the master contract, the GSA Contracting Office
will provide an overall assessment of contractor performance utilizing
the performance standards indicated. Contractors shall be given a
minimum of 30 calendar days to submit comments, rebutting statements, or
additional information. The GSA will provide for review at a level above
the GSA Contracting Officer to consider disagreements between the
parties regarding the evaluation. The ultimate conclusion on the
performance evaluation is a decision of the GSA. Copies of the
evaluation, contractor response and review comments, if any, shall be
retained as part of the evaluation and may be used to support future
award decisions for a period no longer than 3 years after completion of
contract performance. The completed evaluation shall not be released to
other than Government personnel and the contractor whose performance is
being evaluated and will be considered "Source Selection Information."

The GSA Contracting Office will maintain a database of contractor
performance ratings for all task orders. The task order ratings, along
with performance documentation supporting the original contract awards,
will be made available to agencies/organizations for review. Master and
task order evaluations, along with the Contractor's comments, will be
made a part of the contract file and will be used as a portion of the
past performance indicators for future Government work.

## 46. TASK ORDER EVALUATION: CITC-FCXC-\_\_\_ (MAY 1997)

The task order evaluation forms are to be completed by the A/OPC each
quarter (1 October, 1 January, 1 April and 1 July) and at the completion
of the task order to evaluate the Contractor's performance. Completed
evaluations are to be electronically forwarded to the GSA Contracting
Officer at the Internet address: rebecca.koses@gsa.gov.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

**TASK ORDER PERFORMANCE QUESTIONNAIRE**

**NOTE: Offerors DO NOT fill out this form. This is the questionnaire
which will be used by A/OPCs in their quarterly task order evaluations**

**Contact Information:**

  ---------------- ------- ----------- --------- ---------- -----------------------
  Name:                                          Phone:     

                                                 Fax:       

  Title/Position                                            

                                                            

  Company Name &                                            
  Address:                                                  

                                                            

                                                            

                                                            
  ---------------- ------- ----------- --------- ---------- -----------------------

**Relationship Information:**

  -------------- -------------------------- -- ----------------------------
  Contractor:                                  

                                               

  Contract                                     
  Number/Task                                  
  Order Number:                                
  -------------- -------------------------- -- ----------------------------

Describe the products and/or services that are being/were provided:

  -----------------------------------------------------------------------

  -----------------------------------------------------------------------

  ----------------------------------------- -----------------------------
  Period of Performance (Start and End      
  Dates):                                   

  ----------------------------------------- -----------------------------

  ------------------------ ------------- -------------------------------------
  Type of Contract Award:  Competitive   
                           Process (Best 
                           Value)        

                           Competitive   
                           Process       
                           (Lowest       
                           Price)        

                           Sole-Source   

  Initial Cost Estimate                  

  Actual Contract Cost: at               
  Beginning:                             

  Current or Final                       
  Contract Cost:                         
  ------------------------ ------------- -------------------------------------

**PAST PERFORMANCE QUESTIONNAIRE**

  ---------------- ------------------------------------------------------- ------
  **1. To what                                                             
  extent did the                                                           
  contractor                                                               
  adhere to their                                                          
  implementation                                                           
  schedule?**                                                              

                   Considerably shortened and smooth implementation        
                   (Excellent)                                             

                   Implementation on time as scheduled (Good)              

                   Implementation delayed and behind schedule              
                   (Unsatisfactory)                                        
  ---------------- ------------------------------------------------------- ------

  --------------- ------------------------------------------------------- ------
  **2. To what                                                            
  extent did the                                                          
  contractor                                                              
  submit required                                                         
  reports and                                                             
  documentation                                                           
  in a timely                                                             
  manner?                                                                 
  (including                                                              
  invoices)**                                                             

                  On time every time (Excellent)                          

                  Usually on-time, but periods of delays (at start or     
                  just occasionally throughout contract) (Good)           

                  Information is out-dated by time of receipt and/or      
                  reports are almost always delayed (Unsatisfactory)      
  --------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **3. To what                                                           
  extend were                                                            
  the                                                                    
  contractor's                                                           
  reports                                                                
  accurate and                                                           
  complete?                                                              
  (including                                                             
  invoices)**                                                            

                 Very Accurate, detailed, and useful reports (Excellent) 

                 Accurate reports, more details provided promptly upon   
                 request (Good)                                          

                 Errors found in reports or invoices (Unsatisfactory)    
  -------------- ------------------------------------------------------- ------

  ------------ ------------------------------------------------------- ------
  **4. How                                                             
  well did the                                                         
  contractor                                                           
  solve                                                                
  problems                                                             
  without                                                              
  guidance                                                             
  from you?**                                                          

               Constantly monitored system, noticed potential problem  
               areas, and offered solutions on their own initiative    
               (Excellent)                                             

               Responded promptly and resolved any problems brought to 
               their attention (Good)                                  

               Required constant follow-up to ensure that problems     
               were resolved as agreed. (Unsatisfactory)               
  ------------ ------------------------------------------------------- ------

  ------------------ ------------------------------------------------------- ------
  **5. Did the                                                               
  contractor commit                                                          
  adequate resources                                                         
  to the contract to                                                         
  meet your needs                                                            
  (implementation,                                                           
  day-to-day, and                                                            
  emergency or                                                               
  problem                                                                    
  situations)?**                                                             

                     Provided timely and talented resources during all       
                     phases of the contract life (Excellent)                 

                     Abundant resources at start of contract, but needed     
                     re-assembly of resources to deal with problems or       
                     emergencies (short time delay) (Good)                   

                     Provided insufficient or unknowledgeable resources      
                     (Unsatisfactory)                                        
  ------------------ ------------------------------------------------------- ------

  ------------------------ ------------------------------------------------------- ------
  **6. What level of                                                               
  integration experience                                                           
  has the contractor                                                               
  demonstrated                                                                     
  (software/hardware)?**                                                           

                           Very knowledgeable, smooth integration with customer's  
                           internal computer systems (Excellent)                   

                           Knowledgeable for routine installations; however,       
                           additional resources were required to handle unusual    
                           configurations (Good)                                   

                           Rough integration, programming "bugs", required         
                           corrective measures by customer's computer systems      
                           staff (Unsatisfactory)                                  
  ------------------------ ------------------------------------------------------- ------

  --------------- ------------------------------------------------------- ------
  **7. To what                                                            
  extend did the                                                          
  contractor                                                              
  provide timely                                                          
  technical                                                               
  assistance?**                                                           

                  Knowledgeable, quick response to problems on and        
                  off-site (Excellent)                                    

                  Quick response, but not always knowledgeable OR         
                  Knowledgeable, but not always prompt (Good)             

                  Slow, barely competent assistance (Unsatisfactory)      
  --------------- ------------------------------------------------------- ------

  ----------------- ------------------------------------------------------- ------
  **8. How                                                                  
  effective has the                                                         
  contractor been                                                           
  in identifying                                                            
  user                                                                      
  requirements?**                                                           

                    Anticipates needs and provides solutions before         
                    requested (Excellent)                                   

                    Provides just what is needed when requested (Good)      

                    Requires several attempts and much discussion before    
                    new needs can be met (Unsatisfactory)                   
  ----------------- ------------------------------------------------------- ------

  ----------------- ------------------------------------------------------- ------
  **9. How flexible                                                         
  was the                                                                   
  contractor in                                                             
  responding to                                                             
  various levels of                                                         
  the customer's                                                            
  organization?**                                                           

                    Willing and able to answer questions and provide        
                    information (ad hoc reports if necessary) to anyone     
                    within the organization within the security boundaries  
                    of the contract (Excellent)                             

                    Preferred to respond to all inquiries through a central 
                    contact point but would provide ad hoc reports at the   
                    request of users (within the security boundaries of the 
                    contract) (Good)                                        

                    Required all information to go through a central point  
                    of contact (including reports) (Unsatisfactory)         
  ----------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **10. How                                                              
  useful was the                                                         
  contractor's                                                           
  customer                                                               
  service                                                                
  support?**                                                             

                 Contact made on first attempt, courteous,               
                 knowledgeable, and responsive to questions and requests 
                 for all levels of the organization (Excellent)          

                 Contact usually on first attempt, usually courteous,    
                 usually knowledgeable, usually timely response to       
                 questions and requests (different levels of service for 
                 different levels within the organization) (Good)        

                 Hard to make contact, sometimes rude, sometimes         
                 unknowledgeable, often required follow-up to obtain     
                 answers or ensure requests were met (Unsatisfactory)    
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **11. How                                                              
  satisfactory                                                           
  is the                                                                 
  contractor's                                                           
  product?**                                                             

                 Cards delivered on time, last until expiration,         
                 replaced promptly, users like card (Excellent)          

                 Occasional problems with card quality (flattening,      
                 breaking, mag stripe erasing), but replaced quickly     
                 (Good)                                                  

                 Cards flatten or break often, constant replacement is   
                 necessary, users inconvenienced during replacement      
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **12. How                                                              
  stable is the                                                          
  contractor's                                                           
  merchant                                                               
  network?**                                                             

                 No problems, not noticeable if system "goes down",      
                 merchants know how to process card (Excellent)          

                 Occasional "down-time", but rare and quickly resolved,  
                 sometimes slight delay between merchants being added to 
                 network and knowing how to process card \-- but quickly 
                 resolved when identified (Good)                         

                 Merchants (on network) often unfamiliar with card       
                 procedures, user's inconvenienced by system "down time" 
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **13. In your                                                          
  opinion, how                                                           
  secure is the                                                          
  contractor's                                                           
  system? If you                                                         
  do not have                                                            
  "first-hand"                                                           
  knowledge of                                                           
  the                                                                    
  contractor's                                                           
  physical                                                               
  security                                                               
  procedures or                                                          
  data security                                                          
  procedures,                                                            
  please answer                                                          
  based on what                                                          
  you've been                                                            
  told by the                                                            
  contractor.                                                            
  ???**                                                                  

                 Physical system and data protection is ensured through  
                 rigorous security measures which are constantly         
                 reviewed and upgraded to maintain the best protection   
                 possible (Excellent)                                    

                 Standard data protection is maintained through password 
                 access and "virus" checks. Physical security is         
                 adequate (Good)                                         

                 Physical and/or data security has been compromised but  
                 corrective measures were barely adequate                
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  ------------ ------------------------------------------------------- ------
  **14. How                                                            
  aggressive                                                           
  has the                                                              
  contractor                                                           
  been in                                                              
  stopping                                                             
  card use                                                             
  fraud?**                                                             

               Cards are canceled immediately upon notification,       
               contractor cooperates fully with any fraud              
               investigation on charges made before the card was       
               reported, and reports make possible fraud easy to       
               identify (Excellent)                                    

               Cards are canceled immediately upon notification and    
               reports can be used to identify possible fraud (Good)   

               Cards are canceled next business day or later, have     
               found instances of charges on invoice made after card   
               was reported to contractor (Unsatisfactory)             
  ------------ ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **15. How                                                              
  effective is                                                           
  the                                                                    
  contractor's                                                           
  method of                                                              
  limiting                                                               
  purchases to                                                           
  those                                                                  
  authorized                                                             
  under the                                                              
  terms of the                                                           
  contract?**                                                            

                 Merchants will not accept the card for items not        
                 authorized under the terms of the contract (Excellent)  

                 "Unauthorized" purchases are clearly identified on the  
                 reports/invoice to allow us to take internal            
                 disciplinary measures (Good)                            

                 All unauthorized purchases must be researched           
                 internally to determine if the item purchased was       
                 appropriate use of the card (Unsatisfactory)            
  -------------- ------------------------------------------------------- ------

  --------------- ------------------------------------------------------- ------
  **16. How                                                               
  helpful is the                                                          
  contractor when                                                         
  dealing with                                                            
  emergency                                                               
  situations?**                                                           

                  Contractor anticipates the impact of newsworthy         
                  emergencies before notification, card delivery is       
                  expedited, purchase parameters are expanded or          
                  restricted as needed (Excellent)                        

                  Contractor responds quickly to emergency requests       
                  (Good)                                                  

                  Contractor handles all requests the same, regardless of 
                  the situation (Unsatisfactory)                          
  --------------- ------------------------------------------------------- ------

  ----------------- ------------------------------------------------------- ------
  **17. How                                                                 
  "user-friendly"                                                           
  are the                                                                   
  contractor's                                                              
  forms and                                                                 
  interfaces?**                                                             

                    Forms and computer interfaces are intuitive (no         
                    training needed), easy to understand and complete;      
                    computer interfaces are also transparent to the user,   
                    and "idiot proof" (Excellent)                           

                    Form instructions are clear, computer interfaces        
                    require minimal training to use (Good)                  

                    Forms are confusing, computer interfaces require        
                    extensive training and computer skills to use           
                    (Unsatisfactory)                                        
  ----------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **18. How                                                              
  useable and                                                            
  accurate are                                                           
  the guides and                                                         
  instructions                                                           
  provided to                                                            
  the end                                                                
  users?**                                                               

                 User instructions are stand-alone documents.            
                 Clarifications are not necessary (Excellent)            

                 User instructions are clear, accurate and up-to-date    
                 (Good)                                                  

                 User instructions have errors and are out-dated causing 
                 user confusion (Unsatisfactory)                         
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **19. How                                                              
  flexible and                                                           
  accurate are                                                           
  the                                                                    
  contractor's                                                           
  financial                                                              
  systems?**                                                             

                 Transactions are posted quickly, debits and credit by   
                 transaction are clearly identified, payments with split 
                 disbursements (single check for more than one account)  
                 are made according to directions, problem transactions  
                 are clearly identified throughout the resolution        
                 process (Excellent)                                     

                 Transactions are posted promptly, debit and credits by  
                 card or account are identified, split disbursements are 
                 made according to directions, and problem transactions  
                 are identified (Good)                                   

                 Often transactions are posted late, causing             
                 difficulties reconciling the invoice with user          
                 receipts, payments are applied to the oldest debits     
                 regardless of instructions, problem transactions get    
                 "lost" in the system so resolution is never clear       
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **20. How                                                              
  effective are                                                          
  the                                                                    
  contractor's                                                           
  problem                                                                
  resolution                                                             
  processes?**                                                           

                 Questionable transactions are promptly credited if not  
                 resolved by payment due date, documentation is quickly  
                 forwarded, corrective action is taken to ensure         
                 contractor errors are not repeated, and transactions    
                 are re-billed on the next invoice if the error was made 
                 on our end (Excellent)                                  

                 Questionable transactions are resolved, corrective      
                 action is taken for contractor errors, prompt payment   
                 is expected for any charges that were our error (Good)  

                 Cards have been suspended while arguing about           
                 questionable transactions, documentation is slow in     
                 coming, and because of the contractor's financial       
                 system the final account balance is often muddled       
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **21. How                                                              
  useable and                                                            
  useful is your                                                         
  access to the                                                          
  contractor's                                                           
  database?**                                                            

                 All information is accessible and up-to-date (current   
                 or previous day), standard and ad hoc reports can be    
                 created and downloaded to our computer system,          
                 interface is easy to understand, customize, and use     
                 (Excellent)                                             

                 Standard information is accessible and up-to-date (up   
                 to a week delay), standard reports can be downloaded to 
                 our system, interface is easy to use (Good)             

                 Information is out-dated and useless (just a copy of    
                 monthly paper reports), minimal reports are available   
                 for downloading, interface is difficult and requires    
                 extensive training (Unsatisfactory)                     
  -------------- ------------------------------------------------------- ------

**FLEET CARD**

**Below are 43 different data elements and services. For each item
please indicate whether the contractor currently provides/maintains that
information for you:**

  --------------------------------------------------------------- ---------
                                                                  **Yes**

  Reports summarized at different levels of your organization     

  Accounting Code                                                 

  Minority/women owned business codes (1057 information)          

  1099 status                                                     

  Equipment Type (description or code)                            

  Specific Equipment Identification (e.g., license plate number)  

  Individual Equipment Fuel Type (e.g., gasoline or diesel)       

  Purchase parameters by card                                     

  Computerized ordering forms or processes                        

  Electronic File Transfer (e.g., TCP/IP)                         

  Magnetic Tape reports and invoices                              

  EDI (ASC X12)                                                   

  Taxes Identified on Invoice (state motor fuel tax, sales tax,   
  and FET)                                                        

  Taxes [Deducted]{.underline} prior to Invoice Net Amount Due    

  Date of Purchase                                                

  Time of Purchase                                                

  Transaction Number (identifying each individual transaction)    

  User Identification (signature or PIN)                          

  Merchant Type (e.g., fuel, maintenance, repair)                 

  Merchant Name                                                   

  Location Identification (Name or Number of individual station)  

  Location Address (including state and zip code)                 
  --------------------------------------------------------------- ---------

  --------------------------------------------------------------- ---------
                                                                  **Yes**

  --------------------------------------------------------------- ---------

  --------------------------------------------------------------- -------
  Merchant zip code                                               

  Merchant's Taxpayer identification number                       

  Merchant's area code and telephone number                       

  Type of Purchase (fuel or non-fuel)                             

  Type of Fuel Purchased (e.g., gasoline or diesel)               

  Grade of Fuel (regular, mid-grade, premium)                     

  Type of Unit (e.g., gallon, liter)                              

  Number of Units Purchased                                       

  Price per Unit                                                  

  Total Price (Extended Total)                                    

  Non-Fuel Product Type (e.g., car wash, TBA, oil, repair)        

  Non-Fuel Total Price                                            

  Federal Excise Tax                                              

  State Motor Fuel Tax                                            

  State Sales Tax                                                 

  Local Motor Fuel Tax                                            

  Local Sales Tax                                                 

  Discounts off fuel (from posted price)                          

  Discounts off non-fuel (from standard price)                    

  Order Number                                                    

  Merchant DUNS Number                                            
  --------------------------------------------------------------- -------

**COMMENTS:**

  -----------------------------------------------------------------------

  -----------------------------------------------------------------------

**TRAVEL CARD**

**Below are 32 different data elements and services. For each item
please indicate whether the contractor currently provides/maintains that
information for you:**

  --------------------------------------------------------------- ---------
                                                                  **Yes**

  Reports summarized at different levels of your organization     

  Accounting Code                                                 

  Minority/women owned business codes (1057 information)          

  1099 status                                                     

  Purchase parameters by card                                     

  Computerized ordering forms or processes                        

  Electronic File Transfer (e.g., TCP/IP)                         

  Magnetic Tape reports and invoices                              

  EDI (ASC X12)                                                   

  Sales tax amount                                                

  Carrier/Merchant/Establishment Name                             

  Carrier/Merchant/Establishment address (city and state)         

  Merchant zip code                                               

  Merchant's Taxpayer identification number                       

  Merchant's area code and telephone number                       

  Transaction Number (identifying each individual transaction)    

  Unit Cost                                                       

  Quantities                                                      

  Unit of Measure                                                 

  Product Codes                                                   

  Product Descriptions (line item detail)                         
  --------------------------------------------------------------- ---------

  --------------------------------------------------------------- ---------
                                                                  **Yes**

  Ship to/From Zip Codes                                          

  Freight Amount                                                  

  Duty Amount                                                     

  Order Date                                                      

  Discount Amount                                                 

  Order Number                                                    

  Merchant DUNS Number                                            

  Hotel/Motel Fire Safety Act (FSA) statistics                    

  Airline Ticket Numbers for Common Carrier Transactions          

  Class of Travel Identifier (Carrier's fare/class of service     
  code)                                                           

  Maximum Available Leg-by-Leg Itinerary Data for Common Air/Rail 
  Carrier Transactions                                            
  --------------------------------------------------------------- ---------

**COMMENTS:**

  -----------------------------------------------------------------------

  -----------------------------------------------------------------------

**PURCHASE CARD**

**Below are 28 different data elements and services. For each item
please indicate whether the contractor currently provides/maintains that
information for you:**

  --------------------------------------------------------------- ---------
                                                                  **Yes**

  Reports summarized at different levels of your organization     

  Accounting Code                                                 

  Minority/women owned business codes (1057 information)          

  1099 status                                                     

  Purchase parameters by card                                     

  Computerized ordering forms or processes                        

  Electronic File Transfer (e.g., TCP/IP)                         

  Magnetic Tape reports and invoices                              

  EDI (ASC X12)                                                   

  Sales tax amount                                                

  Merchant/Establishment Name                                     

  Merchant/Establishment address (city and state)                 

  Merchant zip code                                               

  Merchant's Taxpayer identification number                       

  Merchant's area code and telephone number                       

  Transaction Number (identifying each individual transaction)    

  Unit Cost                                                       

  Quantities                                                      

  Unit of Measure                                                 

  Product Codes                                                   

  Product Descriptions (line item detail)                         
  --------------------------------------------------------------- ---------

  --------------------------------------------------------------- ---------
                                                                  **Yes**

  Ship to/From Zip Codes                                          

  Freight Amount                                                  

  Duty Amount                                                     

  Order Date                                                      

  Discount Amount                                                 

  Order Number                                                    

  Merchant DUNS Number                                            
  --------------------------------------------------------------- ---------

**COMMENTS:**

  -----------------------------------------------------------------------

  -----------------------------------------------------------------------

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 47. MASTER CONTRACT EVALUATION: CITC-FCXC-\_\_\_ (MAY 1997)

The master contract evaluation form is to be completed by the GSA
Contracting Officer each quarter (1 October, 1 January, 1 April and 1
July) and at the completion of the master contract(s) to evaluate the
Contractor's performance.

**MASTER CONTRACT PERFORMANCE QUESTIONNAIRE**

**NOTE: Offerors DO NOT fill out this form. This is the questionnaire
which will be used by GSA Contracting Officer in his/her quarterly
master contract evaluations**

**PAST PERFORMANCE QUESTIONNAIRE**

  ---------------- ------------------------------------------------------- ------
  **1. To what                                                             
  extent did the                                                           
  contractor                                                               
  adhere to their                                                          
  implementation                                                           
  schedule?**                                                              

                   Considerably shortened and smooth implementation        
                   (Excellent)                                             

                   Implementation on time as scheduled (Good)              

                   Implementation delayed and behind schedule              
                   (Unsatisfactory)                                        
  ---------------- ------------------------------------------------------- ------

  --------------- ------------------------------------------------------- ------
  **2. To what                                                            
  extent did the                                                          
  contractor                                                              
  submit required                                                         
  reports and                                                             
  documentation                                                           
  in a timely                                                             
  manner?                                                                 
  (including                                                              
  invoices)**                                                             

                  On time every time (Excellent)                          

                  Usually on-time, but periods of delays (at start or     
                  just occasionally throughout contract) (Good)           

                  Information is out-dated by time of receipt and/or      
                  reports are almost always delayed (Unsatisfactory)      
  --------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **3. To what                                                           
  extent were                                                            
  the                                                                    
  contractor's                                                           
  reports                                                                
  accurate and                                                           
  complete?                                                              
  (including                                                             
  invoices)**                                                            

                 Very Accurate, detailed, and useful reports (Excellent) 

                 Accurate reports, more details provided promptly upon   
                 request (Good)                                          

                 Errors found in reports or invoices (Unsatisfactory)    
  -------------- ------------------------------------------------------- ------

  ------------ ------------------------------------------------------- ------
  **4. How                                                             
  well did the                                                         
  contractor                                                           
  solve                                                                
  problems                                                             
  without                                                              
  guidance                                                             
  from you?**                                                          

               Constantly monitored system, noticed potential problem  
               areas, and offered solutions on their own initiative    
               (Excellent)                                             

               Responded promptly and resolved any problems brought to 
               their attention (Good)                                  

               Required constant follow-up to ensure that problems     
               were resolved as agreed. (Unsatisfactory)               
  ------------ ------------------------------------------------------- ------

  ------------------ ------------------------------------------------------- ------
  **5. Did the                                                               
  contractor commit                                                          
  adequate resources                                                         
  to the contract to                                                         
  meet your needs                                                            
  (implementation,                                                           
  day-to-day, and                                                            
  emergency or                                                               
  problem                                                                    
  situations)?**                                                             

                     Provided timely and talented resources during all       
                     phases of the contract life (Excellent)                 

                     Abundant resources at start of contract, but needed     
                     re-assembly of resources to deal with problems or       
                     emergencies (short time delay) (Good)                   

                     Provided insufficient or unknowledgeable resources      
                     (Unsatisfactory)                                        
  ------------------ ------------------------------------------------------- ------

  ------------------------ ------------------------------------------------------- ------
  **6. What level of                                                               
  integration experience                                                           
  has the contractor                                                               
  demonstrated                                                                     
  (software/hardware)?**                                                           

                           Very knowledgeable, smooth integration with customer's  
                           internal computer systems (Excellent)                   

                           Knowledgeable for routine installations; however,       
                           additional resources were required to handle unusual    
                           configurations (Good)                                   

                           Rough integration, programming "bugs", required         
                           corrective measures by customer's computer systems      
                           staff (Unsatisfactory)                                  
  ------------------------ ------------------------------------------------------- ------

  --------------- ------------------------------------------------------- ------
  **7. To what                                                            
  extend did the                                                          
  contractor                                                              
  provide timely                                                          
  technical                                                               
  assistance?**                                                           

                  Knowledgeable, quick response to problems on and        
                  off-site (Excellent)                                    

                  Quick response, but not always knowledgeable OR         
                  Knowledgeable, but not always prompt (Good)             

                  Slow, barely competent assistance (Unsatisfactory)      
  --------------- ------------------------------------------------------- ------

  ----------------- ------------------------------------------------------- ------
  **8. How                                                                  
  effective has the                                                         
  contractor been                                                           
  in identifying                                                            
  user                                                                      
  requirements?**                                                           

                    Anticipates needs and provides solutions before         
                    requested (Excellent)                                   

                    Provides just what is needed when requested (Good)      

                    Requires several attempts and much discussion before    
                    new needs can be met (Unsatisfactory)                   
  ----------------- ------------------------------------------------------- ------

  ----------------- ------------------------------------------------------- ------
  **9. How flexible                                                         
  was the                                                                   
  contractor in                                                             
  responding to                                                             
  various levels of                                                         
  the customer's                                                            
  organization?**                                                           

                    Willing and able to answer questions and provide        
                    information (ad hoc reports if necessary) to anyone     
                    within the organization within the security boundaries  
                    of the contract (Excellent)                             

                    Preferred to respond to all inquiries through a central 
                    contact point but would provide ad hoc reports at the   
                    request of users (within the security boundaries of the 
                    contract) (Good)                                        

                    Required all information to go through a central point  
                    of contact (including reports) (Unsatisfactory)         
  ----------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **10. How                                                              
  useful was the                                                         
  contractor's                                                           
  customer                                                               
  service                                                                
  support?**                                                             

                 Contact made on first attempt, courteous,               
                 knowledgeable, and responsive to questions and requests 
                 for all levels of the organization (Excellent)          

                 Contact usually on first attempt, usually courteous,    
                 usually knowledgeable, usually timely response to       
                 questions and requests (different levels of service for 
                 different levels within the organization) (Good)        

                 Hard to make contact, sometimes rude, sometimes         
                 unknowledgeable, often required follow-up to obtain     
                 answers or ensure requests were met (Unsatisfactory)    
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **11. How                                                              
  satisfactory                                                           
  is the                                                                 
  contractor's                                                           
  product?**                                                             

                 Cards delivered on time, last until expiration,         
                 replaced promptly, users like card (Excellent)          

                 Occasional problems with card quality (flattening,      
                 breaking, mag stripe erasing), but replaced quickly     
                 (Good)                                                  

                 Cards flatten or break often, constant replacement is   
                 necessary, users inconvenienced during replacement      
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **12. How                                                              
  stable is the                                                          
  contractor's                                                           
  merchant                                                               
  network?**                                                             

                 No problems, not noticeable if system "goes down",      
                 merchants know how to process card (Excellent)          

                 Occasional "down-time", but rare and quickly resolved,  
                 sometimes slight delay between merchants being added to 
                 network and knowing how to process card \-- but quickly 
                 resolved when identified (Good)                         

                 Merchants (on network) often unfamiliar with card       
                 procedures, user's inconvenienced by system "down time" 
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  --------------- ------------------------------------------------------- ------
  **13. In your                                                           
  opinion, how                                                            
  secure is the                                                           
  contractor's                                                            
  system? If you                                                          
  do not have                                                             
  "first-hand"                                                            
  knowledge of                                                            
  the                                                                     
  contractor's                                                            
  physical                                                                
  security                                                                
  procedures or                                                           
  data security                                                           
  procedures,                                                             
  please answer                                                           
  based on what                                                           
  you've been                                                             
  told by the                                                             
  contractor.**                                                           

                  Physical system and data protection is ensured through  
                  rigorous security measures which are constantly         
                  reviewed and upgraded to maintain the best protection   
                  possible (Excellent)                                    

                  Standard data protection is maintained through password 
                  access and "virus" checks. Physical security is         
                  adequate (Good)                                         

                  Physical and/or data security has been compromised but  
                  corrective measures were barely adequate                
                  (Unsatisfactory)                                        
  --------------- ------------------------------------------------------- ------

  ------------ ------------------------------------------------------- ------
  **14. How                                                            
  aggressive                                                           
  has the                                                              
  contractor                                                           
  been in                                                              
  stopping                                                             
  card use                                                             
  fraud?**                                                             

               Cards are canceled immediately upon notification,       
               contractor cooperates fully with any fraud              
               investigation on charges made before the card was       
               reported, and reports make possible fraud easy to       
               identify (Excellent)                                    

               Cards are canceled immediately upon notification and    
               reports can be used to identify possible fraud (Good)   

               Cards are canceled next business day or later, have     
               found instances of charges on invoice made after card   
               was reported to contractor (Unsatisfactory)             
  ------------ ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **15. How                                                              
  effective is                                                           
  the                                                                    
  contractor's                                                           
  method of                                                              
  limiting                                                               
  purchases to                                                           
  those                                                                  
  authorized                                                             
  under the                                                              
  terms of the                                                           
  contract?**                                                            

                 Merchants will not accept the card for items not        
                 authorized under the terms of the contract (Excellent)  

                 "Unauthorized" purchases are clearly identified on the  
                 reports/invoice to allow us to take internal            
                 disciplinary measures (Good)                            

                 All unauthorized purchases must be researched           
                 internally to determine if the item purchased was       
                 appropriate use of the card (Unsatisfactory)            
  -------------- ------------------------------------------------------- ------

  --------------- ------------------------------------------------------- ------
  **16. How                                                               
  helpful is the                                                          
  contractor when                                                         
  dealing with                                                            
  emergency                                                               
  situations?**                                                           

                  Contractor anticipates the impact of newsworthy         
                  emergencies before notification, card delivery is       
                  expedited, purchase parameters are expanded or          
                  restricted as needed (Excellent)                        

                  Contractor responds quickly to emergency requests       
                  (Good)                                                  

                  Contractor handles all requests the same, regardless of 
                  the situation (Unsatisfactory)                          
  --------------- ------------------------------------------------------- ------

  ----------------- ------------------------------------------------------- ------
  **17. How                                                                 
  "user-friendly"                                                           
  are the                                                                   
  contractor's                                                              
  forms and                                                                 
  interfaces?**                                                             

                    Forms and computer interfaces are intuitive (no         
                    training needed), easy to understand and complete;      
                    computer interfaces are also transparent to the user,   
                    and "idiot proof" (Excellent)                           

                    Form instructions are clear, computer interfaces        
                    require minimal training to use (Good)                  

                    Forms are confusing, computer interfaces require        
                    extensive training and computer skills to use           
                    (Unsatisfactory)                                        
  ----------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **18. How                                                              
  useable and                                                            
  accurate are                                                           
  the guides and                                                         
  instructions                                                           
  provided to                                                            
  the end                                                                
  users?**                                                               

                 User instructions are stand-alone documents.            
                 Clarifications are not necessary (Excellent)            

                 User instructions are clear, accurate and up-to-date    
                 (Good)                                                  

                 User instructions have errors and are out-dated causing 
                 user confusion (Unsatisfactory)                         
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **19. How                                                              
  flexible and                                                           
  accurate are                                                           
  the                                                                    
  contractor's                                                           
  financial                                                              
  systems?**                                                             

                 Transactions are posted quickly, debits and credit by   
                 transaction are clearly identified, payments with split 
                 disbursements (single check for more than one account)  
                 are made according to directions, problem transactions  
                 are clearly identified throughout the resolution        
                 process (Excellent)                                     

                 Transactions are posted promptly, debit and credits by  
                 card or account are identified, split disbursements are 
                 made according to directions, and problem transactions  
                 are identified (Good)                                   

                 Often transactions are posted late, causing             
                 difficulties reconciling the invoice with user          
                 receipts, payments are applied to the oldest debits     
                 regardless of instructions, problem transactions get    
                 "lost" in the system so resolution is never clear       
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  -------------- ------------------------------------------------------- ------
  **20. How                                                              
  effective are                                                          
  the                                                                    
  contractor's                                                           
  problem                                                                
  resolution                                                             
  processes?**                                                           

                 Questionable transactions are promptly credited if not  
                 resolved by payment due date, documentation is quickly  
                 forwarded, corrective action is taken to ensure         
                 contractor errors are not repeated, and transactions    
                 are re-billed on the next invoice if the error was made 
                 on our end (Excellent)                                  

                 Questionable transactions are resolved, corrective      
                 action is taken for contractor errors, prompt payment   
                 is expected for any charges that were our error (Good)  

                 Cards have been suspended while arguing about           
                 questionable transactions, documentation is slow in     
                 coming, and because of the contractor's financial       
                 system the final account balance is often muddled       
                 (Unsatisfactory)                                        
  -------------- ------------------------------------------------------- ------

  --------------------- ------------------------------------------------------- ------
  **21. How useable and                                                         
  useful is your access                                                         
  to the contractor's                                                           
  database?**                                                                   

                        All information is accessible and up-to-date (current   
                        or previous day), standard and ad hoc reports can be    
                        created and downloaded to our computer system,          
                        interface is easy to understand, customize, and use     
                        (Excellent)                                             

                        Standard information is accessible and up-to-date (up   
                        to a week delay), standard reports can be downloaded to 
                        our system, interface is easy to use (Good)             

                        Information is out-dated and useless (just a copy of    
                        monthly paper reports), minimal reports are available   
                        for downloading, interface is difficult and requires    
                        extensive training (Unsatisfactory)                     

  **22. How responsive                                                          
  was the contractor to                                                         
  agency/organization                                                           
  task                                                                          
  requests/orders?**                                                            

                        The Contractor responded to each and every task         
                        request/order from both mandatory and non-mandatory     
                        users and submitted an offer to each group while        
                        exceeding contract timeframe requirements (Excellent)   

                        The Contractor responded to every task request/order    
                        received from mandatory users and submitted an offer,   
                        and responded to most of the task requests/orders       
                        received from non-mandatory users and submitted an      
                        offer within contract timeframe requirements (Good)     

                        The Contractor responded to every task request/order    
                        received and submitted an offer, but was late in their  
                        submission (Unsatisfactory)                             

  **23. How well did                                                            
  the Contractor meet                                                           
  socio-economic                                                                
  goals?**                                                                      

                        The Contractor exceeded its goals for use of small,     
                        small-disadvantaged and women-owned small business      
                        (Excellent)                                             

                        The Contractor met its goals for use of small,          
                        small-disadvantaged and women-owned small business      
                        (Good)                                                  

                        The Contractor did not meet its goals for use of small, 
                        small-disadvantaged and women-owned small business      
                        (Unsatisfactory)                                        
  --------------------- ------------------------------------------------------- ------

**COMMENTS:**

  -----------------------------------------------------------------------

  -----------------------------------------------------------------------

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

## 48. PRIVACY ACT NOTIFICATION: 52.224-1 (APR 1984)

The Contractor will be required to design, develop, or operate a system
of records on individuals, to accomplish an agency function subject to
the Privacy Act of 1974, Public Law 93-579, December 31, 1974 (5 U.S.C.
552a) and applicable agency regulations. Violation of the Act may
involve the imposition of criminal penalties.

## 49. PRIVACY ACT: 52.224-2 (APR 1984)

\(a\) The Contractor agrees to\--

\(1\) Comply with the Privacy Act of 1974 (the Act) and the agency rules
and regulations issued under the Act in the design, development, or
operation of any system of records on individuals to accomplish an
agency function when the contract specifically identifies\--

\(i\) The systems of records; and

\(ii\) The design, development, or operation work that the contractor is
to perform;

\(2\) Include the Privacy Act notification contained in this contract in
every solicitation and resulting subcontract and in every subcontract
awarded without a solicitation, when the work statement in the proposed
subcontract requires the redesign, development, or operation of a system
of records on individuals that is subject to the Act; and

\(3\) Include this clause, including this subparagraph (3), in all
subcontracts awarded under this contract which requires the design,
development, or operation of such a system of records.

\(b\) In the event of violations of the Act, a civil action may be
brought against the agency involved when the violation concerns the
design, development, or operation of a system of records on individuals
to accomplish an agency function, and criminal penalties may be imposed
upon the officers or employees of the agency when the violation concerns
the operation of a system of records on individuals to accomplish an
agency function. For purposes of the Act, when the contract is for the
operation of a system of records on individuals to accomplish an agency
function, the Contractor is considered to be an employee of the agency.

\(c\) (1) "Operation of a system of records," as used in this clause,
means performance of any of the activities associated with maintaining
the system of records, including the collection, use, and dissemination
of records.

\(2\) "Record," as sued in this clause, means any item, collection, or
grouping of information about an individual that is maintained by an
agency, including, but not limited to, education, financial
transactions, medical history, and criminal or employment history and
that contains the person's name, or the identifying number, symbol, or
other identifying particular assigned to the individual, such as a
fingerprint or voiceprint or a photograph.

**ADDENDUM TO CLAUSE 52.212-4 CONTINUED**

\(3\) "System of records on individuals," as used in this clause, means
a group of any records under the control of any agency from which
information is retrieved by the name of the individual or by some
identifying number, symbol, or other identifying particular assigned to
the individual.

## 50. CONTRACTOR REQUEST FOR PAYMENT OF THE GUARANTEED MINIMUM: CITC-FCXC-\_\_\_ (MAY 1997)

At the conclusion of the initial 5-year base period and satisfactory
performance, the Contractor may request payment of the guaranteed
minimum. The request shall include:

a\) GSA Contract Number;

b\) Identification of business line(s) and CLIN(s);

c\) Date of request;

d\) The statement: "In accordance with Clause CITC-FCXC-\_\_\_ (MAY
1997) entitled Contractor Request for Payment of the Guaranteed Minimum,
\[[    Company Name      ]{.underline}\] is requesting payment of the
guaranteed minimum; and

e\) Demonstrate satisfactory performance in accordance with C.10,
Quality Assurance, and the addendum to 52.212-4, paragraph 45, Contract
Performance Standards.

# 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS---COMMERCIAL ITEMS (AUG 1996) (DEVIATION\--MAY 1996) 12.301(b)(4)

> \(a\) The Contractor agrees to comply with the following FAR clauses,
> which are incorporated in this contract by reference, to implement
> provisions of law or Executive orders applicable to acquisitions of
> commercial items:
>
> \(1\) 52.222-3, Convict Labor (E.O. 11755); and
>
> \(2\) 52.233-3, Protest After Award (31 U.S.C 3553).
>
> \(b\) The Contractor agrees to comply with the FAR clauses in this
> paragraph (b) which the Contracting Officer has indicated as being
> incorporated in this contract by reference to implement provisions of
> law or executive orders applicable to acquisitions of commercial items
> or components:

\*[   X   ]{.underline}\* (1) 52.203-6, Restrictions on Subcontractor
Sales to the Government, with Alternate I (41 U.S.C. 253g and 10 U.S.C.
2402).

\*[   X   ]{.underline}\* (2) 52.203-10, Price or Fee Adjustment for
Illegal or Improper Activity (41 U.S.C. 423).

\*[    X   ]{.underline}\* (3) 52.219-8, Utilization of Small Business
Concerns and Small Disadvantaged Business Concerns (15 U.S.C. 637 (d)(2)
and (3));

\*[   X   ]{.underline}\* (4) 52.219-9, Small, Small Disadvantaged and
Women-Owned Small Business Subcontracting Plan (15 U.S.C. 637 (d)(4));

\*\_\_\_\_\_\* (5) 52.219-14, Limitation on Subcontracting (15 U.S.C.
637(a)(14)).

\*[   X   ]{.underline}\* (6) 52.222-26, Equal Opportunity (E.O. 11246).

\*[   X   ]{.underline}\* (7) 52.222-35, Affirmative Action for Special
Disabled and Vietnam Era Veterans (38 U.S.C. 4212).

\*[   X   ]{.underline}\* (8) 52.222-36, Affirmative Action for
Handicapped Workers (29 U.S.C. 793).

\*[   X   ]{.underline}\* (9) 52.222-37, Employment Reports on Special
Disabled Veterans and Veterans of the Vietnam Era (38 U.S.C. 4212).

\*\_\_\_\_\_\* (10) 52.225-3, Buy American Act---Supplies (41 U.S.C.
10).

\*[   X   ]{.underline}\* (11) 552.225-9 Trade Agreements Act (Deviation
FAR 52.225-9).

\*\_\_\_\_\_\* (12) Reserved.

\*[   X   ]{.underline}\* (13) 52.225-18, European Union Sanctions for
End Products (E.O. 12849).

\*\_\_\_\_\_\* (14) 52.225-19, European Union Sanctions for Services
(E.O. 12849).

\*\_\_\_\_\_\* (15) (i) 52.225-21, Buy American Act---North American
Free Trade Agreement Implementation Act---Balance of Payments Program
(41 U.S.C 10, Pub. L. 103-187).

\*\_\_\_\_\_\* (ii) Alternate I of 52.225-21.

\*\_\_[X]{.underline}\_\_\* (16) 52.239-1, Privacy or Security
Safeguards (5 U.S.C. 552a).

\*[   X   ]{.underline}\* (17) 52.247-64, Preference for Privately Owned
U.S.-Flag Commercial Vessels (46 U.S.C. 1241).

\*\_\_\_\_\_\* (This acquisition is being conducted under
\*\_\_\_\_\_\_\* delegation of GSA\'s exclusive procurement authority
for FIP resources. The specific GSA DPA case number is \*\_\_\_\_\_\*

> \(c\) The Contractor agrees to comply with the FAR clauses in this
> paragraph (c), applicable to commercial services, which the
> Contracting Officer has indicated as being incorporated in this
> contract by reference to implement provisions of law or executive
> orders applicable to acquisitions of commercial items or components:

\*\_\_\_\_\_\* (1) 52.222-41, Service Contract Act of 1965, As amended
(41 U.S.C. 351, et seq.).

\*\_\_\_\_\_\* (2) 52.222-42, Statement of Equivalent Rates for Federal
Hires (29 U.S.C. 206 and 41 U.S.C. 351, et seq.).

\*\_\_\_\_\_\* (3) 52.222-43, Fair Labor Standards Act and Service
Contract Act---Price Adjustment (Multiple Year and Option Contracts) (29
U.S.C. 206 and 41 U.S.C. 351, et seq.).

\*\_\_\_\_\_\* (4) 52.222-44, Fair Labor Standards Act and Service
Contract Act---Price Adjustment (29 U.S.C. 206 and 41 U.S.C. 351, et
seq.).

\*\_\_\_\_\_\* (5) 52.222-47, SCA Minimum Wages and Fringe Benefits
Applicable to Successor Contract Pursuant to Predecessor Contractor
Collective Bargaining Agreement (CBA) (41 U.S.C. 351, et seq.).

> \(d\) Comptroller General Examination of Record. The Contractor agrees
> to comply with the provisions of this paragraph (d) if this contract
> was awarded using other than sealed bid, is in excess of the
> simplified acquisition threshold, and does not contain the clause at
> 52.215-2, Audit and Records---Negotiation.
>
> \(1\) The Comptroller General of the United States, or an authorized
> representative of the Comptroller General, shall have access to and
> right to examine any of the Contractor\'s directly pertinent records
> involving transactions related to this contract.
>
> \(2\) The Contractor shall make available at its offices at all
> reasonable times the records, materials, and other evidence for
> examination, audit, or reproduction, until 3 years after final payment
> under this contract or for any shorter period specified in FAR Subpart
> 4.7, Contractor Records Retention, of the other clauses of this
> contract. If this contract is completely or partially terminated, the
> records relating to the work terminated shall be made available for 3
> years after any resulting final termination settlement. Records
> relating to appeals under the disputes clause or to litigation or the
> settlement of claims arising under or relating to this contract shall
> be made available until such appeals, litigation, or claims are
> finally resolved.
>
> \(3\) As used in this clause, records include books, documents,
> accounting procedures and practices, and other data, regardless of
> type and regardless of form. This does not require the Contractor to
> create or maintain any record that the Contractor does not maintain in
> the ordinary course of business or pursuant to a provision of law.
>
> \(e\) Notwithstanding the requirements of the clauses in paragraphs
> (a), (b), (c) or (d) of this clause, the Contractor is not required to
> include any FAR clause, other than those listed below (and as may be
> required by an addenda to this paragraph to establish the
> reasonableness of prices under Part 15), in a subcontract for
> commercial items or commercial components---

\(1\) 52.222-26, Equal Opportunity (E.O. 11246);

\(2\) 52.222-35, Affirmative Action for Special Disabled and Vietnam Era
Veterans (38 U.S.C. 2012(a)); and

\(3\) 52.222-36, Affirmative Action for Handicapped Workers (29 U.S.C.
793).

\(4\) 52.247-64, Preference for Privately Owned U.S.-Flagged Commercial
Vessels (46 U.S.C. 1241) (flow down not required for subcontracts
awarded beginning May 1, 1996).

CONTRACT EXHIBITS AND CONTRACT DOCUMENTS

Exhibit 1 - Sample Small Business Subcontracting Plan

Exhibit 2 - Benchmark Task for Integrated Solution Card Services

Exhibit 3 - Benchmark Task for Fleet Card Services

Exhibit 4 - Benchmark Task for Travel Card Services

Exhibit 5 - Benchmark Task for Purchase Card Services

Exhibit 6 - Historic Programmatic Data for the Fleet Card Program

Exhibit 7 - Historic Programmatic Data for the Travel Card Program

Exhibit 8 - Historic Programmatic Data for the Purchase Card Program

Exhibit 9 - Mandatory Users of the Fleet Card Program

Exhibit 10 - Mandatory Users of the Travel Card Program

Exhibit 11 - Mandatory Users of the Purchase Card Program

Exhibit 12 - Card Design for the Integrated Solution Card

Exhibit 13 - Card Design for the Fleet Card Program

Exhibit 14 - Card Design for the Travel Card Program

Exhibit 15 - Card Design for the Purchase Card Program

Exhibit 16 - Sample Standard Task Request/Order

Exhibit 17 - Sample Tailored Task Request

Exhibit 18 - Sample Tailored Task Order

Exhibit 19 - Format for Charge Volume, Number of Transactions and
Cardholders

Exhibit 20 - Format for Client References

Exhibit 21 - Client Reference Questionnaire

Exhibit 22 - Format for Merchant Acceptance

Exhibit 23 - Client Reference Questionnaire for Value-Added Products and
Services

Exhibit 24 - Client Reference Questionnaire for Best Practices

Exhibit 25 - Client Reference Questionnaire for Promising Practices

Exhibit 26 - Office of Federal Procurement Policy Letter 89-1

Exhibit 27 - Format for Charge Volume

# INSTRUCTIONS TO OFFERORS SECTION

## 1. 52.212-1 INSTRUCTIONS TO OFFERORS\--COMMERCIAL ITEMS (OCT 1995)

\(a\) Standard industrial classification (SIC) code and small business
size standard. The SIC code and small business size standard for this
acquisition appear in Block 10 of the solicitation cover sheet (SF
1449). However, the small business size standard for a concern which
submits an offer in its own name, but which proposes to furnish an item
which it did not itself manufacture, is 500 employees.

\(b\) Submission of offers. Submit signed and dated offers to the office
specified in this solicitation at or before the exact time specified in
this solicitation. Offers ~~may~~ shall be submitted on the SF 1449,
letterhead stationery, ~~or~~ and as otherwise specified in the
solicitation. As a minimum, offers must show\--

\(1\) The solicitation number;

\(2\) The time specified in the solicitation for receipt of offers;

\(3\) The name, address, and telephone number of the offeror;

\(4\) A technical description ~~of the items being offered in sufficient
detail to evaluate compliance with the requirements in the solicitation.
This may include product literature, or other documents, if necessary~~;
as described in the "Instructions to Offerors" herein;

\(5\) ~~Terms of any express warranty~~;

\(6\) Price and any discount terms;

\(7\) \"Remit to\" address, if different than mailing address;

\(8\) A completed copy of the representations and certifications at FAR
52.212-3;

\(9\) Acknowledgment of Solicitation Amendments;

\(10\) ~~Past performance information, when included as an evaluation
factor, to include recent and relevant contracts for the same or similar
items and other references (including contract numbers, points of
contact with telephone numbers and other relevant information); and~~

\(11\) ~~If the offer is not submitted on the SF 1449, include a
statement specifying the extent of agreement with all terms, conditions,
and provisions included in the solicitation. Offers that fail to furnish
required representations or information, or reject the terms and
conditions of the solicitation may be excluded from consideration~~.

\(c\) Period for acceptance of offers. The offeror agrees to hold ~~the
prices in~~ its offer firm for

~~30~~ 240 calendar days from the date specified for receipt of offers,
unless another time period is specified in an addendum to the
solicitation.

\(d\) ~~Product samples. When required by the solicitation, product
samples shall be submitted at~~

~~or prior to the time specified for receipt of offers. Unless otherwise
specified in this solicitation, these samples shall be submitted at no
expense to the Government, and returned at the sender\'s request and
expense, unless they are destroyed during preaward testing~~.

\(e\) ~~Multiple offers. Offerors are encouraged to submit multiple
offers presenting alternative terms~~

~~and conditions or commercial items for satisfying the requirements of
this solicitation. Each offer~~

~~submitted will be evaluated separately~~.

\(f\) Late offers. Offers or modifications of offers received at the
address specified for the receipt

of offers after the exact time specified for receipt of offers will not
be considered.

\(g\) ~~Contract award (not applicable to Invitation for Bids). The
Government intends to~~

~~evaluate offers and award a contract without discussions with
offerors. Therefore, the offeror\'s initial offer should contain the
offeror\'s best terms from a price and technical standpoint. However,
the Government reserves the right to conduct discussions if later
determined by the Contracting Officer to be necessary. The Government
may reject any or all offers if such action is in the public interest;
accept other than the lowest offer; and waive informalities and minor
irregularities in offers received~~.

\(h\) ~~Multiple awards. The Government may accept any item or group of
items of an offer, unless~~

~~the offeror qualifies the offer by specific limitations. Unless
otherwise provided in the Schedule,~~

~~offers may not be submitted for quantities less than those specified.
The Government reserves the~~

~~right to make an award on any item for a quantity less than the
quantity offered, at the unit prices~~

~~offered, unless the offeror specifies otherwise in the offer~~.

\(i\) ~~Availability of requirements documents cited in the
solicitation. (1) The Index of~~

~~Federal Specifications, Standards and Commercial Item Descriptions and
the documents listed in it may be obtained from the General Services
Administration, Federal Supply Service Bureau,~~

~~Specifications Section, Suite 8100, 470 L\'Enfant Plaza, SW,
Washington, DC 20407 ((202)~~

~~755-0325/0326).~~

~~(2) The DOD Index of Specifications and Standards (DODISS) and
documents listed in it may be obtained from the Standardization
Documents Desk, Building 4D, 700 Robbins Avenue,~~

~~Philadelphia, PA 19111-5094 (telephone (215) 697-2569).~~

~~(i) Automatic distribution may be obtained on a subscription basis.~~

~~(ii) Individual documents may be ordered from the Telespecs ordering
system by touch-tone telephone. A customer number is required to use
this service and can be obtained from the Standardization~~

~~Documents Order Desk or the Special Assistance Desk (telephone (610)
607-2667/2179).~~

\(3\) ~~Nongovernment (voluntary) standards must be obtained from the
organization responsible for their preparation, publication or
maintenance~~.

## 2. INSTRUCTIONS TO OFFERORS: L-FSS-FCXC-\_\_\_ (MAY 1997)

Offerors are instructed to submit their offers in accordance with this
section.

## 3. SUBMISSION OF OFFERS IN THE ENGLISH LANGUAGE: 52.214-34 (APR 1991) 

Offers submitted in response to this solicitation shall be in the
English language. Offers received in other than English shall be
rejected.

## 4. SUBMISSION OF OFFERS IN U.S. CURRENCY: 52.214-35 (APR 1991) 

Offers submitted in response to this solicitation shall be in terms of
U.S. dollars. Offers received in other than U.S. dollars shall be
rejected.

## 5. PREAWARD ON-SITE EQUAL OPPORTUNITY COMPLIANCE REVIEW: 52.222-24 (APR 1984) 

An award in the amount of \$1 million or more will not be made under
this solicitation unless the offeror and each of its known first-tier
subcontractors (to whom it intends to award a subcontract of \$1 million
or more) are found, on the basis of a compliance review, to be able to
comply with the provisions of the Equal Opportunity clause of this
solicitation.

## 6. SERVICE OF PROTEST: 52.233-2 (AUG 1996)

> \(a\) Protests, as defined in section 33.101 of the Federal
> Acquisition Regulation, that are filed directly with an agency, and
> copies of any protests that are filed with the General Accounting
> Office (GAO), shall be served on the Contracting Officer (addressed as
> follows) by obtaining written and dated acknowledgment of receipt
> from:

General Services Administration\
Federal Supply Service, FCXC\
Attn: Ms. Rebecca Koses\
1941 Jefferson Davis Highway, Room 507\
Arlington, VA 22202

> \(b\) The copy of any protest shall be received in the office
> designated above within one day of filing a protest with the GAO.

## 7. PREPROPOSAL CONFERENCE: L-FSS-FCXC-\_\_\_ (MAY 1997)

A preproposal conference will be held for the purpose of explaining and
interpreting the statements of work and requirements of this
solicitation. Inquiries concerning the Solicitation shall be submitted
in writing to the issuing office at the address shown below:

GSA, FSS, Services Acquisition Center

(FCXC) Rebecca Koses or Darlena Bikowski

1941 Jefferson Davis Highway, Room 507

Arlington, VA 22202

or submit inquiries in writing utilizing INTERNET as follows:

rebecca.koses@gsa.gov

Subject: Recompete of Card Programs

darlena.bikowski@gsa.gov

Subject: Recompete of Card Programs

Answers to questions will be provided to all offerors being solicited,
giving due regard to the proper protection of proprietary information.
**OFFERORS ARE INSTRUCTED SPECIFICALLY TO CONTACT ONLY THE SOLICITATION
ISSUING OFFICE IN CONNECTION WITH ANY ASPECT OF THIS REQUIREMENT PRIOR
TO CONTRACT AWARD. OFFERORS ARE REQUIRED TO SUBMIT ALL INQUIRIES IN
WRITING, THE GOVERNMENT WILL NOT RESPOND TO VERBAL INQUIRIES.**
Questions may also be faxed to the attention of Rebecca Koses or Darlena
Bikowski at (703) 305-5094. Questions will be considered any time prior
to, or during the conference; however, offerors will be asked to confirm
oral questions in writing. **TO BE ANSWERED DURING THE PRE-PROPOSAL
CONFERENCE, QUESTIONS MUST BE SUBMITTED NO LATER THAN THREE (3) DAYS
PRIOR TO THE CONFERENCE.** Subsequent to the conference, a transcript of
the questions and answers, and a list of attendees will be posted
electronically on the Internet site specified herein.

Due to limited conference space, each offeror should limit the number of
participants to three (3) persons. In order to facilitate conference
preparations, it is requested that you notify the Federal Supply Service
(FSS) of the number of persons who will attend.

The Government assumes no responsibility for any expense incurred by an
offeror prior to contract award.

Offerors are cautioned that, notwithstanding any remark or
clarifications given at the conference, all terms and conditions of the
solicitation remained unchanged unless they are changed by amendment. If
the answers to conference questions, or any solicitation amendment,
create ambiguities, it is the responsibility of the offeror to seek
clarification prior to submitting an offer.

The conference will be held at:

Location: General Services Administration

18th & F Streets NW, Auditorium

Washington, DC 20405

Date: \_\_\_\_\_\_\_\_\_\_, 1997

Time: 9:00 a.m. Eastern time to 1:00 p.m.

## 8. PERIOD FOR ACCEPTANCE OF OFFERS: L-FSS-FCXC-\_\_\_ (MAY 1997) 

The offeror agrees to hold its offer (both technical and price) firm for
240 calendar days from the date specified for receipt of offers within
which offer may be accepted.

## 9. INFORMATION COLLECTION REQUIREMENTS: A-FSS-40 (OCT 1988)

The information collection requirements contained in this
solicitation/contract that are not required by regulation have been
approved by the Office of Management and Budget pursuant to the
Paperwork Reduction Act and assigned OMB Control No. 3090-0163.

## 10. AWARD: L-FSS-59 (APR 1984)

Until a formal notice of award is issued, no communication by the
Government, whether written or oral, shall be interpreted as a promise
that an award will be made.

## 10. BEST AND FINAL OFFERS: L-FSS-FCXC-\_\_\_ (MAY 1997)

> \(a\) Upon the conclusion of discussions the Contracting Officer will
> request a \"best and final\" offer. Oral requests will be confirmed in
> writing.
>
> \(b\) The request will include---
>
> \(1\) Notice that discussions are concluded;
>
> \(2\) Notice that this is the opportunity to submit a best and final
> offer;
>
> \(3\) The specified cutoff date and time;
>
> \(4\) A statement that any modification proposed as a result of the
> best and final offer must be received by the date and time specified
> and will be subject to the Late Submissions, Modifications, and
> Withdrawals of Proposals provision of this solicitation.
>
> \(c\) The Contracting Officer will not reopen discussions after
> receipt of best and final offers unless it is clearly in the interests
> of the Government to do so. If discussions are reopened, the
> Contracting Officer will issue an additional request for best and
> final offer.
>
> \(d\) It is the Contracting Officer\'s desire to conclude negotiations
> between date of closing and December 30, 1997.

## 11. CLARIFICATIONS OR AMENDMENTS TO THE SOLICITATION: L‑FSS‑FCXC-\_\_\_ (MAY 1997)

Information relative to the solicitation or any amendments thereto will
be posted electronically via the Internet at the following address:

**http://pub.fss.gsa.gov/fm/future/index.html**

Offeror's must then forward their acknowledgment of their receipt of any
amendments issued electronically to:

rebecca.koses@gsa.gov

or fax it to:

\(703\) 305-5094

## 12. DISPOSITION OF PROPOSALS: L-FSS-FCXC-\_\_\_ (MAY 1997)

After a Contractor has been selected, unsuccessful proposals will be
disposed of as follows: One copy of each proposal will be retained by
the issuing office and the remainder will be destroyed. No destruction
certificate will be furnished.

## 13. ANNOUNCEMENT OF AWARD(S): L-FSS-FCXC-\_\_\_ (MAY 1997)

After having notified the successful offeror and all other participating
offerors, announcement of the contract award(s) will be made in the
Commerce Business Daily and on the Internet Web site.

## 14. SUBMISSION OF PROPOSALS: L-FSS-FCXC-\_\_\_ (MAY 1997)

14.1 *Summary Instructions:*

a)  The information provided shall be concise, specific and complete,
    and shall demonstrate a thorough understanding of the requirements
    as described in the Schedule of Services of the solicitation.
    Additionally, the offeror must demonstrate a balanced, reasonable
    price relationship for each contract line item and base and option
    year(s) of the contract. Proposals that merely offer to conduct a
    program in accordance with the Government\'s requirements, as
    described in the Schedule of Services, will not be considered
    acceptable and will not receive further consideration. The offeror
    must submit a technical proposal in compliance with the
    Government\'s requirements.

b)  Technical proposals shall clearly address the requirements of the
    Schedule of Services and the noted evaluation criteria. The
    technical proposal is the primary determining factor of an offeror's
    ability to perform. Offerors are cautioned that the use of any
    format other than the one described in this section could result in
    the evaluation panel\'s inability to give maximum ratings. In order
    to assure completeness to all requirements of this RFP, the proposal
    shall have a check list matrix indicating the specific locations of
    all responses to the Government\'s various requirements.

14.2 *General Proposal Submission Instructions:*

a)  Format: The proposal submission shall be on 8-1/2 x 11-inch paper,
    in a commercially standard font size (no smaller than 10 pitch),
    double-spaced, three-hole punched, and securely placed in a
    three-ring loose leaf binder.

b)  Presentation: Unnecessarily elaborate brochures or other
    presentations beyond that sufficient to present a complete proposal
    are not desired. Elaborate art work, expensive paper and bindings,
    and expensive visual and other presentation aids are not solicited.

c)  Arrangement: Proposals shall be arranged in three physically
    separate volumes and individually titled: (1) Volume I-Contract Data
    and Business Plan; (2) Volume II-Technical Proposal; and (3) Volume
    III-Price Proposal. Each volume shall have a table of contents for
    easy reference. The separate volumes are fully described in
    paragraph 14.3, Content of Proposal Submission Instructions.

d)  Page Limitation on Technical Proposal: [For each business line
    offered]{.underline}, the technical proposals are limited to **250
    pages**, from cover to cover. **The page limitation is EXCLUSIVE
    of:**

-   Volume I-Contract Data and Business Plan;

-   Client references;

-   Client reference evaluation sheets

-   Handouts or transparencies used in the oral presentation;

-   Handouts or transparencies used in the demonstration;

-   Volume III-Price Proposal;

-   Benchmark Tasks;

-   Procedures/requirements of offeror's Bank or Credit Card Association
    or similar document described in subparagraph g), below;

-   Security procedures as described in C.13, Security Requirements;

-   Backup system and procedures as described in C.14, System Backup;
    and

-   Draft presentation package as described in C.27.2, Presentation
    Packages.

    If the offeror submits pages in excess of the limitation, the
    Government will only read and evaluate the first 250 pages of the
    offeror's technical proposal.

a)  Quantity To Submit:\
    \
    (1) [For each separate business line offered]{.underline}, offerors
    shall submit one (1) original and one (1) copy of Volume I-Contract
    Data and Business Plan, one (1) original and six (6) copies of their
    technical proposal and one (1) original and two (2) copies of the
    price proposals and contract data, to the address shown in Block 15
    of the Standard Form 1449. Originals shall be marked or stamped
    "**ORIGINAL**." Copies shall be marked or stamped "**COPY**" or
    "**DUPLICATE ORIGINAL**."\
    \
    (2) [If offering an integrated solution or more than one business
    line]{.underline}, offerors shall follow the format as specified in
    subparagraph (1), above. The offeror need not duplicate information
    if the information is identical to two or more business lines. For
    example, if the offeror's authorized negotiators are the same for
    the fleet and travel card, it need not duplicate the
    information\--only provide it once and reference where it is
    provided.

b)  Where to Submit Proposals: Proposals must be received in the Federal
    Supply Service (FSS) Bid Room, Crystal Mall No. 4, Room C-39, 1941
    Jefferson Davis Highway, Arlington, VA 22202, ATTN: RFP
    FCXC-\_\_\_\_\_\_\_\_\_\_\_, by \[insert date\]. Block 30 of the SF
    1449 must be signed by an authorized corporate official.

c)  Additional Submission Requirements: The proposal shall contain
    one (1) copy of the procedures/requirements of the offeror's Bank or
    Credit Card Association, or similar document, if applicable. The
    document does not count towards the page limitation of the proposal.

d)  Provide two copies of any oral presentation/demonstration materials,
    such as handouts or transparencies, which will be used in the
    presentation/demonstration two (2) business days prior to the oral
    presentation/demonstration, and subject to the restrictions in
    paragraph 14.3.1, General Instructions for Oral Presentations and
    Demonstrations.

e)  Submittal Checklist: The following checklist is provided for
    offeror's convenience and summarizes all proposal submissions:
    \[insert checklist\]

14.3 *Content of Proposal Submission Instructions:*

a\) Volume I-Contract Data and Business Plan: This part includes the
Solicitation/ Contract/Order for Commercial Items, including the
Standard Form (SF) 1449, continuation of the SF 1449. It shall also
include the information required in the Addendum to Clause 52.212-4,
paragraph 29, Organization Conflict of Interest (certificates);
paragraph 30, Authorized Negotiators; paragraph 31, Contract
Administration Plan; paragraph 39, Card Action Teams (CATS); paragraph
41, Key Personnel; as well as the information required in the
Solicitation Provisions 52.212-3 and 52.219-1. No other technical
information shall be included in this section.

b\) Volume II-Technical Proposal: **[No pricing information shall be
included in any portion of the technical proposal]{.underline}**. *NOTE:
If the information required does not apply to the requirements of the
particular business line offered for each portion of the technical
proposal (the narrative portion, the oral presentation portion and the
demonstration portion), the requirement to address the information is
self-deleting (e.g., information on ATM data is self deleting on the
fleet and purchase card since both cards do not require ATM products and
services as a requirement).* There are three parts to the technical
proposal for each and every business line offered (narrative, oral
proposal and demonstration). The offeror shall provide the following
information ***[for each business line offered]{.underline}.***

> 1\) **PERFORMANCE:** This part consists of narrative technical
> information only. The information provided shall be clear, concise,
> specific and complete, and shall demonstrate the offeror's historic
> ability to perform requirements in an acceptable manner; the offeror's
> corporate experience; responsiveness to clients and customer
> satisfaction; and the offeror's ability to be innovative in Card
> Program(s). The offeror must submit a technical proposal in compliance
> with the Government\'s requirements as described below. Subparagraphs
> a) through e) address past performance, corporate experience and
> responsiveness as it relates to past performance and corporate
> experience. Subparagraphs f) through i) address innovation and
> responsiveness to innovation.
>
> a\) [Corporate Card Projects:]{.underline} Provide a detailed
> narrative description of five (5) Government and/or corporate card
> projects. These projects must have been successfully completed, or
> must be current and ongoing, between January 1994 to the present.
> Three of the five projects submitted shall either be completed within
> the past 12 months or currently ongoing and shall be of a minimum of
> 1-year duration. All five projects shall be of a volume as large or
> greater than: \$100,000 charge volume for the Fleet Card; \$25,000,000
> charge volume for the Travel Card; and \$25,000,000 charge volume for
> the Purchase Card. All five projects shall be similar to the scope and
> complexity to the work that is to be completed under the resultant
> contract. At a minimum, the narrative shall:
>
> \(i\) Provide the charge volume, number of transactions and
> cardholders of each project and explain how the work is similar to the
> work required under this contract. Break out the charge volume, number
> of transaction and cardholders by each type of service in the format
> provided in Exhibit 19;
>
> \(ii\) Fully describe each project from start-up to completion.
> Include a discussion of implementation, account set-up and
> maintenance, electronic access, technology refreshment, transition,
> reporting, dispute resolution, delinquency management, type and level
> of interaction with the client, integration, etc. Discuss the tools
> and processes used to perform each project. Provide the project
> schedule for each project showing the milestones for each major step
> of the project. The narrative shall address whether major
> tasks/milestones/deliverables were on schedule and, if applicable, the
> rationale for changing the schedule. If offering an integrated
> solution, include a detailed description of the integrated project(s)
> performed and address the level of integration provided.
>
> \(iii\) Discuss challenges encountered, solutions contemplated,
> solution(s) applied, rationale for solution(s) selected and end
> result;
>
> \(iv\) Provide the name, address, telephone and facsimile numbers of a
> different client reference for each project (for a total of 5
> references) in the format provided in Exhibit 20. Submit the reference
> questionnaire in Exhibit 21 to each client reference; instruct each
> client reference to fill out the questionnaire; and have each client
> reference return the questionnaire directly to the GSA Contracting
> Officer by \[insert date\]. GSA may contact references to verify past
> performance information provided[^79]. \[NOTE: CLIENT REFERENCES AND
> QUESTIONNAIRES DO NOT COUNT TOWARDS THE PAGE LIMITATION. OFFERORS
> SHALL USE THE FORMAT SPECIFIED IN EXHIBITS 21 AND 22.\];
>
> b\) [Corporate Accounts:]{.underline} Provide the charge volume,
> number of transactions, and number of cardholders for each type of
> account (e.g., centrally billed account, individually billed account,
> ATM, travelers checks, bank checks) for the offeror's top 5 corporate
> accounts. Include typical terms and conditions for corporate accounts
> submitted.
>
> \(i\) Provide the name, address, telephone and facsimile numbers of a
> client reference for the offeror's top 5 corporate accounts (for a
> total of 5 references) in the format provided in Exhibit 20. Submit
> the reference questionnaire in Exhibit 21 to each client reference;
> instruct each client reference to fill out the questionnaire; and have
> each client reference return the questionnaire directly to the GSA
> Contracting Officer by \[insert date\]. GSA may contact references to
> verify past performance information provided. \[NOTE: CLIENT
> REFERENCES AND QUESTIONNAIRES DO NOT COUNT TOWARDS THE PAGE
> LIMITATION. OFFERORS SHALL USE THE FORMAT SPECIFIED IN EXHIBITS 21 AND
> 22.\];
>
> c\) [Merchant Acceptance:]{.underline} Identify the total number of
> accepting establishments by type of establishment and verify that the
> offeror has widespread domestic and international acceptance of the
> offeror's card product, ATM product, travelers checks product and bank
> check product proposed. The offeror shall present the data in the
> format provided in Exhibit 22. Describe the mechanism proposed to add
> new merchants and merchant types and discuss what merchant recruitment
> support will be provided and what procedures will be used.
>
> d\) [Value-Added Products and Services:]{.underline} Discuss the
> value-added products and services offered in detail and provide any
> commercial terms and conditions proposed. Include the technical
> information requested in Block 19 of the SF 1449, paragraph B.6.4,
> Value-Added Products and Services (NO PRICE INFORMATION SHALL BE
> INCLUDED IN THE TECHNICAL NARRATIVE). Demonstrate product experience
> in providing value-added products and services.
>
> \(i\) Submit the name, address, telephone and facsimile numbers of
> three (3) client references for EACH value-added product and service
> offered. Submit the reference questionnaire in Exhibit 23 to each
> client reference; instruct each client reference to fill out the
> questionnaire; and have each client reference return the questionnaire
> directly to the GSA Contracting Officer by \[insert date\]. GSA may
> contact references to verify past performance information provided.
> \[NOTE: CLIENT REFERENCES AND QUESTIONNAIRES DO NOT COUNT TOWARDS THE
> PAGE LIMITATION. OFFERORS SHALL USE THE FORMAT SPECIFIED IN EXHIBITS
> 21 AND 23.\]
>
> e\) [Best Practice Innovation:]{.underline} Provide a detailed
> narrative description of three "best practices" performed by the
> offeror and detail how the best practice may be applied to any
> resultant contract. Include a discussion of how the practice met
> client objectives, significant or extraordinary results or saved
> significant time, money and/or resources. Demonstrate innovation and
> address the level and extent of channeling of corporate resources into
> research and development efforts. Discuss challenges and risks
> encountered, possible options contemplated, direction taken and
> rationale, and end result. A "best practice" is defined as one
> considered to be superior to a usual practice because it produced
> significant or extraordinary results or saved significant amounts of
> time, money and/or resources. The best practice must be exportable to
> other organizations though may require some adaptation. Explain how
> the best practice may be exported to the Government's card program.
>
> \(i\) Provide a different point of contact, company name, address and
> telephone number for each of the three "best practices." Submit the
> reference questionnaire in Exhibit 24 to each client reference;
> instruct each client reference to fill out the questionnaire; and have
> each client reference return the questionnaire directly to the GSA
> Contracting Officer by \[insert date\]. GSA may contact references to
> verify past performance information provided. \[NOTE: CLIENT
> REFERENCES AND QUESTIONNAIRES DO NOT COUNT TOWARDS THE PAGE
> LIMITATION. OFFERORS SHALL USE THE FORMAT SPECIFIED IN EXHIBITS 21 AND
> 24.\]
>
> g\) [Promising Practice Innovation:]{.underline} Provide a detailed
> narrative description of three (3) "promising practices" performed by
> the offeror and provide an analysis of the promising practice to
> include how the practice met client objectives; achieved significant
> or extraordinary results or saved significant amounts of time, money
> and/or resources. Demonstrate innovation and address the level and
> extent of channeling of corporate resources into research and
> development efforts. Discuss challenges and risks encountered,
> possible options contemplated, direction taken and rationale, and end
> result. Discuss lessons learned. A "promising practice" is a
> conditional "best practice" (see paragraph f) above for the definition
> of a best practice). It is determined to be conditional because it was
> tried once or tried under unusual circumstances. It may not be readily
> exportable, however. Explain why the promising practice may not be
> exportable.
>
> \(i\) Provide a different point of contact, company name, address and
> telephone number for each of the three "promising practices." Submit
> the reference questionnaire in Exhibit 25 to each client reference;
> instruct each client reference to fill out the questionnaire; and have
> each client reference return the questionnaire directly to the GSA
> Contracting Officer by \[insert date\]. GSA may contact references to
> verify past performance information provided. \[NOTE: CLIENT
> REFERENCES AND QUESTIONNAIRES DO NOT COUNT TOWARDS THE PAGE
> LIMITATION. OFFERORS SHALL USE THE FORMAT SPECIFIED IN EXHIBITS 21 AND
> 25.\]
>
> 2\) **TECHNICAL EXCELLENCE**[^80]**:** This part consists of narrative
> technical information, oral presentation and demonstration. The
> information provided shall be clear, concise, specific and complete,
> and shall demonstrate the offeror's technical approach, technical
> expertise, electronic capability and transition plan. The information
> provided shall demonstrate the offeror's qualifications to perform all
> aspects of the Government's requirements; ability to clearly and fully
> demonstrate the offeror's understanding of the requirements; and the
> ability to successfully accomplish the Government's requirements. The
> offeror must submit a technical proposal in compliance with the
> Government\'s requirements as described below:
>
> a\) [Technical Approach:]{.underline} This part consists of detailed
> narrative technical information only. The offeror must demonstrate its
> comprehension of the Government's requirements and how the offeror
> will approach the accomplishment of required tasks. Describe the
> technical approach in the following areas and provide the technical
> documentation described and as requested:
>
> \(i\) Demonstrate EC/EDI capability as described in C.6, Electronic
> Commerce/ Electronic Data Interchange. Provide a trading partner
> agreement;
>
> \(ii\) Provide a copy of the offeror's security procedures as
> described in C.13, Security Requirements \[NOTE: SECURITY PROCEDURES
> DO NOT COUNT TOWARDS THE PAGE LIMITATION\--ONLY THE INFORMATION
> REQUESTED IN THIS PARAGRAPH SHALL BE PROVIDED\];
>
> \(iii\) Describe the offeror's backup system and provide a copy of the
> offeror's procedures as described in C.14, System Backup \[NOTE:
> DESCRIPTION OF BACKUP SYSTEM AND PROCEDURES DO NOT COUNT TOWARDS THE
> PAGE LIMITATION\--ONLY THE INFORMATION REQUESTED SHALL BE PROVIDED\];
>
> \(iv\) Describe any specifications (e.g., electronic specifications,
> size, quantities, frequency, other parameters) for statement inserts
> (C.19) and statement messagings (C.20). Identify the insert/messaging
> process and demonstrate the offeror's understanding of the
> requirements[^81];
>
> \(v\) Provide the offeror's generic card design[^82];
>
> \(vi\) Describe prefixes and numbering system approaches that will
> meet the requirements stated in C.24, Account Number (and if offering
> on the Travel Card Program, also address paragraph CC.6, Account
> Number for the Travel Card Program);
>
> \(vii\) Provide the offeror's draft presentation package[^83] as
> described in C.27.2, Presentation Packages \[NOTE: THE DRAFT
> PRESENTATION PACKAGE DOES NOT COUNT TOWARDS THE PAGE LIMITATION\--ONLY
> THE INFORMATION REQUESTED SHALL BE PROVIDED\];
>
> (viii)Provide the offeror's verification that their authorization
> systems will meet the requirements stated in C.28, Year 2000
> Compliance;
>
> \(ix\) Discuss what identifiers will allow posted credit transactions
> to be matched to the original charge as described in C.31, Posting of
> Transactions; and
>
> \(x\) Provide the offeror's agreement to be the Government's agent for
> document repository as described in C.42, Record Retention and
> Retrieval.
>
> \(xi\) Demonstrate the offeror's understanding of the requirements of
> the Schedule of Services in the following areas:

-   C.6, Program Volume Growth and Technological Advances;

-   C.7, Card Program(s) Requirements;

-   C.11, Reporting of Centrally Billed Accounts to Credit Bureaus;

-   C.12, Delinquency Control for Centrally Billed Accounts;

-   C.15, Investigation Assistance;

-   C.16, Audit Assistance;

-   C.17, Marketing and Advertising;

-   C.18, Master Contract Newsletter;

-   C.21, Master Contract Training Conference;

-   C.22, Release of Program Information;

-   C.32, Tax Exempt Status;

-   C.44, Card Fees;

-   C.45, Government-Wide Shut Down;

-   C.46, Liability for Centrally Billed Accounts;

    ***Specific to the Fleet Card Program:***

-   CA.3, Fleet Card Program Requirements.

    ***Specific to the Travel Card Program:***

-   CB.3, Travel Card Program Requirements;

-   CB.21, Late Fees on Individually Billed Travel Card Accounts;

-   CB.22, Reinstatement Fees on Canceled Individually Billed Travel
    Card Accounts;

    ***Specific to the Purchase Card Program:***

-   CC.3, Purchase Card Program Requirements;

> \(xii\) If offering an integrated solution, demonstrate the offeror's
> understanding of the requirements of the Schedule of Services and
> describe the offeror's technical approach to integrating two or more
> business lines. Describe the offeror's technical approach to
> determining how to improve front-end (e.g., account set-up, account
> maintenance, card issuance, cardholder services) and/or back-end
> (e.g., transaction processing, reporting, accounting, invoicing,
> reconciliation) processes.
>
> b\) [Technical Expertise:]{.underline} This part consists of an oral
> presentation of proposal information [for each business line
> offered]{.underline} to the Source Selection Evaluation Board (SSEB -
> Referenced in the Evaluation of Commercial Items, paragraph 2(e)) and
> the GSA Contracting Office. **NOTE: THE LATE PROPOSALS RULE (FAR
> 52.212-1(F), LATE OFFERS, WILL NOT BE APPLIED TO THIS PORTION OF THE
> PROPOSAL(S) (ORAL PRESENTATION ON TECHNICAL EXPERTISE).** The
> information provided shall be clear, concise, specific and complete,
> and shall demonstrate a thorough understanding of the requirements as
> stated in the Schedule of Services, and the offeror's ability to
> accomplish each of the requirements stated in paragraphs:

-   C.23, Card Design and Embossing;

-   C.25, Training Requirements;

-   C.29, Transaction Authorizations;

-   C.30, Authorization Controls;

-   C.33, Foreign Currency Conversion;

-   C.35, Centrally Billed Accounts;

-   C.36, Suspension Procedures For Centrally Billed Accounts;

-   C.37, Cancellation Procedures For Centrally Billed Accounts;

-   C.40, Customized Services;

    ***Specific to the Fleet Card Program:***

-   CA.5, Card Design and Embossing for the Fleet Card Program;

-   CA.6, Training Requirements for the Fleet Card Program;

-   CA.7, Authorization Controls for the Fleet Card Program;

-   CA.8, Tax Exempt Status;

-   CA.10, Fleet Card Program Accounts.

    ***Specific to the Travel Card Program:***

-   CB.5, Card Design and Embossing for the Travel Card Program;

-   CB.7, Training Requirements for the Travel Card Program;

-   CB.9, Authorization Controls for the Travel Card Program;

-   CB.11, Travel Card Program Centrally Billed Accounts;

-   CB.12, Travelers Checks;

-   CB.15, Travel Card Program Individually Billed Accounts;

-   CB.16, Individually Billed Travel Card Accounts and Credit Bureaus;

-   CB.17, Individually Billed Travel Card Accounts and Delinquency
    Control;

-   CB.18, Individually Billed Travel Card Account Suspension
    Procedures;

-   CB.19, Individually Billed Travel Card Account Cancellation
    Procedures;

-   CB.20, Liability for Individually Billed Accounts on the Travel Card
    Program;

-   CB.23, Per Card Annual Fees or Pre-Funded Cards for Individually
    Billed Travel Card Accounts.

    ***Specific to the Purchase Card Program:***

-   CC.5, Card Design and Embossing for the Purchase Card Program;

-   CC.6, Training Requirements for the Purchase Card Program;

-   CC.8, Authorization Controls for the Purchase Card Program;

-   CC.10, Purchase Card Program Accounts; and

-   CC.11, Bank Checks.

> Offerors are advised that overly elaborate presentations or
> presentation materials are not desired by the Government. The offeror
> must present an oral proposal in compliance with the Government\'s
> requirements, in the format and order as described below. At a
> minimum, the oral presentation shall:
>
> \(i\) Demonstrate the offeror's qualifications to perform all aspects
> of the work. The oral proposal shall:

-   Begin with the presenters' introduction of him/herself by name,
    position, and company affiliation;

-   Provide the total charge volume of all business and the number of
    years of experience. Provide the total charge volume of corporate
    business classified by type of experience with each card product and
    service programs (e.g., centrally billed accounts, individually
    billed accounts (Travel Card Program only), ATM (Travel Card Program
    only), Travelers Checks (Travel Card Program only), Bank Checks
    (Purchase Card Program only) and number of years of corporate
    experience. The presentation shall break out the data in the format
    provided in Exhibit 27;

> \(ii\) Clearly and fully demonstrate the offeror's understanding of
> the Government's requirements and describe in detail how the offeror
> will successfully accomplish the Government's requirements. Stating
> that the offeror understands and will comply with the requirements is
> not adequate. Similarly, phrases such as "standard procedures will be
> employed" or "well-known techniques will be used" are also inadequate.
> The offeror's statements will be construed as a guideline for similar
> tasks arising under the contract. Discuss how the offeror will
> successfully perform each facet of the Government's requirements from
> a technical perspective. In particular, discuss how the offering will
> accomplish the requirements stated in the above reference paragraphs
> in the Schedule of Services, as well as meeting the Government's
> objectives as stated in C.5, Program Objectives, technology
> refreshment, service improvements, and integration capabilities.
> Identify the tools to be utilized. Also discuss FROM A TECHNICAL
> PERSPECTIVE how the offeror will accomplish the Financial
> Consideration to Agencies/Organizations requirements\--specifically,
> what process, mechanism and systems will be used, how it will work,
> how the offeror will accommodate multiple remittance frequencies, and
> end of fiscal year government processing;
>
> \(iii\) If offering an integrated solution, describe in detail how the
> offeror will accomplish integration of two or more business lines.
> Identify whether the integrated solution proposed will improve
> front-end (e.g., account set-up, account maintenance, card issuance,
> cardholder services) and/or back-end (e.g., transaction processing,
> reporting, accounting, invoicing, reconciliation) processes. Describe
> what and how functions can be consolidated and what and how
> efficiencies may be gained. Describe and discuss the platform(s) to be
> used for providing integrated card services and detail advancement
> capabilities of the platform and any limitations the proposed
> platform(s) may pose;
>
> \(iii\) Describe the offeror's technical capacity to perform the
> Government's requirements. Technically respond to the following
> scenario and include a discussion on how the work will be performed,
> the offeror's ability to perform more than the evaluated quantities
> and what the offeror's maximum capacity is. ***SCENARIO: You receive
> all of the Government's task orders and must provide card services for
> the entire Federal Government. At a minimum, you will process the
> total charge volume, total transaction volume and have the total
> number of cardholders specified in Exhibit 6 (Fleet Card Program),
> Exhibit 7 (Travel Card Program) and/or Exhibit 8 (Purchase Card
> Program). END SCENARIO.***
>
> \(iv\) Identify the technical platform(s) that will be utilized and
> discuss its features, technological advancement capabilities and any
> limitations that may negatively impact the Government's programs.
> Demonstrate that the offeror can provide technological advancement and
> has a track record of technological development over the past three
> years.
>
> \(v\) Discuss how the offeror's proposed Card Program(s) will
> accomplish each of the Government's objectives as described in
> paragraph C.5, Program Objectives.
>
> c\) [Electronic Capability:]{.underline} This part consists of a
> demonstration of the offeror's proposed electronic access and
> reporting systems [for each business line offered]{.underline} to the
> Source Selection Evaluation Board (SSEB) and the GSA Contracting
> Office. **NOTE: THE LATE PROPOSALS RULE (FAR 52.212-1(F), LATE OFFERS,
> WILL NOT BE APPLIED TO THIS PORTION OF THE PROPOSAL(S) (DEMONSTRATION
> ON ELECTRONIC CAPABILITY).** The information provided shall be clear,
> concise, specific and complete, and shall demonstrate a thorough
> understanding of the requirements as stated in the Schedule of
> Services, and demonstrate the technical approach to accomplishing the
> requirements as stated in paragraphs:

-   C.34, Program and Transaction Data;

-   C.38, Agency Reporting Requirements; and

-   C.39, GSA Contracting Office Reports.

    ***Specific to the Fleet Card Program***

-   CA.9, Program and Transaction Data for the Fleet Card Program; and

-   CA.11, Fleet Card Program Reporting Requirements.

    ***Specific to the Travel Card Program***

-   CB.10, Travel Card Program and Transaction Data for Centrally Billed
    Accounts;

-   CB.13, Travel Card Program Reporting Requirements; and

-   CB.14, Travel Card Program and Transaction Data for Individually
    Billed Accounts.

    ***Specific to the Purchase Card Program***

-   CC.9, Purchase Card Program and Transaction Data; and

-   CC.12, Purchase Card Program Reporting Requirements.

> The demonstration shall illustrate the following:
>
> \(i\) At a minimum, a Level 3 platform;
>
> \(ii\) Compatibility with a variety of computer systems;
>
> \(iii\) The ability to receive and transmit data electronically;
>
> \(iv\) Account set-up;
>
> \(v\) Account maintenance;
>
> \(vi\) Transaction dispute and tracking;
>
> \(vii\) Invoicing;
>
> \(viii\) Reconciliation;
>
> \(ix\) Access to all program and transaction data at all levels,
> including a roll-up section;
>
> \(x\) Integration capabilities (applicable to the Integrated Solution
> Card Program only);
>
> \(xi\) The ability to extract and manipulate data; and
>
> \(xii\) The ability to provide data in a wide variety of media.
>
> The demonstration shall include a clear, concise handout of the
> electronic access and report screens utilized in the demonstration.
> The handout shall include system specifications, hardware/software
> requirements, format of data, and storage capability.
>
> Include a detailed discussion of the types of data elements and levels
> of data that can be captured or obtained by the offeror and provided
> to the Government at both the agency and GSA Contracting Office level
> with the proposed system. Discuss the offeror's ability to provide or
> obtain the data elements specified in C.34.6.1, Transaction Data
> Elements. Discuss how current the program and transaction data are
> (e.g., real-time, current within 24 hours, 30 days, etc.). Identify
> how many merchants have Level 2 and Level 3 capabilities by merchant
> category.
>
> d\) [Transition Plan:]{.underline} This part consists of narrative
> technical information only. The information provided shall be clear,
> concise, specific and complete, and shall demonstrate how the offeror
> will manage and perform transitions under the Government's Card
> Program(s) as described in C.41, in a smooth and seamless manner. The
> offeror must submit a technical proposal in compliance with the
> Government\'s requirements as described below:
>
> \(i\) Provide a detailed narrative description that describes the
> offeror's transition plan for each of the following types of
> transition: Contract start-up, agency/organization, master contract,
> and technological advance for each type of circumstance: (1) As an
> incumbent; and (2) as a successor. Address both the technical aspects
> and managerial aspects of each type of transition.
>
> \(ii\) For contract start-up, include a detailed discussion on the
> phase-in schedule for both mandatory and non-mandatory users, response
> and processing of standard and tailored task requests/orders, and
> implementation schedule steps (e.g., training, electronic access,
> program forms, card issuance, and card activation) and milestones in
> accordance with C.27, Start-Up Implementation Requirements; CB.8,
> Additional Start-Up Implementation Requirements for the Travel Card
> Program; and CC.7, Additional Start-Up Implementation Requirements for
> the Purchase Card Program. Discuss the relationship with the incumbent
> and successor contractors, participation in the kick-off conference
> and provide the offeror's draft presentation package. Demonstrate a
> smooth, seamless transition.
>
> \(iii\) For agency/organization transitions, include a detailed
> discussion on programmatic and operational support (including
> retention of personnel experienced with the Government's Card
> Program(s), customer service, reconciling balances, settling
> transaction disputes, phase-in, phase-out, and program start and
> completion. Demonstrate a smooth, seamless transition.
>
> \(iv\) For master contract transition, include a detailed discussion
> on programmatic and operational support (including retention of
> personnel experienced with the Government's Card Program(s), customer
> service, reconciling balances, settling transaction disputes,
> phase-in, phase-out, program start, program completion and contract
> close-out as addressed in C.43, Post Contract Requirements.
> Demonstrate a smooth, seamless transition.
>
> \(v\) For technological advance transitions, include a detailed
> discussion of the phase-in/phase-out processes, equipment or platform
> changes related to technological advances in the Card Program(s), and
> demonstrate a smooth, seamless transition.
>
> NOTE: The offeror's narrative statements will be construed as a
> guideline for similar transitions arising under the contract.
>
> 3\) **MANAGEMENT:** This part consists of narrative technical
> information only. The information provided shall be clear, concise,
> specific and complete, and shall demonstrate how the offeror will
> manage the Government's Card Program(s). The narrative shall
> demonstrate the offeror's ability to manage and staff all aspects of
> the Government's requirements to effectuate a high-quality, seamless
> Card Program(s) operation. The offeror shall explain and demonstrate
> its organization and structure, plan of accomplishment, employment
> methodologies, staffing, communication and quality assurance. The
> offeror must submit a technical proposal in compliance with the
> Government\'s requirements as described below:
>
> a\) [Plan of Accomplishment:]{.underline} This part consists of
> detailed narrative technical information only. Describe the management
> approach proposed.
>
> \(i\) Provide an Organization Plan. This plan shall describe, at a
> minimum:

-   The offeror's current corporate structure, chain of command and
    areas of corporate and personnel responsibility; and

-   How the operations structure is grouped and managed. Identify the
    organizational component which will be responsible for conduct of
    this contract and the total number of personnel overall;

> \(ii\) Provide a management plan that:

-   Correlates to the staffing chart required in subparagraph b), below
    and references all aspects of contract performance and each portion
    of the staffing chart utilized. The descriptions should provide for
    staffing both routine and special situations. The plan must be
    definitive enough to provide a clear understanding of how the
    offeror would staff and manage different and concurrent types of
    projects and size of tasks (e.g., standard task requests/orders,
    tailored task requests, tailored task orders), involving different
    combinations of functions (e.g., program marketing, program
    implementation, account set-up, account maintenance, customer
    service, customized services, invoicing, reconciliation, payment,
    integration of two or more business lines, etc.). The plan should
    include the offeror's approach to using the various technical and
    supervisory skill levels. The plan must be clear, complete and
    detailed enough to allow for application to actual work performed
    under this contract. The offeror's descriptive statements will be
    construed as a guideline for staffing and managing similar projects
    arising under the contract; and

-   Explains how the company will establish and maintain communication
    with the GSA Contracting Officer, GSA Contracting Office, A/OPCs,
    ordering Contracting Officers and other Government personnel. This
    explanation shall be comprehensive and cover both written and verbal
    communication and areas of responsibility;

> b\) [Personnel:]{.underline} This part consists of detailed narrative
> technical information only. Demonstrate the offeror's staffing
> capabilities of both key and support personnel. Provide a staffing
> chart and use it in a narrative that describes how it will enable the
> required work to be accomplished within the timeframes specified.
> Include the working relationship between the offeror's project
> manager, pertinent operational and other support staff and corporate
> officers. The number of dedicated employees anticipated to be assigned
> to each applicable organizational element should be identified, as
> well as any organizational changes anticipated to perform the contract
> in the future;
>
> For key personnel identified under paragraph 41, of the Addendum to
> Clause 52.212-4, Key Personnel, the offeror shall provide the resume
> of each individual who is anticipated to perform in these positions.
> Key personnel resumes shall be signed and dated by the applicable
> individual and countersigned by the offeror. The resume shall
> demonstrate the background, education, and scope and breadth of the
> individual's experience as it relates to the requirements listed in
> Section C.26, Personnel. Offeror's are advised that, in accordance
> with paragraph 41 of the Addendum to Clause 52.212-4, Key Personnel,
> the qualifications of the individuals demonstrated on the resumes
> shall be the standard for all personnel, in the same job category,
> under the contract;
>
> \(c\) [Employment Methodology:]{.underline} Provide a description of
> offeror's methodology for determining and obtaining personnel
> resources for staffing of the work effort. This description shall
> include, at a minimum:
>
> \(i\) Employment methodologies (e.g., use of independent consultants,
> teaming arrangements, subcontractors, part time employees, shifting of
> personnel resources, etc.), recruitment and recruitment strategy, and
> a detailed discussion of how staffing requirements are determined; and
>
> \(ii\) A narrative of how, why and when the offeror anticipates the
> use of subcontractors, to include the specific types of tasks to be
> subcontracted and the identification of subcontractors and synopsis of
> the corporate experience of each subcontractor;
>
> \(d\) [Quality Assurance Plan:]{.underline} Describe the company's
> overall quality control system, including managerial involvement and
> types and levels of review before, during and upon completion of
> projects. Describe the quality assurance tools, measures and
> procedures that will be utilized to ensure that the quality
> requirements in C.10, Quality Assurance, are met and identify the
> individual(s) responsible for quality assurance and their
> responsibilities;

c\) Volume III-Price Proposal: This part consists of the Contract Line
Item Numbers, Section B, by CLIN. The offeror shall provide pricing for
the base year and each option year. The offeror may reproduce the
Contract Line Item Number forms as necessary. If additional space is
required to price, the offeror may use plain bond paper and clearly
identify each CLIN offered, in the format provided. Include what, if
any, assumptions are made as well as the basis for those assumptions,
and provide examples of each pricing proposed. Include all elements
described in B.5, Financial Consideration to Agencies/Organizations,
B.6, Pricing Instructions and B.7, Benchmark Tasks.

Offered prices shall be inclusive of all costs. This shall include all
direct labor costs (inclusive of G&A, overhead, profit, fringe benefits,
escalation) and other direct costs (products, supplies and materials)
associated with the requirement and be in a manner consistent with the
offeror's cost or general accounting standards. All costs required to
meet the Government's requirements in the Schedule of Services are to be
included in this commercial price.

Offerors shall address the Industrial Funding Fee and Financial
Consideration to Agencies/Organ-izations in their price proposal. If
offerors adopt a volume-based approach to pricing, the pricing proposed
must not adversely affect agencies/organizations that place their orders
first. As individual agencies/organizations will place separate orders
with contractors, it would not be effective to create an incentive to
wait for other agencies/organizations to place orders to obtain a volume
based discount.

If quantity discounts are offered on the value-added products and
services, please indicate what the quantity discounts are. Where
additional space is necessary, use plain bond paper and clearly mark the
contract line item number for which the pricing is being offered.

**ALTERNATIVE PRICING PROPOSALS ARE ENCOURAGED.**

14.3.1 *[General Instructions for Oral Presentations and
Demonstrations]{.underline}*:

> a\) **[Where:]{.underline}** Oral presentations and demonstrations
> will be conducted at the General Services Administration, Federal
> Supply Service, Crystal Mall No. 4, 1941 Jefferson Davis Highway,
> Arlington, VA 22202. The facility will be available for inspection by
> the offerors prior to the time set for the actual presentation and
> demonstration.
>
> b\) **[Schedule:]{.underline}** Oral presentations and demonstrations
> will be scheduled with offerors as soon as possible after the closing
> date for receipt of proposals. The late proposals rule (FAR
> 52.212-1(F), Late Offers) will not be applied to the oral
> presentation(s) and demonstration(s) portion of the proposal(s). The
> scheduling of the oral presentations and demonstrations will be
> dependent upon the number of offers received. The order in which
> offerors will make their presentation/demonstration to the SSEB and
> the GSA Contracting Office will be determined by lottery at a time
> determined by the GSA Contracting Officer after receipt of proposals.
> **OFFERORS WILL NOT BE PERMITTED TO ATTEND THE LOTTERY DRAWING.** Once
> notified of their scheduled presentation/demonstration date and time,
> offerors shall complete their presentation/demonstration on the
> scheduled date and time. Requests from offerors to reschedule their
> presentation/demonstration will not be entertained and no rescheduling
> of the presentation/demonstration will be done unless determined
> necessary by the Government to resolve unanticipated problems or
> delays encountered. The GSA reserves the right to reschedule the oral
> presentation/demon-stration, with reasonable notice, at the sole
> discretion of the GSA Contracting Officer.
>
> c\) **[Form of Presentations:]{.underline}** Offerors shall make their
> oral presentation/demonstration in person to the SSEB and the GSA
> Contracting Office personnel. Submission of video tapes or other forms
> of media containing the presentation/demonstration for evaluation is
> not authorized and such technical proposals shall be rejected.
>
> d\) **[Equipment:]{.underline}** The Government will provide a screen
> and a manual overhead projector and/or a desktop projector (Proxima
> Desktop Projector 5500). Offerors are to indicate their equipment
> preference at the time of scheduling. Extension cords will also be
> provided. All other equipment shall be provided by the offeror.
>
> e\) **[Time Allowed for Oral
> Presentations/Demonstrations:]{.underline}** **For each business line
> offered**, each offeror will have a maximum of four (4) hours
> (excluding Q&As) in which to make its presentation/demonstration to
> the SSEB and authorized procurement personnel, broken out as follows:
> Two (2) hours for the oral presentation followed by questions and
> answers and two (2) hours for the demonstration followed by questions
> and answers. Each segment will run 60 minutes, followed by a short
> break, and reconvene for the final 60 minutes. The sessions will run
> successively with the oral presentation first and the demonstration
> last. There will be a break in-between sessions. Each session's and
> segment's time limit will begin with the GSA Contracting Officer's
> direction to begin.
>
> f\) **[Clarification of Oral Presentation/Demonstration
> Points:]{.underline}** After completion of the oral
> presentation/demonstration or each session's two-hour time limit,
> whichever occurs first, the Government may request clarification of
> any of the points addressed in the oral presentation or demonstration
> which are unclear and may ask for elaboration by the offeror on any
> point which was not adequately supported. Any such interaction between
> the offeror and the Government will be for clarification only, and
> will not constitute discussions within the meaning of FAR 15.610.
> **[The time required for clarifications will not be counted against
> the offeror's time limit]{.underline}**. Only persons making the
> presentation are allowed to respond to the question.
>
> The Government will not inform an offeror of their strengths,
> deficiencies, or weaknesses during the presentation/demonstration, and
> the Government will not engage in discussions during the
> presentation/demonstration.
>
> g\) **[Offeror's Presentation/Demonstration Team:]{.underline}** The
> offeror's presentation/demon-stration team shall be limited to no more
> than 5 people. Only Key Personnel members of the offeror's in-house
> staff shall participate in the presentation/demonstration. The only
> exception is that any individuals who are proposed as Key Personnel to
> perform on the contract, but who are not currently employed by the
> offeror, may participate in the presentation/demonstration. Within
> those constraints, offerors shall have the option of selecting the key
> personnel participants to make their firm's oral
> presentation/demonstration to the SSEB and the GSA Contracting Office.
>
> h\) **[Documentation:]{.underline}** At the close of the oral
> presentation/demonstration or each session's two-hour time limit,
> whichever occurs first, the offeror shall provide the SSEB and the GSA
> Contracting Office with a listing of the names, firms, and position
> titles of all presenters. Two copies of any presentation/demonstration
> materials, such as handouts or transparencies, **[which will be used
> in the presentation/ demonstration]{.underline}** will be submitted
> two (2) business days prior to the oral presentation/demonstration.
> The Late Proposals rule (FAR 52.212-1(F), Late Offers, will not be
> applied to the two copies of any presentation/demonstration materials.
> Oral presentation/demonstration materials shall be legible. No
> additions or changes to this written documentation will be accepted at
> the time of the oral presentation/ demonstration. **The Government
> will not accept for evaluation any additional documentation (such as
> procedures, manuals, administrative handbooks or guides, etc.) which
> may or may not have been referenced during the
> presentation/demonstration**. At its election, GSA will either
> videotape or record each offeror's oral presentation/demonstration and
> any subsequent questions and answers. Such videotapes or transcripts
> will be used by the SSEB and GSA Contracting Office, if necessary,
> during scoring of the technical proposal. A copy of the videotape or
> transcript will be provided to the offeror for its records upon
> written request. After contract award, such videotapes or transcripts
> may also be used by GSA to assist agencies in their task order
> selection process. GSA may set up an award library for official
> government personnel to view such videotapes or read such transcripts.
>
> i\) **[Price:]{.underline}** No price information shall be included in
> the offeror's oral presentation or documentation. No price information
> shall be included in the offeror's demonstration or documentation.
>
> j\) **[Restrictions:]{.underline}** For the oral presentation, the
> offeror shall use no more than 25 overheads/slides. There is no limit
> to the number of overheads/slides for the demonstration.
>
> k\) The oral presentation/demonstration shall not constitute
> discussions as defined in FAR 15.601 and 15.610.
>
> l\) Presenters should not include overly detailed, technical
> information on materials. Do not duplicate the technical proposal(s)
> on handouts/slides.

## 15. BENCHMARK TASK INSTRUCTIONS: L-FSS-FCXC-\_\_\_ (MAY 1997)

Add when identified.

# EVALUATION OF COMMERCIAL ITEMS

## 1. 52.212-2 Evaluation\--Commercial Items 

\(a\) ~~The Government will award a contract resulting from this
solicitation to the responsible offeror whose offer conforming to the
solicitation will be most advantageous to the Government, price and
other factors considered~~. See paragraph 2, Method of Award.

The following factors shall be used to evaluate offers:

**FACTORS ARE DESCRIBED IN PARAGRAPH 3, EVALUATION CRITERIA**

Technical and past performance, when combined, are more important than
price.

\(b\) Options. The Government will evaluate offers for award purposes by
adding the total price for

all options to the total price for the basic requirement. The Government
may determine that an offer is unacceptable if the option prices are
significantly unbalanced. Evaluation of options shall not obligate the
Government to exercise the option(s).

\(c\) A written notice of award or acceptance of an offer, mailed or
otherwise furnished to the

successful offeror within the time for acceptance specified in the
offer, shall result in a binding

contract without further action by either party. Before the offer\'s
specified expiration time, the

Government may accept an offer (or part of an offer), whether or not
there are negotiations after its receipt, unless a written notice of
withdrawal is received before award.

## 2. METHOD OF AWARD: M-FSS-FCXC-\_\_\_ (MAY 1997)

\(a\) Contract award will be made to responsible, technically acceptable
offeror(s) whose offer(s) conform to the solicitation and represent the
best value to the Government, price and other factors listed below
considered. The factors to be used in the evaluation are technical and
cost or price. For purposes of this solicitation, technical quality is
considered more important than price. As the proposal(s) become more
equal in their technical merit, the evaluated price becomes more
important.

\(b\) Proposals unrealistic in terms of technical content or price will
be deemed reflective of an inherent lack of technical competence or
indicative of a failure to comprehend the complexity and risk of the
contract requirements. Determination of best value will be made in terms
of the results of the evaluation against the source selection evaluation
criteria.

\(c\) The Government plans to make multiple awards in the aggregate for
each group of contract line item numbers (CLINs) as follows:

+---------------------+---------------+---------------+---------------+
| **Description**     |               | **CLINs**     |               |
+---------------------+---------------+---------------+---------------+
| Group 1 - Fleet     | BA.0001       | BA.0002       | BA.0003       |
| Card                |               |               |               |
|                     | BA.1001       | BA.1002       | BA.1003       |
|                     |               |               |               |
|                     | BA.2001       | BA.2002       | BA.2003       |
|                     |               |               |               |
|                     | BA.3001       | BA.3002       | BA.3003       |
|                     |               |               |               |
|                     | BA.4001       | BA.4002       | BA.4003       |
|                     |               |               |               |
|                     | BA.5001       | BA.5002       | BA.5003       |
+---------------------+---------------+---------------+---------------+
| Group 2 - Travel    | BB.0001       | BB.0002       | BB.0003       |
| Card                |               |               |               |
|                     | BB.1001       | BB.1002       | BB.1003       |
|                     |               |               |               |
|                     | BB.2001       | BB.2002       | BB.2003       |
|                     |               |               |               |
|                     | BB.3001       | BB.3002       | BB.3003       |
|                     |               |               |               |
|                     | BB.4001       | BB.4002       | BB.4003       |
|                     |               |               |               |
|                     | BB.5001       | BB.5002       | BB.5003       |
+---------------------+---------------+---------------+---------------+
| Group 3 - Purchase  | BC.0001       | BC.0002       | BC.0003       |
| Card                |               |               |               |
|                     | BC.1001       | BC.1002       | BC.1003       |
|                     |               |               |               |
|                     | BC.2001       | BC.2002       | BC.2003       |
|                     |               |               |               |
|                     | BC.3001       | BC.3002       | BC.3003       |
|                     |               |               |               |
|                     | BC.4001       | BC.4002       | BC.4003       |
|                     |               |               |               |
|                     | BC.5001       | BC.5002       | BC.5003       |
+---------------------+---------------+---------------+---------------+

In order to provide agencies/organizations the greatest range of master
contractor choices, the Government plans to make multiple awards that
offer a wide variety of products and services to agencies/organizations.
For example, the Government may award contracts containing minimum core
requirements; "premium" contracts containing several value-added product
and service choices; contracts that provide for an integrated solution;
and a variation of all the products and service choices so that
agencies/organizations have a maximum array of the level and types of
products and services offered.

\(d\) Each of the evaluation factors have been divided into subfactors.
The specific evaluation factors and the evaluation subfactors and their
relative importance are addressed below. All elements will be measured
against standards which have been developed to represent specific
requirements of the RFP. The evaluation will include the determination
of advantages, disadvantages and risks for each factor and subfactor.

\(e\) Offerors' technical proposals, containing the material specified
in the Instructions to the Offerors Section, paragraph 14, Submission of
Proposals, of this solicitation, will be reviewed, evaluated and rated
by members of a Source Selection Evaluation Board (SSEB) set up for this
purpose. Proposals which are unable to be brought to a minimally
acceptable level through negotiations will be rejected. Attempts will be
made to negotiate marginal technical proposals to an acceptable level,
but if unsuccessful, these proposals will be rejected. Offerors are on
notice that proposals which are unrealistic in terms of technical
content or lack of technical competence, or indicative of failure to
comprehend the complexities and risks of the solicitation requirements,
will be rejected. Acceptable technical proposals will be evaluated for
price.

\(f\) The Government intends to evaluate proposals and award a
contract(s) after conducting written or oral discussions with all
responsible offerors whose proposals have been determined to be within
the competitive range. However, each initial offer should contain the
offeror's best terms from a cost or price and technical standpoint. The
Government reserves the right to award on the basis of the initial
proposal without any discussions.

## 3. EVALUATION CRITERIA: M-FSS-FCXC-\_\_\_ (MAY 1997)

The following chart represents the relative importance of the evaluation
factors which will be used to evaluate each technical proposal:

+----------------+-------------------+---------------------------------+
| **Evaluation   | **Description**   | **Relative**                    |
| Factor/**      |                   |                                 |
|                |                   | **Importance**                  |
| **Subfactor**  |                   |                                 |
+----------------+-------------------+---------------------------------+
| *Evaluation    | *Performance*     | *Equally Important as Factor 2* |
| Factor 1*      |                   |                                 |
+----------------+-------------------+---------------------------------+
| Subfactor 1A   | Past Performance  | Equally important as 1B         |
+----------------+-------------------+---------------------------------+
| Subfactor 1B   | Corporate         | Equally important as 1C         |
|                | Experience        |                                 |
+----------------+-------------------+---------------------------------+
| Subfactor 1C   | Responsiveness    | Significantly more important    |
|                |                   | than 1D                         |
+----------------+-------------------+---------------------------------+
| Subfactor 1D   | Innovation        |                                 |
+----------------+-------------------+---------------------------------+
| *Evaluation    | *Technical        | *Significantly More Important   |
| Factor 2*      | Excellence*       | than Factor 3*                  |
+----------------+-------------------+---------------------------------+
| Subfactor 2A   | Technical         | Equally important as 2B         |
|                | Approach          |                                 |
+----------------+-------------------+---------------------------------+
| Subfactor 2B   | Technical         | Equally important as 2C         |
|                | Expertise         |                                 |
+----------------+-------------------+---------------------------------+
| Subfactor 2C   | Electronic        | Equally important as 2D         |
|                | Capability        |                                 |
+----------------+-------------------+---------------------------------+
| Subfactor 2D   | Transition Plan   |                                 |
+----------------+-------------------+---------------------------------+
| *Evaluation    | *Management*      |                                 |
| Factor 3*      |                   |                                 |
+----------------+-------------------+---------------------------------+
| Subfactor 3A   | Plan of           | Equally as important as 3B      |
|                | Accomplishment    |                                 |
+----------------+-------------------+---------------------------------+
| Subfactor 3B   | Personnel         | Significantly more important    |
|                |                   | than 3C                         |
+----------------+-------------------+---------------------------------+
| Subfactor 3C   | Quality Assurance |                                 |
|                | Plan              |                                 |
+----------------+-------------------+---------------------------------+

## 4. EVALUATION OF TECHNICAL CRITERIA: M‑FSS‑FCXC‑\_\_\_ (MAY 1997)

The technical factors for the Fleet, Travel, and Purchase Card Programs
are listed below and are in the order of importance specified. The
technical proposals will be evaluated based on the material specified in
the Instructions to Offerors Section of this solicitation and the
offeror's demonstrated understanding of the requirements of the Schedule
of Services as set forth in the proposal(s).

\(a\) Factor 1, Performance: The Government will evaluate: (1) The
offeror's historic ability to perform requirements in an acceptable
manner; (2) the offeror's corporate experience; (3) responsiveness to
clients and customer satisfaction; and (4) the offeror's ability to be
innovative in card programs. In evaluating Factor 1, the Government will
consider work performed that is similar to the size (or larger/greater),
scope and complexity (e.g., \$100,000 charge volume for the Fleet Card;
\$25,000,000 charge volume for the Travel Card; and \$25,000,000 for the
Purchase Card). The Government's evaluation will include the
effectiveness of the card projects and programs; verification of global
acceptance of the offeror's card products and services; the offeror's
past performance as it relates to quality, accuracy, timeliness,
responsiveness, customer satisfaction, communication and providing
integrated solutions; the commercial tools/processes utilized; the
offeror's corporate experience in providing a wide variety of
value-added products and services; and innovation in card-based
programs. The Government prefers offerors with a minimum of three (3)
years of corporate experience similar to the requirements anticipated
under any resultant contract and a prefers offerors that have a
demonstrated track record in providing a wide variety of value-added
products and services. The Government also prefers offerors that can
provide a proven integrated solution. The Government's evaluation will
be based on information contained in the proposal and reference
comments. Factor 1 contains four subfactors: Past Performance, Corporate
Experience, Responsiveness and Innovation. Factor 1, Performance is
**[equally]{.underline}** as important as Factor 2, Technical
Excellence.

\(1\) Subfactor 1A, Past Performance, will be evaluated based upon the
offeror's ability to successfully perform card projects. In evaluating
Past Performance, the Government will consider the size, scope and
complexity of past projects; the offeror's ability to deliver a quality
product/service that meets client objectives within project schedules;
commercial tools and processes utilized; delinquency management and
problem-solving and analytical skills. The Government prefers those
offerors that can demonstrate accomplishments similar to the
Government's requirements (e.g., different account types) in a timely
and accurate manner using commercial products and services. The
Government also prefers those offerors with demonstrated integrated
solutions. Subfactor 1A, Past Performance, is **[equally]{.underline}**
as important as Subfactor 1B, Corporate Experience.

\(2\) Subfactor 1B, Corporate Experience, will be evaluated based upon
the offeror's corporate experience in providing card programs. In
evaluating Corporate Experience, the Government will consider the size,
scope and complexity of the offeror's top five (5) corporate accounts;
under what typical terms and conditions the corporate accounts were
provided; the extent of merchant acceptance of the offeror's card
product; the ability to add new merchants and merchant types as well as
the level of merchant recruitment support provided; the offeror's
corporate experience in providing value-added products and services; and
client references. The Government prefers those offerors that have at
least three (3) years of corporate experience and who are able to offer
a wide variety of value-added products and services. Subfactor 1B,
Corporate Experience, is **[equally]{.underline}** as important as
Subfactor 1C, Responsiveness.

\(3\) Subfactor 1C, Responsiveness, will be evaluated based upon the
offeror's track record in responsiveness and commitment to customer
satisfaction. In evaluating Responsiveness, the Government will consider
the offeror's responsiveness to changes in technical direction; ability
to meet client objectives; ability to be cooperative, business-like and
concerned with client interests; ability to control costs, overall
technical and management performance including staffing levels; customer
service, dispute resolution, communication, and customer satisfaction
with the program. Subfactor 1C, Responsiveness is
**[significantly]{.underline}** more important than Subfactor 1D,
Innovation.

\(4\) Subfactor 1D, Innovation, will be evaluated based upon the
offeror's ability to be innovative and creative. In evaluating
Innovation, the Government will consider the success of the best and
promising practices to accomplishing stated client objectives;
significant or extraordinary results or saved significant time, money
and/or resources; corporate investment in research and development and a
demonstrated record of technology development; exportability of the best
practice in Government programs; and technology refreshment. The
Government will also consider the offeror's performance in overcoming
challenges and abating risks. The Government prefers those offerors that
invest in research and development and demonstrate on-going technology
development. The Government will also consider the offeror's track
record in technological development and providing
advancement/refreshment consistent with the those offered the commercial
marketplace.

\(b\) Factor 2, Technical Excellence, is based upon the offeror's (1)
qualifications to perform all aspects of the Government's requirements;
(2) ability to clearly and fully demonstrate the offeror's understanding
of the requirements; and (3) ability to successfully accomplish the
Government's requirements. The Government will evaluate how
well-qualified the offeror is to perform all aspects of the work, how
well the offeror understands the requirements and precisely how the
offeror will approach and accomplish the required tasks. The Government
will consider the commerciality (off-the-shelf) of offered products and
services; superiority of technical approach with particular emphasis on
the offeror's ability to provide a commercial card program that meets
the Government's requirements; and the offeror's technical capacity. The
Government's evaluation will be based on information contained in the
proposal and reference comments. It contains four subfactors of
**[equal]{.underline}** importance: Technical Approach, Technical
Expertise, Electronic Capability, and Transition Plan. Factor 2,
Technical Excellence, is **[significantly]{.underline}** more important
than Factor 3, Management.

\(1\) Subfactor 2A, Technical Approach, will be evaluated based upon the
offeror's ability to clearly and fully demonstrate its comprehension of
the Government's requirements and how the offeror will approach the
accomplishment of required tasks. In evaluating Technical Approach, the
Government will consider the offeror's ability to perform EC/EDI; the
level and extent of security procedures to protect the Government's card
programs; the ability of the back-up system proposed to be seamless and
not interrupt the Government's card programs; the number of the prefixes
and numbering system approaches proposed that assist in recognition of
Government accounts; the offeror's verification that their authorization
systems meet the requirements described n C.28, Year 2000 Compliance;
how credit transactions can be matched to the original charges to enable
easy cardholder identification; the offeror's agreement to be an agent
for the Government for document repository; the offeror's overall
understanding of the Government's requirements; and the offeror's
ability to demonstrate a sound approach to integrated solutions.
Subfactor 2A, Technical Approach, is **[equally]{.underline}** as
important as subfactor 2B, Technical Expertise.

\(2\) Subfactor 2B, Technical Expertise, will be evaluated based upon
the offeror's ability to clearly and fully demonstrate its comprehension
of the Government's requirements and how it will accomplish the required
tasks. In evaluating Technical Expertise, the Government will consider
the offeror's depth and breadth of understanding of the requirements.
The Government will consider the offeror's technical plan for
accomplishing the requirements with particular attention to how the
offeror will meet the Government's objectives as stated in paragraph
C.5, Program Objectives; how the offeror will implement and perform the
card programs; the level and extent of programmatic and operational
support (e.g., card design and embossing, training, transaction
authorizations, authorization controls, foreign currency conversion
\[NOTE: Offers which propose foreign exchange systems which are
prejudicial against the Government, or fail to provide a method for
determining the accuracy of the exchange rate applied or which are not
based upon current world market rates are unacceptable\], centrally
billed accounts, individually billed accounts (travel card only),
suspension and cancellation processes, and customized services) in a
timely and accurate manner. In particular, the evaluation of Subfactor
2B will emphasize:

-   The ability to identify, report and strip taxes (fleet card only);

-   The ability for billing and invoicing to be flexible in frequency;

-   The ability to accurately track and post payments in accordance with
    client instructions;

-   The nature and extent of reconciliation assistance (and
    particularly, the offeror's ability to work with DBOs or designees
    to effectuate timely and accurate reconciliation);

-   The ability to resolve disputes speedily and accurately;

-   The level and types of controls for delinquency management;

-   The level and extent of risk mitigation measures (travel card
    only\--e.g., per card annual fees or pre-funded cards for
    individually billed accounts);

-   The ability to provide travelers checks and ATM (travel card only)
    products and services;

-   The ability to provide bank check (purchase card only) products and
    services;

-   The ability to provide training to cardholders, A/OPCs, DBOs, TDOs
    and EOs;

-   The ability to integrate two or more business lines (integrated
    solution only) \[NOTE: The Government prefers both front-end and
    back-end processes to be integrated as well as integration of all
    three business lines\];

-   Use of off-the-shelf commercial tools and processes and their
    adaptability/flexibility;

-   The offeror's maximum capacity; and

-   The technical aspects of accomplishing the Financial Consideration
    to Agencies/Organizations requirement \[NOTE: No financial
    information shall be provided here\].

The Government will also consider the advancement capabilities and
flexibility of the offeror's proposed platform(s) and to what extent, if
any, limitations of the proposed platform(s) would negatively affect the
Government's programs. Subfactor 2B, Technical Expertise, is
**[equally]{.underline}** as important as subfactor 2C, Electronic
Capability.

\(3\) Subfactor 2C, Electronic Capability, will be evaluated based upon
the offeror's ability to demonstrate its electronic access and reporting
systems can provide full, complete access and data for both agency and
GSA Contracting Office reports that enable the Government to manage its
card programs and streamline backroom processes. The Government will
evaluate the Level 3 platform proposed to provide the program and
transaction data and the Contractor's ability to obtain the data
specified. The Government prefers offerors that can provide all the
program and transaction data requirements for each transaction and
prefers flexible platforms that allow technological upgrades without
program disruption. The Government will also consider the extent to
which the offeror's proposed systems are compatible with a variety of
standard commercial computer systems. The Government prefers the use of
commercial systems over proprietary systems. The Government will also
consider how user-friendly the overall systems are from a typical users
standpoint; the level and speed in which data can be received and
transmitted electronically; the relative ease of master file, account
set up and maintenance functions; the ability to dispute and track
transactions; the flexibility to receive invoices and the level and type
of account reconciliation that can be done electronically (e.g.,
changing/adding accounting codes, etc.); the level and extent of the
access to data elements; the level and extent of the ability to extract
and manipulate data for ad hoc reporting; how current and detailed the
data is (the Government prefers current data defined as previous day's
data and prefers detailed data (i.e., Level 3 data)) and to what extent
the offeror can provide and obtain all the data elements specified in
C.34.6.1, Transaction Data Elements; and the offeror's ability to
provide data in a wide variety of media. The Government will also
consider the level and extent of integration capabilities. Subfactor 2C,
Electronic Capability, is **[equally]{.underline}** as important as
subfactor 2D, Transition Plan.

\(4\) Subfactor 2D, Transition Plan, will be evaluated based upon the
offeror's ability to effectuate and manage a seamless transition in four
areas (contract start-up, agency/organization transition, master
contract transition, and technological advance transition) as an
incumbent and as a successor. The Government will consider the extent to
which the offeror's transition plan minimizes the impact to the
Government in the phase-in and phase-out process of each type of
transition. The Government will also consider the ability of the
proposed milestone schedules to ensure continuous contract coverage for
all participants; the timing and level of clear communication to all
participants; level and extent of programmatic and operational support;
the extent of customer service levels; the retention of experienced
personnel to effectuate a seamless transition; the level and quality of
assistance provided to reconcile balances and settle disputes; and speed
and accuracy of closing out the Government's program.

\(c\) Factor 3, Management, is based upon the offeror's ability to
manage and staff all aspects of the Government's requirements to
effectuate a high-quality, seamless Card Program operation. The
Government will evaluate the offeror's organization and structure,
management plan of accomplishment, employment methodologies, staffing,
communication and quality assurance. The Government's evaluation will be
based on information contained in the proposal and reference comments.
Subfactor 3A, Plan of Accomplishment, is **[equally]{.underline}** as
important as Subfactor 3B, Personnel.

\(1\) Subfactor 3A, Plan of Accomplishment, will be evaluated based upon
the offeror's ability to manage and oversee the Government's
requirements. The Government will consider how the operations structure
is grouped and managed; the level and extent of the offeror's management
plan of accomplishment in satisfying the Government's requirements with
particular attention to how the offeror would manage the task ordering
process within the required timeframes; and how the offeror will
establish and maintain communication, at what level and extent, with a
variety of Government personnel; and to what level and extent management
will participate in the card program. Subfactor 3A, Plan of
Accomplishment, is **[equally]{.underline}** as important as Subfactor
3B, Personnel.

\(2\) Subfactor 3B, Personnel, will be evaluated based upon the
offeror's demonstration that they have adequate staffing capabilities of
both key and support personnel. Staffing charts will be used to
understand the relationships between personnel and across various
offices responsible for different portions of the Government's card
programs, and how they interrelate and come together to perform the
requirements. The Government will consider the offeror's ability to
staff and perform different and concurrent types of projects and sizes
of tasks involving different functions or combination of functions
(e.g., marketing, implementation, integration, customer support, A/OPC
support, GSA Contracting Office support, training, billing, reporting,
etc.); the offeror's methodology for determining and obtaining personnel
resources; and the level and quality of key personnel proposed.
Subfactor 3B, Personnel, is **[significantly]{.underline}** more
important than Subfactor 3C, Quality Assurance Plan.

\(3\) Subfactor 3C, Quality Assurance Plan, will be evaluated based upon
the offeror's ability to meet the quality requirements of the Schedule
of Services by evaluating the offeror's quality control system,
including managerial involvement. The Government will consider how
contract requirements will be monitored, at what level, and by whom. The
Government will also evaluate how the offeror will ensure A/OPC task
order evaluations are submitted in a timely fashion; the quality
assurance tools, measures and procedures proposed; and corrective
measures to correct and prevent services or items of inferior quality.

## 5. EVALUATION OF PRICE FOR EACH BUSINESS LINE: M‑FSS‑FCXC‑\_\_\_ (MAY 1997)

The financial proposals will be evaluated separately for each business
line. Any financial offer based upon a factor other than basis points
per dollar transacted must be demonstrably to the Government's advantage
to be considered. All offers shall include each component of the Tier 1
requirements of a business line (e.g., offers on the travel card must
include individually billed accounts, centrally billed accounts, ATM,
and travelers checks).

***Solely for the purposes of evaluation***, the Government will
evaluate the prices offered utilizing the evaluation method stated
below. The numbers utilized in the Government's method of evaluation are
hypothetical numbers only and **[do not represent]{.underline}** actual
or historical figures, Government estimates, likely prices, or likely
amount of orders. They are used solely for the purpose of illustrating
the price evaluation method. The evaluation method of price is as
follows:

TIER 1 PRICING

+-----------------------------------+-----------------------------------+
| Contract Line Item Numbers        | Evaluation Method                 |
| (CLINs)                           |                                   |
+-----------------------------------+-----------------------------------+
| -   BA.0001, BA.1001, BA.2001,    | Evaluated Quantity of Charge      |
|     BA.3001, BA.4001 and BA.5001  | volume                            |
|                                   |                                   |
| -   BB.0001, BB.1001, BB.2001,    | x                                 |
|     BB.3001, BB.4001 and BB.5001  |                                   |
|                                   | Basis Points Offered              |
| -   BC.0001, BC.1001, BC.2001,    |                                   |
|     BC.3001, BC.4001 and BC.5001  |                                   |
+-----------------------------------+-----------------------------------+

TIER 1 PRICING (continued)

+-----------------------------------+-----------------------------------+
| Contract Line Item Numbers        | Evaluation Method                 |
| (CLINs)                           |                                   |
+-----------------------------------+-----------------------------------+
| -   BA.0001 (a), BA.1001 (a),     | (if offered)                      |
|     BA.2001 (a), BA.3001 (a),     |                                   |
|     BA.4001 (a) and BA.5001 (a)   | Evaluated Quantity of Charge      |
|                                   | volume                            |
| -   BB.0001 (a), BB.1001 (a),     |                                   |
|     BB.2001 (a), BB.3001 (a),     | x                                 |
|     BB.4001 (a) and BB.5001 (a)   |                                   |
|                                   | Basis Points Offered              |
| -   BC.0001 (a), BC.0001 (a),     |                                   |
|     BC.2001 (a), BC.3001 (a),     |                                   |
|     BC.4001 (a) and BC.5001 (a)   |                                   |
+-----------------------------------+-----------------------------------+
| -   BB.0001 (b), BB.1001 (b),     | Evaluated Quantity of Checks      |
|     BB.2001 (b), BB.3001 (b),     |                                   |
|     BB.4001 (b) and BB.5001 (b)   | x                                 |
|                                   |                                   |
| -   BC.0001 (b), BC.1001 (b),     | Price Offered                     |
|     BC.2001 (b), BC.3001 (b),     |                                   |
|     BC.4001 (b) and BC.5001 (b)   |                                   |
+-----------------------------------+-----------------------------------+
| -   BB.0001 (c), BB.1001 (c),     | Evaluated Quantity of ATM         |
|     BB.2001 (c), BB.3001 (c),     |                                   |
|     BB.4001 (c) and BB.5001 (c)   | x                                 |
|                                   |                                   |
|                                   | Price Offered                     |
+-----------------------------------+-----------------------------------+
| -   BA.0001 (b), BA.1001 (b),     | Evaluated Quantity of Hours       |
|     BA.2001 (b), BA.3001 (b),     |                                   |
|     BA.4001 (b) and BA.5001 (b)   | x                                 |
|                                   |                                   |
| -   BB.0001 (d), BB.1001 (d),     | Hourly Rate                       |
|     BB.2001 (d), BB.3001 (d),     |                                   |
|     BB.4001 (d) and BB.5001 (d)   |                                   |
|                                   |                                   |
| -   BC.0001 (c), BC.1001 (c),     |                                   |
|     BC.2001 (c), BC.3001 (c),     |                                   |
|     BC.4001 (c) and BC.5001 (c)   |                                   |
+-----------------------------------+-----------------------------------+

Each option year price will be added to the base year price to determine
the total contract price for Tier 1 pricing.

TIER 2 PRICING

+-----------------------------------+-----------------------------------+
| Contract Line Item Numbers        | Evaluation Method                 |
| (CLINs)                           |                                   |
+-----------------------------------+-----------------------------------+
| -   BA.0002 (a) through (o),      | (if offered)                      |
|     BA.1002 (a) through (o),      |                                   |
|     BA.2002 (a) through (o),      | Unit of Issue                     |
|     BA.3002 (a) through (o),      |                                   |
|     BA.4002 (a) through (o) and   | x                                 |
|     BA.5002 (a) through (o)       |                                   |
|                                   | Price Offered                     |
| -   BB.0002 (a) through (q),      |                                   |
|     BB.1002 (a) through (q),      |                                   |
|     BB.2002 (a) through (q),      |                                   |
|     BB.3002 (a) through (q),      |                                   |
|     BB.3002 (a) through (q),      |                                   |
|     BB.4002 (a) through (q) and   |                                   |
|     BB.5002 (a) through (q)       |                                   |
|                                   |                                   |
| -   BC.0002 (a) through (o),      |                                   |
|     BC.1002 (a) through (o),      |                                   |
|     BC.2002 (a) through (o),      |                                   |
|     BC.3002 (a) through (o),      |                                   |
|     BC.4002 (a) through (o) and   |                                   |
|     BC.5002 (a) through (o)       |                                   |
+-----------------------------------+-----------------------------------+

5.1 *Award for Fleet Card:* The following formula will be used in
evaluating total overall price (options will be evaluated by adding the
total price for all options to the total price for the basic
requirement) for the fleet card.

BA.0001 - BA.0002

5.2 *Award for an Integrated Solution Fleet Card:* The following formula
will be used in evaluating total overall price (options will be
evaluated by adding the total price for all options to the total price
for the basic requirement) for the integrated solution.

BA.0001 (a) - BA.0002

5.3 *Award for Travel Card:* The following formula will be used in
evaluating total overall price (options will be evaluated by adding the
total price for all options to the total price for the basic
requirement) for the travel card.

BB.0001 - BB.0002

5.4 *Award for an Integrated Solution Travel Card:* The following
formula will be used in evaluating total overall price (options will be
evaluated by adding the total price for all options to the total price
for the basic requirement) for the integrated solution.

BB.0001 (a) - BB.0002

5.5 *Award for Purchase Card:* The following formula will be used in
evaluating total overall price (options will be evaluated by adding the
total price for all options to the total price for the basic
requirement) for the purchase card.

BC.0001 - BC.0002

5.6 *Award for an Integrated Solution Purchase Card:* The following
formula will be used in evaluating total overall price (options will be
evaluated by adding the total price for all options to the total price
for the basic requirement) for the integrated solution.

BC.0001 (a) - BC.0002

## 6. PRODUCTIVITY REFUND: M‑FSS‑FCXC‑\_\_\_ (MAY 1997)

Any productivity refund offered will not impact the aggregate financial
proposal described above; however, as the difference in aggregate
financial proposals become less significant, the offeror's productivity
refunds becomes more significant. Agencies are required by OMB Circular
A-125 to weigh the requirement to make early payment against the good
stewardship inherent in effective cash management principles. Any
productivity refund offered must take this requirement into account.

## 7. BENCHMARK TASK EVALUATION: M‑FSS‑FCXC‑\_\_\_ (MAY 1997)

Insert when completed, technical.

BENCHMARK PRICING

+-----------------------------------+-----------------------------------+
| Contract Line Item Numbers        | Evaluation Method                 |
| (CLINs)                           |                                   |
+-----------------------------------+-----------------------------------+
| -   BA.0003, BA.1003, BA.2003,    | Evaluated Benchmark Quantity      |
|     BA.3003, BA.4003 and BA.5003  |                                   |
|                                   | x                                 |
| -   BB.0003, BB.1003, BB.2003,    |                                   |
|     BB.3003, BB.4003 and BB.5003  | Price Offered                     |
|                                   |                                   |
| -   BC.0003, BC.1003, BC.2003,    |                                   |
|     BC.3003, BC.4003 and BC.5003  |                                   |
+-----------------------------------+-----------------------------------+

#  52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS---COMMERCIAL ITEMS (JAN 1997) (DEVIATION\--MAY 1996) 

> \(a\) Definitions. As used in this provision:
>
> Emerging small business means a small business concern whose size is
> no greater than 50 percent of the numerical size standard for the
> standard industrial classification code designated.
>
> Small business concern means a concern, including its affiliates, that
> is independently owned and operated, not dominant in the field of
> operation in which it is bidding on Government contracts, and
> qualified as a small business under the criteria in 13 CFR Part 121
> and size standards in this solicitation.
>
> Small disadvantaged business concern means a small business concern
> that---
>
> \(1\) Is at least 51 percent unconditionally owned by one or more
> individuals who are both socially and economically disadvantaged, or a
> publicly owned business, having at least 51 percent of its stock
> unconditionally owned by one or more socially and economically
> disadvantaged individuals, and
>
> \(2\) Has its management and daily business controlled by one or more
> such individuals. This term also means a small business concern that
> is at least 51 percent unconditionally owned by an economically
> disadvantaged Indian tribe or Native Hawaiian organization, or a
> publicly owned business having at least 51 percent of its stock
> unconditionally owned by one or more of these entities, which has its
> management and daily business controlled by members of an economically
> disadvantaged Indian tribe or Native Hawaiian organization and which
> meets the requirements of 13 CFR Part 124.
>
> Women-owned small business concern means a small business concern---
>
> \(a\) Which is at least 51 percent owned by one or more women or, in
> the case of any publicly owned business, at least 51 percent of the
> stock of which is owned by one or more women; and
>
> \(b\) Whose management and daily business operations are controlled by
> one or more women.
>
> Women-owned business concern means a concern which is at least 51
> percent owned by one or more women; or in the case of any publicly
> owned business, at least 51 percent of the stock of which is owned by
> one or more women; and whose management and daily business operations
> are controlled by one or more women.
>
> \(b\) Taxpayer identification number (TIN) (26 U.S.C. 6050M).
>
> \(1\) Taxpayer Identification Number (TIN).
>
> \_\_\_\_\_TIN: \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_.
>
> \_\_\_\_\_TIN has been applied for.
>
> \_\_\_\_\_TIN is not required because:
>
> \_\_\_\_\_Offeror is a nonresident alien, foreign corporation, or
> foreign partnership that does not have income effectively connected
> with the conduct of a trade or business in the U.S. and does not have
> an office or place of business or a fiscal paying agent in the U.S.;
>
> \_\_\_\_\_Offeror is an agency or instrumentality of a foreign
> government;
>
> \_\_\_\_\_Offeror is an agency or instrumentality of a Federal, state,
> or local government;
>
> \_\_\_\_\_Other. State basis. \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \(2\) Corporate Status.
>
> \_\_\_\_\_Corporation providing medical and health care services, or
> engaged in the billing and collecting of payments for such services;
>
> \_\_\_\_\_Other corporate entity;
>
> \_\_\_\_\_Not a corporate entity:
>
> \_\_\_\_\_Sole proprietorship
>
> \_\_\_\_\_Partnership
>
> \_\_\_\_\_Hospital or extended care facility described in 26 CFR
> 501(c)(3) that is exempt from taxation under 26 CFR 501(a).
>
> \(3\) Common Parent.
>
> \_\_\_\_\_Offeror is not owned or controlled by a common parent.
>
> Name and TIN of common parent:
>
> Name\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> TIN\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \(c\) Offerors must complete the following representations when the
> resulting contract is to be performed inside the United States, its
> territories or possessions, Puerto Rico, the Trust Territory of the
> Pacific Islands, or the District of Columbia. Check all that apply.
>
> \(1\) Small business concern. The offeror represents as part of its
> offer that it \[   \] is, \[   \] is not a small business concern.
>
> \(2\) Small disadvantaged business concern. The offeror represents
> that it \[   \] is, \[   \] is not a small disadvantaged business
> concern.
>
> \(3\) Women-owned small business concern. The offeror represents that
> it \[   \] is, \[   \] is not a women-owned small business concern.
>
> Note: Complete paragraphs (c)(4) and (c)(5) only if this solicitation
> is expected to exceed the simplified acquisition threshold.
>
> \(4\) Women-owned business concern. The offeror represents that it
> \[   \] is, \[   \] is not, a women-owned business concern.
>
> \(5\) Tie bid priority for labor surplus area concerns. If this is an
> invitation for bid, small business offerors may identify the labor
> surplus areas in which costs to be incurred on account of
> manufacturing or production (by offeror or first-tier subcontractors)
> amount to more than 50 percent of the contract price:
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_.
>
> \(6\) Small Business Size for the Small Business Competitiveness
> Demonstration Program and for the Targeted Industry Categories under
> the Small Business Competitiveness Demonstration Program. \[Complete
> only if the offeror has represented itself to be a small business
> concern under the size standards for this solicitation.\]
>
> \(i\) (Complete only for solicitations indicated in an addendum as
> being set-aside for emerging small businesses in one of the four
> designated industry groups (DIGs).) The offeror represents as part of
> its offer that it \[   \] is, \[   \] is not an emerging small
> business.
>
> \(ii\) (Complete only for solicitations indicated in an addendum as
> being for one of the targeted industry categories (TICs) or four
> designated industry groups (DIGs).) Offeror represents as follows:
>
> \(A\) Offeror\'s number of employees for the past 12 months (check the
> Employees column if size standard stated in the solicitation is
> expressed in terms of number of employees); or
>
> \(B\) Offeror\'s average annual gross revenue for the last 3 fiscal
> years (check the Average Annual Gross Number of Revenues column if
> size standard stated in the solicitation is expressed in terms of
> annual receipts)
>
> (Check one of the following):
>
> Average Annual Gross Number of Employees Revenues
>
> \[   \] 50 or fewer \[   \] \$1 million or less
>
> \[   \] 51-100 \[   \] \$1,000,001-\$2 million
>
> \[   \] 101-250 \[   \] \$2,000,001-\$3.5 million
>
> \[   \] 251-500 \[   \] \$3,500,001-\$5 million
>
> \[   \] 501-750 \[   \] \$5,000,001-\$10 million
>
> \[   \] 751-1,000 \[   \] \$10,000,001-\$17 million
>
> \[   \] Over 1,000 \[   \] Over \$17 million
>
> \(d\) Certifications and representations required to implement
> provisions of Executive Order 11246---
>
> \(1\) Certification of non-segregated facilities. (Applies only if the
> contract amount is expected to exceed \$10,000)---
>
> By submission of this offer, the offeror certifies that it does not
> and will not maintain or provide for its employees, any facilities
> that are segregated on the basis of race, color, religion, or national
> origin because of habit, local custom, or otherwise and that it does
> not and will not permit its employees to perform their services at any
> location where segregated facilities are maintained. The offeror
> agrees that a breach of this certification is a violation of the Equal
> Opportunity clause in the contract.
>
> \(2\) Previous Contracts and Compliance. The offeror represents
> that---
>
> \(i\) It \[   \] has, \[   \] has not, participated in a previous
> contract or subcontract subject either to the Equal Opportunity clause
> of this solicitation, the clause originally contained in Section 310
> of Executive Order 10925, or the clause contained in Section 201 of
> Executive Order 11114; and
>
> \(ii\) It \[   \] has, \[   \] has not, filed all required compliance
> reports.
>
> \(3\) Affirmative Action Compliance. The offeror represents that---
>
> \(i\) It \[   \] has developed and has on file, \[   \] has not
> developed and does not have on file, at each establishment,
> affirmative action programs required by rules and regulations of the
> Secretary of Labor (41 CFR Subparts 60‑1 and 60‑2), or
>
> \(ii\) It \[   \] has not previously had contracts subject to the
> written affirmative action programs requirement of the rules and
> regulations of the Secretary of Labor.
>
> \(e\) Certification Regarding Payments to Influence Federal
> Transactions (31 U.S.C. 1352). (Applies only if the contract is
> expected to exceed \$100,000.) By submission of its offer, the offeror
> certifies to the best of its knowledge and belief that no Federal
> appropriated funds have been paid or will be paid to any person for
> influencing or attempting to influence an officer or employee of any
> agency, a Member of Congress, an officer or employee of Congress or an
> employee of a Member of Congress on his or her behalf in connection
> with the award of any resultant contract.
>
> \(f\) Buy American Act---Trade Agreements---Balance of Payments
> Program Certificate. (Applies only if the General Services
> Administration Acquisition Regulation clause GSAR 552.225‑9 entitled
> "Trade Agreements Act (Deviation FAR 52.225-9)", is included in this
> solicitation.)
>
> \(1\) The offeror hereby certifies that each end product, except those
> listed in paragraph (f)(2) of this provision, is a U.S. made end
> product (as defined in the GSAR clause 552.225-9 entitled "Trade
> Agreements Act (Deviation FAR 52.225-9)" and that components of
> unknown origin have been considered to have been mined, produced, or
> manufactured outside the United States, a designated country, a North
> American Free Trade Agreement (NAFTA) country, or a Caribbean Basin
> country, as defined in section 25.401 of the Federal Acquisition
> Regulation.
>
> \(2\) Excluded End Products:
>
> Line item No. Country of origin
>
> \_\_\_\_\_\_\_\_\_\_\_\_ \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
> \_\_\_\_\_\_\_\_\_\_\_\_ \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
> (List as necessary)
>
> \(3\) Offers will be evaluated by giving certain preferences to U.S.
> made end products, designated country end products, NAFTA country end
> products (Canadian end products and Mexican end products)~~,~~ and
> Caribbean Basin country end products over other end products. In order
> to obtain these preferences in the evaluation of each excluded end
> product listed in paragraph (f)(2) of this provision, offerors must
> identify and certify below those excluded end products that are
> designated or NAFTA country end products, or Caribbean Basin country
> end products. Products that are not identified and certified below
> will not be deemed designated country end products, NAFTA country end
> products, or Caribbean Basin country end products. Offerors must
> certify by inserting the applicable line item numbers in the
> following:
>
> \(i\) The offeror certifies that the following supplies qualify as
> "Canadian end products, Mexican end products, or designated country
> end products" as those terms are defined in the GSAR clause 552.225‑9
> entitled "Trade Agreements Act (Deviation FAR 52.225-9)":
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
> (Insert line item numbers)
>
> \(ii\) The offeror certifies that the following supplies qualify as
> "Caribbean Basin country end products" as that term is defined in the
> GSAR clause 552.225-9 entitled "Trade Agreements Act (Deviation
> FAR 52.225‑9)":
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
> (Insert line item numbers)
>
> \(4\) Offers will be evaluated in accordance with paragraph (c) of the
> GSAR clause 552.225-9 entitled "Trade Agreements Act (Deviation
> FAR 52.225‑9)."
>
> \(g\) (1) Buy American Act---North American Free Trade Agreement
> (NAFTA) Implementation Act---Balance of Payments Program Certificate.
> (Applies only if FAR clause 52.225-21, Buy American Act---North
> American Free Trade Agreement (NAFTA) Implementation Act---Balance of
> Payments Program, is included in this solicitation.)
>
> \(i\) The offeror certifies that each end product being offered,
> except those listed in paragraph (g)(1)(ii) of this provision, is a
> domestic end product (as defined in the clause entitled "Buy American
> Act---North American Free Trade Agreement Implementation Act---Balance
> of Payments Program" and that components of unknown origin have been
> considered to have been mined, produced, or manufactured outside the
> United States.
>
> \(ii\) Excluded End Products:
>
> Line item No. Country of origin
>
> \_\_\_\_\_\_\_\_\_\_ \_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_\_\_\_ \_\_\_\_\_\_\_\_\_\_\
> (List as necessary )
>
> \(iii\) Offers will be evaluated by giving certain preferences to
> domestic end products or NAFTA country end products over other end
> products. In order to obtain these preferences in the evaluation of
> each excluded end product listed in paragraph (g)(1)(ii) of this
> provision, offerors must identify and certify below those excluded end
> products that are NAFTA country end products. Products that are not
> identified and certified below will not be deemed NAFTA country end
> products.
>
> The offeror certifies that the following supplies qualify as "NAFTA
> country end products"\' as that term is defined in the clause entitled
> "Buy American Act---North American Free Trade Agreement Implementation
> Act---Balance of Payments Program:"
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
> (Insert line item numbers)
>
> \(iv\) Offers will be evaluated in accordance with FAR Part 25.
>
> \(2\) Alternate I. If Alternate I to the clause at 52.225-21 is
> included in this solicitation, substitute the following paragraph
> (g)(1)(iii) for paragraph (g)(1)(iii) of this provision:
>
> (g)(1)(iii) Offers will be evaluated by giving certain preferences to
> domestic end products or Canadian end products over other end
> products. In order to obtain these preferences in the evaluation of
> each excluded end product listed in paragraph (b) of this provision,
> offerors must identify and certify below those excluded end products
> that are Canadian end products. Products that are not identified and
> certified below will not be deemed Canadian end products.
>
> The offeror certifies that the following supplies qualify as "Canadian
> end products" as that term is defined in the clause entitled "Buy
> American Act---North American Free Trade Agreement Implementation
> Act---Balance of Payments Program":
>
> \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\
> (Insert line item numbers)
>
> \(h\) Certification Regarding Debarment, Suspension or Ineligibility
> for Award (Executive Order 12549). The offeror certifies, to the best
> of its knowledge and belief, that---
>
> \(1\) The offeror and/or any of its principals \[   \] are, \[   \]
> are not presently debarred, suspended, proposed for debarment, or
> declared ineligible for the award of contracts by any Federal agency,
> and
>
> \(2\) \[   \] Have, \[   \] have not, within a three-year period
> preceding this offer, been convicted of or had a civil judgment
> rendered against them for: commission of fraud or a criminal offense
> in connection with obtaining, attempting to obtain, or performing a
> Federal, state or local government contract or subcontract; violation
> of Federal or state antitrust statutes relating to the submission of
> offers; or commission of embezzlement, theft, forgery, bribery,
> falsification or destruction of records, making false statements, tax
> evasion, or receiving stolen property; and \[   \] are, \[   \] are
> not presently indicted for, or otherwise criminally or civilly charged
> by a Government entity with, commission of any of these offenses.

**END OF SOLICITATION**

[^1]: ^\*^ ROM is defined as "Read Only Memory."

[^2]: ^·^ RAM is defined as "Random Access Memory."

[^3]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^4]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^5]: ^\*^ ROM is defined as "Read Only Memory."

[^6]: ^·^ RAM is defined as "Random Access Memory."

[^7]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^8]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^9]: ^\*^ ROM is defined as "Read Only Memory."

[^10]: ^·^ RAM is defined as "Random Access Memory."

[^11]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^12]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^13]: ^\*^ ROM is defined as "Read Only Memory."

[^14]: ^·^ RAM is defined as "Random Access Memory."

[^15]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^16]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^17]: ^\*^ ROM is defined as "Read Only Memory."

[^18]: ^·^ RAM is defined as "Random Access Memory."

[^19]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^20]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^21]: ^\*^ ROM is defined as "Read Only Memory."

[^22]: ^·^ RAM is defined as "Random Access Memory."

[^23]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^24]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^25]: ^\*^ ROM is defined as "Read Only Memory."

[^26]: ^·^ RAM is defined as "Random Access Memory."

[^27]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^28]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^29]: ^\*^ ROM is defined as "Read Only Memory."

[^30]: ^·^ RAM is defined as "Random Access Memory."

[^31]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^32]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^33]: ^\*^ ROM is defined as "Read Only Memory."

[^34]: ^·^ RAM is defined as "Random Access Memory."

[^35]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^36]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^37]: ^\*^ ROM is defined as "Read Only Memory."

[^38]: ^·^ RAM is defined as "Random Access Memory."

[^39]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^40]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^41]: ^\*^ ROM is defined as "Read Only Memory."

[^42]: ^·^ RAM is defined as "Random Access Memory."

[^43]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^44]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^45]: ^\*^ ROM is defined as "Read Only Memory."

[^46]: ^·^ RAM is defined as "Random Access Memory."

[^47]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^48]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^49]: ^\*^ ROM is defined as "Read Only Memory."

[^50]: ^·^ RAM is defined as "Random Access Memory."

[^51]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^52]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^53]: ^\*^ ROM is defined as "Read Only Memory."

[^54]: ^·^ RAM is defined as "Random Access Memory."

[^55]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^56]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^57]: ^\*^ ROM is defined as "Read Only Memory."

[^58]: ^·^ RAM is defined as "Random Access Memory."

[^59]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^60]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^61]: ^\*^ ROM is defined as "Read Only Memory."

[^62]: ^·^ RAM is defined as "Random Access Memory."

[^63]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^64]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^65]: ^\*^ ROM is defined as "Read Only Memory."

[^66]: ^·^ RAM is defined as "Random Access Memory."

[^67]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^68]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^69]: ^\*^ ROM is defined as "Read Only Memory."

[^70]: ^·^ RAM is defined as "Random Access Memory."

[^71]: ^§^ EPROM is defined as "Erasable Programmable Read Only Memory."

[^72]: ^¨^ EEPROM is defined as "Electrically Erasable Programmable Read
    Only Memory."

[^73]: Optical Character Recognition (Scan Line)

[^74]: Vehicle identification must be at least 9 characters in length to
    accommodate most Federal vehicles. International Fleet Management
    System (IFMS) vehicles utilize nine characters -- GXX-XXXXX (X =
    numbers).

[^75]: Miscellaneous Charges are fees not directly attributable to
    purchases made using the card (e.g., special report fees).

[^76]: Each agency submitting a tailored task request will evaluate the
    proposal in accordance with subparagraph (b) of FAR 16.505.

[^77]: The tailored task request must also state the relative importance
    of the evaluation factors (e.g., less than, more than, equal to,
    significantly less than, significantly more than, etc.).

[^78]: The agency will also state the evaluation methodology it will
    utilize (e.g., best value, technically acceptable/low price, etc.).

[^79]: The late proposals rule (FAR 52.212-1 (f), Late Offers, will not
    be applied to receipt of client reference questionnaires. GSA
    reserves the right to obtain and use other data pertaining to the
    offeror\'s performance in the evaluation of proposals. By past
    performance, the Government means the offeror\'s record of
    conforming to project requirements, timely performance, submitting
    acceptable deliverables, cooperating with ordering offices, and
    providing customer satisfaction.

[^80]: Instructions for the oral presentation and demonstration are
    addressed in subparagraph 14.3.1, below.

[^81]: The draft presentation package will not be evaluated as part of
    the offer.

[^82]: The draft presentation package will not be evaluated as part of
    the offer.

[^83]: The draft presentation package will not be evaluated as part of
    the offer.