SNB Production Workflow

SNB Production WorkflowGuideProjects

Projects

The job itself, once it is won — and the one screen in Sales with no "New" button.

A project is a job the company has actually won. Everything the factory does hangs off it: tasks, deliveries, material issued, invoices.

Warning

There is no “New project” button, and that is deliberate.

A project comes from an accepted quotation on a request. Creating one directly would produce a job with no customer agreement behind it, no price, and nothing to invoice against.

If you need a project, raise a request and win it.

1Open the list

Go to Projects.

The columns are Project number, Customer, Title, Status, Priority and Deadline. Note the header: no create action.

Open the list — Projects

2Open one

Click a row to open the project.

The row menu (⋮) carries six actions:

  • View and Edit
  • Generate Tasks — drafts the production chain
  • Print — the job ticket
  • Delete, and Restore for one that was deleted
Open one — Projects

What happens next

Getting a job to the factory is three decisions, not one, and they are made on the project’s own page rather than from this list.

1. Generate the tasks

Generate Tasks reads the project type’s workflow template and drafts a chain of tasks — but it does not hand anything over. The tasks are created at pending, and every screen in the factory is blind to pending.

Warning

Generating is not releasing, and it used to be.

Until this changed, one click created the chain and put it on the department screens in the same breath. If you remember it that way, that is why the floor is not seeing a job you have generated.

Two things about what it generates are worth knowing:

2. Review the production flow

Review the production flow opens the job’s graph. A template is a starting guess — a galvanized-steel sign needs no paint job — and this is where a factory manager makes the chain match what this job actually takes.

It also refuses to release a job whose graph would never finish. See Production → Reading the flow and Changing the flow.

3. Schedule it, then start it

Schedule production records a planned start date. The helper text says what it is: “A plan, not a trigger. The job still has to be started by hand once its production flow has been checked.” It puts the job on the handover board.

Start production is the handover. Every step becomes visible on its department screen and work can begin.

The button says why it cannot, before you press it, rather than failing afterwards. It is dim with the reason in the confirmation when:

Pull off the floor takes it back. Nothing new is released to a department, and work already started or finished stays exactly as it is — the record of what was done is not rewritten.

All three are covered in full under Production → Handing it over, including the four faults that refuse a release.