Solicitation_PTL_System_A004.docx

Solicitation No. S-AQMMA-12-R-0413 A004 Personnel Tracking Locator Department of State

TABLE OF CONTENTS

iii Section B – SUPPLIES OR SERVICES AND PRICES/COSTS

B.1 SERVICES

The Contractor shall provide the equipment and services in accordance with Section C, and the attachments.

B.2 TYPE OF CONTRACT

The Government contemplates single award of a stand-alone, hybrid contract resulting from this solicitation. Contract types will be firm-fixed-price for CLINS X001 through X007, and labor hour or time-and-materials for CLIN X008.

B.3 PAYMENT, CEILING, AND WITHHOLDING

The Government will pay the Contractor the unit prices specified in this section. The Government shall impose a deduction from the amount of payment for each instance of unacceptable performance or non-performance in accordance with Attachment 1, Quality Assurance and Surveillance Plan (QASP).

BASE YEAR

1,880

1,880

1,880

1,880

1,880

1,880

OPTION YEAR 1

1,880

1,880

1,880

1,880

1,880

1,880

OPTION YEAR 2

1,880

1,880

1,880

1,880

1,880

1,880

OPTION YEAR 3

1,880

1,880

1,880

1,880

1,880

1,880

OPTION YEAR 4

1,880

1,880

1,880

1,880

1,880

1,880

SECTION C – STATEMENT OF WORK (SOW)

C.1 INTRODUCTION

The Department of State (DOS), Bureau of Diplomatic Security (DS), Office of Security Technology (ST), Personnel Tracking and Locator Section, has a requirement for a Government owned, contractor operated enterprise personnel tracking system which can ingest the full spectrum of personnel tracking devices on the market currently and with the ability to ingest future next generation devices at minimal cost to the government for adaptation. The proposed system will replace the current nine year old system that supports Personnel Tracking and Locating (PTL) operations both domestically and overseas.

C.2 BACKGROUND

DS is responsible for deployment of technical security systems that reduce risk to government personnel and facilities. Specifically, the protection of government personnel traveling from the protected mission facility to their foreign counterpart’s office is of paramount importance in the execution of U.S. foreign policy.

C.3 MISSION

The PTL mission is to provide tracking and monitoring capabilities to USG personnel worldwide in support of foreign policy requirements.

C.4 CONTRACTUAL OVERVIEW

The Contractor shall provide three (3) complete redundant PTL Systems. The three systems shall be designated and utilized in the following capacities: 1) Production Server, 2) Back-up Server, and 3) Test Server (i.e., (Gold Standard) verification, certification and authorization (C&A)).

The PTL Systems shall employ state-of-the-art hardware and software technologies to provide the capability to monitor and ingest multiple device formats over varied transmission paths (i.e., worldwide cellular SMS messaging and data, and satellite based tracking devices). The PTL Systems shall aggregate the data collected and distribute it to various front end user systems, and provide a default display capability.

The PTL Systems shall be capable of ingesting data from currently deployed devices, which are PECOS-based, Iridium devices manufactured by NAL Research. The PTL system shall be device agnostic and capable of ingesting multiple other device types, as the government also desires to expand its device portfolio with commercial Iridium devices, Global Star based devices, and cellular devices, among others. Using task orders, the contractor shall integrate devices selected by the government into the PTL system when necessary. The contractor shall also be free to recommend new devices for integration if the devices use FIPS-approved encryption mechanisms.

The PTL Systems shall be fully redundant with intra-site hot failover, therefore in the event of a component failure the system shall automatically switch over to its backup component without the need for manual intervention.

The PTL services shall be based at designated Government locations inside the continental United States.

· Commercial-Off-The-Shelf (COTS) fully redundant turn-key system that satisfies the requirements enumerated below.

· Engineering and technical services to include system installation, operational validation of all system elements that support the PTL Systems operations, and associated data services.

· Operations maintenance, technical support, and sustainment services required to support a 24x7x365/6 DOS activities worldwide. The services shall ensure all software and hardware are functional and remain up-to-date.

· Contractor shall assume all costs associated with any required licensing or maintenance agreements.

C.5 PERSONNEL TRACKING LOCATOR (PTL) SYSTEMS

The DOS mission portfolio is comprised of a significant number of devices that are currently deployed worldwide. The PTL Systems shall be device agnostic and be capable of ingesting data from the tracking devices currently deployed, as well as new, FIPS-approved-encrypted devices using varied transmission paths. The PTL Systems shall be adaptable to allow for new device types and the integration of other transmission paths as necessary.

In order to leverage the existing DOS infrastructure and approved assets the PTL Systems shall provide compatibility with Oracle Version 11 with Oracle Advanced Security - Transparent Data Encryption (TDE).

In order to facilitate the DOS Certification and Accreditation (C&A) requirements, any solution proposed shall be able to document approval or accreditation by another entity of the federal Government. The PTL hardware shall be capable of being approved by the State Department Information Technology Change Control Board (ITCCB), See Attachment 5 for the current list of approved hardware and software.

C.5.1 Web Interface

The PTL Systems shall possess the following capabilities:

C.5.1.1 Facilitate the viewing of live track data, historical track data, emergency messages, track administration functions, user administrative functions, and data export functions through a unified, secured, and web interface.

C.5.1.2 Display live/historical tracks with the following device information for all ingested devices: device ID, alias/call-sign, last reported latitude/longitude, last reported track receive time, and emergency status. If the device provides speed, direction or brevity code then the web interface shall display that information as well.

C.5.1.3 Have the capability to export historical device data in CSV format to files.

C.5.1.4 Be able to create, retrieve, update, or delete brevity codes from capable trackers.

C.5.1.5 Record a “receive” timestamp with each received device update

C.5.1.6 Provide secure two-way messaging capability to trackers capable of receiving messages.

C.5.1.7 Provide users the capability to filter live/historical tracks individually or as part of a device group. Each user approved to do so shall be able to filter by device, device name/alias, date/time, or device group.

C.5.1.8 Use role-based access control for all functions and commands available to the government. Users shall be granted only the minimum necessary permissions to perform functions for any given device group. User administration functions shall be granted only to authorized administrators.

C.5.1.9 Provide a means to access all configuration settings through the same unified interface. These shall include all software and program settings except settings of the internal COTS products

C.5.1.10 Provide the capability to authorized administrators to assign a user separate permissions for each nested device group. These permissions include but are not limited to the ability to view or modify devices within the device group.

C.5.1.11 Provide system-wide notifications to all users upon software updates, maintenance cycles, or system-wide configuration changes.

C.5.1.12 Allow users to create nested device groups and to assign or reassign devices under the user’s control to any of the device groups under that user’s control.

C.5.1.13 Show only devices, functions, and configuration settings for which a user has authorization.

C.5.1.14 Allow users to remotely configure all capable trackers for which a user has permissions to modify. This configuration shall include remotely changing the reporting rate of each tracker.

C.5.1.15 Display an audible/visual emergency warning to the user in the event that a user-viewable device sends an emergency message to the system.

C.5.1.16 Provide an authorized user the ability to configure a Geofence for each user-viewable device. The user shall have the ability to configure whether the Geofence activates when a device enters the Geofence, exits the Geofence, or both.

C.5.1.17 Allow an authorized user the ability to define and edit multiple Geofences or zones for each user-viewable device (at least 10).

C.5.1.18 Be capable of importing a Geofence from file. When the Geofence for any device activates, the PTL System's web interface shall provide an audio and visual warning to those users with the viewing permissions for that device.

C.5.1.19 In an emergency, allow an authorized user to remotely activate the microphone of audio-capable trackers. The administrator shall have the capability to globally enable or disable this function. Contractor will define safeguards over how this feature will be controlled to ensure access to this feature will be limited to a restricted group of authorized users only, and track implementation of this feature in the audit logs.

C.5.1.20 Provide users the capability to filter live/historical tracks individually or as part of a device group. Each user shall be able to filter by device, device name/alias/call sign, date/time, or device group.

C.5.1.21 Provide an authorized user the ability to edit a user-modifiable tracker’s association data, including each tracker’s alias or call-sign.

C.5.1.22 Provide an authorized user the ability to edit emergency contact information for each user-viewable device.

C.5.1.23 In the event of an emergency, the PTL Systems shall send an emergency notification via e-mail to the configured emergency contact(s) associated with that device in the system.

C.5.1.24 Allow authorized users to manually deactivate an audible/visual emergency warning and geo-fence warnings.

C.5.1.25 Provide an authorized user the capability to export live tracking data and emergency messages via unencrypted UDP, unencrypted TCP, and HTTPS protocols to any other IP address and port. An authorized user shall be able to switch between export protocols at any time.

C.5.1.26 Provide a secure built-in web viewer that allows a user to see selected trackers as icons directly in the web application. Viewer shall allow the user to pan and zoom on the map.

C.5.1.27 Provide the user with the capability to disable the built-in viewer when necessary, in order to save bandwidth, or so that the user can use an external viewing application

C.5.1.28 Have the ability to zoom to a specified tracker, resolution less than or equal to 250m for geospatial imagery and street level for street maps.

C.5.1.29 Differentiate trackers within the display so that a user may distinguish between closely-spaced trackers.

C.5.1.30 Have the ability to zoom to a specified tracker, at street-level resolution, meaning streets must be distinctly identifiable, for both geospatial imagery and street maps.

C.5.1.31 Provide an authorized user the ability to configure a Geofence for a user-viewable device by highlighting the area directly on a map.

C.5.1.32 Provide a visual warning when a device enters or exits a Geo-fence.

C.5.1.33 Display the following device information when an icon is selected : device ID, device model, alias/call-sign, last reported latitude/longitude, last reported MGRS, last reported time, and emergency status. If a device provides speed, direction or brevity code then the web interface shall display that information as well.

C.5.2 Operator Display and Presentation

The PTL Systems shall:

C.5.2.1 Serve data to multiple external viewing applications. These applications include but are not limited to Google Earth, ESRI and FalconView.

C.5.2.2 Provide an external viewing application with the ability to display the following device information: device ID, device model, alias/call-sign, last reported latitude/longitude, last reported MGRS, last reported time, emergency status, and brevity code. If the external viewing application supports the ability to display speed and direction this also shall be provided to an external viewing application.

C.5.2.3 Provide and or develop the capability to integrate layers of geospatial data and overlay the data on a Google Earth Baseline.

C.5.3 System Monitoring

The PTL Systems shall provide security auditing and monitoring services, to include intrusion detection and firewall monitoring.

As deemed necessary by the government, the Contractor shall use network management software, another automated process, or a combination of the two to monitor the connection status and health of the externally-connected networks. These externally-connected networks include but are not limited to VPN's to other systems and incoming device transmission networks such as satellite ground stations.

C.5.4 Special Technical Requirements

The PTL Systems shall meet the following technical requirements:

C.5.4.1 Ingest multiple device formats over varied transmission paths, including but not limited to PECOS, Iridium, Global Star, and various 2G/3G/4G cellular networks via Short Message Service (SMS) and data.

C.5.4.2 Ingest, at a minimum, device ID, position, and elevation data from each tracker, and any brevity code. If the device provides it, the PTL Systems shall also ingest device send time, speed, and direction.

C.5.4.3 Provide the ability to ingest encrypted device data using FIPS-approved encryption algorithms where encryption is supported by the device.

C.5.4.4 Utilize an Application Programming Interface (API) for integration to third-party external viewing applications and systems. This API shall include at a minimum: retrieval of live or historical tracks by ID, Alias, Date, Device Group, or other filters, and retrieval of device metadata and geo-fences.

· The API shall be exposed through secured and encrypted services, be it web services, remote method invocation, or complete exposure of proprietary format to the government.

· All API methods shall be exposed, documented, and provided to the government. All API methods and documentation shall be accessible without requiring proprietary software or a license.

C.5.4.5 Provide secure two-way messaging capability to trackers capable of receiving messages.

C.5.4.6 Record a “receive” timestamp with each received device update.

C.5.4.7 Provide the ability to import and export real-time data in the JBFSA format (Versions 1.0, 1.0a, 2.3 and FFT 2.4). The contractor shall update this capability for forward compatibility as required.

C.5.4.8 The production server shall consist of performance languages, either compiled or JIT-compiled, suitable to an enterprise environment.

C.5.4.9 The PTL shall have the ability to store all tracking data for a minimum of two (2) years.

C.5.4.10 (OPTIONAL) Provide the capability to export live track data and emergency messages in real-time through a one-way guard.

C.6 INSTALLATION AND DEPLOYMENT SERVICES

The Contactor shall be responsible for the installation of the PTL systems in a dedicated Government facility. The Contractor shall provide a comprehensive test plan that will be used to verify the full design functionality and operational readiness of the PTL system once installed. The Contractor shall provide the test plan to the COR for review. Installation shall including the following:

· Pre-configuring and installing software.

· Connecting the PTL systems to the Government provided communication and internet.

· Installing the PTL systems, including web servers, database servers, Open Street/Open Topo map servers, and peripheral equipment.

· Documenting the entire system architecture and Standard Operating Procedures (SOPs). The SOP will serve as a living document outlining daily operations procedures, and coordination with the DS point-of-contact (POC) for emergency events and technical support.

· Performing system testing and verification to ensure the operational readiness of the system and the full function of fail-over mechanisms.

C.6.1 Pre-Deployment Tasks

The Contractor shall participate in pre-deployment planning prior to operations as directed by the Contracting Officer Representative (COR). These activities typically include providing engineering support and technical data. All Contractor specific terminology inherent to the system shall be documented and defined using industry accepted definitions.

The DOS shall perform acceptance testing prior to deployment of the PTL Systems.

C.7 OPERATION, MAINTENANCE AND SUSTAINMENT SERVICES

The Contractor shall provide Tier 1 maintenance support for the three (3) PTL servers and software applications. Tier 1 supports includes responding to questions regarding the PTL application, assisting with user creation, and device management Operations maintenance, technical support, and sustainment services required to support a 24x7x365/6 DOS activities worldwide. The services shall ensure all software and hardware are functional and remain up-to-date.

When a service call is placed the Contractor shall acknowledge receipt of that call within thirty minutes and be on-site during normal DOS business hours and outside of normal business hours in accordance with the priority levels enumerated in the table below. Normal business hours are defined as 07:30 am to 4:30 pm EST, Monday through Friday including all designated federal holidays. The Contractor shall employ a trouble ticket system for logging, tracking, and retaining the history of all service calls.

The Contractor shall perform the following maintenance tasks in support of the PTL program:

· Monitor and maintain comprehensive awareness of system health and status.

· Performing routine and preventative maintenance of all hardware associated with the PTL system consistent with reasonable commercial practices for systems of its type.

· Update all software and operating system versions, security patches, software upgrades and patches; hardware fixes and upgrades; virus signatures, and other maintenance activities for software components used in the PTL system.

· Adhere to the Contingency Plan (i.e., included in the Quality Control Plan), and the defined response protocols, and systematic procedural checklists for rapidly assessing and resolving problems.

C.7.1 Scheduled System Outages

The Contractor shall provide a written notice to the COR one (1) week in advance of all planned or required system maintenance activities that require a PTL systems outage. The Contractor shall ensure that planned system outages do not conflict with critical DOS activities or are performed during times when there is a traditional high level of user activity. The Contractor shall provide the required Incident Report within 24 hours for schedule outage.

C.7.2 Unscheduled System Outages

In the event of an unplanned outage, or component failure the Contractor. upon arriving on-site, shall immediately ensure that the systems automatically switched over to the redundant backup system and the failure is transparent to the end-users. The Contractor shall then assess the extent and cause for the outage and provide an estimated time to restore the failed system to full operation. The Contractor shall provide the required Incident Report within 15 minutes of unscheduled outage.

C.7.3 Development Cycles and Modernization Updates (Critical Gap)

The Contractor shall provide regular development cycles. These cycles shall include bug-fixes, software/server patches, implementation of future (minor) core requirements, and future (minor) built-in web viewer requirements and shall occur at least every 90 days or sooner if deemed necessary by the COR. Updates shall also include modernization updates as part of the regular development cycles. These modernization updates shall include updating the PTL Systems and built-in web viewer such that it can be viewed properly in DOS-approved web browsers. Updates shall be tested on the Test Server in a test domain prior to updating the Production Server. As part of the update package, Contractor shall provide documentation and technical support 60 days in advance of the anticipated change to meet DOS configuration change management requirements and obtain approval for the change.

C.7.4 System Administration

The Contractor shall provide all database, network, and underlying system administration and configuration services. Daily administration of the system by the government shall be restricted to user management and device administration to include, tracking device management, device communications, and device dissemination for regions of interest.

C.8 ENGINEERING AND TECHNICAL SUPPORT

The Contractor shall assist the DOS in immediately achieving security authorization and certification under NIST 800-37 and 800-53 at the “Medium” level and eventually move the system to the “High” level as required by DOS/IRM.

C.8.1 Software or Architecture Modifications

The PTL Systems consists of COTS products that will act as the server for tracking and locating personnel in regions of interest worldwide. Given that the system consists of COTS products, accredited for other federal agencies, certain modifications to system software and or architecture may be required to finalize DS security standards and information systems accreditations and related C&A testing requirements. The Contractor's support for software and architecture modifications shall be provided through the task order process. See H.9.

C.8.2 Certification and Accreditation (C&A)

The Contractor shall be required to support the DOS C&A process for both the initial PTL systems and for any re-certifications (i.e., entire system or individual elements) resulting from future system updates, upgrades, or modifications.

The PTL Systems shall be capable of immediately obtaining a DOS certification and accreditation (C&A) at a “Medium” level as demonstrated through previous federal certifications and authority to operate. Examples include the Department of Defense DIACAP processes.

The Contractor may be required to assist the DOS in meeting the information assurance requirements at the high level for confidentiality, integrity and availability as defined by the National Institute of Standards and Technology.

The Contractor shall assist in the planning and preparation for the security C&A as part of DOS FIPS 200 and FISMA implementation effort. In coordination with PTL and the DS Chief Technology Officer (CTO), the Contractor shall make changes to ensure that the application can immediately meet security requirements for a ”Medium” system as documented in the National Institute of Standards and Technology, to include but not limited to those specified within NIST Special Publications 800-37 and 800-53. Contractor will coordinate and create any additional security certification and accreditation documentation for the application/solution and assist with any testing requirements.

The Contractor shall provide certification documentation as required above, to meet current NIST requirements for a system categorized as ”medium” for confidentiality, integrity and availability and be prepared to move the system to “High” once directed by the government.

The Contractor shall provide both electronic and hardcopy copies of the documentation that identifies the standards-compliant Application Programming Interface (API) for integration to third-party external viewing applications and systems.

Any modifications in order to meet NIST 800-37 and 800-53 at the “Medium” level shall be identified and submitted for approval to the COR. DS shall not incur costs for complete system redesigns in order to obtain the initial necessary authority to operate tracking system at the system categorization level determined by DOS.

The Contractor shall comply with the following standards in support of this SOW and incorporate them into proposed solution:

a. Comply industry standard quality management practices

b. Comply with AIS Security standards

c. Comply with DOS Standards and Procedures – including all Foreign Affairs Manual (FAM), Department of Defense Acquisition Regulations (DOSARS), and Foreign Affairs Handbook (FAH)

The re-certification support will be an ongoing process to include periodic system updates, upgrades, and modifications that may occur in the life cycle operations of the server. This support includes the following.

· Attending meetings with DS security specialists and those supporting the C&A efforts.

· Identifying protocols that support the C&A efforts.

· Identifying and providing supporting documentation.

· Identifying a security architecture needed to meet C&A requirements for protecting, auditing, and validating safeguards.

The Contractor's support for the new PTL systems C&A and future system re-certifications shall be provided through the task order process. See H.9.

C.8.3 Device Integration

The PTL system shall be device agnostic and capable of ingesting tracking data from multiple device types to expand The DOS tracking device data compatibility portfolio includes commercial interfaces for Iridium devices, Global Star based devices, and cellular devices. The Contractor shall also be free to recommend new devices for integration if the devices use FIPS-approved encryption mechanisms.

The Contractor shall support the PTL systems capability to permit the import of data of future device data into the system using a plug-in architecture. The Contractor shall be required to fully integrate new device data into the PTL system and provide a common operating picture for all deployed devices. The Contractor's support for future device integration shall be provided through the task order process. See H.9.

C.9 TRAINING

The Contractor shall provide initial and advanced user training sessions upon twenty-four (24) hour notice from the COR. The sessions shall be conducted for DOS PTL System operators.

C.9.1 Initial User Training

The objective for the initial user training sessions shall be provided to give DOS operators a solid working knowledge and a practical understanding of how to use the PTL Systems interface and functions. The initial user training sessions shall be twenty-four (24) hours in duration (i.e., three days). Following the completion of the sessions the participants shall possess:

· Working knowledge of the capabilities and limitations of the PTL Systems and servers.

· Working knowledge of the systems data flow.

· Basic understanding of the system administration steps and requirements.

· Working knowledge of system operations, including all facets of web interfaces.

· Working knowledge of associated device configuration

· Working knowledge of data monitoring.

· Working knowledge of output monitoring.

· Basic understanding of system troubleshooting, including; associated device troubleshooting, the interpretation of system faults and problem resolution.

C.9.2 Advanced User Training

The objective for the initial user training sessions shall be to give DOS operators a solid working knowledge and a practical understanding of how to use the PTL Systems interface and functions. The advanced user training sessions shall be sixteen (16) hours in duration, (i.e., 2 days). Following the completion of the sessions the participants shall possess:

· Proficient knowledge of the capabilities and limitations of the PTL Systems.

· Proficient knowledge of the systems data flow.

· Proficient understanding of the system administration steps and requirements.

· Proficient knowledge of system operations, including all facets of web interfaces.

· Proficient knowledge of associated device configuration

· Proficient knowledge of data monitoring.

· Proficient knowledge of output monitoring.

· Proficient understanding of system troubleshooting, including; associated device troubleshooting, the interpretation of system faults and problem resolution.

C.9.3 Training Plan

The Contractor shall provide a training plan which addresses how to deploy upgrades and ensure cultural adaptation should any changes be necessary to the user interface. The Contractor shall present the proposed format and outline of the training sessions for COR approval

C.10 DOCUMENTATION

C.10.1 Deployment Plan

The Contractor shall provide a Deployment Plan and Project Life Cycle that will be used in the implementation of the tracking program. Both shall include for each phase, the description of activities to take place, a schedule demonstrating any dependencies, control gates, and milestones.

C.10.2 Configuration Management Plan (CMP)

The Contractor shall provide a CMP which will incorporate a configuration control board which includes the COR, contractor, PTL staff and other constituencies invited by PTL. The document will describe how the Contractor plans to maintain document and software baselines in coordination with the COR, plan subsequent development cycles and delivery, and provide suggested revisions to the PTL Systems. The Contractor shall present the proposed format and outline of the plan for COR approval.

C.10.3 Quality Control Plan (QCP)

The Contractor shall provide a QCP which describes how the contractor will maintain control over the quality of the Contractor processes. The QCP shall include a Contingency Plan, that delineates defined response protocols, and systematic procedural checklists for rapidly assessing and resolving problems. The plan shall include corrective action procedures when deficiencies or insufficient performance are identified.

The Contractor shall adhere to the QCP in a manner that ensures that the highest levels of performance are utilized under this contract. The Contractor’s QCP shall emphasize prevention over detection and ensure that all aspects of service are performed in accordance with the terms of this contract. The Contractor will be responsible for monitoring contract performance and customer satisfaction and make necessary updates to the QCP when issues arise or when instructed by the COR. The Contractor shall comply with all applicable current and future laws, directives, and policies including the following:

· Foreign Affairs Handbooks (FAH)

· Foreign Affairs Manual (FAM)

· Department of State Standardized Regulations (DSSR)

· National Electric Code (NEC)

· International Building Code (IBC)

· Computer-Aided Design (CAD) Standards

· Security Classifications E.O. 13526

· Federal Travel Regulation (FTR)

· Freedom of Information Act (FOIA) – Title 5 U.S.C. Section 552)

· Privacy Act (5 U.S.C. § 552a)

· Uniform Federal Accessibility Standards (UFAS)

· Security Health Environmental Management (SHEM)

· Security Classification Guide for the Design and Construction of Overseas Facilities

The Contractor shall provide monthly status reports addressing activities, observations and recommendations. This will be a written report that will address the activities and findings of the prior month. This report will be designed to provide the GTM a comprehensive understanding of where the Contractor is in the project plan, any issues that have arisen, proposed solutions with a cost benefit analysis of those solutions, and a report on any issues from the previous month that needed to be updated.

C.10.4 Usage Reporting

The PTL Systems shall provide reporting to include air time usage, last device report date and geo-location. Reports shall be customizable to include trackers by device ID or trackers by device group.

C.10.5 Monthly Status Report

Provide a monthly status report of the time of tracks received for all ingested tracker devices.

C.10.6 Situation and Incident Reporting

The Contractor shall submit situation and incident reports:

1. An Incident Report shall be provided within fifteen (15) minutes of any unscheduled outage and within twenty-four (24) hours prior to a scheduled outage.

2. The Incident Report format shall be the responsibility of the Contractor and will be approved by the COR or designee prior to initiation of PTL System operations.

C.10.7 System Design Documentation

The Contractor shall provide systems design documentation describing complete system architecture and full accreditation boundary. The documentation shall include, the PTL Systems, networking equipment, inter-connections, redundancy and failover design, software language(s) used; and all methods/means by which servers, network, and software are secured.

C.11 TRANSITION PLAN

The Contractor shall perform in accordance with the Preliminary Transition Plan. The transition period shall not exceed ninety (90) calendar days. Full performance shall commence following the end of the transition period provided the PTL Systems have been granted DOS authority to operate.

The Contractor shall submit a Final Transition Plan reflecting any revisions or changes to the Preliminary Transition Plan within ten (10) calendar days of receiving the Notice of Contract Award. Any proposed revisions to the Contractors Preliminary Transition Plan shall not result in an increase in the allotted ninety (90) day transition timeframe. The COR will review any changes to the Preliminary Transition Plan within 10 calendar days of receipt.

C.11.1 Phase-in Performance

The Contractor shall assume full responsibility for an orderly phase-in of operations. During the Transition Period the Contractor shall:

· Provide the Installation and Deployment Comprehensive Test Plan

· conduct the required user training

· install and test the PTL Systems

· acquire the necessary levels of insurance

· participate in a preliminary joint inventory of all Government Furnished Property

C.11.2 Phase-Out Performance

At the end of the contract a follow-on competition shall be conducted by the CO. In the event the current Contractor is not awarded the follow-on contract the Contractor shall, within 30 calendar days of notice by the CO, develop a Phase-Out Plan for the orderly transition of the operations. The Contractor phase-out procedures shall not disrupt or adversely affect the day-to-day operations and shall result in a smooth and orderly transfer.

SECTION D – packaging and marking

D.1 MARKING OF REPORTS

All reports delivered by the Contractor to the Government under this contract shall prominently show on the cover of the report:

(a) Name and Business address of the Contractor;

(b) Contract number and delivery order number, if applicable;

(c) Date of report; and

(d) Program office(s).

D.2 PACKING LIST(S)

A packing list or other suitable shipping document shall accompany each delivery and shall include the following information:

(a) Name and address of consignor;

(b) Name and address of consignee;

(c) Government contract number:

(d) Government bill of lading number covering the shipment, if any; and

(e) Description of the items shipped, including item number, quantity, number of containers, and package number, if any.

D.3 WARRANTY NOTIFICATION

In accordance with FAR 46.706 (b)(5), the Contractor shall stamp or mark the supplies delivered, or otherwise furnish notice with the supplies, of the existence of a warranty, if any. Sufficient information shall be presented duration of the warranty and the name and telephone number of the Contracting Officer to be notified if the supplies are found to be defective.

Solicitation No. S-AQMMA-12-R-0413 A004 Personnel Tracking Locator

SECTION E – INSPECTION AND ACCEPTANCE

E.1 CLAUSES INCORPORATED BY REFERENCE FAR 52.2522 (FEB 1998)

This contract incorporates the following clauses by reference, with the same force and effect as if they were given in full text. Upon request, the CO will make their full text available.

http://www.acquisition.gov or http://farsite.hill.af.mil/

These addresses are subject to change. If the Federal Acquisition Regulation (FAR) is not available at the locations indicated above, use the Dept. of State Acquisition Website at http://www.statebuy.state.gov.

E.2 SCOPE OF WORK AND ACCEPTANCE

Final inspection and acceptance of the PTL Server shall be carried out in accordance with a structured test and acceptance plan approved by the COR, prior to delivery to DOS. Unless otherwise agreed, the Contractor and DOS shall jointly carry out and complete the acceptance activities and the result shall be accounted for in reports designed to clearly document whether the acceptance criteria are met or not. Acceptance of the system shall not be refused because of minor deviations.

If the Contractor at any time has reason to believe that a delivery or performance undertaken in this contract will be delayed, it shall promptly notify DOS and shall subsequently define in writing the estimated period of delay and the estimated new date of delivery or performance.

SECTION F – DELIVERIES OR PERFORMANCE

F.1 CLAUSES INCORPORATED BY REFERENCE FAR 52.2522 (FEB 1998)

This contract incorporates the following clauses by reference, with the same force and effect as if they were given in full text. Upon request, the CO will make their full text available. Go to the Internet at:

https://www.acquisition.gov or http://farsite.hill.af.mil/

These addresses are subject to change. If the Federal Acquisition Regulation (FAR) is not available at the locations indicated above, use the Dept. of State Acquisition Website at http://www.statebuy.state.gov.

F.2 FEDERAL ACQUISITION REGULATION (48 CFR CH. 1)

F.3 PERIOD OF PERFORMANCE

This contract is comprised of a one (1) year base period, and a four (1) year option periods. The CO can extend the term of the contract for an additional six (6) months in accordance with FAR 52.217-8, Option to Extend Services clause contained in Section I of this contract.

F.4 DELIVERABLES

The Contractor shall provide all deliverables in the timeframe and/or format approved by the COR. The CO shall notify the Contractor in writing of any additional deliverables that may arise during contract performance.

SECTION G – CONTRACT ADMINISTRATION DATA

G.1 DESIGNATION OF ADMINISTRATIVE CONTRACTING OFFICE

This contract will be administered as follows:

Primary Contracting Officer (CO):

1701 North Fort Myer Drive Arlington, VA 22209 Office: (703) 875-6645

Contract Specialist

1400 Wilson Boulevard Arlington, Virginia 22209

Administrative Contract Specialist:

Attn: Maxine Hodges 1400 Wilson Boulevard Arlington, Virginia 22209

Written communications regarding the administration of this contract shall make reference to the contract number and shall be mailed to the above address. The COR is responsible for oversight of the technical aspects of the Contractor's performance.

G.2 CONTRACTING OFFICERS REPRESENTATIVE DOSAR 652.242-70 (AUG 1999)

(a) The CO may designate in writing one or more Government employees, by name or position title, to take action for the CO under this contract. Each designee shall be identified as a COR. Such designation(s) shall specify the scope and limitations of the authority so delegated; provided, that the designee shall not change the terms or conditions of the contract, unless the COR is a warranted CO and this authority is delegated in the designation.

(b) The COR for this contract will be Mr. Brett Yankie.

(c) The COR is responsible for inspection and acceptance of services. These duties include review of Contractor invoices, including the supporting documentation required by the contract. The COR may provide technical advice, substantive guidance, inspections, invoice approval, and other purposes as deemed necessary under the contract.

G.3 GOVERNMENT TECHNICAL MONITORS (GTM)

a. A GTM may be designated to provide technical monitoring, advice and assistance, in the monitoring and evaluation of a contractor’s performance at separate consular locations. The GTM is appointed by the CO.

b) The GTM for this contract will be Mr.