Your readings. Your overview. monicore.one.
Sensors, existing plants and digital inspections on one shared platform.
With monicore.one, egatti is developing a platform that brings readings and device states together in an understandable way. The goal: connect devices, recognise developments, trace alarms and provide information where it is needed — in the dashboard, via QR code or directly at the device.
The M1 product family combines sensors, gateways, the software platform and small mobile applications into one system.
- View readings and states together.
- Integrate existing data sources selectively.
- Use information in the office, on the move and on site.
monicore.one
Why we are developing MoniCore
Transparency in operation
Temperature, humidity, pressure or device state: information should be clearly visible with unit, time of measurement and origin. Missing data and outdated values must remain clearly recognisable.
Include existing systems
New sensors and existing data sources should come together in one view via suitable interfaces. Existing plants do not have to be replaced completely.
From reading to action
Trends, alarm rules and digital inspections should help classify anomalies and handle tasks traceably.
Reachable on site
A QR code at the device or measuring point should lead directly to the right view or mini app. E-paper adds digital information on site.
M1
The M1 product family
One shared core, matching building blocks for data acquisition and use.
M1 Core
The central software platform for readings, devices, trends, alarms, evaluations and administration.
M1 Node
The intended naming concept for sensor nodes acquiring readings and states.
M1 Gateway
The intended naming concept for the link between radio devices and the platform.
M1 Probe
The intended naming concept for connected probes and sensors.
M1 Minis
Small, purpose-built applications for device information, inspections, feedback and on-site capture.
Own hardware · MoniCore M1+
MoniCore M1+ — sensors and data acquisition for your monitoring
The MoniCore M1+ product family connects sensors, states and industrial signals to one shared platform for readings, trends, alarms and evaluations.
In development – pilot projects by arrangement
MoniCore M1 Node – own development for chemicals and business-critical units
- Transmit interval
- every 2 minutes by default
- PT100, 4-wire
- probe cable silicone or steel-flex, lengths 0.5 to 15 m
- Temperature & humidity
- Sensirion SHT45 – manufacturer spec typ. ±0.1 °C and ±1.0 % RH
- Power
- D-size battery, 19,000 mAh, 3.6 V
- Housing
- PC to UL 94 V-0: flame-retardant, self-extinguishing, suitable for outdoor use
- Service life
- designed for up to 10 years – depending on transmit power and interval
Basis for service life: our own current measurement per radio packet. Ranges, accuracies and availability are defined per version.
The M1+ variants describe the planned product line; ranges, accuracies, housing, power and availability are defined for the specific version. In addition, MoniCore.one integrates third-party LoRaWAN sensors and your existing sensors.
Ask about M1+- M1+ TTemperatureplanned
- M1+ THTemperature and humidityin development
- M1+ TH-RTD4Temperature and humidity plus external 4-wire PT100in development
- M1+ PTExternal temperature measurement with PT100/PT1000in development
- M1+ PPressureplanned
- M1+ DPDifferential pressureplanned
- M1+ CO₂CO₂, temperature and humidityplanned
- M1+ LeakWater and leak detectionplanned
- M1+ DIDigital inputs, e.g. door contactsin development
- M1+ PulseMeter pulsesplanned
- M1+ VibVibration and condition monitoringplanned
- M1+ AnalogConnection of 4–20 mA and 0–10 V signalsplanned
- M1+ RS485Connection via Modbus RTUplanned
Wireless instead of cable
Measure where cables are expensive or impossible
LoRaWAN radio brings readings out of rooms where you don’t want to – or may not – run a cable. The sensor measures right at the point of interest, the gateway transmits independently of the plant network – no wall penetration, no cable tray, no change to the control system.
Why wireless – and not cable?
With cable
- Cable route through ATEX zones – ignition protection and Ex documentation
- Penetrations into cleanrooms – approvals, requalification, possibly downtime
- Interface in the control system – engineering and change control
- Weeks to months of lead time
With wireless sensors
- Battery-powered sensor right at the measuring point
- No penetration, no cable route, no change to the control system
- Autonomous gateway – independent of the plant network
- Ready to measure in days
Field record: 3 years of control-room monitoring data
3
years of continuous use
2
min interval
around the clock
788,400
payloads per sensor
3 × 365 × 24 h × 30/h
1.58
million readings
temperature + humidity
15
limit violations
reliably detected and reported
Every violation arrived as an email – before it could turn into a failure.
Where LoRaWAN works
How it works
Five steps to a running wireless network
- 1
Survey the building
We measure radio coverage on site at every planned measuring point – signal strength and quality, even in basements and behind reinforced concrete.
Walkdown
- 2
Document everything
Readings, gateway locations and antenna planning go into a report. It is the basis for installation – and for qualification in GMP.
Radio report
- 3
Order the starter kit
The kit arrives pre-configured in a case: gateway, sensors and accessories, neatly packed and ready to go.
In a case
- 4
Plug in & place
Plug the gateway in – the LTE link is up. Mount sensors by magnet, bracket or cable tie exactly where it’s critical.
Plug & play
- 5
Log in
Sign in at monicore.one: live readings, set limits, activate email alerts. Done.
Live data
More safety
One gateway to start – redundant when it matters
The number of gateways depends on the building and criticality. Every sensor transmits to all gateways in range; if one fails, the others take over automatically.
1gateway
Start & pilot
Ideal for getting started, one room or one floor.
2gateways
Redundant
Two gateways with SIM cards from two different carriers – our standard for critical areas.
3gateways
Large building
Several floors or long buildings: every measuring point is heard by at least two gateways.
4gateways
Campus & highest availability
Several buildings or a site – coverage with reserve, even while one gateway is serviced.
We deliver it all – from the starter kit in a case to a redundant network ready for qualification.
Request a site surveySet-up
From device to understandable reading
The planned set-up flow leads from the selected data connection via the recognised device to a usable data point. Templates should simplify recurring configurations: known field mappings, measurands and units then do not have to be created again each time.
Unknown fields are offered for review. Engineering units, owners and alarm limits are not guessed from a technical field name.
The complete path is a development goal. Fully automatic productive release without review is not promised.
- 1Connect the data source
- 2Recognise and assign the device
- 3Confirm data points and mapping
- 4Provide tiles and trends
- 5Configure monitoring and notification
Dashboard & trends
Understand values — recognise developments
The dashboard should bring current values, freshness and device states together at a glance. Configurable tiles and saved charts create the right overview for each use.
In the trend explorer, several series should be viewed together, time ranges selected and conspicuous sections examined more closely.
Intended scope
- Values with unit, time and quality indication
- Single or multiple series in comparison
- Clear legends, grids and axes
- Tooltips for reading individual points
- Time range, zoom, pan and reset
- Separation of live view and historical section
- Saved views and chart compositions
- CSV and PDF export of the selected data
A missing value is not zero. An old reading is not a current state. MoniCore is meant to keep these differences visible.
Alarms
Recognise anomalies and handle them traceably
Configurable warning and alarm rules are planned for monitoring. Besides limits, these include delays, hysteresis and detection of missing data.
An alarm should keep its entire history: occurrence, acknowledgement, return to normal and related notifications. A vanished limit violation does not replace a required acknowledgement.
- Rules per data point and responsible area
- Warning, alarm and missing data as distinct states
- Acknowledgement by an authorised person with comment
- Traceable rule version and trigger values
- E-mail as intended notification channel
- Further channels depending on integration and offer
- Visible delivery errors and traceable delivery attempts
QR & mini apps
Scan. Inform. Act.
A QR code should lead directly to the right device view or mini app. Depending on release, current values, tiles, trends, device status or a compact entry form appear.
Content should be extendable later. A simple reading view can become, for example, a combined view with additional data points and a trend.
Intended mini apps
- Device information and current values
- Visual inspection / walkdown with OK and NOK
- Fault and maintenance report
- Manual reading or meter capture
- Feedback with comment and optional attachment
Administration
QR codes should be generated, assigned, printed, reprinted and revoked centrally. Validity, revision and previous assignments remain traceable. Project-specific or cross-project use within the authorised context is configured separately from public access.
Access
Public views only show explicitly released content. Protected functions still require login and authorisation.
E-paper
Information right where it is needed
E-paper and smart labels are planned as part of the M1 offering. They should show selected values, device status, names and a matching QR entry directly at the device or measuring point.
Versioned templates and managed assignments should simplify maintenance. Replacing a sensor or display must remain traceable.
- Managed display and object assignment
- Configurable content and layouts
- Reading, unit, time of measurement and validity
- QR entry to the device view or mini app
- Visible update and transmission status in administration
An e-paper display can keep its last image without power. Time of measurement and validity are therefore part of the intended display. The display is an additional information surface, not an independent release authority.
Interfaces
Bringing new sensors and existing data together
MoniCore is being developed for different data sources. Besides LoRaWAN and ChirpStack, industrial interfaces and existing historian systems are part of the target picture.
| Interface | Intended use | Status |
|---|---|---|
| LoRaWAN / ChirpStack | Radio devices and several separate ChirpStack connections | In development, confirm per project |
| MQTT / HTTP / REST | Data from gateways, applications and APIs | To be checked per project |
| OPC UA | Read-only connection of automation data | Planned |
| OSI/AVEVA PI | Read-only connection of selected historian tags | Planned |
| Modbus TCP / Modbus RTU | Connection of suitable devices and signals | Planned |
| Other MES/ERP/building systems | Integration as required | After technical review and separate agreement |
OPC UA and OPC DA are not the same. A read-only connection does not authorise sending control commands to source plants.
Operating models
Matching your infrastructure
Several operating forms are planned for M1 Core. Actual availability and the operating concept are agreed per project.
M1 Core Cloud
Central provision as a managed platform.
M1 Core On-Prem
Operation in the customer’s infrastructure.
M1 Core Edge
Local processing on suitable on-site hardware.
M1 Core Field
Site concept for outdoor use or use without an existing customer network, e.g. with mobile connectivity.
Offline buffering and synchronisation depend on the chosen architecture and are demonstrated for the specific operation.
Clear responsibilities and traceable changes
The intended administration separates platform operation and customer organisations. Authorised persons should be able to invite members, manage roles and trace access and quotas.
Planned overall scope
- Customer/tenant and organisation management
- User onboarding and invitations
- Login, password reset and effective access lock
- Role-based operation
- Management of devices, connections, QR targets and mini apps
- Plan, term and usage
- Audit log of important changes
Offer
An offer matching your use
For MoniCore, combinations of platform use, sensors or hardware rental, and set-up and support are planned. The scope is put together by data points, required functions and operating model.
The relevant factors
- Confirmed and licensed signal/data point tags
- Required interfaces and connections
- E-paper/display scope
- QR and mini app scope
- Data retention and desired services
- Set-up, support and, if applicable, hardware rental
What is a signal tag?
A signal tag describes a usable data point, for example a temperature channel. The same data point is not counted again just because it appears in several charts, tiles, QR views or on e-paper at the same time. Connector scope, physical displays and data points are listed separately. Final prices, periods, included quantities and any additional costs are set in the specific offer.
Typical fields of application
As examples, not as already qualified reference projects:
- Temperature and humidity monitoring in rooms and storage
- Condition monitoring of suitable devices and measuring points
- Accompanying monitoring of cold or storage areas
- Building, technical and plant information
- Digital rounds, visual inspections and fault reports
- Combining sensor and existing plant data
Specific use in quality-critical or regulated areas requires a separate assessment and a demonstrated suitability scope.
Field examples & LoRaWAN in detailTraceability considered from the start
Time of measurement, origin, configuration and changes are part of MoniCore’s development approach. Roles, audit logs and controlled workflows should support traceable use.
MoniCore is therefore not offered as generally “GMP-validated”, “Annex 11 compliant” or “21 CFR Part 11 compliant”. Suitability for a regulated purpose must be demonstrated for the specific application, configuration and qualification.
From need to the right monitoring concept
- 01
Understand the application
Which values, devices and workflows should be considered?
- 02
Plan the connection
Clarify sensors, existing systems, data paths and access.
- 03
Build a pilot
Implement a defined workflow with agreed test criteria.
- 04
Evaluate the result
Review data, operation, running and next steps together.
- 05
Agree the expansion
Define scope, operation and support per project.
Would you like to use readings more clearly or add a digital step to an existing workflow? Describe your application. Together we will check which MoniCore building blocks fit.
Discuss your application