DOD concurred with this recommendation. In June 2017, DOD published Chairman of the Joint Chiefs of Staff Manual (CJCSM) 4301.01, which provides guidance for integrating OCS into established planning processes during deliberate, crisis action, and theater campaign planning. Specifically, CJCSM 4301.01 requires each Service Component in conjunction with the Joint Task Force OCS Integration Cell to record OCS and contractor management observations, insights, lessons and lessons learned. The Manual further requires the Joint Staff to consolidate lessons learned from the service components and to submit them to the Joint Lessons Learned Information System and the contracting OCS communities of practice. By taking steps to identify the roles and responsibilities of the service components in collecting OCS issues, DOD is better positioned to plan for the use of contractor support, as recommended.
DOD concurred with our recommendation. Subsequently, on November 14, 2018, the Department of the Navy issued OPNAV Instruction 3020.12,’Planning for Operational Contract Support.’ This instruction prescribes policy, responsibilities, and requirements for supporting OCS for joint and naval operations, and implements the Office of the Secretary of Defense OCS policy contained in DOD Directive 3020.49 and DOD Instruction 3020.41. By taking steps to identify OCS roles and responsibilities, the Navy is better positioned to plan for the use of contractor support, as GAO recommended. Additionally, the Marine Corps published Marine Corps Regulations Publication 4-11H and Marine Corps Order 4200.34, which outline OCS roles and responsibilities as well as expectations and methods of capturing OCS lessons learned. Specifically, Marine Corps Regulations Publication 4-11H, which was issued in February 2016, is a multi-Service publication that focuses on unit-level tactics related to OCS staff organization and capabilities. The Publication also contains an overview of Service unique theater support, external support and systems support contracting capabilities. Marine Corps Order 4200.34, which was issued in September 2016, contains instructions on personnel, operations, and logistics germane to the Marine Corps’ Contingency Contracting Force Program. Finally, in August 2016, the Department of the Air Force published Air Force Instruction 64-105, which outlines OCS roles and responsibilities. The Instruction also lays out procedures for preserving OCS lessons learned and disseminating the information collected from after action reports to the component headquarters within the Air Force. By taking steps to identify OCS roles and responsibilities, the military services are better positioned to plan for the use of contractor support, as GAO recommended.
DOD concurred with our recommendation. As of September 2020, DOD has taken steps to focus OCS training to all planners, including those outside the logistics directorate. In December 2015, the Joint Staff J7 certified the Joint OCS Planning and Execution (JOPEC) course of instruction for Joint training. The Joint Staff, per this training certification, is working with the Joint Deployment Training Center and the Joint Force Staff College to provide student administrative and course catalog support for future JOPEC training. In August 2020, OSD officials stated that they have secured funding for development of a new, online strategic-level OCS course, which they plan to develop, test, and field in 2021. Finally, OSD officials said that the updated OCS instruction will also address training for planners beyond the logistics directorate; officials anticipate the instruction being issued in late 2020. We will continue to monitor these efforts and this recommendation will remain open at this time.
DOD partially concurred with this recommendation. In April 2017, officials from the Office of the Deputy Assistant Secretary of Defense for Program Support reported the department decided against creating a ‘joint proponent’ for OCS issues. Rather, the course of action chosen was to designate the Joint Staff (J4) as the OCS focal point and the Under Secretary of Defense (Acquisition, Technology, and Logistics) as the Principal Staff Advisor. Officials stated that the Joint Staff (J4) will serve as the focal point for integrating OCS issues from the Joint Lessons Learned Program and into DOD processes and procedures. In June 2017, DOD published the Chairman of the Joint Chiefs of Staff Manual (CJCSM 4301.01), which provides guidance for integrating OCS into established planning processes during deliberate, crisis action, and theater campaign planning. More specifically, CJCSM 4301.01 delineated roles and responsibilities for the Joint Staff (J4) to include assisting combatant command staffs in resolving OCS problems and identifying critical joint OCS capability deficiencies. We believe these actions meet the intent of our recommendation.
DOD concurred with this recommendation. In November 2015, DOD reported that it had created an OCS community of practice in JLLIS as a central repository of OCS documents, announcements, observations, best practices, and issues. According to Joint Staff officials, the Joint Staff (J-7) and Joint Staff (J-4) established an OCS community of practice in JLLIS in late 2015. The OCS community of practice is intended to allow organizations or users with similar interests, responsibilities, issues, and concerns to readily communicate and share information. Equally important, the community of practice can be used to support sharing, collaboration, and the exchange of information to facilitate the lesson learned process. Furthermore, for its forthcoming Operational Contract Support: Joint OCS Lessons Learned Guide, the Joint Staff (J-4) established an OCS label in JLLIS by creating a standard format for observation titles in the system to enable rapid search and retrieval of the OCS data. By taking steps to improve the functionality of JLLIS for sharing OCS lessons learned, DOD is better positioned to systematically track and share OCS lessons learned department-wide, as GAO recommended in March 2015.