Status update on iDCIM deployment and operational metrics:

1: The re/installation process

We have loop back the database log and retrieved the installation history from 18th Nov 2025 (the date sync with Sim-DCIM)

Below is the statistics of the re/installation process:

Result	Count	%
Succ	145	81%
Fail	34	19%

The 34 fails are mainly due to below:

Reason	e.g.
Hardware issue	Parts connectivities mostly
BIOS issue	Wrong BIOS setting, some BIOS configs are now automated
Data Error	Wrong Input of Router IP / IPMI password etc.
Compatibility / Bug	Compatibility (like X11 do not support ISO Mount)

Some portion of install is through mount ISO to install, statistics are as below:

Result	Count	%
Succ	145 + 127	82%
Fail	34 + 27	18%

Note: with new PXE-Server is deployed on all DC, success rate is believed to improve more.

And for other network automation, statistics are as below:

Operation	Succ	Fail	%
Update Bandwidth Record	246	43	85%
Assign IP	251	38	86%
Release IP	229	10	96%
Get Real-time Switch Config	191	7	96%
Update VLAN	73	0	100%

Average time taken for re/install

The Actual Time Taken Recorded:

• Average installation time: ~20 minutes
• of course time taken before and after installation also affecting the total time
  • e.g. the >2hrs order last week are due hardware issue
• We can deep-dive into Sales-to-NOC inter-operation to improve the time taken if you allow

2: The "Error" issues regardings in Slack channels

Today we developed a tidy software with help of Ice:

• to scan through database of Sim-DCIM and iDCIM
• to identify the discrepancies between these 2 systems

The report after Ice reviewed can reveal that:

• Most of the "Error" are mainly due to the Unfamiliar to iDCIM operation
• e.g.:
  • Billings did not terminate Service either in Sim-DCIM or iDCIM
  • NOC did not create service before performing operation in iDCIM
  • Non-equivalent operations were performed in Sim-DCIM and iDCIM

Conclusion:

• As in the data-level, iDCIM can replicated operation as in Sim-DCIM
• But the Not perfected Training and SOP to NOC and Other teams caused these discrepancies/errors. We need to Apologize and Improve

3: Bandwidth via Tokyo to China

feature has been implemented, now:

• asking Kevin to provide multiple Direct-China servers for testing
• UI is also updated to support colleagues to control the IP list
• currently we can get all MRTG graphs, tomorrow I will get network team to help to figure out the mapping between "RRID" and Servers

4: Auto Provisionings

As we priviously discussed with you:

• There is a queue of servers as Standard Packages
• during auto-provisioning, these servers will be assigned to the installation orders
• This feature is already implemented and ready to go

Ice's Feedback:

• ⚠️ Concern: This flow will greatly increase workload for NOC
• Requested us to imitate the flow from Sim-DCIM instead
• ✅ Formula received from Tommy for filtering available servers
• ⚠️ Your advice required on how to proceed

5: API for Clients, Reseller Portal

from the April discussion with you of features of reseller portal:

• ✅ Client and Reseller API already developed alongside iDCIM progress
• 📅 Testing phase will begin once iDCIM is stably transitioned
• DataPlug, VA will integrate the Reseller API on their WHMCS

6: Other Ongoing Projects

• ☁️ Cloud Infrastructure Project:
  • ✅ Ceph cluster deployment in progress (Cheong) - distributed storage solution
  • 🚀 Kube-Virt cluster and networking (Brandon & Mike) - VM orchestration on Kubernetes
• 🔒 Security & Monitoring Enhancement:
  • 📊 SIEM solution deployment underway (Cheong) - enhanced monitoring for iDCIM and all projects