Pilot → Scale

How KintaTair works

1

Field pilots first: learn by doing

We begin with a field pilot tailored to the customer's operational profile. A pilot is designed as a defined scenario: select a representative zone (office floor, production line, or storage area), instrument it with sensors and an actuator package, and run the system under normal operating conditions for a predefined period. This practical approach surfaces edge cases such as shift-based occupancy patterns, equipment heat loads, and local ventilation constraints. Each pilot produces a deployment playbook that includes device placement, commissioning checklists and scenario-specific control logic.

Case example: a small manufacturing floor in Penang was instrumented for four weeks. The pilot captured occupancy peaks tied to two daily shifts and identified times when ventilation could be reduced safely without degrading measured air trends. The resulting playbook informed a repeatable deployment across two similar facilities in the same industrial park.

2

Data collection and measurable outcomes

Data collection focuses on actionable metrics: CO2 trends, particulate measurements, temperature and humidity, equipment runtime and energy consumption hooks. We prioritize data that drives decisions about when to ventilate, when to recirculate, and when to defer equipment activation based on occupancy and air quality.

  • Sensor placement scenarios derived from pilot learnings
  • Standardized data schemas for cross-site comparison
  • Report templates for compliance and operational review

Collected data is presented in concise reports that compare baseline and pilot-period trends. These reports emphasize what changed, under which conditions, and actionable next steps for facility managers.

3

AI-driven control with human oversight

AI-driven control is applied incrementally. We first validate simple rule-based strategies from pilot insights, then layer adaptive algorithms that adjust setpoints and ventilation schedules based on observed behavior. Human operators retain override capabilities and full visibility into decision logs.

Practical scenario: adaptive ventilation that follows occupancy patterns while keeping key air metrics within target ranges, audited by staff during a 30-day monitoring window.

Our AI models are trained on local pilot data and tuned for the specific operational profile; we avoid opaque one-size-fits-all configurations and instead produce interpretable control actions aligned with the site's objectives.

4

Integration with existing systems

Integration is planned from day one. KintaTair devices provide local control interfaces, Modbus/API adapters and exportable telemetry so they can coexist with building management systems and energy meters.

We map integration points in a pre-deployment technical survey and prioritize non-invasive strategies where possible to reduce downtime.

Typical integration paths

Examples include direct actuator control for ventilation dampers, BACnet/Modbus bridges for legacy BMS, and secure cloud connectors for analytics. Each path is documented with configuration templates for repeatable rollout.

5

Service, maintenance and local support

Service and maintenance are designed for local operability. After commissioning, we hand over an operational manual and a maintenance checklist tailored to the installed device set and the site's environmental conditions.

KintaTair supports scheduled health checks, remote diagnostics and on-site commissioning visits depending on the selected service tier.

6

Commercial models and procurement scenarios

We offer commercial models that reflect common procurement scenarios in Malaysia: pay-per-site pilots, subscription-based analytics, and resources purchase with optional service contracts.

  • Pilot contracts with defined scope and success criteria
  • Subscription analytics and remote support tiers
  • Resources purchase with local commissioning and optional service SLA

Each model includes transparent deliverables so procurement teams can evaluate cost, timeline and expected operational outputs without vague claims.

7

From pilot to repeatable deployment

Scaling from a pilot to multiple sites follows a playbook-based approach: reuse validated device configurations, replicate sensor placement patterns, and reuse control recipes that matched the pilot scenario. Our emphasis on case studies and operational examples helps facilities compare like-for-like deployments and make procurement decisions based on measured pilot outcomes rather than theoretical benefits.

Case study: a mid-size manufacturing plant in Penang integrated KintaTair intelligent climate devices and an AI-powered air monitoring layer to reduce downtime from HVAC variability. Scenario: sensors deployed in four production halls, AI models trained on two months of local temperature, humidity, and particulate data. Outcome: operations teams received prioritized maintenance alerts and ventilation schedules that aligned with production cycles, enabling better control over process-critical humidity and reducing scrap from moisture-sensitive processes. The narrative focuses on step-by-step adaptation: baseline audit, targeted sensor placement, model calibration with site-specific data, and phased rollout. Practical lessons include balancing sensor density with actionable analytics, validating model recommendations with short A/B trials, and creating operator dashboards that translate AI signals into simple operational steps.

Contact our commercial team

For commercial partnerships, field trials, or procurement for Malaysian facilities, contact KintaTair. We work with facility managers, integrators, and energy teams to design deployment scenarios, pilot proofs of concept, and operational handover documents that align with local regulations and site constraints.

  • [email protected]
  • +60128365198
  • Tingkat Perusahaan 6, Perai Industrial Estate, 13600 Perai, Pinang, Malaysia
  • 860910491069
Request a pilot