Hey Michael, Don't forget why we are where we are...his name is Mr. Graff. He created the divergence of the shows because he didn't like the way UL was running the program. This will probably not change any time soon, much like the requirement to have IR video and a flammability database. The divergence is going to continue with the RBOC's as well...I think in the next couple of years you will see SBC switch over to ANSI based specifications, which is something Larry Wong is leaning toward. It is to difficult to get Telcordia to re-examine outdated or misguided requirements, leading many test labs to do their own thing (Altitude is a prime example). I tend to look at it as job security for the time being...
See ya in the halls, Dave Spencer Compliance Engineer Oresis Communications, Inc. 14670 NW Greenbrier Parkway, Beaverton, OR 97006 (503)533-0717 Dir: (503)466-6289 Fax: (503)533-8233 http://www.oresis.com dspen...@oresis.com -----Original Message----- From: michael.garret...@radisys.com [mailto:michael.garret...@radisys.com] Sent: Thursday, November 02, 2000 11:27 AM To: nebs@world.std.com Subject: Bipolar NEBS conferences Group, I wholeheartedly agree with Steve's comments and I know I'm not alone. I'm under the impression that most firms faced a choice this year - Baltimore or Vegas. For companies with compliance staffs large enough to split coverage, sending different people to each was an option - typically more expensive. For smaller firms, this was not an option. Even for those that split attendence, you're pushing things further down the path of divergence Steve highlighted in his message - one group of people get one set of information, the other group gets another. Beyond the participants, many of the exhibitors faced the same choice - how do we staff two booths? Working within the NEBS environment can be complicated enough with out this further curve in the road. Considering deltas for Verizon, AT&T, SBC, ETSI, etc. to complete the passel of certifications and divergent documentation needed to position telecom equipment for sale in the world market today is challenging enough without setting things up for a he said/she said situation by holding two separate conferences concurrently (or two conferences at all!). When I look at other industries and how they hold conferences, it amazes me that we have come to this place. The IEEE EMC Symposium brings virtually everyone in that community together once a year for technical education and exposure to the vendors in the field - labs, equipment vendors, consultants, etc. The SEMICON shows in the semiconductor industry have a similar model with (much larger) regional shows held at different times throughout the year. In both of these cases, there is a consortium of stakeholders who come together to put things on. When contrasted with the model for the NEBS conference(s), you have one firm (Verizon or UL) working with others in the area (joint sponsors) to put something on. It's typically not open to a wide variety of participants. The agenda is largely set by a small group of people who have done it for some time. From my standpoint, a significant segment (equipment vendors) are underrepresented (or not represented at all) in the planning and execution of the show. And while the conferences in their present form have been beneficial, my sense is that they fall well short of the potential that could be achieved. I feel it likely that both of these firms (Verizon and UL) feel losing control of what they've developed by opening things up to a broader consortium is not in their best interest - I hope that this is not the case. Even if they maintain their shows - which I hope is not the case - I emplore them to work together to ensure they will be held on different dates. Beyond the conferences, there are other issues in this space that REQUIRE that we, as an industry, get together and work things out. The main issue in this space is likely revisions to the standards, but I'm sure there are others, as well. I'm interested in hearing what others have to say on this - either on the NEBS forum (thank you Mr. Curtis) or in e-mail to me directly. Material sent to me will not be shared with others unless implicit permission is stated in the text of the message. Regards, Michael Garretson Sr. Compliance Engineer RadiSys Corporation +1 503 615-1227 <end - Today's rant> "Owen, Steve" <Steve.Owen@COMPA To: "'nebs@world.std.com'" <nebs@world.std.com> Q.com> cc: "Ramirez, Al (CustomSystems)" <ramire...@compaq.com>, "Lyons, Sent by: Mike" <mike.ly...@compaq.com> nebs-approval@wor Subject: RE: NEBS 2001 Announcement ld.std.com 11/01/2000 01:56 PM Please respond to nebs While we appreciate the need for Verizon to get a head start on next year's conference, we certainly hope they can find a way to work with UL and get the NEBS conference(s) joined back into a single event. Having two conferences, especially overlapping conferences as was the case this year, puts extra strain on equipment manufacturers and others because they have to send representatives to both conferences to make sure they have a complete understanding of all the issues. One of the big topics this year (at both conferences I believe) was that of divergence. RBOCs are diverging from NEBS and diverging from each other. This complicates things greatly for equipment manufacturers. Having two NEBS conferences only serves to accelerate this trend. We urge Verizon, UL, and Telcordia to work together to bring us back to a unified conference in 2001. Regards, Mike Lyons, Steve Owen, and Al Ramirez Compaq Computer Corporation -----Original Message----- From: Jon D. Curtis [mailto:j...@curtis-straus.com] Sent: Wednesday, November 01, 2000 3:05 PM To: nebs@world.std.com Subject: NEBS 2001 Announcement Posted for Chuck Graff. November 1, 2000 RE: Verizon Communications NEBS Announcement In the fall of 2001, Verizon will be sponsoring our 7th annual NEBS conference. The conference will be titled: "NEBS 2001 - Network Challenges for the 21st Century." We are presently working on the dates and location. Our new format was well received this year, and we will continue to strive to make enhancements to the program. Since the Verizon Central Office (CO) tour was such a major success, in 2001 we are going to provide conference attendees with a virtual tour of a typical Verizon CO. In 2001, we are going to invite the Telecom industry to participate more fully in the conference. A new feature to be added, will be a series of innovative talks entitled "The Vendors Corner". Multiple vendors will be invited to present their creative solutions on complex issues in achieving NEBS compliance. To facilitate this new session equipment manufacturers and test labs are invited to submit a paper (1 per company) to Verizon. The paper should include unique aspects of NEBS compliance that your Company has experienced. This could include historical perspectives (interesting planning and testing stories) as well as lessons learned and implemented in current planning efforts for NEBS compliance. Only those who are selected will be notified after the papers are submitted. The selected presenter(s) will be allotted 20 minutes during NEBS 2001 to present their paper. All forms of media which are to be used during the presentation should be included as part of the submission. Rules for submission of papers: Initial Submission Date: January 15, 2001 (late papers will not be accepted) Initial Submission Format: Word 7.0, Times New Roman, 12 Point. No confidential or proprietary information will be accepted. Notification Date: The selected presenters will be notified by Email in February 2001. Presentation Receipt Date: Final Presentation must be received by Verizon no later than June 1, 2001 Final Submission Format: Power Point Ver 97 and any other media agreed upon by Verizon, at time of first submission. All Submissions should be sent Email to: ludwig.c.gr...@verizon.com We look forward to seeing you at "NEBS 2001 - Network Challenges for the 21st Century". The conference will be informative, educational, interactive, and most of all innovative. As more information becomes available, you will be notified. Chuck Graff Senior Member of Technical Staff Verizon Communications
