Automated Data Monitoring and Reporting_DRAFT PWS.docx

FPDS Monitoring, Reporting and Validation Services

United States Department of Treasury Treasury Common Services Center

Table of Contents

1.0 Background

The Treasury Common Services Center (TCSC) provides shared acquisition and operational support services across the Department of the Treasury. As part of this mission, TCSC Acquisition Services supports Treasury-wide procurement reporting, analytics, data quality, and acquisition oversight activities.

The Federal Procurement Data System (FPDS) is the Federal Government’s authoritative repository for contract action data and serves as a primary source for acquisition reporting, management oversight, strategic decision-making, and public transparency. Treasury acquisition data reported to FPDS is used by Treasury leadership, the Office of Management and Budget (OMB), the Office of Federal Procurement Policy (OFPP), oversight organizations, and the public.

TCSC requires a secure, web-based platform and associated support services to monitor, validate, analyze, and report on Treasury procurement data. The platform shall support procurement data quality, spend analysis, compliance monitoring, reporting automation, and acquisition performance measurement across Treasury organizations.

The objective of this requirement is to improve the quality, accuracy, accessibility, and usability of Treasury procurement data while supporting acquisition management, reporting, audit readiness, category management, and strategic decision-making activities.

2.0 Performance Requirements

2.1 FPDS Data Monitoring, Reporting and Validation System Based on the Federal Acquisition Regulations The Contractor shall provide, operate, and maintain a secure web-based platform and associated support services that enable Treasury-wide procurement data validation, reporting, oversight, and analytics.

The platform shall support Federal Procurement Data System (FPDS) reporting and data quality requirements and remain aligned with applicable Federal acquisition regulations, policies, reporting guidance, and government-wide procurement data standards. This includes applicable FAR requirements, class deviations, OFPP guidance, OMB reporting requirements, DATA Act requirements, and other acquisition reporting requirements that become effective during contract performance.

At a minimum, the platform shall provide:

· A Treasury-customized website supporting up to 750 users, with secure account management, role-based access controls, configurable dashboards, and customizable reporting views.

· Automated data validations targeting all FPDS Contract Action Report (CAR) elements, primarily driven by FAR-based logic, the FPDS Data Dictionary, and Treasury-specific validation rules, with results visualized through customizable dashboards and reports.

· Automated and individualized notifications to data submitters and designated oversight personnel for each detected anomaly, discrepancy, potential error, or data inconsistency identified through validation activities.

· Summary alerts, exception reporting, and workflows tailored to Treasury oversight personnel, enabling collaborative resolution, tracking, and monitoring of data quality issues.

· On-demand reporting of procurement data quality metrics, including error rates, accuracy rates, and trend analyses at the Department, Bureau, and office levels.

· Quarterly and annual Verification & Validation (V&V) reviews and reports in support of Office of Federal Procurement Policy (OFPP) requirements for Improving Federal Procurement Data Quality.

· Automated generation of quarterly randomized contract action samples in accordance with applicable OFPP and OMB Verification & Validation (V&V) guidance, including organizational breakdowns by Department, funding bureau, and contracting bureau.

· Automated tracking and reporting of V&V review completion status, including visibility into reviewer progress, outstanding reviews, and bureau-level completion rates.

· Reporting by individual V&V data elements and associated validation categories to support Treasury oversight, compliance monitoring, and annual reporting requirements.

· Automated reporting and dashboards identifying the status of contract actions, including actions in draft, pending review, incomplete, or other user-defined statuses, to support oversight and completion of Treasury procurement reporting requirements.

· User-configurable dashboards and reporting views supporting daily, monthly, quarterly, annual, and year-to-date reporting periods.

· Maintenance and uptime monitoring of the platform, dashboards, and supporting infrastructure as part of core service delivery.

· Technical support services available via phone and email during standard Government business hours.

· Interactive user training (live and virtual) sessions offered at least quarterly or as requested by TCSC, including user guidance, onboarding support, and platform functionality training for Treasury personnel.

2.2 Spend Data Categorization and Analysis

The Contractor shall analyze Treasury procurement FPDS data using standardized classification techniques and provide reports breaking down spend by commodities and services. At a minimum, the analysis shall include:

· Procurement Instrument Identifier (PIID) and Reference PIID

· Contracting and Funding Organizations

· Description of Requirement

· Commodity/Service Designation

· NAICS and PSC Codes

· Category Management alignment:

· https://acquisitiongateway.gov/category-management

· Current and Total Period of Performance (Base + Options)

· Obligated Amount

· Total Dollar Value (Base + Options)

· Total Contract Value

Spend data analysis must be structured for trend analysis across time periods and support strategic sourcing, category management, and Treasury’s small business outreach objectives.

2.3 Algorithmic Reporting and Metrics Automation

The Contractor shall provide, maintain, and enhance automated reporting capabilities that support Treasury procurement oversight, reporting, and decision-making activities. The Contractor is encouraged to incorporate automated analytical methods, configurable business rules, business intelligence tools, predictive analytics, anomaly detection techniques, machine learning-assisted capabilities, or similar technologies, where appropriate, to enhance reporting, monitoring, and analytical capabilities. All reporting methodologies, business rules, formulas, assumptions, exclusions, and calculation logic used to generate metrics shall be documented and made available to the Government upon request.

The Contractor shall obtain Government approval prior to implementing any material changes to reporting methodologies, business rules, analytical models, automated decision-support functionality, or other capabilities that may affect reported results, performance metrics, or data interpretations. The Contractor shall ensure that all automated reporting, analytical, and monitoring capabilities operate in a manner that supports transparency, traceability, and validation of reported results. Upon request, the Contractor shall provide sufficient documentation to enable Government review and understanding of the methodologies used.

Reports and reporting capabilities shall:

· Be automatically generated on a monthly basis and available on demand for authorized Treasury users.

· Support up to six (6) ad hoc or custom reports per month at the request of TCSC Acquisition Services.

· Provide configurable filtering, sorting, drill-down, export, and visualization capabilities to support self-service reporting and analysis by Treasury personnel.

· Be delivered in accordance with the timelines identified in Section 4.0, Deliverables.

· Include documentation describing formulas, methodologies, assumptions, exclusions, business rules, and calculation logic used to generate metrics, particularly for high-risk or compliance-sensitive reporting elements.

Examples of Reporting Capabilities:

· Contract Transfer Reports: Identify and track contracts transferred to other agencies.

· Expiring Contracts Reports: Identify, track, and automate notifications of expiring contracts and options.

· Forecasting Reports: Identify and track upcoming recompete actions.

· Active Contracts Reports: Identify, track, and summarize ongoing contracts by department, agency, office, and individual.

The Contractor shall provide training and training tools or library to TCSC Acquisition Services personnel on reporting functionality, methodologies, metrics, and analytical capabilities. Virtual, instructor-led training shall be provided quarterly or upon request.

The Contractor shall implement appropriate controls to protect Government-provided information and shall use such information solely for purposes directly related to performance of work under this contract. Government data shall not be used for purposes unrelated to contract performance.

2.4 Metrics Monitoring Requirements

The platform shall support automated monitoring, reporting, and visualization of the following performance areas:

A. FPDS Data Check / Accuracy Monitoring

· Perform daily automated reviews of newly submitted FPDS Contract Action Reports (CARs) to identify potential data anomalies or compliance issues.

· Use logic primarily based on the FAR, Treasury-specific policies, and FPDS Data Dictionary rules.

· Provide automated email alerts to data submitters and supervisory personnel when errors or inconsistencies are detected.

· Track and report the percentage of CARs with flagged issues, with accuracy/error rate trends available at the Department, Bureau, and office levels.

· Include the ability to separately monitor and report on key DATA Act-specific elements.

B. Verification & Validation (V&V) Process Automation

· Generate quarterly randomized samples of contract actions in accordance with OFPP and OMB verification and validation guidance that is accessible within ten (10) calendar days of the end of each fiscal quarter.

· Track completion status of the V&V process, with visibility into reviewer progress and bureau-level completion rates.

· Provide reporting by OFPP-defined data elements, and by organizational breakdowns (Department, Bureau, office).

· Include dashboards and/or reports showing the status of actions (i.e. number of unreviewed, draft, or pending actions) to assist with annual closeout and compliance tracking for each bureau to be available within fifteen (15) days after the end of the fiscal year.

· Include tools to coordinate and assist with annual V&V Reporting:

· https://trumpwhitehouse.archives.gov/sites/whitehouse.gov/files/omb/procurement/memo/improving-data-quality-guidance-for-annual-verification-and-validation-may-2011.pdf C. ProcureSTAT Scorecard Reporting

The Contractor shall provide automated, filterable reports to support Treasury’s ProcureSTAT and internal procurement performance tracking. Reports must be configurable by time period (daily, monthly, quarterly, YTD) and organizational unit (Department, funding Bureau, and contracting Bureau). At a minimum, reporting shall include:

· Procurement Activity Metrics: Dollars obligated, number of actions, and unique vendors awarded.

· YTD Progress: Obligations compared to prior fiscal year totals and net change versus the same period last year.

· High-Risk Indicators:

· Competition Rate: Obligated dollars for competed actions ÷ total obligations.

· One-Bid Rate: Competed dollars with one bid ÷ total competed dollars (per OMB revised methodology).

· Contract Type Breakdown: Totals for Cost-type, T&M, and Labor-hour awards.

· Acquisition Planning Metrics:

· Expiring Contracts: With filters for contract type, award type, and dollar range.

· Procurement Acquisition Lead Time (PALT) Reporting: Average days from solicitation to award, excluding anomalies, filterable by Bureau and award attributes.

The platform shall support drill-down capabilities, trend analysis, and exportable reporting formats suitable for Treasury and OMB performance reviews.

D. Small Business Goal Tracking

· Socioeconomic achievement tracking by a customizable time period, bureau, and office.

· Obligated dollar range breakouts (i.e. <$10k, $10k - $250k, $250k - $1M, $1M - $5M, etc.) for small business set-asides.

E. Sustainability and Category Management Compliance

· Track compliance with government-wide sustainability mandates by reporting on:

· The percentage of new applicable contract actions that include sustainable product/service requirements.

· Use of bio-based products per applicable FAR requirements.

· Include summary views for OFPP and category management reporting needs.

F. Additional Capabilities for Procurement Performance

· The Contractor may propose additional monitoring or reporting capabilities that leverage automation, AI/ML, or Robotic Process Automation (RPA) to improve data quality or oversight efficiency.

· These may include anomaly detection, predictive analytics, or custom modules for Treasury-specific reporting not covered above.

3.0 Technical Requirements

As part of the solution, the following technical and operational constraints apply throughout the performance period:

· The Contractor shall provide responsive technical support to users Monday through Friday, from 8:30 AM to 4:30 PM ET, excluding federal holidays.

· The Contractor shall manage user onboarding, including account creation and login assistance, and support role-based access.

· The solution must rely solely on publicly available FPDS data. No direct integration with Treasury’s contract writing systems is permitted.

· The Contractor shall not be granted routine physical access to any federally controlled facilities and will not require access to systems containing sensitive or classified data.

· The Contractor shall not access or handle any taxpayer information or tax return data.

· The only Government-furnished information (GFI) to be provided will be FPDS user email addresses, their supervisors’ names, and contact information. The Contractor and Treasury shall jointly maintain updated user contact lists to ensure continued email alert accuracy.

· For purchases under the micro-purchase threshold, the Contractor may receive limited supplemental data (not otherwise available via FPDS) on a monthly basis, solely for the purposes of spend analysis and ProcureSTAT reporting.

4.0 Deliverables

The Contractor shall provide the deliverables identified in this section in electronic formats that are accessible, editable, and suitable for Government use. Deliverable formats shall be mutually agreed upon by the Government and Contractor after award, unless otherwise specified by the Contracting Officer (CO).

The Contractor shall provide all reports, analyses, dashboards, notifications, and other required outputs in accordance with the performance requirements and delivery timelines established in this section.

4.1 Deliverables Schedule

The Contractor shall notify the CO and COR as soon as it becomes apparent to the Contractor that a scheduled deliverable will be late. The Contractor shall include in the notification the rationale for the late delivery, the expected date for the delivery and the project impact of the late delivery. The COR will review the new schedule. The Government will reflect any change(s) to task order terms and conditions via modification executed by the CO.

5.0 Inspection and Acceptance

Inspection will be at the Government’s location(s) stated herein in accordance with FAR 8.406-2 “Inspection and Acceptance”. In addition, performance standards, acceptable quality levels, method of surveillance, and resulting impact are provided as the Quality Assurance Surveillance Plan, Attachment 1.

5.1 Specific Acceptance Criteria

The specific quality measures as set forth below will be applied to each deliverable received from the contractor under this contract. Any perceived conflict with the quality measures listed below should be immediately reported to the Contracting Officer.

· Accuracy: Content shall be technically correct, reflect current regulatory frameworks (including FAR updates), and use appropriate terminology.

· Clarity: Deliverables must be well-organized, logically structured, and easily understood by acquisition professionals.

· Specification Validity: All deliverables must meet the functional and performance expectations defined in the PWS and any post-award clarifications.

· Editability: All documents must be provided in an editable format (e.g., Word, Excel, PowerPoint) to allow Government updates.

· Format Compliance: Deliverables must be submitted electronically, Section 508-compliant, and compatible with current Treasury systems and software.

· Timeliness: Deliverables must be submitted in accordance with the timelines outlined in Section 4.0 unless otherwise modified by the CO.

5.2 Rejection Procedures

Deliverables that fail to meet the acceptance criteria outlined in Section 5.1 will be subject to the following rejection process:

· The COR will provide written notification of rejection within 10 business days of receipt.

· The Contractor shall correct and resubmit the deliverable within 5 business days of rejection notice, unless otherwise agreed upon.

· This review-and-revision cycle shall continue until the deliverable is accepted by the COR.

· Any schedule adjustments resulting from deliverable rework shall be addressed through a formal contract modification.

6.0 Quality Control Plan

The Contractor shall establish and maintain internal quality control procedures to ensure all services and deliverables comply with the requirements outlined in this contract. These procedures must be sufficient to monitor performance, identify and correct deficiencies, and ensure continuous improvement throughout the contract period.

While the Government does not require formal submission of a Quality Control Plan, the Contractor is expected to apply industry best practices and maintain documentation of quality control activities. Upon request, the Contractor shall make this documentation available to the Government for review.

7.0 Period of Performance

The anticipated contract period of performance is as follows:

Base Period:

8.0 Place of Performance

The anticipated work shall be performed primarily at the Contractor’s own facility. However, certain activities—such as initial system setup, onboarding, or meetings requiring direct coordination—may necessitate the Contractor’s presence at Government facilities located in Washington, DC.

Any on-site support must be coordinated in advance with the Contracting Officer’s Representative (COR) and comply with applicable security and access protocols. Virtual collaboration is encouraged for routine communications, training, and technical support, unless otherwise specified by the Government.

9. Observance of Legal Holidays/Federal Non-Work Days

9.1 The Contractor shall establish a standard holiday schedule that coincides with the Government's schedule for employees working on a Government site(s). All Government offices will be closed, except for minimum essential personnel required for in-house operations, during Federal holidays. Except as otherwise specified, the Contractor shall not schedule or conduct routine work that requires Government personnel to participate on Federal holidays. Holidays observed are listed below. Holidays and other non-work days are not billable unless work is requested by the Government and performed on these days. The Government hereby provides NOTICE and Contractor hereby acknowledges RECEIPT that Government personnel observe the below listed days as holidays. The following is a list of Government holidays:

· New Year’s Day,

· Martin Luther King’s Birthday,

· President’s Day,

· Memorial Day,

· Independence Day,

· Labor Day,

· Columbus Day,

· Veteran’s Day,

· Thanksgiving Day,

· Christmas Day, and

· Inauguration Day (every fourth year) (Washington, DC)

When such holidays fall on a Saturday, the preceding Friday will be considered the holiday. When such holidays fall on a Sunday, the succeeding Monday will be considered the holiday.

9.2 No work shall be performed by Contractor personnel on Federal holidays or other non-work days without prior written approval of the Contracting Officer Representative.

9.3 Work performed on holidays, weekends, or other non-work days shall be billed at the "normal" unit prices.

9.4 There are certain types of irregularly occurring circumstances that prompt the Government to close offices where Contractor personnel are working, either on a national or local basis (e.g., bomb threats, inclement weather, power outages, death of a national figure, or funding lapses). Contractor personnel shall not work if the Government is closed, unless otherwise authorized by a fully executed Order from the CO. Non-work due to the Government closing its facility(ies) is not an expense directly reimbursable to the Contractor.

10.0 Quality Assurance Surveillance Plan

In addition to the other provisions of this Section, the Government will evaluate performance of services in accordance with the Quality Assurance Surveillance Plan (QASP), provided as Attachment 1.

11.0 Contract Administration Office

11.1 The Contractor must use one of the following Government contacts, as applicable, as the focal point for all matters regarding this contract:

Contracting Officer (CO) is as follows:

Name: Angela C. Gallo Phone: (240) 613-0038 Email: Angela.C.Gallo@irs.gov

The Contracting Officer’s Representative (COR) is as follows:

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

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

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

11.1.

11.2.

11.3.

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

11.3.2. Constitutes a change as defined in the clause entitled “Changes”;

11.3.3. In any manner causes an increase or decrease in the contract price, or the time required for contract performance;

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

11.3.5. Interferes with the contractor's right to perform under the terms and conditions of the contract; or

11.3.6. Directs, supervises or otherwise controls the actions of the contractor's employees.

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

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

11.6 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.”

11.7 Written communications must make reference to the contract number and task order number (if applicable), and must be mailed to the above address.

11.8 The CO, in accordance with Subpart 1.6 of the FAR, is the only person authorized to make or approve any changes to any of the requirements of the contract or any task order issued there under, and notwithstanding any clauses contained elsewhere in this solicitation or contract, such authority remains solely with the CO. In the event the Contractor makes any changes at the direction of any person other than the CO, the change will be considered to have been made without authority and no adjustment will be made in the contract or task order price to cover any increase in cost incurred as a result thereof.

Notwithstanding anything to the contrary contained in the contract or any task order issued there under, the CO shall be the only individual authorized to accept nonconforming work, waive any requirement of the contract, and/or modify any term or condition of the contract or task order(s) issued there under. The CO is the only individual who can legally obligate Government funds.

No costs chargeable to any task order issued under the contract can be incurred before receipt of a fully executed task order or specific authorization from the CO.

12.0 Travel

Travel is not authorized for this requirement.

13.0 Post Award Evaluation of Contractor Performance

13.1 Contractor Performance Evaluations

The Government acquisition team shall complete evaluations of Contractor performance in accordance with FAR Subpart 42.15 and FAR 8.406-7, including both interim and final evaluations. Evaluations will be prepared using the Contractor Performance Assessment Reporting System (CPARS).

The Contractor will have at least thirty (30) calendar days to review each evaluation and submit comments or rebuttals. Interim evaluations may be prepared at the Government’s discretion during the contract period. Final evaluations will be conducted within 30 calendar days following the end of each performance period and at contract completion.

All Contractor comments will be reviewed before finalizing the evaluation. Disagreements not resolved between the Government and the Contractor will be elevated to the Director, Office of the Chief Procurement Officer (OCPO).

Performance evaluations are solely at the discretion of the Government and are not subject to appeal under the Disputes Clause (FAR 8.406-6). Final evaluations and any associated comments will be retained in the official contract file and accessible in CPARS for use in future source selections. For more information, visit: https://www.cpars.gov.

13.2 Inspection Rights and Annual Performance Monitoring

The Government reserves the right to inspect the Contractor’s and any subcontractor’s facilities and operations during normal business hours to ensure compliance with the contract and to monitor ongoing performance. Based on inspection results, the CO may direct corrective actions if deficiencies are identified.

13.3 Electronic Access to Contractor Performance Evaluations

The Contractor may access, review, and comment on performance evaluations through the CPARS portal at https://www.cpars.gov. The Contractor must designate a Primary Point of Contact (POC) and an Alternate POC during registration, both of whom shall be responsible for timely processing and acknowledgment of performance evaluations within the required 30-day timeframe.

14.0 Key Personnel

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

14.1. The Contractor assigned personnel that will perform the tasks stated in the Performance Work Statement, including the Program Manager, are designated as “Key Personnel”. Such Key Personnel are as follows:

14.2. The Contractor assigned personnel that will perform the tasks stated in the Performance Work Statement, including the Program Manager, are designated as “Key Personnel”. Such Key Personnel are as follows:

14.3. The Contractor shall use the key personnel set forth in its price for performance of the effort set forth under the contract. In the event that one or more of the personnel are not available, or become unavailable, the Contractor shall furnish substitute personnel of equal or superior relevant skills, which substitutions shall be subject to approval of the CO.

14.4. Substitution of Key Personnel –

14.4.1. The Contractor shall assign to the contract those persons whose resumes were submitted with its offer who are necessary to fill the requirements of the contract and task orders issued there under. No substitutions shall be made except in accordance with this clause.

14.4.2. The Contractor shall not allow personnel substitutions during the contract performance period unless the Contractor promptly notifies the CO, with a copy to the COR, and provides the information required by paragraph (3) below. All proposed substitutions must be submitted, in writing, at least fifteen (15) working days in advance of the proposed substitutions to the CO, and provide the information required by paragraph (3) below.

14.4.3. All requests for substitutions must provide a detailed explanation of the circumstances necessitating the proposed substitutions, a complete resume for the proposed substitute, and any other information requested by the CO needed to approve or disapprove the proposed substitution. All proposed substitutions must have relevant qualifications that are equal or superior to the qualifications of the person(s) to be replaced. The CO, or an authorized representative, will evaluate such requests and promptly notify the Contractor of approval or disapproval thereof.

14.5. During the contract performance period, any substitution or replacement of key personnel must be proposed by the Contractor and authorized by the CO in advance of such actual substitution or replacement.

15.0 Subcontractor Personnel

The Contractor shall furnish the Government with the name of all firms to be used as subcontractors for each type of work to be performed prior to performing any work under this contract in the quote submission. The Government reserves the right to accept or reject any subcontractors proposed.

16.0 Non-Payment for Additional Work

Any additional services or changes to work specified that is performed by the Contractor, either at his own volition or at the request of an individual other than a duly appointed Contracting Officer except as may be explicitly authorized in the applicable contract task order, are not authorized and will not be paid for by Treasury. Only a duly appointed Contracting Officer is authorized to change terms and conditions in this contract.

17.0 Access to Government Facilities

During the term of the task order, the rules and regulations of the entrance to and exit from the Government facility for the Contractor's personnel must be made available as required. During all operations on Government premises, the Contractor's personnel must comply with the rules and regulations governing the conduct of personnel and the operation of the facility. The Government reserves the right to require the Contractor's personnel to sign in and sign out upon entrance to and exit from the Government facility. There may be occasions where contractor personnel are required to provide support or attend meetings at a Government facility where a security background is required. When notified by the COR of support requirements at these locations, the Contractor shall provide full name (first, middle and last) as well as birth date, social security number and citizenship status to the COR at least (3) business day prior to the required support date.

18.0 Organizational Conflicts of Interest

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.

16.

17.

18.

18.1. The Contractor warrants that, to the best of the Contractor’s knowledge and belief, there are no relevant facts or circumstances, which could give rise to an organizational conflict of interest as defined in FAR Subpart 9.5, Organizational and Consultants Conflicts of Interest, or that the Contractor has disclosed all such relevant information in writing to the CO.

18.2. The Contractor is responsible for notifying the CO of any actual or potential organizational conflict of interest that arises after contract award. The Contractor agrees that if an actual or potential organizational conflict of interest is discovered after award, the Contractor shall make a full disclosure in writing to the CO no later than three business days after discovery, to include conflicts or potential conflicts that may surface at the subcontract level. This disclosure must include a description of actions which the Contractor has taken or proposes to take, after consultation with the CO, to avoid mitigate or neutralize the actual or potential conflict.

18.3. The CO may impose appropriate constraints to avoid or mitigate any actual or potential organizational conflict of interest. The CO may terminate the contract for convenience, in whole or in part, if he/she deems such terminations necessary to avoid an organizational conflict of interest. If the Contractor was aware, or should have been aware, of a potential organizational conflict of interest prior to award, or discovered an actual or potential conflict after award and did not disclose or misrepresented relevant information to the CO, the Government may terminate the contract for default, recommend suspension or debarment of the Contractor from Government contracting, or pursue such other remedies as may be permitted by law or the contract.

18.4. The Contractor further agrees that it shall include this clause in all subcontracts and in lower tier subcontracts unless a waiver is requested from, and granted by, the CO.

19.0 Procedures for Correspondence

All correspondence must be subject to the following procedures:

1.

2.

3.

4.

5.

6.

7.

8.

9.

10.

11.

12.

13.

14.

15.

16.

17.

18.

19.

19.1. Technical correspondence must be addressed to the COR with information copies to the CO; and

19.2. All other correspondence, e.g., request for waivers, deviations, or modifications to the requirements, and terms and conditions of the contract, must be addressed to the CO with an information copy to the COR or his designated representative.

20.0 Public Release of Contract Documents Requirement

The Contractor agrees to submit, within ten business (10) days from the date of the CO’s execution of the initial Contract, any task order, or any modification to the Contract or task order (exclusive of Saturdays, Sundays, and Federal holidays), a .pdf file of the fully executed document with all proposed necessary redactions, including redactions of any trade secrets or any commercial or financial information that it believes to be privileged or confidential business information, for the purpose of public disclosure at the sole discretion of the Treasury. The Contractor agrees to provide a detailed written statement specifying the basis for each of its proposed redactions, including the applicable exemption under the Freedom of Information Act (FOIA), 5 U.S.C. § 552, and, in the case of FOIA Exemption 4, 5 U.S.C. § 552(b)(4), shall demonstrate why the information is considered to be a trade secret or commercial or financial information that is privileged or confidential. Information provided by the Contractor in response to the Contract requirement may itself be subject to disclosure under the FOIA.

The Treasury will carefully consider all Contractor proposed redactions and associated grounds for nondisclosure prior to making a final determination as to what information in such executed documents may be properly withheld.

21.0 Section 508 Accessibility of Electronic and Information Technology Requirements All tools, reports, dashboards, and documentation provided by the contractor shall comply with Section 508 of the Rehabilitation Act Amendment of 1998 for Americans with Disabilities (ADA). This ensures that individuals with disabilities are provided comparable access or the same accessibility to all software information and data as individuals without disabilities. Additional details may be found on:

12.0 13.0 14.0 15.0 16.0 17.0 18.0 19.0 20.0

· The Department of the Treasury, Treasury Directive 87-06 site:

· https://home.treasury.gov/about/general-information/orders-and-directives/td87-06

· The U.S. General Services Administration (GSA) Section 508 official site:

· https://www.section508.gov/manage/

22.0 Status of Performance

During the life of the Contract should any incident occur which the Contractor believes may circumvent or encumber the performance of the Contract, the Contractor shall immediately notify the CO. The receipt of such a notice shall not be construed as a waiver by the Treasury of any of its rights and remedies provided by law or under the terms of the Contract.

image1.jpeg