Excerpt |
---|
S&OCIT's current Systems & Operations Division, including NOC, Systems Engineering and Production Control: total effort is N relatively small to M weeks to understand the needs of Workday, decommission jobs, commission new integration jobs through Tidal, and prepare for support escalation for integration incidents. |
These notes are a result of CIT's brainstorming meetings about Workday on 4/12 and 4/13 2011.
Assumptions
- Some users may call the NOC and the NOC needs to know what to say, even if it is - call Workday's Workday’s help desk.
- Disaster Recovery is relevant because of the synching of systems. There are scenarios of one or the other systems being down long enough for routine synching to be interrupted. This will need analysis, documentation, and testing.
- Presumably someone is worrying about Workday's Workday’s DR plan and escrow or code.
- Keys for encryption of data will be escrowed.
- The Big Red Button process exists for issues with WorkDay/Cornell integrations.
- We don't don’t have any reason to expect CIT Prod Control is to run Workday Payroll jobs.
Tasks
- Assess, plan and decommission HR/Payroll jobs
- Create, document, automate, and test new Workday integration jobs
- Discuss, agree on, plan for and document NOC 's ‘s role in outage reporting
- Provide documentation, escalation paths, tools, training and expertise in troubleshooting after-hour Workday <-> CUintegration incidents
Open Questions
- Who is responsible for the PDF jobs that go to multiple HR/Payroll customers now?
- What are the escalation paths when integrations in and out of Workday fail and troubleshooting on both sides is needed. We need something contractual that deals with escalation paths, triage of pushing and pulling data, phone numbers, expected turn around time, ticketing system expectations.
- What kind of outage reporting is expected at Cornell at the NOC, if any? Because Workday is going to be coupled with PS and IDmgmt to support many core Cornell process incident reporting via the NOC may have many advantages than leaving the NOC oblivious of issues at Workday
- Decide on what kind of integration failure scenarios to design fault tolerance and monitoring for for the routine, automated integrations.
- What are requirements for test environments and procedures for testing integrations when either side change because of local upgrades respectively.
- If the HR/PY datamarts are to be rebuilt what is the timing and the hardware budget for that?
- What is the inventory of all payroll related jobs - and which jobs stay, which change? They do data transfers via FTP,Bank FTPs... Who is responsible for them in the future, including trouble shooting after hours?
- What is the expectation of the CIT Help Desk in terms of troubleshooting provisioning calls that include Workday or core HR/Payroll function calls. What basic steps would they expect to take in the event they get called?