There are three major use cases the hierarchy needs to solve:
- Push a complete version of the hierarchy to an external system
- Push changes/ additions/ deletions made to the hierarchy to an external system
- Provide the Procurement/ Grant specific parts of the hierarchy as of a specific date
Due to size of the PIEE hierarchy, the best way to provide this as a service should be researched. The hierarchy should be made exportable as a csv with the 5.11.1 release. If this is truly the best way to provide the whole hierarchy, then no changes should be needed.
Changes are going to be made to the hierarchy (currently spanning 35K groups and 55K DoDAACs) nearly every day. PIEE shall determine the best way to provide these updates to external systems so they can stay in sync with changes made in PIEE.
Provide an API to distribute changes to the procurement and grants DoDAACs in the hierarchy.
- The scope of this service is limited to the procurement DoDAAC changes.
- Other DoDAACs, Pay, Acceptance, Ship To, etc. are NOT in scope for this change.
When a change does occur to a procurement DoDAAC in the PIEE hierarchy, make that change available to consumers of the service.
-
Changes include:
- New Procurement/ Grant DoDAAC Added to Hierarchy
- Procurement/ Grant DoDAAC is moved from one group to another
Provide the ability to export the Procurement hierarchy (Groups and DoDAACs that manage Procurement DoDAACs) as of a specific date. For Example:
- System “X” requests a copy of the procurement hierarchy on Friday with an as of date of Monday
- A new DoDAAC was added on Wednesday
- The output should NOT include the DoDAAC that was added (or any other changes after 23:59 Monday)
Document |
Demo |
Doc |
Last Updated |
Notes |
Procurement Hierarchy API Overview |
|
|
August 2018 |
This is an overview of the Procurement Hierarchy API changes. |