SysOps Service Catalog

Catalog

Published view of what IT offers, who each service is for, what approvals it needs, and how each request should enter the platform.

Session requiredAuthenticated routes expect a real session token or cookie.API base: https://dev.sysopsai.net/api
Published Services

Make services visible before people ask for them the wrong way.

The catalog is now part of the route-native web shell, giving the self-service front door a production application home instead of keeping it only in demo HTML.

Audience: staff, managers, service deskUse: intake readiness + expectation settingConnected to: Request + Knowledge + Approvals
published
12

Catalog services live

catalog-linked
78%

Requests mapped to a catalog service

knowledge-backed
7

Services with self-service guidance

to improve
22%

Requests still arriving off-catalog

Published Service Families

Services should be described in business language while still carrying the governance IT needs to deliver them well.

Catalog-backed intake
ServiceTypical UseStandard TimingEligibility / Approval
Identity and accessRequest access, change access, or validate approval requirementsSame day triage; 1-3 business days for standard fulfillmentNamed approver required for most access changes
Data and reporting supportFix data issues, request enhancements, or validate reporting dependencies1 business day triage; scoped delivery varies by complexityBusiness sponsor required for net-new reporting work
Website and content publishingSubmit content work, planned releases, or content issue corrections1 business day intake; scheduled publish windows applyContent owner required before publish approval
Collaboration and Teams workspace servicesRequest workspace help, ownership changes, or standards guidanceSame day guidance; 2-5 business days for structural changesManager or workspace owner approval may be required
Service support and incident responseReport a problem affecting users, access, or service availabilityImmediate routing for severity-based incidentsNo approver needed for incident reporting

Catalog To Delivery Flow

The catalog should not be a static brochure. It should route people into the right next step.

1

Understand

User reads service definition, timing, eligibility, and approval requirements.

2

Choose Path

The platform routes the user to self-service, request intake, or live support based on service type.

3

Govern

Approvals, ownership, and downstream tracking are applied before the work moves into delivery.