Ingesting asset operations and back-office data into Data 360
Key Takeaway
Data in a data lake object (DLO) can be used for Segmentation and Activation only after its fields are mapped to data model objects (DMOs) and the required relationships are set up. For custom data streams, you do that setup yourself. The Manufacturing data kit's predefined data streams arrive with their DMOs and mappings.
Data 360 is where Agentforce Manufacturing brings together large amounts of asset, customer, sales, and service data. This includes data stored outside Salesforce in data lakes, warehouses, and other systems. You ingest asset operations and back-office data into Data 360 and map it to a standardized data model. After that, you can harmonize, query, transform, and segment the data at scale. Sales and service teams use it to make data-driven decisions, optimize business operations, maximize asset operational performance, and improve customer satisfaction.
When to use Data 360
Use Data 360 with Agentforce Manufacturing when the requirement is to unify and analyze large-scale manufacturing data stored in external data lakes, warehouses, and systems. Data 360 ingests, harmonizes, and analyzes data on manufacturing operations, assets, and customers.
Data 360 isn't the only way to move data, so match the tool to the requirement.
| Tool | What it does | Where the data lands |
|---|---|---|
| Data 360 | Unifies and analyzes large-scale data from external data lakes, warehouses, and systems | Data 360 |
| MuleSoft Accelerators for Manufacturing | Syncs and transfers data on sales agreements, rebates, and other records from external systems, such as ERP and product information management systems | Agentforce Manufacturing |
| CSV Data Management | Uploads large CSV datasets | Salesforce, as records |