Loren Data's SAM Daily™

fbodaily.com
Home Today's SAM Search Archives Numbered Notes CBD Archives Subscribe
FBO DAILY - FEDBIZOPPS ISSUE OF APRIL 10, 2016 FBO #5252
DOCUMENT

65 -- Intravenous PUMPS - Attachment

Notice Date
4/8/2016
 
Notice Type
Attachment
 
NAICS
333911 — Pump and Pumping Equipment Manufacturing
 
Contracting Office
U.S. Department of Veterans Affairs;Strategic Acquisition Center;10300 Spotsylvania Ave;Fredericksburg VA 22408
 
ZIP Code
22408
 
Solicitation Number
VA11916N0162
 
Response Due
4/22/2016
 
Archive Date
5/22/2016
 
Point of Contact
Maurice Spencer
 
E-Mail Address
e.Spencer@va.gov<br
 
Small Business Set-Aside
N/A
 
Description
This is sources sought notice: The Department of Veterans Affairs' Strategic Acquisition Center (SAC) is issuing this sources sought synopsis as a means of conducting market research to identify parties having an interest in and the resources to support this requirement for IV Pumps. The result of this market research will contribute to determining the method of procurement. The applicable North American Industry Classification System (NAICS) code assigned to this procurement is 333911. The Product Service Code is 6515. THERE IS NO SOLICITATION AT THIS TIME. This request for capability information does not constitute a request for proposals; submission of any information in response to this market survey is purely voluntary; the government assumes no financial responsibility for any costs incurred. If your organization has the potential capacity to perform supply this commodity, please provide the following information: 1) Organization name, address, email address, Web site address, telephone number, size and type of ownership for the organization, small business status; and 2) Tailored capability statements addressing the particulars of this effort, with appropriate documentation supporting claims of organizational and staff capability. If significant subcontracting or teaming is anticipated in order to deliver technical capability, organizations should address the administrative and management structure of such arrangements. The government will evaluate market information to ascertain potential market capacity to 1) provide the commodity consistent in scope and scale with those described in this notice and otherwise anticipated; 2) secure and apply the full range of corporate financial, human capital, and technical resources required to successfully perform similar requirements; 3) implement a successful project management plan that includes: compliance with delivery schedules; and meeting the rigid listed specifications. BASED ON THE RESPONSES TO THIS SOURCES SOUGHT NOTICE, THIS REQUIREMENT WILL BE PROCURED THROUGH FULL AND OPEN COMPETITION. Telephone inquiries will not be accepted or acknowledged, and no feedback or evaluations will be provided to companies regarding their submissions. Sources Sought Submission Instructions: Interested parties who consider themselves qualified to deliver the listed commodities are invited to submit a response to this Sources Sought Notice by 22 April 2016. All responses under this Sources Sought Notice must be emailed to maurice.spencer@va.gov. NOTICE A.INTERESTED QUOTERS MUST RESPOND TO QUESTIONS ASKED IN THIS RFI. B.BROCHURES AND PAMPLETS ARE NOT CONSIDERED ADEQUATE RESPONSE TO THE QUESTIONS IN THIS RFI. C.QUOTERS MUST ADDRESS THE MTRS AND HOW THEIR PRODUCTS CAN MEET OR EXCEED THE STANDARDS. D.IF QUOTERS ARE UNABLE TO MEET THE STANDARDS OF THE MTRS THEY SHOULD PROVIDE THE REASON WHY. E.YOUR HELP IS GREATLY APPRECIATED; IT WILL ALLOW US TO DEVELOP A BETTER UNDERSTANDING OF WHAT'S AVAILABLE IN INDUSTRY. BACKGROUND: VHA is comprised of 152 medical centers responsible for providing high quality and timely commodities and services for our veterans and their families. The medical facilities are located throughout the United States. Intravenous (IV) Pump is an apparatus designed to deliver measured amounts of a drug or IV solution through IV injection over time. A device used with intravenous fluids to deliver a desired infusion rate by exerting positive pressure on the tubing or on the fluid. Calculations and maintains flow rates prevents unexpected bolus of fluid-used hourly for small and large patients at risk for volume overload, meds, fluids, or medications needing precision. This device administers fluids in a ways that would be impractical, expensive, and unreliable if it were performed manually. Scope: This requirement for the purchase, delivery, installation, testing, training, calibrating, and maintenance services of the Intravenous (IV) Pump in accordance with the technical specifications defined in this sources sought. This procurement will include a standard warranty. A summary of the requirements are the following: a) The contractor shall deliver, install, activate, calibrate, and test (IV) Pumps and associated software. b) The contractor shall provide on-site clinical training on the use of (IV) Pumps and software at each VA site purchasing equipment and/or services under this contract. Training must be provided following installation of each newly purchased machine. c) The contractor shall provide Technical Training to hospital staff responsible for servicing/maintaining this device to include repairs. d) The contractor shall provide a 1 year manufacturer's warranty to protect against manufacturer's defects. e) The contractor shall provide an optional extended warranty plan that extends the original manufacturer's warranty. f) The contractor shall provide an optional annual preventative maintenance plan for each (IV) Pumps and software application. g) The contractor shall provide all required documentation that includes any applicable regulatory documentation, user's guide, complete service manual, design specifications, and training materials. h) The contractor shall provide trade-in for existing (IV) Pump inventory The contractor shall provide all parts, supplies, material, and labor required to meet the technical requirements of this solicitation. SAMPLE DELIVERABLES. MTR #Minimum Technical Requirement MTR 1.1General Medical device establishment shall provide a clear statement of the indications for use of the infusion pump, including, but not limited to: ? The intended use environment; ? The intended route(s) of administration for infusion; ? The fluids or fluid types supported; ? Any specific uses for the infusion pump; ? The indicated treatment population. MTR 1.2General Medical device establishment shall provide a detailed description (including, where appropriate, assembly drawings, bill of materials, schematics, and/or specification control documents) of the infusion pump and its functional components and accessories, including, but not limited to: ? The infusion delivery mechanism; ? The bolus mechanism; ? The drug reservoir; ? Pump tubing and connectors (built-in or external to the pump); ? A user-interface, consisting of the programming unit, display unit, audio and tactile notification units; ? Power supply; ? Pump battery and circuitry to charge and monitor the battery; ? A communication interface, including network components and interfaces to other devices and systems; MTR 1.3General Medical device establishment shall provide a detailed description of the principle of operation of the infusion pump (i.e., the scientific principles behind how the device achieves its intended use). MTR 1.4General Medical device establishment shall provide a detailed description of how the infusion pump is designed for mobility, various environmental conditions (e.g., water exposure, altitude, electromagnetic interference), and ruggedness. MTR 1.5General Medical device establishment shall provide a detailed description of the user interface components of the pump, including keypads, control menus, data entry screens, displays, indicator lights, alarms, auditory and tactile feedback, infusion sets, cassettes, free-flow prevention mechanisms, tubing, latches, doors or other components or accessories of the physical pump that may be manipulated. MTR 1.6General Medical device establishment shall provide a detailed description of the software design, including, but not limited to: ? A drug library or other dose error reduction mechanism; ? A real time clock (RTC); ? On-board memory; ? Pump log; ? Alarm handler; ? Watchdog timer. MTR 1.7General Medical device establishment shall provide a description of all the fluid(s) to be administered by the infusion pump with a listing of tested products. MTR 1.8General Medical device establishment shall list known fluid characteristics that are not compatible with the infusion pump. MTR 2.1Hazard AnalysisMedical device establishment shall identify circumstances in which users and/or patients are exposed to a potential source of harm as well as identify hazards and the potential causes of the hazards. MTR 2.2Hazard AnalysisMedical device establishment shall provide a detailed description of the process for identifying initiating events and sequences of events for each hazardous situation throughout all aspects of device use. MTR 2.3Hazard AnalysisMedical device establishment shall provide an argument demonstrating that known system hazards have been adequately addressed for the device, including, but not limited to: ? Infusion Delivery Error (i.e., intended medication selected and delivery attempted, but failure to deliver within the right time, dose, volume, patient, or anatomical or physiologic site specifications, which can include over-delivery, under-delivery, or delay in delivery situations); ? Incorrect Therapy (i.e., failure to select or deliver the intended medication because the wrong substance was selected for delivery); ? Biological / Chemical Contamination (i.e., unintended contact with biological or chemical substance, or unintended patient or provider physiologic response to intended biological or chemical substance); ? Traumatic Injury (e.g., burns, cuts, abrasions, air embolisms, electric shock, etc.). MTR 3.1ConfigurationInfusion pump shall be multichannel (i.e., two or more channels) allowing for simultaneous infusion from and monitoring of more than one IV line used on one patient. MTR 3.2ConfigurationInfusion pump shall securable to an IV pole intended for transport and capable of attaching at least two multichannel infusion pumps on a single IV pole. MTR 4.1Delivery Infusion pump shall be capable of delivering continuous and intermittent (non-continuous) infusions. MTR 4.2Delivery Infusion pump shall be capable of delivering secondary (i.e., piggyback) infusions. MTR 4.3Delivery Infusion pump shall be capable of automated secondary (piggyback) infusion that switches from a programmed secondary flow rate to the primary flow rate once the device has delivered the secondary volume. MTR 4.4Delivery Infusion pump shall allow flow to be visually assessed. MTR 5.1Administration SetsMedical device establishment shall identify any dedicated administration set or the specifications and/or specific models of infusion sets that are appropriate for use with the infusion pump. MTR 5.2Administration SetsInfusion pump shall have administration sets that protect against unintended gravity flow when the set is removed from the infusion pump. MTR 5.3Administration SetsInfusion pump shall have set-based free-flow protection (e.g., anti-free-flow clamp or valve). MTR 5.4Administration SetsInfusion pump shall have administration sets that have an air-trapping reservoir or another means of removing air from the set. MTR 5.5Administration SetsInfusion pump shall have administration sets that are free of di(2-ethylhexyl)phthalate (DEHP). MTR 5.6Administration SetsInfusion pump shall have administration sets that resist damage from long-lasting crimping from either clamps or the pumping mechanism. MTR 5.7Administration SetsInfusion pump shall have administration sets with needleless IV connection. MTR 6.1SettingsInfusion pump shall be calibrated in flow settings of milliliters per hour (mL/hr). MTR 6.2SettingsInfusion pump shall have a flow range of 0.1 milliliters per hour (mL/hr) to at least 999 mL/hr. MTR 6.3SettingsInfusion pump shall have a Keep Vein Open (KVO) rate of 0.1 milliliters per hour (mL/hr) to at least 5 mL/hr. MTR 6.4SettingsInfusion pump shall have a Volume To Be Infused (VTBI) able to be set at values from 1 milliliter (mL) to at least 9,999 mL. MTR 6.5SettingsInfusion pump shall have a minimum setting increment of 0.1 milliliters per hour (mL/hr). MTR 6.6SettingsInfusion pump shall be capable of changing a flow setting with no more than a 10-second interruption in pumping. MTR 6.7SettingsInfusion pump shall be capable of patient weight entry. MTR 6.8SettingsInfusion pump shall have a maximum patient weight setting of 500 kg. MTR 7.1Display Infusion pump shall provide visual feedback to the user. MTR 7.2DisplayInfusion pump shall have a refresh rate of at least 80Hz (100Hz) to avoid flicker. MTR 7.3DisplayInfusion pump shall display the drug name and dose being infused by each channel in TALLman lettering. MTR 7.4DisplayInfusion pump shall display complete words in preference to abbreviations MTR 8.1Accuracy Medical device establishment shall define the accuracy specifications over the range of selectable flow rates and bolus volumes, including information on: time period over which accuracy is specified; time to reach steady-state flow accuracy; effect of infusion rate changes or bolus delivery on accuracy. MTR 8.2AccuracyMedical device establishment shall identify any factors that may affect flow accuracy, such as ambient temperature, fluid temperature, pressure (e.g., head-height, backpressure, atmospheric pressure), fluid viscosity, or changes in flow rate or bolus delivery (e.g., such as when titrating medication). MTR 8.3AccuracyInfusion pump shall be capable of maintaining accurate (i.e., flow error less than five percent of the flow setting) delivery of liquids through intravenous (IV) routes for therapeutic and/or diagnostic purposes. MTR 9.1DERS / Drug LibraryInfusion pump shall have a built-in dose error reduction system (DERS) to warn users of programming errors that could result in under- or over-delivery. MTR 9.2DERS / Drug LibraryInfusion pump shall default to DERS on startup. MTR 9.3DERS / Drug LibraryInfusion pump shall have DERS functionality for secondary infusions that is equivalent to that for primary infusions. MTR 9.4DERS / Drug LibraryInfusion pump shall allow for selecting a drug library for the specific clinical care area, selecting the drug and concentration to be administered, and responding to pump alerts. MTR 9.5DERS / Drug LibraryInfusion pump shall have a drug library that allows for a minimum of 20 care areas. MTR 9.6DERS / Drug LibraryInfusion pump shall have a drug library that allows for a minimum of 500 drugs per care area. MTR 9.7DERS / Drug LibraryInfusion pump shall be able to specify entire drug name(s) (i.e., without abbreviations). MTR 9.8DERS / Drug LibraryInfusion pump shall have a drug library that is configurable to a facility's current ordering and delivery practices such that minimum and maximum dose limits as well as standard concentrations can be established for drugs in each clinical location. MTR 9.9DERS / Drug LibraryInfusion pump shall have a drug library that allows limits for intermittent (non-continuous) infusions. MTR 9.10DERS / Drug LibraryInfusion pump shall have "soft" and "hard"-limit capabilities to prevent against medication errors. MTR 9.11DERS / Drug LibraryInfusion pump shall trigger an alert if the same drug or solution is programmed on more than one channel. MTR 9.12DERS / Drug LibraryInfusion pump shall be capable of non weight-based and weight-based dosing options. MTR 9.13DERS / Drug LibraryInfusion pump shall prompt the user to enter a patient weight when a weight-based drug (i.e., a drug that is dosed by patient weight) is selected from the Drug Library. MTR 9.14DERS / Drug LibraryInfusion pump shall trigger an alert if different patient weights are entered on different channels. MTR 9.15DERS / Drug LibraryInfusion pump shall prompt the user to confirm all patient weight changes. MTR 9.16DERS / Drug LibraryInfusion pump shall have log-analysis software to aggregate the alert information from infusion pumps' logs. MTR 9.17DERS / Drug LibraryInfusion pump shall have a drug library is wirelessly updated. MTR 9.18DERS / Drug LibraryInfusion pump shall have drug parameters that are automatically calculated, based on: drug selected, weight or body surface area (BSA) entry, rate or dose entry, VTBI entry. MTR 9.19DERS / Drug LibraryInfusion pump shall NOT allow for automatic dose calculation if any of the values needed (e.g., drug, weight, rate, VTBI) for accurate drug dosing are missing. MTR 10.1AlarmsMedical device establishment shall provide a detailed description of all alarm and/or information messages and recommended actions when alarms and/or information messages are provided. MTR 10.2AlarmsInfusion pump shall issue an alarm (audio and visual) in response to a hazardous situation and each alarm shall be clearly indicated to the user. MTR 10.3AlarmsInfusion pump shall have volume control for audible alarms in which the lowest setting is still able to be heard. MTR 10.4AlarmsInfusion pump shall have visual alarm indicators that can be clearly seen from at least 15 feet away. MTR 10.5AlarmsInfusion pump shall alarm due to one or more hazards, including, but not limited to: ? Occlusion (supply side and patient side); ? Air-in-line; ? Free flow/Improper flow of fluid; ? Depleted battery or no power; ? Defective battery; ? Low or Empty reservoir; ? No reservoir; ? Dose limit/Bolus limit exceeded; ? Panel unlocked/door open; ? Key pressed alarm; ? Power on self test (POST) failure - issued when one of the POST tests fails; ? ROM/RAM CRC test failure; ? Tone test failure; ? Pump mechanism failure; ? Watchdog alarm - issued when the watchdog timer expires; ? Overheating; ? Drug library mismatch; ? Infusion set not loaded properly. MTR 10.6AlarmsInfusion pump shall continuously alarm and indicate imminent battery depletion 30 minutes before the battery is depleted. MTR 10.7AlarmsInfusion pump shall have a clear, persistent indication (i.e., warning) displayed any time the DERS is not in use. MTR 10.8AlarmsInfusion pump shall allow for momentary silence of audible alarms in which the alarm automatically reactivates after no longer than two minutes if the alarm condition is still present. MTR 10.9AlarmsInfusion pump shall NOT allow for the possibility to indefinitely disable alarms without correcting the problem that triggered the alarm. MTR 1.68ControlsInfusion pump shall have control mechanisms to prevent or detect hazardous situations, which include, but are not limited to: ? Power on self test (POST) checks - performed during pump startup or initialization; ? Battery test; ? Stuck key test; ? Tone test; ? Pump mechanism failure test; ? Watchdog interrupt tests; ? (Periodic) System checks - including a CPU test and ROM/RAM CRC tests; ? Air detection sensors; ? Environmental monitoring sensors; ? Sensor checks - to check the proper functioning of sensors attached to the pump, if any; ? Dose error reduction checks. MTR 11.1ControlsInfusion pump shall be fluid-proof and automatically alarm and shut down if fluid penetrates the electronic circuitry. MTR 11.2ControlsInfusion pump shall detect upstream occlusions and alarm and terminate flow if 50 to 100 microliters of air enters the line. MTR 11.3ControlsInfusion pump shall have a memory in the event of temporary power interruption such that it can retain information including, but not limited to: programmed settings, total volume infused, alarm occurrences, system errors, user key presses, and the time and date of each event. MTR 11.4ControlsInfusion pump shall indicate if patient weight has not been entered. MTR 11.5ControlsInfusion pump shall indicate if a selected drug has non weight-based and weight-based dosing options. MTR 12.1LogsInfusion pump shall have data log(s) that store all user interactions and pump settings for at least one week of operation. MTR 12.2LogsInfusion pump shall have a date- and time-stamped event log that indicates at a minimum the error codes, alarms, flow rate, and key presses. MTR 12.3LogsInfusion pump shall have a separate log for recording dose limit events and user responses (e.g., override soft limit, reprogram pump, etc.). MTR 12.4LogsInfusion pump shall be capable of downloading the data log(s) to a computer in an easy-to-analyze format (e.g., comma-separated values [CSV] file extension). MTR 12.5LogsInfusion pump shall be capable of printing out all information stored in the data log(s). MTR 12.6LogsInfusion pump shall have data log(s) that can be accessed wirelessly. MTR 12.7LogsInfusion pump shall have log(s) that are not lost if the device is turned off for an extended period, if the battery is depleted or changed, or if a new patient is selected. MTR 12.8LogsInfusion pump shall have data log(s) that include all pump settings, setting changes, and alarms. MTR 12.9LogsInfusion pump codes from log(s) shall have code interpretation(s) readily available in a service or operator manual, if codes are used. MTR 13.1PowerInfusion pump shall have integral battery(ies) that can run for at least four hours at a flow rate of 25 mL/hr with all channels running. MTR 13.2PowerInfusion pump shall contain battery(ies) that can fully recharge in less than eight hours independently of the main power switch. MTR 13.3PowerInfusion pump shall automatically switch over to battery power in the event of a line-power failure. MTR 13.4PowerInfusion pump shall start up immediately when plugged in to line power even with a depleted battery and recharge the battery once plugged in without any other intervention. MTR 14.1Connectivity Medical device establishment shall provide a detailed description of any communication capabilities between the infusion pump and a hospital information management system or another device. MTR 14.2Connectivity Medical device establishment shall provide a detailed description of the incorporated radio-frequency wireless technology, including information about the specific RF wireless technology and characteristics, the RF wireless technology's use and functions (e.g., remote monitoring or control, software updates, etc.), the data to be transmitted including any alarms transmitted wirelessly, quality of service (QoS) needed, wireless security measures and protocols, and any limitations or restrictions relating to coexistence with other RF wireless technology and electromagnetic compatibility of the wireless technology. MTR 14.3Connectivity Infusion pump shall have wireless capabilities for transferring data to and from a centralized server over a hospital's wireless network. MTR 14.4Connectivity Infusion pump shall be capable of both wireless and wired communication. MTR 14.5Connectivity Infusion pump shall have a data port that allows for transfer of infusion data. MTR 15.1IT SecurityMedical device establishment shall provide a complete the VA Form in Appendix A from VA Directive 6550 Pre-Procurement Assessment of Networked Medical Systems. Provide a copy of VA Directive 6550 Appendix A Form. MTR 15.2IT SecurityMedical device encryption module shall have FIPS 140-2 certification in accordance with VA security requirements for medical devices/systems connected to VA information networks. Provide certificate number. MTR 15.3IT SecurityMedical device establishment shall ensure the security of all procured or developed systems and technologies, including their subcomponents (hereinafter referred to as "Systems"), throughout the life of this contract and any extension, warranty, or maintenance periods. This includes, but is not limited to workarounds, patches, hotfixes, upgrades, and any physical components (hereafter referred to as Security Fixes) which may be necessary to fix all security vulnerabilities published or known to the vendor anywhere in the Systems, including Operating Systems and firmware. The vendor shall ensure that Security Fixes shall not negatively impact the Systems. MTR 15.4IT SecurityMedical device application software (e.g. image acquisition, manipulation, reconstruction, analysis, display, etc.), and any Off the Shelf commercial Operating System (OS) necessary for operation and maintenance of the system being purchased, are to be provided by the contractor. The OS must be the latest major release currently available for purchase in the commercial marketplace or no older than one release prior to the latest major release. Older releases may be acceptable if authorized in writing by the requesting facility and approved by the Contracting Officer. Application software updates compatible with the offered system's hardware shall be kept current at no cost to the Government as long as the equipment is in use in VA, DoD or any other Government agency health facility. MTR 15.5IT SecurityMedical device software and commercial OS licenses provided must be perpetual. MTR 15.6IT SecurityUpdates to the operating system or system application that remedy bugs or defects in system function should be provided free of charge for the life of the product. If the updates are embedded with system upgrades that add additional functionality and the vendor is unable to provide the update as a distinct deliverable separate from the upgrade, the VA will not be liable for the cost. MTR 15.7IT SecurityAll medical device hard drives or other media containing VA sensitive data must follow VA's currently published media sanitization policy - VA Handbook 6500.1 Electronic Media Sanitization. MTR 15.9IT SecurityMedical device establishment shall identify if the infusion pump is capable of being remotely controlled from a distance and provide a detailed description of the measures incorporated to address hazards. MTR 16.1Cleaning / DisinfectionMedical device establishment shall provide detailed cleaning and disinfection instructions for reusable infusion pumps and accessories. MTR 16.2Cleaning / DisinfectionMedical device establishment shall identify cleaning and disinfection agents that are suitable for device reuse. MTR 16.3Cleaning / DisinfectionInfusion pump shall NOT be damaged by diluted bleach or other commonly used cleaning and disinfecting solutions. MTR 17.1StandardsMedical device shall meet ANSI/AAMI/IEC 60601-2:2007/(R) 2012, or equivalent electrical safety standard, that applies to the basic safety and essential performance of medical electrical equipment and medical electrical systems. MTR 18.1RegulationsMedical device manufacturer shall be a registered establishment with the U.S. Food and Drug Administration (FDA) in accordance with 21 CFR Part 807. MTR 18.2RegulationsMedical device shall be listed with U.S. Food and Drug Administration (FDA) in accordance with 21 CFR Part 807. MTR 18.3RegulationsMedical device shall be classified by U.S. Food and Drug Administration (FDA) under Infusion Pump in accordance with 21 CFR § 880.5725. MTR 18.4RegulationsMedical device shall be legally cleared for commercial distribution within the United States (U.S.) in accordance with the Federal Food, Drug, and Cosmetic Act as authorized by U.S. Food and Drug Administration (FDA) and as evidenced by Premarket Notification 510(k) clearance. Provide 510(k) number. MTR 19.1InstructionsA minimum of five copies of the user/operator's manual shall be provided. MTR 19.2InstructionsA minimum of five copies of the technical/service manual shall be provided. MTR 20.1TrainingClinical training shall be provided to end-users of this medical device that covers how to operate the device safely and effectively. MTR 20.2TrainingTechnical training shall be provided to hospital staff responsible for servicing/maintaining this medical device that covers maintenance and repair of the device. MTR 21.1Service / SupportMedical device establishment shall provide technical support and repair parts must be readily available whenever as well as wherever the infusion pump is marketed. MTR 21.2Service / SupportAll software keys for service and/or support of the infusion pump shall be provided to the facility Biomedical Engineering Program Manager. MTR 21.3Service / SupportAll vendors shall provide service/maintenance/diagnostic software and associated security keys to provide for in-house service of the equipment as a line item on quotes. If the license is at no cost or has a cost associated with it and the facility elects to purchase the item, the vendor will provide no cost renewal of the software license or security key for the duration of the installation at a VHA facility. At a minimum, the service software will include system diagnostics down to board or module level, error codes and definitions, and system setup capabilities to include networking, DICOM configuration and peripheral connectivity. The facility Biomedical Engineering Program Manager will make the determination of technical competency for the servicing Biomedical Engineering Support Specialist or Engineer and OEM training will not be a pre-requisite for provision of the service software. MTR 21.4Service / SupportUpdates to the operating system or system application that remedy bugs or defects in system function shall be provided free of charge for the life of the product. If the updates are embedded with system upgrades that add additional functionality and the vendor is unable to provide the update as a distinct deliverable separate from the upgrade, the VA will not be liable for the cost. MTR 21.5Service / SupportUpgrades that add system functionality shall be at no cost during the warranty period. MTR 21.6Service / SupportMedical device establishment shall provide a detailed listing, including but not limited to part description and price, for all replacement parts. MTR 22.1WarrantyStandard warranty shall be no less than one year to include parts and labor that becomes active upon the date of equipment acceptance. MTR 23.1Trade-InsExisting infusion pump inventory shall be considered for trade-in. INSTRUCTIONS: Submit a brief description, five (5) pages or less (including cover letter) that demonstrates how your company can provide (IV) Pumps throughout the Veterans Health Administration. Provide your past experience in performing these services for other government (federal or states) agencies; as evidence list three contracts in the past five years, include POC and phone number. Responses should include business size, business type, socio-economicstatus, and capability. Please submit your responses to the following contracting specialist Mr. Maurice Spencer, at Maurice.spencer@va.gov. Responses are due by 3:00pm EST April 22, 2016. DISCLAIMER This sources sought is issued solely for information and planning purposes only and does not constitute a solicitation. All information received in response to this sources sought that is marked as proprietary will be handled accordingly. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. Responders are solely responsible for all expenses associated with responding to this sources sought. NOTICE F.INTERESTED QUOTERS MUST RESPOND TO QUESTIONS ASKED IN THIS RFI. G.BROCHURES AND PAMPLETS ARE NOT CONSIDERED ADEQUATE RESPONSE TO THE QUESTIONS IN THIS RFI. H.QUOTERS MUST ADDRESS THE MTRS AND HOW THEIR PRODUCTS CAN MEET OR EXCEED THE STANDARDS. I.IF QUOTERS ARE UNABLE TO MEET THE STANDARDS OF THE MTRS THEY SHOULD PROVIDE THE REASON WHY. J.YOUR HELP IS GREATLY APPRECIATED; IT WILL ALLOW US TO DEVELOP A BETTER UNDERSTANDING OF WHAT'S AVAILABLE IN INDUSTRY.
 
Web Link
FBO.gov Permalink
(https://www.fbo.gov/notices/f9c74e391bc13f1c9cbe8832775c1b27)
 
Document(s)
Attachment
 
File Name: VA119-16-N-0162 VA119-16-N-0162_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=2664788&FileName=VA119-16-N-0162-000.docx)
Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=2664788&FileName=VA119-16-N-0162-000.docx

 
Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 
Record
SN04078130-W 20160410/160408234221-f9c74e391bc13f1c9cbe8832775c1b27 (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 |
ECGrid: EDI VAN Interconnect ECGridOS: EDI Web Services Interconnect API Government Data Publications CBDDisk Subscribers
 Privacy Policy  Jenny in Wanderland!  © 1994-2024, Loren Data Corp.