WO2008145981A2 - Systèmes de gestion d'information - Google Patents

Systèmes de gestion d'information Download PDF

Info

Publication number
WO2008145981A2
WO2008145981A2 PCT/GB2008/001792 GB2008001792W WO2008145981A2 WO 2008145981 A2 WO2008145981 A2 WO 2008145981A2 GB 2008001792 W GB2008001792 W GB 2008001792W WO 2008145981 A2 WO2008145981 A2 WO 2008145981A2
Authority
WO
WIPO (PCT)
Prior art keywords
data
user
store
stored
records
Prior art date
Application number
PCT/GB2008/001792
Other languages
English (en)
Other versions
WO2008145981A3 (fr
Inventor
Nicholas Lightbody
Original Assignee
Deskspace Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Deskspace Limited filed Critical Deskspace Limited
Publication of WO2008145981A2 publication Critical patent/WO2008145981A2/fr
Publication of WO2008145981A3 publication Critical patent/WO2008145981A3/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • G06F8/38—Creation or generation of source code for implementing user interfaces

Definitions

  • This invention relates to computer-based information management systems, particularly to the structure of such systems such as to facilitate specifying and configuring them to meet users' requirements.
  • SMO's Small and medium scale organisations
  • IISS's Integrated Information Software Systems
  • This glass ceiling is caused in part by the difficulty in managing complexity when the organisation grows beyond a certain point and in part by increasing difficulty in maintaining efficient risk management and quality control. In order to grow beyond a certain point, SMO's need to deploy an IISS.
  • Any IISS may, with use of the appropriate technology, be deployed over a local area network, a wide area network, or via any other means of connecting computers. It may employ web browsers or other means for displaying interfaces.
  • the present invention may provide an information management system structure which overcomes or at least mitigates the problems set out above.
  • the invention may provide an information management system adapted to generate a plurality of user interfaces from a common interface structure, said system comprising means for retrieving data essential for the generation of each of said interfaces from a separate interface configuration data storage means, the system further comprising user operable means for modifying the data stored in said interface configuration data storage means.
  • the invention may provide an information management system comprising a plurality of user interface instances which differ from each other under the control of reconfigurable data such that any interface can be transformed into any other by altering said reconfigurable data
  • the invention may extend to a method of operating a computer system comprising generating a plurality of user interfaces from a common interface structure wherein the step of retrieving data essential for generating said user interfaces from a separate interface configuration data storage means.
  • the individual user interfaces e.g. individual screens or windows, with which a user can control and receive information from the information management system are generated based on user-defined data. This allows a single master interface structure to be used to generate all of the user interfaces simply by retrieving the appropriate data from the interface configuration data storage means.
  • Such a structure in which a user interface is generated by retrieving data stored by a user in order to build the interface, has several advantages over conventional arrangements in which user interfaces are hard-coded - i.e. generated from object code. For example it allows a robust basic master user interface structure to be developed which is retained as it is implemented for each particular instance of the user interface. It also allows the rapid creation of a large number of interfaces which may be quite different from one another in detailed appearance and functionality but which retain a common look and feel, without coding them separately.
  • a further advantage achievable in accordance with the invention is that any given user interface can easily be altered in appearance and/or functionality in dependence on a range of conditions e.g. navigation history, current data module or even user inputs. This is preferably effected by changing the appropriate data in the interface configuration data storage means or by means of calculations which change the appropriate data output by the interface configuration data storage means.
  • Preferred embodiments of the invention provide a method of using computer software to implement a business process which permits and enables rapid specification, development, configuration and deployment (together “Development”) of easy-to-use IISS's for a wide range of different customer organisations.
  • user operable means are provided for entering or manipulating the data stored in the interface configuration data storage means.
  • this takes the form of a Rapid Development and Deployment Environment ("RDDE") designed to enable the system development method of the invention to function efficiently.
  • RDDE Rapid Development and Deployment Environment
  • the RDDE is arranged to manipulate other configuration data.
  • the information management system comprises one or more modules constituting a core system, including as a minimum the common interface structure referred to above, wherein the core system is arranged to be configured by retrieving data from data storage, e.g. the interface configuration data storage means.
  • the RDDE thus provides a way to configure and change the core System so that every customer can be supplied with a version of the same core System, configured to their own individual requirements by configuration data.
  • the ability to configure a system which is achievable in accordance with the invention means that widely differing systems may be based on a single robust core system and can be implemented by manipulation of user data which does not jeopardise the functioning of the core components.
  • Every customer can receive easy-to-install updates of the core system without affecting their configuration data and so without impacting on the appearance and functionality of their system; and therefore without jeopardising the stability or reliability of their system. Accordingly every customer can benefit from the improvements developed for other customers merely by installing an update.
  • Both the RDDE and the core system use a significant level of indirection - the ability to reference something using a name, reference, or container instead of the value itself- to achieve flexibility and configurability.
  • preferred embodiments of the invention allow any SMO to be supplied with an IIS S that exactly meets its agreed needs in a more timely and cost effective manner than is currently the case.
  • this editing comprises the ability to remove one or more elements from the common interface structure.
  • this editing comprises the ability to remove one or more elements from the common interface structure.
  • the means for editing the common interface structure allows a user to adjust the position of one or more elements. Again this would be a global change affecting all instances of the interface.
  • the user interfaces will typically comprise one or more interaction objects, e.g. buttons, for invoking a particular associated action.
  • interaction objects e.g. buttons
  • the appearance of said interaction objects and the action associated with them are determined by the data stored separately in a button configuration data storage means, which is editable by user operable editing means. This allows great flexibility to a development user in the functionality which can be provided, without requiring access to or knowledge of the underlying code. It also allows the operation of the interaction objects easily to be altered during running of the system by simply allowing the system to alter the data stored in the button configuration and function library data storage means.
  • a further advantage afforded by the set-up outlined above is the ease with which text or sounds associated with the interaction objects can be changed en masse, e.g. for an alternative language module. No access to the underlying code is required, it is sufficient simply to replace the data at predetermined points in the button configuration data storage means with the new data; or if the data is already stored (i.e. the system is loaded with another language module), simply to re-address it.
  • the user interfaces - e.g. screens or windows - with which an end user can interact with a information management system can be constructed using data in the interface configuration data storage means.
  • a similar arrangement of data storage is employed to navigate between windows, i.e. to implement the topographical layout of the information management system.
  • the information management system further comprises a routing configuration data storage means and user operable means for modifying data stored in said routing configuration data storage means, the system being adapted to generate a second user interface after a first user interface in dependence on the data stored in said second configuration data storage means.
  • Such embodiments of the invention are advantageous since they allow a high degree of flexibility in the layout and order in which screens etc. are accessed without any permanent links being written into the underlying software. This makes the system robust to changes - e.g. the insertion or removal of an additional screen. It also allows for example different users, e.g. those having different security levels, to access screens or not access screens in different orders or to skip some. It also reduces the risk that an unauthorised user can accidentally access a screen which they are not supposed to. This is a frequent hazard in conventional information management systems in which the navigation between screens is embedded in hard-coded logic which can be very hard to verify fully in all its permutations. By contrast in accordance with the aforementioned preferred embodiments of the present invention, the navigation logic can simply be realised with a matrix of connections, replicated for each user or class of user with appropriate modifications.
  • the invention provides an information management system adapted to generate a first user interface including a plurality of interaction objects, each of said interaction objects being associated with a data table stored in a configuration data storage means, at least one of said interaction objects being configured to generate a further user interface in dependence on the data stored in said data table, the system further comprising user operable means for modifying the data stored in said configuration data storage means.
  • the system comprises window configuration data storage means for storing data used to determine the appearance and characteristics of user interface or display windows together with user-operable means for manipulating the configuration data in said storage means. For example the size or location of a window or whether it is printable and if so in what format may be stored in the storage means - e.g. a data table.
  • the storage means e.g. a data table.
  • the window data may be altered indirectly by an end-user — e.g. by recording the size and position of a window when the end-user closes it so that the size and position of the window is restored when the window is next opened.
  • the system comprises means for storing relationship data determining which other records a newly created record is automatically linked to and user-operable means for viewing and editing said relationship data.
  • relationship data determining which other records a newly created record is automatically linked to and user-operable means for viewing and editing said relationship data.
  • the system is arranged such that at least some and preferably all text appearing on any user interface is stored in a separate textual data storage means and is retrieved when the associated user interface is generated.
  • the system comprises means for storing standard fields identification data and user-operable means for manipulating the same. This allows users to use standard fields, suitably relabelled where appropriate, to store end-user data.
  • This has the advantage that the underlying core system can be made to function robustly without being affected by configuration and customisation for users. It supports the underlying philosophy of configuration and customisation of the system rather than tying the system to a rigid database structure.
  • the system comprises means for storing column sort data separate from the data itself.
  • the column data might include the order in which the data is to be sorted and the labels associated with the column. This feature makes it easy to provide new data columns in a user interface since essentially the functionality is contained in the column sort data storage means.
  • the system could be implemented in a number of architectures such as on a standalone data processor, a local or wide area network or a remote server delivered via the internet. Where implemented over a network this could be for example using a client-server model, a peer to peer network, or any other configuration.
  • the system is implemented over a client-server network wherein the interface configuration data storage means is/are provided on a client workstation or on the server but in the latter case mirrored on the client workstation. This reduces network traffic and thus improves performance.
  • Preferably some or all of the other configuration data storage means referred to hereinabove is provided or mirrored on a client workstation. Any individual configuration data storage means or sub-combination thereof is envisaged as residing on such a workstation.
  • the system is deployed on one or more servers remote from the LAN or WAN of the user where the workstation used by the user runs, instead of on the user's own computer, in a virtual client environment on one of those servers.
  • the graphical user interface generated by the system is transmitted to the user over the internet and user input transmitted back to the virtual client to provide command and control of the virtual client session.
  • This embodiment has the advantage of performance since the network traffic over the internet is minimised with all data processing undertaken locally on the servers.
  • a further advantage is that the computer required by the user needs only to be able to receive and display the interface transmitted by the server and in turn return the user's input.
  • the invention provides an information management system comprising a client machine and a server machine in data communication with the client machine and adapted to generate a plurality of user interfaces on the client machine from a common interface structure, comprising means for retrieving data essential for the generation of each of said interfaces from a configuration data storage means on said server machine.
  • one of the client and server machines comprises user operable means for modifying the data stored in said configuration data storage means.
  • the invention provides an information management system comprising a client machine and a server machine in data communication with the client machine, said client machine being adapted to display a plurality of user interface instances which differ from each other under the control of reconfigurable data stored on said server such that any interface can be transformed into any other by altering said reconfigurable data.
  • the invention extends to a server and server software comprising means for storing reconfigurable data and adapted to supply said data to a client which is adapted to display a plurality of user interface instances which differ from each other under the control of said reconfigurable data supplied by said server such that any interface can be transformed into any other by altering said reconfigurable data.
  • the invention also extends to a client and client software adapted to receive data from a server and to display a plurality of user interface instances which differ from each other under the control of said data received from said server such that any interface can be transformed into any other by altering said data.
  • the invention provides a method of developing an integrated information software system comprising providing a core system including means for generating a plurality of user interfaces, and storing data in interface configuration data storage means, said data controlling the appearance and functionality of said respective user interfaces.
  • the invention provides a business process for developing an integrated information software system comprising the steps of specifying a customer's requirements and entering said customer requirements in the form of configuration data to configure a core system to provide said integrated information software system, wherein said requirements are in at least one category selected from the group comprising: the appearance of a user interface; the functionality of a user interface; and the available routes with which user interfaces can be navigated by a user of said integrated information software system.
  • the embodiments of the invention described here permit the rapid development and deployment of computer-based IISS's each of which meets the differing requirements of a different purchaser, in an improved manner compared with current methods.
  • the invention can provide the opportunity for the creation of a business process which first ascertains the IISS requirements of an organisation then delivers an IISS matching that requirement but does this an improved manner compared with the existing means of developing and supplying IISS's.
  • the Rapid Development Environment provided in accordance with preferred embodiments of the invention enables: (i) a Publisher/Developer or Configurer to rapidly deliver an IISS to a client's specification; and (ii) a Publisher/Developer to rapidly create and deploy additional functionality.
  • the preferred embodiment includes suites of interfaces, tools and services, described below, enabling the process of specifying and configuring a system to function, for the: (i) Publisher/Developer: (configuration and additional functionality); (ii) Configurer: (configuration); (iii) Administrator (some configuration); and (iv) User (configuration of their own user options).
  • the Invention permits a business utilising them, whether a publisher, developer or configurer, (in any case a "Developer") to deliver to their SMO clients the IISS that the client requires in a timely, efficient and profitable manner.
  • a publisher whether a publisher, developer or configurer, (in any case a "Developer") to deliver to their SMO clients the IISS that the client requires in a timely, efficient and profitable manner.
  • the specific modular design of the core system enables: (i) the Developer to efficiently and profitably support their client with easy to install updates; and
  • the Administrator of an IISS built using the preferred embodiments of the invention has at their disposal a series of interfaces, tools and services enabling them to perform their role quickly and efficiently.
  • Users of an IIS S built using the preferred embodiments of the invention receive a visually informative, interactive, consistent presentation of their information enabling them to work more efficiently. This means that users naturally wish to undertake work within such a system. Working within it is seen as an advantage rather than a burden. In consequence, such an information system efficiently and contemporaneously collects data derived from the end-user's work, providing up-to-date information derived from that data to other end- users and the administrator.
  • Figure 1 is a schematic block diagram of the main parts of a system embodying the invention
  • Figures 2(a) to (g) are block diagrams illustrating a non-exclusive range of possible file structures for the main system components
  • Figure 3 is a schematic block diagram illustrating the use of stored and environmental data in controlling the operation of an interface button within an embodiment of the invention
  • Figure 4 shows an implementation of an embodiment of the invention broken down into four phases and further broken down into eleven separate stages;
  • Figure 5 provides an illustration of some of the tools that may be used by the embodiment in each of the 11 stages presented in Figure 4;
  • Figure 6 gives an example of the indirection structure behind the software used by the tools presented in Figure 5;
  • Figure 7 further shows various interconnections between the principle components, their division into Interfaces, Tools and Services as well as the principle direction of the data flow through these interconnections; and Figure 8 shows the components and connections used when a user tries to login to the system, controlling both data access and the interface screens to be displayed.
  • IISS integrated information software system
  • a Component is a logical construct, not necessary a physical manifestation.
  • the System & User Data Component(s) may conveniently comprise multiple digital files stored or hosted on multiple different computers potentially running under different computer operating systems. This is not necessary but it is possible and may be desirable in some cases.
  • Fig . 1 illustrates the six logical Components of an embodiment of the invention: the Configuration Component (1) in which is stored the configuration data controlling the Interface Component (3) providing the Licensee's Users with their specified integrated information software system (ITSS); the Specialist Screens Component (2) stores particular User interface screens specific to each Licensee; the Deployment Licence (4) stores key data controlling and informing the IISS both so that it is only useable by the permitted Licensee and controlling access to the licensed features and modules; the System & User Data Component(s) (5) store data controlling use of the IISS and the User Data that the IISS has been configured to store and deliver to Users; the Admin User Accessible Logic and Interface Component (6) is accessible at Developer Level to higher level Users employed by the Licensee so that they can develop their own layouts, reports,
  • Fig. 2(a) illustrates a digital computer file structure where the components (1) - (6) have all been assembled as parts of a single file
  • Fig 2(b) illustrates a digital computer file structure where the components (I) - (6) have been assembled as parts of two files, one the Interface File (A) to be accessed by any User (containing Components (1) (2) & (3)), whether it is located locally on a workstation or remotely by means of network communication, the other, the Server File (B) (containing Components (4) (5) & (6)), which may be located remotely on a server or another workstation or which may be located on the User's own workstation.
  • the Interface File (A) to be accessed by any User (containing Components (1) (2) & (3)), whether it is located locally on a workstation or remotely by means of network communication, the other, the Server File (B) (containing Components (4) (5) & (6)), which may be located remotely on a server or another workstation or which may be located on the User's own workstation.
  • Fig. 2(c) illustrates a digital computer file structure where the components (1) — (6) have been assembled as parts of three files. This is similar to that described in fig 8.1(b)(ii) except Components (1) and (2) have been separated out into a Configuration File (C) located locally to the Interface File (A) which contains the Interface Component.
  • C Configuration File
  • Fig 2(d) illustrates a digital computer file structure where the components (1) — (6) have been assembled as parts of four files. This is similar to that described in Fig. 2(c) except Component (6) the Admin User Accessible Logic and Interface Component has been located in a separate Business Logic File (D). This has the advantage that the Server File (B) can be replaced on an upgrade whilst the Licensee retains Component (6) in the separate File (D) containing their own in-house development work which will continue to function in conjunction with the new File (B) containing Components (4) and (5).
  • Fig. 2(e) illustrates a digital computer file structure where the components (1) - (6) have been assembled as parts of five files. This is similar to that described in Fig.
  • Fig. 2(f) illustrates a digital computer file structure where the components (1) - (6) have been assembled as parts of six' files. This is similar to that described in Fig. 2(e) except Component (4) the Deployment Licence Component has been located in a separate Licence File (E). This has the advantage that the Licence File (E) can be replaced in order to provide the Licence with revised Licence Terms without accessing or changing any other part of the IISS.
  • Fig. 2(g) illustrates a digital computer, file structure where the components (1) - (6) have been assembled as parts of multiple files. This is similar to that described in Fig. 2(f) except that every Component is shown as comprising multiple Files. For example: the
  • System & User Data Component (5) could access a variety of different data sources hosted at different locations and possibly running under different computer operating systems.
  • any dataset stored on the server may be downloaded in whole or in part and stored temporarily on the workstation in order to be used and possibly amended on the workstation without suffering the delay inherent in network communication with the server. Records amended in this way on the workstation may be uploaded back onto the server, so replacing the original copies of those records on the server, in order that information entered on the workstation shall thereafter be stored on the server. Record Locking and Validation procedures may be used to govern which record is stored after two users edit the same record simultaneously.
  • the modules in the core system must retrieve and apply data from the appropriate configuration data storage. The particular example of the generationof a graphical element of a user interface screen is explained below in detail with reference to Fig. 3.
  • Fig: 3 show a schematic representation of control of the display of an interface button, and thus whether it is active or not, providing to a User, to whom it is visible, access to a Function.
  • a Function may be any action perfo ⁇ ned on behalf of or for the benefit of the User.
  • This example illustrates a type of preferred method that may be used extensively in an IISS in accordance with the invention.
  • each object in the Interface forming part of the Master Interface Model may be recalculated and redisplayed by this method whenever the User has some Interaction with the Interface.
  • a single Interface screen or layout may be used for many Users with different Access Rights, so that the higher level users will be able to see and use a wide variety of Buttons but various lower levels of users will only be able to see and use the more limited set of Buttons which they are permitted to use. This is preferred behaviour to offering the User many Buttons where when they try to click the button either it does nothing or they are told that they are not permitted to use this function.
  • Every Button may have a Specified Function (14b) assigned to it in the Configuration.
  • the Specified Function refers to a Function stored in and called from the Function Library (10). To call the Function the User must Click or Select the relevant Interface Button (1). The User cannot Click or Select the relevant Interface Button if it has been rendered invisible by reason of its Calculated Status (12) being 0.
  • the embodiment herein described comprises four main parts: a core system which includes basic 'shell' structures for the functions of the IIS S; configuration data which is used by the core system structures to generate the IISS; user data which is the data which the IISS acts on as required by users; and a rapid development and deployment environment (RDDE) which manipulates the configuration data.
  • the RDDE is only provided to those users who will be altering the IISS itself, e.g. configurers or developers, as opposed to end users who will only work with user data.
  • Figure 4 shows a process of using an embodiment of invention broken down into four phases and further broken down into eleven separate stages.
  • the requirements of the customer or vertical market for the IISS are analysed and a specification is agreed.
  • the IISS is configured to meet the requirements agreed in phase 101.
  • documentation is prepared and in the fourth phase 104 data are loaded. The process defined by these four phases can be further broken down into eleven separate stages, corresponding with the four phases.
  • the first more detailed stage 105 corresponding to the first overall phase 101, is to obtain information defining the customer's requirements for an IISS. (Numbers shown within boxes in Figures 5 and 6 in brackets correspond with components shown in Figure 7 where they are not specifically numbered in this description.) The next seven stages correspond with phase 102.
  • the next two stages 113, 114 correspond to the third phase 103; they are to prepare documentation 113 and to prepare training material 114.
  • the final stage 115, corresponding with the fourth phase 104, is to import data provided by the customer and process them as necessary.
  • Figure 5 provides an illustration of some of the tools that may be used by the method of the invention in each of the eleven stages presented in Figure 4.
  • the specification tool 16 is used to capture data about fields, reports, users and other requirements.
  • the settings inspector 17 is used to configure a copy of the most recent version of the core systems with the customer's details 106.
  • the licence details are entered in an empty secure licence file 18.
  • the access authority tool, confidentiality level tool and EDDT management tool may be used as at step 19.
  • the specification tool may be used to provide screen labels for appropriate fields together with the language inspector and the case tool as at step 20.
  • the following modules 21 may be used: the single master interface model; the layout component inspector; the standard fields inspector; the interface inspector; the language inspector; the layout router inspector; the category attribute tool; the user defined lookup tool; the calculation inspector; the window tool; the button parameter tool; and the column sort tool.
  • the following modules 22 may be used: the button parameter tool; the function library; the calculation inspector and the workflow tool.
  • help tool For preparing documentation 113 the help tool, button help tool, and layout help tool (23) may be used.
  • Figure 6 gives an example of the indirection structure behind the software. It shows how the tools, inspectors and models of Figure 5 are linked to various tables and other data structures.
  • the settings inspector for setting up customer's details (17) uses the settings tables (43).
  • For entering licence details in an empty secure licence file (18), the licence tables (44) are used.
  • the access authority tool (24) uses the user's tables (45) and the
  • the confidentiality level tool (25) uses the user's table (45), while the EDDT management tool (26) makes use of the EDDT tables (46), the sales tax tables (47), the transaction codes tables (48) and the currency tables (49).
  • the arrows show further links between other models, tools and inspectors and the various tables and data structures that they use.
  • the graphic elements and tiles tables 50, 51); the layout components tables (52); the language tables (53, 54); the standard fields key tables (55); the new dialogue cases tables (56); the multi-channel marker tables (57); the new record cases tables (58); the router tables (59); the window tables (60); the button parameter tables (61); the column sort tables (62); the function library tables (63); the user definable data calculations tables (64); the user definable look up data tables (65); workflow tables (66); workflow-stages tables (67); and the help tables (68).
  • Figure 7 shows a Schematic View of the Principle Components of the Software Element of the Invention and their General Types of Interconnection. The components are split into those that run on the Workstation (69) and those that run on the Server (70). The
  • Workstation contains Interfaces for use by the Publisher/Developer or Configurer (71);
  • the Workstation further contains various Tools for use by the Publisher/ Developer or Configurer (74) and tools for use by the User (76).
  • the Server (70) contains a Deployment Licence (18) which for example stores data controlling the licensee and their users' use of the IISS in accordance with the licence granted to the licensee by the Publisher / Developer / Configurer including which user data modules are available; the number of users who may be given access; the number of users who may log in simultaneously; the number of enterprise IDs available; whether or not multiple personalities are permitted; and whether or not multiple locations are permitted.
  • the server also contains tables and tools for use by the Administrator (80) and tables for use by the Publisher/ Developer or Configurer (81).
  • the server contains data modules for use by the User (82).
  • Figure 7 further shows various interconnections between the principle components as well as the principle direction of the data flow through these interconnections.
  • the Layout Router Inspector in the interfaces for the Publisher/Developer or Configurer (71) exerts a principle control over the services for the User (79).
  • the User Preferences Tool in Box 76 stores its data in the User's Tables on the Server in Box 45 which controls various aspects of the user interface in Box 73.
  • Figure 8 shows the components and connections used in logging a User into the System, Controlling Data Access, and controlling the Interface Screens to be displayed.
  • the User Name and Password entered are checked, via the Network (86), against the User Data (45) stored on the Server (70). If the User is determined to be valid, the Licence validity is then checked against the Licence Data (18) stored on the Server (70). If the Licence is valid, processing proceeds to the next step, in which data are uploaded to the Workstation after log in (84). The Workstation is then logged in to the Core System as an Authorised User (85). Components of the logged in Workstation (85) use the network in the logged in state (87) to access components of the Server (70) such as Data Modules, User Defined Calculation Tables, and User History.
  • the logged in Workstation (85) contains controls for the Interface appearance, controls for dete ⁇ nining which interface screen is to be displayed, and controls for accessing data.
  • the User and Licence Data uploaded from the Server (45) in Step 84 includes inter alia the EDDT Membership Details; the User's Access Level, Function Level, Module Access Level, Data Authority and Confidentiality Level; the Current Enterprise Data; and Licence Data. These data are used by the logged in Workstation (85) for determining what the User sees within the User Interface after User Interaction is completed. For example the . Licence Data read from Server (70) during the Log in attempt (83) and passed through the uploading stage (84) to the Workstation logged in (85) are used to determine what permitted modules the User can access, which in turn is used to control the data displayed.
  • Fields may be of different types and are used to store different sorts of data.
  • a set of Records are said to be Filtered from the total set of Records on some specific criteria.
  • the Developer Level user has access to all components in the "Publisher/Developer or Configurer" and the "Server" areas illustrated in Figure 7 together with everything available to both Administrators and Users. Figure 7 is described in greater detail later.
  • the Administrator Level user has access to all components in the "Administrator” and some in the "Server” areas illustrated in Figure 7 together with everything available to Users.
  • Each User is allocated an "Access Level” a numeric value controlling which specific layouts within the user interface of the IIS S ("User Interface”) they will be permitted to access.
  • Each User is allocated a "Function Level" a numeric value controlling the visibility and thus availability of every interface button calling a function from the function library (264).
  • Each User is allocated a series of "Module Access Rights" numeric values controlling their access to each user data module (82).
  • Each User is allocated a "Data Authority” a numeric value which is accessed by the Access Authority Tool in determining to what data they should be permitted access.
  • Each User is allocated a series of "Confidentiality Levels", a numeric value which determines the Confidentiality Level of the records that User is permitted to view.
  • a Confidentiality Level can be attributed to any record in order to control access.
  • Any user may interact with the RDDE and/or an IISS created using the RDDE by a variety of means including:
  • the Core System uses a series of Environmental Factors to control which User Interface is * displayed, what are the state or appearance of graphical elements in that Interface and what data is displayed to the current User.
  • the Status Inspector Plus (202) displays the current values of significant system variables to a Developer.
  • the Settings/Licence Inspector (203) displays the current values of system settings and licensee settings.
  • System settings enable or disable Services and/or features within those Services.
  • Licensee settings display, for example, the name of the Licensee, numbers of permitted users, enabled Data Modules and Features.
  • the screens or layouts used by all levels of users throughout the Core System are assembled from layout components stored in tables accessed through the Layout Component Inspector (204) ready for use when building new screens or layouts.
  • Components can merely be dragged and dropped or copied and pasted into their required locations on new or amended screens or layouts.
  • This Inspector stores data on each Component enabling the Developer to search for Components fulfilling specific criteria.
  • Each Data Module contains a very large number of "Standard Fields" of each different data type which can be used by the Developer for a specific client system build without needing to add new fields to the RDDE and Core System structure to match the client's requirements.
  • the Inspector also displays the Text Label used in the User Interface (stored as a Language Variable in a Language Table) to label the field enabling the Developer to edit that Text Label as required.
  • the Inspector includes a variety of Filters and Sorts to enable the Developer to quickly and easily locate the Standard Field records to which he wishes to refer and/or edit.
  • Interface Inspector (206) enables every element within the User Interface to be independently configured using graphical and/or textual elements.
  • the data tables containing the Interface data can be saved and reloaded into any other version of the IIS S or replaced with any other set.
  • the interface elements can be categorised as follows: (i) "Graphical Tiles” used as Tabs, Buttons, Labels, Icons, Symbols, Dividers and Backgrounds. These may include a variety of different versions for each single interface element which enable its "state” to be shown to the user through visual changes in appearance;
  • the Interface Inspector enables the Developer to edit every interface element in order to independently control the appearance of each part of the user interface.
  • Event Inspector The Event Inspector (208) and the Event Tables, to which it provides access for inspection and editing, contains a table of records recording specific events that occur during use of the IISS (Event Record(s)) and tables of records containing information about each type of event (Explanatory Tables).
  • the Records created become a Log of significant events during the use of the IISS.
  • Events may record, for example, system errors or administrative or user actions.
  • each Error Record records any relevant information concerning an error event including when where and how it occurred together with error code key(s) linking to records in the Explanatory Tables which enable interpretation of the error codes.
  • the Error Records enable the Developer and those providing System Support to identify and analyse procedures within the IISS which require development and/or potential changes in training materials and documentation.
  • these Records may record occasions when, for example, the Administrator creates or disables a user, deletes a user's history or takes other significant steps in changing the data held by the IISS.
  • these Records may record occasions when, for example, a User deletes a record or takes other significant steps in changing the data held by the IISS
  • a user navigational step within the IISS is instigated by the user through User Command and Control and the Layout Router then determines the destination Interface Screen / Layout which is then displayed to the user.
  • the identity of the next screen to be displayed is controlled by the BP Key (defined below under Button Parameter fool) derived from the user's last User Command and Control interaction with the IISS.
  • the BP Key gives access to a record in the Layout Router configuration tables storing the identity of the screen to be displayed. These tables can be edited by the Developer using the Layout Router Inspector to direct the user to any screen required at any point in the user's navigation.
  • the Layout Router Inspector (209) can be used to configure many different data tables.
  • One configuration may provide access to Interface Screens / Layouts within the RDDE which are never accessed by another configuration.
  • the Developer can substitute one table or set of tables with another set to provide the client's users with a completely different navigational and interface experience.
  • Each Layout Router data table stores the relevant data for a user's navigation of the IISS in a single record.
  • Each table has multiple records.
  • Each record stores Layout Router data required for a single user access level.
  • Multiple records store the Layout Router data for multiple user access levels. Accordingly, the Layout Router can be used to control the user navigational experience of many different user access levels.
  • Each user access level can have, if required, a completely different IISS user interface.
  • the Layout Router results in all user navigation around the IISS being "soft-coded", thus editable by changing the value of a variable, without accessing the underlying coding. This gives the Developer great flexibility. If a client wants a particular Layout Screen to be displayed to a specific level User at a certain point in their interaction with the IISS the new screen is produced, based on the Single Master Interface Model described above, and the Router set to display that screen at the specified point in the user's future navigation of the HSS.
  • the Window Tool (210) and the Window Table, to which it provides access for inspection and editing, contains records in which are stored variables controlling the display of User Administrator and Developer Interface Screens (Window Variables).
  • Each Window Record contains a unique key identifying the Screen to which the record relates.
  • the Position, scale and size of the Screen are controlled by the Window Variables contained in the Window Table record for that screen linked through the unique key.
  • the Window Variables are updated so that next time the Screen is used it will be displayed where the User last placed it, with the same size and scale.
  • Non-exclusive examples of other data which can be stored in the Window Table are variables identifying the type of Screen, controlling access, controlling whether or not the Screen is printable and if it is the relevant print variables such as paper source, size, orientation and scale
  • BPT Button Parameter Table
  • Each virtual button within the User System Interface stores a single numeric value. This value combined with an Environmental Variable derived from the current context of the IS, provides a unique key ("the BP Key") giving access to the appropriate record in the BPT.
  • the values stored in this table provide control over the IISS Interface and thus the user experience.
  • the Interface can be set to change its appearance and behaviour dependant on specific values obtained from the current BPT record accessed by the unique key.
  • the Button Parameter Tool enables the Developer to edit the variables stored in each record of the BPT in order to independently configure the behaviour of every Button within the interface.
  • the BPT may also be used as a storage medium by programmed procedures running within the ESS ("Programs"). Such a procedure may output a change of value or values held in a specific record or records of the BPT in order to change the way in which the IISS responds to user interaction in the future.
  • the BPT also enables the programmatic Function called by specified User Buttons to be selected and set from the list of available functions.
  • variables stored by the BPT can be categorised as follows, all of which include variables used by Programs and/or written to by Programs: (i) variables controlling the activation or deactivation of individual Interface Elements (such as Buttons); or
  • the Specification Tool (16) enables a client with or without the help of a Developer to record their principal IISS requirements.
  • the data stored by the Tool may be used manually as a definitive information source by the Configurer, forming an instantly documented specification and/or to automatically configure an ESS within the Invention's RDDE.
  • the Tool assists the client in organising data taken from legacy systems so mat it can be automatically imported into the new ESS.
  • the Tool enables the data fields ("fields") required by the client to be defined and linked to the existing fields within the standard data structure of the RDDE.
  • the Specification Tool can then be used to define the different screen layouts of fields that they require for records, listings, reports, outputs and other layouts, to define the fields on which the user must be able to search and what is to be displayed when records have been found and to define any other process or control that they require within their new ESS.
  • Help Table records may store textual Help together with other Help resources such as images and movies which explain or elucidate use and operation of the IISS
  • Help may relate to any specific object on any Interface Screen / Layout and/or any Interface Screen / Layout. Help records each contain a unique key identifying the screen or interface object to which they relate. Accordingly, the Help is contextually sensitive. The User or Developer is provided with the appropriate help for the screen or object in which they indicate their interest
  • Help may non-exclusively comprise any explanatory material including explanatory text, images, animated "movies" with or without a sound track which may comprise a commentary, web pages viewable through a web browser.
  • Help may explain what a specific interface buttons does or may explain how to undertake an entire process
  • Any user may also obtain additional Help explaining concepts, terms or words used in Help text.
  • Every data record within the RDDE contains a series of fields ("Data Key Fields") by which it can be related to one or more records in any other data table(s). Thus any record can be related to any other record(s).
  • the data required to create these relationships can be automatically recorded on record creation and/or at any later time. This is controlled by the settings in the relevant record in the Case Table.
  • An Environmental Variable automatically provides the Case Key to access the correct Case Table record.
  • the Case Table contains records each of which controls the automatic creation of relationships between the subject record and any other records in the IISS in specific circumstances.
  • the appropriate Case Table record controls which Data Key Fields in the current record are populated with the unique keys of other records at the point at which the Case Table Control is invoked.
  • the Developer can use the Case Tool to create new Case Table records, and to edit existing Case Table Records, in order to control automatic relationship creation where appropriate.
  • Every column of data displayed in the form of listings within the IISS can be configured to sort alternately A to Z and Z to A for different types of data for example text number date and time data by configuring the Column Sort Table on the Server
  • Each record in this table relates to a specific User Interface Layout.
  • the names of the Column Headings are stored in this Table.
  • the new layout will then provide full Column Sort services.
  • the Invention uses a single "Master" computer layout screen which is copied and used as the foundation for every user System Screen throughout the IS. Every element in this screen automatically changes to reflect the type of data it is being used to display, the current Active Mode within which it is being used and the availability of user functions. In consequence the user receives a very consistent and responsive experience (263).
  • the Interface can be built to change its appearance dependant on the values it derives from the Button Parameter Table, calculations using its own name and other variables such as the current Data Module and user inputs ("Environmental Variables").
  • the RDDE offers a number of different "Active Modes" for the IISS each of which changes the behaviour and appearance of the current copy of the User Interface Screen.
  • the Active Mode of each User Interface Screen is noted within its technical name.
  • the Layout Router is directed to display a new layout the active mode to be used for that layout is determined by information incorporated within its name.
  • the Master Interface layout screen comprises many graphical and textual fields in multiple layers.
  • the graphical or textual objects displayed by each field, at any given point in the use of the IISS are controlled by a calculation engine which itself is controlled by Environmental Variables.
  • the Status Inspector (221) displays the current values of significant system variables to an Administrator.
  • the Settings Inspector (222) displays the current values of system settings and licensee settings.
  • System settings enable or disable features and services.
  • Licensee settings include, for example, the name of the Licensee and numbers of permitted users.
  • Licensee Settings which control, for example, the number of permitted users and the Data Modules which can accessed.
  • Language Inspector The Language Inspector (207) and the Language Tables, to which the Language Inspector provides access for inspection and editing, contains records in which are stored textual variables to be displayed on User and Developer Interface Screens ("Language Variables").
  • Each Language Record contains many Language Variables any of which may be used on any Screen within any Interface.
  • All textual material not comprising Data stored in Data Modules on the Server, which is displayed to users (non-exclusively including textual labels, screen messages and status messages) may be stored in a Language Table.
  • An IISS may be conveniently localised for any language or market by substitution of one or more Language Table or Tables with replacement(s) in the desired language.
  • Developers and Administrators accessing the Users' Table through the Users/EDDT Inspector (225) can create edit enable disable and delete Users. They can also interrogate the User's history data on the server in order to check what any specific user has been doing.
  • Each User's record in the Users' Tables (45) can edited to change variables such as then- Name, Password, Access Level, Data Authority, Function Level and EDDT Team Membership. The latter is explained further below.
  • No user can access any part of the RDDE or an ESS built using the RDDE, other than the login screen without entering the correct user name and password at login in circumstances where their user table record has currently an enabled status.
  • the Users/EDDT Inspector can be used to inspect and edit a User's Team Membership.
  • the Users/EDDT Inspector (225) provides access to a User's Team membership. Every Team forms part of a hierarchical structure within multiple layers of the structure of an Enterprise.
  • every Team belongs to a Department, every Department to a Division and every Division to an Enterprise.
  • Each User can belong to as many Teams as required.
  • the Team or Teams of which a User has membership is/are used by the Access Authority Tool to determine the User's access rights to any given record.
  • the Users/EDDT Inspector is used to inspect, add or remove the Team memberships of any User.
  • the Users/EDDT Inspector provides an Administrator with access to the EDDT Management Tool (235) and Tables (46) on the Server. Calculation Inspector
  • Calculation Inspector gives the Administrator direct access to the formulation of such calculations in each Data Module. These are Used Defined Calculations, which may, if required, utilise data stored in the User Defined Lookup Tables (65).
  • the User Defined Calculation Tables (64) are located on the Server and accessed from the Administrator Interfaces through the Calculation Inspector (224).
  • the Client maintains direct control over the way in which their IIS S calculates values numeric, textual or graphical and is thus able to adjust them over time as circumstances dictate and second the Client's Server installation can be moved to a more recent version by normal data transfer maintaining the integrity of their IISS without any further manual updating being required.
  • the Client can, of course, choose to build their own data structures within the Business Logic File which remain their own full responsibility and which will not be updated by the Developer when other parts of the IISS are updated.
  • the Access Control / Authority Tool (231) provides a very flexible and powerful means of controlling who can or cannot exercise each type of Data Access to any given Data Module record.
  • Access Right(s) Possible types of access to a Data Module (together “Access Right(s)”) include the right to: (i) create a record;
  • Every record is owned and controlled by the Team or Teams of which the Record creator was actively a member at the moment of creation.
  • Every user may belong to one or more Teams.
  • a user belonging to more than one Team can, at any time, elect to be treated as currently inactive in one or more of the Teams to which they belong. Failing such an election they are treated as being concurrently Active in all their Teams.
  • the system administrator can adjust the following values which enable the Access Control system to be adjusted to meet user requirements:
  • Authority Enhancements every user permitted to use the IIPP has a base authority of 1. Each user can be given one of a number of enhanced levels of authority, each of which multiple their Authority by an enhancement value. The Administrator sets the numeric enhancement value for each enhanced level of Authority);
  • This calculation refers to the current EDDT Model of the Organisational structure, rather than that which existed at the date of creation of each record enabling organisational structural changes to be easily catered for.
  • Whether or not the User can exercise the Access Right in question depends on whether their Actual Data Authority in this case is greater than or equal to the Data Authority required to exercise this Access Right as set by the Administrator as described above.
  • This tool (232) provides the System Administrator with considerable flexibility in controlling which users can see which information. It enables the System Administrator to give each User a different Confidentiality Level in relation to any Data Module.
  • the Administrator can create edit and delete Confidentiality Level Records in the UIu table at will. Users with the ability to create and/or edit Data Module records can set the User Confidentiality Level required to have any access to each individual record.
  • the EDDT Inspector 225
  • the Administrator to check and change a User's Team Membership
  • the EDDT Management Tool 235
  • the hierarchical structure of the Enterprise to be modelled ready for use in the EDDT Inspector
  • This Tool is located on the Server and accessible from the EDDT Inspector.
  • Each record belongs to one of the defined hierarchical levels. For example in the case of a four level system a record is created for each Enterprise, each Division, each Department and each Team. Each record, depending on its level, is specified to be a "child" of the appropriate "parent" record. Thus Team Z may be the child of Department Y, itself the child of Division X, itself the child of Enterprise W.
  • the RDDE incorporates the ability to service multiple Enterprise Identities simultaneously administered through the Enterprise Identities Inspector (223) and the Multiple Enterprises IDs Tool (237) on the server.
  • an Administrator can create more than one Enterprise Identity in order to concurrently run multiple enterprises .
  • the Administrator can configure many different Enterprise Identities stored in the Enterprise Tables (238) so that a single IISS can provide all required services both to users working for different separate Enterprises or for users working for more than one Enterprise at the same time.
  • Configuration of an Enterprise Identity includes all the data that distinguishes that Enterprise from any other, for example, data comprising its:
  • the hierarchical structure of the Enterprise is then modelled using the EDDT Management Tool accessible on the Server.
  • This tool (239) enables the System Administrator to create, delete and edit the Category Attribute records in the tables (240) from which fixed Category and Attribute value lists are created.
  • the Administrator can thus create appropriate Categories for use in each Data Module then create the required list of Attributes to be displayed in relation to each Category in each Module.
  • Each set of Categories and Attributes may be set to be either Fixed or Dynamic.
  • a dynamic set pe ⁇ nits users to add values to either Categories and/or Attributes which are then reflected in future lists of available Categories and Attributes.
  • a Fixed set means that only those values entered by the Administrator using this Tool will be available.
  • This Tool enables the System Administrator to create, delete and edit User Defined Lookup Table (65) ("UIu Table") records which are both used to create User Defined Value Lists and to store Used Defined data to be used by User Defined Calculations.
  • UIu Table User Defined Lookup Table
  • values stored in the UIu Table can be amended as necessary, for example, where fulfilling a Rate Card function, to reflect changes in the Enterprise's pricing structure.
  • New records can be added, amended or deleted to ensure that the Administrator has complete control over the data used by the Value Lists and Calculations configured to use this data.
  • This UIu structure is to ensure that any unique values used by the client enterprise within calculations are stored within the data structure of the RDDE completely separate from the system structure.
  • the Interface (263) presents to the User a variety of graphical and textual items providing information regarding both the Data in which they are interested or with which they are working and the Command and Control options that are available to them as a User.
  • the consistent interface enables users to quickly learn how to use any IISS built using the invention.
  • the user undertakes different activities in different Active Modes but is not aware of this fact.
  • the Active Mode is one of the Environmental Variables controlling the appearance and behaviour of the user interface.
  • the basic Active Modes are Browse, Edit, Find and Print, but other Active Modes can be created by the Developer as required.
  • Some data tables, or sections of such tables may regularly be copied from the server to the workstation Mirror Tables (290) for local use on the workstation.
  • Such tables may comprise system configuration data and/or user data. Means may be provided for such data to be written back to the server and for conflicts resulting from the same record being edited by different users to be resolved.
  • key system settings are set and stored on the server in the settings tables (43) and are thus editable by an administrator from any workstation. On login the user's workstation uploads these settings from the server for local use during the user's session.
  • Means may be provided to automatically upload a new set of settings from the server in certain circumstances.
  • Each means of finding records in each module uses a different screen design which can thus be tailored exactly to a client's requirement. This means that screen designs can be simple and easy to use rather than becoming congested with too many potentially confusing options.
  • MCM Multi Channel Marker System
  • An alternative find operation (“QuickFind”) may be offered in Browse mode enabling the user to search on a small number of common fields and instantly display the record(s) meeting those criteria without entering Find Mode which may thus be reserved for undertaking more complex queries.
  • the automatic record linking service controlled by the current configuration of the Case Tool means that often a user does not need to actually "Find” records. Merely by clicking on a linked record or Tab giving access to another Data Module will immediately display all the records in the target Data Module linked to the current record. Thus the user can often "find” records without having to undertake any "Find” selection as such - the operation becomes automatic. Since any currently displayed records can be instantly marked with the MCM and then instantly recalled, this provides great ease of use and flexibility for the differing requirements of different users.
  • Reports can be created in a variety of ways.
  • the IIS S is preconf ⁇ gured to enable a user to view and print reports comprising records they have found by whatever means, whether pre-ordained or through their manual selection.
  • the user can also dynamically specify their own report contents, within predefined formats and save those hybrid reports for future reuse.
  • the PrePrint / Merge Tool (265) is displayed. This provides a variety of features including selecting the normal print options (what is to be printed, number of copies, paper format etc) previewing that which is to be printed, setting the sort order and format of the printed output and outputting to other formats such as PDF other software program formats and email.
  • the Merge options within the Tool enable the user to set up merged output to dynamically include data from each record. For example to personalise the contents of a letter to include reference to information held within the IISS in relation to the intended recipient or job or project to which the communication relates.
  • the User Preferences Tool gives each user access to settings controlling how the IISS responds to their use. For example these could include:
  • Button Help (267). Until this Help is turned off clicking on any button in the User Interface displays information about what that button does. This allows the user to find out what each button does before actually using its functionality. This information can be printed. The user can turn off Button Help and revert to normal operation with a single click.
  • a single click of an interface button displays the Layout Help Tool (268) giving information about the layout currently displayed, describing its functions and how to use them.
  • Keywords within this Help information are themselves explained with additional Help displayed by clicking on the keyword. This aids user understanding and results in the Help data being non-repetitious and thus easier and quicker for the Developer to update as further versions of the IISS are released. This info ⁇ nation can be printed.
  • the Properiser Tool (269) provides users with an easy means of dealing with unusual and anomalous use of letter case and symbols in words whilst retaining the convenience of automatic conversion of names to the correct case. This issue occurs primarily in relation to person, organisation, and trade names where non- standard use of upper and lower case characters make automatic correction of case difficult.
  • the tool enables users to specify:
  • the user can always move through the set sequentially using the Previous or Next Services or move to one end or other of the set using First or Last Service.
  • New record creation may be part of an automatic process or may be "manual".
  • the new record may be linked at creation to other records to which the current record on which the User is located is related through the current configuration of the Case Table and the Case which the IISS is configured to call at this point.
  • a New Record Dialogue is displayed enabling the User to select from existing records, from any relevant Data Modules, if this appropriate, to which to link the new record. Where new information is inserted in the Dialogue which does not relate to any existing record the IISS will automatically create another new record as necessary.
  • a user wanting to enter an Expense may find it convenient to find a previous similar example, duplicate that, and change it as necessary.
  • Duplicate record is not a true duplicate. It is a new record superficially similar to the original record but with its own unique identity.
  • a user may delete a record.
  • the procedure is designed to ensure that this cannot be undertaken unintentionally.
  • the user is prompted to hold down another key whilst clicking the delete button again.
  • the Omit button omits the current record and ⁇ ah> Omit displays all the currently omitted records. This provides a very useful combination of functionality when dealing with sets of records.
  • the Developer has configured the Case Tool so that Data Module records are automatically linked to any other relevant records in the same or any other Data Modules. This enables the User to always be able to quickly and easily display sets of records which are relevant to their current task or requirement.
  • a refinement to automatic linking may be to provide two or more different perspectives for the basis on which linking is established and/or the basis on which it is displayed. For example whilst viewing a history record with both a related job and a related contact the user may wish to link automatically to communications relating to the job or to the contact - each requirement comprises a different perspective.
  • Sorting all Columns A-Z or Z-A All Listings can be sorted A-Z and Z-A by clicking the column heading. This service is controlled by the data stored in the column sort table record for any given screen.
  • Every record can be marked with a virtually limitless variety of Attributes. These can be ⁇ selected from pre-defined fixed lists, capable of being edited by the system administrator, to control the input, where users are not permitted to enter a value not already in the list, or dynamic so that they automatically offer all the Attribute values already entered in that Data Module and permit the user to add new values not previously entered. Every Attribute is grouped under a single Category under a single Data Module. Thus the user, wishing to select an Attribute for a record must first select the appropriate Category and then select the desired Attribute from the various Attributes listed or grouped under that Category within that Data Module.
  • Attributes Users can select and record as many Attributes as they wish in respect of every record. These Attributes can then be searched for or found using a multi layered Boolean logic filtering system where, for example, records with Attribute "A” and Attribute "B” or Attribute “C” or Attribute “D” (and for many more iterations of the and /or logic) can be instantly displayed and then marked using the Multi Channel Marker described above.
  • the Attributes filtering can be combined with numeric and/or data range filter criteria.
  • On logging in the user may be automatically placed on the record on which they were located when they last logged off and thus can work in a continuance from their previous session.
  • Coding in its basic form enables a set of records to be marked with an alpha-numeric string as an identifier to enable that set of records to be recalled at any time.
  • An interface may be provided to enable records to be found by reference to their coded string.
  • a further interface, for List Management, may be provided whereby records within a given coded set may be recalled and then records added or removed from that set by means of a procedure that adds or removes the current code from one or more specified records.
  • Any record can be marked as the "parent” of any other record where a Data Module is configured to provide this service. This enables the construction of "Tree Structures” where records can be linked easily and quickly to a series of other records through an number of intermediate stages.
  • Sort Service Whilst all listings provide the column heading Sort Service described above all Data Modules can also be sorted by any combination of selected criteria required by the user.
  • Any records can be locked to prevent any future amendment.
  • Such locking can be absolute or subject to an overriding ability controlled by the System Administrator to unlock the record only able to be utilised by high level users.
  • Multi-Channel Marker System Every record, in every Data Module, can be "marked” by a user in any one or more of several different user "Marker Channels". Each user can name their own marker channels as they wish. A single click will immediately display all records marked by this user in the current marker channel. Channels can be changed at will. The user can instantly display records marked in any combination of the seven channels. This powerful system makes it very easy for users to do what they want most, to be able to redisplay any given set of records they have been dealing with quickly and easily.
  • the user can also display records marked in more than one channel by merely selecting the MCM channels on which to search.
  • the user may have access to seven channels and one can be kept hidden for system or Administrator use.
  • Server Deployment Licence, Tools and Data (70)(18)(80)(81)(82)
  • the "Server” components described below would be located on a physically separate computer providing the Server service. However, this is not necessarily the case.
  • the Server components could equally form part of a single deployment of the Invention on as single computer, used for example, by a single user as a workstation, or by a server offering multiple user "virtual" sessions to remote or network users.
  • the Deployment Licence (18) is a preferred feature of the Invention.
  • the Licence controls what the user is entitled to do in terms of both the Data Modules available for use by the user, date by which the Deployment Licence expires, what specific services the user may utilise and how many users may be authorised to use the IISS or may be permitted to login at one time.
  • the Developer is enabled, using these Licensing variables, to configure a Deployment of the ⁇ SS in whatever is the most commercially appropriate manner for a given client.
  • a client wishing to lease the IISS can be given an Expiry Date a specific period after the next Lease Payment is due, and be sent a new Expiry Date code after payment has been received.
  • These tables (246) store the records regarding Events automatically created throughout the Core System which can be inspected by an Administrator from any workstation through the Event Inspector.
  • This Tool (231) enables an Administrator to edit a User's Authority to access Records in each Data Module.
  • This Tool (232) enables an Administrator to edit a User's Confidentiality Level which controls which Records in each Data Module they can access based on the comparison between their Confidentiality Level and the Confidentiality Level of the individual Record.
  • These tables (234) store all the Records created by each User as they navigate through the IIS S if that feature has been activated by an Administrator. This data being stored on the Server means that a User can log on to any Workstation and use their existing User History to move back or forwards over the records over which they have navigated during a previous session.
  • This Tool enables an Administrator to create and edit multiple hierarchical layers in the structure of an Enterprise, to which Users may be given membership using the Users/EDDT Inspector.
  • the RDDE incorporates the ability to service multiple Enterprise Identities simultaneously.
  • the Administrator can configure many different Enterprise Identities using the Multiple Enterprise IDs Tool (237) so that a single IIS S can provide all required services to users working for different separate Enterprises or for users working for more than one Enterprise at the same time. ,
  • Configuration of an Enterprise Identity includes all the data that distinguishes that Enterprise from any other, for example, data comprising its:
  • Tax Identity - Registered No., Taxation Periods (iii) Tax Identity - Registered No., Taxation Periods; and (iv) Financial Identity - Accounting Codes, Conventions, Accounting Periods.
  • This tool (239) enables the System Administrator to create, delete and edit the Category Attribute records from which fixed Category and Attribute value lists are created.
  • the Administrator can thus create appropriate Categories for use in each Data Module then create the required list of Attributes to be displayed in relation to each Category in each Module.
  • Each set of Categories and Attributes may be set to be either Fixed or Dynamic.
  • a dynamic set permits users to add values to either Categories and/or Attributes which are then reflected in future lists of available Categories and Attributes.
  • a Fixed set means that only those values entered by the Administrator using this Tool will be available.
  • This Tool enables the System Administrator to create, delete and edit User Defined Lookup Table (65) ("UIu Table") records which are both used to create User Defined Value Lists and to store Used Defined data to be used by User Defined Calculations (64).
  • UIu Table User Defined Lookup Table
  • values stored in the UIu Table can be amended as necessary, for example, to reflect changes in the Enterprise's pricing structure. New records can be added, amended or deleted to ensure that the Administrator has complete control over the data used by the Value Lists and Calculations configured to use this data.
  • this UIu structure is to ensure that all unique values and business logic calculations used by the client enterprise are stored within the data structure of the RDDE and thus as data, may be moved from one version of the IIS S to another. Hence this UIu structure divorces the licencee's unique business logic from the formal database structure of the of the ESS.
  • An Administrator can use this Tool (244) to create and edit Workflows, which are series of Tasks to be undertaken in relation to, for example, a Project; which a User can then use, via a Function, as the model on which to base automatic creation of a whole series of Tasks to be performed or completed in relation to, for example, a specific Project.
  • a specific workflow can be selected and applied to any other record so that a series of Tasks then exist to be undertaken in relation to that record. If the workflow is designed to be sequential this can enable management of processes automated exception analysis based on what tasks have or have not been completed.
  • Each Task can be configured by the Administrator to be created only if specific values relating to, for example the related Project, hold a specific value or are within a certain range.
  • the creation of individual records in the workflow can be intelligent so that only relevant Task records are created.
  • User Data Modules (82) comprise the core building blocks of the user data holding aspect of the Core System. Each Module contains data that is essentially different to every other. Some records are Transactional meaning that one or more such records may be created primarily in relation to a Non Transactional Record. For example, these could include:
  • Projects Non-Transactional Records
  • a Project is a generic term covering something to be done for a Client, or for an Individual or Organisation where the user does not have Clients and includes something to be done for the user's own Enterprise - thus it is the place where most "things to be done" are separately identified in order that Transactional Records may then be created recording what is to be done (Future) or what has been done (Communications, History, Expenditure, Income and Ledger); Lines (Transactional Records) - each Project can comprise an Order and the Line records comprise the line items in that order;
  • Transport Records a generic place to store any data or information not stored elsewhere, for example details of Physical Items such as Paper Files, Documents and other Storage Media or the address or location of any information, web page or data such as a computer Uniform Resource Locator ("URL");
  • URL Uniform Resource Locator
  • Movements Transactional Records— every movement of every Product/Asset is recorded to provide accurate data and a complete audit trail;
  • Bills Transactional Records
  • each record comprises a claim for payment, usually but not necessarily addressed to a Client, which may be in respect of a Project, and which is intended to create Income;
  • Ledger Transactional Records
  • Ledger records created in relation to Bills, Expenditure and transfers of funds enabling the preparation of a Trial Balance, Balance Sheet, Profit and Loss Account, Cash Flow or any other relevant financial Analysis.
  • a Configurer can, using the Invention, specify, configure and deliver a high quality IISS exactly matching a client's requirement in an efficient and timely manner.
  • the Administrator of an IISS built using the Invention has at their disposal a series of Interfaces Tools and Services enabling them to perform their role quickly and efficiently.
  • a typical IISS built using the Invention's RDDE will include programming, other logical elements, configuration tables, data tables and user screens ("System Components") ready for deployment on the selected hardware under the selected operating system and utilising the support of the selected database application environment.
  • a Single File IISS where System Components are included within a single file
  • a Dual File IISS where the System Components are deployed on the user's computer Workstation in one file with the exception of the data tables which deployed on a network server in a second file (to enable, for example, reduced network traffic by undertaking most processing work and logical activity on the workstation leaving merely the data to be transferred over the network and enabling the workstation interface file to be upgraded by merely replacing it and importing the configuration tables records)
  • a Triple File IISS similar to the Dual File IISS but where the configuration tables are abstracted into a second file residing on the user's workstation (to enable, for example, the upgrading of the other file on the workstation, the User Interface and Logic file (excluding configuration) by merely replacing it with a new version);
  • a Quadruple File IISS similar to the Triple File IISS where a second file is provided on the server to which the users have a high level of access and into which they can build their own business logic enabling all network users to access their own Business Logic services whilst still accessing all the services provided by the rest of the IISS (to enable, for example, the upgrading of the data file by replacement and importing of data table records whilst leaving tile user's Business Logic file untouched);
  • a Pentuple File IISS similar to the Quadruple File IISS where a third file is provided on the user's workstation to store specialist user screens designed and deployed for this particular installation so that the rest of the system can be upgraded whilst leaving those screens untouched;
  • Some examples deployments of IISS created using the Invention may comprise:
  • the methodology made possible by the Invention could enable the business to deploy the IISS it required, quickly and at an acceptable cost and benefit from regular system upgrades in the future without having to commission custom development work.
  • the IISS deployed may be identical versions produced using the RDDE, merely configured differently to deliver a completely different IISS to each client.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Human Computer Interaction (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • User Interface Of Digital Computer (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Input From Keyboards Or The Like (AREA)

Abstract

La présente invention concerne un système de gestion d'information comportant une base de données d'information (5) servant au stockage d'enregistrements de données (82); un composant d'interface (3) servant à la génération d'interfaces utilisateurs permettant la saisie, l'accès et la manipulation d'enregistrements de données (82) par un utilisateur dans ladite base de données d'information (5); une unité de données de contexte servant au stockage de données identifiant un utilisateur et les opérations effectuées par un utilisateur; et une unité de configurations (1, 2) servant au stockage de données de configuration identifiant des opérations spécifiques à effectuer en réponse à une entrée d'utilisateur lors du stockage de données identifiées dans ladite unité de données de contexte. Ledit composant d'interface (3) est sensible à une entrée d'utilisateur pour générer des interfaces utilisateurs permettant la saisie, l'accès et la manipulation d'enregistrements de données (82) par un utilisateur dans ladite base de données d'information (5) en fonction de ladite entrée d'utilisateur, des données de contexte stockées dans ladite unité de données de contexte et des données stockées dans ladite unité de configurations.
PCT/GB2008/001792 2007-05-25 2008-05-27 Systèmes de gestion d'information WO2008145981A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GB0710109.0 2007-05-25
GB0710109A GB0710109D0 (en) 2007-05-25 2007-05-25 Information management system

Publications (2)

Publication Number Publication Date
WO2008145981A2 true WO2008145981A2 (fr) 2008-12-04
WO2008145981A3 WO2008145981A3 (fr) 2009-08-20

Family

ID=38265396

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/GB2008/001792 WO2008145981A2 (fr) 2007-05-25 2008-05-27 Systèmes de gestion d'information

Country Status (2)

Country Link
GB (1) GB0710109D0 (fr)
WO (1) WO2008145981A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112364619A (zh) * 2020-11-27 2021-02-12 智业软件股份有限公司 一种自定义表单生成方法、终端设备及存储介质
CN115129216A (zh) * 2022-06-29 2022-09-30 北京达美盛软件股份有限公司 一种跨组织的数据配置管理方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020091763A1 (en) * 2000-11-06 2002-07-11 Shah Lacky Vasant Client-side performance optimization system for streamed applications
WO2005015454A1 (fr) * 2003-07-22 2005-02-17 Sap Aktiengesellschaft Configuration declarative et concepts de personnalisation pour structure commerciale orientee services
US20060136872A1 (en) * 2004-12-20 2006-06-22 Microsoft Corporation Integrated setup for generating customization XML
US20060271910A1 (en) * 2005-05-27 2006-11-30 Microsoft Corporation Method and system for customizations in a dynamic environment

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020091763A1 (en) * 2000-11-06 2002-07-11 Shah Lacky Vasant Client-side performance optimization system for streamed applications
WO2005015454A1 (fr) * 2003-07-22 2005-02-17 Sap Aktiengesellschaft Configuration declarative et concepts de personnalisation pour structure commerciale orientee services
US20060136872A1 (en) * 2004-12-20 2006-06-22 Microsoft Corporation Integrated setup for generating customization XML
US20060271910A1 (en) * 2005-05-27 2006-11-30 Microsoft Corporation Method and system for customizations in a dynamic environment

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
BREHM L ET AL: "Tailoring ERP systems: a spectrum of choices and their implications" SYSTEM SCIENCES, 2001. PROCEEDINGS OF THE 34TH ANNUAL HAWAII INTERNATI ONAL CONFERENCE ON JANUARY 3-6, 2001, PISCATAWAY, NJ, USA,IEEE, 3 January 2001 (2001-01-03), pages 2946-2954, XP010549936 ISBN: 978-0-7695-0981-5 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112364619A (zh) * 2020-11-27 2021-02-12 智业软件股份有限公司 一种自定义表单生成方法、终端设备及存储介质
CN112364619B (zh) * 2020-11-27 2022-08-26 智业软件股份有限公司 一种自定义表单生成方法、终端设备及存储介质
CN115129216A (zh) * 2022-06-29 2022-09-30 北京达美盛软件股份有限公司 一种跨组织的数据配置管理方法及系统

Also Published As

Publication number Publication date
GB0710109D0 (en) 2007-07-04
WO2008145981A3 (fr) 2009-08-20

Similar Documents

Publication Publication Date Title
Davis Business process modelling with ARIS: a practical guide
US7571392B2 (en) User definable task based interface
Davis ARIS design platform: advanced process modelling and administration
KR101033446B1 (ko) 데이터 통합 시스템의 사용자 인터페이스
US7496890B2 (en) Generation of configuration instructions using an abstraction technique
AU2011202413B2 (en) An automated publishing system that facilitates collaborative editing and accountability through virtual document architecture
US8904342B2 (en) System and method for rapid development of software applications
US20040221259A1 (en) Method and apparatus for status display with intermediate database access
US20070094306A1 (en) Method and model for enterprise system development and execution
US20110246535A1 (en) Apparatus and Method for Constructing Data Applications in an Unstructured Data Environment
US20200151226A1 (en) System and method for creation and handling of configurable applications for website building systems
Li Jira 8 Essentials: Effective issue management and project tracking with the latest Jira features
WO2008145981A2 (fr) Systèmes de gestion d'information
Turley Professional Microsoft SQL Server 2016 Reporting Services and Mobile Reports
Li Jira Essentials
Vesterli Oracle ADF Survival Guide: Mastering the Application Development Framework
Jennings Microsoft Access 2010 in depth
Woodruff Learning ServiceNow: Administration and development on the Now platform, for powerful IT automation
FitzGerald Crystal Reports XI Official Guide
Munro Learn FileMaker Pro 16: The Comprehensive Guide to Building Custom Databases
Chaffin et al. Cross-database searching: the implementation of Metalib
Johnson Microsoft Office Access 2007 on Demand
Fitzgerald Crystal Reports 2008 Official Guide
Hodel Beginning Microsof t Dataverse
Hild et al. Pro SharePoint Solution Development: Combining. NET, SharePoint and Office 2007

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08762201

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08762201

Country of ref document: EP

Kind code of ref document: A2