Merge pull request #275 from dandaly/opi-dev-prov-life-pldm

docs: opi dev prov life updated bmc section with pldm

OPI_DEVICE_PROV_LIFE.md

@@ -19,10 +19,15 @@ For the purposes of this specification a 'device' is a PCI device that intends t
 
 ## BMC Connectivity Baseline
 
-- **PLDM Type 2 (Monitoring & Control)**: Device shall support DMTF PLDM type 2 sensors using a standard PCIe connector physical medium MCTP transport (e.g. SMBus, PCIe VDM, USB).  This includes the ability to read and monitor in addition to being able to set thresholds for:
-  - Temperature Sensors SHALL be supported
-  - Voltage Sensors SHALL be supported
-- **Identification**: Devices shall identify themselves to the BMC with the equivalent of the QR code for use in sZTP.
+1. **PLDM**: Device shall support DMTF Platform Level Data Model (PLDM) type 2 (Monitoring & Control) using a standard PCIe connector physical medium MCTP transport (e.g. SMBus, PCIe VDM, USB). This includes the ability to read and monitor in addition to being able to set thresholds. PLDM is used to support get the following information from the device:
+    1. **Temperature**: Temperature sensors shall be supported
+    2. **Power**: Voltage sensors shall be supported
+    3. **Identification (via FRU)**: The Following fields are defined by [DSP0257](https://www.dmtf.org/sites/default/files/standards/documents/DSP0257_1.0.0.pdf) - 212 (General FRU Record):
+        1. **Type, Model, Part Number**: Used to identify the type, model, and part number for this device
+        2. **Serial Number**: Used to identify this particular device
+        3. **Manufacturer, Manufacturer Date, Vendor, Name, SKU**: Used to identfy the manufacturer including the SKU
+        4. **Version**: The hardware version of this device
+        5. **Asset Tag**: The same information provided by a QR code on the physical device.
 
 ## Life Cycle Management