CASPER
CASPER (*Centralized* *Automated* *Sort* *Processes* *Evaluation* and *Reporting* tool) is the end-to-end change management tool for network design change requests across geographies; bringing near real-time visibility to all upcoming changes, establishing reliable communication between FCs and transportation, auditing and remediating launch configuration errors, and ensuring the appropriate information is available for FC leaders make informed decisions.
- We surface near real-time visibility of all network design change requests across geographies.
- We consolidate information needed in an easy to use format for teams affecting and affected by the network design management process.
- We standardize network design constraint models used to evaluate change requests.
- We create a direct feedback loop to the network planning teams to ensure no changes requested violate established FC constraints.
- We reduce friction to ensure all changes are approved, rejected, and executed quickly.
- How do we maintain uniqueness among each change request uploaded?
- Until TORCH is launched, all change requests are created using SIMs. Hence we do not have any unique identifier to identify each change request. To resolve this issue we create a hash of FC name, request type, parent sort name, stacking filter, sim link with respect to a change. Ideally this combination should remain static for a change request and should avoid collision. Hash is made case-insensitive i.e the case of the input letters doesn't change the uniqueness of hash.
Any opinions in this post are those of the individual author and may not reflect the opinions of AWS.