Production Scheduling for Job Shops: When the Whiteboard Stops Working

Job shop production scheduling outgrows a whiteboard when the board can no longer hold the four things a schedule depends on: capacity, routing, material, and due dates. The fix is getting those inputs into one place, visible on the floor, before you automate anything clever.

Here is a Monday we hear about often in job shops. The production manager arrives at 6:45, and the whiteboard says the CNC mill runs brackets first, then housings. Over the weekend, a customer called the owner and a rush job jumped to the top. Housing material has not arrived. Second shift scrawled a note that the bracket fixture is cracked. By 7:30, three people have rewritten the same column, and the saw sits idle because nobody knew it was free.

Nobody did anything wrong here. The board just had no room for all the information it was being asked to hold.

Key takeaways

  • Write down where capacity, routing, material, and due dates live today. If they live in four places, that is the first thing to fix.
  • Choose a priority board or finite capacity based on your bottleneck machines, not on software features.
  • Put the queue at each work center before you add any scheduling math.
  • Capture actual start and finish times so you can compare them to your routing estimates and correct the ones that are off.

The whiteboard stops working before anyone admits it

Shops rarely decide to leave the whiteboard. They drift away one workaround at a time: a spreadsheet, then another for material, then a text thread for hot jobs. The signs:

  • Constant reshuffles. The job order changes several times a day, by memory.
  • Hot jobs that never cool down. When everything is urgent, nothing is clearly next.
  • Idle machines next to a backlog. Work is waiting at the wrong machine or for the wrong part.
  • Late news on due dates. Someone learns a job is late on the day it should ship.

Kyo has written before about why small production issues turn into big delays. The schedule is where every one of those delays eventually lands.

What does a real schedule need to know?

In most job shops, four inputs matter, and each usually lives somewhere different today.

  • Capacity. Hours each work center (a machine, cell, or crew doing one kind of operation) actually has this week, after maintenance and absences. Often it lives in the production manager’s head.
  • Routing. The sequence of operations a part follows (saw, mill, deburr, inspect), with setup and run time for each. It may sit on a traveler (the paper packet that follows a job through the shop), in an ERP (enterprise resource planning, the system that handles orders, inventory, and accounting), or nowhere at all.
  • Material. Whether stock, purchased parts, and outside processing are on hand. Usually that is a purchasing spreadsheet or the buyer’s inbox.
  • Due dates. The date promised to the customer, and whether it changed. That is in the order system, in email, or in the owner’s last phone call.

When these live in four places, people reconcile them by hand at the whiteboard. Kyo’s article on managing work order requirements and milestones covers keeping job details in one record, the foundation scheduling builds on.

Do you need finite capacity scheduling or a better priority board?

Finite capacity scheduling means the schedule only loads each machine with as much work as it can actually do in the time available. If the mill has 40 hours this week, the schedule will not give it 55. Infinite capacity planning, by contrast, lines jobs up by due date and assumes the hours will be there.

A priority board is simpler. It ranks jobs and shows what is next at each work center, without checking whether everything fits.

  • A priority board is often enough when routings are short and the real problem is that nobody can see the current order.
  • Finite capacity starts to earn its keep when jobs share bottleneck machines, setups are long, and you regularly promise dates that the floor cannot hit.

Starting with the board and adding capacity math later is a perfectly good path.

Put the schedule on the floor without another login

A schedule on the production manager’s laptop is just a private whiteboard. Operators need to see what is next at their station and report when a job starts, stops, or hits a problem. That usually means a shared screen or tablet at each work center showing its queue, with one-tap start, complete, and hold. Operators do not need a separate login, and nobody has to walk to the office to see what is next.

Those updates also give you what the whiteboard never could: actual times. Kyo’s post on how to gather real-time production statistics shows how that data turns schedule guesses into numbers you can trust.

Automate in stages: visibility, then capacity, then what-if

Stage 1: visibility. One job list, one queue per work center, live status from the floor.

↓

Stage 2: capacity. Routing times and available hours, so overloaded machines get flagged.

↓

Stage 3: what-if. Test a rush job or machine outage and see which due dates move.

Each stage pays off on its own. Stage 1 alone can take a lot of the Monday-morning rewriting off the production manager’s plate.

The platform matters less than the inputs. Some shops use a scheduling module in their ERP. Others build a custom application on a platform like Claris FileMaker, which can keep jobs, routings, and floor updates in one place across desktop, iPad, and web browser. The right answer matches how your floor works.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We help job shops pull capacity, routing, material, and due dates into one schedule the whole floor can see.

Frequently asked questions

Can a spreadsheet handle job shop production scheduling?

For a while, yes, if one person owns it and the job mix is stable. It struggles once several people update it at once and material and routing data live elsewhere.

What is the difference between an MES and a scheduling tool?

An MES (manufacturing execution system) tracks what is happening on the floor in real time: job status, labor, quality checks. A scheduling tool decides what should happen next. The two work best when they share the same job data.

Do we need accurate routing times before we start?

No. Start with the times you have and let actual floor data correct them over a few weeks.

Not sure your job data is solid enough to schedule from? Book a free 20-minute Data Health Check and we will tell you what we see.

Engineering Change Control for Manufacturers: Getting the Right Revision to the Floor

Engineering change control is the process that decides how a drawing or spec change gets requested, approved, and released, so every open job runs to the current revision. When it works, the machinist never has to wonder which print is right. When it does not, the floor finds out the hard way.

Here is the kind of Tuesday we hear about from contract machining shops. The engineer updated a bracket drawing to Rev C last week, moving one hole 0.020” for a customer fit issue. The traveler (the paper packet that follows a job through the shop) still holds a Rev B print from when the job was released. The operator runs 200 parts to Rev B. Inspection catches it two days later, after the parts have already gone to the plater.

Key takeaways

  • Map your current change path, from first email to operator’s print, and count the handoffs.
  • Give every ECR a home and a status, even if the first version is a shared form.
  • Record the revision on every released job so a change can find the work it affects.
  • Pull obsolete prints from the floor the day a new revision releases.
  • Attach customer-specific requirements to the order so they travel with the job.

How does the wrong revision reach a machine?

Almost never through carelessness. It happens because the revision lives in one place and the work lives in another.

  • The CAD folder has the new drawing, but nothing tells the scheduler that three released jobs use it.
  • Printed travelers outlive the revision they were printed against.
  • The customer’s change arrives by email to whoever answered the phone, and stays in that inbox.
  • Approval is a hallway conversation, so nobody can say later who signed off or when.

The cost shows up as scrap, rework, rush material, and a hard customer conversation. On an audited part, add a nonconformance report.

Give every change request a record of its own

The fix starts with two plain definitions. An ECR (engineering change request) is the formal ask: someone says “this part should change, and here is why.” An ECO (engineering change order) is the approved, released change: the decision that the new revision is official and what happens to work in progress.

An ECR can come from anyone, including the customer or an operator who sees a tolerance that cannot be held. An ECO is released by the people who own the design and the schedule.

A lightweight flow can look like this:

Someone submits an ECR with the part, current revision, reason, and markup

↓

Engineering reviews and drafts the new revision

↓

Quality and production weigh in on impact (tooling, inspection, open jobs)

↓

Approver signs off and the ECO is released

↓

New revision becomes the only one available for new work, and affected jobs are flagged

Nothing here needs a large team. It needs one place where the request lives, a clear status (submitted, in review, approved, released), and a named approver.

Linking revisions to open jobs is where control actually happens

When each job records the part number and revision it was released against, releasing an ECO can produce a list: every open job, every unshipped order, and every kitted traveler still pointing at the old revision. Each one gets a decision. Let it finish on Rev B because the customer agreed. Stop it and reprint. Rework the parts already made.

That decision gets recorded on the job, so nobody has to remember it. Kyo’s article on customizing production steps and requirements shows how routing and requirements can be tied to the specific job, which is the same structure a revision link depends on.

One shop rule needs no software at all: pull obsolete prints the day they are replaced instead of filing them next to the new ones.

Where do customer-specific requirements belong?

On the order, attached to the revision they apply to. Contract manufacturers often run one part for two customers with different marking or inspection rules. If those rules live in a sales rep’s notes, a revision change can quietly drop them.

Kyo’s post on reviewing and adopting requirements for specific orders covers how to capture those terms at order entry so they travel with the job. When an ECO releases, the change record should show whether any customer-specific requirement is affected, and who confirmed it.

The audit trail comes from the records you already keep

If you are certified to a quality standard, or your customers audit you against one, expect questions about how drawing revisions are controlled and how you know the floor used the right one. The exact requirements depend on the standard and the customer, so confirm them with your quality lead or registrar.

A change process built as records can answer many of those questions directly. Each ECR and ECO carries who asked, who approved, when it released, and what was decided for each affected job. Kyo’s article on maintaining historical records for future reference and replication shows why that history pays off when a part is reordered years later.

This can be built in many tools. A PLM (product lifecycle management) system may fit if you have a large engineering team. Some manufacturers do better with a focused workflow connected to the job and order data they already run, and a custom Claris FileMaker app is one way to build that without replacing the systems that work.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We can help shops connect engineering changes to the jobs and orders they affect, so the floor builds to the released revision.

Frequently asked questions

What is the difference between an ECR and an ECO?

An ECR (engineering change request) proposes a change and explains why. An ECO (engineering change order) is the approved, released change that makes the new revision official and decides what happens to work already in progress.

Do we need PLM software for engineering change control?

Not necessarily. Many manufacturers only need change requests, approvals, and released revisions linked to their jobs and orders, which a focused custom workflow can handle.

What should happen to jobs already running when a revision changes?

Each affected job needs a recorded decision: finish to the old revision with customer agreement, stop and reprint, or rework.

If revisions in your shop still travel by email and memory, book a free 20-minute Data Health Check and we will look at where the handoffs break.

What a FileMaker-Based ERP Should Cover for a Manufacturer

A FileMaker ERP for a manufacturer should cover seven connected jobs: quoting, orders, inventory, work orders, purchasing, shipping, and job costing, all reading from one shared record. You build them in stages, but you plan for all seven from the start. Everything else can wait until those seven run cleanly, and accounting can stay in the package you already use.

Here is a Tuesday morning we hear about often. A customer calls the operations manager asking when their order ships. She checks the order spreadsheet, walks to the floor to ask the lead which step the job is on, then emails purchasing to find out if the bar stock arrived. Three sources, three answers, and none of them agree with the whiteboard.

An ERP (enterprise resource planning system, software that ties sales, production, inventory, and purchasing into one record) exists to fix exactly that. The question is what yours needs to do.

Key takeaways

  • List the seven core modules and mark which ones today live in a spreadsheet, a whiteboard, or someone’s memory.
  • Name the single leak that costs you the most (margin, late shipments, or stock) and make that module your first stage.
  • Write down the features you can defer so they stay on the roadmap instead of creeping into phase one.
  • Leave accounting where it is and plan the integration, not a replacement.

Scope the FileMaker ERP around how your shop runs

Packaged ERP systems are built to cover every kind of manufacturer. That can leave you configuring around screens you never use while the workflow that makes your shop different stays in a side spreadsheet. A custom build starts from how work actually moves through your building. We have written about building a custom ERP around manufacturing workflows; this post is the scope checklist.

The seven modules that carry the day

Each module hands its data to the next. Miss a link and someone rekeys it.

  • Quoting. Material, setup, run time, outside processing, and margin in a repeatable model. An accepted quote becomes the order without retyping.
  • Orders. One record per customer order with part, revision, quantity, promise date, and status. This is where the “when does it ship” question gets answered.
  • Inventory. On hand, allocated, and on order for each item, with every receipt, issue, and adjustment logged so the count on screen matches the shelf.
  • Work orders. The job traveler in digital form: operations, routing, materials to pull, and who completed each step. This is also where WIP (work in process, jobs started but not finished) becomes visible.
  • Purchasing. Purchase orders tied to the jobs or stock levels that triggered them, with expected dates feeding order promise dates.
  • Shipping. Pick, pack, and ship against the order, with tracking on the same record customer service reads.
  • Job costing. Estimated versus actual material, labor, and outside services per job, so the next quote learns from the last one.

Why does one source of truth matter more than any single module?

Now the same Tuesday, after the build. The operations manager opens the order. She sees the work order is at deburr, the bar stock has arrived, and the ship date still holds. One screen, one answer.

That only works because the modules share records instead of passing files:

Quote accepted

↓

Order created with the quoted part and price

↓

Work order generated, materials allocated

↓

Shortages raise a purchase order

↓

Job completes, shipment recorded

↓

Actual costs roll up against the original quote

The integration between your ERP and CRM follows the same rule. Customer data lives in one place and every module reads it from there.

What can wait until phase two?

Reasonable candidates for the roadmap rather than the first release:

  • MRP (material requirements planning, automated forecasting of what to buy and when) until you trust your inventory counts.
  • Finite scheduling (planning jobs around real machine and shift capacity), once work orders are reliably tracked.
  • Quality and nonconformance tracking, unless a customer or certification requires it now.
  • Portals and dashboards beyond the few reports you check daily.

These all depend on clean data from the core seven, and they are far easier to build once that data exists.

Build first where money leaks today

A staged build usually works better than a big-bang cutover (switching everything over on one date): each stage proves itself before the next begins, and your team learns the system a piece at a time. Let the money set the order.

  • If jobs regularly lose margin and nobody knows why until month end, start with quoting and job costing.
  • If customers call to ask where their order is, start with orders and work orders.
  • If you expedite material or find stock you already owned, start with inventory and purchasing.

Pick the costliest leak, run that module for a few weeks, then connect the next. Our earlier piece on why FileMaker is an inexpensive alternative to packaged ERPs covers the cost side of that choice.

Where does accounting fit?

Keep it where it is. Your bookkeeper knows QuickBooks (or whatever you run), your accountant reviews it, and rebuilding a general ledger adds risk without adding value. The ERP handles operations, the accounting package handles the books, and an integration carries customers, invoices, and vendor bills between them so nobody types an invoice twice. Claris documents a QuickBooks connector in Claris Connect, its integration service, with actions such as creating customers, invoices, and purchase orders. Plug-ins and direct API connections are other options, and the right one depends on which edition of QuickBooks you run.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We scope FileMaker ERP builds module by module, starting with the one that is costing you the most today.

Frequently asked questions

Can FileMaker be used as an ERP for a manufacturing company?

Yes. FileMaker can run quoting, orders, inventory, work orders, purchasing, shipping, and job costing in one connected system. It is one option among several; the bigger decision is scoping around how your shop works.

Do we have to replace QuickBooks to use a FileMaker ERP?

No. Accounting can stay in the package you already use, and an integration connects the two so customers, invoices, and bills are not entered twice.

How long does it take to get the first module running?

It depends on the module and how clean your existing data is. A staged approach puts one module into daily use before the next begins.

If you want a second set of eyes on where your data is breaking down, book the free 20-minute Data Health Check.

Manufacturers: Passing a Customer Quality Audit Without a Fire Drill

The best way to pass a customer manufacturing quality audit is to make traceability part of normal production. Connect each job to its material lots, inspections, process records, certificates, and approved revisions as the work happens. Then an audit request becomes a search and review, not a week of reconstructing evidence.

Good documentation does more than satisfy an auditor. It shows a customer that the shop can control repeat work and respond when something goes wrong.

Key takeaways

  • Make traceability part of normal production: link every job to its material lots, inspections, approved revisions, and certificates as the work happens.
  • A review-ready job record answers six questions: which specification governed the work, and which certificates shipped with it.
  • Start by reconstructing one recent shipment the way an auditor would, then fix the first place the trail breaks.

The audit request arrives on Tuesday

A major customer asks for the material certification, inspection results, and process history for three shipments. The quality manager knows the records exist, but not in one place.

One certificate is attached to a receiving email. Inspection results are in a workbook. The traveler is in a file cabinet. A revised drawing is on the shared drive, but the team cannot immediately prove which revision production used. The request is due Friday.

People stop their ordinary work to search. The quality manager becomes the coordinator for a system that should already know the answer.

Kyo’s article on automating certificates of conformity and test reports shows how structured job data can make required outputs repeatable.

Traceability should start before production

Audit readiness begins when the order and specification enter the system. The job should identify the customer requirement, approved drawing or specification revision, required inspections, material rules, and any documents that must follow the shipment.

Material receipt

↓

Lot or heat recorded and documents attached

↓

Material issued to a specific job

↓

Operations and inspections recorded

↓

Shipment package generated from the job record

This chain creates context. A certificate is not merely a PDF in a folder. It is evidence for a specific received lot that was used on defined jobs and shipments.

Kyo covers the material side in tracking raw materials, formulas, and processes. The system must preserve the identifiers that matter to the company’s products and customer obligations.

What should the job record prove?

A review-ready job record should make it practical to answer:

  • Which customer order and specification governed the work?
  • Which material lots or batches were consumed?
  • Which operations were completed, by whom, and when?
  • Which inspections were required and what were the results?
  • Which nonconformances, deviations, or rework events occurred?
  • Which certificates and reports accompanied the shipment?

The exact evidence depends on the contract, industry, and quality system. Software should support those requirements, not invent them. The quality team owns the procedure and retention rules; the application makes consistent execution and retrieval easier.

How does documentation become a sales advantage?

A customer does not want a polished audit day followed by unreliable daily work. It wants evidence that the supplier can reproduce the same control on the next order.

Fast retrieval sends a clear signal. When the customer asks about a lot, the team can produce the job, material, inspection, and shipment chain without improvising. When a correction is needed, the shop can identify affected work and respond with scope instead of uncertainty.

That credibility supports renewals and larger contracts. Kyo’s article on manufacturing CRM and compliance standards explains why quality history belongs in the customer relationship, not only in a quality folder.

Start with the hardest record to retrieve

Choose one recent shipment and try to reconstruct its evidence as an auditor would. Time each step. Note where the chain depends on a person’s memory, an email search, or an ambiguous filename.

Then fix the highest-risk break. That may be material-lot capture, revision control, inspection completion, or document generation. Use required fields and status gates carefully, so the system prevents missing evidence without encouraging people to enter meaningless placeholders.

Test normal exceptions too: substituted material, split lots, partial shipments, rework, and a revised specification after release. An audit-ready system needs to tell the truth when the path is not tidy.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We turn existing quality procedures into connected workflows that make evidence easier to capture, review, and retrieve.

Frequently asked questions

What records do customers usually request during a quality audit?

Requests may include specifications, material certificates, lot traceability, inspection results, process records, training evidence, nonconformance records, and shipment documents. Contract and quality requirements determine the exact set.

Does software make a manufacturer compliant?

No. Software can support controls and evidence, but compliance depends on applicable requirements, procedures, execution, oversight, and validation.

Should audit documents be stored separately from job records?

Files may live in a document store, but the system should maintain a reliable relationship between each document and the job, material, inspection, or shipment it supports.

Pick one shipped job and bring it to a free 20-minute Data Health Check. We will trace its audit evidence with you and show where the trail breaks.

Do Manufacturers Need a Separate CRM, or Can Claris FileMaker Do the Job?

Yes. FileMaker can serve as a capable manufacturing CRM when customers, quotes, jobs, and service history already live in the same custom application. A separate CRM makes more sense when the company needs specialized sales automation, marketing operations, or enterprise capabilities that should remain outside the production system.

The right answer depends on what “CRM” means to the team. For a manufacturer, customer relationships are often inseparable from operational performance.

Key takeaways

  • Claris FileMaker works well as a manufacturing CRM when customers, quotes, jobs, and service history already live in the same system.
  • A separate CRM earns its place when you need large-team sales automation, marketing operations, or a company-wide standard, with each system owning clearly defined fields.
  • Either way, data quality decides whether people trust it. Set matching rules and account ownership before you automate anything.

A manufacturer’s CRM needs more than contact notes

A generic CRM usually centers on leads, opportunities, activities, and pipeline. Those records matter, but an account manager at a custom manufacturer also needs answers from the shop.

What did this customer order last year? Which drawing revision governed the current job? Did the last three orders ship on time? Is a quality issue still open? Which quote resembles the new request, and was that work profitable?

When FileMaker already holds the jobs and quotes, a customer record can connect those facts without copying them into a second product.

Customer and contacts

↓

Opportunities and quotes

↓

Jobs, requirements, and production status

↓

Shipments, issues, and follow-up

The CRM becomes a record of the working relationship. Sales sees operational truth in an appropriate view, while production keeps control of the detailed workflow.

What should a FileMaker manufacturing CRM include?

Start with the work the team performs, not a checklist from a software comparison page:

  • Account, location, and contact relationships.
  • Opportunities, next actions, ownership, and expected value.
  • Quote history, versions, assumptions, and outcome.
  • Open jobs, current promise status, and relevant exceptions.
  • Customer requirements, documents, and communication history.
  • Service issues, corrective actions, and follow-up commitments.

FileMaker can present these records through role-specific layouts and scripted workflows. The exact security model, mobile behavior, integrations, and performance should be validated for the solution and current FileMaker version.

Kyo’s article on integrating ERP and CRM for manufacturing shows why connected operational and customer data gives the team a more useful picture than two isolated dashboards.

Data quality decides whether the CRM is trusted

A custom CRM can still fail if every department creates its own version of the same account. Define matching rules, ownership, required fields, and review paths for suspected duplicates. Preserve useful history when records merge.

The process should handle common problems:

  • The same company appears under a legal name and a trade name.
  • A contact moves to another customer.
  • Two salespeople create the same prospect.
  • Shipping and billing addresses are treated as separate accounts.
  • Imported lists contain stale or incomplete records.

Kyo’s detailed guide to CRM cleanup in FileMaker covers standardizing, merging, and validating the data before automation multiplies the mistakes.

When should a manufacturer buy a separate CRM?

A dedicated CRM may be better when the company has a large sales organization, sophisticated territory and compensation rules, mature marketing automation, many external sales integrations, or a corporate standard shared across multiple business units.

The system should earn its separation. Define which product owns each shared fact. The CRM may own leads, opportunities, and sales activity. FileMaker may own accepted quotes, jobs, and production status. Customer identity and status changes need a controlled exchange with monitoring for failed or duplicate transfers.

Do not let both systems casually edit the same fields. That creates a daily sync argument the business must resolve.

Kyo’s article on tailoring CRM systems for manufacturing compliance adds another consideration: permissions, customer requirements, and evidence may need to cross the boundary without exposing unrelated operational data.

How should you decide?

Map one customer relationship from first inquiry through repeat order. List the questions each role needs to answer and the source for each answer. Then identify the workflows that are unique to the company and the capabilities that are genuinely standard.

Use FileMaker as the CRM when the value comes from connecting customer work to the custom operational model. Use a separate CRM when its specialized sales capabilities outweigh the cost of integration and ownership.

The goal is not to replace a useful platform. It is to put each responsibility in a system the business can govern.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We help manufacturers extend the FileMaker systems they already trust and connect a dedicated CRM when the business case calls for one.

Frequently asked questions

Is FileMaker CRM software?

Yes. Many manufacturers run their CRM in Claris FileMaker. Because it is a custom application platform, a development team builds the CRM around the company’s own customers, quotes, and jobs, and connects it to other operational workflows.

Can FileMaker track opportunities and sales activity?

Yes, a solution can model opportunities, ownership, stages, tasks, communication, quotes, and related records. The design should reflect the company’s sales process.

Can FileMaker connect to a separate CRM?

Often, yes. The integration method depends on the CRM, available APIs, authentication, data ownership rules, and monitoring requirements.

Not sure where your customer data should live? Book a free 20-minute Data Health Check, and we will map what your system already knows about each customer.

Preventive Maintenance Tracking Without Buying a Separate CMMS

Preventive maintenance tracking does not have to live in its own software. For many manufacturers, the simplest working version is a maintenance record inside the system that already runs jobs and schedules, so the next service window shows up right next to the work it will interrupt.

Picture the second-shift lead on a Thursday night. The spindle on the older horizontal mill starts to whine. The service sticker is faded, the clipboard by the machine stops in June, and the tech who keeps it all in his head is on vacation. Friday’s hot job is scheduled on that mill.

That is the problem this post is about. Not a missing app. A missing record.

Key takeaways

  • You may not need a separate CMMS. A maintenance record inside the system that already runs your schedule is often enough.
  • Each record needs five things: asset, interval, last done, next due (calculated, not typed), and parts.
  • Put maintenance windows on the production schedule and check tasks off at the machine, so planned downtime stops colliding with promised work.
  • Start with the five to ten machines whose failure would hurt a delivery date most.

Paper and memory fail at the worst possible moment

Most shops already do preventive maintenance. The trouble is that the record lives in three places: a sticker on the machine, a binder in the office, and one experienced person’s memory.

Someone has to remember the interval. Someone has to find the binder. Someone has to notice that a machine running double shifts hits its hour-based service twice as fast as the calendar suggests. When any link breaks, preventive maintenance quietly becomes reactive maintenance, and that always lands on the busiest week.

What does a minimum maintenance record need?

A useful preventive maintenance record answers five questions:

  • Asset: which machine, press, compressor, or fixture, with a unique ID you can put on a tag.
  • Interval: how often the task is due, by calendar days, run hours, or cycles.
  • Last done: the date (or meter reading) of the most recent completed service, and who did it.
  • Next due: calculated from the interval, not typed by hand, so it cannot drift.
  • Parts and supplies: the filters, belts, or lubricants the task consumes, so they are on the shelf before the window opens.

Add a checklist per asset and a notes field, and you have a history that survives vacations and retirements.

Maintenance windows belong on the production schedule

When the next-due date for the mill lives in the same place as the jobs booked on the mill, the conflict is visible before it happens.

A basic flow might look like this:

Asset reaches its interval (date, hours, or cycles)

↓

Maintenance task appears as “due soon” with a target window

↓

Scheduler sees the window beside the jobs booked on that machine

↓

Planned downtime is placed between jobs, not in the middle of one

↓

Completed task resets the next-due date automatically

If your system already captures run time or cycle counts, as described in Kyo’s post on gathering real-time production statistics, usage-based intervals can be driven by actual machine use instead of a guess. Overdue tasks can then surface the same way other problems do, on an exception view for orders and inventory that shows only what needs attention today.

Check-offs should happen at the machine, not at the desk

If the tech has to walk back to an office PC after every task, entries get batched at the end of the shift and details get lost.

Mobile check-off fixes that. The tech scans a tag on the machine, the right task list opens, they tick off each step, snap a photo of the worn belt, and sign. No paper form. No photo hunt. No duplicate entry.

This works on several platforms. If you run Claris FileMaker, it is one practical option: Claris documents that FileMaker Go’s Insert from Device script step can capture photos, scan barcodes, and collect signatures on an iPhone or iPad. Kyo’s post on mobile capture with photos, signatures, and QR codes walks through what that looks like in practice.

When is a standalone CMMS worth it?

A CMMS (computerized maintenance management system) is software built specifically to plan, track, and document maintenance work. For some operations it is exactly the right call.

A dedicated CMMS often makes sense when:

  • You have a full maintenance department with its own planners and a large, complex asset base.
  • You need deep spare-parts inventory management, vendor service contracts, and maintenance cost accounting.
  • Regulators or customers require formal maintenance documentation and reporting that a purpose-built package already handles.
  • Maintenance runs largely independent of production scheduling.

It is often more than you need when a couple of techs handle maintenance alongside other work, the asset list fits on a page or two, and the real pain is visibility rather than planning depth. Then a separate system adds another login and another set of data that does not talk to your schedule. The better fit is usually extending what already works.

How do you know it is paying off?

Track these from the record itself:

  • Unplanned stops per month on the machines you put on a schedule.
  • Percent of tasks completed on time versus overdue.
  • Jobs rescheduled because of a breakdown.

Give it a quarter and watch the trend move from surprise to plan.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We help shops put maintenance records next to the production schedule so planned downtime stops colliding with promised work.

Frequently asked questions

Can we track preventive maintenance in a spreadsheet?

You can start there, but spreadsheets struggle with usage-based intervals, mobile check-offs, and per-asset history. Most shops outgrow them once more than one person updates the file.

Should intervals be based on calendar time or machine hours?

Use whatever the equipment manufacturer recommends for each task. Many machines need both: some tasks by calendar, others by run hours or cycles. Your record should support either.

What if we already have some maintenance history on paper?

Enter the most recent completed service per asset to set accurate next-due dates. Scan and attach older history later if audits or warranty claims need it.

Not sure what your current data can support? Book a free 20-minute Data Health Check and we will take a look together.

Shop-Floor Visibility Without a Full ERP: Tracking Jobs, Materials, and Status in One Place

You can get reliable shop-floor visibility without buying a full ERP. A focused custom app can connect each job to its materials, operations, costs, and current status, giving the team one place to answer where the work is, what it is costing, and whether it will ship on time.
The value is not a prettier production board. It is a record that changes as the work changes.

A job traveler should not disappear into the shop

Job 4521 starts with an approved quote and a promised date. Planning releases the traveler. Material moves to cutting. The first operation finishes, but the paper traveler waits on a cart. The schedule still says the job is in cutting. Sales tells the customer everything is on track because no one has reported a problem.
At inspection, the team finds a dimensional issue. Two parts need rework. The note goes on paper, the cost goes nowhere, and the promise date becomes a guess.
A visible system records each transition where it occurs. The operator does not write a status in one place and ask someone else to update another. Starting, pausing, completing, scrapping, and moving material are the events that build the current picture.
Kyo’s article on gathering real-time production statistics explains why the useful report begins with reliable activity capture.

Can the shop answer three basic questions?

Every production system should answer:

Where is the job? Show the current operation, work center, queue position, and blocker.
What is it costing? Connect labor, material, outside services, scrap, and rework to the job.
Will it ship on time? Compare remaining work, required material, capacity, and the promise date.

Spreadsheets often answer one question at a time. A schedule may show dates but not material shortages. An inventory file may show quantity but not what is reserved. A costing sheet may be complete only after the job closes.
Visibility comes from relationships. Job 4521 should point to its operations, material demand, actual issues, quality results, and shipment. Each screen can stay simple because the records underneath are connected.

What does one source of truth look like?

Quote becomes job
↓
Job creates operations and material demand
↓
Shop activity updates status and actual cost
↓
Exceptions appear before the promise is missed
↓
Shipment closes the operational record
Materials belong in that flow. When receiving records a delivery, available inventory changes. When a job pulls material, on-hand and job cost change together. When unused material returns, both records are corrected through a controlled transaction.
Kyo covers that pattern in real-time inventory tracking. The point is not to make the number move faster. It is to make the movement explainable.

Build the screens around work, not around tables

An operator needs a short queue, clear instructions, required documents, and a fast way to report the result. A planner needs capacity, shortages, blocked work, and late-risk indicators. Sales needs a customer-facing status without access to internal production details.
One application can provide those different views while keeping one underlying job record. That is more useful than forcing every role into the same crowded dashboard.
The workflow also has to allow real exceptions. A job may skip an operation, return for rework, split into partial shipments, or wait on customer approval. Kyo’s article on customizing production steps and requirements shows why the system must reflect how the shop actually routes work.

Start with one value stream

Do not begin by digitizing every form in the building. Pick one product family or work center where visibility is poor and the business effect is clear. Define the status events, material transactions, and exceptions that matter. Pilot them with the people doing the work.
Measure practical outcomes: fewer status-chasing messages, earlier shortage detection, more accurate job cost, and fewer late surprises. Small production issues become large delays when the system hides them until the schedule is already broken.

Frequently asked questions

Do we need an ERP to track production in real time?

No. A focused application can capture production events and report current status. The right architecture depends on volume, integrations, devices, and availability requirements.

How does a custom app know where a job is?

Operators or connected equipment record defined events such as start, pause, complete, move, inspect, or ship. Those events update the job’s current state.

Can the app track materials with the job?

Yes. Receipts, reservations, pulls, returns, and scrap can be modeled as transactions tied to the job and inventory item.

What should we pilot first?

Choose a workflow with frequent status questions or costly late surprises, and include normal exceptions rather than testing only the ideal path.

Where to start

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We design shop-floor tools around the decisions each role makes, then connect those views to one controlled operational record.

If your team cannot answer where a job is without walking the floor, talk with Kyo Logic about a focused visibility pilot.

Manufacturers: The Real Cost of Running Production on Disconnected Tools

Disconnected manufacturing tools cost more than their subscription fees. When an order lives in QuickBooks, spreadsheets, email, and a whiteboard, the shop pays through duplicate entry, stale status, preventable expediting, and decisions made from conflicting information. A connected custom system reduces that tax by giving each business event one controlled home.
The problem is easy to miss because each tool works on its own. The cost appears in the spaces between them.

One order lives four different lives

A customer emails a revised purchase order. Sales updates the quote spreadsheet. Production is already using a printed traveler based on the first version. Purchasing has material demand in another workbook. Accounting creates the customer order in QuickBooks using the new quantity but the old promised date.
Nothing looks broken in isolation. Every file opens. Every team can point to a record. Yet the company no longer has one answer to a basic question: What did we promise?
Someone forwards the email.
Someone updates the traveler.
Someone finds the mismatch after material has been cut.
Kyo’s article on misaligned sources of truth in manufacturing explains why these conflicts become operational risk, not merely administrative inconvenience.

What does the disconnected-tools tax include?

Rekeying time. The same customer, part, quantity, and date are entered in multiple places. That work creates no new value and introduces opportunities for error.
Version disputes. People spend time proving which spreadsheet, attachment, or message is current. Decisions wait while the team reconstructs history.
Late exceptions. A shortage or delay sits inside one tool until someone manually carries it to the person who can act.
Unreliable costing. Material, labor, rework, and outside services arrive on different schedules. The real margin appears after the team has already quoted the next job.
Customer trust. Sales gives an answer based on the system it can see. Production knows something different. The customer experiences the mismatch.
One more spreadsheet often feels cheaper than changing the process. Kyo’s piece on when one more spreadsheet becomes a bottleneck shows when that trade stops working.

Why is a bigger ERP not automatically the fix?

An enterprise ERP can connect broad business functions, but it also brings a broad implementation. A custom manufacturer running quotes, jobs, and materials across separate tools may need a focused system for quote-to-job flow, shop status, materials, and exceptions, while keeping accounting or another specialized product in place.
Replacing four disconnected tools with one oversized system can trade one problem for another. If the workflows do not match the shop, people rebuild the old process in side spreadsheets.
The better starting question is: Which facts must remain connected from the customer’s request through shipment? Build or select the system around those facts and define clean boundaries with every tool that remains.

What would a connected custom system change?

Customer revision received
↓
Controlled order version updated
↓
Material demand and production plan recalculate
↓
Affected roles see the exception
↓
Customer promise is confirmed or changed
The app does not need to perform every function. It needs to make ownership clear. Accounting can remain authoritative for financial transactions. The custom system can own the operational job, material requirements, and status. The integration should pass defined facts with a visible failure queue.
Kyo’s article on FileMaker as an affordable ERP alternative gives another view of how smaller manufacturers can buy the control they need without adopting enterprise weight.

Measure the cost before choosing the cure

For two weeks, track how often people re-enter the same data, ask for status, correct a mismatch, expedite material, or discover a change late. Record the minutes and the business effect. Include supervisors and operators, not only office staff.
That evidence shows where connection matters first. It may point to one workflow, such as order revision control, rather than a complete system replacement. A bounded first project is easier to test and more likely to earn adoption.

Frequently asked questions

What are disconnected manufacturing tools?

They are systems or files that hold related operational information without a reliable shared record or controlled exchange.

Are spreadsheets always a problem in manufacturing?

No. Spreadsheets are useful for analysis and temporary work. Risk rises when they become the authoritative system for a shared, changing operation.

Does a connected system have to replace QuickBooks?

No. Accounting can remain in QuickBooks while a custom operational system manages jobs, production, and material flow through a defined integration.

How can we estimate the hidden cost?

Track duplicate entry, correction, status-chasing, expediting, and late discovery for a representative period, then attach labor and business impact to each event.

Where to start

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We connect the records and handoffs that run the shop while preserving the systems that still do their jobs well.

If the same order has a different answer in every department, contact Kyo Logic to map the smallest connected workflow that would remove the conflict.

Manufacturers: Getting Quotes Out Faster Without Underpricing the Job

Manufacturers can get quotes out faster without underpricing by capturing the same cost inputs in a repeatable model, reusing relevant history, and recording assumptions that production can later test. Speed should come from structure, not from removing the detail that protects margin.

Custom and contract shops often feel forced to choose: quote fast and guess, or quote carefully and lose the opportunity to a quicker competitor. A connected process removes much of that trade.

The rush quote starts with incomplete information

A prospect sends a drawing and asks for pricing by tomorrow. Estimating needs material, quantity breaks, setup, run time, outside processing, inspection, packaging, and margin. The closest past job is buried in a folder, and its actual labor was never compared with the estimate.

The estimator knows the work but spends the morning rebuilding inputs. Under time pressure, one outside-service fee is left as a placeholder. The quote goes out. The shop wins the order and discovers the missing cost after production begins.

Fast quoting is not mainly a typing problem. It is a data-reuse and handoff problem.

Which inputs should every manufacturing quote capture?

A structured quote can separate:

  • Material: item, grade, size, quantity, yield, scrap factor, and current price basis.
  • Labor: setup and run assumptions by operation or work center.
  • Outside services: process, supplier estimate, freight, and expected lead time.
  • Quality and documentation: inspections, testing, certificates, and customer-specific requirements.
  • Commercial assumptions: quantity breaks, lead time, validity, margin, and exclusions.

Kyo’s article on capturing client-provided materials, specifications, and requirements shows why the intake record should preserve the details that drive price and production.

The model should make missing information visible. It should not silently turn an empty field into zero cost.

How does a past job make the next quote better?

New request received

↓

Comparable jobs found by part, process, material, or customer

↓

Estimate and actual results compared

↓

Assumptions adjusted for the new quantity and conditions

↓

Approved quote becomes the production job

Past jobs are useful only when their actual results are trustworthy. The estimator should see estimated versus actual material, setup, labor, scrap, and outside service. A similar job with a large variance deserves investigation, not blind reuse.

The explanation matters too. A note such as “first article required two fixture changes” gives the number context that a raw total cannot.

The clean handoff prevents the second round of entry

When the customer accepts, the approved quote should create or populate the operational job. Customer details, part and revision, quantity, required date, operations, material assumptions, outside services, and quality requirements should move through a controlled handoff.

That avoids rekeying and preserves what the business sold. Production can see which assumptions were approved and flag a change before it becomes unplanned work.

Kyo’s article on connecting online orders to billing, inventory, and shipping demonstrates the broader value of carrying structured information through the order lifecycle.

Approval rules should follow risk

Not every quote needs the same review. Set approval thresholds around margin, total value, unusual material, new processes, expedited lead time, or missing cost inputs. A routine repeat job can move quickly. A first-time aerospace part with outside testing should receive the attention its risk deserves.

The system should record who approved the quote and which version the customer accepted. When the request changes, create a new version instead of overwriting the original assumptions.

After the job closes, compare estimate with actual and route meaningful variance back to estimating. That feedback protects future pricing. Kyo’s discussion of custom ERP solutions for manufacturing shows how one operational data model can connect those stages.

Frequently asked questions

What is the fastest way to improve manufacturing quoting?

Standardize required inputs, expose missing information, and make comparable estimate-versus-actual job history easy to find.

Should a quote use current material prices?

The company should define its price source, effective date, validity period, and treatment of volatile material. Those rules should be visible in the quote.

Can quoting software prevent underpricing?

It can reduce missing inputs and apply approval rules, but it cannot remove commercial judgment or guarantee a profitable outcome.

What should happen when a quote is accepted?

The approved version should hand customer, part, quantity, operations, materials, requirements, and promise information into the job without uncontrolled reentry.

Where to start

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We turn quoting knowledge into a repeatable workflow that helps estimators respond faster while keeping the assumptions visible.

If your best estimator rebuilds every quote from memory, talk with Kyo Logic about a structured quote-to-job workflow.

Manufacturers: How to Stop Missing Delivery Dates You Promised

To stop missing manufacturing delivery dates, connect each customer promise to material readiness, real capacity, and current production status. Then surface risks while the team can still resequence work, expedite the right item, or reset the commitment. A promise date stored only on an order is not a schedule.

On-time delivery is trust. One late job can damage a customer relationship that took years to build.

Why does a believable promise become late?

Sales commits to Friday based on a normal lead time. Planning puts the job on a whiteboard. A required component is due Wednesday, but the purchase order slips. Cutting loses half a shift to rework on another job. Inspection becomes a queue. Each team knows part of the story, but no shared view recalculates the risk.

On Thursday afternoon, the job is still two operations from complete. The customer learns only after asking.

The missed date is the final event. The causes appeared earlier as a late material receipt, a capacity conflict, a stalled operation, or a quality exception.

Kyo’s article on why small production issues become big delays shows why early visibility changes the response.

A promise date needs an operational chain

Customer requirement accepted

↓

Material and outside-service dates confirmed

↓

Operations scheduled against real capacity

↓

Shop activity updates remaining work

↓

Exceptions change the projected completion date

A shared schedule should distinguish the requested date, committed date, planned completion, and current projected completion. Those values answer different questions. Hiding them in one field prevents the team from seeing whether a commitment is drifting.

The production record also needs a definition of “complete.” A job may leave the last machine but still require inspection, documentation, packaging, or an outside process. The schedule should include every step required to ship.

Which warning signals matter before a job is late?

The team does not need more notifications. It needs a short exception list tied to action:

  • Required material is not available by the operation need date.
  • An operation has not started by its planned time.
  • Reported scrap or rework threatens the required quantity.
  • Remaining work exceeds available capacity before the promise date.
  • An outside service has no confirmed return date.
  • A required approval or inspection is still open.

Kyo’s article on gathering real-time production statistics describes the activity data that makes these warnings credible.

Each exception should have an owner and a next review time. Otherwise, the dashboard becomes another place where late work is displayed without being managed.

Schedule from status, not from a weekly reconstruction

A schedule is only as current as its inputs. If operators report completion at the end of the week, the system cannot warn the planner on Tuesday. Capture start, pause, completion, quantity, and blocking reason close to the work.

That does not require a complicated interface. A station may show the ready queue and a few clear actions. The system can calculate remaining work and risk from those events.

Planning also needs controlled ways to resequence jobs. A rush order may be the right decision, but the software should show which existing promises it displaces. Capacity is not created by changing a color on a board.

Kyo’s guide to production planning with FileMaker workflow automation explains how structured status and planning can remain connected.

Tell the customer before the customer asks

Even a strong system cannot prevent every delay. Material shortages, equipment failures, quality problems, and changed customer requirements still happen. The operational advantage is recognizing the effect early.

Sales can contact the customer with a specific explanation, a revised date, and options. That is different from discovering the problem when the promised shipment does not arrive.

Track the reason for each changed commitment. Over time, management can see whether misses come from quoting, purchasing, capacity, quality, outside services, or status capture. Fixing the recurring cause improves more than one schedule.

Kyo Logic builds custom Claris/FileMaker and manufacturing software for New England companies. We connect customer commitments to real shop activity, so teams can manage delivery risk before it becomes a broken promise.

Frequently asked questions

What is the difference between a promise date and a projected date?

The promise date is the commitment made to the customer. The projected date is the system’s current estimate based on material, capacity, status, and remaining work.

Can production software guarantee on-time delivery?

No. It can improve planning, visibility, and response, but actual delivery also depends on suppliers, equipment, quality, staffing, and operating discipline.

What status should operators record?

Capture only what supports decisions, commonly start, pause, complete, quantity, scrap or rework, and a blocking reason.

What should a late-job dashboard show?

Show the affected promise, current operation, remaining work, material or capacity constraint, risk reason, owner, and next action.