The Selection & push block on a request's page sends your answer back to the client's Deployr: equipment rows, documents and notes, and the linked design with its reports.
- 1
Fill the rows: Pull engineered equipment replaces them with the models chosen in the linked design's latest equipment selection, or choose Add item and type them.
- 2
Give every row a Tag that no other row uses. Deployr matches rows on tag.
- 3
Choose Attach document for any drawing, datasheet or photo to send, and add Selection notes if you want.
- 4
Choose Push selection to Deployr, or Push to Deployr without equipment when the rows are blank.
The block then says what was sent: how many equipment items and how many documents.
What a push must carry
- An equipment selection, fan selection or pump selection request needs at least one equipment row.
- Any other request, such as a heat load, pipe sizing or design review, can go back without rows. It still has to carry something: a row, a document, a note or a linked design.
- A blank row is left out. A row with anything typed in it is sent, so it needs its tag.
- Every tag must be unique. Pushing again updates the rows with matching tags in place.
What goes with a linked design
With a design linked, Kelvin also sends its calculations, pipe layout and equipment selection. For a refrigeration design it makes a fresh PDF report of each record saved against it with results, too: the Cycle report, and every pipe layout, equipment selection, charge, energy and cost record. Heat Load reports aren't included. Without a design, only the rows, documents and notes go.
Documents can be PDFs, images (PNG, JPEG, WebP, HEIC), spreadsheets (XLSX, XLS, CSV) and CAD drawings (DWG, DXF).
When a push is refused
- The organisation isn't paired: Kelvin says it hasn't accepted a Deployr connection code yet. See Pair with a client's Deployr.
- The request carries no reference Deployr can match, or Deployr can't match any of them: check the references on the request against the client's records in Deployr.
- Kelvin's report service is over its limit: the push still goes, without the reports, and they are queued to follow. See When reports can't be made.
- Your firm has reached its daily report limit: the push stops, and the message gives your firm's count and limit. Try again later.
Note
Pushing doesn't change the request's status. Set Report issued yourself when the work is issued.