joq overview l.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
JOQ Overview PowerPoint Presentation
Download Presentation
JOQ Overview

Loading in 2 Seconds...

play fullscreen
1 / 11

JOQ Overview - PowerPoint PPT Presentation


  • 210 Views
  • Uploaded on

JOQ Overview. 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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'JOQ Overview' - albert


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
problem statement
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
example of contract chain of authority changes over contract lifecycle
Example of contract chain of authority changes over contract lifecycle*

Chain of Command at Award

Contract transferred to Aberdeen

Army Realigns Aberdeen contracting office under MEDCOM

Army Realigns contracting under ASA (ALT)

SECArmy

SECArmy

SECArmy

SECArmy

Chief of Staff

ASA (ALT)

Chief of Staff

ASA (ALT)

AMC

ACA

AMC

AMC

CELCMC

Northern Region

MEDCOM

MEDCOM

CECOM

(W15P7T)

Aberdeen

(W91ZLK)

Aberdeen

(W91ZLK)

Aberdeen

(W91ZLK)

Contract

W15P7T-08-C-9999

And mods

Modification

P0xxxx changes

Procuring Office

Modifications

Modifications

And closeout

*This does not imply any known or planned changes to any specific contract or agency

joq objectives
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
assumptions
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
tasks phase i
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
outcomes
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
change approval process

Change Approval Process

Step I:

DAASC

JOQ

Pending

Changes

File with Updates and Adds (Procurement Flag)

Service contacts Notified

Step II:

JOQ

Pending

Changes

Service Contact reviews and verifies changes

Service Contact accepts and updates changes

site selection

Site Selection

In AIM (or other system):

Air Force

Army

Navy

ODA

Chief of Staff

ASA (ATL)

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?

can t find home process

“Can’t Find Home” Process

Querying System:

AIMS

JOQ

Location

Finder

Notification

Capture Name, Contact, Service, and Description

Service Rep Notified

Service Representative:

JOQ

Updates Hierarchy

Or

Provides Person with correct location

Researches Issue

slide11

User Access is through

systems

P

U

R

C

H

A

S

E

C

A

R

D

Joint Organization Query Logical Architecture

Increment 1

Data Mining

DAASC

Procurement

Indicator/DODAAC

SA

History

Tables

JOQ

AIM

SA

Future

  • DoDAAC to AOPC
  • JOQID
  • Identifies 5 (Army/AF) or 6 (Navy) levels;
  • PCard unique link to banks

OUID

  • OUID
  • JOQ ID
  • DoDAAC
  • UIC
  • Ordering Codes
  • Organization
  • Name
  • + Name Alias

OUID

OUID

OUID

Emma

Active, Inactive,

Closed

* Existing GEX Map/Feed

SA= Service Administrator Access