Osaka, 542-8558,
Japan
Inabata & Co. Technographics
Discover the latest software purchases and digital transformation initiatives being undertaken by Inabata & Co. and its business and technology executives. Each quarter our research team identifies on-prem and cloud applications that are being used by the 4207 Inabata & Co. employees from the public (Press Releases, Customer References, Testimonials, Case Studies and Success Stories) and proprietary sources.
During our research, we have identified that Inabata & Co. has purchased the following applications: Amazon EC2 for Application Hosting and Computing Services in 2021, a-blogcms for Content Management in 2019, SAP S/4HANA Cloud for ERP Financial in 2018 and the related IT decision-makers and key stakeholders.
Our database provides customer insight and contextual information on which enterprise applications and software systems Inabata & Co. is running and its propensity to invest more and deepen its relationship with Amazon Web Services (AWS) , Microsoft , Cloudflare or identify new suppliers as part of their overall Digital and IT transformation projects to stay competitive, fend off threats from disruptive forces, or comply with internal mandates to improve overall enterprise efficiency.
We have been analyzing Inabata & Co. revenues, which have grown to $513.7 million in 2024, plus its IT budget and roadmap, cloud software purchases, aggregating massive amounts of data points that form the basis of our forecast assumptions for Inabata & Co. intention to invest in emerging technologies such as AI, Machine Learning, IoT, Blockchain, Autonomous Database or in cloud-based ERP, HCM, CRM, EPM, Procurement or Treasury applications.
IaaS
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
Insight Source |
|---|---|---|---|---|---|---|---|---|---|
| Amazon Web Services (AWS) | Legacy | Amazon EC2 | Application Hosting and Computing Services | IaaS | n/a | 2021 | 2021 | ||
|
|
|
|
Application Hosting and Computing Services | IaaS |
|
2018 | 2018 |
|
|
|
|
|
|
Content Delivery Network | IaaS |
|
2022 | 2022 |
|
|
|
|
|
|
Content Delivery Network | IaaS |
|
2020 | 2020 |
|
|
Content Management
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
Insight Source |
|---|---|---|---|---|---|---|---|---|---|
| appleple | Legacy | a-blogcms | Content Management | Content Management | n/a | 2019 | 2019 |
ERP Financial Management
Vendor |
Previous System |
Application |
Category |
Market |
VAR/SI |
When |
Live |
Insight |
Insight Source |
|---|---|---|---|---|---|---|---|---|---|
| SAP | SAP ERP ECC 6.0 | SAP S/4HANA Cloud | ERP Financial | ERP Financial Management | Mitsui Knowledge Industry (MKI) | 2018 | 2018 | In 2018, Inabata & Co. engaged Mitsui Knowledge Industry to convert its SAP ERP ECC 6.0 estate to SAP S/4HANA Cloud as the company standard for its global organization, aligning core systems across overseas locations under a single ERP Financial platform. The program targeted consolidation of trading house business management and administration functions into SAP S/4HANA Cloud while preserving the MKI-Trade Suite business process templates already in use at overseas offices. The implementation retained MKI-Trade Suite process designs and focused on application-level configuration rather than process redesign, with MKI operating the operating system, HANA database, and SAP Basis system administration as part of a managed service on Microsoft Azure. SAP S/4HANA Cloud was provisioned in a public cloud architecture, and the managed service scope explicitly included SAP Basis and database operations to centralize run and maintain responsibilities previously split across multiple vendors. Architecture and integrations centered on migrating the SAP S/4HANA instance to Microsoft Azure and embedding Azure Site Recovery for replication, failover, and recovery as part of Inabata’s business continuity plan. MKI executed a combined SAP S/4HANA conversion and Azure migration, running rehearsals to limit cutover risk, targeting under 50 hours of downtime and completing the switchover within 48 hours. The project began execution in November 2019 and leveraged Azure operational features added during the program. Governance shifted toward a single-vendor managed operations model with MKI to eliminate multivendor overhead and standardize runbooks and service menus on Azure. The conversion and move to the MKI managed service on Azure were reported as more efficient than the previous multi-provider setup, and MKI established a repeatable offering that pairs SAP S/4HANA Cloud conversions with Azure migrations for other trading house clients. |
| First Name | Last Name | Title | Function | Department | Phone | |
|---|---|---|---|---|---|---|
| No data found | ||||||
| Date | Company | Status | Vendor | Product | Category | Market |
|---|---|---|---|---|---|---|
| No data found | ||||||