🎬 Clorian Ecosystem Presentation
Overview: From ITSM to Business OperationsPurpose: More than a technical exercise, Clorian is a simulated environment documenting a two-act operational evolution, designed to deliver immediate value in Shared Service Centers (SSC) environments:
- Act 1 (Clorian 1.0 – ITSM): Solving a classic traceability problem: real-time bidirectional synchronization between an operational database and Jira Cloud via webhooks, eliminating polling latency.
- Act 2 (Clorian 2.0 – Business Ops): Evolution toward business process control. On that same data layer, an Order-to-Cash reconciliation control (three-way match) is implemented, with exception classification by severity and a 48h SLA.
The result is not a raw data dump, but a prioritized exception report. The same AHT and FCR logic from digital banking, applied to revenue protection and operational coordination.
☁️ Clorian 1.0: ITSM Synchronization (MySQL ↔ Jira)
Real-Time IntegrationPurpose: Operational coordination through bidirectional incident synchronization between MySQL and Jira Cloud, applying ITIL v4 principles and ensuring complete ticket lifecycle traceability.
🔧 Technical Stack
Java 17+ • JDBC • Spring Boot 3.3.3 • REST API • MySQL
✅ Key Features
- Emitter (DB Connector): Detection of new tickets, automatic issue creation in Jira, and status polling every 30 seconds.
- Receiver (Webhook): HTTP endpoint for real-time updates (<1s latency) from Jira to MySQL.
- Cycle prevention: Idempotency logic via the
last_sync_statusfield to avoid infinite loops. - Unified mapping: Precise synchronization of 5 states (Open, In Progress, Waiting for Customer, Resolved, Closed).
🎥 Video Demo
Watch the end-to-end flow: ticket created in MySQL → appears in Jira (~30s) → status change in Jira → immediate update in MySQL (<1s).
📊 Clorian 2.0: O2C Reconciliation Control (Order-to-Cash)
Business Operations & SSCPurpose: Reuse the ecosystem’s data layer to control the Order-to-Cash business process: detect financial exceptions, prioritize them by severity, and generate executive reports for stakeholders, applying the same AHT/FCR logic from digital banking.
🔧 Tech Stack
SQL (MySQL) • Three-Way Match • Exception Analysis • SLA & KPIs
✅ Key Features
- Explicit business rule: Every confirmed booking must match to the penny in collected amount (payments – refunds) and delivered amount (tickets). Any deviation is an exception.
- Three-Way Match: Cross-referencing 3 sources of truth (Booking vs Payment vs Ticket) to simultaneously detect collection and delivery gaps.
- Severity classification: Automatic labeling (CRITICAL, HIGH, MEDIUM) combining the amount at risk and time open.
- SLA control: Breach alert at 48 hours, replicating regulated banking operation standards.
- Executive summary: Aggregated queries delivering 4 control KPIs (number of exceptions, € at risk, average hours, breaches) instead of raw data dumps.
🎥 Video Demo
View control flow: business rule → three-way match → prioritized exceptions view → executive summary for decision making.
🔍 How do these projects relate to my professional profile?
This ecosystem is not a theoretical exercise: it’s the practical application of a two-act professional evolution, designed to deliver immediate value in Shared Service Centers (SSC) and Business Operations environments:
- Clorian 1.0 (ITSM): Demonstrates my ability to understand integration architectures, coordinate with technical teams, and ensure complete incident traceability (ITIL v4).
- Clorian 2.0 (Business Ops): Demonstrates that I can use that same data to govern a business process. I apply internal control logic (three-way match), severity classification, and executive reporting, learning quickly from the Senior who designs the strategy.
- Day 1 value: I don’t aim to be a senior architect or a pure developer. My value lies in being the operational bridge: I understand the technical logic (Java, SQL, APIs) to translate business needs into compliance controls, SLAs, and frictionless traceability.
🔎 I’m actively seeking opportunities in Barcelona as: