TECHNOLOGY / OUR APPROACH

Condition signals.
Connected context.

Mercer Monitor is being designed to help teams interpret motor measurements over time, with a clear connection between the signal, the operating context, and the maintenance record.

Temperature

Planned temperature trends would help teams follow changes in recorded surface or other specified measurement locations. Readings need consistent units, locations, and operating context.

Vibration

Planned vibration views would organize recorded RMS velocity readings in mm/s. Sensor placement, measurement method, and operating speed matter when comparing values.

Motor load

Planned load views would place readings alongside operating demand, helping distinguish a changing duty cycle from a change that deserves investigation.

THE PLANNED DATA PATH

From a reading to a useful record.

01 / INPUT

Measurement files

Upload timestamped readings and associate them with an asset.

02 / CONTEXT

Cloud workspace

Organize units, equipment details, trends, and configured thresholds.

03 / REVIEW

Maintenance action

Review charts, export a report, and record an inspection or service note.

Proposed architecture. Cloud storage and automated notification delivery are planned product capabilities, not active services on this website.

FIRST VERSION

A useful starting point.
A deliberate scope.

We plan to prioritize structured measurement uploads and straightforward analytics. Teams would bring measurements from their existing collection process.

Explore the Concept

Consistent measurement records

Planned asset IDs, timestamps, units, and validation to make comparisons meaningful.

Trends and configured thresholds

Planned charts and threshold events for human review. Settings should reflect the motor, measurement method, and operating conditions.

Reports and service context

Planned exports and a maintenance journal to make inspection findings easier to share.

WHAT COMES LATER

A path toward
connected measurements.

Connecting measurement modules is a subsequent development stage.

We plan to explore module selection, installation, communication methods, sampling needs, and equipment compatibility with pilot participants. No sensor hardware is currently offered, and compatibility has not been established.

Module connectivity, automated ingestion, and notification channels will depend on technical validation and feedback from early users.

ENGINEERING RESPONSIBILITY

Insight to support
qualified judgment.

Temperature, vibration, and load alone do not establish a fault diagnosis. Planned alerts would indicate that a configured condition deserves review, rather than prove a failure or predict a remaining service life.

Mercer Monitor is not intended as a protection relay, emergency shutdown system, or replacement for manufacturer guidance, trained personnel, and appropriate inspection procedures.

HELP SHAPE WHAT COMES NEXT

Built around your
maintenance reality.

Tell us about your motors, your measurements, and the decisions you need to make.

Apply for a Pilot
STAY IN THE LOOP

Follow the development.

Request occasional Mercer Monitor development and pilot updates by email.

Review and send the prepared request in your email app.

READY FOR YOUR REVIEW

Your email is prepared.

No message has been sent. Open the draft in your email app, or copy the message and send it to james@mercermotorworks.org.

Open Email App →