Operations Intelligence · evidence-state hub
Operational intelligence that turns rental evidence into reviewable decisions.
Operations360 is developing an evidence-governed intelligence layer for rental operations. It begins with the Production, preserves uncertainty and permission boundaries, and keeps people responsible for consequential decisions.
Current evidence state Mixed evidence states: shared foundations have been verified in staging; the three requirement recommenders are under development and are not generally available.
The operator problem: decisions arrive before the evidence is complete
A Production may contain approved scope, dates, equipment, package, Crew, transport, supplier and return records, while important decisions still live in calls, documents or specialist judgement. Operational Intelligence should show what is known, what is missing, what changed and what a responsible person must review without converting an assumption into operational truth.
What the current evidence supports
One Production evidence spine
Permission-scoped Production, Requirement, equipment, Warehouse, Crew, Logistics, return and exception records provide the shared evidence context on staging.
Component-aware package planning
Package planning can preview exact-window required and optional component shortages and expand a reviewed template into ordinary Production requirements on staging. It does not auto-reserve or invent substitutes.
Three requirement-review assistants
Power Requirement Intelligence, Vehicle Requirement Intelligence and Team Requirement Intelligence are being developed as distinct review-candidate workflows. None is generally available.
Broader governed assistance
Future increments may connect more evidence and decision types only after deterministic evaluation, tenant isolation, permission and human-review gates are proven.
Evidence inputs
Current Production scope
Approved requirement revisions, venue, operating window, departments, work packages and accountable owners.
Operational records
Equipment identity, reservations, package components, Warehouse state, Crew roles, transport jobs, supplier commitments, custody and returns.
Specialist evidence
Approved external designs, inspections, policies, qualifications and reviewer decisions with source, version, scope and freshness.
Explicit unknowns
Missing identity, quantity, time, location, approval or responsibility remains visible and can force clarification or abstention.
Bounded outputs
Evidence-grounded explanations
Supported evaluations can expose the facts, deductions, source state and unresolved blockers behind a bounded operational answer on staging.
Requirement candidates
The three named workflows may prepare candidates, assumptions and review questions. A candidate is not a reservation, allocation, booking, assignment or technical approval.
Governed follow-through
Later milestones may connect approved candidates to existing authoritative commands only after purpose-specific confirmation, concurrency and audit contracts are accepted.
Worked Production examples
Sound · lighting · LED/video
A mixed corporate Production needs three separate reviews
Approved department requirements exist, but the Production still needs power, vehicle and team requirement decisions before readiness can be assessed.
- 01Read the current Production revision, venue windows and approved department requirements.
- 02Keep the Power, Vehicle and Team questions separate because their evidence and reviewers differ.
- 03Prepare bounded candidates with source facts, assumptions, missing evidence and explicit exclusions.
- 04Route each candidate to the authorised operational or specialist reviewer.
- 05Apply nothing until the relevant person approves it through an authoritative workflow.
Bounded outcome The Production receives three review packets rather than one unexplained recommendation or an autonomous commitment.
Sound rental
Sound package evidence stops at the current product boundary
An approved sound requirement names a console, stage box, I/O and cable needs, while one exact identity and the specialist completeness decision remain unresolved.
- 01Retain the approved requirement and its source version.
- 02Use staging-verified package planning only to preview recorded components and create ordinary requirements after review.
- 03Mark unresolved identity or evidence instead of inferring compatibility.
- 04Require a qualified sound lead to decide technical completeness and approval.
Bounded outcome Package planning is staging-verified. Sound completeness is planned until a reviewed Sound pack exists, so the intelligence layer must abstain from compatibility or release claims.
A common review contract for every proposed requirement
Under development This review sequence describes the intended evidence contract; it is not a generally available autonomous workflow.
- 01Identify the exact Production, current revision and decision being requested.
- 02Resolve permission-visible evidence and label its source, version and freshness.
- 03Separate recorded facts, calculated results, assumptions and missing inputs.
- 04Prepare a bounded candidate with reasons, alternatives and explicit exclusions.
- 05Ask an authorised person to accept, revise or reject the candidate.
- 06Use the existing authoritative service for any later write and retain before-and-after evidence.
The intelligence boundary
- No requirement candidate is a reservation, purchase, booking, allocation, assignment or supplier commitment.
- No model output may bypass tenant isolation, role permissions, current-version checks or explicit approval.
- No Sound output may claim acoustic, RF, electrical, rigging, compatibility approval or technical-release approval.
- Power, Vehicle and Team decisions retain their separate specialist and operational exclusions.
- A missing or conflicting source must produce clarification, visible uncertainty or abstention-not invented certainty.
Frequently asked questions
Is Operational Intelligence generally available?
No. Shared foundations have been verified in staging, while Power, Vehicle and Team Requirement Intelligence are under development and their broader availability is planned.
Does it make operational changes automatically?
No. Under-development requirement candidates are review material only. Any future write must use the relevant permissioned service and explicit confirmation.
Can it approve a Sound system?
No. Package planning has been verified in staging, but Sound completeness is planned pending a reviewed Sound pack. Qualified people retain technical design, compatibility and approval responsibility.
Why publish these pages before release?
They explain the operator problems, evidence contract, development state and exclusions so evaluators can understand the direction without mistaking it for a generally available feature.
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