all data is live and searchable

Production Runs (new pages)

The new Production pages run production in adilas on the Apex look: one board for every run, one page to start a run, a page for each run, a scan page for the floor and printed travelers. A company turns them on for itself. Until then, and for anyone on the Snow Owl or Classic look, the Production home and its build forms work as before. A run saves the same adilas records the build forms save: a build PO for each step, packages for what comes out, and an EOT for a run with phases.

Turning it on

  • Open Production settings (the settings link on the Production home; once the new process is on, also Production Settings in the Apex menu) and choose On under "Use the new Production process". It needs the Page settings permission (176) and a company on the Apex look.
  • You can set up your processes first: Production Templates opens before the switch is on.
  • A company that reports production to Metrc keeps the build forms for now: the switch is locked and says why. The new pages will send runs to Metrc in a later update.
  • With it on, people on the Apex look get the new pages from the Production home, the build forms and an EOT's "Create build" link. The Production home as it was stays one click away (Production home on the board).

Production Runs (the board)

  • The numbers at the top filter the board: In progress, Ready to finish (in their last phase), Planned, Finished in the last 7 days, and the work in progress at cost.
  • Each run shows its phase and how long it has been in it. Next moves it to its next phase; tick several runs to move each one. Finish run opens the run at its finish. More has the rest: Finish now, Add output, Adjust inputs, Print traveler, Run again, Save as template, the pick ticket and EOT, and Cancel.
  • Scan a package tag or a run traveler into the box at the top, or type an item, a recipe or a run code, to open it on Production Scan.
  • Below the runs: Start a run, Items with stock (Extract, Package and More for each item, with a vendor filter for companies with several vendors), Categories, the recipes (with what each still needs before it can be built) and Inventory & links (on hand by location and every production page you can open).

Starting a run (New Production Run; it needs the View Custom Code & Reports permission, 126)

  • Pick what you are running: Extract, Package or split, Combine packages, Testing sample, Recipe build or Manufacture. Choose the packages and how much of each goes in, then name what comes out.
  • Check makes every check a save would make and saves nothing: stock, units, cost shares and the ice-down date. Start saves the run.
  • Finish now makes the outputs at once. Finish later starts a run with phases (for example Extracting, Purging, Ready to weigh) that holds what went in until you finish it.
  • A recipe run can be planned for a date: Reserve and plan holds its packages on a pick ticket, and the board shows it as Planned until you start it.
  • Costs come from what went in: each output takes its share of the run's value, by its cost share, or by quantity when all the outputs are in one unit. Every document a run writes nets to $0.00, except a write-off.
  • A run of more than 50 outputs is saved in steps of 50. If a step stops, the run stays In progress with what was saved, and Finish run finishes the rest.

A run's page

  • The phases, what went in, what came out with each output's cost and share, the documents (POs, packages, EOT, pick ticket) and the run's history.
  • Add output takes some output before the run finishes (a QC sample, say). Adjust inputs returns or adds inputs until the first output. Finish with no output writes the run off. Cancel puts everything back, before any output only.
  • Undo: a run made at once by mistake can be undone within 15 minutes, while its outputs are untouched. It writes one reversing document and puts the items' costs back.
  • Save as template keeps the run's process, outputs and shares for next time.
  • Print a traveler to go with the work: scanning its code opens the run.

Production Scan (for a phone or tablet): scan a package, a traveler or a pick ticket, or type an item, a recipe or a run code. A package shows what it holds and offers Testing sample, Package, Extract and Combine; a run opens with its next step.

Changes on the old pages: while a run is open, its POs, packages and EOT can't be changed on the old edit pages, which say which run holds them. A finished run's documents can still be voided or edited there, and the run notes it. Each night adilas compares every run with its documents and lists any difference on the board.