Module hierarchy

Programming Skills. One of the first steps in building RuleMaster expert system is creating the module hierarchy for the prototype. This requires skill in top-down design and structiared programming. 

Typically, a hypermedia system is formed of a network of links and nodes, within which it may be possible to identify substmctures of various degrees of complexity. The overall stracture is influenced both by the intrinsic organisation of associative links within the body of information, and by the style of the hypermedia authoring environment. Wright and Lickorish [18] identify a number of different categories of hypermedia stmcture. Beyond text with a strong linear discourse structure (perhaps with footnotes), such stmctuies may be loops modules hierarchies matrices or networks. A distinction between structure and presentation, in the senses which Wright [16] identifies in conventional technical texts, is less clear in hypermedia systems, where the presentation to the user of links is fundamental to the structure of the systeia... 

Table VII3.1.2-1 Control Activity Module Hierarchy and Functions [3] ...

The SSIM is hierarchical, in the sense that several modules (processes, subprograms) can be maintained at the same time and synthesized separately. A module hierarchy graph represents the calling relations among the different modules. Figure 3 summarizes the SSIM design representation. 

The CTD is organised into five modules. A schematic representation of the stmcture and hierarchy is shown in Figure 6.1. Module 1 is designed to contain region-specific information such as application forms and other administrative provisions that may apply. As such, it is not harmonised and is not considered part of the CTD. The other four modules present the technical data in a harmonised format. Module 2 should contain critical overview assessments of the quality, non-dinical and clinical data, together with summaries of the non-clinical and clinical data. The objective of this section is to provide reviewers with an introduction to the submission, and to orient... 

Structure Evaluating) was first developed before the MultiCASE system. It uses the same technology but differs in some ways. The major algorithmic difference in MultiCASE is the use of hierarchy in the selection of descriptors, leading to the concept of biophores and modulators. Another important difference is that only with MultiCASE new internal proprietary data can be used to create new databases. 

The control module layer is the lowest level and defines how field devices (e.g., valves, pumps, controllers, etc.) interact with the process control system. Phases are at the next layer and describe small (often generic) sequences (e.g., fill, transfer, initiate temperature control, etc.) that operate on a unit. At the next layer up the hierarchy, phases may be combined into unit operations to perform more complex functions (e.g., distillation, crystallization, etc.). 

The central idea in a modular hierarchy is the module which is a structure or a system that may be regarded both as a whole, de-composible into submodules identified with a lower level, and as a part combinable into super-modules identified with a higher level. 

Planning and scheduling. This module corresponds with the business part of the control hierarchy. It has a business model and based on plant data (current and past values), on external data (market data, external plant info, etc.) and using the company business goals derives a production plan for the plant. It gives capacity production values as well as quality values to the lower, optimization, level. The resolution time at this level is days or weeks. 

A decision model represented by means of the Decision Ontology contains much information that is also relevant when an MCDA method is used (e.g., the hierarchy of the Goals). The application of such methods would be simplified if this information could directly be used in an MCDA tool. However, MCDA methods impose restrictions on the relations between the Decision Objects. For instance, AHP requires the sub-goals of a goal to be independent of each other. These restrictions are formally defined within the DecislonAnalysis module. 

In the Major Unit Process Evaluation module, information about plant design and operating characteristics is stored in a hierarchy of frame-like classes. The logic for gathering this information is controlled by a structure of ALEX demons and variables. 

Figure 4. KNODE file hierarchy as viewed from the job control module.

---