How workflows work opens the section: what a workflow is, and the journey from asking for one to using it. A diagram splits it at the point that matters, since setting one up is manual and happens once, while running it is not. It closes on the decision most people leave implicit, which of a workflow’s proposals should accept themselves and which should wait for a person. That is less a question about trusting the output than about staying informed: a record that changes with nobody watching is how a register drifts from what the team believes is in it.
A new Your first steps section walks a new asset through four, in order, each ending by naming the next. Asset information onboarding is step one, and it is a review rather than a data-entry job: Aevy builds the asset record from the data room, you check the units, their names, their parts and the headline facts, and you add the custom fields your team tracks beyond the standard ones. Getting to know your documentation is step two, mapping the stakeholders first and then the agreements that govern the asset, with a diagram of how one counterparty reaches a hundred documents and a dozen duties. Assess the data room is step three, checking what you hold against what you should. Set up the automations is step four, picking the workflows that match work your team already does badly or slowly.
Eight workflow guides cover the running work, each naming the technologies it runs on: blade inspections and oil sampling for wind, statutory inspections across all three, preventive and corrective maintenance, handover punchlist, internal auditing and document handover. Statutory inspections also names the regimes covered, the United Kingdom, France, Germany and Spain, with other geographies in development.
Also in Document handover
