1. SPOT ES OUTREACH 4/6/2017 Splash Screen Participant Arrival
General Greetings
Background if Presenter is Introduced by Conference Host
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

2. SPOT ES OUTREACH
4/6/2017
The Synchronized Predeployment and Operational Tracker Enterprise Suite (SPOT ES)
Overview
Introduce SPEAKER(S)
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

3. Agenda SPOT ES and Operations SPOT ES an Evolving Tool For The Future
SPOT ES OUTREACH
4/6/2017
Agenda
SPOT ES and Operations
SPOT ES an Evolving Tool For The Future
SPOT ES and Policy
SPOT ES Phases
SPOT ES Access and Capabilities
JAMMS
TOPSS
SPOT ES Integration
SPOT ES Future Enhancements
SPOT ES Resources
Business Rules & Processes/Best Practices
Address any facility logistics
Address any support
Thank Hosts
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

4. SPOT ES OUTREACH
4/6/2017
SPOT Enterprise Suite
A single, joint enterprise system on a Service Oriented Architecture (SOA) employed for:
the management, tracking and visibility of contractors accompanying U.S. forces overseas and contingency operations.
capturing movement and location information about operating forces, government civil servants, and government contractors in specified operational theaters.
providing dynamic, ad hoc reporting by putting the power of data reporting and analysis in the hands of the analyst.
The Department of Defense has designated SPOT as the joint Web-based database1 to assist the CCDR in maintaining awareness of the nature, extent, and potential risks and capabilities associated with contracted support in support of contingency operations, humanitarian or peacekeeping operations, or military exercises designated by the CCDR. As such, SPOT:
• Serves as the central repository for up-to-date status and reporting on contingency
contractor personnel.
• Tracks contract capability information for all DoD-funded contracts supporting contingency
operations, humanitarian or peacekeeping operations, or military exercises
designated by the CCDR.
• Provides by-name accountability of DoD-funded contingency contractor personnel
and other personnel as directed by USD(AT&L) or by the CCDR.
• Contains minimum contract information necessary to establish and maintain accountability
and visibility of contractors and contract capabilities for all contracts awarded
to support contingency operations, external and systems support contracts and contracting
activities.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

5. OPERATION BENEFITS OPERATION NEEDS
SPOT ES OUTREACH
4/6/2017
Planning and Results
Plan missions and logistics Provide Situational Awareness (SA) Provide personnel accountability Support legal investigations involving personnel Determine contract compliance (e.g. use of Government Furnished Services) Execute Search missions (e.g. finding lost/missing personnel)
Capture and monitor activities related to tracking the movement of contractor, government civilian, and military personnel in target AOR (e.g. CENTCOM) Enable validation of the registration data against SPOT enrollment data Facilitate the accountability of non SPOT persons to be tracked and associate accurate valid registration data
OPERATION BENEFITS
OPERATION NEEDS
About SPOT
SPOT provides a standardized front-end user interface for use by defense contractors, government agencies and the military and generates Letters of Authorization (LOAs) as a part of the deployment process. SPOT generates digitally signed LOAs with a unique SPOT barcode to comply with Homeland Security Presidential Directive 12: Policy for a Common Identification Standard for Federal Employees and Contractors.
SPOT supports system integration with authoritative data sources, such as FPDS-NG for contracts and DMDC for personnel, to validate user-entered information and increase the qual­ity of system data. With data uploaded from JAMMS, SPOT allows verification of a person’s identity in theater, tracks movements, and pro­vides theater commanders up-to-date visibility into contractor assets and capabilities.
Combatant Commander (CCDR) primarily includes geographic combatant commanders (GCC) – U.S. Central Command (CENTCOM), U.S. European Command (EUCOM), U.S. Pacific Command (PACOM), U.S. Southern Command (SOUTHCOM), U.S. Northern Command (NORTHCOM), and U.S. African Command (AFRICOM).
It also includes U.S. Special Operations Command (SOCOM) when assigned to a Joint Operational Area (akin to the GCCs) and U.S. Joint Forces Command (JFCOM) in their training mission. These CCDRs have authority to approve contractor “entry”, establish deployment requirements, and provide government furnished services to contract personnel as authorized.
CCDRs provide and consume SPOT information. .
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

6. SPOT ES: The Evolving Application
SPOT ES OUTREACH
4/6/2017
SPOT ES: The Evolving Application
Four components NOW comprise SPOT ES:
SPOT NIPRNet – SPOT deployed on the Non-secure Internet Protocol Router Network
SPOT SIPRNet – SPOT deployed on the Secure Internet Protocol Router Network
JAMMS – Joint Asset Movement Management System
TOPSS – Total Operational Picture Support System
SPOT is a program within the Business Transformation Agency’s Defense Business Systems Acquisition Executive (DBSAE) directorate.
SPOT NIPR
SPOT SIPR
JAMMS
The Joint Asset Movement Management System (JAMMS) is an information technology application developed to capture movement and location information about operating forces, government civil servants, and government contractors in specified operational theaters.
TOPSS
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

7. Background: Policy IAW DoDI 3020.41
SPOT ES OUTREACH
4/6/2017
Background: Policy IAW DoDI
Provide Leader Awareness of Contractor Footprint in their Area Of Responsibility for Contingency and Force Protection Planning
Provide Leader Visibility of Capabilities within AOR
Provide Full Accountability
Provide Audit Type Capability for Contracted Assets
Provide Leaders Awareness Of Contractor Footprint In His Area Of Responsibility For Contingency and Force Protection Planning
“… information shall be used to assist planning for the provision of force protection, medical support, personnel recovery, and other support. It should also provide planners an awareness of the nature, extent, and potential risks and capabilities associated with contracted support in the area of responsibility (AOR).
Provide Leaders Visibility of Capabilities within AOR
“…database shall provide a central source of CDF personnel information and a summary of services or capabilities provided by all external support and systems support contracts.”
Provide Full Accountability
One significant sub-category of contingency contractor personnel, called contractors deploying with the force (CDF), is subject to special deployment, redeployment, and accountability requirements and responsibilities. It turn, SPOT helps to “Maintain by-name accountability of all CDF personnel and contract capability information in a joint database.”
Provide Audit Type Capability for Contracted Assets
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

8. SPOT: Meeting the Needs Past, Present, and Future
SPOT ES OUTREACH
4/6/2017
SPOT: Meeting the Needs Past, Present, and Future
DoD
DoDI
U. S. Army to DoD wide
Other Departments and Agencies
Memorandum of Understanding
Department of Defense
DoS
USAID
SPOT was designated by the Office of the Secretary of Defense (OSD) as the system of record in accordance with DoDI , Contractor Personnel Authorized to Accompany the U.S. Armed Forces, which requires a single joint database for logistics, operations, planning, and reporting of deployed contractor status to government and defense contractor stakeholders.
The environment of US contingency operations without a military draft, with a cap on the number of military and an expanded national strategy that includes nation building and reconstitution require more contractors at a higher ratio of contractor to military than ever before in US history. As of early 2008, at least 190,000 private personnel were working on US-funded projects in the Iraq theater according to a Congressional Budget Office (CBO) survey. That means that for each uniformed member of the US military in the region, there was also a contract employee – a ratio of 1 to 1. In the Korean conflict, the ratio was 2.5 uniformed personnel for each contractor while in Vietnam, the comparable figure was 5 to 1.
SPOT has expanded from a U.S. Army-only system to a DoD-wide system and is currently being implemented in other Government agencies. Both the Department of State (DoS) and the United States Agency for International Development (USAID) began using SPOT within the second quarter of FY08.
The Departments of Defense (DOD) and State (State) and the U.S. Agency for International Development (USAID) have relied extensively on contractors to support troops and civilian personnel and carry out reconstruction efforts in Iraq and Afghanistan. While recognizing the benefits of using contactors, GAO and others have noted the risks and challenges associated with relying on contractors. To help increase contractor oversight, the National Defense Authorization Act for Fiscal Year 2008 directed DOD, State, and USAID to sign a memorandum of understanding (MOU) on contracting in Iraq and Afghanistan that identified a database to track information on contractor personnel and contracts performed in the two countries. In their July 2008 MOU, the agencies designated the Synchronized Pre-Deployment and Operational Tracker database (SPOT) as their system for tracking the required information. GAO's testimony addresses how contractor personnel and contract information can aid agencies in managing contracts and the status of SPOT's implementation. It is drawn from GAO's ongoing and prior contingency contracting work. This work involved meeting with agency officials, including those in Iraq, and reviewing agency documents. GAO obtained agency views on previously unreported information, which the agencies generally agreed with.
DOD, State, and USAID now require their contractors in Iraq to enter personnel data into SPOT, but only DOD and State require their contractors to do so in Afghanistan. A critical factor in prompting the use of SPOT was DOD's requirement that contractor personnel have SPOT-generated letters of authorization (LOA) to, among other things, enter Iraq or Afghanistan.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

9. SPOT ES Phases Register personnel in central repository
SPOT ES OUTREACH
4/6/2017
SPOT ES Phases
Enrollment
Movement Capture
Data Aggregation
Reporting & Data Analysis
Register personnel in central repository
Screen & verify against authoritative data sources (e.g., DMDC, ABIS, IAFIS, etc)
Issue credentials
Capture biometrics information (if applicable)
Capture scans of credentials with deployed devices at target locations
Capture key data elements to track movement data
Aggregate movement transactions from scanning devices
Reconcile based on data quality rules
Associate Card ID with enrollment record
Consolidate into central repository
Generate standard and ad hoc reports such as:
Movement transactions by location (country, city, building), ID type, personnel type
Movement transactions in last seven days
Movement transactions for specific person
Leverage advanced analytics for data analysis
Movement Capture : Identify in theater staffing resources
Search for deployed personnel by specific skills and experience
Filterable by country, location, contract, contracting company, clearance, nationality, etc.)
Reporting & Data Analysis : Plan for logistics and operations
Analyze historical movement records to develop metrics and trends for consumption of GFS/GFE
Apply metrics and trends to planned deployments in order to determine future consumption of GFS/GFE
Reporting & Data Analysis : Analyze movement information
Standard reports and dashboards filterable by common views (COCOM, country, personnel category, contracting company, contract, date/time, person name, nationality, source system, etc.). Ability to drill down from summary information to detailed information.
Ad hoc reports based on common views (COCOM, country, personnel category, contracting company, contract, date/time, person name, nationality, source system, etc.)
Acronyms:
DMDC - Defense Manpower Data Center
ABIS – Automated Biometrics Identification System
IAFIS - Integrated Automated Fingerprint Identification System
USAID - United States Agency for International Development
COCOM - Combatant Command
EDIPI - Electronic Data Interchange Personal Identifier
DBA - Defense Base Act
GFS/GFE – Government Furnished Services/Equipment
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

10. SPOT: User Groups and Roles
SPOT ES OUTREACH
4/6/2017
SPOT: User Groups and Roles
Three (3) Primary User Groups (Roles)
Contractor Company
Company Administrator
Government Organization
Government Administrator / Government Authority
Contracting Community (Government)
Contracting Administrator / Contracting Officer (KO)
Each role limits access to data and functionality in SPOT
Each role has specific credentials for which you can register
Ex: you have an AKO login, but you want the ability to access SPOT using a software certification
Contractor Company
Contractor companies (CCs) include entities hired by U.S. federal organizations to provide known or potential contingency contractor personnel. CCs provide information into SPOT that
assists the GA, CCDR, and CC in maintaining visibility and awareness. SPOT improves the management of contingency contractor personnel to ensure timely and accurate
access to government-furnished support from predeployment to redeployment. CCs must perform the following contract-mandated activities in support of SPOT and the DoD Contractor Management mission.
Note: Pre-Contract Registration Activity
Assign a company administrator who is trained on SPOT to act on behalf of the CC and ensure timely, accurate inputs and maintenance of information in SPOT. SPOT registration process is available at
Company Administrators (CAs) include entities hired by U.S. federal organizations to provide known or potential contingency contractor personnel.
CAs populate information into SPOT relative to employees of their company. This assists the GAs and CCDRs in maintaining visibility, accountability and awareness of the contractor personnel deployed to a contingency.
CAs are beneficiaries of data in SPOT as it improves the management of contingency contractor personnel to ensure timely and accurate access to government-furnished support from predeployment to redeployment
The cognizant government authority (GA) will be either military or government civilian and refers to U.S. federal entities responsible for managing contingency contracts and their contractor
personnel. The GA makes decisions on behalf of the federal government and ensures contract compliance to facilitate effective management of contractors. For the DOD, the individual serving as the GA and their delegated roles and responsibilities will be determined by the contracting officer. For non-DoD agencies, the individual will be determined in accordance with Agency policy and procedure. GA may include multiple organizations (Military Departments, DoD agencies, Joint Theater Support Contracting Commands, non-DoD federal agencies) and individuals (e.g., contracting officers, contracting administrators, contracting officer representatives). GAs are both providers and consumers of the information maintained in or accessed by SPOT. GAs will perform the following activities in support of SPOT and the DoD Contractor Management
mission.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

11. SPOT: Capabilities by Roles
SPOT ES OUTREACH
4/6/2017
SPOT: Capabilities by Roles
Government Administrator
Government Authority
Authorize LOA
(Government Authority only)
Initiate LOA
Add / Maintain Persons
Initiate Deployment
Add / Maintain Contract
Maintain Deployment
Information
Company Administrator
Add / Maintain Persons
Initiate Deployment
Initiate LOA
Add / Maintain Contract
Maintain Deployment
Information
Add / Maintain Contract
Approve LOA
(Contracting Officer only)
Contracting Administrator
Contracting Officer
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials 11

12. SPOT Produced Letter of Authorization
SPOT ES OUTREACH
4/6/2017
SPOT Produced Letter of Authorization
GAO has reported extensively on the management and oversight challenges related to using contractors in contingency operations and the need for decision makers to have contract and contractor personnel information as a starting point to address these challenges. The lack of such information limits agency planning efforts, increases costs, and introduces unnecessary risk. For example, GAO previously determined that by not considering contractor resources when developing an assistance strategy for Afghanistan, USAID's ability to make informed resource allocation decisions was impaired. Similarly, it was estimated in 2006 that DOD's lack of visibility on what government support contractors were entitled to cost an extra $43 million in Iraq as the government provided them free meals and a food allowance. Many of GAO's past recommendations focused on improving agency officials' ability to obtain contract and contractor personnel information.
A unique barcode is generated for each LOA
JAMMS scans contractor location data which is uploaded to SPOT records
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

13. SPOT: NIPRNet and SIPRNet
SPOT ES OUTREACH
4/6/2017
SPOT: NIPRNet and SIPRNet
SPOT is deployed over two DoD networks, NIPRNet (unclassified) and SIPRNet (classified). The networks are information conduits allowing access to the contractor identity and movement data stored in SPOT.
The distinction between the two deployments of SPOT is the classification of data available over the networks.
As SIPRNet is a secure network, contractor identification and movement-related data classified as Secret will be provided across SIPRNet only
The Secret Internet Protocol Router Network (SIPRNet) is a system of interconnected computer networks used by the United States Department of Defense and the U.S. Department of State to transmit classified information (up to and including information classified SECRET) via the TCP/IP protocol suite in a completely secure environment. It also provides services such as hypertext document access and electronic mail. As such, SIPRNet is the DoD’s classified version of the civilian Internet together with its counterpart, the TOP SECRET and SCI Joint Worldwide Intelligence Communications System, JWICS. The NIPRNet is used for unclassified information.
The “look and feel” of the SPOT application will remain the same regardless of the network. However, there will be differences in login procedures and data availability between SIPRNet and NIPRNet. These differences are explained in this Quick Guide. Differences between SPOT NIPRNEt and SIPRNet While the SPOT application will look and operate identically on NIPRNet and SIPRNet, the differences that users will see are in the data displayed in SPOT. Data classified as Secret will be displayed in SPOT SIPRNet, including:
• Classified contract numbers
• Names of foreign nationals
• Identifying contractors to units
This will mean that values entered into a field in SPOT NIPRNet will be different than the same field in SPOT SIPRNet. The business rules will be the same; however, the values will be populated with secret data in SPOT SIPRNet. SPOT data from NIPRNet will be migrated to SPOT SIPRNet and refreshed on a daily basis.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

14. JAMMS (Joint Asset Movement Management System)
SPOT ES OUTREACH
JAMMS (Joint Asset Movement Management System)
4/6/2017
JAMMS captures movement and location information about operating forces, government civil servants, and government contractors through data collection points established in specified operational theaters.
JAMMS data collection points are established at:
Dining Facilities (DFACs)
Vehicle Issue Points
Ports of Debarkation (APODs/SPODs)
Billeting facilities
Department of State (DoS) facilities
Central Issue Facilities (CIFs)
Medical locations
Morale, Welfare, and Recreation (MWR) locations
Convoy staging areas
Fuel Points
Personnel moving through a JAMMS data collection point present a form of identification that the system recognizes. A JAMMS operator scans the ID card, and information about the cardholder is stored electronically. Information captured by JAMMS is uploaded daily to SPOT.
JAMMS data collection points can recognize Common Access Cards (CACs), Real-Time Automated Personnel Identification System (RAPIDS) card barcodes, SPOT-generated LOAs, Defense Biometric Identification System (DBIDS) identification cards, Federation for Identity and Cross-Credentialing Systems (FiXs) cards, Biometric Identification System for Access (BISA) cards, and some driver’s licenses and passports.
The Joint Asset Movement Management System (JAMMS) is an information technology application developed to capture movement and location information about operating forces, government civil servants, and government contractors in specified operational theaters. JAMMS data collection points are established at Dining Facilities (DFACs); Aerial Ports of Debarkation (APODs); Central Issue Facilities (CIFs); Medical locations; Convoy staging areas; Fuel Points; Vehicle Issue Points; Billeting, Department of State (DoS), and Morale, Welfare, and Recreation (MWR) locations. JAMMS has rapidly evolved to scan a wide range of identity media, such as the Common Access Cards (CACs), Real-Time Automated Personnel Identification System (RAPIDS) card barcodes, Synchronized Pre-deployment and Operational Tracker (SPOT)-generated Letters of Authorization (LOAs), Defense Biometric Identification System (DBIDS) identification (ID) cards, Federation for Identity and Cross-Credentialing Systems (FiXs) cards, Battlefield Information System Application (BISA) cards and some driver’s licenses and passports
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

15. SPOT and JAMMS Integration
SPOT ES OUTREACH
4/6/2017
SPOT and JAMMS Integration
JAMMS Operations
Personnel movement data collected, data assembled into an encrypted batch file for upload
SPOT builds a JAMMS record, matches movement data to an individual, creates an exception report if individual not registered in SPOT
Users and external systems query SPOT for movement data; SPOT provides data requested
JAMMS Equipment
JAMMS consists of a laptop computer, two barcode scanners, and additional equipment in the kit. JAMMS is a stand-alone system that has no external network connectivity at this time. File transfers are accomplished using a CD or DVD and an Internet connection through an external machine.
This JAMMS User Manual (UM) identifies JAMMS components and provides the user with instructions on how to assemble the JAMMS equipment, begin scanning personnel credentials and subsequently to upload files to SPOT.
JAMMS is issued with a Panasonic Toughbook laptop computer (model CF30) that supports the JAMMS application software. Additional JAMMS equipment includes a hand-held barcode scanner, CD/DVD-drive, surge protector, world power travel adapter, notebook security cables with a combination lock, and a carrying case.
Capability developed by DMDC to track contractor personnel movements within the AOR
Stand alone laptop application; no direct communications link for transfer data
Mar 07 – 17 JAMMS systems to CENTCOM AOR; Nov 07 / May 08 – additional 220 JAMMS units being fielded
JAMMS stationed at installation choke points: APODs, DFACs, convoy points
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

16. Scenario: SPOT and JAMMS
SPOT ES OUTREACH
4/6/2017
Scenario: SPOT and JAMMS
Access Control Systems
Scans card/credential
Checks for authorization
Logs entry/exit
ID Management Systems
Register personnel info
Issue credential cards
Aggregates movement data
Diverse technologies
SPOT Application
Integrated contractor personnel visibility
Personnel
Information Standard
SPOT User
Base Access Point
CAC
Clearance
Other
Attributes
Contact
Identifier
Biographic
JAMMS accepts multiple forms of credentials and aggregate personnel & movement data to provide to other systems.
JAMMS has rapidly evolved to scan a wide range of identity media, such as the Common Access Cards (CACs), Real-Time Automated Personnel Identification System (RAPIDS) card barcodes, Synchronized Pre-deployment and Operational Tracker (SPOT)-generated Letters of Authorization (LOAs), Defense Biometric Identification System (DBIDS) identification (ID) cards, Federation for Identity and Cross-Credentialing Systems (FiXs) cards, Battlefield Information System Application (BISA) cards and some driver’s licenses and passports.
SPOT System
DBIDS

Base Access Point
Movement
Data
Personnel
Data
SPOT Database
Integrated data
Personnel and movement
BISA
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

17. SPOT Administrator: Dashboard Report
SPOT ES OUTREACH
4/6/2017
SPOT Administrator: Dashboard Report
All Example Reports derive artificial data from the test or training SPOT instance.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

18. Report Example: JAMMS Summary
SPOT ES OUTREACH
4/6/2017
Report Example: JAMMS Summary
All Example Reports derive artificial data from the test or training SPOT instance.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

19. SPOT: Total Operational Picture Support System (TOPSS)
SPOT ES OUTREACH
4/6/2017
SPOT: Total Operational Picture Support System (TOPSS)
Provides Dynamic, Ad Hoc Reporting on a Service Oriented Architecture (SOA)
Puts power of data reporting and analysis in the hands of analysts to make immediate and effective decisions
Use reports and dashboards to monitor visibility and analyze trends
Proven Scalability to adapt to emerging requirements and data sources
Secure, SIPRNet- based, NIPRNet-ready Business Intelligence Solution (ATO 2009)
ATO (Authority to Operate) 2009 – For DISA for SPOT ES (TOPSS) on SIPRNet
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

20. TOPSS: Features Summary
SPOT ES OUTREACH
4/6/2017
TOPSS: Features Summary
Reporting
Ad-Hoc report creation of multiple report styles
Dynamic, suggested entities and attributes
Role-Based Security filters report styles, elements, and results
Integration
Web Service based integration to consumer applications
Integrates with external authoritative data sources
Automated system administration, performance monitoring, and system auditing
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

21. TOPSS: Virtual Data Entities
SPOT ES OUTREACH
4/6/2017
TOPSS: Virtual Data Entities
TOPSS builds a catalog of virtual data entities that extend across data sources
Consolidate into a single virtual entity
Data can be held in multiple data tables
Data in multiple databases
Analysts and Reporters do not need to be concerned about those sources and how to consolidate them
For Example: Virtual Person Record
Consolidation of Personal Records and Data, home and work information, skills, and locations where they have been
Presented as a single, simple entity to analysts and users
Skills
Home
Work
Location
Person
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

22. TOPSS Report Types Reports Catalog Pre-generated, Standard Reports
SPOT ES OUTREACH
4/6/2017
TOPSS Report Types
Reports Catalog
Provides a starting point and reference of previously built reports
System provided
Reports by other users
Pre-generated, Standard Reports
Preconfigured reports run and filtered for individual users
Ad Hoc Reports from Templates
Multiple Report Layouts supported, including:
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

23. Report Example: Geospatial Analysis
SPOT ES OUTREACH
4/6/2017
Report Example: Geospatial Analysis
Report on Location-Based Data
Locations coordinates displayed on map
Use standard map display capabilities, such as Google Maps, Google Earth, etc.
SIPR Maps via NGA
Geospatial Queries
Provide Point Locations for entities on a map
Any location based coordinates and data
Geometric Queries
Show time-based locations and movement of entities
Perform Proximity queries (what entities were “near” each other?)
All Example Reports derive artificial data from the test or training SPOT instance.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

24. Report Example: Time Series Analysis
SPOT ES OUTREACH
4/6/2017
Report Example: Time Series Analysis
2009/06
2009/07
2009/08
2009/09
2009/10
2009/11
2009/12
2010/01
2010/02
2010/03
Historical and data trend analysis
Data extrapolation into future trends
Multiple forecasting methodologies:
Straight Line
Polynomial
Exponential
Logarithmic
Plus Up
Rolling Average
Historical Pattern
All Example Reports derive artificial data from the test or training SPOT instance.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

25. Report and Data Security
SPOT ES OUTREACH
4/6/2017
Report and Data Security
Data elements filtered and masked by user rights and permissions
Users can only generate authorized reports
Some users are only allowed summary reporting capabilities, but cannot drill into detailed data
Users can only see authorized data entities
Some users can see usage activities, system and data metrics, etc
Users can only see authorized data results
Some data filtered by user groups – COCOM users only see data relevant to their COCOM; Government agencies only see data related to their agency, etc.
Some data filtered or masked for privacy concerns (SSN, EDIPI)
All data access is fully audited and archived for absolute traceability
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

26. SPOT ES Data Integration

27. SPOT ES OUTREACH
4/6/2017
SPOT version 7.1
SPOT will ensure that contract numbers for DOD contracts follow consistent formatting rules
Additional verbiage added to LOA concerning the GFSs
Customer Management Center contact information updated
SPOT will allow entry of a Theater Business Clearance number if required on the contract and task order
The process of digital signing of the LOA will be streamlined with fewer screens
SPOT will provide advance notice of deployments nearing their end dates
End dates will be configurable
SPOT will notify affected users that their deployments and/or LOAs will be canceled or closed
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

28. SPOT PM: Jeffrey Taylor,
SPOT ES OUTREACH
4/6/2017
Support Resources
SPOT
SUPPORT
Customer Management Center (CMC) at: or
Chat at
SPOT
PROGRAM OFFICE
SPOT PM: Jeffrey Taylor,
/ DSN
SPOT
oUTREACH
For communications and conferences:
SPOT ES Points of Contact
For technical questions, contact the SPOT Help desk:
Comm (CONUS/OCONUS):
Chat:  
SPOT
TRAINING
For additional training, please contact us at:
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

29. SPOT ES Resource Center
SPOT ES OUTREACH
4/6/2017
SPOT ES Resource Center
The SPOT-ES Resource Center Web site contains resources for the SPOT-ES community, including:
FAQs: Frequently Asked Questions regarding SPOT-ES components
Alerts: System Outages, Updates, and other bulletins regarding SPOT-ES component availability.
Document Library: Quick Guides, Training Handbooks, and other reference material available for download
Training: Training Schedule, Course Descriptions, and links to request training
Registration: Links to register for SPOT-ES components
Help Desk: Live 24/7 customer support
The URL is:
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

30. Defining Business Rules and Processes
Some tasks, such as entering contract information, can be completed by more than one type of SPOT user
Establishing organizational information early can make using SPOT simpler for all categories of users
Defining and communicating who should do what can help eliminate delays
Ensuring that users are registered appropriately and organizational hierarchy has been defined in SPOT can save time
Establishing organizational consistency in areas such as how contract numbers are entered and exactly which organizational names are used can also help streamline processes. Once LOAs and deployments are initiated, changing information such as organizational alignment and contract numbers can be a very complex and time-consuming process.

31. SPOT Best Practices can Save Time
Carefully defining key business rules can help prevent delays later in the process, for example:
What types of users are responsible for what tasks?
What organization each user should be associated with?
What role each user should be assigned?
Who are the appropriate sponsors?
Once an LOA is approved, information cannot be changed on it without revoking it and starting over
Taking care to ensure that all information on LOAs is correct before approving it can save time
Contracting officers can define the default Government Furnished Services for a contract, doing so when the contract is added reduces the need to assign these services to each LOA individually
If a foreign national does not require a CAC, an official FIN may not be needed; other unique identifiers may be entered as an alternative

32. Questions? ReCap and Summary
SPOT ES OUTREACH
4/6/2017
Questions and Answers
Questions? ReCap and Summary
Questions
Any instructor “knowledge checks”
Evaluation
Next Steps
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

33. Summary: SPOT ES Benefits
SPOT ES OUTREACH
4/6/2017
Summary: SPOT ES Benefits
SPOT provides:
Central, integrated source of information
Aids in planning
Single standard user interface
A standard tool for the functional management of CAAF
Reduces manual data entry through integration with related industry and government authoritative systems
Automated movement tracking via JAMMS
Digitally signed LOAs with unique SPOT barcodes
Complies with Homeland Security Presidential Directive 12 Policy
SPOT Advantages
Provides a central, integrated source of information to assist Defense Contractors and Combatant Commanders in planning force protection, medical support, personnel recovery, and logistics support of contractors who accompany the U.S. Armed Forces
Presents a single standard user interface for Government and industry to locate and correlate any individual to contract information and points of contact for routine actions and to manage emergency situations in an area of operation
Provides a standard tool for the functional management of contractors accompanying the force that reduces manual data entry through integration with related industry and Government authoritative systems
Provides movement tracking through an automated interface with Joint Asset Movement Management System (JAMMS)
Provides near-real time connectivity of scanning technologies with SPOT system providing up-to-date visibility into contractor assets and capabilities by leveraging existing authoritative systems and DoD business processes to identify deployed contractors and their movements
Generates digitally signed Letters of Authorization with unique SPOT barcode to comply with Homeland Security Presidential Directive 12 Policy for a Common Identification Standard for Federal Employees and Contractors\Provides a standardized document required for contractors to carry while on travel, streamlining the process by automating KO signature through PKI encryption
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials

34. SPOT ES OUTREACH 4/6/2017 Splash Screen.
Thank you to hosts, participants, etc.
File:Cordero V1.0
Operations > Training > Training Materials > Briefing Materials