1 / 11

Joint Organizational Query (JOQ) System Update

Joint Organizational Query (JOQ) System Update. Defense Procurement and Acquisition Policy. Background.

sopoline-madden
Download Presentation

Joint Organizational Query (JOQ) System Update

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. Joint Organizational Query (JOQ)System Update Defense Procurement and Acquisition Policy

  2. Background • Historically, the Department of Defense (DoD) and the greater defense community have utilized numerous methods to identify organizations and determine authorities designated to those organizations. These include, among others, the Department of Defense Activity Address Code (DoDAAC), the Unit Identification Code (UIC), Tax Identification Number (TIN), and Data Universal Numbering System (DUNS) Number. Over time, numerous system and department changes have caused several misalignments of data. • Introduction of the Organizational Unique Identifiers creates additional challenges

  3. Organizational Identifiers DODAAC UIC OUID CAGE DUNS TIN

  4. Problems • Issuance of contracts with destination acceptance assigned to places that can’t do it • Contractors • Remote deployed units • Inaccurate aggregation of procurement reporting by middle tiers, e.g. Army Materiel Command • Inaccurate traceability of funding authority by organization

  5. Needs • A better process for maintaining hierarchy of organizations with procurement authority • Ability to identify whether an organization can issue MIPRs • A funding hierarchy to be able to track funding organizations • Required for small business reporting to Congress and for internal controls • Ability to identify whether a location can perform acceptance

  6. Way Ahead • Developing proposals to add parent DODAAC and specific roles to DODAAD data • Seeking advice on best approach

  7. Purpose • The Joint Organizational Query (JOQ) system was created to capture the authoritative hierarchical command structures • JOQ will support the business processes of the Department by enabling access, translation, mapping, and storage of authority hierarchical data. • This process will enable a common reference for reporting by procurement pre-award, post-award, dispersing, and funding. • By utilizing the already existing organizational hierarchies, JOQ strives to reduce conflicts occurring due to the multiple purposes served by particular organization identifiers and hierarchies and support management of the Total Force and Operational Contract Support (OCS) • Command (OUID) • Procurement • Financial (Funding and Pay)

  8. JOQ Capabilities • The Joint Organization Query (JOQ) capability will provide a common cross reference, mapping, and management tool for procurement reporting by DoDAAC and other organization identifiers, including OUID. • By enabling roll-up reporting across authority levels and by procurement, funding, payment, and other hierarchies, JOQ will facilitate functional audits and business requirements and provide a family tree structure for identified organizations. • As an example, JOQ will enable greater visibility and reporting of procurement via the Government Purchase Card, connecting the procurement authority (down to the cardholder) to the organizational command structure.

  9. JOQ Architecture

  10. DISCUSSION

More Related