What Teams Found When They Looked at Their Data
Operations and engineering leads from across Malaysia share what the Pattern Review, Detection Setup, and Watch Programme produced for their teams.
← Back to HomeFrom Our Clients
Engagements completed between April and May 2025.
Ravi Yesudas
Operations Manager · Petaling Jaya
We started with the Pattern Review expecting a fairly generic output. What we got was specific — it identified three areas in our throughput data where patterns had been drifting for weeks. We hadn't noticed because nothing had actually failed yet. The summary was clear enough to share directly with our engineering lead without explanation.
Pattern Review · May 2025
Faridah Hamzah
Head of Engineering · Shah Alam
The training session was the part I didn't expect to find useful — I thought it would be basic — but it changed how my team reads alert data. The framing around what counts as genuine deviation versus routine variation is something we refer back to regularly. Setup took about two and a half weeks from our initial call.
Detection Setup · April 2025
Jason Lau
Operations Lead · Kuala Lumpur
We'd tried two other tools before this. Both were too noisy — my team stopped paying attention to alerts within a week because so many were false. With Caldera Wren, the threshold calibration was done properly and we've had fewer than five alerts in six weeks, all of which were worth investigating. That's what we needed.
Operations Watch Programme · April 2025
Norzahra Kamaruddin
Process Manager · Selangor
I appreciated that the scope was written down clearly before any work started. We knew what we'd receive, what wasn't included, and what the timeline would be. When the summary arrived it was exactly what had been described. Straightforward engagement with no surprises — which is more valuable than it sounds when you've dealt with vague service agreements before.
Pattern Review · May 2025
Teoh Chuan Wei
Systems Engineer · Putrajaya
The maintenance handbook is genuinely useful. We've added two data streams since the initial setup and used it to configure the new thresholds ourselves without going back to the team. That was the whole point — we didn't want to be dependent on an external party for day-to-day operation — and it's worked as intended.
Operations Watch Programme · April 2025
Suraya Ahmad
VP Operations · Kuala Lumpur
We started with the Pattern Review to check whether our data was even in a state worth setting up detection on. It wasn't entirely — there were format issues with two of our streams. Caldera Wren pointed that out in the summary and described what preparation would be needed before setup made sense. Honest, practical, and it saved us from spending money on configuration work that wouldn't have produced clean results.
Pattern Review · May 2025
Case Studies
Detailed accounts of three recent engagements — the situation, the approach, and what it produced.
Manufacturing Operations · Selangor
Operations Watch Programme · 8 weeks
Situation
The operations team was monitoring four production line data streams manually. They were checking figures daily but had no consistent method for identifying when a reading was genuinely outside normal range versus routine variation. Two production pauses in three months had occurred without prior warning from the data.
Approach
We set up the Watch Programme across all four streams. Each stream was reviewed to establish a baseline, thresholds were configured at meaningful deviation points, and a single alert view was set up covering all four streams in one place. A training session and maintenance handbook were provided before handover.
Outcome
In the eight weeks following setup, the team identified two anomalous patterns early enough to investigate before they escalated. The alert view reduced the time spent on daily manual checks by an estimated 40 minutes per day. The maintenance handbook has been used to add one additional data stream independently.
Technology Services Firm · Kuala Lumpur
Detection Setup · 3 weeks
Situation
The engineering team had an existing monitoring tool but found it produced too many alerts for the team to act on meaningfully. Most alerts were dismissed without investigation because the volume had eroded confidence in the system. They wanted something configured more precisely for their actual data patterns.
Approach
We ran a Pattern Review first to establish what the data actually showed, then moved directly into Detection Setup. Thresholds were calibrated against the baseline identified in the review. The training session included specific guidance on distinguishing types of alerts the team would encounter in their environment.
Outcome
Alert volume dropped by over 80% compared to the previous tool. The team began acting on alerts consistently rather than dismissing them. Three genuine anomalies were detected and investigated in the first month — none of which would have stood out against the previous system's noise floor.
Logistics Operation · Klang Valley
Pattern Review · 1 week
Situation
The operations team had collected two years of route and throughput data and wanted to understand whether there were patterns in the data worth monitoring before investing in a full detection setup. They were also unsure whether their data format was suitable for this type of analysis.
Approach
We reviewed a sample across three of their main data streams. One stream had formatting inconsistencies that would require cleaning before detection setup could work reliably. We documented this clearly in the summary alongside findings from the two usable streams.
Outcome
The team used the summary to understand what preparation their data needed before continuing. The Pattern Review findings identified seasonal patterns in throughput figures that the team hadn't previously quantified — information they found useful independent of any subsequent detection work.
By the Numbers
Figures from engagements completed through May 2025.
Engagements completed
Average client satisfaction (out of 5)
Industry sectors served in Malaysia
Engagements delivered within agreed scope
MSC Malaysia Member
Registered technology firm under the MSC Malaysia programme.
PDPA-Aligned
Data handling practices aligned with Malaysia's Personal Data Protection Act 2010.
PIKOM Affiliate
Active member of the National ICT Association of Malaysia.
Reach Us Directly
We respond to enquiries within one business day.
Address
Level 19, Mercu 3, KL Eco City, Jalan Bangsar, 59200 KL
Hours
Mon–Fri 9am–6pm
Sat 9am–1pm
Ready to Look at Your Data?
Send us an enquiry and we'll suggest a sensible starting point based on what you're working with.
Send an Enquiry