AURONAHelp Center
Kenta / Using Kenta

Record an equipment commitment and review its impact

Retain typed supplier assertions, evidence and stage-impact decisions without replacing a forecast or actual date.

Current Revision 2 Reviewed Oct 25, 2026

Applicability

Current Kenta guidance; implementation-source applicability 0.3.0, evaluation scope. Source review does not establish customer production acceptance.

Download PDF (173 KB)Contact support
On this pageBefore you beginHypothetical synthetic equipment exampleInputs and terminologyProcedureVerify the resultWhat happens nextTroubleshooting

Before you begin#

  • Permission to maintain the equipment record and inspect the chosen source versions.
  • An accountable owner and retained evidence for any recorded date; separate review and manager authority for controlled proposals.

Hypothetical synthetic equipment example#

Use demonstration tag SWG-01 with recorded specifications 480 V / 3200 A. Suppose a supplier source asserts receipt on 2027-05-20: record receive + supplier commitment, the date, owner, linked stage, exact source and reason. Keep any earlier expectation in History and review the stage impact separately. The electrical specification is not converted into MW and the assertion is not an actual receipt or permission to energize.

Inputs and terminology#

Inputs and terminology
TermMeaning
Assertion kindManufacture, shipping, receipt, installation, testing or handover; these describe different events.
Date basisTarget, supplier commitment, forecast or actual. The kind and basis must both be explicit.

Procedure#

  1. Inspect current delivery evidence

    Open the equipment record → Delivery. Read the current commitment, earlier versions and any newer-source warning.

  2. Record the assertion

    Choose Record commitment. Select its kind and basis, the date or explicit unknown, owner, linked stage and exact source versions.

    Explain the assertion and its qualifications. Save only after inspecting the current record revision.

  3. Review the linked stage

    Open the milestone-impact history when a commitment changes. Inspect the stage's current target and forecast.

    Record the impact assessment. Use the separately authorized date-change proposal and application workflow if a stage date must change.

Verify the result#

A new commitment revision retains its meaning, date, owner, sources and reason. Its effect on delivery work is visible.

What happens next#

A supplier assertion is not an actual event. A changed commitment does not automatically change a milestone forecast or authorize physical readiness.

Troubleshooting#