Plants
Plant sites
- Edge gateway
- PLC / SCADA
- Shop-floor tablets
- Local buffer
For CIOs, infrastructure and IT operations heads
Run it in our cloud, your cloud or your plant. We operate it to the same standard.
Your hosting choice depends on policy, data residency, existing cloud commitments and plant connectivity. We support every model, document who runs what, and back it with service levels, recovery targets and monthly reporting.
- India regions by default
- AWS · Azure · Google Cloud
- Customer-cloud ready
- On-premise option
- Plant edge gateways
01 · Deployment options
Five ways to deploy. Compare them side by side.
Trikaan cloud
Multi-tenant SaaS operated by Trikaan, with logical isolation per customer.
Choose this when: You want the fastest start and lowest running effort.
What you get
- Fastest go-live
- All upgrades included
- Lowest total cost
- Fully managed by us
Trade-offs
- Shared infrastructure (isolated data)
- Release timing follows our schedule
| Dimension | Trikaan cloud | Dedicated | Your cloud | On-premise | Hybrid edge |
|---|---|---|---|---|---|
| Data isolation | Logical | Single-tenant | Your account | Your premises | Cloud + plant |
| Data residency | India (default) | Region of choice | Your region | Your site | Mixed |
| Who runs infra | Trikaan | Trikaan | Trikaan (in your account) | You (we support) | Shared |
| Upgrades | Automatic | Scheduled with you | Scheduled with you | Planned projects | Scheduled |
| Time to start | Fastest | Fast | Moderate | Longest | Moderate |
| Custom keys | On request | Yes | Yes | Yes | Yes |
| Offline at plant | Via edge | Via edge | Via edge | Native | Native |
| Cost profile | Subscription | Subscription + infra | Subscription + your cloud bill | Licence + your infra | Subscription + edge |
02 · Reference topology
Plants, field and head office — one platform, two regions.
Field
Field teams
- Offline mobile apps
- GPS & maps
- Queued sync
Primary region
Cloud core
- Application services
- Databases & files
- AI services
- Monitoring
DR region
Recovery site
- Replicated backups
- Standby services
- Runbooks
Plant → cloud
Outbound TLS from edge gateways; optional VPN or private link.
Field → cloud
Encrypted sync over mobile networks when available.
Office → cloud
SSO through your identity provider; optional IP allow-list.
Primary → DR
Encrypted replication of backups to a second region.
03 · How we manage your cloud
A managed-operations calendar, so nothing is left to “someone will check”.
Continuous
- Health checks and uptime monitoring
- Automated alerts to on-call engineers
- Threat detection
- Backup jobs and verification
Weekly
- Patch review and scheduling
- Capacity and performance review
- Failed job and sync review
- Security alert review
Monthly
- Operations report to you
- Access review support
- Cost review (your cloud)
- Restore test sample
Quarterly / annual
- Service review with leadership
- Capacity plan for next quarter
- DR test (annual)
- Architecture review
04 · Service levels & recovery
Pick the resilience your operations need.
Standard
Business
Back-office, planning and reporting workloads.
- Availability target
- [99.5%]
- RPO
- [24 hours]
- RTO
- [24 hours]
- Backups
- Daily, [X] days retained
- Support hours
- Business hours
- DR test
- Annual
Enhanced
Most chosenOperations
Production, dispatch and quality on the shop floor.
- Availability target
- [99.9%]
- RPO
- [1 hour]
- RTO
- [4 hours]
- Backups
- Continuous + daily
- Support hours
- Extended, P1 24×7
- DR test
- Semi-annual
Critical
Mission-critical
Multi-plant, 24×7 operations with machine integration.
- Availability target
- [99.95%]
- RPO
- [15 minutes]
- RTO
- [1 hour]
- Backups
- Continuous, cross-region
- Support hours
- 24×7
- DR test
- Quarterly
[All figures are placeholders; final service levels are set in your contract.] RPO = maximum data loss window. RTO = maximum time to restore service.
Disaster recovery, rehearsed — not assumed
Encrypted backups
Versioned, encrypted and stored separately from production.
Cross-region copies
Backups replicated to a second region.
Point-in-time restore
Recover to a moment before an error or attack.
Immutable copies
Protected from deletion or ransomware.
Documented runbooks
Step-by-step recovery procedures, kept current.
Tested restores
Results shared in a DR test report.
05 · When the internet goes down
Production doesn’t wait for the link to come back.
Plants in industrial areas and field teams in villages lose connectivity. The platform is designed so work continues and data catches up.
| Scenario | What keeps working | On reconnect |
|---|---|---|
| Plant internet down | Edge gateway buffers machine data; local apps queue entries. | Data forwarded in order, no gaps. |
| Field without network | Mobile apps work fully offline — onboarding, mapping, visits. | Queued sync with conflict review. |
| Cloud region issue | Failover to recovery region per tier. | Service restored within RTO. |
| Power cut at plant | Gateway on UPS (recommended); data buffered. | Resumes automatically. |
| ERP unavailable | Integration queue holds messages. | Retries until delivered; alerts if stuck. |
06 · Cloud cost governance
In your cloud, every rupee is visible.
Tagging by plant and module
Every resource labelled so costs map to business units.
Right-sizing
Regular review of over-provisioned resources.
Scheduling
Non-production environments scaled down out of hours.
Reserved capacity advice
Recommendations on commitments and savings plans.
Budgets & alerts
Alerts before spend crosses agreed thresholds.
Monthly cost report
Spend by environment, plant and service.
07 · What you see every month
An operations report your IT head can forward to the CFO.
- Availability
- [99.9x%]
- Incidents by severity
- [N]
- p95 response time
- [X ms]
- Patches applied
- [N]
- Backup verification
- [Pass]
- Cloud spend (your cloud)
- [₹X]
- Changes and releases deployed
- Capacity trend and forecast
- Security alerts and outcomes
- Open actions and owners
08 · Moving in, and moving out
Migration is planned like a cutover. Exit is planned on day one.
Migration
Inventory
Systems, data volumes, integrations and users.
Plan
Wave plan, cutover window, rollback criteria.
Rehearse
Trial migrations with reconciliation reports.
Reconcile
Counts, balances and stock checked against source.
Cut over
Planned window with parallel run where needed.
Decommission
Old systems archived or retired on your approval.
Exit & portability
Full export
All data in open formats (CSV, JSON, PDF, original files).
Schema documentation
Data dictionary so your team can load it elsewhere.
Transition assistance
Agreed hours of support during transition.
Integration handover
API and connector documentation.
Certified deletion
Data deleted after handover, confirmed in writing.
No exit penalties
Beyond the agreed contract term. [Confirm commercial terms.]
Questions IT teams ask
Which cloud providers do you support?
Trikaan cloud runs in India regions by default. For dedicated or customer-cloud deployments we support AWS, Microsoft Azure and Google Cloud, and on-premise or hybrid edge where policy or connectivity requires it.
Where is our data stored?
In India regions by default on Trikaan cloud. Dedicated environments run in the region you choose; customer-cloud deployments stay in your own account and region; on-premise data stays at your site.
Can we move from Trikaan cloud to our own cloud later?
Yes. The same platform runs in every model, so moving is a planned migration — inventory, rehearsal, reconciliation and cutover — not a re-implementation.
Who has access to production?
Only named Trikaan operations engineers, through SSO with least-privilege roles. Access is logged and reviewed, and in your own cloud account access is granted and revocable by you.
How are upgrades handled?
Automatic on Trikaan cloud, scheduled with you on dedicated and customer-cloud deployments, and run as planned projects on-premise — always staged, tested and with instant rollback.
What hardware do plants need?
Typically an edge gateway per plant (on UPS, recommended) to connect PLC/SCADA, weighbridges and scanners, plus shop-floor tablets or terminals. We survey the site and confirm before go-live.
Do you provide a status page?
Yes. Availability is reported on a status page and in the monthly operations report, alongside incidents, patches, backup verification and — in your cloud — spend.
