Pulse uses operational data from source systems to connect business activities, identify patterns, evaluate their impact, and generate recommendations.
Pulse is designed for different industries and operational environments, including production, retail, wholesale, logistics, services, and others.
Integrations use industry-specific damain models to map source-system data into Pulse. Each model defines the entities, relationships, and integration flow that apply to a particular operational context.
Pulse uses a shared internal data model to process this information consistently across industries. The internal model itself is not part of this integration documentation.
Domain model assignment
Each Pulse environment uses one domain model. The domain model is selected when the environment is created and cannot be changed afterward.
A subscription can contain multiple Pulse environments. Different environments can therefore use different domain models or be used for separately managed integrations.
Choose the required domain model when creating the environment.
For example:
- A company that operates multiple distinct business units, such as retail and manufacturing, may use a separate Pulse environment for each business unit.
- A company with operations in two countries may use separate environments when those operations are managed or integrated separately.
- Different environments within the same subscription can use different models.
Choose the model that matches the operational context represented by the environment.
Start here
- Review the integration overview.
- Authenticate with the Pulse API.
- Choose a domain model, according to your industry or operational environment.
- Follow the integration guide for that model.
Domain models
Domain models describe how data from a specific industry or operational environment is represented when integrating with Pulse.
Available domain models: