Working with your IT team and ERP partner
Our forward-deployed engineers work inside systems your IT team runs and around an ERP your partner may support. This page sets out who is responsible for what, how access is requested, how changes to the ERP go through your change control and who owns what.
Who is responsible for what
Section titled “Who is responsible for what”| Who | Responsible for |
|---|---|
| Your IT team | Your network, your devices and your security policy. Every account in your systems and what it can reach. Your change control. Day-to-day administration of the ERP. |
| Your ERP partner | The inside of the ERP: its configuration, the modules it ships with, customizations and upgrades. |
| Our engineers | The software around the ERP: the operations layer and the agent layer. They build it, release it and, during the engagement, run and monitor it. |
| Your workflow owners | How each workflow should work, and sign-off on changes to it. |
The line between us and your ERP partner is the edge of the ERP. Your partner configures the modules the ERP ships with. We build what the ERP does not cover, around it, and work alongside your partner.
How we attach to the ERP
Section titled “How we attach to the ERP”The ERP stays the system of record. We read from it and write to it only through interfaces it supports. In order of preference those are a supported API, database views or a read replica, file and EDI exchange, and screen automation as a last resort.
The Systems and Data Audit records which one each connection would use. Your IT manager or ERP administrator agrees to it before anything is built. Attaching to your existing ERP covers each option and the rules for writing back.
How access is requested
Section titled “How access is requested”- Our engineers send your IT manager a written request. It names the system, read or write, the engineer or agent that needs it, the reason and the end date.
- Your IT team creates the accounts: a named account for each engineer and a separate service account for each agent.
- Read access comes first. The Discovery Sprint needs read access to the ERP data and no write access at all.
- Write access is requested one workflow at a time, when that workflow is ready to write back. It covers only the transactions that workflow creates.
- Your IT team can disable any account at any time, without asking us.
Access and credentials has the full procedure, including offboarding.
How changes to the ERP are made
Section titled “How changes to the ERP are made”We build around the ERP, so much of the work needs no change inside it. Sometimes a workflow does need one: an account for the API, a database view, a field to hold a reference number, a change to an EDI map, a scheduled export. Then:
- Our engineers write the request: what is needed, why, what it touches, how to test it and how to undo it.
- The request goes through your change control, like any other ERP change.
- Your ERP administrator or your ERP partner makes the change. Our engineers do not change your ERP’s configuration.
- The change is tested together with the software that depends on it before either reaches production.
It works the other way too. Tell us before an ERP upgrade, or before a change to a field, a price list structure or an EDI map that a workflow reads, so we can test against it first.
Our own weekly releases are a separate matter. Releases and change control covers how they are tested, approved and rolled back. It also covers the minimum we work to if you have no formal change control today.
Who owns what
Section titled “Who owns what”- The ERP and its data are yours, as they were before we arrived.
- You own the custom code and the data built for you. We keep our reusable tooling, and your contract gives you the right to keep running and changing the copy inside your software after we leave.
- Accounts in your own systems are yours: created by your IT team, removable by your IT team.
- Who holds the AI model provider account and the hosting account during the engagement is agreed in your contract. If either is ours, it moves to you at handover. Stages and terms lists what your contract records.
- During the engagement we run the operations layer and the agent layer. After a handover, your team or another vendor runs them.
Handover and exit covers what is handed over.