Asset Lifecycle: from Onboarding to Service
Trace the path of an asset from initial data ingestion and record creation through health scoring, issue detection, and service execution across PTC Orbit.
Overview
An asset in PTC Orbit moves through a series of stages: it enters the platform through data synchronization, becomes a managed record with scored health metrics, surfaces alerts when conditions change, and generates work orders when service is required. Each stage involves a different module and, in many cases, a different persona. This topic maps that journey end to end so you can see how modules connect.
Workflow Stages
1. Tenant provisioning and data sync. An implementer provisions the PTC Orbit tenant, configures Matillion pipelines, and establishes full and incremental data sync from external systems into Snowflake. Asset records flow from Salesforce, AWS S3, or custom REST endpoints into staging tables. For details, see
Tenant Provisioning and Operationalization and
Setting Up Data Sync.
2. Platform configuration. An administrator installs the PTC Orbit package, configures roles and groups to control access, sets up list views and forms for day-to-day use, and creates dashboards to visualize operational metrics. For details, see
Installation and Configuration.
3. Asset record creation. With data flowing into the platform, end users create and manage asset records directly or import them through the data sync pipeline. Each record captures the asset name, product, account, location, and operational attributes. Four views provide different perspectives on the installed base: list, group, location, and map. For details, see
Assets.
4. Health scoring. Scoring models evaluate each asset against weighted factors and criteria to quantify risk, health, and opportunity. Scores update during scheduled batch jobs and surface on the asset detail view. For details, see
Scores.
5. Issue detection. IoT alerts and operator requests appear as pending items when an asset requires attention. Each pending item shows the alert type, priority, associated asset, and current status. For details, see
Pending Items.
6. Service execution. A pending item that warrants action becomes a work order. The
Work Order page tracks the maintenance task from assignment through completion. For recurring service needs, campaigns standardize and automate work order generation across multiple assets. For details, see
Work Orders and
Campaigns.
Personas Involved
• Implementer: provisions the tenant and configures data sync pipelines.
• Administrator: installs the package, sets up roles, views, forms, and dashboards.
• End user: manages asset records, reviews scores and alerts, and creates work orders.
What To Do Next