Headquarters U.S. Air Force
Integrity - Service - Excellence
OUID to
RC/CC Link
Note: RC/CC = Responsibility Center /Cost Center (RC/CC) codes.
Mark Novitski
SAF/FMPT
1
Agenda
Background
Definitions
OUID AF Implementation
OUID AF Implementation to track $$
Next Step
Action Items
2 Integrity - Service - Excellence
Background
OSD (P&R) Functional Perspective
Track all resources by Organization to the billet
OSD directive
“Who’s on First??”
SAF/XC__ AF POC (OSD P&R perspective)
Database on GCSS housed @ Gunter (ELSG managed)
AF/A3/5 Global Force Management (GFM) role in OUID?
AF/A1 role in OUID?
How do we take a GFM perspective and relate to $$ tracking
OUID not equal to RC/CC
RC/CC not equal organization
GFM expectation? Reporting in the next 10 years?
3 Integrity - Service - Excellence
GFM Note
Grab a reference:
AIR MOBILITY COMMAND INSTRUCTION 65-605 (AMCI65-605)
4 MAY 2007, Incorporating Change 1, 29 August 2007
Financial Management; Responsibility Center/Cost Center (RC/CC) Codes
Purpose. This instruction prescribes the Responsibility Center / Cost Center (RC/CC)
codes used in the Air Force accounting system. These codes identify resources and
costs for all major commands (MAJCOMs) and their subordinate units across the
Air Force. This instruction provides definitions, use, and coding required to achieve
the correlation of programming, budgeting, and accounting data. RC/CC codes are
used to identify a specific responsibility center that carries out the mission, conducts
a major line of activity, or produces one or more outputs.
Note: This instruction does not apply to National Guard Bureau (NGB) and Air Force Reserve Command (AFRC) units.
Challenge: Compare/contrast a GFM DI Organizational Element (OE)
and a USAF Responsibility Center.
A GFM DI OE is an aggregation point w/ a leader. In other words, the underlying
precept for the GFM DI data is leadership and chain of command (leadership).
4 Integrity - Service - Excellence
GFM - OUID
GFM DI – Enables integration of data across domains and
systems
Makes force structure visible, accessible, and understandable
across DoD for effective and efficient force management
Uniquely identifies organizational element, or OE (doctrine,
billets, crews, garrison force, and augmentation).
equipment authorization, and chain-of-command links
Provides the common reference for force structure across
Department of Defense (DoD) Warfighter, Intelligence and
Business domain information systems
Personnel, readiness, planning and finance systems, etc.
OUID
An OUID is a unique GFM DI identifier for an organization
OUIDs provide GFM DI force structure information across the
DoD Enterprise
“…facilitate machine-to-machine exchange of data …”
5 Integrity - Service - Excellence
GFM Note
Force Management Identifier (FMID) and
Organizational Unique Identifier (OUID).
The GFM DI semantics are described via DATA MODEL, not a flat
table. The Data Model is called the GFM Information Exchange
Data Model, or GFMIEDM, from which the GFM XML Schema
Definition, XSD, is derived and is an augmented subset of the Joint
C2 & Consulting IEDM, or JC3IEDM). The GFMIEDM has 12
objects, each identified with an FMID. If an object represents an
OE then its FMID is also called its OUID.
OEs are the nodes (or “boxes”) in an org tree and are only a part of
the GFM DI semantics. The other major part is the “Command
Structure, or the links of the org tree and are based on the DOD
command and support relationships (from the levels of authority).
6 Integrity - Service - Excellence
RC/CC
The RC/CC data element was designed to directly
relate to an organization.
Today many RC/CC’s used relate to non-org values
(e.g. Function, Program, Project)
We need to return to the RC/CC directly relating to
the organization
RC/CC not a data element in SFIS
Part of OUID alias
Organization Unique ID (OUID)
SFIS data element
Directly relates to an organization
Hierarchal structure
Up to AF
Down to Billet
7 Integrity - Service - Excellence
RC/CC
Issues
Other than org uses of the RC/CC
Track Congressional Add’s
Civ Pay
Contracts
Tuition Assistance
Old requirement – 1 RC/CC to 1 PEC
Still valid?
Legacy BQ MART Edits BQ? Master Appropriation Reference Table (MART)
BQ data not going into DEAMS Defense Enterprise Accounting and Management System
FC 6b, 6c, 64 (to ECSS) Expeditionary Combat Support System
Dept 97 funds
75% of RC/CC’s do not relate to org
8 Integrity - Service - Excellence
Definitions
9 Integrity - Service - Excellence
PASCode
8 character A/N field
Typically used in personnel
Displays on civilian SF-50’s
Displays on Mil Pers UMPR
Position 1 & 2 id location/servicing pers ofc
Position 3 & 4 identify MAJCOM
Position 5 thru 8 identify organization
Relates to an Mil or Civ position number
UMD POS NR: 0000039413 (civ)
CAID POS NR: 000422500N (civ)
AU13F1MT AU(Andrews), 13 (HAF), F1(FM), MT(FMP)
10 Integrity - Service - Excellence
OUID
An OUID is a 64-bit binary data element
The OUID is built upon an Enterprise-wide (DoD)
Identifier (EwID) Allocation Scheme
16 character Alpha/Numeric field => Hexadecimal Version;
can also be displayed as a 20 digit number between 0 and 18 billion-billion (2**64 – 1).
Randomlygenerated “dumb” number not
hierarchical => not technically random; prefix is 1 come, 1 served.
st st
7 Org servers, 1 OUID registry (OUID
Phonebook) – alias maintained
72060561860348089 = 375th Compt Sqdn/FM @ Scott AFB
11 Integrity - Service - Excellence
OUID
AF Org Server access
Machine to machine
Web services
No plan for individual look-up
OUID Registry access
Now - Request excel from ELSG
Mar 2011 ????
OUID alias’
How do we load them in the registry
Many to 1; 1 to many
72060561860348089 = 375th Compt Sqdn/FM @ Scott AFB
12 Integrity - Service - Excellence
DODAAC
Probably not a player
13 Integrity - Service - Excellence
OUID AF Implementation
OUID currently available (Air Force) is at an
intermediate (organization) level (e.g. 375th
CS/FM)
How do we link down to the:
Sub organization (e.g. 375th CS/FMA)?
billet?
How do we link OUID to MAJCOM/NAF?
New ORG = New OUID
Process defined?
Responsibilities
Linking defined?
14 Integrity - Service - Excellence
OUID AF Implementation
Tracking $$
LinkOUID to RC/CC’s in OUID registry as
Alias's
Multiple OUID to RC/CC
Multiple RC/CC to Alias’s
How many alias's can be linked to one OUID?
Process to link RC/CC to OUID?
How do we link non org RC/CC’s to OUID?
Time Consuming Base Level effort
15 Integrity - Service - Excellence
FM Perspective - RC/CC
to OUID
Reviewing the current process and data required for
linking the OAC/OBAN/RCCC to PASCode,
Organizational Unique ID (OUID), and DODAAC (Which
One)
PASCode OUID
SF1LFPGQ 72060561860348089
65, YY, 300500
OAC, OBAN, RC/CC
DODAAC
Scott AFB, 375th Compt SQDN/FM (RC/CC’s go from 300500 thru 3005ZZ)
16 Integrity - Service - Excellence
Organization OUID
Up to AF
DoD
Military (O/E), Civilian, &
Contractor FTE’s depicted.
May be multiple levels
between 3 ltr and billet
AF
OUID ????????
PASCode N/A
RC/CC N/A NAF
OUID ????????
PASCode N/A
RC/CC N/A MAJCOM
OUID ????????
PASCode N/A
RC/CC N/A Wing Level
OUID ????????
PASCode N/A
RC/CC N/A
OSD’s understanding - the services Base Level CPS/FM
or DoD agencies will create the OUID: 72060561860348089
relationships to roll up the data PASCode SF1LFPGQ
RC/CC 300500
Integrity - Service - Excellence 17
Organization OUID
Down to Billet
Base Level CPS/FMA Billet (SSAN?)
Military (O/E), Civilian, &
OUID ???????? OUID ????????
Contractor FTE’s depicted.
PASCode N/A PASCode N/A
May be multiple levels
RC/CC 300510 RC/CC N/A
between 3 ltr and billet
May UMD ?????
Base Level CPS/FMF be
Billet
OUID ????????
OUID ????????
PASCode N/A
Base Level CPS/FM
OUID: 72060561860348089
PASCode N/A
RC/CC 300520
multi RC/CC N/A
PASCode SF1LFPGQ UMD ?????
RC/CC 300500 ple Billet
DODAAC ????? Base Level CPS/FMP
OUID ???????? levels
OUID ????????
PASCode N/A
PASCode N/A
RC/CC N/A
RC/CC 300540
UMD ?????
Billet
Base Level CPS/FMC OUID ????????
OUID ???????? PASCode N/A
PASCode N/A RC/CC N/A
RC/CC 300570 UMD ?????
Integrity - Service - Excellence 18
Other Considerations
Funds distribution using OUID
Reporting by OUID
OUID not in legacy
Not currently in CRIS
Next generation Data Warehouse
19 Integrity - Service - Excellence
OUID Discussion
SFIS Governance Board
Within AF
20 Integrity - Service - Excellence
Next Step
Understand
Ownership
Roles and responsibilities
Work processes
Work with ERP’s
Work Scott AFB
OUID to RC/CC relationships
Work OUID relationships down to Billet
Work OUID relationships up to AF
Work AMC bases
Work COCOM’s
21 Integrity - Service - Excellence
Action Items
22 Integrity - Service - Excellence
Questions
Integrity - Service - Excellence 23
Thank You!
Integrity - Service - Excellence