Let’s Map Quest Harmonization

Let’s Map Quest Harmonization

As with most journeys, there are usually multiple ways to get to the final destination. Shortest route, shortest time, intermediate stop offs. We all get tired of going down the same old road, day after day, week after week and as in some standard development cases, year after year. Too bad there wasn’t a GPS for standard development. Wouldn’t it be nice if we could just load in the resultant destination of our choosing…..in order to achieve U.S., CANADIAN, MEXICAN…..and or IEC in the shortest possible time?

Trying to complete some standard development projects is analogous to driving home from NEMA offices during a late afternoon snow storm……you know where you want to go, you know multiple routes and the theoretical time to your front door….but it takes forever, no matter how hard you try.

Consider the following facts…..In most cases…CANENA THSC’s consist of the same people that also participate in NEMA, UL STP, USNC/IEC TAGs, Canadian and Mexican National subcommittees, which all typically have their own separately convened meetings and end up talking about the very same topics…3, 4, 5 times. Why?  Aren’t we smarter than that?

As Industry and Standard Developers grow increasingly weary towards the initiation of future standard development efforts due to the amount of time to publication, can’t we get there by considering a more direct and sensible approach?  As an example, CANENA THSC GR and CANENA THSC WG2 activities have begun to conduct joint meetings with IEC SC17B WG2/UL task forces (including TAG members) to resolve technical differences thereby reducing the existing deviations between IEC standards and the IEC based (CANENA developed) standards UL 60947-1 and UL 60947-4-1.  Refer to my earlier blog posted on 7/27/11 and contained in the following link for related standard development innovations.  WHY NOT.aspx

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.