Type of document: Contract Notice
Country: United States


Department of Health and Human Services

Official Address:
1095 Willowdale Road Morgantown WV 26505

Zip Code:

Rebecca S Mullenax, Phone 304-285-5880, Fax 304-285-6083, Email


Date Posted:


Contract Description:
Sole Source FBO Notice for Procurement Request 00HCPC16-2018-22691
Title: Development of HL7 Fast Healthcare Interoperability Resources (FHIR) Profiles and Implementation Guide for Vital Records Mortality Reporting
The Centers for Disease Control and Prevention (CDC) and the National Center for Health Statistics (NCHS) located in Hyattsville, MD intends to award a sole source firm fixed price purchase order to Shakir Consulting, Inc. 5795 Blackbird Lane, La Verne, CA 92750-2370 for Development of HL7 Profiles.
CLIN 0001:

The purpose of this contract is to assist NCHS and its stakeholders with the development of an HL7 FHIR Implementation Guide for mortality reporting. The artifacts created will trace back to the VR DAM R2. The contractor will also assist NCHS in balloting the artifacts through the HL7 balloting process and will help to reconcile any comments received during the balloting process. In accordance with the Statement of Work:

Statement of Work
TITLE: Development of HL7 Fast Healthcare Interoperability Resources (FHIR) Profiles and Implementation Guide for Vital Records Mortality Reporting


The Centers for Disease Control and Prevention (CDC) serves as the national focus for developing and applying disease prevention and control, environmental health, and health promotion and health education activities designed to improve the health of the people of the United States. The National Center for Health Statistics (NCHS), which is located within the Centers for Disease Control and Prevention (CDC), is the Nation’s principal health statistics agency. It compiles statistical information to guide actions and policies to improve the health of the Nation. It is a unique public resource for monitoring health information and a critical element of public health and health policy.
The National Vital Statistics System (NVSS) is one of the data systems within NCHS used for this monitoring activity. NVSS is a legislatively-mandated data program, producing data on births, deaths, and fetal deaths. Over 6.5 million state records are collected annually for processing, coding, analysis, and publication in aggregate form electronically and on paper; of these events, about 2.6 million are death records. The receipt and initial processing of these records and the coding of the cause-of-death literals on them occurs primarily through staff and systems located at the NCHS facility in Research Triangle Park, North Carolina. Subsequent editing, processing, analysis, publication and dissemination of the data occur through staff located at the Hyattsville, Maryland facility.
One of the goals of the NVSS is to improve the timeliness and quality of the mortality data. Timely reporting of death information is critical for detecting and defining pandemic and other calamitous events as well as showing shifts in causes of death by age, race and sex. Yet, timely death reporting has been a major challenge for the vital statistics system, partially due to the outdated and inefficient technology and the lack of standards to facilitate the exchange of information between hospital/healthcare based IT systems and electronic vital registration systems.
Because much of the data collected through the NVSS comes from hospital and other medical records, NCHS and the vital statistics community have worked collaboratively since 2007 to establish national standards whereby information can be exchanged electronically from hospital and other health records to the electronic registration systems. This work resulted in the publishing of the Health Level Seven International (HL7) Version 3 Domain Analysis Model: Vital Records (VR DAM), Release 1. This document describes the workflows and stakeholders for transmitting birth and death data to and from U.S. vital records systems. It also describes how birth, death and fetal death records are processed in the U.S. and identifies the stakeholders participating in the data exchange. The VR DAM serves as the framework to guide future standards development for vital records exchange. The VR DAM is based on the core set of vital records data elements that are on the United States (U.S.) Standard Certificates of Live Birth and Death and the U.S. Standard Report of Fetal Death. In May 2017, the VR DAM was updated to a Release 2, titled the HL7 Cross-Paradigm Domain Analysis Model: Vital Records Release 2 (VR DAM R2).
Since the first release of the VR DAM, information exchange specifications for Vital Records have been developed as HL7 v2.5.1 and v2.6 message conformance profiles; HL7 Clinical Document Architecture (CDA) implementation guides and Integrating the Healthcare Enterprise (IHE) Technical Framework Supplements; and HL7 Fast Healthcare Interoperability Resources (FHIR) profiles and resource bundles. A prototype, FHIR-based clinical decision support tool for mortality reporting was tested at the IHE Connectathon in January 2018.
The purpose of this contract is to assist NCHS and its stakeholders with the development of an HL7 FHIR Implementation Guide for mortality reporting. The artifacts created will trace back to the VR DAM R2. The contractor will also assist NCHS in balloting the artifacts through the HL7 balloting process and will help to reconcile any comments received during the balloting process.
The Contractor shall develop and establish a procedure to complete the development of an HL7 FHIR Implementation guide that will include the FHIR profiles for mortality reporting. To be of eventual utility, the profiles should be of sufficient detail to inform the development of specifications for FHIR-based Application Programming Interfaces (APIs) for electronic death registration systems and to support physician-facing FHIR-based clinical decision support tools for mortality reporting.
The contractor will compare the proposed profiles for mortality reporting to the published VR DAM Release 2 as well as the current published version of the HL7 FHIR implementation guide. The Contractor will highlight where revisions to the existing draft mortality profiles may be needed, where relevant profiles have not yet been developed for mortality reporting, and where any inconsistencies exist between the existing draft profiles for mortality and the current published version of the FHIR implementation guide. The contractor will also help NCHS to prepare for the FHIR DevDays event to be held in Boston in June 2018 and will lead the FHIR profiling work for mortality reporting that will take place during that event. The contractor will also develop all materials and artifacts needed to assist NCHS with the HL7 balloting process for the FHIR Implementation guide for mortality reporting, including but not limited to helping NCHS to reconcile any comments received during the balloting process and publishing a final HL7 implementation guide.
The contractor shall complete the development of FHIR profiles for mortality reporting as defined in the tasks below. All labor, materials, and equipment shall be required to complete the defined tasks.
Work Breakdown
The following data flow diagram illustrates the major tasks in this project and the relationship this project has to work products produced in related external projects:

Specific Tasks
The contractor is expected to complete the work in two phases. The tasks involved in each project phase are described below.
Phase I: Vital Records Death Reporting STU FHIR Implementation Guide. Prepare a Standard for Trail Use version of an HL7 FHIR Implementation Guide for use by jurisdictional public health agencies in obtaining vital records death notifications and forwarding applicable death report records to the NCHS.

Phase I Tasks Descriptions
1. FHIR Resource Profiling. Use output work products from the US Core Implementation Guide Development project, the Vital Records Domain Analysis Model Specification Modeling Project, and the Death on FHIR Prototype Project (see and ) to select or define the applicable FHIR resources required to enable jurisdictional and national vital records death reporting. Create FHIR resource profiles to constrain and extend the selected FHIR resources to meet the data requirements of vital records death reporting.
2. FHIR Implementation Guide Development. Create Bundle resource specifications to serve as grouping a set of profiled resources to act as an exchangeable collection of data for use as the payload of exchanges defined for death reporting in the Vital Records DAM. Create an Implementation Guide resource and specification defining the set of rules about how the bundles of death reporting FHIR resource profiles are to be implemented in software solutions supporting vital record death reporting. This will include presenting the project to the Health Level Seven International (HL7) Public Health Workgroup and updating the existing HL7 Project Scope Statement to reflect how the draft FHIR profiles can help support the development of FHIR APIs and FHIR-based clinical decision support tools for mortality reporting.
3. Vital Record Death Reporting STU FHIR IG Balloting. Prepare the
Vital Records Death Reporting Implementation guide for inclusion in an HL7 ballot as a standard for trial use. Obtain and consolidate the ballot comments made by members of the ballot pool in preparation for review and reconciliation. Work in conjunction with the HL7 Public Health Workgroup to reconcile ballot comments, finalize the VRDR IG, and submit the approved VRDR IG for publication as a standard for trial use.
Phase II: Vital Records Death Reporting Normative FHIR Implementation Guide. As NCHS uses the Vital Records Death Reporting STU FHIR Implementation Guide prepared in phase I in NCHS-sponsored proof-of-concept pilot projects, both to demonstrate the utility and to confirm the efficacy of the specification, this second phase will include revision of the VRDR IG to include lessons learned from the POC Pilots and incorporate harmonized jurisdictional data requirements. The revised VRDR IG will be balloted as a Normative FHIR Implementation Guide.

Phase II Tasks Descriptions
4. VR Death Reporting STU FHIR IG Pilot Projects. Provide technical support for a minimum of two and a maximum of five pilot implementation projects. Each pilot will involve the NCHS, one or more Jurisdictional Public Health Agencies, and local Vital Records Death Reporting originating data sources. The purpose of the pilot projects is to validate the completeness and efficacy of the VRDR STU FHIR IG. Technical support to the project is limited to responding to questions regarding the VRDR STU FHIR IG specification and providing expert advice regarding the resolution of identified defects or deficiencies in the guide.
5. VR Death Reporting STU FHIR IG Update. Update the VRDR STU FHIR IG in response to defects or deficiencies identified while executing pilot implementation projects and new data requirements stemming from VR Death Reporting Jurisdictional data requirements harmonization. Upgrade the VRDR STU FHIR IG to use the most recent normative release of FHIR resources and profiles. Realign the VRDR STU FHIR IG with the most recent published version of the Vital Records Domain Analysis Model.
6. VR Death Reporting FHIR IG Normative Ballot. Prepare the Vital Records Death Reporting Implementation guide for inclusion in an HL7 ballot as a normative specification. Obtain and consolidate the ballot comments made by members of the ballot pool in preparation for review and reconciliation. Work in conjunction with the HL7 Public Health Workgroup to reconcile ballot comments, finalize the VRDR IG, and submit the approved VRDR IG for publication as a normative specification.
Project Management: Kick-off Meeting, Project Plan, Monthly and Final Reports, HL7 Conferences and Workgroup Meetings
7. The Contractor will conduct a kickoff meeting with NCHS/CDC to review deliverables and milestones, and create and manage a project plan to maintain schedule and budget. The contractor will work with NCHS/CDC to identify a team to provide input into the project and shall conduct at minimum bi-weekly calls with the team to discuss project status, stakeholder issues, and identify data needs.

8. The contractor shall produce monthly reports on the progress of the FHIR profiling for mortality effort against the approved project schedule. The report shall be submitted by the 10th day of each month. At the end of each project phase, the contractor shall produce a final report on the FHIR profiling mortality effort.

9. The contractor will attend, participate in, and help lead NCHS’s involvement in the FHIR DevDays event in Boston, Massachusetts in June of 2018 as well as the HL7 Working Group meeting in September 2018 and January 2019.
All materials to undertake and complete this project shall be provided by the contractor.
The period of performance shall commence upon award and complete no later than September 30, 2021.
The contractor shall perform all work under the contract offsite.
The contractor shall provide the following deliverables to the contracting officer’s representative and the technical monitor by the dates reflected below.
Deliverables Date Required
Attend Kick-off meeting and provide summary and Project plan Within 10 days of award
FHIR Resource Profiling (as described in Phase 1, task 1: conduct an analysis of work products from related external projects, select or define FHIR resources for death reporting, participate in HL7 FHIR DevDays event, create FHIR resource profiles to constrain and extend the selected FHIR resources) October 2, 2018
FHIR Implementation Guide Development (as described in Phase 1, task 2: bundle FHIR resources for inclusion in a vital records death reporting implementation guide, create the implementation guide specifications and supporting documentation) November 2, 2018
Vital Record Death Reporting Standard for Trial Use FHIR Implementation Guide Balloting (as described in Phase 1, task 3: prepare the ballot material, ballot the FHIR implementation guide, obtain and consolidate ballot comments, reconcile ballot comments, finalize the implementation guide, publish the implementation guide as a Standard for Trial Use) March 29, 2019
Provide technical advice for Pilot projects (as described in Phase 2, task 4) January 29, 2021
Standard for Trial Use FHIR Implementation Guide Update (as described in Phase 2, task 5) March 26, 2021
FHIR Implementation Guide Normative Ballot (as described in Phase 2, task 6) August 13, 2021
Monthly Reports and Final Report. Final Report to be provided one month after close of each contract phase. 10th day of each month after contract award; final report one month after each contract phase.

Travel will be required to attend and lead the FHIR profiling efforts at the FHIR DevDays event in Boston, Massachusetts in June of 2018. Travel will also be required to attend the HL7 Working Group meetings as requested by NCHS and to participate in Connectathons and/or the balloting process.

A. Prohibition on the Use of Appropriated Funds for Lobbying Activities (Jul 1999)

The Contractor is hereby notified of the restrictions on the use of Department of Health and Human Service’s funding for lobbying of Federal, State and Local legislative bodies. Section 1352 of Title 10, United Stated Code (Public Law 101-121, effective 12/23/89), among other things, prohibits a recipient (and their subcontractors) of a Federal contract, grant, loan, or cooperative agreement from using appropriated funds (other than profits from a federal contract) to pay any person for influencing or attempting to influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in connection with any of the following covered Federal actions; the awarding of any Federal contract; the making of any Federal grant; the making of any Federal loan; the entering into of any cooperative agreement; or the modification of any Federal contract, grant, loan, or cooperative agreement. For additional information of prohibitions against lobbying activities, see FAR Subpart 3.8 and FAR Clause 52.203-12.

In addition, the current Department of Health and Human Services Appropriations Act provides that no part of any appropriation contained in this Act shall be used, other than for normal and recognized executive-legislative relationships, for publicity or propaganda purposes, for the preparation, distribution, or use of any kit, pamphlet, booklet, publication, radio, television, or video presentation designed to support, or defeat legislation pending before the Congress, or any State or Local legislature except in presentation to the Congress, or any State or Local legislative body itself.

The current Department of Health and Human Services Appropriations Act also provides that no part of any appropriation contained in this Act shall be used to pay the salary or expenses of any contract or grant recipient, or agent acting for such recipient, related to any activity designed to influence legislation or appropriations pending before the Congress, or any State or Local legislature.
(End of Clause)

B. Privacy Act Applicability (Apr 2000)

(a)While the Privacy Act is not applicable, the appropriate security controls and Rules of Behavior should be incorporated to protect the confidentiality of information, proprietary, sensitive, and Personally Identifiable Information (PII) the Contractor may come in contact with during the performance of this contract.

(b) Notification is hereby given that the Contractor and its employees are subject to criminal penalties for violation of the Privacy Act to the same extent as employees of the Government. The Contractor shall assure that each of its employees knows the prescribed rules of conduct and that each is aware that he or she can be subjected to criminal penalty for violation of the Act. A copy of 45 CFR Part 5b, Privacy Act Regulations, may be obtained at ;tpl=/ecfrbrowse/Title45/45cfr5b_main_02.tpl

(c) The Project Officer is hereby designated as the official who is responsible for monitoring contractor compliance with the Privacy Act.

(d) The Contractor shall follow the Privacy Act guidance as outlined in the Privacy Act of 1974 (5 USC 552a) and Section 308(d) of the Public Health Service Act.

(End of Clause)
C. Data Subject to Confidentiality Requirements (May 1998)

The type(s) of data subject to the clause at 352.224-70, Confidentiality of Information, which has been incorporated by reference in Section I, are as follows:

Personal Health Information (PHI)

Following are the requirements for handling these data:

All data will be handled in accordance with the procedures /requirements outlined in the Privacy Act of 1974 (5 USC 552a) and Section 308(d) of the Public Health Service Act.

(End of Clause)

D. Dissemination of Information (May 1998)

No information related to data obtained under this contract shall be released or publicized without the prior written consent of the Project Officer.

(End of Clause)

E. Systems Security and Safeguards

Information Technology Security
The Contractor’s performance and resulting deliverables must adhere to all federal, HHS, and/or CDC IT security policies and procedures. Based upon the scope of this contract, adherence to the following IT Security guidance is required whether the entire contract or order (hereafter “contract”), or portion thereof, includes information technology resources or services in which the Contractor has physical or logical (electronic) access to, or operates a Department of Health and Human Services (HHS) system containing, information that directly supports HHS’ mission. The term “information technology (IT)”, as used in this contract, includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed to be controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), cloud environments, and related resources. This clause does not apply to national security systems as defined in FISMA.

The Contractor is responsible for the following: (1) Protecting Federal information and Federal information systems in order to ensure their-(i) Integrity, which means guarding against improper information modification or destruction, and includes ensuring information non-repudiation and authenticity; (ii) Confidentiality, which means preserving authorized restrictions on access and disclosure, including means for protecting personal privacy and proprietary information; and (iii) Availability, which means ensuring timely and reliable access to and use of information.(2) Providing security of any Contractor systems, and information contained therein, connected to an HHS network or operated by the Contractor, regardless of location, on behalf of HHS. (3) Adopting, and implementing, at a minimum, the policies, procedures, controls, and standards of the HHS Information Security Program to ensure the integrity, confidentiality, and availability of Federal information and Federal information systems for which the Contractor is responsible under this contract or to which it may otherwise have access under this contract. The HHS Information Security Program is outlined in the HHS Information Security Program Policy, which is available on the HHS Office of the Chief Information Officer’s (OCIO) Web site.

All development or implementation of an electronic information system or any electronic data collection effort conducted in the performance of this contract will be required to complete Certification and Accreditation (C&A)/Security Assessment and Authorization (SA&A) prior to operation resulting in an Authority of Operate (ATO) from CDC. The contractor shall be required to complete all security documentation and materials necessary to obtain an ATO. The contractor shall comply with all applicable HHS, CDC, FISMA, HIPPA, NIST, and other federal policies and regulations in the performance of the security requirements.

All information systems developed, implemented, or maintained in support of this contract must adhere to the security controls outlined in the National Institute of Standards and Technology (NIST) Special Publication 800-53, Recommended Security Controls for Federal Information Systems and Organizations () and NIST 800-53A, Guide for Assessing the Security Controls in Federal Information Systems and Organizations.

The Contractor must follow the latest guidance available from NIST and other recognized sources, including but not limited to:
• FIPS Publication 199, Standards for Security Categorization of Federal Information and Information Systems (),
• FIPS Publication 200, Minimum Security Requirements for Federal Information and Information Systems (),
• NIST Special Publication 800-18, Guide for Developing Security Plans for Federal Information Systems (),
• NIST Special Publication 800-37, Guide for Applying the Risk Management Framework to Federal Information Systems: A Security Life Cycle Approach (),
• NIST publication SP 800-44 Guidelines on Securing Public Web Servers, ()
• NIST Special Publication 800-53, Security and Privacy Controls for Federal Information Systems and Organizations (),
• NIST Special Publication 800-60, Guide for Mapping Types of Information and Information Systems to Security Categories Vol. 1 () and Vol. 2 (),
• NIST Special Publication 800-63, Electronic Authentication Guideline ().
• NIST publication SP 800-95 Guide to Secure Web Services, () when applicable.
• Web Application Security Consortium ()
• Open Web Application Security Project (OWASP) ().

The contractor must follow CDC development standards and use the CDC web template package. All CDC websites, campaign sites, and applications must use the standard CDC web template to ensure a consistent look and feel for CDC websites. The template and guidance will be provided as needed by the CDC Project Officer or the Center’s ISSO.

All web content must reside on a domain and must be hosted at CDC or in a CDC-authorized environment. The contractor may not establish a .com, .org, or other type of site to host CDC funded content or web applications.

During any application development or enhancement, the contractor shall work closely with NCHS offices/divisions and NCHS Information System Security Officer (ISSO) to ensure all CDC-related technical and security standards, processes and procedures are followed. This working relationship shall continue through full production.

If use of a cloud environment is needed, the provider must be FedRAMP certified. The contractor shall comply with FedRAMP requirements as mandated by Federal laws and policies, including making available any documentation, physical access, and logical access needed to support this requirement. The cloud environment must also have an Authority to Operate from HHS.

All publicly accessible Federal websites and web services must provide service over a secure connection. The strongest privacy protection currently available for public web connections is Hypertext Transfer Protocol Secure (HTTPS).

Government access for IT inspection. The Contractor shall afford the Government access to the Contractor’s and subcontractors’ facilities, installations, operations, documentation, databases, and personnel used in performance of this contract to the extent required to carry out a program of IT inspection (to include vulnerability testing), investigation, and audit to safeguard against threats and hazards to the integrity, confidentiality, and availability, of HHS data or to the protection of information systems operated on behalf of HHS.

Standard for Encryption Language
• The Contractor shall use Federal Information Processing Standard (FIPS) 140-2-compliant encryption (Security Requirements for Cryptographic Module, as amended) to protect all instances of HHS information during storage and transmission.

• The Contractor shall verify that the selected encryption product has been validated under the Cryptographic Module Validation Program (see ) to confirm compliance with FIPS 140-2 (as amended). If requested, the Contractor shall provide a written copy of the validation documentation to the Contracting Officer and the Contracting Officer’s Technical Representative.

• The Contractor shall use the Key Management Key (see FIPS 201, Chapter 4, as amended) on the HHS personal identification verification (PIV) card; or alternatively, the Contractor shall establish and use a key recovery mechanism to ensure the ability for authorized personnel to decrypt and recover all encrypted information (see ). The Contractor shall notify the Contracting Officer and the Contracting Officer’s Technical Representative of personnel authorized to decrypt and recover all encrypted information.

• The Contractor shall securely generate and manage encryption keys to prevent unauthorized decryption of information in accordance with FIPS 140-2 (as amended).

• The Contractor shall ensure that this standard is incorporated into the Contractor’s property management/control system or establish a separate procedure to account for all laptop computers, desktop computers, and other mobile devices and portable media that store or process HHS information.

• The Contractor shall ensure that its subcontractors (at all tiers) which perform work under this contract comply with these requirements.

HSPD-12 Compliance
As part of the Federal HSPD-12 directive, all information systems deployed within/outside of any federal infrastructure must be able to support HSPD-12 compliant Personal Identity Verification (PIV) of federal employees and contractors. The government has complied with HSPD-12 by issuing PIV cards with embedded digital certificates to all users of federal information systems. In accordance with this directive, all vendors providing hardware and software to the federal government are required to ensure that these PIV cards will integrate with their software and hardware at the application level. Contractor must be able to implement and support PIV card integration.

Standard for Security Configurations
The Contractor shall apply approved security configurations to information technology (IT) that is used to process information on behalf of CDC. The following security configuration requirements apply.

• The Contractor shall configure its computers that contain CDC data with the applicable United States Government Configuration Baseline (USGCB) (see ) and ensure that its computers have and maintain the latest operating system patch level and anti-virus software level. Note: USGCB is applicable to all computing systems, including desktops and laptops-regardless of function-but not including servers.

• The Contractor shall ensure IT applications operated on behalf of CDC are fully functional and operate correctly on systems configured in accordance with the above configuration requirements. The Contractor shall use Security Content Automation Protocol (SCAP)-validated tools with USGCB Scanner capability to ensure its products operate correctly with USGCB configurations and do not alter USGCB settings-see The Contractor shall test applicable product versions with all relevant and current updates and patches installed. The Contractor shall ensure currently supported versions of information technology products meet the latest USGCB major version and subsequent major versions.

• The Contractor shall ensure IT applications designed for end users run in the standard user context without requiring elevated administrative privileges.

• The Contractor shall ensure hardware and software installation, operation, maintenance, update, and patching will not alter the configuration settings or requirements specified above.

• The Contractor shall (1) include Federal Information Processing Standard (FIPS) 201-compliant (see ), Homeland Security Presidential Directive 12 (HSPD-12) card readers with the purchase of servers, desktops, and laptops; and (2) comply with FAR Subpart 4.13, Personal Identity Verification.

• The Contractor shall ensure that its subcontractors (at all tiers) which perform work under this contract comply with these requirements.

F. Security Clearance Requirements (Jul 1999)

(a) Definitions.
“Employees” means both contractor and subcontractor employees unless otherwise noted:
The phrase “CDC owned or leased facilities” includes ATSDR, NIOSH/PRC/Pittsburgh, Pa.; NIOSH/Morgantown, W.V.; NIOSH/SRC/Spokane, WA.; NIOSH/Cincinnati, Ohio; NCHS/Research Triangle Park, N.C.; NCHS/Hyattsville, Md. NCID/Fort Collins, Colorado; NCID/Anchorage, Alaska, and NCID/San Juan, Puerto Rico.

(b) General
All contract employees who will be performing work under this contract on-site (i.e., in a CDC owned or leased facility) for a period exceeding 90 days in duration (45 days if employee is designated to work in Building 10, 15, or 17 at 1600 Clifton Road, Atlanta, GA, or at CDC’s Lawrenceville, GA facility) shall receive a favorable suitability determination prior to reporting to work at an on-site facility. Any contract employee(s) who cannot obtain a favorable suitability determination, will not be permitted to work at an on-site facility (see paragraph B below on temporary determinations.)

The Contractor shall be responsible for managing its workforce to ensure that sufficient contract employees who meet all suitability requirements are available to perform the duties required under the contract. New or replacement contract employees must have previously received a favorable suitability determination in sufficient time to perform work at an on-site facility under the contract. If it has been over one (1) year since a contract employee has worked in a position on a Federal contract for which a security clearance was required, a new National Agency Check and Inquiry (NACI) must be obtained.

(c) Temporary Determinations/Clearances

The Contracting Officer may, as appropriate, authorize and grant temporary suitability determinations to contract employees. However, the granting of a temporary determination shall not be considered as assurance that full clearance will follow. The granting of a temporary determination shall not prevent, preclude or bar the withdrawal or termination of any temporary determination. Prior to the Government’s issuance of a temporary determination, the Contractor shall obtain and provide to the Contracting Officer a state-wide criminal records check for all on-site contract employees. The Contractor shall also obtain and provide to the Contracting Officer a state-wide motor vehicle violations check for any contract employee required to operate a motor vehicle as part of their duties under the contract at an on-site facility. All criminal record checks and motor vehicle violation checks shall cover a twelve (12) month period beginning twelve (12) months prior to the date of the contract award. Criminal record checks and motor vehicle violation checks may be obtained through local state, county or city law enforcement agencies at contract employee’s place of residence. Where state-wide criminal record and motor vehicle violation systems are not available, county-wide or city-wide checks may be substituted. All substitutions shall be certified by the law enforcement agency that a state-wide criminal record system is not available.

(d) Required Information for NACI Clearance:

Unless otherwise specified, the Contractor shall submit the completed forms specified below to the appropriate office as directed by the Contracting Officer not later than 5 calendar days from the effective date of the contract. Items (1) through (6) must be completed by contract employees who require access to on-site facilities in the performance of the contract. Additionally, the contractor shall furnish, on a monthly basis, item (7) (if the information requested in Item (7) is provided as part of the Contractor’s standard invoice, no additional submission is required). The Government will furnish the necessary forms to the Contractor.

(1) Two (2) completed Forms FD-258, “FBI Fingerprint Charts”***

(2) One (1) completed Standard Form 85, “Questionnaire for Non-Sensitive Positions”

(3) One (1) completed “Declaration for Enrollment”

(4) One (1) resume or curriculum vitae or completed job application form

(5) One (1) copy of the state-wide criminal records check

(6) One (1) copy of the motor vehicle violations check (when applicable)

(7) A complete listing of all current Contractor and Subcontractor on-site employees by name, work location and employer.

*** The CDC, Human Resource Management Offices (HRMO) have the necessary equipment to complete fingerprint charts (FD-258). The Contractor may contact the Contracting Officer for arrangements regarding utilization of the HRMO fingerprinting equipment. The fingerprint charts may also be completed through a local state, county or city law enforcement agency at the employee’s place of residence.

Using the required information specified above, a National Agency Check and Inquiry (NACI) will be processed by the CDC through the Office of Personnel Management and the Federal Bureau of Investigations (OPM/FBI) on each contract employee who will be performing duties on-site.

(d) Removal of Contractor Employees

The Contracting Officer may request the Contractor to immediately remove any contract employee from the on-site facility who has failed to receive a suitability determination and whose continued employment is deemed contrary to the public interest, inconsistent with the best interests of security, or is identified as a potential threat to the health, safety, security, general well-being or operational mission of the on-site facility and its population. The Contracting Officer may also request the Contractor to immediately remove any contract employee from the on-site facility should it be determined that the individuals are being assigned to duty who have been disqualified for suitability reasons, or who are found to be unfit for performing duties during their tour(s) of duty. Contract employees who are requested to be removed from the on-site facility are required to leave the work site immediately.

The Contracting Officer will make all determinations regarding the removal of any contract employee from the on-site facility, except under certain conditions. When a Contracting Officer is not available, either during the day or after normal business hours, or in situations where a delay would not be in the best interest of the Government, or a potential threat to the health, safety, security, general well- being or operational mission of the facility and its population, the Project Officer will have the authority to direct immediate removal of the contractor employee from the on-site facility. The Contracting Officer shall subsequently provide the official notification to the Contractor for removal of a contract employee from the CDC facility. When removal is directed due to a non-suitability determination as a result of the NACI, no further information will be provided. If removal is directed for other reasons relating to specific conduct of the employee during performance of the work, the Contracting Officer’s official notification will provide information as to these reasons.

(e) Identification Badges/Cardkey Access:

(1) Identification Badges:

The Contractor shall require each contract employee who has been authorized unescorted access to an on-site facility, either through the temporary clearance process or the formal NACI process, to display an identification badge as required and furnished by the CDC. The Contractor shall submit to the Project Officer a completed Identification Badge Request Form (CDC Form 0.1137) for each contract employee who has been authorized unescorted access to an on-site facility. Contact the Project Officer for details on additional procedures, specific addresses and hours of business for issuance of Identification Badges for all other CDC locations.

(2) Cardkey Access:

Unescorted access to certain on-site facilities at CDC may only be gained through the use of a Cardkey. If a contract employee has been determined to need regular unescorted access to one of the Cardkey access designated areas, a Cardkey Request Form (CDC Form 0.834) must be completed and submitted to the Project Officer for written approval. Contact the Project Officer for details of procedures and specific addresses and hours of business for issuance of Cardkey Access.

(3) Return of Identification Badges/Cardkeys

The Contractor shall arrange for the return of any employee identification badges and/or cardkeys immediately upon their separation of the duties at the on-site facility. Contact the Project Officer for location of the depositories for the return of badges. Cardkeys shall be returned to the appropriate Physical Security Activity Office.

(End of Clause)


The Government and the Contractor understand and agree that the services to be delivered under this contract by the Contractor to the Government are non-personal services and the parties recognize and agree that no employer-employee relationship exists or will exist under the contract between the Government and the Contractor personnel. It is, therefore, in the best interest of the Government to afford both parties a full and complete understanding of their respective obligations.

Contractors are not federal employees, and federal employees may not interact with contractor personnel as if there is an employer-employee relationship. This means that federal employees do not:

• Supervise contractor employees;
• Hire, fire or discipline contractor personnel;
• Schedule individual contractor personnel hours;
• Reassign contractor personnel;
• Grant or deny contractor personnel leave requests (but you have the right and obligation to know which personnel will be on-site and when);
• Assess performance or individual contractor personnel;
• Provide performance feedback to individual contractor personnel;
• Provide input for contractor employee’s annual (or periodic) performance appraisals;
• Provide or discuss contractor employee performance and career development plans;
• Provide training not stipulated in the contract to contractor personnel without coordination with the Contracting Officer and/or Office of General Counsel; and
• Provide rewards or awards unless performance meets specific criteria and they are approved by the Contracting Officer and the OGC.

We contract for services, not for individuals. The companies with whom we contract have processes to deal with personnel issues. Federal employees can forward concerns to the Contracting Officer and/ or Contracting Officer’s Representative, who are charged with communicating issues to the Contractor.

Only authorized Contracting Officers and purchase card holders may solicit and negotiate services from contractors. The consequences of other individuals soliciting or negotiating services include additional documentation and delays as well as personal liability.

Contractor personnel may not perform inherently governmental functions. This means that federal employees cannot request or allow contractor personnel to perform the following:
• Represent the government;
• Supervise or direct federal employees;
• Determine which supplies/services are to be purchased by the government;
• Negotiate or obligate the government to pay for goods or services;
• Determine federal program priorities, draft strategic plans; or
• Perform other functions involving the exercise of discretion in applying governmental authority or value judgments.

Federal employees must ensure that the work stipulated in the contract is performed in accordance with the terms and conditions of the contract. The contract defines the government’s obligations and the contractor’s responsibilities. Contractors do not have “other duties as assigned.” Federal employees:
• May not require, agree, or encourage performance of service outside scope of the contract;
• May not request contractor personnel to perform prior to obligation of funding by the Contracting Officer;
• May not perform the Contractor’s work/obligations or provide Contractor personnel government resources (including other Contractor services), training, government owned vehicles, or supplies except as stipulated in the contract;
• Shall ensure that hours/services required under the contract are provided;
• Shall ensure that the government is billed properly for direct labor, which includes only time spent working on direct contract requirements.
• Generally may not authorize contractor employees to bill direct labor for team building or other activities; and
• May not put contractor employees in the position of taking unpaid leave in order to join and be viewed as part of the team.

Federal employees have a duty to conserve and protect government resources, and must ensure that government furnished property, facilities, and resources are used only for contract performance. Federal employees may not give preferential treatment or endorse any product, service, individual, or company.
Federal employees may not provide information to contractor employees except as required for contract performance and as authorized to distribute the information.
Contractors shall submit Freedom of Information Act (FOIA) requests for information not necessary for performance set forth in the contract. Only Contracting Officers may release source selection information. Proprietary data being used by the Government may not be shared without the express or implied consent of the owner of the data.
Federal employees may not allow contractors to use the agency’s name, seal, or acronym in connection with commercial activity unless approval is obtained. Contractor employees may not use government business cards or business cards that state or imply that they are federal employees.
Federal employees may never solicit gifts from contractor employees, and may not accept gifts (anything of value including local transportation) unless an exception to the gift rules applies. Federal employees may not accept contributions to group gifts from contractor employees.
Contractor personnel’s use of government furnished property (government computers, telephones, etc.) is subject to the terms of the contract. Contractors may not use GFP for the following:
• Outside business activities,
• Personal activities, or
• Soliciting/fundraising

Contractor personnel are required to identify themselves as contractors when they attend meetings, answer telephones, respond or send emails using a government/military address, or work in situations where their actions may be construed as acts of government officials.
Contractors may not represent the government or represent themselves as government employees. Contractors may not use government organizational occupational titles.

Federal employees may have professional relationships with contractor personnel, but if they have a close personal relationship (or financial interest), with the contractor employee, they may not give advice, make recommendations, or make decisions pertaining to the Contractor for whom the contractor person works.

Federal employees have a duty to report (promptly and accurately) adverse information about contractor performance. Federal employees must resolve all performance issues through the COR and Contracting Officer. The COR and

Contracting Officer have a duty to take appropriate contractual action. Federal employees have a duty to report improper and potentially criminal activity (ies) to the appropriate government office (Office of the Inspector General or OGC) and not to the Contractor.

Given the nature of the task requirements and the working environment, it may be necessary for government and contractor personnel to work as a team to accomplish work objectives, share knowledge, and work in a mutually supportive role. This should be accomplished while preserving the non-personal services nature of the task. The operational need to work in concert should be accomplished in a manner consistent with preserving the management responsibilities of the Contractor.

Working in a team environment, absent a designated contractor supervisor, may require the government to provide work direction to contractor personnel. Work direction means a communication to contractor personnel that directs or approves approaches, documents, presentations, or refinements to work; fills in details or otherwise completes the general description of work or documentation items; shifts emphasis among work areas or tasks; or furnishes similar instructions to contractor personnel. Work direction includes requiring analyses and development of administrative related products within the scope of work for the task.

The Contractor is at all times responsible for the quality of contractor personnel work. It is the direct responsibility of the Contractor to perform all tasks normally associated with an employer-employee relationship, e.g., completing time cards, resolving quality of work issues, ensuring high motivation and morale, and resolving government-identified contractor performance concerns. The physical absence of a contractor direct line supervisor does not relieve the Contractor of these responsibilities.
To ensure effective and efficient administration of duties, the contractor personnel need to establish and maintain work procedures that facilitate close and continuous coordination with agency Contracting Officers (CO), Project Officers (PO), and other Program Management (PM) personnel.
In addition, NCHS frequently responds to politically sensitive, high level support requirements with extremely short suspense actions. To function effectively and efficiently as a team member in this environment, the Contractor must ensure personnel provided possess a high degree of subject matter knowledge, skills, and abilities to perform the tasks relating to the objective. The Contractor supervision of Contractor personnel must also reflect the need to sustain a high-performing, highly motivated, and responsive team.

H. Smoke Free Working Environment (May 2009)

In compliance with Department of Health and Human Services (DHHS) regulations, all contractor personnel performing work within CDC/ATSDR facilities shall observe the CDC/ATSDR smoke-free working environment policy at all times. This policy prohibits smoking in all CDC/ATSDR buildings and in front of buildings which are open to the public. This policy is also applicable to contractor personnel who do not work full-time within CDC/ATSDR facilities, but are attending meetings within CDC/ATSDR facilities.

(End of Clause)

I. Release of Information

The program, this contract, any delivery/task order(s) issued under this contract, or actions as a result of this contract, pertain to a national security issue, and as such, all information is non-releasable. Any outside inquiries shall be immediately reported to the Government Contracting Officer for action.

The Contractor shall not, unless authorized in writing by the Contracting Officer or cognizant Project Officer or Technical Monitor, release or provide any information regarding work performed under this contract and any or all individual delivery/task orders issued against this contract.

(End of Clause)

J. FAR 52.216-1 Type of Contract (Apr 1984)

The Government contemplates award of a Performance Based Fixed Price Contract.

(End of Clause)

K. Non-Disclosure Agreements for Contractor and Contractor Employees – Mar 2006

(a) The Contractor shall prepare and submit a Non-Disclosure Agreement (NDA) to the Contracting Officer prior to access of government information or the commencement of work at CDC.

(b) The NDA made part of this clause, exhibit I and II, is required in service contracts where positions and/or functions proposed to be filled by contractor’s employees will have access to non-public and procurement-sensitive information. The NDA also requires contractor’s employees properly identify themselves as employees of a contractor when communicating or interacting with CDC employees, employees of other governmental entities (when communication or interaction relates to the contractor’s work with the CDC), and members of the public. The Federal Acquisition Regulation (FAR) 37.114 (c), states “All contractor personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public or Congress that they are Government officials, unless, in the judgment of the agency, no harm can come from failing to identify themselves. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.”

(c) The Contractor shall inform employees of the identification requirements by which they must abide and monitor employee compliance with the identification requirements.

(d) During the contract performance period, the Contractor is responsible to ensure that all additional or replacement contractors’ employees sign a NDA and it is submitted to the Contracting Officer prior to commencement of their work with the CDC.

(e) Contractor employees in designated positions or functions that have not signed the appropriate NDA shall not have access to any non-public, procurement sensitive information or participate in government meeting where sensitive information may be discussed.

(f) The Contractor shall prepare and maintain a current list of employees working under NDAs and submit to the Contracting Officer upon request during the contract period of performance. The list should at a minimum include: contract number, employee’s name, position, date of hire and

(g) NDA requirement.

L. Observance of Legal Holidays and Facility Closure (Government Facilities Performance) (Feb 2011)

(1) Holidays
Government personnel observe the following listed days as holidays:

Washington’s Birthday
Memorial Day
Independence Day
Labor Day
Veterans’ Day
Thanksgiving Day
Christmas Day
New Year’s Day
Columbus Day
Martin Luther King Day

Any other day designated by Federal Statute
Any other day designated by Executive Order
Any other day designated by Presidential proclamation

For purposes of contract performance, the Contractor shall observe the above holidays on the date observed by the Government. Observance of such days shall not be cause for an additional period of performance or entitlement to compensation except as otherwise set forth in the contract. No form of holiday or other premium compensation will be reimbursed, however this does not preclude reimbursement for overtime work authorized in writing by the Contracting Officer.

(2) Unscheduled Facility Closures

In the event Government facilities are closed due to inclement weather, potentially hazardous or unsafe conditions, or other special circumstances, contractor personnel assigned to work within those facilities are automatically dismissed. Notwithstanding the terms of this clause, the contractor shall comply with any specific contract terms that require a level of ongoing support for critical operations during times of facility closure. The contractor may also continue to provide support under a scheduled telework arrangement in accordance with the terms of the contract if the contract expressly authorizes telework in writing.

(3) Cost Impact

Accounting for costs associated with an unscheduled facility closure is unique to each contract and depends upon a number of factors such as:

• Contract type, e.g. Fixed Price, Time and Materials, or Cost Reimbursement.
• Contractor’s established management and accounting practices for unproductive time.
• The inclusion and applicability of other contract clauses.
• The ability of the contractor to mitigate costs by reassigning employees to work on
other contracts, to work from a different facility, or to work remotely from home in accordance with contract telework provisions.
• Whether the contractor works onsite

L. Section 508 of the Rehabilitation Act (29 USC 794d)
Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d) requires Federal agencies to purchase electronic and information technologies (EIT) that meet specific accessibility standards. All final deliverables must comply with applicable Section 508 accessibility standards, and CDC reserves the right to reject deliverables that fail to meet the standards. Remediation of any materials that do not comply with the applicable provisions of 36 CFR Part 1194 as set forth in the SOW or PWS, shall be the responsibility of the contractor or consultant retained to produce the Web- suitable content or communications material. Regardless of format, all electronic documents – including text, audio or video – must conform to applicable Section 508 standards to allow federal employees and members of the public with disabilities to access information that is comparable to information provided to persons without disabilities.
The following Section 508 provisions apply to the content or communications material identified in this SOW or PWS:
36 CFR 1194.22, .31, and .41
Documents must be in unlocked form. Acceptance checklists for various file formats are available at
(End of Clause)


The Contract Officer Representative (COR) for this procurement will be:

The Technical Monitor for this procurement will be:

SECTION 12 – Quality Assurance Surveillance Plan (QASP)

The Contractor shall meet the requirements of the Quality Assurance Surveillance Plan (QASP).

1.0 Introduction

1.1 Since this is a Performance-Based Contract, the Government must effectively validate in a timely manner the performance of the Contractor in meeting the services required. This QASP provides a systematic surveillance method for the services, and describes the methodology by which the Contractor’s performance will be monitored.

1.2 The principal focus of the surveillance system is the Contractor’s performance of the indicators identified in the Performance-Based Matrix in Column 1 of the Performance Based Statement of Work (PBPWS). Therefore, the QASP surveillance standards are identical to those in IC.

1.3 This QASP will be used to provide surveillance for the task order.

1.4 For the purpose of this plan, AGENCY considers the FAR Clause 52.246-6 Inspection Time and Materials and Labor-Hour to meet the FAR Part 37.601 criteria for establishing a procedure for reduction of price or fee of a contract.

1.5 This QASP:

1.5.1 Identifies the services and products that will be measured.
1.5.2 Establishes the specific standards of performance for each required output.
1.5.3 Establishes the responsibilities for performing the measurement.
1.5.4 Defines the Government role in overseeing the performance.
1.5.5 Provides for feedback to the Contractor regarding quality, quantity, and timeliness of the service outputs.
1.5.6 Establishes timeframes for communicating performance improvements.

2.0 Methods of Surveillance

2.1 The Performance-Based Matrix lists the services to be monitored and the standards to be applied.

2.2 This QASP is based on the premise the Government desires to maintain a quality standard for acquisition support services.

2.3 The Contractor, and not the Government, is responsible for management and quality control actions to meet the terms of the contract. The role of the Government is quality assurance to ensure contract standards are achieved.

2.4 In this contract the Contractor quality control program is the basis for service quality. The Contractor is required to only deliver acquisition support services that conform to the requirements of the contract.

3.0 Roles and Responsibilities

3.1 The Contractor’s primary responsibility is to ensure all requirements are met at the required quality level. The Government shall ensure this responsibility has been met before payment is made to the Contractor. The primary Government team members are the Contracting Officer’s Technical Representatives (COTRs) and the Contracting Officer (CO).
3.2. The CO has the overall responsibility for overseeing the Contractor’s performance. The CO is responsible for monitoring Contractor performance in the areas of contract compliance, contract management, and the resolution of all issues relative to the language of the contract.

3.3 The CORs are responsible for directly monitoring, assessing, recording, and reporting on the technical performance of the Contractor. The CORs will have primary responsibility for signing off on all invoices and documenting the inspection and evaluation of the Contractor’s performance.

3.4 The CORs will work with staff and the Contractor to ensure good communication and resolve any problems not requiring the CO’s authority.

4.0 Surveillance:

The PO will evaluate the performance objectives through periodic inspections during each service month.

4.1 The following information will be included:
4.1.1 Contract paragraph number referencing the requirement.
4.1.2 A short description of the requirement for which surveillance is to be undertaken.
4.1.3 Date, time, and location of surveillance.
4.1.4 Results of surveillance.
4.1.5 Signature of individual accomplishing the surveillance.
4.2 All performance must be documented, whether acceptable or unacceptable. When unacceptable performance is documented, the COTRs shall take the following actions:
4.2.1 If Government actions caused the unacceptable performance, take steps to prevent it in the
4.2.2 If the Contractor’s performance is unacceptable, inform the Contractor’s representative of the unacceptable performance and the reasons why it is unacceptable.
4.2.3 If the Contractor wants to dispute the results of the surveillance, refer it to the CO for
4.3 Performance should not be determined unacceptable until all possible contributing factors have been considered.
4.4 For required tasks not shown on the Performance-Based Matrix, the Government still retains the right to inspect any item included in the contract. These services will be inspected periodically and the results provided to the CO.

5.0 Standards
All standards in the Performance-Based Matrix must be met. All deliverable dates and other contractual completion dates must also be met. If any of the standards are not met, the Government shall receive consideration from the Contractor for breach of contract.
5.1 Late performance is inexcusable unless the Contractor can justify all of the following:
5.1.1 The delay was not the Contractor’s fault.
5.1.2 The delay was not foreseeable.
5.1.3 It was beyond the Contractor’s control to avoid the delay.
5.2 All work shall be performed in accordance with the Performance-Based Work Statement. The COR shall not consider the services complete until all deficiencies have been corrected.
5.3 The COR shall determine whether the failure was a minor non-conformance or a substantive non-conformance.

6.0 Procedures

The Government will inspect performance requirements to ensure contractor compliance and record results of inspection, noting the date and time of inspection. Unacceptable performance and complaints shall be referred to the CO for investigation and validation. The CO will investigate and validate the unacceptable performance and/or customer input. The Contractor shall be given a reasonable amount of time after notification to correct the unacceptable performance and report to the CO that the deficiency has been corrected. If deficiencies are not corrected, the PO will notify the CO and recommend a course of action.

7.0 Contract Performance Evaluation

7.1 FAR 42.15 – Contractor Performance Information establishes the Government’s responsibility for recording and maintaining contractor performance information. This requirement does not apply to procedures used in determining incentive awards or other incentive systems, although the two systems should be mutually supporting.

7.2 FAR 42.1501 – Past performance information is relevant information for future source selection purposes, regarding a Contractor’s actions under previously awarded contracts. It includes, for example, the Contractor’s record of conforming to contract requirements and to standards of good workmanship; the Contractor’s record of forecasting and controlling costs; the Contractor’s adherence to contract schedules, including the administrative aspects of performance; the Contractor’s history of reasonable and cooperative behavior and commitment to customer satisfaction; and generally, the Contractor’s business-like concern for the interest of the customers.

7.3 The general procedures to be used are addressed in the following FAR section.

42.1503 Procedures:

(a) Agency procedures for the past performance evaluation system shall generally provide for input to the evaluations from the technical office, contracting office and, where appropriate, end users of the product or service. (b) Agency evaluations of contractor performance prepared under this subpart shall be provided to the contractor as soon as practicable after completion of the evaluation. Contractors shall be given a minimum of 30 days to submit comments, rebutting statements, or additional information. Agencies shall provide for review at a level above the CO to consider disagreements between the parties regarding the evaluation. The ultimate conclusion on the performance evaluation is a decision of the contracting agency. Copies of the evaluation, contractor response, and review comments, if any, shall be retained as part of the evaluation. These evaluations may be used to support future award decisions, and should therefore be marked “Source Selection Information”.

All data files, reports, and correspondence should be submitted to the CDC Contracting Officers Representative (COR) via email. Deliverables will include a monthly comprehensive report on the status of the project.

(End of Clause)

VIII. Contract Officer Representative and Technical Monitor
The Contract Officer Representative will be:

The Project Officer for this procurement is:

SECTION XII —– PAYMENT TERMS (note if and how partial payments are allowed).

Payment will be made in accordance with the line items established herein and in accordance with FAR 52.232-25, Prompt Payment, which states that the due date for making invoice payments shall be the 30th day after the designated billing office (see block 21 of the order) has received a proper invoice from the vendor or the 30th day after Government acceptance of the services performed by the vendor, whichever is later.

This contract action is for a services for which the government intends to solicit and negotiate with only one source under the authority of FAR 13.106-1(b) (SAP) and 41 U.S.C 3304(a) (1). Interested persons may identify their interest and capability to respond to the requirement or submit proposals.
The notice of intent is not a request for competitive quotations; however, all quotations/responses received within (15) days of the issuance of this notice will be considered by the Government. A determination by the Government not to compete this proposed contract based upon responses to this notice is solely within the discretion of the Government. Information received will normally be considered solely for the purpose of determining whether to conduct a competitive procurement. Any quotation/response should be e-mailed to purchasing agent Rebecca Mullenax at by COB on May 11, 2018.

Response Date:

Sol Number:


Who are we?

From publishing the first national directory of public sector contracts, to being the first to market with our online Tracker solution, we have been the true pioneers of technology and innovation in the public sector marketplace. Throughout our 39 years, we have continued to evolve and chart new territory – placing our customers at the heart of everything we do. Take your business to the next level with Tracker now.

If you request a demo today!

Download your Free UK Defence Industry Report

Get SAAS-Y This Summer with DCI

A member of our sales team will give you a call to discuss your business with you and create a demo personalised to your business and sector needs.

Start Your Free Trial Today

Download your Free UK Defence Industry Report

Download your Free UK Defence Industry Report

When you sign up for a 3 day free trial or demo.

Limited time only

    BiP Solutions owns DCI and we look after your details carefully. We offer a range of products, services and events (some of which are free) that help buyers tender more efficiently and suppliers find, bid for and win public and private sector contracts. Only tick this box if you wish to receive information about these. We will never share your details with third parties and you will have the opportunity of opting out of communications every time we contact you. For further details, please see our Privacy Policy