Why amalgamation followed CDS modernization

I was Manager, IT Operations and Incident Response at TMX Group from February 2025 to October 2026. The mandate was L1 Monitoring and Major Incident Management, and infrastructure ownership sat outside that scope.

CDS Post Trade Modernization moved post-trade support from mainframe to open systems. Monitoring and major incident work could not stay split across two support groups that had grown up around different platforms.

Two support groups before the merge

When I joined, IT Operations was one team in name but split in practice. ComOps carried CDS work. Site2 Ops covered the rest of TMX.

One manager covered both groups, with one team lead for each. The team had 17 people in that two-lead shape. Each group had its own habits for severity language, escalations, and how incidents reached executives.

One monitoring and major incident team

After the platform migration I amalgamated the two groups into one monitoring and major incident team. The whole team cross-trained in incident management practice.

I also documented incident management across TMX businesses and subsidiaries, including Trayport, for all severity levels, and led ServiceNow Major Incident Management integration with Google Workspace automation that creates a Chat space and Meet bridge for each troubleshooting team. Those items sat on the same timeline as consolidation because post-modernization operations need one escalation picture, not two.

What seventeen to fourteen represented

Headcount moved to 14 people after amalgamation. That number reflects organizational consolidation after modernization: two support groups merged into one operating model for monitoring and major incident work.

I do not present the move from 17 to 14 as a personal cost-savings achievement or a productivity metric. I was accountable for making one team operate reliably, not for selling a finance story about the delta.

The difficult work was cultural and operational. Two paging habits had to become one severity language, one set of escalation expectations, and clear lanes for team leads once the org chart showed a single team.

Operating model after consolidation

The unified team ran through three team leads. After amalgamation a third lead was appointed specifically for incident management, on top of the day-to-day operations the leads already carried.

I kept escalations, executive communications, and team-lead development as manager accountabilities. I also served as Incident Lead for P1 and P2 incidents across TMX, excluding Trayport, while the process design covered Trayport and every other business at all severity levels.

I supported CDS modernization go-live and post-go-live operations during the mainframe-to-open-systems transition, and strengthened production change requirements for technical documentation, implementation evidence, procedural completeness, and accountable authorization within my assigned scope.

Record at TMX

My TMX position was impacted in a restructuring in October 2026. The amalgamation record stands on verified scope: one monitoring and major incident team after CDS Post Trade Modernization, consolidation from 17 to 14 people, and manager accountability for escalations and executive communications through three team leads.