I_01_b - IT4 STAR Production Support PWS 2023Final.docx

Department of the Treasury Office of D.C. Pensions

System to Administer Retirement

Performance Work Statement Production Support

1.0 Background

The Balanced Budget Act of 1997 requires the Secretary of the Treasury to assume certain responsibilities for the pension plans of District of Columbia retired police officers, firefighters, teachers, and judges. These responsibilities, which have been delegated by the Secretary to the Office of D.C. Pensions, include investment and management of fund assets, distribution of certain pension benefits, and management control and benefits administration of these pension plans.

As part of its responsibilities under the Act, Office of D.C. Pensions (ODCP) is leading the development, implementation and operation of an integrated pension/payroll system called The System to Administer Retirement (STAR). ODCP has successfully deployed 7 STAR releases. STAR Release 5 marked the last major release.

STAR is based on the 9.2 version of Oracle/PeopleSoft pension and payroll modules. STAR supports the pension benefits administration for the annuitants covered by the District of Columbia Judges', Police Officers’ and Firefighters’, and Teachers’ Retirement Plans. With the deployment of release 5, STAR is also able to split the benefits payments into the federal and district portions for all payments moving forward.

The Bureau of the Fiscal Service through its Office of Information Systems Security is responsible for the current system hosting and production support and will be responsible for supporting the next deployed functionality once it is in production. The new production support contractor will work with Fiscal Service and the Technical Support Team for operational support of the STAR system. Fiscal Service will leverage this contract to maintain and enhance STAR. Additionally, the production support contractor will be responsible for developing and deploying new functionality. STAR’s standard business cycle includes monthly and quarterly migrations. Monthly migrations generally include data and query changes. Quarterly migrations include the same as monthly migrations and also include change requests for new requirements/software, fixes for implemented requirements/software, and may include upgrades to the underlying COTS software. All quarterly migrations follow a rigorous set of unit, system, and regression testing prior to migration.

2.0 Statement of Goals, Requirements, and/or Objectives

The objective of this statement of work is to obtain contractor IT services to provide supplemental support for the Fiscal Service Technical Support Team and the services it provides in the areas of:

General production support:

· Problem management

· Application maintenance

· System and database administration

· Application development

· Application implementation

· Test administration

· Knowledge transfer

· Application analysis

· Test administration

· Special projects

2.1 Tasks

2.1.1 Production Support and Upgrade Services

Outcome

· The Bureau of the Fiscal Service’s Technical Support Team is self-sufficient in operating and maintaining STAR where contractor support was provided.

· Updated system documentation, tracking logs and electronic library reflect the current production environment where contractor support is provided.

General Production Support Deliverables and Acceptable Quality Levels

· Problem Trouble Tickets Corrected and Documented on or before the established STAR response and resolution standards. The standard response times for production trouble tickets are noted below.

· STAR software Patches and Fixes Analyses finalized one week prior to final test.

· STAR software Patches and Fixes Implemented according to STAR protocols and mutually agreed upon requirements and schedule.

· STAR system analyses finalized one week prior to the Change Control meeting at which the analysis(es) is to be presented.

· STAR software upgrades Implemented according to STAR protocols and mutually agreed upon requirements and schedule. The schedule is developed collaboratively as a part of the implementation planning process.

· Change Request Analyses finalized one week prior to the Change Control meeting at which the analysis(es) is to be presented.

· Change Requests (CR), Operations Maintenance Requests (OMR), and Query Requests (QR) implemented according to STAR protocols and mutually agreed upon requirements and schedule. The schedule is developed collaboratively as a part of the implementation planning process. For CR’s and QR’s, the delivered functionality meets the requirements specified in the supporting documentation. For OMR’s, the delivered functionality meets the requirements specified in the existing baseline documentation. Design documents are uploaded into ODCP’s document repository.

· Quality Assurance of STAR calculations are conducted monthly on the previous months’ new cases to ensure STAR is properly calculating the federal/district split amounts. Results are available at the end of each month for the previous month’s cases.

· System and Database Administration support are provided according to STAR documented protocols.

· Special Project Support according to STAR protocols and mutually agreed upon requirements and schedule. The schedule is developed collaboratively as a part of the implementation planning process.

· Knowledge Transfer provided to the Fiscal Service Technical Team so that the team is self-sufficient in operating and maintaining STAR where contractor provided support and Database Administration provided according to STAR protocols.

Deliverables

Depending on support required, deliverables will be modified data in STAR or code changes appropriately documented within ODCP’s SharePoint site for STAR configuration management.

Deliverables are due on or before the date scheduled.

The Fiscal Service Technical Support Team adheres to the following standards for managing production trouble tickets. The contractor is expected to adhere to the same standards.

· Critical: 24 hours

· High: 5 business days (sooner if necessary)

· Medium: 10 business days to “ready to migrate” status

· Low: 20 business days to “ready to migrate” status The Fiscal Service Technical Support Team follows a strict configuration management methodology. The contractor is expected to follow the same methodology.

Pre-determined standards are not used for approved change requests, configuration item change requests, patches and fixes, and special projects. Instead unique schedules, milestones and standards are developed for each.

Monitoring Method

Acceptance criteria will be identified at the order level.

· Government review of deliverable quality and timeliness.

· Independent review of adherence to configuration management requirements.

2.1.1.1 Problem Management

The contractor will support the Fiscal Service Technical Support Team in providing Problem Management to support the users of the STAR system. The problem management functional area coordinates the resolution of production problems among system end-users and those operating/maintaining the system. It includes receiving incidents from users and informing users of potential workarounds or resolutions. The problems are then assigned for resolution. Users are responsible for providing detailed information surrounding their reported problems, for actively participating in the solution, and for approving the final results in a timely manner.

When directed, the contractor will support the Fiscal Service Technical Team by supporting the end users of STAR by providing the following services:

· Receive calls from end-users of STAR

· Determine priority and log problem trouble ticket information in STAR Track

· Receive end-user issue/request information assigned by Fiscal Service Support Desk

· Log issues or administrative requests received in the STAR Track database

· Resolve application and database issues in the production support environment

· Fulfill STAR stakeholder requests

· Escalate issues or requests to appropriate production support organization or resource

· Notify stakeholders of status/resolution of issues

2.1.1.2 Application Maintenance

The contractor will support the Fiscal Service Technical Team by performing maintenance support for the STAR production environment. The support shall include production fixes (problem trouble tickets), Operation Maintenance Requests (OMR’s), Query Requests (QR’s), and approved Change Requests (CR’s). Quality assurance measures are provided monthly. Problems are to be documented in Treasury’s STARTrack problem tracking system and final design and development documentation to be updated in STARBase, ODCP’s electronic library.

2.1.1.3 System and Database Administration

The contractor will support the Fiscal Service Technical Team in providing system and database administration services for development efforts. Service includes:

2.1.1.4 Application Development and Implementation

The contractor will support the Fiscal Service Technical Team in providing STAR software application development services in response to approved CR’s. The change control process is defined in the Change Control Plan and includes all infrastructure, application and configuration item changes. All design documentation is to be updated and stored in STARBase, ODCP’s electronic library, and follow the standards established for STAR. These activities are managed as special projects and implemented using the standard system development lifecycle that includes plan, design, build, test, and deploy.

2.1.1.5 Business Analysis and Testing

The contractor will support the Fiscal Service Technical Team in requirements gathering and coordinating requirements and testing activities. Services will include:

· Interacting across the team and with clients to perform technical requirements validations for new and existing development

· Creating new requirements and updating existing requirement documents

· Participating in all aspects of the software development lifecycle

· Leading and/or facilitating requirements gathering sessions

· Developing test plans and test reports

· Creating test scripts and update the test scripts each release

· Testing functionality, verify results and report findings to the team

2.1.1.6 Project Management

The Project Manager will have the authority to make any technical, hiring and dismissal decisions, or special arrangements regarding each contract year. The Project Manager shall be responsible for the overall management and coordination of each contract year and shall act as the central point-of-contact with the Government. The Project Manager shall have full authority to act for the Contractor in the performance of the required services. The Project Manager, or a designated representative, shall meet with the COR to discuss problem areas as they occur. The Project Manager or designated representative shall respond within four work hours after notification of the existence of a problem. The project manager shall be able to fluently read, write and speak the English language.

2.1.1.7 Knowledge Transfer

The contractor will team assist the Fiscal Service Technical Team to provide the services described above. As a part of the teaming effort, the contractor will transfer any knowledge gained from the work effort to the Fiscal Service Technical Team to ensure self-sufficiency within the Fiscal Service Technical Team.

2.1.1.8 Application Development and Implementation

Outcome

· The Bureau of the Fiscal Service Technical Support Team is self-sufficient in operating and maintaining STAR where contractor support was provided.

· Updated system documentation, tracking logs and electronic library reflect the current production environment where contractor support is provided.

System Enhancements, Upgrades, and Special Projects Deliverables and Acceptable Quality Levels

· STAR software analyses finalized one week prior to the Change Control meeting at which the analysis(es) is to be presented.

· STAR software upgrades Implemented according to STAR protocols and mutually agreed upon requirements and schedule. The schedule is developed collaboratively as a part of the implementation planning process.

· Change Request Analyses finalized one week prior to the Change Control meeting at which the analysis(es) is to be presented.

· Change Requests implemented according to STAR protocols and mutually agreed upon requirements and schedule. The schedule is developed collaboratively as a part of the implementation planning process. The delivered functionality meets the requirements specified in CR and supporting documentation. Design documents are updated and entered into ODCP’s design document repository.

· Special Project Support according to STAR protocols and mutually agreed upon requirements and schedule. The schedule is developed collaboratively as a part of the implementation planning process.

· Knowledge Transfer provided to the Fiscal Service Technical Team so that the team is self-sufficient in operating and maintaining STAR where contractor provided support.

Performance Measures

· The Fiscal Service Technical Support Team follows a strict configuration management methodology. The contractor is expected to follow the same methodology.

· Pre-determined standards are not used for approved change requests, query requests, patches and fixes, and special projects. Instead unique schedules, milestones and standards are developed for each.

Monitoring Method

· Government review of deliverable quality and timeliness.

· Independent review of adherence to configuration management requirements.

2.2 Special Projects

2.2.1 Records Management

Outcome

The record management support repository shall be in compliance with the ODCP File Plan.

· The Records repository is in accordance with OCIO, PTR, and ODCP requirements.

· Records repository remains a maintainable, upgradeable and operable system.

· Updated system documentation and electronic library reflect the ODCP File Plan.

· Records management administrative requirements (e.g. file plans, records schedules, etc.) are updated to reflect current OCIO, PTR, and NARA guidance.

· Support staff in incorporating records management processes in their daily work.

Records Administration Acceptable Quality Levels

· The Records repository is in compliance with the ODCP Records Management Governance Plan.

· The Records repository is updated based on the ODCP Records repository process and procedures documentation.

· The Records repository process and procedures documents are updated based on any new or revised PTR, NARA, and OCIO guidance.

· Records management administrative requirements (e.g. file plans, records schedules, training materials, etc.) are updated within 180 days after receipt of new guidance.

Outcome

The ODCP SharePoint site:

· is maintained in accordance with the ODCP SharePoint Administrator’s Guide and Governance Team;

· updated based on OCIO’s current implementation of Microsoft SharePoint.

SharePoint Acceptable Quality Levels

To Be Provided

2.2.2 SharePoint Support

3.0 TRAVEL

All travel shall be in accordance with the Federal Travel Regulations (for travel in 48 contiguous states) the Joint Travel Regulations, DOD Civilian personnel, Volume 2, Appendix A (for travel to Alaska, Hawaii, Puerto Rico, and U.S. territories and possessions), and if required by the Performance Work Statement, the Standardized Regulations (Government Civilians, Foreign Areas) Section 925, “Maximum Travel Per Diem Allowances for Foreign Areas” (for travel not covered in the Federal Travel Regulations or Joint Travel Regulations).

It is anticipated that the contracting staff will be located within the Office of DC Pensions, in Washington, DC and will support the Fiscal Service Technical Support Team in Parkersburg, West Virginia. All local travel will be in Washington, DC. Non-local travel may be required to the Parkersburg, W.V. location.

Contractors shall provide original or copies of all receipts for travel to include airline tickets or other commercial means of transportation, lodging, meals, gas, mileage, etc. Receipts must be received and approved by the Government prior to payment of invoices for travel.

4.0 REPORTS

A Monthly Status Report according to Work Breakdown Structure will be due by the 5th business day of the month for the previous month, including a monthly invoice referencing labor categories, hours worked by sub-task of the Work Breakdown Structure, period work was performed, and rate will be due by the 5th business day of the month for the previous month.

5.0 PERIOD OF PERFORMANCE

The period of performance for this requirement will be for one base year and four option years as follows:

· One Base Year: Date of Award, 2023 through Twelve Months, 2024

· Option Year I: Date of Award through Twelve Months, 2025

· Option Year II: Date of Award through Twelve Months,2026

· Option Year III: Date of Award through Twelve Months, 2027

· Option Year IV: Date of Award through Twelve Months, 2028

6.0 GOVERNMENT FURNISHED PROPERTY

Government Furnished Property (Material, Equipment, and Information) is to be provided in conjunction with required performance under this Statement of Work. Disposition at the end of the task shall be in accordance with FAR clause 52.245-1.

All work will be performed on-site, unless specifically designated within each order.

6.1 Government Furnished Equipment

Upon commencement of the task, unless otherwise indicated, the Government will provide one copy each of the following equipment products to the Contractor.

· COTS licensing of any existing Treasury software licenses as applicable.

· Required technical communications interface and access support as required.

· Computer workstations for on-site labor.

· Telephones.

At the request of the Government, the Contractor shall immediately return any Government provided equipment, specialized or offtheshelf software, and all other materials that were provided by the Government for the Contractor to use to complete assigned work.

6.2 Government Furnished Information

Upon commencement of the task, unless otherwise indicated, the Government will provide one copy of any documents that have been provided to Treasury by the District Government up to this point in time that are determined to be relevant to the work to be performed.

As determined by mutual agreement, the Government will provide additional information that may be required in the performance of the tasks.

At the request of the Government, the Contractor shall immediately return any Government provided equipment, specialized or off-the-shelf software, and other materials that were provided by the Government for the Contractor to use to complete the assigned tasks.

7.0 PLACE OF PERFORMANCE AND ACCESS TO GOVERNMENT PROPERTY AND FACILITIES

The primary work site for the Contractor shall be the Government’s location at:

· 1722 I St, NW, Washington, DC

The Contractor will also be allowed limited access to the other Government or District facilities as specified below:

· 900 7th Street, NW, Washington, DC

· Bureau of the Fiscal Service, Parkersburg, West Virginia

8.0 APPLICABLE CLAUSES

The Ordering CO may include additional contract clauses in BPA Orders , other than those enumerated in this section, such as (1) additional “required when applicable” FAR clauses, (2) activity or Component clauses, (3) unmentioned FAR alternate clauses, and (4) Order specifically tailored clauses.

8.1 FAR CLAUSES INCORPORATED BY REFERENCE (FAR 52.252-2) (FEB

1998)

This BPA incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the CO will make their full text available. Also, the full text of a clause may be accessed electronically at www.acquisition.gov .

(End of clause)

The following FAR clauses are incorporated by reference into the BPA :

FAR Clause No. Title and Date

8.2 FAR Clauses Incorporated in Full Text

The following FAR clauses are incorporated in full text:

8.2.1 52.217-8 Option to Extend Services (Nov 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed 6 months. The Contracting Officer may exercise the option by written notice to the Contractor within 30 days.

(End of Clause)

8.2.2 52.217-9 -- Option to Extend the Term of the Contract (Mar 2000)

(a) The Government may extend the term of this contract by written notice to the Contractor within 1 day; provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least 60 days. The preliminary notice does not commit the Government to an extension.

(b) If the Government exercises this option, the extended contract shall be considered to include this option clause.

(c) The total duration of this contract, including the exercise of any options under this clause, shall not exceed 60 months.

(End of Clause)

9.0 IRS CLAUSES (TO BE ADDRESSED BY CO)

9.1 DTAP Clause 1052.224-1 – Contract Publication (APRIL 2013)

9.1.1 1052.201-70 Contracting Officer's Representative (COR) appointment and authority.

As prescribed in 1001.670-6, insert the following clause:

CONTRACTING OFFICER'S REPRESENTATIVE (COR) APPOINTMENT AND AUTHORITY (APR 2015)

(a) The COR is ____ [insert name, address and telephone number].

(b) Performance of work under this contract is subject to the technical direction of the COR identified above, or a representative designated in writing. The term “technical direction” includes, without limitation, direction to the contractor that directs or redirects the labor effort, shifts the work between work areas or locations, and/or fills in details and otherwise serves to ensure that tasks outlined in the work statement are accomplished satisfactorily.

(c) Technical direction must be within the scope of the contract specification(s)/work statement. The COR does not have authority to issue technical direction that:

(1) Constitutes a change of assignment or additional work outside the contract specification(s)/work statement;

(2) Constitutes a change as defined in the clause entitled “Changes”;

(3) In any manner causes an increase or decrease in the contract price, or the time required for contract performance;

(4) Changes any of the terms, conditions, or specification(s)/work statement of the contract;

(5) Interferes with the contractor's right to perform under the terms and conditions of the contract; or

(6) Directs, supervises or otherwise controls the actions of the Contractor's employees.

(d) Technical direction may be oral or in writing. The COR must confirm oral direction in writing within five workdays, with a copy to the Contracting Officer.

(e) The Contractor shall proceed promptly with performance resulting from the technical direction issued by the COR. If, in the opinion of the Contractor, any direction of the COR or the designated representative falls within the limitations of (c) above, the Contractor shall immediately notify the Contracting Officer no later than the beginning of the next Government work day.

(f) Failure of the Contractor and the Contracting Officer to agree that technical direction is within the scope of the contract shall be subject to the terms of the clause entitled “Disputes.”

(End of clause)

9.1 Designation of Government Contracting Officers Representative (COR)

a. The individuals named below is hereby designated as the Government Contracting Officer’s Representative (COR). If an alternate COR is also listed below, that person will serve in the COR’s stead when the primary COR is unavailable.

The COR is responsible for the technical administration of this contract, in accordance with the provisions of the clause included herein entitled, "Technical Direction."

Primary:

Shalamar Barnes - Department of the Treasury Office of DC Pensions 1500 Pennsylvania Avenue, NW Washington, DC 20220

Alternate:

David Roth - Department of the Treasury Office of DC Pensions 1500 Pennsylvania Avenue, NW Washington, DC 20220

b. The COR, or his/her authorized representative, shall be responsible for coordinating with the Contractor the technical aspects of the contract. The COR is not authorized to make any changes that affect the contract amount, terms or conditions. The COR is the only person with the authority to act as agent of the Government under this contract. Only the Contracting Officer has authority to: (1) direct or negotiate any changes in the Statement of Work; (2) modify or extend the period of performance; (3) change the delivery schedule; (4) authorize reimbursement to the Contractor any costs incurred during the performance of this contract; or (5) otherwise change any terms and conditions of this contract.

9.2 Technical Direction

Performance of the work under this contract shall be subject to the technical direction of the Contracting Officer’s Technical Representative. The term "technical direction" is defined to include, without limitation, the following:

a. Directions to the Contractor which redirect the contract effort, shift work emphasis between work areas or tasks, require the pursuit of certain lines of inquiry, fill in details or otherwise serve to accomplish contractual statements of work.

b. Provision of information to the Contractor which assists in the interpretation of drawings, specifications or technical portions of the work description.

c. Review and, where required by contract, approval of technical reports, drawings, specifications or technical information to be delivered by the Contractor to the Government under the contract.

Technical direction must be within the general scope of work stated in the contract. The COR does not have the authority to, and may not, issue any technical direction which: (1) constitutes the assignment of any additional work outside the general scope of the contract; (2) in any manner causes an increase or decrease in the total contract cost, or time required for the contract performance or (3) changes any of the expressed terms, conditions or specifications of the contract. All technical directions shall be issued in writing by the COR or shall be confirmed by him/her in writing within 5 working days after issuance unless otherwise specified herein.

The Contractor shall proceed promptly with the performance of technical directions duly issued by the COR in the manner prescribed by this article and within his/her authority under the provisions of this article.

If, in the opinion of the Contractor, any instruction or direction issued by the COR is within one of the categories as defined in (1) through (3) above, the Contractor shall not proceed, but shall notify the Contracting Officer, in writing, within 5 working days after receipt of any such instruction or direction and shall request the Contracting Officer to modify the contract accordingly. Upon receiving such notification from the Contractor, the Contracting Officer shall issue an appropriate contract modification or advise the Contractor, in writing, that, in his/her opinion, the technical direction is within the scope of this article and does not constitute a change. The Contractor shall thereupon proceed immediately with the direction given. A failure of the parties to agree upon the nature of the instruction or direction, or upon the contract action to be taken with respect thereto, shall be subject to the provisions of the contract clause entitled Contract Terms and Conditions--Commercial Items, FAR 52.212-4(d).

9.3 Security Requirements (SEP 2002)

The information processed by STAR is considered to be sensitive, but unclassified data; containing personal information about individuals. As such, the Contractor is required to treat all data with confidentiality. Contract employees will be required to sign a non-disclosure agreement that outlines their responsibilities to protect the data and comply with the STAR Security Plan.

The Contractor shall ensure that all applicable personnel working on this BPA, including subcontractors, meet the following security requirements for contractors to protect against unauthorized disclosure of Sensitive But Unclassified (SBU) data. SBU data includes, but is not limited to, information that is protected from disclosure by the Privacy Act, 5 U.S.C. § 552a.

1) All applicable personnel shall be United States citizens or have lawful permanent resident status.

2) All applicable personnel shall be subject to a National Agency Check, Law and Credit (NACLC) investigation in accordance with the Department of the Treasury Security Manual (TD P 71-10). Applicable personnel shall not begin working on this BPA until all security forms have been properly completed and submitted to the Contracting Officer’s Technical Representative for processing, as follows:

a) Completed fingerprint cards

b) Non-disclosure Agreement

c) Fair Credit Reporting Act Release

d) SF 85-P, “Questionnaire for Public Trust Positions”

3) The Contractor shall ensure that all documentation relative to the System to Administer Retirements (STAR) be developed, processed, accessed, safeguarded, transmitted, and destroyed in accordance with TD P 71-10.

4) Applicable personnel shall wear Treasury issued identification badges when working in Government facilities.

5) Applicable personnel are prohibited from removing Treasury information and/or data from STAR.

6) Applicable personnel who undergo NACLC investigations that reveal, but are not limited to, the following, may be unacceptable under this contract: conviction of a felony, a crime of violence or a serious misdemeanor; a record of arrests for continuing offenses; or failure to file or pay Federal income tax. The Government reserves the right to determine if a Contractor employee assigned to a task shall continue with the task. The Contractor shall agree to remove the person assigned within one day of official notification by the Government and provide a replacement within five days. New hires or substitutions of personnel are subject to the NACLC investigation requirement.

All information collected under this contract shall be considered procurement sensitive. Contractor staff must be a United States citizen or possess alien status in the United States and be able to pass a Government background investigation, if required, by the Department of the Treasury.

During the period of this task, access to Department of the Treasury facilities for Contractor representatives shall be granted as deemed necessary by the Government. All contractor employees whose duties under this contract require their presence at any Treasury, or Treasury Bureau facility shall be clearly identifiable by a distinctive badge furnished by the Government. In addition, corporate identification badges shall be worn on the outer garment at all times. It is the sole responsibility of the Contractor to provide this corporate identification. Upon the termination of the employment of any contractor personnel working on this task, all government furnished identification shall be returned to the issuing office. All on-site contractor personnel shall abide by security regulations applicable to that site.

The contractor may be requested to sign a non-disclosure agreement regarding all deliverables and other pertinent information relative to this requirement. All information provided by the government shall be returned to the government at the conclusion of this contract. In addition the contractor must have provided the personnel associated with this contract, all security awareness training and all other requirements contained in the FISMA regulations, NIST guidelines and all other public law which shall include those requirements of the Federal Acquisition Regulations (FAR). Classified information will NOT be made available to the contractor.

9.3.1 Personnel Identity Verification of Contractor Personnel (October 2005)

(a) The Contractor shall comply with Treasury and Bureau personal identity verification procedures that implement HSPD-12, OMB guidance memorandum M-05-24 and FIPS Pub 201.

(b) The Contractor shall insert this provision in all subcontracts when the subcontractor is required to have physical access to a Federally controlled facility or access to a Federal information system.

Contractors shall also comply with the attached (Attachment 1) Contractor Responsibilities Following Granting of Access or Issuance of Identification Media (PIV Card).

9.4 Confidentiality

1. Nondisclosure of Confidential Information

a. Nondisclosure. Neither the contractor nor any of its employees will disclose any information specifically identified as confidential at or prior to disclosure to contractor by Treasury (the “Information”) for any purpose other than in furtherance of the consulting services to be rendered by the contractor to Treasury. All retirement, personnel, and payroll records or information pertaining to specific individuals in the custody of either Treasury or the Government of the District of Columbia to which the contractor has access shall be treated as confidential Information. The contractor will take all steps reasonable and necessary so that the confidentiality of the Information in the contractor’s possession will be maintained by it.

b. Return of documents. Upon termination of the contractor’s engagement, all documents and records in the contractor’s possession containing the Information will be returned to Treasury.

2. Application

Notwithstanding anything to the contrary herein, this Provision shall not apply to any Information:

a. which at the time disclosed to, or obtained by, the contractor is in the public domain;

b. which becomes part of the public domain through no fault of the contractor;

c. which was communicated to the contractor by a third party who is not, to the contractor’s knowledge, subject to any confidentiality obligations with respect thereto;

d. which is required to be disclosed by law, including, without limitation, pursuant to the terms of a subpoena or other similar process or in connection with a litigation, arbitration or other proceeding; provided, however, that the contractor shall, prior to disclosing such Information, give prior timely notice of such required disclosure to the Treasury and the government of the District of Columbia to enable them to challenge any such legal process; or

e. which was independently developed by the contractor.

3. The contractor shall ensure that this provision is incorporated in all subcontracts, task orders and similar agreements entered into or issued in support of this Agreement.

9.5 (Treasury Dept.) Required Central Contract Registration – Existing Contracts (JAN 2002)

The United States Department of the Treasury has adopted the Department of Defense’s Central Contractor Registration database as its database for contractor information. (This clause does not apply to the Treasury Bureau known as the Comptroller of the Currency.) Accordingly, the following requirements apply to this contract.

(a) Definitions. As used in this clause -

(1) “Central Contractor Registration (CCR) database” means the primary Department of Defense (DoD) repository for contractor information required for the conduct of business with DoD.

(2) “Data Universal Number System (DUNS) number” means the 9-digit number assigned by Dun and Bradstreet Information Services to identify unique business entities.

(3) “Data Universal Numbering System+4 (DUNS+4) number” means the DUNS number assigned by Dun and Bradstreet plus a 4-digit suffix that may be assigned by a parent (controlling) business concern. This 4-digit suffix may be assigned at the discretion of the parent business concern for such purposes as identifying sub-units or affiliates of the parent business concern.

(4) “Registered in the CCR database” means that all mandatory information, including DUNS number or the DUNS+4, if applicable, is in the CCR database; the DUNS number has been validated; and all edits have been successfully completed.

(b) (1) The contractor agrees to register in the CCR database within 15 calendar days of the date of this modification (see Block 16c, Date Signed, on the SF30).

(2) During performance and through final payment of the contract, the contractor further agrees that (a) it will remain registered in the CCR database and (b) it will maintain its vendor record in the CCR with current, complete and accurate data.

(3) The contractor agrees that, after registering in the CCR database, it shall provide notification of its registration to the Contracting Officer along with its DUNS number or, if applicable, its DUNS +4 number. The contractor shall provide this confirmation within the 15 calendar day registration period specified in paragraph (b)(1) above.

(4) Lack of registration in the CCR database will make the contractor ineligible to receive payments under the contract and may make the contractor ineligible for contract renewal.

(5) DoD established a goal of registering an applicant in the CCR database within 48 hours after receipt of a complete and accurate application via the Internet. However, registration of an applicant submitting an application through a method other than the Internet may take up to 30 days. Therefore, the contractor should consider applying for registration immediately.

(c) The Contractor is responsible for the accuracy and completeness of the data within CCR, and for any liability resulting from the Government’s reliance on inaccurate or incomplete data. To remain registered in the CCR database after the initial registration, the Contractor is required to confirm on an annual basis that its information in the CCR database is accurate and complete.

(d) Following the Contractor’s initial registration in CCR and receipt of any Treasury Department (excluding the Comptroller of the Currency) award of a contract, purchase order, delivery order, task order, basic agreement, basic ordering agreement, or blanket purchase agreement, the Contractor must directly notify the Contracting Officer of any of its changed mandatory business data in CCR within three business days of the change. (See the CCR Handbook at www.ccr.gov for the current mandatory registration data fields, or contact the CCR Assistance Center at 888-227-2423 or 616-961-4725.)

(e) Contractors may obtain information on registration and annual confirmation requirements via the Internet at http://www.ccr.gov, from the Defense Electronic Business Program Office (Defense e-Business) at contact.ccr@us.pwcglobal.com, from the CCR Assistance Center at 888-227-2423 or 616-961-4725, from the Defense Logistic Information Service at dlis support@dlis.dla.mil.

(f ) Contractors such as some consultants and sole proprietorships that are small firms that would otherwise have no use for a Dun & Bradstreet (D&B) number, may use an alternative D&B registration method. If needing a D&B number principally for CCR registration, such a Contractor should call D&B toll-free at 800/333-0505, and clearly state that it is a very small business and simply needs a DUNS number for the purpose of CCR registration.

ATTACHMENT #1

CONTRACTOR RESPONSIBILITIES FOLLOWING GRANTING OF ACCESS OR ISSUANCE OF IDENTIFICATION MEDIA (PIV CARD)

The Contractor and each of its subcontractors shall comply with the following requirements once a Contractor or subcontractor employee has been granted physical access to a Federally controlled facility and/or has been issued a personal identification verification (PIV) card.

1. When Contractor or subcontractor realizes physical access to a Federally controlled facility or access to a Federal system is no longer required.

The Contractor and its subcontractors shall immediately notify the Contracting Officer (CO) and the Contracting Officer’s Technical Representative (COR) whenever an employee of the Contractor or subcontractor, having been provided physical access to a Federally controlled facility or access to a Federal system is no longer in need of such access, regardless of whether the changed circumstance is temporary or permanent. Notification is required even if the Contractor or subcontractor intends to return that employee to a position requiring access at some future time. Immediate shall mean not more than twelve (12) hours from when first realizing access is no longer required.

2. When Contractor or subcontractor employee’s PIV card is lost, stolen or not accounted for; or employee misuses access or PIV card; or employee commits criminal act in connection with the access or PIV card.

The Contractor or subcontractor shall also comply with the above notification requirement whenever: (a) a PIV card issued to one of its employees is lost, stolen or otherwise not accounted for; or whenever the Contractor or subcontractor reasonably believes one of its employees, having been authorized access to a Federal facility or Federal system, and/or issued a PIV card, has misused the authorized access or the PIV card, or committed a criminal act in the use of said access or PIV card.

3. When the Contractor is required to return an employee’s PIV card

The Contractor and its subcontractor shall be responsible for all PIV cards issued to its employees and the immediate return of a PIV card to the CO or the COR whenever the need for the card ceases to exist, whether the changed circumstance is temporary or permanent. The Contractor or subcontractor shall immediately notify the CO or COR whenever a circumstance arises requiring the return of a PIV card. Return of the PIV card is required even if the Contractor or subcontractor intends to return that employee to a position requiring access at some future time. The return of a PIV card must be completed within three (3) work days following notification to the CO or COR, including the day on which it was determined that the PIV card was no longer required, by delivering it to the COR.

The Contractor or subcontractor shall return the PIV card issued to any of its employees who are reasonably believed to have engaged in misuse of the card or engage in some criminal conduct involving to the use of the card.

4. Quarterly reports by Contractor to PIV card Manager

The Contractor and its subcontractors shall maintain a record of all of its employees having been issued PIV cards, to include the full name of the employee and the number assigned to the card. The Contractor shall deliver to the COR a copy of that record at the end of every third month following contract award or commencement of the Homeland Security Presidential Directive (HSPD)-12 PIV contract requirements. A copy of that report shall also be delivered to the COR, ATTACHMENT #2

Sample WBS

Section 508 Compliance

IR1052.239-9008 Section 508 Information, Documentation and Support

(SEP 2006)

In accordance with 36 CFR 1194, Subpart D, the electronic information technology (EIT) products and product support services furnished in performance of this contract shall be documented to indicate the current conformance level with Section 508 of the Rehabilitation Act of 1973, per the 1998 Amendments, and the Architectural and Transportation Barriers Compliance Board’s Electronic and Information Technology Accessibility Standards. At no time during the performance of the award shall the level of conformance go below the level of conformance in place at the time of award. At no additional cost, the contractor shall provide information, documentation, and support relative to the supplies and services as described in Section J, Attachment [Fill in]. The contractor shall maintain this detailed listing of compliant products for the full contract term, including forms of extensions, and shall ensure that it is current within five calendar days after award and within three calendar days of changes in products being utilized as follows:

(a) Product support documentation provided to end-users shall be made available in alternate formats upon request, at no additional charge.

(b) End-users shall have access to a description of the accessibility and compatibility features of products in alternate formats or alternate methods upon request, at no additional charge.

(c) Support services for products shall accommodate the communication needs of end-users with disabilities.

IR1052.239.9010 Section 508 Services (SEP 2006)

All contracts, solicitations, purchase orders, delivery orders and interagency agreements that contain a requirement of services which will result in the delivery of a new or updated electronic and information technology (EIT) item/product must conform to the applicable provisions of the appropriate technical standards in 36 CFR 1194, Subpart B, and functional performance criteria in 36 CFR 1194.31, Subpart C, unless an agency exception to this requirement exists.

The following technical standards and provisions have been determined to be applicable to this contract:

_X__ 1194.21, Software applications and operating systems.

_x_(a) _x_(b) _x_(c) _x_(d) _x_(e) _x_(f) _x_(g) _x_(h) _x_(i) _x_(j) _x_(k) _x_(l)

_X__ 1194.22, Web-based intranet and internet information and applications.

_x_(a) _x_(b) _x_(c) _x_(d) _x_(e) _x_(f) _x_(g) _x_(h) _x_(i) _x_(j) _x_(k) _x_(l) _x_(m) _x_(n) _x_(o) _x_(p)

___ 1194.23, Telecommunications products.

__(a) __(b) __(c) __(d) __(e) __(f) __(g) __(h) __(i) __(j) __(k) - __(k:1) __(k:2) __(k:3) __(k:4)

___ 1194.24, Video and multimedia products.

__(a) __(b) _x_(c) x__(d) x__(e)

___ 1194.25, Self contained, closed products.

__(a) __(b) __(c) __(d) __(e) __(f) __(g) __(h) __(i) __(j)

___ 194.26,…