JC Thermal Monitor can integrate thermal cameras such as FLIR AX8 and further suitable sensors into monitoring, diagnostic and endurance test projects. The integration page describes how camera, measurement data, user interface, Modbus-related runtime logic, digital signals, snapshots and customer-specific workflows work together.
View FLIR IntegrationMonitoring and diagnostics platform
JC Thermal Monitor
A local, server-based system for continuous thermal monitoring, technical diagnostics and automated test projects. JC Thermal Monitor combines FLIR AX8 data, digital signals, Modbus, rules, incidents, tickets, snapshots, evidence reports and operational health in a traceable workflow. The software is a standalone monitoring product and also the technical basis for JC-Technology risk analysis and endurance test projects.
Software platform
From measurement data to traceable decisions.
JC Thermal Monitor is designed for industrial environments where temperatures are not only checked occasionally, but must be observed over time, evaluated and documented as a technical decision basis. The system connects camera data, digital states and operator decisions with evidence, reports and technical diagnostics. It can run permanently or be used as a temporary platform for diagnostic, risk analysis and endurance test projects.
- Project and location structure for plant areas, cameras, measurement points and reports.
- ROI synchronization for FLIR AX8 with spot, box, DI and DO ROIs.
- Spot and box ROIs are still enabled and positioned in the AX8 web interface; Thermal Monitor imports the enabled ROIs after synchronization.
- Parallel operation next to existing AX8 systems, as long as the camera and Thermal Monitor do not control the same output at the same time.
- Measurement storage per ROI with individual sampling cadence, Celsius-based history, retention and shared visualization.
- Virtual multi-camera alarm rules with AND/OR logic, hysteresis, threshold time, cooldown, delta, rate-of-change and edge conditions.
- Conditions can combine ROIs, digital inputs and digital outputs from several separate cameras in one rule.
- Filters for schedules, previous incidents and repeated activations.
- Actions for events, digital outputs, timed impulses, impulse stop, camera torch, asynchronous snapshot jobs and e-mail notifications through action jobs.
- Incident workflow with acknowledgement, classification, summary, frozen trigger evidence and report view.
- Investigation tickets with technician assignment, checklist, measurements, notes and attachments.
- Role-based access with Admin, Operator, Technician and Viewer monitor view.
- Operational health for camera, Modbus, ROI freshness, poller, workers, rules, impulses, system incidents, e-mail and snapshot jobs.
- Usable as a pilot installation, temporary diagnostic platform or permanent monitoring system.
Pilot, diagnostics, operation
Thermal Monitor is typically discussed as a project or pilot installation because camera, network, ROI model, alarm strategy, signals, reporting needs and operating environment must be considered together. In service projects, the platform can also be used for a limited period to capture measurements, alarms and events for a concrete finding.
Request pilot or diagnostics Details and featuresFLIR Integration
Thermal cameras and sensors as part of monitoring.
Software basis
The platform behind risk analysis, monitoring and endurance testing.
In many projects, the customer does not need to buy a permanent system immediately. JC Thermal Monitor can also be used as a temporary measurement and diagnostic platform: for charging area monitoring, PV/inverter checks, plant observation, test cycles, digital signals, Modbus data and technical reports.
Diagnosticstemporary installation for concrete failure patterns
Pilot operationcollect measurements before permanent investment
Rulesmap test, alarm and event conditions traceably
Reportsevidence reports as a basis for technical decisions
Core features
For plants where a thermal image is an operating state.
Live and history
Temperature series, digital signals and incident markers remain stored in the project context. Visualization shows Thermal History, Incident Timeline and Digital Timeline in the same time window; stored/API values remain Celsius-based.
ROI and measurements
Locations connect real plant areas with AX8 cameras and ROIs. Spot and box positions remain in the camera web interface; Thermal Monitor uses the synchronized measurement points afterwards.
Multi-camera rules
Rules can combine direct temperature values, differences, fast changes, digital states and edges from several cameras. This creates alarms beyond single AX8 threshold logic.
Evidence and reports
When a rule triggers, trigger context, ROI values, condition results, actions, lifecycle, asynchronous snapshot evidence and printable evidence reports remain traceable.
Tickets
Incidents can be converted into investigation tickets with technician assignment, work instruction, checklist, Measure tasks, notes and attachments. The workflow is not a full CMMS replacement.
Impulses and e-mail
Actions are processed as action jobs: they can write events, set digital outputs, run or stop timed impulses through the impulse worker, schedule snapshots, switch the camera torch and send e-mails or log dry-runs.
Health and diagnostics
Operational Health shows worker heartbeats, camera and Modbus state, ROI freshness, rule runtime, action diagnostics, impulse runtime, system incidents and snapshot job status.
Parallel operation
Thermal Monitor can run next to an existing AX8 system because monitoring access reads the camera registers. Only digital outputs need clear ownership: camera/existing system or Thermal Monitor.
On-premise and access
The system is designed for local installation, with roles, Viewer monitor access, authenticated snapshot delivery and separate background processes.
Technical basis
More stable than a dashboard, more flexible than a camera recorder.
The current implementation uses FastAPI, PostgreSQL/TimescaleDB, Alembic migrations, Docker Compose runtime, a separate poller, action worker, snapshot worker and impulse worker. For the user, the result matters most: a traceable thermal operating history with evidence reports, protected access, alarm details, diagnostics and a clear operator workflow instead of isolated screenshots.
Camera focusFLIR AX8 as the first target integration
Operating modelocal / on-premise
WorkflowMonitoring, alarm, incident, ticket, snapshot, report
DataROI history, digital states, trigger evidence, attachments
IntroductionPilot project or customer-specific integration