NZ270986A - Distributing electronic images of business forms to remote users - Google Patents

Description

270986 • •-.'.v/Uy Dato<3): !.9:.1Dj5D. • njcwte Specification Filed: !"?• I0»Q1 &oG)Eaa/DQ j P-Jtiication Dat»: ; ' .0. Journal No: jjfc).) Patents Form No. 5 Our Ref: AS204594 This is a divisional out of application number 240269 dated 17 October 1991.

Mil Mr ttw provtaioM of 3 0) th® i %>«cHtection has feen aipc daflprf - NEW ZEALAND PATENTS ACT 1953 COMPLETE SPECIFICATION N.Z. PATENT OFFICE 24 APR 1995 RECEIVED FORMS AUTOMATION SYSTEM We, MOORE BUSIHES5 FORMS, INC., a corporate under the state of Delaware, USA of 300 Lang Boulevard, Grand Island, New York 14072-1697, United States Of America hereby declare the invention, for which We pray that a patent may be granted to us and the method by which it is to be performed, to be particularly described in and by the following statement: PT0585906 - 1 _ 270986 BACKGROUND AND SUMMARY OF THE INVENTION Conventionally, large organizations that use large volumes of many different types of business forms have the forms printed in paper form internally or by a manufacturer of business forms, and then store the forms in one or more warehouses for distribution to each of the geographically remote user locations of that organization. Distribution costs can be significant, especially if the locations are widely disseminated, and there can be significant costs associated with the warehousing, inventory and obsolescence of preprinted paper forms. If attempts are made to do away with inventorying of preprinted forms, electronic forms may be stored for printing of paper forms on demand, however typically systems capable of electronic storage and retrieval are marketed by vendors supplying only one type of equipment, so that the systems are not versatile enough to be utilized even within a single location of the organization unless all printers and related equipment at that location are compatible. Further, such systems do not have conventional preprinted forms manufacture integrated therewith, and are therefore limited.

Also, when new forms are required, they are typically designed at a location where the need for the form is first recognized. The newly designed form may, or may not, become part of the forms package available to other interested parts of the organization, and even if it ultimately becomes available, may go through a redundant design (followed by page 2) 2 2700 sequence before being adopted by the organization headquarters. Usually, no"centralized forms facility is provided, requiring redundant entry and processing of information in electronic or hard copy format.

According to the present invention, a method is provided which overcomes the major elements of the problems indentified above. According to the present invention, is is possible for a large number of consumer of forms, having numerous geographically remote user locations with varying needs for many different types of forms, to eliminate or minimize the warehousing, inventory, and obsolescence costs associated with preprinted forms, to minimize the number of preprinted forms utilized, to minimize redundant entry and processing of information, and to provide centralized design, control and management of electronic forms.

According to the invention, the same form may be printed at a number of geographically remote locations on different types of printers, the forms can be distributed and updated automatically and efficiently, and if a form is needed but not readily reproducible on in house equipment, an order for the form may be transmitted to a vendor's manufacturing facility or facilities (e.g. located geographically proximate the remote user locations to be served) for production and distribution.

A system which -may implement the invention is described in copending New Zealand application No 240269. 3 According to one method aspect of the invention, a method of electronically developing, producing, managing, and distributing a plurality of different business forms for an entity having a plurality of geographically remote use locations with different needs for different business forms, is provided. The method comprises the steps of: (a) at a centralized location, storing the plurality of business forms in electronic format including print images; (b) based on geographic location, volume requirements, form construction, and equipment profile, determining which of the geographically remote use locations will be provided with business forms, and storing that information at the centralized location; and, (c) through electronic scheduling or in response to commands input at the centralized location, automatically distributing forms from the centralized location to the geographically remote use locations for that particular form, according to the determinations provided in step (b). There may be the further step (d) of providing for electronic storage of the forms at decentralized locations, and subsequent processing. The subsequent processing comprises selecting either data entry and production using electronic imaging, or traditional production, as determined in step (b). Step (a) is practiced to store the business forms to be distributed to both the first and second use locations in both the first and second printer formats; and step (c) is practiced to automatically distribute forms in electronic format to the first and second printers, for printing into paper forms at the first and second use locations. This insures that the mofat current version of the form is available at all sites, including data entry and/or production sites. 2709 According to another method aspect of the present invention, a method of providing a user of a plurality of different business forms at a plurality of geographically remote locations with the business forms in an efficient manner, and without the necessity of warehousing preprinted paper forms, is provided. The method comprises the steps of: (a) storing the business forms in electronic format at a centralized location; (b) producing the business forms in paper form at geographic locations proximate each of said geographically remote use locations in response to an electronic order generated by a centralized or remote command; and (c) delivering the business forms in paper form to each of said geographically remote use locations after production thereof. The centralized location is a first centralized location, and the method typically comprises the further step of (d) creating business forms in electronic format at a second centralized location, and transmitting the created form in electronic format to the first centralized location.

The invention also contemplates a method of handling business forms, comprising the steps of: (a) creating a plurality of business forms in electronic format using a plurality of different business form creating computer programs; (b) maintaining the business forms created in step (a) in a display image format to which variables may be added for variable image data; (c) converting the display of form image format for each of a plurality of forms to desired printer formats; (d) simultaneously transmitting the printer formats to each of a plurality of compatible printers; and (e) printing out the forms on the compatible printers. 2/0 Further, a method of distributing business forms to each of a plurality of remote end users is provided, comprising the steps of: (a) storing in electronic format in a computer a plurality of different business forms; (b) also storing in the computer predefined commands, including date and extent of distribution commands, relating to the distribution of the electronic business forms; (c) periodically polling the computer to locate applicable date commands; and (d) in response to applicable date commands located in step (c), automatically distributing the electronic business forms to those of the plurality of end users specified by the distribution commands.

Alternatively, instead of step (d) above, the following may be provided: (d) in response to applicable date commands located in step (c), readying the electronic business forms for distribution to those of the plurality of end users specified by the distribution commands; and (e) manually verifying the distribution of the electronic business forms to those of the plurality of end users specified by the distribution commands, and after manual verification, automatically distributing the electronic business forms to those of the plurality of end users specified by the distribution commands.

Even more generally, the invention contemplates practicing the above steps for any electronic images, not just business forms.

It is the primary object of the present invention to provide for the effective and efficient creation and production of electronic and preprinted business forms for large consumers of forms having multiple locations. This and other objects of the invention will become clear from an inspection of the detailed description of the invention, and from the appended claims. 2709oG 6 BRIEF DESCRIPTION OF THE DRAWINGS FIGURE 1 is a schematic block diagram comprising a high level functional overview of an exemplary system which is implemented according to the invention; FIGURE 2 is a block diagram showing one embodiment of a more detailed interrelationship between the components of the FIGURE 1 system; FIGURE 3 is a block diagram showing an overview of the interconnections between the central library facility (CLF), forms automation platform (FAP), and end users; FIGURE 4 is a schematic view of the FAP; FIGURE 5 is a schematic like that of FIGURE 4 for a host computer utilizable with the CLF and the FAP; FIGURE 6 is a data model diagram for data structures provided by the FAP, for detailed implementation according to the invention; FIGURE 7 is a data flow diagram of exemplary program control processes performed by the FAP, for detailed implementation according to the invention; FIGURES 8a-8e are schematics giving lower level breakdowns of the major elements of FIGURE 7; FIGURE 9 is a flow diagram illustrating access to the CLF from the FAP; 2709 7 comprising a high level functional overview of an exemplary system which is implemented according to the invention; FIGURE 2 is a block diagram showing one embodiment of a more detailed interrelationship between the components of the FIGURE 1 system; FIGURE 3 is a block diagram showing an overview of the interconnections between the central library facility (CLF), forms automation platform (FAP), and end users; FIGURE 4 is a schematic view of the FAP; FIGURE 5 is a schematic like that of FIGURE 4 for a host computer utilizable with the CLF and the FAP; FIGURE 6 is a data model diagram for data structures provided by the FAP, for detailed implementation according to the invention; FIGURE 7 is a data flow diagram of exemplary program control processes performed by the FAP, for detailed implementation according to the invention; FIGURES 8a-8e are schematics giving lower level breakdowns of the major elements of FIGURE 7; FIGURE 9 is a flow diagram illustrating access to the CLF from the FAP; 2709 EIGURE 10 is a schematic diagram illustrating exemplary components of the CLF of the system of FIGURES 1 and 2; FIGURE 11 is a CLF data model diagram, for detailed implementation according to the invention; FIGURE 12 is a schematic showing the CLF data base relationships, for detailed implementation according to the invention; FIGURES 13a-13i provide a schematic structure chart for the CLF, for detailed implementation according to the invention; FIGURE 14 is an exemplary flow diagram for releasing forms from the CLF to end user sites based upon a distribution profile; FIGURE 15 is an exemplary flow diagram for transmitting an electronic form, initiated at the CLF; and FIGURE 16 is an exemplary flow diagram for transmitting a print request, initiated at the CLF. nTrrATT.TD DESCRIPTION OF TPTR DRAWTNGS A forms automation system is illustrated generally by refernce numeral 10 in FIGURES 1 and 2. The forms automation system 10 will be utilized by those consumers of business forms who have large numbers 9 270 of business forms (both type and amount) that will be utilized at a number of geographically remote use locations. The system 10 is designed to be marketed by a business forms manufacturing company that has conventional forms production facilities, although it could be marketed by a wide variety of different types of companies. The system 10 is particularly useful when it it implemented in such a way that forms may be produced directly at the use locations, or in a conventional manufacturing facility, depending upon the construction of that particular form, the extent of its distribution, the quantity of forms utilized, and the like.

In this description, the term "vendor" or "manufacturer" when utilized refers to the entity providing the forms automation system according to the invention, typically a conventional business forms manufacturer. The term "customer" or "user" refers to the vendor's customer, namely the organization that has a plurality of geographically remote use locations, and consumes the business forms (also encompassing multiple departments that are remote within the same building, for example).

The major objectives of the system 10 are to provide for the centralized design of business forms, the centralized management and distribution of electronic and pre-printed (paper) forms, the co-existence of the same form in both paper and electronic formats, and the flexibility to meet the user's requirements. The major components of the system 10 comprise computer means providing the central library facility (hereinafter denoted by the acronym "CLF") 12, and computer means providing the 2709 forms automation platform (hereinafter denoted by the acronym "FAP") 14. The CLF 12 is preferably located in one of the customer's facilities (e.g. the same facility that has the main frame computer 34). This also typically is one of the use locations. The FAP 14 may, under some circumstances, be located at a customer's facility, but more typically is located at one of the vendor's facilities. In any case, the CLF 12 and FAP 14 provide for centralized design, management, and distribution of business forms. Appropriate conventional communications components are provided to inter-relate the CLF 12 and FAP 14, and to communicate with a variety of other stations.

In the schematic illustration in FIGURE 1, the end user station 15 comprises a plurality of geographically remote use locations, each of which may have a printer — such as a laser printer 16 — associated therewith. A computer, such as a PC, is provided at each of the use stations 15, as schematically illustrated in FIGURES 1 and 2, interfaced (two way communication) with the CLF lz. The PC and CLF may utilize IBM's OS/2 (version 1.2), or an equivalent multi-taBking operating system.

The CLF 12 may also control an internal electronic forms composition system 17 maintained by the organization having the geographically remote use locations 15, which may in turn control a high speed printing device, such as a high speed laser printer 18, or other non-impact printer. Both the CLF 12 and FAP 14 may also provide information to a standard business forms manufacturing facility, shown generally by reference numeral 19, for 11 2705 ( producing business forms. For example, the CLF 12 could access facility 19 through an external applications data base 28. Different types of manufacturing facilities encompassed by facility 19 may -- for a large conventional business forms manufacturer such as Moore Business Forms, Inc. — include a traditional plant 20, a short run facility 21, an intelligent imaging facility 22, or other types of facilities 23. Also, the FAP 14 may control an internal print shop 24 at the FAP 14 location, for providing camera ready copy. The printing facilities 21, 23, and 24 deliver printed fotms — as indicated by line 25 -- to the use locations 15 via a motor vehicle or the like (e.g. a common carrier), while the traditional plant 20 supplies paper forms to the use locations 15 through a warehouse 26 run by the forms manufacturer, a contractor, or another. The imaging facilities 22 typically provide paper forms to the use locations 15 via mail or a courier service 27 or the like.

As illustrated schematically in FIGURE 2, the CLF 12 includes an internal applications data base 29 (and associated database access mechanisms), and includes as part of the preferred embodiment communication facilitating components thereof, such as a vendor supplied token ring (or other network adapter) 30 communicating with an (e.g. token ring) electronic data network 31. The applications data base 29 may have as its data model "SQL", a commercially available package, such as that sold by IBM with its OS/2 (version 1.2) system. A conventional communications interface component 32, such as an IBM 3270 standard protocol interface, is 270 12 also preferably provided, as is the communications protocol module 33. The CLF 12 may be provided on main frame computer 34 directly at a customer (user's) location, with a front end processor 35 — such as an IBM 3745/3720 -- interconnected between the module 33 and the computer 34, and a front end processor 36 — e.g. an IBM 3745/3720 — connected between the main frame computer 34 and the token ring network 31.

The forms automation platform 14 includes a commercially available applications database 37 (such as that sold by Oracle Systems Corp. under the trademark "Oracle"), witn a component thereof 38 providing custom design of the forms. The forms design function is preferably accomplished utilizing a compatible commercially available primary design software package, such as Perform, sold by Delrina Technology, JETFORM, sold by Indigo, or MECCA III ("DOCS"), sold by Altigraph. A communications protocol module 39 is also utilized (such as an IBM SDLC), while the token ring adapter 40 is provided for optional communications over token ring network 31.

One ox. the primary functions of the FAP 14 is to provide for the centralized design of business forms. It is the entry point into the system 10, and contains software that controls the execution of the other processes within the system 10. As earlier indicated, forms design packages are associated therewith, such as the DOCS, or PERFORM, packages. The forms may be designed elsewhere and downloaded to the FAP 14 prior to transmission to the CLF 12. The FAP 14 communicates with the CLF 13 2,./ QQh (preferably two way) by modems 41, or a token ring, or networked protocols defined by the IEEE 802.5 or 802.2 standards. A terminal 43 (see FIGURE 4), including a display screen 44, and inputting means such as a keyboard 45 and/or mouse 46, are provided as a human interface to the FAP 14. Other technologies could also be utilized, such as scanners and digitalization apparatus.

In addition to the forms design packages, the FAP 14 contains application software for a number of other functions. A file management function manages display (source) images for all released forms and forms that are scheduled for up-date/release. This software creates, maintains, up-dates and ensures the integrity of the display image library.

A user friendly interface function is provided by software that allows the operator to be queried for information regarding print formats and distribution profiles for each form. This information is logically associated with the display image within the file management system function so that whenever an electronic form is created or up-dated, it will have the necessary components. The forms administrator at the FAP 14 will obtain the following information for each electronic form created or up-dated: form identification; form description; form processing (e.g. new/update); the design software used to design the form; the release date; the security level; the distribution profile (user sites, output devices/sites, generic customer environment information); the paper base production requirements (e.g. manufacturing facilities, or 14 internal print shops for camera ready copy); and variable data field encoding.

The FAP 14 also converts the display images to appropriate print formats based upon the distribution profile specified for each form. This is typically done right in the forms design package 38 itself (e.g. in PERFORM). The operator inputs what printer formats the form is to be provided in, and the package 38 does the necessary formatting (either single or multiple). That is, if a form is to be distributed at a first location having a first printer with a first printer format, and to a second geographically remote user location, having a second printer with a second printer format (e.g. a different manufacturer for the second printer than the first printer), the display images must be converted to print formats for both the first and second printers. That is, the same electronic business form will exist in different formats. The print image files will be validated for existence, having been previously formatted based upon the customer profile, and downloaded to the CLF 12. The CLF 12 may effect distribution on a scheduled release date. Of course this is practiced with any number of printers.

The system 10 may have any one of the following output formats: display image; encoded display image; print format; and production output. The display image format may require no conversion, and — for example -- can be used to merely display the form on a screen (e.g. the screen 44 of the CLF 12). For the encoded display image format, the operator at the FAP 14 has encoded the variable data 270986 fields, and this format is used for merging variable data with the electronic form in a conventional manner via a batch process at the u&er site. This format, too, can be sent to a display terminal (e.g. 44). Print formats should be able to support output to postscript printers, as well as for printers for all other major manufacturers such as IBM, Hewlett Packard, Xerox, etc. The production output formats will support an output for a manufacturing production facility 19, via a PC to PC (e.g. DOCS to DOCS) transmission. This output may be used to produce camera ready copy. This will insure the most updated form at all times. It also will provide an output to control an internal print shop 24 for producing camera ready copy.

As earlier indicated, the FAP 14 communicates with the CLF 12 via modems 41, token ring 31, or the like. Print images and form profiles are transferred to the CLF 12, and update processing within the CLF 12 is scheduled. Display and print images for updated forms will be downloaded to the CLF 12, and appropriate file management functions, such as archiving, will be scheduled and performed.

Major components of the data flow diagram of FIGURE 7 include the FAP administrator software 86, form maintenance process 87, profile maintenance process 88, CLF administrative software 89, CLF update process 90, a report generation process 91, and the FAP utility process 92. FIGURE 8a illustrates a detail data flow diagram for the form maintenance process 87. FIGURE 8b illustrates a detail data flow diagram for the profile maintenance process 88. FIGURE 8c illustrates detail data flow 16 diagram for the CLF update process 90. FIGURE 8d illustrates a detail data flow diagram for the report generation process 91; and FIGURE Be illustrates a detail data flow diagram for the FAF utility process 92.

FIGURE 5 provides a schematic of a conventional host computer 34 and its interrelationship to other components in a typical configuration. The computer 34 may include applications software 49, a printer control 50, and a communications module 51. A printer 52, such as an IBM 3800, is controlled by the printer controller 50 software, e.g. JES AND AFP, both by IBM. Other printers 52, such as the Xerox 9700, of course may also be utilized. The communications module 51, such as an IBM SNA, is interconnected with a communications controller 53, such an an IBM 37XX FEP. A personal computer 54 may be interconnected to the controller 53 via a token ring or other link, and control a locally attached printer 16, or access other printers in the network. The controller 53 is connected through modems 55 to other PCs 54 (at sites 15). Controller 53 can communicate through the token ring 31 with the CLF 12 and FAP 14, or through modems 42 with the CLF 12. Communications may also be provided optionally through modems 56 with a cluster controller 57 — such as an IBM 3174/3274 — which in turn is interconnected with a communications interface (such as an IBM 3270) and a PC (such as a 3270 emulation PC). PC 58 may function as a print/file server to support multiple devices.

The controller 53 (typically located on host 34) will run a version of a network control program 17 2? OSt. (e.g. OS/2 version 1.2 from IBM) that supports peer to peer networking. The PC 54 has a Moore Forms Print Server. Therefore, CLF 12 communicates directly with PC 54 through controller 53 automatically, without "bothering" host 34.

The major menu items provided to the user of the FAP 14 are provided on menu screens. The main menu will allow selection of the forms design program, updating the central library with selected forms, defining a form profile for a current form, defining form fields for a current form, customer profile information, CLF profile information, and a customer profile query. Many others may also be provided. Typical screens for each of these above specific menu items are as follows: For forms design, a list of the design software defined for a particular customer will be displayed, e.g.: Forn Profile Library Reports Utility Exit Run Forn Design Progran Enter Custoner ID: 3-1234567-00000 Forn SH JFDESIGN PERFORM F3 Char Kode: Replace Page 3 Count: 3 18 ?0iSb6 For downloading information (e.g. forms and release dates) to the CLF 12: Update Exit Update Central Library vitb Selected Foras.

CLF ID: SAVANNAH CENTRAL LIBRARY UPDATE Select Custoner ID Forn ID Rev Status 3-1234567-00000 TINF0RM 0 Completed 3-1234567-00000 SIGDEH0 0 Completed 3-1234567-00000 UHIVFILL 0 Coupleted Press IF5I to return to nenu To select Forn for Library Update, enter To save selections, press IF10I. Char Mode: Replace Page 1 Count: 3 rr-jj / 19 For encoding a variable data information field, which is sent to the CLF 12 and verified there: Profile Query Bxt Define Foro Profile for current fori.

FORN FIELDS Field Dane TIMFLD1 Sequence 1 Location 2x4in Field Type CHAR Length 8 Fornat**°*MX Validation NONE Calculation NONE Field Kane TIMFLD2 Sequence 2 Location 2x3in Field Type CHAR Length 10 Fornat**Mt***X Validation NONE Calculation NONE Field Nane TIHFLD3 Sequence 3 Location 4x4in Field Type DATE Length 8 FornatMM-DD-YY Validation NONE Calculation NONE Press IF5I to return to nenu Char Mode: Replace Page 2 Count: 3 For illustrating form profile information for a form which has been created: Fields Query Exit Define Fora Fields for current forn.

FORN PROFILE INFORMATION Cust ID 3-1234567-00000 Oust Nane XTZ BANK Forn ID TINF0RM Descr CUSTOMER ADD & TIN CHANGES-HP H/S2 CART.

Revision 0 Forn Status NEW Release Status COMPLETED Forn Path C:\XYZBANK Fore Width 8.5 No. of Pages 1 Fora Length 11 No. of Parts 1 Orientation PORTRAIT Duplex N Forn SW JFDESIGN FORM FILES: File Nane PD Type CLF ID TINFORM.IFD HP S SAVANNAH TINFORH.HDF HP C SAVANNAH TINFORH.PRT HP P SAVANNAH By Date Created FAP 19-N0V-90 Modified FAP 19-N0V-90 Released Press IF51 to return to nenu Char Node; Replace Page 1 Count: 1 a 21 An exemplary screen for inputting data, e.g. customer profiles, is: Query Exit Hove to query screen CUSTOMER PROFILE INFORMATION Cust ID 3-1234567-00000 Directory C:\CSBANK Cust Nane XYZ BANK Contact S. Jones CUSTOMER ADDRESS: Addr 222 MAIN STREET Phone Nunber (800) 800-8000 Fax Nunber (800) 800-8001 SHIPPING ADDRESS: Addr 222 MAIN STREET City SPRINGFIELD State MB Zip 00001 Cntry USA City SPRINGFIELD State HE Zip 00001 Cntry USA Attn S. JONES HW/SW S HW/SW Nane: Description JFDESIGN JETFORM DESIGN V. 2.1 HPLJIID HEWLETT-PACKARD LASERJET IID PERFORM PERFORM Y.2.1 Press (F5) to return to nenu Char Mode: Replace Page 1 Count 1 i 22 o An exemplary screen for inputting CLF profile information is: Query Exit Move to query screen CLF ID Location Description Adninistrator Phone Nunber Moden Nunber Fax Nunber CENTRAL LIBRARY FACILITY PROFILE INFORMATION Custoner ID SPRINGFIELD 3-1234567-00000 XYZ BANK, SPRINGFIELD, ME IBM PS/2 MODEL 80, >S/2 V. 1.2 S. JONES (800) 800-8000 (800) 800-8002 (800) 800-8001 Press IF5I to rove to nenu Char Mode: Replace Page 1 Count 1 Exit Return to caster record An exemplary customer profile query screen is: CUSTOMER PROFILE QUERY Cust ID 3-1234567-00000 Hardware/Software CLF ID SAVANNAH Type H S S Nane HPLJIID JFDESIGN PERFORM The data model diagram for FAP 14 is provided in FIGURE 6. The same conventions are utilized here and as in the CLF data model diagram of FIGURE 11. The connections in FIGURE 6 refer to the relationship between the two entities; i.e. two entities connected by an arrow with one arrow head at one end and a double arrow head at the other end are said to have a "one-to-many" relationship. In a relational database construct, this means that for each parent record in the first entity there may/shall exist many child records in the second entity. A glossary of the individual tables of the FAP 14 illustrated in FIGURE 6 is as follows: 24 270 FORMS AUTOMATION PLATFORM TABLES DATA ENTITY NAME ALIAS Ret. I ASSOCIATION INFO CUSTOHER/CLF ASSOCIATION TABLE 76 CLF PROFILE CLF MASTER TABLE 77 CUSTOMER PROFILE CUSTOMER MASTER TABLE 78 DISTRIBUTION INFO FORM DISTRIBUTION TABLE 79 FIELD DESCRIPTIONS FORM FIELD DEFINITION TABLE 80 FORM FILENAMES FORM DISTRIBUTION FILENAMES TABLE 81 FORM PROFILES FORM MASTER TABLE 82 FORM SH £ PRINTER INFO FORMS SH/PRINTERS TABLE 83 PRINTER IDENTIFIERS FORM FILE PRINTER TYPES TABLE 84 SYSTEM PARAMETER INFO FAP SYSTEM PARAMETER TABLE 85 Each file typically has a number of elements, either of the number or character type, having predefined lengths. A listing of the elements, type (characters or numerical), field length, and description of the elements, for each of the tables 76-85 of FIGURE 6 is as follows: Nane: ASSOCIATION INFO; 76 ALIAS: CUSTOHER/CLF ASSOCIATION TABLE ELEMENT NAME COLUMN NAME TYPE LENGTH CLF ID CLFJD CHAR (8) CUSTOMER IDS CUST_ID CHAR (15) PRIMARY KEY: (CLFJD, CUST.ID) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: DEPENDENT OF: CUSTOMER MASTER TABLE - CUST.HAST CLF MASTER TABLE - CLFJJAST CREATED IN: FAPDB.SQL script CREATE TABLE CLF_CUST ( CLFJD CHAR (8), CUSTJD CHAR (15) ) DESCRIPTION Uniquely identifies each Central Library Facility. Custoner ID. Uniquely identifies each custoner. 26 270986 NAME: CLF PROFILE; 77 ALIAS: CLF MASTER TABLE ELEMENT NAME COLUHN NAME TYPE LENGTH CLF ID CLF-ID CHAR (8) CLF DESCRIPTION CLF.DESC CHAR (40) CLF LOCATION LOCATION CHAR (25) CLF ADMINISTRATOR ADMIN CHAR (30) CLF PHONE NUMBER PHONE.NO CHAR (15) CLF MODEM NUMBER MODEM.NO CHAR (15) CLF FAX NUMBER FAX NO CHAR (15) DESCRIPTION Uniquely identifies a Central Library Facility.

Description of the Central Library Facility environnent.

Description of the Central Library Facility Location.

Nane of the CLF Adninistrator.

Phone nunber of the CLF location.

Moden phone nunber of the CLF location.

Fax phone nunber of the CLF location.

PRIMARY KEY: (CLF-ID) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: PARENT OF: CUSTOMER/CLF ASSOCIATION TABLE - CLF.CUST CREATED IN: FAPDB.SQL script CREATE TABLE CFL.MAST ( CLFJD CHAR (8), CLF-DESC CHAR (40), LOCATION CHAR (25), ADMIN CHAR (30), PRONEJO CHAR (15), HOOEMJO CHAR (15), FAX NO CHAR (15) ): NAME: CUSTOMER PROFILE; 78 ALIAS: CUSTOMER MASTER TABLE 27 ELEMENT NAME COLUMN NAME TYPE LENGTH DESCRIPTION CUSTOHER ID CUSTJD CHAR (15) Custoner Identifier. Uniquely identifies a custoner.

CUSTOMER NAME CUSTJAME CHAR (30) Custoner's full nane.

FORM PATHNAME EORH.PATH CHAR (75) Full Pathnane cn systen where custoner's forns are located NO OF REVISIONS NOJEVS NUMBER (1) Nunber of revisions supported on the systen for a custoner ADDRESS LINE 1 ADDR1 CHAR (30) Street address line 1.

ADDRESS LINE 2 ADDR2 CHAR (30) Street address line 2.

CITY CITY CHAR (25) City address line.

STATE/PROVINCE STATE CHAR (4) State or province address line.

ZIP ZIP CHAR (10) Zip code address line.

COUNTRY COUNTRY CHAR (4) Country address line.

CONTACT NAME CONTACT CHAR (30) Nane of custoner contact person.

PHONE NUMBER PHONE.NO CHAR (15) Phone nunber of custoner.

FAX NUMBER FAXJIO CHAR (15) Fax phone nunber of custoner.

SHIPPING LINE 1 SHIPJDDR1 CHAR (30) Shipping address line 1.

SHIPPING LINE 2 SHIPJDDR2 CHAR (30) Shipping address line 2.

SHIPPING CITY SHIP.CITY CHAR (25) Shipping city address line.

SHIPPING STATE/PRO SHIP-STATE CHAR (4) Shipping state or province line.

SHIPPING ZIP SHIP.ZIP CHAR (10) Shipping zip code address line.

SHIPPING COUNTRY SHIP-COUNTRY CHAR (4) Shipping country address line.

SHIPPING ATTENTION SHIPJTTN CHAR (30) Nane of person for ship-to attention.

PRIMARY KEY: (CUSTJD) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: PARENT OF: FORM SH & PRINTER INFO TABLE - CUST.MHSH 28 ASSOCIATION INFO TABLE - CLF.CUST FORM PROFILE TABLE - FORM_MAST DEPENDENT OF: CREATED IN: FAPDB.SQL script CREATE TABLE CUSTJ4AST ( CUSTJD CHAR (15), CUSTJAME CHAR (30), FORM_PATH CHAR (75), NO_REVS NUHBER (1), ADDR1 CHAR (30), ADDR2 CHAR (30), CITY CHAR (25), STATE CBAR w, ZIP CHAR (10), COUNTRY CHAR <4), CONTACT CHAR (30), PHONENO CHAR (15), EAX_N0 CHAR (15), SHIP_ADDR1 CHAR (30), SHIP_ADDR2 CHAR (30), SHIP_CITY CHAR (25), SHIP_STATE CHAR <4>, SHIPJIP CHAR (10), SHIP_COUNTRY CHAR (4), SHIP.ATTN CHAR (30), 29 270986 NAME: DISTRIBUTION INFO; 79 ALIAS: FORH DISTRIBUTION TABLE ELEMENT NAME COLUHN NAME TYPE CUSTOMER ID CUSTJD CHAR CLF ID CLFJD CHAR VENDOR FORtf ID FORMJD CHAR VENDOR FORH REV FORM_REV NUMBER DIST INDICATOR DISTJLAG CHAR DIST STATUS DIST.STATUS CHAR DIST DATE DIST_DATE DATE HEADER FILENAME HDRJILE CHAR DIST FILENAME DISTJILE CHAR PRIHARY KEY: (CUSTJD CLFJD, FORMJD, FORH .REV) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: None CREATED IN: FAPDB.SQL script CREATE TABLE DISTJNFO / \ CUSTJD CHAR (15), CLFJD CHAR (8), FORMJD CHAR (8), FQRM_REV NUMBER (1>, DISTJLAG CHAR (1), DIST.STATUS CHAR (1), DIST_DATE DATE, LENGTH DESCRIPTION (IS) Custoner Identifier. Uniquely identifies a custoner. (8) Uniquely identifies a Central Library Facility. (8) Uniquely identifies a forn for a custoner. (1) Uniquely identifies a revision of a forn for a custoner. (1) Indicates whether or not a forn has been selected for distribution to a CLF. (1) Indicates the distribution status of the forn.

Date of distribution to a CLF. (12) Nane of the header file for the Corn. (12) Nane of the packed distribution file for the forn.

HDRJILE DISTJILE ); CHAR (12), CHAR (12) NAME: FIELD DESCRIPTION; 80 ALIAS: FORH FIELD DEFINITION TABLE ELEMENT NAME COLUMN NAME TYPE LENGTH CUSTOMER ID CUSTJD CHAR (15) FORM ID FORMJD CHAR (8) FORM REV FORM.REY NUMBER (1) FORM FIELD NUMBER FID JO NUMBER (3) FORM FIELD NAHE FLDJAME Cf'AR (20) FORH FIELD LOC FLDJOC CHAR (20) FORH FIELD LENGTH FLDJEN NUMBER (5) FORH FIELD TYPE FLDJYPE cnAR (10) FORH FIELD FORMAT FLDJORMAT CHAR (30) FORM FIELD VAL FLDJAL CHAR (50) FORM FIELD CALC FLD.CALC CHAR (80) DESCRIPTION Custoner 10. Uniquely identifies a custoner. Uniquely identifies a forn for a custoner. Uniquely identifies a revision of a forn.

Forn field nunber or tabbing order.

Forn field nane.

Forn field coordinate location.

Forn field length.

Forn field data type.

Forn field data format.

Forn field validation.

Forn field calculation.

PRIMARY KEY: (CUSTJD, FORMJD, FORH.REV) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: DEPENDENT OF: FORM PROFILE TABLE - FORH_MAST CREATED IN: FAPDB.SQL script CREATE TABLE FORHJLDS ( 270986 CUSTJD CHAR (15), FORMJD CHAR (8), FORM_REV NUMBER (1), FLD_NO NUMBER (3), FLDJAME CHAR (20), FLD.LOC CHAR (20), FLD-LEN NUMBER (5), FLDJYPE CHAR (10), FLD-FORMAT CHAR (30), FLD_VAL CHAR (50), FLD CALC CHAR (80) ): NAME: FORH FILENAMES; 81 ALIAS: FORK DISTRIBUTION FILENAMES ELEMENT NAME COLUMN NAME TYPE LENGTH CUSTOMER ID CUSTJD CHAR (15) FORM ID FORMJD CHAR (8) FORM REV FORM.REV NUMBER (1) CLF ID CLFJD CHAR (8) FORM FILE NAME FILEJAME CHAR (12) FORM FILE TYPE FILiVTYPE MAR (1) FORM PRINTER TYPE FILE EXT CHAR (2) PRIMARY KEY: (CUSTJD, FORMJD, F0RM_REV, CLFJD) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: DESCRIPTION Custoner ID. Uniguely identifies a custoner. Uniquely identifies a forn for a custoner. Uniquely identifies a form revision for a forn. Uniquely identifies a Central Library Facility Form filenane including file extension.

Form file type.

Type of printer forn is designed for.

DEPENDENT OF: 270986 FORH PROFILE - FORHJttST TABLE CREATED IN: FAPDB.SQL script CREATE TABLE FORMJILES ( CUSTJD CHAR (15), FORMJD CHAR (8), FORM_REV NUMBER (1), CLFJD CHAR (8), FILEJJAME CHAR (12), FILE_TYPE CHAR <».

FILE EXT CHAR (2) ); NAME: FORH PROFILE; 82 ALIAS: FORH HASTER TABLE ELEMENT NAME COLUMN NAME TYPE LENGTH DESCRIPTION CUSTOMER ID CUSTJD CHAR (15) Custoner ID. Uniquely identifies a custoner.

FORH ID FORMJD CHAR (8) Uniquely identifies a forn for a custoner.

FORH REV FORM.REV NUMBER (1) Uniquely identifies a revision of a forn.

FORM DESCRIPTION FORM_DESC CHAR (40) Description of forn.

FORM CATEGORY FORM_CAT CHAR (10) Category that forn belongs to. NOT USED.

FORH SUB CATEGORY FORM_SUB CHAR (10) Sub category that forn belongs to within category. NOT USED.

FORM PATHNAME FORH_PATII CHAR (75) Full pathnane of directory where forn is stored.

FORM DESIGN SH FORH_SH CHAR (8) Executable nane of forn design software used.

FORH DESIGN STATUS FORM_STATUS CHAR (1) Design status of the forn.

RELEASE STATUS REL.STATUS CHAR (1) Release status of the forn.

FORM HIDTH FORH_HDTH NUMBER (4, 2) Width of forn.

FORM LENGTH FORM_LEN NUMBER (4, 2) Length of forn NUMBER OF PAGES NO.PAGES NUMBER (3) Nunber of pages in the forn. 33 270986 NUMBER OF PARTS NO.PARTS NUMBER (3) Nunber of parts to the forn.

DUPLEX INDICATOR DUPLEX CHAR (1) Indicator of whether or not the forn is to be printed duplex.

PAGE ORIENTATION PGORIENT CHAR (9) Page orientation of the forn.

FORM CREATION DATE CREATEJ1ATE DATE Systen date on which forn was created.

CREATOR NAME CREATEJAME CHAR (10) Nane of person who created forn.

FORH MODIF DATE MODJATE DATE Systen date on which forn was last nodified.

MODIFIER NAME MODJAHE CHAR (10) Nane of person who last nodified forn.

FORM RELEASE DATE RELJATE DATE Systen date on which forn was last released.

RELEASOR NAME RELJAME CHAR (10) Nane of person who last released forn.

PRIHARY KEY: (CUSTJD, FORMJD, FORM.REV) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: PARENT OF: FORM FILENAMES TABLE - FORMJILES FIELD DESCRIPTIONS TABLE - FORHJLDS DEPENDENT OF: CUSTOHER MASTER TABLE - CUST-MAST CREATED IN: FAPDB.SQL script CREATE TABLE FORM.HAST ( CUSTJD CHAR (15), FORH J D CHAR (8), FORHJEV NUMBER H), FORMJESC CHAR (40), FORM_CAT CHAR (10), FORM_SUS CHAR (10), FORMJATII CHAR (75), FORM.SW CHAR (8), 34 FORM_STATUS CHAR (1), REL.STATUS CHAR (1), FORKJfDTH NUMBER (4, 2) FORH JEN NUMBER (4, 2) NOJAGES NUMBER (3), NOJARTS NUHBER (3), DUPLEX CHAR (1), PG_0RIENT CHAR (9>, CREATE.DATE DATE, CREATE JIAHE CHAR (10), M0D_DATE DATE, HOD_NAME CHAR (10), REL_DATE DATE, REL NAME CHAR (10) ); NAME: FORHS SH/PRINTERS; 83 At,IAS: FORHS SH/PR INTERS TABLE ELEMENT NAHE COLUMN NAME TYPE LENGTH DESCRIPTION CUSTOHER ID CUSTJD HW/SH INDICATOR HWSHJYPE HH/SH NAHE HHSHJAHE HH/SH DEXRIPTION HWSW DESC CHAR (15) Customer ID. Uniquely identifies a custoner.

CHAR (1) Indicates whether entry is hardware (printer) or software.

CHAR (8) Executable or invokable nane of hardware of software.

CHAR (40) Description of hardware or software.

PRIHARY KEY: (CLF_ID, CUSTJD) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES; DEPENDENT OF: CUSTOMER MASTER TABLE - CUSTHAST CREATED IN: FAPDB.SQL script CREATE TABLE CUST NWSW ( CUSTJD HWSHJYPE HWSWJAHE HWSHJJESC ); CHAR CHAR CHAR CHAR (15), (1). (8), (40) NAME: PRINTER IDENTIFIERS; 84 ALIAS: PRINTER TYPE TABLE 27 ELEMENT NAME FORH SH NAHE FORH FILE TYPE PRINTER TYPE COLUMN NAHE TYPE LENGTH DESCRIPTION FORH.SW FILE.TYPE FILE EXT CHAR (8) Forn software executable nane.

CHAR (1) Forn software file type.

CHAR (2) Printer type supported in forn software.

PRIHARY KEY: (EORM_SW) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: PARENT OF: FORH FILENAMES TABLE - FORHJILES DEPENDENT OF: CREATED IN: FAPDB.SQL script CREATE TABLE FILEJXT ( FORM SW CHAR (8), 270 9 & tj 36 FILE_TYPE CHAR (1), FILE_EXT CHAR (2) >; NAME; SYSTEM PARAMETER INFO; 85 ALIAS: FAP SYSTEH PARAMETER TABLE ELEMENT NAME COLUMN NAHE TYPE LENGTH DESCRIPTION FA!? ID FAPJD CHAR (8) Uniquely Identifies a Forns Automation Platforn.

FAP DESCRIPTION FAP.DESC CHAR (40) Description of the Forns Autonation Platforn environnent.

FAP LOCATION FAP_LOC CHAR (20) Location for Forns Autonation Platforn.

FAP ADMINISTRATOR ADMIN CHAR (30) Nane of the Forns Autonation Platforn Adninistrator.

FAP PHONE NUMBER PHONEJIO CHAR (15) Forns Autonation Platforn location phone nunber.

FAP MODEM NUMBER HOOEMJO CHAR (15) Forns Autonation Platforn noden phone nunber.

FAP FAX NUMBER FAX.NO CHAR (15) Forns Autonation Platforn fax phone nunber.

NUMBER OF REVS NO_REVS NUMBER (1) Number of forn revisions supported on a Forns Autonation Platforn.

PRIHARY KEY: (FAPJD) INDEXES: None defined.

RELATIONSHIP TO OTHER TABLES: None CREATED ID: .

FAPDB.SQL script CREATE TABLE SYSJARAMS ( FAPJD CHAR (8), FAPJJESC CHAR (40), FAPJCC CHAR (20), ADMIN CHAR (30), 27 0 37 PHONE NO CHAR MOOEH NO CHAR (15) FAX NO CHAR (15) NO REVS NUMBER (1) >; FIGURE 7 is a data flow diagram for the FAP 14. Utility, report generation, archiving, form maintenance, profile maintenance, and CLF 12 updating functions are provided, as illustrated in FIGURE 7. The interrelationships between the various components as shown in FIGURE 7 are more fully indicated by FIGURES 8a-8e.

FIGURE 9 provides a flow chart indicating the general steps executed by FAP 14 for accessing the CLF 12 from the FAP to transfer form information. The program is initiated from a command file, as indicated at 100. A session with a target CLF 12 is allocated. This step is indicated since typically a vendor's FAP 14 can be associated with more than one CLF 12, for example a centralized location for the FAP 14 may serve a number of CLFs 12, one associated with each different customer (each customer having a plurality of geographically remote user stations). At 102, the files indicated for transfer are transferred from the FAP 14 to the targeted CLF 12, and confirmation is provided at 13. Then the remote CLF table population function is initiated at 104, and when that function is completed it is confirmed at 105. Data may then be sent to and from the CLF 12 from and to the FAP 14 at 106, for example data useful for determining the status of the forms. An acknowledgement is issued at 107, and any post 270 38 completion processing done at 108 before the processing ends.

As illustrated in FIGURE 10, the CLF 12 preferably communicates via modems 41 with the FAP 14, or token ring if located in the same facility, and via modems 42 with the host computer 34. In order to provide human interface, a terminal 143 having a video display 144 and a keyboard 145 and/or mouse 146, is provided associated, with the CLF 12. Other technologies could also be utilized, such as optical disks, and the like, to store the forms on either magnetic or optical media.

As illustrated schematically in FIGURE 3, major functions of the CLF 12 are forms management and distribution. The application software 29 creates, maintains, up-dates and ensures the integrity of the database 29 provided by CLF 12. The CLF 12 also processes end user requests inputted by device 143 (e.g. via the various electronic communications facilities already discussed), and distributes electronic forms to all of the user locations 15. Inherent in the CLF 12 is restricted user access based on security levels, the production of desired reports to support the customer's requirements, sorting of the contents of the library based upon user specified parameters, and up-dated processing. At the CLF a search will be conducted of the electronic forms database 29 on a predetermined basis, to determine all forms scheduled for release on a specified date. The forms will then be distributed based upon the end user profiles which have been designated. The CLF 12 is a logical entity, and its processes may be distributed over 27 39 one or more processors, either directly on the customer's main frame 34, or at the vendor's facility, utilizing a file server, or the like.

User interface software executed by CLF 12 is menu driven in the preferred embodiment. The major menu items provided to the user of the CLF 12 main menu screen utilizing terminal 143 are forms, profile management, distribution management, release function, queries and report, and utilities. A typical main menu screen is as follows: CENTRAL LIBRARY FACILITY MAIN MENU Enter the Capital Letter of the Item Below and Press Enter-> -- Forms management Profile management Distribution management Release function Queries and reports Utilities F3=EXIT The first item of selection is "Forms management". The Forms management menu typically appears as follows: 40 270 9 a CENTRAL LIBRARY FACILITY FORMS MANAGEMENT MENU Enter the Capital Letter of the Item Below and Press Enter-> -- List/delete/update forms Field information list Output format list Print form F2=REFRESH F3=EXIT The first selectable item from the Forms management menu is the forms list. A forms list screen, showing descriptions and other information of a few exemplary forms might appear as follows: CENTRAL LIBRARY FACILITY FORHS LIST Type a P in the action column to print and press PF4.

Revision Release Creation Action Form Id Status Date Date Date Forms Description _ CSADRTIN CUR - - - CUSTOHER ADDRESS & TI CSDEMOGR CUR - - - DEMOGRAPHIC INFORMATl _ CSSGNCRD CUR - - - SIGNATURE CARD CSUMIVER CUR - - UNIVERSAL FORH F3-EXIT F4-QUEUE PRINT The last of the selectable items in the Forms management menu is the forms print selection, the screen for which might appear as follows: 270 CENTRAL LIBRARY FACILITY PRINT FORHS Enter nunber of copies and destination for each forn More: ♦ NUHBER PRINTER SITE CANCEL FORH ID FORH DESCRIPTION COPIES ID ID PRINT CSSGNCRD SIGNATURE CARD N PF3-EXIT PF4-PR0CESS REQUEST PF8-NEXT FORH By filling information into the prompt sections of this screen, an operator of CLF terminal 43 can schedule printing of a desired number of copies of specific forms to a desired printer at a desired use location.

The second menu item in the main menu is the profile management option. The typical profile management menu screen appears as follows: 42 270 CENTRAL LIBRARY FACILITY PROFILE MANAGEMENT MENU Enter the Capital Letter of the Item Below and Press Enter-> User profile Category profile Site profile corporate proFile Geographic profile cusTomer profile grOup profile Printer profile F2=REFRESH F3=EXIT The first selectable item of the profile management menu is the user profile, a screen of which appears as follows: 43 C* "v x , .

USER PROFILE Update/Delete: Type "U" and/or "D" in ACTION column and press "ENTER" Add: Press F4; Associations: Type an "S" i ACTION column and press F6 ACT USER USER NAME CORP GEO.

ID ID ID FLAG DATE TIME - TOH Ton - CLA Cristie 111 Y 12-10-1990 10:10:10 - DLY Donna - FEA Fran - JOE Joe 111 232 - JZA Julie - SAM SAM D002 **** END OF OUTPUT «*** F2-REFRESH F3-EXIT F4-ADD If F4 is actuated from the above screen, then the following screen appears: 44 27086 USER PROFILE ADO Enter Data in all fields -- THEN press "ENTER" User ID : User Nane Corporate ID..: Geographic ID.: Telephone No..: Distribution Ticklcr Flag Anin. flag. gut Data***"*"*"*******"*'****"** Lock Out Date: Lock Out Tine: Lock Out Flag.: version 0.1 .ekF2-REFRESH F3-EXIT The third selectable item from the profile management menu is the site profile. The site profile screen appears as follows: CENTRAL LIBRARY FACILITY SITE PROFILE Custoner ID: 2-4561686-00000 Custoner Kane: State Bank Site ID Site Description Orographic ID Network ID FLA001 Tampa Banking Dept TPA001 FLATPA01 GE0001 Atlanta Branch ATL001 GEOATLOl NYC002 New York Branch WC001 NYNYC02- CHI003 Chicago Branch CHI001 ILCHI01 SCA001 South Carolina Office CAE00I SCACAE01 PF3-EXIT The sixth menu item on the profile management menu screen is the customer profile. When that menu item is selected, the customer profile screen typically appears as follows: CENTRAL LIBRARY FACILITY CUSTOMER PROFILE 2-4561686-00000 State Bank The American Road Atlanta GA 30123 USA Don Jones 800-321-1234 PF3=EXIT Customer ID: Customer Name: Address: Contact Name: Phone Number: The Group profile of groups list item provides the following exemplary screen: 2709b' GROUPS LIST UPDATE/DELETE: Type U and/or D in action column and press Enter. ADD: Press F4; ASSOCIATION: Type an S in action column and press F6.

Action Group ID Seq. # Group Description Test 1 Test 2 Test 3 Test 4 Test 5 Test 6 New Group Added First MRC Group 1 1 2 1 2 3 1 1 0002 F3-EXIT 61 G2 G2 G3 G3 G3 GRP101 MRC 001 ***** END OF OUTPUT ***** F4-ADD F6-ASS0CIATI0NS F12-CANCEL If F4 is actuated from the above screen, then the following exemplary screen appears.

ADD DISTRIBUTION GROUP Type in entries for the distribution group and press <Enter> to add.

Group Id Sequence Number ...

Group Description F3-EXIT F12-Cancel If F6 is actuated from the Groups list screen, then the following appears: 47 27098 ASSOCIATION HENU Type the Id of a base item and press <Enter>, OR type an "S" and press <Enter> for a selection listing of the base iten.

Base Iten Id Association Itens _F0RM _GR0UPS _GR0UP ID .FORMS .SITES SEQ. NUMBER .... _USER _SITES _SITE JJSERS .PRINTERS .GROUPS .PRINTER SITES F3-Exit F12-Cancel Upon insertion of a particular group ID from the groups list screen (e.g. "Gl"), the following exemplary screen appears: SITES ASSOCIATED WITH A GROUP Group ID: Gl SEQ: 1 DESC: TEST 1 ADD: Press F4; DELETE: Type a "D" in action column and press <Enter>. ACT SITE DESCRIPTION CORP GEO. HODEM TELEPHONE NET ID ID ID ID KANSAS KANSAS SI SIT101 NEW SITE ADDED HISC WISCONSIN D002 **** END OF OUTPUT ***** F3-EXIT F4-AD0 F12-CANCEL 48 2/09 q If F4 is actuated from the above screen, then the following exemplary screen appears, to support data entry to get sites associated with a group: ADO SITES ASSOCIATED WITH A GROUP To add items to the association list, type one or more "S" in MORE: + the action colunn and press <Enter>.

SITE DESCRIPTION CORP GEO.

M00EM TELEPHONE NET ID ID ID ID ALA ALABAMA CALIF CALIFORNIA COLO COLORADO COLNET FLA FLORIDA FLANET KANSAS KANSAS MASS MASSACHUSETTS MICH MICHIGAN MINN MINNESOTA 55543210000000000 SI S2 S3 SIT101 NEW SITE ADDED 12- -1-90 F3-EXIT F8-FWD F12-CANCEL The last selectable item on the profile management menu is the printer profile option. When the printer profile option is selected, the screen that typically appears is as follows: 49 Customer ID: CENTRAL LIBRARY FACILITY PRINTER PROFILE 2-4561686-00000 Customer Name: State Bank Printer ID Printer Type Printer Manufacturer Name 01 PS Adobe PostScript Hewlett Packard LaserJet 02 HP 03 AF IBM 3800 Printers IBM 4019 Printer 04 05 AF MF XEROX 9700 Printer PF3=EXIT The third selectable item on the main menu is the distribution management function. If that function is selected, the screen that typically appears is as follows: Enter the Capital Letter of the Item Below and Press Enter-> The fourth selectable item on the main menu is the release function. If that function is selected, the screen that typically would appear is as follows: CENTRAL LIBRARY FACILITY DISTRIBUTION MENU New form distribution cycle Add form distribution Delete form distribution FS=REFRESH F3=EXIT 50 27098 CENTRAL LIBRARY FACILITY RELEASE FORMS MENU Enter the Capital Letter of the Item Below and Press Enter -> Release forms to site Automatic release release From remote site F2=REFRESH F3=EXIT The first selectable item on the release forms menu is to release the.form to desired sites. If that item is selected, the typical screen that would appear is as follows: CENTRAL LIBRARY FACILITY RELEASE TO SITES Do you wish to release New/revised forms (N) or All forms (A)? Enter Selection here (N, A) > Also select one of the choices below: Release All Forms to All Sites Release All Forms for Specific Site(s) Release Specific Forms(s) to All Sites Release Specific Form(s) to Specific Sites F2=Refresh F3=Exit The above provides a description for the major screens that appear in the implementation of the CLF 12 functions, although other screens are provided too, for example customer specific screens depending upon what queries and reports are desired, and conventional utilities functions. 2709 FIGURE 11 is a data model diagram for the CLF 12. The individual components illustrated in FIGURE 11 are individual files which have particular elements or records therein in predefined fields and with predefined addresses. The bare essentials of the system are contained within the dotted lines, but the other files are also important for ultimate maximum utilization. The connections in FIGURE 11 refer to the relationship between the two entities; i.e. two entities connected by an arrow with one arrow head at one end and a double arrow head at the other end are said to have a "one-to-many" relationship. In a relational database construct, this means that for each parent record in the first entity there may/shall exist many child records in the second entity. In the preferred embodiment, the various files have the following major elements: The customer profile file 150 contains all relevant information about the customer. The configuration of that file is as follow: 52 2709 i 6 TABLE NAME: CUSTOMER PROFILE ALIAS: CP ELEHEKT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Custoner ID CP_CUS_ID 1 006 Uniquely identifies each custoner.

Country Indicator CP_HBF_CTRY_ID E 001 Country indicator for the custoner ID.

Custoner ID CP_HBF_ID E 015 Corporate identifier for a custoner.

Custoner Nane CP-NME E 030 Nane of custoner.

ADCR1 CP_ADR_1 E 030 Street address one.

ADDR2 CP_ADR_2 E 030 Street address tvo.

City CPCTY E 030 Nane of city.

State Prov CP.STE E 004 State or province abbreviation.

Zip CP_ZIP E 010 The custoner's zip code (U.S.) or postal code.

Country CP.CTRY E 004 Nane of country in which the custoner is located.

Nun Versions CP_NBR_ARC E 001 Nunber of archived forn versions to keep.

Contact Nane CP_CTC E 030 Nane of the contact person at the custoner location.

Contact Phone CP_CTC_TEL E 015 Phone nunber of the custoner contact person.

Custoner Status CP_STA_CDE E 001 Current CLF custoner status V - deleted 'A1 - Activ< Custoner Status Date CP_STA_DTE E 008 Date of status change for custoner CLF ID CP_CLF_ID E 010 A unique identifier for each custoner's CLF Nun Levels CP_NBR_LVL E 001 The nunber of corporate organization levels to be uset Level Nane 1 CP_C0RP_LVL_1 E 015 First nane for corporate level definition Level Nane 2 CP_C0RP_LYL_2 E 015 Second nane for corporate level definition Level Nane 3 CP_C0RP_LVL_3 E 015 Third nane for corporate level definition Key Data: Prinary Key (CLF Custoner ID) Indexes: Nane On Coluims Type of Work CusidK CLF Custoner ID Prinary, Ascending, Unique Relationship to Other Tables: Parent of: Forn Profile Category Profile Printer Profile 270 Corporate Profile Geographic Profile User Profile Site Profile Group Profile All Tables are Access Thru CLE Custoner ID As many corporate level definitions may be provided as is necessary in order to meet the customer's needs.

The corporate profile provides a file 151 for the customer to charge back the forms to various entities within the organization. This file typically has the same number of levels as the nunvber of levels for the corporate level definition in the customer profile file 150. An exemplary corporate profile file 151 is as follows: 54 270 (i TABLE NAHE: CORPORATE PROFILE ALIAS: CO ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Custoner ID Corporate ID 006 006 Level 1 E 020 Level 2 E 020 Level 3 E 020 Rev Data: Prinary Key (CLF Custoner ID, Corporate ID) Foreign Key FK.C0RPA (CLF Custoner ID) References Custoner Profile on Delete Cascade; Indexes: Nane On Coluims Type of Index Uniquely identifies each custoner.

Code for each different corporate profile for a custoner Highest level in corporate organization.

Second highest level in corporate organization. Third highest level in corporate organization.

CORPIDX CLF Custoner ID Prinary, Ascending, Unique Corporate ID Relationship to Other Tables: Parent of: User Profile Thru CLF Custoner ID, Corporate ID Site Profile Thru CLF Custoner ID, Corporate ID Dependent of: Custoner Profile Thru CLF Custoner ID The geographic profile file 152 has data for the various geographically remote user locations, such as branches, offices, etc. A typical geographical profile file 152 is configured as follows: 55 27098 TABLE NAME: GEOGRAPHIC PROFI ELEMENT/RECORD DB TABLE ELE. KEY LEN CLF Custoner ID 1 006 Geographic ID 2 006 SHSA-Code E 003 Country Nane E 004 Region Nane E 020 State/Province Nane E 004 State Region Nane E 020 City Nane E 030 City Region Nane E 030 Building/Branch ID E 015 Floor Nunber E 003 ALIAS: GP DEFINITION Uniquely identifies each custoner.

Unique Code for each different geographic profile used Nane of Country (International Code).

Nane of Region.

Nane of State or Province.

Nane of Region within a State o: Province.

Nane of City.

Nane of Region within City.

Code to Identify a Building or Branch.

Nunber of the Floor in the Building.

Key Data: Prinary Key (CLF Custoner ID, Geographic ID) Foreign Key FK_GEOA (CLF Custoner ID) References Custoner Profile on Delete Cascade; INDEXES: Nane On Colunns Type of Index DE01DX CLF CUSTOMER ID PRIHARY, ASCENDING, UNIQUE GEOGRAPHIC ID Relationship to other Tables: Parent of: User Profile Thru CLF Custoner ID, Geographic ID Site Profile Thru CLF Custoner ID, Geographic ID Dependent of: Custoner Profile Thru CLF Custoner ID 56 2/OQUq The security table 153 limits access to the various files in the data model of FIGURE 11 to ensure that only people with the appropriate responsibility can command the system to perform important functions. The typical configuration of the security table 153 is as follows: TABLE NAME: SECURITY ALIAS: SE ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Customer ID 1 006 Uniquely Identifies each custoner.

User ID 2 006 The Logon ID associated with each CLF user.

Password 3 006 The Password associated with each user ID.

Security Funct E 001 The Authority to maintain the security table.

Prof Hgmt Funct E 001 The Authority to naintain profile tables.

Form Hgmt Funct E 001 The Authority to naintain the central forms library.

Dist Funct E 001 The Authority to control forn distribution to end sil Release Funct E 001 The Authority to release forms to the end user site.

Report Funct E 001 The Ability to produce reports.

Security Level E 001 Defines the level of authority for each user.

Distribution Tickler Flag E 001 Flag to indicate if new forms have arrived in the system.

Key Data: Primary Key (CLF Customer ID, User ID, Password) Foreign Key FK_Sea (CLF Customer ID, User ID) References User Profile On Delete Cascade; Indexes: Nane On Columns Type of Hork SE1DX CLF Customer ID Primary, Ascending, Unique User ID Password Relationship to Other Tables: Dependent of: User Profile Thru CLF Customer ID, User ID 57 2 'i 0 & b t) The user profile file 154 describes the end user, and it is interrelated with the security table 153. A typical configuration of the user profile file 154 is as follows: TABLE NAME: USER PROFILE ELEMENT/RECORD DB TABLE ELE. KEY ALIAS: UP LEN DEFINITION CLF Custoner ID User ID User Nane User Phone Lock Out Flag Lock Out Date Lock Out Tine Corporate ID Geographic ID Distribution Tickler Flag 1 2 E E E E E E 006 006 030 015 001 002 008 006 006 001 Uniguely identifies each custoner.

The Logon ID associated with each CLF user.

Mane of User.

Telephone nunber of user.

Indicator which allows or prevents a user fron signing on.

Date a user's ID is locked due to invalid access attenpts.

Tine a user's ID is locked due to invalid access attenpts.

Code for each different corporate profile for a custoner.

Unique code for each different geographic profile used.

Flag to indicate new forns have arrived in the database.

Key Data: Prinary Key (CLF Custoner ID, User ID) Foreign Key FKJJSERA (CLF Custoner ID, Corporate ID) References Corporate Profile On Delete Restrict; Foreign Key FKJJSERB (CLF Custoner ID, Geographic ID) References Geographic Profile On Delete Restrict; Foreign Key FKJJSERC (CLF Custoner ID) References Custoner Profile On Delete Restrict; 58 2/09 Indexes: Nane USER1DX USERIDXA On Colunns Type of Index CLF Custoner ID Prinary, Ascending, Unique User ID CLE Custoner ID Ascending Corporate ID USERIDXB CLF Custoner ID Ascending Geographic ID Relationship to Other Tables; Parent of: User/Site Thru CLF Custoner ID, Site Security Thru CLF Custoner ID, User ID • Dependent of: Custoner Profile thru CLF Custoner ID Corporate Profile thru CLF Custoner ID, Corporate ID Geographic Profile thru CLF Custoner ID, Geographic ID 59 The site profile 155 is interrelated with the geographic and corporate profiles. A file in the site profile 155 is provided for each user location. Typically hardware, such as a printer 16 and/or a PC (e.g. 94, at 15), is provided at the geographically remote user locations which correspond to the files in the site profile 155. A typical configuration of the site profile file 155 is as follows: Qff 60 7091? TABLE NAME: SITE PROFILE ELEMENT/RECORD DB TABLE ELE.

KEY LEN CLF Custoner ID ST_CLF_CUS_ID 1 006 Site ID ST_SITE_ID 2 006 Site Description SUBSCRIPTION E 030 Corporate ID ST_C0RP_1D E 006 Geographic ID ST_GEO_ID E 006 Moden Phone STJOOEHTEL E 015 Netvork ID ST_NETKORK_ID E 004 Data Type ST_CHR_TYP E 001 Key Data: Prinary Key (CLF Custoner ID, Site ID) Foreign Key FK_SITEA (CLF Custoner ID) ALIAS: ST DEFINITION Indexes: Nane SITEIDX On Colunns Type of Work Uniquely identifies each custoner.

Identifier to uniquely identify a site for a custoner Description of site Code for each different corporate profile for a custoner Unique code for each different geographic profile use The phone nunber to be dialed for connunications.

The physical connunication identifier Code to indicate if the site is ASCII or EBCIDIC data type References Custoner Profile On Delete Restrict; Foreign Key FK_SITEB (CLF Custoner ID, Corporate ID) References Corporate Profile On Delete Restrict; Foreign Key FK_SITEC (CLF Custoner ID, Geographic ID) References Geographic Profile On Delete Restrict; CLF Custoner ID Prinary, Ascending, Unique Site ID SITEIDXA CLF Custoner ID Ascending Corporate ID SITEIDXB CLF Custoner ID Ascending Geographic ID Relationship to Other Tables; Parent of; User/Site Profile thru CLF Custoner ID, Site ID 61 2/0 9 b Site/Printer Profile thru CLF Custoner ID, Site ID Site/Group Profile thru CLF CuBtoner ID, Site ID Dependent of: Custoner Profile thru CLF Custoner ID Corporate Profile thru CLF Custoner ID, Corporate ID Geographic Profile thru CLF Custoner ID, Geographic ID 62 2709 o u Interrelated with the user profile 154 and the site profile 155 is the user/site data file 156.

This relates a user to a site; a user can only access forms and perform functions as they relate to their accelerated site. A typical configuration of element 156 is as follows: TABLE NAME: SITE/USER DATA ALIAS: SU ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Custoner ID 1 006 Uniquely identifies each custoner.

Site ID 2 006 Identifier to uniquely identify a site for User ID 3 006 The Logon ID associated with each CLF user.

Key Data: Primary Key (CLF Customer ID, Site ID, User ID) Foreign Key FK_SUA (CLF Custoner ID, User ID) References User Profile On Delete Cascade; Foreign Key FK_SUB (Clf Custoner ID, Site ID) References Site Profile On Delete Cascade; Indexes: Nane On Colunn6 Type of Index SUIDX CLF Custoner ID Prinary, Ascending, Unique Site ID User ID SUIDXA CLF Custoner ID Ascending User ID CLF Custoner ID Ascending Site ID SUIDXB Relationship to Other Tables: Dependent of: User Profile thru CLF Custoner ID, User ID Site Profile thru CLF Custoner ID, Site ID 63 270906 The group profile file 157 relates to groups of forms. A group is a particular combination of electronic forms, i.e. a segmentation scheme for the forms, grouped for the purpose of distribution to sites or different organizations. A typical configuration of the group profile file 157 is as follows: TABLE NAME: GROUP PROFILE ALIAS: GR ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Custoner ID GR_CLF_CUS_ID 1 006 Uniquely Identifies each custoner.

Group ID GR_GRP_ID 2 006 Code to uniquely identify the distribution group.

Group Sequence Nunber GR_GRP_SEQ_NBR 3 003 Sequence nunber to control level within a group.

Group Description GR-GRP_DSC E 030 Description of the distribution group.

Key Data: Prinary Key (CLF Custoner ID, Group ID, Group Sequence Nunber) Foreign Key FK_GRPA (CLF Custoner ID) References Custoner Profile On Delete Cascade; Indexes: Nane On Coltunns Type of Index GRP1DX CLF CustoRer ID Prinary, Ascending, Unique Group ID Group Sequence Nunber Relationship to Other Tables: Parent of: Site/Group thru CLF Custoner ID, Group ID, Group Sequence Nunber Group/Forn thru CLF Custoner ID, Group ID, Group Sequence Nunber Dependent of: Custoner Profile thru CLF Custoner ID 27 64 Interfacing between the site profile 155 and the group profile 157 is the site/group data file 158. This assigns a group to a site — i.e. specific groups of forms are distributed to the sites they are associated with. A typical configuration of the file 158 is as follows: 2709 TABLE NAME: SITE/GROUP DATA ALIAS: SG ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Customer ID SG_CLF_CUS-ID 1 006 Uniquely identifies each customer.

Site ID SG_SITE_1D 2 006 Identifier to uniquely identify a site for a custoner Group ID SG_GRP_ID 3 006 Code to uniquely identify the distribution group Group Sequence Number SG_GRP_SEQ_NBR 4 003 Sequence number to control level within a group Key Data: Primary Key (CLF Custoner ID, Site ID, Group ID, Group Sequence Nunber) Foreign Key FK_SGA (CLF Custoner ID, Site ID) References Site Profile On Delete Cascade; Foreign Key FK_SGB (CLF Custoner ID, Site ID) References Group Profile On Delete Cascade; Indexes: Nane On Colunns Type of Index SGIDX CLF Custoner ID Prinary, Ascending, Unique Site ID Group ID Group Sequence Nunber SGIDXA CLF Customer ID Ascending Site ID SGIDXB CLF Custoner ID Ascending Group ID Group Sequence Number Relationship to Other Tables-.

Dependent of: Site Profile thru CLF Customer ID, Site ID Group Profile thru CLF Customer ID, Group ID, Group Sequence Nunber 66 The printer profile file 159 has information regarding the model and manufacture of each of the printers that will be controlled by the computers of the system 10. The typical configuration of the printer profile file 159 is as follows: 67 27 0915$ PRINTER PROFILE DB TABLE ELE. KEY LEN PP_CLF_CUS_ID 1 PP_PTR_ID 2 PP PTS TYP E TABLE NAME: ELEMENT/RECORD CLF Custoner ID Printer ID Printer Type Printer Type Description PP_PTR_DSC E Printer HFR Nane PP_PTR_MFR_NME E Key Data; Prinary Key (CLF Custoner ID, Printer ID) Foreign Key FK_PTRA (CLF Custoner ID) References Custoner Profile On Delete Cascade; Indexes; On Colunns ALIAS: PP DEFINITION 006 006 002 015 020 Uniquely identifies each custoner.

Code to uniquely identify each printer.

Code of printer type (see list below). Description of the printer and printer type Nane of printer nanufacturer Nane PTRIDX Type of Index CLF Custoner ID Prinary, Ascending, Unique Printer ID Relationship to Other Tables; Parent of; Dependent of; Printer Type Codes; Site/Printer Thru CLF Custoner ID, Printer ID Custoner Profile thru CLF Custoner ID Code Description HP HP PCL H5 HP PCL 5 AF AFP MF META FILE DT DOT MATRIX XC XICS PS POSTSCRIPT DC DOT MATRIX COLOR 68 2/0 Interrelated with the site profile file 155 and the printer profile file 159 is the site/printer data file 160. Some forms will be printed at the user sites, while other forms will be printed by the vendor. The site/printer data file 160 is utilized only for those forms which will be printed by the user at the user's locations, which printers (e.g. 16) may have different printer formats. A typical configuration of the site/printer data file 160 is as follows: 2/0 9 L i. 69 TABLE NAME: SITE/PRINTER DATA ALIAS: SP ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Customer ID Site ID Printer ID Printer Type K°v Data: SP_CLF_CUS_ID SP_SITE_ID SP_PTR_ID SP-PTR-TYP 006 006 006 002 Prinary Key (CLF Customer ID, Site ID, Printer Type) Foreign Key FK_SPA (CLF Customer ID, Site ID) References Site Profile On Delete Cascade; Foreign Key FK-SPB (CLF Customer ID, Printer ID) References Printer Profile On Delete Cascade; Indexes: Uniquely identifies each customer Identifier to uniquely identify a site for a custom r Identifier to uniquely identify a printer Code of printer type (see list below under printer profile) Nane On Columns Type of Index SPIDX CLF Customer ID Primary, Ascending, Unique Site ID Printer ID SPIDXA CLF Custoner ID Ascending Site ID SPIDXB CLF Custoner ID Ascending Printer ID Relationship to Other Tables: Parent of: Distribution Profile thru CLF Customer ID, Site ID, Printer ID Dependent of: Printer Profile thru CLF Customer ID, Printer ID Site Profile Thru CLF Customer ID, Site ID ^ v> 70 The distribution data file 161 is interrelated to the site/printer data file 160 and the form profile data file 162. The typical configuration of the distribution data file 161 is as follows: TABLE NAME: DISTRIBUTION PROFILE ALIAS: DP ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION CLF Custoner ID DP_CLF_CUS_ID 1 006 FORH ID DP_FRM_ID 2 008 SITE ID DP.SITJD 3 006 Printer Type DP_PTR_TYPE 4 002 Printer ID DP.PTRJD 5 006 Release Code SP_RLS_CDE E 001 Xnit Date DP_XMIT-DTE E 008 Key Data: Prinary Key (CLF Custoner ID, Forn ID, Site ID, Printer ID) Foreign Key FK_DPA (CLF Custoner ID, Forn ID) References Forn Profile on Delete Cascade; Foreign Key FK_DPB (CLF Custoner ID, Site ID, Printer ID, Printer Type) References Site/Printer Data On Delete Cascade; Indexes: Nane On Colunns Type of Index Uniquely identifies each custoner Code to uniquely identify a forn for a custoner Identifier to uniquely identify a site for a custoner Code of printer type (see 11st on printer profile) Code to uniquely identify a printer Code to indicate release action (see list below) Date the forn vas transmitted (released) to the site DPIDX DPIDXA DPIDXB CLF Custoner ID Primary, Ascending, Unique Form ID Site ID Printer ID CLF Custoner ID Ascending Form ID CLF Custoner ID Ascending Site ID 71 2709b Printer ID Printer Type DPIDXC CLF Custoner ID Ascending Printer Type Relationship to Other Tables: Dependent of: Site/Printer Data thru CLF Custoner ID, Site ID, Printer ID Forn Profile thru CLF Custoner ID, Fotn ID Release Codes: Code Description 0 Forn is current 1 Forn is new to distribution 2 Forns has been revised 9 Forn is inactive (l' ucally deleted) The form profile data file 162 has stored therein the elements of each form and characteristics of the form, e.g. descriptive information. Typically, a number of electronic forms will be stored therein that are identical except for printer formatting since it is necessary to be able to print the same form on a number of different types of printers. The necessary elements for recordation of each form include a unique identifier, a description of the form, the name of the software package (e.g DOCS) used to design the form, a code to indicate whether the form is new or revised, when the form was created and/or last revised, when the form is to be released and/or the previous release dates, the number of parts to the form, the code to identify whether it has a landscape or portrait orientation, the length of the form, and the width of the form. A typical configuration of the form profile data file 162 is as follows: 72 2/00 u 6 TABLE NAME: FORM PROFILE ALIAS: FP ELEHENT/RECORD DB TABLE ELE.

KEY LEN DEFINITION CLF Customer ID FP_CLF_CUS_ID 1 006 Uniquely identifies each custoner.

Forn ID FP.FORHJD 2 008 Code to uniquely identify a forn for a customer.

Forn Sub ID FP_FRM_SUB_ID 3 003 Code to uniquely identify each revision of the forn.

Custoner Catalog Nunber FP_CUS_CAT_NBR E 015 Customers number to identify the forn.

Form Description FP-Description E 030 Description of forn.

Forn Design Software FP_Design_SFW E 010 Software package used to design the fori.

Forn Status Code FP_STA_CDE E 001 Code to indicate that the forn is new or revised.

Forn Creation Date FP_CRE-DATE E 010 Date forn was created (fron FAP).

Form Revision Date FP_REV_DATE E 010 Date forn was last revised (fron FAP).

Form Release Date FP_RLS_DATE E 010 Date the forn is to be released to users.

Prior Release Date FP_OLD_RLS_DTE E 010 Date of the previous release date Category ID fp_ctg_id E 010 Code of forn category to which a forn is assigned FAP ID FP_FAP_ID E 010 Unique identifier of the FAP that created the forn.

FAP Phone Hoden Number FP_FAP_TEL_MODEH E 015 Telephone number of the FAP noden.

Nunber of Parts FP_NBR_PRT E 003 Nunber parts to the forn.

Forms Orientation FP_0RT E 001 Code to identify landscape (L) or portrait (P) node.

Length of Form FP_LEN E 008 Length of the forn.

Width of the Forn FP_WID E 008 Width of the forn.

Key Data-.

Primary Key (CLF Customer ID, Form ID, Forn Sub ID) Foreign Key FK_FPA (CLF Custoner ID) References Custoner Profile On Delete Cascade; Foreign Key FK_FPB (CLF Custoner ID, Category ID) References Category Profile On Delete Set Hull; Indexes: Name On Columns Type of Index FPIDX CLF Customer ID Prinary, Ascending, Unique 73 27098 Forn ID Forn Sub ID FPIDXA CLF Custoner ID Ascending Category ID Relationship to Other Tables: Parent of: Distribution Profile thru CLF Custoner ID, Forn ID Forn Output Fornat thru CLF Custoner ID, Forn ID, Forn Sub ID Forn Eield Infornation thru CLF Custoner ID, Forn ID, Sub ID Dependent of: Custoner Profile thru CLF Custoner ID Category Profile thru CLF Custoner ID, Category ID 2"K*5 vtn / D 9 y s 74 The category table file 163 is utilized to indicate the form category to which a particular form has been assigned. A typical configuration of the category table 163 is as follows: TABLE NAME: CATEGORY TABLE ELEMENT/RECORD DB TABLE ELE. KEY LEN ALIAS: DEFINITION CT 006 010 030 CLF Custoner ID CT_CLF_CUS_ID Category ID CT_CTG_ID Category Description CT_CTG_DSC Key Data: Prinary Key (CLF Custoner ID, Category ID) Foreign Key (FK_CTA (CLF Custoner ID) References Custoner Profile on Delete Restrict; Indexes: Nane On Colunns Type of Index Uniquely identifies each custoner.

Code of forn category to which a forn is assigned.

Description of forn category.

CTIDX CLF Customer ID Primary, Ascending, Unique Category ID Relationship to Other Tables: Parent of: Forn Profile thru Category ID Dependent of: Custoner Profile thru CLF Customer ID / Also interrelated with the form profile data file 162 are the usage statistics file 164, the form field information file 165, and the form output format file 166. A typical configuration of the usage statistics file 164 is as follows: TABLE NAME: USAGE STATISTICS ELEMENT/RECORD DB TABLE ELE. KEY LEN CLF Customer ID E 006 Forn ID E 008 Forn Sub ID E 002 User ID E 006 Printer Type E 002 Site ID E 006 Date Used E 002 Time Used E 002 Nunber of Copies E 002 ALIAS: STAT DEFINITION Uniquely identifies each custoner.

Code to uniquely identify a forn for a custoner.

Code to uniquely identify each revision of the form.

The logon ID associated with each CLF user.

Code of printer type (HP-PCL, Postscript, etc.).

Identifier to uniquely identify a site for a customer.

Date the forn was used Tine the forn was used The nunber of copies printed at user site.

A typical configuration of the form field information file 165 used for form fill capabilities is as follows: NAME: FORM FIELD INFORMATION ELEMENT/RECORD DB TABLE ELE. KEY LEN ALIAS: FF DEFINITION CLF Custoner ID Forn ID Forn SUB ID Field Nunber Field Nane Data Description Field Length Field Fornat Field Type Field Location Key Data: Prinary Key (CLF Custoner ID, Forn ID, Forn Sub ID, Field Nunber) Foreign Key FKJF (CLF Custoner ID, Forn ID, Forn Sub ID) References Forn Profile on Delete Cascade; Indexes: Nane On Columns Type of Index 1 2 3 4 E E E E E E 006 008 003 003 020 040 002 005 001 040 Uniquely identifies each custoner.

Code to uniquely identify a forn for a custoner.

Code to uniguely identify each revision of the forn.

Sequential nunber of fields within a forn.

Nane of the field Concise description of data used in this field Describes the length of the field Describes the field fornat.

Defines the field type. I.E. Nuneric The location of the data in the users file FFIDX CLF Custoner ID Prinary, Ascending, Unique Forn ID Forn Sub ID Field Nunber Relationship to Other Tables: Dependent of: Forn Profile thru CLF Custoner ID, Forn ID, Forn Sub ID A typical configuration of the form output format file 166 provides how the form is to be printed -- the various print formats available. It is as follows (note that the output format of each form may be "source", "print ready" (and various versions), or "compiled"): NAME: FORM OUTPUT FORMAT ALIAS: FO ELEHENT/"ECORD DB TABLE ELE.

KEY LEN DEFINITION CLF Custoner ID FO_CLF_CUS_ID 1 006 Uniquely identifies each custoner.

Forn ID F0_F0RM_ID 2 008 Code to uniquely identify a forn for a custoner.

Forn Sub ID FO_FRM_SUB_ID 3 002 Code to uniquely identify each revision of the forn.

Output Fornat Type FOJKMTTYP 4 001 Code that describes fron type S-Source C-Conpile P-Print Ready Printer Type F0_PTR_TYP 002 Code of printer type (HP-PCL, Postscript, etc.).

Forn Fornat File ID FO_FILE_NAME E 012 File ID where forn fornat data is stored. DOS 8.3 Fornat.

Compression Indicator FO_COMPRESS_IND E 001 Code to tell if the forn is conpressed. Y-Yes N-No Key Data: Prinary Key (CLF Custoner ID, Forn ID, Forn Sub IS, Output Format Type, Printer Type) Foreign Key FK_F0A (CLF Custoner ID, Forn ID, Form Sub ID) References Forn Profile On Delete Cascade; Indexes: Nane On Columns Type of Index FOIDX CLF Custoner ID Prinary, Ascending, Unique Eoro ID Forn Sub ID Output Fornat Type Printer Type Relationship to Other Tables: Dependent of: Forn Profile thru CLF Customer ID, Forn ID, Forn Sub ID 78 The security interface for all of the fil»M | provided through menu file 167. A typical configuration of the file 167 is as follows: NAME: MENU ALIAS: MENU ELEMENT/RECORD DB TABLE ELE. KEY LEN DEFINITION Security Level 1 000 Defines the level of aiill|n|.||u - UY rot «>ach user.

Progran ID Progran Nane Progran Desc Screen Loc Trans ID Key Data: Prinary Key (CLE Custoner ID, ????) Foreign Key CATA (CLF Custoner ID) References Custoner Profile On Delete Cascade; Where desired, as a dependent of the group profile file 157, a group/form file may be provided associates forms to a group. The group/form file is illustrated at 169 in FIGURE 12. A typical configuration of the group/form file, if utilized, is as follows: NAME: GROUP/FORM ALIAS: ELEMENT/RECORD DB TABLE ELE. KEY CLF Custoner ID 1 Group ID 2 Group Sequence Number 3 Forn ID 4 Key Data: Prinary Key (CLF Custoner ID, Group ID, Group Sequence Nunber, Forn ID) Foreign Key EK_GFA (CLF Custoner ID, Group ID, Group Sequence Number) References Group Profile On Delete Cascade; Indexes: Name On Colunns Type of Index GFIDX CLF Custoner ID Prinary, Ascending, Unique Group ID Group Sequence Nunber Forn ID GFIDXA CLF Custoner ID Ascending Group ID Group Sequence Nunber GFIDXB CLF Custoner ID Ascending Forn ID Relationship to Other Tables: Dependent of: Group Profile thru CLF Custoner ID, Group ID, Group Sequence Nunber GF LEN DEFINITION 006 Uniquely identifies each custoner. 006 Code to uniquely identify the distribution group. 003 Sequence nunber to control level within a group 008 Code to uniquely identify a forn for a custoner. 80 27091 After selection of the appropriate form and other information, the form is printed and/or displayed, as indicated schematically at 168 in FIGURE 11.

FIGURE 12 contains the same basic information as FIGURE 11, but shows the data base relationships for referential integrity purposes, and is self-explanatory.

FIGURES 13a through 13i provide a detailed structure chart which shows the program-defined menu structure for the CLF 12. The interrelationship between the individual figures are specifically illustrated thereon, and the relationships between the various elements are self-explanatory from FIGURES 13a through 13i. Elements 190 are elaborated upon in FIGURE 14.

FIGURE 14 illustrates the general flow for the release of forms from the CLF 12 to the end user sites 15 (190 in FIGURE 13a). At 201, the CLF software periodically (e.g every weekday) polls the distribution profile for forms in the computer hosting the CLF to release electronic forms based upon release date (that is, if the release date has now been reached). At 202, the forms available for release are gathered. At 203, the communications software is alerted, and the forms are passed in as an input. At 204, the forms are transferred using the telecommunications infrastructure in place to the sites 15 (e.g. the PCs 154 thereat), as defined by the distribution profile. At 205, the receiving site communication software (e.g. OS/2, version 1.2) receives the forms. At 206, upon receipt of the forms, the applications software is alerted for 81 27098 processing of the transmission. The forms are preferably initially stored on disk. Ultimately, at 207, the applications software may direct the electronic forms to be printed at a printer (e.g. 16), to produce a paper form.

FIGURE 15 indicates the general flow for sending a form to one of the geographically remote user locations from the CLF 12. At 210 the program is initiated from the CLF 12 applications file 29. A session with the desired remote station or stations (locations) is allocated at 211, and all requested files are sent at 212. Confirmation that the files have been sent is provided at 213. Any data to be received from the remote location is received at 214, and receipt acknowledged at 215, before the program ends.

FIGURE 16 illustrates the general flow chart for sending a print request from CLF 12 to a remote user location having a printer, e.g. 16, for actually printing the form that was sent according to 210-213. The program is started from the CLF 12 applications software 29 at 217, a session is allocated with the remote location at 218, the print request is sent at 219 to the corresponding software at the remote location, and is confirmed at 220 before the program ends.

It will thus be seen that according to the present invention method has been provided for eliminating or minimizing warehousing, inventory, and obsolescence costs that a customer typically incurs in association with preprinted paper forms, forms distribution costs are minimized, and the number of preprinted forms can be 82 2/098 greatly minimized (for example the number of forms can be dropped from 20,000 to 5,000 in conventional operations). Centralized control is provided for electronic forms design, and the co-existence of a fcrm in electronic and paper media is provided.

Labor savings are achieved by eliminating redundant entry and processing of information by providing a centralized system, and where a customer desires, off load processing may be provided from the customer's main frame computer 34 to the vendor's computer (e.g. location of the FAP 14). Based upon geographic location, volume requirements, form construction (e.g. number of parts, MCP, etc.), and equipment profiles, exactly how paper forms will be constructed and delivered to end user sites 15 will be determined.

The system as described above has numerous special applications, and it is impossible within the scope of a patent application to designate all possible uses of the system for particular functions description of one particular implementation and method of operation may serve to illustrate the versatility and functionality of the invention.

A FAP 14 is provided at the vendor's facility, and is used to design electronic and preprinted forms, to control variable data fields for the electronic forms, and to control and directly communicate with the CLF 12 located on the customer's premises. Upon release of new forms or update of existing forms, the CLF populates the forms library containing appropriate form images and updates the appropriate tabLes with and control information. This file is sent to a softwjare distribution resource in a main frame computer at a centralized location, which is central to a number of geographically remote user locations which it will service. Preferably, a main frame computer utilizes the customer environment; although the forms could be stored in the customer's main frame, if desired. At the scheduled release dates, either automatically, or by operator control or verification at the centralized location, the CLF will effect distribution of the electronic forms to a file server residing in each of the geographically remote user locations.

The forms automation system 10 in this particular example is used to automate the ultimate customer interview process that occurs when new accounts are established at a banking institution, or changes are made to existing accounts. The exact detail of the processing performed during the customer (bank's) interview will determine the forms which are to be printed. For example opening of checking accounts, time deposit accounts, and savings accounts will generate different forms that are ultimately printed. In addition to printing the electronic forms, the forms automation system 10 according to the invention will produce a check list of all forms printed as a result of specific activity on an account, and all forms required to document an interview will be printed immediately at the completion of the interview process so that the bank's customer will have -- before he or she leaves the bank -- a paper form. Three to five bank customer interviews can take place concurrently and 84 27 the common data for each will automatically be transferred from one electronic form to the other.

ARGO Bankpro software is downstream of the CLF 12, as an end user interface. The customer data is transferred to the main frame through platform automation support software (PASS), a commercially available system, and at the main frame the data is stored in a CIS software package, provided by Hogan.

The file server in each bank remote user site is networked to other devices in that location, for example by an IBM Lan 1.2. A laser printer will be located in each remote site, such as an HP LASERJET, to provide actual printing at the user location. Different printers can be provided at different locations since the forms creation software at the FAP 14 will format each individual electronic form in whatever formats are necessary to properly print with the various printers at the user locations a.c which the printers are located. JF MERGE software, from the same manufacturer as the JETFORM forms design package, will reside on the file server, and will be provided to produce the forms, which will be printed as soon as the transaction is completed.

During processing, the customer will store the variable data to be added to the form at a generic data base. At the completion of the transaction/end bank customer interview, the forms automation software will be invoked. Variable data will be extracted from the generic data base and an Ascii file created, which will be used to input to the form merge software (e.g. JF MERGE). The forms required to verify the transaction will be printed, and a check list form to make sure that all 270 necessary steps have been completed will also be printed.

While the implementation described above is practiced with only a few (e.g. five) different forms, it may be expanded to encompass literally thousands of different forms.

While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limitad to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements and methods included within the spirit and scope of the appended claims. 270986 86

Claims (33)

WHAT WE CLAIM IS:

1. A method of distributing electronic images to each of a plurality of geographically remote end users, comprising the steps of: (a) storing a plurality of different electronic images in a first computer at a centralized location; (b) also storing in said first computer predefined commands, including date and extent of distribution commands, relating to the distribution of the electronic images: %'( (j hj5*h * . i (c) periodically polling said first computer to (d) in response to applicable date commands located in step (c) automatically distributing the electronic images to those of the plurality of end users specified by the distribution commands.

2. A method as recited in claim 1 wherein step (c) is practised once every weekday.

3. A method as recited in claim 1 further comprising step (e) of manually verifying the distribution of the electronic images to those of the plurality of end users specified by the distribution commands, and after manual verification, automatically distributing the electronic images to those of the plurality of end users specified by the distribution commands.

4. A method as recited in claim 3 wherein steps (d) and (e) are practised at a location remote from said geograph: = end locate applicable date c users. 27098 87

5. A method as recited in claim 3 wherein a second computer is located at each of the geographically remote end users, and wherein step (e) is facilitated by two way communication between said first said second computers.

6. A method as recited in any one of claims 1 to 3 wherein said electronic images consist of a plurality of different business forms.

7. A method as recited in claim 6 wherein step (c) is practised once every weekday.

8. A method as recited in claim 5 wherein the business forms are stored in electronic format at a centralised location before being produced in paper form at geographic locations proximate each of the geographically remote end user locations in response to an electronic order generated by a centralised or remote command; and then delivered in paper form to each of the geographically remote end locations after production thereof.

9. A method as recited in claim 8 wherein the production and delivery of the business forms are practised simultaneously at at least one of the geographically remote use locations.

10. A method as recited in claim 9 wherein the centralised location is a first centralised location, and comprising the further step of creating business forms in electronic format at a second centralised location, and transmitting the created form in electronic format to the first centralised location.

11. A method as recited in claim 10 wherein the first centralised locations are geographically remote from erc:ia other.

12. A method as recited in claim 10 wherein a first pri^nter.4,'iS'^ ^ provided at one of the remote end user locations and wnte&'ein / a second printer is provided at a secofra^*^ remote end user location, the printers having 270986 88 different formats; and wherein the business forms are created and stored in both printer formats; and wherein the business forms are produced and delivered so the same paper business form is provided with each of the first and second printers.

13. A method as recited in claim 8 wherein the centralised location is a first centralised location, and a second centralised location is provided- to create and transmit business forms in electronic format to the first centralised location.

14. A method as recited in claim 13 wherein a first printer is provided at one of the remote end user locations and wherein a second printer is provided at a second remote end user location, the printers having different printer formats; and wherein the business forms are created and stored in both printer formats; and wherein the business forms are produced and delivered so the same paper business form is provided with each of the first and second printers.

15. A method as recited in claim 8 wherein the business forms are produced and delivered by producing the business forms in a business forms manufacturing facility geographically proximate, but still distinct from, the remote end user location, and delivering the paper forms via motor vehicle from the manufacturing facility to the user location.

16. A method as recited in claim 8 further comprising storing the plurality of business forms in an electronic format including printing images at the centralised location; determining which of the geographically remote end user locations will be provided with business forms based on geograwfJift ^IcScu^j-on, volume requirements, form construction, and equipment profile,°^knd storing that information at said centralised locat|o»l£- ^nd automatically distributing forms from the cenqralislici. ^ location to the geographically remote end user locations, ,fp£ that 270986 89 particular form through electronic scheduling or in response to commands input at said centralised location according to the determinations.

17. A method as recited in claim 16 comprising a further step of providing for electronic storage of the forms at decentralised locations, and subsequent processing.

18. A method as recited in claim 17 wherein said subsequent processing comprises selecting either data entry and production using electronic imaging, or traditional production as in the determining step.

19. A method as recited in claim 16 wherein said centralised location comprises a first centralised location, and comprising a second centralised location; and comprising the further step of designing and modifying the business forms in electronic format at the second centralised location.

20. A method as recited in claim 19 wherein the second centralised location is geographically remote from the first centralised location, and from the remote end user locations.

21. A method as recited in claim 16 wherein a first of the use locations has a first printer with a first printer format, and wherein a second of the remote end user locations has a second printer utilising a second printer format different than the first printer format, and wherein the stored business forms are to be distributed to both the first and second remote end user locations both the first and second printer formats; and wherein t^e-j^siness forms are delivered automatically in electronic forma^tS ^tli^^trst and second printers, for printing into paper forms afc5"the first-^and second remote end user locations. |i 1 1 V *>/

22 . A method as recited in claim 16 wherein said cent^||/iffl^.^ location is at one of the remote end ut-er locations.

23. A method as recited in claim 19 comprising the further step of, at the second centralised location, storing information about up-dating and release date information for the forms in electronic format, and automatically transmitting the up-dated forms in electronic format and release information to end user sites at the appropriate time.

24. A method as recited in claim 16 comprising the further step of, in response to commands entered at centralised or remote locations, distributing electronic forms through a communication network for subsequent processing by end users.

25. A method as recited in claim 16 comprising the further step of, in response to commands entered at centralised or remote locations, distributing electronic forms through a communication network for subsequent production by end users.

26. A method as recited in claim 1 further comprising the steps of: maintaining the business forms created in a display image format to which variables may be added for variable image data; electronically transmitting the display image format; and ultimately converting the display of form image formats to desired printer formats.

27. A method as recited in claim 26 further comprising the steps of: simultaneously transmitting the printer formats to each of a plurality of compatible printers; and printing out the forms on the compatible printers.

28. A method as recited in claim 27 wherein the plurality of business forms in electronic format use a plurality of different business forms creation computer programs. 270986 91

29 . A method as recited in claim 28 wherein the display of form image format is converted to desired printer formats utilising the business forms creation computer programs.

30. An electronic image produced according to the method as claimed in any one of claims 1 to 29.

31. A business form produced from an electronic image as claimed in claim 30.

32. A method of producing electronic images substantially as herein described and with reference to the drawings.

33. A method of producing electronic images as claimed in claim 32 wherein a business form is produced from the electronic image. MOORE BUS USES FORMS, INC By their Attorneys BALDWIN, SON & CAREY (i I PSr: