Skip to main content
KaryaFlow business operating system
Explore the product

Industry workflow / HVAC and AC service

Read the system before replacing the symptom.

Connect indoor and outdoor units, operating readings, refrigerant use, preventive schedules, technician stock and commercial closure in one service history.

Explore a sample workflowRequest an evaluation workspace

OPERATING SCENE

Paired units, refrigerant accountability and seasonal service

An AC complaint may originate in airflow, refrigerant, power, controls, drainage or installation. A useful docket preserves paired-unit identity and measured conditions, not merely a completion photograph.

Shared field-service kernelVertical-specific docketConfigurable industry workflow

The service daybook

One accountable chain from request to settlement.

The shared field-service kernel keeps customer, site, asset, job, inventory, money, people, approval and audit records continuous. This template changes the vocabulary, controls and evidence required for this trade.
  1. 01

    Identify the system

    Pair the units and bring capacity, refrigerant, warranty, access and fault history into view.

  2. 02

    Plan the visit

    Assign the right competence, stock, tools and service window for the stated condition.

  3. 03

    Measure and correct

    Record operating conditions, diagnosis, material, work and post-service readings.

  4. 04

    Close the loop

    Resolve entitlement, invoice, collection, recommendations and the next planned obligation.

Vertical operating dossier

The records this service model must understand.

Each ledger below answers a different operational question. Together they prevent critical context from collapsing into free-text notes.
01

Jobs

Service motions

The template starts with recognisable work, not a generic task type.

  • Complaint diagnosis and repair
  • Installation, relocation and commissioning
  • Preventive maintenance and seasonal readiness
  • Refrigerant leak detection and rectification
  • AMC visit and repeat-performance review
02

Assets

Installed or entrusted assets

Every visit inherits the identity, location, entitlement and history needed to act responsibly.

  • Indoor and outdoor unit pairing, model and serial
  • Capacity, refrigerant type and installation date
  • Electrical, drainage, piping and controller context
  • Site zone, access and operating environment
  • Reading, fault and component-replacement history
03

Evidence

Proof another role can trust

Evidence stays proportionate, permission-aware and attached to the exact job and asset.

  • Ambient, inlet and outlet conditions
  • Pressure, current or temperature readings appropriate to the job
  • Leak, drainage, airflow and electrical observations
  • Refrigerant type and quantity issued or recovered
  • Commissioning test and customer handover
04

Warranty and AMC

Commercial entitlement

Coverage, exclusions and external authority remain explicit before work becomes a claim or invoice.

  • Separate installation warranty, manufacturer warranty and AMC scope
  • Generate planned visits from covered assets and seasonal cadence
  • Keep excluded material and chargeable variation visible before work
  • Carry repeat cooling complaints into entitlement and root-cause review
05

Stock and tools

Field custody

Availability means the right item, responsible custodian and reconciled return state are known.

  • Track refrigerant cylinders and usage by technician and job
  • Reserve filters, capacitors, controls, copper and drainage material
  • Record gauges, vacuum pumps and test instruments required
  • Reconcile recovered components and unused material at return
06

Payments and collections

Money at the handoff

The service result, invoice responsibility and actual settlement state remain distinct.

  • Approve installation or repair variation before chargeable work
  • Separate labour, consumables, parts and tax on the invoice handoff
  • Record collection mode and provider-confirmed payment state
  • Keep AMC-covered work distinct from paid extras

Service promise and system boundary

Urgency is operational. Authority is explicit.

SLA clocks must produce responsible action, while every external integration reports only what its provider has actually confirmed.
SLAResponse and closure controls
  1. 01

    Prioritise no-cooling, critical-site and repeat complaints by policy

  2. 02

    Expose access, skill, part and refrigerant dependencies before dispatch

  3. 03

    Escalate missed arrival, unresolved leak and repeat performance loss

  4. 04

    Closure requires readings, material usage and operating-state evidence

PROVIDERExternal authority boundaries
  • Maps and routing are estimates returned by the configured provider
  • Object storage preserves uploaded evidence but does not validate the diagnosis
  • GST and payment outcomes are claimed only after provider confirmation
  • Messaging status reflects provider delivery, not customer comprehension
EXCEPTION VIEW

Lead with what can no longer wait.

Surface repeat cooling loss, unit-pair mismatch, unsafe electrical observations, unexplained refrigerant use, missed PM and chargeable work awaiting approval.

Cross-ledger continuity

The value appears at the handoff.

The template must preserve these relationships rather than creating separate customer, stock, service and billing truths.
01

Asset complaint

Asset complaint to qualified dispatch. The destination receives source context, responsible role and evidence state.

02

Diagnosis

Diagnosis to estimate approval. The destination receives source context, responsible role and evidence state.

03

Refrigerant issue

Refrigerant issue to measured consumption. The destination receives source context, responsible role and evidence state.

04

Completion

Completion to GST-ready invoice. The destination receives source context, responsible role and evidence state.

05

Service history

Service history to AMC planning. The destination receives source context, responsible role and evidence state.

Explore other industries

One service core, shaped for different operating contexts.

Each workflow adapts records, checklists and exception language without creating a separate business system.
SERVICE

Service and technical operations

Industry-shaped workflows built on the shared KaryaFlow service core.

Industry workflowPest controlTreatment plans, chemical custody and recurring proof
Industry workflowElectrical contractorProjects, crews, measured work and material control
Industry workflowPlumbingEmergency triage, fittings custody and revisit control
Industry workflowElevator and lift AMCStatutory schedules, certified assignment and digital logbooks
Industry workflowWater purifierUnit history, consumable lifecycle and measured service
Industry workflowSecurity and CCTVDevice topology, commissioning proof and privacy-aware service
Industry workflowFire safetyExpiry control, statutory inspections and corrective ownership
Industry workflowSolarSite arrays, generation evidence and planned care
Industry workflowFacility managementMulti-site SLAs, mixed disciplines and client reporting
Industry workflowAppliance serviceSerialised products, entitlement decisions and part recovery
OPERATIONS

Site and business operations

Additional workflows for teams managing people, places, equipment and customer commitments.

Industry workflowHome automationControllers, scenes and consent-aware configuration handoff
Industry workflowIT and computerDevice custody, diagnostics and data-safe repair
Industry workflowAutomobile repairVehicle history, estimate control and workshop custody
Industry workflowEquipment rentalAvailability, custody, meter use and return condition
Industry workflowCleaning servicesSite zones, recurring crews and quality recovery
Industry workflowMedical equipmentDevice traceability, controlled evidence and service escalation

AC and HVAC evaluation

Inspect the operating pattern with sample data.

Use the Playground for immediate exploration or request a scoped evaluation workspace for your organisation.
Open the PlaygroundSee the shared field core