sapl/sapl-vision-roadmap
2
0
Code Issues 18 Packages Projects 1 Wiki

Pilot: Launch ITMS at 1 SAPL location — pilot testing to identify changes required #18

New Issue
Open
opened 2026-09-11 14:42:38 +05:30 by shridhar.sabat · 0 comments
shridhar.sabat commented 2026-09-11 14:42:38 +05:30
Owner
Copy Link
Copy Source

Objective

Launch ITMS as a pilot at 1 SAPL location to validate real-world fit before org-wide rollout. Goal of the pilot: learn what changes are required — in workflows, data model, and UX — when real IT staff and real assets/tickets replace the prototype seed.

Pilot scope (1 location)

  • Pick pilot location + pilot users (suggest Santosh + Vishal + 1-2 floor IT staff)
  • Import real asset inventory for that location into CMDB (replaces seed data)
  • Define ticket categories/priorities to match location's actual IT issues
  • Run live: all IT issues at that location go through ITMS only (no parallel tracking)
  • CMDB edges: record real switch → server → ticket dependencies

What we're testing (success criteria)

  1. Do real tickets fit the data model, or do categories/priority levels need change?
  2. Is the asset → impact flow (switch down → which servers/tickets) accurate with real data?
  3. Do users adopt the PWA (mobile + desktop)?
  4. What's missing for management reporting at the location level?

Output

Pilot feedback report → change list (data model changes, workflow changes, UX gaps) feeding the next iteration before scaling to remaining locations.

Milestone: Project: ITMS (id 100). Related card: #17.

## Objective Launch ITMS as a **pilot at 1 SAPL location** to validate real-world fit before org-wide rollout. Goal of the pilot: learn **what changes are required** — in workflows, data model, and UX — when real IT staff and real assets/tickets replace the prototype seed. ## Pilot scope (1 location) - [ ] Pick pilot location + pilot users (suggest Santosh + Vishal + 1-2 floor IT staff) - [ ] Import real asset inventory for that location into CMDB (replaces seed data) - [ ] Define ticket categories/priorities to match location's actual IT issues - [ ] Run live: all IT issues at that location go through ITMS only (no parallel tracking) - [ ] CMDB edges: record real switch → server → ticket dependencies ## What we're testing (success criteria) 1. Do real tickets fit the data model, or do categories/priority levels need change? 2. Is the asset → impact flow (switch down → which servers/tickets) accurate with real data? 3. Do users adopt the PWA (mobile + desktop)? 4. What's missing for management reporting at the location level? ## Output **Pilot feedback report → change list** (data model changes, workflow changes, UX gaps) feeding the next iteration before scaling to remaining locations. > Milestone: Project: ITMS (id 100). Related card: #17.
shridhar.sabat added this to the Project: ITMS — IT Ticket & Asset Management milestone 2026-09-11 14:42:38 +05:30
shridhar.sabat added the vision/roadmap label 2026-09-11 14:42:38 +05:30
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
vision/roadmap
Vision & Longterm Roadmap card
No labels vision/roadmap
Milestone
No items
No Milestone Project: ITMS — IT Ticket & Asset Management
Projects
Clear projects
No projects
SAPL Vision & Longterm Roadmap
Under Review / Pilot
Assignees
Clear assignees
ajay.sable shridhar.sabat
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sapl/sapl-vision-roadmap#18