Manufacturing Events

ToolRecord:Upsert

Filtering Patterns

source: jedi.events.manufacturing.v1

detail-type: ToolRecord:Upsert

---

Example

// Example 'ToolRecord:Upsert' event
{
    "time": "2022-12-14T16:23:10.373Z",
    "source": "jedi.events.manufacturing.v1",
    "detail-type": "ToolRecord:Upsert",
    "detail": {
        "id": {
            "mpbid": "FFFF000000",
            "serialNumber": "GA12340000000",
            "toolId": "https://mke.tl/M000004C3",
            "vendorId": "ABCD 1234"
        },
        "firmware": {
            "partNumber": "012CDF",
            "version": "001FED"
        },
        "ble": {
            "version": "0.1.2.3",
            "moduleType": "BGM220",
            "macAddress": "2C549188C9E3"
        },
        "link": {
            "mpbid": "FFFF000001"
        },
        "uniqueDeviceId": "1234567890ABCDEFGHIJ",
        "ttiPartNumber": "0123456789",
        "region": "US",
        "bornOnDate": 1641796823,
        "createdAt": 1641796823,
        "updatedAt": 1641796823,
        "mfgProductionDate": 1641796823,
        "mfgLastUpdateDate": 1641796823
    }
}

NOTE

The only required field within the event Detail is id.mpbid. All other fields are optional. Event consumers should treat data received as an “Upsert,” meaning that when a record is received if it does not exist it must be added. If it does exist, fields should be populated for the first time or overwritten. Events will contain partial updates, and a tool record may receive multiple updates over the tool’s life.