I have been putting off the writing of this page for the last few months. Macy’s West was a big and important client, but my memories of most of the people and the projects that we did for them are hazy. To make matters worse, I have found very few notes about the installation and no photos whatsoever.
Macy’s flagship store and Union Square.
Macy’s was acquired by Federated in 1994 shortly after both companies emerged from bankruptcy. TSI had been pitching Macy’s West, the division that was administered in San Francisco, about purchasing an installation of the AdDept system for some time.
I am pretty sure that the original inquiry from Macy’s West came from Gary Beberman, who had been our liaison for the very first AdDept systems at Macy’s East in New York City (described here) and who had also consulted on the installation at Neiman Marcus (described here). He and his wife, who also worked at Macy’s, had moved to the Bay Area, and Gary had taken a job at Macy’s West. The advertising department was looking for a system, and Gary recommended that AdDept be considered. He told them what we had accomplished in Manhattan and probably also mentioned things that could have been done but weren’t.
I vaguely remember doing a demo in San Francisco, and I think that Doug Pease might have come with me. I have a vague recollection that someone from the I. Magnin stores, by then managed by Macy’s West, was in attendance. It may very well be that the Macy’s West advertising department was able to use an AS/400 that had formerly been used (probably for accounting) by I. Magnin.
In the first few years most of our dealings were with Gary. I did quite a bit of consulting on my trips to San Francisco, but he did most of the training of the users in San Francisco. Since they used hardware they already owned, we were not involved in quite a few aspects of the installation that we often were.
That arrangement was positive in that it allowed me and the rest of the people at TSI to spend more time on more productive activities. The down side, however, was that none of us at TSI had a good feel for how well the installation was going. Macy’s West seldom called for support and used AdDept for fifteen years. Our association stopped only when the corporate bigwigs brought all of the administrative functions to the Big Apple.
My visits to Macy’s: I made a half dozen or so trips to Macy’s West over the years. I flew to San Francisco on whatever airline had the best rates at the time. It might have been United, Delta, or American. The flight back was always on a red-eye.
The advertising department at Macy’s was located in a building that was a few blocks from the huge store in Union Square. It might have been on Fremont St. I stayed at a Holiday Inn that was on either Mission St. or Market St. I don’t think that the hotel is still there. It may have been sold to another chain.
I did not rent a car; I took BART from and to the airport, and I walked from the hotel to Macy’s headquarters. I may have taken a taxi once or twice. I only remember one meal that I ate in San Francisco. Gary Beberman and I walked to one of his favorite restaurants that was, I think, in Chinatown. I remember no further details. My meals on other occasions were probably grabbed in passing from fast food places.
I am pretty sure that on one occasion I took the cable car from the turnaround on Powell Street up to the top of the hill. I did not visit the Cable Car Museum. It was in my price range. So, either I did not know about it, or I might have been pressed for time.
The people: I only have notes and memories of two people whom I worked with in the first twelve or thirteen years. Emily White was the Senior VP of the advertising department from May 1996 to October 1998. Doug knew her from their time together at G. Fox in Hartford. I later worked more closely with her at Meier & Frank in Portland.
Around the turn of the century there was a major upheaval in the department. This is what I wrote in 2000:
They have recently undergone wholesale personnel changes. We have done a lot of work for them designing interfaces. We have designed very few reports. They must use a number of queries to create reports. The original training was done by Gary Beberman, who lives in San Francisco, and was our first liaison at Macy’s East.
I do not have a good feel for what they are doing at Macy’s West. I imagine that they could benefit a great deal from a few days of our time.
Dan Stackhouse was our liaison in later years. He was in charge of the local network used in the department. He did not really know much about either the AS/400 or the AdDept system, but he was able to gather specs for new projects for us and address connectivity issues.
I remember that Dan was fired by Macy’s, and he sued them over this action. He asked me to submit an affidavit explaining our relationship. I did what he asked, but I doubt that it helped his cause much. I searched the Internet for references to his lawsuit. I did not find much.
AxN: Because of Gary’s close involvement with the project, almost all of the work that we did for Macy’s West was in the establishment of interfaces with their corporate accounting systems. We customized very few reports for them.
One very unusual project was the coding and installation a menu that could be used by people in the merchandise departments to look at information about their ads. They set up user IDs for each department or group that were restricted to the programs and queries available from this menu.
The only other project that I remember in much detail was involved with AxN, TSI’s system for sending and managing insertion orders for newspaper advertising space. Unlike Macy’s East1, the people in San Francisco were very enthusiastic about delivering insertion orders via the Internet.
TSI’s initial contact with the newspapers that would hopefully be subscribing to the service was a letter written by me and signed by someone at the advertising department. I remember vividly that the woman whom we asked to sign it had no additions or changes to the letter, and she definitely wanted us to send it. However, she did not want to take the time to sign the letters herself. She said, “You can just sign them.” So, for the first and only time in my career I added the role of forger to the long list of activities that I did for the company.
The AxN installation at Macy’s West provided TSI with a few far-flung clients. Macy’s purchased Liberty House, the chain of department stores and resort-wear stores based in Hawaii, in 2001. One of those stores was in Guam, and the Pacific Daily News subscribed for several years.
The last trip: My last trip to Macy’s West was for two days at the end of July 2007. I learned that Sheila Field was the Senior VP of marketing. She had in fact been there for several years and before that at Foley’s in Houston, where I spent a lot of time in the mid-nineties. I never had met her, and she was also not available on this occasion. I did meet with many other people. I did not do a great job of learning names. Here is the unedited list from my notes:
Sheila Field.
Sheila Field2 is the Senior VP. She is from Foley’s. I almost certainly know her, but I did not get to see her on this trip. Kedar Stanbury3 is in finance, which means planning at Macy’s West. So is Von Jones4. Their boss is Chuck Allen5. The business office manager is Gary Veran6. His assistant is Diane _______. Laurie Hamilton7 is the print media director. Jennifer Hung8, Kelly ____, and Terry _____ work for Laurie.
They reported quite a few anomalies that they had been living with. I made it clear that they should report these to TSI. We always fixed things promptly. They gave me a list of areas that they were interested in using AdDept for:
Contracts.
Work group limitations for purchase orders. Does this even work? They want to make sure that the direct mail people create nothing but direct mail purchase orders. Do we have a way to do this?
The plan was for me to return in “a few weeks”. I cannot overstate how psyched they were for using AdDept more productively. My notes stated that I thought that they would approve whatever programming was needed for every item on the list.
Alas, the plan never was carried out. In February of 2009 management of all advertising for all Macy’s divisions was consolidated in New York. Within a few years none of the people mentioned above were still working for Macy’s. I don’t think that any of them made the transition to New York.
This consolidation was a major blow to TSI. I knew that there was little or no chance of persuading the consolidated Macy’s to use AdDept. Macy’s West was a big client for both AdDept and AxN.
1. For some reason Macy’s East never used AdDept for insertion orders. They did not even use it to print copies. Instead they called each paper and described each ad that they wanted to run to the newspaper’s rep. It baffled me that they could not appreciate how much faster and easier it would be to use AdDept, which had all of the information on the order, to send orders to all papers at once. Everyone who used AxN—both newspapers and advertising departments—were very happy with it.
2. Sheila Field’s LinkedIn page can be found here.
My recollection is that the first inquiry from Neiman Marcus came in early 1992 On the other end of the phone line was the manager of the advertising business office. Although I worked with her pretty closely for a fairly extensive period of time, I don’t remember her name.
She must have responded to a mass mailing that I sent after the installation at Hecht’s was under control. I addressed those letters to advertising directors. So, the advertising director must have given it to her. In our telephone conversation she explained to me how they did things at Neiman’s. I told her that I thought that our system could help her with some of their problems. I then sent her materials about how AdDept worked and tried to relate aspects of AdDept to Neiman’s situation.
She asked us to pay them a visit. I arranged for Sue Comparetto and me fly to Dallas to meet with the potential users and to do a demonstration for them at IBM’s local office. The business office of Neiman’s advertising department was on one of the upper floors of the company’s flagship store on Main Street.
When we arrived there I was surprised to find that the rest of the advertising department would not be involved in the discussion. Although Neiman Marcus was still using the system in 2014, I never spoke with anyone from the rest of the department. They used an advertising agency for most of their advertising, including newspaper ads. In fact, the lady that we were dealing with did not even want the rest of the department to have access to the system. She really just wanted a system to keep track of expenses and co-op.
The stores only had two sales per year— First Call in February and Last Call in August, or maybe the other way around. They used the traditional 4-5-4 retail calendar (described here) with which we were already familiar, but Neiman’s first month was August, not February.
My AdDept demo needed a major change of emphasis. I usually emphasized that the main reason for a centralized database was for everyone to take advantage of work done by others. She did not want the others involved at all. Also, the most impressive part of the demo was how quickly a newspaper ad could be scheduled. She had little interest in that task, which was the agency’s responsibility. Nevertheless, the reaction to what I showed was quite positive.
After the demo Sue and I rented a car and drove to Austin for a little R&R with Marlene Soul, one of her friends from high school. She was, if you can believe it, a consultant in feng shui, which she claimed was mostly about being organized.
Marlene took us to a comedy club in downtown Austin, which was definitely a swinging place. I also remember sitting around at her house while she tortured her cat with a long flexible semi-rigid wire that ended with a feather. The slightest twitch made the feather jump and fly.
I made a note to myself to buy one of these when I arrived back in New England so that I could use it to drive my cantankerous cat Woodrow crazy. I did, and it did. He had to hide under the couch so that he could not see it.
The following morning we went birding with Marlene and a group that met every Saturday morning. I was exceptionally bad at it. I have had poor vision since the third grate, and I have always been notoriously bad at finding things anywhere. However, this gathering did spark enough interest in me to become a little more knowledgeable in ornithology.
Upon returning to the office I spent a couple of days putting together a detailed proposal for Neiman Marcus. It did not include as much custom programming as usual. The main objective was for the AS/400 to be able to generate a file to be used by the expense payable system on the mainframe.
The business office manager accepted the proposal a short time after receiving it. I sent her a software contract, which she signed. I then ordered the hardware and system software from IBM and we received an installation date. I knew that we would not have the interface done by then, but we would need some data to test the interface anyway, and there would be no data on day one.
From our perspective this was by far the easiest sale that we had ever had, and the installation, which took place in August of 1992, also went rather smoothly. I had to spend quite a bit of time fine-tuning the coding for the incredibly complicated interface with their corporate financial system. I did not care. I loved to do that kind of work because, once it was in place, the chances of them scrapping the system were minuscule1.
People in the IT department2, however, were furious that the lady from the advertising business office had signed a contract with TSI without consulting them. They were nice enough to me, and they were quite cooperative about establishing the interface between the two systems. However, her career at Neiman Marcus did not last long after AdDept was installed and working smoothly.
The key to the success of the installation was effecting the financial interface. It involved a considerable amount of two-way communication between AdDept and the corporate mainframe. Gary Beberman, who had been TSI’s liaison for the first AdDept installation at Macy’s East (described here), was extremely effective as the go-between for TSI and the mainframe programmers.
I found this list of the steps involved in a document written in 2000:
1. A list of general ledger accounts is downloaded. AdDept’s general ledger account table is updated. 2.A list of departments with the accompanying hierarchy is downloaded. The department table and the rest of the hierarchy is updated. 3. Expenses are uploaded to the accounts payable system. The accounts payable system feeds the general ledger. 4. Co-op transactions are also uploaded to the accounts payable system. The accounts payable system feeds the general ledger. 5. General ledger transactions in the advertising accounts are downloaded at the end of the month. An AdDept program compares the downloaded transactions with the uploaded transactions. A list of exceptions is printed. Additional transactions are placed in a batch file, which can be converted to real AdDept transactions.
The walk down to Dealey Plaza is an easy one.
I made a fairly large number of visits to Dallas during the installation period. Thereafter, a few years would sometime go by between requests for visits. Here are a few memories that I have maintained of those trips.
Neiman’s flagship store at Christmas time.
In the nineties I spent a lot of time in the American Airlines section of the DFW airport. My favorite restaurant there was a Mexican cantina.
I also spent a lot of in autos driving between the airport and either Dallas or Fort Worth, where TSI had several clients. Sometimes I took a cab; usually I rented a car from Avis.
On my first solo trip to Neiman’s I was a little late and a little lost. I crossed Main Street in the middle of the street. A cop stopped me with every intention of giving me a ticket for jaywalking. I was polite, however, and he let me go with only a warning.
One of my early visits was in December during the running of the Dallas Marathon. I went out for a jog and watched some of the real runners near the finish line. This must have been on a Saturday or a Sunday.
The temperature on that day was around 30. I was wearing stretch leggings, shorts, a tee shirt, and a nylon jacket. Most of the real runners were wearing shorts and singlets. At Neiman’s on Monday the business manager, who was a originally from Pittsburgh, confided to me that she and her husband were concerned about whether the cold weather might harm their child if they let her play outside. She admitted that no one in Pittsburgh would have thought twice about their kids being out for hours in such weather.
On another occasion I walked to the State Fair grounds on a Friday evening. I was surprised to discover thousands of people celebrating Juneteenth. I had never heard of this event before.
One summer evening after working at Neiman’s I took a stroll down to Dealey Plaza, which is the the location of the ramp to I-35. I wanted to conduct a personal investigation of the interchange, the “grassy knoll”, the Texas Book Depository (which had been converted into a museum), and the other locations associated with the assassination. A few minutes earlier the fatal presidential motorcade had passed right by Neiman’s flagship store, which is .6 miles from the plaza.
One day after the system was operational the business office manager drove me to lunch for some authentic Texas barbecue. I cannot say that I was very impressed. I have never understood the idea of cooking all of the flavor out of meat just so it could be coated with barbecue sauce.
Neiman’s made a big deal out of Christmas. Not only did they publish their famous catalog with one outrageous gift idea, but they also sponsored an evening in which their VIP clients could shop without dealing with the riffraff. The store open that evening only to those who were sent an invitation. Each was assigned an employee to tour the store with them. I am not sure what the employees were expected to do. I looked for members of the Ewing family, but I did not see any.
On my visit on September 9, 2000, the temperature reached 109°. It was also the thirty-fifth day in a row with no rain. That was the day that I understood why the streets in Texas are almost all concrete, as opposed to asphalt. Anything that was paved with asphalt turned gooey when the temperature got that high.
I did not actually work with most of the subsequent Neiman’s employees enough to burn in lasting memories. I did find some notes that provided me with some information on some of them;
Jeff Netzer.
I was surprised to discover that many of the successors to the female business office manager mentioned above were Aggies, that is, graduates of Texas A&M. The first was Jeff Netzer3, who worked at Neiman’s from 1996-1999. He called TSI a few years later when he was employed at Sewell Automotive Company. I saw Jeff there when they invited me to assess the possibility of us designing a system for this company. This experience is described here.
The second Aggie was named Brian Harvey4. He worked in the advertising department from 1998-2000. I met him in 2000, but I don’t remember him.
After Brian’s departure the advertising business office was run by Alea Montez. I remember that she called the office for support several times. I don’t think that I ever met her.
The last Aggie was Brian Davis5, whose title at Neiman’s was Media Analyst. I don’t remember him at all. I don’t think that I ever met him in person.
A striking omission in this list is everyone in any other area of advertising. I never succeeded in interesting anyone in even considering what TSI had done for so many others in similar positions.
I had quite a bit of contact with a number of IT people at Neiman’s. I met a few in person, but I don’t remember any names.
In the 2000’s Neiman’s hired an AS/400 consultant to help them with connectivity and to upgrade their system. We had a good relationship with him, but I don’t remember his name.
1. In fact, the AdDept installation at Neiman’s lasted longer than that of any other client. Part of the explanation for that was that Neiman’s was one of the few AdDept clients that was not bought out by another company. When we closed TSI’s doors for the last time in 2014, Neiman’s was still using AdDept. For all that I know, it may have continued after that.
2 The IT people worked in a building in Las Colinas, a few miles from the flagship store in downtown Dallas. I went there a couple of times and met a few people there.
She knows there’s no success like failure, and failure is no success at all.—Bob Dylan’s “Love Minus Zero/No Limit” Continue reading →
In the early years of the marketing of TSI’s GrandAd system for advertising agencies I distinctly remember being disappointed that the second installation (at Potter Hazlehurst) was even more difficult than the first. This tendency was definitely repeated with the system for retail advertising departments, AdDept (design described here). The second installation, which was began in the spring of 1990, was much more problematic than the first.
I had never heard of P.A. Bergner & Co. I now know that the chain’s original store was in Peoria, IL. After it acquired the Boston Store chain in 1985, the company moved its headquarters to the upper floors of the Boston Store in downtown Milwaukee. In 1989 the company also acquired the Carson Pirie Scott stores. The corporate management of all of these stores, including all aspects of advertising, was handled in Milwaukee.
I was not yet familiar enough with the nature and history of American department stores to understand the importance of the timing of that last acquisition. Bergner’s advertising department was presumably given a budget to acquire a computer system to enable it to handle the absorption of the Carson’s stores. The money probably had to be spent in 1990. Any portion that was not spent vanished. Little or nothing for future years was budgeted. I came to understand these things later. I wish that the situation had been spelled out to me.
Moreover, Sue and I continually tried to portray TSI as a strong stable organization that was especially good at big projects. That was true a few years later, but in 1990 the company consisted of:
Me,
Sue Comparetto (who basically wrote checks, closed the books, and did presidential stuff),
Sandy Sant’Angelo, who could do simple programming, of which there was still quite a lot,
Kate Behart, who helped with marketing and served as day-to-day contact with some clients,
Denise Bessette, who worked only part time, all of which was devoted to projects for Macy’s East,
One or two administrative people.
The only way that the whole Bergner’s project could be implemented on time was for me to do almost all the programming work myself. The closest that I came to admitting this to Bergner’s was when I told them that Sue was terrible about time. Anything with a deadline had to come through me. Dan Stroman was quite taken aback when I said this. I was also pretty shocked when I had discovered this, but there was no sense in denying it.
Maybe I should try to grow a big white mustache.
Several IBM reps were involved in the sale of the AS/400 for the AdDept system to Bergner’s. The one whom I remember best was Sue Mueller. One of our last meetings took place shortly after the trip that Sue Comparetto and I took to England (described here). Sue brought to Milwaukee a copy of the magazine. When Sue Mueller saw my picture on the cover, she literally did not believe that it was a photo of me.
My recollection is that IBM sold Bergner’s a model B30 of the AS/400, the same machine that Macy’s was using. I think that it also had the faxing software and the modem that it required, and it definitely included OfficeVision/400, the word processing software.
Our primary contract person at Bergner’s during the negotiations was Dan Stroman1, who was either the advertising director or the production manager. He arranged for me to meet with the individual managers—production, ROP, direct mail, and business office. Either I did not do a very good job of collecting the requirements from them, or they did not do a good job of describing what they needed.
We tried to emphasize to Dan the importance of having one person designated as the liaison between TSI and the users. At first he wanted the liaison to be a person from the IT department. However, everyone agreed that the person whom the IT department assigned to the project, Kee-Huat Chua, would never have worked for many reasons. So, the job was given to Sheree Marlow Wicklund2, who at the time was the manager of the merchandise loan room.
I don’t think that in 1990 TSI yet owned the tools to produce detailed design documents. If we did, we certainly did not use them for that purpose in this installation. I merely described in the proposal what we planned to do.
The project was focused on quite a few things that required significant design changes.
Bergner’s stores had four or five logos (the name on the store’s signs). So, a table for logos had to be created, and separate versions of each ad were needed for each version of an ad.
On some pages of some direct mail catalogs and newspaper inserts the merchandise varied by market. That is, one “block” on a page might show items from one department in one market and different ones in others. Bergner’s called these “swing pages”. Providing a way to handle them meant, among other things, that the entire approach to measuring books needed to be rethought.
Bergner’s wanted to use the system to “traffic” production jobs. We proposed to do this by defining lists of steps, which we called “production schedules” and “timetables”—date relationships to the release date (the date that the materials were delivered to the printer or the newspaper). This approach worked well for setting up the original schedule, but the traffic coordinators did not like to use it, and I never did figure out how we could make it more useful for them. Sheree was certainly of little help.
Macy’s newspaper coordinators ordered their space reservations by phone. Joyce Nelson3, the newspaper manager at Bergner’s, sent a schedule to each paper once per week with all the ads, positioning requests, and other notes for every ad to be run in that paper over the next week. She wanted the system to fax them all. I was very happy to add this feature.
Bergner’s employees wanted to be able to record comments in many places. These requests were often difficult to accommodate. I devised a trick to handle some of them. IBM’s office-vision software had the ability to run programs within documents and to display the output sent to an output queue within the document instead! The parameters for the program could even be included in the document. So, a form letter could be created for sending detailed information about an ad to a group of people. The text surrounding the report could be changed every time. I especially liked this approach because I was fairly certain that it could not be replicated on any other system.
I was signed on to our B10 all day every day.
By the time that the software was delivered, TSI had a small AS/400 in its office, and we quickly established peer-to-peer communication with Bergner’s system. This allowed us to sign on to their system from TSI’s office and to send programs directly from our AS/400 to theirs over the phone lines. I worked all day on programs in TSI’s office and installed the ones that I deemed to be working early in the morning. This was feasible because our office was an hour ahead of theirs.
I communicated with Sheree via the AS/400’s messaging system, which supported both plain text and word processing documents. Kate communicated with Sheree by telephone. I expected Sheree to interact with the users and managers personally. Instead they had weekly meetings that all the managers attended. They appear to have been mostly gripe sessions. Sheree took notes and sent me a list of the issues reported. She did not send one document per area; all areas were included on one document.
I liked the idea that we received a written record of the issues, but my responses expressed my exasperation at some of them. Often users were still complaining about things that I was positive had been fixed. In other cases they had changed their minds about decisions that they had previously made and we had implemented. I responded to all of the issues that Sheree had sent in one document. I did not anticipate that Sheree would share all of my responses with all of the managers. I guess that I should have anticipated that possibility, but I had not worked at a large company for seventeen years, and the meetings at Macy’s were usually limited to one area at a time.
At any rate, I ended up on several shit lists because I responded negatively in print to some managers’ comments, and all of the other managers got to read. It never occurred to Sheree that if I had wanted everyone to read my answers, I could easily have sent the document with the responses to each of them.
More than a scribe.
Privately I was outraged that Sheree had violated what I considered to be a special relationship between the developer and the liaison. I expected her to be a strong advocate for the system when working with the users and an equally strong advocate for the users when speaking with us. She evidently considered herself more of a project manager whose responsibility was to organize and keep everyone informed. She did this. However, for such a complex system with such a compressed timeline, this was just not enough.
I talked with Dan about the situation, and I pleaded for a different liaison. He said that it was out of his hands. Ouch.
The installation at Bergner’s should have been a great success story. Some of the areas—notably the newspaper and loan room areas—were working very well in record time. The other areas proceeded much more slowly. I felt extremely frustrated by the incredibly inefficient process upon which Bergner’s insisted.
Bergner’s put the X back in Xmas.
Nevertheless, by the time of my visit in December of 1990 the ill will had dissipated to the point that they invited me to the department’s Christmas party. I could hardly believe it. A live band was playing. There was a mosh pit! The young people who worked in the creative and production areas were going crazy. The old fogeys with whom I dealt were much more subdued.
That evening Joyce Nelson asked me to give her a demonstration of my technique of throwing playing cards. She produced a deck of bridge cards, which are not as easy to throw as poker cards. However, I was sure that I could spin one at least twenty yards. Unfortunately, the ceiling was too low. To get a card to go a long way, its flight must describe a loop. I could not possibly throw a card at high velocity without it crashing into the ceiling or floor after a few yards. I had to demur, and I never got another chance to display my prowess.
Not for jugglers.
I located in our basement a few pages of memos written by me or Sheree about the installation. Kate had written notes in the margins. At a distance of thirty years (!) I could not understand the details of what was being discussed, but it was evident that I was trying to juggle a large number of balls at once. However, the use of the test system and the attitude of some managers made it seem like the balls were all coated with fly paper.
At some point in 1991 Bergner’s agreed that we had met the terms of the contract, which, by the way, was TSI’s simple version with only a few amendments. They made the last payment and also indicated that they also wanted to prepay TSI’s software maintenance for, I think it was, a year. They asked us to send them an invoice for this, but they wanted the description to be something like “Miscellaneous programming projects”.
The proverbial wolf was at TSI’s door again, and we had never turned down a check. So we did what they asked.
Bergner’s also approved quite a few enhancements that TSI had quoted. These projects were not covered by the original contract. So, I was still very busy with writing and installing all of the new code.
We used part of the money to hire Tom Moran to help with marketing. His role at TSI is discussed here. Perhaps I should have hired a programmer instead. I was more confident in my ability to produce an abundance of good code than my skill at closing sales. Also, I could not afford to devote the time necessary to train a programmer.
Bankruptcy: By August of 1991 Bergner’s had not sent TSI any checks in several months. We learned that the company had filed for Chapter 11 bankruptcy. My recollection is that they owed us more than $10,000. We had no experience with this; none of our previous clients had ever done this.
Our first experience.
Dan told me on the phone that Bergner’s would not be allowed to pay any invoice that was received prior to the default date and was still open. I realized immediately that they must have suspected that this was coming. That “miscellaneous” check was done that way so that we would be obliged to provide support for programming projects that they never paid for.
Maybe no letter?
I wrote them a letter that said that we intended to apply the money from the miscellaneous check to the projects that we had delivered but they had not paid for, and we would begin to bill them for software maintenance. The Senior VP of advertising, Ed Carroll3, was furious at me personally. Dan Stroman called me about the situation. He said that I didn’t know who our friends were.4 Well, he might have been a friend, but I don’t think that many people at Bergner’s qualified for that distinction. I told him that our legal advisers (Me, Myself, and I) said that money given on deposit like that could be applied to open invoices. Dan did not respond to that. Instead, he asked if he wanted us to continue as a customer. I told him that I wanted them to become a paying customer.
I don’t remember the details of the rest of this episode. We continued to support the users at Bergner’s. They asked for a few more projects. We felt compelled to bill them at higher rates to try to make up for the money that we had lost.
I learned later that much of the retail advertising community considered Ed Carroll a sleazeball. What his advertising department did with that invoice was probably illegal or at least against company policy. He resented that what I proposed would make him look bad.
Test Environment: I found a letter dated May 13, 1992 that Kee-Huat Chua sent to TSI. It began with these two sentence fragments.
As you are aware of PAB’s intention to set up separate program environments for the AS/400 system. What it entails: one environment for intensive testing by users and one environment for developer/programmer to perform units [sic] test on the program module(s).
It then describes electronic forms that we needed to fill out before we made changes to the system. After we sent the form to him, he would copy the entire production library and the entire data library to the test environment. When this would happen is not designated in the letter. It could not be done if anyone was using the system. So, presumably it would be done at night.
After the libraries were duplicated, we would be allowed to sign on and implement the changes. We were also supposed to test them and send him a memo documenting that we tested them.
I guess that the users would then test them, but the letter does not mention it. It also does not mention how the changes will get into the production environment.
However, it does emphasize (in bold print, capital letters, and underlines), “NO COMPILING OF PROGRAMS ALLOWED DURING OFFICE HOURS UNLESS UNDER SPECIAL CIRCUMSTANCES; when making program modification.” Those special circumstances are not described.
Kee also included a list or reasons why this approach would be good for “TSI/Programmer:”
– To better perform & concentrate on their development. – Less interruption and delay for development tasks. – Secure production application: AdDept.
Although I considered this additional requirement a breach of our contract, I did not feel that I could refuse outright. I was sure that no matter what the missing details were, it would slow down our delivery of projects that they had requested by 50 percent or more. It also pretty much excluded them from ever getting new releases of our software.
This time Dan called me. I told him that we could have done it using test libraries from the beginning, but the project would have been hopelessly behind schedule if we had. He replied that he thought that that was what I would say.
I didn’t say this to Dan, but I also knew that this approach guaranteed that we would be doing a lot of extra work for which we would not be compensated. I cannot imagine who would really benefit from this. The alleged benefits for Bergner’s were equally bogus:
– To stabilize the “live”/production system both in the short run and the long run. – To adhere with PAB’s standard of implementing computer systems established by Management Information Systems – To encourage more users involvement with the implementation of the application.
I was mostly thankful that they did not come up with the idea of inserting this guy from the IT department between us and their system while we were still working on the base system specified in the contract.
I made lots of mistakes, but I also fixed problems very rapidly.
This was a good example of why it always took IT departments ages to develop and install new software and why so many companies ended up outsourcing the IT department itself. My shoot-from-the-hip approach admittedly required some pain and frustration for a short period of time. However, it had worked extremely well in the ad agency environment, and it would also eventually prove effective in many other retail advertising departments.
If only it were that easy.
Documentation and Ease of Use: Macy’s East’s long and involved contract did not require TSI to provide written documentation of how the programs worked. Although they demanded a commission for any AdDept systems sold in the first year after it was signed, they considered the whole project a custom job.
I no longer possess a copy of our contract with Bergner’s, and so I cannot check on whether it specified anything about documentation or not. I doubt it. Producing a user’s handbook that covered every eventuality of every aspect of the system would have been an overwhelming undertaking that got worse with every program change or new module. Instead, I made a conscientious effort to try to make the system fairly easy to use.
The layout of all of the screens was consistent.
The top three lines of data entry screens described the purpose. The screen number was in the upper right corner.
If a new item was being created, the word “New” was also in the upper right corner, and it blinked.
If the item already existed, the user ID, date, and time of the creation and last change were displayed.
All binary fields required the entry of Y or N. The 5250 standards used by all of the terminals and PC’s did not support check boxes.
The options for all fields that would have had radio buttons on a GUI (graphical user interface)5 were listed on the screen.
Two function keys were available at all fields that were verified against the database. F2 produced a detailed description of the field. F4 called a program that allowed the user to list and from the existing entries. Exiting these programs returned the user to the original screen with the cursor position maintained.
All dates were entered in the form MMDDYY.
All fields were verified when the Enter key was pressed. Any entries that were not valid were highlighted, and the cursor was positioned there.
The format for all reports was as consistent as possible. The report number was almost always in the upper right corner.
A list of the names of the most important tables and their key fields was provided for querying purposes. The names of the fields was consistent from table to table.
The biggest gripes were the lack of a user handbook and that the system was not “intuitive”. I considered trying to write a handbook, but I could not figure out a way to do it. Furthermore, I could not even start on it until all the programming required in the contract had been completed.
In all honest, I have never seen a system that was intuitive. The text-based user interface, which the only thing IBM provided at the time, probably seemed difficult to people who had never learned the keyboard.
I thought of a few ways to provide better documentation later, and we provided them to both new and existing clients. By then, however, Bergner’s had decided to try to find a different system.
Camex Interface: We were not the only software developers who felt Bergner’s wrath. When the AdDept installation began, Bergner’s produced its ads using Camex software on very expensive workstations from Sun Microsystems. Macy’s East did, too. Both of them wanted Camex to work with us for a two-way interface between the two systems. The story of how this project never got off the ground is recounted here.
Epilogue: The story of the installation has at least four epilogues:
I think that after the bankruptcy brouhaha Bergner’s hired Gary Beberman, who had done a fantastic job as our liaison at Macy’s East, to help them. He called me about it. I told him that they had a good system installed, but we did not get along with some of the people there. I told him about the restrictive process that IT had set up for me to use. He was sympathetic, but he had no advice about how to turn around. He also warned me not to use Bergner’s as a reference account.
Bergner’s advertising department tried unsuccessfully to replace AdDept for years, maybe even decades. I went back there for something some time in (I think) 1992. Joyce told me that they now had two systems, a pretty one and an ugly one. She said that she preferred the ugly one that worked.
Bergner’s emerged from bankruptcy in 1993. They paid us pennies on the dollar. In 1998 the company, then known as Carson’s, was acquired by Proffitt’s Inc., which later became Saks Inc. All of the other Saks Inc. divisions used AdDept. Carson’s was merged with Younkers and Herberger’s, which both had successfully used AdDept. The resulting entity was called the “northern division”. Saks Inc. sold the division to the Bon-Ton in 2005, which closed down all 267 stores in 2018. During that entire disastrous sequence of events Ed Carroll ran the advertising department in Bergner’s. Carson’s, the northern division of Saks Inc., and the entire Bon-Ton.
Some time early in the 2000’s I unexpectedly ran into Ed and Sheree (?!) at Saks Inc. in Birmingham, AL. Steve VeZain, who was in charge of the corporate marketing group, had asked me to come there for some other reason. Sheree was cordial to me, but when Ed saw me he barked, “What are you doing here?” More about this event is documented here. I never saw Dan Stroman again. I have no idea what happened to him.
Miscellaneous: Here are a few things that I remember about the installation:
Lovable Bucky?
Dan and his wife had Sue and me over for supper on evening. She was a big University of Wisconsin fan. I remember her saying “How could you not love Bucky Badger?” I thought that Bucky Badger was ridiculous then. I have subsequently learned to hate him. The Stromans’ house was on a large pond. Dan had a boat. I don’t know why, but he revealed to me that he had had a vasectomy.
Bergner’s insisted that I stay at the Mark Plaza Hotel when I was in Milwaukee. It had a doorman. He held the door for me even though I always had a free hand. I guess that that was his job, but it annoyed me. I have always hated it when people offered an unsolicited service and then expected a tip.
One evening I tried to get some work done in TSI’s office, where I had “passed through” to Bergner’s system. After a while I became too drowsy to be productive. So, I intended to end my remote session. Unfortunately I keyed in PWRDWNSYS on a command line rather than ENDPASTHR. I accidentally shut down their system! I had to call the IT support line in Milwaukee and talk someone through starting it up again from the system console.
The German food in Milwaukee was unbeatable.
One day Dan Stroman, a guy from production whose name I don’t remember, and I went to lunch at a Thai place. I didn’t think much of it.
I had fun jogging down by Lake Michigan in the evenings.
Failure: This entry has made me think about the nature of failure.
For about thirty-five years I designed, wrote, implemented, documented, and supported software systems. In the fifteen-year period that we actively marketed AdDept, we had thirty-five installations. Of all of those, the only one that I would characterize as a failure was the one at P.A. Bergner & Co.
I probably made mistakes. I tried to work on everything at once. I wanted to provide each stakeholder in the department with something to show that we were making progress.
Perhaps I should have insisted on doing one media at a time. Would Bergner’s have accepted that strategy? Who can say? They put a lot of pressure on us to get the entire project delivered. They seemed to have underestimated how much new programming they wanted. I am certain that I never said that we had already written software that was not actually working, but we were definitely trying to be optimistic. We desperately wanted the job. Maybe some statements that we made got misinterpreted.
I often took the “one area at a time” approach in other installations. We usually started with ROP and quickly achieved successful faxing of insertion orders and printing of schedules. That served as a confidence booster. If we had achieved important objectives quickly, perhaps no one would have suggested that wretched test environment. That approach would probably have also eliminated the weekly committee meetings. If my reports had been to one manager at a time, I would have been more careful in my comments.
In some future installations I designed one-time programs to help with the initial loading of tables by reading in user-supplied spreadsheet files. It did not occur to me to try this at Bergner’s, and no one suggested it. I am not sure that they actually had any files that I could have used.
I learned my lesson. In all subsequent AdDept presentations, I emphasized what I called “our dirty little secret”, to whit, the biggest factor in determining the success of an installation was the person who acted as liaison. I also took pains to specify what precisely the liaison’s responsibility and traits should be.
I also recognized that I should never have put in writing anything even slightly derogatory about a third party. Thereafter I always assumed that everyone would read every word that I wrote.
I learned one other lesson from this experience. I needed to investigate prospective clients more closely. From then on I asked prospective clients why they had decided to pursue automation of their advertising department at this point in time.
I can’t be too hard on myself, however. I don’t know of anyone else who managed to automate two advertising departments of large retailers. Over the years I installed thirty-five AdDept systems.
1. I never saw Dan Stroman again. I have no idea what happened to him. I suspect that he must fallen out of Ed’s favor. He may have been blamed for selecting TSI to design and implement the administrative system and for the collapse of the Camex interface project.
2. Sheree (pronounced like Sherry) Wicklund now goes by Sheree Marlow. Her LinkedIn page is here.
Ed
Joyce
3. Joyce Nelson worked for the company until 2004. Her LinkedIn page is here.
4. Ed Carroll, one of the very few people in my life who really hated me, died in 2016. His obituary is here.
5. IBM did not provide OS/400 with a real GUI until more than a decade later, and even then what they suggested was slow, resource-intensive, and lame compared to what people were accustomed to on PC’s and Macs. TSI’s screens maintained the same format throughout the history of the company because we never found a way to convert the hundreds of screens that we had to produce something that was reasonably attractive. The approach that came closest was to write everything over in a language that used CGI for HTML files. That was how AxN worked.
In early 1988 Sue Comparetto, who had handled the GrandAd accounts in New York City, received a call at TSI from IBM’s Manhattan office. One of our contacts, Quique (KEY kay) Rodriguez1 wanted to talk with us about Macy’s New York. Its advertising department had been using software programs on an obsolete System/34 to keep track of its advertising expenses and income. The system had been developed internally by people who no longer worked for Macy’s. Documentation was minimal.
Macy’s New York had recently merged with Macy’s New Jersey. The new entity was called Macy’s Northeast, and its offices were on an upper floor of the “world’s largest store” on 34th St. in Manhattan. The advertising department’s existing system had already been stretched to the limits and would never be able to handle the increased load. Moreover, the users were not happy with some aspects of the code. Alan Spett2, one of a very large number of vice-presidents at Macy’s, had been provided by corporate with a budget for replacing or updating the existing system.
This may have been the last time that I actually jumped.
I jumped for joy and clicked my heels when I heard about this opportunity. For some time I thought that companies that produced and/or scheduled their own advertising represented a attractive untapped market for the skills and knowledge that we had acquired from our seven years works with advertising agencies. Evidently I was right. We had never approached any of these departments because I had absolutely no idea how we could even identify which companies created and placed their own ads.
Coincidentally, IBM had just announced a new mini-computer, the AS/400, to replace the System/36 (which had replaced the System/34 in 1983). This announcement and its implications for TSI are described in considerable detail here.
The train brought us to Penn Station, only a block or so from Macy’s.
I made several trips by Amtrak train to the city to document the requirements for the new system. Sometimes I was accompanied by Michael Symolon, TSI’s marketing director at the time, and sometimes by Sue. We soon learned that Macy’s advertising department did everything that an ad agency did except keep track of the amount of time spent on individual production jobs. In fact, they had an advertising agency name that they used when ordering media. In addition, the department had many other needs that regular ad agencies lacked. Specifically, they were required to allocate both production and media expenses to the selling departments. These departments were identified by three-digit numbers. Each was assigned to an administrative group that also had a number. In turn there were three levels of vice-presidents who “owned” administrative groups3.
Macy’s also billed the merchandise vendors (Clinique, Ralph Lauren, Levi’s, etc.) a portion of the expense for ads that featured their products. The cost to the merchandise department was net of these “co-op” billings. The contract could be for a percentage of the media cost or it could be a fixed amount.
The first phase of this job entailed providing Macy’s with everything that they needed to get the ads in all media scheduled—printed schedules in the format that they liked, “insertion orders” (called “delivery tickets” by other retailers) to accompany the materials sent to the media vendors, and so on—in every media. It also included keeping track of expenses and co-op for each level of the merchant hierarchy. There were several different formats that they used for reporting these breakdowns.
I envisioned that the creation of any ad would consist of five steps:
An ad number within the season and a version code that was usually blank would be entered, or ad numbers could be assigned by the system by pressing a function key.
A new ads screen allowed selection of the ad type (e.g., black-and-white ROP) and entry of the primary run date, which must fall with the season.
The other information that applied to all of the media for the ad would be entered on a header screen. This varied by type of ad, but each screen included selection of a pub group—a list of newspapers, markets, or stations.
A media selection screen showed one line for each pub in the pub group with dates, quantities, rates, and other costs or discounts. Any line could be edited or deleted. Additional pubs could be specified.
A participants screen to provide the list of departments or groups for the ad with the expected cost percentages and co-op amounts for each.
Storewide ads could be entered rather quickly. Ads with many departments or groups might take a few minutes. This approach was warmly received. The employees were accustomed to specifying the participants for each pub in the ad.
After the schedule was created, any aspect of an ad could be changed, or the ad could be killed, (in exceptional cases), deleted, or moved to a different date. New ads could be defined. Once the ad was run, the actual participants and the actual co-op could be provided. History records with dates, times, and user ID’s were kept for all changes.
How did Macy’s determine the percentage of the actual cost of each ad that was to be allocated to each department or administrative group? The process astounded me. In one room4 were seated from three to five clerks. Each was provided with a stack of newspapers and a list of ads that were scheduled to be run as well as lists of department numbers and the numbers of administrative groups. They looked through the newspapers to find the ads that Macy’s had run. They then measured—with a ruler!—each of the “blocks” in the ad to see how many columns wide (six columns to a page) and how many inches deep (i.e., vertically) the block was. They then entered the column inches for each block. For blocks that were not specific to a department or group, a special “storewide” department #999 was created. The total of the measurements must exactly equal the total size of the ad.
My approach changed this process so that the clerks measured ads, not insertions (the ad in a specific paper). If the ad was already measured, the clerk could see what had been entered, who did it, and when.
A similar process was also required for each page of each direct mail piece and newspaper insert. The ads for other media were not measured, but actual percentage breakdowns were recorded.
Similarly, the actual co-op dollars received from the selling departments (a process called “turning in”) could be recorded. Lists of missing co-op could be printed.
The most important financial reports for Macy’s compared the committed co-op and costs with the actual measured costs and actual co-op. They could be run for any or all merchants (the vice presidents who owned the departments) and any or all media.
Camex was located at 75 Kneeland St. in Boston.
In addition to all of this, Alan had ideas for other modules such as an inventory system for the merchandise used for photo shoots in the studio in Newark and a system to manage the shoots themselves. He also wanted us eventually to work on an interface with the Camex system that Macy’s used to create the images for the ROP6 ads and books. Thank goodness these ideas were not included in the original contract.
TSI’s GrandAd system for ad agencies had been built around a file for ads, the key to which was a three-digit client number and a five-digit job number. So, each client could have up to 99,999 jobs. For the departmental system, which I decided to call AdDept, I designed a similar structure, but, since Macy’s itself was the only client, I made the three-digit code stand for the season. 891 meant spring of 1989. 892 was fall of 1989. Eventually, a one-digit code for the century was added as well, but otherwise this proved to be a very feasible approach.
Many other structural changes were necessary. The most significant one was the designation of a one-character version code as part of the unique identifier (key) to the main media file. This could be used to make distinctions that varied by pub (media vehicle). For example, one item in an ad might be “swapped out” for a different item in another ad. The catalogs sent to some markets might not include some pages.
The new table for the pub groups mentioned above allowed Macy’s to identifying papers in which they often ran the same ad, e.g., the tabloids. There was no limit on the number of pub groups, and pubs could be in any number of pub groups.
I did not mention this to anyone at the time, but while I was gathering requirements, I noticed a very serious flaw in the design of Macy’s existing software for the S/34. The same ad was run in a few papers, but each insertion in each paper was given a separate ad number. The clerks doing the measuring were each assigned one or more newspapers. They measured and then entered into the computer the amount of space for each department in each ad. The person next to them might have already measured the same ad in a different paper, but there was no way for them to use that information; they had to key it all in again. So, with the S/34 design the increase in the number of papers added by the merger would more than double the work in allocating costs. My approach would decrease the work even with more papers. They would only measure the ad in one paper.
How great was this? The ROI for this feature alone would easily surpass the cost of the entire system in the first year!
How was such a colossal blunder possible? Well, the S/34 programs were designed for Macy’s New York, which advertised almost exclusively in only three papers: The New York Times (a broadsheet), the Daily News (a tabloid), and Newsday, a Long Island newspaper with a unique shape. Each of these would require separate versions and therefore separate measurements. However, all of the new papers were either tabloids or broadsheets. There was no need for separate measurements.
At some point in mid-summer TSI needed to do a presentation for Macy’s at IBM’s office on Madison Avenue in New York. There was no competition; no other software developer wanted anything to do with this project. The alternative for Macy’s was to enlist their IT department to do something. No one mentioned this, but I was quite certain that the IT department would not be able to deliver a functioning system that met all the requirements within the required time frame. Of course, I was not certain that we could do it either. However, we had delivered several large projects on schedule, and I was willing to put in the hours5 to make this one a success.
590 Madison Ave., then known as the IBM Building.
I wanted to demo the GrandAd system and explain how we would adjust the database to fit Macy’s. I made arrangements to use a S/36 in IBM’s office at 590 Madison Avenue to show how our advertising agency system currently worked and how it could be adapted. I considered–and still do–this to be the most important presentation that I ever gave. It was my only chance to persuade Macy’s Advertising Director, Howard Adler, that TSI should be contracted to do the project. I figured that if we got Macy’s, and we did a good job, a whole new market would be opened to us. At that point I was still naive enough to assume that other retailers would surely be much less difficult because we had already done the programming for the largest retail advertiser in the country.
I needed to transport our GrandAd programs and our demo data to New York. Not only was it not possible in 1988 to send them there electronically using something like FTP. We did not even have access to a compatible medium. The I/O device on IBM’s S/36 in NYC read 8” diskettes. Our system in CT used 5¼” diskettes. So, I saved our programs and our data onto nine 5¼” diskettes. Then I used a machine that I had purchased for just this purpose to copy the 5¼” diskettes onto previously blank 8” diskettes. I then loaded the 8″ diskettes into a “magazine” that I had obtained somewhere. The S/36 in New York included a device for reading diskettes from such a magazine.
This is the only photo that I could find of a magazine. The diskettes are inserted in and removed from the opposite side.
You say that you are not familiar with the concept of diskette magazines? For over a decade IBM used them on the S/34 and the S/36. As far as I know, no other system from any manufacturer followed suit.
They were almost completely plastic. Their width was about an inch and a half. The other dimensions were just large enough for 8” diskettes. One side was open to allow insertion and removal of diskettes. Small plastic rails on the top and bottom of the open side kept the diskettes separate from one another. The only thing on the magazine that was not plastic was a small metallic bar near the top of the open space that held the diskettes in. The bar could be lifted up on a hinge to allow access to diskettes. The machine that read the diskettes could also do this (like a juke box), and it was smart enough to read them sequentially.
The process of saving and converting the programs and data, which I probably did over a weekend, took several hours. I then inserted the 8” diskettes into the magazine, put it in my sample case with my other materials, and then stowed the sample case in the trunk of my Celica. I do not remember why, but I must have left the car in the sun for several hours. When Michael and I reached New York and took out the magazine, we could see that the little iron bar that restrained the diskettes had apparently become hot enough to melt little notches into all the diskettes. The magazine drive on IBM’s system refused to read them. O tempora, o mores!
Michael had a brilliant idea. He used a sharp knife to slit the edge of each damaged diskette and nine new diskettes that we borrowed from IBM. The actual data was not, of course on the plasticized paper that one could handle (and therefore slit). It was on a very thin circle of magnetized film inside. For each new diskette Michael replaced the blank film disk inside with the one that he had retrieved from a diskette that I had made. Then he carefully inserted the nine new diskettes that hopefully contained our programs and data into the magazine. I then loaded the magazine into the S/36’s magazine drive again and entered the command to restore the files. The machine successfully read six diskettes. However, at that point it made an awful noise and totally mangled the seventh diskette including, because we had no way to reseal the side that Michael had slit, the precious film inside.
My dog could not juggle six balls.
So, I was faced with the prospect of making the most important presentation of my life with absolutely no software to demonstrate. The pony in my “dog and pony show” was a stick-figure drawing. Would anyone notice?
Fortunately, my many years of experience in debate at adjusting a presentation at the last minute kept me from panicking. I began the presentation by apologizing for the technical problem. I then illustrated the approach that we proposed to take using the whiteboard that IBM provided, and I answered questions as well as I could.
It was enough. Macy’s agreed to put in motion the process of contracting with TSI. As Alan later said, “You were definitely the only game in town.”
The plan was to install the system in the “System/36 environment” of a B30 model of an AS/400. The I/O devices were a single 8” diskette drive and a ½” tape drive. TSI had no system that had either of these drives, and so our only choice was to execute the cumbersome conversion process every time that we needed to make changes.
TSI could not even afford J. Cheever Loophole.
I sent Alan our usual two-page contract. He sent it to their legal department and returned one with about twenty-five pages. I should mention that the TSI was dirt poor at this time. Sue and I had been low on funds before, but this was the first situation that rose to a crisis level. Details are posted here. We certainly could not afford a lawyer. I had to read the contract very carefully and assume the worst. After a few changes, we agreed, signed it, and started work. I did almost 100 percent of the coding. The other programmers were busy with work for our other clients, and I did not trust Sue to do the work.
I was not able to use a single program from the GrandAd system. I thought that at least one of the many insertion order programs that we had written for ad agencies would be usable without much modification, but I was wrong. The people in retail advertising just do not think like the people in advertising agencies. Every single program was written from scratch.
We had no time to produce a detailed design document describing the project. Our drop-dead deadline was the end of the season in late January. All programs must be totally functional. The process was:
Write the code.
Get it to the point where there was something to show to Macy’s.
Save the changes to 5¼” diskettes.
Copy the 5¼” diskettes to 8” diskettes.
Take the train to New York.
Install the new software from the 8″ diskettes. This could take up to an hour.
If changes had been made to the database definitions, make them on Macy’s system.
Make changes on the fly as necessary.
Show Macy’s how the new code works.
Save the changes to 8” diskettes.
Bring the 8″ diskettes on the train ride to TSI.
Copy the 8” diskettes to 5¼” diskettes.
Install the changes on TSI’s system.
The luxurious Windsor Locks Amtrak stop. This is the view looking north. From the parking lot the engine’s light could be seen under the bridge.
This was, to be sure, a terrible way to do things. It required me to make at least one trip to New York every week for several months. Usually it was up and back on the same day. I stayed overnight at a hotel a couple of times. Often I made two up-and-back trips in a week. Each trip required a twenty-five minute drive to the train platform. I boarded the train at 6:00 AM in Windsor Locks. There is only a platform there. I therefore sat in my car with the heat on until I saw the light of the train approaching.
The word you did not want to see was “DELAYED”.
If everything went well, I arrived back at the train platform at 9:30PM. The trains in the evening, however, were almost never on time. Those trains originated in Miami, FL. There were plenty of opportunities for delay as each one crawled its way north. A report on my most memorable Amtrak experiences is posted here.
During this process Alan would quite often come up with new thoughts as to what should be in the “base system” covered by the contract. I grumbled, but I almost always did what he asked. One morning I saw a Daily News in Penn Station with the headline “Macy’s Computer System is Driving Me Crazy!” I bought a paper, cut out the headline, and taped it to the inside of my sample case.
Meanwhile, TSI had received only a deposit from Macy’s. However, we were desperate to receive that final check. I saw no alternative to this nightmarish schedule.
The scope of the project was enormous, and almost nothing from the GrandAd code was usable for this project. In addition to everything else, the emphasis at Macy’s was on newspaper ads. In my experience ad agencies used the term “print”, which for them referred to direct mail and magazines. Most agencies treated newspapers as magazines that published more often on cheaper paper to a geographically limited audience. The ingrates who ran the papers did not even offer discounts to ad agencies. Macy’s, on the other hand, could run a dozen or more ads in one issue of a newspaper.
Time to go home.
Mirabile dictu! By February, 1989, the system was stable enough that Macy’s paid us most of the balance. This did not end the crisis at TSI, but it allow us to meet the payroll for a few months. In retrospect, I cannot imagine how we pulled it off. I remember working seven days a week. I was always at work by 6AM, and I seldom left before 7PM7. I admit that I always went home for lunch, and I usually took a short nap.
Gary Beberman.
What enabled the completion of this seemingly impossible task in that amount of time was the fact that Alan somehow got Gary Beberman8 to serve as the project manager. He could speak advertising to the workers at Macy’s and geek to us. I only trained one person; Gary trained the others. I am not sure where Alan found Gary or how he got assigned to the project, but he was a godsend. He saved us a huge amount of time and frustration, and he was also quite adept on pouring oil on troubled waters during the frustrating periods in which I was working feverishly on the code.
The next two projects for Macy’s were an inventory system for the “loan room” (usually called “merch room” at other retailers) and a more sophisticated system of entering and reporting actual costs, what Macy’s called “financials”. I gathered the specs for these projects on trips to Macy’s and produced detailed design documents, which Alan quickly approved.
Denise Bessette did almost all of the programming on these two large requests, and she did an outstanding job. I installed the code and showed the people at Macy’s how to use the programs.
Merchandise that was afraid of the traffic could have just as easily taken the train.
The loan room gathered merchandise needed for photo shoots and sent it to the photo studio in Newark or to some other location. Part of the automation of this process was the printing of tags for each item. Almost as soon as this was implemented, the amount of pilferage reportedly decreased dramatically. The merch room manager told me that previously a lot of merchandise had trouble remembering the way back to Manhattan from Newark. She was extremely happy with the new system.
Denise also completed the other project according to the approved design document, and I delivered it. The finance manager then produced a bevy of changes that she wanted. I offered to quote the changes at TSI’s usual fee of $75 per quote. Alan said that Macy’s was under the impression that these programs fell under the terms of the original contract. It clearly did not include them. He was also surprised that I insisted on charging for my time at Macy’s after the warranty period. I would not give in on these matters, and this caused some bitterness.
At some point in this process TSI leased an AS/400 model B10 from IBM. We hooked everyone up to it, and we converted all of Macy’s programs to run in the native environment instead of the System/36 environment. This project went fairly smoothly. I don’t remember any great headaches, and the programs were considerably faster.
In other respects the installation also proceeded rather smoothly as long as Gary was there, but when he and his wife moved to the West Coast, things started to get a little testy. Alan hired Satish Rahi9 (accent on the second syllable in both names) to manage the installation. Satish must have presented himself as an alternative to paying TSI to program reports. He thought that he could produce any desired output using a third-party query product from a company called Gupta Technologies. Their Wikipedia page is here.
Satish was shocked that the product did not work on most of our tables. I told him that there was nothing in our contract that said or implied that third-party products (of which even then there were quite a few) would work with tables that we designed and implemented. IBM’s Query/400 product had no trouble with any of our tables. After considerable digging I determined that the source of the problem was that we wrote records in BASIC, not in SQL10, which was not even available on the AS/400 yet. The designers of Gupta’s product evidently did not take this into account when they began marketing to AS/400 customers.
Satish started lecturing me about industry standards for databases. I explained that the industry standard for writing x-digit positive integers in BASIC was N x, which left-pads these numbers (such as the ad number) with blanks, as opposed to ZD x, which left-pads with zeroes. In fact, most versions of BASIC did not even have a way to write “zoned decimals” without writing extraneous code to do it11. One day I got so upset while arguing with Satish about this that I seriously considered driving down to the Amtrak stop so that, after sitting on a train for over three hours, I could ride the elevator up to his floor at Macy’s and punch him in the nose.
Not long after this conversation Alan fired Satish, and eventually we changed all the programs to “zone” all the integers. Of course, we got paid for neither this project nor the conversion to the native environment, but we felt that we had to do them to hope to stay in IBM’s and Macy’s good graces.
Denise Jordaens.
From that point on we dealt with Denise Jordaens12 and Lee Glickman13 at Macy’s. Things stabilized, but the department did not get nearly as much out of the system as it could have.
Over these years Macy’s went through a lot of changes. In January of 1992 the company declared bankruptcy, thereby leaving TSI with a stack of unpaid invoices. In 1994 Macy’s was absorbed into Federated Department Stores, which had itself just emerged from bankruptcy. This gave them a new set of standards to abide by. Eventually other acquisitions gave Macy’s in New York a large number of new stores to manage on the east coast. They continued to use the loan room system and to pay our maintenance bills. They never asked about any of the enhancements that were installed at Macy’s South and Macy’s West.
There were other complications as well. On one occasion Macy’s asked for someone from TSI to visit so they could explain their problems with and aspirations for the system. My schedule was totally booked for weeks in advance. I asked Sue to take the trip. She did. I don’t know what transpired, but Denise Jordaens later told me that they made a voodoo doll of Sue and stuck pins in it.
I may have made some bad decisions about Macy’s. I did not yet understand how decisions about products and services like those offered by TSI were made in a large retail advertising department. This issue is discussed in more detail here.
TSI probably should have charged more for the original installation and used the money to hire another full-time programmer. Maybe we should have tried to borrow money from somewhere. I was unwilling to put all of our eggs in the Macy’s basket. Macy’s declaration of bankruptcy was a devastating blow to TSI. When Macy’s was acquired by Federated Department Stores14, it appeared to me that the decision to concentrate our efforts elsewhere had been a sound one.
As it turned out, however, Macy’s eventually gobbled up nearly all of the regional department stores in the entire country. The strategy that I chose helped TSI succeed for more than twenty years, but if I had gambled on Macy’s, we might still be in business in 2021. On the other hand, we would have been working almost exclusively for Macy’s for most of that time. Such an experience might have really driven me crazy.
The story of the Macy’s installation had a bizarre final chapter. It is recorded here.
1. According to his LinkedIn page (which is here), in 2021 Quique Rodriguez is retired and enjoying family time. I suppose that it is possible.
2. Alan Spett lives in Atlanta in 2021. His LinkedIn page can be found here.
3. So, I designed the database with five levels of participants. The lowest level was always called a department, but the names of the other four levels to be used on reports and screens could be specified by each AdDept client. At all Macy’s divisions they were called Administrative Groups, Group VP’s, Senior VP’s, and Group Senior VP’s.
4. This same room housed the AS/400, at least for a while. I sat at an empty desk when I was there. When the first phase of the installation was completed, some of the measurement clerks were reassigned to other tasks.
5. Unfortunately, I don’t think that I was careful enough to account for the large number of unproductive hours that I would spend on trains, in meetings at Macy’s, and in converting files. The round-trip train ride alone accounted for six or seven hours and a drive of nearly an hour, So, each full day at Macy’s was matched by another full work day getting there and back!
6. ROP stands for “run of press”. All display ads (as opposed to preprinted inserts) that are run in a newspaper are called ROP. It is not an acronym; all three letters are pronounced.
7. I am a “morning person”. Any work that I did after 7PM was likely to be counterproductive. Moreover, I needed a few caffeine-free hours so that I could fall asleep at 10PM and stay asleep.
8. I have kept in touch with Gary Beberman. He moved to California to work as a consultant and then was employed by Macys.com. Macy’s West and Neiman Marcus hired him as a consultant during their AdDept installations. He was the only consultant whom I ever respected. He has lived in Marin County for the last five years. He and his wife are hoping to retire to Italy.
10. SQL (structured query language) was invented in the seventies by two IBM researchers, but at the time of the debut of the AS/400 no IBM computers used it much. The reason, we were told, was that it was much less efficient than the ISAM methods that IBM endorsed. Later IBM computers, including the AS/400, were designed to maximize the efficiencies of SQL queries.
11. What I said to Satish was correct from my perspective, but perhaps I should have asked him what made Gupta Technologies think that the AS/400’s relational database conformed to these “industry standards” that he cited. After all, SQL had been invented by IBM, and IBM was not yet positioning its AS/400 as an alternative to the “standard” databases such as Oracle, Sybase, or Informix.
12. According to her LinkedIn page (here) Denise Jordaens still works as coordinator of media systems for Macy’s.
13. I think that this might be Lee Glickman’s LinkedIn page.
14. A more detailed discussion of TSI’s long and torturous relationships with Federated Department Stores can be found here.
