DTNH22-12-R-00542.pdf

DTNH22-12-R-00542

SOLICITATION, OFFER AND AWARD

4. TYPE OF SOLICITATION2. CONTRACT NUMBER 3. SOLICITATION NUMBER

7. ISSUED BY CODE 8. ADDRESS OFFER TO (If other than Item 7)

ORDER UNDER DPAS (15 CFR 700)

6. REQUISITION/PURCHASE NUMBER

NOTE: In sealed bid solicitations "offer" and "offeror" mean "bid" and "bidder".

NEGOTIATED (RFP)

SEALED BID (IFB)

5. DATE ISSUED

1. THIS CONTRACT IS A RATED RATING PAGE OF PAGES

1 87

C. E-MAIL ADDRESS

EXT.NUMBERAREA CODE

B. TELEPHONE (NO COLLECT CALLS)A. NAME

10. FOR

INFORMATION

CALL:

CAUTION: LATE Submissions, Modifications, and Withdrawals: See Section L, Provision No. 52.214-7 or 52.215-1. All offers are subject to all terms and conditions contained in this solicitation.

(Date)(Hour) local timeuntildepository located in copies for furnishing the supplies or services in the Schedule will be received at the place specified in Item 8, or if hand carried, in the

SOLICITATION

9. Sealed offers in original and

PART IV - REPRESENTATIONS AND INSTRUCTIONS

OTHER STATEMENTS OF OFFERORS

EVALUATION FACTORS FOR AWARD

INSTRS., CONDS., AND NOTICES TO OFFERORS

REPRESENTATIONS, CERTIFICATIONS AND

LIST OF ATTACHMENTS

CONTRACT CLAUSES

PART III - LIST OF DOCUMENTS, EXHIBITS AND OTHER ATTACH.

I

J

K

L

M SPECIAL CONTRACT REQUIREMENTS

CONTRACT ADMINISTRATION DATA

DELIVERIES OR PERFORMANCE

INSPECTION AND ACCEPTANCE

PACKAGING AND MARKING

DESCRIPTION/SPECS./WORK STATEMENT

SUPPLIES OR SERVICES AND PRICES/COSTS

SOLICITATION/CONTRACT FORM

PART II - CONTRACT CLAUSESPART I - THE SCHEDULE

H

G

F

E

D

C

B

A

SEC. DESCRIPTION PAGE(S) (X) DESCRIPTION SEC. (X)

11. TABLE OF CONTENTS

18. OFFER DATE17. SIGNATURE

SUCH ADDRESS IN SCHEDULE.

IS DIFFERENT FROM ABOVE - ENTER

15C. CHECK IF REMITTANCE ADDRESS

EXT.NUMBERAREA CODE

15B. TELEPHONE NUMBER

(Type or print)AND

ADDRESS

OF

OFFEROR

CODE FACILITY

16. NAME AND TITLE OF PERSON AUTHORIZED TO SIGN OFFER15A. NAME

DATEAMENDMENT NO.DATEAMENDMENT NO.

and related documents numbered and dated):

amendments to the SOLICITATION for offerors

(The offeror acknowledges receipt of

14. ACKNOWLEDGEMENT OF AMENDMENTS

CALENDAR DAYS (%)30 CALENDAR DAYS (%)20 CALENDAR DAYS (%)10 CALENDAR DAYS (%)

(See Section I, Clause No. 52.232.8)

13. DISCOUNT FOR PROMPT PAYMENT

designated point(s), within the time specified in the schedule.

by the offeror) from the date for receipt of offers specified above, to furnish any or all items upon which prices are offered at the price set opposite each item, delivered at the

12. In compliance with the above, the undersigned agrees, if this offer is accepted within ______________ calendar days (60 calendar days unless a different period is inserted

NOTE: Item 12 does not apply if the solicitation includes the provisions at 52.214-16, Minimum Bid Acceptance Period.

OFFER (Must be fully completed by offeror)

IMPORTANT - Award will be made on this Form, or on Standard Form 26, or by other authorized official written notice.

28. AWARD DATE

(Signature of Contracting Officer)

27. UNITED STATES OF AMERICA

25. PAYMENT WILL BE MADE BY

26. NAME OF CONTRACTING OFFICER (Type or print)

CODE 24. ADMINISTERED BY (If other than Item 7)

ITEM

(4 copies unless otherwise specified)

23. SUBMIT INVOICES TO ADDRESS SHOWN IN

41 U.S.C. 253 (c) ( 10 U.S.C. 2304 (c) (

22. AUTHORITY FOR USING OTHER THAN FULL AND OPEN COMPETITION:

21. ACCOUNTING AND APPROPRIATION20. AMOUNT19. ACCEPTED AS TO ITEMS NUMBERED

AWARD (To be completed by government)

CODE

12-0014306/05/2012 X

NPO-320

Office Of Acquisition Management

DOT/NHTSA/NPO-320

1200 New Jersey Avenue, SE W51-310 Washington, DC 20590

NHTSA 1430 ET 07/06/2012

Wendell Crowder wendell.crowder@dot.gov

366-5456

X

X

X

X

X

X

X

X

X

X

X

X

X

PAGE(S)

ROSS JEFFRIES

AUTHORIZED FOR LOCAL REPRODUCTION

Previous edition is unusable

STANDARD FORM 33 (Rev. 9-97)

Prescribed by GSA - FAR (48 CFR) 53.214(c)

1-2 3-13

14-34 35-36 38-40 41-43 44-52

53-57

58-59

60-67

68-74

75-87

ITEM NO. SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

NAME OF OFFEROR OR CONTRACTOR

2 87

CONTINUATION SHEET

REFERENCE NO. OF DOCUMENT BEING CONTINUED PAGE OF

DTNH22-12-R-00542

(A) (B) (C) (D) (E) (F)

This a Request for Proposal (RFP) to provide timeshare/hosting services for the National Driver Register's Problem Driver Pointer System (PDPS). Contract award is anticipated on 8/1/12.

Period of performance is 10 years from date of award (1 Base Year and 9 Option Years).

Delivery: 08/01/2012 Delivery Location Code: SHIP TO (1)

DOT/NHTSA/

1200 New Jersey Avenue, SE Washington DC 20590

FOB: Destination

0001 Timesharing Services for PDPS

OPTIONAL FORM 336 (4-86)

Sponsored by GSA

FAR (48 CFR) 53.110

NSN 7540-01-152-8067

DTNH22-12-R-00542 Timesharing Services for Problem Driver Pointer System

SECTION B - SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 SUPPLIES/SERVICES

The contractor shall furnish, on a firm-fixed price basis, the necessary qualified personnel, facilities, materials, supplies, equipment, and services to fulfill the contract requirements in accordance with the Statement of Work (SOW), Section C, and other terms and conditions of the Contract for the effort entitled “Timesharing Services for Problem Driver Pointer System (PDPS).

B.2 PRICE SCHEDULES

B.2.1. BASE PERIOD – YEAR ONE

(From the date of contract award through twelve (12) months thereafter.)

B.2.1.1 Kickoff Meeting, Installation & Configuration Migration (From date of Contract Award through 3 months thereafter).

CLIN DESCRIPTION

CONTRACT

SECTION

FIRM FIXED

PRICE

1001 Kick-Off Meeting C.3.1 $ 1002 Installation and Configuration C.3.2-C.3.3 $ 1003 Migration C.3.4 $

B.2.1.2 Base Level of Service, Operations & Maintenance –PDPS Application Hosting & Administration (From completion of Migration (CLIN 1003) through nine (9) months thereafter).

Note: The Total Fixed Price for CLIN 1004 may be adjusted to reflect an actual period of performance that is less than, or greater than 9 months.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

9 $

B.2.1.3 Optional Additional Level of Service Requirements (Same period of performance as Price Schedule B.2.1.2) Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.1.2. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

1005 Additional SAN – 100 GB 100 GB $ 1006 Additional Virtual Application Server 1 Server $ 1007 Additional CPU for the DB Server 1 CPU $ 1008 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.2. BASE PERIOD – YEAR TWO

(The prices listed in this Section B.2.2 are in effect from the end of the BASE PERIOD—YEAR ONE through twelve (12) months thereafter.)

B.2.2.1 Base Level of Service, Operations & Maintenance –PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

12 $

B.2.2.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.2.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

2002 Additional SAN – 100 GB 100 GB $ 2003 Additional Virtual Application Server 1 Server $ 2004 Additional CPU for the DB Server 1 CPU $ 2005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.3. BASE PERIOD – YEAR THREE

NOTE: The term of the services, and the type of services provided during this Base Period –Year Three will depend upon the government’s decision to exercise the following Option Period One.

If the government decides to exercise the option period, then the services identified in Price Schedule B.2.3.1 and B.2.3.2 shall be provided for a twelve-month period following the completion of Base Period— Year Two. Price Schedule B.2.3.3 would not apply.

If the government decides not to exercise the option period, then the services identified in Price Schedules B.2.3.1 and B.2.3.2 shall be in effect for a nine-month period following the completion of Base Period – Year Two. Price Schedule B.2.3.3 would then become effective on the tenth month of this Base Period— Year Three and will continue for three months thereafter (resulting in a total period of performance for this Base Period—Year Three of twelve months.)

B.2.3.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

But refer to

NOTE above

But refer to NOTE above

B.2.3.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.3.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

3002 Additional SAN – 100 GB 100 GB $ 3003 Additional Virtual Application Server 1 Server $ 3004 Additional CPU for the DB Server 1 CPU $ 3005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.3.3 Phase- Out Period Note: This Price Schedule will only apply if the government elects not to exercise the following Option Period.

See “NOTE:” above.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

3007 Phase-Out Period C.6 Monthly $ Per Month

3 $

B.2.4. OPTION PERIOD ONE– YEAR FOUR

NOTE: The term of the services, and the type of services provided during this Option Period One –Year Four will depend upon the government’s decision to exercise the following Option Period Two.

If the government decides to exercise the option period, then the services identified in Price Schedule B.2.4.1 and B.2.4.2 shall be provided for a twelve-month period following the completion of Base Period— Year Three. Price Schedule B.2.4.3 would not apply.

If the government decides not to exercise the option period, then the services identified in Price Schedules B.2.4.1 and B.2.4.2 shall be in effect for a nine-month period following the completion of Base Period – Year Three. Price Schedule B.2.4.3 would then become effective on the tenth month of this Option Period One—Year Four and will continue for three months thereafter (resulting in a total period of performance for this Option Period One—Year Four of twelve months.)

B.2.4.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

But refer to

NOTE above

But refer to NOTE above

B.2.4.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.4.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

4002 Additional SAN – 100 GB 100 GB $ 4003 Additional Virtual Application Server 1 Server $ 4004 Additional CPU for the DB Server 1 CPU $ 4005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.4.3 Phase- Out Period Note: This Price Schedule will only apply if the government elects not to exercise the following Option Period.

See “NOTE:” above.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

4007 Phase-Out Period C.6 Monthly $

B.2.5. OPTION PERIOD TWO– YEAR FIVE

NOTE: The term of the services, and the type of services provided during this Option Period Two –Year Five will depend upon the government’s decision to exercise the following Option Period Three.

If the government decides to exercise the option period, then the services identified in Price Schedule B.2.5.1 and B.2.5.2 shall be provided for a twelve-month period following the completion of Option Period One—Year Four. Price Schedule B.2.5.3 would not apply.

If the government decides not to exercise the option period, then the services identified in Price Schedules B.2.5.1 and B.2.5.2 shall be in effect for a nine-month period following the completion of Option Period One – Year Four. Price Schedule B.2.5.3 would then become effective on the tenth month of this Option Period Two—Year Five and will continue for three months thereafter (resulting in a total period of performance for this Option Period Two—Year Five of twelve months.)

B.2.5.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

But refer to

NOTE above

But refer to NOTE above

B.2.5.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.5.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

5002 Additional SAN – 100 GB 100 GB $ 5003 Additional Virtual Application Server 1 Server $ 5004 Additional CPU for the DB Server 1 CPU $ 5005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.5.3 Phase- Out Period Note: This Price Schedule will only apply if the government elects not to exercise the following Option Period.

See “NOTE:” above.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

5007 Phase-Out Period C.6 Monthly $

B.2.6. OPTION PERIOD THREE– YEAR SIX

NOTE: The term of the services, and the type of services provided during this Option Period Three –Year Six will depend upon the government’s decision to exercise the following Option Period Four.

If the government decides to exercise the option period, then the services identified in Price Schedule B.2.6.1 and B.2.6.2 shall be provided for a twelve-month period following the completion of Option Period Two—Year Five. Price Schedule B.2.6.3 would not apply.

If the government decides not to exercise the option period, then the services identified in Price Schedules B.2.6.1 and B.2.6.2 shall be in effect for a nine-month period following the completion of Option Period Two—Year Five. Price Schedule B.2.6.3 would then become effective on the tenth month of this Option Period Three—Year Six and will continue for three months thereafter (resulting in a total period of performance for this Option Period Three—Year Six of twelve months.)

B.2.6.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Month $ Per Month

But refer to

NOTE above

But refer to NOTE above

B.2.6.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.6.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

6002 Additional SAN – 100 GB 100 GB $ 6003 Additional Virtual Application Server 1 Server $ 6004 Additional CPU for the DB Server 1 CPU $ 6005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.6.3 Phase- Out Period Note: This Price Schedule will only apply if the government elects not to exercise the following Option Period.

See “NOTE:” above.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

6007 Phase-Out Period C.6 Month $

B.2.7. OPTION PERIOD FOUR– YEAR SEVEN

NOTE: The term of the services, and the type of services provided during this Option Period Four –Year Seven will depend upon the government’s decision to exercise the following Option Period Five.

If the government decides to exercise the option period, then the services identified in Price Schedule B.2.7.1 and B.2.7.2 shall be provided for a twelve-month period following the completion of Option Period Three—Year Six. Price Schedule B.2.7.3 would not apply.

If the government decides not to exercise the option period, then the services identified in Price Schedules B.2.7.1 and B.2.7.2 shall be in effect for a nine-month period following the completion of Option Period Three—Year Six. Price Schedule B.2.7.3 would then become effective on the tenth month of this Option Period Four—Year Seven and will continue for three months thereafter (resulting in a total period of performance for this Option Period Four—Year Seven of twelve months.)

B.2.7.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

But refer to

NOTE above

But refer to NOTE above

B.2.7.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.7.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

7002 Additional SAN – 100 GB 100 GB $ 7003 Additional Virtual Application Server 1 Server $ 7004 Additional CPU for the DB Server 1 CPU $ 7005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.7.3 Phase- Out Period Note: This Price Schedule will only apply if the government elects not to exercise the following Option Period.

See “NOTE:” above.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

7007 Phase-Out Period C.6 Monthly $

B.2.8. OPTION PERIOD FIVE– YEAR EIGHT

NOTE: The term of the services, and the type of services provided during this Option Period Five –Year Eight will depend upon the government’s decision to exercise the following Option Period Six.

If the government decides to exercise the option period, then the services identified in Price Schedule B.2.8.1 and B.2.8.2 shall be provided for a twelve-month period following the completion of Option Period Four—Year Eight. Price Schedule B.2.8.3 would not apply.

If the government decides not to exercise the option period, then the services identified in Price Schedules B.2.8.1 and B.2.8.2 shall be in effect for a nine-month period following the completion of Option Period Four—Year Seven. Price Schedule B.2.8.3 would then become effective on the tenth month of this Option Period Five—Year Eight and will continue for three months thereafter (resulting in a total period of performance for this Option Period Five—Year Eight of twelve months.)

B.2.8.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

But refer to

NOTE above

But refer to NOTE above

B.2.8.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.7.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

8002 Additional SAN – 100 GB 100 GB $ 8003 Additional Virtual Application Server 1 Server $ 8004 Additional CPU for the DB Server 1 CPU $ 8005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.8.3 Phase- Out Period Note: This Price Schedule will only apply if the government elects not to exercise the following Option Period.

See “NOTE:” above.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

8007 Phase-Out Period C.6 Monthly $

B.2.9. OPTION PERIOD SIX– YEAR NINE

NOTE: The term of the services, and the type of services provided during this Option Period Six –Year Nine will depend upon the government’s decision to exercise the following Option Period Seven.

If the government decides to exercise the option period, then the services identified in Price Schedule B.2.9.1 and B.2.9.2 shall be provided for a twelve-month period following the completion of Option Period Five—Year Eight. Price Schedule B.2.9.3 would not apply.

If the government decides not to exercise the option period, then the services identified in Price Schedules B.2.9.1 and B.2.9.2 shall be in effect for a nine-month period following the completion of Option Period Five—Year Eight. Price Schedule B.2.9.3 would then become effective on the tenth month of this Option Period Six—Year Nine and will continue for three months thereafter (resulting in a total period of performance for this Option Period Six—Year Nine of twelve months.)

B.2.9.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

But refer to

NOTE above

But refer to NOTE above

B.2.9.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.9.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

9002 Additional SAN – 100 GB 100 GB $ 9003 Additional Virtual Application Server 1 Server $ 9004 Additional CPU for the DB Server 1 CPU $ 9005 Additional T-1 line 1 T-1 Line $

Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.9.3 Phase- Out Period Note: This Price Schedule will only apply if the government elects not to exercise the following Option Period.

See “NOTE:” above.

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

9007 Phase-Out Period C.6 Monthly $

B.2.10. OPTION PERIOD SEVEN– YEAR TEN

NOTE: The Period of Performance for this Option Period Seven—Year Ten shall be as follows:

Base Level of Service: Price Schedule B.2.10.1 shall be in effect for a nine-month period following the completion of Option Period Six—Year Nine.

Optional Additional Level of Service Requirements: Price Schedule B.2.10.2 shall be in effect for a nine-month period following the completion of Option Period Six—Year Nine.

Phase-Out Period: Price Schedule B.2.10.3 shall be in effect for a three-month period beginning ten months following the completion of Option Period Six—Year Nine.

The total period of performance for this Option Period Seven—Year Ten is twelve months.

B.2.10.1 Base Level of Service, Operations & Maintenance—PDPS Application Hosting & Administration

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

10001 PDPS Application Hosting/ Administration

C.3.5 through C.5.12 Monthly $ Per Month

9 $

B.2.10.2 Optional Additional Level of Service Requirements Note: The CLINs appearing in the following price schedule apply to service requirements over and above the Base Level of Service covered under Price Schedule B.2.10.1. This additional service may be ordered at the option of the government at any time during the effective term of this Price Schedule.

CLIN DESCRIPTION UNIT OF ISSUE

UNIT

PRICE

10002 Additional SAN – 100 GB 100 GB $ 10003 Additional Virtual Application Server 1 Server $ 10004 Additional CPU for the DB Server 1 CPU $ 10005 Additional T-1 line 1 T-1 Line $

10006 Remote access for additional NDR person via Secure ID

Remote Access for 1 additional NDR user

B.2.10.3 Phase- Out Period

CLIN DESCRIPTION

CONTRACT

SECTION

UNIT OF

ISSUE

UNIT

PRICE

UNITS

TOTAL

FIXED

PRICE

10007 Phase-Out Period C.6 Monthly $

SECTION C – DESCRIPTION/ SPECIFICATIONS/ WORK STATEMENT

Note: Attachment 19 provides a list of terms and acronyms, along with their corresponding definitions, used within this document.

C.1 INTRODUCTION AND BACKGROUND

The National Driver Register (NDR) program of the National Highway Traffic Safety Administration (NHTSA), U.S. Department of Transportation (DOT), acts as a nationwide clearinghouse for driver licensing decision makers (i.e., State driver licensing authorities and Federal agencies that employ people as drivers). It is also a source of information for programs related to airline, railroad, highway, and maritime safety administered by Federal agencies. It may also be used by employers to inquire on employees who are being hired as motor vehicle operators or airline pilots.

C.1.1 Legislative Background Established by Public Law 86-660 in 1960, the NDR began operating in July 1961. Basic provisions of the law remain in effect, but significant changes have been legislated since the NDR was founded. Access to the NDR is granted by statute (Title 49 U.S.C. Chapter 303).

Public Law 97-364, known as the NDR Act of 1982, significantly affected the NDR. This legislation required a more effective and immediate means of obtaining information on problem drivers, which resulted in the development of the Problem Driver Pointer System (PDPS). Under PDPS, when a probable identification is made as a result of an inquiry on a driver license applicant, the NDR sends a request for the driver's status (i.e., licensed, eligible, not eligible, reported deceased) to the State of Record (SOR) on behalf of the State of Inquiry (SOI). The SOR then sends the driver's status data directly to the SOI. Four States pilot tested the PDPS process in 1987. The PDPS is derived from the results of the pilot test and the comments received during the rulemaking, which was finalized on August 20, 1991. It has been implemented nationwide.

The most recent legislation affecting the NDR is the Motor Carrier Safety Improvement Act of 1999. This law requires an NDR check before any motor vehicle operator’s license is issued or renewed.

C.1.2 PDPS General Description The PDPS is a centralized database of drivers whose privilege to drive has been suspended, revoked, cancelled or denied for cause. It is operated by NHTSA in cooperation with the 50 States and the District of Columbia (D.C.).

The Federal Aviation Administration (FAA), Federal Railroad Administration (FRA), United States Coast Guard (USCG), National Transportation Safety Board (NTSB), certain employers, and individuals are also authorized to access NDR information. These entities are often referred to as “other authorized users of the PDPS”. The PDPS serves as a central point of contact for the chief driver licensing official in a State to use to determine if a license applicant has been reported as a problem driver by any other State. Such information alerts States of potential problem drivers. This facilitates both the administration of driver improvement actions and driver license issuance.

All States and DC participate in PDPS in conformance with the NDR Act of 1982.

The PDPS uses its file of information regarding problem drivers at the PDPS host computer system to support a pointer system that coordinates the exchange of information between States of Inquiry, the NDR, and States of Record.

When a State sends an inquiry, the PDPS responds to the inquiry by sending the match indication and the matching data back to the SOI and sends a Driver Status request to the SOR. The SOR transmits the response (the Driver Status) directly to the SOI.

After the SOI receives the Status, it may decide to request a full Driver History Record or a printed Driver License Abstract from the SOR. The Driver History Request must be sent from the SOI to the SOR, the Driver License Abstract Request may be sent to the SOR through PDPS.

PDPS involves much more than inquiry service. States can also submit records for addition, changes, and deletion.

PDPS provides authorized users access to NDR information.

States send updates (identification data regarding problem drivers, i.e., driver license number, full legal name, alias names, date of birth, height, weight, sex, eye color, and Social Security Number (if collected by the State)) and inquiries (identification data regarding persons who are applying for or renewing licenses) via the PDPS client.

In addition, States may completely replace all of their data on the PDPS with a new set of data. This process is called a Clean File. This is a 2-day process performed by PDPS six to eight times a year (on Saturday and Sunday) which unloads the master files and indices, deletes old records, and reloads the files. A State may participate by sending their complete file of data in update format on the week prior to the Clean File weekend. States are encouraged to participate at least once a year.

The file search involved in processing inquiries is a soundex-based name-search routine. This is needed, because there is no nationwide method to uniquely identify drivers. When the name search finds a record in the PDPS file that qualifies as a match, it returns a probable identification to the inquiring party. The user is then responsible for verifying that the applicant and the problem driver are the same person.

A principal objective of the PDPS application is the rapid provision of timely and accurate data to support licensing approval and denial decisions by State driver licensing personnel at the licensing agency office.

States are responsible for intra-state hardware, software and communications. The State application programs may be written in any language and may be running on a host system of any manufacture. States are also responsible for the development of software interfaces and procedures for communicating with PDPS via the AAMVAnet, Inc.

network.

Network connectivity support for State interaction with PDPS is provided through the American Association of Motor Vehicle Administrators’ network (AAMVAnet™). This network handles all network traffic between the State systems and the PDPS host system. The network is a virtual private network (VPN) procured by AAMVA through its current provider, Verizon Business. State FTP and SFTP traffic also traverses this network.

All interactive messages are routed through AAMVA’s Network Control Software (NCS). This application distributes traffic to its designated destination. This software facilitates communication between different hardware platforms and operating systems.

C.1.3 PDPS Operations and Environment

SOLICITATION NOTICE

For a description of the operating environment in existence at time of RFP release, refer to:

Attachments 2-4 “PDPS Current Hardware Configurations” Attachments 5-7 “PDPS Current Production and Development Hardware Environments and PDPS

Current Production Software Environment” Attachments 8 and 9, Section J – “PDPS Network Environment.

PDPS receives the inquiries from the various states via web service interface. The Web service has been developed using SOAP protocol and is deployed under the Web Logic application server. The Web service transfers the inquiries to the Database server. The messages are transmitted internally within the Database using Oracle Advance Queues and go through processing logic using Oracle PL/SQL code. The responses from the System are sent using a Java program by invoking the AAMVA Web service. There are two Database server nodes performing the inquiry transactions in a RAC environment.

States and other authorized users send files via SFTP/FTP to the PDPS application. These files are stored under the Oracle ASM managed Cluster File System (ACFS) on the Database Servers. This allows the files to be seen by both the Database Servers.

PDPS handles Personally Identifiable Information (PII) data. This is encrypted at the table space level using Oracle's Transparent Data Encryption (TDE) solution.

C.1.3.1 Data Center Facilities and Infrastructure The PDPS Servers are housed in a secure Data Center. The Servers are behind a firewall and access is controlled via specific firewall rules. The Data Center has backup generator power and UPS facilities. The Disaster Recovery (DR) facility is located in a different geographical location and the Database is replicated to the DR site using standard Dataguard replication.

C.1.3.2 PDPS Physical Servers (Refer to Attachments 2-4) The PDPS application utilizes four dedicated Servers. Two servers serve as application servers and the other two serve as database servers. The Development environment has a similar architecture as well. There is also a Windows Development server used for source version control, code development etc.

C.1.3.3 PDPS Hardware / Software (Refer to Attachments 5-7).

The load balancer receives transactions from PDPS users and ensures that the requests are evenly distributed across the PDPS application servers. Likewise, state FTP/SFTP requests go through the load balancer as well.

The PDPS system processes messages from the states, sends out the responses and generates the reports for the NDR users. The states send interactive messages through the AAMVA network. AAMVA invokes the web services on the Application Servers to send interactive messages to PDPS. The web services are deployed on the Web Logic Application Server. The load balancer distributes the AAMVA messages between the two application servers. Each of the application servers sends the message to its primary database. Application Server 1 has Production DB Server 1 as the primary database and Application Server 2 has the Production DB Server 2 as the primary database.

In case the primary database is not available, they send the message to the secondary database, which is Production DB Server 2 for Application Server 1 and Production Server DB 1 for Application Server 2.

The Production Database Server 1 and Production Database Server 2 share the database files on shared SAN disks in an Oracle Real Application Cluster (RAC) environment.

Batch messages are received from and sent to States and other authorized users via FTP or SFTP. The majority of the messages (interactive and batch) are driver inquiry messages. The PDPS system processes messages in real time interactive mode or in nightly batch jobs. The nightly batch jobs generate PDF reports. This system also has weekly batch jobs for maintenance activities. The GUI implemented using the Oracle Application Express allows the NDR staff to access various reports and manage driver pointers in the database.

The PDPS Application Support Team uses the Windows and UNIX servers to connect to the database and application servers for daily maintenance activities. The Windows server also has supporting software such as CVS, Toad, SQL Developer, Request Tracker, Putty etc. The Oracle Enterprise Manager is used to manage the databases using the web browser.

C.1.3.4 PDPS/AAMVAnet Inc. Network Specifications (See Attachments 8-9) The AAMVA connectivity services are fully managed MPLS services consisting of the Telco circuit and vendor premises equipment (VPE) package that includes a Cisco 1841 router and a dial up modem for AAMVA vendor's remote access for management and maintenance.

C.1.3.5 Data Center Software The CA Insight Database Performance Manager for Distributed Databases is a tool which allows the database to be proactively monitored and managed across the IT infrastructure. Performance issues are addressed before the PDPS application is impacted. CA Insight allows for monitoring on a 24 hours a day, seven days a week basis.

C.2 GENERAL REQUIREMENTS

NHTSA requires services for a hybrid Cloud (dedicated/virtual) hosting environment for the NDR program.

Specific Requirements are addressed in Section C.3 of this contract.

The contractor shall be responsible for the physical configuration of the PDPS Network, its interface with AAMVAnet™ and NCS and its interface with NDR staff and application support contractors who are responsible for internal NDR operations.

The contractor shall cover all of the NDR’s technical and general support requirements for migration, operation and support of hosting services, database services, network management, and infrastructure management including application servers, database servers, network connectivity, security, Storage Area Network (SAN), Secure File Transfer Protocol/File Transfer Protocol (SFTP/FTP), and disaster recovery.

C.3 SPECIFIC REQUIREMENTS

NHTSA's IT environment must make use of current technologies to provide the best possible support at the most reasonable cost. NHTSA requires that the PDPS application be moved from the current dedicated server web services architecture to a hybrid Cloud environment (Refer to Attachments 10-13) to capitalize on cost savings over the life of the system.

NHTSA requires migration of the existing application servers (production and development) and the Windows development server to virtual servers. The database servers must remain as dedicated physical servers and the data must remain hosted on a SAN

The contractor shall be responsible for moving the PDPS system from the existing environment to the an infrastructure that meets contract requirements, and performing acceptance tests to verify that the PDPS application is operational and meets performance guidelines. PDPS must continue to operate at the current site until after the acceptance tests have been completed successfully. All relocation efforts shall require coordination with NHTSA.

NHTSA will require access to the new system and to the contractor’s technical staff to verify operational capabilities. The contractor shall create the Development environment first and then provide the necessary support for the installation/configuration of the PDPS Development application. This will allow the NDR staff to perform the required functionality and performance tests. While the contractor in coordination with the Government works in the development environment, the contractor shall immediately install and configure the production environment and DR environment.

The contractor shall host and perform administrative duties including, but not limited to, database administration, OS administration, network administration, and infrastructure administration for the PDPS application environment for the remainder of the contract.

The contractor shall provide the Development environment within one month from the contract award date and shall provide the Production and Disaster Recovery environments within two months from the contract award date.

If testing the NDR application in the Development environment provided does not meet the current performance of the NDR system, the contractor shall revise the environment to meet the required performance. The revised environment may take into account the need for additional hardware (e.g., additional processors, additional memory, SAN, etc.).

The contractor also shall be prepared to migrate the PDPS from the existing Solaris 10 OS to a Linux OS if requested by the government. NHTSA may require this migration after successful completion of migrating PDPS in accordance with the contract requirements. In the case of a migration, the contractor shall provide a test infrastructure similar to the Development infrastructure but with Linux OS.

C.3.1 Kick-off Meeting Within two (2) weeks of contract award, NHTSA and the contractor shall participate in a “Kick-off” meeting to be held at the contractor’s office. During this meeting, the contractor shall present an oral briefing which shall include an overview of the contract’s requirements, a discussion of how the contractor will fulfill those requirements, and any other information relevant to this contract’s performance. Discussions regarding the Contractor’s technical approach and plan of action shall take place and serve as the basis for a revised action plan as required.

C.3.2 Infrastructure Installation / Configuration The contractor shall host the PDPS environment in the Continental United States (CONUS). Any regions or areas outside of the CONUS are not permitted.

This section states the minimum requirements for physical servers, virtual servers, and network components that must be met to create a stable infrastructure that will allow the PDPS application to perform at or exceed its current performance levels as stated below.

Real time (Interactive) messages are processed (within the PDPS application) internally in 2 seconds The application infrastructure internal network speed is 1GBit/sec

C.3.2.1 SAN Installation/Configuration (Refer to Attachments 20-21) The PDPS application uses SAN storage. The contractor shall configure SAN on the database and application servers and be responsible for storing SAN data. The size of the SAN shall be 1.15TB for the production environment and 1.2TB for the development environment.

C.3.2.2 Database Physical Server Installation/Configuration (Refer to Attachments 20-21) The contractor shall provide four (4) physical, dedicated database servers; two (2) for the production environment and two (2) for the development environment. The servers shall allow the PDPS Oracle 11g R2 database to perform at or greater than the PDPS application performance levels detailed in Section C.3.2. The contractor shall supply database servers that meet or exceed the performance of the existing hardware configuration.

C.3.2.3 OS Installation for Each Physical Server The contractor shall install and configure the Sun Solaris 10 operating system on all the UNIX servers including physical Servers and Virtual Servers. The contractor shall ensure that the OS release version is current (or as specified by NDR) and fully supported by a licensed vendor and it is compatible with Oracle 11g R2 database configurations and communication with the SAN. Also, the OS must support the FTP and SFTP requirements from the various States and other users that use the PDPS application.

C.3.2.4 Installation and Configuration of FTP/SFTP Accounts The contractor shall configure FTP or SFTP connections for the 50 States, District of Columbia, US Coast Guard, FRA, and FAA. Each entity shall have a separate UNIX account and security shall prevent each account from seeing other account’s files. When additional users require FTP/SFTP access, accounts shall be established in the same manner.

C.3.2.5 Oracle 11g R2 Database Installation/Configuration (Refer to Attachments 24-25) Oracle Enterprise Edition 11g R2 is used as the database server for the PDPS database system.

The contractor shall install and configure Oracle 11g R2 on the database servers and install and configure the Oracle client on the virtual application servers and Windows development virtual server.

• Oracle 11g R2 software shall be installed with the patch level existing in the current environment at time of migration.

• The Oracle version used in the current environment is Oracle Database 11g R2 Enterprise Edition Release

11.2.0.2 - 64 bit with the Partitioning, Real Application Clusters (RAC), Automatic Storage Management, OLAP, Transparent Data Encryption (TDE), Data Mining and Real Application Testing options.

• Oracle Dataguard Software needs to be configured on the Production Database Servers to be able to replicate the data to the DR Database server using standard Dataguard software.

The contractor shall perform the functions as specified in sections C 3.2.5.1 through C.3.2.5.9.

C.3.2.5.1 Database Creation and Configuration The contractor shall create empty instances on the two production and development database servers along with the minimum required tablespaces. NHTSA will create the application schema and associated tablespaces. The empty instances shall be as follows:

Two clustered production database instances; one instance on each Production Database Server Two clustered development database instances; one instance on each Development Database Server One non-clustered development database instance on the Development Database Server Node 1

C.3.2.5.2 Real Application Clusters (RAC) Configuration The contractor shall configure the RAC as a 2-node cluster for production databases to allow the two Oracle instances to share the same database storage. Similarly, a clustered RAC configuration shall be configured for the two development databases.

C.3.2.5.3 ASM and Oracle Cluster File System (ACFS) configuration ASM shall be the storage solution. The contractor shall configure the ASM and Cluster File System to include, but not be limited, to the following:

• Configure disk groups

• Configure ACFS to hold regular non-database files shared between the two nodes The disk group and tablespace configurations shall be consistent with the existing database configurations and shall facilitate the database creation from the current database files.

C.3.2.5.4 Server and Listener Grid Configuration The contractor shall configure the Oracle listeners and test the connectivity to the databases.

C.3.2.5.5 Installation and Configuration of the Oracle Client The contractor shall install the Oracle Client 11g on the application virtual servers and Windows development virtual server.

C.3.2.5.6 Installation and Configuration of Oracle Enterprise Manager The contractor shall install and configure the Oracle Enterprise Manager on all of the database instances.

C.3.2.5.7 Database backups and Recovery The contractor shall be responsible for having a database backup plan and recovery plan that are approved by the NHTSA COTR and to perform periodic recovery tests to ensure that the backup and recovery plans are working properly.

C.3.2.5.8 OCJ4 Installation Oracle Containers for Java (OC4J) is Oracle’s application server which is used to run the formatter for printing documents from the PDPS UI. The contractor shall install and configure OCJ4 on all of the database servers.

C.3.2.5.9 Database Performance Monitoring Software (Refer to Attachment 14) The contractor shall install CA Insight or similar ‘industry standard’ tool, with the approval of the COTR, to monitor the health and performance of the database. The contractor shall monitor the database parameters specified in Attachment 14, PDPS Database Parameter Monitoring Matrix.

C.3.2.6 Virtual Application Server Installation/Configuration (Refer to Attachments 10-12 and 24-25).

The contractor shall create two or more virtual application servers for the production environment. The same setup is required for the development environment. Both environments shall allow the PDPS application to perform at or greater than the performance levels stated in Section C.3.2. Refer to Attachments 10-12 and 24-25, PDPS Target Production and Development Hardware and Software Environments and Configurations for application server configuration guidelines.

C.3.2.6.1 OS Installation and Configuration for each Virtual Application Server The contractor shall install and configure the latest release (or release version as specified by the COTR) of Sun Solaris OS on each of the virtual Application Servers. It shall be fully supported by a licensed vendor and compatible with application server software (i.e., WebLogic, JBoss, etc.) configurations.

C.3.2.6.2 WebLogic/JBoss Installation/Configuration The contractor shall support the installation of the WebLogic or JBoss software on the virtual application servers and support the setup and configuration.

C.3.2.7 PDPS Virtual Windows Development Server (Refer to Attachments 13 and 22)

C.3.2.7.1 Windows OS Installation and Configuration On the Windows virtual server, the contractor shall install and configure the Microsoft Windows OS. The contractor shall perform all of the installation and configuration activities including, but not limited to, the following:

• Install Windows Server 2003 R2, Service Pack 1 or a similar OS.

• Create all users and associated permissions.

• Configure FTP/SFTP.

C.3.2.7.2 Supporting Software NOTE: Please refer to the installation and configuration of the following software in Section C.3.4.3.

• Source Code control system (CVS)

• Request Tracker (RT)

• DOORS (Requirements Tracking Tool)

• Toad

C.3.2.8 and C.3.2.9 RESERVED

C.3.2.10 Load Balancer Installation/Configuration The contractor shall install and configure a load balancer to distribute the HTTP requests to the application servers.

The contractor shall also install and configure a load balancer to distribute the FTP requests to the database servers.

The PDPS system currently uses the F5 load balancer. With the approval of the COTR, the contractor may use an alternative load balancer.

The load balancer shall be able to handle 400,000 or more HTTP requests/day with a peak of 40,000 or more HTTP requests/hour and evenly distribute them to the application servers.

C.3.3 Network Installation and Configuration

C.3.3.1. Configuration of Network Connectivity with AAMVAnet™ The AAMVAnet™ connectivity services are fully managed MPLS services consisting of the Telco circuit and vendor premises equipment (VPE) package that includes a Cisco 1841 router and a dial up modem for Verizon's remote access for management and maintenance.

The contractor shall provide one regular voice grade line (i.e., POTS line) for each connection/VPE package.