TL9000测量手册5.6和5.7版的主要区别

TL9000测量手册5.6和5.7版的主要区别
整理：胡子春2020.7.20
测量手册5.6内容测量手册5.7内容
1 3.5.2k):修正问题数据，同时对于24个月内
提交的任何错误数据，重新提交改正好的数
据。

当出现下列的一种或者多种情况且导致数
据发生变化时，可以认为数据出现了错误：
1）在数据申报时该测量指标不能有效的满
足要求。

2）未遵从数据采集和校验流程。

3）数据采集脚本或者工具有错误。

4）最近提交的数据出现数据源变化。

当重新计算的TL9000指标月度数据偏离已
经提交数据的1%可以认为数据发生了变化。

换句话说，重新计算的指标值大于已经提交
指标值1.01倍，或者重新计算的指标值小于
已经提交指标值的0.99倍，就认为是数据发
生了变化。

3.5.2k):修正问题数据，同时对于24个月内提交的任何错误数据，重新提交改正好的数据。

当出现下列的一种或者多种情况且导致数据发生变化时，可以认为数据出现了错误：
1）在数据申报时该测量指标不能有效的满足要求。

2）未遵从数据采集和校验流程。

3）数据采集脚本或者工具有错误。

4）最近提交的数据出现数据源变化。

当重新计算的TL9000指标月度数据偏离已经提交数据的1%可以认为数据发生了变化。

换句话说，重新计算的指标值大于已经提交指标值1.01倍，或者重新计算的指标值小于已经提交指标值的0.99倍，就认为是数据发生了变化。

该要求也适用于在认证前规定的三个月提交数据。

This requirement also applies to the required three months of data submitted prior to certification.
24.2.5产品和服务排除
组织必须排除那些不再完全为通用客
户群提供支持的产品的数据。

排除必须仅适
用于已向客户发出正式的告知，告知任何产
4.2.5产品和服务排除
组织必须排除那些不再完全为通用客户群提供支持的产品的数据。

排除必须仅适用于已向
客户发出正式的告知，告知任何产品和服务处于增加和维护（A&M），终止制造（MD）状态，
“终止提供新服务”的状态，停止支持（EOS）或生命终止（EOL）。

品和服务处于增加和维护（A&M），终止制造（MD）状态，“终止提供新服务”的状态，停止支持（EOS）或生命终止（EOL）。

对于与软件相关的产品或服务，排除适用于通用版本以及特定的软件版本。

它也适用于没有部署新软件特性发布的任何软件产品。

该排除不适用于已被后续版本替代已报废的可现场替换单元（FRU），除非这些单元已完全从现场被召回。

对于与软件相关的产品或服务，排除适用于通用版本以及特定的软件版本。

它也适用于没有部署新软件特性发布的任何软件产品。

该排除不适用于已被后续版本替代（产品的一部分的）个别已报废的可现场替换单元（FRU），除非这些单元已完全从现场被召回。

This exclusion does not apply to individual Field Replaceable Units which are part of a product in general availability that have been made obsolete by a later version unless those units are completely recalled from the field.
37硬件测量：7硬件测量
5个地方修改处合起来理解是：
针对原5.6版变化内容的进一步澄清。

主要是对产品退役阶段的数据报告进行剔除。

是从
产品生命周期阶段来考虑，而不是GA阶段。

The wording in five places throughout this section has been revised to correctly reflect the change
in the R5.6Point Release to eliminate the reporting of data during a product’s retirement phase.
This eliminates the confusion raised by references to life cycle instead of general availability
phase.
48.2Software Problem Report Measurement
(SPR)软件问题报告测量8.2Early Software Problem Report Measurement(eSPR)早期软件问题报告测量
现有的软件问题报告测量（SPR）指标调整为早期软件问题报告（eSPR）测量。

相比SPR，eSPR 有以下变化：
1、只有在主版本软件发布后的最初12个月内软件问题报告才被计算。

2、正常化单元是客户和该版本软件有关的报告问题数量。

Replaces the existing Software Problem Report Measurement(SPR)with a new Early Software Problem Report Measurement(eSPR).The new measure is similar to the old with the following changes: 1.Only software problem reports within the first12months after the introduction of a major release are counted.
2The normalization unit is the number of customers reporting problems with the release.
早期软件问题报告（eSPR）测量跟踪的是软件（GA阶段后）在早期发布期间被客户发现和报告的问题。

该测量用于评估源于客户软件问题报告数量，是表示在其运行的生命周期中早期部分期间交付的产品。

The early Software Problem Report(eSPR)measurement tracks the software problems that are found and reported by customers during early deployment,just after General Availability.
This measurement is used to evaluate the number of customer originated software problem reports that are indicative of the software quality of the product delivered during the early part of its operating life cycle.
在5.1.2b)中的计算规则适用于针对所有产品类型的eSPR测量计算软件问题报告，具体如下：1）只有在eSPR周期报告的软件问题报告才被计算；
2）针对eSPR报告的目的，在软件发布或其后的软件更新发布，软件报告问题必须被归入到软件发布。

3）当软件发布或软件更新不能被确定时，软件问题报告应被归入到最新软件版本；
4）当报告的问题是被怀疑是软件相关的问题，但是不能在其后的调查过程中被重现，必须被计算；
5）多个来自于同样客户的同样的软件问题报告，针对同样的版本或其后软件更新的版本，在第一个月份中报告的问题应被计算为单个问题报告
6）针对eSPR的分母，在eSPR期间，假如他们至少报告了一个发布的问题报告，计算客户数。

7）针对eSPR的分母，在发行的eSPR期间，每一个已经报告至少一个问题的发布，一个客户算一次。

The counting rules in5.1.4b)apply in counting software problem reports for the eSPR measurement for all product categories,with the following clarifications:
1)Only software problem reports that are reported during the eSPR Period shall be
counted.
2)For the purposes of eSPR reporting,a software problem reported in a software release
or a subsequent software update for that release,shall be attributable to the software
release.
3)In cases where the software release or software update cannot be determined,the
software problem report shall be attributed to the most recent software release.
4)Problem reports where the reported problem is suspected to be software related but
cannot be reproduced during subsequent investigations shall be counted.
5)Multiple reports of the same software problem from the same customer for the same release or a subsequent software update shall be counted as a single problem report in
the first month in which the problem is reported.
6)For the eSPR denominator,customers are only counted if they have reported at least
one problem report for the release within the eSPR Period.
7)For the eSPR denominator,a customer is counted once for each release for which it has reported
at least one problem within the release's eSPR Period。

在5.1.4c)的计算规则排除，适用于针对所有产品类型的eSPR测量计算软件问题报告，具体如下：
1）被确定是一个硬件问题的报告不应被计算，即使设计方案或替代方法用软件来执行；
2）问题报告由于输入数据导致的错误被排除；
3）软件问题报告针对软件发布或相关软件更新，超过了那个软件发布的eSPR周期，被排除；4）假如组织不能确认被报告的问题报告准确的软件发布或软件更新，但是组织知道在讨论中的缺陷在前12个月的所有软件发布或软件更新过程中已经被解决，那么在讨论中的问题报告被排除。

5）在一个软件发布撤销或不再支持后的问题报告被排除。

The counting rule exclusions in5.1.4c)apply in counting software problem reports for the eSPR measurement for all product categories,with the following clarifications:
1)A problem report that is determined to be a hardware problem shall not be counted even
if the design solution or workaround is implemented in software.
2)Problem reports due to faults in input data are excluded.
3)Software problem reports against a software release or associated software update that
fall outside of the eSPR Period for that software release are excluded.
4)If the organization cannot confirm the exact software release or software update to which
the problem report is reported,but the organization knows that the defect in question has already been fixed in all software releases or software updates that were released in the previous12months,then the problem report in question is excluded.
5)A problem report reported after a software release is withdrawn or no longer supported is excluded.
Afactor：Number of calculation periods in a year，年度化因素：在一年中计算的周期数量（注：一般为12个月）；
eSPs：Total number of customers that have reported at least one problem since the start of the software release’s eSPR Period for each distinct software release(s)or associated software updates。

eSPs：自从每一个不同软件发布或相关软件升级，在软件发布的eSPR周期内开始，已经报告了至少一个问题的客户总数；
eSp1：Total number of Critical software problems reported for the month
for software releases within their eSPR Periods；
eSp1：在其eSPR周期内的软件发布，该月致命软件问题报告的总数
eSp2：Total number of Major software problems reported for the month
for software releases within their eSPR Periods
eSp2：在其eSPR周期内的软件发布，该月严重软件问题报告的总数
eSp3：Total number of Minor software problems reported for the month
for software releases within their eSPR Periods；
eSp3：在其eSPR周期内的软件发布，该月轻微软件问题报告的总数
eSPR1：Critical early software problem reports per customer release
按客户发行的致命早期软件问题报告：eSp1x Afactor/eSPs eSPR2：Major software problem reports per customer release 按客户发行的严重早期软件问题报告：eSp2x Afactor/eSPs eSPR3：Minor software problem reports per customer release 按客户发行的轻微早期软件问题报告：eSp3x Afactor/eSPs
5A new edition of the Product and Service Category Tables is being published
产品和服务类别表R5.6in conjunction with the R5.7Point Release.These changes included:
●产品和服务类别表R5.7
Incorporating the change from SPR to eSPR within the tables
●在表中变更了SPR到eSPR；
Adding a new rule to the product category selection advice preceding Table A1 Organizations choosing a category in Families1through6or Family8cannot exclude Clause8.3 in the Requirements Handbook in its anizations without responsibility for design and development should look to the service categories in Family7for the appropriate category.
●在表A-1前增加了产品类型选择告知规则
组织选择从1族到6或8族的一个产品类型时，从整体上看，不能排除要求手册中8.3条款。

没有设计和开发责任组织应该去寻找服务类别中的7的合适类别。

Combining the four DSL categories into a single category
●4个DSL列表合并成一个产品类别；
Changing the manufacturing categories under7.7to include internal services
●修改了制造类别7.7，包括了内部服务。

Splitting8.5.1Optical Fiber(now Optical Fiber Material)into8.5.1.1Optical Fiber and8.5.1.2 Optical Glass
●拆分了8.5.1光纤（现在是光纤材料）到8.5.1.1光纤和8.5.1.2光玻璃；
Changing one of the partial outage definitions in Table A3for seven categories
●在表A-3中变更了部分中断7个类别定义中的一个。