PT SMI: Enhancing an Existing Application with Inquiry Feature

Client

Sarana Multi Infrastruktur (SMI)

Year

2026 - 2026

PT SMI: Enhancing an Existing Application with Inquiry Feature
Sarana Multi Infrastruktur (SMI)

PT SMI's Financial Data Stayed Out of Reach on Mobile

PT Sarana Multi Infrastruktur (Persero), PT SMI, needed its users to check debtor and financial KPI information without waiting until they were back at a desk. The company already had a data warehouse synced with its Core System, so the data existed. It just lacked a mobile-accessible layer on top of it. 

Hence, SMI collaborated with Suitmedia to build a Debtor Data Inquiry feature and integrate it directly into Mobile Approval & Notification Manager, the mobile app its users already had open for approvals.


Why Remote Access to the Desktop System Wouldn't Have Worked

1. Users need remote access to the existing desktop reporting tool. 

Approvals and KPI checks happen in the field, in meetings, between appointments, but the data describing them sat in a Core System and warehouse built for a desk and a scheduled review. That setup worked when financial review was a deskbound task, not when decisions started happening wherever SMI's people actually were.

2. The root cause comes from a mismatch between where SMI's financial decisions actually get made and where the data lives. 

Approvals and KPI checks happen in the field, in meetings, between appointments, while the data describing them sat in a Core System and data warehouse built for a desk and a scheduled review. That architecture made sense when financial review was a deskbound activity, but it stopped matching how SMI's own decision-makers actually worked.

3. Fresher data and system stability pulled in opposite directions.

Querying the Core System directly would have offered more current numbers, at the cost of putting mobile query load on a live transactional system. Sourcing from the already-synced data warehouse instead meant stable performance, with data only as current as the last warehouse sync. SMI chose stability.


Building the Feature Into the App Users Already Had Open

1. Suitmedia integrated the new inquiry feature into Mobile Approval & Notification Manager rather than building a separate app for it. 

Users already opened that app daily to handle approvals, which made it the natural home for a feature meant to support the same kind of in-the-moment decision-making. Building a standalone inquiry app would have meant a separate login, a separate release cycle, and one more icon competing for space on a user's phone, the exact fragmentation SMI was trying to move away from elsewhere in its mobile strategy. Folding the feature into an app people already trusted and used meant adoption didn't depend on anyone remembering a new tool existed. One mobile destination, not two logins to manage.

2. The project moved through a fully gated SDLC, with a written sign-off closing out nearly every stage. 

Solution Definition produced a project charter and a BRD-FSD-TSD documentation set, each requiring sign-off before development began. Solution Development built the feature, its UI/UX, and the data integration against the warehouse, alongside internal test scripts and a system user guide. Solution Testing ran UAT and regression testing, each gated by sign-off, before Solution Deployment handled migration strategy, a production trial run, and a data migration sign-off ahead of go-live.


What This Project Shows About Extending an Existing App

1. A new need doesn't always justify a new app. 

Integrating into Mobile Approval & Notification Manager kept users inside one mobile destination instead of fragmenting their daily toolkit further, even if it meant designing within an existing app's constraints.

2. A sign-off at every stage only works if someone acts on what it protects. 

Gated approvals prevent disputed scope later, but they also slow a project down. Use them where rework would be expensive, and build a measurable target, like time-to-decision or usage rate, into the next enhancement before development starts, not after launch.


Strategic Insights for the C-Suite

1. Mobile enablement projects fail when they're treated as a UI problem

Making a screen smaller, or wrapping an existing interface in a responsive layout, answers the wrong question entirely. The real test isn't whether financial data can technically be displayed on a phone. It's whether the person making a time-sensitive call can get that data at the exact moment the decision is happening, in a meeting, in the field, between appointments, rather than hours later when they're finally back at a desk. 

2. Extending an existing app is a governance decision as much as a technical one. 

Folding a new capability into a tool employees already use daily protects adoption. It also means every future feature request now competes for space inside that same app's architecture and release cycle, a constraint worth weighing before the next enhancement gets added on top of this one.

Industry

Expertises

Organization Type

How We Transform Ideas into Reality