Lornefield Pensions Administration / BB-Demo – Kickoff
Callcompleted
Lornefield Pensions Administration: documents · 2023-04-05 11:00
Kickoff with Imogen Hartley and Craig Paterson. The workspace exists with no users or connectors. Order of connection agreed: calls, tickets, invoices. Craig wants advance notice of any change, and the invoices source needs Morag's written approval.
What was said
What this says
Current to 10 Oct 26Kickoff with Imogen Hartley and Craig Paterson. The workspace exists with no users or connectors. Order of connection agreed: calls, tickets, invoices. Craig wants advance notice of any change, and the invoices source needs Morag's written approval.
What happened: Tobias Renwick explained that the brain runs in Lornefield's own Snowflake account, with a read-only credential per source that Craig creates and can revoke. The admin console showed no users and no connectors.
Customer view: Craig wants to know before a refresh time shifts or a connector is reconfigured, not after. Imogen asked what happens if the helpdesk is changed unannounced.
Commercial: Daniel Okafor noted that Starter has a limit on connectors, so the order is deliberate. Craig makes most system changes himself, so he is the key person for keeping the brain loading.
Watch: The invoices connector depends on Morag's blessing and a written read scope. A source change made unannounced would stall records indexed.
Themes
Current to 9 Oct 26Theme
Kickoff and connector setup
Importance
neutral
Sentiment
positive
Voice
user
Who was there
BB-Demo
CRMmade from
Them
CRMmade from
Follow-up
Next steps
Current to 9 Oct 26- Tobias sends a written scope note for each source.
- Craig creates the read-only credential for the call recorder before the hands-on session.
- Daniel sends the written plan, and Imogen brings Morag in on the invoices note.
Risks
Current to 9 Oct 26- An unannounced change to a source system could stop a connector loading and stall records indexed.
- The invoices connector is blocked until Morag has the read scope in writing.
- Starter's connector limit means three sources use the allowance and choices must be deliberate.
Opportunities
Current to 9 Oct 26- Craig, the day-to-day administrator, is engaged and agrees the change-notice habit.
- Once calls, tickets and invoices are connected, the brain can combine them for relationship managers.
Transcript
Daniel Okafor NoneGood morning, everyone. Thank you for your time. Let me just check who's here. Imogen, Craig, and Tobias, I think I can see you.
Tobias Renwick NoneI'm here. Morning. Craig, I don't think we've spoken before, so a pleasure.
Craig Paterson NoneMorning. Aye, likewise. Just to flag, my audio's been a bit temperamental, so shout if I drop out.
Imogen Hartley NoneMorning, all. Craig is the one who'll live with this day to day, so I'd ask Tobias to pitch things at his level rather than mine.- Tobias Renwick NoneHappily. To begin, perhaps I should ask what your security and systems people will need to see, because that shapes how I explain the architecture.
- Craig Paterson NoneIn our case that's mostly me, plus a note for the trustees' side that Imogen has already seen. What I want to know is where the data sits, who can read what, and what touches our source systems.
- Tobias Renwick NoneThen I'll be precise. The brain is built and run inside your own Snowflake account. The data lands there, under your access rules, and nothing is stored in an account of ours. The honest answer to what touches your source systems is a connector for each, using a read-only credential that you create and that you can revoke at any time. The trade-off is that you carry the housekeeping of those credentials, but in return you retain control.
- Craig Paterson NoneThat's how I'd prefer it. Who creates the credential, me or you?
- Tobias Renwick NoneYou do. We tell you the scope we need and you create it. We never hold a password that you haven't issued and cannot withdraw.
- Daniel Okafor NoneAnd for context, the order of connection is calls first, then tickets, then invoices, as Imogen and I agreed. Starter has a limit on connectors, so we're choosing deliberately.
- Imogen Hartley NoneThe invoices one needs Morag's blessing, as I mentioned to Daniel. She wants the read scope in writing first.
- Tobias Renwick NoneOf course. I'll write a short scope note for each source, saying what is read and what is not. For the accounting system that'll be invoice headers and lines and nothing about bank details.
- Craig Paterson NoneRight. I've got the admin console open and I'll read out what it's showing. Workspace is created. Users, none yet. Connectors, none connected. So we're at the starting line, which is where I'd expect to be.
- Tobias Renwick NoneThat is exactly right. Daniel, would you take the next part, the timing?
- Daniel Okafor NoneYes. The plan from here is the first connector on the call recorder, then a settling period, then tickets, then invoices. We'd try to have the first source loaded within the first couple of weeks.
- Craig Paterson NoneCan I ask about change windows? What I don't like is finding out after the fact that something moved. If a refresh time shifts or a connector gets reconfigured, I'd like to know before, not after.
- Tobias Renwick NoneThat's reasonable and I'd treat it as a rule. The nightly refresh is designed to be complete by seven in the morning your time on business days. If we need to change when it runs, or change a connector, we tell you in advance and agree a window with you. I'd rather you had it in writing in the plan.
- Craig Paterson NoneAye, that'll do me. I'll keep an eye on it from my side as well.
- Imogen Hartley NoneThe real question for me is what happens if a source changes under us. Say the helpdesk is reconfigured by someone who doesn't know the brain is reading it.
- Tobias Renwick NoneA very good question, and the honest answer is that the connector will likely stop loading, and the symptom is that records indexed stop growing. We watch for that. But the better protection is a habit on your side, which is that Craig tells us before a system is changed. Then it's a planned adjustment, not an incident.
- Craig Paterson NoneThat I can do. It's usually me making the change anyway.
- Daniel Okafor NoneWhich makes you the most important person on this call, Craig, if I may say. How are you for time over the next fortnight?
- Craig Paterson NoneReasonable. Mornings are better. I've got a month-end that I can't move, but otherwise I can give it a couple of hours at a time.
- Tobias Renwick NoneThen I'd propose a hands-on session, just Craig and myself, next Wednesday afternoon, where we connect the first source live. Daniel may join if he's free.
- Daniel Okafor NoneI'll join if I can, and if not I'll read the notes. Let me close the loop on the next steps. Tobias sends the scope notes, source by source. Craig creates the read-only credential for the call recorder ahead of the session. Imogen brings Morag in on the invoices note. And I send everybody the written plan. Have I missed anything?
- Imogen Hartley NoneNo, that's right. Thank you all, I'm pleased we're underway.
- Craig Paterson NoneCheers, everyone. Regards.
- Tobias Renwick NoneThank you. Best.
Callsmade from