Small evolutions, strong constraints – 72 m.d/year
Context: for “a major international group”, a purchase income application system for all contracts, based on the consolidation of the actual volumes of purchases of all subsidiaries.
A BRMS (Business Rules Management System) formalizes contracts with suppliers: in case of evolution, it is essential to ensure traceability of each changes and the history logging for legal, regulatory, fiscal requirements and to allow auditors to rule correctly on accounts completeness and accuracy. Failure to comply with these requirements can have very serious legal and economic consequences.
The detailed understanding of the requirements and solutions allowed us the following achievements:
- Advocate for an overhaul of a component whose implementation has improved performance by a factor of 20 of the calculation.
- Detect and fix anomalies, perform functional and adaptive changes (for example, rules engine upgrade).
- Simplify and add deployment process automation.
- Level 3 support
Technologies, tools : .NET, C#, rule engine BRMS (Business Rules Management System), IBM JRules/ODM, Web services, Oracle DB, OBI (Oracle BI engine).
Around an MDM software package, the customer emploies many contractors for MDM and applications interfaces developments. To ensure consistency and the successful completion of complex production restarts, he gave us the responsibility for deploying “complex” releases relying on the durability of Cantor teams to ensure the continuity of expertise.
Technologies, tools : IBM MDM CE, JavaEE, DB2
Technical study for development of a new business functionality
Our maintenance tasks led us to locate some technical anomalies in the data. As part of preventive maintenance periodic reviews, we identified the cause of the anomalies: a business process failure.
We suggested to use a “business data quality” reporting that has been agreed to and has quickly become a standard tool for users.
Technologies, tools : MDM STIBO STEP, JavaEE, Jboss, MySQL, TCD Excel