Set up the automations
The asset is set up, you know who and what govern it, and you know what is missing from the file. Step four is choosing what runs from here. Aevy has a set of workflows, your package includes some of them, and the useful question is not which are impressive but which match work your team is already doing badly or slowly.
After assessing the data room. Which workflows your package includes, and on how many assets, is part of your agreement with Aevy. Ask your Aevy contact what yours covers before choosing.
Start where the pain is
Section titled “Start where the pain is”The best first workflow is one that replaces something a person does today and dislikes. That gives you a comparison, a person who cares whether it works, and a result you can judge inside a month.
| If today somebody | Start with |
|---|---|
| Rebuilds a blade defect list from campaign reports | Blade inspection findings |
| Keeps a spreadsheet of inspection expiry dates | Statutory inspections |
| Reads service reports looking for what needs doing | Preventive maintenance |
| Cannot say whether a defect raised months ago was fixed | Corrective maintenance |
| Files lab reports without comparing them | Oil sampling |
| Is chasing a contractor through a takeover list | Handover punchlist |
Pick a first asset, not the portfolio
Section titled “Pick a first asset, not the portfolio”Switching a workflow on is per asset, so start on one site where you know the answer already. That is the only way to tell a workflow that is wrong from a workflow that is right about something you had not noticed.
Give it a month of real documents. A workflow judged on the backfill alone tells you how it reads history, not how it behaves when a report lands on a Tuesday.
Settle the two questions
Section titled “Settle the two questions”Every workflow asks the same two while it is being set up, and both are easier to answer with a real asset in front of you.
- The bar. How serious something has to be before it becomes work. Start strict: a list nobody trusts is a list nobody opens, and widening later costs a conversation while winning back attention costs months.
- The start date. Whether to read everything on file or only what arrives after a date you name. Backfill where the history is the point, as with oil trends; start from a date where the backlog is managed elsewhere.
Each guide’s “decide before it runs” section says what else its own workflow asks.
Then decide what runs without you
Section titled “Then decide what runs without you”Once a workflow has settled, the last choice is whether its proposals still wait for a person. That is covered in how workflows work, and it is worth reading before you turn anything to auto-accept: the question is less whether you trust the output than whether you would notice a record changing.
What’s next
Section titled “What’s next”- How workflows work: the full set, and what each needs before it runs.
- Suggestions: the review queue every workflow ends in.
- Getting around: the rest of the platform, now that yours is running.