Loren Data's SAM Daily™

FBO DAILY - FEDBIZOPPS ISSUE OF JUNE 03, 2017 FBO #5671
DOCUMENT

D -- DSS Services for VISN 16 sites - Attachment

Notice Date

6/1/2017
 

Notice Type

Attachment
 

NAICS

541511 — Custom Computer Programming Services
 

Contracting Office

Department of Veterans Affairs;Chief, A&MM (90C/NLR);Central Arkansas Veterans HCS;2200 Fort Roots Drive, Bldg 41, Room 224;North Little Rock AR 72114 1706
 

Solicitation Number

VA25617Q0720
 

Response Due

5/25/2017
 

Archive Date

6/24/2017
 

Point of Contact

Sheila D Reed
 

E-Mail Address

7-1053<br
 

Small Business Set-Aside

Service-Disabled Veteran-Owned Small Business
 

Description

This is a SOURCES SOUGHT ANNOUNCEMENT ONLY. It is neither a solicitation announcement nor a request for proposals or quotes and does not obligate the Government to award a contract. Requests for a solicitation will not receive a response. Responses to this sources sought must be in writing and submitted via email to Sheila Reed at Sheila.reed@va.gov by Monday, June 5, 2017, 12:00 pm central time. The purpose of this sources sought announcement is for market research to: make appropriate acquisition decisions and to secure knowledge of potential qualified Service Disabled Veteran Owned Small Businesses (SDVOSB) and Veteran Owned Small Businesses (VOSB). Responses to this notice shall include the following: (a) company name (b) address (c) point of contact (d) phone and email (e) DUNS number (f) Cage Code (g) Tax ID Number (h) Type of small business, e.g. Service Disabled Veteran Owned Small Business (SDVOSB) or Veteran-owned Small Business (VOSB) and (i) must provide a capability statement that addresses the organizations qualifications and the ability to provide the product(s) and/or services described in the Statement of Work (SOW) herein. The South Central VA Health Care Network (VISN 16) is seeking qualified SDVOSB/VOSB contractors who can provide: DSS Services to include project management, installation, implementation support, testing and training for SAV Link, Data Link and ICU in accordance with the SOW below. IMPORTANT NOTE: The Government is not obligated to, nor will it pay for or reimburse, any costs associated with responding to this sources sought announcement. This notice shall not be construed as a commitment by the Government to issue a solicitation or ultimately award a contract, nor does it restrict the Government to a particular acquisition approach. The Government will in no way be bound to the information contained in this announcement, in the event a solicitation is issued. The VA is mandated by Public Law 109-461 to consider a total set-aside for SDVOSB/VOSB. However, if responses from SDVOSB/VOSB firms prove inadequate, an alternate set-aside, or, full and open competition, may be considered. No subcontracting opportunities for this procurement are anticipated. The North American Classification System (NAICS) code for this acquisition is 541511, Custom Computer Programming Services and size standard is $27.5 million. NOTICE TO SDVOSB/VOSB: All Service Disabled Veteran Owned Businesses (SDVOSB) or Veteran Owned Small Businesses (VOSB) who respond to this notice or a solicitation must be registered and certified with the Department of Veterans Affairs Center for Veterans Enterprise VetBiz Registry located at http://vip.vetbiz.gov. SDVOSB/VOSBs must be verified in the VIP database when an offer is submitted and at the time of contract award and unverified firms will be considered non-responsive and ineligible for award. VISN 16 ICU/ARK Analytics Project Interface Component Statement of Work (SOW)/Specifications 1. SCOPE This Statement of Work (SOW) defines the business and operational requirements for the Interface for Critical Care Data, a vital component of the Intensive Care Unit/Anesthesia Record Keeper (ICU/ARK) Analytics system, hereafter called ICU/ARK Analytics. An Interface for Critical Care Data, hereafter called Interface, is an information technology component that is part of the ICU/ARK Analytics medical system for Veterans Integrated Service Network 16 (VISN 16). An instance of each Interface is installed and runs on each of the VistA systems that support the medical facilities within VISN 16. The Interface transfers data between the VistA systems and the other system components of ICU/ARK Analytics, namely the ICU and ARK Clinical Information System (CIS) components and the Analytics component. 1.1 BACKGROUND ICU/ARK Analytics is a medical information system that supports and records care delivery in critical care and surgical settings. The system receives and generates its own data - for example, input from physiologic monitors, anesthesia machines, and other devices; and also input by clinicians regarding assessments and procedures. An ICU/ARK Analytics system operates in a total patient care environment that also includes patient demographics, allergies, problem lists, lab results, medication orders, and other clinical information. Within the Veterans Health Administration (VHA), this information is created and managed within the Veterans Health Information Systems and Technology Architecture (VistA), which is a separate system from an ICU or ARK CIS. Yet, information from both ICU and ARK CISs and from VistA is required for a complete representation of the patient and his/her delivered care. The purpose of the Interface is to provide a data bridge between VistA and the other components of an ICU/ARK Analytics system. This enables clinicians to create, capture, and access critical care data in a single representation, and specifically enables clinicians to document procedures and assessments in the same system in which automated data is collected and displayed. 2. APPLICABLE DOCUMENTS VA Handbook 6500 Waiver/Compensating Control Approval http://vaww.aac.va.gov/systemsecurityservices/Documents/PDF%20files/VAHandbook6500InformationSecurityProgramWaiverProcess.pdf VA Directive 6500 Information Security Program http://www1.va.gov/vapubs/Search_action.cfm?formno=&tkey=&dType=0&SortBy=rpch&sort=desc&oid=0 VA Handbook 6500.3 Certification and Accreditation of VA Information Systems http://www1.va.gov/vapubs/viewPublication.asp?Pub_ID=419&FType=2 National Institute of Standards and Technology Special Publication 800-53 Recommended Security Controls for Federal Information Systems and Organizations http://csrc.nist.gov/publications/nistpubs/800-53-Rev3/sp800-53-rev3-final_updated-errata_05-01-2010.pdf VA Acquisition Regulation (VAAR), Subchapter H Clauses and Forms, Part 852 Solicitation Provisions and Contract Clauses, Section 246-70--Guarantee http://www.va.gov/oamm/oa/ars/policyreg/vaar/vaar852.cfm#85224670 3. REQUIREMENTS The business and system interface requirements will be those capabilities that currently reside in the Document Storage Systems (DSS) Databridge Version 1.8 or the most current version at time of contract performance; these capabilities are hereafter called Interface. 3.1 General. 3.1.1 The Contractor shall provide all labor, materials, project management, tools, and software to furnish and install on Government provided hardware all the Interface capabilities currently found in DSS Databridge Version 1.8 or higher. The Contractor shall provide a single release of the Interface to all VISN 16 facilities regardless of the ICU/ARK vendor(s) selected. 3.1.2 The Interface shall not interfere with the existing computer programs currently in use at each of these locations, including but not limited to VISTA/CPRS, Windows 7, Internet Explorer, Microsoft Office, Windows-based programs, Barcode Medication Administration (BCMA) system, and VA antivirus software. 3.1.3 The Interface shall include a prorated continuation of license for the three VA Medical Centers listed in Table 1 below. The Interface shall include software maintenance and support including all software fixes, upgrades, patches, and/or software enhancements. Contractor shall provide all technical support and any on-site and/or remote service required. Name Location VA Gulf Coast Veterans Health Care System (VHCS) Biloxi, MS Michael E. DeBakey VAMC Houston, TX Jack C. Montgomery VAMC Muskogee, OK 3.1.4 All maintenance and support services (see paragraph 3.1.3 above), including but not limited to routine maintenance and upgrades, shall be provided during normal business hours of 8:00 am- 4:30 pm CST Monday Friday, excluding Federal Holidays as indicated below. Contractor may submit for consideration a list of any additional holidays observed by the company. The  phone number and point of contact to be used for coordinating Interface support / project management services shall be provided to the Contractor by site after contract award. If any problem should arise, Contractor s contact for VISN 16 shall be the Contracting Officer s Representative (COR), to be identified post-award, during normal working hours. Federal Holidays observed by VISN 16 are: New Year s Day Martin Luther King Day Presidents Day Memorial Day Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day 3.1.5 The Contractor must be able to provide maintenance and support services during normal working hours as indicated above in paragraph 3.1.4 or within a specified time agreed upon by the Contractor and the VISN 16 COR. 3.1.6 The Contractor shall notify the VISN 16 COR of any changes to function and operation of the Interface. Notification should be in advance of user potential discovery if possible and must be within the same business day as user potential discovery if advanced notification is not possible. 3.1.7 The Contractor shall be completely responsible for the maintenance, repair, upgrades, and updates to the software provided under this contract. On-going software updates and patches shall be included in order to keep the software components at the most current software releases and include software feature requests. These updates and/or required patches shall be installed during normal working hours and shall be coordinated with the Clinical Applications Coordinator (CAC) at each individual site. 3.1.8 All maintenance services shall be provided in a timely manner and in accordance with the Contractor s customary business practices; however prolonged delay in resolving software problems will be noted in the Government s various past performance records on the Contractor (e.g., www.ppirs.gov). 3.1.9 Contractor shall provide all software updates/upgrades at no additional cost to the government throughout the duration of this project. Notwithstanding, Contractor shall provide any written exceptions to the above with his/her signed proposal. If the Contractor does not list any exceptions, any additional costs associated with the above shall be the Contractor s responsibility. 3.1.10 Contractor is reminded of, and shall agree to, the fact that any variations or adjustments to contract terms that result in changes to cost, schedule, and technical performance must be coordinated with and approved by the Contracting Officer (CO). The CO is the only person who can approve such changes on behalf of the Government. 3.2 Installation and Implementation. 3.2.1 The Contractor shall provide Interface implementation services, including but not limited to project management, software installation, implementation, support, testing, configuration, and training at all locations where the Interface is to be licensed. The services shall include all labor, supplies, supervision, travel, per diem, and customary charges required to complete the installation and implementation. In addition to the Interface installation and implementation, the Contractor s price shall include extract staging, initial loading and testing of VISN 16 data from source systems available at the time of installation, and data validation. 3.2.2 The Contractor shall be responsible for the complete Project Management of the Interface. The Contractor shall provide a single, qualified Project Manager (PM) as a sole Point of Contact for VISN 16. The PM shall be VISN 16 s primary point of contact and shall be responsible to oversee and manage Interface operation. Project Management shall be provided to VISN 16 during normal operating hours of 8:00 am- 4:30 pm CST, Monday through Friday. The Contractor shall provide the name and contact information of the Project Manager to the VISN 16 COR during the pre-work orientation. The COR will be notified a minimum of fourteen (14) days in advance of any change to the Project Manager assigned to VISN 16. 3.2.3 All installation and implementation services defined herein shall be completed as within as reasonable timeframe as agreed upon between the vendor and the VISN 16 COR; however, completion at all sites must be done by 12-31-17. Notwithstanding, it is understood that the strategic plan and/or timelines may be updated for any delays caused by the Government or for any delays by the Contractor determined to be acceptable to the Government in accordance with the contract terms. 3.3 Performance Requirements. 3.3.1 The Interface shall successfully integrate VistA/CPRS with the other components of the ICU/ARK Analytics, namely the ICU and ARK CIS components and the Analytics component. The Interface shall make VistA/CPRS data available in the ICU CIS and ARK CIS and the Analytic System and shall make ICU CIS and ARK CIS data available in VistA/CPRS, regardless of the ICU CIS and ARK CIS products selected by VISN 16. 3.3.2 The Interface shall be configurable to utilize either HL7 messaging or XML technology as a communication means. 3.3.3 The Interface shall facilitate storage of the ICU/ARK CIS output and the image of the recorded anesthesia/ICU case in a PDF file in the VistA modules or VistA Imaging systems. 3.3.4 The Interface shall maintain strict backwards compatibility while introducing new ICU/ARK vendor specifications. 3.3.5 The Interface shall provide data extraction from VistA for receipt/loading by the Analytics component. 3.3.6 The Interface shall provide the capability to interchange data with any combination of single CIS for ICU, single CIS for ARK, single CIS for both ICU and for ARK, or separate CISs for ICU and for ARK. 3.3.7 The Interface shall provide the capability for synchronization of the CIS clock to the clock of a VistA system. 3.3.8 The Interface shall provide the capability to manage a session as a VistA user, using VistA access/verify codes, for a CIS. 3.3.9 The Interface shall provide the capability to manage a session for a named user. 3.3.10 The Interface shall provide the capability to manage a session under a pre-defined user key. 3.3.11 The Interface shall provide the capability to manage a session for an anonymous user. 3.3.12 The Interface shall provide the capability to manage a perpetual session for a critical care setting. 3.3.13 The Interface shall provide the capability for CIS to establish (log on) a session for access to VistA. 3.3.14 The Interface shall provide the capability to terminate a session capability for CIS to log off a session. 3.3.15 The Interface shall provide the capability to terminate a session from CIS fault. 3.3.16 The Interface shall provide the capability for VistA to terminate (time out) a session. 3.3.17 The Interface shall provide the capability to resume a session terminated by CIS fault. 3.3.18 The Interface shall provide the capability to resume a session terminated by VistA. 3.3.19 The Interface shall provide the capability to transfer location information. 3.3.20 The Interface shall provide the capability to transfer clinical provider group information. 3.3.21 The Interface shall provide the capability to perform selection and identification of a patient and must ensure the successful matching of appropriate ICU/ARK records with patient records in VistA/CPRS. 3.3.22 The Interface shall provide the capability to read patient data in VistA and transfer to CIS. 3.3.23 The Interface shall provide the capability to read and transfer patient data of specific types. 3.3.24 The Interface shall provide the capability to read and transfer demographic data for a patient. 3.3.25 The Interface shall provide the capability to read and transfer Admission, Discharge, Transfer (ADT) data for a patient. 3.3.26 The Interface shall provide the capability to read and transfer Allergy list data for a patient. 3.3.27 The Interface shall provide the capability to read and transfer Pharmacy Order data for a patient. 3.3.28 The Interface shall provide the capability to read and transfer Clinical Warnings and Advanced Directive data for a patient. 3.3.29 The Interface shall provide the capability to read and transfer Dietary and Nursing Order data for a patient. 3.3.30 The Interface shall provide the capability to read and transfer Vital Sign data for a patient. 3.3.31 The Interface shall provide the capability to read and transfer Laboratory Result data for a patient. 3.3.32 The Interface shall provide the capability to read and transfer Surgery data for a patient. 3.3.33 The Interface shall provide the capability to set patient object properties. 3.3.34 The Interface shall provide the capability to query VistA for change to patient data. 3.3.35 The Interface shall provide the capability to query Surgical data for a patient. 3.3.36 The Interface shall provide the capability to receive patient data change events. 3.3.37 The Interface shall provide the capability to receive event changes from ADT. 3.3.38 The Interface shall provide the capability to receive event changes from Pharmacy Order. 3.3.39 The Interface shall provide the capability to receive event changes for Patient Registration. 3.3.40 The Interface shall provide the capability to receive Vital Signs data change events. 3.3.41 The Interface shall provide the capability to receive Laboratory result messages. 3.3.42 The Interface shall provide the capability to transfer update data from VistA to CIS. 3.3.43 The Interface shall provide the capability to perform confirmed transfer of update data from VistA to CIS. 3.3.44 The Interface shall provide the capability to detect unsuccessful transfer of updated data from VistA to CIS and shall provide users with real-time notification of failed data transfers. 3.3.45 The Interface shall provide the capability to write Text Integration Utility (TIU)/progress notes to VistA. 3.3.46 The Interface shall provide the capability to write contents of a TIU to VistA. 3.3.47 The Interface shall provide the capability to write a TIU note signature to VistA. 3.3.48 The Interface shall provide the capability to write the file address of a PDF to VistA. 3.3.49 The Interface shall provide the capability to write Surgical data for a patient to VistA. 3.3.50 The Interface shall provide the capability to extract VistA data and export as a file. 3.4 Testing and Certification. 3.4.1 The Contractor shall pre-test the software at various implementation stages in accordance with the Picis ICU CIS and/or Draeger Innovian ARK systems being implemented under other contracts. After pre-testing the system, the Contractor shall certify to the VISN 16 via e-mail that the system is ready for acceptance testing, and that it meets all requirements as specified. Submission of this certification of system readiness shall be accomplished by the Contractor prior to the beginning of the scheduled Government Acceptance Test. 3.4.2 Final Acceptance Testing: The government shall accept the Interface upon thirty (30) days of continuous operation of the system without fault in a production environment. This thirty (30)-day window is considered the acceptance test period during which time the Contractor shall confirm that all facilities within VISN 16 are able to gain access and use the Interface as intended. Successful operation includes operation in accordance with the documentation published by the Contractor for the computer software and in accordance with the functional requirements described in the SOW. If a fault occurs, the acceptance test period will stop. Upon the Contractor s correction of the fault, the 30-day acceptance test period will re-start. It is understood that the Contractor shall be responsible to correct any fault experienced during the acceptance test period at no charge to the Government. The Contracting Officer will accept or reject the Interface based on recommendation from the COR. The commencement date of the acceptance test will be on a mutually agreed upon date and time between the COR and the Contractor. This initial testing shall be conducted in the presence of the COR for proof-of-performance and throughout the duration of the testing period. 3.5 Availability. 3.5.1 The Interface shall be operable and available for use 97% of the normal operating hours unless otherwise stated. Downtime will be computed from notification of problem during normal work hours. Scheduled maintenance will be excluded from downtime during normal working hours as detailed herein. Operational Uptime will be computed during a month-long time period. Repeated failure to meet this requirement can subject the Contractor to Termination for Cause action. 3.5.2 The Contractor shall provide a contingency plan for when the system is brought off-line for maintenance or technical issues/problems. 3.5.3 Notification of unscheduled outages and events that degrade system functionality and/or performance shall be disseminated to the user community within 30 minutes of the occurrence. The business impact must be noted. 3.6 Training. 3.6.1 The Contractor shall create training curricula, user manuals, and other training tools that include a description of the Interface capabilities and deliver these items to all levels of users. 3.6.2 Training tools must include detailed scenarios for use of the system to perform acceptance testing of the Interface component. 3.6.3 The Contractor shall provide the necessary training as required by the VA so that VISN 16 can maximize the benefits of the system. Within thirty (30) calendar days of receipt of award, the Contractor shall submit to both the CO and to the COR a written plan that outlines the best approach for training clinical and non-clinical staff of VISN 16 on the overall operations of the system. This written plan will include a sample curriculum and recommendations on the level of staff which will attend which sessions. It is understood that training shall be provided in various forms of media, including but not limited to, tutorials, manuals, and on-site training. 3.6.4 Upon completion of the tutorial-based training by the VA personnel described in paragraph 3.6.3 above, the Contractor shall provide on-site training to the clinical and non-clinical staff on the use and operations of the software. The VISN 16 COR shall be responsible to notify the Contractor on the location for each of the sessions. The Contractor shall provide all training materials and/or manuals required for the above. The VA will coordinate the use of any additional equipment required, such as overhead projectors, sound systems, and/or computers, which may be required. Contractor shall provide guidance on completing any adjustments or other actions which may be undertaken by operating personnel in the event of failure, provided that such adjustment or action will in no way jeopardize the Government's rights under contract guarantee clause. Only qualified Contractor s personnel, upon completion of installation, will provide the training. Contractor shall contact the COR upon completion of the installation of the solution, testing, and final acceptance of the hardware and software by the government to discuss final implementation and training. Date and times of training shall be mutually agreed upon with the COR or designated alternate and the Contractor. 3.7 Security and Privacy. 3.7.1 The Contractor and the Interface must comply with all VA security requirements. Minimum security control requirements are addressed in NIST SP 800-53 and VA Handbook 6500.3, Appendix D. 3.7.2 Contractor acknowledges that information security is critical to the ICU/ARK Analytics system. The Interface shall meet standards set forth by the Health Insurance Portability and Accountability Act of 1996 (HIPAA), The Privacy Act of 1974, Enterprise Architecture standards, and VA Cyber-Security requirements. Contractor agrees to adhere to all VA Requirements, policies and procedures with reference to security and background investigations further defined below in paragraph 3.7.8. 3.7.3 The Interface shall allow for the implementation of individual-user access restrictions from the other components of ICU/ARK Analytics. 3.7.4 Vendor shall have an approved Business Associate Agreement (BAA) with VA. If the offeror does not currently have a signed BAA they should contact the HIPAA Program Management Office to initiate the process: 3.7.5 Contractor shall be approved for Site to Site One VA VPN Access. This may require approval by the VA Office of Cyber Information Security (OCIS). 3.7.6 Remote Access: If it is determined by the COR that the Field Service Engineers (FSEs) and authorized Contractor personnel will require remote access to the system in order to meet the software maintenance and administration requirements of this Contract, the Contractor agrees to the above and to adhere to VISN 16 s guidelines and the Federal guidelines set forth herein. If approved by the VISN ISO, the Contractor shall be provided with an approved OCIS Site to Site VPN account. The COR will provide the Contractor with additional information on how to proceed with the above during the pre-work orientation meeting. Notwithstanding, it is agreed upon and understood that remote access will only be provided for technical support within the Continental United States. 3.7.7 Vendor shall provide a completed Manufacturer Disclosure Statement for Medical Device Security (MDS2). The Contractor agrees to sign the VA s Confidentiality and Security Agreements in accordance with VA policies and procedures. 3.7.8 A VA Police background check shall be a requirement as further defined herein for all Contractors and any Subcontractors employee(s) providing services to the Government. This shall allow the Contractor to access areas within the Medical Center such as offices, clinics, patient rooms, and other restricted areas. No employee shall be permitted to perform work or access non-public areas unescorted without a background check and written clearance by VA Police. If requested by the COR, the Contractor shall provide the following information: Name (full, including previous names) of any employee who will be performing work under this contract. Social Security Number Date of Birth Race State(s)/Other Countries lived-in 3.8 Compliance. All services shall be performed and software shall function in conformance with all VA safety and Security standards, manufacturer's/industry standards, Health Insurance Portability and Accountability Act (HIPPA), Section 508 Compliance requirements, Occupational, Safety and Health Administration (OSHA guidelines), National Electrical Codes (NEC), and other applicable state, local, national and industry standards. Software provided shall be approved by VA s OCIS-Health Information Security Division on three levels: Technical Vulnerability, Hardening Guideline Comparison, and HIPPA Control Analysis. 3.9 Product Modification, Removal, or Recall. If any product awarded under this solicitation requires modification, or if any product is removed or recalled by the Contractor or manufacturer, or if any required modification, removal or recall is suggested or mandated by a regulatory or official agency, the Contractor or manufacturer will immediately take the following steps: 1. Notify the Contracting Officer (CO) by the most expeditious manner possible. Follow up by providing the CO two written hard copies of the notification, which shall include, but not be limited to, the following: a. Complete item description and/or identification, order numbers from customers and the contract number assigned as a result of an award on this solicitation. b. Reasons for modifications, removal or recall. c. Necessary instructions for return for credit, replacement, or corrective action. 2. Provide the above information to all agencies and VA facilities that purchased the product. The Contracting Officer shall be provided a copy of the notification in 1 above and a list of all agencies and/or VA facilities notified. 3.10 Competency of Personnel. 3.10.1 The Contractor shall have an established business, with an office and staff. The staff includes a "fully qualified" FSE and a "fully qualified" FSE who will serve as the backup. "Fully Qualified" is based upon training and on experience in the field. For training, the FSE(s) has successfully completed a formal training program relevant to the software described in this statement of work. For field experience, the FSE(s) has sufficient experience with respect to services required under this contract. 3.10.2 The FSEs shall be authorized by the Contractor to perform the software maintenance services. All work shall be performed by "Fully Qualified" competent FSEs. The Contractor shall provide written assurance of the competency of their personnel and a list of credentials of approved FSEs for product the Contractor services at the VAMC. The CO may authenticate the training requirements and/or request training certificates or credentials from the Contractor at any time for any personnel who are servicing or installing software on any VAMC equipment. The Government may require the Contractor to remove an FSE from the Government facility if the FSE is not performing in accordance with contract requirements. 3.10.3 If subcontractor(s) are used, they shall be approved by the CO; the Contractor shall submit any proposed change in subcontractor(s) to the CO for approval/disapproval. 3.11 Guarantee/Warranty. In addition to the provisions of VAAR 852.246-70, the Contractor warrants that the Interface will be free from defects of workmanship under normal use for a period of not less than one year. This shall include all initial installed software and upgrades or updates. Contractor will replace or repair the analytic solution if necessary to the satisfaction of the Government during the entire warranty period at no cost to the government 3.12 Pre-Work Orientation. 3.12.1 Contractor s employees shall attend a pre-work orientation meeting, up to two (2) hours duration, at the VAMC prior to the commencement of workon site. The VA will schedule this meeting and will include discussion of the following topics: 1. Fire and Safety 2. Infection control 3. Disaster procedures 4. Privacy Training 5. Cyber Security Training 6. Installation schedule 7. VA On-site Security Guidelines 8. COR Duties and Responsibilities 9. Other Project specific items 3.12.2 The Contractor shall be responsible to ensure that Contractor s or Sub-Contractors employees coming to the work site have attended pre-work orientation for the information required above. 3.13 Unauthorized Use of Government Equipment. 3.13.1 The Contractor shall not allow his/her employees, including subcontractors employees, to open desk drawers, cabinets, or to use office equipment, including the use of non-pay telephones for any purpose other than a local emergency call. 3.13.2 The Contractor shall be responsible to provide all necessary equipment, tools, parts, and materials to perform the work. The Government shall not be obligated to provide any equipment, tools, parts, and materials to assist the Contractor in performing the work. 3.14 Identification, Parking, Smoking, and VA Regulations. 3.14.1 The Contractor's employees and/or subcontractors approved by the COR shall wear visible identification at all times while on the premises of the VAMC. Required identification shall include but may not be limited to a company identification card, which shall include the company name, employee name, title, and a photograph of the employee. 3.14.2 All employees of the Contractor or subcontractor providing services to the Government shall wear a company uniform identified with the company name and/or logo. Uniforms shall be neat and clean at all times while working on the VA premises and will be approved by the COR. 3.14.3 Possession of weapons of any type is prohibited. Enclosed containers, including tool kits, shall be subject to search. Violations of VA regulations may result in citation answerable in the United States (Federal) District Court, not a local district, state, or municipal court. 3.14.4 It is the responsibility of the Contractor to park in the appropriate designated parking areas. Information on parking is available from the VA Police Section. The VISN 16/VAMC will not invalidate or make reimbursement for parking violations of the Contractor under any conditions. 3.14.5 Smoking is prohibited inside any buildings at any VAMC. 3.14.6 Any interior or exterior doors that shall be unlocked specifically to gain access for performance of contract requirements shall be kept locked during the performance of work unless it results in the creation of a safety hazard. In those instances, the Contractor shall take necessary actions to maintain the same level of security prior to gaining access/performing work. Should any other devices need to be unlocked like an entry gate, those devices shall be locked immediately upon entry or exit. 3.14.7 At no time shall the Contractor allow any person into a locked area or loan keys/access cards to another person. Failure to comply with this requirement may lead to the Government holding the Contractor in default and subject the Contractor and employees to contract and other legal remedies. 3.14.8 Due to the nature of working at a Government facility, the Contractor's staff shall be required to sign in and out each day at a designated location determined by the COR or local facility coordinator. 3.14.9 The Contractor agrees that none of its officers or employees shall use or reveal any research, statistical, medical, or security information which may be obtained during the performance of the work or as a result their presence on Government premises without the written consent of the Government 3.15 Service Manuals/Tools/Equipment. The VISN 16 VAMCs shall not provide tools, test equipment, or service manuals to the Contractor to perform any services defined herein. The Contractor shall be responsible to obtain, have on file, and make available to the COR all operational and technical documentation on the equipment that are necessary to meet the requirements of this contract. The location and listing of the service data manuals, by name and/or the manuals themselves shall be provided to the CO upon request. 3.16 Operating/Maintenance Manuals. In addition to the training materials, Contractor shall provide an electronic copy of the operating and/or user s manuals and two (2) hard copies of each manual that fully explain and facilitate user understanding Interface software operation. Copies will be provided to COR and to each facility CAC for use in the Information Resource Management (IRM) department. Contractor herein grants authorization for VISN 16 to make multiple copies for internal use if necessary. Updated service manuals will be provided to the CO and COR with each major update. END OF SOW
 

Web Link

FBO.gov Permalink
(https://www.fbo.gov/spg/VA/VACAHCS598/VACAHCS598/VA25617Q0720/listing.html)
 

Document(s)

Attachment
 

File Name: VA256-17-Q-0720 VA256-17-Q-0720_1.docx (https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=3545171&FileName=VA256-17-Q-0720-000.docx)

Link: https://www.vendorportal.ecms.va.gov/FBODocumentServer/DocumentServer.aspx?DocumentId=3545171&FileName=VA256-17-Q-0720-000.docx

 

Note: If links are broken, refer to Point of Contact above or contact the FBO Help Desk at 877-472-3779.
 

Record

SN04528795-W 20170603/170601235023-7b3d694bfdd10f48a2a7d37d964a10b5 (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 |