AURONAHelp Center
Kenta / Using Kenta

Review an equipment substitution

Connect the proposed equipment revision to technical evidence and separately authorized commercial, budget, schedule and commissioning consequences.

Current Revision 3 Reviewed Oct 29, 2026

Applicability

Current Aurona implementation-source guidance. Customer-specific permissions, commercial confirmations and operational acceptance remain with their owning applications and authorized people.

Download PDF (138 KB)Contact support
On this pageBefore you beginCheck workflow availabilityReview the proposalObtain separate authorized decisionsFinalize and reconcileInspect retained evidence and historyIf an action or relationship is missing

Before you begin#

Confirm the organization/project, equipment reference and intended approved/proposed revision. You need the relevant record access and explicit decision capabilities; technical-review authority is separate from contract, budget and schedule authority. Use the actual published workflow and exact supporting document revisions.

Check workflow availability#

Where the workspace displays Change writing awaits release activation, the records are available for inspection and new revisions/decisions await release activation. A guide does not enable connected-change writing or establish customer production acceptance. Check the current operating limitation before planning an approval task.

Review the proposal#

  • Identify the replacement and retain the source requirement, equipment revision and reason for change.
  • Inspect the exact supporting document versions and record technical findings or missing evidence through the authorized review workflow.
  • Check linked procurement commitments, cost exposure, schedule impact and commissioning requirements. Absence of a recorded effect does not prove that no effect exists.

Obtain separate authorized decisions#

Use the current Change register and the intended revision. Each required reviewer records the relevant decision through Approve this revision or the available disposition action. Do not describe a technical acceptance as permission to purchase, increase the budget or replace a schedule baseline. Current authority, state and evidence are checked on the server.

Finalize and reconcile#

When available to the authorized actor, Finalize approved change checks the exact revision, evidence and all required decisions. The interface states that local approved effects commit together and external authority remains pending until reconciled. Confirm that the resulting commitment, cost and schedule records and commissioning evidence refer to the intended revision; do not count commitment and cost exposure twice.

Inspect retained evidence and history#

Use the governed analytics/reporting and retained history to inspect the approved basis and resulting records. A new revision requires its applicable review; historical acceptance is not automatically acceptance of a replacement revision. ERP transport and scheduled delivery require actual configured providers and are not implied by this process.

If an action or relationship is missing#

Check current permission, required evidence, record state, workflow configuration and the exact revision. Keep unresolved conditions visible and use the existing authorized Support Center rather than putting equipment/customer context in a public documentation URL.

Open Kenta