Learning from the Network 017 - pre-FDIS and FDIS

ISO CS has some internal processes and house style conventions that are not always obvious, and may be applied differently by different persons in ISO CS. The final editing work of the ISO CS Editors is much appreciated. There are often many small improvements in wording and formatting. The editing is meticulous, and effort is made to apply the rules with flexibility. But the ISO editors are not technical experts in the subject matter, and it is possible for errors to occur. Therefore ISO CS and TC67 have instituted (from December 2001) the 2-week pre-FDIS review:

In response to concerns that the final editing has, on occasion, introduced technical errors so significant as to cause in some cases negative voting at FDIS, ISO CS has instituted a two-week (not a day longer) review of the FDIS just prior to ballot. This is a special arrangement for ISO/TC67, and is a courtesy to the Project Leader for finding "show stopper" errors inadvertently introduced; the FDIS itself is the final proof for general review. The "Ready for ballot" document will be sent to the responsible committee Secretary.

Here is some specific feedback from one TC67 Subcommittee secretary, and we know that other Subcommittee have experienced these same situations regarding changes made in the final stages ......

- It proved to be necessary as secretary of a subcommittee to carry out a thorough check (as per the ISO Directives Part 1, 2.7.5) for errors introduced in the course of preparation of the FDIS that effect the validity of the text. Don't assume automatically that the ISO CS final editing work is without errors. Apart from errors we also commented on other changes made by ISO CS. Requests to bring some of these changes back to the original text are not always honoured (is our humble position). It was noticed (afterwards) that recently some comments from a P-member on errors during the FDIS voting period were not incorporated by ISO CS.

It should be noted that the TC and SC Secretaries are not always right, either!

- After various requests in the previous years, we received at the start of the voting period this year a marked up FDIS version of ISO CS. This cooperation was more efficient and saved of course time. We discuss now per Email our views and wishes. Compared to previous years this is an improvement, we know now in advance before publication what the final text will be.

- Some changes were needed because of a certain ISO house style, not known to us.
*We prefer a minimum use of hyphens (as per dictionary), less then ISO CS is applying. Application of hyphens not always consistent.
*Sometimes correct, sometimes not, changes were made by ISO CS from "Notes" to "Examples".
*Certain changes in standards are not in line with previous edited and published standards; not all ISO CS editors seem to have the same ISO house style.

Here is an real example of a change to a document submitted as "Ready for FDIS, made by ISO CS and published in the FDIS. Improvements have been made; but "less than" became "more than" and this would have significant cost implications for the manufacturer, or, more likely, undermine the credibility of the Standard if not corrected:

Wording as submitted "Ready for FDIS":
... one casting out of each production lot or for production lots less than 10, or 1 out of every 10 production castings shall be volumetrically examined in all critical areas ...

Wording as published in the "FDIS":
... one casting out of each production lot or, for production lots of more than ten castings, one out of every ten castings shall be examined by ultrasonic or radiographic methods in all critical areas ...

Perhaps the key learnings are [1] to maintain communication with the responsible ISO CS editor; [2] to request notification of all changes both before and after FDIS; [3] to ensure that any differences are resolved to mutual satisfaction.

This page is a part of teched within ASWS and is maintained with the TC67 Portal by

This page 'learn017.htm' was last updated on 17 July 2003.