Air_Defense_Planning_Tool_PWS_25_Jun_2013.docx

PWS/25 Jun 2013 Page 2 of 13 Automated Air Defense Planning Tool for IAMDC

AUTOMATED AIR DEFENSE PLANNING TOOL

FOR US CENTRAL COMMAND (CENTCOM)

INTEGRATED AIR AND MISSILE DEFENSE CENTER (IAMDC) EXERCISES

IN THE CENTCOM AREA OF RESPONSIBILITY (AOR)

PERFORMANCE WORK STATEMENT (PWS)

25 June 2013

TABLE OF CONTENTS

Table 1

ACRONYMS/ABBREVIATIONS:

1.0. INTRODUCTION/BACKGROUND. In July 2010, US Central Command (CENTCOM) established the Integrated Air and Missile Defense Center (IAMDC) in the United Arab Emirates (UAE) to serve as a joint/coalition ‘think tank’ to exercise live, virtual and constructive combined air and missile defense operations focusing on integration and interoperability to promote regional security through multi-national defense against ballistic missiles, cruise missiles, and air breathing threats. The IAMDC declared Initial Operating Capacity (IOC) on 24 March 2011.

2.0 DESCRIPTION OF OBJECTIVE. This Performance Work Statement (PWS) supports the CENTCOM IAMDC exercises and simulations in the CENTCOM Area of Responsibility (AOR). CENTCOM will use an automated air defense planning tool in the educational and interoperability exercises to demonstrate regional integrated air and missile defense concepts. To fully execute this mission, IAMDC requires an UNCLASSIFIED automated air defense planning tool capable of modeling air and missile threats, off-site technical and system support, and on-site exercise support.

3.0 REQUIREMENTS.

3.1. Automated Air Defense Planning Tool

3.1.1. Software must be capable of running effectively on conventional computer laptops running the standard desktop configuration (SDC) image; there should be no unique requirements or specialized equipment to be added to the systems unless provided by the contractor.

3.1.2. The system must be capable of modeling air and missile threats to include: ballistic/cruise missiles and rockets, Unmanned Aerial Systems (UASs), and fixed/rotary-winged aircraft; US and Partner Nations ground-based and sea-based air and missile defense assets, to include: surveillance sensors, fire control sensors, and weapons; US and Partner Nations air-based air defense assets, to include: airborne surveillance and fighters; and Airspace Control Orders (ACOs).

3.1.3. The system must be both scalable and interoperable. As a scalable capability, it must support increased capability through the addition, exchange, or growth of modular components that expand the system up to 10 computers. The planner is currently required on six (6) computers with the capability of growing to a total of 10 computers as other nations participate in partner exercises. All computers for this requirement will be provided by the contractor, to the government, for the sole purpose of operating this system. Interoperability must include the ability to network with similar systems at remote sites with the specific requirement to generate system changes on one system to update the others. As the scope of the exercise or as software demands increase new laptop computers may be required and will be provided by the contractor to the Government.

3.1.4. The software must be able to model the following:

· US and Partner Nations ground- and sea-based, point and area, air and missile defense assets, to include: surveillance sensors, fire control sensors, and weapons;

· US and Partner Nations air-based air defense assets, to include: airborne surveillance and fighters;

· Air and missile threats, to include ballistic/cruise missiles and rockets, UASs, and fixed/rotary-winged aircraft;

· Airspace control orders (ACOs).

3.1.5. The software must be RELEASEABLE to persons from the following Partner Nations: United Arab Emirates, Saudi Arabia, Bahrain, Qatar, Kuwait, Oman, Jordan and NATO partners Great Britain and France. It must be in compliance with International Traffic in Arms Regulations (ITAR).

3.1.6. The software must be an UNCLASSIFIED exportable system with sufficient fidelity to distinguish between upper and lower tier and short range air defense (SHORAD) elements’ relative capabilities.

3.1.7. The software must be able to:

· Import terrain and obstruction data in commonly available formats;

· Allow a user to create a complex scenario in eight (8) hours involving a 500x500 km region with 20 defended areas, twenty 20 threat launch areas, 20 surveillance sensors, and 30 weapon batteries with associated fire control sensors;

· Allow a user to make simple modifications to an existing scenario in 10 minutes, such as relocation and re-orientation of sensors and weapon batteries;

· Provide interactive 2D and 3D visualization of all components and terrain, to include expected trajectories of threats and interceptors, surveillance patterns, fire control sensor patterns and ACOs;

· Provide assessment of the coverage of defended areas against threats under a complex scenario;

· Provide assessment of launch area denied;

· Capture views in images that are easily exported to PowerPoint.

· Provide line of site (LOS) assessment and analysis based on terrain in regards to Radar and Frequency Modulation communication. Operator must be able to determine if terrain masking affects detection of communications.

· Provide the operator the ability to select different flight altitudes and speeds in order to accomplish proper sensor and engagement analysis.

· Define PATRIOT system radar sectors to emulate the different PATRIOT systems present in the region. Operators must be able to enter and azimuth and rotate the radar sectors together.

· Database imagery must:

· Feature updatable Levels of Detail (LOD’s)

· Filter higher resolution LODs through all lower resolution LODs

· Provide updatable LODS via a patching mechanism to ensure future updates to the database without requiring a complete recompile for minor updates

· Be covered by a minimum 20 meter commercial color imagery

· Provide primary training areas covered with a minimum of 1 meter commercial color imagery

· Provide orthorectified imagery that ensures roadways, rivers, and other geospatial features align

· Database terrain must:

· Have a minimum commercial level 2 DTED equivalent baseline for all training areas of interest.

· Support a patching mechanism to update terrain files without requiring a complete recompile of the database for minor updates.

· Database must be Public Information release Authorization (PIRA) approved to support IMADC’s CENTCOM AOR mission.

· Create a map square with coordinates of Upper Left Corner: 33 Deg 8 Min N, 31 Deg 37 Min E and lower Right Corner: 16 Deg 55 Min N, 77 Deg 13 Min E.

· Create a notional country with Lat/Long data points of:

· 26.6740277778 54.9604444444

· 26.9048611111 56.1565555556

· 27.1776388889 56.5132777778

· 26.5691111111 56.9958888889

· 26.1284444444 57.2686944444

· 25.394 57.4365555556

· 24.9323611111 57.5205

· 24.9113611111 58.2549444444

· 24.8694166667 58.6746111111

· 24.7645 59.2621666667

· 24.9323611111 59.5769166667

· 25.2890833333 59.7238055556

· 25.6248333333 59.5979166667

· 25.9186111111 59.3461111111

· 26.2963055556 59.2621666667

· 26.5691111111 59.3670833333

· 26.8418888889 59.472

· 27.0097777778 59.7238055556

· 27.1146944444 59.9336666667

· 27.4294444444 60.2064444444

· 28.0589722222 59.7028333333

· 28.4156944444 59.1362777778

· 29.0452222222 58.7795277778

· 29.7166944444 58.5487222222

· 30.5350833333 58.2549444444

· 31.3744444444 58.0870555556

· 32.27675 58.0660833333

· 32.7803611111 57.8142777778

· 33.2839722222 58.0241111111

· 33.5357777778 57.9821388889

· 33.7036666667 57.1008333333

· 33.57775 56.4922777778

· 33.7666111111 55.7158888889

· 33.6826666667 55.0863611111

· 33.6197222222 54.0371666667

· 33.5567777778 53.4915833333

· 33.1580833333 52.7781388889

· 33.5357777778 52.5892777778

· 33.7875833333 52.1905833333

· 33.9764444444 51.8758055556

· 34.0184166667 51.5820277778

· 33.7456111111 51.3302222222

· 33.1161111111 51.2253055556

· 32.90625 51.4771111111

· 32.5075555556 51.4771111111

· 32.27675 51.1833333333

· 31.7311666667 51.1833333333

· 31.3114722222 51.0154722222

· 31.0806666667 50.4908611111

· 30.9127777778 50.1761111111

· 30.3462222222 50.1341388889

· 30.1993333333 50.4489166667

· 29.9685 50.4698888889

· 29.5278333333 50.6167777778

· 29.1711111111 50.9735

· 28.9403055556 51.2043333333

· 28.4996388889 51.7499166667

· 28.33175 52.1066388889

· 27.8910833333 52.0646666667

· 27.68125 52.3584444444

· 27.3874722222 52.5053333333

· 27.1986388889 52.7151666667

· 26.7369722222 53.0928888889

· 26.5061666667 53.4915833333

· 26.5011111111 54.3066111111

· 26.6740277778 54.9604444444

· 26.9048611111 56.1565555556

· 27.1776388889 56.5132777778

· 26.6740277778 54.9604444444

· Must provide data output in both Excel spreadsheet format and XML format of the following types identified in Table 2:

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All CAL sizes, names, and coordinates

All DAL sizes, names, and coordinates

All CAPs sizes, names, and coordinates

All Airbase sizes, names, coordinates, and CAP association

All Call sign Names

All FEZ sizes, names, and coordinates

All JEZ sizes, names, and coordinates

All Air Corridor sizes, names, and coordinates

All Bullseye sizes, names, and coordinates

All Lines (e.g. FEBA, Commit, etc) sizes, names, and coordinates

All Special Points names and coordinates

All other participant developed item sizes, names, and coordinates

All FEZ sizes, names, and coordinates

All JEZ sizes, names, and coordinates

All Air Corridor sizes, names, and coordinates

All Bullseye sizes, names, and coordinates

All Lines (e.g. FEBA, Commit, FSCL, etc) sizes, names, and coordinates

All Special Points names and coordinates

All other participant developed item sizes, names, and coordinates

All FEZ sizes, names, and coordinates

All JEZ sizes, names, and coordinates

All Air Corridor sizes, names, and coordinates

All Bullseye sizes, names, and coordinates

All Lines (e.g. FEBA, Commit, FSCL, etc) sizes, names, and coordinates

All Special Points names and coordinates

All other participant developed item sizes, names, and coordinates

Table 2

3.2. Task 1: On-Site Exercise Support

3.2.1. Task 1 Overview. The contractor shall provide on-site representative for exercise and planning tool support at Al Bateen Air Base in Abu Dhabi, United Arab Emirates as requested by the government in table 4.

3.2.2. Subtasks. At the beginning of each exercise, on-site personnel shall:

· Install software and load updates;

· Conduct system orientation and familiarization training with IAMDC exercise personnel;

· Provide system overview briefing for exercise participants;

· Load user provided threat data;

· Validate system and database integrity prior to exercise;

· Develop and inputs sensors and weapons systems parameters;

· Provide technical system support throughout the exercise;

· Compile modeling data for group presentations;

· Archive system data files;

· Complete Defense Design data for use as input to simulation systems

· Prepare systems for next use.

3.2.3. Personnel Qualifications. The representative assigned to or utilized by the contractor must have the required Knowledge, Skills, and Abilities (KSAs) set forth below and shall be fully capable of performing the required tasks from Section 3.2 of this PWS in an efficient, reliable, and professional manner. Qualified personnel shall be provided at contract start unless previously negotiated by the Contracting Officer.

The contractor shall ensure employees have the required KSAs, outlined in paragraph 3.2.3.1, before starting work under this contract and ensure any other certifications/licenses are obtained (and maintained current) as required by Foreign Country Clearance Guide: a valid US driver's license, a valid US passport, an appropriate country visa.

3.2.3.1. Knowledge, Skills, and Abilities.

Contractor personnel shall have full knowledge and skills to operate, maintain, and debug exercise systems, and must be English-speaking, with enough clarity to be understood by second language listeners. Contractor is required to be able to provide a 2 to 3 hour class on how to operate the software to a small group of both US contractors and government personnel. Contractor will also be required to operate the software for a GCC Nation team and then for the GCC Regional team.

3.3. Task 2: Off-Site Technical and System Support

3.3.1. Task 2 Overview. The contractor shall provide off-site telephone and e-mail support for trouble shooting and answering questions. Required support is not expected to exceed twenty (20) hours per year. Response to user concerns is required within 72 hours.

3.3.2. Subtasks. Contractor employees providing off-site technical assistance shall possess full knowledge and skills to operate, maintain, and troubleshoot exercise systems via telephone and e-mail.

3.3.3. Personnel Qualifications. Personnel assigned to or utilized by the contractor must have the required Knowledge, Skills, and Abilities (KSAs) set forth below and shall be fully capable of performing the required tasks from Section 3.3 of this PWS in an efficient, reliable, and professional manner.

Qualified personnel shall be provided at contract start unless previously negotiated by the Contracting Officer.

3.3.3.1. Knowledge, Skills, and Abilities.

Contractor personnel must have full knowledge and skills to operate, maintain, troubleshoot, and debug exercise systems via telephone and e-mail and must be English-speaking, with enough clarity to be understood by second language listeners

4.0. DELIVERABLES. The contractor shall provide deliverables in a format mutually agreed upon by the Government and the contractor. The Contracting Officer’s Representative (COR) will have the right to reject or require correction of any deficiencies found in deliverables. In the event of rejection of any deliverable, the contractor will be notified in writing by the COR of the specific reasons why the deliverable was rejected. The contractor shall have 30 workdays to correct the rejected deliverable and resubmit to the COR for re-inspection. If no comments are provided within 30 calendar days of deliverable receipt, the deliverable will be deemed to have been accepted by the Government.

exercise

return from travel

Table 3

4.1. Automated Air Defense Planning Tool. Delivery of the automated air defense planning tool shall be made to IAMDC’s physical address no later than fifteen (15) days prior to exercise start date.

4.2. Monthly Status Report. At a minimum, the report shall contain progress from the previous month, status of contract milestones, resource expenditures for the project, total contact hours for Task 3.3, and issues/concerns and associated recommendations. Delivery will be made via e-mail to IAMDC Deputy Director, COR and Contracting Officer no later than the 10th of the month.

4.3. Trip Report. The contractor shall complete a trip report within ten (10) days of return from travel and deliver via e-mail to IAMDC Deputy Director, COR and Contracting Officer.

5.0. GOVERNMENT FURNISHED PROPERTY.

5.1. Government Provided Equipment/Office. GPE on-site for contractor personnel assigned to Task 1 will include a work area equipped with a desk, chair, access to telephone, Common Access Card (CAC), access to a computer equipped with unit specific software (including e-mail access) and access to a printer and facsimile machines (secure and non-secure).No GPE will be provided for contractor personnel assigned to Task 2.

5.2. Government Support- Personnel. The Government will provide access to government facilities and exercise locations and equipment for contractor personnel assigned to Task 1, as needed.

6.0. DATA. The Government has restricted rights data to the Automated Air Defense Planning Tool in accordance with Federal Acquisition Regulation (FAR) Clause 52.227-14.

7.0. TRAVEL. The contractor shall be required to travel in support of tasks listed above to fulfill PWS requirements. All trips will be in accordance with regulatory requirements and actual travel shall be coordinated and pre-approved by the COR in writing. Trips scheduled below are subject to change. The Government estimates one (1) trip to occur between October and January and 3 trips between January and June. Firm dates for each exercise will be provided to the contractor no later than (NLT) 30 days prior to exercise start. The Government will only reimburse allowable costs in accordance with FAR Part 31.205-46. The Contractor shall be required to provide travel receipts to the COR for all allowable costs and complete a trip report within 10 days of completion of travel. Travel projections are subject to change based on Government requirements. Local travel to attend meetings within the local city or base of assignment commuting vicinity shall be considered a cost of doing business and shall not be separately reimbursed.

Table 4

8.0. SECURITY INSTRUCTIONS. A DD 254, Department of Defense Contract Security Classification Specification, will be required for this contract.

8.1. Clearance. Performance under this PWS shall require a SECRET clearance. The Contractor shall provide a National Agency Check (NAC) for all contractor employees who are to be provided access to Government e-mail/internet, LAN/WAN and other Government information networks. If access to classified information is a requirement at the Contractor’s facility, a SF 312 Non-Disclosure Agreement (NDA) initiated by the company’s Facility Security Officer (FSO) is required. The Contractor must possess or obtain a facility security clearance at the appropriate classification level for the work prior to performing contract work.

9.0 TRANSITION PLAN: Twenty hours of dedicated IAMDC personnel training will be required for systems not already in use prior to the initial exercise under this contract.

10.0. ADMINISTRATION CONSIDERATIONS.

10.1. Performance Schedule. This contract will have a base year of 26 October 2013 to 25 October 2014 with two (2) option years.

10.2. Place of Performance. In accordance with paragraph 3.2 of PWS, the contractor personnel assigned to Task 1 shall be located at Al Bateen Air Base, UAE to perform and accomplish tasks identified in this PWS. There is no required place of performance for contractor personnel assigned to Task 2.

10.2.1. Telework. Telework shall not be permitted for this contract beyond off-site assistance identified in paragraph 3.3. Task 2.

10.3. Duty Hours. Normal duty hours for Task 1 are 0700 -1400 local, Sunday through Thursday, except Wednesday which are 0700-1600. Normal duty hours for Task 2 are at the contractor’s discretion but must be in accordance with paragraph 3.3.2.

10.4. Base Shutdown/Inclement Weather. The Contractor will follow guidance of the installation containing their place of performance to determine reporting schedules due to base closure or inclement weather.

10.5. Physical/Mailing Address and Contact Information.

10.6. Access to Required Areas or Facilities.

10.6.1. Identification Requirements. The contractor is responsible for ensuring the identification requirements for contractor personnel are obtained to ensure special passes or badges are issued for access to required areas or facilities. Contractor personnel are required to submit color copies of their passport’s information page and visa page. All required identification will be requested by the government to the contractor no less than fifteen (15) days prior to the arrival date of contractor personnel. Failure by contractor personnel to submit government requested identification requirements can result in delay or denial of base access.

10.6.2. Sponsorship. Only government employees (military or civilian) are authorized to sponsor contractors on base. Contractors cannot sponsor other contractors on base.

10.7. Medical. The U.S. Government will not furnish primary care for contractor personnel. The contract company shall be responsible for medical arrangements for their employees. The U.S. Government will only provide medical support when there is a risk to life, limb, or eyesight. All costs associated with the treatment and transportation of contractor personnel to the selected civilian facility shall be reimbursable to the Government and shall be the responsibility of the Contractor personnel, their employer or their health care provider.

10.8. Laws and Regulations. Contractor personnel shall comply with local host nation and base laws and regulations.

10.9. Weapons, Firearms, and Ammunition. Contractor personnel are prohibited from possessing weapons, firearms, or ammunition while in the CENTCOM AOR.

10.10. Physical Security. The contractor is responsible for safeguarding all government property and controlled forms provided for contractor use. At the end of each work period, all government facilities, equipment, and materials shall be secured.

10.11. Reporting and Suspicious Activity. Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DOD personnel, contractor personnel, resources, and classified or unclassified defense information.

10.12. Synchronized Pre-Deployment and Operational Tracker (SPOT). SPOT is designated as the Joint Enterprise contractor management and accountability system to provide a central source of contingency contractor information. Contractor companies are required to maintain by name accountability within SPOT. Registration can be accomplished through https://spot.altess.army.mil. Letter of authorization is required through this system.

10.13 Kickoff Meeting. The contractor shall attend a kick off meeting specific to the contract requirement with the COR and the Administrative Contracting Officer within thirty (30) days of contract award. The Contractor shall provide concurrence with the date, time and location for the meeting via email notification to the contracting officer at the time of the award.

11.0 APPENDIX A – SERVICE DELIVERY SUMMARY

a) qualified personnel are on the job at contract start unless previously negotiated by the Contracting Officer AND

b) the mission is not impacted due to position vacancies or personnel qualifications

There is no mission impact due to position vacancies or unqualified personnel.

Task 2 performance is acceptable when:

There is no mission impact due to position vacancies or unqualified personnel.

Develop and submit all required deliverables

a) 100% of deliverable requirements are met and received on time AND

b) critical information is accurate.

Table 5