DOD concurred with our recommendation and reported in August 2018 that life-cycle cost estimates for SPOT-ES are included in Select & Native Programming Data Input System for Information and Technology (SNAP-IT) and the DOD Information Technology Portfolio Repository. These estimates are updated annually, or more frequently if there are changes.
DOD concurred with our recommendation. In June 2019, WHS provided us with information that it cited as implementing the recommendation. WHS provided documentation that AT&L (now A&S) had developed a mechanism within TOPSS (the reporting module of SPOT-ES). WHS additionally provided documentation of use of this mechanism to track contractor performance of SPOT data entry, such as timeliness in reporting contractor arrival into theater. Therefore, the recommendation can be closed as implemented.
DOD concurred with our recommendation. In August 2018, the office of the Assistant Secretary of Defense for Logistics and Materiel Readiness reported that the requirement for registration in the Data Services Environment could not be completed because the capability is not funded by the Defense Information Services Agency and is no longer a DOD enterprise capability.
DOD concurred with our recommendation. In August 2018, the office of the Assistant Secretary of Defense for Logistics and Materiel Readiness reported that an update of DOD Instruction 3020.41 is in progress, and will include updated SPOT provisions. However, as of August 2020, the updated instruction had not been issued.
USAID has issued guidance on tracking contractor personnel, as statutorily required in the National Defense Authorization Act of Fiscal Year 2013, and as we recommended. Specifically, in June 2017, USAID issued “Data Collection for Contingency Contracting: A Mandatory Reference for ADS 300,” to enhance USAID’s ability to collect acquisition data related to contingency operations. This guidance identifies the Assistant Administrator, Bureau for Management (AA/M) as responsible for contracting data collection and report creation. Additionally , the guidance identifies eight statutorily required data elements to be collected, including the total number and value of contracts entered into, the total number and value of active contracts, identification of the extent to which contracts were entered into competitively, the total number of contractor personnel recorded in SPOT, contractor personnel performing security functions, and contractor personnel killed or wounded under any USAID contracts.
DOD partially concurred with our recommendation. DOD stated that it agreed to provide clarity regarding the purpose and use of JAMMS to improve the timeliness and reliability of JAMMS data, though it did not agree that such guidance could include direction on the number and location of JAMMS terminals and how frequently JAMMS’s data should be uploaded into SPOT-ES. DOD stated that it would revise language in DOD Instruction 3020.41, Operational Contract Support, to reflect in policy the requirement to use the entire SPOT Enterprise Suite (SPOT-ES), which includes JAMMS. DOD also stated that the combatant commander should establish the requirements for terminal quantities and locations and for data upload schedules based on operational needs in the relevant theater. We agreed with DOD that the combatant commands need flexibility based on operational requirements. In August 2018, the office of the Assistant Secretary of Defense for Logistics & Materiel Readiness reported that the update to DOD Instruction 3020.41 is in progress and will clarify information on the JAMMS capability. However, as of August 2020, the updated instruction had not been issued. Updated SPOT-ES Business Rules dated May 10, 2018 incorporate the role of JAMMS in maintaining visibility of contractor personnel.