PWS-RFI.pdf

PERFORMANCE WORK STATEMENT

FOR

U. S. MARINE CORPS TRAINING & EDUCATION COMMAND

RANGE AND TRAINING AREA

MANAGEMENT (RTAM) BRANCH

USMC RANGE MANAGERS TOOL

KIT (RMTK) SUSTAINMENT AND

UPGRADES

1.0 Background:

Training and Education Command (TECOM) RTAM, Army, Navy, and Air Force, requires technical support for the RMTK and Marine Corps Range and Training Area Management Systems (MCRTAMS) including provisions of the RMTK tools approved for Foreign Military Sales customers. The RMTK and MCRTAMS support is provided for unit commanders, headquarter staffs, operating units, range managers, cross-service users, and international customers in a desktop, web, and mobile environment. The RMTK is provided as a set of range safety standard metrics that relates range capabilities to specific training requirements using established range safety standards. RMTK on MCRTAMS provides access to and supports the RMTK for safety, range use, range planning, and range support functions as MCRTAMS stores and provides Geographic Information System (GIS) data for Marine Corps ranges and training areas in addition to other non-Marine Corps areas where the Marine Corps regularly trains. MCRTAMS also provides the Marine Corps’ integrated and readily available range inventory and training range database in a web environment.

The RMTK is a suite of tools in the form of a software application that currently runs as an Environmental Systems Research Institute (ESRI) ArcMap Extension utilizing ESRI 3D Analyst and Spatial Analyst extensions, ARC Server for the web enabled portions of MCRTAMS and in a Xamarin framework for the mobile environment. The danger zone tools within RMTK depict a three dimensional (3D) area associated with firing weapons/lasers/explosives where the risk of damage, injury or death does not exceed an acceptable level. The RMTK danger zone tools allow the user to create and modify danger zones. The danger zones encompass the ground and airspace for lateral and vertical containment of projectiles, fragments, debris, and components resulting from the firing, launching, and/or detonation of ordnance. This three-dimensional zone accounts for weapon accuracy, failures, ricochets, and broaches/porpoising of a specific weapon/munition type delivered by a specific aircraft type, laser energy and direct/indirect fire weapons ordnance. Danger Zones represent the minimum safety requirements designed for live fire training on Department of Defense (DOD) training ranges.

The Marine Corps is the lead and Chair of the Aviation Range Safety Sub-Group as designated by the DOD’s Cross Service Range Use Standardization Working Group (RUSWG), the RTAM Branch is tasked to develop comprehensive strategies accommodating the differing Service and National perspectives, and varying needs for range utilization and safety, which forms the basis of the WDZ tool/data in addition to Service considerations in the remainder of the RMTK tools. Specifically, the Weapons Danger Zone (WDZ) tool is the accepted United States Service air to ground danger zone tool for all air to ground activities to provide weapons danger zones and risk analysis. The RMTK tools may be provided to North Atlantic Treaty Organization (NATO) and other Partners for Peace (PfP) nations to facilitate interoperability. A Foreign ally may submit a new danger zone request and obtain access to an RMTK tool.

The RTAM Branch is responsible for establishing a cohesive management framework that ensures the objectives of the various sponsored initiatives are executed within program constraints. This includes establishing a cohesive management organization and support framework to execute management of business and technical attributes of program initiatives, oversight of prime vendor performance (e.g., progress, investment), and coordinating actions among Integrated Product Teams (IPT) and other participating activities (e.g., NATO Range Safety Working Group, International Range Safety Working Group).

WDZ tool data cubes consist of the data necessary to determine the initial impact distribution (Delivery Accuracy), the ricochet impact distribution, and the failure mode impact distribution. These data are used to generate a combined probability distribution function (pdf) that defines the potential impacts from a training range event. While the term “Data Cube” is applied to the various subcomponents of the WDZ weapon model, the actual data cube is comprised of both organized multi-dimensional look-up tables (created in Microsoft Access) that sample a weapon’s physical performance data and coefficient terms describing a polynomial approximation to a physical characteristic specific to the weapon’s unique behavior. These interpolated data are integral to the data cube through various software interfaces and these data are used as a data point within the data cube. Weapon systems that have similar ballistic and failure mode characteristics use the same data and modeling format.

The RMTK suite of tools are created in VB.Net and C++ and Xamarin. The User Interface tools are written using VB.Net and the RMTK engine is compiled into a C++ Dynamic Link Library (DLL). The database foundations of the tools are created in Microsoft Access and Microsoft SQL Server. The RMTK mobile tools will be developed and maintained for use in an iOS and Android. For the WDZ tool the WDZ Software Specification Documents Volume I-VI (Applicable Documents 7.0.15) provide detailed technical information regarding the WDZ tool required to create and integrate the WDZ data cubes.

2.0 Scope:

The scope of this Performance Work Statement covers RMTK technical support to TECOM and the RTAM Branch, including software maintenance, database development, engineering support, integration services, functionality and range safety parameter updates within the Multi-Service RMTK suite of tools, RMTK integration services and functionality updates within the MCRTAMS and the integration of ETR, SDZ, and WDZ into a mobile environment. The technical support also includes the services of subject matters with expertise relevant to the technical support or as otherwise described below.

In addition, the scope includes FMS purchases of the technical support and subject matter expertise.

Technical support is for the following RMTK tools:

Surface Danger Zones (SDZ) – SDZ Tool

Surface danger zones (SDZs) define the ground and airspace designated within the training complex (to include associated safety areas) for vertical and lateral containment of projectiles, fragments, debris, and components resulting from the firing, launching, or detonation of weapon systems to include explosives and demolitions. The SDZ Tool generates surface danger zones in accordance with parameters defined in MCO 3570.1C (Applicable Document 7.0.1). The size and shape of an SDZ is dependent on specific user input such as the location of firing points and targets, weapon system, ammunition, impact media, and/or terrain. The capability to develop SDZs on the map serves as the basis for other RMTK uses, such as mission planning, range deviations, range modernization/planning, and range certification.

Weapon Danger Zones (WDZ) – WDZ Tool Weapon danger zones (WDZs) define the ground and airspace for lateral and vertical containment of projectiles, fragments, debris, and components resulting from the firing, launching, and/or detonation of aviation delivered ordnance. The RMTK WDZ Tool creates WDZs for aerial platforms (fixed wing, rotary wing, and unmanned aircraft systems (UAS)) delivering air to ground weapons. The size and shape of a WDZ is dependent on a variety of aircraft delivery parameters to include airspeed, altitude, delivery angle, and aerial platform bearing to target.

Range planners from all services must know the locations of WDZs to safely execute single service and joint training exercises. The WDZ Tool will provide a common aviation delivered weapons danger zone format across the entire DoD and foreign militaries.

Explosive training range danger zones – Explosive Training Range Tool (ETR) RMTK will support breaching operations and explosives training by generating associated explosive danger zones. Definitions and parameters for the explosive danger areas are available in MCO 8020.10 (Applicable Document 7.0.5) Marine Corps Explosives Safety Program and Department of the Army Pamphlet (DA- PAM) 385-64 (Applicable Document 7.0.9) Explosive Safety. General DoD guidance for this application can be found in Naval Sea Systems Command (NAVSEA) NAVSEA OP5 Volume 1(Applicable Document 7.0.7), Ammunition and Explosives Ashore Safety Regulations for Handling, Storing, Production, Renovation and Shipping.

Laser Range Management – Laser Range Management Tool (LRMT) RMTK will provide a tool to support and automate the certification and management of Army, Navy, Air Force, and Marine Corp laser ranges. Most tactical lasers operated on certified military ranges are hazardous to personnel and are usually treated as direct fire weapons. The laser surface danger zones (LSDZ) associated with these lasers are generated by the LRMT in accordance with parameters defined in Military Handbook (MIL-HDBK) 828B (Applicable Reference 7.0.12), Range laser Safety, Operations Naval Instruction (OPNAVINST) 5100.27/MCO 5104.1A (Applicable Document 7.0.6) Navy Laser Hazards Control Program, and Technical Bulletin Medical (TB MED) 524 (Applicable Document 7.0.8) Control Of Hazards to Health from Laser Radiation. The LRMT will develop LSDZs to help users manage the inherent risks associated with ground and airborne laser designation training exercises.

On range noise - Noise Tool Firing weapon systems causes noise, which can be an annoyance to both on-post and off-post residents. The Army Engineer Research and Development Center, Construction Engineering Research Laboratory (ERDC-CERL) has modeled noise contours associated with firing events. Noise contours are based on the weapon system, munitions, firing location, target location, and atmospheric conditions. RMTK will allow Range Managers to place noise contours in the context of other map layers to gain better situational awareness of their range complex and take action to mitigate complaints. The RMTK Noise tool is designed as a range management tool, not a National Environmental Policy Act (NEPA) noise compliance tool due to the difference between range and NEPA noise measurement requirements.

On range ammunition storage potential explosion radii – On Range Ammunition Handling Tool (ORAH)

Ammunition temporarily stored in total support of the training mission for use on a range has an explosive potential that is hazardous to personnel and property.

Definitions and parameters for the explosive safety quantity-distance (ESQD) arcs are available in MCO 8020.10 (Applicable Document 7.0.5), Marine Corps Ammunition Management and Explosives Safety Policy Manual and DA PAM 385-64 (Applicable Document 7.0.9), Army Ammunition and Explosives Safety Standards. General DoD guidance for this application can be found in NAVSEA OP5 Volume 1 (Applicable Document 7.0.7). RMTK will represent the ESQD arcs in a map context.

Range clearance – Range Clearance Tool (RCT)

The Range Clearance Tool is designed to meet Marine Corps requirements to enhance the safety and sustainability of operational training ranges through the management and accountability of accumulated unexploded ordnance and munition, target, and other range-related debris. Use of the RCT is required for Marine Corps use with policy found in MCO 3550.9 (Applicable Document 7.0.2), Range Certification and MCO 3550.12 (Applicable Document 7.0.3), Operational Range Clearance.

Range design – Range Design Tool (RDT) The Range Design Manual/Range Design Tool (RDM/RDT) is a software application within the RMTK which supports and assists regions and installations with range design and the initial planning of new or modified Range Training Areas (RTAs). The tool assists installation range personnel through the range design process by providing the capability to create site maps with applicable progress checklists, conduct analysis on the potential construction site and complete the initial construction form.

The RDM/RDT allows users to provide a detailed, scaled "blueprint style" overlay on any USMC range using multi-service and a comprehensive, specified design for individually aligned range in orders to better articulate how to satisfy USMC range requirements.

Range development and planning (RDAP) – RDAP Tool The RDAP Tool will assist users in placing Army standard ranges as defined in

Training Circular (TC) 25-8 (Applicable Document 7.0.10), Training Ranges on Army ranges. RMTK will allow the user to move and rotate range footprints to allow them to fit within the confines of their allotted land resource. Users will be able to view potential range footprints (and their associated SDZ) in the context of 3D terrain, other potential ranges, existing ranges and other information in an electronic map format.

Training event visualization (TEPS) TEPS will provide situational awareness by displaying RMTK generated danger zones, (i.e. SDZs, LSDZs, WDZs and/or explosive danger zones) in the context of other installation and training complex datasets. Danger zones will be displayed in 3D with the ability to add time lines so that the 3D danger zones can be displayed in a graphic time line. TEPS will be capable of visualizing training at all levels including Combined Arms Live Fire Exercises (CALFEX-Army)/ Combined Arms Exercises (CAX-USMC) that use time sensitive events and utilize phaselines and movements.

Probabilistic surface danger zones (PSDZ) – PSDZ Tool The PSDZ tool will allow users to determine a SDZ utilizing ricochet data and terrain data to properly show the mitigation effects provided by the terrain. The methodology relies on using terrain data and ricochet data as the basis for an individual point to point PSDZ to be developed. The PSDZ will maintain the 1:1,000,000 chance of hazardous fragment escapement standard. The PSDZ Tool will support range safety policy found in MCO 3570.1C (Applicable Document 7.0.1), by generating unclassified PSDZs, based on ricochet and terrain. The PSDZ Tool will allow the user to determine the predicted shot fall after contact with terrain. The PSDZ Tool incorporates specific probabilistic methodologies developed under the auspices of the North American Treaty Organization (NATO) Range Safety Working Group and the International Range Safety Advisory Group and within the multi-national Technical Cooperation Program (TTCP). The PSDZ Tool incorporates the data and formula as outlined within Allied Range Safety Publication (ARSP) 2 Volumes 1 & 2 (Applicable Documents 7.0.13). The tool incorporates deterministic surface danger zones of participating TTCP nations. The PSDZ Tool will allow a user to produce PSDZs for multiple targets and firing points for inclusion as a composite PSDZ. For terrain-mitigation, the tool will identify any intervening terrain (elevation data).

Foreign Danger Zones – (FSDZ, WDZ tools) The FSDZ tool creates SDZs in accordance with foreign policy documents approved by the service proponents.

RMTK Mobile applications

The RMTK mobile applications are SDZ, ETR, and WDZ. They are to be utilized in a mobile disconnected environment to allow basic creation of danger zones on mobile devices and for review by range controls.

3.0 Objectives:

Listed below are nine (9) objectives that make up this PWS, which are further described in paragraph 4.3 Specific Requirements.

1. RMTK Systems Support - This task encompasses sustaining support for the existing RMTK suite of tools and provision of SMEs with knowledge of ground to ground probabilistic methodologies and specific weapons technical requirements that will be included in the RMTK suite of tools. SMEs supporting RMTK Systems Support shall have in-depth knowledge of small and large caliber munitions and how to integrate small caliber danger zones and small caliber ricochet methods into the GIS environment.

2. RMTK Recommendations and Strategies - This task is to provide recommendations and strategies concerning upcoming version changes, best practices, and hardware associated with RMTK that will help the Government develop its future years plan to support the RMTK.

3. MCRTAMS RMTK Systems Support - This task ensures that the RMTK tools that are housed within MCRTAMS function as a cohesive program and is integrated with the desktop version of the RMTK as outlined in paragraph 4.3.3 of this PWS.

4. WDZ Tool Support - This task requires the Contractor to provide subject matter expertise with knowledge of aircraft systems properties to include UAS, munitions, precision guided munitions/guidance systems, and terminal effects to support the development of air-to-ground danger zones for the WDZ program and to update and maintain the WDZ program for the DoD Services.

5. RMTK End User refresher and advanced training - This task is to conduct formal RMTK training sessions that teach USMC Range and RTAM staff updated function and familiarity within the RMTK suite of tools.

6. Help Desk Support - This task is to provide help desk support.

7. WDZ training FMS only - This task is to conduct formal WDZ training sessions for

FMS customers.

8. Foreign Military Sales - This task is to provide approved FMS countries the above objectives other than Tasks 2 or 3 (RMTK recommendations and strategies and MCRTAMS RMTK systems support).

9. RMTK Mobile Support – This task ensures that the RMTK tools housed within RMTK mobile (ETR, SDZ, WDZ) function as a cohesive program and are integrated with the desktop version of the RMTK as outlined in paragraph 4.3.9 of this PWS.

4.0 Requirements: The Contractor shall support the TECOM RTAM effort consistent with the activities identified:

4.1 General Requirements: The Contractor shall provide all materials, equipment, personnel, and facilities necessary to support this capability requirement and deliver the types of services and deliverables specified by this PWS. The Contractor is responsible for providing suitable technical and analytical expertise to support ongoing responsibilities delineated in this PWS.

4.1.1 Place of Performance: Work efforts in support of this PWS will be accomplished at the Contractor’s facility(ies). Short duration meetings may be held at TECOM or via teleconference.

4.1.2 Development Details: Data shall be sufficient, competent, and relevant to support Contractor's findings and consistent with fact. Third-Party or Contractor Proprietary, or commercial applications shall not be used unless previously approved in writing by the Contracting Officer Representative (COR).

4.1.3 Security Requirements: This contract will require the contractor to have a Secret Facility Clearance and will require certain contractors to obtain and maintain classified access eligibility.

The contractor shall have a valid Secret Facility Clearance prior to classified performance. The prime contractor and all sub-contractors (through the prime contractor) shall adhere to all aspects of 32 CFR Part 117 NISPOM and DoD Manual 5220.22 Volume 2. All personnel identified to perform on this contract shall maintain compliance with Department of Defense, Department of the Navy, and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. This contract shall include a DoD Contract Security Classification Specification (DD-254) as an attachment.

Certain contractors will be required to perform IT-I/II duties that will require favorably adjudicated Tier 5/3 Level investigations. The Defense Counterintelligence Security Agency (DCSA) will not authorize contractors to submit the necessary Tier Level investigations solely in support of IT level designation requirements, but are required to submit investigations for those employees requiring both Secret access and IT-II designation. The Government Contracting Activity Security Office (GCASO) is required to submit any required investigations in support of IT-I level designations. The contractor is required to provide a roster of prospective contractor employees performing IT-I duties to the MCSC Contracting Officer’s Representative (COR).

This roster shall include: full names, Social Security Numbers, e-mail address and phone number for each contractor requiring investigations in support of IT Level designations. The COR will verify the IT-I requirements and forward the roster to the GCASO. Contractors found to be lacking required investigations will be contacted by the GCASO.

Facility Security Officers (FSOs) shall be responsible for notifying the host Command Personnel Security Office (PERSEC Office) via encrypted e-mail if any contractor performing on this contract receives an unfavorable adjudication. The FSO must also notify the PERSEC Office, within 24 hours, of any adverse/derogatory information associated with the 13 Adjudicative Guidelines concerning any contractor performing on this contract, if they have been granted an IT designation, issued a CAC, an access Building Badge and/or granted classified access. The FSO shall notify the Government (written notice) within 24 hours of any contractor personnel added or removed from the contract that have been granted IT designations, issued a Common Access Card (CAC) and/or a Building badge/access. For this PWS tasking, the Contractor’s facilities shall have a Facility Security Clearance (FCL) at the Secret clearance level to support Secret document storage.

4.1.3.1 Contractor personnel shall gain access to the Joint Munition Effect Manual (JMEM) (Applicable Document 7.0.11) software suite, Combat Weapon Delivery Software (CWDS), air-to-ground Weapon System Evaluation Program (WSEP) database, All Weapons Information System (AWIS) database to help guide in the development of WDZ’s. The Contractor shall store country specific data as needed to support the development of foreign nations’ weapons danger zones.

4.1.4 Common Access Card (CAC) Requirement: The COR will identify and approve only those Contractor employees performing on this contract that require CACs in order to perform their job functions. In accordance with Headquarters, United States Marine Corps issued guidance relative to Homeland Security Presidential Directive – 12 (HSPD-12), all personnel must meet eligibility criteria to be issued a CAC. In order to meet the eligibility criteria, Contractor employees requiring a CAC must obtain and maintain a favorably adjudicated Personnel Security Investigation (PSI.) Prior to authorizing a CAC, the employee’s Defense Information Security Systems (DISS), or successor application, record must indicate a completed and favorably adjudicated PSI or (at a minimum) that a PSI has been submitted and accepted (opened). The minimum acceptable investigation is a T-1 (Trustworthiness / Suitability). If a Contractor employee’s open investigation closes and is not favorably adjudicated, the Contractor must immediately retrieve the CAC and return it to the COR.

Facility Security Officers (FSOs) are responsible for notifying the host Command Servicing Security office if any Contractor employee performing on this contract receives an unfavorable adjudication after being issued a CAC. The FSO must also notify the host Command Servicing Security office of any adverse/derogatory information associated with the 13 Adjudicative Guidelines/Factors concerning any Contractor employee issued a CAC. The required DISS Incident will be filed by the

FSO.

Each CAC is issued with a “ctr@usmc.mil” e-mail account that the individual Contractor employee is responsible to keep active by logging in on a regular basis (at least twice a month), sending an e-mail and clearing any unneeded e-mails. Contractors and Contractor employees are prohibited from “auto-forwarding” their .mil e-mail account to their .com e-mail account. If the “ctr@usmc.mil” e-mail account is not kept active, G-6 will deactivate the account and CAC will lose its functionality. Contractor employees shall solely use their government furnished “ctr@usmc.mil” e-mail accounts for work supporting the USMC, conducted in fulfillment of this contract, and shall not use a Contractor supplied or personal e-mail account to conduct government business. The use of a Contractor or personal e-mail account for Contractor business or personal use is allowed, but only when using cellular or a commercial internet service provider.

If a Contractor employee loses eligibility for a CAC due to an adverse adjudicative decision, the Contractor employee also loses eligibility to perform on MARCORSYSCOM contracts. CACs are not issued for convenience.

The Contractor shall develop a Work Breakdown Structure (WBS) for all tasks required in this contract, in accordance with the delivery schedule.

4.1.4 The Contractor shall participate and take notes/minutes in the quarterly Program Management Reviews (PMRs) and/or CMWG meetings, at a time and place to be designated by the Government, in accordance with delivery schedule. If the PMR is not to be conducted via electronic means (video teleconference, net meeting or other electronic means) the Contractor shall attend the quarterly PMRs in person at locations as designated by the Government. The Contractor shall be prepared to discuss all programmatic issues. The Contractor shall also provide paper and electronic copies of its presentations to the PMR/CMWG and all Government attendees 10 days prior to the PMR. The agenda, approximate number of attendees and additional topics for the quarterly program reviews will be sent by the Government to the Contractor no later than 5 business days before the scheduled program review date.

DELIVERAB

LE

FORMAT DATE

REQUIRED

Acceptable Quality Level

(AQL)

4.1.5 The Contractor shall maintain and update the RMTK embedded help software, to include the Glossary of Terms, in accordance with the delivery schedule.

4.1.5.1 The Contractor shall ensure that the RMTK suite of tools will pass appropriate accreditation procedures, to include compliance with appropriate Defense Information Systems Agency’s (DISA) Security Technical Implementation Guides (STIGs) (Applicable Document 7.0.14) and provide status quarterly in accordance with the delivery schedule.

notes/minutes from the quarterly Program Management Reviews (PMRs) and/or

CMWG

meetings

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Initial submission 5 days after each PMR and/or

CMWG.

Contractor shall address all Government comments no later than 5 days

Error free upon second Contractor submission to Government.

DELIVERAB

LE

FORMAT DATE

REQUIRED

Acceptable Quality Level

Updates to RMTK help software and glossary of terms

Embedded help in the RMTK tools Initial submission As required and defined in WBS; The contractor will address all Government comments and resubmit no later than 5 days after receipt

Error free upon second contractor submission to the Government.

DELIVERAB

LE/

PERFORMA

NCE

REQUIREME

NT

FORMAT DATE

REQUIRED

Acceptable

4.1.5.2 The Contractor shall perform secure configuration control of application code. The Contractor is allowed to follow industry best practices performing software development (including the use of secure off-site repositories).

4.1.5.3 Kick-Off meeting shall be conducted at Government facilities no later than 15 business days after award in accordance with the delivery schedule. The purpose of this kickoff meeting is to:

Introduce key Government and Contractor personnel Review terms and conditions of the contract Review PWS requirements, schedule (to include travel) and deliverables to ensure understanding between all parties Provide answers to Contractor questions regarding the administration of the contract Establish preliminary dates for future program events Discuss any other items the COR may deem appropriate to discuss Obtain Non-Disclosure Agreements from ALL Personnel performing on this contract In addition, administrative items, such as invoicing, communication mechanisms, access to Government systems, etc. will be addressed System Authorization Access Request 2875 forms provided by the Government for Common Access Card issuance.

4.1.5.4 The Contractor shall maintain and update the WDZ specification volumes I-VI in accordance with the delivery schedule.

RMTK passes accreditation procedures

Embedded within RMTK RMTK must obtain accreditation annually without a gap in accreditation.

The contractor will revise documentation associated with accreditation no later than 5 days after receipt of comments/error s

The contractor will successfully resolve all issues within 5 days of identification of problem.

4.1.5.5 The Contractor shall deliver a monthly status report in accordance with the delivery schedule.

4.1.6 Contractor employees shall identify themselves as Contractor personnel by introducing themselves or being introduced as Contractor personnel and displaying distinguishing badges or other visible identification for meetings with Government personnel. In addition, Contractor personnel shall appropriately identify themselves as Contractor employees in telephone conversations and in formal and informal written correspondence.

4.1.7 Monthly Report The Contractor shall deliver a monthly report that details monthly significant events.

4.2 Reserved.

4.3 Specific Requirements:

4.3.1RMTK Systems Support:

4.3.1.1 The Contractor shall incorporate and modify workflow to include all new/updated safety standards established into the RMTK suite of tools that are provided by the Government or otherwise identified in the MCO 3570.1D (Applicable Document 7.0.1), MCO 3550.9A(Applicable Document 7.0.2), MCO

3550.10 (Applicable Document 7.0.4), Policies and Procedures for Range and Training Area (RTA) Management and MCO 3550.12 (Applicable Document 7.0.3).

DELIVERAB

LE

FORMAT DATE

REQUIRED

Acceptable Quality Level

Monthly status report

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Initial submission on the 5th of each month.

The contractor shall correct errors and resubmit each submission within five days of receipt of Government comments

Error free upon second submission.

4.3.1.2 The Contractor shall ensure that the RMTK suite of tools accurately define the operational capability of all the danger zones with information provided by the COR.

4.3.1.3 The Contractor shall ensure that the hazards associated with danger zones have horizontal and vertical components that are depicted and can be queried.

4.3.1.4 In addition to any other deliverables identified in this PWS, the

Contractor shall submit a yearly deliverable of all items created, generated, produced to develop the RMTK suite of tools including, but not limited to, algorithms (with function descriptions) or “pseudo” code formulas, databases, class diagrams, use cases, executable (object code) and non-executable (source code) codes, on a DVD(s) in accordance with the delivery schedule.

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

RMTK Safety Updates Proposal

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

The contractor shall acknowledge a request for a safety update proposal within 48 hours of receipt

The contractor shall proposed a solution, including a timeline for its implementation of that solution, within 72 hours of receipt of the request for a safety update proposal

Safety updates are critical. The contractor shall meet its obligation to acknowledge and implement safety solutions within the expected time frame 100% of the time.

In addition, the updates proposal shall be error free upon submission 100% of the time.

RMTK Safety Updates

Executable file and integration of emergent safety requirements.

As mutually agreed upon in the proposed solution; if

The contractor shall integrate the RMTK update

4.3.1.5 The Contractor shall ensure that any newly developed foreign surface danger zones are included in the RMTK FSDZ.

4.3.1.6 The Contractor shall implement Government provided installation

Range Design Plan data and update RMTK.

nothing is stated in the proposed solution, the executable file will be delivered and the integration will be completed no later than 72 hours after the request for a safety update proposal.

accurately 100% of the time.

Compilation of yearly software Configuration Items/source code

Algorithms (with function descriptions) or “pseudo” code formulas, databases, class diagrams, use cases, executable (object code) and non-executable (source code) source codes. Delivered on

CD/DVD.

The contractor will deliver the initial submission 45 days prior to the end of the PoP for Government review; The contractor will address all Government comments (including correcting errors) and resubmit no later than 5 days after receipt of Government comments

Final submission must contain no errors, address all Govt comments to COR’s satisfaction, and be submitted to Govt no less than 5 days after receipt of Govt comments.

4.3.1.7 The Contractor shall develop and execute desktop and web RMTK test plans for MCRTAMS, Range Facilities Management Support System (RFMSS), and the Marine Corps, Army, Navy, and Air Force.

4.3.1.8 The Contractor shall troubleshoot problems identified by the COR as related to GIS applications/extensions.

4.3.1.9 The Contractor shall deliver to the COR documentation on data quality and GIS workflows for the RMTK suite of tools in accordance with the delivery schedule.

4.3.1.10 The Contractor shall maintain and update the web based range certification module resident on MCRTAMS.

4.3.1.11 The Contractor shall maintain the database for tracking of all range certifications in the Marine Corps within the MCRTAMS range certification module.

4.3.1.12 The Contractor shall maintain and update the PSDZ Tool with technical munitions data provided by the COR.

4.3.1.13 The Contractor shall maintain and update the LRMT with information concerning laser use on ranges and laser systems as provided by the COR.

DELIVERAB

LE

FORMAT DATE

REQUIRED

Acceptable Quality Level

RMTK GIS

data quality and workflow(s) documentatio n

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

As required for the tool release schedule defined in the

WBS;

The contractor will correct errors/ address Government comments and resubmit no later than 5 days after receipt of Government comments

Error free upon second submission

4.3.1.14 The Contractor shall maintain and update the ETR Tool with explosives data and explosives training data as provided by the

COR.

4.3.1.15 The Contractor shall maintain and update the Noise Tool for range noise with small caliber, large caliber, and air to ground data as provided by the COR.

4.3.1.16 The Contractor shall maintain and update the ORAH Tool with information for temporary ammunition storage on operational training ranges as provided by the COR.

4.3.1.17 The Contractor shall maintain and update the RCT with range clearance information as provided by the COR.

4.3.1.18 The Contractor shall maintain and update the RDT with range design drawings that are provided by the COR.

4.3.1.19 The Contractor shall maintain and update the RDAP with range planning information provided by the COR.

4.3.1.20 The Contractor shall maintain and update the SDZ tool with surface danger zone information provided by the COR.

4.3.1.21 The Contractor shall maintain and update the MCRTAMS implementation of the web ETR, SDZ, and WDZ to ensure compatibility with the desktop based version of RMTK.

4.3.1.22 The Contractor shall implement the Government database of foreign danger zones into the FSDZ tool as provided by the COR.

4.3.1.23 The Contractor shall maintain, update, and integrate the desktop based RCT into a MCRTAMS web based RCT with information provided by the COR.

4.3.1.24 The Contractor shall deliver an updated production release of software once per year for all RMTK tools outlined in 2.0, Scope, in accordance with the delivery schedule.

DELIVERAB

LE

FORMAT DATE

REQUIRED

Acceptable

4.3.1.25 The Contractor shall perform regression testing of all RMTK tools set forth in 2.0, Scope, and deliver the test report to the Government that includes a plan to correct any deficiencies found during testing in accordance with the delivery schedule.

4.3.1.26 The Contractor shall ensure that RMTK outputs are in a standard format compatible with RFMSS.

4.3.2 RMTK Recommendations and Strategies:

Updated of

RMTK

baseline

The Contractor shall provide the RMTK tools in executable form as baseline via email to the COR

As required for the tool release schedule defined in the

WBS;

The contractor will correct errors/ address Government comments and resubmit no later than 5 days after receipt of Government comments.

All identified errors in code resolved within 5 days.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Regression test deficiency plan

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

As required for the tool release schedule defined in the

WBS;

The contractor will correct errors/ address Government comments and resubmit no later than 5 days after receipt of Government comments

Error free upon

4.3.2.1 The Contractor shall provide recommendations that ensure compatibility with future modifications and/or improvements to version changes of computer operating systems, software, hardware, and database versions/types. The recommendations shall include known upcoming version changes to the computer operating systems, software, hardware, and database versions/types. The recommendations shall be provided in the monthly status report in accordance with the delivery schedule.

4.3.2.2 The Contractor shall provide recommendations for specific RMTK management, safety, planning and risk analysis solutions that may apply to DOD range and training areas users and operators. The solutions shall be based upon upcoming version changes in ESRI software. The recommendations shall be provided in the monthly status report in

4.3.2.3 The Contractor shall provide specific information on Contractor proposed content and functionality improvements of the tools within RMTK based upon best practices for the GIS community in the monthly status report in accordance with the delivery schedule.

4.3.2.4 When development of new WDZs has be initiated by one or more of the Services and vetted through the Configuration Management Working Group (CMWG), the Contractor shall determine and propose the schedule and performance parameters associated with the development of the danger zone and forward the proposed information to the appropriate Service(s) for approval during the PMR in accordance with the delivery schedule. If the proposed WDZ schedule and development parameters are not approved at

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Recommendat ions document

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

As required and defined in the

WBS;

The contractor will correct errors/ address Government comments and resubmit no later than 5 days after receipt of Government comments

Error free upon the PMR the Contractor will be required to adjust and resubmit within five days for COR approval.

4.3.3 MCRTAMS RMTK Systems Support: The Contractor shall define MCRTAMS functionality and ensure that the RMTK tools that will be housed within MCRTAMS will function and be compatible with the desktop-based RMTK.

4.3.3.1 The Contractor shall maintain and update the RMTK interfaces incorporated within MCRTAMS in accordance with the delivery schedule.

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Development schedule

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

The contractor shall acknowledge a request for a development schedule 2 days of receipt The contractor shall deliver the schedule within 5 days of the acknowledgme nt

The contractor shall resubmit to correct errors within 5 days of receipt of Government’s comments

Error free upon second submission.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

RMTK

interfaces for

MCRTAMS

Items/source code

The Contractor shall deliver source code and forms for MCRTAMS

Annually as defined in

WBS

Error free upon

4.3.3.2 The Contractor shall update the web enabled versions of ETR, SDZ, and WDZ RMTK tools in combination with the stand-alone versions of RMTK tools.

4.3.3.3 The Contractor shall ensure that all tools are engineered to run in the current and planned versions as derived from PWS 4.3.2 version of MCRTAMS.

4.3.3.4 The Contractor shall ensure that tools are engineered to run in the current and planned versions as derived versions from PWS 4.3.2 server version of the ESRI software.

4.3.3.5 The Contractor shall ensure that all RMTK tools are engineered to run in the current and planned versions as derived from PWS 4.3.2 version of Citrix.

4.3.4 WDZ Tool Support:

4.3.4.1 The Contractor shall update and submit data cubes for Government provided information regarding aircraft within the WDZ Tool.

4.3.4.2 The Contractor shall submit an Integrated Master Schedule (IMS) of WDZ priorities established by the multi-service CMWG quarterly in accordance with the delivery schedule.

4.3.4.3 The Contractor shall deliver a matrix of WDZ dependencies that will preclude the development of the IMS for the Government. If there are any dependencies creating obstacles to the development of a WDZ or associated data cube, the Contractor shall update the dependencies list and inform the Government in accordance with the delivery schedule.

5 days to correct errors and resubmit

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Integrated master schedule

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Quarterly as defined in the

WBS

5 days to correct errors and resubmit

Error free upon

4.3.4.4 The Contractor shall deliver the results of verification and validation of WDZs with any pertinent updates to the Government annually in accordance with the delivery schedule.

4.3.4.5 The Contractor shall deliver test plans for quality control procedures annually in

4.3.4.6 The Contractor shall integrate new weapons data into the WDZ database, WDZs, modules, and/or models when provided by the COR.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Dependencies matrix

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Monthly in the monthly status report;

5 days to correct errors and resubmit

Error free upon second submission.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Verification and validation results

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Annually as defined in

WBS

5 days to correct errors and resubmit 5 days to correct errors and resubmit

Error free upon second submission.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

QA test plans MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Annually as defined in

WBS

5 days to correct errors and resubmit

Error free upon

4.3.4.7 The Contractor shall gather designated weapons dispersion data from DoD departments and approved Foreign Allies (that have approval from the COR). Whenever the data is proven to be deficient to calculate WDZs, the Contractor shall document the deficiencies in the monthly status report. The COR will review and provide the necessary data and/or allow the Contractor to use modeling and simulation techniques to calculate WDZs. The Contractor shall deliver to the COR the weapons data and methodology used to develop a WDZ in accordance with the delivery schedule.

4.3.4.8 The Contractor shall present problems, resolutions and suggestions in the monthly status report with its recommendations, courses of action, and time constraints, in accordance with the delivery schedule.

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Compiled data from DoD departments and approved foreign allies.

In addition, when data is insufficient to calculate a WDZ develop methodology, a new WDZ

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Annually as defined in

WBS

5 days to correct errors and resubmit

Error free upon second submission.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Problems, resolutions, suggestions for WDZ

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Monthly in the monthly status report;

5 days to correct errors and resubmit

Error free upon

4.3.4.9 The Contractor shall acknowledge receipt of all WDZ problems, suggestions, and communications from the COR in one working day. The contractor shall respond with a proposed way ahead no later than 5 working days after receipt. The Contractor shall maintain a record of these activities that can be reviewed by the COR upon request and shall be provided at the scheduled quarterly reviews, in accordance with the delivery schedule.

4.3.4.10 The Contractor shall update and maintain the WDZ Tool desktop version.

4.3.4.11 The Contractor shall deliver regression test plan results to the COR for review and approval, at every Quarterly PMR, in accordance with the delivery schedule.

4.3.4.12 The Contractor shall ensure that WDZs developed will generate three-dimensional WDZs for single and composite multi- weapon releases including:

(1) terrain profile, (2) weapon trajectories, (3) broached/porpoising ordnance, ricochets, (4) fragmentation, and (5) explosive effects that include the capability of using terrain to mitigate the effects of broaching/porpoising or ricochet. The Contractor shall develop and integrate new WDZs into the baseline when provided by the COR.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Acknowledgm ent of Government communicatio n

Via email Not later than one working day after Government notice

100% timely Acknowledgment

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Regression test plan results

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Quarterly as defined in

WBS

5 days to correct errors and resubmit

Error free upon

4.3.4.13 The Contractor shall deliver “Data Cubes,” in accordance with the delivery schedule, that define weapon trajectories and ricochets while utilizing Circular Error Probable for Training (CEPt) Polygons and incorporate range scores and Joint Munitions Effectiveness Manual (JMEM) (Applicable Document 7.0.11) Air-to- Ground Weaponeering System (JAWS) JMEM tables for Collateral Damage/Fragmentation Arcs.

4.3.4.14 The Contractor shall deliver all design documentation and methodologies used to develop any weapons data cubes, in accordance with the delivery schedule.

4.3.5 RMTK End User refresher and advanced training:

4.3.5.1 Annual RMTK users/training working group. The Contractor shall conduct 80hrs of RMTK Users’ training at a Government designated and provided site for no more than 50

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Data cubes MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM and an extension executable form as baseline.

As developed and defined in the WBS

5 days to correct errors and resubmit

Data cubes are error free on second resubmission.

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

WDZ

specification volumes

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Annually at least 45 days before end of

POP

10 days to correct errors and resubmit

Error free upon second submission.

Design documents

As required and defined in the WBS;

10 days to correct errors and resubmit

Error free upon trainees annually when directed by the COR. The RMTK program training will utilize specific RMTK information concerning lessons learned and new developments from the past year. The training days shall adhere to normal business hours at the location provided (i.e. 8 AM to 5 PM).

4.3.6 Help Desk Support:

4.3.6.1 The Contractor shall provide subject matter expertise for “tier 3” high level help desk tech support for the WDZ tool and it shall be limited to COR designated personnel only. Tier 3 is for handling the most difficult or advanced WDZ programmatic problems as provided by the COR (i.e., not limited to, computer crashing on a particular part of the WDZ program, internal failure of the program, error messages that can’t be easily derived, weapons anomalies). The Help Desk shall be available 0800-1700 Eastern Time. The Contractor shall record and resolve trouble calls in accordance with the delivery schedule.

4.3.7 WDZ FMS Training:

4.3.7.1 For this requirement, the contractor will execute COR approved virtual or in-person WDZ training for the customer. For in-person training the contractor must be able to provide hardware assets with pre-loaded software. Training will consist of 3 total days of instruction for no more than 10 students utilizing media and practical application methods which also includes setting the customer up with delivered tools on the customers own workstations. For virtual training, the customer will supply their own hardware and licensing for the periods of instruction. Periods of instruction will only utilize the customer’s specific delivered WDZ tool.

4.3.8 Foreign Military Sales:

For FMS, the weapons data shall be in database format, tables from existing country policy, or weapons manufacturer data and may in some cases need to be derived by the SME for inclusion in the existing RMTK suite of tools. The danger zone data shall be in a database format and/or converted to a format that will allow the RMTK to utilize the data to create

DELIVERAB

LE

FORMAT DATE

REQUIRED

ACCEPTABLE

QUALITY

LEVEL

Help desk support metrics

MS Word Document, Power Point or Excel Spreadsheet/Worksheet (for Windows) via email or on CD-ROM

Monthly in the monthly status report

5 days to correct errors and resubmit

Error free upon specific foreign danger zones.