Specials QA Validation Process Part 1
Introduction
When a customer asks for a configuration that cannot be set as in the standard BTO or CTO process, a special SKU is created for that server.
A Special is a SKU (Stock Keeping Unit) that has specific requirements for a customer that may include:
• Firmware locked down to a specific version.
• Options installed in specific slots.
Overview
The software and hardware configurations are specified in a document known as CID (Customer Intend Document) that has the information needed to configure and validate the specific settings a server needs to have for a specific customer.
Each special has a SKU (Stock Keeping Unit) number that has to be used when getting information for the Hardware parts and also at the UUT registration during testing. The SKU is used as a trigger for diagnostics to apply the customer required settings.
This document is intended to be uses as guide for the new Special validation process and briefly describes what you need, where to get it and how to perform the validation process.
What is a CID?
A CID is a guide for the Hardware and Software specifications you have to follow to meet the customer requirements for their custom-configured servers. The documents specifies a lot of different aspects, from the splash screen for the server at POST to the labels and packaging the server has to have when the customer opens the box.
Also, the CID often specifies the steps you have to follow to verify things like the BIOS specific configuration, customer software image download, custom iLO password, OS settings, etc.
What is MyPIM?
Once you have the Special Configuration Code (Product SKU) you can use the MyPIM page to get the PO File for the Special you are going to test.
Is very important that the PO file to be used in the specials comes at all from the file downloaded from myPIM this is because it is a copy of the order that is used in the factory and the main idea of our laboratory in Costa Rica is simulate the factory’s conditions.
The Jira cases will be classified as: defect, existing SKU (update), migration or new SKU. Depends of which is the case the QA process will be a few different, in the following table we can see some differences
Search from various English teachers...
Corrections · 1
0
Specials QA Validation Process Part 1
Introduction
When a customer asks for a configuration that cannot be set as in the standard BTO or CTO process, a special SKU is created for that server.
A Special is a SKU (Stock Keeping Unit) that has specific requirements for a customer that may include:
• Firmware locked down to a specific version.
• Options installed in specific slots.
Overview
The software and hardware configurations are specified in a document known as a CID (Customer Intend Document) that has the information needed to configure and validate the specific settings a server needs to have for a specific customer.
Each special has a special SKU (Stock Keeping Unit) number that has to be used when getting information for the Hardware parts and also at the UUT registration during testing. The SKU is used as a trigger for diagnostics to apply the customer required settings.
This document is intended to be used as guide for the new Special validation process and briefly describes what you need, where to get it and how to perform the validation process.
What is a CID?
A CID is a guide for the Hardware and Software specifications you have to follow to meet the customer requirements for their custom-configured servers. The documents specifies a lot of different aspects, from the splash screen for the server at POST to the labels and packaging the server has to have when the customer opens the box.
Also, the CID often specifies the steps you have to follow to verify things like the BIOS specific configuration, customer software image download, custom iLO password, OS settings, etc.
What is MyPIM?
Once you have the Special Configuration Code (Product SKU) you can use the MyPIM page to get the PO File for the Special you are going to test.
It is very important that the PO file to be used in the specials comes at all from the file downloaded from myPIM this is because it is a copy of the order that is used in the factory and the main idea of our laboratory in Costa Rica is simulate the factory’s conditions.
The Jira cases will be classified as: defect, existing SKU (update), migration or new SKU. It depends of which is the case the QA process will be a few different, in the following table we can see some differences. No tiene sentido.
Muy bien!!! De hecho, fantastico!!!!!!
Want to progress faster?
Join this learning community and try out free exercises!
Don’t miss out on the opportunity to learn a language from the comfort of your own home. Browse our selection of experienced language tutors and enroll in your first lesson now!
Start Learning Today
