1 / 15

Global Force Management Data Initiative GFM DI Mr. George Sprung Joint Staff J-8

Purpose/Agenda. PURPOSE: To brief Global Force Management Data Initiative (GFM DI) to the OPSDEPS and to obtain a position on data accessAGENDA: Problem and SolutionLeadership GuidanceGFM DI Approach, Schedule, StatusIssues

lavonn
Download Presentation

Global Force Management Data Initiative GFM DI Mr. George Sprung Joint Staff J-8

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


    1. Global Force Management Data Initiative (GFM DI) Mr. George Sprung Joint Staff J-8/MASO 22 February 2008 The overall classification of this briefing is UNCLASSIFIED

    2. Purpose/Agenda PURPOSE: To brief Global Force Management Data Initiative (GFM DI) to the OPSDEPS and to obtain a position on data access AGENDA: Problem and Solution Leadership Guidance GFM DI Approach, Schedule, Status Issues & Recommendations Data Access Data Compilation Funding Way Ahead

    3. GFM DI Org Server CONOPS

    4. Problem Answering seemingly simple questions regarding the disposition, status, capabilities, and associated costs of the Department’s units and equipment can take months 30+ DoD force structure systems evolved separately…cannot easily exchange data Command relationships are seldom documented ADCON, COCOM, OPCON not always captured Deployments and activities still recorded manually The reason for the many different systems is because each service has its own responsibilities for sourcing and managing their piece of the pie. Not all systems need to be able to easily interchange data. Command Relationships are documented within Deployment orders (or the like). The issue may be that existing data bases do not have the required field to show command relationships associated with the unit's current mission. The reason for the many different systems is because each service has its own responsibilities for sourcing and managing their piece of the pie. Not all systems need to be able to easily interchange data. Command Relationships are documented within Deployment orders (or the like). The issue may be that existing data bases do not have the required field to show command relationships associated with the unit's current mission.

    5. GFM DI: A Critical Enabler of the Solution Electronic representation of authorized force structure Visible, accessible, understandable, and trusted across DoD for effective and efficient force management Uniquely identifies billets (authorized by law), crews, equipment authorization, and chain-of-command links Enables integration of data from disparate sources Provides a common format for representing force structure authorizations across DoD personnel, readiness, planning, and finance systems This appears to be a good thing as long as it is not "editable" across DOD.This appears to be a good thing as long as it is not "editable" across DOD.

    6. Strategic Planning Guidance, Mar 04 Joint Planning Guidance, Jun 04 Quadrennial Defense Review, Feb 06 Joint Planning Guidance VII, Jun 06 The CJCS with USD (P&R) will provide the SecDef a plan to make force structure authorization data visible and accessible by Sep 07 and address the resources to reach full operational capability by Oct 09 DoDI 8260.03 Aug 06, Organizational Force Structure Construct for GFM Directs documenting force structure using the GFM Information Exchange Schema Program Decision Memorandum III, Dec 06 Services fund and complete GFM DI force structure authorization data by the end of FY 08 GFM DI Implementation Plan briefed to DAWG 9 Mar 07, DepSecDef approved 26 Mar 07 – update DAWG Fall 07 Capability Development Document for GFM DI Increment 1 -JROCM signed 28 Jan 08 Leadership Guidance

    7. “Authorized” versus “On-Hand” Currently, within the Marine Corps, we only report readiness to the BN or SQDN level. Data beyond that point is not monitored or is account for when a percentage of the unit deploys to form part of a task-organized force. I think this is something the Marine Corps needs to consider. Is there value to be gained in having our lowest level combat formations report an individual readiness assessment? Currently, within the Marine Corps, we only report readiness to the BN or SQDN level. Data beyond that point is not monitored or is account for when a percentage of the unit deploys to form part of a task-organized force. I think this is something the Marine Corps needs to consider. Is there value to be gained in having our lowest level combat formations report an individual readiness assessment?

    8. GFM DI Schedule

    9. GFM DI – IOC Status The Marine Corps is the only service that hasn't accomplished "something". Have there been any dates identified within FY08?The Marine Corps is the only service that hasn't accomplished "something". Have there been any dates identified within FY08?

    10. Proposed DepSecDef Access Policy Memorandum Access to force management data is a vital element of the Global Force Management Data Initiative, the Defense Readiness Reporting System, and a host of current and future force management, planning, financial, analytical, and readiness systems. To enable these systems and transformational processes, the Services, Joint Staff, Office of the Secretary of Defense, and the Combatant Commands shall save their force management data within the Department down to the individual billet, crew, and crew vehicle levels. Access control of force management data is delegated to the Undersecretary of Defense for Personnel and Readiness in conjunction with Chairman of the Joint Chiefs of Staff. Guidance and delegations established in this memorandum shall remain in effect until superseded by governing DOD issuances. Does "access control" also account for permissions for viewing and manipulating data? Note. Personnel status does not equate to Combat readiness. Does "access control" also account for permissions for viewing and manipulating data? Note. Personnel status does not equate to Combat readiness.

    11. Access to Data Issue Force Management, Personnel, Readiness, Command Control, and Financial Systems require data at the billet level Discussion DoDD 8320.02, “data assets shall be accessible to all users in the DoD except where limited by law, policy, or security classification” DoDI 8260.03 Force structure is the central theme for integrating data within the DoD DoD Components shall make the Organization Server data visible, so that authorized users can discover data through search services DoD Components shall ensure only [Org Server] data is used for any force structure representation in other automated systems DoDI 7730.64 requires Components to report to the billet level

    12. Access to Data – Component Positions USA, USMC, and USAF plan to document to the billet level, but share at the UIC level and/or UTC level USSOCOM only supports sharing force management data on a need to know basis and with USSOCOM context USJFCOM agrees to share data -- requests USD(P&R) and CJCS roles and responsibilities be clearly defined JS, OSD, USN, USTRANSCOM, USSTRATCOM, USCENTCOM, USEUCOM, USNORTHCOM, USPACOM, and USSOUTHCOM agree to share data down to the billet level

    13. Data Compilation Issue Exposing the total authorized force structure in a net-centric environment creates potential for operational security concerns Discussion Preponderance of force structure is treated as unclassified Data currently exists in multiple unclassified systems – GFM DI enables “one stop shopping” for authorized DoD users Blanket classification would impact existing unclassified systems New paradigm requires risk assessment to balance accessibility and security Classification is important when discussion missions and combat effectiveness/readiness.Classification is important when discussion missions and combat effectiveness/readiness.

    14. Funding Issue Compliance with JPG VII, dtd Jun 06 and PDM III, dtd Dec 06 Discussion OSD – Certifies no funding issues…compliant with JPG VII/PDM III JS – Certifies no funding issues…compliant with JPG VII/PDM III USA – Certifies no funding issues…compliant with JPG VII/PDM III USN – Certifies no funding issues…compliant with JPG VII/PDM III USAF – Certifies no funding issues…compliant with JPG VII/PDM III USMC – Certifies no funding issues…compliant with JPG VII/PDM III OUSD(I) – Acknowledges new requirement…reprogramming MIP funds

    15. Way Ahead Obtain a unified military position on data access Continue to monitor progress of Component Org Servers—document a representative piece of each Service force structure authorization data in accordance with GFM DI specifications and present to the JROC Provide an update to the Deputies Advisory Working Group Conduct an operational security assessment in accordance with the Interim Guidance for Development of the Force

    16. Questions?

More Related