MES and warehouse system for made‑to‑measure production

Your ERP takes the order. NODE runs the shop floor.

NODE plans every work step with durations it learns from your finished work, puts the sheets of several orders on one fabric roll, lights the right bin and trolley place for each operator and books what is used. Your ERP stays the leading system and gets the results back.

Request a demo
  • Re-planned every 30 minutes
  • 13 operator languages
  • Postings queued while the ERP is offline

Made for awnings, screens, pleated blinds and vertical blinds.

Five questions every manufacturer knows.

Each one has a usual answer: walk the floor, call around, open a spreadsheet. Here is the answer NODE gives.

The usual answer
  • In their heads
  • Searching for parts
  • Errors and rework
With NODE
  1. The station shows how it's done: drawing, instructions and checklist. No sign-off without checks.
  2. The light shows the right parts: pick by light at the shelf, the right place on the trolley.
  3. Set up once by your experts, used for every order.

Your best people's experience, at every station.

Want to start with this question?

Write to sales@jentschmann.ch Call +41 44 735 83 83

Where NODE goes further.

The parts that set NODE apart, each with a one‑minute film.

Planning

Plans that learn how long work takes.

NODE plans a station and a time for every work step, around target dates, priorities and shift calendars, checked against qualifications.

  • Wider fabric, longer sewing: a regression model learns effects like this from your finished work steps, retrained every night.
  • Re-planned every 30 minutes, and again as soon as a calendar or qualification changes.
  • Finished product planning shows every planned finish against its target date: on time, tight or late.
Cut optimization

Several orders, one fabric roll.

NODE places the sheets of all waiting orders on the right fabric article and roll width, for awning and screen fabric and pleated blinds, and shows the plan's waste before the first cut.

  • Edge trims, cut positions and width tolerances are applied to every sheet.
  • Opened rolls go first; their remaining length is in stock and on the roll label.
  • The plan lists each roll to bring, with its storage bin, and shows which fabric is missing.
Handling trolleys and pick by light

Parts and material, found by light.

Starting a work step lights the shelf bins with its material and a free place on the handling trolley. At the next station, the same place lights up again.

  • Place rules keep the parts of different finished products apart.
  • Several people pick at one shelf, each in their own colour.
  • One LED strip covers many places, with no extra device per bin.
ERP integration

Your ERP stays in charge. Nothing is typed twice.

Your ERP remains the leading system for orders, articles, purchasing and the financial view of stock. NODE plans and runs production and the shop-floor warehouse, and already exchanges data with Business Central.

  • Orders arrive with their order positions, typically about a minute after they are entered in the ERP.
  • Consumption, output, moves and finished work steps are reported back. ERP offline? Postings wait in the job queue and are never dropped; after a longer outage, one click sends the remaining postings.
  • If the ERP cannot confirm a goods receipt position, NODE does not book it, so there is no stock your ERP doesn't know.
Customer Language

Every operator, their language.

13 languages, and your process data in them: the ERP code LI shows as “Left”, “Links” or “Lewa”, and rework reasons appear in each operator's language. Your own terms survive every update.

Shipping

Packed smart. Shipped for less.

NODE fits each delivery group into your boxes and the shipping carriers' limits, and picks the lowest total price from your rates.

AI assistants

Describe it. The assistant enters it, if you let it.

Off until you switch it on. Then you describe the task, the assistant shows its plan, and you check the result in NODE. Claude, Codex or a local model work through the MCP server, with exactly the API roles of their token.

Follow one order through the whole factory.

One awning order, from the ERP to the storage bin, in six stops. Scroll through them; each plays the matching scene from the film.

01Order in

The order arrives from your ERP.

Its order positions appear in NODE. One release creates a finished product per piece, each with its own barcode and work steps.

02Planning

Station and time for every work step.

A planning run fits them around target dates, calendars and qualifications.

03Cutting

The cutter asks NODE for the next pull-off.

After the cut, NODE books the used length off the roll.

04Stations

Every station shows what this step needs.

Drawing, checklist and inputs on the terminal. On the handling trolley, the place with the parts lights up.

05Feedback

Finished in NODE. Reported to the ERP.

Finishing a step books the material it used. Consumption, output and finished work steps go back to the ERP.

06Reorder

Roll empty? Your ERP reorders.

NODE reports the stock change; purchasing stays in your ERP. When the delivery arrives, one scan fetches the purchase order.

From the ERP to the bin: one continuous flow.

Every stop above uses the same order, the same articles and the same storage bins.

Also in NODE, on the same orders and storage bins.

Your process, set up by your team.

Your own people draw the routings, design the station screens and decide who sees what.

Set up by your team

  • Routings you draw yourself. Steps, decisions and gates in one editor. Every release builds the work steps from it.
  • Your own fields. Attributes add your own fields to order positions. Decisions and station views can read them.
  • Checks with your limits. Checklist templates set the inputs and their good values. Anything outside counts as failed.
  • One login on every device. Permission groups set what each person sees, qualifications where they may work; at the station an access card is enough.

What your IT will ask

  • Runs on your own server. On-premise, installed with NodeManager on Docker or as Windows services.
  • Nothing to install on browsers and tablets. Terminals, handhelds and the hall TV load NODE from the server and update with it. Only machine clients, the Connector and the optional Kiosk Browser app are installed.
  • Licensed by module and by number of process stations and storage areas.
  • Access only as granted. Permission groups for people, API roles for machines, integrations and AI assistants. The MCP server ships switched off.
  • Security documented. Attack surfaces, measures and remaining risks are described for the EU Cyber Resilience Act and your own assessment. The document and an SBOM are available on request. At every start, NODE's services check their program files against a manufacturer-signed manifest, and the typical two updates a year each include security fixes.

Start with one business case

Start with the question that hurts most today: material, planning, transparency or know‑how. The next area follows, step by step.

  1. Pick one business case.Material, planning, transparency or know‑how.
  2. Run it on real orders.Set up for that part of your production and connected to your ERP.
  3. Add the next area.On the same orders, articles and storage bins.

Let's look at your production.

Tell us which of the five questions costs you most, and we'll start there.

Write to sales@jentschmann.ch Call +41 44 735 83 83

NODE is developed and supported by Jentschmann AG in Switzerland.NODE – your production, connected.