Enterprise technology engineering

Engineering for systems
that cannot stop

MC3D is a technology engineering firm. It takes on the architecture, the software development, the integration, the modernization, the observability, and the artificial intelligence of the system already in production. The core stays up.

Let's talk about your operationSee how we solve it

Where MC3D comes in

MC3D takes that layer. The ERP, the bus, and the legacy stack remain the client's.

Published experience at Banco de Chile, Entel, and the Budget Office.

01 · The client's

Channels

  • Branch, web, and mobile
  • IVR and service
  • Business-to-business integration

02 · MC3D takes this

Engineering

  • Enterprise architecture and software development
  • Integration and modernization
  • Observability and artificial intelligence

03 · Stays up

Core

  • Oracle SOA, OSB, and OIC
  • SAP, Banner, and CRM
  • Tuxedo and other legacy systems

A transaction crosses that engineering. The core does not stop.

  • Continuity Integration without cutting the service.
  • Traceability Every hop is recorded.
  • Change The core is modernized while it stays up.

Capabilities

Architecture, software development, and artificial intelligence, alongside integration

The system already in production stays. MC3D sustains the engineering that connects it to the channels and makes it visible.

01

Enterprise architecture

We write down what stays in the system already running and what engineering is built on top: boundaries, rules, and how the service is observed.

02

Software development

The process the package does not provide is built to measure. When the suite does not cover the record, the Java, or the inference, MC3D's platforms come in.

03

Integration and modernization

Oracle, SAP, or the legacy stack stays. Integration and modernization run without cutting the service.

04

Observability

The transaction trace and system supervision are visible before the service stops. In Falcon, InfraSense watches the nodes.

05

Artificial intelligence

KAI infers where the file cannot leave the premises: documents, vision, and voice. Compute is added by joining the machine to the grid.

Own platforms / Built by MC3D

Intellectual property for what the suite does not cover

KAI, Falcon LCP, Phoenix AWR, and AIRE belong to MC3D. They do not replace the core already in operation. They cover inference, the business record, the Java interface, and the process.

Artificial intelligence

KAI

Multi-agent inference where the file does not leave the premises. The engine runs in Java: documents with RAG and CAG, vision, and voice. The caller receives a ticket and polls until the answer is ready. Adding a machine means joining it to the CSF grid.

On premises · RAG and CAG · Vision and voice
See the platform

Enterprise solutions

Falcon LCP

The data the ERP does not model returns to a single copy. The module is an XSD: the application, the DMN rules, the report, the map, and supervision come from that schema.

XSD · DMN rules · InfraSense
See the platform

Technology continuity

Phoenix AWR

The runtime for the Java interface the browser no longer runs. Applets, AWT, Swing, and JavaFX run on the desktop and on Android.

Desktop · Android · JavaFX
See the platform

Enterprise orchestration

AIRE

The designer and console for BPEL 2.0 processes. The process stays explicit and the instance can be followed, alongside the suite already in operation.

BPEL 2.0 · Processes · Instances
See the platform

Experience

What was solved, and on which platform

Banking

Banco de Chile

Architecture of the electronic funds transfer on OSB and SOA Suite, with Oracle Business Rules. Cloud Control supervises the operation.

Telecommunications

Entel

Reference architecture on SOA Suite 12c and BPM Suite. Oracle ERP Cloud integrated with SAP OnPremise.

Government

Budget Office

Design and construction of SIGFE Agregación: a custom service bus, transmission agents, and a rules engine.

Education

Santo Tomás

Oracle CRM, benefits management, Banner ERP, MINEDUC, and DEMRE in the same operation, plus the quotation application.

Method

From the operation to the system, and from the system to the code

01 /

We read what cannot be switched off

We start from what is already in production. The architecture is agreed with the people who run it.

02 /

We fix the system

What is integrated, what a rule decides, and what stays visible. Documents are reviewed in pairs before building.

03 /

We leave it running and visible

Implementation and go-live without cutting the service. The core keeps answering while it is integrated.

Let's talk

Tell us what
cannot stop

Write to MC3D