The Cole Papers

APSU sessions focus on Y2K as worries over Atex recede

PALM SPRINGS, Calif. -- It was probably 110 in the shade, and the living was easy at the annual meeting of the Association of Publishing Systems Users held here Sept. 12-16.

Despite the distractions offered by desert hikes and myriad golf courses greening up the Palm Springs landscape, most of the two-hour sessions had few empty chairs. This may be because breakout session topics were geared toward some of the very concrete issues users face back at their newspapers.

John Pereira, newsroom systems editor at the Contra Costa Times of Walnut Creek, Calif., thought his was time well spent. "It helps to know what other people are doing that we aren't -- particularly if other sites take those things for granted," Pereira said. "I brought home a couple examples of that."

Sixty-three newspaper publishing systems users, nearly one-third of them first-time attendees, registered for the combination of business meetings, special interest groups and breakout sessions geared toward increasing both practical and planning skills.

"APSU and its predecessor, Anug, helped me get where I am today by providing a helping hand through the trials and tribulations that face a publishing systems manager," said Mark Siple, publishing systems engineer at the Columbus (Ohio) Dispatch, who also manages the group's list server. "It is my sincere wish that the organization will continue to help the new managers who are coming up in the industry."

APSU, which started life as the Atex Newspaper Users Group 25-plus years ago, reorganized three years ago under the new moniker in order to include newspaper users of various other systems that have become almost symbiotically entwined with the original Atex product. The change was a welcome one.

"I think the group needs to refocus," said Pereira. "The focus can be wider (bring in more vendors on a more equal basis with Atex) or it can be narrower (tighter focus on special interest groups such as DewarView and Atex Enterprise). Or it can do both."

But, he suggested, "I don't think the half-in, half-out, mostly-Atex approach works anymore. Many of us use third-party vendors and our business with Atex, while it is our most important vendor, is limited to certain pieces of our systems."

The structure of the four-day meetings nonetheless continues to reflect an Atex influence (the company now is Atex Media Solutions Inc. of Bedford, Mass.). On Sunday, Atex sponsored a "meet-the-users" session (closed to the press) as well as inviting attendees (including press) to a generous reception at Palm Springs' St. James Cafe.

At the closed session, attendees were "encouraged" to submit their questions in advance to the 19 Atex representatives, including CEO Larry Mihalchik and Richard Simpson Jr., the new senior vice president for North American sales and operations. (One question: "Why did you want questions in advance this year?")

Users who attended the closed-door meeting said Atex executives were told of users' concerns about Y2K upgrades, new installs, support, the future of DewarView (it's not going away), whither Edpage (it will exist in a significantly different incarnation) and the relevance of small customers (of course they're important).

The questions were more interesting than most of the answers, according to reports from users. However, when users questioned Atex's economic viability, they were pleased with both the news and the straightforwardness with which it was delivered. Long-time Atex user Bruce Adomeit, news technology coordinator at the Star Tribune in Minneapolis, was reassured by the financial report.

"There's no question now about whether Atex will be around next year," Adomeit said. "Newspapers are spending dollars, which translates to R&D funds for vendors -- and new products for customers. It's a non-vicious circle."

While the overall function of a systems users group is to address common needs, the varied backgrounds of the users at this meeting led to the implementation of special interest groups to address their diverse needs. They focused on suppliers (Autologic Information International, Cascade Systems, Edgil Associates, SoftAd, Unisys) or Atex products (Enterprise, DewarView, Press2Go, Edpage, ClassPag).

Adomeit said he believed the same good fiscal news presented by Atex is shared by the other suppliers at the conference, including Monotype Systems Inc. of Rolling Meadows, Ill., Harris Publishing Systems Corp. of Melbourne Fla., and FutureTense of Acton, Mass.

While a shared demo room was provided (at supplier cost), suppliers had to compete with special interest groups or breakouts for demo time -- which led to an occasional hallway grumble from exhibitors who felt they got less than their fair share of attention.

Jan. 1, 2000, is coming
Tick, tick, tick.

It was not just the future of the suppliers that provided fodder for conference sessions -- fewer than 500 days remain before the world finds out exactly what the Year 2000 has in store for virtually every one of the billions of computers ever made.

So scheduling a day's worth of Y2K breakout sessions was well-timed, to say the least. The sessions addressed Y2K issues through case studies, a roundtable on Y2K preparation (as related to suppliers, wire, advertisers and consultants) and developing a plan to test systems for Y2K compliance.

Generically, of course, citizens have been warned to prepare for Y2K in ways similar to the advice on earthquake preparedness found in any California phone book: Keep a six-week supply of cash, water and groceries on hand, and anticipate that power will be off so have plenty of blankets on hand.

And of course, there's the more Y2K-specific advice -- avoid flying or elective surgery come 1/1/2000. (Even the U.S. government is printing billions of additional dollar bills -- roughly a 20 percent increase.)

The consequences of clicking over to a new millennium are far-reaching, with a separate set of concerns for every domain. Breakout attendees, most of whose newspapers are already deeply engaged in Y2K projects, had no shortage of problems, advice and warnings to share:

  • Like other issues technological, when it comes to Y2K, management often talks the talk, but walking the walk is less likely. This unfortunate but predictable reality can continue throughout the Y2K project.

  • System managers and MIS directors must not only attend to ongoing, run-of-the-mill newspaper projects, they must simultaneously prepare and execute Y2K plans -- usually, at least among attendees of this forum, with virtually no additional staff.

  • System managers are among the most vulnerable employees for scapegoating should Y2K problems disrupt various aspects of the newspaper's operations. The project and responsibilities can be so demanding that, as one user quipped, "Early retirement is looking better and better."

    Consequently, some newspapers are recognizing the need for an upside to that heavy responsibility systems people carry around. While not especially common, newspapers are offering bonuses or other incentives to ensure that key members of the systems staff stick around through completion of projects -- or even midway through 2000.

    In other words, key systems folks may have unprecedented leverage in negotiating with upper management for what they need (or want), if management can be helped to recognize what's at stake.

    One user reported that his newspaper was setting the bonus at around $5000 (plus eight weeks of vacation), contingent on the success of the project.

  • So many programmers competent in Cobol, the language of choice when code for many legacy systems was written, have retired or been downsized that, according to one attendee, "Cobol is a one-word résumé." Y2K issues have created heavy demand for the skills needed to prowl through heaps of code to locate those insidious time bombs.

  • Plan to put out a minimal product in case there are problems. Figure out how many pages you'll print, and what press configuration you'll use. And it wouldn't hurt to line up some printers who can do hand paste-up, if needed.

  • Anyone involved with computers or Y2K projects should be diligent in planning and documenting test procedures. Similarly, keep records of correspondence and conversations with suppliers -- whether by telephone, e-mail, snail mail or face-to-face. (But remember, e-mail can be subpoenaed, so be careful what you say.)

  • Make sure that you know what your insurance covers and what it doesn't.

  • Avoid simultaneous projects that may draw heavily on staff resources, or complicate your ability to diagnose any potential computer problems. For example, ask your advertising department to hold off on making those annual rate changes -- whatever you do, don't schedule them for Jan. 1, 2000.

  • Make sure that staff schedules are set well in advance -- for example, critical people need to be at the newspaper at the stroke of midnight rather than at a party or on a cruise somewhere around the international date line. Also, plan your budget to cover the overtime you're likely to need.

  • Have you already installed your suppliers' Y2K upgrades? Often, Y2K-related problems are subtle, and suppliers may continue to find bugs even when their Y2K fixes have been anointed with the "complete" and "compliant" label. Keep watching your suppliers' web sites for announcements of fixes.

  • You've heard it before, but you probably can't hear it often enough: Try out your test plan well in advance. Y2K testing is likely to require an unpredictably high amount of time before you can be sure a system is going to weather the turning of the millennium.

    Dave Hard, manager of publishing systems support at Philadelphia Newspapers Inc., which publishes the Philadelphia Inquirer and Philadelphia Daily News, reported that he tried 250 ads over two weeks to get a benchmark, made necessary changes and checked again -- which was another two-week commitment.

    Originally, Hard said, he had scheduled only three days to address that issue.

  • Networked systems can add a geometric number of problems to an already complex set of problems.

  • And don't forget to include in your tests your photo desk, as well as your voice mail and telephone systems, and your uninterruptible power supply.

    Gary Ward, publishing systems manager of The State in Columbia, S.C., recommended that you talk to all of your suppliers in the last two weeks before the new year to make sure you've got all of your ducks in a row. It wouldn't hurt to make a final visit to their web sites, too.

  • Anticipate that deliveries of supplies -- from ink to paper to office staples -- may be delayed. Make sure you have adequate inventory to get you through any dry spells that may occur.

  • Consider purchasing new electrical generators. If the Y2K bug strikes your local power company, it could easily take 36 hours before big industry gets power. And in the event of a brownout, you could lose your equipment to variations in electrical frequency, resistance and current.

  • Dig out those old Telerams and Tandy Model 100s -- they're unlikely to have Y2K issues. At the same time, talk to staffers who work from home. Older PCs should be able to connect to your system, but the Bios in each may need to be reset.

  • Jim Crowley, a lawyer and systems manager of the Columbus (Ohio) Dispatch, warned users to be attentive to the language of warranties and contracts. For example, something as simple as verb tense can technically mitigate a supplier's liability or limit its responsibility.

  • Newspapers must remember that they're not just customers, they're also suppliers. As a supplier, you must anticipate the possibility of doling out huge quantities of make-goods to advertisers.

    Project management and help desks
    As pressing as Y2K is, the meeting's planners included a huge number of breakout sessions to address the more traditional users group topics, including two sessions on project management and a three-session track on help desks.

    The help desk session addressed client/server architecture, help desk applications, most common calls and expectations, distributed help in a diverse hardware/software environment, retraining, and choices about what to support and what not to support.

    In addition, there was a five-session, two-day track on programming and tools from UNIX/AIX, pagination sports agate, and telephony and computers.

    In the spirit of the multiple-system users group, there were skills-oriented breakout sessions to complement the special interest group meetings. Quark XPress users got two special sessions to discuss libraries, archiving and new features in XPress 4.0.

    Atex Enterprise users had four sessions, including a roundtable on support, discussions on system administration and a how-to for going live. And DewarView users had two sessions to learn how to use Microsoft Word's new macros.

    There also were roundtables on ClassPag, J-11s, remote computing, image setting and advertising, as well as sessions featuring case studies in sales force automation.

    "The Y2K and help desk sessions that I attended were very animated," said Hard. "And, especially the Enterprise people I spoke to were very happy, feeling they got more than they paid for."

    In addition to all these system concerns, a good chunk of the meetings was devoted to the future of APSU.

    "Going into this meeting, all of us on the board were feeling pretty down, I think. Coming out, given the response to the sessions, I'm encouraged," said Randy Jessee, former APSU president and director of news systems at The Virginian-Pilot in Norfolk, Va. "We've got to do some returning, perhaps reinventing of the group. But we're going to move ahead and continue to be a viable organization."

    Needless to say, perhaps, but APSU has made ample arrangements for discussion -- the heart of any users group -- to continue in the periods between its annual meetings:

  • The APSU Wire, managed by Paul Schulman of The Record in Hackensack, N.J., is available every Monday morning by e-mail or AP delivery.

  • Siple runs seven spam-proofed listservs for users. They provide announcements, general discussions, an e-mail version of the APSU wire, and areas devoted to Edpage, Enterprise, international and Press2Go users.

  • Members also have access to the Ask APSU and Ask Atex hotlines, run by Cecil Richmond of the Indianapolis Star, and the APSU hard copy library, held together by Sandra Fitzgerald of Indianapolis Newspapers Inc., which publishes the morning Star and evening News.

  • And of course, the association has its own web site, http://www.APSU.com/.

    Despite difficulties in making the transition from a single-supplier users group to an umbrella organization covering any number of systems, hopes remain that the group's membership and range of services will grow rapidly.

    "Two or three years ago, the group decided to open the organization up to other vendors and users of other vendors. For whatever reason, we did not do a very good job of following through," said Jim Beatty, technology manager for the Seattle Post-Intelligencer.

    "At next year's conference I think you will see several general sessions that would apply to all users, regardless of vendor -- sessions like UNIX, Photoshop, Word Macros, etc. Along with general sessions, you should see vendor-specific sessions, like an Enterprise or DewarView workshop, along with other sessions specific to other vendors."

    -- L. Carol Christopher

    Adobe
    Systems Inc.,
    (408) 536-6000,
    e-mail: service@adobe.com;
    Atex Media Solutions Inc.,
    (617) 275-2323;
    e-mail: info@atex.com.

    From THE COLE PAPERS, October 1998, Copyright © 1998, All Rights Reserved.

  • Top | ColeGroup.com | Consulting | Cole Papers | NewsInc. | Cole's Store | Miscellanea | Search
    Copyright © 1990-2012, The Cole Group. All Rights Reserved. Contact us.
    Modified date: 07/22/2002, 11:43:24 AM.
    URL: http://www.colepapers.net/tcp.archive/cole_papers_98/tcp_98_10/APSU.html