TAC 09998 PWS v7 - Veterans Affairs



PERFORMANCE WORK STATEMENT (PWS)DEPARTMENT OF VETERANS AFFAIRSVeterans Health Administration (VHA)VISN 10 Real Time Location System (RTLS)System Asset Tracking Upgrade and MaintenanceDate: 5/26/2017TAC-18-44328PWS Version Number: 1.0 Contents TOC \o "1-3" \h \z \u 1.0BACKGROUND PAGEREF _Toc484781849 \h 42.0APPLICABLE DOCUMENTS PAGEREF _Toc484781850 \h 53.0SCOPE OF WORK PAGEREF _Toc484781851 \h 53.1APPLICABILITY PAGEREF _Toc484781852 \h 63.2ORDER TYPE PAGEREF _Toc484781854 \h 64.0PERFORMANCE DETAILS PAGEREF _Toc484781856 \h 64.1PERFORMANCE PERIOD PAGEREF _Toc484781857 \h 64.2PLACE OF PERFORMANCE PAGEREF _Toc484781858 \h 64.3TRAVEL PAGEREF _Toc484781859 \h 64.4CONTRACT MANAGEMENT PAGEREF _Toc484781860 \h 64.5GOVERNMENT FURNISHED PROPERTY PAGEREF _Toc484781861 \h 74.6SECURITY AND PRIVACY PAGEREF _Toc484781862 \h 74.6.1POSITION/TASK RISK DESIGNATION LEVEL(S) PAGEREF _Toc484781863 \h 75.0SPECIFIC TASKS AND DELIVERABLES PAGEREF _Toc484781864 \h 85.1PROJECT MANAGEMENT PAGEREF _Toc484781865 \h 85.1.1AGILE PROJECT MANAGEMENT METHODOLOGY PAGEREF _Toc484781866 \h 85.1.2TECHNICAL KICKOFF MEETING PAGEREF _Toc484781867 \h 95.1.3CONTRACTOR PROJECT MANAGEMENT PLAN PAGEREF _Toc484781868 \h 105.1.4REPORTING REQUIREMENTS PAGEREF _Toc484781869 \h 105.1.5TRANSITION (OPTIONAL TASK) PAGEREF _Toc484781870 \h 105.2RTLS ACTIVE ASSET TRACKING Technology Integration to Maximo PAGEREF _Toc484781871 \h 115.2.1RTLS DATA TO MAXIMO PAGEREF _Toc484781872 \h 125.2.2CENSIS CENSITRAC PAGEREF _Toc484781873 \h 125.3RTLS PASSIVE ASSET TRACKING TECHNOLOGY INTEGRATION TO MAXIMO PAGEREF _Toc484781874 \h 125.3.1RFID HANDHELD SCANNERS PAGEREF _Toc484781875 \h 125.3.2PASSIVE RFID PORTAL PAGEREF _Toc484781876 \h 135.4ASSESSMENT OF CURRENT HOSTING ENVIRONMENT PAGEREF _Toc484781877 \h 135.5SOFTWARE MAINTENANCE AND Monitoring Support PAGEREF _Toc484781878 \h 145.6Operational Support (Help Desk) PAGEREF _Toc484781879 \h 155.6.1SUPPORT RESPONSE TIMES PAGEREF _Toc484781880 \h 165.7Testing AND Validation PAGEREF _Toc484781881 \h 175.8SYSTEM ADMINISTRATION PAGEREF _Toc484781882 \h 175.8.1CONFIGURATION MANAGEMENT SERVICES PAGEREF _Toc484781883 \h 185.9BACKUPS AND DISASTER RECOVERY PAGEREF _Toc484781884 \h 185.10MAP UPDATE SUPPORT PAGEREF _Toc484781885 \h 196.0GENERAL REQUIREMENTS PAGEREF _Toc484781886 \h 196.1PERFORMANCE METRICS PAGEREF _Toc484781887 \h 196.2FACILITY/RESOURCE PROVISIONS PAGEREF _Toc484781888 \h 20 BACKGROUNDReal Time Location System (RTLS) is an umbrella term that includes multiple technologies for locating and tracking items. It includes Wireless Fidelity (Wi-Fi) based location finding, active and passive Radio Frequency Identification (RFID), and a few other location technologies, including ultrasound (US) and infrared (IR). The potential uses and benefits of this technology throughout VA are significant, and include improvement of quality of patient care, improved patient satisfaction, reduction of health care asset management costs, improvement of capacity/resource planning, improvement of employee and patient safety, as well as improvement of general asset management and inventory.Veterans Integrated Service Network (VISN) 10 serving Indian, Michigan, and Ohio, comprised of former VISNs 10 and 11, implemented an enterprise-wide Real Time Location System (RTLS) with three (5) distinct applications in twelve (12) facilities in Illinois, Indiana, Michigan, and Ohio. The five RTLS applications include:Asset Tracking – using both passive and active technologiesRFID Enabled Cardiac Cath Lab Supply CabinetsSterile Processing Workflow Temperature MonitoringPatient Elopement and WanderingThe RTLS solution brought five areas together for configuration, use, and reporting under one unified graphic user interface (GUI) software package and through a centralized, networked, virtual, server-system. VISN 10 used Shipcom Wireless’ Catamaran and VISN 11 used Intelligent InSites.NOTE: October 1, 2015 VA System of Ohio Veterans Integrated Service Network (VISN 10) and the Veterans in Partnership Healthcare Network (VISN 11) integrated. The facilities in VISN 10 now include the following sites:Ann Arbor, VA Medical Center (VAMC) - Ann Arbor, MichiganBattle Creek, VA Medical Center - Battle Creek, MichiganChillicothe, VA Medical Center – Chillicothe, OhioCincinnati, VA Medical Center – Cincinnati, OhioCleveland, VA Medical Center – Cleveland, OhioColumbus, VA Ambulatory Care Center – Columbus, OhioDayton, VA Medical Center – Dayton, OhioSaginaw, VA Medical Center-Saginaw, MichiganDetroit, VA Medical Center – Detroit, MichiganNorthern Indiana Health Care, VA Medical Centers – Fort Wayne and Marion, IndianaIndianapolis, VA Medical Center – Indianapolis, IndianaDanville, VA Medical Center – Danville, Illinois (currently part of VISN 12)Every facility uses different technologies to help locate assets. REF _Ref444155483 \h Appendix B – VA Medical Centers Asset Tracking Systems outlines and illustrates the technologies for each facility. Each facility uses a server to communicate location data to a central, virtualized server solution, which hosts the RTLS software. VISN 10 currently utilizes Naigos (IN, MI) and Solarwinds (OH) to monitor system performance and Remedy Force (IN, MI) and Solarwinds (OH) to track incidents, incident status and change requests.APPLICABLE DOCUMENTSThe Contractor shall comply with the following documents, in addition to the documents in Paragraph 2.0 in the T4NG Basic Performance Work Statement (PWS), in the performance of this effort:VA VISN 11 RTLS System Document Master Single February 1, 2016VISN 10 documentationUse Case SolutionsSCOPE OF WORKThe contractor shall provide services to upgrade and maintain the existing VISN 10 RTLS asset tracking solution. The Contractor shall provide integration services to connect the existing facility RTLS active asset tracking technologies to Maximo. These integrations will send data (active tag ID, location of tag, date, and time) from the RTLS asset tracking technology to Maximo. In addition, the Contractor shall provide integration services that provide updates to the assets (locations) in the Censis Censitrac sterile processing workflow technology to Maximo. It should be noted that not all instruments in Censitrac are considered assets. The contractor shall also provide integration services to connect the existing facility passive asset tracking technologies to Maximo. These services will include providing hand held RFID scanners capable of running Maximo Mobile Anywhere software and providing a solution which will allow existing RFID portals to report asset locations to Maximo. When an RFID tag enters the presence of an RFID portal field, the RF energy “excites” the chip on the tag and reflects back its unique ID code. The unique code is associated with the asset. VISN 10 installed approximately 704 Jamison portals (Jamison Door Company models include Hawk, Gnome, and Slims).The VISN 10 RTLS solution communicates with other VA systems to provide data and acquire data. RTLS sends location and inventory date data to the asset system of record. MAXIMO, the new asset system of record, will receive RTLS including the location and inventory data. Another important connection is the Censis and Maximo interface. The MAXIMO and RTLS interface is vital for maintaining an accurate inventory for Logistics, Biomed, and OIT. To achieve an accurate inventory with RTLS, the system will have the capability to update MAXIMO with adjustable update frequency (minimum once per day). The Contractor shall provide operational and maintenance services for the upgraded VISN 10 RTLS asset tracking solution. This includes software maintenance and monitoring, operation support and system administration. The Contractor shall have access to the RTLS infrastructure, which includes a virtual environment located at the Battle Creek VAMC Data Center, and servers located at each medical center. The contractor shall also assess this RTLS infrastructure to determine its capability to support the upgraded asset tracking solution and recommend any required system upgrade, modifications, or replacements to ensure the optimal operation and support of the upgraded VISN 10 RTLS asset tracking solution. APPLICABILITYThis task order (TO) effort PWS is within the scope of paragraph(s) 4.2.1, 4.2.2, 4.2.3, 4.2.9, 4.4, 4.8.1, 4.8.2, 4.8.3, 4.8.5, 4.8.6 and 4.8.7 of the T4NG basic PWS.ORDER TYPEThe Contractor shall propose their solution on a firm fixed price (FFP) basis.PERFORMANCE DETAILSPERFORMANCE PERIODThe base period of performance shall be 12 months from date of award. There shall be two (2) 12-month options.PLACE OF PERFORMANCEThe contractor shall perform these tasks in Contractor facilities under this PWS. In cases where the contractor cannot perform upgrade and maintenance work remotely, the contractor may do the tasks at the VA facilities noted above.TRAVELThe Government only anticipates travel under this effort to perform the tasks associated with any on site software maintenance, which the Contractor cannot accomplish remotely. Include all estimated travel costs in your firm-fixed price line items. The Government will not directly reimburse these costs. CONTRACT MANAGEMENTAll requirements of Sections 7.0 and 8.0 of the T4NG Basic PWS apply to this effort. This TO shall be addressed in the Contractor’s Progress, Status and Management Report as set forth in the T4NG Basic ERNMENT FURNISHED PROPERTYNot applicableSECURITY AND PRIVACYAll requirements in Section 6.0 of the T4NG Basic PWS apply to this effort. Specific TO requirements relating to Addendum B, Section B4.0 paragraphs 1 and 2 supersede the corresponding T4 Basic PWS paragraphs, and are as follows, 1.The vendor shall notify VA within 24 hours of the discovery or disclosure of successful exploits of the vulnerability which can compromise the security of the Systems (including the confidentiality or integrity of its data and operations, or the availability of the system). Such issues shall be remediated as quickly as is practical, based upon the severity of the incident. 2.When the Security Fixes involve installing third party patches (such as Microsoft OS patches or Adobe Acrobat), the vendor will provide written notice to VA that the patch has been validated as not affecting the Systems within 10 working days. When the vendor is responsible for operations or maintenance of the Systems, they shall apply the Security Fixes based upon the requirements identified within the contract.POSITION/TASK RISK DESIGNATION LEVEL(S)Position SensitivityBackground Investigation (in accordance with Department of Veterans Affairs 0710 Handbook, “Personnel Suitability and Security Program,” ATTACHMRNT B)Low / Tier 1Tier 1 / National Agency Check with Written Inquiries (NACI) A Tier 1/NACI is conducted by OPM and covers a 5-year period. It consists of a review of records contained in the OPM Security Investigations Index (SII) and the DOD Defense Central Investigations Index (DCII), Federal Bureau of Investigation (FBI) name check, FBI fingerprint check, and written inquiries to previous employers and references listed on the application for employment. In VA it is used for Non-sensitive or Low Risk positions.Moderate / Tier 2Tier 2 / Moderate Background Investigation (MBI) A Tier 2/MBI is conducted by OPM and covers a 5-year period. It consists of a review of National Agency Check (NAC) records [OPM Security Investigations Index (SII), DOD Defense Central Investigations Index (DCII), FBI name check, and a FBI fingerprint check], a credit report covering a period of 5 years, written inquiries to previous employers and references listed on the application for employment; an interview with the subject, law enforcement check; and a verification of the educational degree.High / Tier 4 Tier 4 / Background Investigation (BI) A Tier 4/BI is conducted by OPM and covers a 10-year period. It consists of a review of National Agency Check (NAC) records [OPM Security Investigations Index (SII), DOD Defense Central Investigations Index (DCII), FBI name check, and a FBI fingerprint check report], a credit report covering a period of 10 years, written inquiries to previous employers and references listed on the application for employment; an interview with the subject, spouse, neighbors, supervisor, co-workers; court records, law enforcement check, and a verification of the educational degree.The position sensitivity and the level of background investigation commensurate with the required level of access for the following tasks within the PWS are:Position Sensitivity and Background Investigation Requirements by TaskTask NumberTier1 / Low / NACITier 2 / Moderate / MBITier 4 / High / BI5.1 FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX 5.2 FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX 5.3 FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX 5.4 FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX 5.5 FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX 5.6 FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX 5.7 FORMCHECKBOX FORMCHECKBOX FORMCHECKBOX The Tasks identified above and the resulting Position Sensitivity and Background Investigation requirements identify, in effect, the Background Investigation requirements for Contractor individuals, based upon the tasks the particular Contractor individual will be working. The submitted Contractor Staff Roster must indicate the required Background Investigation Level for each Contractor individual based upon the tasks the Contractor individual will be working, in accordance with their submitted proposal.SPECIFIC TASKS AND DELIVERABLESPROJECT MANAGEMENTAGILE PROJECT MANAGEMENT METHODOLOGY As part of the integration services, the Contractor shall implement an Agile project management methodology, which shall include breaking the project execution into Product Builds (not to exceed three (3) months in duration). Each build shall be made up of individual sprints (two- four (2-4) weeks in duration). The Contractor shall develop the Build Plan in collaboration with the VA project team prior to beginning the build. The Build Plan is the scope of work which will be completed in the agreed up build timeframe. The Contractor shall provide a Sprint Plan prior to the beginning of each Sprint which defines the work to be completed during the Sprint. Once the Sprint Plan is approved by the Government, the Government will establish the Sprint cadence and determine when the Sprint is deemed complete. The contractor shall maintain the project backlog continuously for each build. All activity scheduled in each build and backlog shall be captured and have status showing all work items, changes, risks, and impediments. The requirements data shall be linked to test scripts and test data.Once the build plan is completed and accepted, the Contractor will initiate Sprint Planning for the first Sprint of the build. All activity scheduled in each sprint and backlog will be captured and have status showing all work items, changes, impediments, and retrospectives. The Contractor shall:1.Initiate and participate in a Sprint Planning Meeting, at the beginning of each Sprint. 2.Initiate and participate in a Sprint Review Meeting at the end of each Sprint.3.Support, coordinate and provide input for the Sprint Acceptance Criteria. The Sprint Acceptance Criteria shall be coordinated and approved for every sprint. The Contractor shall provide a certified Scrum Master to execute the necessary Agile processes. The Contractor shall incorporate its Agile project management approach as part of the Project Management plan subsection delivered under the Contractor Project Management Plan required under Section 5.1.3below.The order of development and implementation shall be as follows:1.Ohio sites – Airista/Ekahau – 5 sites2.Centrak sites – 2 sites3.Awarepoint – 2 sites4.Others – 2 sitesDeliverables:A.Build PlanB.Sprint PlanTECHNICAL KICKOFF MEETING The Contractor shall hold a technical kickoff meeting within 10 days after TO award. The Contractor shall present, for review and approval by the Government, the details of the intended approach, work plan, and project schedule for each effort. The Contractor shall specify dates, locations (can be virtual), agenda (shall be provided to all attendees at least five (5) calendar days prior to the meeting), and meeting minutes (shall be provided to all attendees within three (3) calendar days after the meeting). The Contractor shall invite the Contracting Officer (CO), Contract Specialist (CS), COR, and the VA PM.CONTRACTOR PROJECT MANAGEMENT PLANThe Contractor shall deliver a Contractor Project Management Plan (CPMP) that lays out the Contractor’s approach, timeline and tools to be used in execution of this TO effort. The CPMP should take the form of both a narrative and graphic format that displays the schedule, milestones, issues including an issue log, risk management approach including a risk registry and resource support. The initial baseline CPMP shall be concurred upon and updated monthly thereafter. The Contractor shall update and maintain the VA approved CPMP throughout the period of performance.The CPMP shall include governance plans for controlling policies and procedures in accordance with standard industry best practices for project management, execution and tracking. The plan shall describe the Contractors approach to achieving the projects objectives through the application of sound business principles and measurements to defined performance metrics.The CPMP shall include a communication plan which provides a stakeholder analysis and the contractor’s approach to manage communications with these stakeholders. The CPMP shall also include how the Contractor shall coordinate and execute planned, routine, and ad hoc data collection reporting requests as identified within the PWS. The CPMP shall also include a lessons-learned plan which provides the contractor’s approach to collect implement and report on lessons learned to include the benefits realized.Deliverables: Contractor Project Management PlanREPORTING REQUIREMENTSThe Contractor shall provide the Contracting Officer’s Representative (COR) with weekly Progress Reports. The weekly Progress Reports shall cover all work completed during the reporting period and work planned for the subsequent reporting period. The report shall also identify any problems that arose and a description of how the problems were resolved. If problems have not been completely resolved, the Contractor shall provide an explanation including their plan and timeframe for resolving the issue. The Contractor shall monitor performance against the CPMP and report any deviations. The weekly progress report shall also include an updated issue log and risk registry. The Government expects that the Contractor will continually communicate with the VA so issues that arise are transparent to both parties to prevent escalation of outstanding issues.Deliverables: Weekly Progress ReportTRANSITION (OPTIONAL TASK)The Contractor shall perform transition activities to transition business and technical domain knowledge of the existing RTLS infrastructure, and shall complete a Transition Project Plan detailing all activities specific to ensure seamless transition of the required maintenance activities detailed in PWS Sections 5.2 through 5.6. The Plan shall detail Contractor and VA roles and responsibilities in this process and include the Contractor’s strategy, timeline, and approach to address all tasks required in PWS Sections 5.2 through 5.6.Upon COR approval of the Transition Plan, the Contractor shall create a Phase-In Transition Checklist identifying a detailed list of tasks, responsibilities, deliverables and timelines required to implement the Plan. The Contractor shall execute the steps identified in the Phase-In Transition Checklist and shall revise the checklist to document the successful completion of all transition activities.Deliverables: Transition Project Plan Phase-In Transition ChecklistRTLS ACTIVE ASSET TRACKING Technology Integration to MaximoThe contractor shall provide integration services to connect the existing VISN 10 RTLS active asset tracking technologies to Maximo. The VISN 10 RTLS active asset tracking solution includes a collection of technologies in VAMCs in Indiana, Illinois, Michigan, and Ohio (see REF _Ref444155483 \h APPENDIX B – VA MEDICAL CENTERS ACTIVE ASSET TRACKING SYSTEMS). The technologies by facility are listed in Table 1 below.Table SEQ Table \* ARABIC 1 - VISN 10 RTLS TechnologiesRTLS TechnologiesFacilityBase TechnologiesAdditional TechnologyCentrak – 900 MHzDetroit900 MHzInfraredCentrak – MultimodeIndianapolis802.11 (Wi-Fi)InfraredAirista/EkahauChillicotheCincinnatiClevelandColumbusDayton802.11 (Wi-Fi)InfraredAwarepointDanvilleAnn Arbor802.15.4 (ZigBee)AeroscoutBattle Creek802.11 (Wi-Fi)UltrasoundRF CodeSaginaw433 MHzInfraredSonitorNIHCSUltrasoundRTLS DATA TO MAXIMOThe vendor shall provide an interface which provides RTLS data from the facilities to Maximo. The interface shall send the location, date, and time of the RTLS tag when the tag communicates with the RTLS location engine. The vendor shall provide provide the VA with the ability to define the frequency of the update from the RTLS to Maximo. In addition to the location, time, and date, the vendor shall the interface with battery levels and RFID tag IDs. The interface shall provide fields in the MAXIMO file for equipment inventory.Data Fields sent from RTLS to MaximoDateTimeRTLS ID (tag ID)Location (Resolved by RTLS technology location engine)Battery level of RTLS tagCENSIS CENSITRACThe Contractor shall provide a solution, which will provide Maximo with the location of an asset that Censis Censitrac tracks through the sterile processing workflow. Censis Censitrac identifies the asset by the id (### EE##### or ### MX###### - which is the VistA instance followed by EE or MX and a number). The location comes from the Censis Censitrac program when the asset associated with a tray, which the end user scans to a location (e.g. clean storage shelf, decontamination, clean corridor).Data from Censis Censitrac?Location?Date/Time?EE or MX asset ID #RTLS PASSIVE ASSET TRACKING TECHNOLOGY INTEGRATION TO MAXIMOThe contractor shall provide integration services to connect the existing VISN 10 RTLS passive asset tracking technologies to Maximo. All VISN 10 sites utilize the same passive asset tracking solution (see APPENDIX A- Passive Asset Tracking System)RFID HANDHELD SCANNERSThe contractor shall provide an iOS-based RFID scanner compatible with the Omni-ID tag (900 MHz). The scanner shall also have an IR scanner. The handheld scanner will run Maximo Mobile Anywhere software, which will provide workflows including: commissioning an RFID tag (active or passive) to an asset, decommissioning a tag from an asset, updating the location and/or date of an asset, displaying the battery level of active tag, and other workflows. PASSIVE RFID PORTALThe contractor shall provide a solution, which will provide Maximo with the location of RFID tags from fixed portals (RFID readers or antenna). Data from RFID PortalsLocationDate/TimeRFID Tag IDEnterprise Service BusFacility RTLS Technology 1Facility RTLS Technology 2Facility RTLS Technology NMaximo ServerHandheld ScannerEnterprise Service BusFacility RTLS Technology 1Facility RTLS Technology 2Facility RTLS Technology NMaximo ServerHandheld ScannerFigure SEQ Figure \* ARABIC 1 – The Facility RTLS Technologies will provide Maximo the RFID Tag ID (active), Location, Date, and Time. The handheld scanner will provide the RFID Tag ID (passive), Location, Date, and Time and receives a query of the assets in each location scanned from Maximo. ASSESSMENT OF CURRENT HOSTING ENVIRONMENTThe Contractor shall assess the current server hosting environment and recommend changes or modifications to support the proposed solution. The server hosting environment shall provide the ability to serve the needs of the integrations for the upgraded asset tracking RTLS solution. This includes the interfaces of the RTLS technologies and Maximo required in paragraphs 5.2 and 5.3. Appendix A and B refer to the RTLS asset tracking technologies at each of the facilities. Appendix C contains a list of the current servers for the previous RTLS solution. OIT will make servers available from the listed resources for use to support the proposed solution. The assessment of the servers for supporting the interfaces and the RTLS technologies (e.g. location engines) shall include the architecture for a robust, fault tolerant design. The assessment shall consider the Backup and Recovery Plan developed in section 5.9.DeliverablesAssessment Report for supporting RTLS InterfacesSOFTWARE MAINTENANCE AND Monitoring SupportThe Contractor shall provide software maintenance and monitoring support of the connections between RTLS technologies at each facility and Maximo. The RTLS solution consists of varying RTLS asset tracking technologies listed in Table 1 below and outlined in Appendices A and B.The Contractor shall provide a plan to monitor the RTLS solution, which includes a specific monitoring mechanism for each application and asset tracking system currently in place at each facility as described in Appendices A and B. The monitoring shall also include the RTLS hardware used to locate tags (e.g. IR, US), exit exciters, servers, interfaces, RTLS location engines, and all other RTLS infrastructure components other than the VA owned wireless infrastructure. The Contractor shall provide software maintenance and support of all existing software encompassing the complete RTLS solution as defined in the PWS (does not include Maximo). The Contractor shall be responsible for continuing any subscriptions necessary to keep the RTLS solution at optimal performance levels throughout the entire Period of Performance (PoP). See Appendix D for existing software subscriptions and descriptions of maintenance support currently in place through December 2, 2017. The Contractor shall provide support via email and phone response 24 hours per day, seven days per week, 365 days per year, including all holidays. The Contractor shall provide remote software fixes, if possible, and via on site staff if necessary. The Contractor shall maintain the existing software by providing bug fixes, version releases, patches, and updates on a quarterly basis. VA Table SEQ Table \* ARABIC 2: Software License/subscriptions, Software Maintenance/Basic Hardware MaintenanceVendorSiteLicense TypeAeroScoutBattle CreekSoftware License and MaintenanceInSitesAll sites Software License and MaintenanceRF CodeSaginawSoftware License and MaintenanceSonitorNIHCSSoftware License and MaintenanceAwarePoint Ann ArborSoftware License and MaintenanceAwarePointDanvilleSoftware License and MaintenanceCentrakIndianapolisSoftware License and MaintenanceCentrakDetroitSoftware License and MaintenanceAirista/EkahauChillicotheSoftware License and MaintenanceAirista/EkahauCincinnatiSoftware License and MaintenanceAirista/EkahauClevelandSoftware License and MaintenanceAirista/EkahauColumbusSoftware License and MaintenanceAirista/EkahauDaytonSoftware License and MaintenanceJamison PortalsOhio facilitiesMaintenance* VA will utilize enterprise software license for Oracle license and maintenance.DeliverablesSystem Monitoring and Software Support PlanDisaster Recovery PlanOperational Support (Help Desk)The Contractor shall provide Help Desk support meeting the requirements listed below for the entire RTLS system. Help Desk support is expert-level troubleshooting and analysis methods. This support includes assistance in direct response to the problems and issues associated with the Asset Tracking technologies of the RTLS solution. The contractor shall work with users to troubleshoot reported issues and work with partners to resolve RTLS operations problems. The Contractor Help Desk support shall also perform risk management mitigations for solutions to new or unknown issues. The Contractor shall develop a Help Desk Support Plan and Standard Operating Procedures (SOP) using industry best practices that includes:Help Desk Phone Number.Providing help authorized users.Authenticating a USER through questions/challenges in the user profile before giving access; providing information; or making changes to the system.Maintaining an online ticket tracking system.Managing and tracking all environment outages.Managing Help Desk request fulfillment, access management, and planned and preventive maintenance.Providing input and technical support to VA help/service desks on all layers until resolution.Providing problem management tracking of problem requests and timely resolutions Notifying the VA Project Manager (PM) of scheduled maintenance windows.Providing monthly Help Desk Usage reports.Providing Ticketing, incident and outage information/reports. The reports shall include: Ticket Volume - Quantity received, closed, reassigned, new tickets created (by the Contractor), or those introduced due to new releases and as classified by severity. These metrics shall be referenced both as a weekly (or more frequently as directed) variable and a cumulative, running total throughout the contract period.Timeliness of trouble ticket resolution in accordance with (IAW) with the severity levels metrics below - to include average (mean and median) number of calendar days to close a ticket, and average (mean and median) age of tickets. The source data used as the basis for these counts to include identification of date opened and date closed for each ticket will be made available upon the COR’s request.Deliverables:Help Desk Support PlanMonthly Help Desk Usage reports Updates to the Help Desk SOP and Support Plan SUPPORT RESPONSE TIMESThe Contractor shall provide the following levels of support response times:Severity 1: Produces an emergency in which the software for the location services or interfaces is inoperable, produces incorrect results, or fails catastrophically.Response: The Contractor shall provide hotline support within 60 minutes, and continuous resolution attempts until the issue is resolved. The Contractor shall resolve Severity 1 problems in less than forty-eight (48) hours. Severity 2: Produces a detrimental situation in which performance (throughput or response) of the software degrades substantially under reasonable loads, such that there is a severe impact on use; the software is usable, but materially incomplete; one or more functions or commands is inoperable; or the use is otherwise significantly impacted.Response: The Contractor shall provide hotline support within 2 hours. The Contractor shall resolve Severity 2 problems in less than seventy-two hours Severity 3: Produces an inconvenient situation in which the Licensed Software is usable, but does not provide a function in the most convenient or expeditious manner, and the user suffers little or no significant impact.Response: The Contractor shall resolve Severity 3 problems in less than seven (7) days.Severity 4: Produces a noticeable situation in which the use is affected in some way, which is reasonably correctable by a documentation change or by regular release from the Contractor.Response: The Contractor shall resolve Severity 4 problems in the regularly scheduled quarterly maintenance release.Testing AND ValidationThe vendor shall test and validate changes necessitated by modifications by RTLS technology software. When a change to the RTLS software requires changes to the interfaces between RTLS and Maximo, the vendor shall provide that support. The vendor shall provide all the support and upgrades to bugs and enhancements to ensure the interfaces run optimally. Prior to releasing a software update, OEM sponsored or otherwise, the contractor shall test and validate the software to minimize downtime. The contractor shall provide an upgrade and testing plan for each upgrade. The contractor shall not install updates unless test results show success and approval by the COR. The contractor shall use the server-hosting environment provided by the VA for the live system, test system, and other systems.SYSTEM ADMINISTRATIONThe Battle Creek virtual environment hosts virtual servers acting as a central hub for administration and data collection for the entire RTLS solution (See REF _Ref484608715 \h Table 4 in Appendix C – Hosting Environment).The Contractor shall, support, and maintain servers and plan for service outages and other problems that arise. The contractor shall maintain the RTLS system to ensure it runs optimally and achieves an uptime indicative of a high reliable system. Acceptable downtime periods may include upgrade to software and replacement of hardware. Unacceptable downtimes are software interface bugs, interface failure, and hardware component failure (not including hardware for which OIT is responsible).VISN RTLS Administration Responsibilities System administration responsibilities include but not limited to the following activities:Setup and maintain user accountsMaintain system uptimeIdentify hardware failureMonitor system performanceProvide guidelines for use of the computer system and networkInstall/maintain software (OS and application software)Create file systemsCreate backup and recovery policyMonitor network communicationsImplement policies for use of the computer system and networkSetup security policiesWindows patching, problem analysisManage serversDeliverables:Upgrade and Testing plansUptime ReportIncident Reports (Root Cause Analysis)CONFIGURATION MANAGEMENT SERVICESThe Contractor is responsible for establishing a VISN 10 RTLS change process with the VA's concurrence to record all changes to the deployed RTLS system and releases. This contractor shall support the VA-appointed change management resource on these duties. The contractor shall prepare the necessary Release/Change/Configuration documentation in support of the change control process.DeliverablesRelease NotesChange Control Process DocumentationChange Control Execution DocumentationChange Management Plan for patches/updates/hardware/etc.BACKUPS AND DISASTER RECOVERYThe vendor shall provide a plan for backups and disaster recovery to reduce downtime and ensure the integrity of the RTLS solution. The selected contractor shall provide a plan and solution to minimize lost data which will backup data and recover the backed-up data in a disaster scenario. The vendor shall ensure the backup and disaster recovery solution is robust. The vendor shall include the recovery period (time to restore the live system) and backup schedules, in their plans The vendor shall also provide any backups of configurations and disaster recovery of servers – this DOES NOT INCLUDE Maximo servers.Disaster Recovery and BackupsConfigurations of RTLS to Maximo interfacesConfiguration of Censis to Maximo interfaceConfiguration of systems supporting passive interfacesRTLS technology solutionsNOT includedMaximoCensisDeliverableBackup and Disaster Recovery PlanMAP UPDATE SUPPORTThe vendor shall provide support for calibration and RTLS map due to construction projections for renovations in a medical center by updating RTLS floor map. The vendor will apply the updated map from the facility’s engineering department to the RTLS technology server which includes Cisco’s Mobility Service Engine (MSE) and the RTLS technology software. The facility will prepare the map for processing and upload. The vendor shall coordinate the calibration activities with the facilities requiring the work. The vendor shall provide calibrations twice (2) per year.Facilities needing CalibrationsChillicotheCincinnatiClevelandColumbusDaytonFacilities needing Map SupportAnn ArborBattle CreekDanvilleDetroitNIHCSIndianapolisSaginaw GENERAL REQUIREMENTS PERFORMANCE METRICSThe table below defines the Performance Standards and Acceptable Performance Levels for Objectives associated with this effort. Performance ObjectivePerformance StandardAcceptable Performance LevelsTechnical NeedsShows understanding of requirementsEfficient and effective in meeting requirements Meets technical needs and mission requirementsOffers quality services/productsMeets response criteria of PWS para 5.3.1 Satisfactory or higher1. Severity 1 Response times met 100% 2. Severity 2,3,4 Response times met 95 %Project Milestones and ScheduleQuick response capabilityProducts completed, reviewed, delivered in timely mannerNotifies customer in advance of potential problemsSatisfactory or higher3. Project StaffingCurrency of expertisePersonnel possess necessary knowledge, skills and abilities to perform tasksSatisfactory or higher4. Value AddedProvided valuable service to GovernmentServices/products delivered were of desired qualitySatisfactory or higherThe Government will utilize a Quality Assurance Surveillance Plan (QASP) throughout the life of the contract to ensure that the Contractor is performing the services required by this PWS in an acceptable manner. The Government reserves the right to alter or change the surveillance methods in the QASP at its own discretion. A Performance Based Service Assessment Survey will be used in combination with the QASP to assist the Government in determining acceptable performance levels. FACILITY/RESOURCE PROVISIONS The Government will provide office space, telephone service and system access when authorized contract staff work at a Government location as required in order to accomplish the Tasks associated with this PWS. All procedural guides, reference materials, and program documentation for the project and other Government applications will also be provided on an as-needed basis.The Contractor shall request other Government documentation deemed pertinent to the work accomplishment directly from the Government officials with whom the Contractor has contact. The Contractor shall consider the COR as the final source for needed Government documentation when the Contractor fails to secure the documents by other means. The Contractor is expected to use common knowledge and resourcefulness in securing all other reference materials, standard industry publications, and related materials that are pertinent to the work.APPENDIX SEQ Appendix_ \* ALPHABETIC A - PASSIVE ASSET TRACKING SYSTEM All VISN 10 sites utilize the same passive asset tracking and management solution. The solution consists of Vizinex RFID and Omni ID -flex tags, RFID scanners, Intelligent InSites upload software, and Intelligent InSites asset management platform.Currently, 100,000+ RTLS and RFID tags uniquely identify assets and additional assets will receive tags to identify them in electronic inventory lists (EIL). A RFID-enabled scanner identifies assets in inventories using customized Intelligent InSites software to update asset location information. The inventory process consists of scanning a room-location barcode, scanning of asset RFID tags, and then a subsequent scan of the room-location barcode. The user repeats the 3-step process for all locations which need to be inventoried. The RFID scanner stores room and asset information uploads the data to the Intelligent InSites database.APPENDIX SEQ Appendix_ \* ALPHABETIC B – VA MEDICAL CENTERS ACTIVE ASSET TRACKING SYSTEMSThe RTLS, deployed at the above aforementioned VA Medical Centers, uses various technologies to track and identify the location of objects using RFID tags that transmit wireless signals. The system requires an active or passive RFID tag to track the assets on equipment inventory listing (EIL). Transmitters/receivers/sensors/access points, located throughout the facilities help determine the location of the object and to send information to the RTLS. See Appendix E for building inclusion list. A specific technology monitors each of the active RTLS technologies within VISN 10 facilities in Illinois, Indiana, and Michigan. Each facility uses a combination of hardware and software to track active tags. Maintenance Support shall include the monitoring of these systems on a continually basis to ensure that the RTLS solution is functioning at optimal performance levels.Table SEQ Table \* ARABIC 3 - Active Technology Monitoring SoftwareFacilityTechnologyMonitoring SoftwareHigh Level FunctionsDetroitIndianapolisCenTrakGMSMonitor status of system infrastructure and tagsBattery status for tags and monitorsGenerate hardware LBI reportSearch device IDsAnn ArborDanvilleZigBeeAwarePoint Status ServerMonitor status of network bridges, sensors, tagsCreate/remove devices and tags Device lookupSaginawRF CodeZone ManagerMonitor and configure locator devicesDiagnostic status view for tags and locator devicesNIHCS (Fort Wayne & Marion)SonitorSonitor Client & SolarWindsSonitor ClientMonitor status of tags, HDRs, and ASRs Configure HDRs, and ASRs, but must be performed by Sonitor personnel.Map view used to tune devicesSolarWindsMonitors other technologies in addition to Sonitor devices on the network Monitors online status of RTLS devices Sends alerts if the network drops an RTLS device Battle CreekStanley HealthcareStanley EngineConfiguration and status reporting of exciters, antennas, and tagsChange tag options for signal send rateTune devicesMap view with map layout mimicking the MSE mapsChillicotheCincinnatiClevelandColumbusDaytonAirista/EkahauEkahau SoftwareConfiguration and status reporting of exciters, antennas, and tagsChange tag options for signal send rateTune devicesMap calibrationAnn Arbor VAMC (506) – ZigBeeThe RTLS solution for the Ann Arbor VAMC tracks and manages the condition of over 26,000 assets. Awarepoint provides the active tag tracking throughout the facility using the 802.15.4 (ZigBee) protocol. The design covers all designated areas of the hospital with active tag tracking capability. The system operates anywhere in the facility without disruption, even in occupied patient rooms and sterile areas. Low-profile sensors plug securely into electrical outlets and form a wireless mesh network that provides seamless operation. The 802.15.4 solution doesn’t require a calibration. The 802.15.4 solution tracks small, battery-powered tags (less than 1.5 inch square) securely attached to equipment. Users track equipment from any accessible hospital-based computer using the RTLS GUI. REF _Ref443468398 \h \* MERGEFORMAT Figure 1 depicts the hardware and software architecture for Ann Arbor.Figure SEQ Figure \* ARABIC 2: Ann Arbor Architecture – Current ConfigurationThe deployed wireless mesh network derives its advantages from the following:Its use of a ZigBee (IEEE 802.15.4-base specification) mesh networking standardThe strength of its positioning engine algorithms The design of its tags A plugged-in sensor automatically becomes part of a network node that collects and routes data from tags to a coordinating bridge node, which forwards data to the RTLS server for interpretation. Each node on this network is self-routing and connects to other nodes. Connections between nodes dynamically update and optimize, as required. These ad hoc routing capabilities give each node the ability to automatically reroute messages in case of a node failure that might occur in the mesh. The table below lists the technical specifications for the tags and hardware.Battle Creek VAMC (515) – 802.11 WI-FI + Ultrasound AeroScout tags and hardware track and manage around 17,000 assets that are on and off the EIL. The RTLS solution tracks the items throughout the facility. AeroScout’s tags use an 802.11 active RFID technology with ultrasound capabilities for greater location granularity. Active 802.11 tags are affixed to assets—from mobile laptops on medical carts to infusion pumps and beds. The AeroScout uses the widely accepted Wi-Fi standard (802.11) as its communications protocol for RTLS and other visibility data. The VA uses their Wi-Fi networks as Active RFID readers without having to install other infrastructure. The AeroScout data capture solution has a low impact on existing networks. AeroScout uses a “beaconing” method that does not require tag-reader association to communicate. This lengthens the tag battery life, eliminates strain on Wi-Fi networks, and enables high scalability. AeroScout tags scale to meet the needs of large enterprises with tens of thousands of assets. AeroScout uses a patented Wi-Fi clear channel assessment mechanism to eliminate interference with the network.The solution provides indoor and outdoor capability (RSSI/TDOA)—it uses multiple algorithms to determine location: both TDOA (time of arrival, best for outdoors) and RSSI (signal strength, best for indoors), depending on the environment. Although Wi-Fi-based location is sufficient for some areas of the medical center, but further granularity is required in many patient care areas. AeroScout Exciters trigger AeroScout tags to transmit when in range of a specific and confined area. This chokepoint option expands the applicability of the AeroScout system, allowing the VA to use the same tags for both area and room level granularity. During the roll-out of the Active Tagging Solution, it became apparent that not all building locations were covered within the RTLS Contractual Design Document. These areas are commonly referred to as the “out of scope” locations and are as following:Figure SEQ Figure \* ARABIC 3: The AeroScout hardware and the Intelligent InSites software solutionDanville VAMC (550) – ZigBee AwarePoint provides the technology for Danville VAMC to track and manage the condition of about 11,000 assets. AwarePoint uses an 802.15.4 (ZigBee) protocol throughout the facility. The RTLS Team created a design to cover all designated areas of the hospital with active tag tracking capability. The system operates anywhere in the facility without disruption, even in occupied patient rooms and sterile areas. Low-profile sensors plug securely into electrical outlets and form a wireless mesh network that provides seamless operation. The infrastructure doesn’t require a calibration. Users track assets with small, battery-powered tags (less than 1.5 inch square) securely attached to the equipment using any accessible hospital-based computer and the RTLS GUI. REF _Ref443553447 \h \* MERGEFORMAT Figure 3 depicts the hardware and software architecture for Danville.Figure SEQ Figure \* ARABIC 4: Danville’s architecture depicts the AwarePoint hardware with the RTLS software solution.The deployed wireless mesh network derives its advantages from the following:Its use of a ZigBee (IEEE 802.15.4-base specification) mesh networking standardThe strength of its positioning engine algorithms and softwareThe design of its tags and sensorsAs soon as a sensor is plugged in it automatically becomes a network node that collects and routes data from tags to a bridge node, which forwards the data to RTLS for interpretation. Each node on this network is self-routing and able to connect to other nodes. Connections between nodes are dynamically updated and optimized, as required. These ad hoc routing capabilities give each node the ability to automatically reroute messages in case of a node failure. Detroit VAMC (553) – 900 MHz + Infrared CenTrak provides the technology for the Detroit VAMC to track about 25,000 assets. CenTrak provides a 2nd generation IR (Gen2IR) solution with 900MHz data-transfer capabilities. RTLS tracks the assets throughout the facility with special consideration for the Cardiac Catheterization Lab and nine OR suites (two minor procedure, six full suites, and one cysto) within Medical Center Building 100. CenTrak’s RTLS combines use of IR (Gen2IR) and active RFID. A monitor transmits the unique room number using Gen2IR (infrared, IR) to any tag in that room. The tag communicates the room number and its own unique ID through RF (900 MHz) to the CenTrak Location Server through an antenna using a hospital’s existing wired or Wi-Fi network, where it can be accessed in real-time by hospital personnel.The infrared signal generated by the Gen2IR will not pass through walls, and it does not suffer from traditional IR line-of-sight limitations. This provides greater granularity precision. Monitors provide greater location granularity data in rooms, hallways, and bays. Monitors use battery-power. RTLS estimates location based on RF triangulation where it doesn’t need room- or sub-room-level location data. Figure SEQ Figure \* ARABIC 5: Detroit VAMC hardware and software architecture.Indianapolis VAMC (583) – 802.11 Wi-Fi + 900 MHz + InfraredCenTrak provides the technology for the Indianapolis VAMC to track about 24,000 assets. CenTrak utilizes a 2nd generation IR (Gen2IR) solution with both 802.11 Wi-Fi and 900MHz data transfer capabilities (900MHz reduces battery usage).CenTrak combines use of 802.11 Wi-Fi, Gen2IR and active RFID. A monitor transmits the unique room number using Gen2IR to any tag in the associated room. The tag communicates the room number and its own unique ID through 900 MHz or 802.11 Wi-Fi RF to the CenTrak Location Server. Hospital personnel may search for the location of the tag via the RTLS GUI.Gen2IR will not pass through walls nor suffer from traditional IR line-of-sight limitations. It provides certainty-based RTLS. Battery-powered monitors positioned in rooms, hallways, and bays provide location granularity with certainty. RTLS estimates location based on RF trilateration in areas with no required room- or sub-room-level locations. Figure 5 Indianapolis VAMC current ArchitectureFigure SEQ Figure \* ARABIC 6: Indianapolis VAMC architecture of the hardware and software for the RTLS solution.Northern Indiana Healthcare System (610) – UltrasoundNorthern Indiana Health Care System facilities in Marion and Fort Wayne utilize an ultrasound-based RTLS technology from Sonitor to track and manage the condition of about 17,000 assets with special consideration of the four OR suites located in pairs at both facilities, Inpatient Building 172 and Clinical/Medical Building 138 in Marion and Patient/Administration Building 1 in Fort Wayne. Sonitor IPS tracks equipment indoors using ultrasound (USID). The tag transmits a unique identification signal using ultrasound waves. Receivers use Digital Signal Processing (DSP) algorithms pick up the signal and transmit it through an existing LAN/Wi-Fi network.No risk of electromagnetic interference with or from other equipment because the solution uses ultrasound. The low quantity of data transmitted from the tags requires minimal LAN bandwidth. Hospitals with existing wired or wireless LAN may easily deploy the solution. The tags have optional communication buttons for custom configuration and a relatively small footprint.Figure SEQ Figure \* ARABIC 7: Northern Indiana Facilities (Fort Wayne/Marion) architecture.Saginaw VAMC (655) – 433 MHz + IRThe Saginaw VAMC implementation uses RF Code, an active UHF asset-tracking technology provider, to track about 11,000 assets. The system coverage includes four OR suites located in Building 1, Flag Pole Building 8, Warehouse Building 9, and Building 22. The system uses active RFID technology supplemented with infrared capabilities for greater location granularity.The use of infrared achieves room-level tracking granularity by “localizing” or pinpoint asset location in defined areas associated with the sensor location. When coupled with active RFID technology to track assets in large, dense environments, this IR approach provides tracking assets down to the room level. Each room is outfitted with the following:A740 Room Locator that emits a unique ID through infraredIR light strips that emit the IR signal created by the A740IR-enabled asset tags that receive the unique IR ID and transmit that data.Saginaw implementation continues as of December 2015 as part of an expansion of the original configuration. The following areas are still in the process of final configuration:The facility has completed all the cabling and installation of the hardware for InSites to configure all CBOCs, Figure 7 Saginaw Current Architecture Chillicothe (538), Cincinnati (539), Cleveland (541), Columbus (757), Dayton (552) – Wi-Fi + IRThe Chillicothe, Cincinnati, Cleveland and Dayton VAMCs, and Columbus VAACC implementations use Airista/Ekahau, a Wi-Fi and IR asset-tracking technology provider, to track about 75,000 assets. The system uses active RFID technology supplemented with infrared capabilities for greater location granularity. The use of infrared achieves 100% room-level or sub-room-level tracking granularity by “localizing” or pinpoint asset location in defined areas associated with the sensor location. Currently, Ekahau tags in Ohio VAMCs send data packets to Cisco wireless access points which the Ekahau RTLS Control uses to determine the tag location based on its calibration. Catamaran pulls the data from the ERC and also send those data to Maximo. Ekahau TagEkahau RTLS Controller (ERC)Shipcom Wireless CatamaranMaximoConfigurable chirp rate (Moving: 1/min; stationary: 4/day)IR beacon provide 100% room/sub-room level locationRoom-level accuracy with calibration of Wi-Fi (Ekahau Site Survey)Ekahau TagEkahau RTLS Controller (ERC)Shipcom Wireless CatamaranMaximoConfigurable chirp rate (Moving: 1/min; stationary: 4/day)IR beacon provide 100% room/sub-room level locationRoom-level accuracy with calibration of Wi-Fi (Ekahau Site Survey)APPENDIX SEQ Appendix_ \* ALPHABETIC C – HOSTING ENVIRONMENTBattle Creek’s server room hosts the central, virtualized server solution. The solution allows users from the facilities listed in Section REF _Ref444155942 \r \h 1 to find assets, run reports and other RTLS related activities. Battle Creek’s local OIT and OIT Region staffs maintain the system.The virtualized server resides in the Battle Creek facility. The virtualized server solution will have eight (8) IBM servers (model x3650M3) and two (2) HP servers Model DL380. Additionally, staff will augment the CVI in Battle Creek to include three (3) additional hosts for VMWare, SSDs, and an end-to-end backup solution. This solution will go live in the first quarter of fiscal year 2017.Table SEQ Table \* ARABIC 4 - Current hardware specifications for servers hosting the RTLS solution in Indiana and MichiganROLEOSRAM (GB)CPU (vCPU)C: (GB)E: (GB)Centralized - APP1Windows Server 2012 R2 x642263050Distributed UI - WEB1Windows Server 2012 R2 x641643050Distributed UI - WEB2Windows Server 2012 R2 x641643050Distributed UI - WEB3Windows Server 2012 R2 x641643050Distributed UI - WEB4Windows Server 2012 R2 x641643050Distributed RTLS - WEB5Windows Server 2012 R2 x641643050Distributed RTLS - WEB6Windows Server 2012 R2 x641643050Distributed RTLS - WEB7Windows Server 2012 R2 x641643050Connector - Ann ArborWindows Server 2012 R2 x64623050Connector - Battle CreekWindows Server 2012 R2 x64623050Connector - DanvilleWindows Server 2012 R2 x64623050Connector - DetroitWindows Server 2012 R2 x64723050Connector - IndianapolisWindows Server 2012 R2 x64743050Connector - NIHCSWindows Server 2012 R2 x64623050Connector - SaginawWindows Server 2012 R2 x64623050Connector - VISNWindows Server 2012 R2 x64623050MS SQL 2012 SP2 SQL1Windows Server 2012 R2 x6424830200RTLS BI Application - BIAPP1Windows Server 2012 R2 x6416430100RTLS BI DatabaseWindows Server 2012 R2 x64646301000RabbitMQ Cluster Member 1Windows Server 2012 R2 x640000??????Future Release Support?????RabbitMQ Cluster Member 2Windows Server 2012 R2 x640000Totals288705702,100The servers in use in Ohio facilities are at end-of-life. Currently, each facility uses two servers (clustered for fault tolerance) for Ekahau, two for Catamaran, and one for Censis. A two-server cluster serves as a pre-production (quality assurance) environment. Dayton, Cincinnati, Cleveland and Chillicothe have an additional 8 servers (two server clusters) to support the Patient Elopement application. The VISN 10 RTLS solution in Ohio uses 42 servers, which are at end of life. The servers reside at the corresponding facility and the two pre-production servers are in Cleveland.Appendix SEQ Appendix_ \* ALPHABETIC D - EXISTING ASSET TRACKING SOFTWARE SUPSCRIPTIONSOEMSiteType of License/SupportDescriptionRF CodeSaginawAnnual Maintenance Support24/7 Technical SupportSoftware Upgrades and Bug FixesSonitorNIHCSAnnual Maintenance SupportSoftware Updates - software releases, including service releases (new builds) and new versions (higher version number) pertinent to the Sonitor RTLS configuration;Quarterly Remote Software Performance verifications;Email Support (one business day response time).AwarePointAnn Arbor/DanvilleAnnual Maintenance SupportNOC Access;Quarterly onsite diagnostic performance assessments.CentrakDetroit/IndianapolisAnnual Subscription/ Maintenance SupportAnnual Software License and Support Software Maintenance - bug fixes, upgrades and standard software patches, for: -CenTrak Location Server;Streaming Connector to User Interface Providers;Infrastructure devices: Monitors, Virtual Walls, LF Exciters, Stars, etc.;GMS (Global Monitoring System) Onsite and GMS Managed;Support Services - Software and Hardware, Level 3, for: Monitoring of GMS for RTLS performance;Updating GMS for architectural modifications or infrastructure additions;Configuration of GMS, as needed, as maintenance demands evolve, e.g. adding use cases, tags and devices;Level 3 support of onsite resources (VA), e.g. Trouble shooting, location accuracy, performance enhancements, infrastructure adjustment recommendations, etc.;Technical Assistance Center (TAC), Level 3, 9AM to 5PM, Eastern Time;Warnings, Bulletins, Alerts, Product Change Notices (PCNs) - Technical tips and FAQs;CenTrak Knowledge Center access;Engineering Assistance (via TAC).AISAnn Arbor/DanvilleAnnual SupportRemote monitoring of ZigBee network hardware twice per week using Status ServerTwice per week email report of network health will be sent to the VA Visits whenever required by the network health, as reported using Status Server, with a minimum of four scheduled visits per site every four months;Phone and email support 8-5 Eastern Time for hardware issues reported by hospital;Equipment maintenance, including labor for bridge/sensor replacement and low-battery tag replacement;Swap out of low-battery tags with ZigBee tags Limited to 12,000 tag swaps per yearTroubleshooting of any staff-reported issues on each visit;Assistance with tagging of up to fifty new assets on each visit;Documentation of activities on each visit;Packaging/handling/RMA documentation of any warranty replacement equipment; most often, immediate replacement of warranty equipment from the maintenance stockEkahauOhio SitesAnnual SupportAnnual Software License and Support Software Maintenance - bug fixes, upgrades and standard software patches, for: -Ekahau RTLS Controller (ERC)Infrastructure devices: IR BeaconsSupport Services - Software and Hardware, Level 3, for: Monitoring of ERC for RTLS performance;Updating ERC for architectural modifications or infrastructure additions;Configuration of ERC, as needed, as maintenance demands evolve, e.g. adding use cases, tags and devices;Level 3 support of onsite resources, e.g. Trouble shooting, location accuracy, performance enhancements, infrastructure adjustment recommendations, etc.;Technical Assistance Center (TAC), Level 3, 9AM to 5PM, Eastern Time;Warnings, Bulletins, Alerts, Product Change Notices (PCNs) - Technical tips and FAQs;Knowledge Center access;Engineering Assistance (via TAC).APPENDIX E – INCLUDED BUILDING LISTFacilityBuildingAnn Arbor15Ann Arbor1Ann Arbor2Ann Arbor22Ann Arbor24Ann Arbor28Ann Arbor3Ann Arbor31Ann Arbor32Ann Arbor30Ann Arbor4Ann Arbor7Ann ArborCWEALTHAnn ArborCWTAnn ArborDOMAnn ArborAA-IPCCAnn ArborHURONTAnn ArborMHICMAnn ArborNCRC 14Ann ArborNCRC 15Ann ArborNCRC 16Ann ArborNCRC 18Ann ArborT4Ann ArborT5Ann ArborT7Ann ArborToledo-CBOCAnn ArborUniversityAnn ArborFlint-CBOCAnn ArborJackson CBOCAnn ArborT2Ann ArborT3Ann ArborT6Ann ArborToledo AnnexAnn ArborToledo Satellite OPCAnn ArborToledo Vet CenterBattle Creek1Battle Creek10Battle Creek101Battle Creek109Battle Creek11Battle Creek12Battle Creek127Battle Creek13Battle Creek131Battle Creek132Battle Creek133Battle Creek134Battle Creek135Battle Creek136Battle Creek137Battle Creek138Battle Creek14Battle Creek140Battle Creek141Battle Creek144Battle Creek145Battle Creek151Battle Creek154Battle Creek155Battle Creek156Battle Creek157Battle Creek158Battle Creek159Battle Creek16Battle Creek160Battle Creek161Battle Creek162Battle Creek163Battle Creek164Battle Creek165Battle Creek168Battle Creek169Battle Creek17Battle Creek170Battle Creek171Battle Creek172Battle Creek173Battle Creek174Battle Creek175Battle Creek176Battle Creek177Battle Creek178Battle Creek179Battle Creek18Battle Creek180Battle Creek181Battle Creek182Battle Creek183Battle Creek184Battle Creek185Battle Creek186Battle Creek187Battle Creek188Battle Creek189Battle Creek19Battle Creek190Battle Creek191Battle Creek192Battle Creek193Battle Creek194Battle Creek195Battle Creek196Battle Creek197Battle Creek199Battle Creek2Battle Creek20Battle Creek200Battle Creek21Battle Creek22Battle Creek23Battle Creek24Battle Creek25Battle Creek26Battle Creek27Battle Creek28Battle Creek29Battle Creek3Battle Creek30Battle Creek300Battle Creek32Battle Creek33Battle Creek39Battle Creek4Battle Creek40Battle Creek5Battle Creek51Battle Creek515Battle Creek515BYBattle Creek515GABattle Creek515GCBattle Creek515LABattle Creek5GBattle Creek6Battle Creek65Battle Creek69Battle Creek7Battle Creek70Battle Creek73Battle Creek8Battle Creek82Battle Creek82MRIBattle Creek83Battle Creek84Battle Creek85Battle Creek9Battle Creek96Battle Creek97Battle Creek98Battle Creek99Battle CreekTRPBattle CreekTRP2Battle CreekBHBattle CreekGCBattle CreekGROPCBattle CreekHCCBattle CreekHCHVBattle CreekLANSBattle CreekMETBattle CreekMUSKBattle CreekRCS2Battle CreekVAOCBattle CreekVASCBattle CreekVCODetroit100Detroit103Detroit1Detroit10Detroit11Detroit12Detroit13Detroit14EDetroit14WDetroit18Detroit19Detroit22Detroit23Detroit31Detroit6Detroit67Detroit7Detroit8DetroitT42DetroitVBADetroitWAREHOUSEIndianapolis0Indianapolis1Indianapolis101Indianapolis19Indianapolis2Indianapolis21Indianapolis22Indianapolis3Indianapolis33Indianapolis4Indianapolis401Indianapolis41Indianapolis42Indianapolis5CSRIndianapolisR5WIndianapolis7Indianapolis9IndianapolisANXIndianapolisBRTCIndianapolisCHIndianapolisCLIndianapolisDOMIndianapolisFCIndianapolisFHIndianapolisHOMIndianapolisIBIndianapolisIUIndianapolisLBIndianapolisNBIndianapolisNIFSIndianapolisOPTIndianapolisR2IndianapolisR3IndianapolisR3WHIndianapolisROIndianapolisT6IndianapolisVCCIndianapolisVETIndianapolisVNMSIndianapolisWBMarion1Marion10Marion100Marion105Marion108Marion11Marion114Marion118Marion119Marion12Marion120Marion121Marion122Marion123Marion124Marion127Marion128Marion13Marion135Marion136Marion137Marion138Marion139Marion140Marion145Marion149Marion15Marion150Marion153Marion155Marion16Marion165Marion166Marion167Marion168Marion169Marion17Marion170Marion171Marion172Marion173Marion174Marion175Marion18Marion183Marion184Marion185Marion19Marion190Marion2Marion20Marion21Marion22Marion24Marion25Marion3Marion3004Marion4Marion41Marion42Marion47Marion49Marion5Marion50Marion51Marion52Marion53Marion54Marion55Marion55AMarion58Marion6Marion60Marion610Marion62Marion65Marion69Marion7Marion72Marion73Marion75Marion76Marion78Marion79Marion8Marion83Marion9Marion91Marion93Marion94Marion95Marion96Marion97MarionQ102MarionQ26MarionQ27MarionQ28MarionQ29MarionQ30MarionQ31MarionQ32MarionQ33MarionQ34MarionQ35MarionQ36MarionQ37MarionQ28MarionQ55MarionT501MarionT504MarionT516MarionT517NIHCSCBOCFWNIHCSCBOCGONIHCSCBOCMUNIHCSCBOCPUNIHCSCOBCSBNIHCSSBVCFort Wayne1Fort Wayne10Fort Wayne15Fort Wayne16Fort Wayne17Fort Wayne2Fort Wayne3Fort Wayne4Fort Wayne5Fort Wayne6Fort Wayne7Fort WayneT1Fort WayneT2Fort WayneT3Fort WayneT4Fort WayneT5Fort WayneT6Fort WayneFWWCFort WayneLSaginaw1Saginaw16Saginaw19Saginaw2Saginaw20Saginaw21Saginaw22Saginaw3Saginaw30SaginawSaginawSaginaw4Saginaw6SaginawAOPCSaginawBDXSaginawCADBOCSaginawCHBOCSaginawCLOPCSaginawENG TRLSaginawGOPCSaginawGOPC2SaginawGOPC3SaginawGRYBOCSaginaw9SaginawHCASaginawOSCODASaginawSAGADMSaginawSVCSaginawTCVCSaginawTOPCDanville13Danville14Danville19Danville100Danville101Danville102Danville103Danville104Danville110Danville111Danville112Danville113Danville114Danville115Danville116Danville119Danville123Danville124Danville125Danville128Danville129Danville136Danville200Cleveland1Cleveland1AClevelandECClevelandNAVClevelandTRClevelandClevelandTRLClevelandClevelandDayton115Dayton126Dayton127Dayton128Dayton131Dayton135Dayton138Dayton1CCDayton226Dayton302Dayton305Dayton307Dayton310Dayton315Dayton320Dayton321Dayton322Dayton330Dayton340Dayton408Dayton409Dayton410Dayton411DaytonHA-1DaytonHA-2DaytonWPAFBCincinnati341Cincinnati0204VCincinnati1Cincinnati15Cincinnati16Cincinnati3Cincinnati8CincinnatiTCCincinnatiTECincinnatiTFChillicothe1Chillicothe3Chillicothe7Chillicothe8Chillicothe9Chillicothe18Chillicothe20Chillicothe21Chillicothe22Chillicothe23Chillicothe24Chillicothe25Chillicothe26Chillicothe27Chillicothe28Chillicothe30Chillicothe31Chillicothe35Chillicothe36Chillicothe38Chillicothe39Chillicothe40Chillicothe60Chillicothe210 (Under Construction)Chillicothe212Chillicothe228Chillicothe247Chillicothe252ChillicotheCCColumbus1A ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download