RC-ACS Request access

Telemetry and data platform · our own hardware

Know what every unit is doing, at every site.

RC-ACS puts a controller on each piece of equipment. It reads the unit's own meters, reports them over an encrypted link, and carries your commands back. You see every location in one panel, and your systems get the same data through an API.

  • Per unit one controller, one display
  • Per site days counted in local time
  • Per person a role and a reach
The RC-ACS panel Illustration with sample data: totals for the period, a chart of counts in and out by day, and a list of units with their connection state. Counted in Counted out Units online 31,516 26,353 38 / 40 Unit 07 · North site Unit 12 · Harbor site last reading 4 s ago last reading 2 h ago Online Offline
Illustration with sample data.

How it works

Four parts, each doing one job. Nothing on the unit decides anything about your business: it measures, reports and executes.

  1. 1

    Hardware on the unit

    A controller wired to the equipment's meter and command lines, and a small display beside it. The controller counts every pulse the unit emits and sends the pulses you ask for.

  2. 2

    Encrypted connection

    Each device creates its own key on first boot and introduces itself with a signed message. From then on it talks over TLS and can only reach its own channel.

  3. 3

    The panel

    Companies, sites, units and people in one place. Meter readings become daily totals in each site's local time, and reports compare sites and units over any period.

  4. 4

    Your platform, through the API

    Your system opens a session on a unit, sends a command with its own reference, and is told what the unit actually confirmed, by signed webhook or by polling.

Data flow The unit's controller and display connect over TLS to RC-ACS, which serves the panel to people and the API to your platform. Unit RC-ACS Panel Your platform controller + display accounting · sessions · audit TLS, one key per device people, by role API key, signed events

What you get

Everything below works today.

Meter accounting you can add up

Each reading is compared with the previous one for the same installation. Totals are kept per day, in the site's time zone, so a week, a month or a whole company is a plain sum, and the chart always matches the table beside it.

Where each count came from

Counts in are split by origin: what your platform sent and the unit confirmed, and everything else the unit counted on its own. Counts out are always what the unit measured, never what someone typed.

Commands that are confirmed, not assumed

A command carries your reference. Repeat the call after a network error and nothing is sent twice. The answer is what the unit confirmed, which can be less than you asked. A command with no answer is never retried on its own.

Presence, proven on the screen

A free unit shows a QR code that changes every two minutes and works once. After scanning, the display shows a short number the person types back, and each further action asks for the number on the screen at that moment.

Install by code, not by serial number

A new board shows a setup code on its display. The technician types that code next to the unit in the panel and the board is installed. Moving a board closes one accounting period and opens another; nothing is erased.

Roles with a reach

Owners see their company, managers the sites assigned to them, technicians the technical side of theirs. The same rules apply in the panel and behind it, so hiding a button is never the only protection.

Reports for decisions

In, out, net and retention against the previous period; trends by day, week or month; sites and units ranked side by side; units that counted nothing in the period. Export to CSV or print.

Tickets and an audit trail

People on site open tickets for the company or for RC-ACS support and follow them in one thread. Every sign-in, change and refusal is recorded with who did it and from where, and entries cannot be edited.

The hardware

Two small devices per unit, running our own firmware. They are installed once and managed from the panel.

Controller
Eight digital inputs and eight outputs, Ethernet and Wi-Fi. Reads the unit's pulse meters and drives its command lines with the timing set for that unit in the panel.
Display
A 3.5-inch color screen that shows the QR code, the session number, or the setup code while the board waits to be installed.
Configuration
Pulse value and timing are set per unit in the panel and pushed to the controller. No laptop on site, no file to copy.
Status
Online state, firmware version, signal strength and the last reading of each device, visible to the technician responsible for the site.
Controller and display A diagram of the controller, with its input and output terminals and a network port, next to the display showing a QR code. 8 inputs 8 outputs display MCULAN SCAN

Security is part of the design

What is in place today, stated plainly. We do not list certifications we do not hold.

  • Each device has its own identity. A key created on the device at first boot; the server keeps only the public half. A different key claiming the same serial number is refused.
  • Devices are fenced in. TLS on every connection, and each device can publish and read only its own channel.
  • Two steps for every person. Password plus an authenticator app, with no exception by role. Repeated failures lock the account for a while.
  • Denied by default. A route that does not declare what it requires answers no. What belongs to another company answers "not found".
  • API keys you can lose only once. Shown a single time, stored only as a keyed hash, revocable at once, optionally limited to your networks or to read-only use.
  • Signed events. Every webhook carries a timestamped signature your server can verify, and is only ever sent to a public HTTPS address.
  • Sensitive actions ask again. Creating an API key or acting on someone's behalf requires a fresh authenticator code, and both names go into the audit trail.
  • Checked before every release. Static analysis, dependency audit, production configuration check and the full test suite run before anything is published.

An API your platform can rely on

One key per company. The API speaks only about units, sessions and amounts; your accounts and your business rules stay with you.

  • List units and see which are available, busy or offline.
  • Open a session from the code a person scanned on the unit.
  • Send a command with your own reference; repeating it is safe.
  • Receive each result as a signed event, or read them in order.
  • Errors always have the same shape, with a stable code.
# Which units can take a session right now?
curl https://<your-rcacs-host>/api/v1/machines \
  -H "Authorization: Bearer $RCACS_KEY"

{
  "results": [
    {
      "id": 12,
      "name": "Unit 07",
      "status": "available",
      "location": {
        "name": "North site",
        "timezone": "America/Chicago"
      }
    }
  ]
}

# Every event arrives signed.
RCACS-Signature: t=1795041731,v1=5f1c…e02a

Who it is for

Operators with many sites

You place equipment in locations you do not staff. RC-ACS tells you what each unit counted, which ones went quiet, and how one site compares with another.

Platforms that reach physical units

Your users act on a unit from their phone. RC-ACS is the layer that proves they are in front of it, executes the command, and reports what really happened.

Field technicians

Install a board by typing the code on its screen, check that it is online, see its last readings, and open a ticket when something is wrong.

RC-ACS is in early access

Tell us how many sites and units you run and what you need to measure. We answer every message.

support@rcacs.net