OR Management System

Added: May 12, 2017 4:51 pm Modified: Jun 07, 2017 10:17 amTrack Changes The purpose of this Amendment is to extend the response date to 06/22/2017 4:30pm for RFQ VA246-17-Q-0806 Combined Solicitation.

Added: May 12, 2017 4:51 pm Modified: May 31, 2017 5:32 pmTrack Changes The purpose of this Amendment is to give the response to the question received and to extend the response date to 06/7/2017 for RFQ VA246-17-Q-0806 Combined Solicitation. All bid of RFQ shall be email to Audrey.wooten@va.gov by 2pm 6/6/2017.

Response to questions

Does the solution have to be FISMA compliant?

Answer: Yes

Does the solution have to be cleared by VA Software Assurance Team for source code scanning using Fortify?

Answer: Unable to provide at this time.

Does VA require source code to be submitted for security clearance for this project?

Answers: No

Does the solution have to be cleared by Nessus scans?

Answer: Unable to provide at this time

Does the solution have to be part of VA Risk Vision system and have an approved ATO?

Answer: Unknown at this time.

Will VA provide the interface for read and write to VistA using VistA exchange or directly to VistA? As far as it is known yes

Will VA provide the interface to ARK using HL7 or proprietary Philips interface to Compurecord? Answer: HL7

Does the SAFE Software License brand name or equal need to be OI&T TRM Approved?

Answer: yes

Does the SAFE Application brand name or equal need to be OI&T TRM Approved?

Answer: yes

Does the Real View Software License brand name or equal need to be OI&T TRM Approved?

Answer: yes

Does the Real View Command Center Software License brand name or equal need to be OI&T TRM Approved?

Answer: yes

Does the Real View Command Center Software brand name or equal need to be OI&T TRM Approved?

Answer: yes

Does the Sonitor RTLS Software Engine License brand name or equal need to be OI&T TRM Approved?

Answers: yes

Will the Sonitor RTLS Software Engine License brand name or equal need to be compatible with the existing RTLS solution already deployed at the Salisbury VAMC?

Answers: N/A

Does the Sonitor Wireless Patient CareTag S-Tag G2 brand name or equal need to be OI&T TRM Approved?

Answers: yes

Will the Sonitor Wireless Patient CareTag S-Tag G2 brand name or equal need to be compatible with the existing RTLS solution already deployed at the Salisbury VAMC?

Answers: N/A

Does the Sonitor HDR Wireless Gateway Receiver (REC-A150) brand name or equal need to be OI&T TRM Approved? Answers: yes

Will the Sonitor HDR Wireless Gateway Receiver (REC-A150) brand name or equal need to be compatible with the existing RTLS solution already deployed at the Salisbury VAMC?

Answers: N/A

Does the Dell Small Form Factor PC brand name or equal need to be OI&T TRM Approved?

Answers: no

Does the IP Camera for each OR brand name or equal need to be OI&T TRM Approved?

Answers: no

If all of the commercial items do not need to be OI&T TRM Approved, will the Salisbury VA medical center be securing waivers to use the commercial items requested?

Answers: no

Does the VA require successful completion of VistA integration testing in the VA SandBox and EHMP programs for HL7 interfaces?

Answers: yes

Will the VA be providing VistA interface hostnames and port designations?

Answers: yes

Can you provide the brand name for CLIN 0016?

Answers: Sonitor

Is CLIN 0026 a requirement?

Answers: yes

Can a brand name or equal solution leverage the existing VA wireless network?

Answers: no

Is the Physician mobile app described in the Scope required to be OI&T TRM approved?

Answers: yes

Is the Physician mobile app described in the Scope required to be MASA scanned?

Answers unknown

Is the Physician mobile app described in the Scope required to be approved by VHA software assurance team after source code scanning by Fortify?

Answers: unknown

What mobile devices will the Physician mobile app described in the Scope run on?

Answers: Android and Iphone

How many mobile devices will the Physician mobile app run on?

Answers: approximately 50

Will the VA be providing the mobile devices running the Physician mobile application?

Answer: no

Will the mobile devices running the Physician mobile app be FIPS 140-2 certified?

Answers: If pt. info is included

Will the mobile devices running the Physician mobile app be OI&T MASA scanned, fortify scanned and OI&T TRM approved?

Answer: TRM

Will the mobile devices running the Physician mobile app be on the VA wireless network?

Answer: no

Is the OR charge mobile tablet described in the Scope required to be OI&T TRM approved, OI&T MASA scanned, VHA Software Assurance Fortify scanned?

Answer: unknown

What is manufacture and model will the OR charge mobile tablet described in the Scope? Answer: Vendor to provide

How many OR charge mobile tablets are required? Answer: approximately 1

Will the OR charge mobile tablet be FIPS 140-2 certified,

Answer: yes

Will the OR charge mobile tablet be OI&T MASA scanned, VHA Software Assurance Fortify scanned and OI&T TRM approved?

Answers: TRM

Will the OR charge mobile tablet be on the VA wireless network?

Answer: yes

Will the bedside PCs described in Scope 2.0 be VA issued PCs?

Answer: yes

Does Instant web-based visibility at bedside PC require PIV compatibility? yes

Is there a requirement for staff to authenticate to the system when using Instant web-based visibility at bedside PC?

Answers: yes

Can the Pre/Post Op care-boards us the VA wireless network?

Answer: Yes with TRM approval

Who is the current integration provider referenced in #12 of the application requirements? Steris

Are the HCC locations going to be leveraging this solution, or just the 7 ORs in the Salisbury VA Medical Center?

Answer: This solicitation is just for SBY at this time

Is the proposed solution allowed to leverage a direct integration to VistA/CPRS without leveraging a KITS package? Answer: unknown

Second group of questions

1) What current OR management system is currently being used at the Salisbury VA Medical Center? none

2) In reference to the system's reporting requirements, is there a required format of these reports? i.e. .pdf, .xslx, .docx, etc Answer: PDF

3) In reference to the server requirements, are the current systems requiring integration into the new OR management system SQL based? Answer: Unable to provide information

4) In reference to the server requirements the vendor is asked to provide the capability to store reports for 5 years.  Are these reports to be stored on site? 

Answer: Yes Additionally the item description doesn t reference a long-term storage capability, are we to assume the VA has a storage solution in place? No

Third group of questions

1) Would the government consider revising the solicitation to facilitate more than one compliant bidder and thereby allowing evaluation of a solution that, in the opinion of our team, offers a more viable and cost effective solution for the VA and delivers on the core business requirements as depicted in this solicitation? Answer: The solicitation requirement is Brand name or equal to and all vendor must meet what is required in SOW for the need of the facility.

No duplication of enterprise systems (RTLS, VistA Imaging, and Anesthesia Record Keeping).

Simplified interface with legacy systems reducing complexity, start-up and maintenance costs.

Immediate adoption by staff through avoidance in change of clinical practices and need for retraining.

Reduced project risk removing the government as responsible for a complex multi system integration.

2) Can the government clarify requirement under Section "3.0 Technical Requirements", "a. Application Requirement",

Answer: Must be compatible with the current integration provider at the Salisbury location and both HCC locations."

Answer: Steris integration

3) Can the government clarify requirement under Section "3.0 Technical Requirements", "F. Analytics Package configuration requirements", "ii. Configure analytic cube to host data for above reports." Answer: Configure data to provide required reports

Added: May 12, 2017 4:51 pm Modified: May 19, 2017 9:36 amTrack Changes The purpose of this Amendment is to add the response date of 06/1/2017 for RFQ VA246-17-Q-0806 Combined Solicitation. All question regarding RFQ shall be email to Audrey.wooten@va.gov by 3pm 5/22/2017.

Added: May 12, 2017 4:51 pm VA246-17-Q-0806

Page 1 of

Page 8 of 9

Page 1 of

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in FAR Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation. Quotes are being requested and a written solicitation will not be issued. The solicitation number is VA246-17. This acquisition is issued as a Request for Quote (RFQ). The solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-86. The associated North American Industrial Classification System Code (NAICS) for this procurement is 541512 with size standard of 27.5M employees. This solicitation has been set-aside for service-disabled veteran-owned small businesses.

SYNOPSIS

The Department of Veterans Affairs, VISN 6 Network Contracting Office, on the behalf of the Salisbury VA Medical Center has a need for an OR Management System. This is Brand name or equal to Firm Fix price requirement. This procurement is for new equipment only; no remanufactured or "gray market" items. All items must be covered by the manufacturer's warranty.

VAMC Salisbury

STATEMENT OF WORK

Surgical Workflow Solution

BACKGROUND



The VAMC Salisbury, 1601 Brenner Avenue Salisbury, NC 28144 requires a Surgical Workflow Solution; capable of interfacing with patients and family members, providing real time information on patient status and an overall improvement in customer care and experience. This solution will automate surgical workflow and use analytics to measure, analyze, and deliver patient safety and Operating Room (OR) efficiency data. Additionally, this solution will provide perioperative staff members and surgical team s awareness of patient, equipment, and operating room status throughout the course of patient care. The intent of this solution is to identify delays in getting patients through the perioperative process so that efficiencies and increased patient safety can be realized and to increase visibility into the surgical workflow by staff, patients and family members.



2.0 SCOPE

VA intends to award a single Delivery Order, Firm Fixed Price to a contractor capable of providing the outlined Surgical Workflow Solution System & supporting ancillary services; the associated installation and configuration services, as well as the incorporated staff training requirement.



This requirement will consist of a software/application solution, reporting/analytics capabilities, compatible server system and supporting software, dash board workstations and the ability to interface with the existing systems and must demonstrate the performance capabilities detailed throughout this document. A Turn-Key Installation providing all services, training, hardware, cables and accessories for a complete and functional system.

Physician mobile app: for surgeons to stay continuously informed of patient workflows, exceptions, delays, cancellations and automatic notification.

OR charge mobile tablet: continuously updated each day with patient workflows, staffing, exceptions and delays, on demand data analytics.

Auto notifications: automatically capture patient arrivals to OR and instantly notify surgeons and key surgical staff.

Instant web-based visibility at bedside PC: continuous patient visibility and communication to OR, Pre and Post Op staff.

Pre/Post Op care-boards: continuous patient visibility and updates to surgeons and staff via large format displays located in Pre/Post Op areas, OR control desk and staff lounges.

Command center: continuous patient visibility and communication to physicians, management and staff.

Staffing solutions: electronic staffing boards assignments posted for OR rooms, breaks and relief

Contract Duration: The base contract period is one (1) year from date of contract award.



Place(s) of Performance: VAMC Salisbury 1601 Brenner Ave Salisbury, NC 28144



Hours of Operation. VA site-representative(s) or Contracting Officer Representative(s) (COR) will establish a window of time in which access and requirement performance will be authorized in accordance with the conditions outlined with this SOW.

3.0 TECHNICAL REQUIREMENTS The following technical specification requirements are set forth for the Surgical Workflow Solution:



Application Requirements. The application solution shall:

1. Provide Perioperative scheduling package that will interface with VistA surgery scheduling package. Provide the ability to load special equipment in the system for selection when scheduling case.

2. Provide HIPPA compliant, real-time patient status to operating room staff providing streamline transition of patients as they move throughout the perioperative suite, capturing progress along every point of the process and communicating relevant updates to the physicians, nurses and families via highly visible displays. Provide accessibility by authorized staff via smart phones/tablets. Provide HIPPA compliant updates to family s email/text.

Collect procedure specific data (start/stop times, anesthesia times, room open/room closed, first case starts, turnaround time, OR utilization, OR block time, overtime, out of block utilization, surgeon/anesthesia arrival time).

Provide technology designed to provide the OR team with real-time, accurate patient data from various hospital sources (lab, radiology, EMR..).

Collect data required by the Surgical Complication Improvement Project (SCIP) and VA's National Surgical Quality Improvement Project (VASQIP). Data will be collected by the system but then reported by VA in to SCIP and VASQIP. Example data includes: Prophylactic antibiotic received within 1 hour prior to surgical incision and Prophylactic antibiotic selection for surgical patients.

Display overall information on the perioperative process and progress of the patient through the processing the OR on multiple screens, monitors or displays (OR desk, SPS, Chief of Surgery's office, Surgery suite, PACU, Pre-Op, patient s family waiting room, etc.) and for multiple audiences in order to maintain privacy requirements when/where necessary.

Anonymize patient information and align with HIPAA regulations.



Provide real time patient tracking via RFID tracking device assigned to patient to be used in conjunction with RTLS designed to eliminate additional keyboard entry. Sensor tags will not interfere with other medical equipment.



Provide live real time dashboard designed for OR managers, administration, and surgeons with the information each of the team members need. (browser based) Command center providing continuous patient visibility and communication to physicians, management staff. Anesthesia module to allow anesthesiologist to monitor patient status, flow and associated time stamps across many rooms on one page. Automatic notification alerting surgeons, anesthesiologist, environmental service, SPS when changes made in schedule, patients/room ready.



Provide digital patient file display with real time patient information available for all team members to view on dedicated display in the OR with real-time, up-to date patient data for situational awareness. Easy to read display to optimize patient safety and clinical decisions based on real time information. Provide automatic access to key information from diverse IT systems- lab, radiology, medical records, allergies patient safety check list display, information on blood products, lab results, specimen inventory and disposition, staff information. The display maintains visibility of time sensitive information: antibiotic administration, tourniquet time, patient repositioning.



Provide IP cameras in each operating suite with controlled access through command center.



Provide kiosk for family registration/information. Provide the ability for families to receive updates via personal device.



Provide surgery scheduling capabilities allowing cases to be scheduled in advance or same day of surgery date. Surgeons entered in system for easy selection. Special equipment such as c-arm, etc. can be loaded into the system for selection when scheduling a case. Ability to select equipment to see and select from drop down list of equipment entered in system. Comment column for other pertinent information. Management of block time by surgeon/specialty.



Must be compatible with the current integration provider at the Salisbury location and both HCC locations.



Reports Requirement. The solution shall:



Include a report generator to document:

Pre-operative events.

Total time to complete Pre-Op prep/checklist process

Total length of stay in Pre-Op

Order in which the Pre-Op prep/checklist was completed

Time to complete each Pre-Op Checklist item

iv. Time Patient occupied Pre-Op bed/bay after Pre-Op checklist was completed



Operating room events.

Time into OR / Time out of OR

Total Anesthesia time (Induction to time out of OR)

Operative Time (Incision time to close time)

Turnover time

OR Block Utilization by Surgeon (Percentage of OR time utilized as compared to

OR time allocated/blocked for a given surgeon)

OR Block Utilization by Service (Ortho, Uro, General, etc...)

Time out procedure time (Time safety checklist is started to time safety checklist has been completed)



Schedule events.

i. Total number of ORs anticipated and actually running each day

ii. Total number of patients on the surgery waiting list



Generate/create ad-hoc user reports. The reports would use the measures listed above but be customizable by the facilities. No additional measures, other than those listed above are required to be included in the ad-hoc reports.

Provide automatic reporting and data charts using dashboards with touch of the finger or click of a mouse in real time.



Interface Requirements. The system provided shall interface with:



Veterans Information Systems and Technology Architecture (VistA) Surgery Package - Solution shall supply all VA defined required data elements to VistA Surgery at defined trigger points in the Surgery Scheduling and tracking process; VistA Surgery will continue to supply data to other VistA modules per current processes.



VistA Integration Accepts and filters information from VistA to allow views of VistA data elements i.e. labs, ADT. Proposed solution shall have an HL7 interface capable of accepting patient demographic information (ADT) and order (ORM) messages received from the VistA scheduling package. These data elements should be provided in real time and updated automatically.



VistA Imaging / Text Integration Utilities (TIU) - Receives images and stores them for display to VistA users. Solution shall supply TIU using existing HL7/VistA Imaging interface and specific note titles.



Anesthesia Record Keeping (ARK) Picis, Version 8.6 - Proposed solution shall receive Anesthesia related information from ARK and ARK will receive Surgery Schedule information from the proposed solution.



Patient monitors Proposed solution shall receive vital signs related information from the patient monitors located in the operating rooms. VAMC Salisbury currently has the following Philips MP50/ MP70 patient monitor equipment. The 5th floor will have Phillips MX800 monitors. Facility plans to upgrade to the Phillips MX800.

Server Requirements. The server provided shall:



Provide any physical server hardware, OS, and database licenses (such as SQL) required interface to VistA/CPRS. OS shall be a currently supported OS and shall not be prior to Windows Server 2008 (i.e. Windows 2003 is not permitted)



Describe whether the system can integrate with Active Directory or LDAP.



3. Provide capability of storing acquired reports for 5 years



Installation and Configuration Requirements.



1. The Installation shall consist of the following:

The selected contractor shall conduct site surveys of each of the designated locations within thirty (30) days following contract award.



Each site survey shall include all electrical and IT cable drops necessary.



A technical plan for each site shall be submitted with within ten (10) business days after all surveys have been completed.



Complete installation of each display board workstation:

i. Mounting of monitor and associated PC

ii. Any necessary Data line pulls

iii. Any necessary electrical work required to power monitor and associated PC



2. Configuration shall consist of:

A. Interface testing, with the following documentation:

i. Kits built for VistA Interfaces

ii. Patch descriptions

iii. Test scripts

Installation guides

Implementation and back out plans



B. Pre-operative events display information configuration requirements:

i. Work with the VHA clinical staff to document pre-operative milestones and process flow for each of the milestones.

ii. Map VistA/CPRS data elements to pre-operative milestones and document milestone completion criteria.

iii. Document criteria for marking a patient ready for transport to Operating Room for planned surgical procedure.

Setup alert conditions and appropriate notification mechanism.

Setup access control for access to Pre-Op milestone completion.

Identify locations where read-only Pre-Op dashboard displayed for use by perioperative staff.



C. Operating Room events display information configuration requirements:

i. Work with the VHA clinical staff to document clinical process flow

ii. Verify mapping of VistA/CPRS data elements to display board.

iii. Verify mapping of Anesthesia data elements to display board.

iv. Configure display board to accept data from physiological monitors

v. Configure site-specific checklists.



D. Scheduling events display information configuration requirements:

i. Work with hospital s perioperative staff to configure site-specific color key

ii. Identify locations where read only OR-Schedule dashboard will be displayed for use by perioperative staff

iii. Define dashboard configuration for each of the locations.

iv. Define access control list for users who can modify the day of surgery schedule v. Define application URL and mechanism to deploy URL for use by authorized users



E. Family Waiting display information configuration requirements:

Work with hospitals perioperative staff to configure

Identify locations where display monitor will be located for use by patients loved ones.

Define display board workstation configuration for each of the locations.



F. Analytics Package configuration requirements:

Configure predefined reports

Configure analytic cube to host data for above reports

Define access control list for users who can access these reports

Define application deployment method for authorized users



Training Requirements.



1. Go-live/Initial Training



Clinical applications training for super-users, administrator, nurses, physicians, and other clinical staff shall be provided onsite during go-live for one week, 8 hour days



Training shall be provided on the user interface, application, and its features



Training shall provide super-users and end-users with the capability of being self-sufficient in operating the system by the end of the training session



2. Follow-up/Refresher Training - Clinical applications training shall be provided after clinical

users have had hands-on experience with the system, between 3-9 months following go-live for at least two days.



Provide quick notes or reference guides during on-site training during the Go Live Training.



Technical Training to be provided within the first year of installation - Provide technical training for maintenance and service for technical personnel at each site/regional OI&T and/or Biomedical personnel. Training should at minimum address the following topics:



A. Commissioning and preventative maintenance

B. Troubleshooting

C. Server maintenance and backup procedures

D. Provide technical training for configuration of each interface

E. Provide technical training for configuration of each type of display board

workstation

F. Provide details as to whether this training will be provided onsite or remotely

4.0 SECURITY.

a. Contractor must provide completed documentation for the solution including, but not limited to, VA Directive 6550 and Manufacturer Disclosure Statement for Medical Device Security (MDS2).

b. The Contractor shall adhere to all VA Privacy & Security requirements including the Privacy Act and the Business Associate Agreement.

c. Any Contractor staff requiring access to the VA network will complete required Privacy training and Rules of Behavior agreements in accordance with VAMC policy

d. Must be VA Patient Identification Verification (PIV) compliant

5.0 SERVICE SUPPORT

a. During the warranty period, the vendor shall provide service, at no cost, Monday-Friday between the hours of 8:00 am 5:00 pm (excluding federal holidays).

b. Vendor will supply 24 hour phone technical support for the duration of ownership of the equipment.

c. Vendor must obtain and show proof of National or Point to Point VPN certification. Any offsite server or network maintenance or support provided by the vendor can only be done via VPN access.

d. Offer a service support agreement with base year plus three additional years. This shall include all interfaces, remote service or application access charges, telephone technical or application support charges, or any fees associated with supporting this equipment.

e. Provide coverage under the same install team locally once the implementation is complete.

B.3 PRICE/COST SCHEDULE

ITEM INFORMATION

ITEM NUMBER

DESCRIPTION OF SUPPLIES/SERVICES

QUANTITY

UNIT

UNIT PRICE

AMOUNT

0001





1.00

EA

__________________

__________________

0002



1.00

EA

__________________

__________________









GRAND TOTAL

__________________

B.4 DELIVERY SCHEDULE





The following Federal Acquisition Regulation (FAR) and Veterans Affairs Acquisition

Regulation (VAAR) provisions and clauses are applicable to this acquisition and are available for view at: http://farsite.hill.af.mil/



FAR Clauses:

52.203-99 PROHIBITION ON CONTRACTING WITH ENTITIES THAT REQUIRE CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS (DEVIATION) (FEB 2015)

52.203-17 Contractor Employee Whistleblower Rights and Requirements to Inform Employees of Whistleblower Rights (SEP 2013)

52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber Content Paper

(MAY 2011)

52.212-4 Contract Terms and Conditions- Commercial Items (SEP 2013)

52.212-5 Contract Terms and Conditions Required to Implement Statutes or Executive Orders-Commercial Items (SEP 2013)

52.204-10 Reporting Executive Compensation and First-Tier Subcontract Awards (JUL 2013)

52.209-6 Protecting the Government s Interest When Subcontracting with Contractors Debarred, Suspended, or Proposed for Debarment (AUG 2013)

52.219-6, Notice of Total Small Business Set-Aside (NOV 2011) (15 U.S.C. 644)

52.222-3 Convict Labor (JUN 2003)

52.222-19 Child Labor Cooperation with Authorities and Remedies (MAR 2012)

52.219-28 Post Award Small Business Program Rerepresentation (Jul 2013)

52.222-21 Prohibition of Segregated Facilities (FEB 1999)

52.222-26 Equal Opportunity (MAR 2007)

52.222-35 Equal Opportunity for Veterans (SEP 2010)

52.222-36 Affirmative Action for Workers with Disabilities (OCT 2010)

52.222-50 Combating Trafficking in Persons (MAR 2015)

52.223-18 Encouraging Contractor Policies to Ban Text Messaging While Driving (AUG 2011)

52.232-33 Payment by Electronic Funds Transfer- System for Award Management (JUL 2013)

52.252-2 Clauses incorporated by Reference (FEB 1998)



VAAR Clauses:

852.203-70 Commercial Advertising (JAN 2008)

852.232-72 Electronic Submission of Payment Requests (NOV 2012)

852.246-70 Guarantee (JAN 2008)

852.246-71 Inspection (JAN 2008)



FAR Provisions:

52.204-7 System for Award Management (JUL 2013)

52.212-1 Instructions to Offerors- Commercial Items (JUL 2013)

52.216-1 Type of Contract (APR 1984)



1. Offeror shall provide an itemized list of the items

Offeror shall provide a quote addressing CLINS (0001-0021)

52.212-2 Evaluation-Commercial Items (JAN 1999)



BASIS FOR AWARD

The Government intends to make an award based on the initial quotations. Award will be made to that vendor with the lowest overall price in accordance with the salient characteristic in section B of solicitation.



The Government will award a firm fixed priced contract to the responsible offeror who is the lowest priced technically acceptable.





52.212-3 Certifications and & Representations (NOV 2013)

52.225.25 PROHIBITION ON CONTRACTING WITH ENTITIES ENGAGING IN CERTAIN ACTIVITIES OR TRANSACTIONS RELATING TO IRAN REPRESENTATION AND CERTIFICATIONS

VAAR Provisions:



852.211-72 TECHNICAL INDUSTRY STANDARDS (JAN 2008)

852-215-70 Service-Disabled Veterans-Owned and Veteran-Owned small business evaluation factors (JUL 2016) Deviation)

852.233-70 Protest Content/Alternative Dispute Resolution (JAN 2008)

852.233-71 Alternative Protest Procedure (JAN 1998)

852.252-70 Solicitation Provisions or Clauses Incorporated by Reference (JAN 2008)

852.273-74 Award without Exchanges (JAN 2003)





852.273-72 ALTERNATIVE EVALUATION (JAN 2003)



The Government will award a contract resulting from this solicitation to the responsible offeror submitting the lowest priced offer that conforms to the solicitation. Offerors may revise offers anytime during the specified period. At the end of the specified time period for receipt of offers, the responsible offeror submitting the lowest priced offer will be in line for award. IAW VAAR 812.302 Tailoring of Provisions and Clauses for the Acquisition of Commercial items, this contract will be awarded using a Lowest Price Technically Acceptable (LPTA) approach. Technical ability will be evaluated as Acceptable/Unacceptable, Pass/Fail, or Go/No-Go. Tradeoffs are not permitted.

Quotations shall include the RFQ number, the proposed unit prices, the proposed extended prices, any prompt payment discount terms, any shipping charges, company name, and point of contact, address, phone number, tax identification number, and DUNS number.

The Government shall consider quotes received by 10:00 AM Eastern Standard Time, 2/28/2017 10AM, 2017. Quotes are to be e-mailed to Audrey.wooten@va.gov