BioNumerics 100 user network license (all modules)

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Federal Acquisition Requirements (FAR) Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; quotes are being requested, and a written solicitation will not be issued. The solicitation number for this requirement is 30386 and is hereby issued as a Request for Quote (RFQ) using FAR Subpart 13.5 Simplified Acquisition Procedures. The Centers for Disease Control and Prevention intends to award a firm-fixed-price purchase order for the following requirement, please either fill in the dollar amounts or provide a separate excel spreadsheet containing the same information including a list of line item number(s) and items, quantities, units of measure, and options, if applicable: BRAND NAME REQUIRED BioNumerics, a molecular subtyping analysis software that combines information from various genomic and phenotypic sources into a global database and is able to conduct conclusive analyses that meets all of the requirements for Advanced Molecular Detection (AMD) participating programs and partners. This software is already in use at CDC in several programs, including PulseNet, and many participating public health laboratories. The scientists at CDC and in the PH network, consisting of state health departments, local health departments, and federal agencies (CDC, USDA/FSIS, and FDA) have extensive experience with this software and have massive amounts of data that is currently managed, analyzed and exchanged in this format. SEE ATTACHED RFQ Your quote shall include the following: - Total Price for CLINs 0001 -4002 - Capabilities in accordance with the Request for Quote and Evaluation Factors The quote format is at the discretion of the offeror. It is the offeror's responsibility to be familiar with the applicable clauses and provisions. Clauses and provisions may be accessed via the Internet at website http://farsite.hill.af.mil. This solicitation document and incorporated provisions and clauses are those in effect through the Federal Acquisition Circular (FAC) 2019-01 (Dec 20, 2018). This acquisition is set aside for small business under North American Industry Classification System (NAICS) code 511210. A Firm-Fixed Price purchase order will be issued in writing to the successful offeror. To be eligible to receive an award resulting from this solicitation, contractor must be registered in the System for Award Management. To register apply via the Internet at http://www.sam.gov. For questions on registration contact Federal Service Desk at +1 (555) 000-0000. Include FAR 52.212-3, Offeror Representations and Certifications with Offer or indicate if it is available online at SAM.gov. No telephonic quotes will be processed. Questions must be received no later than 11:00 A.M., Eastern Standard Time on March 18, 2019. Quotes must be received no later than 11:00 A.M., Eastern Standard Time on March 21, 2019. Year Please send any questions and quotes to William Brannen at contact@example.gov. Attachments: 1. Request for Quote (RFQ) Line Items ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE 0001 BioNumerics Full Configuration 100-user Network Licneses dongle 915-551-377 100 user POP 9/30/19-9/29/20 100 Each 0002 BioNumerics Full Configuration 10 internet Licenses SN002-238-874 quantity 10 POP 9/30/19-9/29/20 10 Each Option 1 Year 2 Items: ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE 1001 BioNumerics Full Configuration 100-user Network Licneses dongle 915-551-377 100 user POP 9/30/20-9/29/21 100 Each 1002 BioNumerics Full Configuration 10 internet Licenses SN002-238-874 quantity 10 POP 9/30/20-9/29/21 10 Each Option 2 Year 3 Items: ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE 2001 BioNumerics Full Configuration 100-user Network Licneses dongle 915-551-377 100 user POP 9/30/21-9/29/22 100 Each 2002 BioNumerics Full Configuration 10 internet Licenses SN002-238-874 quantity 10 POP 9/30/21-9/29/22 10 Each Option 3 Year 4 Items: ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE 3001 BioNumerics Full Configuration 100-user Network Licneses dongle 915-551-377 100 user POP 9/30/22-9/29/23 100 Each 3002 BioNumerics Full Configuration 10 internet Licenses SN002-238-874 quantity 10 POP 9/30/22-9/29/23 10 Each Option 4 Year 4 Items: ITEM SUPPLIES / SERVICES QTY / UNIT UNIT PRICE EXTENDED PRICE 4001 BioNumerics Full Configuration 100-user Network Licneses dongle 915-551-377 100 user POP 9/30/23-9/29/24 100 Each 4002 BioNumerics Full Configuration 10 internet Licenses SN002-238-874 quantity 10 POP 9/30/23-9/29/24 10 Each Statement of Work Period of Performance: 9/30/2019-9/29/2020 baseperiod 9/30/2020-9/29/2021 option1, year2 9/30/2021-9/29/2022 option 2, year3 9/30/2022-9/29/2023 option 3, year4 9/30/2023-9/29/2024 option 4, year5 Title: Applied Maths, BioNumerics Software License. SECTION 1 - BACKGROUND As CDC programs continue to incorporate AMD based methods into their surveillance, reference and outbreak detection systems, reliable software systems are required to analyze these more complex data. This acquisition includes a 100 seat multi-user network license for BioNumerics (bioMerieux, Applied-Maths), 10 off-site internet licenses and all associated upgrades and support during a 12 month period of performance, beginning 9/30/2018. BioNumerics is a commercial, off-the-shelf software application that is used for the analysis, comparison and visualization of conventional gel, phenotypic and genomic sequencing data. It is widely used by CDC scientific staff, and the broader public health community for the analysis of molecular epidemiologic data, and has a 21 year history as the foundational software of PulseNet. OAMD currently maintains consolidated site licensing for the majority of CDC users, and a limited group of external partners and collaborators. This acquisition supports this critical requirement, by extending licensure for 100 simultaneous CDC users, and 10 external users, from programs across CDC's four infectious disease centers. OAMD has maintained consolidated licensing for BioNumerics since 2015. This consolidated licensing replaced multiple individual licenses, and allowed for significant cost-savings and efficiency in license management and coordination. OAMD continues to monitor license utilization, and has made minor adjustments and expansions to site licensing, according to changes in demand. SUBSECTION A - DEFINITIONS AMD advanced molecular detection OAMD Office of Advanced molecular Detection SECTION 2 - PURPOSE The purpose of this procurement is to renew 100 seat Multi-User Network License (MUNL) of the BioNumerics Client software and 10 BioNumerics Client off-site internet licenses. SECTION 3 - SCOPE OF WORK The contractor will provide license and phone support for the following software ONE (1) Base period 1. 100 seat Multi-User Network License (MUNL) for BioNumerics Client software 2. 10 BioNumerics Client off-site internet licenses 3. Continually provide subsequent upgraded releases to the Bionumerics server and all user licenses to the latest versions during term of contract 4. Existing BioNumerics server licenses are included for support and upgrade. 5. Provide MUNL and BioNumerics server upgrades released during POP including extra functionality in modules and/or plugins. TWO (2)-OPTIONAL for 4 X 12 month period 1. 100 seat Multi-User Network License (MUNL) for BioNumerics Client software 2. 10 BioNumerics Client off-site internet licenses 3. Continually provide subsequent upgraded releases to the Bionumerics server and all user licenses to the latest versions during term of contract 4. Existing BioNumerics server licenses are included for support and upgrade. 5. Provide MUNL and BioNumerics server upgrades released during POP including extra functionality in modules and/or plugins. SECTION 4 - TASKS TO BE PERFORMED Contractor software licenses and suppport 1. Provide Maximum 100 seat Multi-User Network License (MUNL) for BioNumerics Client software. 2. Provide 10 off-site BioNumerics Client internet licenses 3. Provide telephone and email support services 4. Continually provide subsequent upgraded releases to the Bionumerics server and all user licenses to the latest versions during term of contract 5. Applications and executables for the wgMLST and other sequence analysis based algorithms on the Bionumerics calculation engine 6. Existing BioNumerics server licenses are included for support and upgrade. 7. Provide MUNL and BioNumerics server upgrades released during POP including extra functionality in modules and/or plugins. SECTION 5 - GOVERNMENT FURNISHED MATERIALS No Government Furnished Materials SECTION 7 - DELIVERABLES/REPORTING SCHEDULE Base period Items Description Quantity or No. of Copies Delivery Date Deliver To MUNL BioNumerics Client Software Network License and Maintenance 100 On or before 9/30/2019 COR & OAMD Science Officer BioNumerics Client Off-site internet license Off-site internet license 10 On or before 9/30/2019 COR and OAMD Science Officer Option Periods year 2-5 Items Description Quantity or No. of Copies Delivery Date Deliver To MUNL BioNumerics Client Software Network License and Maintenance 100 First day of option PoP or before. COR and OAMD Science Officer BioNumerics Client Off-site internet license Off-site internet license 10 First day of option PoP or before. COR OAMD Science Officer SECTION 8 - REFERENCE MATERIALS NA SECTION 11 - EVALUATION FACTORS Potential vendors must be able to provide the brand name Multi-User Network License (MUNL) and internet license for BioNumerics Client software and required phone support over the course of the base and option periods. SECTION 11A Acquisition is for software licenses maintenance The below information complies with CDC Security and Privacy compliance requirements for Federal Information Security Modernization Act of 2014 (FISMA 2014) Security Compliance Y If the contract is the vendor to provide the products as hardware and/or software to CDC, the vendor shall comply with the applicable IT security references Standards 1, 2, and 5. Standard-1: Procurements Requiring Information Security and/or Physical Access Security A. Baseline Security Requirements 1) Applicability. The requirements herein apply whether the entire contract or order (hereafter "contract"), or portion thereof, includes either or both of thefollowing: a. Access (Physical or Logical) to Government Information: A Contractor (and/or any subcontractor) employee will have or will be given the ability to have, routine physical (entry) or logical (electronic) access to government information. b. Operate a Federal System Containing Information: A Contractor (and/or any subcontractor) employee will operate a federal system and information technology containing data that supports the HHS mission. In addition to the Federal Acquisition Regulation (FAR) Subpart 2.1 definition of "information technology" (IT), the term as used in this section includes computers, ancillary equipment (including imaging peripherals, input, output, and storage devices necessary for security and surveillance), peripheral equipment designed tobe controlled by the central processing unit of a computer, software, firmware and similar procedures, services (including support services), and related resources. 2) Safeguarding Information and Information Systems. In accordance with the Federal Information Processing Standards Publication (FIPS)199, Standards for Security Categorization of Federal Information and Information Systems, the Contractor (and/or any subcontractor) shall: a. Protect government information and information systems in order toensure: - Confidentiality, which means preserving authorized restrictions on access and disclosure, based on the security terms found in this contract, including means for protecting personal privacy and proprietary information; - Integrity, which means guarding against improper information modification or destruction, and ensuring information non-repudiation and authenticity; and - Availability, which means ensuring timely and reliable access to and use of information. b. Provide security for any Contractor systems, and information contained therein, connected to an HHS network or operated by the Contractor on behalf of HHS regardless of location. In addition, if new or unanticipated threats or hazards are discovered by either the agency or contractor, or if existing safeguards have ceased to function, the discoverer shall immediately, within one (1) hour or less, bring the situation to the attention of the other party. c. Adopt and implement the policies, procedures, controls, and standards required by the HHS Information Security Program to ensure the confidentiality, integrity, and availability of government information and government information systems for which the Contractor is responsible under this contract or to which the Contractor may otherwise have access under this contract. Obtain the HHS Information Security Program security requirements, outlined in the HHS Information Security and Privacy Policy (IS2P), by contacting the CO/COR or contact@example.gov. d. Comply with the Privacy Act requirements and tailor FAR clauses as needed. 3) Information Security Categorization. In accordance with FIPS 199 and National Institute of Standards and Technology (NIST) Special Publication (SP) 800-60, Volume II: Appendices to Guide for Mapping Types of Information and Information Systems to Security Categories, Appendix C, and based on information provided by the ISSO, CISO, or other security representative, the risk level for each Security Objective and the Overall Risk Level, which is the highest watermark of the three factors (Confidentiality, Integrity, and Availability) of the information or information system are the following: Confidentiality: [ X ] Low [ ] Moderate [ ] High Integrity: [ ] Low [ X ] Moderate [ ] High Availability: [ X ] Low [ ] Moderate [ ] High Overall Risk Level: [ ] Low [ X ] Moderate [ ] High Based on information provided by the ISSO, Privacy Office, system/data owner, or other security or privacy representative, it has been determined that this solicitation/contract involves: [ X ] No PII [ ] Yes PII 4) Personally Identifiable Information (PII). Per the Office of Management and Budget (OMB) Circular A-130, "PII is information that can be used to distinguish or trace an individual's identity, either alone or when combined with other information that is linked or linkable to a specific individual." Examples of PII include, but are not limited to the following: social security number, date and place of birth, mother's maiden name, biometric records, etc. PII Confidentiality Impact Level has been determined to be: [ X ] Low [ ] Moderate [ ] High 5) Controlled Unclassified Information (CUI). CUI is defined as "information that laws, regulations, or Government-wide policies require to have safeguarding or dissemination controls, excluding classified information." The Contractor (and/or any subcontractor) must comply with Executive Order 13556, Controlled Unclassified Information, (implemented at 32 CFR, part 2002) when handling CUI. 32 C.F.R. 2002.4(aa) As implemented the term "handling" refers to "...any use of CUI, including but not limited to marking, safeguarding, transporting, disseminating, re-using, and disposing of the information." 81 Fed. Reg. 63323. All sensitive information that has been identified as CUI by a regulation or statute, handled by this solicitation/contract, shall be: a. marked appropriately; b. disclosed to authorized personnel on a Need-To-Knowbasis; c. protected in accordance with NIST SP 800-53, Security and Privacy Controls for Federal Information Systems and Organizations applicable baseline if handled by a Contractor system operated on behalf of the agency, or NIST SP 800-171, Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations if handled by internal Contractor system; and d. returned to HHS control, destroyed when no longer needed, or held until otherwise directed. Destruction of information and/or data shall be accomplished in accordance with NIST SP 800-88, Guidelines for Media Sanitization. 6) Protection of Sensitive Information. For security purposes, information is or may be sensitive because it requires security to protect its confidentiality, integrity, and/or availability. The Contractor (and/or any subcontractor) shall protect all government information that is or may be sensitive in accordance with OMB Memorandum M-06-16, Protection of Sensitive Agency Information by securing it with a FIPS 140-2 validated solution. 7) Confidentiality and Nondisclosure of Information. Any information provided to the contractor (and/or any subcontractor) by HHS or collected by the contractor on behalf of HHS shall be used only for the purpose of carrying out the provisions of this contract and shall not be disclosed or made known in any manner to any persons except as may be necessary in the performance of the contract.The Contractor assumes responsibility for protection of the confidentiality of Government records and shall ensure that all work performed by its employees and subcontractors shall be under the supervision of the Contractor. Each Contractor employee or any of its subcontractors to whom any HHS records may be made available or disclosed shall be notified in writing by the Contractor that information disclosed to such employee or subcontractor can be used only for that purpose and to the extent authorized herein. The confidentiality, integrity, and availability of such information shall be protected in accordance with HHS and [CDC] policies. Unauthorized disclosure of information will be subject to the HHS/[CDC] sanction policies and/or governed by the following laws and regulations: a. 18 U.S.C. 641 (Criminal Code: Public Money, Property or Records); b. 18 U.S.C. 1905 (Criminal Code: Disclosure of Confidential Information); and c. 44 U.S.C. Chapter 35, Subchapter I (Paperwork Reduction Act). 8) Internet Protocol Version 6 (IPv6). All procurements using Internet Protocol shall comply with OMB Memorandum M-05-22, Transition Planning for Internet Protocol Version 6 (IPv6). . 9) Government Websites. All new and existing public-facing government websites must be securely configured with Hypertext Transfer Protocol Secure (HTTPS) using the most recent version of Transport Layer Security (TLS). In addition, HTTPS shall enable HTTP Strict Transport Security (HSTS) to instruct compliant browsers to assume HTTPS at all times to reduce the number of insecure redirects and protect against attacks that attempt to downgrade connections to plain HTTP. For internal-facing websites, the HTTPS is not required, but it is highly recommended. 10) Contract Documentation. The Contractor shall use provided templates, policies, forms and other agency documents to comply with contract deliverables as appropriate. 11) Standard for Encryption. The Contractor (and/or any subcontractor) shall: a. Comply with the HHS Standard for Encryption of Computing Devices and Information to prevent unauthorized access to government information. b. Encrypt all sensitive federal data and information (i.e., PII, protected health information [PHI], proprietary information, etc.) in transit (i.e., email, network connections, etc.) and at rest (i.e., servers, storage devices, mobile devices, backup media, etc.) with FIPS 140-2 validated encryption solution. c. Secure all devices (i.e.: desktops, laptops, mobile devices, etc.) that store and process government information and ensure devices meet HHS and CDC-specific encryption standard requirements. Maintain a complete and current inventory of all laptop computers, desktop computers, and other mobile devices and portable media that store or process sensitive government information (includingPII). d. Verify that the encryption solutions in use have been validated under the Cryptographic Module Validation Program to confirm compliance with FIPS 140-2. The Contractor shall provide a written copy of the validation documentation to theCOR. e. Use the Key Management system on the HHS personal identification verification (PIV) card or establish and use a key recovery mechanism to ensure the ability for authorized personnel to encrypt/decrypt information and recover encryption keys. Encryption keys shall be provided to CDC Office of Chief Information Security Officer(OCISO). 12) Contractor Non-Disclosure Agreement (NDA). Each Contractor (and/or any subcontractor) employee having access to non-public government information under this contract shall complete the CDC non-disclosure agreement, as applicable. A copy of each signed and witnessed NDA shall be submitted to the Contracting Officer (CO) and/or CO Representative (COR) prior to performing any work under this acquisition. 13) Privacy Threshold Analysis (PTA)/Privacy Impact Assessment (PIA) - The Contractor shall assist the CDC Senior Official for Privacy (SOP) or designee with conducting a PTA for the information system and/or information handled under this contract in accordance with HHS policy and OMB M-03-22, Guidance for Implementing the Privacy Provisions of the E- Government Act of 2002. a. The Contractor shall assist the CDC SOP or designee in reviewing the PIA at least every three years throughout the system development lifecycle (SDLC)/information lifecycle, or when determined by the CDC SOP that a review is required based on a major change to the system (e.g., new uses of information collected, changes to the way information is shared or disclosed and for what purpose, or when new types of PII are collected that could introduce new or increased privacy risks), whichever comes first. B. Training 1) Mandatory Training for All Contractor Staff. All Contractor (and/or any subcontractor) employees assigned to work on this contract shall complete the applicable HHS/CDC Contractor Information Security Awareness, Privacy, and Records Management training (provided upon contract award) before performing any work under this contract. Thereafter, the employees shall complete CDC Security Awareness Training (SAT), Privacy, and Records Management training at least annually, during the life of this contract. All provided training shall be compliant with HHS trainingpolicies. 2) Role-based Training. All Contractor (and/or any subcontractor) employees with significant security responsibilities (as determined by the program manager) must complete role- based training (RBT) within 60 days of assuming their new responsibilities. Thereafter, they shall complete RBT at least annually in accordance with HHS policy and the HHS Role- Based Training (RBT) of Personnel with Significant Security Responsibilities Memorandum. All HHS employees and contractors with SSR who have not completed the required training within the mandated timeframes shall have their user accounts disabled until they have met their RBT requirement. Training Records. The Contractor (and/or any subcontractor) shall maintain training records for all its employees working under this contract in accordance with HHS policy. A copy of the training records shall be provided to the CO and/or COR within 30 days after contract award and annually thereafter or upon request. C. Rules of Behavior 1) The Contractor (and/or any subcontractor) shall ensure that all employees performing on the contract comply with the HHS Information Technology General Rules of Behavior. 2) All Contractor employees performing on the contract must read and adhere to the Rules of Behavior before accessing Department data or other information, systems, and/or networks that store/process government information, initially at the beginning of the contract and at least annually thereafter, which may be done as part of annual CDC Security Awareness Training. If the training is provided by the contractor, the signed ROB must be provided as a separate deliverable to the CO and/or COR per defined timelines above. D. Incident Response FISMA defines an incident as "an occurrence that (1) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (2) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines incidents as events involving cybersecurity and privacy threats, such as viruses, malicious user activity, loss of, unauthorized disclosure or destruction of data, and so on. A privacy breach is a type of incident and is defined by Federal Information Security Modernization Act (FISMA) as the loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where (1) a person other than an authorized user accesses or potentially accesses personally identifiable information or (2) an authorized user accesses or potentially accesses personally identifiable information for an other than authorized purpose. OMB Memorandum M-17-12, "Preparing for and Responding to a Breach of Personally Identifiable Information" (03 January 2017) states: Definition of an Incident: An occurrence that (1) actually or imminently jeopardizes, without lawful authority, the integrity, confidentiality, or availability of information or an information system; or (2) constitutes a violation or imminent threat of violation of law, security policies, security procedures, or acceptable use policies. Definition of a Breach: The loss of control, compromise, unauthorized disclosure, unauthorized acquisition, or any similar occurrence where (1) a person other than an authorized user accesses or potentially accesses personally identifiable information or (2) an authorized user accesses or potentially accesses personally identifiable information for an other than authorized purpose. It further adds: A breach is not limited to an occurrence where a person other than an authorized user potentially accesses PII by means of a network intrusion, a targeted attack that exploits website vulnerabilities, or an attack executed through an email message or attachment. A breach may also include the loss or theft of physical documents that include PII and portable electronic storage media that store PII, the inadvertent disclosure of PII on a public website, or an oral disclosure of PII to a person who is not authorized to receive that information. It may also include an authorized user accessing PII for an other than authorized purpose. The HHS Policy for IT Security and Privacy Incident Reporting and Response further defines a breach as "a suspected or confirmed incident involving PII". Contracts with entities that collect, maintain, use, or operate Federal information or information systems on behalf of CDC shall include the following requirements: 1) The contractor shall cooperate with and exchange information with CDC officials, as deemed necessary by the CDC Breach Response Team, to report and manage a suspected or confirmed breach. 2) All contractors and subcontractors shall properly encrypt PII in accordance with OMB Circular A-130 and other applicable policies, including CDC-specific policies, and comply with HHS-specific policies for protecting PII.To this end, all contractors and subcontractors shall protect all sensitive information, including any PII created, stored, or transmitted in the performance of this contract so as to avoid a secondary sensitive information incident with FIPS 140-2 validatedencryption. 3) All contractors and subcontractors shall participate in regular training on how to identify and report a breach. 4) All contractors and subcontractors shall report a suspected or confirmed breach in any medium as soon as possible and no later than 1 hour of discovery, consistent with applicable CDC IT acquisitions guidance, HHS/CDC and incident management policy, and United States Computer Emergency Readiness Team (US-CERT) notification guidelines. To this end, the Contractor (and/or any subcontractor) shall respond to all alerts/Indicators of Compromise (IOCs) provided by HHS Computer Security Incident Response Center (CSIRC) or CDC Computer Incident Response Team (CSIRT) within 24 hours via email at contact@example.gov or telephone at 866-655- 2245, whether the response is positive or negative. 5) All contractors and subcontractors shall be able to determine what Federal information was or could have been accessed and by whom, construct a timeline of user activity, determine methods and techniques used to access Federal information, and identify the initial attack vector. 6) All contractors and subcontractors shall allow for an inspection, investigation, forensic analysis, and any other action necessary to ensure compliance with HHS/CDC Policy and the HHS/CDC Breach Response Plan and to assist with responding to a breach. 7) Cloud service providers shall use guidance provided in the FedRAMP Incident Communications Procedures when deciding when to report directly to US-CERT first or notify CDC first. 8) Identify roles and responsibilities, in accordance with HHS/CDC Breach Response Policy and the HHS/CDC Breach Response Plan. To this end, the Contractor shall NOT notify affected individuals unless and until so instructed by the Contracting Officer or designated representative. If so instructed by the Contracting Officer or representative, all notifications must be pre-approved by the appropriate CDC officials, consistent with HHS/CDC Breach Response Plan, and the Contractor shall then send CDC- approved notifications to affected individuals; and, 9) Acknowledge that CDC will not interpret report of a breach, by itself, as conclusive evidence that the contractor or its subcontractor failed to provide adequate safeguards for PII. E. Position Sensitivity Designations All Contractor (and/or any subcontractor) employees must obtain a background investigation commensurate with their position sensitivity designation that complies with Parts 1400 and 731 of Title 5, Code of Federal Regulations (CFR). F. Homeland Security Presidential Directive (HSPD)-12 The Contractor (and/or any subcontractor) and its employees shall comply with Homeland Security Presidential Directive (HSPD)-12, Policy for a Common Identification Standard for Federal Employees and Contractors; OMB M-05-24; FIPS 201, Personal Identity Verification (PIV) of Federal Employees and Contractors; HHS HSPD-12 policy; and Executive Order 13467, Part 1 - 1.2. Roster. The Contractor (and/or any subcontractor) shall submit a roster by name, position, e-mail address, phone number and responsibility of all staff working under this acquisition where the Contractor will develop, have the ability to access, or host and/or maintain a government information system(s). The roster shall be submitted to the COR and/or CO by the effective date of this contract. Any revisions to the roster as a result of staffing changes shall be submitted immediately upon change. The COR will notify the Contractor of the appropriate level of investigation required for each staff member. If the employee is filling a new position, the Contractor shall provide a position description and the Government will determine the appropriate suitability level. G. Contract Initiation and Expiration 1) General Security Requirements. The Contractor (and/or any subcontractor) shall comply with information security and privacy requirements, Enterprise Performance Life Cycle (EPLC) processes, HHS Enterprise Architecture requirements to ensure information is appropriately protected from initiation to expiration of the contract. All information systems development or enhancemen...