Hochiki Corporation Adopts 'ACMS Apex' to In-House Data Integration Infrastructure
Hochiki Corporation has adopted Data Application's 'ACMS Apex' platform to streamline data integration between systems and accelerate digital transformation. By moving away from siloed custom developments, the company has established a standardized in-house integration foundation.
📋 Article Processing Timeline
- 📰 Published: May 20, 2026 at 20:53
- 🔍 Collected: May 20, 2026 at 12:31
- 🤖 AI Analyzed: May 20, 2026 at 12:36 (4 min after Collected)
Data Applications (DAL) announced that Hochiki Corporation, a company specializing in fire and disaster prevention, has adopted the enterprise data integration platform 'ACMS Apex' to build an in-house integration infrastructure for both internal and external systems.
[Background of Implementation]
Hochiki previously utilized a model of individual development and operation for various business systems, including SAP S/4HANA, which led to several challenges:
- Long lead times (6 months to a year) to implement connections due to technical adjustments.
- Increased security risks due to fragmented access routes.
- Deteriorated maintainability and internal control caused by legacy code from individual developments.
- Increased burden of cross-departmental coordination.
Hochiki decided to build a common integration platform ensuring flexibility and security.
[Reasons for Adoption]
The decision was driven by ACMS Apex's ability to integrate with the 'RACCOON' data handling platform, its intuitive GUI facilitating rapid in-house development, and its robust security, internal control capabilities, and scalability for future external service integration.
[Results]
By centralizing system integration through ACMS Apex and standardizing connection methods, the following results were achieved:
- Established a framework for stable integration with external systems.
- Significant reduction in time required for recovery during system failures.
- Reduction in development and operational workload, allowing the IT department to concentrate resources on core business goals.
[Future Outlook]
Hochiki plans to further consolidate its system integrations into ACMS Apex, aiming to continue promoting company-wide digital transformation with a secure, in-house-developed platform.
[Background of Implementation]
Hochiki previously utilized a model of individual development and operation for various business systems, including SAP S/4HANA, which led to several challenges:
- Long lead times (6 months to a year) to implement connections due to technical adjustments.
- Increased security risks due to fragmented access routes.
- Deteriorated maintainability and internal control caused by legacy code from individual developments.
- Increased burden of cross-departmental coordination.
Hochiki decided to build a common integration platform ensuring flexibility and security.
[Reasons for Adoption]
The decision was driven by ACMS Apex's ability to integrate with the 'RACCOON' data handling platform, its intuitive GUI facilitating rapid in-house development, and its robust security, internal control capabilities, and scalability for future external service integration.
[Results]
By centralizing system integration through ACMS Apex and standardizing connection methods, the following results were achieved:
- Established a framework for stable integration with external systems.
- Significant reduction in time required for recovery during system failures.
- Reduction in development and operational workload, allowing the IT department to concentrate resources on core business goals.
[Future Outlook]
Hochiki plans to further consolidate its system integrations into ACMS Apex, aiming to continue promoting company-wide digital transformation with a secure, in-house-developed platform.
FAQ
What was the main purpose of Hochiki's adoption of ACMS Apex?
The goal was to move away from individual development of system integrations, reduce operational burdens, improve security, strengthen internal controls, and establish a foundation for DX.
Why was ACMS Apex chosen?
It was selected for its intuitive GUI enabling rapid in-house development, integration with ETL features, future scalability, and robust security and internal controls.
What benefits have been achieved?
The standardization of integrations has established a stable operating environment, reduced operational workloads, and allowed the IT department to focus on strategic tasks.