Summary
This article describes BPM’s go-live process, including final validation, communication, and post-deployment monitoring. It ensures all changes are effectively implemented and communicated to the campus community.
Body
The Implementation & Go-Live phase manages the promotion of approved configurations to the production Workday environment and ensures all impacted users are informed, trained, and supported.
Purpose
The purpose of this article is to describe how BPM coordinates go-live activities, validates successful configuration deployment, and ensures campus communication and documentation updates are completed.
Go-Live Preparation
Prior to production deployment:
- Verify successful UAT completion and approvals.
- Review configuration readiness with WSS.
- Validate training and KBA updates.
- Confirm all affected roles have appropriate security and access.
Use the Go-Live Checklist Template to ensure all items are complete.
Communication & Documentation
BPM collaborates with University Relations to ensure timely and accurate communication to stakeholders:
- Draft communication templates summarizing change impacts and effective dates.
- Coordinate Newswire announcements or targeted departmental messages.
- Link to updated KBAs, SOPs, or reference guides in the communication.
Monitoring & Validation
Following deployment:
- Monitor Workday transactions using process reports.
- Validate routing, notifications, and completion times.
- Address any post-launch feedback or issues immediately.
- Confirm the process is functioning as intended.
Outputs
- Successful deployment to production
- Updated KBAs and documentation
- Campus communication published
- Post-launch validation report