> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/setup-guidepro/admin/service-model.md).

# Service Model

<figure><img src="/files/7iX2vzGvM0YQz6BnrgOW" alt=""><figcaption></figcaption></figure>

The Equipme Service Model provides a comprehensive framework for managing IT products and services throughout their entire lifecycle. This visual diagram illustrates how different components work together to deliver flexible, scalable solutions to end users.

### Core Components

**Product (Bundle)** At the heart of the model lies the product layer, which integrates master data from multiple sources including ITScope, Synaxon, and custom data sources. These products form the building blocks that are assembled into services.

**Service (Configurable)** Services are the actual offerings delivered to end users—think "Workplace as a Service" or "Managed365." These are configurable solutions that combine products with specific service attributes and can be customized through three key offer types:

* **Rental** - Subscription-based services
* **Purchase** - One-time acquisitions
* **Leasing** - Long-term leasing arrangements

### Service Architecture

**Basic Service (Foundation Services)** Foundation services are essential prerequisites that must exist before other services can be booked. Examples include cloud zones or Office365 tenants—the "required" indicators in the diagram show these dependency relationships. These create the necessary infrastructure upon which other services depend.

**Linked Services (Managed Services)** A powerful new capability that connects services and products tied to a service or product booking. These can be mandatory or optional add-ons, such as MDM services for device management or managed services linked to customer inventory. This creates intelligent service chains that automatically provision related capabilities.

**Add-Ons (Service Requests)** Add-ons are one-time service enhancements that can be booked for existing product and service instances—like on-site installations or PC reimaging. They don't have independent lifecycles but enhance and support core offerings.

### Booking Contexts

The model supports four distinct booking contexts, each designed for specific use cases:

**Employees & Locations** Services are booked for specific employees or locations, enabling precise tracking of who uses what and where, ensuring accurate service and product allocation.

**Cloud** Customers can create containers to map business applications and book Infrastructure/Platform as a Service offerings (like VMs), providing flexibility in cloud resource management.

**Global** Services can be booked without specific assignment to employees or locations, appearing only in the customer's inventory list—ideal for organization-wide licenses or infrastructure.

**Workplace** This special container assigns services to employee objects and serves as a prerequisite for dependent service bookings, creating a comprehensive workplace solution per user.

### Additional Capabilities

**Options** The model includes essential management features:

* **Security** - Integrated security protocols
* **Archiving** - Archiving capabilities for compliance
* **Support** - Built-in support workflows

### The Power of the Booking Action

The central orange button represents the critical action point where services are assigned to their appropriate booking contexts. This is where configuration meets execution, transforming service definitions into actual provisioned solutions.

### Why This Matters

This service model delivers extraordinary flexibility and control. It allows organizations to:

* Build complex service dependencies that automatically provision prerequisites
* Link related services for comprehensive managed solutions
* Track costs and resources with precision across different contexts
* Scale services from individual users to global deployments
* Maintain complete lifecycle management from order to retirement

The Equipme Service Model transforms traditional IT service management into a dynamic, interconnected ecosystem where products, services, and dependencies work together seamlessly to deliver exceptional customer experiences.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://hub.equipme.io/setup-guidepro/admin/service-model.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.