Every Friday, we share a roundup of what the PT BATI Mulia Sejahtera team worked on from Monday to Thursday. The week of 5–8 October 2026 was mostly behind-the-scenes work: deepening our technical understanding of the database platform we are testing, and tidying up how we document and review important company documents.
Tuesday–Wednesday: Mapping Tibero's Editions and High-Availability Options
Building on our proof of concept for migrating the Job Shop Planner (JSP) database from Microsoft SQL Server to Tibero, we studied the editions and architectures available, so that our future recommendations match the scale and needs of each system.
Tibero comes in two main editions: Standard Edition (SE) for mid-sized servers, and Enterprise Edition (EE) for large, mission-critical systems. To keep services running when something goes wrong, several levels of high availability are available to choose from.
• Standby HA: a standby server that takes over (fails over) only when the primary server fails.
• Active HA: one node handles writes while the other nodes stay active to serve read queries such as reports.
• TAC (Tibero Active Cluster): multiple nodes read from and write to the same database at once, and capacity grows by adding nodes; its Oracle counterpart is RAC.
Wednesday: Building an Internal Technical Glossary
So that everyone on the team speaks the same language with clients and vendor technical teams, we compiled a Tibero Glossary in Indonesian. It briefly explains product terms, database options and types of technical services, together with their equivalents on platforms the market already knows.
This simple step helps new team members get up to speed faster and makes our explanations to clients clearer and more consistent.
Tuesday–Thursday: Streamlining How We Review Contractual Documents
On the governance side, we reviewed several contractual documents in both Indonesian and English. Each round of revisions came with a summary of changes in Word and PDF, so reviewers can see the key points without rereading the entire document.
This habit speeds up decision-making, keeps the revision trail tidy, and reduces the risk of misinterpretation between languages.
Closing
Not every week brings a big launch. Foundational work like this ensures that every technical recommendation we make, and every agreement we enter, rests on solid understanding. Look out for our next roundup next Friday.
Considering a database migration, or need an architecture that stays reliable when things go wrong? Get in touch with the PT BATI Mulia Sejahtera team at batimulia.com.
More Articles
This Week at BATI: Building JSP Web's Production Environment, Securing Source Code, and Reviewing a Cloud Pilot Plan
This week the BATI team began building JSP Web's production environment, completed a security checklist for its source code and deployment pipeline, and carefully reviewed the scope of work for a JSP Web cloud proof of concept.
This Week at BATI: Preparing JSP Web for the Cloud and Designing a Partner Program
This week the BATI team signed an NDA with a cloud service provider, assessed JSP Web’s readiness to migrate to the cloud, and designed a partner program to extend JSP Web’s reach in manufacturing.
This Week at BATI: Tibero Database Migration, Digital Document Protection, and Our 2026–2037 Roadmap
This week the BATI team tested migrating the Job Shop Planner database to Tibero 7 and prepared a code conversion guide, developed a document protection system for digital forensics, and completed our 2026–2037 Balanced Scorecard.