Sector
Manufacturing and Industrial
Manufacturing and Industrial: the registers and engineering services RJV offers, and what they do not cover.

On this page
How the sector changes the requirements
Plants where uptime, quality and supplier performance decide cost and operational systems cannot be disturbed.
Systems RJV runs for this sector
Each is a register kept by an account, whose records move only along permitted steps and whose changes are recorded.
- Production Line Registry
- Supplier Quality Register
- Quality Nonconformance Tracker
- Maintenance Scheduler
- Asset Tracker
- Inventory Tracker
Engineering services for this sector
What this does not cover
The registers here keep records only. They do not connect to controllers and they are not part of any safety function. The industry editions describe how offerings are packaged for a sector and the engineering page describes how an engagement runs. To discuss your situation, use Work with Us.
Works with
- Asset Tracker: Works with. Used in this industry.
- Dataset Lineage Register: Works with. Used in this industry.
- Factory Data Platform: Works with. Written for this industry.
- Industry editions: Works with. One of the eight editions.
- Inventory Tracker: Works with. Used in this industry.
- Maintenance Scheduler: Works with. Used in this industry.
- OT Security Assessment: Works with. Written for this industry.
- Production Line Registry: Works with. Used in this industry.
- Quality Nonconformance Tracker: Works with. Used in this industry.
- Sentinel: Works with. Used in this industry.
- Supplier Quality Register: Works with. Used in this industry.
- Workforce Register: Works with. Used in this industry.
Deploying for this industry
RJV checks a device for this industry against the sovereign profile. It is the strictest set of checks RJV applies for the industry, chosen by RJV. It is not a certification and it does not replace what your regulator requires.
- The release runs in production mode.
- The public origin is set.
- The authenticator key is set and at least 32 characters.
- The public origin uses https.
- The listen address is not a wildcard: a TLS-terminating proxy sits in front and the application binds loopback or a private address.
- Any outbound mail relay uses TLS (implicit or STARTTLS) or a loopback hand-off.
- The operator and administration surfaces are limited to a named management network (a warning, not a failure, until it is set).
- No outside service is configured: there is no mail relay, so the release makes no outbound connection of its own.
With the environment the release would start with, run rjv preflight --profile sovereign. It adds these checks to the device and database checks and exits non-zero if any fails. Each offering listed above runs in the same release, so the profile applies to all of them together.
- Published
- 29 October 2026
- Revision
- 2