Services
The Services screens manage project-based and ongoing work delivered to customers -- consulting, development, migration, support, and infrastructure services. A service is always linked to an SVC-class entitlement and belongs to an organization. Services track scope, status, assigned team, timeline, and can have individual service requests as deliverables.
List view
Open MIDDAG Account > Services to see all services across all organizations.
Columns
| Column | What it shows |
|---|---|
| Title | Service title (clickable -- opens detail view) |
| Type | Service type: hosting, support, infrastructure, consulting, development, mobile-apps, migration, upgrade, or project-management |
| Organization | The customer organization (clickable) |
| Entitlement | The linked SVC-class entitlement code (clickable) |
| Priority | Low, Normal, High, or Urgent |
| Status | Proposal (gray), Approved (blue), In Progress (blue), On Hold (yellow), Delivered (green), Closed (green), or Cancelled (red) |
| Start Date | When work began (or is scheduled to begin) |
Filters and search
- Search -- type a service title, organization name, or entitlement code
- Status -- filter by Proposal, Approved, In Progress, On Hold, Delivered, Closed, Cancelled, or All
- Type -- filter by service type
- Priority -- filter by Low, Normal, High, Urgent, or All
- Organization -- filter to a specific organization
Detail view
Click any service title to open the detail view.
Header
The header shows:
- Service title with a status badge and priority indicator
- Service type
- Action buttons: Edit, Approve, Start, Hold, Deliver, Close, Cancel (available actions depend on current status)
Service data
| Field | Description |
|---|---|
| Title | Service name |
| Type | Category of work |
| Status | Current lifecycle status |
| Priority | Urgency level |
| Description | Detailed scope description |
| Organization | Customer name (clickable) |
| Entitlement | SVC-class entitlement code (clickable) |
| Contract | Linked contract (clickable, if applicable) |
| Assigned Team | Team or individual responsible for delivery |
| Start Date | When work began |
| Estimated End | Target completion date |
| Actual End | When work was actually completed |
Linked entitlements and credit consumption
Below the service data, a section shows:
- Entitlement -- the SVC-class entitlement that governs this service, with its status and period
- Credit consumption -- if the entitlement uses a credit-based model (UST hours), a summary shows total allocated hours, hours consumed by service requests, and remaining balance
Service requests
A table of all service requests (deliverables) under this service, showing SR number, title, priority, status, assigned person, estimated hours, and due date. Click any row to open the service request detail.
Status lifecycle
A horizontal workflow visualization:
@ Proposal -> @ Approved -> @ In Progress -> o On Hold -> o Delivered -> o Closed
CurrentEach completed step shows its timestamp. Transitions that skip steps (e.g., Proposal directly to Cancelled) are also supported.
Actions
| Action | Available when | What it does |
|---|---|---|
| Edit | Any non-terminal | Update title, description, dates, team, or priority |
| Approve | Proposal | Approve the service proposal and move to Approved |
| Start | Approved | Begin work and transition to In Progress |
| Hold | In Progress | Pause work temporarily (On Hold) |
| Resume | On Hold | Resume work and return to In Progress |
| Deliver | In Progress | Mark all deliverables as complete |
| Close | Delivered | Finalize the service (terminal for active work) |
| Cancel | Any non-terminal | Cancel the service with a required reason note |
Related pages
- Service Requests -- individual deliverables within a service
- Entitlements -- the SVC-class entitlement that provisions services
- Contracts -- the legal agreement governing the service
- Environments -- infrastructure the service may operate on
- Organizations -- the customer receiving the service
- Entitlement Classes -- how SVC class provisions services