Shift reports, quality, and the spreadsheet that still runs the line

A shift still ends with a report. Paper in a binder, a form in a shared Drive, or a body of text in an email the next supervisor reads in the parking lot. Counts, downtime, who called in, and the one machine that sounded wrong. Cyriac Zeh and Nidrosoft start with that report, because a model that cannot draft the next shift's handoff from the notes already taken is a booth demo. We stand at the cell, we read last week's books, and we watch who types the ERP after the fact.

Quality holds live in Excel more often than the quality manual admits. A column for lot, a column for defect, a column for who is allowed to release. The MES has a hold flag. People still text the quality lead because the flag is late. We map both systems. The Sheet is usually the truth at 6am. The MES is the truth at audit time. A useful build drafts the hold row from the inspection note and parks it for a named release. We will not flip a hold to ship because a timer ran out.

Planning sits in the ERP, then in a side workbook, then in a hallway conversation. SAP, NetSuite, Epicor, or a cousin holds the work order. The planner copies firm orders into a Sheet that the supervisors actually use. Purchasing lives in the same copy with a highlighted late PO. Nidrosoft does not start by replacing the ERP. We start by naming which file the standup reads. If that file is the Sheet, the first draft writes to the Sheet and tells the ERP later, with a person in between.

Maintenance and tooling have their own book. A clipboard on the machine. A CMMS login nobody remembers. A parts cage with a binder. Downtime codes get picked in a hurry and then argued on Friday. We treat those codes as data only after we have watched a changeover. A model that invents a root cause from a two-word note is how you buy the wrong part. We will draft a work order from the note and the asset id. A technician still writes what they saw.

Nidrosoft has not shipped a public MES, SCADA, or shop-floor product. There is no branded line tablet in the archive. Cyriac Zeh will say that in the first conversation. We build into the ERP, the Sheet, the inbox, and the shift book you already run. If you need a logo of a plant we automated, you will not find one on the work page. We will not borrow Omnira Dental or Nexuvo and rename them for a buyer in operations.

Omnira Dental is a live clinic system. Nexuvo is a live dealer system that pulls private-party inventory overnight and cuts manual outreach. Eviction Wizard is a live notice-to-writ dashboard. Those products prove we ship operator queues in messy industries. They are not factories. A plant buyer who wants proof of floor software should treat this page as a method page, then ask us to walk a shift. That walk is the proof. A fake case study is not.

What we will take is the same class of work we take everywhere. Intake a messy artifact. Draft a structured record. Put it in a queue. A person signs. Shift notes become a handoff. Inspection notes become a hold row. Vendor emails become a late-PO list. Scrap tickets become a reason-code draft. None of that requires a public floor brand. It requires access to the book and a supervisor who will tell us when the draft is wrong.

If you need a historian, a PLC program, or a vision system that stops the line, you need a controls integrator. Nidrosoft will not pretend to be one. We will sit next to that integrator on the reporting and the queue. We will not flash a PLC. Scope will say that in a sentence a plant manager can forward to engineering. Mixing those jobs on one PO is how both slip.

Supervisors write the book in the last fifteen minutes, or they skip it and talk in the doorway. The next shift spends twenty minutes reconstructing. We collect the artifacts that already exist: downtime punches, count screens, a photo of the whiteboard, a voice note on a personal phone. A draft handoff can assemble those into the template the plant already uses. The outgoing supervisor edits the sentence about the machine that sounded wrong. That sentence is the job. The assembly is the work we can take.

Attendance and overtime sit in a Sheet that payroll also uses. Someone copies badge data. Someone adds a note about a late arrival. We will not own payroll. We will draft the exception list the supervisor already emails to HR. A wrong overtime flag is a grievance. The click that sends that email stays human. If your union contract has a notice rule, we put that rule in the scope as a gate, not as a prompt trick.

Safety observations and near-miss notes arrive on paper cards or a form that quality owns. They rot in a box. We can transcribe and file them against a line and a date, then draft the weekly list EHS already makes. We will not close a corrective action. We will not decide severity. Plants that want an agent to close CAPA items should hire a different firm and keep their counsel close. We file. They close.

Multi-shift plants argue about counts. First shift's number and the ERP's number and the warehouse's number disagree. We do not pick the winner. We put the three numbers on the same handoff row and mark the gap. Finance and operations already have a meeting for that gap. A model that averages them is how you hide shrink. Nidrosoft would rather show the gap in the morning than explain a quiet average at month-end.

Incoming inspection is a bench, a gage, and a traveler. Results go into the MES if the clerk has time, or into a Sheet if they do not. A late truck makes the clerk choose speed. We draft the inspection row from the traveler photo or the typed note and queue it. Quality accepts. Material that sits in a gray zone on the dock is a plant decision. We will not move a bin in the ERP because a photo looked fine.

In-process checks and first-article notes have the same split. The operator marks a paper. Someone keys it later. We can draft the digital row and keep the paper as the image on the record. Auditors like the image. Operators like the paper. Fighting that habit in week one is how the build dies. We follow the paper until the operator asks for the tablet. We do not start with the tablet.

Scrap and rework codes are politics. The easy code gets picked. The honest code takes a sentence. We keep a short list the plant already agreed on and we ask for the sentence when the code is other. A generated novel about root cause is worse than a blank. The quality lead already knows this. Our job is to stop the silent default to the first dropdown item without making the operator write an essay at the cell.

ERP transactions after a jam are where people hide. Backflush, a manual issue, a work order split in SAP, NetSuite, or Epicor. We will draft the transaction from the count the supervisor signed on the handoff page. We will not post it. Controllers who want an agent with post rights will hear no on the first call. A posted wrong issue is a physical inventory ghost that cycle count has to chase. Nidrosoft would rather look slow at go-live than explain that ghost to finance.

Nerlude is live at nerlude.com. Plants already have the same mess founders have: vendor portals, VPN certs, a historian license, a domain for the careers page, a forgotten test environment. Keys sit with a contractor. Renewals surprise the controls lead. Nerlude is a control center for services, credentials, and 30, 14, and 7 day alerts. We point plants at it when the outage was a lapsed login, not a bearing. It will not run the cell.

TokenTra is live at tokentra.io. If the company already pays OpenAI, Anthropic, Azure, or Bedrock for a document tool or a vision pilot, the invoice needs a name. TokenTra breaks spend by project and team. Public results on this site say teams cut 10 to 30 percent of wasted AI spend after they can see it. A plant with no model bill can skip this. A plant that bought three pilots last year cannot.

Nexuvo is a dealer product. It finds inventory, writes outreach, and runs overnight. Dealers acquire 3x more inventory with 80 percent less manual outreach on the figures we publish. We mention it here for the habit, not the industry. A plant that wants overnight vendor follow-up on late POs can use the same queue idea: draft the chaser, hold send for purchasing. We will not scrape a marketplace for your raw material and call it Nexuvo for steel. Different system. Same idea of a queue that works while the building is empty.

Protectron is live for EU AI Act classification and drafted docs. A plant selling a machine-learning inspection tool into Europe may need it. A plant using a model only on internal shift notes may not. We mention it so a buyer does not ask us for a legal opinion in a quality manual. Counsel plus a product like Protectron is the path. A paragraph we generated from your homepage is not.

Embed means we walk the line on a shift that is not a tour shift. We read the book. We sit with quality on a hold. We sit with planning on the Sheet. Nidrosoft does this from San Diego and on site when the plant will have us. Approved access only. We do not need a badge to every cage on day one. We need the file the standup trusts.

Diagnose means we cost the recurring work in the units the leads already use. Minutes on the shift handoff. Hours keying incoming inspection. Hours chasing late POs in the planner workbook. Hours arguing counts between the cell and the warehouse. We score feasibility against your ERP rights and your plant network. A site that will not grant a service account gets a smaller first build on Drive and mail. We write that constraint down. A roadmap that ignores it is a slide.

Scope means you buy a result a supervisor can run on night shift. Shift notes become a drafted book in the template you already use. Inspection notes become a hold row on the quality Sheet. Vendor mail becomes a late-PO list for purchasing. We write what the system may draft and what it may not post, release, or ship. Safety and quality closes stay human. If a director wants an agent that releases holds at 2am with no click, we stop the scope.

Build and Own happen in your tenant. Someone in operations or quality pairs on the queue. Training uses last night's book, not a toy plant. When we step back, the supervisor should run the draft without calling us. Cyriac Zeh stays for the work you name. Hosting sits on Azure, AWS, Google Cloud, private infrastructure, or what you already run. EU residency is available when a customer contract needs it.

An AI audit in a plant is two weeks in the work. We read shift books, the quality hold Sheet, the planner workbook, and the inbox purchasing uses for expedites. We talk to a supervisor on a real shift, a quality lead on a live hold, and a planner who owns the side workbook. Nidrosoft will decline an audit that is only an executive offsite about lights-out manufacturing. Process design is yours. Filing and queues are what we map and cost.

Each opportunity sits next to a system the plant already pays for. The ERP. The MES the cell ignores during a jam. Excel. Outlook or Gmail. The CMMS nobody remembers. Nerlude if vendor renewals and VPN certs are the quiet fire. That list keeps the roadmap from becoming a stack replacement. We will not rip out the MES in a quarter. Anyone who offers that as an AI project is selling a program Nidrosoft does not sell.

Risks go on the map next to the book they would hit. A drafted scrap code that hides a repeat defect. A posted issue that creates an inventory ghost. A release on a quality hold. A near-miss note filed under the wrong line. We mark those as gates before anyone asks for a batch post. Plants that want speed without gates should buy a consumer tool and accept the audit finding. Plants that want Nidrosoft want the gates in the PO language a controller can read.

Email cyriac@nidrosoft.com with the ERP name, the headcount on the floor, and the fire. Shift handoffs, quality holds, or late POs. Book the public calendar if a plant manager or ops director can grant folder or ERP read access the same week. Two weeks later you have a ranked list of hours and gates a supervisor can run. You do not have a new production system, and Nidrosoft will not sell one.

A first build we take is the shift handoff. Downtime punches, count screens, a whiteboard photo, and a voice note go in. The plant's existing template comes out. The outgoing supervisor edits the sentence about the machine that sounded wrong. The next shift reads one page. We log the sources. Plants that want the draft to mail itself to corporate without a sign will not like us. Unsigned books become fiction by Thursday and the argument starts at standup.

A second build we take is the hold and inspection queue. A traveler photo or a typed note goes in. A row lands on the quality Sheet or the MES hold list. Quality clicks accept. Images stay attached for the auditor. Release stays a named person. We will wire an email to the planner when a hold ages past the hour the plant already defined in the quality manual. We will not invent that hour for you on the first visit.

A third build we take is purchasing follow-up. Late PO lines become a list. Draft chasers sit in a queue. Purchasing sends. Overnight processing can prepare the list the way Nexuvo prepares dealer outreach, without touching a marketplace. Transformation is audit plus two or three queues plus training for the leads who will run them, then the next cell. We need a sponsor and an ERP admin. Without those, we stay on one book.

NanoBrief can help a plant that writes the same quality or customer brief from a short questionnaire. Public timing on this site is under two minutes against 3-plus hours for the shipped templates. Your PPAP packet, a customer 8D, or a first-article write-up is slower because the attachments already exist in a folder. We will time it on your questions and your required fields. We will not claim a two-minute PPAP. That sentence would be a lie and a buyer would catch it.

Corporate AI training for a manufacturer is a sprint on their shift book and their quality Sheet. Directors get the ranked map and the gates on post and release. Supervisors bring last night's handoff, including the messy one. We write the first draft together on the projector. A ballroom talk about robots is a different product. Say which one you want before we book travel. Cyriac Zeh has run operator rooms in San Diego. The artifact has to be in the room.

We refuse training that cannot open the ERP, the MES report, or the quality workbook. If the room is only corporate strategy, hire a strategy firm. If the room is only ChatGPT seats for supplier emails, buy the seats from the vendor. Come back when a lead will grant folder access and bring last night's book. Mixing those rooms without a shared backlog produces a playbook nobody opens on night shift.

Safety training content is yours. We can file the current PDF and quiz it if that is in scope. We will not generate a lockout or tagout procedure from a homepage and laminate it on the machine. Procedures need the people who do the work, the EHS lead, and the last incident file. A generated card that misses a step is a record you do not want in an investigation. Nidrosoft will not put our name on that card.

After training, the first queue should be obvious. Shift handoff, quality holds, or late POs. If it is not obvious, buy the two-week audit. The room only collected opinions about robots. Nidrosoft would rather sell the audit than a second workshop that repeats the first afternoon on the same book. Email cyriac@nidrosoft.com if you are choosing between them. We will pick one and name the folder access we need on Monday.

Hire a strategy consultancy if the board wants a lights-out story and no one will share last night's book. Nidrosoft is a poor fit. Cyriac Zeh will say so. Hire a controls integrator if you need PLC work, vision that stops the line, or a historian. We will not bid that as an AI project. Buy ChatGPT seats if the only request is supplier-email help. TokenTra can wait until a real model bill exists and someone can name the project on the invoice.

Do not book us without a decision maker. A vendor who wants a logo, a student project, or a consultant with no ERP or folder access will get a decline. We work with plants that can name an ops owner, approve a service account or a Drive folder, and pick a repeating job such as handoffs. Smaller shops fit when one queue pays for itself before the next hire. Larger companies start on one line or one site, then copy the runbook.

We will not take autonomous release, ship, scrap-as-final, or payroll sends. We will not flash a PLC or write ladder logic. We will not invent OEE percentages you do not already collect the same way on the same report. If a vendor scorecard requires a public floor logo we have not shipped, we will fail that row on purpose. That is cheaper than a fictional case study a plant manager would have to defend.

If the company is really a software vendor selling into plants, use the software industry page. TokenTra, Nerlude, evals, and Protectron live there. If the company is a clinic with a small lab, use the healthcare page and Omnira Dental. Mixing those scopes on a manufacturing PO is how the PO sits in legal for a month while someone argues which MSA applies. Name the object you want filed: a book, a hold, or a late PO.

Write cyriac@nidrosoft.com with the ERP name, the site, and the fire. Shift handoffs, quality holds, or late POs. Cyriac Zeh reads that mail from San Diego. Attach a redacted shift template or a screenshot of the hold Sheet if you can share one. Book the public calendar if a plant manager can join the same week. A pitch for lights-out manufacturing with no artifact attached will get a no in one reply.

The first live process should look like a page a supervisor already knows at 6am. A drafted shift book. A hold row with a photo. A vendor list purchasing still sends. Nidrosoft has 125 products shipped and 16 public systems. None of the 16 is a floor OS, and this page says so. Adjacent clicks are Nerlude, TokenTra, and the Nexuvo figures for overnight queues in automotive. Ask us to walk a shift if you need proof we can stand in one.

You own the workflows on day one. They run in your ERP permissions, your Drive, and your cloud bill. After we leave, a quality lead should add a scrap reason code and a new reviewer without a San Diego call. If they cannot, we did not finish the Own step. Audit trails stay on in the queue. Money movement, hold release, and ship confirmations stay on a named login the controller already knows.

Healthcare and software pages cover Omnira Dental, TokenTra, Nerlude, and the ticket queue for teams that also run those stacks. Read how we work for Embed, Diagnose, Scope, Build, Own. Read about for Cyriac Zeh and the San Diego studio. Use contact for the public calendar or write cyriac@nidrosoft.com with the book and the fire. The work starts when someone who can approve ERP or folder access and name who signs a hold is on the thread.