Question 1

What is Zemerc?

Accepted Answer

Zemerc builds enterprise software for industrial work: projects, production, integrity, safety and the management systems above them. It is a portfolio of 27 applications, not a single platform with modules. Each application is the system of record for one class of industrial record, a risk register, an interface, a certificate, a meter reading, a transmittal, and is built around the rules the team keeping that record already applies to it.

Question 2

Is Zemerc a suite or a set of separate applications?

Accepted Answer

Zemerc is a portfolio of separate, independently operable products. Each application has its own users, data, controls and release lifecycle, and each is commercially standalone. The applications share common governance principles rather than a mandatory shared database. Where records genuinely relate, they use consistent record rules and terminology so information can be understood across operating areas without creating runtime dependency between products.

Question 3

What distinguishes these applications from general enterprise software?

Accepted Answer

They derive status from governed records wherever the underlying evidence supports that derivation. Gate readiness, control effectiveness and similar positions are calculated from the records beneath them rather than entered as unsupported declarations. Where no approved method exists for a derived figure, the application reports that limitation and presents the underlying component measures rather than generating an unsupported result. PSM applies this principle to process-safety indices for which no certified engineering method is configured.

Question 4

How many applications are there, and how are they organised?

Accepted Answer

The portfolio contains 27 applications organised across 8 operating areas and four stages of an industrial operation: deliver the project, operate the asset, protect people and govern the record. Each application has one primary operating area. Where an application is materially relevant to another area, the directory identifies that relationship as well.

Question 5

How do I determine which application we need?

Accepted Answer

Start with the industrial record, workflow or decision that needs stronger control, then identify the application designed to govern it. Use the problem index in the application directory to start from the operational record, workflow or control that needs stronger governance and identify the application designed to manage it.

Question 6

Can I see what the applications actually look like?

Accepted Answer

Yes. Each application page uses screens from that application, and the corresponding application guide explains what the application governs, the workflow it enforces and the evidence behind the displayed position. The application-tour library provides recorded walkthroughs, while a working session demonstrates the relevant application against records similar to those used by your organisation.

Question 7

Can we adopt one application?

Accepted Answer

Yes. Each application is independently operable and commercially standalone. A client can adopt one application without any requirement to purchase another. A second application is adopted when another operational requirement justifies it. It is not a technical dependency created by the first application.

Question 8

Does any application require another Zemerc application to work?

Accepted Answer

No. Where two applications are useful together, that relationship is described explicitly, but each application remains operable without the other. Where the work genuinely passes from one team to the next, a single named record crosses the boundary; the inspection record becoming completion evidence, the integrity finding becoming maintenance work. The receiving application keeps its own view and its own history of it; nothing is merged.

Question 9

Can these run alongside the systems we already have?

Accepted Answer

Yes. An organisation can adopt a Zemerc application for the records it needs to govern while retaining existing systems for other functions. Replacing systems that already meet the organisation's requirements is not a prerequisite for adopting a Zemerc application.

Question 10

How does implementation work?

Accepted Answer

Implementation follows six phases with defined gates covering scope, structure, rules, migration, the first live period and the decision on any subsequent application. Most of it is decisions your own organisation makes about its own record; who may change it, what makes an entry valid, who may approve, and what happens when a value is corrected. The application enforces those answers; it does not supply them.

Question 11

How long does an implementation take?

Accepted Answer

Zemerc does not publish a generic implementation duration because the timescale depends on the application, the maturity of the existing records and controls, the number of approval routes and the volume of history to be migrated. The implementation sequence and its gates are defined. Each gate requires a specific decision or artefact, such as an agreed record model, recognised hierarchy or approved cut-over point, before the next phase proceeds.

Question 12

What actually gets configured?

Accepted Answer

Implementation establishes the structures on which the application depends, including the operational hierarchy, shared registers for equipment, personnel, organisations and locations, and the roles and tenancy rules applied to later controls. Then the controls themselves; approval routes and segregation of duties enforced on identity, templates and their revisions so an executed record keeps the version it was signed against, and the sequences that lock once configured.

Question 13

Is the software customised for us?

Accepted Answer

Client requirements are implemented through governed configuration rather than a client-specific fork of the product codebase. This preserves a common product lifecycle while allowing hierarchies, controls and workflows to reflect the organisation's approved rules. Configuration covers the hierarchy, master and reference registers, roles, approval routes, templates and workflow sequences required for the application to operate against the client's governance model.

Question 14

Where does the software run?

Accepted Answer

Deployment is confirmed for each application and engagement. Several applications support Zemerc-hosted deployment, client cloud tenancy or deployment within the client network, and at least one supports fully offline operation. Not every application supports every deployment mode, and some modes remain under development. The supported deployment options for the application under consideration are confirmed before implementation.

Question 15

Does Zemerc have to host it?

Accepted Answer

No. Zemerc-hosted deployment is an available deployment model, not a condition of using a Zemerc application. Where an application supports deployment in a client cloud tenancy or within the client network, those are supported deployment options for that application.

Question 16

What availability or uptime does Zemerc commit to?

Accepted Answer

Zemerc does not publish generic uptime figures, availability targets or service-level commitments on this website. Service commitments are defined for the specific application and deployment in the applicable agreement. If availability is material to your decision, raise it for the specific application and deployment under consideration so the applicable commitment can be confirmed.

Question 17

What happens to the records we already keep?

Accepted Answer

Existing records and controls are the starting point. The application is configured around the registers, stages and approval rules the responsible team already maintains, subject to the controls required by the product. Historical migration defines which records are brought into the application, which remain in the existing source system and the approved cut-over point from which the new application becomes the system of record.

Question 18

Can we get our data in and out?

Accepted Answer

Yes. The applications carry a data management area with guided import, export, templates and a migration workspace, which is the same machinery an implementation uses to bring history across. Controlled export is part of record governance. Authorised records must remain retrievable in a usable form throughout their required lifecycle.

Question 19

What happens when somebody corrects a value?

Accepted Answer

The original record is preserved. Where a governed reading or record requires correction, the correction is introduced through a controlled substitution or superseding record rather than by overwriting the original evidence. Approved engineering records are superseded rather than edited. Where a superseded record has dependent records, those dependencies are identified for reassessment. Effective dating also preserves the method applicable to a historical reporting period.

Question 20

How is access controlled?

Accepted Answer

Access is controlled through identity, role, tenancy and approval authority so segregation of duties is enforced by the application rather than relying on informal working practice. Several applications enforce tenant separation using database-level row security, and controlled changes retain an audit record of who made the change, when it occurred and what changed.

Question 21

Do the applications hold security or compliance certifications?

Accepted Answer

No. Zemerc does not claim certifications for its applications unless a specific certification has been independently established and approved for publication. The website describes implemented controls rather than implying certification. Examples include database-level tenant isolation in applicable applications, identity-based segregation of duties, append-only audit history and immutable records where evidence must be preserved.

Question 22

Do the applications conform to the industry standards they reference?

Accepted Answer

They are built to work with those standards, and they say which one governs a given record; a barrier performance standard carries its governing standard, and the obsolescence model is aligned to the obsolescence-management standard. Where an application is aligned with a standard, the website states alignment rather than certification or conformance unless that status has been formally established. Where a valid engineering result depends on an approved method, the application does not produce the result until that method is available.

Question 23

Can the applications integrate with our other systems?

Accepted Answer

Not as a generally available live capability today. Some applications include integration catalogues, but integrations that have not been tested against live external systems are not presented as active production integrations. What does exist is governed import and export through the data management area, which is how data moves between systems today. If a specific integration is a requirement for you, treat it as an open question to be answered for that application rather than as something this website has already promised.

Question 24

Is there AI in these applications?

Accepted Answer

The portfolio is not marketed as AI-powered. Where assistive capabilities exist, they are described according to the functionality actually implemented. Assistive features are advisory and optional. A capability that is not backed by a live implementation is not presented as an available production feature.

Question 25

Could an AI feature affect a governed figure?

Accepted Answer

No. Governed figures are derived from underlying records using defined calculation methods. Where no approved method exists, the application reports that limitation rather than estimating the result. This separation protects the traceability and reproducibility of governed results. Advisory features do not alter the deterministic calculation path.

Question 26

What are application tours?

Accepted Answer

Application tours are short recorded walkthroughs produced from the applications themselves. Each tour explains the governed record, the controls applied to it, what the application derives from the record and the boundaries of the demonstrated capability. The library is organised by application, operating area and the kind of tour; application overview, dashboard, workflow, reporting, administration, data management, feature walkthrough or getting started.

Question 27

Why are some tours marked coming soon?

Accepted Answer

The library includes both completed tours and tours that are still in production. An unpublished tour is identified by its subject and planned coverage and is not presented as playable. Every tour has its own page, together with the relevant application information and a written guide covering the same subject.

Question 28

Where do I get help?

Accepted Answer

The support page brings together application guides, application tours, getting-started guidance, implementation guidance and the FAQ so users can reach the appropriate support route for their question. If those resources do not answer the question, the contact route sends the enquiry to the appropriate team.

Question 29

How do I sign in to an application?

Accepted Answer

Each Zemerc application has its own sign-in. Customers receive the address for their applications during implementation; there is no shared public portal.

Question 30

What are your support response times?

Accepted Answer

Zemerc does not publish generic response times, severity targets or support tiers on this website. Applicable support commitments are defined in the agreement for the specific application or service. Raise the question for the application under consideration so the applicable support arrangement can be confirmed.

Question 31

Do you publish pricing?

Accepted Answer

No. Each application is bought on its own for a specific team, so what is being priced is a specific application, a specific deployment mode and a specific scope; none of which a published table would represent honestly. The discussion starts with the record or workflow that needs stronger control, the application designed to govern it and the deployment context in which it would operate.

Question 32

What happens in a working session?

Accepted Answer

Bring one register, project, asset or vessel from your current operation. The working session demonstrates the relevant application against records of that type. The people worth having in the room are the ones who keep the record and the one who signs it; everything worth deciding is decided by whether those two recognise what they are looking at.

Question 33

Do we have to buy services alongside the software?

Accepted Answer

No. Zemerc applications are independently operable products. Implementation, configuration and technical services are available where required, but the software does not depend on those services to operate. Where your organisation has the capability to configure the registers, approval routes and historical migration itself, client-led adoption is a supported engagement model.

Direct answers, including where the answer is no.

6 questions that arise most often.

33 answers, each directly linkable.

About Zemerc

Applications

Application independence

Implementation

Deployment

Data

Security

Integrations

AI

Application tours

Support

Commercial engagement

Four places that go further.

Ask about your own operation.