Presentation is loading. Please wait.

Presentation is loading. Please wait.

JOQ Overview. Problem Statement DoD develops and maintains redundant authorization and reporting hierarchies for EBusiness applications –Distribute and.

Similar presentations


Presentation on theme: "JOQ Overview. Problem Statement DoD develops and maintains redundant authorization and reporting hierarchies for EBusiness applications –Distribute and."— Presentation transcript:

1 JOQ Overview

2 Problem Statement DoD develops and maintains redundant authorization and reporting hierarchies for EBusiness applications –Distribute and maintain access –Consolidate reporting Currently each application hierarchy developed and maintained separately –Duplicate maintenance efforts –Differences in reporting – hard to compare data across sources DODAAC widely used as an identifier, but changes not well handled by applications Reporting of actions in FPDS-NG complicated by inability to maintain historical hierarchies –Further complicated by transition from DODAAN to DODAAC in 2004 (except DoN) and by ongoing reorganizations

3 Example of contract chain of authority changes over contract lifecycle* SECArmy ASA (ALT) AMC CECOM (W15P7T) Contract W15P7T-08-C-9999 And mods Chief of Staff CELCMC Chain of Command at Award Contract transferred to Aberdeen SECArmy Aberdeen (W91ZLK) ACA Northern Region Modification P0xxxx changes Procuring Office Army Realigns Aberdeen contracting office under MEDCOM *This does not imply any known or planned changes to any specific contract or agency SECArmy AMC Chief of Staff MEDCOM Aberdeen (W91ZLK) Army Realigns contracting under ASA (ALT) SECArmy AMC ASA (ALT) MEDCOM Aberdeen (W91ZLK) Modifications And closeout

4 JOQ Objectives Common cross reference for hierarchical reporting by: –Procurement –Resource Management –Requiring organization Aligning various authority structures (e.g DODAAC, CAGE) using OUID as a key Control access to applications using –Standardized functional role descriptions where possible –Limited unique or system-peculiar roles Enable mapping of EDIPI to functional role and organization authorities to facilitate access control

5 Assumptions Use current FPDS hierarchies as a starting point –Procurement –Command Initial focus on roles involved in writing and modifying contracts, issuing purchase cards Later phases to cover post-award and other processes

6 Tasks – Phase I Simulate OUIDs (assigning JOQIDs) for organizations issuing purchase cards –Map hierarchical relationships –Capture appropriate identifiers and tie to appropriate point in hierarchy Simulate OUIDs for organizations using FPDS –Map hierarchical relationships –Include procurement, finance/budget, requisitioning –Capture appropriate identifiers and tie to appropriate point in OUID hierarchy Explore how much standardization can be achieved in functional roles –PCOLS, FPDS Map functional roles to hierarchical nodes Develop a system interface to allow use of JOQ by other systems

7 Outcomes Hierarchy management –Purchase Card –eSRS –FPDS Standardized role based access –Multiple applications Automate infrastructure and reduce manpower resources for system administration Enable deployment of PCOLS, resulting in smoother transition to SMARTPAY2

8 Change Approval Process DAASCJOQ Pending Changes Service contacts NotifiedFile with Updates and Adds (Procurement Flag) JOQ Pending Changes Service Contact reviews and verifies changes Service Contact accepts and updates changes Step I: Step II:

9 Site Selection In AIM (or other system): Air Force Army Navy ODA AMC ATEC MEDCOM NGB SMDC COE CENTCOM Gulf Region Great Lakes & Ohio River Mississippi Valley North Atlantic Northwestern Other Pacific Ocean South Atlantic South Pacific Southwestern Central (W917B) Contracting Office (W916QW) Southern (W917BK) Northern District (W917BE) Where am I? Chief of Staff ASA (ATL)

10 “Can’t Find Home” Process AIMSJOQ Service Rep NotifiedCapture Name, Contact, Service, and Description JOQ Researches Issue Provides Person with correct location Querying System: Service Representative: Location Finder Notification Updates Hierarchy Or

11 JOQ OUID AIM Emma Data Mining OUID 1.OUID 2.JOQ ID 3.DoDAAC 4.UIC 5.Ordering Codes 6.Organization Name + Name Alias DoDAAC to AOPC JOQID Identifies 5 (Army/AF) or 6 (Navy) levels; PCard unique link to banks Active, Inactive, Closed History Tables DAASC Procurement Indicator/DODAAC Joint Organization Query Logical Architecture Increment 1 * Existing GEX Map/Feed Future User Access is throughsystems SA= Service Administrator Access PURCHASECARDPURCHASECARD SA


Download ppt "JOQ Overview. Problem Statement DoD develops and maintains redundant authorization and reporting hierarchies for EBusiness applications –Distribute and."

Similar presentations


Ads by Google