Systems Applications Architecture

IBM's SAA is a reality

Andrew M. Seybold
Andrew Seybold's Outlook on Professional Computing

June 1, 1989

IBM recently rolled out Office Vision, its long awaited, first wave, SAA (Systems Applications Architecture) software.

In what many observers see as perhaps the most significant software announcement of the decade, the new products are designed to give common access and a common user interface across the entire range of IBM's product line from mainframe computers to PCs.

Office Vision, as the products are called, is composed of: Offiace Vision/2LAN, Office Vision products running on IBM 400 series computers, and Office Vision products running on IBM computers communicating in VM, MVS, VM-Asian lafiguage, and MVS-Asian language computer platform languages.

This is the first of an entirely new generation of software based on thc SAA specifications IBM has been touting for many years. The thrust of these programs is to provide office functions across all ofthe existing computing platforms (mainframes, mini-computers, and desktop workstations (PCs).

The products provide a common user access (CUA) as well as transparent sharing of data from one platform to another. The products include many applications which are based on programs already running on one or more IBM machines. The software has been designed to work with PROFS, and Office/400.

Key points in thc announcement include SAA applications providing an integrated family of office systems, a new, and revised CUS graphical model with workplace extensions to OS/2 Extended Edition, support for OS/2 Extended Edition, IBM-DOS and nonprogrammable terminals (dumb terminals), evolution from existing office products with upgrade provisions for the installed base, and extensive support for 20 languages (including two versions of English: American and British).

The program basics

The packages, called OfficeVision collectively, will provide mail, calendar, address book, notebook (basic editor), file systems (libraries), and telephone dialing. Each will be available in two releases, thc first in 1989 and the second in 1990. While most ofthe features will be implemented in the first release, several key features and "direct connect" functions will not be included until the second release (see below).

In addition, there will be (am) many programs that will run underneath OfficeVision on all ofthe platforms. Some of these will be IBM products (DisplayWrite etc.) but many will be provided by third party vendors. Each of the applications contains code which permits it to "snap" into OfficeVision and become an integrated part of it (scc page 6).

What is OfficeVision?

Perhaps the best way to describe OfficeVision is to start at thc dcsktop on an OS/2 equipped PC. OfficeVision is installed beneath the Presentation Manager Desktop and is, in turn, its own desktop. This may sound somewhat confusing but it can bc likened to having a shell "below" the main operating system and then being able to install devices, applications and other things in the second shell.

Each icon on the desk mn represent a file, an action (print, shred, mail), an application which has been installed below the main OfficeVision Desktop, or any other function. In other words thc icons can refer not only to files and applications but also to sub-sest of things which include actions to be taken on a file or piece of data.

One way to visualize this is to consider two icons, one which represents a memo and the other marked "mail." By dragging the memo icon to the mail icon and letting go of the mouse button, you have directed the system to send the memo via electronic mail. Without having to pull down any other menus, you are presented with an addressing window and a list of mail recipients. Drag the proper name to the address window, click on 'send', and thc memo is sent.

The fun begins. You may have more than one icon marked "mail." One might bc marked "mad", one might be labeled "staff," one named "boss," and one called "London Office." Instead of having to drag the icon to a generic mail icon, drag it to the one which has been predefined as "staff" and the memo is sent automatically to all of the people listed in your staff mailbox.

Let's walk though a memo which has arrived in the "inbox". First, the inbox beeps (or a number is shown in increments) to indicate the arrival of new mail. Click on the "inbos" to display the message in iconic format with an associated title. Next, dick on the mcssagc to open and read it, file it by dragging it to thc file drawer, or perform several functions on it. It is even possible to drag the memo to a telephone icon where thc telephone program will "find" the number and dial it. Dragging the mcmo to your address book would add thc namc and address on the memo, automatically.

The products

The announcements are divided into platforms. The first is thc Lo& Area Network version (OfficeVision LAN) which supports an OS/2 server and both OS/2 and DOS-based work stations. Release one provides mail service, correspondence processing, an addres book, a file system, and telephone support and will ship in September 1989. Release two, which is scheduled to ship in March of 1990, adds calendar, decision support, a file cabinet, a library, online help and tutorials, and an application development platform. The application platform is designed to provide the ability to add-in othcr programs developed either in-housc or by IBM and othcr ISVs (Independent Software Vendors), using functions and calls designed to provide "snap in" capability.

OfficeVision becomes a truly integrated office environment. IBM has announced Display Write 5/2 as onc of these "snap in" applications and othcr vendors also have announced programs (and were demonstrating them) which will "snap in" to OfficeVision IAN. OVLAN is a stand alone network program which does not require interconnection to a mini or a mainframe and is a very powerful software system in its own right. The other releases detailed below can provide for OVLAN to operate in conjunction with the mini and mainframe versions ofthe program and providc for the seamless movement of data from onc platform to any of the others.

Pricing for the IAN version is $750 for the server, $210 for the Office DOS requester, and $540 for a conversion package that lets the DOS requester feature talk to the OS/2 Office Server in an OS/2 office. The user interface under OS/2 with Presentation Managers is well thought out, makes full use of the mouse (pointing device) and iconic symbols, and is fast.

The DOS interface is, quite frankly, awful. IBM decided to build it for the lowest common demoninator, 8088 based PCs and XTs. Therefore, its graphical representation is very poor, looking like the OS/2 desktop was drawn by a 5 year old. However, the implementation is vcry functional and when clicking on an icon, a text based listing of the functions which can be performed by that icon, is displayed. (IBM really should have considered thc large installed-base of 80286 and 80386 users who have EGA graphics and who would have benefited by having a much more robust graphical user interface. Maybe they are trying to get all of these users to move to OS/2, but I would have been happier to sec a version of the user interface running under Windows, and I am sure Microsoft would have been happy too).

OfficeVision/MVS

This product is the MVS member ofthe OfficeVision software and is designed to run on the MVS platform (mainframes) sold by IBM. This series of programs supports non-programmable terminals, as well as OS/2 and DOS based PCs. It has been designed to permit users of existing MVS office products to upgradc to the SAA platform without having to scrap existing software, and both MVS/XA and MVS/ESA environments are supported.

This package includes OfficeVision/ MVS (the host program) and has four features on thc host program: a document writing feature a document composition feature, an applications connectivity feature and an application access feature.

The OS/2 Office features of the MVS package include: LAN and direct connections to OS/2 Extended Edition workstations, an IBM-DOS requester for OS/2 Office IAN, and an IBMDOS direct connection feature for optional host and workstation products.

This version provides for migration of cxisting Personal Services/CICS, Applications Support Facility (ASF), Integrated Procession of Data and Text (IPDT), and Personal Manager programs.

Pricing is typically IBM in nature, and runs from $15,000 to $51,000 with a one-time charge for thc OS/2 office fcaturcs which are equal to the LANbased product.

The first release will be available in September 1989, with a second release of the product scheduled in June 1990.

OfficeVision/VM

Designed to run on the VM platforms (midrange machines), OV/VM provides support for NPTs (non-programmable terminals), as well as OS/2 and DOS workstations. Like the rest of the product line, direct connect is supported in release 2.

Ov/VM extends the usability of existing VM officc products and provides a path to SAA.

Ov/VM consists of a host program (OfficeVision/VM);two OS/2 features: a LAN, and a direct conncction for OS/ 2 Extended Edition workstations. In addition, it includes a DOS Requester for thc OS/2 Officc LAN feature, as well as an IBM DOS dircct conncct option, host and workstation product support

Prices range from $8,500 to $51,000, plus OS/2 and DOS direct connect features previously listed.

OfficeVision AS/400

This version of the software is designed for the IBM series of AS/400 midrange computers. It also includes support for existing AS/400 systems mnning OS/ 400 (the operating system for thc AS/ 400 series minicomputers). Upgrades to AS/400 Office are included with thc package.

This package includes OfficeVision/ 400 (currently AS/400 Officc), as the host program, two OS/2 Office features: a IAN, and a direct connection for OS/2 Extended Edition workstations, an IBM-DOS requestor implementation for thc OS/2 Office IAN, and lastly, host and workstation optional products.

Pricing starts at $2,885 and goes to $28,640 with a $945 per month licensing fee. Delivery is June 1990.

What they did well

IBM's software engineers appear to have put it all together. They have done a marvelous job with the user interface and I was told that many of the objectoriented features which are in OfficeVision will find their way into Presentation Manager.

The ability to providc an upgrade path to thc 370, AS/400, and othcr mini and mainframe users of the world has been implemented well. Upgrades to existing office functions have also been handled very well, and the seamless integration and movement of data appears to bc very robust and complete.

The users' or programmers' ability to "snap in" other programs and integrate them with OfficeVision should go a long way to helping companies provide solution based systems to their endusers.

The method of delivery is unique and speculative on IBM's part. In the miniand mainframe world, the applications are to be distributed on a single media such as a tape and the customer will pay only for what he uses, not for everything contained on the tape, a clear indication that IBM is placing a lot of faith and trust in its end-user community.

The seamlessness of the products from one platform to another is amazing. It is truly not possible to discover if the data you request is being provided by the OS/2 workstation, an AS/400, resides on a 370 or a combination of all of these.

What they didn't do well

IBM claims that it has worked for several years with corporate accounts, defining what is needed, insuring compatibility with existing programs such as PROFS and learning what functions and fcawrcs are needed. In several instances I feel that they either did not ask the right questions or did not listen to the right answers. These areas have to do with the implementation of the user interface within thc DOS world, failure to provide a calendar for the OS/2 vcrsion until Release two (and then only a poor attempt at one), appointment making, and the insistence that "send" and "print" are two separate actions and require two separate operations.

The DOS interface. As I stated before this is the worst attempt of a graphical user interface that I have ever seen. Users who have 80286 and 80386 systems may not even want to try and use it. If I am right, this could hinder the acceptance of these programs in corporations. The 286 and 386 systems are usually the ones which am on the desktops of thou most into computers, and these are the ones who tend to lead the charge towards better computing within a company. The least IBM could have donc was to provide a user interface running under Windows. This would have helped prepare the end-user for a shift to OS/2 with Presentation Manager by enabling him to start becoming familiar with the techniques involved in using this type of interface.

The calendar. As far as the calendar is concerned, IBM claims that the reason it elected to wait until the second release of OS/ 2 IAN is because there is some coding to do before it can be used with PROFS and AS/400 office. In addition, IBM stated that the user community was not really turned on to calendars in general. According to IBM this is a feature that probably won't be used much. I believe that calendar functions, coupled with to-do fists, and phone messaging systems, is one of the items which will become very popular with this program, if implemented properly. If not, the door is open to IBM's competition to provide these functions.

People who have never used an electronic calendar have no idea whether they will like it or not. Those who have used a text based system cannot visualize the differences available in a graphical based system which provides much more function than they are used to. The OfficeVision calendar section must be reworked significantly, if IBM expects it to be accepted by the end-user community.

Appointments. There is no "tick" mark or some other form of mark on the six month view to show that appointments have been made. Even my Sharp Wizard does this. Next, one cannot have both a graphical view and a text based view of the calendar. The six month view has a graphical representation. However, zooming into a one month view shows a text window with appointments that scroll up and down. I was not able to see the data entry screens or play with any of those features but it is obvious that one should view a good calendar by day, week, month, six month, and yearly increments, showing different level of details for appointments and commitments as well.

Right now it's unclear at IBM if the "group" or "meet me" functions included in PROFS have been implemented in OfficeVision. I know them's no provision for off-loading the calendar to my laptop with a "merge and compare" fcature. I hope IBM will reconsider the use of calendar functions before reeleaseing the product to the marketplace.

There are some very good calendar and time manager programs on the market or about to be released. Maybe IBM should leave these functionss to third -party vendors because it appears that PIMs (Personal Information Managremetn) software can't be "all things to all people."

Print and send. When I asked if it was possible to build a common distribution list that included E-Mail, dial-up mail services, fax, and printer distribution, the answer was no. When I pressed further I discovered the design criteria considers "print" and "send" to be two separate operations. Therefore, if I draft a document to send via E-Mail, Fax, external E-mail, and also a printer, I must first "send" it and then "print" it, Had IBM implemented the Intel/DCA (CAS) Communications Applications Standard, this problem would have been addressed, and it would help convince other software vendors to incorporate the same implementation within their programs.

OfficeVision "below" Presentation Manager

At the moment OfficeVision on thc OS/2 platform is installcd below the OS/2 Prcscntation Manager. It was developed as a separate package and resides as a folder on the OS/2 dcsktop. Opening the folder provides yet another desktop, with access to all of thcOfficeVision software as well as access to those programs which "snap" to it.

Looking at thc system implementation, it is obvious that future releases of OS/2 Extended Edition will include much of the object oriented action type of structure which makes OfficeVision so easy to usc. Once a user gets into OfficeVision, and if enough applications bccomc available which "snap" to it, he will never see the OS/2 dcsktop again. Until then, he will have to navigate between the OfficeVision Dcsktop and the PM one; a minor annoyance that will, I am sure, be corrected over time.

Final Comments

IBM is betting Armonk on this software. I think it's a real winner. The software will, no doubt, find its way rapidly into IBM shops all over the world. The question is: will it also find its way into non-IBM shops, or shops which do not have any mainframe or mini-computer equipment. Will the end-user community see this product as useful for standalone local area networks or will they preceive it to be designed only for use whcrc connections to minis and mainframes are required?

From my perspective, it should be viewed in both lights. First and foremost, it is an excellent tool to permit transparent interconnection and a common user intcrface across IBM's full range of computing cquipmcnt. It provides a very well thought-out and implemented upgrade path for users of IBM's existing office products.

It can also be a valuable resource in the IAN environment. OfficeVision should be considered as the glue underneath OS/2 that holds everything together. It goes well beyond the level of integration offered under OS/2 Presentation Manager. If IBM "fixes" the DOS user interface or adds a Windows vcrsion of it, I believe that it will convince the non-connected users of the world that there is a viable network operating system.

I'm impressed with what I've seen. Obviously until we get the "real" software up and running, we'll reserve final judgement, but at this point we are willing to say: Congratulations IBM for a job well done!

Andrew M. Seybold

Copyright 1989 Andrew Seybold's Outlook, Inc.