FBODaily.com | FedBizOpps: PRESOL | J | Preventive Service Maintenance

FBO DAILY - FEDBIZOPPS ISSUE OF JULY 30, 2017 FBO #5728
SOLICITATION NOTICE

J -- Preventive Service Maintenance

Notice Date: 7/28/2017
Notice Type: Combined Synopsis/Solicitation
NAICS: 811219 — Other Electronic and Precision Equipment Repair and Maintenance
Contracting Office: Department of the Army, U.S. Army Medical Command, REGIONAL HEALTH CONTRACT OFF CENTRAL, ATTN: MCAA GP L31 9V, 2539 GARDEN AVENUE, JBSA FT SAM HOUSTON, Texas, 78234-0000, United States
ZIP Code: 78234-0000
Solicitation Number: W81K00-17-T-0357
Archive Date: 8/19/2017
Point of Contact: Efren B. Ramirez, Phone: 2102214820
E-Mail Address: efren.b.ramirez.civ@mail.mil
(efren.b.ramirez.civ@mail.mil)
Small Business Set-Aside: N/A
Description: This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6 and FAR Part 13 Simplified Acquisition Procedures, 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 is W81K00-17-T-0357 and is issued as a Request for Quote (RFQ). This solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-95 and Defense Federal Acquisition Regulation Supplement Publication Notice (DPN) 20161222. This solicitation is for annual Preventive Service Maintenance on 15 MedStations for inpatient care at Bayne Jones Army Community Hospital, Fort Polk, Louisiana. The period of performance is 01 October 2017 thru 30 September 2018.The associated North American Industrial Classification System (NAICS) code for this procurement is 811219 with a size standard of with a size standard of $20,500,000.00. This procurement is being conducted as full and open competition. All eligible businesses may submit an offer, which will be considered. Offers are due by 4 August 2017, at 10:00 AM, Central Standard Time. The point of contact is Mr. Efren Ramirez at (210) 221-4820 or efren.b.ramirez.civ@mail.mil. Offers shall be submitted via e-mail. Questions shall be submitted via e-mail not later than 4 August 2017. No questions will be entertained after this date. PYXIS Maintenance FFP Provide Basic Service Maintenance on 15 Medstations and one Desktop CIISAFE. Also Includes 67 SupplyStations, 7 ProcedureStn and one JITrBUD - in accordance with the Performance Work Statement. Bidder must provide all labor, supplies, tools material, transportation, parts, and equipment to perform Preventive Maintenance (PM) in accordance with Addendum 52.212-2. FOB: Destination PURCHASE REQUEST NUMBER: 0011022916 AMOUNT CMR FFP CONTRACTOR MANPOWER REPORTING FOB: Destination PURCHASE REQUEST NUMBER: 0011022916 AMOUNT DELIVERY INFORMATION CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC 0001 POP 01-OCT-2017 TO 30-SEP-2018 N/A W2NK USA MEDDAC FT POLK W2NK USA MEDDAC FT POLK 7606 VIRGINIA AVENUE BLDG 4372 FORT POLK LA 71459-5110 210-221-7928 FOB: Destination W42CXW 0002 POP 01-OCT-2017 TO 30-SEP-2018 N/A (SAME AS PREVIOUS LOCATION) FOB: Destination W42CXW CLAUSES INCORPORATED BY REFERENCE 52.212-4 Contract Terms and Conditions--Commercial Items JAN 2017 ADDENDUM TO 52.212-4 (w) The non-FAR Part 12 discretionary FAR, DFARS, AFARS, and LOCAL clauses included herein are incorporated into this contract either by reference or in full text. If incorporated by reference, see clause 52.252-2 herein for locations where full text can be found. (End of Clause) CLAUSES INCORPORATED BY REFERENCE 52.204-9 Personal Identity Verification of Contractor Personnel JAN 2011 52.204-10 Reporting Executive Compensation and First-Tier Subcontract Awards OCT 2016 52.204-18 Commercial and Government Entity Code Maintenance JUL 2016 52.204-21 Basic Safeguarding of Covered Contractor Information Systems JUN 2016 52.222-3 Convict Labor JUN 2003 52.222-21 Prohibition Of Segregated Facilities APR 2015 52.222-26 Equal Opportunity SEP 2016 52.222-36 Equal Opportunity for Workers with Disabilities JUL 2014 52.222-50 Combating Trafficking in Persons MAR 2015 52.222-51 Exemption from Application of the Service Contract Labor MAY 2014 Standards to Contracts for Maintenance, Calibration, or Repair of Certain Equipment--Requirements 52.223-3 Hazardous Material Identification And Material Safety Data JAN 1997 52.223-5 Pollution Prevention and Right-to-Know Information MAY 2011 52.223-18 Encouraging Contractor Policies To Ban Text Messaging While Driving AUG 2011 52.225-13 Restrictions on Certain Foreign Purchases JUN 2008 52.232-18 Availability Of Funds APR 1984 52.232-33 Payment by Electronic Funds Transfer--System for Award Management JUL 2013 52.232-39 Unenforceability of Unauthorized Obligations JUN 2013 52.233-3 Protest After Award AUG 199652.233-4 Applicable Law for Breach of Contract Claim OCT 2004 252.203-7000 Requirements Relating to Compensation of Former DoD Official SEP 2011 252.203-7002 Requirement to Inform Employees of Whistleblower Rights SEP 2013 252.204-7003 Control Of Government Personnel Work Product APR 1992 252.225-7048 Export-Controlled Items JUN 2013 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports JUN 2012 252.232-7010 Levies on Contract Payments DEC 2006 CLAUSES INCORPORATED BY FULL TEXT 52.209-10 Prohibition on Contracting With Inverted Domestic Corporations. (NOV 2015) (a) Definitions. As used in this clause-- Inverted domestic corporation means a foreign incorporated entity that meets the definition of an inverted domestic corporation under 6 U.S.C. 395(b), applied in accordance with the rules and definitions of 6 U.S.C. 395(c). Subsidiary means an entity in which more than 50 percent of the entity is owned-- (1) Directly by a parent corporation; or (2) Through another subsidiary of a parent corporation. (b) If the contractor reorganizes as an inverted domestic corporation or becomes a subsidiary of an inverted domestic corporation at any time during the period of performance of this contract, the Government may be prohibited from paying for Contractor activities performed after the date when it becomes an inverted domestic corporation or subsidiary. The Government may seek any available remedies in the event the Contractor fails to perform in accordance with the terms and conditions of the contract as a result of Government action under this clause. (c) Exceptions to this prohibition are located at 9.108-2. (d) In the event the Contractor becomes either an inverted domestic corporation, or a subsidiary of an inverted domestic corporation during contract performance, the Contractor shall give written notice to the Contracting Officer within five business days from the date of the inversion event. (End of clause) 52.219-28 POST-AWARD SMALL BUSINESS PROGRAM REREPRESENTATION (JULY 2013) (a) Definitions. As used in this clause-- Long-term contract means a contract of more than five years in duration, including options. However, the term does not include contracts that exceed five years in duration because the period of performance has been extended for a cumulative period not to exceed six months under the clause at 52.217-8, Option to Extend Services, or other appropriate authority. Small business concern means a concern, including its affiliates, that is independently owned and operated, not dominant in the field of operation in which it is bidding on Government contracts, and qualified as a small business under the criteria in 13 CFR part 121 and the size standard in paragraph (c) of this clause. Such a concern is ``not dominant in its field of operation'' when it does not exercise a controlling or major influence on a national basis in a kind of business activity in which a number of business concerns are primarily engaged. In determining whether dominance exists, consideration shall be given to all appropriate factors, including volume of business, number of employees, financial resources, competitive status or position, ownership or control of materials, processes, patents, license agreements, facilities, sales territory, and nature of business activity. (b) If the Contractor represented that it was a small business concern prior to award of this contract, the Contractor shall rerepresent its size status according to paragraph (e) of this clause or, if applicable, paragraph (g) of this clause, upon the occurrence of any of the following: (1) Within 30 days after execution of a novation agreement or within 30 days after modification of the contract to include this clause, if the novation agreement was executed prior to inclusion of this clause in the contract. (2) Within 30 days after a merger or acquisition that does not require a novation or within 30 days after modification of the contract to include this clause, if the merger or acquisition occurred prior to inclusion of this clause in the contract. (3) For long-term contracts-- (i) Within 60 to 120 days prior to the end of the fifth year of the contract; and (ii) Within 60 to 120 days prior to the date specified in the contract for exercising any option thereafter. (c) The Contractor shall rerepresent its size status in accordance with the size standard in effect at the time of this rerepresentation that corresponds to the North American Industry Classification System (NAICS) code assigned to this contract. The small business size standard corresponding to this NAICS code can be found at http://www.sba.gov/content/table-small-business-size-standards. (d) The small business size standard for a Contractor providing a product which it does not manufacture itself, for a contract other than a construction or service contract, is 500 employees. (e) Except as provided in paragraph (g) of this clause, the Contractor shall make the representation required by paragraph (b) of this clause by validating or updating all its representations in the Representations and Certifications section of the System for Award Management (SAM) and its other data in SAM, as necessary, to ensure that they reflect the Contractor's current status. The Contractor shall notify the contracting office in writing within the timeframes specified in paragraph (b) of this clause that the data have been validated or updated, and provide the date of the validation or update. (f) If the Contractor represented that it was other than a small business concern prior to award of this contract, the Contractor may, but is not required to, take the actions required by paragraphs (e) or (g) of this clause. (g) If the Contractor does not have representations and certifications in SAM, or does not have a representation in SAM for the NAICS code applicable to this contract, the Contractor is required to complete the following rerepresentation and submit it to the contracting office, along with the contract number and the date on which the rerepresentation was completed: The Contractor represents that it ( ) is, ( X ) is not a small business concern under NAICS Code 811219- assigned to contract number. (End of clause) 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998) This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es): http://farsite.hill.af.mil (End of clause) 52.252-6 AUTHORIZED DEVIATIONS IN CLAUSES (APR 1984) (a) The use in this solicitation or contract of any Federal Acquisition Regulation (48 CFR Chapter 1) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the date of the clause. (b) The use in this solicitation or contract of any DoD FAR Supplement (48 CFR Chapter 2) clause with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation. (End of clause) 252.204-7012 SAFEGUARDING COVERED DEFENSE INFORMATION AND CYBER INCIDENT REPORTING (OCT 2016) (a) Definitions. As used in this clause-- Adequate security means protective measures that are commensurate with the consequences and probability of loss, misuse, or unauthorized access to, or modification of information. Compromise means disclosure of information to unauthorized persons, or a violation of the security policy of a system, in which unauthorized intentional or unintentional disclosure, modification, destruction, or loss of an object, or the copying of information to unauthorized media may have occurred. Contractor attributional/proprietary information means information that identifies the contractor(s), whether directly or indirectly, by the grouping of information that can be traced back to the contractor(s) (e.g., program description, facility locations), personally identifiable information, as well as trade secrets, commercial or financial information, or other commercially sensitive information that is not customarily shared outside of the company. Controlled technical information means technical information with military or space application that is subject to controls on the access, use, reproduction, modification, performance, display, release, disclosure, or dissemination. Controlled technical information would meet the criteria, if disseminated, for distribution statements B through F using the criteria set forth in DoD Instruction 5230.24, Distribution Statements on Technical Documents. The term does not include information that is lawfully publicly available without restrictions. Covered contractor information system means an unclassified information system that is owned, or operated by or for, a contractor and that processes, stores, or transmits covered defense information. Covered defense information means unclassified controlled technical information or other information, as described in the Controlled Unclassified Information (CUI) Registry at http://www.archives.gov/cui/registry/category- list.html, that requires safeguarding or dissemination controls pursuant to and consistent with law, regulations, and Governmentwide policies, and is-- (1) Marked or otherwise identified in the contract, task order, or delivery order and provided to the contractor by or on behalf of DoD in support of the performance of the contract; or (2) Collected, developed, received, transmitted, used, or stored by or on behalf of the contractor in support of the performance of the contract. Cyber incident means actions taken through the use of computer networks that result in a compromise or an actual or potentially adverse effect on an information system and/or the information residing therein. Forensic analysis means the practice of gathering, retaining, and analyzing computer-related data for investigative purposes in a manner that maintains the integrity of the data. Information system means a discrete set of information resources organized for the collection, processing, maintenance, use, sharing, dissemination, or disposition of information. Malicious software means computer software or firmware intended to perform an unauthorized process that will have adverse impact on the confidentiality, integrity, or availability of an information system. This definition includes a virus, worm, Trojan horse, or other code-based entity that infects a host, as well as spyware and some forms of adware. Media means physical devices or writing surfaces including, but is not limited to, magnetic tapes, optical disks, magnetic disks, large-scale integration memory chips, and printouts onto which covered defense information is recorded, stored, or printed within a covered contractor information system. Operationally critical support means supplies or services designated by the Government as critical for airlift, sealift, intermodal transportation services, or logistical support that is essential to the mobilization, deployment, or sustainment of the Armed Forces in a contingency operation. Rapidly report means within 72 hours of discovery of any cyber incident. Technical information means technical data or computer software, as those terms are defined in the clause at DFARS 252.227-7013, Rights in Technical Data--Noncommercial Items, regardless of whether or not the clause is incorporated in this solicitation or contract. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, technical orders, catalog-item identifications, data sets, studies and analyses and related information, and computer software executable code and source code. (b) Adequate security. The Contractor shall provide adequate security on all covered contractor information systems. To provide adequate security, the Contractor shall implement, at a minimum, the following information security protections: (1) For covered contractor information systems that are part of an information technology (IT) service or system operated on behalf of the Government, the following security requirements apply: (i) Cloud computing services shall be subject to the security requirements specified in the clause 252.239-7010, Cloud Computing Services, of this contract. (ii) Any other such IT service or system (i.e., other than cloud computing) shall be subject to the security requirements specified elsewhere in this contract. (2) For covered contractor information systems that are not part of an IT service or system operated on behalf of the Government and therefore are not subject to the security requirement specified at paragraph (b)(1) of this clause, the following security requirements apply: (i) Except as provided in paragraph (b)(2)(ii) of this clause, the covered contractor information system shall be subject to the security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, ``Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations'' (available via the internet at http://dx.doi.org/10.6028/NIST.SP.800-171) in effect at the time the solicitation is issued or as authorized by the Contracting Officer. (ii)(A) The Contractor shall implement NIST SP 800-171, as soon aspractical, but not later than December 31, 2017. For all contracts awarded prior to October 1, 2017, the Contractor shall notify the DoD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award. (B) The Contractor shall submit requests to vary from NIST SP 800-171 in writing to the Contracting Officer, for consideration by the DoD CIO. The Contractor need not implement any security requirement adjudicated by an authorized representative of the DoD CIO to be nonapplicable or to have an alternative, but equally effective, security measure that may be implemented in its place. (C) If the DoD CIO has previously adjudicated the contractor's requests indicating that a requirement is not applicable or that an alternative security measure is equally effective, a copy of that approval shall be provided to the Contracting Officer when requesting its recognition under this contract. (D) If the Contractor intends to use an external cloud service provider to store, process, or transmit any covered defense information in performance of this contract, the Contractor shall require and ensure that the cloud service provider meets security requirements equivalent to those established by the Government for the Federal Risk and Authorization Management Program (FedRAMP) Moderate baseline (https://www.fedramp.gov/resources/documents/) and that the cloud service provider complies with requirements in paragraphs (c) through (g) of this clause for cyber incident reporting, malicious software, media preservation and protection, access to additional information and equipment necessary for forensic analysis, and cyber incident damage assessment. (3) Apply other information systems security measures when the Contractor reasonably determines that information systems security measures, in addition to those identified in paragraphs (b)(1) and (2) of this clause, may be required to provide adequate security in a dynamic environment or to accommodate special circumstances (e.g., medical devices) and any individual, isolated, or temporary deficiencies based on an assessed risk or vulnerability. These measures may be addressed in a system security plan. (c) Cyber incident reporting requirement. (1) When the Contractor discovers a cyber incident that affects a covered contractor information system or the covered defense information residing therein, or that affects the contractor's ability to perform the requirements of the contract that are designated as operationally critical support and identified in the contract, the Contractor shall-- (i) Conduct a review for evidence of compromise of covered defense information, including, but not limited to, identifying compromised computers, servers, specific data, and user accounts. This review shall also include analyzing covered contractor information system(s) that were part of the cyber incident, as well as other information systems on the Contractor's network(s), that may have been accessed as a result of the incident in order to identify compromised covered defense information, or that affect the Contractor's ability to provide operationally critical support; and (ii) Rapidly report cyber incidents to DoD at http://dibnet.dod.mil. (2) Cyber incident report. The cyber incident report shall be treated as information created by or for DoD and shall include, at a minimum, the required elements at http://dibnet.dod.mil. (3) Medium assurance certificate requirement. In order to report cyber incidents in accordance with this clause, the Contractor or subcontractor shall have or acquire a DoD-approved medium assurance certificate to report cyber incidents. For information on obtaining a DoD-approved medium assurance certificate, see http://iase.disa.mil/pki/eca/Pages/index.aspx. (d) Malicious software. When the Contractor or subcontractors discover and isolate malicious software in connection with a reported cyber incident, submit the malicious software to DoD Cyber Crime Center (DC3) in accordance with instructions provided by DC3 or the Contracting Officer. Do not send the malicious software to the Contracting Officer. (e) Media preservation and protection. When a Contractor discovers a cyber incident has occurred, the Contractor shall preserve and protect images of all known affected information systems identified in paragraph (c)(1)(i) of this clause and all relevant monitoring/packet capture data for at least 90 days from the submission of the cyber incident report to allow DoD to request the media or decline interest. (f) Access to additional information or equipment necessary for forensic analysis. Upon request by DoD, the Contractor shall provide DoD with access to additional information or equipment that is necessary to conduct a forensic analysis. (g) Cyber incident damage assessment activities. If DoD elects to conduct a damage assessment, the Contracting Officer will request that the Contractor provide all of the damage assessment information gathered in accordance with paragraph (e) of this clause. (h) DoD safeguarding and use of contractor attributional/proprietary information. The Government shall protect against the unauthorized use or release of information obtained from the contractor (or derived from information obtained from the contractor) under this clause that includes contractor attributional/proprietary information, including such information submitted in accordance with paragraph (c). To the maximum extent practicable, the Contractor shall identify and mark attributional/proprietary information. In making an authorized release of such information, the Government will implement appropriate procedures to minimize the contractor attributional/proprietary information that is included in such authorized release, seeking to include only that information that is necessary for the authorized purpose(s) for which the information is being released. (i) Use and release of contractor attributional/proprietary information not created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is not created by or for DoD is authorized to be released outside of DoD-- (1) To entities with missions that may be affected by such information; (2) To entities that may be called upon to assist in the diagnosis, detection, or mitigation of cyber incidents; (3) To Government entities that conduct counterintelligence or law enforcement investigations; (4) For national security purposes, including cyber situational awareness and defense purposes (including with Defense Industrial Base (DIB) participants in the program at 32 CFR part 236); or (5) To a support services contractor (``recipient'') that is directly supporting Government activities under a contract that includes the clause at 252.204-7009, Limitations on the Use or Disclosure of Third-Party Contractor Reported Cyber Incident Information. (j) Use and release of contractor attributional/proprietary information created by or for DoD. Information that is obtained from the contractor (or derived from information obtained from the contractor) under this clause that is created by or for DoD (including the information submitted pursuant to paragraph (c) of this clause) is authorized to be used and released outside of DoD for purposes and activities authorized by paragraph (i) of this clause, and for any other lawful Government purpose or activity, subject to all applicable statutory, regulatory, and policy based restrictions on the Government's use and release of such information. (k) The Contractor shall conduct activities under this clause in accordance with applicable laws and regulations on the interception, monitoring, access, use, and disclosure of electronic communications and data. (l) Other safeguarding or reporting requirements. The safeguarding and cyber incident reporting required by this clause in no way abrogates the Contractor's responsibility for other safeguarding or cyber incident reporting pertaining to its unclassified information systems as required by other applicable clauses of this contract, or as a result of other applicable U.S. Government statutory or regulatory requirements. (m) Subcontracts. The Contractor shall-- (1) Include this clause, including this paragraph (m), in subcontracts, or similar contractual instruments, for operationally critical support, or for which subcontract performance will involve covered defense information, including subcontracts for commercial items, without alteration, except to identify the parties. The Contractor shall determine if the information required for subcontractor performance retains its identity as covered defense information and will require protection under this clause, and, if necessary, consult with the Contracting Officer; and (2) Require subcontractors to-- (i) Notify the prime Contractor (or next higher-tier subcontractor) when submitting a request to vary from a NIST SP 800-171 security requirement to the Contracting Officer, in accordance with paragraph (b)(2)(ii)(B) of this clause; and (ii) Provide the incident report number, automatically assigned by DoD, to the prime Contractor (or next higher-tier subcontractor) as soon as practicable, when reporting a cyber incident to DoD as required in paragraph (c) of this clause. (End of clause) 252.204-7015 NOTICE OF AUTHORIZED DISCLOSURE OF INFORMATION FOR LITIGATION SUPPORT (MAY 2016) (a) Definitions. As used in this clause-- Computer software means computer programs, source code, source code listings, object code listings, design details, algorithms, processes, flow charts, formulae, and related material that would enable the software to be reproduced, recreated, or recompiled. Computer software does not include computer data bases or computer software documentation. Litigation support means administrative, technical, or professional services provided in support of the Government during or in anticipation of litigation. Litigation support contractor means a contractor (including its experts, technical consultants, subcontractors, and suppliers) providing litigation support under a contract that contains the clause at 252.204-7014, Limitations on the Use or Disclosure of Information by Litigation Support Contractors. Sensitive information means controlled unclassified information of a commercial, financial, proprietary, or privileged nature. The term includes technical data and computer software, but does not include information that is lawfully, publicly available without restriction. Technical data means recorded information, regardless of the form or method of the recording, of a scientific or technical nature (including computer software documentation). The term does not include computer software or data incidental to contract administration, such as financial and/or management information. (b) Notice of authorized disclosures. Notwithstanding any other provision of this solicitation or contract, the Government may disclose to a litigation support contractor, for the sole purpose of litigation support activities, any information, including sensitive information, received- (1) Within or in connection with a quotation or offer; or (2) In the performance of or in connection with a contract. (c) Flowdown. Include the substance of this clause, including this paragraph (c), in all subcontracts, including subcontracts for commercial items. (End of clause) 252.244-7000 SUBCONTRACTS FOR COMMERCIAL ITEMS (JUN 2013) (a) The Contractor is not required to flow down the terms of any Defense Federal Acquisition Regulation Supplement (DFARS) clause in subcontracts for commercial items at any tier under this contract, unless so specified in the particular clause. (b) While not required, the Contractor may flow down to subcontracts for commercial items a minimal number of additional clauses necessary to satisfy its contractual obligation. (c) The Contractor shall include the terms of this clause, including this paragraph (c), in subcontracts awarded under this contract, including subcontracts for the acquisition of commercial items. (End of clause) IRAPT Invoicing, Receipt, Acceptance and Property Transfer (iRAPT) - formerly known as WAWF iRAPT is the authorized method to electronically process vendor request for payment. This application allows DOD vendors to submit and track Invoices and Receipt/Acceptance documents electronically. Contractor shall (i) register to use iRAPT at https://wawf.eb.mil and (ii) ensure an electronic business point of contract (POC) is designated in the System for Award Management at https://www.sam.gov within ten (10) calendar days after award of this contract/order. iRAPT Instructions: Questions concerning payments should be directed to the Defense Finance and Accounting Service (DFAS) 8899 E. 56TH STREET; INDIANAPOLIS, IN 46249-3800 (Block 18a of your purchase order/contract) at DFAS - INDY VP GFEBS (HQ0490) TEL: (801) 605-7095. Please have your purchase order/contract number ready when calling about payments. You can easily access payment and receipt information using the DFAS web site at http://www.dfas.mil/money/vendor. Your purchase order/contract number or invoice number will be required to inquire status of your payment. The following codes and information will be required to assure successful flow of iRAPT documents. Foreign Vendors will submit banking information in the Comments Tab of the iRAPT invoice. TYPE OF DOCUMENT [X the appropriate block] Invoice (Contractor Only) Invoice and Receiving Report (COMBO) Invoice as 2-in-1 (Services Only) Receiving Report (Government Only) CAGE CODE: ISSUE BY DODAAC: ADMIN BY DODAAC: INSPECT BY DODAAC: ACCEPT BY DODAAC: SHIP TO DODAAC: PAYMENT OFFICE FISCAL STATION CODE: EMAIL POINTS OF CONTACT LISTING: (Use Group e-mail accounts if applicable) INSPECTOR Primary: Alternate: ACCEPTOR Primary: RECEIVING OFFICE POC: Primary: CONTRACT ADMINISTRATOR/ SPECIALIST: Your.Name@mail.mil DSN: Comm: - Fax: CONTRACTING OFFICER: See Block 31b on SF1449 for email address. Any modification requests must be in writing and submitted to:ADMIN DODAAC. (End) HIPAA Non-Defense Health Agency (Non-DHA) Health Insurance Portability and Accountability Act (HIPAA) Business Associate Agreement (BAA) (7 July 2014) Introduction In accordance with 45 CFR 164.502(e)(2) and 164.504(e) and paragraph C.3.4.1.3 of DoD 6025.18-R, "DoD Health Information Privacy Regulation," January 24, 2003, this document serves as a BAA between the signatory parties for purposes of the HIPAA and the "HITECH Act" amendments thereof, as implemented by the HIPAA Rules and DoD HIPAA Issuances (both defined below). The parties are a DoD Military Health System (MHS) component, acting as a HIPAA covered entity, and a DoD contractor, acting as a HIPAA business associate. The HIPAA Rules require BAAs between covered entities and business associates. Implementing this BAA requirement, the applicable DoD HIPAA Issuance (DoD 6025.18-R, paragraph C3.4.1.3) provides that requirements applicable to business associates must be incorporated (or incorporated by reference) into the contract or agreement between the parties. (a) Catchall Definition. Except as provided otherwise in this BAA, the following terms used in this BAA shall have the same meaning as those terms in the DoD HIPAA Rules: Data Aggregation, Designated Record Set, Disclosure, Health Care Operations, Individual, Minimum Necessary, Notice of Privacy Practices (NoPP), Protected Health Information (PHI), Required By Law, Secretary, Security Incident, Subcontractor, Unsecured Protected Health Information, and Use. -Breach means actual or possible loss of control, unauthorized disclosure of or unauthorized access to PHI or other PII (which may include, but is not limited to PHI), where persons other than authorized users gain access or potential access to such information for any purpose other than authorized purposes, where one or more individuals will be adversely affected. The foregoing definition is based on the definition of breach in DoD Privacy Act Issuances as defined herein. -Business Associate shall generally have the same meaning as the term "business associate" in the DoD HIPAA Issuances, and in reference to this BAA, shall mean [insert name of Business Associate signatory to this BAA]. -Agreement means this BAA together with the documents and/or other arrangements under which the Business Associate signatory performs services involving access to PHI on behalf of the MHS component signatory to this BAA. -Covered Entity shall generally have the same meaning as the term "covered entity" in the DoD HIPAA Issuances, and in reference to this BAA, shall mean [insert name of MHS component signatory to this BAA]. -DHA Privacy Office means the DHA Privacy and Civil Liberties Office. The DHA Privacy Office Director is the HIPAA Privacy and Security Officer for DHA, including the National Capital Region Medical Directorate (NCRMD). -DoD HIPAA Issuances means the DoD issuances implementing the HIPAA Rules in the DoD Military Health System (MHS). These issuances are DoD 6025.18-R (2003), DoDI 6025.18 (2009), and DoD 8580.02-R (2007). -DoD Privacy Act Issuances means the DoD issuances implementing the Privacy Act, which are DoDD 5400.11 (2007) and DoD 5400.11-R (2007). -HHS Breach means a breach that satisfies the HIPAA Breach Rule definition of breach in 45 CFR 164.402. -HIPAA Rules means, collectively, the HIPAA Privacy, Security, Breach and Enforcement Rules, issued by the U.S. Department of Health and Human Services (HHS) and codified at 45 CFR Part 160 and Part 164, Subpart E (Privacy), Subpart C (Security), Subpart D (Breach) and Part 160, Subparts C-D (Enforcement), as amended by the 2013 modifications to those Rules, implementing the "HITECH Act" provisions of Pub. L. 111-5. See 78 FR 5566- 5702 (Jan. 25, 2013) (with corrections at 78 FR 32464 (June 7, 2013)). Additional HIPAA rules regarding electronic transactions and code sets (45 CFR Part 162) are not addressed in this BAA and are not included in the term HIPAA Rules. -Service-Level Privacy Office means one or more offices within the military services (Army, Navy, or Air Force) with oversight authority over Privacy Act and HIPAA privacy compliance. I. Obligations and Activities of Business Associate (a) The Business Associate shall not use or disclose PHI other than as permitted or required by the Agreement or as required by law. (b) The Business Associate shall use appropriate safeguards, and comply with the DoD HIPAA Rules with respect to electronic PHI, to prevent use or disclosure of PHI other than as provided for by the Agreement. (c) The Business Associate shall report to Covered Entity any Breach of which it becomes aware, and shall proceed with breach response steps as required by Part V of this BAA. With respect to electronic PHI, the Business Associate shall also respond to any security incident of which it becomes aware in accordance with any Information Assurance provisions of the Agreement. If at any point the Business Associate becomes aware that a security incident involves a Breach, the Business Associate shall immediately initiate breach response as required by part V of this BAA. (d) In accordance with 45 CFR 164.502(e)(1)(ii)) and 164.308(b)(2), respectively), as applicable, the Business Associate shall ensure that any subcontractors that create, receive, maintain, or transmit PHI on behalf of the Business Associate agree to the same restrictions, conditions, and requirements that apply to the Business Associate with respect to such PHI. (e) The Business Associate shall make available PHI in a Designated Record Set, to the Covered Entity or, as directed by the Covered Entity, to an Individual, as necessary to satisfy the Covered Entity obligations under 45 CFR 164.524. (f) The Business Associate shall make any amendment(s) to PHI in a Designated Record Set as directed or agreed to by the Covered Entity pursuant to 45 CFR 164.526, or take other measures as necessary to satisfy Covered Entity's obligations under 45 CFR 164.526. (g) The Business Associate shall maintain and make available the information required to provide an accounting of disclosures to the Covered Entity or an individual as necessary to satisfy the Covered Entity's obligations under 45 CFR 164.528. (h) To the extent the Business Associate is to carry out one or more of Covered Entity's obligation(s) under the HIPAA Privacy Rule, the Business Associate shall comply with the requirements of HIPAA Privacy Rule that apply to the Covered Entity in the performance of such obligation(s); and (i) The Business Associate shall make its internal practices, books, and records available to the Secretary for purposes of determining compliance with the HIPAA Rules. II. Permitted Uses and Disclosures by Business Associate (a) The Business Associate may only use or disclose PHI as necessary to perform the services set forth in the Agreement or as required by law. The Business Associate is not permitted to de-identify PHI under DoD HIPAA issuances or the corresponding 45 CFR 164.514(a)-(c), nor is it permitted to use or disclose de-identified PHI, except as provided by the Agreement or directed by the Covered Entity. (b) The Business Associate agrees to use, disclose and request PHI only in accordance with the HIPAA Privacy Rule "minimum necessary" standard and corresponding DHA policies and procedures as stated in the DoD HIPAA Issuances. (c) The Business Associate shall not use or disclose PHI in a manner that would violate the DoD HIPAA Issuances or HIPAA Privacy Rules if done by the Covered Entity, except uses and disclosures for the Business Associate's own management and administration and legal responsibilities or for data aggregation services as set forth in the following three paragraphs. (d) Except as otherwise limited in the Agreement, the Business Associate may use PHI for the proper management and administration of the Business Associate or to carry out the legal responsibilities of the Business Associate. The foregoing authority to use PHI does not apply to disclosure of PHI, which is covered in the next paragraph. (e) Except as otherwise limited in the Agreement, the Business Associate may disclose PHI for the proper management and administration of the Business Associate or to carry out the legal responsibilities of the Business Associate, provided that disclosures are required by law, or the Business Associate obtains reasonable assurances from the person to whom the PHI is disclosed that it will remain confidential and used or further disclosed only as required by law or for the purposes for which it was disclosed to the person, and the person notifies the Business Associate of any instances of which it is aware in which the confidentiality of the information has been breached. (f) Except as otherwise limited in the Agreement, the Business Associate may use PHI to provide Data Aggregation services relating to the Covered Entity's health care operations. III. Provisions for Covered Entity to Inform Business Associate of Privacy Practices and Restrictions (a) The Covered Entity shall provide the Business Associate with the notice of privacy practices that the Covered Entity produces in accordance with 45 CFR 164.520 and the corresponding provision of the DoD HIPAA Issuances. (b) The Covered Entity shall notify the Business Associate of any changes in, or revocation of, the permission by an Individual to use or disclose his or her PHI, to the extent that such changes affect the Business Associate's use or disclosure of PHI. (c) The Covered Entity shall notify the Business Associate of any restriction on the use or disclosure of PHI that the Covered Entity has agreed to or is required to abide by under 45 CFR 164.522, to the extent that such changes may affect the Business Associate's use or disclosure of PHI. IV. Permissible Requests by Covered Entity The Covered Entity shall not request the Business Associate to use or disclose PHI in any manner that would not be permissible under the HIPAA Privacy Rule or any applicable Government regulations (including without limitation, DoD HIPAA Issuances) if done by the Covered Entity, except for providing Data Aggregation services to the Covered Entity and for management and administrative activities of the Business Associate as otherwise permitted by this BAA. V. Breach Response (a) In general. In the event of a breach of PII/PHI held by the Business Associate, the Business Associate shall follow the breach response requirements set forth in this Part V, which is designed to satisfy both the Privacy Act and HIPAA as applicable. If a breach involves PII without PHI, then the Business Associate shall comply with DoD Privacy Act Issuance breach response requirements only; if a breach involves PHI (a subset of PII), then the Business Associate shall comply with both Privacy Act and HIPAA breach response requirements. A breach involving PHI may or may not constitute an HHS Breach. If a breach is not an HHS Breach, then the Business Associate has no HIPAA breach response obligations. In such cases, the Business Associate must still comply with breach response requirements under the DoD Privacy Act Issuances. If the DHA Privacy Office determines that a breach is an HHS Breach, then the Business Associate shall comply with both the HIPAA Breach Rule and DoD Privacy Act Issuances, as directed by the DHA Privacy Office, regardless of whether the breach occurs at DHA or at one of the Service components. If the DHA Privacy Office determines that the breach does not constitute an HHS Breach, then the Business Associate shall comply with DoD Privacy Act Issuances, as directed by the applicable Service-Level Privacy Office. The Business Associate shall contact the Covered Entity for guidance when the incident is not an HHS Breach. This Part V is designed to satisfy the DoD Privacy Act Issuances and the HIPAA Breach Rule as implemented by the DoD HIPAA Issuances. In general, for breach response, the Business Associate shall report the breach to the Covered Entity, assess the breach incident, notify affected individuals, and take mitigation actions as applicable. Because DoD defines "breach" to include possible (suspected) as well as actual (confirmed) breaches, the Business Associate shall implement these breach response requirements immediately upon the Business Associate's discovery of a possible breach. (b) Government Reporting Provisions The Business Associate shall report the breach within one hour of discovery to the Covered Entity and to the US Computer Emergency Readiness Team (US CERT) -the other parties as deemed appropriate by the Covered Entity. The Business Associate is deemed to have discovered a breach as of the time a breach (suspected or confirmed) is known, or by exercising reasonable diligence would have been known, to any person (other than the person committing it) who is an employee, officer or other agent of the Business Associate. The Business Associate shall submit the US-CERT report using the online form at https://forms.us-cert.gov/report/. Before submission to US-CERT, the Business Associate shall save a copy of the on-line report. After submission, the Business Associate shall record the US-CERT Reporting Number. Although only limited information about the breach may be available as of the one hour deadline for submission, the Business Associate shall submit the US- CERT report by the deadline. The Business Associate shall e-mail updated information as it is obtained, following the instructions at http://www.us-cert.gov/pgp/email.html. The Business Associate shall provide a copy of the initial or updated US-CERT report to the -Covered Entity and the applicable Service-Level Privacy Office, if requested by either. Business Associate questions about US-CERT reporting shall be directed to the Covered Entity or Service- Level Privacy Office, not the US-CERT office. The additional US Army and the US Army Medical Command (MEDCOM) reporting requirements are addressed in the PII Breach Reporting and Notification Policy. The latest version of this policy can be obtained from the Covered Entity or the MEDCOM Privacy Act/Freedom of Information Act (FOIA) Office at: usarmy.jbsa.medcom.list.medcom-foia-users@mail.mil. If multiple beneficiaries are affected by a single event or related set of events, then a single reportable breach may be deemed to have occurred, depending on the circumstances. The Business Associate shall inform the Covered Entity as soon as possible if it believes that "single event" breach response is appropriate; the Covered Entity will determine how the Business Associate shall proceed and, if appropriate, consolidate separately reported breaches for purposes of Business Associate report updates, beneficiary notification, and mitigation. When a Breach Report initially submitted is incomplete or incorrect due to unavailable information, or when significant developments require an update, the Business Associate shall submit a revised form or forms, stating the updated status and previous report date(s) and showing any revisions or additions in red text. Examples of updated information the Business Associate shall report include, but are not limited to: confirmation on the exact data elements involved, the root cause of the incident, and any mitigation actions to include, sanctions, training, incident containment, follow-up, etc. The Business Associate shall submit these report updates promptly after the new information becomes available. Prompt reporting of updates is required to allow the Covered Entity to make timely final determinations on any subsequent notifications or reports. The Business Associate shall provide updates to the same parties as required for the initial Breach Report. The Business Associate is responsible for reporting all information needed by the Covered Entity to make timely and accurate determinations on reports to HHS as required by the HHS Breach Rule and reports to the Defense Privacy and Civil Liberties Office as required by DoD Privacy Act Issuances. In the event the Business Associate is uncertain on how to apply the above requirements, the Business Associate shall consult with the Covered Entity (or the Service-Level Privacy Office, which will consult with the DHA Privacy Office as appropriate) when determinations on applying the above requirements are needed. (c) Individual Notification Provisions If the DHA Privacy Office determines that individual notification is required, the Business Associate shall provide written notification to individuals affected by the breach as soon as possible, but no later than 10 working days after the breach is discovered and the identities of the individuals are ascertained. The 10 day period begins when the Business Associate is able to determine the identities (including addresses) of the individuals whose records were impacted. The Business Associate's proposed notification to be issued to the affected individuals shall be submitted to the parties to which reports are submitted under paragraph V (a) for their review, and for approval by the DHA Privacy Office. Upon request, the Business Associate shall provide the DHA Privacy Office with the final text of the notification letter sent to the affected individuals. If different groups of affected individuals receive different notification letters, then the Business Associate shall provide the text of the letter for each group. (PII shall not be included with the text of the letter(s) provided.) Copies of further correspondence with affected individuals need not be provided unless requested by the Privacy Office. The Business Associate's notification to the individuals, at a minimum, shall include the following: -The individual(s) must be advised of what specific data was involved. It is insufficient to simply state that PII has been lost. Where names, Social Security Numbers (SSNs) or truncated SSNs, and Dates of Birth (DOBs) are involved, it is critical to advise the individual that these data elements potentially have been breached. -The individual(s) must be informed of the facts and circumstances surrounding the breach. The description should be sufficiently detailed so that the individual clearly understands how the breach occurred. -The individual(s) must be informed of what protective actions the Business Associate is taking or the individual can take to mitigate against potential future harm. The notice must refer the individual to the current Federal Trade Commission (FTC) web site pages on identity theft and the FTC's Identity Theft Hotline, toll-free: 1-877-ID- THEFT (438-4338); TTY: 1-866-653-4261. -The individual(s) must also be informed of any mitigation support services (e.g., one year of free credit monitoring, identification of fraud expense coverage for affected individuals, provision of credit freezes, etc.) that the Business Associate may offer affected individuals, the process to follow to obtain those services and the period of time the services will be made available, and contact information (including a phone number, either direct or toll- free, e-mail address and postal address) for obtaining more information. Business Associates shall ensure any envelope containing written notifications to affected individuals are clearly labeled to alert the recipient to the importance of its contents, e.g., "Data Breach Information Enclosed," and that the envelope is marked with the identity of the Business Associate and/or subcontractor organization that suffered the breach. The letter must also include contact information for a designated POC to include, phone number, email address, and postal address. If the Business Associate determines that it cannot readily identify, or will be unable to reach, some affected individuals within the 10 day period after discovering the breach, the Business Associate shall so indicate in the initial or updated Breach Report. Within the 10 day period, the Business Associate shall provide the approved notification to those individuals who can be reached. Other individuals must be notified within 10 days after their identities and addresses are ascertained. The Business Associate shall consult with the DHA Privacy Office, which will determine which media notice is most likely to reach the population not otherwise identified or reached. The Business Associate shall issue a generalized media notice(s) to that population in accordance with Privacy Office approval. The Business Associate shall, at no cost to the government, bear any costs associated with a breach of PII/PHI that the Business Associate has caused or is otherwise responsible for addressing. Breaches are not to be confused with security incidents (often referred to as cyber security incidents when electronic information is involved), which may or may not involve a breach of PII/PHI. In the event of a security incident not involving a PII/PHI breach, the Business Associate shall follow applicable DoD Information Assurance requirements under its Agreement. If at any point the Business Associate finds that a cyber security incident involves a PII/PHI breach (suspected or confirmed), the Business Associate shall immediately initiate the breach response procedures set forth here. The Business Associate shall also continue to follow any required cyber security incident response procedures to the extent needed to address security issues, as determined by DoD/DHA. VI. Termination (a) Termination. Noncompliance by the Business Associate (or any of its staff, agents, or subcontractors) with any requirement in this BAA may subject the Business Associate to termination under any applicable default or other termination provision of the Agreement. (b) Effect of Termination. (1) If the Agreement has records management requirements, the Business Associate shall handle such records in accordance with the records management requirements. If the Agreement does not have records management requirements, the records should be handled in accordance with paragraphs (2) and (3) below. If the Agreement has provisions for transfer of records and PII/PHI to a successor Business Associate, or if DHA gives directions for such transfer, the Business Associate shall handle such records and information in accordance with such Agreement provisions or DHA direction. (2) If the Agreement does not have records management requirements, except as provided in the following paragraph (3), upon termination of the Agreement, for any reason, the Business Associate shall return or destroy all PHI received from the Covered Entity, or created or received by the Business Associate on behalf of the Covered Entity that the Business Associate still maintains in any form. This provision shall apply to PHI that is in the possession of subcontractors or agents of the Business Associate. The Business Associate shall retain no copies of the PHI. (3) If the Agreement does not have records management provisions and the Business Associate determines that returning or destroying the PHI is infeasible, the Business Associate shall provide to the Covered Entity notification of the conditions that make return or destruction infeasible. Upon mutual agreement of the Covered Entity and the Business Associate that return or destruction of PHI is infeasible, the Business Associate shall extend the protections of the Agreement to such PHI and limit further uses and disclosures of such PHI to those purposes that make the return or destruction infeasible, for so long as the Business Associate maintains such PHI. VII. Miscellaneous (a) Survival. The obligations of Business Associate under the "Effect of Termination" provision of this BAA shall survive the termination of the Agreement. (b) Interpretation. Any ambiguity in the Agreement shall be resolved in favor of a meaning that permits the Covered Entity and the Business Associate to comply with the HIPAA Rules and the DoD HIPAA Rules. (End of HCAA Local Clause 5001) CLAUSES INCORPORATED BY FULL TEXT 52.212-5 CONTRACT TERMS AND CONDITIONS REQUIRED TO IMPLEMENT STATUTES OR EXECUTIVE ORDERS-COMMERCIAL ITEMS (DEVIATION 2013-O0019) (JAN 2017) (a) Comptroller General Examination of Record. The Contractor shall comply with the provisions of this paragraph (a) if this contract was awarded using other than sealed bid, is in excess of the simplified acquisition threshold, and does not contain the clause at 52.215-2, Audit and Records -- Negotiation. (1) The Comptroller General of the United States, or an authorized representative of the Comptroller General, shall have access to and right to examine any of the Contractor's directly pertinent records involving transactions related to this contract. (2) The Contractor shall make available at its offices at all reasonable times the records, materials, and other evidence for examination, audit, or reproduction, until 3 years after final payment under this contract or for any shorter period specified in FAR Subpart 4.7, Contractor Records Retention, of the other clauses of this contract. If this contract is completely or partially terminated, the records relating to the work terminated shall be made available for 3 years after any resulting final termination settlement. Records relating to appeals under the disputes clause or to litigation or the settlement of claims arising under or relating to this contract shall be made available until such appeals, litigation, or claims are finally resolved. (3) As used in this clause, records include books, documents, accounting procedures and practices, and other data, regardless of type and regardless of form. This does not require the Contractor to create or maintain any record that the Contractor does not maintain in the ordinary course of business or pursuant to a provision of law. (b) (1) Notwithstanding the requirements of any other clause in this contract, the Contractor is not required to flow down any FAR clause, other than those in this paragraph (b)(1) in a subcontract for commercial items. Unless otherwise indicated below, the extent of the flow down shall be as required by the clause- (i) 52.203-13, Contractor Code of Business Ethics and Conduct (Oct 2015) (41 U.S.C. 3509). (ii) 52.219-8, Utilization of Small Business Concerns (Oct 2014) (15 U.S.C. 637(d)(2) and (3)), in all subcontracts that offer further subcontracting opportunities. If the subcontract (except subcontracts to small business concerns) exceeds $650,000 ($1.5 million for construction of any public facility), the subcontractor must include 52.219-8 in lower tier subcontracts that offer subcontracting opportunities. (iii) 52.222-17, Nondisplacement of Qualified Workers (May 2014) (E.O. 13495). Flow down required in accordance with paragraph (1) of FAR clause 52.222-17. (iv) 52.222-21, Prohibition of Segregated Facilities (Apr 2015). (v) 52.222-26, Equal Opportunity (Sep 2016) (E.O. 11246). (vi) 52.222-35, Equal Opportunity for Veterans (Oct 2015) (38 U.S.C. 4212). (vii) 52.222-36, Equal Opportunity for Workers with Disabilities (Jul 2014) (29 U.S.C. 793). (viii) 52.222-62 Paid Sick Leave Under Executive Order 13706 (JAN 2017) (E.O. 13706). (ix) 52.222-37, Employment Reports on Veterans (Feb 2016) (38 U.S.C. 4212). (x) 52.222-40, Notification of Employee Rights Under the National Labor Relations Act (Dec 2010) (E.O. 13496). Flow down required in accordance with paragraph (f) of FAR clause 52.222-40. (xi) 52.222-41, Service Contract Labor Standards (May 2014), (41 U.S.C. chapter 67). (xii) 13627). (A) 52.222-50, Combating Trafficking in Persons (Mar 2015) (22 U.S.C. chapter 78 and E.O. (B) Alternate I (Mar 2015) of 52.222-50 (22 U.S.C. chapter 78 E.O. 13627). (xiii) 52.222-51, Exemption from Application of the Service Contract Labor Standards to Contracts for Maintenance, Calibration, or Repair of Certain Equipment--Requirements (May 2014) (41 U.S.C. chapter 67.) (xiv) 52.222-53, Exemption from Application of the Service Contract Labor Standards to Contracts for Certain Services--Requirements (May 2014) (41 U.S.C. chapter 67) (xv) 52.222-54, Employment Eligibility Verification (Oct 2015). (xvi) 52.222-55, Minimum Wages Under Executive Order 13658 (Dec 2015) (E.O. 13658). (xvii) 52.222-59, Compliance with Labor Laws (Executive Order 13673) (Oct 2016) (Applies at $50 million for solicitations and resultant contracts issued from October 25, 2016 through April 24, 2017; applies at $500,000 for solicitations and resultant contracts issued after April 24, 2017). Note to paragraph (b)(1)(xvi): By a court order issued on October 24, 2016, 52.222-59 is enjoined indefinitely as of the date of the order. The enjoined paragraph will become effective immediately if the court terminates the injunction. At that time, DoD, GSA, and NASA will publish a document in the Federal Register advising the public of the termination of the injunction. (xviii) 52.222-60, Paycheck Transparency (Executive Order 13673) (Oct 2016). (xix) 52.225-26, Contractors Performing Private Security Functions Outside the United States (Jul 2013) (Section 862, as amended, of the National Defense Authorization Act for Fiscal Year 2008; 10 U.S.C. 2302 Note). (xx) 52.226-6, Promoting Excess Food Donation to Nonprofit Organizations. (May 2014) (42 U.S.C. 1792). Flow down required in accordance with paragraph (e) of FAR clause 52.226-6. (xxi) 52.247-64, Preference for Privately-Owned U.S. Flag Commercial Vessels (Feb 2006) (46 U.S.C. Appx 1241(b) and 10 U.S.C. 2631). Flow down required in accordance with paragraph (d) of FAR clause 52.247-64. (2) While not required, the contractor may include in its subcontracts for commercial items a minimal number of additional clauses necessary to satisfy its contractual obligations. (End of Clause) PWS 1. General Scope of Work 1.1. Non-Personal Services: The contractor shall provide repair and maintenance service for CareFusion (PYXIS) medical equipment located at Bayne-Jones Army Community Hospital, Fort Polk, LA. Contractor shall have a factory trained Technician to repair and work on all medical equipment covered under the CareFusion (PYXIS) contract. Upon arrival to the site, Contractor shall report directly to the Medical Maintenance Department, located in Bayne-Jones Army Community Hospital (BJACH) room 1650. 1.1.1. Point of Contact: At the start of the contract, the Contractor shall have a contract representative and alternate responsible for scheduling and coordinating service calls. The name and phone number of the designated individual and alternate shall be provided to the Medical Maintenance contracting team- Kereese Mclean (POC) kereese.a.mclean.civ @mail.mil, Gertrude Jackson (APOC) gertrude.d. jackson.civ @mail.mil. Ruben Garcia, ruben.qarcia312.mil @mail.mil, (337) 531-3227. 1.1.2. Scheduled Services: Inspections, Preventative Maintenance, and Calibration Verification shall be performed annually or Semi Annually, depending on the equipment (if applicable). Services performed shall be on a scheduled or unscheduled basis as requested. 1.2. Government Area of Responsibility 1.2.1. Make available to the contractor the units for servicing. 1.2.2. Ensure a person from the customer's facility is on hand, after normal duty hours, if services are not completed by 1630. 1.2.3. Perform a quality assurance test, prior to the departure of the contractor's service technician. 1.2.4. Use available personnel to sign all service reports verifying completion and satisfaction of service. 1.2.5. Transportation: No additional cost shall be charged to the Government for transportation and shipment of any parts removed for service. Items shall not be shipped without prior authorization from the Contracting Officer or designated representative. 1.3. Security Requirements - Installation OPSEC 1.3.1. In accordance with AR 530-1, Operations Security (OPSEC), dated 19 April 2007, and DoDM 5205.02-M, DoD Operations Security (OPSEC) Program Manual, dated 03 November 2008, contract personnel shall receive initial OPSEC Level I training which consists of initial and continual awareness training. Within the first 30 days of arrival on Fort Polk contract personnel shall receive initial OPSEC training either by on-line training through the Fort Polk SharePoint OPSEC site on the intranet, or the Defense Security Services website at: http://cdsetrain.dtic.mil/opsec/index.htm. 1.3.2. The contractor shall ensure all applicable employees have completed OPSEC initial training and annual refresher training and shall certify that their workforce has completed the training through the submission of completion certificate(s) to the Contracting Officer and the Contracting Officer's Representative (if appointed) within 30 days of arrival on post. 1.3.3. Operations Security (OPSEC) Awareness Training (AT) attendance and compliance may be documented as a performance metric under the resultant contract, and be part of past performance information in support of future source selections. 2. Installation Specific Security Requirements for PWS/SOW/SOO 2.1. Installation Physical Security 2.1.1. Contractor's must provide an access roster to BJACH Security for submission to Directorate of Emergency Services (DES), Physical Security Office, of all employees monthly or when any personnel change occurs, for access to Fort Polk. Access rosters must be forwarded by the POC to BJACH Security for submission to the Visitors Control Center using a specific format, electronically, from a government computer. All personnel employed under this contract will adhere to all Fort Polk access control policies, which include, weapons registration, transportation of weapons on the installation, access control policies, use of installation passes and ID cards and the operation of motor vehicles. 2.1.2. A check of records through the National Crime Information Center (NCIC) Interstate Identification Index (Ill) is the Army minimum baseline background check for entrance onto Army installations for non-CAC holders, to include entrance of visitors. Contractors will provide proof of all employees using e-verify and ensure that no illegal immigrants are employed under the umbrella of this contract. 2.1.3. The contractor shall provide employees with company identification (ID) cards prior to their commencement of work. The ID format is subject to approval by the government. IDs shall be laminated and include the company's name, ID number, issue and expiration dates, employee name, job title and color photograph. Employees shall wear ID cards on front exterior clothing, above the waist, when performing services under the Performance of Work Statement (PWS)/Statement of Work (SOW) unless otherwise specified herein or approved by the government. 2.2 Physical Security Plan: The contractor shall address the physical security aspects associated with contract performance in government furnished facilities. The plan shall describe how the Security Plan shall prevent unauthorized access, vandalism, pilferage, larceny, sabotage, and arson directed toward contractor controlled facilities. A list of installation buildings for which the contractor shall be responsible shall be included in the plan. The contractor shall maintain an active security checklist for each facility under the contractor's control. The plan shall comply with the provisions of AR 190-11, AR 190-13, AR 190-51, DoD 5100.76(D), 5220.22(D) and the Fort Polk, LA Installation Physical Security Plan. This security plan will be reviewed annually by the DES to ensure regulatory requirements. 2.3 Information Systems Security Plan: The Information Systems Security Plan shall establish security procedures for all computer systems and communications utilized in the performance of this Performance Work Statement (PWS)/Statement of Work (SOW)/Statement of Objective (SQQ). The plan shall conform to AR 25-2, AR 25-1 and AR 380-67. 2.4 The contractor shall immediately notify the contracting officer when an employee terminates employment that has access to government information systems or data. The contractor shall ensure all common access cards issued to employees are returned to the government upon termination of employment and released employee names are to be stricken from the roster maintained by BJACH, Security immediately upon release. 2.5 Installation AT/FP 2.5.1 Pursuant to DoD Instruction Number2000.16, "DoD Antiterrorism (AT) Standards," dated October 2, 2006, each Contractor employee requiring access to a Federally-Controlled Installation, facility and/or federally-controlled information system(s) shall complete Level I AT Awareness Training on an annual basis and receive a certificate of completion. The training is accessible from any computer and is available at https://jkodirect.jten.mil. The contractor is responsible for ensuring that all applicable employees have completed antiterrorism awareness training. The contractor shall certify that their workforce has completed the necessary training, through the submission of completion certificate(s) to the Contracting Officer and the Contracting Officer's Representative (if appointed), within five working days after contract award or prior to access to a federally-controlled installation or information system. (1) Special Instructions: a. Google JKO (Joint Knowledge Online) to begin the process. (A) Click: a. No DOD CAC b. I am a US mil, government civil servant, or contract employee c. I've been directed to take required training on JKO d. Courses e. I do not have a.MIL,.GOV, or.NDU.EDU address or I am a Multi- National Student f. Fill out the contact sheet and email to sponsor {This is the POC) • Sponsor will email to the JKO help desk. {This is the POC) (B) Approval: a. Help desk sends non-CAC user an email with User ID b. User will need to enroll in Course # JS-US007-14 (User has up to 30 days to complete the course) 2.4.2. In the event that the automated system at https:// jkodirect. jten.mil is not available (e.g. server problems), Level I AT Awareness Training can be provided by a qualified instructor. However, if the training is not completed online, the Level I AT Awareness instructor qualification must be coordinated with the installation Antiterrorism Officer or (installation security equivalent) and the resultant name(s) of approved instructors shall be provided to the contracting officer or designee along with all associated cost or schedule impacts to the contract. 2.4.3. Antiterrorism performance (Level I AT Awareness Training attendance and compliance) may be documented as a performance metric under the resultant contract, and be part of past performance information in support of future source selections. 3. Contract Personnel 3.1. Contract personnel will obtain a vehicle pass for access to place of performance. 3.1.2. Badges: Contractor's representative shall report to BJACH 1585, 3rd Street, Room 1650 (337) 531-3227, prior to commencing services during normal operating hours (0800 AM to 1630 PM M-F). The POC or APOC will ensure the contractor has proper identification before work is performed. 3.1.3. The Contracting Officer may require the Contractor to remove from the job site, any employee who is identified as a potential threat to the health, safety, security, general well-being or operational mission of the installation and its population. 3.1.4. All contractor employees must be fluent in spoken and written English. 3.1.5. Contractor personnel shall present a neat appearance, in accordance with standard office attire, and BJACH Command Policy #69 Wear and Appearance of Uniform and Hospital Specific Items of Clothing, and be easily recognized as a contractor employee. This may be accomplished by wearing distinctive badges which contain the company name and employee name, identifying themselves as contractors when they answer the phone, and by providing a descriptive line on their email, identifying them as contractors. 3.2 Hours of Performance 3.2. Monday thru Friday 0800A M to 1630 PM (excluding national holidays) 3.3. Service Parts I Equipment: 3.3.1. Contractor must furnish all software upgrades issued by the equipment manufacturer. All repair parts shall meet exact manufacturer specifications and be the most current revision level. All parts shall be new or remanufactured by the manufacturer of the instruments. 3.3.2. Contractor shall have access to all necessary diagnostic software (if applicable). 3.3.3. Contractor shall have access to unique and/or high mortality replacement parts. 3.4. Mission-Critical Support 3.4.1. Contractor shall provide technical support via telephone 24 hours per day, 7 days a week, with a telephone response time of not more than 2 hours. 3.4.2. In the event the system is disabled, the contractor will respond on site within 6 hours of notification. Contractor will provide all supplies necessary per user requirements. 3.5. Documentation: 3.6. The Contractor shall be responsible for all items of Government equipment throughout the period they are under his/her control. The Contractor shall be responsible for any contractor- caused damage to Government-owned property and shall replace or repair at the contractor's expense. The Contracting Officer will approve replacements or repairs. 3.6.1. The Contractor shall ensure all areas where equipment is serviced on-site are left in a clean, neat, safe, and orderly condition. To prevent safety hazards, no equipment shall be left pulled-out or apart at the end of the workday. All equipment under repair shall be secured at all times. 3.6.2. Contractor shall provide an invoice to the POC or APOC and call (337) 531-3227 for verification of services performed. 3.7. Quality Control: Contractor is to establish actions to control and ensure contract compliance. 3.8. Quality Assurance Surveillance Plan 3.8.1. This Quality Assurance Surveillance Plan (QASP) will be used by the Point of Contact (POC) to evaluate and document the contractor's performance. Surveillance will be conducted and documented IAW FAR 52.212-4, Inspection of Services-Fixed Price Clause. POC is to notify the (KO) of any significant performance deficiencies and is encouraged to provide the KO with recommendations for improvements to the QASP and SOW throughout the life of the contract. PERFORMANCE OBJECTIVE PERFORMANCE STANDARD REFERENCE METHOD OF ASSESSMENT Establish and maintain a Quality Control plan 100% 3.7. POC Monitor IAW system needs/ requirements appropriate parts/ software to service/ maintain 100% 1.1., 1.1.2., 1.2. POC Monitor Comply with safety, security requirements conditions 100% 1.3.1., 2.1, 3.2.2 POC Monitor STANDARD MEASUREMENT PAST PERFORMANCE ASSESSMENT 99 - 100 % Excellent Document Past Performance 96 - 98% Very Good Assessment Report, paying 95% Satisfactory particular attention to 92- 94% Marginal performance that exceeds 92% - Less Unsatisfactory the standard CONTRACTOR MANPOWER REPORTING ACCOUNTING FOR CONTRACT SERVICES-The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report ALL contractor manpower (including subcontractor manpower) required for performance of this contract. The contractor is required to completely fill in all the information in the format using the following web address "https://cmra.army.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer's Technical Representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5) Estimated direct labor hours (including sub-contractor); (6) Estimated direct labor dollars paid this reporting period (including subcontractor); (7) Total payments (including subcontractor); (8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different); (9) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the contractor with its UIC for the purposes of reporting this information); (10) Locations where contractor and subcontractors perform the work (specified by zip code in the United States and nearest City, Country, when in an overseas location, using standardized nomenclature provided on website); (11) Presence of deployment or contingency contract language, and, (12) Number of contractor and sub-contractor employees deployed in theater this reporting period (by country). (13) As part of its submission, the contractor will also provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. The contractor shall notify the Point of Contact (POC) (if applicable) by the 5th working day of November whether or not they have completed this report. If the POC is unavailable, the contractor will notify the Contracting Officer." CLAUSES INCORPORATED BY REFERENCE 52.212-1 Instructions to Offerors--Commercial Items JAN 2017 ADDENDUM TO 52.212-1 (m) The non-FAR Part 12 discretionary FAR, DFARS, AFARS, and LOCAL provisions included herein are incorporated into this solicitation either by reference or in full text. If incorporated by reference, see provision 52.252-1 herein for locations where full text can be found. (End of Provision) CLAUSES INCORPORATED BY REFERENCE 52.204-16 Commercial and Government Entity Code Reporting JUL 2016 52.225-25 Prohibition on Contracting with Entities Engaging in Certain Activities or Transactions Relating to Iran-- Representation and Certifications. OCT 2015 CLAUSES INCORPORATED BY FULL TEXT 52.209-2 PROHIBITION ON CONTRACTING WITH INVERTED DOMESTIC CORPORATIONS-- REPRESENTATION (NOV 2015) (a) Definitions. Inverted domestic corporation and subsidiary have the meaning given in the clause of this contract entitled Prohibition on Contracting with Inverted Domestic Corporations (52.209-10). (b) Government agencies are not permitted to use appropriated (or otherwise made available) funds for contracts with either an inverted domestic corporation, or a subsidiary of an inverted domestic corporation, unless the exception at 9.108-2(b) applies or the requirement is waived in accordance with the procedures at 9.108-4. (c) Representation. The Offeror represents that-- (1) It [ ] is, [ ] is not an inverted domestic corporation; and (2) It [ ] is, [ ] is not a subsidiary of an inverted domestic corporation. (End of provision) 52.209-11 REPRESENTATION BY CORPORATIONS REGARDING DELINQUENT TAX LIABILITY OR A FELONY CONVICTION UNDER ANY FEDERAL LAW (FEB 2016) (a) As required by sections 744 and 745 of Division E of the Consolidated and Further Continuing Appropriations Act, 2015 (Pub. L. 113-235), and similar provisions, if contained in subsequent appropriations acts, the Government will not enter into a contract with any corporation that-- (1) Has any unpaid Federal tax liability that has been assessed, for which all judicial and administrative remedies have been exhausted or have lapsed, and that is not being paid in a timely manner pursuant to an agreement with the authority responsible for collecting the tax liability, where the awarding agency is aware of the unpaid tax liability, unless an agency has considered suspension or debarment of the corporation and made a determination that suspension or debarment is not necessary to protect the interests of the Government; or (2) Was convicted of a felony criminal violation under any Federal law within the preceding 24 months, where the awarding agency is aware of the conviction, unless an agency has considered suspension or debarment of the corporation and made a determination that this action is not necessary to protect the interests of the Government. (b) The Offeror represents that-- (1) It is [ ] is not [ ] a corporation that has any unpaid Federal tax liability that has been assessed, for which all judicial and administrative remedies have been exhausted or have lapsed, and that is not being paid in a timely manner pursuant to an agreement with the authority responsible for collecting the tax liability; and (2) It is [ ] is not [ ] a corporation that was convicted of a felony criminal violation under a Federal law within the preceding 24 months. (End of provision) 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE (FEB 1998) This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es): http://farsite.hill.af.mil (End of provision) 52.252-5 AUTHORIZED DEVIATIONS IN PROVISIONS (APR 1984) (a) The use in this solicitation of any Federal Acquisition Regulation (48 CFR Chapter 1) provision with an authorized deviation is indicated by the addition of"(DEVIATION)" after the date of the provision. (b) The use in this solicitation of any DoD FAR Supplement (48 CFR Chapter 2) provision with an authorized deviation is indicated by the addition of "(DEVIATION)" after the name of the regulation. (End of provision) 252.203-7005 REPRESENTATION RELATING TO COMPENSATION OF FORMER DOD OFFICIALS (NOV 2011) (a) Definition. Covered DoD official is defined in the clause at 252.203-7000, Requirements Relating to Compensation of Former DoD Officials. (b) By submission of this offer, the offeror represents, to the best of its knowledge and belief, that all covered DoD officials employed by or otherwise receiving compensation from the offeror, and who are expected to undertake activities on behalf of the offeror for any resulting contract, are presently in compliance with all post-employment restrictions covered by 18 U.S.C. 207, 41 U.S.C. 2101-2107, and 5 CFR parts 2637 and 2641, including Federal Acquisition Regulation 3.104-2. (End of provision) 252.204-7008 COMPLIANCE WITH SAFEGUARDING COVERED DEFENSE INFORMATION CONTROLS (OCT 2016) (a) Definitions. As used in this provision-- Controlled technical information, covered contractor information system, covered defense information, cyber incident, information system, and technical information are defined in clause 252.204-7012, Safeguarding Covered Defense Information and Cyber Incident Reporting. (b) The security requirements required by contract clause 252.204-7012 shall be implemented for all covered defense information on all covered contractor information systems that support the performance of this contract. (c) For covered contractor information systems that are not part of an information technology service or system operated on behalf of the Government (see 252.204-7012(b)(2))-- (1) By submission of this offer, the Offeror represents that it will implement the security requirements specified by National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, ``Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations'' (see http://dx.doi.org/10.6028/NIST.SP.800-171) that are in effect at the time the solicitation is issued or as authorized by the contracting officer not later than December 31, 2017. (2)(i) If the Offeror proposes to vary from any of the security requirements specified by NIST SP 800-171 that are in effect at the time the solicitation is issued or as authorized by the Contracting Officer, the Offeror shall submit to the Contracting Officer, for consideration by the DoD Chief Information Officer (CIO), a written explanation of- (A) Why a particular security requirement is not applicable; or (B) How an alternative but equally effective, security measure is used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection. (ii) An authorized representative of the DoD CIO will adjudicate offeror requests to vary from NIST SP 800-171 requirements in writing prior to contract award. Any accepted variance from NIST SP 800-171 shall be incorporated into the resulting contract. (End of provision) 52.212-2 EVALUATION--COMMERCIAL ITEMS (OCT 2014) (a) See Addendum 52.212-2 (b) A written notice of award or acceptance of an offer, mailed or otherwise furnished to the successful offeror within the time for acceptance specified in the offer, shall result in a binding contract without further action by either party. Before the offer's specified expiration time, the Government may accept an offer (or part of an offer), whether or not there are negotiations after its receipt, unless a written notice of withdrawal is received before award. (End of provision) ADDENDUM TO 52.212-2 Award will be made using the lowest price technically acceptable (LPTA) source selection process. Award will be made to the responsible offeror on the basis of the lowest evaluated price of proposals meeting or exceeding the acceptability standards for non-cost factors. Award maybe made without discussions with offerors (except communications conducted for the purpose of minor clarification). Therefore, each initial offer should contain the offeror's best terms from a technical and price standpoint. However, the Government reserves the right to conduct discussions if it is later determined by the contracting officer to be necessary. Paragraph (a) is hereby replaced with the following: The Government will award a contract resulting from this solicitation to the responsible bidder whose quote, conforming to the solicitation, is Lowest Priced, Technically Acceptable (LPTA). Award will be on an all or none basis. The following factors will be used to evaluate quotes: Technical acceptability and price 1. Technical Capability. The following adjectival ratings will be used in evaluating the offeror's technical quote: Acceptable - To receive this rating, the offerors product shall meet each of the performance objectives set forth in the solicitation. Unacceptable - An unacceptable rating will be assessed on any offeror that presents items that demonstrate any of the following: a. Failure to meet each of the performance objectives set forth in the solicitation. b. Failure to qualify the "yes" or "no" response of each performance objectives in sufficient detail for the Government to determine whether the item satisfactorily meets the requirements of this solicitation. Technical acceptability: Explain how your firm's capability, to include any processes currently in place, that will ensure the specifications identified in Performance Work Statement, are met. Statements that the offeror understands, can or will comply with all specifications, or statements paraphrasing the specification of parts thereof, or phrases such as "standard procedures will be used" or "well-known techniques will be used", will be considered insufficient. • Field service technicians must be qualified and trained on the Carefusion Medstation Systems. • Technicians must have two years of working experience with Carefusion Medstation Systems, effective with the current date. • Contractor must have the capability to use only new or reconditioned parts for which the quality is equal to or better than the Original Equipment Manufacturer (OEM's) original part. • Contractor must have the capability to provide all software upgrades issued by the equipment manufacturer. • Service Technicians must pass background checks to meet installation and Medical Treatment Facility (MTF) access requirements by installation Provost Marshal Office or Base Security. • Contractor must provide technical support via telephone 24 hours per day, 7 days a week, with a telephone response time of not more than 2 hours. • Contractor must provide on-site response within 6 hours of notification (in the event the system is disabled). • Potential contractors must be registered in the System for Award Management (SAM) to be eligible for award. The SAM website is http://www.sam.gov. 2. Price Contractors must submit their proposals to the following address: Regional Health Contracting Office MCAA-S Attn: Mr. Efren Ramirez 3551 Roger Brooke Drive, Room L31-9V Fort Sam Houston, TX 78234-6200 Proposals must be submitted on time to the mailing address above, or by fax to (210)221-3446 Attn: Mr. Efren Ramirez or e-mail to efren.b.ramirez.civ@mail.mil Evaluation Process: All quotes will be evaluated on their price and technical acceptability. The award decision will be based on the lowest priced technically acceptable quote. (End of provision) 52.212-3 OFFEROR REPRESENTATIONS AND CERTIFICATIONS--COMMERCIAL ITEMS (JAN 2017) ALTERNATE I (OCT 2014)
Web Link: FBO.gov Permalink
(https://www.fbo.gov/spg/USA/MEDCOM/DADA09/W81K00-17-T-0357/listing.html)
Place of Performance: Address: Bayne Jones Army Community Hospital, Fort Polk, Louisiana, 71459, United States; Zip Code: 71459
Record: SN04603397-W 20170730/170728232450-36ca286f2382afce61f88021ec670779 (fbodaily.com)
Source: FedBizOpps Link to This Notice
(may not be valid after Archive Date)

| FSG Index | This Issue's Index | Today's FBO Daily Index Page |

Loren Data's SAM Daily™

J -- Preventive Service Maintenance