Design
The data model decisions.
The asset model is the foundation. Decide whether assets represent whole machines, major assemblies or both, and how parent and child assets relate, because maintenance plans, warranties and reporting all hang from that hierarchy. Next, decide which system owns the bill of materials and parts pricing; usually the ERP stays in charge, with product items and price books synced to Salesforce. Finally, classify work types carefully, separating install, preventive, warranty and billable repair, since those categories drive scheduling durations, required skills and invoicing.
ERPSales orders create installation work, while parts inventory, pricing and billable service lines move between the ERP and Field Service so invoicing stays accurate.
IoT and equipment telemetryConnected machines can send alarms and meter readings that open cases or trigger maintenance work before the customer notices a problem.
Product lifecycle managementEngineering documents, service bulletins and revision history reach technicians through the work order, so they repair the configuration actually installed.