A request's page runs its five steps across the top: Review, Context, Link design, Selection & push and Issue. Each mark says whether the step is done, current or not started, and choosing one jumps to its part of the page.
- 1
Read what the client sent in the Request block: the request type, who raised it, the scope of work, notes and any equipment information.
- 2
Under Assigned to, choose the member of your firm carrying it.
- 3
When you start, move the Status on from Received. That completes Review.
- 4
Read Deployr context: the customer, quote, site and its equipment, pulled from the client's Deployr the first time the request is opened. Refresh context pulls them again.
- 5
In Link design, choose the System design the work is done in, or create one with New design from request. The Open in buttons take you to its stations.
- 6
In Selection & push, send the work back to the client's Deployr.
- 7
In Issue reports, email the reports to the client.
Linking a design
Linking a design makes it the selected system on every calculation page and in the header. New design from request names the design after the request and takes the refrigerant, load and temperatures from the request's operating data. A figure the request doesn't carry starts at the page default (10 kW, −10 °C evaporating, 45 °C condensing) with no cited source, so check each one in Cycle, the refrigerant included. A request for HVAC or hydronic work offers a new HVAC or hydronic project instead, named after the request with its scope; its design conditions and loads are entered on its own stations.
When each step counts as done
- Review: the status has moved on from Received.
- Context: Deployr's context is on the request.
- Link design: a system design is linked.
- Selection & push: a push has been sent to Deployr, with or without equipment.
- Issue: reports have been emailed to the client.
A step can be done out of order. One left behind reads Not done.
Who does what
Owners, admins and engineers can assign, set the status, pull context, link a design and push. Reviewers can read the request, check the linked design in Sign-off and email the reports.
Note
Assignment is Kelvin's own record of whose desk a request is on. The client's Deployr isn't told.