Request for Proposal - Revised 121209.doc

RFP# CC-09-HQ-R-0013

Revised 12/12/2008

TABLE OF CONTENTS

SECTION I PERFORMANCE WORK STATEMENT..……….…………………..2

SECTION II

CONTRACT LINE ITEMS……………………………..……………..18

SECTION III

CONTRACT CLAUSES

SECTION IV

INSTRUCTIONS AND EVALUATIONS FACTORS………

SECTION V

REPRESENTATIONS AND CERTIFICATIONS…………………...59

SECTION VI

PAST PERFORMANCE QUESTIONNAIRE………………………..71

SECTION VII

PERFORMANCE REQUIREMENTS SUMMARY MATRIX……..76

Attachment 1:

Domestic General Purpose, Private Label and Business Attachment 2:

Foreign Portfolio Attachment 3:

Credit Card Schedules and Definitions Attachment 4:

Section 508 Traceability Matrix Attachment 5:

Preliminary Third Party Service Provider Information

Security Self Assessment Attachment 6:

Information System Security Plan Attachment 7:

Subcontracting Plan Attachment 8:

Organization Conflicts of Interest Disclosure/Representation

PERFORMANCE WORK STATEMENT

1.0 Vision

The Office of the Comptroller of the Currency (OCC) needs services for data collection, aggregation, validation, storage, retrieval and reporting services for a distinct set of Credit Card data submitted periodically by federally regulated banks ( “Banks”). This effort is intended to support risk based bank supervision of large banks by enhancing benchmarking and analytic capabilities.

2.0 Background

The purpose of collecting the Credit Card data on a monthly basis is to develop standard data elements, definitions and reporting schedules to conduct early warning analysis and benchmarking across major credit card issuers.

Credit Card data elements, definitions and schedules are described in Attachments 1 through 3. Credit Card data must be submitted by nine (9) OCC supervised credit card issuers on a monthly basis using data from the previous month end (the “As of Date”). The Banks’ first filing will be for the months of January and February 2009, with an As of Dates of January 31, 2009 and February 28, 2009, respectively. This data will be submitted by the banks no later than March 31, 2009 (see Figure 1). On a monthly basis thereafter, banks will have thirty (30) calendar days after the previous month’s end to submit the data - the “Reporting Date” (see Figure 2). Banks may file the data for the previous month any time during those thirty (30) days. As needed, banks may resubmit their filing, either of their own accord or at the direction of the OCC.

3.0 Scope The Contractor shall provide an electronic interface for filing or uploading of periodic reports for Credit Card data. The quality and reliability of the data shall be checked as part of the vendor and banks’ data validation processes. The Agency requires services and expertise in working with large complex bank companies in regards to risk based analysis, benchmarking, and risk reporting for revolving credit card exposures.

The Contractor shall provide direct assistance to banks to resolve data quality issues and make recommendations to the OCC for further improving data quality. The Contractor shall provide a data repository for the storage of the data, which is conducive to the generation of reports and analytical analysis. The Contractor shall provide expertise in data aggregation and report design. The Contractor shall provide a secure web-based portal from which government agency users may generate previously defined reports, execute ad-hoc queries and define and/or download data extracts against the previously submitted data. The content available from the web-based portal will be accessed by users to conduct ongoing supervision and risk based analysis.

4.0 Requirements The following performance requirements address the minimum required results to collect, aggregate, validate, store, retrieve and report on data series discussed herein.

The data elements to be collected depend on the Credit Card type. Lists of data elements and definitions have been provided as follows:

· Domestic General Purpose, Private Label and Business (Attachment 1)

· Foreign Portfolio (Attachment 2)

The Contractor shall gather and store data elements identified in the attachments. Where appropriate, and with the prior approval of the OCC, the Contractor may derive certain items in order to ensure common definitions and consistency across banks (e.g. average daily balance, the mapping of credit scores to a score with a common definition). All accounts (pre-charge-off) will be reported by the banks as well as all accounts charged-off within past 12 months. As additional supervisory requirements are defined, additional data elements may be added to the scope of data collection and validation. Additional data elements will be within the scope of this requirement.

As part the reporting requirements for this initiative, the Contractor shall be required to aggregate and provide the data in a reporting schedule format (Attachment 3). Instructions for mapping between the data elements and the schedules are also provided with the schedules.

The Contractor shall be responsible for adhering to the elements as described in the lists of data elements and the Credit Card Schedule Metrics and Definitions as provided by OCC (Attachments 1 through 3).

The following outlines the minimum requirements the Contractor shall provide:

4.1 Data Collection and Transmission

· The Contractor shall collect loan level and portfolio Credit Card servicing data from large complex bank companies based on the prior month-end on a monthly basis. There will be no more than nine (9) participating banks.

· The Contractor’s system shall be available and ready to collect, aggregate, validate, store, retrieve and report credit card data at the time of contract award.

· The initial monthly data collection from the banks shall be for the months of January and February 2009 with As of Dates of January 31, 2009 and February 28, 2009, respectively. The Contractor’s system shall have the ability to receive data starting March 1, 2009 (See Figure 1). The banks will submit this data no later than March 31, 2009. Monthly filings shall be accepted thereafter beginning the first of every month for the previous month’s data (See Figure 2).

· The Contractor shall be responsible for developing and assembling the structured formats (e.g. delimited text files) that will be utilized for data collection and transmission from banks based on the data elements as specified by the OCC (see Attachments 1 and 2).

· The Contractor shall leverage previous data collection efforts involving participating banks and incorporate to the OCC’s system repository any of the items defined in the OCC’s list of data elements (see Attachments 1 and 2) from the period of January 2008 to December 2008. This data shall be added to the OCC’s system repository no later than March 31, 2009.

· The Contractor shall be responsible for the collection, transmission and receipt of Credit Card bank data files from banks.

· The Contractor shall be responsible for the coordination of the monthly period end data submission with banks.

· The Contractor shall be responsible for resolving any bank compliance issues of data based upon format, structure, transmission, and quality of the data from the banks based on the OCC templates and data definitions that may arise during contract performance.

· Logical names for each data element will be provided to the Contractor by the OCC. The logical (or short business names) shall be required for use when rendering reports, executing ad-hoc queries, etc.

· The Contractor shall be responsible for working with the banks to achieve data submission compliance based on any additions, modifications, and clarifications to the data elements, schedules or definitions, as directed and approved by the OCC.

· The Contractor shall be responsible for working with the banks on the facilitation of data mapping or transformation of elements from single and/or disparate systems to comply with the Contractor’s data collection compliance and processes.

· The Contractor shall be responsible for collecting Credit Card data from single and/or disparate information systems based on the banks’ information systems.

· The Contractor shall be responsible for notifying and obtaining the approval from the OCC to request a resubmission of data by a given bank. The Contractor shall be responsible for providing the appropriate supporting documentation to justify the need for the resubmission to the OCC for approval of request.

· The Contractor shall be responsible to begin assisting participating bank companies with the preparation and submission of filings immediately upon contract award.

· The Contractor shall be responsible for working with banks to develop the strategy and plan of action for collecting required data elements, which are not readily available from participating bank systems. The Contractor will not be responsible for developing, modifying or fixing any deficiencies noted in participating bank systems. However, the Contractor shall notify the OCC of such findings through status reports discussed in Section 4.10.4.

· The Contractor shall collect and leverage account level credit bureau attributes for expanded data analysis capabilities. The contractor shall be responsible for safeguarding the privacy of account information to ensure that no SSNs, names, addresses, bank account numbers or other personally identifiable information will be obtained under this contract. This ad hoc task will be performed with prior approval and direction from the OCC.

· The Contractor shall describe its modeling capabilities to include expertise to estimate credit card portfolio defaults and credit losses under a variety of constraints and scenarios.

· The Contractor shall be responsible for conducting modeling to include estimating credit card portfolio defaults and credit losses based on a variety of OCC specified constraints and scenarios. This ad hoc task will be performed with prior approval and direction from the OCC.

4.2 Data Validation and Verification

· The Contractor shall be responsible for conducting a quality verification process covering all data prior to submitting finalized data to the OCC.

· The initial verification process shall be completed within three (3) business days of the Reporting Date (See Figures 1 and 2).

· The Contractor shall be responsible for validating the data submitted from the Banks in terms of data element compliance based on the lists of data elements and the OCC schedule templates and definitions (Attachments 1 through 3); mandatory field requirements and constraints; and performing a quality review based on the following criteria for the generation of the Edit and Data reports:

· Field specific data distributions including counts and percentages of loans with valid data;

· Identification of data that is not available for reporting because data is not maintained or collected;

· Edit check reports identifying on loan level and portfolio data that is corrupt and/or failed;

· Data trend reports to track improvements in data contributions; and

· Data quality benchmarking reports – Bank comparisons.

· Edit and data quality reports shall be submitted to the OCC within three (3) business days after the Reporting Date. (See Figures 1 and 2) Thereafter, progress reports on the remediation of edit and data quality issues shall be submitted weekly. When no filings have been submitted, the report shall reflect this fact.

· The Contractor shall be responsible for performing analysis on individual and aggregate metrics and on benchmark analysis metrics.

· The Contractor shall implement an initial set of edit and data quality rules based on their knowledge and experience. The rules shall be previously developed and currently in use with existing credit card data collection systems for a significant period of time. The rule set shall be submitted to the OCC for review as part of the vendor’s proposal.

· The Contractor shall utilize their expertise and lessons learned from assisting the banks in order to make recommendations to the OCC for the implementation of additional automated edit and data quality rules.

· The Contractor’s system shall support the addition of new automated edit and data quality rules as well as the modification or deletion of existing rules.

· The Contractor shall incorporate any additional edit and data quality rules provided by the OCC on an ongoing basis. Additional rules shall be implemented into the Contractor’s system within ten (10) business days after the request from the OCC.

· The Contractor shall remove any existing edit and data quality rule from the Contractor’s system within ten (10) business days after receiving a request for removal from the OCC.

· The Contractor shall provide the OCC with a quarterly report listing all edit and data quality rules, which have been implemented, modified or removed from their system as well as the date of their implementation, modification or removal.

· The first quarterly report of all edit and data quality rules shall be submitted to the OCC no later than sixty (60) calendar days after contract award. Thereafter, the quarterly report shall be due at the beginning of each calendar quarter.

· The Contractor shall utilize any pre-existing business relationships with the banks in order to facilitate data submission compliance. The Contractor shall be responsible for keeping the OCC informed of any necessary remediation of failed validity or data quality rules.

· The Contractor shall be responsible for working with OCC to define the data collection and analytical details for collecting and reporting the Credit Card metrics based on schedules and definitions as provided by the OCC.

· The Contractor shall complete quality verification and assist with any required resubmissions in order to have the data ready for the generation of analytical reports or data extracts within ten (10) business days after the Reporting Date (See Figures 1 and 2).

· If resubmissions occur after the initial ten (10) business days, the Contractor shall update reports previously received or otherwise due (as defined by schedules detailed herein) within four (4) business days.

· The Contractor shall prepare and submit to the OCC, prior to contract award, a Data Quality Management Plan, which will document the processes by which the requirements for Data Validation and Verification shall be met. This document shall be submitted as part of the vendor’s proposal. Proposed changes to the Data Quality Management Plan shall be submitted to the OCC for approval prior to implementation.

4.3 Data Aggregation

· The Contractor shall be responsible for data aggregation; providing and aggregating bank loan level and portfolio data based on the lists of data elements and the OCC Credit Card Metrics schedules and data definitions (Attachments 1 through 3).

· The Contractor shall be responsible for aggregation among the Banks and shall perform computations based on the OCC Credit Card Metrics schedules and data definitions.

· The Contractor shall be responsible for working with the individual bank teams for the aggregation and validation of data from single and/or disparate systems.

4.4 Data Storage and Technology

· The Contractor shall provide and maintain the technology utilized to complete the tasks as set forth by this performance work statement.

· In the event of a resubmission(s), the original submission as well as any resubmission from a bank for a given month shall be retained for reference purposes.

· All loan level and portfolio level data as well as all data aggregations (be it historical data from 2008 or data provided by the banks) must be retained by the Contractor for the life of the contract.

· All loan level and portfolio level data and all data aggregations (be it historical data from 2008 or data provided by the banks) shall be available for the life of the contract for use in reports, ad hoc queries and extracts as described throughout this Performance Work Statement.

· With prior approval from the OCC, loan level data and historical loan level data from 2008 (submissions or resubmissions) which has been available in the system for use in reports, ad hoc queries and extracts, as described throughout this Performance Work Statement, may be archived, but shall not be destroyed.

· At the end of the contract term or upon contract termination, the Contractor shall provide the OCC with a full extract of all data (loan level submissions and resubmissions, portfolio level, and aggregations) - be it historical data from 2008 or data provided by the banks. The extract shall be provided to the OCC in a file format mutually agreed upon by both the Contractor and the OCC.

· The Contractor shall be responsible for coordinating, assisting and responding to banks’ points of contact on the setup and configuration of any software required for data storage and transmission.

· The Contractor shall provide system availability 24x7 except for the maintenance period to be mutually agreed between the Contractor and OCC. The system shall be available at least 99% of the time.

· The Contractor shall prepare and provide to the OCC a Data Management Plan (DMP). The DMP shall document all facets of the Contractor’s processing and storage of OCC data. This will include the storage schema and details of the logical and physical database model of the Contractor’s underlying database(s) for this system. The Contractor shall maintain and provide updates to the DMP accordingly when management and/or storage requirements change.

· The Contractor shall provide the first version of the DMP to the OCC prior to contract award. This document shall be submitted as part of the vendor’s proposal. Updates to the DMP shall be submitted to the OCC within seven (7) business days after the Contractor implements any new management or storage procedure.

· If needed for reporting purposes, the OCC reserves the right to periodically transmit additional data to the Contractor for storage and inclusion in reports. Such data shall be transmitted in an agreed upon format and manner by both the Contractor and the OCC.

4.5 Reporting

4.5.1 Single Report

· The Contractor shall provide a definition of a single report prior to contract award. This definition shall be clearly outlined in the vendor’s proposal.

4.5. 2 Reporting Interface

· The Contractor shall provide secure internet access to a web-based portal for accessing previously defined reports, an ad-hoc query capability and data extracts.

· The website shall be production ready at the time of contract award.

· The website shall be accessible to OCC approved personnel.

· Access to the website shall be provided to OCC approved personnel no later than March 13, 2009.

· The website shall support a minimum of 50 concurrent users.

· The website and its associated functionality shall be compatible with Microsoft Internet Explorer 6 and above.

· The website and its associated functionality shall be Section 508 Compliant at time of contract award.

4.5.3 Reporting OCC Schedules and Standardized Reports

· The Contractor shall provide the report(s) based on the OCC credit card metrics schedules and data definitions.

· The Contractor shall provide the credit card metrics schedules to the OCC within seven (7) business days after the Reporting Date (See Figures 1 and 2). These schedules should be production ready no later than March 30, 2009.

· These report(s) must be downloadable into a MS Excel format based on the OCC metric dimensions and presentation as depicted in the OCC schedules (see Attachment 3) for the purpose of data analytics, pivot table creation and user designed reports.

· Once run, the resulting reports shall be printable to a printer defined on the user’s local machine.

· The Contractor shall be responsible for working with the OCC to develop up to 30 standardized recurring reports; formatted as defined by the OCC. Standardized recurring reporting shall include Credit Card Metrics. This reporting capability shall include but is not limited to:

· Providing the definition of a report;

· Identifying and customizing a monthly report deliverable;

· Providing up to 30 report templates on a recurring basis for Credit Card data. Templates shall support data reporting across the multiple reporting sources. Reporting templates may be substituted for another and/or updated reports;

· Delivering periodic market research pieces and/or ad-hoc analysis

· The required format of the standard reoccurring reports will be provided by the OCC to the Contractor after contract award.

· The Contractor shall be responsible for designing, constructing and deploying the standardized reports, within ten (10) business days of receiving a request for creating said reports from the OCC.

· On a monthly basis, previously deployed standardized reports shall be provided to the OCC within ten (10) business days after receipt the Reporting Date (See Figures 1 and 2).

4.5.4 Gap Analysis Report

· The Contractor shall be responsible for developing a GAP analysis report depicting the elements on the submission from each bank. The report shall include, but is not limited to the following metrics:

· Detail information of the elements provided and not provided by a given bank;

· Percentage of elements provided by all banks both individually and in aggregate;

· Conformity of the data submitted based on the defined OCC Metric schedules and definitions; and

· Quality of data compared to the submission of other banks.

· The GAP analysis report shall be due no later than three (3) business days after the Reporting Date (See Figures 1 and 2).

4.5.5 Additional Reports

· The Contractor shall assist and provide recommendations to the OCC on additional analytical reports based on their expertise in data aggregation and analytics. The OCC reserves the right to have the Contractor standardize these reports, and include or replace, existing standardize recurring reports as described in Section 4.5.3 Reporting OCC Schedules and Standardized Reports.

· The Contractor shall develop on demand analysis and reports as requested by OCC.

· The Contractor shall be responsible for designing, constructing and deploying additional reports, including on demand analysis and reports, within ten (10) business days of receiving a request for creating said reports from the OCC.

4.5.6 Ad-hoc Queries and Reporting

· The Contractor shall be responsible for providing a secure online ad-hoc query capability via the web based portal against loan level and portfolio Credit Card records and display the query results based on the measures specified in the query.

· The ad-hoc query tool shall allow the user to filter data in the database according to any number of parameters.

· The ad-hoc query tool shall allow the user to select what data elements from the database to include in the result set.

· The ad-hoc query tool shall allow the user to view the results of the search securely online.

· The ad-hoc query tool shall allow for the download of the result set to the user’s local machine in various file formats (e.g. a delimitated file, Microsoft Excel or SAS).

· For large results where downloading the result set to a local machine would be performance prohibitive, the Contractor shall provide a mechanism for submitting an online request that the result set in the desired format be made available for transmission to the OCC through a secure delivery method (e.g. utilizing secure file transfer protocol). The size threshold of such a result set is to be determined.

· It is mandatory that Contractors address all restrictions placed on its services with regard to downloading materials.

· The ad-hoc query tool functionally shall be production ready no later than March 30, 2009.

4.6 Data Extract Capabilities

· The Contractor shall be responsible for extracting and delivering loan level and portfolio bank data by means of a compatible file format (e.g., delimitated file type, Microsoft Excel, SAS) to the OCC. The extract shall include validated Credit Card metrics loan level and/or portfolio data.

· The Contractor shall work with the OCC to define the preferred secure method for delivery of the data (e.g. utilizing secure file transfer protocol).

· The Contractor shall be responsible for extracting the data based on the specific on demand data query requests by the OCC. (i.e., aggregate, loan level or portfolio extractions)

· The Contractor’s system shall have data extract capabilities to meet these requirements no later than March 13, 2009.

· The Contractor shall provide full or partial data extracts of database content upon request from by the OCC.

· Data extracts shall be due no later than one (1) business day after a request by the OCC.

4.7 Technical and Analytical Support

· The Contractor shall be responsible for providing technical and analytical support, Monday through Friday, 8am – 5pm EST.

· The Contractor shall be responsible for providing remediation to the OCC within 24 hours of the initial support call from the OCC to the Contractor.

· The Contractor shall provide the direct contact information for Contractor support personnel.

· The Contractor shall be prepared to provide technical and analytical support beginning the day of contract award.

4. 8 System Testing

· The Contractor shall be responsible for providing a test environment to perform acceptance testing for the OCC requirements referenced in the bullet below.

· The Contractor shall develop and submit to the OCC for approval a Test Plan, which details the process for, and facilitation of acceptance testing of OCC requirements referenced below. Topics shall include, but are not limited to testing and acceptance of the following areas along with a proposed schedule for each. Where appropriate, the Test Plan should solicit the participation of OCC personnel in the acceptance testing process (e.g. testing of standardized reports)

· Reporting OCC Schedules and Standardized Reports as described in Section 4.5.3;

· Gap analysis report as described in Section 4.5.4

· Ad-hoc queries and reporting as described in Section 4.5.6;

· Data extracts as described in Section 4.6

· The test plan shall be submitted to the OCC prior to contract award. This document shall be submitted as part of the vendor’s proposal.

· The contractor shall facilitate acceptance testing through the implementation of the test plan as submitted and approved by the OCC.

4.9 System Training

· The Contractor shall develop and submit to the OCC for approval a user-training plan for the system.

· The Contractor shall submit to the OCC their training plan, prior to contract award. This document shall be submitted as part of the vendor’s proposal.

· The Contractor shall be responsible for delivery of a system user manual and training documentation for OCC review and approval.

· The user manual and training materials shall be submitted to the OCC no later than March 27, 2009.

· The Contractor shall provide training on the secure online reporting and querying capabilities in accordance with the training plan. Up to 10 training sessions shall be performed at two or more of the OCC Training Centers located in Chicago, IL, Dallas, TX, Washington, DC and New York, NY.

· The schedule for initial session(s) shall be determined by the OCC or mutual agreement after contract award. However, the Contractor shall be prepared to begin conducting training sessions no later than March 30, 2009.

4.10 General Management, Resources, Decision Making

4.10.1 Relationships with the Participants

· The Contractor shall take a collaborative approach with the OCC and the participating banks in providing data management assistance. The Contractor shall keep the OCC well informed of project activities, timelines and status to facilitate rapid resolution of any problems or issues that may arise.

· The Contractor shall schedule and coordinate a weekly status conference call at a time mutually agreeable between the Contractor and the OCC to discuss progress of the performance requirements identified. The OCC reserves the right to change the frequency and occurrence of this meeting.

· The Contractor shall provide a report on project activities, timelines, status and issues that may arise during weekly meetings, the first of which shall be held no later than seven (7) calendar days after the date of contract award.

4.10.2 Resources

· The Contractor shall provide the necessary resources to effectively accept data transfers from the OCC; provide support to participant banks and support validation, storage, and reporting services on behalf of the OCC as described in this performance work statement.

4.10.3 Decision Making

· The Contractor shall obtain OCC input and approval on project activities and timelines. The Contractor shall provide the OCC with recommendations and obtain OCC approval prior to making requests of the participating banks.

4. 10.4 Management Reports

· The Contractor shall be responsible for meeting summaries, issues and actions based on meetings held with the participating banking institutions pertaining to data quality, validation, verification and resubmission as specified by the OCC and provide this information to the OCC as part of the weekly report. This report shall include a brief summary of the meeting, participants, location and date time of the meeting.

· The Contractor shall provide a Project Plan identifying key milestones and completion dates for each requirement. The vendor shall submit a draft copy of this document as part of their proposal, with the final version due no later than ten (10) business days after contract award.

· The Contractor shall provide weekly written status reports, both hard and soft copy, to the COTR and CO. The report at a minimum shall consist of:

· Updates to the Project Plan

· Performance requirements completed;

· Performance requirements to be addressed over the next period;

· Issues or risks surrounding performance requirements and mitigation strategies per reporting bank

· Issues requiring OCC assistance; and

· Critical deficiencies discovered to date per reporting bank, even if preliminarily assessed

5.0 Milestones and Deliverables

Table 1 – Performance Requirements Deliverable Summary

The Contractor’s system shall be available and ready to collect, aggregate, validate, store, retrieve and report credit card data at the time of contract award.

The initial monthly data collection from the banks shall be for the months of January and February 2009 with As of Dates of January, 31, 2009 and February 28, 2009, respectively. (See Figure 1). The banks will submit this data no later than March 31, 2009.

The Contractor’s system shall system shall have the ability to receive data starting March 1, 2009 (See Figure 1). Monthly filings shall be accepted thereafter beginning the first of every month for the previous month’s data (See Figure 2).

The Contractor shall leverage previous data collection efforts involving participating banks and incorporate to the OCC’s system repository any of the items defined in the OCC’s list of data elements (see Attachments 1 and 2) from the period of January 2008 to December 2008. This data shall be added to the OCC’s system repository no later than March 31, 2009.

Resubmissions In the event of resubmission, the Contractor shall update reports previously received or otherwise due (as defined by schedules detailed herein) within four (4) business days.

Bank Assistance

Contractor shall begin assisting participating bank companies with the preparation and submission of filings immediately upon contract award.

The initial verification process shall be completed within three (3) business days after the Reporting Date (See Figures 1 and 2).

Data Ready for Reporting All data validation, resubmission, etc. shall be completed so that the Contractor can release the data to the OCC as verified and shall be completed within ten (10) business days the Reporting Date (See Figures 1 and 2).

Initial Set of Automated Data Edit and Quality Checks The initial set of data edit and quality rules shall be submitted to the OCC for review as part of the vendor’s proposal Additional Edit and Quality Checks Additional rules shall be implemented into the Contractor’s system within ten (10) business days after the request from the OCC.

The Contractor shall remove any existing edit and data quality rule from the Contractor’s system within ten (10) business days after receiving a request for removal from the OCC

Edit and Data Quality Reports

Edit and data quality reports shall be submitted to the OCC within three (3) business days after the Reporting Date (See Figures 1 and 2). Thereafter, progress reports on the remediation of edit and data quality issues shall be submitted weekly. When no filings have been submitted, the report shall reflect this fact.

Data Edit and Quality Rules List

Shall be submitted quarterly with the first version due no later than sixty (60) calendar days after contractor award. Thereafter, the quarterly report shall be due at the beginning of each calendar quarter.

Recommendations for additional Data Edit and Quality Rules

Shall be submitted to the OCC at weekly status meetings.

Data Quality Management Plan

The Contractor shall submit to the OCC the Data Quality Management Plan prior to contract award. Proposed changes to the Data Quality Management Plan shall be submitted to the OCC for approval prior to implementation.

At the end of the contract term or upon contract termination, the Contractor shall provide the OCC with a full extract of all data (loan level submissions and resubmissions, portfolio level, and aggregations) - be it historical data from 2008 or data provided by the banks.

Data Management Plan (DMP)

The Contractor shall provide the first version of the DMP to the OCC prior to contract award. This document shall be submitted as part of the vendor’s proposal. Updates to the DMP shall be submitted to the OCC within seven (7) business days after the Contractor implements any new management or storage procedure.

Performance Objective 5.1 Reporting Interface

The secure website shall be production ready at the time of contract award. See also Section 4.8, System Testing.

Access to the website shall be provided to OCC approved personnel no later than March 13, 2009.

Reporting OCC Schedules Standardized Reports

OCC Credit Card schedules shall be production ready no later than March 30, 2009. See also Section 4.8, System Testing.

OCC Credit Card schedules shall be downloadable in a MS Excel format based on OCC data definitions and available no later than seven (7) business days after the Reporting Date (See Figures 1 and 2).

The Contractor shall be responsible for designing, constructing and deploying the standardized reports, within ten (10) business days of receiving a request for creating said reports from the OCC.

Standardized reports shall be provided to the OCC within ten (10) business days after receipt the Reporting Date (See Figures 1 and 2). See also Section 4.8, System Testing.

Gap Analysis Report

Gap analysis report shall become due no later than three (3) business days after the Reporting Date (See Figures 1 and 2). See also Section 4.8, System Testing.

Additional Reports

The Contractor shall be responsible for designing, constructing and deploying additional reports within ten (10) business days of receiving a request from the OCC.

Ad hoc Queries and Reporting Ad-hoc Query and Reporting functionally shall be production ready no later than March 30, 2009. See also Section 4.8, System Testing.

Data extracts shall be provided to the OCC within 1 business day of a request by the OCC.

The Contractor shall be responsible for providing remediation to the OCC within 24 hours of the initial support call from the OCC to the Contractor.

Shall commence on day of contract award.

The test plan shall be submitted to the OCC prior to contract award. This document shall be submitted as part of the vendor’s proposal.

The Contractor shall submit to the OCC their training plan, prior to contract award. This document shall be submitted as part of the vendor’s proposal.

User Manual

The user manual shall be submitted to the OCC no later than March 27, 2009.

Training Materials

The training materials shall be submitted to the OCC no later than March 27, 2009.

Conducting Training The schedule for initial session(s) will be determined by the OCC or mutual agreement after contract award. However, the Contractor shall be prepared to begin conducting training sessions no later than March 30, 2009.

The Contractor shall provide a report on project activities, timelines, status and issues that may arise during weekly meetings, the first of which shall be held no later than seven (7) calendar days after the date of contract award.

Management Reports

Reports on meetings with the participating banks shall be submitted to the OCC weekly.

Draft Project Plan identifying key milestones and completion dates for each objective shall be due prior to contract award. Final version shall be due no later than ten (10) business days after contract award.

Project status reports shall be submitted to the COTR and CO weekly.

SECTION II – CONTRACT LINE ITEM PRICES

Contract line item prices shall be proposed in MS Excel Spreadsheet format. Proposed prices must be: (1) fully loaded firm fixed prices; and (2) propose to the full performance objectives outlined in the PWS. The CLINs outlined are indicative of the pricing schedule being considered by the government however, vendors may propose additional or different CLINs that are commensurate with the vendor’s technical approach.

SECTION III- CONTRACT CLAUSES

1.0 52.212-4 Contract Terms and Conditions-Commercial Items (Feb 2007)

(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. If repair/replacement or reperformance will not correct the defects or is not possible, the Government may seek an equitable price reduction or adequate consideration for acceptance of nonconforming supplies or services. 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 may assign its rights to receive payment due as a result of performance of this contract 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). However, when a third party makes payment (e.g., use of the Governmentwide commercial purchase card), the Contractor may not assign its rights to receive payment under this contract.

(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.

(1) 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-

(i) Name and address of the Contractor;

(ii) Invoice date and number;

(iii) Contract number, contract line item number and, if applicable, the order number;

(iv) Description, quantity, unit of measure, unit price and extended price of the items delivered;

(v) Shipping number and date of shipment, including the bill of lading number and weight of shipment if shipped on Government bill of lading;

(vi) Terms of any discount for prompt payment offered;

(vii) Name and address of official to whom payment is to be sent;

(viii) Name, title, and phone number of person to notify in event of defective invoice; and

(ix) Taxpayer Identification Number (TIN). The Contractor shall include its TIN on the invoice only if required elsewhere in this contract.

(x) Electronic funds transfer (EFT) banking information.

(A) The Contractor shall include EFT banking information on the invoice only if required elsewhere in this contract.

(B) If EFT banking information is not required to be on the invoice, in order for the invoice to be a proper invoice, the Contractor shall have submitted correct EFT banking information in accordance with the applicable solicitation provision, contract clause (e.g., 52.232-33, Payment by Electronic Funds Transfer-Central Contractor Registration, or 52.232- 34, Payment by Electronic Funds Transfer-Other Than Central Contractor Registration), or applicable agency procedures.

(C) EFT banking information is not required if the Government waived the requirement to pay by EFT.

(2) Invoices will be handled in accordance with the Prompt Payment Act (31 U.S.C. 3903) and Office of Management and Budget (OMB) prompt payment regulations at 5 CFR part 1315.

(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.-

(1) Items accepted. Payment shall be made for items accepted by the Government that have been delivered to the delivery destinations set forth in this contract.

(2) Prompt payment. The Government will make payment in accordance with the Prompt Payment Act (31 U.S.C. 3903) and prompt payment regulations at 5 CFR part 1315.

(3) Electronic Funds Transfer (EFT). If the Government makes payment by EFT, see 52.212-5(b) for the appropriate EFT clause.

(4) Discount. 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.

(5) Overpayments. If the Contractor becomes aware of a duplicate contract financing or invoice payment or that the Government has otherwise overpaid on a contract financing or invoice payment, the Contractor shall immediately notify the Contracting Officer and request instructions for disposition of the overpayment.

(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 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. 3701, et seq., Contract Work Hours and Safety Standards Act; 41 U.S.C. 51-58, Anti-Kickback Act of 1986; 41 U.S.C. 265 and 10 U.S.C. 2409 relating to whistleblower protections; 49 U.S.C. 40118, Fly American; and 41 U.S.C. 423 relating to procurement integrity.

(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.

(9) The…