Power Requirement Intelligence · under development
Power Requirement Intelligence: evidence for review, never generator sizing.
A Production can depend on an approved power design without allowing rental software to invent electrical decisions. Operations360 is developing a bounded workflow that carries reviewed evidence into requirement candidates for authorised people to assess.
Current evidence state Under development: a deterministic read-only evaluator has been verified in staging; requirement proposals and general availability are not released.
The operator problem: power evidence and rental execution drift apart
Power scope may originate in a specialist design, venue instruction, equipment schedule or supplier document. The rental operation still needs exact identities, quantities, operating windows, inspection state, transport responsibility and return obligations. Copying those facts manually can lose versions or make a technical assumption look approved.
What the current evidence supports
Read-only evidence evaluation
A deterministic staging runtime can evaluate bounded Power/Genset evidence and intentionally abstains when exact identity or required evidence is unresolved.
Requirement-review candidate
The intended workflow prepares a candidate from approved source facts, records why each line exists and exposes missing inputs for human review.
Generally available workflow
Production availability, user-facing release and any connection to authoritative requirement commands remain planned and separately gated.
Evidence inputs
Approved external design reference
Exact source, revision, author or approver, applicable venue/Production scope and current approval state.
Known equipment identity
Tenant-owned or supplier-owned model, variant, quantity and serviceability records without inferred equivalence.
Production operating window
Preparation, dispatch, venue-use, return and inspection periods plus current location and hand-off responsibility.
Inspection and responsibility evidence
Recorded inspection/defect state, qualified reviewer, supplier confirmation and unresolved safety or compliance dependencies.
Bounded outputs
Abstention and evidence gaps
The staging evaluator can withhold a conclusion when identity, approval, source scope or evidence freshness is insufficient.
Proposed requirement lines
A candidate may carry exact approved identifiers, quantities, time windows and source provenance for review. It cannot select or size the equipment.
Reviewer questions
Conflicts, missing inspection evidence and unclear ownership become explicit questions for the responsible specialist or operator.
Worked Production examples
Sound · lighting · LED/video
Outdoor show with an approved external power schedule
A qualified external design already states the approved equipment identities and operating assumptions for the current Production revision.
- 01Bind the exact approved design revision to the Production.
- 02Match only recorded equipment identities and supplier commitments without choosing equivalents.
- 03Carry approved quantities and operating windows into a requirement candidate.
- 04Expose missing inspection, supplier or reviewer evidence.
- 05Ask the authorised specialist and Operations reviewer to accept, revise or reject the candidate.
Bounded outcome The under-development workflow preserves an approved decision and its provenance; it does not produce the electrical design.
Event power rental
Unresolved generator identity forces abstention
The source says only “125 kVA set” while the exact model, approval scope and current inspection evidence are missing.
- 01Retain the source phrase without resolving it to a tenant asset.
- 02Identify missing exact identity, scope and inspection evidence.
- 03Return a reviewer-required abstention rather than a recommendation.
Bounded outcome The staging-verified evaluator stays read-only and refuses to turn an underspecified phrase into an equipment decision.
Power evidence review before any Production requirement
Under development This review sequence describes the intended evidence contract; it is not a generally available autonomous workflow.
- 01Confirm the current Production and approved external source revision.
- 02Resolve only exact permitted identities and recorded responsibility.
- 03Show facts, gaps, conflicts, assumptions and abstention codes.
- 04Let the qualified specialist confirm technical validity and scope.
- 05Let Operations review availability, supplier, transport and custody consequences.
- 06Use a separate governed action for any accepted Production requirement.
Power safety and responsibility boundary
- Operations360 does not size or select generators.
- Operations360 does not design phase distribution, cabling, protection or earthing.
- Operations360 does not calculate fuel, runtime, emissions, transport suitability or operating safety.
- Operations360 does not issue a compliance conclusion, permit, certification or specialist approval.
- A requirement candidate cannot reserve, source, purchase, dispatch or operate equipment.
Frequently asked questions
Is Power Requirement Intelligence available now?
No. The requirement workflow is under development. A bounded read-only evaluator has been verified in staging, while proposals and general availability remain unreleased.
Will it tell us which generator to use?
No. Operations360 does not size or select generators and cannot design phase, cabling, protection, earthing, fuel or safety controls.
What can the staging evaluator do?
It can evaluate bounded recorded evidence and abstain when exact identity, source scope or approval evidence is insufficient. It performs no operational write.
Who approves a Power requirement?
Qualified specialists retain technical responsibility. Operations may separately review recorded availability, supplier, transport and custody consequences.
Evaluate the operating model before the roadmap.
Use the current rental workflow and evidence guidance to assess fit. These requirement-intelligence pages do not promise general availability.
Review the Production lifecycleReview AI and approval boundaries