Managed Operations
Capacity nobody hands over and walks away from. Local L1 and L2 engineers run it round the clock, on a contractual SLA with structured incident and RMA processes.
Two tiers, one window
| Tier | Role | Position |
|---|---|---|
| L1 | Data centre operations + RMA engineers | Stationed on site |
| L2 | Network + GPU server engineers | Senior engineering |
| PM | Project / service delivery manager | Single contact window |
Response by priority, in the contract
| Priority | Level | Response |
|---|---|---|
| P1 | Critical | 1-hour response |
| P2 | High | 4-hour response |
| P3 | Standard | Next business day |
Continuous monitoring — proactive incident management across all active deployments.
Active managed services
Indonesia
32× · 32-server GPU estate
Active managed serviceSingapore
31× · GPU servers on an InfiniBand fabric
Ongoing Day 2 operationsMalaysia
64× · Rack-scale GPU cluster for a Tier-1 data centre operator
Under monitoringServices include: L1 DC operations · GPU server management · network monitoring · RMA coordination · SLA incident response.
Seven stages, one goal — recovery
-
01
Detection
Identify issues through monitoring, alerts or user reports.
-
02
Assessment
Evaluate severity, scope of impact and affected systems.
-
03
Containment
Take immediate measures to prevent the impact from spreading.
-
04
Investigation
Investigate the root cause and the path to resolution.
-
05
Recovery
Implement the fix and restore systems and services.
-
06
Verification
Confirm service stability and monitor full recovery.
-
07
Closure & RCA
Document findings and implement improvements.
Guiding principles: Protect people and systems · Act fast and responsibly · Collaborate effectively · Communicate clearly · Keep improving
End-to-end RMA, detection to closure
-
01
Fault detection
Monitoring or alert triggers, user-identified issues, ticket raised to RCS support.
-
02
Troubleshooting & verification
Initial troubleshooting, hardware fault verified, affected assets identified.
-
03
RMA request
RMA raised with the OEM with required information; OEM approval.
-
04
Replacement
OEM approves the RMA, replacement shipped, defective part returned.
-
05
Install & verify
Replacement installed, function verified, system confirmed operational.
-
06
Closure
Ticket updated, resolution documented, RMA closed.
Covers all in-service assets: GPU servers · CPU servers · network equipment · storage · other infrastructure.
- All RMA activity follows OEM policy and warranty terms.
- RMA turnaround depends on the OEM and parts availability.
- RCS monitoring integrates alerting, tracking and reporting.
The rest of the lifecycle
AI Compute
Built by Us, Scaled for You. Deploy your GPU cloud instantly on our self-managed clusters. Whether launching your first platform or scaling existing workloads to meet enterprise demand, we deliver the power and reliability you need.
PlatformCloud Platform & Kubernetes
Bring your own images, schedulers and pipelines. You get a Kubernetes cluster and the namespace; we keep the nodes, drivers and fabric underneath healthy.
Tell us what you need to run.
Share your workload requirements, market focus, and timeline. Our expert teams across Taiwan, Singapore, Malaysia, and Indonesia will design the optimal compute service—leveraging our existing GPU capacity or building a dedicated infrastructure tailored to your needs.
Talk to our team →