Attachment_2_End-Use_Monitoring_EUM_Application.pdf

Attachment 2

End-Use Monitoring EUM Application

12 Feb 2016

About the End-Use Monitoring Application

The EUM Application has the following major areas of functionality:

Secure internet access for SCOs and Host Nation (HN) Inspectors

Inventory and disposition records by defense article, country, and combatant command

Prepare a “Planned” inventory report, based on the previous inventory date for each defense article and an established frequency of inspection

A “Delinquent” Inventory report based on past due inspections

An item inventory “History”

Ad Hoc reporting capability, including the ability to save queries for reuse

Input capability to establish and correct inventory records

Ability to confirm each item of inventory by serial number

The ability to defer a scheduled inspection when a particular item may be deployed or otherwise unavailable for inspection

The ability to attach notes (for historical purposes) to aid in subsequent inventory inspections by successors

The ability to adjust, deplete, or transfer inventory records

The ability to trace the origin of an item to the USG program that furnished it

A reconciliation report that collects all enhanced EUM articles from Defense Security

Application Management System (DSAMS) and compares to what is in SCIP-EUM

An application that stores labor hours and cost associated with performing EUM functions

Provision of reference tools and the latest EUM policy and procedural guidance.

The EUM application currently reads and/or writes to 21 data tables. The application resides in

35 Java gadgets and is organized into six sections with a total of 34 possible major screens. It was initially estimated to be about 580 function points in size, but has likely expanded as additional features have been added to the original design.

The data to be populated in the EUM database includes military articles provided as far back as

1950 via the (then active) Military Assistance Program (MAP).

About the EUM data collection process

The critical elements to be obtained for each article in the database are the type of weapon, serial number, associated Military Articles and Services List (MASL) nomenclature, and type of program under which the article was transferred to what country. This data, and particularly serial numbers, are not held centrally in DoD. Rather they are distributed among various system commands, program offices, and manufacturers. Consequently, a major outreach effort is required to obtain the needed data. This must be approached on a weapon-by-weapon, manufacturer-by-manufacturer basis.

About EUM User Support

Due to the constant rotation of military personnel, both SCIP-EUM and EUM, SCOs, Combatant

Commands, customer countries, and others involved in the program need to be enrolled and educated. This requires a combined effort by DSADC and the DSCA EUM program. The SCIP program office handles user enrollment and permission establishment. The EUM program must educate users on the nature of the EUM program and their responsibilities. Since participants are distributed around the world, these processes must generally be conducted remotely, relying heavily on e-mail to accommodate the time zone differences. This task may require occasional travel, sometimes overseas.