|
Term
|
Definition
|
|---|---|
|
Asset
|
A physical piece of equipment, device, or component tracked in PTC Orbit. Each asset record captures serial number, location, status, and service history.
|
|
Asset Score
|
A calculated numeric value representing the health, risk, or opportunity associated with an asset. Scoring models generate asset scores based on configurable criteria.
|
|
Asset Timeline
|
A chronological view of all events, service records, and status changes for a single asset.
|
|
Campaign
|
A coordinated set of service or revenue activities that target multiple assets. PTC Orbit supports service campaigns and revenue campaigns.
|
|
Connector
|
A configured integration path that transfers data between PTC Orbit and an external system such as Windchill, ServiceMax, or a custom source.
|
|
CRUD
|
Create, Read, Update, Delete: the four basic permission levels applied to data objects in PTC Orbit.
|
|
Dashboard
|
A configurable page that displays charts, metrics, and summaries. Administrators create dashboards; end users view them.
|
|
Data Connector
|
See Connector.
|
|
Data Quality
|
The accuracy, completeness, and consistency of asset records. PTC Orbit provides matching rules and data review tools to maintain data quality.
|
|
Form
|
A configurable layout that controls which fields appear when you create or edit a record. Administrators design forms on the Forms configuration page.
|
|
Term
|
Definition
|
|---|---|
|
Group
|
A collection of users who share the same permissions. Administrators assign users to groups on the Groups page.
|
|
Installed Base
|
The complete set of assets deployed at a customer site. An Installed Base record links assets to an account and location.
|
|
IoT Alert
|
A notification generated when a sensor reading from a connected asset crosses a defined threshold. IoT alerts create pending items for review.
|
|
List View
|
A tabular display of records filtered by criteria. Administrators configure list views; end users apply filters and sort columns.
|
|
Term
|
Definition
|
|---|---|
|
Matching Rule
|
A rule that defines criteria for identifying duplicate or related asset records. Matching rules drive the data quality review workflow.
|
|
Operator Request
|
A manually created pending item submitted by an asset operator to flag a maintenance need or anomaly.
|
|
Pending Item
|
A record that captures an IoT alert or operator request requiring evaluation. Pending items can be converted to work orders, dismissed, or escalated.
|
|
Permission
|
An access right that controls whether a role can create, read, update, or delete records of a specific object type.
|
|
Pipeline
|
A data processing job in the Matillion ETL layer that extracts, transforms, and loads data from source systems into PTC Orbit.
|
|
Role
|
A named set of permissions assigned to users. PTC Orbit includes built-in roles (Orbit Admin, Orbit User, Standard User) and supports custom roles.
|
|
Term
|
Definition
|
|---|---|
|
Scoring Model
|
A configurable model that calculates asset scores based on weighted criteria such as age, service history, telemetry data, and operational metrics.
|
|
Service Campaign
|
A campaign type that generates work orders for preventive maintenance, recalls, or field modifications across selected assets.
|
|
Tenant
|
An isolated instance of PTC Orbit provisioned for a single customer organization. Each tenant has its own data, configuration, and user base.
|
|
Telemetry
|
Sensor data collected from IoT-connected assets: temperature, vibration, pressure, operating hours, and similar metrics.
|
|
Work Order
|
A service task record that tracks a maintenance or repair activity from creation through completion. Work orders are assigned to technicians and linked to assets.
|