Jay Byam

Spreadsheet-and-paper tracking works for a while, then the binder fills, the spreadsheet gets messy, downtime reasons collapse into "misc," and operators stop logging because no improvement comes from it.

• The fix they describe is a system that fits how the work actually flows, makes logging fast and low-friction, and turns entries into visible feedback.
• The standard is deliberately modest: data collection does not have to be perfect; it only has to be worth doing.

The post traces the failure sequence directly: the binder fills up, reasons become "misc," "Nobody has time to analyze it," and "operators quietly stop logging because nothing useful ever comes back to them." Byam's summary: OEE fails not because people don't care, but because the system doesn't return value fast enough.

Read original

Leadership at expensive plants requires proof before approving improvements — downtime data to justify replacing a machine, lost hours to justify more operators — so the data has to withstand scrutiny.

• But when a line is down, restarting it takes priority over documenting it.
• Details get lost, failures are simplified, and events are missed.
• The result: a weak case for the fix, repeated questions, delayed spending, and the same failures recurring.

An aluminum mill with roughly $800,000 of material moving through the plant every hour, running 1940s machines.

• Operators write stoppage reasons on paper, and planners or managers key them in later — what the plant can do without automation.
• Byam frames the trap: "The plants losing the most money from downtime often have the weakest downtime data."

Read original

OEE reports how a plant is performing, but not what matters most.

• Pricing individual downtime causes shifts the conversation from opinion to evidence, moves managers from lobbying to proving, and gives operators numbers behind them.
• The key is specificity: dollars tied to particular causes, not just aggregate production.

The same downtime event reads two ways.

• As "Unplanned stop – 3.2 hours," it gets discussed; as "Unplanned stop – $47,000 last quarter," it gets prioritized.
• Byam says most plants already hold enough data to do this.
• The closing line: "Metrics measure.
• Price tags get things fixed."

Read original

In the project they describe, production engineers helped shape how the data should work, and operators improved the system while on shift — flagging entries that did not reflect reality, simplifying steps so they worked in practice, and catching edge cases early.

• The payoff was better data, faster insight, and far less friction getting the change to hold.
• Byam's conclusion is blunt: the difference is not the software, it is the team.
• These posts carry the Kartorium name, but they point to the team, not the tooling, as the decisive factor.
• Since Byam describes this engagement as rare, ask for evidence that it can be repeated.

The contrast is between a rollout that "felt like pulling teeth" and one where engineers shaped the data design and operators corrected the system in real time. Byam calls the engagement rare and credits it with making the project work.

Read original

The focus is less on events as marketing than on learning and exchanging operational experience.

Byam names the MD&M trade shows and describes the short face-to-face chats as "the part worth showing up for."

Read original

Jay Byam describes a familiar pattern: teams track overall equipment effectiveness with spreadsheets and paper logs, but the binder fills up, the spreadsheet gets messy, downtime reasons become “misc.,” and operators stop logging because nothing useful comes back to them.

• The post rejects the easy explanation that operators are “not disciplined enough” or “not bought in.”
• Instead, it argues that tracking has to fit the way work flows, make logging fast and frictionless, and turn entries into visible feedback.
• The line “OEE doesn’t fail because people don’t care.
• It fails because the system doesn’t return value fast enough” sums up the idea.

For brands planning a campaign

For a collaboration on OEE and downtime data, this points away from a pure data-collection message and toward adoption, feedback loops, and operator experience. A campaign could ask what makes logging worth doing on shift, not just what data should be captured.

The post opens with a concrete scene: an aluminum mill has about $800,000 of material moving through the plant every hour, and when the plant stops, that value stops moving.

• Leadership understands the stakes, so every improvement requires proof: show downtime data to replace a machine, or show where hours are lost to add operators.
• But failures are recorded with pen and paper because the machines are from the 1940s, and managers enter the notes into the system later.
• When a line is down, getting it running again takes priority; details get lost, failures get simplified, and events get missed.
• The strongest observation is the paradox: plants losing the most money from downtime often have the weakest downtime data.

For brands planning a campaign

This original shows the operational pressures that make downtime data hard to collect. A collaboration could focus on practical capture methods that work during a stoppage, rather than assuming clean data already exists or dashboards alone will solve the problem.

Jay Byam argues that most manufacturing teams have both a data problem and a prioritization problem.

• Even when data exists, it rarely answers “What should we fix first?”
• OEE tells you about performance, but not necessarily what matters.
• The post contrasts two ways to report a downtime reason: “Unplanned stop – 3.2 hours,” which gets discussed, and “Unplanned stop – $47,000 last quarter,” which gets prioritized.
• Most plants already have enough data, the post says; the missing piece is tying dollars to specific causes rather than just total production.
• That shifts conversations from opinions to evidence, stops managers lobbying and gets them proving their case, and helps operators back up what they say with numbers.

For brands planning a campaign

This is a strong angle for a collaboration on OEE and downtime data because it shifts the conversation from measurement to decision-making. A campaign can ask how teams translate downtime reasons into cost, priority, and capital cases.

This post describes a project that did not feel like “pulling teeth.”

• Production engineers were not just waiting for results; they were shaping how the data should work.
• Operators were not reluctantly entering data; they were improving the system in real time by flagging what did not reflect reality, simplifying it for use on shift, and catching edge cases early.
• Jay Byam sums up the lesson: “The difference isn’t the software.
• It’s the team.”
• The point is less about a tool than about what makes a data project stick: engaged engineers, operators who can change the system, and rapid removal of friction.

For brands planning a campaign

A collaboration should avoid implying that software alone changes behavior. It could feature the team practices and feedback loops that make OEE or downtime data projects succeed, with operators and engineers as active participants rather than passive data sources.

Jay Byam admits conferences are not a favorite, but says the ten-minute face-to-face chats are where much of the learning happens.

• The post makes in-person conversation the reason to show up.
• It is a short, direct account of how manufacturing ideas move through conversations at trade shows and industry events, not just through formal presentations or content.

For brands planning a campaign

A collaboration could work well through event-based or conversation-led formats, such as trade-show discussions, interviews, or short field conversations, as well as long-form posts or product demonstrations.

The fix is not stricter operator discipline but a system that fits the flow of work, makes logging fast and frictionless, and turns entries into visible improvements. Data collection does not have to be perfect; it has to be worth doing.

Frames OEE adoption as a feedback-loop design problem, not an operator-compliance problem.

For brands planning a campaign

A manufacturing software brand can collaborate on content about closing the loop from operator log entry to visible improvement. Show what operators get back, not just what managers can analyze.

Examples: Source 1

Because the plant runs 1940s machines, operators write down stoppage reasons on paper for planners or managers to enter later.

• When a line is down, restarting it takes priority: details get lost, failures get simplified, and events get missed.
• Plants losing the most money from downtime often have the weakest downtime data.

Starts with the operational and capital-decision realities of a high-cost plant, then explains why documentation fails under production pressure.

For brands planning a campaign

Content can address how to capture useful failure reasons in low-automation or older-equipment environments. Show how data capture holds up under shift pressure and produces evidence strong enough to support capital requests.

Examples: Source 1

OEE shows how the plant is performing but does not necessarily show what should be fixed first.

• When a downtime reason is presented as "unplanned stop, 3.2 hours" it gets discussed; when it is presented as "unplanned stop, $47,000 last quarter" it gets prioritized.
• Byam argues that tying dollars to specific causes shifts conversations from opinions to evidence and gives operators numbers behind them.

Translates downtime metrics into financial impact to help compare improvement choices.

For brands planning a campaign

A collaboration could focus on cost-of-downtime framing, prioritization frameworks, or ROI-style content to help brands and plants decide what to fix first. The strongest angle ties specific causes to dollar impact, not just total production.

Examples: Source 1

The result was better data, faster insights, and less friction. The difference, Byam says, is not the software; it is the team.

Uses a concrete project example to show operator and engineer co-design during rollout.

The example highlights an unusually high level of engagement; ask what operator involvement a brand can expect in its own rollout.

For brands planning a campaign

Partner content can focus on change management, operator involvement, and iterative rollout. Avoid implying that software alone produces this result.

Examples: Source 1

They mention MD&M Trade Shows and say those conversations are worth showing up for.

For brands planning a campaign

Event-based collaborations, booth conversations, short field interviews, or trade-show content fit this approach. A brand could propose a live or recorded conversation rather than a purely digital campaign.

Examples: Source 1

The posts promote the brand's approach. Ask whether Jay Byam works for, owns, or is otherwise contracted by Kartorium; the relationship is unstated.

View example

It reads as attendance commentary; no sponsorship, exhibitor role, or partnership is stated.

View example

The overlap with Jay Byam is the practical challenge of keeping plant information current and useful.

Eric Ciampoli's posts connect knowledge and documentation systems, including the OPSIDIAN platform and ERP alignment, with a broader consulting offer. Jay Byam focuses on one narrow loop: whether operators get anything back from logging, and whether the resulting numbers can support a spending decision.

Read original · Original 2

Both treat failure as structural, not a matter of effort or discipline.

Daryl Holley locates the failure in executive alignment and review habits: lean dies where sales, finance, and operations each protect their own number, while metrics become theater. Jay Byam locates it in the capture-and-feedback loop operators experience on the floor.

Read original · Original 2

Readers drawn to Jay Byam's focus on data quality will find a related argument here.

Tim Stuart takes a technical integration approach, covering PLC signals, Ignition workflows, event-driven alerts, and webinars for engineers and IT/OT teams. Jay Byam focuses on operational and organizational questions; buyers evaluating technical depth should ask them about the underlying architecture.

Read original · Original 2

The posts link operational improvement to a platform that brings plant data, documentation, and knowledge together, and ask whether procedures kept pace as equipment and processes changed. That framing suits a campaign about knowledge systems and process consistency around the data, rather than data-capture behavior itself.

Jay Byam's posts focus largely on event recaps and platform promotion: a Manufacturing Day booth recap and a platform post on keeping documentation current.

• They do not closely examine why operators stop logging or quantify downtime hours as a specific cost.
• A brand seeking a concrete argument about why downtime data capture fails on shift would find less of that here; the posts speak more in the platform's voice than from an independent, operator-side perspective.

Examples: Source 1 · Source 2

Both posts use first-person plant examples: a strategy review where sales, finance, and operations each held a different definition of priority, and a weekly ops review that left a yellow metric untouched for eleven weeks because it did not roll up to corporate. That is the right register for a campaign aimed at plant and operations leaders.

The posts diagnose organizational causes rather than the mechanics of capturing OEE and downtime reasons.

• A software brand selling a capture-and-feedback tool would get a diagnostic frame, not a close read of a use case.
• Both examples focus on management decisions, so pair this voice with a product narrative carefully: the argument is that the failure sits in the room above the shop floor.

Examples: Source 1 · Source 2

The posts cover contextualizing raw PLC signals into machine states and events, event-driven alerts and workflows in Ignition, and lightweight analytics for downtime, fault duration, and micro-stops.

• They also offer an article-backed view that continuous improvement fails because it does not reach finance, planning, IT, and HR—not because of the methodology.
• That speaks directly to the audience that would build or configure a downtime-data system.

Jay Byam's posts are engineering- and platform-led, with a promotional tilt: a webinar announcement and a post pointing to a longer analysis.

• They address a controls and IT audience rather than operators on shift, making them a weaker match for a campaign centered on operator behavior and making logging worth doing.
• The brand would gain technical credibility but less of the operator-facing argument that anchors these posts.

Examples: Source 1 · Source 2