Automation & Intelligence
Workflow Automation
The same file is copied between the same three systems every week by a person.
Automating the repeated manual steps in a business process — file handling, notifications, record creation, approvals and scheduled jobs.
We map the process as it actually runs before automating it. Automating a broken process makes it fail faster, so the map frequently changes the scope.
What this covers
- Workflow automation
What you get
- Process map
- Included
- The current process, documented and agreed.
- Automated pipeline
- Included
- Built across the systems and accounts agreed for the workflow.
- Failure alerting
- Included
- Notification when a run does not complete.
- Runbook
- Included
- What to do when it needs human attention.
How it runs, and what it asks of you
The six stages are the same on every Gridsmith engagement. Where your own time is listed, it is the part of a project that is worth knowing before it starts.
- Consultation
- We look at the current system, who maintains it, where it is hosted and what actually needs to change.
- Planning & Scope
- Scope is written as what the system will do, what it will not do, and who owns each account and environment at the end.
- Approval & Start
- Work starts once scope is agreed. Repository, environment and access arrangements are settled first, on the terms the written agreement sets out.
- Design, Development & Updates
- Built in reviewable increments on an environment you can see, rather than revealed at the end.
- Delivery
- Handover covers the running system, written documentation of how it is deployed, and the source-code and account arrangements the written agreement sets out.
- Support (if applicable)
- Maintenance, monitoring and further development are scoped separately rather than assumed — as further work or as an ongoing engagement.