Strengthening the systems behind a trusted market
The Indonesia Stock Exchange (IDX) depends on more than visible trading activity. Behind every market session is a network of operational processes that must be accurate, timely, secure, and resilient.
IDX’s Trading Operation Support System, or SPOP, supports pre-operation activities such as updating trading parameters based on corporate actions and managing trading statements. As IDX’s operations expanded, the system needed to support more types of securities, more reporting activity, and more connections with related applications.
Suitmedia partnered with IDX to enhance SPOP over an ongoing period. The work focused on connecting related systems, automating repetitive updates, improving verification, supporting index operations, and strengthening security controls. The result was designed as SPOP+, a more integrated operational foundation intended to improve efficiency while reducing manual errors and protecting sensitive market information.
A critical market process was becoming too dependent on manual coordination
1. Trading operations begin before the market opens
Market operations do not start when investors begin placing orders. Before trading begins, teams must ensure that relevant parameters, corporate action information, reports, and system conditions are accurate.
SPOP supported these pre-operation activities, including trading parameter updates based on corporate actions and trading statements. These tasks required careful handling because small errors could affect downstream market operations.
As IDX grew, the system needed to accommodate more data, securities, and operational scenarios without making the process harder to control.
2. The existing system needed to support a broader market
IDX wanted SPOP to accommodate all types of stocks being traded or reported on the exchange.
This increased the range of information and operational conditions the system had to manage. A platform designed around a narrower set of use cases could become difficult to maintain as the market expanded.
The challenge was to improve the system without disrupting the processes already relied upon by the Trading Operations division. Enhancements had to add capacity while preserving operational continuity.
3. Related activities were not integrated enough
SPOP needed to work alongside other IDX systems, including IDXNET, DWH, SOA, DSAS, and the IDX website.
When related systems operate separately, employees may need to move data manually between them or verify the same information in multiple places. This creates delays, duplication, and opportunities for inconsistencies.
Integration was therefore more than a technical improvement. It was a way to create a shared operating picture and reduce the number of manual handoffs between systems and teams.
4. Manual updates increased the risk of human error
Trading parameters, remarks, index information, and reports can involve repeated operational steps. When these activities depend heavily on manual input, the risk of omission, duplication, or incorrect timing increases.
The issue is not that employees lack attention or expertise. It is that repetitive work creates opportunities for error even in highly disciplined teams.
Automation could remove avoidable manual steps and allow staff to focus on reviewing exceptions and making decisions that require judgment.
5. Verification needed to become more systematic
A trading operations process needs checks before information is used or released. If verification is handled inconsistently, teams may spend more time reconciling data after the fact.
IDX needed a verification application to provide a clearer control point within the workflow.
This would help ensure that information was reviewed in a consistent manner and that decisions could be traced back to the appropriate operational step.
6. Index operations required more reliable scheduling
Index-related operations included processes where insert and delete activities could create performance or scheduling challenges.
When these activities are handled within the same thread or scheduler, one slow process can affect another. Separating them could help the system manage workloads more predictably.
This was an example of a technical adjustment with an operational purpose. Better scheduling could help protect reliability during time-sensitive market processes.
7. The system handled highly sensitive information
Trading operations involve confidential data, market parameters, system logs, and information that must be protected from unauthorized access or alteration.
Security could not be treated as an optional feature added after development. It needed to be considered across identity, data, connectivity, encryption, logging, and system assessment.
The more integrated SPOP became, the more important security became. More connections create more opportunities for value, but also more points that must be governed.
8. The system had to remain available when operations depended on it
Trading operations require reliability. A system that is slow or unavailable during a critical window can create operational pressure and increase the need for emergency manual work.
SPOP+ needed to be designed for high availability, performance, reliability, and security.
These qualities were not separate technical goals. Together, they supported the confidence of the teams responsible for preparing and managing market operations.
9. Growth required a system that could evolve
IDX’s needs would continue changing as new instruments, reports, processes, and system connections were introduced.
A one-time enhancement would not be enough if the architecture made future changes difficult. SPOP needed a foundation that could support ongoing improvement without repeatedly disrupting trading operations.
The project therefore required both immediate fixes and a longer-term view of maintainability.
Enhancing SPOP through integration, automation, and control
1. Start by identifying the operational friction
Suitmedia first reviewed the features and activities that required improvement or adjustment within SPOP.
The goal was to understand where manual work, disconnected information, verification gaps, or performance constraints affected the Trading Operations division.
This helped prioritize changes based on operational value rather than adding features indiscriminately. Each enhancement needed to improve a real part of the trading preparation and reporting process.
2. Connect IDXNET and SPOP through a listener application
One key enhancement was the integration of IDXNET with SPOP through a listener application.
The listener created a path for related information to move between systems more systematically. This reduced the need for users to transfer or monitor certain information manually.
The integration also improved timing. When one system generated relevant information, the connected process could respond more consistently instead of depending on separate manual action.
3. Build a dedicated verification application
Suitmedia developed a verification application to support the review of operational information.
A dedicated verification layer created a clearer control point. Users could review information before it proceeded to the next stage, helping reduce the risk that incomplete or incorrect data would move through the process.
This also improved accountability. Verification could become a visible and traceable activity rather than an informal check performed differently by different users.
4. Automate trading parameter updates
The solution included automation for parameter updates.
Trading parameters may need to change in response to corporate actions and other market events. Automating these updates could reduce repeated manual entry and improve consistency in how changes were applied.
Automation did not eliminate the need for oversight. It shifted the team’s role from repetitive input toward validation, exception handling, and control.
5. Automate remarks 2 and I-suite processes
SPOP+ also included automation for remarks 2 and I-suite through the development of a SPOP generator application.
The generator supported the creation and handling of required operational outputs more systematically.
This reduced manual preparation and helped standardize the process. A consistent generator could also improve repeatability across different trading and reporting scenarios.
6. Separate index insert and delete processing
To support index automation, the insert and delete threads were separated into different schedulers.
This reduced the risk that one type of process would block or slow the other. Independent scheduling allowed the system to manage these activities with greater control.
The change supported performance and reliability, particularly when multiple index-related actions needed to be processed within time-sensitive operational windows.
7. Connect SPOP+ with the wider IDX system landscape
The enhancement supported integration with DWH, SOA, IDXNET, DSAS, and the IDX website.
Each connection had a different role, but together they created a more coordinated information flow across IDX’s operational environment.
Integration helped reduce duplicate work and improved the ability to maintain consistent information across platforms. It also created a stronger foundation for reporting and downstream use.
8. Design the system for high availability
High availability was a core requirement for the enhanced SPOP application.
The platform needed to remain accessible and operational when trading preparation and reporting activities depended on it. This required attention to system architecture, performance, monitoring, and recovery.
The business reason was clear: operational teams need a dependable system during critical market windows, not one that works only under ordinary conditions.
9. Improve performance by separating workloads
The system’s automation and scheduling changes were designed to distribute processing more effectively.
Separating certain activities helped reduce contention and allowed the platform to handle different tasks with more predictable performance.
This supported operational confidence. Users could complete time-sensitive actions without the system becoming difficult to use when multiple processes ran together.
10. Classify data and information
The security approach included classification of data and information.
Classification helped define how different types of data should be handled, accessed, stored, and protected. Not all information requires the same level of control, so a clear classification model supports more precise security decisions.
This also helped create a shared understanding across teams. Users and administrators could work from clearer rules about the sensitivity of information.
11. Apply data encryption
Encryption was included to protect sensitive information from unauthorized access.
For a trading operations system, data protection is essential both when information is stored and when it moves between connected components.
Encryption strengthened the platform’s security posture and supported confidence in the integration between SPOP and related IDX systems.
12. Manage cryptographic keys securely
Cryptographic key management was considered as part of the wider security design.
Encryption is only as reliable as the way keys are created, stored, used, and protected. A structured approach to key management helped reduce the risk that encrypted data could be compromised through poor control of the keys themselves.
This demonstrated that security was being treated as a complete system rather than a single technical feature.
13. Strengthen user authentication and identification
The platform included controls for authenticating and identifying system users.
This helped ensure that only authorized people could access relevant functions and information. It also created a stronger basis for tracking user activity within the system.
Identity controls were particularly important because SPOP connected several operational systems and supported sensitive pre-operation activities.
14. Manage passwords responsibly
Password management was included as part of the security framework.
Good password controls help reduce the risk of unauthorized access through weak, reused, or poorly managed credentials.
The objective was to make secure access part of normal system use without creating unnecessary friction for authorized employees.
15. Limit system connectivity by time
Time limits on system connectivity added another layer of control.
This helped reduce the exposure created by indefinitely open sessions or connections that remained active longer than necessary.
Time-based controls can support a more disciplined access model, particularly in systems containing confidential market and operational information.
16. Protect log information
System logs can contain sensitive details about users, operations, and events. They are also important for troubleshooting and audit review.
The solution included protection for log information so that records could remain useful without becoming an unmanaged source of exposure.
Secure logs supported both accountability and investigation. Teams could understand what happened while limiting access to the records themselves.
17. Use system assessment data
System assessment data helped IDX evaluate the condition and performance of the platform.
This created a basis for monitoring, identifying weaknesses, and planning future improvements.
Assessment supported a continuous security and performance process. The system could be reviewed and strengthened rather than treated as complete after launch.
18. Build for maintainability and ongoing change
SPOP+ was designed to support continued enhancement as IDX’s operational requirements evolved.
A maintainable platform reduces the cost and risk of future changes. New integrations, automation needs, or security controls can be added within a clearer structure.
This protected the value of the project over time and supported IDX’s broader digital development.
SPOP+ created a stronger operating foundation for IDX
1. IDX gained a more integrated trading operations system
The enhanced SPOP+ application connected related operational activities and systems more effectively.
This reduced the fragmentation between trading preparation, parameter updates, verification, reporting, and related information flows.
The result was a more coordinated environment for the Trading Operations division.
2. Automation reduced repetitive work
Automated parameter updates, SPOP generation, and index processing reduced reliance on manual operational steps.
This helped lower the risk of human error and allowed employees to focus more on reviewing exceptions and ensuring correctness.
The result was greater efficiency without removing the need for human oversight.
3. Verification became a clearer control point
The verification application added structure to the process of checking operational information.
This improved accountability and helped ensure that information was reviewed before it affected downstream activities.
A more systematic verification process also supported stronger confidence in the data used by trading operations.
4. System performance became more predictable
Separating index insert and delete processing into different schedulers helped the system manage workloads more effectively.
This reduced the risk that one process would interfere with another and supported better performance during time-sensitive operations.
Predictable performance is essential when teams rely on the system to prepare the market for trading activity.
5. IDX reduced the risk of inconsistent information
Integration with IDXNET, DWH, SOA, DSAS, and the IDX website helped improve consistency across connected systems.
Reducing manual transfers lowered the risk that different platforms would hold different versions of the same information.
This supported stronger operational coordination and more reliable downstream reporting.
6. Security became a structured part of the platform
Data classification, encryption, key management, authentication, password controls, connection limits, log protection, and system assessment created multiple layers of security.
Together, these controls helped protect confidential information and strengthen the system’s resilience.
The result was a platform better aligned with the sensitivity of financial market operations.
7. The infrastructure supported high availability
SPOP+ was designed to operate on high-availability, high-performance, reliable, and secure infrastructure.
This improved the conditions for the Trading Operations division to perform its work without unnecessary interruption.
Reliability supported both employee confidence and market discipline.
8. Human error risk was reduced
Automation and integration reduced the number of times employees needed to copy, re-enter, or manually process information.
Fewer repetitive steps created fewer opportunities for accidental mistakes.
This was a meaningful operational outcome. In market operations, even small errors can create significant downstream work or risk.
9. The platform supported more effective reporting
Improved integration and structured processing helped support trading report activities more consistently.
Teams could work with information that moved through more controlled and traceable processes.
This improved the foundation for reporting accuracy and operational review.
10. IDX gained a more scalable system
SPOP+ was designed to accommodate different types of stocks being traded or reported and to support other operational needs.
This gave IDX greater flexibility as its market and reporting requirements evolved.
The system could grow with the organization instead of remaining constrained by a narrower original design.
11. The platform strengthened operational confidence
A secure and integrated system helps employees trust that the information they see is current, protected, and connected to the wider environment.
This confidence is important in time-sensitive financial operations. Teams can work more decisively when they are not constantly questioning whether data has been updated or transferred correctly.
12. The system created a foundation for future enhancement
The ongoing nature of the project meant that SPOP+ could continue to evolve after the initial improvements.
IDX could add new features, strengthen integrations, refine automation, and respond to changing operational needs.
The long-term value was therefore greater than a single upgrade. The platform became a more durable foundation for trading operations support.
The deeper lesson: market infrastructure depends on invisible discipline
1. Reliability is built before the market opens
Trading depends on preparation. Parameters, reports, corporate action information, and system conditions must be correct before activity begins.
Systems supporting this work need to be treated as core market infrastructure, even when investors never see them directly.
2. Automation should remove repetition, not remove accountability
Automating parameter updates and generators can reduce manual error, but responsible teams still need to verify outcomes and manage exceptions.
The strongest automation creates more room for judgment while preserving clear controls.
3. Integration reduces operational uncertainty
Connected systems help employees work from a more consistent view of information.
This reduces the need to reconcile records manually and helps teams act with greater confidence.
4. Security must be layered
Confidential market information cannot be protected by one control alone.
Classification, encryption, key management, identity, passwords, session limits, logs, and assessments work together to create a stronger security environment.
5. Scheduling architecture can affect business continuity
The way processes are separated and scheduled can determine whether one workload interferes with another.
Technical architecture is therefore part of operational resilience. It should be designed around time sensitivity and failure impact.
6. Logs are both evidence and risk
Logs support accountability, troubleshooting, and assessment, but they can also contain sensitive information.
Protecting logs preserves their value while reducing the risk that operational history becomes an unmanaged exposure.
7. High availability is a business requirement
A system supporting market preparation cannot be treated like an ordinary internal application.
Availability and recovery should be designed around the consequences of interruption, not only around average usage.
8. Scalable systems support market growth
As instruments, reports, and operational activities expand, the supporting system must keep pace.
A scalable architecture allows the organization to grow without turning every new requirement into a high-risk system redesign.
Strategic Insights for the C-Suite
- Treat trading operations systems as market infrastructure. Their work may be invisible to investors, but their reliability, accuracy, and availability directly support market confidence.
- Automate repetitive processing while preserving human control. The goal is to reduce manual error and free expert teams for validation, exception handling, and judgment—not to remove accountability.
- Use integration to create one reliable operational view. Connected systems reduce duplication, improve data consistency, and help teams make time-sensitive decisions with greater confidence.
- Design security as a layered operating discipline. Data classification, encryption, identity, access limits, password controls, log protection, and assessment must work together. No single control is sufficient.
- Build for future market complexity. Securities, reporting requirements, integrations, and operational processes will evolve. Scalable architecture protects continuity and reduces the risk of repeated, disruptive rebuilds.
