Book a demo
Teamnet JIT

Every line call, built in sequence and sent with its papers.

For suppliers who feed an assembly line on calls - wheel and tyre sets or any other line-side part delivered in sequence. Each call starts its own clock, parts are built in the order the line needs them, each truck leaves with its challan, invoice, e-invoice and e-way bill, and the month is matched with the OEM - for the supplier and the OEM alike.

Follow one call ↓

The problem

Four things every JIT supplier keeps in their head.

Each one is solvable by hand on a quiet day. On a full shift they pile up.

The clock on every callEach call has minutes, not hours. A whiteboard cannot show forty clocks at once.
The order the line needsA call that jumps the queue leaves an older one short of the same part.
Papers with every truckChallan, invoice, e-invoice and e-way bill - each made by hand slows the truck.
A month that matchesChallans, invoices, returns and credit notes agreed with the OEM line by line.
One call, start to finish

Follow call 0417 from the line to the month-end match.

Seven steps, one record. Wheel and tyre sets are the example here; any line-side part delivered in sequence runs the same way. Every screen below is an Example.

Step 1

The call arrives and the clock starts

Who acts: Call desk

Calls come in by themselves from the OEM's sequence system. Each one carries its sequence number, the vehicle's parts and a delivery window set for your plant - for example 40 minutes. The time left is on screen from the first second, and urgent calls are marked. The line team gets the call alert on the Teamnet app.

  • Who gains
  • Call deskEvery clock on one screen.
  • Plant headAn alert if the link to the OEM goes quiet, before calls are missed.
Step 2

The build list is ready

Who acts: Line team

The call turns into a build list - which part goes in which position. For a wheel set: which tyre and which rim for left, right and spare. Material is taken oldest batch first, and the batch is recorded against the call.

  • Who gains
  • Line teamOne list per call, in the order to build, on the Teamnet app.
  • QualityEach part traced to its batch.
Step 3

Short of a part? The call waits in line

Who acts: SupervisorStores

If a part is short, the call waits and shows the one part it needs. Newer calls for the same part wait behind it, so nobody takes stock ahead of an older call. When the stock is received, waiting calls are built first, oldest first - nobody has to remember.

  • Who gains
  • SupervisorOne reason per waiting call, not a hunt.
  • OEMParts arrive in the order its line runs.
Step 4

Checked and labelled

Who acts: Quality

A quality check at receipt and before loading, if your plant uses one. Each set gets a QR sticker that ties it to its call and invoice.

  • Who gains
  • Quality teamChecks on the same record.
  • OEM receivingScan a sticker, see the call.
Step 5

Loaded and sent with its papers

Who acts: DispatchAccounts

Pick the next calls for the truck, choose the vehicle, count trolleys and stillages. Delivery challan, service invoice, e-invoice and e-way bill are made with the dispatch. If the GST portal is slow, the filing keeps trying on its own until it goes through; a supervisor sees anything still waiting.

  • Who gains
  • DispatchOne action, all papers.
  • DriverDocuments in hand before the gate.
  • AccountsInvoice and e-invoice already match the load.
Step 6

Returns and credit on the same record

Who acts: AccountsStores

A set sent back is recorded against its call and invoice - rework, scrap, back to stock or rejected at receiving. Credit notes use the original invoice rate. Trolleys and stillages at the OEM are counted, with a note when the balance grows.

  • Who gains
  • AccountsCredit notes that match the invoice.
  • OEMReturns closed against the same papers it received.
Step 7

The month matches, on paper

Who acts: Finance head

Challans, sequences, invoices, returnable assets, stock and GST are matched for the period. Every difference shows a reason and is closed with a note. A short summary of open differences reaches the supervisors each morning.

  • Who gains
  • Finance headA month agreed with the OEM without a spreadsheet night.
  • OEMOne set of papers for both sides.
OEM material

The OEM's material, counted from gate to return.

When the OEM sends parts and material on its own challan for assembly, Teamnet JIT keeps each challan's balance: received, used, returned, scrapped and still with you.

Under GST, goods sent for job work must come back or be supplied onward within the time the law sets; if they do not, the sender is treated as having supplied them. Teamnet JIT counts the days on every challan and warns before the limit.

  • Gate-in and unloading times on each challan
  • Balance per challan and per part
  • Day count on every challan, with a warning before the limit
  • Rates by date: a new rate applies to calls not yet invoiced
  • Who gains
  • SupplierNo surprise at year end.
  • OEMIts material accounted for, challan by challan.
Who uses it

Each role, its own screen.

The call desk and line on the Teamnet app; planning, accounts and the plant head on the web.

  • Plant headEvery call, its clock and the month's match in one view.
  • Call deskEvery live call and its time left, urgent ones marked.
  • Line teamThe build list per call, oldest batch first.
  • StoresWaiting calls and the part each one needs.
  • QualityChecks at receipt and before loading, part to batch.
  • DispatchTrucks loaded and sent with every paper.
  • Accounts and financeInvoices, credit notes, GST and the month with the OEM.
  • OEMCalls answered in sequence, its material counted.
Your plant, your settings

Set to how your line runs.

  • Delivery window per call
  • Positions per vehicle, such as left, right and spare
  • Truck size, trolleys and stillages
  • Invoice per dispatch, daily, weekly, fortnightly or on demand
  • E-invoice and e-way bill on or off
  • Quality checks at receipt and before loading
  • QR stickers and QR pages
  • Warning days on OEM challans
Reports

What the plant head and the OEM ask for.

  • Delivery window performance
  • Dispatch summary
  • Invoice to challan map
  • GST summary
  • Stock age
  • Part to batch trace
  • Trolleys and stillages at the OEM
One Teamnet

On the same platform as the people who build each call.

The employees and contract workers on your line are the same people Teamnet Workforce counts at the gate and pays each month - one company, one Teamnet AI, one way of keeping data private. Call alerts and the build list reach the line team on the Teamnet app. One app for every Teamnet product, with one login - free for employees and workers. Connected when you want them to be - each product also works on its own.

Who is at the cell comes from the Teamnet-made dual-lane full-height turnstiles, so the call desk knows its crew.

  • Who gains
  • EmployerLine output and line attendance in one place.
  • ContractorThe line-side crew counted at the gate, with the shift's calls on the same app.
  • Employees and workersCall alerts, the build list, their days and their pay on one free app.

See the Teamnet app → See Teamnet Workforce → See Teamnet turnstiles →

Your data

Private AI.

Our own AI models, on our own cloud. Nothing goes out - not to public AI, not to any other provider.

Questions

What JIT suppliers ask us.

How do calls reach Teamnet JIT?

A small agent on a PC in your plant reads calls from the OEM's sequence system and sends them out to Teamnet - nothing needs to reach into your network. It reports its own health, and supervisors are alerted if it goes quiet.

What happens when a part runs short?

The call waits with the part it needs shown. Newer calls for the same part wait behind it. When stock is received, waiting calls are built first, oldest first.

Do you make the e-invoice and e-way bill?

Yes, with each dispatch, if you switch them on. If the GST portal is busy, the filing keeps trying by itself for a set window and is never marked failed; anything still waiting is listed for a supervisor.

We work on the OEM's material. Can we track job-work challans?

Yes. Each challan's balance - received, used, returned, scrapped - is kept, with the day count and a warning before the GST limit.

Can we invoice daily or weekly instead of per truck?

Yes - per dispatch, daily, weekly, fortnightly or on demand, set for your plant.

We do not make wheel and tyre sets. Does it fit our parts?

Yes. Teamnet JIT runs any line-side part delivered in sequence; the build list is set up for your parts and positions. Wheel and tyre sets are one example.

Do we need Teamnet Workforce as well?

No. Teamnet JIT works on its own. With Workforce, who is on the line each shift comes across directly.

Does it run outside India?

Yes. Calls, sequence, dispatch and the month match run the same way at a plant outside India.

See your line calls on Teamnet.

One record for every call - from the line's call to the month's match.

See Teamnet Manufacturing See Teamnet Warehouse See Teamnet EHS

One callBook a demo