FRIDAY / AFTER HOURS
Did the job keep running?
A stopped machine and a lost view need different responses. Both deserve attention before Monday morning.
Machine observations. The right manuals. A service record your next shift can pick up. Marcel brings them together, starting with the phone in your pocket.
Working prototypes. Seeking our first shop trials.
Intermittent stop during warm-up
DEMO-01
Alarm visible. Cause unconfirmed.
FRIDAY / AFTER HOURS
A stopped machine and a lost view need different responses. Both deserve attention before Monday morning.
AT THE CONTROL
The controller revision, the manual page, the last service note. Useful together, right where the question comes up.
NEXT SHIFT
Give the next technician the observation, the checks and the open questions so the investigation can continue.
Start with the job your team needs help with. Each workflow builds on the same machine and service history.
Start with the screen.
Photograph a control screen to read visible alarm text and identify the controller. Unconfirmed identity or missing documentation stays visible.
Screen reading and machine identificationKeep the investigation together.
Record observations and work, review linked manual references, and download a service handoff. A technician records the outcome.
Notes, case history and shift handoffKnow when the plan changes.
Set expected run windows and surface unexpected stops or lost visibility. The next step is dependable observation and alerts on real machines.
Expected production and observation healthThe machine is the starting point.
Scan a machine QR code to reach its approved documents, setup information and service history. Access and document revisions belong with the record.
Machine QR pages and approved documentsMarcel is in prototype development. Shop trials will establish supported machine configurations and practical reliability.
Explore a sample observation, open a service case and leave a useful handoff. Try a lost view or an unfamiliar controller, too.
MILL 03
Training controller / Revision A
DEMO-01
Alarm observedThe sample screen shows an alarm. Its cause and the machine's physical condition are unconfirmed.
Fictional training worksheet · Revision A · Sample page 2
Record the visible message and the time it was observed. Record technician checks separately from the screen observation.
Original demonstration text. This is not a vendor manual or repair procedure.
Start with a phone photo. An installed observer is another path where the machine and capture setup support it.
Check the machine, controller and document revision. A familiar brand name alone does not establish the right manual.
Keep the alarm, source references and technician checks together. Unanswered questions stay part of the case.
Record what was done and the reported result. Download the context the next shift or service technician needs.
The current observer is read-only. It sends no machine commands. An alarm disappearing is an observation; a repair outcome is a separate technician report.
Screen access can open a path to older equipment. Compatibility depends on the actual display, controller, documentation and job.
Initial manual set
Controller manuals available for prototype research. Exact machine configuration and builder documentation still need confirmation.
Documentation research
Selected, edition-specific manuals are available for page search. This is not yet validated diagnosis support.
Next shop trials
Tell us the builder, controller and the problem you want to solve. Repeated access to real equipment will guide what we support next.
Screen recognition is currently tested on synthetic displays. Real-machine validation is the next milestone. A readable screen does not by itself establish reliable monitoring or correct repair guidance.
We are exploring approved program delivery and narrowly defined recovery routines in isolated simulations. These are research directions. Live use would need a specific machine integration and engineering validation. They are not capabilities of the current observer.
/01
A phone at the machine, useful documentation and a record of what happened. Start with a single workflow worth returning to.
/02
Keep an investigation understandable across technicians and shifts. Review observations, reported work and outstanding questions together.
/03
Prepare a clearer handoff before the support call. Help shape future collaboration across customers, sites and service teams.
Help shape the first shop trials
We are looking for shops and service teams willing to put the prototype in front of a technician. Tell us where work gets stuck and what equipment you use.
A short conversation, one candidate machine and a supervised first look. We will work out the fit together.
Talk about your shopOpens your email app. hello@marcelcnc.com