Intel® Transparent Supply Chain data files
· 04/11/2025 ·
This page contains details about the data files that can be downloaded from the Intel® Transparent Supply Chain (Intel® TSC) system. It includes instructions on how to access and download these files, which are crucial for internal reports and device management. The page lists the various types of data files available, their formats (such as .csv), and the steps needed to download them. See the Transfer devices article for instructions on downloading files.
Note
Intel recommends downloading a maximum of 300 device files at a time.
File name construction
The section below outlines the contents and naming conventions of the downloaded zip files.
File name example - certificate_133_20240813_002112.zip
The zip file name is determined as follows:
- Starts with
certificate - The number of found devices
10 - The date the zip file was generated YYYYMONTHDAY
20240813 - The serial number requested
002112
File contents
Each zip file may contain all or some of the files listed below.
The file-name.csv is a spreadsheet containing a list of the serial numbers in the zip file.
The batch_2020-05-26_60277.csv.log is a log file that contains the total number of serial numbers matched in the uploaded serial number.csv file.
The downloaded zip file for multiple devices includes a zip file for each device that was found. Each zip file is named with the serial number of the device to which it is associated. The zip files contain the Intel TSC data files associated with that serial number. See the next section, Intel TSC data files, for details on the individual Intel TSC data files.
Intel TSC data files
The data files ingested from Open Compute Security (OCS) sftp to the Intel TSC Web Portal are signed by the Intel TSC Certificate Authority. The Intel TSC Certificate Authority is used to verify that the files' signatures were issued by the Intel TSC Issuing CA for that supplier.
The Intel TSC data files are generated at the system factory. Each individual serial-number zip file contains multiple Intel TSC Data files. The contents of the zip file are determined by what the customer uploads. Not all zip files contain every type listed below.
The following is a list of the Intel TSC data files that may be included in the zip file.
- As Built Data.xls file -- serialnumber.xls
- Statement of Conformance.xml issued for the
As Built Datafile - Direct Platform Data.xml file
- Platform Certificate.cer file
Statement of conformance
The Statement of Conformance is a signed XML file generated for every signed As Built data file. The Statement of Conformance pulls the data from the As Built data file and populates the following XML tags:
<?xml version=\"1.0\" encoding=\"utf-8\" standalone=\"no\"?\>\<Intel\>
<Statement_of_Conformance\>
<Product_Serial_Number\> XXXXXXX \</Product_Serial_Number\>
<Intel_Part_Number\>Thinkpad_T480s\</Intel_Part_Number\>
<Platform_Model\> Thinkpad_T480s \</Platform_Model\>
<Date_Manufactured\>10/13/2018 08:34:21\</Date_Manufactured\>
<Date_Statement_Created\>5/25/2020 7:46:21 PM\</Date_Statement_Created\>
<As_Built_Date\>10/13/2018 08:34:21\</As_Built_Date\>
<AuthorityInfoAccess\>https://trustedservices.intel.com/content/TSC/certs/TSC_IssuingCAVERIZON_MEDIA-INSPUR.cer\</AuthorityInfoAccess\>
<As_Built_Data_Hash\>9h7vJDkb5NKzzAK3ZD/e1doSKxTVQ4C4pHPOPfmVUGA=\</As_Built_Data_Hash\>
<Legal_Statement\>Legal_Statement\</Legal_Statement\>
</Statement_of_Conformance\>
<Signature
xmlns=\"http://www.w3.org/2000/09/xmldsig#\"\>\<SignedInfo\>\<CanonicalizationMethod
Algorithm=\"http://www.w3.org/TR/2001/REC-xml-c14n-20010315\"/\>\<SignatureMethod
Algorithm=\"http://www.w3.org/2001/04/xmldsig-more#rsa-sha256\"/\>\<Reference
URI=\"\"\>\<Transforms\>\<Transform
Algorithm=\"http://www.w3.org/2000/09/xmldsig#enveloped-signature\"/\>\</Transforms\>\<DigestMethod
Algorithm=\"http://www.w3.org/2001/04/xmlenc#sha256\"/\>\<DigestValue\>y694il4LZQPLdKhiZm23tY6qKtcpcyYSg8YAvtTvMsI=\</DigestValue\>\</Reference\>\</SignedInfo\>\<SignatureValue\>q/4PpmHHiytGdJ4udlNhRmqoR9q5uOkpq6AFi26BntFfz9wHjpu1SUTuRjbG/tA24VyyonSEHGG9
JhpXykhD6J2ZsR6RL6rnkntsbzWdV31VWP1ngHOBzdgFBA3niFIor/anlRrnkMdMfEUogmoH1x1y
EfAbdRMADFwyFMd77ZOd5/yLqctt9rRf6DD1Oo0RaQoLYtilKT3hcdkPcI/fDHW4RkSTDh3iMwl8
kOiBRgzM4k+HUZfXU3ENZ70EGLh8i+oqL3uBHj4kfc5RDq0EaBic5Nmn4YlSQPQ3scPm+m2Jhc0t
0tsqVEj4kc9AiMLEIrEqWmJaF2RSVmBr5QqRGBTcKGIUsh3AEd4maFNitAQW41tAh6hfoWtBYxK6
gOS59Y+o54z6CZ4kuH8Slp/BgdMuZcK7Ob+hdssX3NAxAJGeuIgMRb5M3u0qqIBfuq4B547tuR44
ciBUijo2HwOBHeRVigH9tKnjwekgEwicJLKk8/KdwZ8/93W8R5+qBMG+\</SignatureValue\>\<KeyInfo\>\<X509Data\>\<X509SubjectName\>C=US,
ST=CA, L=Santa Clara, O=Intel Corporation, OU=Transparent Supply Chain
Issuing CA VERIZON_MEDIA-INSPUR,
CN=www.intel.com\</X509SubjectName\>\</X509Data\>\</KeyInfo\>\</Signature\>\</Intel\>
Intel TSC certificate authority
All Intel TSC files are signed using an Intel TSC Certificate Authority (CA) issued for each supplier. The CA is used to verify that the files' signatures were issued by the Intel TSC Issuing CA for that supplier.
The following is the URL for the Intel TSC Issuing CA certs:
https://trustedservices.intel.com/content/TSC/certs/TSC_IssuingCA_ClientDemo1.cer
The following is the URL for the Intel TSC Signing Service Root CA cert:
https://trustedservices.intel.com/content/TSC/certs/TSC_SS_RootCA_Certificate.cer
System As Built Data file
The system level As Built Data file is an Excel spreadsheet generated by the system factory at the time of manufacturing by the factory shop floor control system.
The following table contains the System As Build Data report field format. Each line in the table corresponds to a column in the As Build Data report file. System As Built Data reports do not contain a quantity field. Each component in the system has a line in the report—the System As Build Data report is written in an Excel spreadsheet.
| Report titles | Data field | Data field description | |
|---|---|---|---|
| required | SN_FLAG | SOR#\EOR# | Start of record\End of Record |
| required | SN | SSN | System Serial Number |
| required | WO_NO | WO_NO | Work Order Number |
| required | SYSTEM_ASSEMBLY_SITE | SAAS | System Assembly Site (Company and City) |
| required | BUILD_DATE | SBD | Build Date YYYY/MM/DD HH:MM |
| required | PART_SN | CSN | Part Serial Number |
| required | DATE_CODE | CDC | Component Purchase Date |
| required | LOT_CODE | CCODE | Component Lot Code/Batch Code |
| required | VENDOR_CODE | CMFG | ODM Vendor Code |
| required | VENDOR_NAME | CMFG | Vendor Name English or Chinese |
| Optional | PPID | CPPID | Piece Part Identification |
| required | PART_NO | CPN | ODM Part Number |
| required | PART | CPN | Type of component |
| required | PART_DESC | CDESC | Part Description |
| required | LOCATION | CRD | System Reference Designator |
| required | MAKER_DESC | CMKR | Component Manufacturer name |
| required | MAKER_PART_NO | CMPN | Component Manufacturer part number |
| Optional | INTEL_PN | IPN | Intel 6-3 part number |
- SN_FLAG -- Serial Number flag is used to identify specific rows of the
As Built Datafile- SOR# - The Start of Record is placed in the first row of the spreadsheet\
- EOR# - End of Record - The End of Record is placed in the last row of the spreadsheet
- SN -- System Serial Number. A system is defined as being contained in one Chassis. Each system must have a unique system serial number assigned
- WO_NO -- The factory Work Order number that the system was manufactured under
- SYSTEM_ASSEMBLY_SITE -- System Assembly Site information (ODM Company Name ODM the city of the Factory location)
- BUILD_DATE -- The Build date and time, the date time format is YYYY/MM/DD HH:MM
- PART SN -- The component serial number assigned by the manufacturer
- DATE_CODE -- The date the component was received into the factory inventory; the date format is YYYY/MM/DD
- LOT_CODE -- The lot code / batch code of the component assigned by the component manufacturer
- VENDOR_CODE -- ODM assigned code for the Vendor or Distributor that the component was purchased from
- VENDOR_NAME -- The name of the Vendor or Distributor that the component was purchased from
- PPID -- Piece Part Identification ODM/OEM assigned Unique Identifier assigned to each individual component.
- PART_NO -- ODM assigned part number of the component
- PART -- Type of component (Chassis, Memory, Drive, DIMM, Processor, Motherboard, Network Card, etc.)
- PART_DESC -- Description of the component
- LOCATION -- The reference designation location of the component in the chassis or on the motherboard.
- MAKER_NAME -- The component (OEM) manufacturer's name
- MAKER_PART_NO -- The component (OEM) manufacturer's part number
- INTEL_PN - Intel internal BOM Part Number (N/A for non-Intel products)
Direct platform data file
The Direct Platform Data (DPD) file is a signed XML file generated at the system factory when the system is at the final test station. It collects information on the system-level components.
| System Components |
|---|
| Motherboard |
| Memory DIMMS |
| Processors |
| Network Cards |
| Solid State Drive |
Platform certificate file
The platform certificate file is an X.509 certificate that attests that a specific platform contains a unique TPM, establishing a root of trust in the platform. Platform certificates contain assertions about the trust made by a platform manufacturer. The certificate asserts the platform's security properties and configuration as shipped by the manufacturer.
An enterprise may use a platform certificate to correlate a list of platform serial numbers (used for physical property management) with EK credentials (used for logical property management). The platform serial number attribute is included in the certificate to support this use case. In addition, an enterprise may use the platform certificate to assert non-security related properties, such as platform components, which are included optionally by the platform manufacturer in the certificate. The platform certificate is not expected to expire during the platform's normal life expectancy.
Assertions made by a platform certificate
The following table lists all the fields central to TCG's use of this credential type and that MUST or MAY be in a platform certificate.
| Field Name | Description |
|---|---|
| Credential Type Label | Distinguish credential types issued under a shared key |
| EK Credentials | Identifies the associated EK Credentials |
| Platform Manufacturer String | Name of platform manufacturer as a string |
| Platform Model | Manufacturer-specific identifier |
| Platform Version | Manufacturer-specific identifier |
| Issuer | Identifies the issuer of the credential |
| Platform Specification | Platform Specification to which this platform is built |
| Credential Specification | Platform Certificate Specification Version, Level, and Revision |
| Validity Period | Time period when credential is valid |
| Signature Value | Signature of the issuer over the other fields |
| Platform Serial Number | Platform's unique serial number |