NH DoITEnterprise Lead
NH DHHSProgram Lead
Enterprise Service Bus Implementation
Version 1.0 - January 2026
Internal Planning
DHHS DIVISIONS:DMS (Medicaid Services)DES (Economic Stability)DCYF (Children, Youth & Families)DPHS (Public Health)DBH (Behavioral Health)DLTSS (Long-Term Support)

STATE OF NEW HAMPSHIRE

Conceptual Design Stage — Pending G&C Approval

DoIT

Enterprise Services Lead

DHHS

Program Requirements Lead

Future Program Sponsors (Phases 2-3):

DOT - Department of Transportation
• Operations (Highway/Bridge Maintenance)
• Project Development (Design/Construction)
• Aeronautics, Rail & Transit
• Finance
DOS - Department of Safety
• State Police
• Motor Vehicles
• Emergency Services & Communications
• Homeland Security & Emergency Mgmt

Additional agencies planned for ESB adoption post-DHHS implementation

Statewide Enterprise Service Bus
Implementation Plan

MuleSoft API-Led Connectivity Platform for NH Medicaid Enterprise System Modernization

DHHS Division Program Leadership:

DMS - Medicaid & MMIS
DES - Economic Stability
DCYF - Children & Families
DPHS - Public Health
DBH - Behavioral Health
DLTSS - Long-Term Support

MuleSoft Government Cloud

FedRAMP Moderate

Real-Time Integration

Replace 200+ SFTP

MITA Level 2 → 3.5

Current → Target

30+ APIs

Planned Deployment

Executive Summary

Comprehensive phased implementation plan for deploying a statewide Enterprise Service Bus leveraging MuleSoft Anypoint Platform as the foundation for NH DHHS integration modernization.

DDI Investment

$0.00M

Federal Share (90%)

$0.00M

State Share (10%)

$0.00M

DDI Timeline

0.00 Months

Phases

0 Phases

Target APIs

0+

Operations & Maintenance (Steady-State)

Peak Staffing (Ph 2)

0 FTE

8 State / 20 Contractor

Steady-State (Jan 2028+)

0 FTE

10 State / 7 Contractor

Annual O&M

$0.00M

75% FFP ($2.55M Fed / $0.85M State)

5-Year O&M Total

$0M

Fed: $12.75M / State: $4.25M

Strategic Objectives

  • Replace 200+ SFTP integrations with managed APIs
  • Enable real-time data exchange across MMIS
  • Automate CMS-64, T-MSIS, OCSE-34/157 reporting
  • Achieve MITA Level 3.5 by Q4 2031
  • Onboard DOT & DOS divisions in Phase 3+
  • Establish enterprise API governance framework

Implementation Timeline

22.5-month DDI roadmap (Feb 2026 - Dec 2027) with 6-month incremental milestones aligned to budget cycles

Feb 2026Jun 2026Dec 2026Jun 2027Dec 2027

Phase Details

Detailed breakdown of objectives, activities, and success criteria

Phase 0: Foundation

Feb 1 - Jun 15, 2026 (4.5 months)

Objectives

  • CMS IAPD approval & G&C contracting
  • Deploy MuleSoft Government Cloud (FedRAMP Moderate)
  • Establish connectivity to Conduent ORR ecosystem
  • Create foundational API endpoints (3-5 System APIs)
  • ITSM/ServiceNow foundation setup

Key Activities

  • Execute SI procurement process (GraniteBus partner selection)
  • Provision MuleSoft Anypoint Platform with Runtime Fabric (RTF)
  • Deploy Runtime Fabric agents in NH DHHS data center
  • Configure Anypoint MQ for asynchronous messaging
  • Build DevOps CI/CD pipeline with automated testing
  • Establish ODBC connections to MMIS ORR, NHORR, PBM ORR
  • Deploy object stores for report caching (freshness scoring)
  • Implement TLS 1.3 encryption and API governance policies

Success Criteria

  • CMS IAPD and G&C approvals secured
  • SI partner contract executed
  • MuleSoft Government Cloud operational with FedRAMP compliance
  • 3-5 System APIs deployed with >99% availability
  • ServiceNow integration established for incident management

Phase Budget

Total

$1.81M

Federal (90%)

$1.63M

State (10%)

$181K

Staffing

16 FTE (4 State / 12 Contractor)

Investment Analysis

22.5-month DDI (Feb 2026 - Dec 2027) with 6-month incremental milestones aligned to budget cycles

Includes 15% DDI contingency and 10% M&O reserve for market volatility

$12.75M

DDI Investment

90% FFP Rate

$17.0M

5-Year M&O

17 FTE (10 State / 7 Cont.)

$29.75M

Total Program

FY2026-2032

$24.23M

Federal Share

81% FFP blended

$5.53M

State Share

19% state match

DDI Phase (90% FFP): $12.75M

Federal (90%)

$11.48M

State (10%)

$1.28M

5-Year M&O (75% FFP): $17.0M

Federal (75%)

$12.75M

State (25%)

$4.25M

DDI Budget by Phase ($M) - 6-Month Increments

Phase 0

$1.81M | 16 FTE

4.5 months

Phase 1

$3.60M | 24 FTE

6 months

Phase 2

$4.20M | 28 FTE

6 mo (Peak)

Phase 3

$3.14M | 22 FTE

6 months

Conservative ROI Analysis (40% Benefit Realization Factor)

6-Year Investment

$29.75M

Was $10.2M

Annual Benefits

$32.2M

Was $88.9M

Benefit-Cost Ratio

3.2:1

Was 18.2:1

Payback Period

3.5 yrs

Was 1.2 yrs

*Even with conservative estimates, program delivers positive ROI with NPV of $48.2M (7% discount rate)

Key Risk Factors Applied to Estimates

Talent Risk

+25%

MuleSoft specialists scarce; market premium for architects

Vendor Risk

+15%

SI partner negotiations; Conduent coordination overhead

Timeline Risk

+6 mo

CMS IAPD approval; G&C procurement cycles extended

Integration Risk

+20%

Legacy ORR complexity; 200+ SFTP connections to migrate

Integration Architecture

NH DHHS Enterprise Integration Architecture Overview

MMIS Architecture Diagram
MMIS Services Layer
FedRAMP-Aligned Medicaid Enterprise Data and Integration Platform showing consuming agencies, enterprise data analytics layer with Informatica Cloud, enterprise integration and API fabric with MuleSoft ESB, and operational source systems

Risk Dashboard

Enterprise-level risk assessment and mitigation strategies

1

Critical Risk

3

High Risk

3

Medium Risk

1

Low Risk

Technical Risks

Legacy integration complexity

High
Prob:MediumImpact:High

Mitigation: Detailed discovery POC; maintain SFTP fallback

Integration performance

High
Prob:MediumImpact:High

Mitigation: Performance testing early; horizontal scaling

Organizational Risks

Staff capacity constraints

Medium
Prob:MediumImpact:Medium

Mitigation: Hybrid staffing model; phased implementation

Change resistance

Medium
Prob:MediumImpact:Medium

Mitigation: Training, GraniteBus partnership, change management

Vendor Risks

Conduent data access delays

High
Prob:MediumImpact:High

Mitigation: Early contractual engagement; escalation path

Vendor lock-in

Low
Prob:LowImpact:Medium

Mitigation: Open standards; knowledge transfer

Regulatory Risks

CMS IAPD approval

Critical
Prob:HighImpact:High

Mitigation: Early State Officer engagement; pre-submission review

Security accreditation delays

Medium
Prob:LowImpact:High

Mitigation: Early DoIT security engagement; FedRAMP artifacts

Governance Framework

Enterprise-level governance structure for multi-agency integration

Project Governance Structure

Enterprise Services Planning

Multi-Agency Portfolio Planning Committee

DHHS PortfolioDoIT ArchitectureDOS PlanningDOT PlanningBRMD IT Mgmt

Project Governance Board

DHHS IT Director | DHHS PMO | DoIT Project Lead | GraniteBus | Conduent Liaison

Technical Council

Architecture | Security | Standards

Data Governance

Data Quality | Privacy | Stewardship

Change Advisory

Release Mgmt | Change Control | Risk

API Governance Standards

StandardSpecificationEnforcement
API DesignRESTful, OpenAPI 3.0API Review Board approval
SecurityOAuth 2.0, TLS 1.3, AES-256Security scan before deployment
Performance<250ms p95, >99.9% availabilityAutomated monitoring
DocumentationRAML 1.0, inline examplesCoverage metrics
VersioningSemantic versioningVersion lifecycle management

NH DHHS / DoIT | Document Version 1.0 | January 2026

This document was prepared in support of the NH DHHS MMIS Integration Modernization initiative

Staffing Plan

Phased staffing approach from POC through steady-state operations

Phase 0 Team (Feb 1 - Jun 15, 2026)

4.00 State FTE
12.00 Contractor FTE
16.00 Total FTE
RoleFTETypeResponsibilities
Program Manager1State (DHHS)IAPD/G&C oversight, CMS liaison, stakeholder mgmt
Technical Lead / EA1State (DoIT)EA standards, API governance, MITA roadmap
Senior Business Analyst1State (DHHS)Requirements, T-MSIS/CMS-64 mapping
Security & Compliance1State (DoIT)FedRAMP review, HIPAA compliance, ATO
SI Project Manager1ContractorSI delivery mgmt, project coordination
MuleSoft Solution Architect1ContractorPlatform architecture, API-led design
Senior MuleSoft Developer2ContractorSystem/Process API development
MuleSoft Developer2ContractorAPI components, DataWeave transforms
Data Integration Engineer1ContractorODBC/ORR connectivity, schema mapping
DevOps Engineer1ContractorCI/CD pipelines, RTF deployment
Informatica Developer1ContractorETL workflows, EBI connectivity
QA/Test Engineer1ContractorTest strategy, MUnit/automation
Technical BA1ContractorRAML specs, integration flows
Training/Change Mgmt0.5ContractorTraining curriculum, runbooks
Medicaid/T-MSIS SME0.5ContractorT-MSIS compliance, CMS-64 advisory

Staffing Ramp-Up Timeline

Phase 0 (Feb-Jun 2026)

Foundation: IAPD, G&C, SI procurement, platform setup

State
4
Contractor
12
Total
16

Phase 1 (Jun-Dec 2026)

Core Integration: CMS-64, T-MSIS, eligibility APIs

State
6
Contractor
18
Total
24

Phase 2 (Dec 2026-Jun 2027)

MMIS Expansion: EBI 2.0, PBM, provider portal (Peak)

State
8
Contractor
20
Total
28

Phase 3 (Jun-Dec 2027)

Enterprise & Transition: SFTP retirement, DOT/DOS

State
10
Contractor
12
Total
22

Steady-State (Jan 2028+)

Operations & Maintenance: 17 FTE sustainable model

State
10
Contractor
7
Total
17

Risk-Adjusted Staffing Strategy (IAPD Baseline)

  • • 60-month implementation timeline with 25% talent risk buffer
  • • Phase 0 includes extended G&C approval period and SI procurement
  • • Peak staffing (29.5 FTE) during Phase 1 for core development
  • • Gradual knowledge transfer with State FTE ramp from 6 → 10
  • • Steady-state maintains 10 State + 7 Contractor = 17 FTE
  • • Annual O&M: $3.4M (75% FFP = $2.55M Fed / $0.85M State)
  • • HIGH RISK roles: Integration Architects, DevOps Engineers (25% premium)
Sustainability Plan

Platform Sustainability Overview

Long-term operations & governance framework ensuring continuous platform viability, fiscal responsibility, and alignment with Enterprise Architecture standards.

EA Governance

DoIT Enterprise Lead

Architecture standards & oversight

Steady-State Team

17 FTE

10 State / 7 Contractor

Annual O&M Cost

$3.4M

Risk-adjusted (17 FTE)

Federal Funding

75% FFP

$2.55M Fed / $0.85M State

Platform SLA

99.9%

Availability target

5-Year O&M Total

$17.0M

Fed: $12.75M / State: $4.25M

DoIT Role — Enterprise Services Lead

  • Platform governance and architectural standards
  • Technology strategy and vendor relationship management
  • Security and compliance oversight
  • Cross-agency integration coordination
  • Infrastructure and hosting decisions

DHHS Role — Program Requirements Lead

  • Business requirements and use case prioritization
  • Division-specific integration needs (DMS, DES, DCYF, DPHS, DBH, DLTSS)
  • Federal reporting compliance (CMS, OCSE, ACF)
  • Program-level funding and cost allocation
  • User acceptance and change management

Plan Scope

1

Enterprise Architecture governance and decision-making processes

2

Resource models for development, implementation, and steady-state operations

3

Vendor engagement and contract management strategies

4

Ongoing support and maintenance (O&M) framework

5

Financial sustainability and cost allocation across DHHS divisions

6

Risk management, succession planning, and vendor exit strategies

7

Performance metrics and continuous improvement KPIs

EA Governance

Governance Framework

Enterprise Architecture governance structure ensuring consistent decision-making, standards compliance, and effective change management.

Executive Steering Committee

Quarterly

Members: DoIT Commissioner (Chair), DHHS Commissioner, CFO Representatives

Scope: Strategic Direction, Major Investments

Project Governance Board

Monthly

Members: DoIT Deputy CIO, DHHS CIO, Division Directors (DMS, DES, DCYF)

Scope: Project Oversight, Resource Allocation

Technical Council

Bi-weekly

Members: DoIT Enterprise Architects

Scope: Architecture Reviews, Standards Compliance

Data Governance Council

Monthly

Members: DHHS Data Stewards

Scope: Data Quality, Privacy, Access Control

Change Advisory Board (CAB)

Weekly

Members: Operations Lead, Technical Leads

Scope: Change Approvals, Release Planning

Staffing

Resource Model

Staffing requirements for development, implementation, and steady-state operations with recommended State/Contractor resource allocation.

Development Team (Phases 0-2)

RoleFTETypeResponsibilities
Program Manager1
State (DHHS)
Overall program coordination, stakeholder management
Project Manager1
Contractor
Day-to-day project execution, schedule management
Enterprise Architect1
State (DoIT)
Architecture governance, standards compliance
Integration Architect2
Contractor
MuleSoft design, API patterns (HIGH RISK: scarce)
Senior API Developer4
Contractor
API development, DataWeave (25% market premium)
API Developer6
Contractor
API development, unit testing
Business Analyst2
State (DHHS)
Requirements gathering, business process mapping
Data Analyst2
Contractor
Data mapping, ETL specifications
QA Lead1
Contractor
Test strategy, automation framework
QA Analyst3
Contractor
Test execution, defect management
DevOps Engineer2
Contractor
CI/CD pipeline (HIGH RISK: MuleSoft+DevOps rare)
Security Analyst1
State (DoIT)
Security reviews, compliance validation
Technical Writer1
Contractor
Documentation, API specifications
ServiceNow Developer1
Contractor
ITSM integration, CMDB
Operations Analyst1
Contractor
Monitoring, alerting setup
Conduent Liaison0.5
State (DHHS)
ORR coordination, test env access
TOTAL DDI29.55.5 State / 15.5 Contractor

Resource Mix (26% / 74%)

State Resources: Governance, oversight, institutional knowledge

Contractor Resources: MuleSoft expertise, scalable capacity

Vendor Strategy

Vendor Engagement Strategy

Strategic partnerships and contract structures for MuleSoft, Conduent, and Systems Integrator vendor management.

MuleSoft Premier Support + Professional Services

ComponentDescriptionCost
Anypoint Platform LicenseGovernment Cloud, Runtime Fabric$350,000/year
Premier Support24x7 support, 1-hour P1 responseIncluded
Professional Services200 hours advisory services$60,000/year
Training CreditsAnnual certification/enablement$15,000/year
TOTAL MULESOFT ANNUAL$425,000/year

MuleSoft Engagement Model

Quarterly Business Reviews (QBR)

Strategic alignment with MuleSoft Customer Success

Annual Architecture Review

Deep-dive with MuleSoft Solutions Architect

Beta Features Access

Priority access to roadmap briefings and new features

Named Technical Account Manager

Dedicated TAM for escalation and guidance

O&M

Ongoing Support & Maintenance

Tiered operational support model, incident management, API lifecycle, and platform monitoring framework.

Tier 1: Service Desk

Staffing

State + Contractor

Response

<30 min

Hours: 7am-7pm ET M-F

Responsibilities:

  • First contact resolution (password resets, basic inquiries)
  • Ticket triage and categorization
  • Known issue lookup and workaround guidance

Tier 2: Application Support

Staffing

Contractor

Response

<2 hours

Hours: 7am-7pm ET M-F

Responsibilities:

  • API troubleshooting and debugging
  • Configuration changes and minor fixes
  • Performance investigation
  • Integration issue diagnosis

Tier 3: Engineering Support

Staffing

Contractor + MuleSoft

Response

<1 hour (P1)

Hours: 24x7 on-call

Responsibilities:

  • Complex defect resolution
  • Platform issues (MuleSoft escalation)
  • Architecture changes
  • Emergency hotfixes
Financial Planning

Financial Sustainability

Annual O&M cost projections, federal funding sustainability, and cost allocation model across DHHS divisions.

$16.37M

5-Year O&M Total

$12.28M

Federal Share (75%)

$4.09M

State Share (25%)

$3.1M

Year 1 Annual Cost

Annual O&M Cost Breakdown

Year 1 Cost Categories

5-Year Cost Detail

Cost CategoryYear 1Year 2Year 3Year 4Year 5
MuleSoft Platform$485,000$500,000$515,000$530,000$546,000
Contractor Staff (5.5 FTE)$980,000$1,010,000$1,040,000$1,071,000$1,103,000
State Staff (2.5 FTE)$1,150,000$1,185,000$1,220,000$1,257,000$1,295,000
Infrastructure/Hosting$85,000$88,000$91,000$94,000$97,000
Training/Certifications$60,000$40,000$40,000$40,000$40,000
Contingency (10%)$340,000$350,000$361,000$372,000$383,000
TOTAL ANNUAL O&M$3,100,000$3,173,000$3,267,000$3,364,000$3,464,000
Risk Management

Sustainability Risk Management

Risk identification, succession planning, vendor dependency management, and exit strategies for long-term platform sustainability.

Sustainability Risks & Mitigations

RiskCategoryProbabilityImpactMitigation Strategy
Federal funding reduction
Financial
Medium
High
Diversify funding (grants, cross-agency), maintain state contingency fund
Key personnel turnover
Organizational
High
Medium
Cross-training, documentation, competitive compensation
Vendor dependency (MuleSoft)
Vendor
Low
High
Maintain API portability standards, exit strategy documentation
Technology obsolescence
Technical
Medium
Medium
Annual technology reviews, roadmap alignment with vendor
Contractor transition
Vendor
Medium
Medium
Knowledge transfer requirements, transition period overlap
CMS compliance changes
Regulatory
Medium
High
Active participation in CMS workgroups, early adopter programs
Security breach
Security
Low
Critical
Continuous monitoring, incident response plan, cyber insurance
Performance degradation
Technical
Medium
Medium
Proactive capacity planning, performance baselines

4

High/Critical Impact

5

Medium Probability

2

Low Probability

8

Total Risks Identified

Maturity Planning

MITA 3.0 target progression from Level 2 to Level 3.5 maturity

Target Maturity Matrix by Business Area

Business AreaBaseline (2025)Phase 1-2 (2027)Phase 3 (2029)Phase 4 (2031)
Member Management22.533.5
Provider Management22.533.5
Operations Management22.533.5
Plan Management2233.5
Financial Management22.533.5

Maturity Level Progression

Level 1Level 2Level 2.5Level 3Level 3.5Level 4
Current (L2)Target (L3.5)

Phase 1

  • API Gateway deployment
  • OpenAPI specifications
  • Canonical data models

Phase 2

  • SOA-based federal reporting
  • Real-time eligibility services
  • Event-driven architecture

Phase 3

  • Modular MES components
  • Advanced analytics APIs
  • Cross-program integration

Phase 4

  • MDM for unified records
  • AI/ML services
  • Zero-trust security
ITSM & Operations

IT Service Management Integration

ServiceNow integration and ITIL process alignment for enterprise service delivery

ServiceNow Enterprise Instance

Primary ITSM Platform — DoIT Managed

8
Modules Integrated
4
Phase 0 Priority
API
Bi-directional Sync
24/7
Event Monitoring

ServiceNow Module Integration

Incident Management

Phase 0

API-driven incident creation from monitoring alerts

Change Management

Phase 0

Automated RFC creation for API deployments

Problem Management

Phase 1

Root cause analysis workflows, KEDB population

Service Catalog

Phase 1

ESB service offerings, API subscription requests

CMDB

Phase 0

Auto-discovery of APIs, connections, dependencies

SLA Management

Phase 1

SLA monitoring dashboards, breach notifications

Knowledge Management

Phase 0

Runbooks, troubleshooting guides, API docs

Event Management

Phase 1

Alert correlation, noise reduction, automation

Incident Management Workflow

Alert Detection
Auto-Ticket
Tier 1 Triage
Tier 2 Analysis
Resolution

SLA Targets by Priority

P1
Critical
Response: 15 min | Resolution: 4 hr
P2
High
Response: 30 min | Resolution: 8 hr
P3
Medium
Response: 2 hr | Resolution: 24 hr
P4
Low
Response: 8 hr | Resolution: 72 hr
P1 Critical Triggers
  • • Federal reporting API failure (CMS-64, TMSIS, OCSE)
  • • Eligibility determination system unavailable
  • • Claims processing halted
  • • Security breach or data exposure

Change Management Process

Change Categories

Standard
Auto-approved via CI/CD
24 hours
Normal
CAB Review
5 business days
Emergency
Emergency CAB (ECAB)
4 hours
Major
Full CAB + Executive
15 business days

Change Advisory Board (CAB)

CAB ChairDoIT Service Management
Technical LeadGraniteBus/ESB Team
Business RepDHHS Program
Security RepDoIT Security

CI/CD Pipeline Change Integration

RFC Creation
Auto-create ServiceNow Change
Approval Gate
Wait for CAB (if non-standard)
Deploy
Execute Anypoint Deployment
Health Check
Validate deployment success
Close RFC
Update with results
Configuration Management

ADDM & CMDB Management

Application Dependency Discovery Management and Configuration Management Database design

ADDM Discovery Architecture

CMDB (ServiceNow)

Business Services
Technical Services
Application CIs
Infrastructure CIs
Automated Population

ServiceNow Discovery

Infrastructure Scan
Network Discovery
Storage & Compute

MuleSoft Visualizer

API Discovery
Dependency Mapping
Connector Inventory

NH DHHS Data Center

Mule Runtime
Flex Gateway
Databases

Conduent/Vendor Environments

MMIS ORR
PBM
Provider Systems

Discovery Tool Selection

ServiceNow Discovery

Infrastructure CI discovery

Phase 0
Integration: Native CMDB

MuleSoft Visualizer

API topology & dependencies

Phase 0
Integration: Anypoint Platform

AppDynamics/Datadog

APM & dependencies

Phase 1
Integration: APM Integration

Informatica Axon

Data lineage & catalog

Phase 2
Integration: EBI 2.0

ESB Configuration Item Classes

ESB:API

Published API endpoint

Name, version, status, owner, SLA

ESB:Integration

Point-to-point connection

Source, target, protocol, schedule

ESB:Connector

MuleSoft connector instance

Type, version, configuration

ESB:Runtime

Mule runtime instance

Version, cluster, capacity

ESB:Gateway

Flex Gateway instance

Policies, certificates

ESB:DataSource

External data connection

Type, host, database, schema

ESB:Consumer

API consumer application

App name, owner, usage tier

CI Relationship Model

Business Service
Medicaid Eligibility
Supported By
ESB:API
xapi-eligibility
Depends On
ESB:API
sapi-mmis
Hosted On
ESB:Runtime
mule-prod
Consumes
ESB:DataSource
MMIS ORR

Dependency Impact Analysis Matrix

Failed ComponentImmediate ImpactCascading ImpactPriority
Mule RuntimeAll hosted APIsAll consumers, federal reporting
P1
MMIS ORR ConnectionClaims APIs, eligibilityCMS-64, TMSIS, payments
P1
Flex GatewayExternal API accessProvider portal, MCO
P1
NHORR ConnectionEligibility APIsSNAP-Medicaid sync
P1
Informatica ETLBatch processingEBI feeds, reports
P2
Reference DataCode lookupsAll API validations
P2
Operations Support

Support Tier Structure

Multi-tiered support model for sustainable ESB operations

Tier 0

Self-Service

24/7

Scope

  • API Developer Portal (docs, sandbox)
  • Knowledge Base (FAQs, guides)
  • Status Dashboard (real-time health)
  • Automated Alerts (subscriptions)

Target

Resolve 60% without human contact

Escalation
Tier 1

Service Desk

7 AM - 6 PM ET (M-F)

Scope

  • Initial triage
  • Password resets
  • Access requests
  • Basic diagnostics

Target

Resolve 40%, route remainder <15 min

Escalation
Tier 2

ESB Application Support

7 AM - 7 PM ET, 24/7 P1/P2

Scope

  • API troubleshooting
  • Configuration changes
  • Performance tuning
  • Integration issues

Target

Resolve 50% escalated, >95% SLA

Escalation
Tier 3

Engineering & Vendor

Business hours, 24/7 P1

Scope

  • Complex bugs
  • Platform issues
  • Architecture decisions
  • MuleSoft Premier Support

Target

Root cause analysis, permanent fixes

Escalation
Tier 4

Executive Escalation

As needed

Scope

  • P1 >4hr unresolved
  • P2 >12hr unresolved
  • Business-critical impact
  • Resource mobilization

Target

Vendor escalation, executive action

Steady-State Operations Team

8.5 FTE
Total Operations Staff
4 State
4.5 Contractor
1
ESB Operations Manager
1
Sr. Integration Engineer
2
Integration Engineer
2
Business Analyst
1
Support Lead
2
Support Analyst
1
Security Analyst
1
Sr. API Developer
2
API Developer/Support
2
Application Support
1
DevOps Engineer
1
QA Analyst

On-Call Rotation Schedule

Week 1
Primary
Integration Engineer A
Secondary
DevOps Engineer
Escalation
Sr. Engineer
Week 2
Primary
Integration Engineer B
Secondary
Platform Admin
Escalation
Sr. Engineer
Week 3
Primary
Integration Analyst A
Secondary
Integration Engineer A
Escalation
Ops Manager
Week 4
Primary
Integration Analyst B
Secondary
Integration Engineer B
Escalation
Ops Manager

On-Call Compensation

After-hours:$150/shift
Weekend:$250/day
Holiday:$400/day
Incident work:1.5x rate
Observability

Monitoring & Alerting

Comprehensive observability stack with automated alerting and runbook library

Monitoring Stack

Anypoint Monitoring

API Performance
Metrics: Response time, throughput, errors
Retention: 30 days / 1 year

Datadog/New Relic

Infrastructure
Metrics: CPU, memory, disk, network
Retention: 30 days

Splunk

Logs
Metrics: Application logs, audit logs
Retention: 90 days / 7 years

PagerDuty

Alerting
Metrics: Incident notification, escalation
Retention: N/A

Grafana

Dashboards
Metrics: Operational dashboards
Retention: N/A

Functional Monitoring

Synthetic
Metrics: API health checks
Retention: 30 days

Alert Thresholds

API Response Time (p95)
>500ms
🛑 >1000ms

Investigate, scale if needed

API Error Rate
>1%
🛑 >5%

Investigate root cause

API Availability
<99.5%
🛑 <99%

Immediate investigation

CPU Utilization
>70%
🛑 >85%

Scale or optimize

Memory Utilization
>75%
🛑 >90%

Scale or investigate leak

Queue Depth
>1000
🛑 >5000

Scale consumers

Certificate Expiry
<30 days
🛑 <7 days

Renew certificate

Connector Health
Degraded
🛑 Failed

Restart/failover

PagerDuty Alert Routing

P1 Critical
severity == critical
1Page primary (immediate)
2Page secondary (+5 min)
3Manager (+15 min)
4Director (+30 min)
Auto-resolve: Never
P2 High
severity == high
1Page primary
2Escalate secondary (+30 min)
Auto-resolve: 4 hours
P3 Medium
severity == medium
1Create ticket
2Notify queue
Auto-resolve: 24 hours
P4 Low
severity == low
1Create ticket only
Auto-resolve: 72 hours

Runbook Library
108 Total

Incident Response

15

P1 response, escalation, war room

API Operations

25

Deployment, rollback, scaling

Platform Admin

20

User mgmt, certs, upgrades

Integration Troubleshooting

30

Connector issues, data sync

Federal Reporting

10

CMS-64, TMSIS validation

Disaster Recovery

8

Failover, restore, continuity

# RUNBOOK: RB-INC-001 - P1 Critical Incident Response
TRIGGER: P1 alert or reported critical outage
IMMEDIATE (0-15 min):
☐ Acknowledge PagerDuty alert
☐ Join incident bridge (Teams: ESB-Incident-Bridge)
☐ Verify incident scope and impact
☐ Check recent changes (ServiceNow)
ESCALATION CONTACTS:
• MuleSoft Premier: 1-888-XXX-XXXX
• DoIT NOC: 603-XXX-XXXX
Service Management

Ticketing & SLA Management

ServiceNow ticketing configuration and performance metrics

Key Performance Indicators

First Contact Resolution
42%
Target: 40%
Avg Handle Time
12min
Target: 15min
Customer Satisfaction
4.3/5
Target: 4.2/5
Ticket Backlog
38tickets
Target: 50tickets
MTTR (P1)
1.8hr
Target: 2hr
MTTR (P2)
5.2hr
Target: 6hr
Change Success Rate
98.5%
Target: 98%
Platform Availability
99.92%
Target: 99.9%

SLA Performance

P1
Response: 15 min|Resolution: 4 hr
99.2%
0%Target: 99%100%
P2
Response: 30 min|Resolution: 8 hr
97.5%
0%Target: 95%100%
P3
Response: 2 hr|Resolution: 24 hr
94.8%
0%Target: 95%100%
P4
Response: 8 hr|Resolution: 72 hr
98.1%
0%Target: 95%100%

Ticket Volume Trend

Created
Resolved

ServiceNow Assignment Groups

ESB-Tier1-Triage

Initial ticket receipt

Members: Service Desk agents
Auto-route: All ESB-tagged tickets
ESB-Tier2-Support

Application support

Members: ESB Support Engineers
Auto-route: API/integration issues
ESB-Tier3-Engineering

Complex issues

Members: ESB Architects
Auto-route: Escalated from Tier 2
ESB-Platform-Admin

Platform issues

Members: MuleSoft Admins
Auto-route: Platform alerts, capacity
ESB-DevOps

Deployment issues

Members: DevOps Engineers
Auto-route: CI/CD, automation
ESB-Security

Security incidents

Members: Security team
Auto-route: Security-related tickets

Ticket Category Distribution

API Access
35
API Issues
28
Integration Issues
22
Platform Issues
8
Change Requests
15

SLA Breach Escalation Matrix

Response SLA Breach

Immediate
Notify engineer + backup
+15 min
Notify Ops Manager
+30 min
Notify Service Mgmt

Resolution SLA at 50%

P1/P2
Escalate Tier 3, notify mgr
P3/P4
Send reminder to assignee

Resolution SLA Breach

P1
Incident report, exec review
P2
Manager review, improvement
P3/P4
Weekly ops meeting review
CMS SMC Alignment
CMS MES Repository

CMS Outcomes & Metrics Crosswalk

Comprehensive mapping of GraniteBus ESB capabilities to CMS Streamlined Modular Certification (SMC) required outcomes across all 16 MES modules.

MES Modules
16
Mapped to GraniteBus
CMS Outcomes
74
59 High Alignment
Avg. Alignment Score
90%
Across all modules
Phase 1 Priority
10
Modules in initial rollout

MES Module Alignment Heatmap

Click any module to view detailed outcome mappings

1115
85%
AVS
90%
CP
92%
DSSDW
88%
EVV
94%
EE
95%
EPS
90%
FM
87%
HIE
93%
LTSS
86%
MM
91%
PBM
89%
PDMP
88%
PI
91%
PM
92%
TPL
90%
High Alignment (90%+)
Medium Alignment (80-89%)
Low Alignment (<80%)
CMS MES Certification Reference:

This crosswalk maps GraniteBus ESB capabilities to CMS-Required Outcomes as defined in the MES Certification Repository. Alignment scores indicate the degree to which GraniteBus integration capabilities support the achievement of each CMS outcome. State-specific outcomes will be proposed in the IAPD to address NH-specific program needs.

Phase 0: Foundation

Job Descriptions & Work Breakdown Structure

Detailed role definitions, responsibilities, qualifications, and cost allocation for the 16 FTE Phase 0 team (Months 1-10).

State FTE
4
DHHS & DoIT positions
Contractor FTE
12
SI partner resources
Duration
10
Months (Q3 2026 - Q1 2027)
WBS Tasks
14
Work packages defined

State Positions (4 FTE)

Program Manager

Administrator III1 FTE

1240 hrs

Technical Lead / Enterprise Architect

IT Manager II1 FTE

1000 hrs

Senior Business Analyst

Program Specialist IV1 FTE

1040 hrs

Security & Compliance Analyst

IT Security Specialist1 FTE

1000 hrs

Contractor Positions (12 FTE)

SI Project Manager

Senior Consultant1 FTE

1280 hrs

MuleSoft Solution Architect

Principal Consultant1 FTE

1120 hrs

Senior MuleSoft Developer

Senior Consultant2 FTE

1840 hrs

MuleSoft Developer

Consultant2 FTE

1880 hrs

Data Integration Engineer

Senior Consultant1 FTE

1040 hrs

DevOps Engineer

Senior Consultant1 FTE

1080 hrs

Informatica Developer

Senior Consultant1 FTE

1040 hrs

QA/Test Engineer

Senior Consultant1 FTE

1080 hrs

Technical Business Analyst

Consultant1 FTE

1040 hrs

Training & Change Management Specialist

Consultant0.5 FTE

720 hrs

Medicaid/T-MSIS Subject Matter Expert

Principal Consultant0.5 FTE

560 hrs
Phase 0: Detailed Table View

Job Descriptions Table & Export

Comprehensive tabular view of all Phase 0 positions with filtering, sorting, and Excel export capabilities.

Filter:
Total FTE
16.0
Showing 15 roles
Total Hours
16,960
WBS hours
Duration
10 Months
Phase 0 timeline

Phase 0 Roles Summary Table

Click column headers to sort. All data exportable to Excel.

ID
Title
FTE
TypeClassification
Duration
WBS Hrs
DEV-01Senior MuleSoft Developer
2
Contractor
Senior Consultant4.5mo1,840
DEV-02MuleSoft Developer
2
Contractor
Consultant4.5mo1,880
ARCH-01MuleSoft Solution Architect
1
Contractor
Principal Consultant4.5mo1,120
SI-PMSI Project Manager
1
Contractor
Senior Consultant4.5mo1,280
DEVOPS-01DevOps Engineer
1
Contractor
Senior Consultant4.5mo1,080
DATA-01Data Integration Engineer
1
Contractor
Senior Consultant4.5mo1,040
INF-01Informatica Developer
1
Contractor
Senior Consultant4.5mo1,040
QA-01QA/Test Engineer
1
Contractor
Senior Consultant4.5mo1,080
BA-02Technical Business Analyst
1
Contractor
Consultant4.5mo1,040
SME-01Medicaid/T-MSIS Subject Matter Expert
0.5
Contractor
Principal Consultant4.5mo560
TL-01Technical Lead / Enterprise Architect
1
State
IT Manager II4.5mo1,000
PM-01Program Manager
1
State
Administrator III4.5mo1,240
TRAIN-01Training & Change Management Specialist
0.5
Contractor
Consultant4.5mo720
SEC-01Security & Compliance Analyst
1
State
IT Security Specialist4.5mo1,000
BA-01Senior Business Analyst
1
State
Program Specialist IV4.5mo1,040
TOTALS16.016,960
Excel Export (3 Sheets):
  • Summary: All roles with key metrics
  • Detailed: Full job descriptions
  • Cost Breakdown: Budget allocation
PDF Report (Multi-Page):
  • Page 1: Summary tables with NH branding
  • Pages 2-3: Detailed job descriptions
  • Page 4: Cost breakdown & WBS