Production Lines ​

A company must have at least one production line defined in the system.

Production Settings is a group in the Settings section of the left menu, in company-wide mode, with three views. Production lines holds the lines and their stations. Machine Settings holds the machine setups. Automations holds the webhooks, the action triggers and the setups they run: machine files and drawings.

File generation templates are not here — they live in File settings, under the Files section of the menu. See Reports.

The Production lines view ​

The view starts with a New Production Line tile. Below it, each production line is a row: a header with its name, what it builds, its machine, its client IDs, its counts (stations, checklist items, machines, worktime capacity) and its actions (edit, copy, delete), and below it the cards of its stations in the order the line runs them.

Rows can be collapsed with the arrow on the left. They all start open, and the ones you collapse stay collapsed the next time you open the view.

Lines are grouped by what they build: modules first, then assemblies, then parts. A line that builds more than one of these appears once, under the largest one. Lines with an unrecognised tipo go to a last group, Other.

1. The name of the line and what it builds.
2. The machine of the line. In grey italics when it is read from the line's only machine station.
3. The counts: stations, checklist items, machines and worktime capacity.
4. The drag handle and the position of the station in the line.
5. A station that is in several lines.
6. The two tiles to add a station. See Working with stations.

The production line form ​

The production line (PL) itself has the following fields:

• Name: A name to identify the PL.
• Client ID: An optional list of external identifiers used to link the production line to external systems (e.g. ERP or planning software). Multiple IDs can be added when the line needs to be matched from more than one external source.
• Tipo: The assembly, module or part categories that the PL can produce. At least one is required.
• Line machine: see The machine of a line.
• Worktime Capacity: the capacity of the line, in minutes.
• Stations: on the right side of the form, the stations of the line in order. Add station adds an existing station, you drag a station to change the order, and its menu removes it from the line.

1. What the line builds. At least one is required.
2. The line machine. See The machine of a line.
3. The stations of the line, in order. Drag to reorder; the menu removes a station from the line.

Production lines (PLs) are expected to have at least 1 station. Stations represent steps in the production process.

Working with stations ​

At the end of every line there are two tiles:

• New Production station creates a station and adds it to that line.
• Add existing station lists every station that is not already in the line, including the ones with no line at all.

A station card shows its position in the line, its name, its client station ID, its number of checklist items, its expected worktime, its machine (or Manual when it has none), when it is enabled, and its zones, branches, assembly prefixes and drawing numbers when it has any.

Reordering is done by dragging a station card by its handle. The new order is saved as soon as you drop the card. You cannot drag a card from one line into another: to move a station, add it to the new line and then remove it from the old one.

A station can belong to several lines at once. It then gets a card in each of them, marked Shared, and its cards list the lines it is in. It is the same station in all of them, so editing it from any line changes it everywhere. Its position, on the other hand, belongs to each line separately.

Stations that belong to no line are listed at the end of the view, under No production line. This is normal — a station can be created or left without a line — and it is the only place where you can reach them.

If two stations in the same production line share a zone, a warning is shown at the top of the line, naming the duplicated zone and the stations it is in.

Deleting a station asks what you mean:

• Remove from this line takes it out of that line only. The station stays, and if it was in no other line it moves to the No production line group.
• Delete removes the station from every line and loses its checklist. This cannot be undone.

The station form ​

Station fields:

• Name: Simply a name.
• Client ID: Client ID of the station, usually from an external application that the client wants to link.
• Machine station: tick it if the station runs on a machine, then pick its Machine setup. For example: a Mobi One setup created in Machine Settings. Without it, the station is a manual station. Give each machine station its own machine setup: two stations sharing one setup lose the zones of the first.
• Enable when: when the station is part of a panel's checklist: Always, If Branch in Design, If all Branches in Design, If no Branch in Design, If Zone in Design or If Branch in Zone of Design, using the Branches and Zones below. They work the same as for checklist tasks, below. A station that is not enabled for a panel is greyed out in the viewer.
• Branches: the branches the station looks for.
• Zones (Assemblies): What zones are expected to be produced in this station. For example add 0 for a typical framing station. On a machine station, these are the zones it writes into the machine files: a zone that no station lists is not in the files, and a zone listed twice is written by the first station of the line. See How a file is made.
• Assembly Prefixes (Modules): the assembly prefixes the station works with, for module lines.
• DWG Numbers Filter and Default DWG: which drawings, by drawing number, the viewer shows at this station, and the one it opens first. Leave the filter empty to show them all.
• Expected productivity: the expected pace of the station, typed either as m²/min or as min/m²; the other value is filled in for you.

1. The machine setup of a machine station.
2. When the task is included.
3. How often the task is included. Here: one checklist in every five.
4. What the worker has to add to complete the task.
5. When the station itself is part of a panel's checklist.

Checklist tasks ​

As a last nested item, each station has a Checklist: the entries for the production users to check in the production interface ("the viewer"). Add item adds a task, and each task has an Options menu to move it up or down or delete it.

Checklist fields:

• Task text: The text that will be shown to the production user.

• Branches and Zones: used by Enable when.

• Enable when: when the task is included:

  • Always.
  • If Branch in Design: at least one of its branches is in the design.
  • If all Branches in Design: every one of its branches is in the design, in any zone.
  • If no Branch in Design: none of its branches is in the design.
  • If Zone in Design: at least one of its zones is in the design.
  • If Branch in Zone of Design: one of its branches is in one of its zones.

  The four branch options need at least one branch. The station's own Enable when is checked first: a task of a station that is not enabled is never included.

• QC Inclusion Criteria: All proofs means every checklist gets this task. 1/n adds it to 1 checklist every n checklists; 1/n randomized gives each checklist a 1 in n chance. n is a whole number of 1 or more. The count is kept per batch and per station, so two stations with a task of the same text each take their own panels, and the first panel of a batch always gets the task. Panels set ready from the constructibles list do not count and do not get these tasks, since nobody inspects them.

• DOCS: A feature that allows the company to add documentation specific to the task, such as guidelines, specifications, ... Save the station first to upload them.

• Require form: the task asks for a form, which you design with the button next to it. Expand this form as tasks in checklist shows each field of the form as a task of its own.

• QR field: the task asks for a QR scan.

• Require picture: the task asks for a picture.

The machine of a line ​

A line can name the machine it runs on. Tick Line machine in the line form and pick one.

There are two ways to record it, and both are fine:

• On the line. Use this when the line is one machine — a saw line, a plates cutter. There are no stations to hang it on.
• On a single station. Use this when the line has one station and the machine belongs to it. Nothing changes for the lines you already set up this way.

Either way, the machine's name appears on the line header, next to what the line builds. When it was read off a station rather than set on the line, it is shown in grey italics, so you can tell at a glance where it came from.

If a line has a machine and one of its stations has another one, the form says so. The line's machine is the one that counts for the line. It is a notice, not an error: the form saves either way.

A line with several stations that each have their own machine — an automated panel line — has no single machine to name. Give it one by creating an H&M Mobi One V2 Production Line machine setup and picking it as the line machine. That setup exists to hold what belongs to the whole line rather than to one of its tables; it has no settings yet, and each one will appear as it starts being used. Pick it as the line machine only: a station must never use it, or the MOB v2 files of that line cannot be generated.

Picking a machine setup ​

Both machine pickers — the one on a station and the one on a line — put the setups that usually go there first (under Machine stations or Line machines), and everything else under Other machines. Nothing is hidden: if you pick a setup from the second group, the form tells you where it normally goes and lets you carry on.

Machine Settings ​

Machine Settings starts with two tiles, New Machine setup and Import from JSON. Below them, the setups are grouped: first one group per production line, with the setups that line runs; then Not in any production line, for station and line machines that nothing uses yet; then the rest by machine type. Licensed types (wood profiles cutters, wood plates saw cutters, Voortman and Valk) show how many setups you have out of your licensed maximum.

Each card shows the model, the file types it Produces, and Used by: the stations and production lines that use the setup. It warns only when a station or line machine is used by nothing. Its buttons edit, copy, download as JSON, and delete the setup.

When you create a machine setup, the Model list is grouped by where that kind of machine goes:

• Production line settings — holds what belongs to a whole line. Today that is H&M Mobi One V2 Production Line.
• Machine stations — goes on a station of a line.
• Standalone machines — machines you send generated files to: saws, cutters, profilers. These can also be named as the machine of a logistics line.

The setup window has a General tab (name, model, and what the model is: provider, where it attaches, and what it produces), and depending on the model a Machine file tab, a Machine setup tab with the machine settings, and one tab per file type it produces, holding the default job options for that file.

Most models have no settings of their own: a cutter is configured by the options of the file it is sent, not by a form here. When that is the case the General tab says so instead of showing you an empty form.

1. One group per production line, with the setups that line runs.
2. Used by: the stations and lines that use the setup.
3. A station setup that nothing uses.
4. A licensed type: setups in use out of your licensed maximum.

The machine configuration file ​

Some machine models accept the machine's own configuration file (XML or INI), in the Machine file tab. Uploading it fills the Parsed params, shown next to the uploader as read-only JSON: the top level is open and each block can be expanded. The Current machine file card shows the file name and when it was parsed, so you always know how old the configuration is.

Automations ​

The Automations view holds the Webhooks, which send production events to external systems, and two things that work together: the setups, which say how something is generated, and the action triggers, which say when.

Machine file setups ​

A machine file setup is a saved MOB v2 setup: how the machine file is built — operations, nailing, shifts and layers.

Running one takes a panel design and builds a MOB v2 file for every machine station of every production line of the company, one file per station. There is no way to limit it to a single line. There is no report in between: the files are stored with the design, in its Auto-generated machine files card, and a new run adds a new version of each file. Nothing is copied to the machines: take the files from there.

You use a machine file setup from two places:

• an action trigger, so it runs on its own when a design finishes its analysis, and
• Launch action on the designs table, to run it by hand on the designs you select.

For files you check before they reach the machines, use the MOB v2 Machine File type in Production files instead. See MOB v2 Machine File.

Drawing setups ​

A drawing setup is a saved set of drawings. It decides:

• Drawings to make — one drawing per zone of the panel, with the parts of the other zones drawn as a dashed outline. Pick any of:

  • Zone 0 (frame) — the woods-only layer, drawn as FRAME. When zone 0 also holds plates, they get a drawing of their own, ZONE_0_PLATES, with the frame as a dashed outline, so they do not hide the studs.
  • Positive zones — drawn from the front.
  • Negative zones — drawn from the back, the face they are mounted on.
  • Custom branches — one drawing per custom part branch of the parsing setup that has parts in the panel (window frames, electrical boxes…), with the rest of the panel as a dashed outline. Drawn from the back only when all its parts are in negative zones.

  The first three are on by default. Front and back are the ones produuz.it finds when it reads the panel, the same as in the 3D viewer: each drawing shows the panel as the operator sees it. See Panel Sides and Coordinates.

• Scale of the drawings — auto by default: the largest standard scale (1:10, 1:20, 1:25, 1:50, 1:100) at which the panel and its dimensions fit the page. A fixed scale that does not fit falls back to auto.

• Parts list on each drawing — on by default.

• Draw the nail, screw and glue lines — on by default.

• Company banner in the title block — off by default. Turn it on to print your company banner on top of the title block of every drawing, and pick which one under Banner. The banners are the ones uploaded in your company resources, the same ones the QR stickers use.

What a drawing shows ​

Each drawing is one A3 page with a frame and a title block: the panel, the zone, the drawing number, the project, which side it is seen from, the scale, the material of the zone, the revision and the date.

• Dimensions, following the conventions of hand-made shop drawings. Heights are measured from the bottom. Lengths are measured from the bottom-left corner on a drawing seen from the front, and from the bottom-right corner on one seen from the back: that is the same corner of the panel, so a position reads the same on both sides.
  • Frame: along the bottom, first the position of every stud, measured to its left face and written from the corner; studs side by side (a king and a jack stud) count as one, by their left face. Under it, the openings: from the outer face of the frame to the inner face of the opening, then the clear size of the opening, the wall to the next one and so on, with the position from the corner under each value. Then the overall length. Up both sides, the sill height, the opening height and what is left above it, and the overall height on the right.
  • Zones: both edges of every plate or batten, measured from the edge of the panel, so the joints between plates and any strip of frame a plate leaves uncovered are visible. Battens also get their position from the corner. The clear openings of the zone are added when the plate edges do not already give them. The overall is always the whole panel.
  • The partial sizes always add up to the overall.
• Part references on every piece, the same ones as on the stickers and in the lists. When a piece is too small to hold its reference, the reference sits beside it with a line pointing into it. Pieces with the same reference that sit so close that their labels would crowd each other share one label, with a thin line to each piece.
• A parts list: reference, quantity, section and length for timbers; reference, quantity, width × length × thickness, material and cut-outs for plates; reference, quantity, size and material for the other parts of a custom branch.
• Openings with their size, nail, screw and glue lines with their spacing, holes with their size and their position from the corner, and the angle of every sloped edge.
• The parts of the other zones as a dashed outline, and a small diagram of the zones marking the one on this drawing and the side it is seen from.

On a panel's own drawings card, a drawing marked Needs review has something that could not be drawn or placed cleanly — a reference that found no free spot, for example. Open it and check it before using it.

Running one takes a design and writes the drawings straight into the design's files, marked as generated. There is no report in between.

You use a drawing setup from two places:

• an action trigger, so it runs on its own, and
• the Launch action button on the designs and multipanel groups tables, to run it by hand. Here the setup is optional: without one you get one drawing per zone.

The design's drawings card shows whether a run is working or failed, and warns when a newer IFC arrived after the drawings were made, marking the outdated ones. Generate the drawings again from the same button; Clean deletes the generated ones without touching the drawings you uploaded yourself.

Each setup table has a Used by column naming the action triggers that use the setup. Deleting a setup also deletes the triggers that use it; the delete dialog lists them first.

Action triggers ​

An action trigger runs something on its own when an event happens in production, with nobody clicking anything. Besides a name, it reads as three steps:

1. When this happens — the event. Today the only event is A design finishes its analysis.
2. Only if — an optional condition on a field of the design (name, tipo, or a key of its client data), matched as a full word, a prefix, or "contains". Leave it empty and the trigger applies to every design.
3. Then do this — the action, and the setup it runs with:
   • Generate MOB v2 files and send them to the machines, with a machine file setup.
   • Generate the drawings of the design, with a drawing setup — or none, for the default views.

In the table, a MOB trigger with no setup is marked No setup picked, and a drawings trigger with no setup is marked Default views.

1. Only if: here, only designs whose tipo starts with W.
2. The setup the action runs with.