- CSX²
Service systems are built around teams. The events that break them aren't.
CSX² is designed around events and services requests. Every related function stays connected. Every handoff is traceable.
Fast-track value to one unified service platform.
Months
to Weeks
Siloed tools
to One platform
SLAs and MTTR
to NPS and CSAT
CSX² is live in healthcare today.
The first deployment runs cross-functional service for a healthtech operator.
How CSX² works.
From ITSM
Your existing JSM operation is the foundation. CSX² extends the Jira Service Management you already run into ESM and CSM. Workflows stay intact. The platform expands to carry the events and service requests your current system drops. The Atlassian Service Collection, which includes the ESM and CSM capabilities CSX² runs on, comes free with every JSM subscription. There is nothing new to license.
BUILD PROPERTIES
- HR, Facilities, Legal, and Finance on the same JSM foundation
- Shared catalogs and shared governance
- Rovo agents tuned to your existing service context
Event & service request-centric design
Your events and service requests are the unit of design. CSX² starts from the things that cross functional boundaries. Workflows connect the right functions around a single traceable flow from intake to resolution.
WHAT EXPANSION LOOKS LIKE
- Ownership defined across every function from day one
- Evidence captured at each step
- Approvals built into the workflow, not managed outside it
AI done right
AI runs where trusted knowledge already exists. AI amplifies what is in your knowledge base. CSX² introduces Rovo in phases, starting where content is validated and processes are documented.
WHAT AI ADDS
- Rovo configured on governed workflows, not raw ticket history
- Phased rollout tied to knowledge base maturity
- Consistent answers, not confident wrong ones
Built for regulated environments.
Healthcare
In HealthTech, a service gap is a compliance event. A device incident or regulated workforce change can involve five functions at once. CSX² gives each a shared operational picture and a single traceable flow.
Manufacturing
In high-tech manufacturing, service events affect active programs. A workforce redeployment or access change during an NPI cycle can affect whether a DVT stays on track. CSX² treats those events and service requests as first-class service design problems.
28-campus institution
640,000 users. 28 teams. Live in 12 weeks.
A 28-campus institution unified IT, HR, and academic service operations on a single Atlassian Service Collection foundation.
640K
users
28
Teams
38%
lower licensing
12
weeks to live
$60K
annual savings
Day 0
Discovery Workshop with IT, operations, and HR leads.
Week 1
Rapid Deploy returned a working configuration with governance built in.
Week 6
Service teams validated workflows.
Month 3
Cutover complete. CSX² live across the operation.
Our service operation has never run cleaner. IT, HR, and academic teams ship through the same workflow now, and the governance posture survived the merge.
CIO
28-campus institution
Twelve hours.
A working configuration.
Walk us through your service operation. Trundl returns a scoped plan and timeline.
Format
Remote, on-site, or hybrid
Duration
12 hours, one or two days
Participants
Trundl architects + your IT/ops/compliance leads
You Receive
Current-state assessment, prioritized use case map, scope and timeline
Send your service tooling map ahead. Rapid Deploy comes ready to build.
Latest from Trundl.
The Case For Contextual Delivery whitepaper.
The definitive guide to Accelerated Contextual Delivery. Eight pages. Built for CIOs, CTOs, and VPs of platform strategy.
28-campus institution: service management without silos
How one institution unified service management across IT, HR, and academic operations.
The CSX Masters Community
Service operations leaders sharing how they unify service management across the business.