RESOURCES
What the practice asks of a customer, and what the customer keeps.
Articles in Working together
- Working together
After the engagement: support and the next version
Ordinary changes are the site's to make. The practice holds no access and runs no service desk. When a change is bigger than the notes, the next version is scoped as a new engagement from what you already hold.
· 4 min read
- Working together
Working with IT and compliance
IT decides the posture and the segment. Compliance gets a run record an auditor can read. Both help name the roles that publish and approve, so the answers live in the version rather than in a policy.
· 4 min read
- Working together
Working with your integrator and robot vendors
The practice does not displace the integrator who wired the line or the vendor whose software runs the robots. It builds on your appliance and reaches their systems only by routes you declare.
· 4 min read
- Working together
What the customer keeps
Versions and their history, the corpus, adapters learned on site, the run record, the notes, the posture unchanged, and a team that can change it. All of it on your appliance, none of it with the practice.
· 3 min read
- Working together
What the practice asks of a customer
A statement of done, time with the people who handle the packet, an appliance in the rack, a named posture, named roles, a named corpus, and the team who will take it over. Nothing unusual, all of it necessary.
· 4 min read