--- title: "Engineering Manager - Enterprise Integration Platform (alias ESB)" description: "Led a team of 1 to 7 developers managing 100+ data flows across 20+ business applications on Tibco BusinessWorks ESB for a 1,400-employee real estate group - capacity planning, Agile ceremonies, vendor negotiation, and ~370K EUR annual budget." locale: "en" canonical: "https://portfolio.josedacosta.info/en/achievements/engineering-manager-integration-entreprise" source: "https://portfolio.josedacosta.info/en/achievements/engineering-manager-integration-entreprise.md" html_source: "https://portfolio.josedacosta.info/en/achievements/engineering-manager-integration-entreprise" author: "José DA COSTA" date: "2019" type: "achievement" slug: "engineering-manager-integration-entreprise" tags: ["Tibco BusinessWorks 6", "SOFT Monitor", "ELK Stack", "MongoDB Atlas", "FTP/SFTP", "PGP", "GitLab CI", "PowerApps", "Jira", "Confluence"] generated_at: "2026-04-23T15:45:23.265Z" --- # Engineering Manager - Enterprise Integration Platform (alias ESB) Led a team of 1 to 7 developers managing 100+ data flows across 20+ business applications on Tibco BusinessWorks ESB for a 1,400-employee real estate group - capacity planning, Agile ceremonies, vendor negotiation, and ~370K EUR annual budget. **Date:** October 2023 - March 2024 **Duration:** ~6 months **Role:** Engineering Manager - Enterprise Integration **Technologies:** Tibco BusinessWorks 6, SOFT Monitor, ELK Stack, MongoDB Atlas, FTP/SFTP, PGP, GitLab CI, PowerApps, Jira, Confluence ### Key Metrics - Connected Systems: **-** - Business applications interconnected - Production Flows: **-** - Distinct technical data flows - Jira Tickets: **-** - Jira ESB workspace tickets - SOFT Monitor Alerts: **-** - Monitored and processed ## Presentation _Project definition and scope_ ### Domain Real estate (new construction, investment, rental, hospitality, student residences, commercial) - Enterprise middleware integration ### Target Users All Groupe Pichet departments: Finance, Accounting, Treasury, HR, Marketing, Real Estate Promotion, Rental, Hospitality, Security, IT (~1,400 employees) **Content:** The **Enterprise Integration Platform** (also known as ESB - Enterprise Service Bus) of Groupe Pichet was the **central nervous system of the entire information system**. Built on **Tibco BusinessWorks 6**, it orchestrated all data flows between 20+ business applications: accounting ERP, accounting software, treasury management, hotel PMS, real estate management software, CRM, PIM (Akeneo), DAM (Bynder), marketing automation (marketing platform), dematerialization platform, digital identity management (IGA), time tracking, HR system, fleet management software, and many others. As **Engineering Manager for Enterprise Integration**, I led a team of **1 to 7 developers** (internal staff and contractors from Square IT / RS2I). I created and facilitated all Agile ceremonies (Daily, Sprint Planning, Sprint Review, Sprint Retrospective), drove the ESB roadmap for 2022-2024, managed vendor relationships, and supervised all production flows. This role required interaction with **every department and business unit** of Groupe Pichet (~1,400 employees), as each data flow represented a critical business process. I interacted with **80 people on a daily basis** on entirely diverse subjects. **Domain:** Business Domain **Target Users:** Impacted Users **Functional Scope:** Integration Scope **Scope Accounting:** Accounting (ERP & accounting software) **Scope Treasury:** Treasury **Scope Hospitality:** Hospitality (PMS & channel manager) **Scope Real Estate:** Real estate management software **Scope Identity:** Identity & Access (IGA) **Scope Marketing:** Marketing (Akeneo/Bynder) **Scope H R:** HR (time tracking + HR system) **Scope Demat:** Dematerialization platform **Scope Fleet:** Fleet management software ## Objectives, Context, Stakes & Risks _Strategic vision and constraints_ ### Context Groupe Pichet is a **family-owned real estate group** headquartered in Pessac (Bordeaux metropolitan area), with approximately **1,400 employees**. Operating across new construction, investment, rental, hospitality, student residences, and commercial real estate, the group relied on a complex IT landscape with **20+ specialized applications** that needed to communicate seamlessly. The ESB platform had accumulated significant **technical debt**: instability on the TIBCO BW infrastructure was identified as a critical issue during the **IT transformation project** (the group's IT transformation program launched in 2022). The former ESB team lead (Jean-Francois) was departing, requiring a **complete knowledge transfer** of dozens of complex data flows. The monitoring system (SOFT Monitor) generated **2,377 alerts** that required systematic processing and triage. ### Stake Critical An ESB outage blocks accounting entries (ERP & accounting), student billing (PMS/treasury), CRM leads, pricing updates on websites, and identity management (IGA) - every flow failure has direct business impact ### Stake Complexity 100+ distinct technical flows, each with its own transformation rules, execution schedules, and recipients. Cross-cutting dependencies between 12+ business departments ### Stake Regulatory Financial flows (ERP & accounting software) are subject to strict accounting and regulatory constraints. Zero tolerance for data inconsistency in financial reporting ### Scope Growth & Team Ramp-Up The 2023 roadmap exercise showed the true scope: **903 days of work** estimated across the needs raised by 8 business IT teams, at a pace that kept accelerating (new flows for hotel PMS, treasury software, dematerialization platform, HR system...). **I led the team ramp-up from 2 to 5 FTEs** to absorb this demand. We then brought in **2 additional external consultants on a time & materials basis** to support us on more specific topics. Every new flow was qualified by complexity, estimated in days and arbitrated against competing demands to stay aligned with current capacity. - Drive the ESB roadmap 2022-2024 in collaboration with business units and IT leadership - Manage the middleware team (1 to 7 developers) with a complete Agile ritual - Guarantee availability of 100+ production flows (24/7 for accounting flows) - Integrate new flows requested by business units (hotel PMS, treasury software, financial software, dematerialization platform, HR system, internal business tool...) - Modernize infrastructure: evaluate iPaaS solutions (Middleway SAS, RS2I/TIBCO Cloud), implement CI/CD, replace SoftMonitor with ELK stack **Objectives:** Objectives **Context:** Context **Stakes:** Business Stakes **Stake Critical:** Critical Business Impact **Stake Complexity:** System Complexity **Stake Regulatory:** Regulatory Compliance **Risks:** Identified Risks **Risk1 Title:** Infrastructure Instability **Risk1 Desc:** TIBCO BW infrastructure experienced recurring instability episodes. the IT transformation program identified this as a priority issue: "too much instability on TIBCO BW infra, new platform desired: simpler, faster, less expensive". **Risk2 Title:** Knowledge Concentration **Risk2 Desc:** Critical ESB knowledge was concentrated in a single person (Jean-Francois). His departure required ~10 dedicated knowledge transfer sessions to avoid service disruption. **Risk3 Title:** Alert Fatigue **Risk3 Desc:** With 2,377 SOFT Monitor alerts in the mailbox, there was a real risk of alert fatigue - critical failures buried among routine notifications. **Risk4 Title:** Vendor Lock-in **Risk4 Desc:** Heavy dependency on Square IT for TMA (maintenance) and RS2I for TIBCO expertise. Contract negotiations and vendor management required constant attention. **Capacity Subtitle:** From 2 to 5 FTEs to absorb the rising demand **Capacity Costing Complexity:** Complexity **Capacity Costing Dev:** DEV (incl. TMA) **Capacity Costing Cp:** CP/PO (incl. UAT) **Capacity Costing Total:** Total consumed **Capacity Build Vs Run Note:** 44% Build / 56% Run - showing the weight of operational maintenance on the integration perimeter ## The Steps - What I Did _Chronological phases and personal contributions_ ### Technical Documentation Produced - [object Object] - [object Object] - [object Object] - [object Object] - [object Object] - [object Object] - [object Object] - [object Object] ### Prioritization Criteria **Business criticality**: Financial flows (ERP & accounting) and regulatory flows always took priority - zero tolerance for accounting inconsistencies. **Cross-dependencies**: Flows blocking other teams were escalated (e.g., IGA identity provisioning blocked security, HR, and fleet management). **Sprint allocation**: Simple flows (5 days) were batched together; complex flows (20 days) required a dedicated sprint. **Budget availability**: Some items were "retired from roadmap 2023" when the budget was not approved - these were flagged in orange in the Confluence roadmap. ### Communication of Postponements Every postponement followed a structured process: notification in COPROJ, formal entry in Jira with justification, and direct conversation with the department head. Transparency was key to maintaining trust - business stakeholders accepted delays when they understood the constraints and saw the prioritization logic. - Progressive Onboarding - Full Responsibility & Team Building - Engineering Manager - Full Agile **Phase1 Period:** 2019 - 2021 **Phase2 Period:** 2022 **Phase3 Period:** Oct 2023 - Mar 2024 **Doc Subtitle:** Complete documentation corpus following ITIL standards and Technical Direction requirements **Doc Total:** documents produced **Req Subtitle:** Collecting, qualifying, and prioritizing demands from 8 business teams **Req Summary:** From the 2023 roadmap: **84 flows requested** across 8 teams, **65 retained** for execution, **19 postponed** to align with the team ramp-up phasing. Each postponement required direct communication with the requesting department head and formal justification in COPROJ. **Scope Subtitle:** Active scope control under resource constraints **Scope Planned:** Planned Flows **Scope Retained:** Retained **Scope Postponed:** Postponed **Roadmap Subtitle:** Major workstreams managed across 3 years ## Actors & Interactions _Team, stakeholders, and collaboration dynamics_ ### Structured Onboarding Achraf L. joined the Daily in November 2023 and was operational on critical flows within weeks. The onboarding included paired work sessions with senior team members, progressive access to environments (DEV -> PREPROD -> PROD), and a dedicated Confluence onboarding guide covering each flow family. ### Cross-Company Pair Reviews We set up systematic code reviews pairing internal developers with Square IT and RS2I contractors. This bridged knowledge gaps and prevented silos from forming along company boundaries. Each flow modification required review from at least one person outside the author's company. ### Multi-Company Team Cohesion A team spanning 3 companies (Groupe Pichet internal, Square IT, ...) required explicit working agreements: shared Jira board, common Git branching strategy, unified definition of done, and daily standups where company affiliation was irrelevant. Everyone, one team. ### Mentoring & Growth I accompanied junior and intermediate profiles on TIBCO BW integration patterns, helped them understand the business context behind each flow, and encouraged them to present their work during Sprint Reviews to build their confidence and visibility. **Team Intro:** I contributed to the middleware starting 2021. The team fluctuated between **1 and 7 developers** depending on project phases and contractor availability. **Team Nuance:** The team composition posed unique challenges: mixing internal staff with contractors from different companies (Square IT) required careful coordination to maintain code quality, knowledge sharing, and team cohesion. I implemented pair reviews between internal and external developers to bridge knowledge gaps. **Stakeholders:** Key Stakeholders **Ceremonies:** Agile Ceremonies Established **Ceremony Header:** Ceremony **Frequency Header:** Frequency **Started Header:** Started ## Results - For Me, For the Company _Measurable outcomes and business impact_ ### Flow Costing from Scratch I built the first costing model for ESB flows. The inaugural estimate became the reference template for all subsequent flow estimates presented to business stakeholders and validated by IT leadership. ### Purchase Orders & OPEX **35 purchase orders** issued (Feb 2021 - May 2022) totaling **168K EUR** documented spend. Monthly infrastructure OPEX: **18K EUR/month** for Docker/Kubernetes hosting (216K EUR/year). ### Contract Negotiation - Akeneo PIM As manager, I negotiated a **3-year commitment** at renewal to lock in the rate against a 30% price hike, backed by a cost-benefit analysis vs alternative PIM solutions. ### Concrete Outputs Each workshop produced a **monitoring needs map** per department: which flows are critical, what SLAs are expected, who should be alerted, and what recovery procedures exist. These maps fed directly into the IT transformation roadmap and influenced investment decisions for 2023-2024. ### Strategic Value Running 8 workshops with every DSI team required speaking each department's language - financial terms with accounting, occupancy rates with hospitality, compliance vocabulary with security. This exercise was recognized by IT leadership as a model approach, later replicated for other transformation perimeters. ### Dora Mttr Mean time to recovery for critical flow incidents ### Dora Deploy New flow deployments to production ### Dora Fail Percentage of deploys requiring hotfix ### Dora Lead From business request to production deployment **For Me:** For Me - Personal Growth **Technical Skills:** Technical Skills Acquired **Domain Skills:** Domain & Management Skills **For Company:** For the Company - Business Impact **Delivered Features:** **Key deliverables during my leadership:** - **Hotel PMS integration** → enabled automated accounting entries for 4+ hotel properties, replacing manual data entry - **Treasury migration** (3 lots) → streamlined treasury operations with PGP-encrypted automated flows - **Invoice dematerialization platform** → automated invoice processing reducing manual handling by ~60% - **IGA identity management** → 7 connected systems (fleet management, time tracking, VAUBAN, HR system, TeamsRH, Intranet, internal business tool) ensuring consistent identity provisioning across the group - **IT transformation monitoring workshops** → 8 workshops mapping every department's monitoring needs, feeding into the IT transformation roadmap - **Structured knowledge transfer** → zero service disruption during both the predecessor's and my own departure **Helios Teams Audited:** Teams Audited **Dora Subtitle:** DORA (DevOps Research and Assessment) inspired metrics for the ESB platform (estimates based on project data) **Dora Mttr Label:** MTTR **Dora Deploy Label:** Deploy Frequency **Dora Fail Label:** Change Failure Rate **Dora Lead Label:** Lead Time **Dora Note:** Estimates based on Jira ticket analysis (932+ tickets) and SOFT Monitor alert patterns (2,377 alerts). Not measured with automated DORA tooling - derived from operational experience. ## Project Aftermath _What happened after my departure_ **Content:** ### Immediate Aftermath (March 2024) My departure was preceded by a **rigorous and structured knowledge transfer**: 10+ dedicated sessions covering every perimeter I managed - the complete ESB landscape, PIM, DAM, PSR, Ligneurs. Each session was documented in Confluence with step-by-step guides, flow diagrams, and escalation procedures. The team continued to operate with the Agile ceremonies I had established. Achraf L., who had joined the Daily in November 2023, was already onboarded on the key flows. Square IT contractors maintained the TMA (maintenance) contract. ### Medium Term The **IT transformation program** continued to address the infrastructure instability issues identified during my tenure. The iPaaS evaluations I initiated (Middleway SAS, RS2I/TIBCO Cloud) provided the groundwork for the modernization roadmap. The treasury migration I drove through Lots 1/2/3 was fully operational. ### Today The Groupe Pichet ESB platform remains **critical infrastructure** - the volume and complexity of data flows connecting 20+ applications make it irreplaceable in the short term. The architectural decisions made during my tenure (ELK monitoring, GitLab CI/CD, structured Jira workflows) continue to serve the team. The question of iPaaS migration remains relevant: the instability concerns flagged during the IT transformation program in 2022 ("too much instability on TIBCO BW infra, new platform desired") represent a long-term strategic decision that will shape the group's integration architecture for years to come. ## Critical Reflection _Honest retrospective on the project_ ### Key Figures **47 existing flows** to migrate to the new platform. Estimated effort: **186 days** (42 simple flows x 3 days + 5 complex flows x 12 days). The **Enioka consulting study** (51 pages) provided an independent assessment of the middleware landscape and migration options. Two solutions were evaluated in depth: **Middleway SAS** (French iPaaS vendor, September 2022) and **RS2I / TIBCO Cloud Integration** (October 2022). Both showed promise but the migration scope - rebuilding 47 flows while maintaining production continuity - made the business case difficult to defend against competing budget priorities. ### Ipaas Lessons The iPaaS evaluation taught me that **technical merit alone does not drive architectural decisions** in large organizations. Budget cycles, competing priorities, and organizational inertia all weigh heavily. If I were to redo this, I would have quantified the cost of TIBCO instability incidents in direct business terms (downtime hours x revenue impact) earlier in the process to build a more compelling ROI case. **Strengths:** What Went Well **Improvements:** What Could Be Improved **Would Do Differently:** What I Would Do Differently **Lessons:** Lasting Lessons **Ipaas Subtitle:** A structured evaluation that did not reach execution