The Data We Capture
A key component to the success of our tool data program is standardizing the data we collect. Below you will find details on what data we intend to collect varying by the type of tool and the features it may support.
Any field with a source of “JEDI” or “OneKey” will be generated as part of tool allocation. All other fields will be provided by the manufacturing systems to the Tool Records API during the time the tool is built.
If any tool falls into more than one category, the fields from each of those groups will be captured.
Core Tool
All tracked tool records are required to at minimum define the following data fields.
| Field | Description | Source | Example |
|---|---|---|---|
| MPBID | The unique identifier of the tool A.K.A. Milwaukee Product Binary Identifier. Comprised of: - A 4 digit / 2 byte product identifier as registered in the Memory Map Management systems in HEX format - A serialized unique identifier which must be all upper case, contain no spaces, and be no longer than 50 characters. | Manufacturer | FFFFAAABBBCCCDDD01234 |
OpenLink Tools
Any power tool that supports the OpenLink protocol should have the following fields captured.
| Field | Description | Source | Example |
|---|---|---|---|
| MPBID | The unique identifier programmed into a tool. This extends the base MPBID definition by requiring the format to be comprised of: - A 4 digit / 2 byte product identifier as defined in the MMM systems - A 6 digit / 3 byte serialized sequence number in HEX format. | Manufacturer | FFFF000000 |
| Passwords | Tool specific passwords which are programmed onto the tool in order to run various commands. They include Admin, METCO, Service, and User passwords. | JEDI for non-OneKey tools otherwise OneKey | FFFFFFFFFFFFFFFF |
| BOD | Born On Date. Unix timestamp representing the date at which the tool was produced in HEX format. | Tool Read | AC01DF |
| Serial Number | A unique tool identifier printed on each tool. It is comprised of tool, facility, date, and unit information. | Rating Label | 628D6032300071 |
| Firmware Version | The version of the firmware running on the tool. | Tool Read | 0E010602 |
| Firmware Part Number | The part number of the PCBA which is running the firmware. AKA "SW Part Number" | Tool Read | 35899D65 |
| Region | The region which the tools is being built for. See Defined Region Codes for full list. | Work Order | US, ANZ, JP, EMEA, ... |
| TTI Part Number | The unique part number assigned by TTI during the manufacturing process which distinguishes variations between products and packing variations. | Work Order | 018615010 |
One-Key Tools
Any tool with One-Key features, will have the following fields captured.
| Field | Description | Source | Example |
|---|---|---|---|
| MAC Address | The tool specific MAC address for the BLE module on the tool. | Tool Read | 2C116515C111 |
| Encryption Keys | BLE modules take advantage of this for encrypting BLE Open Link communication with the phone. Are of type High and Low [Deprecated] | JEDI | 336D6B07494E91FF |
| BLE Firmware Version | The firmware version of the BLE module | Tool Read |
Tool ID Tools
Any tool with which will be receiving the Tool ID QR Code sticker or etching.
| Field | Description | Source | Example |
|---|---|---|---|
| ToolID | The full unique URL which is encoded into the QR code | Barcode Scanner | https://mke.tl/00000OL7R |
Multi-layer Security Tools + Tracking Tag
Any tool which supports multi-layer security and the tracking tag, will have the following details captured.
| Field | Description | Source | Example |
|---|---|---|---|
| Certificates | Tool specific SSL certificates which are used to secure Bluetooth communications with the tool. | OneKey | |
| Claim Key | Tool specific key which is used during end-user claim processes to ensure the physical presence of the tool. | OneKey | 0464BB3C6FC21146 |
Bootloader
Any tool which supports the bootloader will have the following fields captured.
| Field | Description | Source | Example |
|---|---|---|---|
| Unique Device ID | A unique identifier of the PCBA the firmware is programmed onto. | Tool Read | 870073000C50315430313920 |
Embedded Tick Capable
Any tool which supports the embedded Tick will have the following fields captured.
| Field | Description | Source | Example |
|---|---|---|---|
| Embedded Tool MPBID | The MPBID of the tool an embedded BLE board is installed onto. | Tool Read | FFFF000000 |
PCBA Logger
The external PCBA data logger requires additional linking information to describe the
| Field | Description | Source | Example |
|---|---|---|---|
| PCBA Tool | The reference code of the tool the PCBA logger is attached to | User |
Outsourced Products
These fields are ones which aid in traceability of an outsourced product. In these cases some additional data may be required in order to properly identify a tool across companies.
| Field | Description | Source | Example |
|---|---|---|---|
| Vendor ID | In some cases with outsourced tools, there is an opportunity to capture a unique ID defined by the vendor. Examples could be a non-Milwaukee Tool alternate serial number or any other unique value that represents a specific tool. | Manufacturer |
Cellular Products
These fields are ones which aid in traceability of a cellular product. Certain additional data may be required in order to properly identify a unique cellular device with vendors.
| Field | Description | Source | Example |
|---|---|---|---|
| IMEI | The International Mobile Equipment Identity (IMEI) is a numeric identifier, usually unique,for 3GPP and iDEN mobile phones, as well as some satellite phones. | Manufacturer | 350457795727930 |
| ICCID | The Integrated Circuit Card Identifier (ICCID) is a unique numeric identifier for the SIM that can be up to 22 characters long. | Manufacturer | 891004234814455936F |