Unit Configs: Difference between revisions
m (→ConfigID) |
|||
| (19 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== ConfigID == | == ConfigID == | ||
Configuration ID is an identifier that references a master build-up document. It's broken down as the following: | Configuration ID is an identifier that references a master build-up document. It's broken down as the following: | ||
|EV]], [[Design Verification|DV]], Milestone | *Unit [[motherboard]] | ||
*Engineering phase [[Engineering Verification|EV]], [[Design Verification|DV]], or [[Production Verifcation|PV]] | |||
*Milestone # of aforementioned hardware phase | |||
*Build-up ID # as designed by the master configID bill-of-materials. | |||
=== Deviation Config === | === Deviation Config === | ||
A type of configuration ID for units that have continued bill-of-material changes after the initial hardware is launched to consumers. These units are considered [[Production Verifcation|PV]] hardware as they are small batches of units with changes to the base bill-of-materials. Deviation configs reference a master build-up document. | |||
* DEV01337 | |||
* SB00269 | |||
== Lamprey Configured == | == Lamprey Configured == | ||
| Line 10: | Line 16: | ||
== Internal Retail == | == Internal Retail == | ||
Retail systems used internally to test kernels and user experience feedback. | |||
=== Non-VMC Assets === | |||
VMC consulting corporation was a company Microsoft used to conduct user experience testing. Non-VMC asset means that the unit is not an owned asset of VMC. | |||
== Development Kit Configuration == | == Development Kit Configuration == | ||
Or simply DK configured. Not only will units in the [[Partner Program]] be equipped with a [[sidecar]]. But [[EV]], [[DV]], or [[PV]] can be configured with [[sidecar]]. The [[Unit Configs#configid|configID]] will reflect if the unit is DK configured. | Or simply DK configured. Not only will units in the [[Partner Program]] be equipped with a [[sidecar]]. But [[Engineering Verification|EV]], [[Design Verification|DV]], or [[Production Verifcation|PV]] units can be configured with [[sidecar]]. The [[Unit Configs#configid|configID]] will reflect if the unit is DK configured. | ||
Examples: | Examples: | ||
* JA''DK'' | * [[Prototype XDK-GB#ADV-XDK-EV2-JADK-EV2|JA''DK'' EV2]] | ||
* XeEV5 ''DK'' | * XeEV5 ''DK'' | ||
* Xe''DK'' | * Xe''DK'' | ||
== Internal SKUs == | |||
== System Level Tester == | |||
SLT. Configuration in which a unit is set up to test a certain aspect or "level" of the system. Such as, but not limited to, the [[GPU]], [[CPU]], or [[Southbridge]]. Different external plastics could be used for engineers to access the system more easily. SLT systems can also feature hot-swap sockets. | |||
{{Consoles}} | |||
Latest revision as of 20:58, 9 April 2024
ConfigID
Configuration ID is an identifier that references a master build-up document. It's broken down as the following:
- Unit motherboard
- Engineering phase EV, DV, or PV
- Milestone # of aforementioned hardware phase
- Build-up ID # as designed by the master configID bill-of-materials.
Deviation Config
A type of configuration ID for units that have continued bill-of-material changes after the initial hardware is launched to consumers. These units are considered PV hardware as they are small batches of units with changes to the base bill-of-materials. Deviation configs reference a master build-up document.
- DEV01337
- SB00269
Lamprey Configured
Unit equipped with Lamprey wires. The term "Stress kits" is a misnomer. All units, retail to dev, are stressed during manufacturing.
Internal Retail
Retail systems used internally to test kernels and user experience feedback.
Non-VMC Assets
VMC consulting corporation was a company Microsoft used to conduct user experience testing. Non-VMC asset means that the unit is not an owned asset of VMC.
Development Kit Configuration
Or simply DK configured. Not only will units in the Partner Program be equipped with a sidecar. But EV, DV, or PV units can be configured with sidecar. The configID will reflect if the unit is DK configured. Examples:
- JADK EV2
- XeEV5 DK
- XeDK
Internal SKUs
System Level Tester
SLT. Configuration in which a unit is set up to test a certain aspect or "level" of the system. Such as, but not limited to, the GPU, CPU, or Southbridge. Different external plastics could be used for engineers to access the system more easily. SLT systems can also feature hot-swap sockets.