HOSPITAL SUPPLY DIV - PHILADELPHIA

and/or identification, the contract number and delivery order numbers
(ii) Reasons for correction, removal or recall.
(iii) Proposed offers for return for credit, replacement or corrective action shall be forwarded to the facility POC and Contracting Officer, for consideration by the Government.
(3.) The vendor will be responsible for all costs associated with a recall.
(h.) REPAIR PARTS, ACCESSORIES, CONSUMABLES, AND TOOLS
(1.) The contractor shall guarantee that the Government will be able to purchase all required repair (spare) parts, accessories, consumables and tools needed to operate and maintain a system, from the contractor for a minimum of five years from the date of final system acceptance. The vendor must include all such items in their contract that are TAA clause compliant. Repair parts are defined as end products/items that will be procured on their own after system has been purchased and used to replace items that have failed or must be replaced to keep the system operational. Tools include repair tools, calibration tools, and any other tools needed to operate and maintain the system. All repair parts, accessories, consumables, and tools that are end products from Trade Agreement Act (TAA) Clause compliant countries; including U.S.-made end products, qualifying country end products and designated country end products as defined by DFARS 252.225-7021 Trade Agreements must be offered as part of the vendor's contract. The items must comply with all other terms and conditions in this solicitation, including Berry Amendment Compliance.
(2.) Vendor shall provide a full listing of all repair parts, accessories, consumables, and tools (must include a description, weight, dimensions, Country of Origin, and price) and distinguish the items to be considered high-failure repair parts (identified by Original Equipment Manufacturer (OEM) and Government). The list shall be updated and maintained for the life of the contract.
(3.) For repair parts, accessories, consumables and tools that are not TAA Clause compliant, the vendor must provide them in the above referenced repair parts list and agree to provide an updated list of non-TAA Clause compliant repair parts for the life of the contract. Non-TAA Clause compliant repair items will not be added to the vendor's
SPE2D1-20-R-0001
SECTION B SUPPLIES OR SERVICES AND PRICES OR COSTS (CONTINUED)
contract. The vendor shall agree that if any items become TAA Clause compliant during the life of the contract, then the vendor shall immediately notify the Government and request that they be added to the contract.
(i.) SUSTAINMENT PLANNING SUPPORT: The vendor shall support Government planning for the sustainment of the systems. This shall include being available to discuss with Government users how to best deploy, maintain, operate the systems, and any other considerations. This shall include providing the Government needed information and data needed to plan out the life-cycle support of the system.
VI. INFORMATION TECHNOLOGY REQUIREMENTS
DEPARTMENT OF DEFENSE (DOD) CYBERSECURITY, RISK MANAGEMENT FRAMEWORK (RMF),
AND/OR SERVICE INFORMATION ASSURANCE (IA) REQUIREMENTS (ONLY ORDERS FOR DOD
CUSTOMERS)
NOTE: For the purposes of this solicitation; Cybersecurity, RMF, and IA requirements are used synonymously to refer to the same set of DoD Cybersecurity regulations and policies.
All DoD requirements for equipment that has an operating system or the capability to be connected to a network shall be required to meet DoD Cybersecurity and individual Military Service IA/RMF requirements. DoD Cybersecurity and Service specific IA/RMF requirements mandate that equipment must receive an Authorization to Operate (ATO) prior to being able to be connected to any DoD network. ATO is Service specific, so reciprocity is dependent on which Services are involved and is not guaranteed. As the requirements may change, the latest specific IA/RMF requirements should be obtained from the requiring site, the Service IA/RMF POC or from the DLA Contracting Officer prior to quoting. Failure to agree to Cybersecurity or Service IA/RMF requirements may result in rejection of the vendor's offer. Failing to disclose that a system cannot meet IA/RMF requirements, failure to meet certification timeframes or failure to receive ATO may result in termination for default under clause 52.249-8 “Default (FixedPrice Supply and Service).".
The following references are applicable DoD Cybersecurity Regulations and Policies:
(1.) United States Statutes (i.) The Health Insurance Portability and Accountability Act of 1996 (HIPAA) (ii.) The Federal Information Security Management Act (FISMA) (iii.) The E-Government Act of 2002
(2.) Office of Management and Budget (OMB) (i.) Circular A-130 (ii.) Guidance M-05-24, Implementation of Homeland Security Presidential Directive (HSPD) 12-Policy for a Common Identification Standard for Federal Employees and Contractors
(3.) National Institute of Standards and Technology (NIST) (i.) The following publications are located at http://www.nist.gov/publication-portal.cfm (ii.) NIST Special Publication (SP) 800-37 Guide for Applying the Risk Management Framework (RMF) to Federal Information Systems (iii.) NIST SP 800-53 Security and Privacy Controls for Federal Information Systems and Organizations
(4.) Federal Information Processing Standards (FIPS)
SPE2D1-20-R-0001
SECTION B SUPPLIES OR SERVICES AND PRICES OR COSTS (CONTINUED)
(i.) The following publications are located at http://www.nist.gov/itl/fipscurrent.cfm (ii.) FIPS Publication (FIPS PUB) 140-2, Security Requirements for Cryptographic Modules (iii.) FIPS PUB 199 Standards for Security Categorization of Federal Information and Information Systems (iv.) FIPS PUB 201-2, Personal Identity Verification of Federal Employees and contractors
(5.) Department of Defense (DoD) (i.) The following publications are located at http://www.dtic.mil/whs/directives/ (ii.) DoD Instruction 5200.2, DoD Personnel Security Program (PSP) (iii.) DoD Instruction 8500.1, Cybersecurity (iv.) DoD Instruction 8520.02, Public Key Infrastructure (PKI) and Public Key (PK) Enabling (v.) DoD Instruction 8510.01, Risk Management Framework Process (RMF) (vi.) DoD Instruction 8551.1, Ports, Protocols, and Services Management (PPSM) (vii.) DoD Instruction 8580.02, Security of Individually Identifiable Health Information in DoD Health Care Programs (viii.) DoD Instruction 6025.18, Privacy of Individually Identifiable Health Information in DoD Health Care Programs (ix.) DoD Directive 5400.11, DoD Privacy Program (x.) DoD Manual 5400.11-R, Department of Defense Privacy Program
VII. ELECTRONIC CATALOG SYSTEM (ECAT)
(a.) Description of ECAT: DLA Troop Support operates and manages the DLA Electronic Catalog System (ECAT). All catalog updates, changes, or deletions will be processed by the DLA Troop Support Contracting Officer. DLA Troop Support's Medical Supply Chain developed ECAT to streamline its business practices and expand its range of procurement options. ECAT is a Net-centric ordering, distribution, and payment system providing Department of Defense and other Federal customers access to multiple manufacturer and distributor commercial catalogs at discounted prices along with specialty noncommercial items as envisioned under this program. ECAT automates the entire customer procurement cycle from searching for products, to creating reorder lists, to submitting an order, to approving an order, to receiving and paying for an order. The MediPrice loader catalog is the prescribed format for entering vendors contract items on ECAT.
(b.) Terms and Conditions Applicable to ECAT:
(1.) The contractor agrees to use the ECAT system to display its catalog for items available to all authorized users.
(2.) The contractor agrees to let all DLA customers authorized to enter the ECAT system to view any information displayed in the system.
(3.) DLA Troop Support may place manual orders under any contract awarded against this solicitation.
(4.) Two contract numbers will be assigned to each contract award. One Administrative contract for automated orders through ECAT and the basic contract number for manual orders placed by DLA Troop Support contract specialists.
(5.) The contractor shall provide its own computer hardware and software necessary to transmit and receive electronic orders.
(6.) All items will be identified by the manufacturer's name and part numbers and conform to the manufacturer's
SPE2D1-20-R-0001
SECTION B SUPPLIES OR SERVICES AND PRICES OR COSTS (CONTINUED)
specifications.
(7.) All terms and conditions, including the contract maximum, of the vendor's basic contract, shall remain in full force and effect for any orders issued through ECAT and manual orders.
(8.) Individual ECAT delivery orders cannot be modified besides just being cancelled if approved by the Contracting Officer within five calendar days of order issuance. Vendors shall accept all orders issued through ECAT, and vendors are not authorized to reject (kill) any order without written preapproval of DLA.
(9.) In order to add/change items in ECAT, the items must first be added/changed under the basic contract. If any basic contract item changes, including items making up an ECAT administrative configuration (defined in Section 14. ii. below), the vendor shall immediately notify the Contracting Officer and shall not accept any orders for the item or ECAT administrative configuration until it matches the basic contract.
(10.) The following items shall not be offered under an ECAT administrative contract even if they are on the basic contract:
(i.) Any item, installation or service that is not pre-priced on the MediPrice loader catalog. (ii.) Any incidental service that is not pre-priced on the MediPrice loader catalog. (iii.) Non-TAA items currently on the MediPrice loader catalog under the Systems Components category as defined in TAA Compliance Section. (iv.) Zero dollar items.
(11.) For all DoD customers, the vendor shall only offer and accept system requirements under their ECAT administrative contract where they agree to offer systems that meet DoD Cybersecurity and individual Military Service Risk Management Framework (RMF) requirements, along with having a supported operating system. By accepting any DoD requirement in ECAT, the vendor confirms that they have a valid RMF Authorization to Operate (ATO) or agrees to go through the RMF approval process and obtain an ATO. Additionally, vendors are required to complete and provide a completed service specific RMF Cybersecurity Questionnaire template upon request by the customer. A vendor performing on a DoD Customer order issued through ECAT constitutes agreement to comply with the applicable Services' RMF requirements.
Vendors may offer systems that do not meet DoD Cybersecurity RMF requirements under an administrative ECAT contract solely for purchase by non-DoD customers, such as the Veterans Administration. This must be noted on the vendor's MediPrice loader catalog by adding “NOT COMPLIANT WITH RMF” in the BEGINNING of the item's Product Description.
(12.) When applicable for a specific medical equipment item, the vendor shall only offer and accept system requirements under their ECAT administrative contract where they agree to offer systems that are able to interface with MHS GENESIS/Cerner Millennium Electronic Health Record (EHR). A vendor performing on a DoD Customer order issued through ECAT constitutes agreement to provide a system that shall interface with MHS Genesis/Cerner Millennium EHR. Applicability shall be determined prior to adding the item to ECAT.
(13.) Each individual item, defined as each item on the MediPrice loader catalog that has its own part number or administrative configuration part number and price, on an ECAT administrative contract shall be considered an end product; thus, it must be in compliance with the Trade Agreement Act (TAA).
(14.) The vendor must follow one of the following strategies for offering systems through ECAT:
SPE2D1-20-R-0001
SECTION B SUPPLIES OR SERVICES AND PRICES OR COSTS (CONTINUED)
(i.) The entire system can be bought through a single part number.
(ii.)Vendors may offer ECAT administrative configuration part numbers for ease of ordering by customers for full systems where there is no single part number configuration offered and the end product system is built from multiple part numbers. (A.) Each ECAT administrative configuration part number shall be comprised of existing part numbers that are already on the vendor's basic contract. (B.) The total price of the ECAT administrative configuration part number must be at or below the combined price of all individual contract part numbers that make up the administrative configuration. (C.) If any part number's pricing goes down on the basic contract, than the ECAT configuration price must be reduced accordingly. (D.) ECAT administrative configuration part numbers may only be used for ordering through the administrative ECAT contract and cannot be used for regular orders through the basic contract. (E.) ECAT administrative configuration part number additions and changes must occur via submission of an ECAT Administrative Configuration Form, supplemental to the MediPrice loader catalog spreadsheet, matching the item(s) in the basic contract. The MediPrice loader catalog and ECAT Administrative Configuration Form will be provided by the Contracting Officer to any contract holder considering to establish an administrative ECAT contract. Items or their pricing may not be changed without formal review, approval and upload to ECAT by DLA.
(iii.) The entire system can be bought by combination of a base system part number and additional customization part numbers already on the basic contract. The base system would be a partial configuration that all customers would receive and would be a single part number or single administrative configuration part number. Further customization to achieve a fully operational system would occur by adding a limited number of accessory or component part numbers on top of the base system. If utilizing this approach, the vendor must ensure that a customer can order a full system by selecting no more than 10 part numbers in ECAT. This method may result in multiple orders being issued that together would make up a single system. This could be caused by customer error or system issues, but the vendor would be obligated to accept all orders if using this method.
(c.) Electronic Catalog System (ECAT) Technical Requirements
(1.) The Contractor shall submit and maintain an Electronic Price and Product Catalog(s) listing all items available to the customers ordering under this contract. The submission of the data shall be by the MediPrice loader catalog template format.
(2.) For the most current guidelines to submit MediPrice additions, changes or deletions, refer to https://www. medical.dla.mil/Portal/ under the ECAT tab, and look for NSN/Part Number: 3RFQ3SEESOW