ID05140075_PWS.docx

PERFORMANCE WORK STATEMENT

For

Patient Movement Items (PMI) Automated Asset Tracking System

A procurement by the U.S. General Services Administration On behalf of the U.S. Air Force Mobility Command Surgeon General Readiness Division (AMC/SGXM), Scott AFB, IL 62225-5219

ITSS Number: GSA ITSS ID05140075

June 6, 2014

This requirement is being solicited as a Task Order under the Not Yet Determined

NAICS

Product Service Code

1. BACKGROUND AND OBJECTIVE/APPLICABLE DOCUMENTS

1.1. Background. Patient Movement Items (PMI) consists of designated medical equipment, durable supplies, and consumable supplies necessary to support a patient during aero-medical evacuation (AE). The main purpose of the PMI Program is to prevent the degradation of the medical elements capabilities due to an outflow of PMI transported with patients through the AE system and/or used in support of a Critical Care Air Transport Team (CCATT). Joint Publication 4-02, Appendix A (26 Jul 2012), identifies the Air Force as having responsibility for overall management, in transit visibility, and tracking of PMI.

The Air Force Surgeon General has delegated program responsibility to the Air Mobility Command Surgeon (AMC/SG). The AE system uses PMI from a Medical Treatment Facility (MTF), Aero-medical Staging Facility (ASF), PMI center or AE squadron. During the use of PMI assets, physical location is tracked using automatic identification and data capture (AIDC) technology installed across AMC PMI and Aero-medical locations.

AMC is seeking to acquire an asset tracking system to report the current location and historical movement of the mobile medical equipment and supplies that are assigned to the Patient Movement Items (PMI) program (PMI ATS).

1.2. Objectives. The ability to access and track assets throughout the PMI network is vital to ensuring mission critical assets are ready, staged and available to treat the critically wounded warfighter. The ability to access and track assets includes a dedicated automated process that maximizes the efforts of the AE and PMI staff. Reducing the cost of un-locatable inventory, labor to perform physical inventories, and the potential for inaccurate data entry are among the specific goals of this initiative. In addition to cost efficiencies, the PMI ATS will increase Commands confidence when reporting and planning on mission readiness. In addition to supporting the direct mission the AE and PMI mission, it is also a key objective to support the stated goals of the Defense Healthcare Agency (DHA) in achieving greater system integration and efficiencies through inter-operability with multi-service medical treatment facilities (MTF’s).

Because PMI assets are used to support patients within both the AOR and throughout the AE peace time transportation network, the PMI ATS needs to interface with the current Defense Medical Logistics Standard Support (DMLSS) platform as well as be capable of sharing asset and tracking information with MTF facility’s and their Real Time Location Systems (RTLS) systems that are being deployed within the DHA MTF’s. It is also the objective of the PMI ATS to support the Department of Defense Information Assurance Certification and Accreditation (DIACAP) certification requirements.

This Performance Work Statement outlines goals and requirements that the PMI ATS system shall meet. The contractor shall also provide the necessary personnel, products, materials and services required to deliver the PMI ATS system, along with technical helpdesk support and equipment maintenance to ensure maximum system availability and effective tracking and management of PMI assets.

1.3. Applicable Documents

· Title 5 of the U.S. Code, Section 552a, The Privacy Act.

· AFPD 33-2, Information Assurance (IA) Program

· Title 44 United States Code Section 3602

· DoDD 8500.1, Information Assurance (IA)

· DoDI 8500.2, Information Assurance (IA) Implementation

· DoDD 8100.2, Use of Wireless Devices, Service and Technologies in the DOD Global Information Grid

· AFI 33-100, User Responsibilities and Guidance for Information Systems

· AFI 33-200, Information Assurance (IA) Management

· AFI 41-209, Medical Logistics Support

· AFI 41-201, Managing Clinical Engineering

· AFI 41-216, Defense Medical Logistics Standard Support (DMLSS)

· DODI 6000.11, Patient Movement

· JP 4-02, Health Service Support

2.0 SCOPE/SPECIFIC TASK

2.1. Scope. The PMI ATS will mirror the geographical and process construct of the Air Force’s AE network. This architecture is made up of 90 PMI locations that management, store and deploy PMI assets. Location capability must be expandable. The count of the PMI ATS tracking locations includes:

· 10 PMI Warehouse and Maintenance Centers (Category I)

· 3 Formal Training Platforms (Category II)

· 18 Active Duty and Theater Units (Category II)

· 59 Air Nation Guard/Air Force and Army Reserve and Navy recycle Units (Category III) Each target locations will receive a computer(s), tracking software, mobile handheld scanner(s), docking station(s), passive RFID antennas, passive RFID reader(s), connecting cabling and power supply(s) and a supply of passive RFID labels (tags).

The PMI ATS application to be installed at each site must have the capability to manage the quantity and asset types that are assigned to the location. System capacity requirements include:

· up to 20,000 items for Category I sites

· up to 10,000 items for Category II sites

· up to 5,000 items for Category III sites PMI asset types include:

· Infusion pump

· Ventilators

· Vital signs monitors

· Suction therapy

· Wound therapy

· O2 Monitoring

· Defibrillator

· Patient Monitor

· Stacking Litter Systems

Each of the tracking site installations will include pre-delivery system configuration (unique to the specific location requirements), travel to and from the location, onsite installation of the computer and scanning hardware, system validation, user training, documentation and manuals. Tracking sites will be configured to share their tracking information with a dedicated Central Server that is located at AMC/SG Scott AFB IL. The connections to this Central Server will comply with the Air Force’s DIACAP requirements.

The following is a list of the 90 PMI locations. AMC SG is responsible for providing vendor with prioritized installation list.

PMI Automated Asset Tracking System Solicitation ID05140075

018th AES Kadena 018th AES DET 1 - Hickam AFB 018th MDG Kadena PMI Center 034th AES Peterson 036th AES Pope 043th AES Pope 045th AES MacDill 051st MDG - Osan Korea 059th MDW MERC - Lackland 059th Medical Wing CASF Lackland AFB 060th MDG ASF Travis AFB 060th PMI Travis 086th AES Ramstein 086th CASF at Ramstein 086th PMI - Ramstein AFB 10 EAES Ramstein 109 AES, Minneapolis 118 AES Nashville 137 AES Oklahoma City 139 AES Scotia 142 AES New Castle 146 AES Channel Islands 156 AES Charlotte 167 AES Martinsburg 183 AES Jackson 187 AES Cheyenne 315 AES Charleston 349 AES Travis 374th PMI Yokota 375 AES Scott 375 MDG MERC Scott HQ AMC/SG PMI Center Scott 379 EAES Al Udeid 379 EMDG Al Udeid 433 AES Lackland 439 AES Westover

445 AES Wright-Patterson 446 AES McChord 452 AES March 455 EAEF Bagram 455 EMDG Bagram 459 AES, Andrews 514 AES McGuire 775th EAEF Andrews 775th EAEF Kelly 775th EAEF Travis 779 ASF Andrews AFB, 779th PMI Andrews 908 AES, Maxwell 911th AES Corapolis (Pitts) 914 AES, Niagara Falls 932 AES, Scott 934 AES, Minneapolis 094th AES Dobbins AFRC AE FTU, Pope AAF, AFMSA/SGSLW (Kelly USA) Belvoir Community Hospital Blanchfield Army Community Hospital

CAMP AS SAYLIYAH

Carl R. Darnall Army Medical Center Eisenhower Army Medical Center Evans Army Community Hospital (Fort Carlson) HQ AMC SG PMI Program Mgmt Laptop Landstuhl Regional Medical Center Madigan Army Medical Center Naval Hospital Rota Spain Naval Hospital Yokosuka Naval Hospital Naples Italy Naval Hospital Camp Lejeune Naval Hospital Camp Pendleton Naval Hospital Guam

Naval Medical Center San Diego Naval Medical Center Okinawa Naval Medical Center, Portsmouth Naval Medical Logistics Command PMITS Tier III Service Center San Antonio Military Medical Center (SAMMC) Tripler Army Medical Center Walter Reed National Military Medical Center (WRNMMC) William Beaumont Army Medical Center Womack Army Medical Center 94th AES Deployable Kits @ HQ AMC SG PMI Center

2.2. System Requirements

2.2.1. System Security

· Vendor is responsible for all Information Assurance certifications/documentation and required approvals.

· The system shall conform to the Department of Defense Information Assurance Certification and Accreditation (DIACAP) IA standards The system shall provide secure protocols for accessing the application that satisfies the principles of “least privileges necessary” and comply with DoD specific username and password requirements.

· The system shall provide user-based security protocols to assign users to particular groups, based on needed application functionality. Setup of new accounts shall be restricted to the top administrator(s).

· The system shall conform to the prevailing Federal Information Processing Standard (FIPS) data encryption process each time that a data file is prepared for distribution.

· The system shall provide automated database management, including settings and processes for backup, recovery, and general data correction. These tools shall be limited to users who belong to the Administrator user group.

· The system shall provide audit logs for tracking any changes to the database.

· The system must be able to interoperate with current fielded medical treatment facility (Travis, Andrews, & San Antonio Medical Center) ATS systems to ensure a system wide enterprise materiel solution.

2.2.2. Data Capture

· The system shall provide the capability of creating tracking records and item identifiers via keyboard entry.

· The system shall provide the capability of using mobile portable handheld scanners to capture either barcodes and/or pRFID (passive RFID) labels with the capability to upgrade to active RFID. The scanners must be capable of synchronizing through a docking cradle. The mobile scanners must be able to receive system and parent table updates during the synchronizing process.

· The system shall provide the option to use fixed pRFID, antennae, & readers to capture data from pRFID labels.

· The system shall provide the capability tracking battery-assisted active RFID tags using the facility’s existing 802.11 Wi-Fi infrastructure.

· The system shall provide the capability of printing barcode labels, and encoding of passive labels.

· The system shall provide system administrators the ability to remotely activate active RTLS tags.

· System will provide hierarchal data composite view for program management at higher headquarters/MAJCOMS as authorized by AMC SG.

· The system shall be capable of tracking both active and passive tags and be able to show last known location and historical locations for any given tagged asset.

· The system shall be capable of monitoring at least 5,000 (CAT III site) individual assets at a single facility and a total number of assets across the enterprise of approximately 1M assets.

· PMI Center Allowance Standard level equipment inventories will be monitored via passive tags and portal detectors or other non-active tracking means.

· The system shall be capable of providing the following levels of resolution based on the intended function of the area.

· The system shall be capable of providing location data to within a specified zone for both active and passive tags.

· The system shall be capable of providing room-level accuracy with at least 97% precision (or confidence) in covered areas for active tags.

· The software shall have an open application programming interface (API) for potential third party application integration.

· The software shall support role-based administration and asset management that allow for various levels of software access, including at a minimum view-only access, edit access, and administrator access. The system shall be capable of providing zone tracking, such as when a tag passes a system-defined boundary or through an egress point.

· The system shall be capable of generating an alert if a tag passes the defined perimeter.

· The system shall be capable of providing historical location data for at least a 12-month period.

· The system shall be capable of providing 98% uptime calculated monthly.

· If the system requires servers to be installed at the facility or unit, then the vendor shall supply uninterruptible power supplies.

· The system shall be capable of covering disparate physical locations (such as outlying buildings or AE and CCATT units). The remote locations may be in different countries and at a distance of hundreds of miles.

· The system shall allow for centralized monitoring of all locations associated with the parent facility. A single building may be up to 200K square feet. The PMI Centers, WRM Storage areas, MTF or clinics may span multiple buildings.

· The system shall be capable of filtering information based on location, building, department, floor, room, or zone.

· The system shall be capable of capturing and managing business requirements, such as equipment location and equipment status (i.e. in use/not in use, moving, not moving, time since moved etc), to facilitate inventory management and asset tracking.

· The system shall have the capability to manually locate passive tags (e.g. a handheld scanner) and shall be capable of capturing the system location of the passive tags (e.g. zone, room, etc.).

· The contractor shall ensure that products provided under this contract, to include hardware, software, firmware, and middleware, whether acting alone or combined as a system, are year 2000 compliant as defined at FAR Part 39.

· The Contractor shall comply with Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d). Specifically, the procurement, development, maintenance, or integration of electronic and information technology (EIT) under this contract must comply with the applicable accessibility standards issued by the Architectural and Transportation Barriers Compliance Board at CFR part 1194.

· Active tags must communicate over the 802.11 access points and network. Proprietary frequencies and other technologies are not an acceptable alternative.

· Active and Passive tags.

· There shall be options available for permanent and temporary mounting.

· The tags shall be able to be cleaned via typical equipment infection control methods (i.e. wiped down with disinfectant).

· Tags shall be capable of being mounted on multiple types of materials used in the construction of medical equipment, including but not limited to plastics and metals.

2.2.4. Item Information

· The system shall be capable of storing the OEM’s serial numbers and other equipment control numbers that may be part of the customer’s legacy system.

· The system shall capable of supporting and storing multiple identification protocols in the asset management database, specifically: Barcode ID(s), pRFID ID(s), RTLS ID(s), and Universal ID(s)

· The system shall provide the ability to link an individual serialized item to a tracking event regardless of which capture technology created the tracking event.

· The system shall provide multiple stratifications of the asset ownership, i.e. ownership ID, ownership group, and ownership class.

· The system shall provide the capability of storing manufacture information, including OEM serial number, make, model, version, picture, description, etc.

· The system shall provide the capability of organizing data into multiple project identification nomenclature formats, including notes, category, project, and other open user-defined fields.

· The system shall support the use of multiple date fields, including acquisition date, expiration date, and due date.

· The system shall supports the storage and cross-referencing of general accounting fields that can be used in calculating ROI, including cost indexing and value (revenue) indexing, and are available to users through report generation tools.

· The system shall provide the ability to print and display key asset activity, including:

· Current item location: The physical presence of the item when it was last physically inventoried (recorded encounter). This includes the date and time and what the item was doing (in use, on stand-by or being repaired) when it was physically encountered.

· History of activity by item: The history of the movement activity of an item is calculated using the database records of when an item changes from one location and status to a different location or status.

· Utility by type: The relationship between an item’s actual use and its total potential to be used. Utility is reported as a percentage and is measured over a span of time at a given location. Re-stated, “The total number of item-days (billable units of measurement) divided by the total potential item-days for items of that same type within the given location.

· Duration by Type by Status: The length of time an item stays in a given status (standby, on patient, repair, or in transit) is reported by status in time units (days).

· The system shall displays information (naming convention) in terms that approximate the nomenclature of the customer legacy system, and employs an open architecture that allows for importing and exporting data records to be used by the legacy system.

2.2.5. Location Information

· The system shall support multiple levels of location granularity, including the capability to define a location with multiple nesting sub-locations.

· The system shall provide the capability to search information about these locations and sub-locations using key searchable fields that include location type, location group, addressing, contact information, and other key location information.

· The system shall support the use of searchable geographical categories, including branch, region, area, and division groupings.

· The system shall support the use of functional sub-categories, searchable by ownership group, project type, or financial and regulatory groupings.

· The system shall provide capability to measure, display and prints summary information on key asset activity, including:

· Current items by location: The physical presence of the item when it was last physically inventoried (last recorded encounter) at a particular location, including the date and time and what the item was doing (in use, on stand-by, or being repaired) when it was physically recorded at that location.

· History of activity by location: The history of all movement activity, by item, at a given location.

· Utility by location: This is the accumulated “utility by item type” generated by a particular location or department. Utility by item type is the relationship between an item’s actually use and its total potential to be used. Utility is reported as a percentage and is usually measured over a span of time at a given location.

· Duration by location: This is the length of time an item stays in a given status, (on standby, on patient, under repair, in transit, etc.) within a given location. Duration is reported by status in time units (days).

· Duration by Status: This is the length of time an item stays in a given status (on stand-by, under repair, in transit). Duration is reported by status in time units (days).

· Displays information (naming convention) in terms that approximate the nomenclature of the legacy system. Asset tracking solution must have an open architecture that allows for importing and exporting of data records to be used by the legacy system.

2.2.6 Alerts

· The system shall allow users to record the response to alerts, within the system.

· The system shall provide the capability to configure, view, log and manage alerts and alarms within the asset tracking solution.

· The system shall provide the capability to alert and alarm whenever a user-defined condition has or has not been met.

2.2.7. Data Accessibility

· The system shall provide the capability to convert data fields taken from external legacy systems that are delivered in common formats like XLS or comma-delimitated into a system data exchange file that can be imported into the asset management database.

· The system shall provide the capability to search the asset-tracking database using a simple text string. The simple text string query must be capable of finding full matches and partial matches within the item, tracking and location tables.

· The system shall provide the capability to view key system data fields in the following viewable formats: form view, grid view, map view, or paper printout.

· The system shall allow visibility of local and remote site tracking records, depending upon the user access profile and group assignment.

· The system shall provide the capability to edit records, individually, or in a batch mode.

· The system shall provide an automated function to create data exchange files that allow local client users to share records between other clients and servers within the asset-tracking network. The connection protocol options shall include Ethernet, HTTPS, or disk. Users may also access a read-only view of the entire tracking database through a system web browser.

· The system shall provide and automated function to create an export file of the searchable system data fields in industry common formats including XLS, PDF, HTML, and RTF.

· The system shall provide the capability to see tracking and asset utilization for other campus networks, aggregated in a single central view. Users are capable of viewing tracking information for a specific campus, region or the entire enterprise, scaling up to 1M assets.

2.2.8. DMLSS Interface. The system shall provide a bi-directional interface that will be used to interface with the current PMI Defense Medical Logistics Standard Support (DMLSS) server. This interface with DMLSS shall conform to the architecture and conventions outlined by Defense Heath Services System (DHSS) and Joint Medical Logistics Functional Development Center (JLMLFDC). This interface is a key feature in the initial deployment of the PMI ATS system and will support the ongoing interoperability between the PMI and DHA MFT’s.

2.2.9. Information Assurance (IA). The contractor shall provide DIACAP formatted system security artifacts along with evidence of their Authority to Operate (ATO) and Authority to Connect (ATC) certification for the system.

2.2.10. System Installation and deployment. The contractor shall be responsible to provide all necessary personnel, products, materials and services required to deliver the system to each of the PMI sites. This includes converting the current PMITS data records into a format that prepares them for import into the new PMI ATS system. This process will include working with the JMLFDC to coordinate the migration protocols and processes that will ensure successful and complete transition to the new PMI ATS. This will include:

· Converting the PMITS 1.0.3.17 data records for importing into the PMI ATS Design PMITS to PMI ATS conversion process to include an import tool and schedule that ensures a full migration of the existing PMIRS data into the PMI Central Serve.

· Coordinate with Scott AFB Network Administration Discuss where the servers will be located, network requirements, and VPN or Administrator support requirements. Configure the PMI servers with OS, SQL, PMI ATS application software and converted PMITS data. STIG Servers, apply required IAVA VMS release findings, ship, unpack and install on site, configure and connect, test, provide documentation and train.

· Coordinate with Individual Base/Service Network Administration Discuss where the individual ATS systems will be located, network requirements, and VPN or Administrator support requirements. Configure the ATS system with OS, SQL, PMI ATS application software and converted PMITS data. STIG Servers, apply required IAVA VMS release findings, ship, unpack and install on site, configure and connect, test, provide documentation and train.

· Onsite installation of the CONUS ANG/AFRC and Army / Navy Recycle Groups Coordinate PMI site sequence planning for Plexus updates: Schedule with local facilities for site visit. Prepare Plexus site laptops, RFID fixed readers and barcode/RFID hand held readers. Travel to site. On site laptop, RFID fixed reader and Hand Held installation. Inventory site Training on Plexus application and RFID tag association.

· Telephone installation of the OCONUS Active Duty and Theater Units Schedule with receiving facility: Prepare PMI ATS site laptop and barcode/RFID hand held readers. Ship prepared hardware to the site. Configure laptop and Hand Held installation over the telephone. Training on Plexus application and RFID tag association by telephone and webinar.

· Setup the DMLSS interface for ongoing data sharing Coordinate the DMLSS system SME to setup the bi-directional interface between the PMI ATS system and DMLSS. This shall include the data outlined by the DHSS AIT interface control documentation. The interface shall be set to an exchange frequency of up to four times every 24 hours. This exchange shall allow the current location information captured in PMI ATS to be delivered back to DMLSS.

The system installation delivery will begin within 60 days after the contract award. The following tasks have been organized in a sequence designed to support the migration from the existing system the new PMI ATS platform.

2.3 SPECIFIC TASK/CLINS

2.3.1. CLIN 0001 “Scott AFB, IL deployment sector“

PMI Central Server

HQ AMC/SG PMI Center, HQ AMC/SGXM , PMI Mgmt

375 MDG MERC

375th AES, 932nd AES

775th DET3

Total

2.3.2. CLINN 0002 “Ramstein AB, GE deployment sector“

Ramstein PMI Center

86th AES

86h CASF

10th EAES

Landstuhl ARMC

Total

2.3.3 CLIN 0003 “Travis AFB, CA deployment sector“

Travis PMI Center, 775th DET2, 60th ASF, 349th AES

Total

2.3.4. CLINN 0004 “Andrews AFB, MD deployment sector“

Andrews PMI Center, 779th ASF, 775th DET 1, Belvoir Community Hospital

Walter Reed National Military Medical Center

Total

2.3.5. CLINN 0005 “PACF deployment sector“

Kadena PMI Center, Yokota PMI Center, 018th DET 1, 018th AES Okinawa, 051st MDG Osan, Total

Site #26

Site #27

Site #28

Site #29

Site #30

Site #31

Site #32

Total

2.3.7. CLINN 0007 “CONUS ANG/AFRC and Army / Navy Recycle Group”

Site #33

Site #34

Site #35

Site #36

Site #37

Site #38

Site #39

Total

2.3.8. CLINN 0008 “CONUS ANG/AFRC and Army / Navy Recycle Group”

Site #40

Site #41

Site #42

Site #43

Site #44

Site #50

Site #51

Total

2.3.9. CLINN 0009 “CONUS ANG/AFRC and Army / Navy Recycle Group”

Site #52

Site #53

Site #54

Site #55

Site #56

Site #57

Site #58

Total

2.3.10. CLINN 0010 “CONUS ANG/AFRC and Army / Navy Recycle Group”

Site #59

Site #60

Site #62

Site #63

Site #64

Site #65

Site #66

Total

2.3.11. CLINN 0011 “OCONUS Active Duty and Theater Units”

Site #67

Site #68

Site #69

Site #70

Site #71

Site #72

Site #73

Site #74

Site #75

Site #76

Site #77

Site #78

Site #79

Site #80

Site #81

Site #82

Site #83

Site #84

Site #85

Site #86

Site #87

Site #88

Site #89

Site #90

Total

Grand total

2.4. TASK

2.4.1. TASK 1. Work with Joint Medical Logistics Functional Deployment Center (JMLFDC) Assist JMLFDC with bi-directional interface control between JMAR and the Electronic Health Record/Patient Movement Request.

2.4.2. TASK 2. Customer Training and Documentation

The Contractor shall provide at least two (2) user manuals and two (2) operator manuals per PMITS location for all hardware and software components, regardless of original equipment manufacturer (OEM). The Contractor shall provide updated documentation for all system components throughout the lifecycle of the system.

The contractor shall provide initial on-site/webinar classroom-based training based on location asset size, to include all necessary student-training materials. The total number of users to be trained at each level of training will vary by CLINN.

The contractor shall provide on-site/Webinar classroom-based “general user” training based on location asset size, and shall include at least the following knowledge areas: end-user software client operation to include launching the application, application navigation, and step-by-step procedures for how to perform queries, application capabilities, and application functions. A knowledge check shall be conducted at the conclusion of the training to ensure knowledge retention.

The contractor shall provide additional on-site classroom-based “super user” training. This “super-user” training shall include at least the following knowledge areas of concentration: Application and database set-up, application and database configuration, user account setup, operation and maintenance. A knowledge check shall be conducted at the conclusion of the training to ensure knowledge retention.

The contractor shall provide site classroom-based “maintenance-level” training. This “maintenance level” training shall include at least the following knowledge areas of concentration: Detailed, step-by-step procedures for all service tools, diagnostic software, and technical documentation necessary to service the system. A knowledge check shall be conducted at the conclusion of the training to ensure knowledge retention.

The contractor will provide to all personnel a “Certificate of Training” at the completion of each level of training, web, media- based or classroom.

2.4.3. TASK 3. Maintenance Support

The contractor shall warranty all equipment and provide ongoing technical support and any required maintenance for a period of 1 year after government acceptance of the operational PMI ATS

2.4.4. TASK 4. Helpdesk Requirements

The Contractor shall provide the necessary support and resources to operate customer support functions to include, but not limited to, help-desk facilities, dial-up access to provide information, tools, techniques and procedures to assist information systems users at all levels, automated support for management of the customer service function, problem reporting and resolution of customer problems, and support to new and existing customer information and support centers.

The Contractor shall respond to and resolve PMI ATS trouble tickets. The Contractor shall provide personnel to respond to the PMI ATS facilities during the normal government workweek of Monday through Friday within the hours of 0730 – 1630 within two hours of notification. The Contractor will provide after duty hours on-call technical support.

The Contractor shall respond to customer issues within 5 hours of notification. Issues identified as Priority issues will be resolved within 2 days unless approved or required otherwise by COR. Routine issues will be resolved within 5 days unless approved or required otherwise by the COR. Hardware maintenance beyond the 1 year warranty period will be provided by the help desk using a pool of government furnished equipment (GFE) to ‘Swap-out” items requiring maintenance.

3.0. QUALITY

3.1. Quality Control. The Contractor shall establish and maintain a complete Quality Control Plan to ensure the requirements of this contract are provided as specified in accordance with the applicable Inspection of Services Clause. The Contracting Officer (CO) will notify the contractor of acceptance or required modifications to the plan. The contractor shall make appropriate modifications (at no additional costs to the government) and obtain acceptance of the plan by the CO. The Government has the right to require revisions of the Quality Control Plan (at no cost to the Government) should the incorporated plan fail to control the quality of the services provided at any time during the contract performance. The plan shall include, but is not limited to the following:

· A description of the inspection system covering all services listed

· The specification of inspection frequency

· The title of the individual(s) who shall perform the inspection and their organizational placement

· A description of the methods for identifying, correcting, and preventing defects in the quality of service performed before the level becomes unacceptable

3.2. Quality Assurance. The Government will perform periodic reviews of the contractor’s performance in accordance with the Government’s Quality Assurance Surveillance Plan (QASP) and the Service Delivery Summary (SDS). The Government reserves the right to review services to be provided to determine conformance with performance and technical requirements. Government quality assurance will be conducted on behalf of the CO. The General Services Administration (GSA) Contractor Officer Representative (COR) will be appointed to coordinate the overall quality assurance of technical compliance.

3.3. Past Performance. The contractor shall specialize in delivering customized enterprise-level DoD Real Time Location Systems (RTLS) solutions. The contractor shall demonstrate expertise and knowledge associated with the Aeromedical Evacuation network and is capable of demonstrating specialized skills associated with the current PMI PMITS application and hardware. The contractor must also demonstrate a current and accurate knowledge of the DIACAP requirements.

3.4. Contractor Responsibilities. The contractor shall obtain all necessary licenses and/or permits required to perform this work. He/she shall take all reasonable precautions necessary to protect persons and property from injury or damage during the performance of this contract. He/she shall be responsible for any injury to himself/herself, his/her employees, as well as for any damage to personal or public property that occurs during the performance of this contract that is caused by his/her employees fault or negligence, and shall maintain personal liability and property damage insurance having coverage for a limit as required by the laws of the State of in which the work is being conducted. Further, it is agreed that any negligence of the Government, its officers, agents, servants and employees, shall not be the responsibility of the contractor hereunder with the regard to any claims, loss, damage, injury, and liability resulting there from.

4.0. DELIVERABLES

4.1 Monthly Status Report. Monthly status reports shall include status of work, schedules, deliverables, current and cumulative task funding status (direct labor and travel funding status to be reported separately as required), risks and risk mitigation techniques, outstanding issues, and proposed resolution approaches and actions to resolve any outstanding issues. The report shall identify milestones and deliverables completed and progress towards major milestones and deliverables. The report shall identify activities and deliverables planned but not completed including the government acknowledgement and approval of the incomplete work. The monthly status report shall be submitted simultaneously with the monthly invoice.

4.2. Program Management Review. The contractor shall schedule, facilitate, and document a Program Management Review (PMR) each quarter with the HQ AMC/SG management for the duration of the contract. The PMR shall be a forum to review task progress, determine additional areas for inclusion, and adjust project resources and milestones based on current progress, new guidance, or policy.

4.3. Meetings, Briefings, etc.: The contractor shall prepare meeting minutes, briefings, background papers, bottom line electronic mail, and other correspondence. Briefing and/or supporting documentation will be delivered on time and in accordance with Government point of contact guidance. The contractors shall participate in meetings, video-teleconferences, web-based collaboration events, working groups, and briefings providing technical support and policy subject matter expertise.

4.4. Deliverable Rights. All test materials, documents, notes, records, software tools acquired, and/or software produced by the contractor under this PWS shall become the property of the U.S. Government, which shall have unlimited rights to all materials and determine the scope of publication and distribution. The contractor shall be required to deliver electronic copies of all documents, notes, records and software to the Government quarterly and upon termination of the contract services or expiration of the contract period.

5.0 PERFORMANCE.

5.1. Work is to be accomplished through the GSA Federal Acquisition Service (FAS), Great Lakes Region 5, through its contract with the selected contractor. Certification by the Government of satisfactory services provided is contingent upon the contractor performing in accordance with the terms and conditions of the referenced contract, this document, the approved technical and price quotes, and all amendments. The client's representative, GSA's representatives, and the contractor's representative(s) shall meet when deemed necessary at the client’s request. The client representative, the GSA representatives, and the contractor’s representative may meet at the place determined by the client representative and GSA representatives.

5.2 Kickoff Meeting. The Contractor shall initiate work on this task order by meeting with GSA CO and key client agency representatives to ensure a common understanding of the requirements, expectations, and ultimate end products. The contractor shall discuss the overall understanding of the project and review the background information and materials provided by the client. Discussions will also include the scope of work, deliverables to be produced, how the efforts will be organized and project conducted; assumptions made/expected and results. A concerted effort shall be made to gain a thorough understanding of the client agency expectations. However, nothing discussed in this or in any subsequent meetings or discussions between the client and the Contractor shall be construed as adding, deleting, or modifying any task order requirements, including deliverable specifications and due dates.

5.3 Period of Performance. The base year will be 12 months with 4 twelve month option years. The period of performance for this requirement is estimated as follows. The performance dates identified are an estimate and the base year may have a different start date. The performance will start on or before September 30, 2014.

5.4. CLIN 0012 –Reserved for Travel. Travel will be handled, to include the reimbursement of expenses, in accordance with the terms and conditions of the contract and the Joint Travel Regulation guidance. All non-local travel arrangements will be the responsibility of the contractor including, but not limited to, airline, hotel, and rental car reservations. The contractor should make all efforts to schedule travel far enough in advances to take advantage of reduced airfares. The contractor shall stay in Government furnished lodging as available.

5.5. Transition/Phase-in Period. The initial period of performance includes a phase-in period not to exceed 30 days after contract start. A joint inventory of all GFE will be accomplished NLT 10 calendar days after contract start. Not later than 30 days after contract start, the Government will make available all relevant information developed or collected throughout the previous contract(s) to the contractor. At or before conclusion of the phase-in period, the contractor shall assume all responsibility for all areas of operation in the PWS.

5.6. Key Personnel. The contractor shall ensure key personnel are staffed and available for performance immediately at contract start. Remaining contractor personnel shall be fully staffed and capable of assuming responsibility for all areas of the operation of the PWS no later than the end of the 30-day phase-in period.

5.7. Phase-out Period. The phase-out period begins thirty days (30) prior to the end of the contract. Within 30 days of the end of the contract, the incumbent contractor shall provide all information developed or collected throughout the contract to the Government.

6.0 GOVERNMENT FURNISHED PROPERTY AND SERVICES. Except for those items specifically stated in paragraph 3 as government-furnished, the contractor shall furnish everything needed to perform this contract.

7.0. SECURITY.

7.1. Physical Security: The physical security section is applicable only to personnel performing work on a DoD installation.

7.1.1 Antiterrorism Training. Contractor personnel shall attend annual Antiterrorism Level I training IAW DoD Instruction 2000.16. Training will be provided by the Government via computer-based training or by briefing conducted by a qualified instructor

7.2. Proper Credentials. The contractors shall ensure their employees are those of their subcontracts have the proper credentials allowing them to work in the applicable country. Persons found to be undocumented or illegal aliens shall be remanded to the proper authorities.

7.3 Clearance. Contract personnel may be required to use classified data management systems to perform functional tasks with AMC/SGX. The Contractor shall comply with DD Form 254, Contract Security Classification Specification, attached to this contract. The Contractor may propose personnel with interim clearances as long as the clearance is finalized within thirty days (30) of contract award. Assigned contract personnel will not have any open JPAS issues /comments prior to working PWS tasks. In the performance of tasks the Contractor shall require access to a broad range of documents to include applicable directives and regulations, classified war mobilization plans and related documents up to and including SECRET. As such, Contractors shall have at a minimum a SECRET clearance as promulgated by the DoD. Contractor shall safeguard classified material in accordance with applicable DoD and Air Force directives. The Government will provide security classification guidance to assigned personnel. The Contractor shall be responsible for creating, maintaining, and disposing of only those Government records that are required in support of contract tasks.

7.3.1 Contractor Consent to Background Checks. Contractor shall not employ persons to perform under this contract if such employee is deemed or identified by Scott AFB as a potential threat to the health, safety, security, general well-being or operational mission of the installation and its population, nor shall contractor or subcontractor employ persons under this contract who have an outstanding criminal warrant as identified by Law Enforcement Agency Data System (LEADS) through the National Crime Information Center. LEADS checks will verify if a person is wanted by local, state, and federal agencies. All contractor and subcontractor personnel must consent to LEADS background checks. Contractor and subcontractor personnel who do not consent to LEADS check will be denied access to the installation. Information required to conduct a LEADS check includes: full name, driver’s license number, and/or social security number, date of birth of the person entering the installation, and completion of a background check questionnaire. Contractor must have this information ready to provide to the Scott Visitor Control Center, if requested.

Contractor must ensure their employees and those of their subcontractors have the proper credentials allowing them to work in the United States. Persons later found to be undocumented or illegal aliens will be remanded to the proper authorities.

7.4. Badges. Contractor is required to provide identification badges for their employees. All contractor personnel must wear these badges while on duty on government site. Badges are required to identify the individual, company name, and be clearly and distinctly marked as contractor. Contractor’s identification badge will not be used as an entry requirement for installation entry or into any government designated controlled or restricted area.

7.4.1. Contractor Registration of Vehicles on USAF Installations. All contractor or contractor employees’ vehicles used in the performance of this contract shall comply with all local, state and federal regulations; and will comply with all installation registration requirements. If a base vehicle pass is issued, it shall be surrendered to Security Forces upon demand or at the end of the contract period.

7.4.2 Access to Installation During Force Protection Conditions (FPCONs). Access to Installation During Force Protection Conditions (FPCONs). Contractor will be assigned a mission essential designation IAW requirements contained in SAFB Integrated Defense and Antiterrorism Plans. Only the installation commander or the unit commander requesting contract support will assign the mission essential designation.

7.5. Property Protection. Property protection for the facility where contractor’s primary work center is located will be the responsibility of the local facility manager and local government Security Manager, or their duly authorized representative IAW AFI 31-101, Integrated Defense, and command/local directives. Contractor must safeguard all government-owned equipment and materials in his/her possession or use.

Contractor Working in Controlled or Restricted Areas: In the unlikely event that a contractor requires access to the controlled or restricted area and does not have the proper security clearance, government will ensure escort(s) are provided for contractor at all times when within a controlled or restricted area. Contractor must have an issued AF Form 1199 and work on base a minimum of four days a week (must have an assigned workspace on base). Contractor is only allowed to escort visitors from the same company for which he/she works, and all visits must be for official business. In addition, contractor must fulfill, maintain, and comply with all security requirements IAW Integrated Defense and command/local directives.

Access to Government Facilities with Controlled or Restricted Areas: Contractor shall comply with security regulations imposed by the installation commander and/or the agency responsible for the project location. Due to specific mission requirements inherent in the nature of controlled or restricted areas on Scott AFB, government may direct contractor to leave the controlled or restricted areas at any given time.

Access to Government Facilities with Controlled or Restricted Areas for Replacement Contractor: The following scenario (i.e., replacement contractor with an inadequate security clearance) is abnormal. Government will ensure replacement contractors not initially possessing the proper clearances and requiring entry to controlled or restricted areas are escorted continuously. Replacement contractor must submit paperwork within seven days of being assigned to obtain an approved security clearance or favorable review. Replacement contractor personnel must obtain a security clearance prior to working with, or having direct access to, classified material. In addition, replacement contractor personnel must obtain a “favorable review” prior to having access to a Controlled Area. The above information must be submitted to 375 SFS/S5 or as directed by government.

7.6. Safeguarding Unclassified and/or For Official Use Only (FOUO) Information. The Contractor shall meet Air Force standards for storing, processing, and handling unclassified and/or Sensitive but Unclassified (SBU) information and systems. Additionally, all resources (e.g. publication/instructions) provided by the government to assist the Contractor in the performance of their contract shall be surrendered upon termination of employment or the end of the contract performance period.

7.7. Trustworthiness Determination – National Agency Check – Industrial Security Management Positions of trust require a favorable National Agency Check (NAC). Per Air Force Manual 33-282, the Contractors/instructors accessing a government network must, at a minimum, have a completed and favorable NAC. In accordance with AFI 31-601, when Contractors require unescorted entry to restricted areas, access to sensitive unclassified information, access to Government Automated Information Systems and/or sensitive equipment, not involving access to classified information, the Contractor’s personnel security questionnaire is processed by the sponsoring Air Force activity per DoD 5200.2-R and AFI 31-501.

7.8. Security Program and Command/Local Directives. The Contractor shall safeguard all Government-owned equipment and materials in his/her possession or use. The Contractor shall meet Air Force standards for storing, processing and handling classified information and systems.