BlackBelt Version 6.1.3 has been released to IntraStage Cloud customers, and is available for on-premise customers. To request an upgrade for your on-premise deployment, please contact firstname.lastname@example.org.
Nov 27, 2018
IntraStage is pleased to announce a coveted award from Teradyne to recognize IntraStage’s outstanding service and support.
IntraStage CEO Tom Armes said “We are excited that our long-standing efforts with Teradyne are being recognized for our outstanding support and the willingness to go above and beyond for the Teradyne’s supplier quality team. This kind attention to customer success continues to set the stage for our expanded relationship with the rest of the Teradyne organization. We look forward to continue providing that kind of success and value in 2018 and beyond.”
IntraStage Version 6.0.9 will be released to Cloud-Hosted customers on Saturday, November 4th, 2017.
Please contact us if you need the release notes in order to review the new features and fixes. If you have an On-Premise IntraStage deployment, please contact your account manager to review the release notes and to schedule an upgrade.
When companies contact us for an SPC (Statistical Process Control) solution, we first start with a requirements document. This requirements phase interviews and takes into account the SPC needs of the different intended users of the system. These needs and the capabilities of the system can vary quite a bit. If you’re considering implementing an SPC solution, it’s a good idea to map out everyone’s needs and expectations first. Some examples of different test data management stakeholders and their SPC needs as we’ve seen them are below:
Another question to ask your internal users is what kind SPC quality methodology is needed. Most stakeholders will say they need Cpk in order to determine how close they are to their specification limits. Ppk usually isn’t what they initially request. However, it’s important to understand that legacy data defines the availability of Cpk vs Ppk (there’s already a stable process where we can calculate Cpk, and we are bringing the data of that process into the system). Most of the time, it makes more sense to start off with Ppk, and transition to Cpk once the process is well defined.
So, to summarize, when your stakeholders say they need SPC, make sure you understand what they mean by SPC and how they’ll be applying SPC rules. Ppk and Cpk are both applicable, depending on your use case.