The DPAS system's security is based upon a tier structure that is aligned to the business layer of the application supported.  For example:  In WM, the tiers are LP, Region, Site and Warehouse.  The IO's security forms for these 4 tiers are based upon the organization's business's name for those tiers.  As DPAS is currently designed, the business names aligned with a tier can be changed without the IOs or DPAS Security being notified.  Organizations must be able to modify the business name to support reorganizations / realignments.  As an example:  LP 1 has a region called "East".  Management decides it would better reflect what it supports if it is renamed to "Atlantic".  When the name changes, the IOs and DPAS Security must work in concert to adjust the security forms to match the name change.  The proposed improvement is to provide the IO and DPAS Security with a notification whenever there is a name change / realignment.  The notification could be via an email. Another option might be to add  these tier changes to the DPAS Security dashboard where they can track the open action to have the forms updated until.  Once the updates have been made, they can close the action.

The DPAS system's security is based upon a tier structure that is aligned to DPAS business layer. Security forms are based upon the tier's business's name.  For example:  In WM, the tiers are LP, Region, Site and Warehouse.  With a notification, DPAS Security can work with the IO to receive a new roles form to add additional access or delete the account if no longer required.

As the DPAS customers and users increase there are more changes occurring that require improved tracking.

 

Accounts with no available access can be addressed more quickly.

 

Frequency: Monthly