What was said
What this says
As at Fri 9 Oct 2026Kamal Hussein agreed to Thursday morning for the rostering connector session and warned that client codes differ between systems, with older ones in the control room. He will send runbook notes.
Ask: Laura Penhaligon wants connector sessions one system at a time: rostering, control room, then finance. She also asked how client codes are held.
Customer view: Kamal is cooperative but careful. He will not change a live system without a backout plan, and he will check whether IT must open anything up.
Next: code mismatches may need a mapping across connectors, and the control room codes are the likeliest problem.
The thread
Updated 9 Oct 26Messages
- Laura Penhaligon 9 Jun 2025 15:10Hi Kamal, Thanks for your time on the call earlier. As promised, I'm writing to get the onboarding sessions into the diary so we don't lose momentum after kickoff. What I'd like to do is start with a working session on the connectors, beginning with the rostering system, then the control-room system, then finance. For each one I'll need you (or whoever looks after that system day to day) on the call, plus read-only credentials set up in advance so we can check the first load together. Could you let me know which mornings or afternoons suit you later this week? I'm flexible, but I'd rather not run two systems in the same session, as it's easier to see what's going on if we take them one at a time. One other thing: before we connect anything, it would help to have whatever you have on how client codes are held in each system. I'd like to understand whether the same client has the same code everywhere, or whether we'll need a mapping. No rush on that last point, but the earlier I see it the fewer surprises we'll have. Best, Laura
- Kamal Hussein 9 Jun 2025 17:45Hi Laura, Thanks. Rostering first makes sense to me. Tuesday afternoon or Thursday morning would both work this week. I'd prefer Thursday morning if you can, as it gives me a day to set up the read-only access properly. I won't change anything on a live system without a backout plan, so I'd rather not rush that part. On client codes: they are not the same everywhere. Which client code is that, is a question I get asked a lot. Rostering and finance mostly agree, but the control room has some older ones. I'll write down what I know and send it over. Most of it is in the runbook already, so I'll check that is current first. I'll check the connector requirements on our side too and tell you if anything needs IT to open up first. Kamal
- Laura Penhaligon 10 Jun 2025 12:03Hi Kamal, Thursday morning is fine, I've put a placeholder in for the rostering session and I'll send the invite shortly. Two hours should be plenty for the first system. The runbook extract would be very useful, thank you. Don't worry about tidying it up, I'd rather see it as it stands. If the control room codes are a mess, better we know now. If IT need to open anything up, just tell me what they need and I can send a short note explaining what we connect to and how, which might save you some back and forth. Speak soon, Laura