Using Kenta

In this guide

• Understand the adopted power-planning basisDistinguish requirements, supply, assumptions and retained scenarios before interpreting a planning balance.
• Connect a load requirement to equipment and deliveryCreate a source-backed requirement, assign an owner and retain its equipment and stage associations.
• Compare planning scenarios without replacing the baselineRetain alternative basis versions and recorded-input screenings with their exact assumptions and limitations.
• Follow a portfolio exception into project delivery workFind the accountable owner and retained evidence behind project, milestone and planning exceptions.
• Maintain stage prerequisites and review delivery changesLink delivery stages, inspect unresolved prerequisites and retain decisions about changed commitments.
• Keep target, baseline, forecast, commitment and actual dates distinctRecord a date with its meaning and evidence instead of substituting one date type for another.
• Work from the equipment register to a retained recordFind equipment, inspect complete technical values and return to the same working register.
• Record an equipment commitment and review its impactRetain typed supplier assertions, evidence and stage-impact decisions without replacing a forecast or actual date.
• Preview, validate and apply an equipment importMap a retained CSV or XLSX source, inspect row-level errors and control updates by stable equipment identifier.
• Understand evidence, findings and technical-review authoritySeparate a detected document difference from an authorized human disposition and its follow-up.
• Record a reviewer disposition and accountable follow-upRetain the outcome, reason, source versions and optional linked action through the authorized review workflow.
• Inspect exact document versions behind a findingFollow the comparison to its original source, location and revision without changing the historical evidence.
• Upload and inspect controlled document versionsRetain original files, security and processing states, structured fields and exact source references.
• Keep a useful register view while inspecting recordsCombine search, filters, sorting, columns, pagination and explicit selection without losing return context.
• Generate an authorized report or exportChoose the reporting basis and inspect permission, freshness and historical-source limits before sharing output.
• Turn an issue into an accountable actionAssign an owner and due date, retain the originating issue and distinguish notification read state from resolution.
• Create a support case with reviewed context and diagnosticsSave a recoverable draft, review exactly what is shared and obtain a durable case reference before treating submission as complete.
• Understand case visibility, follow-up and escalationUse explicitly permitted conversations and case scopes while keeping internal notes and billing context separate.
• Review diagnostic information before sharing itPreview allowlisted context, choose attachments explicitly and keep credentials and unrelated customer data out of support records.
• Build work and cost structures and retain a scope baselineCreate WBS work packages, CBS cost codes and explicit relationships to delivery records; freeze exact work and allocation revisions as a baseline.
• Record supplier commitments and partial receiptsConnect RFQs, quotations, authorized commitments and receipt discrepancies to the actual equipment configuration and project cost allocation.
• Read the cost sheet and revise a forecastUse reconciled budgets, commitments, recognized costs, remaining estimates and explicitly included pending exposure under the configured finance policy.
• Approve a change and apply its authorized effects onceRetain exact proposal revisions and distinct technical, contract, budget and schedule decisions before finalizing local or external effects.
• Configure a test plan and verify exact-revision resultsPublish equipment-specific test checks, record controlled evidence and distinguish independent verification, failure, waiver, invalidation and retest.
• Close deficiencies and issue an accepted handover manifestKeep accountable corrective work, independent closure verification and mandatory readiness decisions separate from test completion counts.
• Investigate governed metrics and retain a historical snapshotUse one authorized metric definition, cutoff and contributing-record set from chart through drill-down and retained snapshot.
• Issue controlled reports and configure delivery schedulesPreview governed data, generate a retained report version and distinguish generation, private download access and external delivery readiness.
• Review an equipment substitutionConnect the proposed equipment revision to technical evidence and separately authorized commercial, budget, schedule and commissioning consequences.

Need assistance?

Documentation explains the task. Existing applications remain responsible for your access, records and support cases.