administrator’s manual optex gui visual user interface · optex optimization expert system...

ADMINISTRATOR’s MANUAL OPTEX–GUI

VISUAL USER INTERFACE DESIGN, IMPLEMENTATION AND MAINTENANCE OF

THE SYSTEM OF INFORMATION AND USER INTERFACE

THIS DOCUMENT CONTAINS CONFIDENTIAL INFORMATION AND INTELLECTUAL PROPERTY OF DO ANALYTICS LLC. AND IS PROVIDED WITH THE UNDERSTANDING THAT ONLY WILL BE USED IN THE ASSESSMENT AND USE OF OPTEX OPTIMIZATION EXPERT SYSTEM, AND WILL REMAIN CONFIDENTIAL, PROTECTING IT AGAINST INSPECTION OF THIRD PARTIES NOT EXPRESSLY AUTHORIZED BY DO ANALYTICS

October 2018

OPTEX OPTIMIZATION EXPERT SYSTEM

OPTEX–GUI – Administrator´s MANUAL

1

CONFIDENTIALITY AGREEMENT

TO READ THIS DOCUMENT THE READER ACKNOWLEDGES THAT IT CONTAINS CONFIDENTIAL INFORMATION INTELLECTUAL PROPERTY OF DO ANALYTICS LLC AND AGREE THAT REMAIN CONFIDENTIAL, KEEPING PEOPLE AGAINST THIRD PARTIES INSPECTION AND ORGANIZATIONS NO EXPRESSLY AUTHORIZED BY DO ANALYTICS.

THE READER ACKNOWLEDGES THAT THE METHODOLOGY OF DEVELOP MATHEMATICAL PROGRAMMING MODELS BASED ON THE CONFIGURATION OF AN INFORMATION SYSTEM AND FURTHER PROCESSING IS OWN AND ORIGINAL OF THE PRODUCT OPTEX OPTIMIZATION EXPERT SYSTEM (OPTEX) , THAT IT WAS ORIGINALLY DEVELOPED BY DECISIONWARE LTDA. AND CURRENTLY OWNS DO ANALYTICS LLC (DOA).

THE READER ACKNOWLEDGES THAT HE KNOWS THAT READ AND/OR STUDY (OR PROVIDE SOMEONE TO

READ OR TO STUDY) THIS DOCUMENT WITH INTENT TO COPY / CHANGE / IMPROVE / SIMPLIFY / DISINTEGRATION / INTEGRATE / SPY (OR ANY OTHER SIMILAR ACTIVITY) i) THE METHODOLOGY IMPLIED IN OPTEX ii) INFORMATION SYSTEMS OF OPTEX, iii) COMPUTER PROGRAMS GENERATED BY OPTEX, AND / OR iv) ACCESS INTERFACES ASSOCIATED TO THE PROGRAMS THAT INTEGRATE OPTEX CORRESPOND TO A VIOLATION OF COPYRIGHT AND INTELLECTUAL PROPERTY OF DO ANALYTICS AND UNDERSTAND THAT DOA MAY TAKE LEGAL ACTIONS TO PROTECT THEIR RIGHTS.

THE INFORMATION CONTAINED IN THIS DOCUMENT MAY NOT BE DISCLOSED TO THIRD PARTIES AND SHALL NOT BE DIGITALLY COPIED OR PHOTOCOPIED, OR USED OR DISCLOSED IN WHOLE OR IN PART, FOR ANY OTHER PURPOSE THAN INTERNAL USE.

THIS RESTRICTION DOES NOT LIMIT THE RIGHT OF READER TO USE THE INFORMATION IN THIS REPORT, THAT IS PUBLIC DOMAIN OR IS OBTAINED FROM OTHER SOURCES WITHOUT RESTRICTION.

ALL INFORMATION OF THE THIRD THAT DO ANALYTICS HAS ACCESS AS A RESULT OF THIS DIFFUSION PROCESS OF THE SERVICES AND PRODUCTS THAT DO ANALYTICS OFFERS WILL BE KEPT STRICTLY CONFIDENTIAL BY DO ANALYTICS AND PROFESSIONALS OF DO ANALYTICS LINKED TO PROCESS.

ALGEBRAIC FORMULATION PRESENTED IN THIS DOCUMENT, THE SOFTWARE THAT CONTAINS THE IMPLEMENTATION OF THE MATHEMATICAL MODELS IN OPTEX CAN ONLY BE USED WITH ACADEMIC PURPOSES, AND LEARNING OF OPTEX; IF THE USER WANT TO USE THE ALGEBRAIC FORMULATION AND / OR COMPUTER PROGRAMS WITH COMMERCIAL PURPOSES THE USER SHOULD ACQUIRE A FORMAL SOFTWARE LICENSE. TO USE THIS MATERIAL AS PART OF A FREE PROCESS THE USER SHOULD HAVE A WRITTEN AND SIGNED AUTHORIZATION BY DO ANALYTICS.

DO ANALYTICS KEEPS THE PROPERTY OF THIS DOCUMENT AND MAY REQUEST ITS RETURN AND/OR ITS DESTRUCTION AT ANY TIME.



2

1. INTRODUCCIÓN

OPTEX OPTIMIZATION EXPERT SYSTEM (OPTEX) is the DO ANALYTICS LLC’s optimization

technology (http://www.doanalytics.net/Documents/OPTEX-Presentation.pdf).

OPTEX is a RAD tool (Rapid Application Development), focused on the design, implementation, start-up

and maintenance of DSSs (Decision Support Systems), conceived as a union of mathematical optimization models with information systems following the modern guidelines of OOP (Object Oriented

Programming), avoiding the intensive use of resources for programming computers in the development and maintenance of computing solutions based on the concepts of Mathematical Programming.

Based on a philosophy of concurrent development, in real time, OPTEX allows to minimize programming

activities; from the formulation of mathematical models and their links with the data model (all supported

in an information system), OPTEX generates online the "front end" for the end user, without generating code or executable linking complicated work. The above translates into the immediate availability of

additions or changes (in the models or in the information systems), and thus in saving time, which can be used more effectively in the mathematical processes modeling and the design of the interface of the DSSs

with other tools from the user organization, as they can be the ERPs, the GISs , …

OPTEX reduces to the minimum the cost of developing mathematical models; proposes a new way to

implement optimization software, which traditionally involves the implementation of one "executable" program for each model. Since its birth in 1991, OPTEX is conceived as a meta-tool (a robot, an expert

system) that allows the development of "all" mathematical models required in just one work environment. OPTEX “automatically” integrates information support system, generating a generic user interface that

allow the administrator to browse the tables of the information system. Last, but most important, OPTEX

is able to generate models based on low-level programs such as C, or high-level programs based on algebraic languages like GAMS, AIMMS, IBM ILOG OPL,... OPTEX ensures minimum implementation

times, competitive computing times and portability of the mathematical models.

OPTEX reduces to the minimum the cost of developing mathematical models; proposes a new way to

implement optimization software, which traditionally involves the implementation of one "executable" program for each model. Since its birth in 1991, OPTEX is conceived as a meta-tool (a robot, an expert

system) that allows the development of "all" mathematical models required in just one work environment. OPTEX “automatically” integrates information support system, generating a generic user interface that allow the administrator to browse the tables of the information system. Last, but most important, OPTEX

is able to generate models based on low-level programs such as C, or high-level programs based on

algebraic languages like GAMS, AIMMS, IBM ILOG OPL, MOSEL, AMPL ... OPTEX ensures minimum implementation times, competitive computing times and portability of the mathematical models.

OPTEX supports all the activities required to implement in real systems solutions based on multiple

mathematical models integrated into a DSS. The process to follow for each mathematical model can be summarized in the following steps:

▪ Mathematical modeling, whose product is an algebraic conceptual model;

▪ Data modeling, whose product is the data model of an information system; ▪ Automatic information system implementation;

▪ Generation of numerical models of a scenario to the real system, which is the result of the interpretation of the data in the information system using the algebraic model;

▪ The numerical problem solution by means of algorithms specialized according to the format of the

problem; ▪ Storage solution in the information system; and

▪ Consulting and addressing of the model results.

http://www.doanalytics.net/Documents/OPTEX-Presentation.pdf



3

Mathematical models are integrated into a single environment around a single data model of the real system

that is optimized, resulting in a change from the traditional of DSSs development environment linking directly the models to the data model. This represents significant increases in the productivity of the

professionals involved in the projects.

Two processing modules allow OPTEX to function as a comprehensive system that offers the user a range

of possibilities that guarantee efficiency and flexibility in the phase of the process of implementation of a DSS. The table summarizes the two processors that integrate OPTEX.

OPTEX PROCESSING MODULES

OPTEX-GUI - VISUAL USER INTERFACE

Using OPTEX-VUI users access all components of OPTEX and application developed information system; in this way allows: i) formulate mathematical models and all their components; ii) designing and implementing application user interface, and iii) prepare, validate, and check the data for the implementation of the modules related to the solution of mathematical models .

OPTEX-EXE – DATABASE PROCESSOR

Using OPTEX-EXE users access to all components of the information system of OPTEX so solve mathematical problems that have formulated, or generate computer codes required to implement DSS on the platform selected by the user: C, GAMS and OPL IBM,...

2. OPTEX-GUI: VISUAL USER INTERFACE

OPTEX-GUI is a client application that operates in MS-Windows in LANs and WANs environments

communicating with two types of servers: i) Data Server via ODBCs under a client/server scheme; and ii) Mathematical Models Server, whose function is to provide services of solution of mathematical models

making use of computers with large capacity computing and using high performance optimization libraries.

OPTEX-GUI corresponds to the visual interface of OPTEX which complies with multiple functionalities

related to the needs of management of OPTEX, these are: ▪ OPTEX-GUI Administrator: this role allows the design, implementation, use and maintenance of:

o Mathematical models under the principles of the mathematical programming

o Data models of information systems they access the mathematical models o User interface (to access menus and screens of data access) for users of mathematical models

▪ OPTEX-GUI User: this role allows the querying and maintaining tables that are part of the information system of the decision support system developed by OPTEX-GUI Administrator.

This manual is oriented OPTEX Administrator, providing the information required to create the application

interface to the application users.

2.1 ACCESS TO OPTEX-GUI WINDOW

OPTEX-GUI access is controlled by a security system based on the definition of users, keywords, and

access menus. To access the system, the user must know the administratorr user name and the keyword,

which can be changed when appropriate.



4

VENTANA DE DIALOGO PARA LOGIN

2.2 CUSTOMIZING THE LOGIN

To customize the OPTEX-GUI access administrator must configure the GENEX.INI file which corresponds

to a file text that should be located in the BIN directory.

GENEX.INI file structure is as follows (in order of lines):

1. Server type: DBF (for having) or SQL (for type SQL servers) 2. DSN: ODBC Data Source Name (for type SQL Server).

3. Directory location Base data OPTEX-GUI (for applications type DBF). 4. Prefix database OPTEX - GUI (applications for SQL type).

5. User access via ODBC (SQL type for applications) 6. Access Key via ODBC (SQL type for applications)

7. User OPTEX-GUI

8. Position Control, parameter that adjust the position of the table handling windows when viewed in vista type form.

9. Key BMP (EEEE), indicates the file type BMP to be used for the Access window to OPTEX-GUI which is must appoint OPTEX_EEEE.bmp. This file must be produced from MS-PowerPoint, with

rectangular-shaped slide.



5

Alternativamente se puede configurar un archivo de control similar a GENEX.INI con cualquier nombre

nemotécnico y con extensión .ogui, la cual se debe vincular a OPTEX_GraphicsUsersInterface.EXE, para acceder a aplicaciones específicas.

Alternatively, the user can configure a control similar to GENEX.INI file with any mnemonic name and

extension .ogui, which the administrator should link to OPTEX_GraphicsUsersInterface.EXE, for access

to specific applications.

2.3 EXPLORER MENUS

As a result of the process of login, the user will have access to a browser window (Explorer) of the interface

of the application from which the user will have access to four areas of work of the application, which can

be accessed by clicking on the corresponding icon: ▪ Data Model: area in which the data model and the characteristics of the user interface of the

application is configured. ▪ Mathematical Models: area in which mathematical models of application are configured

▪ Information System: area in which are controls access to the tables that store databases that do not

depend on the corresponding to the case study scenarios. ▪ Scenarios Information System: area which controls the access to the tables that store data bases

that depend on the corresponding to the case study scenarios.



6

To configure the menu of application should access to the menu of the Data Model, then to the menu of the User Interface and from there access the table referenced by the Explorer Menus.

The parameterization of the VGENEX access menu involves the definition of options that will appear in the

browser OPTEX.

2.4 MULTI-THREADED

OPTEX-GUI is an application multi-threaded, which allows to have several shell windows open at the same

time, this for the convenience of the user and the compatibility with operating systems and modern screens.

Whenever the user opens a window running (shell window) opens a new process that allowing the simultaneous exploration of multiple-table data windows and multiple areas of the information system.



7

OPTEX-GUI the following container windows are handled:

▪ Data tables: is associated with a table of information system, and can contain multiple data windows.

A data window is linked to a specific information system table. The logic of management is based on a scheme of relationship tables based on a hierarchy established from the main table associated with a

specific table, the majority of cases a master table; from this table the user can explore relationships with other tables, each one of these tables allow exploring new tables and so on. The following image

presents an example of described, in which from the window of the master table of breweries is

accessing multiple data windows associated with tables containing the brewery relations with other entities of the system of information, changing the register in the master table, change all the related

records.



8

BREWING PLANTS

BREWING PLANT PRODUCT

BREWING PLANT HOURS

BREWING PLANT RESOURCEPRODUCT

BREWING PLANT INITIAL CONDITIONS

BREWING PLANT RESOURCE

BREWING PLANT FACTORY

▪ Data Areas: OPTEX allows the user to explore areas of data, a directory, or a TABLESPACE that is linked to an ODBC. The exploration allows access to all the tables of the area under exploration and if

this is the case allows the user to edit any table. The exploration of the results of a model is a special

case, in that the user cannot edit the tables.



9

▪ Navigation Menus: is the means of navigating within OPTEX services; three cases of exploration,

which depend on the area of OPTEX which operation the user must be considered:

o IDIS – Industrial Data: It allows to explore all tables associated with data, input and output, of the mathematical models. It is activated from Information System option:

(i) To access the other windows of the navigation menus; it is the entry point of the user to OPTEX-GUI.

(ii) Exploring the industrial data



10

o MMIS - Mathematical Models: allows the user to explore all the tables associated with the

formulation of mathematical models. Activated from the Mathematical Models option

o IDIS – Data Model: allows the user to explore all the tables associated with the design and

implementation of the model data and the GUI interface of the end user.

For detailed information about the management of OPTEX-GUI is suggested to the reader consult the User's Manual of OPTEX-GUI.

2.5 SERVICES OF OPTEX-GUI



11

The following are services that offers OPTEX-GUI to the Administrator of the Information System

that is the central objective of this manual.

Application data model should be stored in a set of tables that are interpreted by OPTEX-GUI for giving form to the end-user interface. For these services the application manager must access OPTEX-GUI

Administrator area, normally achieved from a button/icon in the navigation menu of OPTEX-GUI to which

the administrator (programmer); have access an example of this type of button below.

The Administrators Area corresponds to an information system of the type OPTEX-GUI specifically

oriented to the Maintenance of the Data Models. Upon entering the area of the administrator, the services are offered through a navigation menu which has the following options:

▪ Data Model

▪ User Interface ▪ Users

▪ Help System

Each of the above options is associated to a group of tables that can be accessed through other navigation

menu. The tables associated with the data model are considered as basic tables from them it is possible to generate automatically a prototype for the user interface that can then be refined by the administrator.

The implementation of the application leads to define structures representing the model of data and

information that are stored in tables specially designed for this purpose. OPTEX-GUI facilitates this process. However, it should be noted, that the process of filling the tables do not have to be with OPTEX-GUI,

since it is possible that there are computational tools that facilitate more this way, at least in the initial

stages of implementation of the application which in many cases are associated with massive load of data.

An effective mechanism to develop the application is to fill the data EXCEL template supplied for this purpose, a word processor-oriented tables in any software in general can be filled or to a processor of

spreadsheets and then import them into final tables using the services of import of data from OPTEX-GUI,

or another utility that provides these services. An example is the load of models via EXCEL (for more information refer to the Manual OPTEX-EXCEL-MMS). Data can also come from in the organization's

existing information systems and import/export of data, must therefore be coordinated, OPTEX offers multiple alternatives to do that.



12

Importantly for the administrator is understanding the process and define the most practical way to

implement a prototype of the data model and from there begin the final adjustment process of the interface to the information system.

MENÚ GENERAL OPTEX-GUI

3. INFORMATION SYSTEMS

OPTEX manages the following information:

▪ Mathematical optimization models ▪ The technical characteristics of the elements of the technical-economic system

▪ The results of mathematical models.

To meet the above requirements, the information system of OPTEX is composed of two subsystems:

▪ MMIS: information system of mathematical models ▪ IDIS: industrial data information system.

This manual presents the information required for the development and administration the IDIS information

systems, that means the information system that will store data input to the mathematical models and the

results of the solution of mathematical problems associated with models, that means, system of information that functional user should consult. Related to the development and administration of the mathematical

models (MMIS) should be consulted in the Administrator's Manual of OPTEX.

The data corresponding to the technical information of the industrial system (IDIS) are classified into two

types: ▪ Permanent data associated to technical information of the system that is independent of any

scenario; and ▪ Non-permanent data associated with the existence of a scenario and representing its variability.

For the above reason the IDIS is composed of two subsystems:

▪ SII permanent industrial information system; and

▪ SIE scenarios information system.

IDIS stores the values of the parameters and the elements of the sets of the models for the different scenarios. The value of a parameter, or the elements of a set may be stored in either of the two previous

subsystems.



13

Both SII and the SIE are information systems that depend on mathematical models. Its design and implementation is done using the easiness provided by OPTEX. There is a direct relation between the IDIS

and MMIS, as indices in MMIS defined entities that should be handled in the IDIS data model, and variable-index, parameter-index and constraint-index relations define the relationships of entities of IDIS.

With regard to the SIE, this should be considered as the union of information systems for each scenario. The structure of each of these information systems is dependent on the scenario and it must set in

accordance with the objectives seeking to comply with the study being done.

3.1 DATA ORGANIZATION

Prior to the loading of the MMIS and, should be into account the way in which information for the integrated

management of all OPTIMIZATION EXPERT SYSTEM should be organized. Under the conception of OPTEX, an information system is composed of multiple databases (group of tables) that are conceived as an

information areas and are classified into: ▪ Control of Information Systems: stores the tables corresponding to a data model of a information

system. It is implemented in DBASE tables and it is part of the MMIS.

▪ Control of Mathematical Models: stores the tables corresponding to the formulation of optimization mathematical models. It is implemented in DBASE tables and it is part of the MMIS

▪ Business/Industrial Data: stores the tables corresponding to the data to which the user of the application has access. This area comprises two areas of data: the permanent data of the application,

and the data of scenarios of the mathematical models. The user chooses the type of database that wants to handle, may be in DBASE tables or tables in a server type SQL. It corresponds to the so-

called IDIS

OPTEX, considers the following areas or data directories:

▪ OPTEX-GUI Control Area: stores the tables of OPTEX-GUI control. It is designed and controlled

by DOA;

▪ OPTEX-MMIS Control Area: stores the MMIS control tables. It is designed and controlled by DOA;

▪ IDIS Control Area: stores the IDIS control tables. This area controls all the areas in which

subdivides the IDIS. It is configured by the OPTEX-GUI administrator;

▪ Mathematical Models (MMIS) Data Area: stores data that define mathematical optimization

models. It must be configured by the administrator/modeler of OPTEX-MMIS;

▪ IDIS Data Area: stores permanent IDIS data, it must be maintained by the IDIS users and is controlled by IDIS Control Area;

▪ Scenarios Family Data Area: stores data that are common to a family of scenarios, it must be maintained by the IDIS users and is controlled by the IDIS Control Area. Data from the family of

scenarios is located from the area (root) scenarios (which is defined in the table of parameterization of applications as described in the Manual OPTEX-GUI Administrator). An area corresponds to

each scenario family.

▪ Scenarios Data Area: stores data specific to a scenario, it must be maintained by IDIS users,

receives data from the solution of models, and is controlled by the IDIS Control Area. In this area OPTEX stored data related to the algebraic and matrix/vectors structures of mathematical models

and several reports. Scenarios data area is located under the directory associated with the family of scenarios. Each scenario has an area. Data from the scenario family is located from the area (root)



14

of scenarios that is defined in the data table in the Manual of the OPTEX-GUI Administrator

application definition. An area corresponds to each scenario family.

There are some tables that are common to all applications and therefore are stored in an application-independent directory, this directory corresponds to the directory "/ BIN /".

The tables can be in different formats. The control tables are handled in DBASE format, since they are OPTEX control tables. The IDIS tables can be stored in DBASE or in any type of SQL Server (DB2,

ORACLE, MySQL, SQL SERVER,...) which can be accessed through ODBCs (Open DataBase Connectivity).

Normally, the DBASE control tables are organized in different directories (it is convenient, not necessary),

the tables in SQL are assumed to be organized in a same TABLESPACE linked to the application through

an ODBC which will be used by OPTEX to manage the existing tables.

The following table shows an example of data areas from an OPTEX application.

AREAS OF INFORMATION SYSTEM

AREA DBF TABLES - DIRECTORY SQL TABLES -PREFIX

Control OPTEX-GUI C:/OPTEX/OPTEX (0)

Control OPTEX-MMIS C:/OPTEX/OPTEX (0)

Control IDIS DATA MODEL C:/OPTEX/aaa/aaaCO (1) (0)

Control Mathematical Modeling Information System (MMIS)

C:/OPTEX/aaa/aaaOP (1) (0)

IDIS C:/OPTEX/aaa/aaaDA (1) (2)

ROOT OF THE FAMILY OF SCENARIOS C:/OPTEX/aaa/aaaES/fff (1) fff_(1)

ESCENARIOS DE LA FAMILIA C:/OPTEX/aaa/aaaES/fff/eee (1) fff_eee_(1)

Nota: (0) DBF tables (1) aaa is associated with the application, fff with the family of scenarios and eee with the scenario (2) SQL tables without prefix

The following image shows the directories associated with the data areas of the OPTEX application. Clarifies

that directories can be arranged in any way, the choice in this case is to place them all in the same directory where the directory name is a mnemonic that acts as a prefix in all directories.

At OPTEX can co-exist multiple applications sharing common data areas. The next screen presents the

definition of the areas of an OPTEX application.



15

3.2 MANAGEMENT OF DBASE (DBF) FILES

OPTEX always uses tables in DBF format. This is because that the areas of control of OPTEX (MMIS) tables are always handled in DBF. In the case of the areas of application data (IDIS), they can be handled

DBF tables or servers type SQL acceded using ODBCs.

It is required to take into account two important aspects in the management of the DBF tables:

• DBT Memo Files: When tables contain MEMO fields, the managers of DBF databases linked a special table to store the MEMOs called XXXXX.DBT, where XXXXX is the name of the table containing fields

MEMOs. It is important that these two tables (the DBF and the DBT) must be handled jointly; when

the DBT table is lost, for any reason, it is possible to lose data stored in DBF table.

• NTX Index Files: to control the order of access of records in a table, and to facilitate relationships

between tables that are linked through common fields, OPTEX uses the NTX index files. There may be multiple files NTX, one for each order (index) that the administrator want to have, for a DBF table.

The following image presents the case of the table CONJUNTO.DBF, the administrator have MEMOs stored in the file CONJUNTO.DBT and whose ordering is set from two points of view:

CONJUNTO.NTX and CONJUNT1.NTX.

It is of special importance, since in the absence of the concept of server in the management of the DBF

tables, it is the application that opens the table the responsible for correctly handle of NTX files, avoiding the corruption/damage them. Therefore, the user must have in its mind that if DBF tables are



16

open for applications different from OPTEX, NTX files can become corrupt losing control of the

application. In this case the administrator must delete all NTX files that are considered are corrupt so OPTEX proceed to regenerate them. In general, it is recommended that if the administrator find an

abnormal behavior in DBF tables, mainly records that are not seen or deleted rows continue seeing, proceed to "delete" the NTX and check if it goes away the problem, in the event that it does not

disappear again to report the problem.

For the reader interested in learning more about the DBase, it is suggested to access the information in

Wikipedia (https://es.wikipedia.org/wiki/DBase).

3.3 MANAGEMENT OF SQL SERVERS

For handling servers type SQL, the user must create the corresponding ODBC and link it to the application.

To do this follow the process indicated in the Manual Network Connectivity.

4. STRUCTURING THE IDIS DATA MODEL

The Data Model menu allows access to the tables that store structures related to the application's data

model.

To define the data model the following concepts must take into account: ▪ Entities/Objects

▪ Fields Prototype ▪ Data Tables

▪ Fields of Data Tables

▪ Indexes Data Tables

It is defined as a data model the set of relations established between the previous components. The data model stored in an information system especially designed for this purpose, and from it OPTEX-GUI

automatically generates a prototype user interface for shell windows and table handling. This is the starting

point for the "customization" of the application by adjusting the prototype to the specific requirements of users.

The data model stored in three main tables that store the basic information of the structure of information

system, these tables are:

▪ CAMRE: FIELD PROTOTYPE definition table ▪ CDBAS: DATA TABLE definition tables

https://es.wikipedia.org/wiki/DBase



17

▪ DDBAS: FIELDS OF THE TABLES definition of tables

4.1 PROTOTYPE FIELDS

The prototype fields are fields with predefined settings that is frequently used in data tables. When the user

defines a field as a prototype, OPTEX-GUI copy its features in the definition of the field in the table that

uses it as "default information".

Three types of fields prototype are considered:

▪ Relational key - C-: relational codes correspond to a field by which special prototype, OPTEX-GUI related data tables associated with an object or entity associated with the field. These codes must be

classified as keys to relationship and associated with a master data table. It is assumed that the user

for each entity or object there is a permanent relational code. To ensure the integrity of the system, whenever the field is used in a table, OPTEX-GUI proposes to validate the existence of the contents

of the field in the master table (integrity of data by reference). Likewise, assumes that the characteristics of the field are similar to those defined for relational code in the dictionary of prototype fields. For ease

of the use of these codes, OPTEX defines a prefix that identifies the key fields relational, example

"COD_".

▪ Simple Prototype - P-: simple prototype field which is used to reduce the work of data capture in the process configuration of the data model.

BROWSE WINDOW PROTOTYPE FIELDS



18

FORM WINDOW PROTOTYPE FIELDS

The user must set the following attributes:

▪ Field Prototype Code: code of the field; up to ten (10) character codes are assumed by default. ▪ Description: description of the contents of the field

▪ Class Field Prototype: corresponds to one of the following options: C Relational key

P Simple prototype

T Field time series ▪ Unit of Measure Code: code of the unit of measure that should be the data corresponding to the

field. This information is used in the automatic generation of windows and reports, and in the generation of titles and axes of graphs.

▪ Master Table Associated: code (name) associated with the master table associated with the field. ▪ Type: field type, which can be one of the following:

C Alphanumeric character

N Numeric D Date

L Logical M Memo - unlimited length text-

O Objects Linked Embebed

For fields of type G, I, S, V and T, the field will be created as an alphanumeric field which is associated with the name of the file that stores the object as a Binary Large Object - BLOB.

Depending on the data server some of these fields are adjusted in accordance with field types that manages the server. For example, ORACLE does not handle Boolean fields.

▪ Length: length of the field.

▪ Decimal: decimal places of the field (for numeric fields) ▪ Relational Reference Code: code of the relational field to be used as a reference to generate the

contents of the Code Field Prototype master tables ▪ Filter: filter to be applied on the master table of Relational Reference Code to select the items in

the master table of the Field Prototype Code ▪ Format: defines the format that is used by default, to capture or display the field information. The

allowed formats are the same type xBASE languages accepted.



19

▪ Text Helps in Status Bar (caption): message of support or explanation that appears in the

"status" of the window line. ▪ Topic Connection to HELP file associated with the field in the system of support of MS-Windows.

The topic is linked when the help command is used by context and the cursor is located on the field in a window.

▪ Help Message: help text that will be displayed when the user requests help on the field of OPTEX-

GUI help system.

The last three attributes are used by the help system from OPTEX-GUI which is described later.

4.2 DATA TABLES

The definition of the tables of data involves two steps:

▪ Logical Definition of the Table: is done by configuration tables in the formats of OPTEX-GUI. From this definition OPTEX interprets on-line of the data model.

▪ Physical Table Creation: occurs when a command creates the table in the data server. In the case of servers SQL, OPTEX-GUI type transfers characteristics table and its fields so that they are controlled

by the server when the user access data from OPTEX-GUI or from any other application.

4.2.1 DATA AREAS

With respect to an OPTEX-GUI application manages two information systems each located in a different

area of data: the Control Area and the Data Area. Tables containing the design of the application are located in the Control area. These tables must be configured by the administrator. In the area of

Industrial Data are those tables that must access the user of the application, the tables of the data model

and the user interface are stored in the Control Area.

Depending on the complexity of the OPTEX-GUI application the user can manage coordinated multiple pairs of areas of data integrated into a single environment from the point of view of the end user. The

following types of areas have been designed to handle the necessary complexity of an application that

integrates, mathematical models and information systems:

▪ OPTEX-GUI Control -G-: It corresponds to the area of control of OPTEX-GUI, this area is of exclusive use of OPTEX-GUI, and should not be altered by the administrator of the application

▪ OPTEX Control -O-: It corresponds to the area of control of OPTEX models, is of exclusive use of

OPTEX and must not be altered by the administrator of the application ▪ Application Control -C-: It corresponds to the area of control of the application and its configuration

is the responsibility of the administrator of the application. This area should not be altered by users of the application.

▪ Models Data -M-: It corresponds to the data area that stores the formulation of mathematical models of optimization that OPTEX handles. It must be configured by the administrator of the mathematical

models (the modeler).

▪ Industrial Data -I-: It corresponds to the area of application permanent data. All tables that are part of the data model. The user accesses the tables through the GUI that manager designing.

▪ Family Data -F-: This area is part of the scenarios information system. The parameters of the models that are defined at the level of a family of scenarios will be stored in this area.

▪ Scenario Data-E-: This area is part of the scenarios information system. All cases of mathematical

modeling results are stored in this area. Parameters of the models are also stored when these are defined at the level of scenarios.

4.2.2 TYPES OF TABLES

OPTEX-GUI handles the following types of tables:



20

▪ Master tables (M): tables in which direct attributes of an object are defined. They have associated a

relational code/key/field. They must be defined before the secondary tables laying the object relationships with other objects. For the validation of the content of the fields associated with the

relational codes are adopted the following rules: o In a master table there must no exist two records with the same content for the associated relational

code (unique key);

o To accept the content of a relational code in a table that is not its master table it should validate the existence of the content in the associated master table (integrity by reference). The previous

rules of integrity can be managing automatically by OPTEX-GUI in a SQL server at the time of creating the physical table, OPTEX-GUI transferred directly to the server the validation rules so

that they are taken into account when other applications access the data. ▪ Secondary table (S): tables that contain relationships and attributes of two or more object relations.

▪ Tables prototype (P): a family of tables, all of them represent the same structure. In this case, the

name of the tables is associated with an object which becomes an attribute of the object to the table. ▪ Time Series tables (T): tables to store data with a common temporal resolution time series. They are

two types of tables: associated temporarily, and associated spatially. OPTEX-GUI-ST module automatically handles this type of table.

▪ Result tables (R): tables results of mathematical models. They do not require the definition of their

fields, since its structure depend on mathematical models.

4.2.3 DEFINICIÓN DE LAS TABLAS

The definition of the tables of data involves determining: ▪ The attributes of the table; and

▪ The fields in the table.

4.2.4 DATA TABLE ATTRIBUTES

Attributes that must be defined to characterize a data table are described below:

TABLE: MASTER TABLE OF DATA (CDBAS)

FIELD CODE DESCRIPTION

COD_DB Data Table Code

DESC_DB Description

DES_DB Spanish Description

DIN_DB English Description

ON_SCR Fast Generation Screen

ON_TRA Data Model Transfer

ON_DM Data Model Included

COD_ICO Icon Code

TIPO_FILE Table Type

PATH_DB Data Area

COD_DBG Code Generator Data Table

DIR_FILE Directory of the File

COD_DSN Data Source (DSN)

CLAVE_DSN Key data source (DSN)

USER_DSN User data (DSN) source

CLAVE_HLP Topic Windows Help

DLES_DB Descriptive Text

DLIN_DB English Descriptive Text

COMENTARIO Comment

COMES_DB Spanish Comments

COMIN_DB English Comments

The attributes of a table are:

▪ Code table of information: code (name) associated with the table.



21

▪ Description: description of the table.

▪ Type: type table M Master

S Secondary P Prototype

T Time Series

▪ Data Area: indicates the location of the data table within the zones managed by OPTEX-GUI. The administrator must assign one of the following values:

G Control OPTEX-GUI C Control Application

O Control OPTEX I Industrial System

M Data Mathematical Models

E Data Scenario F Data Root Family

By default, it is assumed the area I. The last three areas are used by applications that use mathematical models of optimization implemented by OPTEX.

▪ Fast screen generation: indicates when in the automatic generation of structures associated with

the table in the user interface must be generated.

For the purpose of management of space of table on the server SQL type are considered the following additional attributes:

▪ Initial records ▪ Data Area Server SQL

▪ Initial size table (%)

▪ Size Extension (%) ▪ Growth Factor

Attributes that must be defined to characterize a data table are described below:



22

4.2.5 TOOLS DATA MODEL

Associated with the management of data tables OPTEX-GUI offers a set of specialized services which can

be accessed through the mouse right click. The following describes the services offered:

▪ BROWSE TABLE

This service allows the administrator to deploy the table associated with the registry in which the administrator is positioned in the Control Table of Tables. To the extent that the administrator moves in

this table, the subordinate window that displays the table is automatically updated.



23

▪ CREATE TABLE

This service allows the administrator to create physical table associated with the registry in which the

administrator is positioned in the Control table of tables. The table is created in accordance with the structure described in the table of fields of the tables. When the administrator work with a server type SQL

are transferred to the server the validation rules for each field. If the table exists OPTEX-GUI transfers

data to the common field changes the existing table and the logical table defined in OPTEX-GUI. It retains data that exist in the data tables, making adjustments in existing fields, eliminating what is not referenced

and trying to save the content when existing fields change format.

The original table is renamed as XX_tttttt, where tttttt corresponds to the name of the table that the administrator is creating. OPTEX-GUI produces a report summary of the accomplished process.



24

▪ CREATE EXCEL TABLE

This service allows the administrator to create physical table associated with the registry in which the table

is positioned in the Control Table of Tables. The table is created in accordance with the structure described

in the table of fields of tables, includes the field names and descriptions of the same so that the user can fill data. The table created in the area of permanent application data with the name of the data table

extension .XML.



25

▪ IMPORT TABLE EXCEL XML

This service allows the administrator to import the contents of a table in an EXCEL workbook to a SQL

table or a DBF table. The EXCEL workbook must contain a single sheet with the table to be imported and the book must be store in XML format, "Spreadsheet XML 2003". Tables with general EXCEL

formats are not imported for this service.

▪ DELETE TABLE

This service allows to eliminate the physical table associated with the registry in which the table is positioned

in the Control Table of tables. When they are working with a server type SQL the success of this operation depends on the way in which the tables on the server are created.

▪ GENERATE DEPENDENT TABLES

This service allows the user to generate tables dependent on other tables called as table generator

(COD_DBG). The process has two stages: o Generation of master tables

o Generation of secondary tables.



26

Generate Master Dependent Tables option means to divide a master generator table into multiple master tables, one for each relational code derived from the code relational table master generator, based

on the value of a filter condition, established for the derived relational code, which is specified in the Table

of Prototypes Fields (CAMRE).

The generation of Secondary Tables Generated is made taking as reference filter master tables of relational fields generated; Additionally, should take into account the mapping between the generated fields

and the fields in the table generator which is defined in the Table of Fields of Tables (DDBAS).

The process followed can be summarized in:

1. A dependent table is related to generating table, whose code is stored in the COD_DBG field, which contains the original records.

2. The generating table must be declared completely on OPTEX, including their fields in the table of fields

of tables (DDBAS) 3. In the table that will generate is determined the relational fields that change and that should be

generated, this based on the information stored in the master of relational fields (CAMRE) where the reference field and the filter is defined to determine the new entity used in OPTEX.

4. For all fields are copied fields according to the mapping established in the DDBAS table.

▪ PROCESSING TABLES

This service allows the user to implement procedures of specialized calculations related to the information

system, such as filling tables that require of calculating complex processes, copy tables...

When the command is activated, OPTEX-GUI will give control to a "METHOD" that the user must have

developed in Visual Objects. The name of the method must be ZZZ_Procesar_Tablas and must belong to the CLASS Genex_Data_Window. Given the flexibility of Visual Objects, the administrator should

be aware that: ▪ The method to connect to a DLL developed by the user in any programming language

▪ From Visual Objects can execute any SQL statement on a database



27

▪ The administrator can run commands and procedures of operating system

ZZZ is the code given to the application. The following window corresponds to a method built for the SSO application.

▪ IMPORT STRUCTURE TABLE

This service allows the administrator to import the structure of a .DBF table to associate it with the fields

in the table associated with the registry in which the table is positioned in the Control Table of Tables. The structure is stored in the Table of Fields of The Tables so that the modeler must complete the

information required by OPTEX, for effective management of information associated with the table.

▪ GENERATE RTF DOCUMENT

This service allows the administrator to generate a RTF document (Rich Text Format, visible and editable in text editors programs) that corresponds to the structure of mathematical models and related to the

OPTEX application data model.



28

For the generation of the documents RTF (Rich Text Format, visible and editable in text editor’s programs)

check the Administrator’s Manual of the RTF Documents.

▪ CREATE EXCEL-XML TABLES

Create or recreate all physical tables described in the data model of OPTEX-GUI automatically. The tables

are created in EXCEL following an XML format, as indicated previously. OPTEX creates an EXCEL

workbook for each table in the data model.

▪ CREATE BOOK EXCEL-XML

Create or recreate all physical tables described in the data model of OPTEX-GUI automatically. The tables

are created in an EXCEL workbook according to an XML format, as indicated previously, which contains a

table of the data model, which includes a description of the table on each sheet. The book that creates permanent application data area with the name OPTEX_aaa. XML, where aaa is the code given to the

application. After handling, while maintaining the structure of tables, the book should be stored in format "Spreadsheet XML 2003" so OPTEX can process it later.



29

▪ DELETE ALL TABLES

It allows to automatically remove all the physical tables described in the data model of OPTEX-GUI. When

they are working with a server type SQL the success of this operation depends on the way in which the tables on the server are created.

▪ EXPORT TO GEOGRAPHIC INFORMATION SYSTEM

Service temporarily suspended.

▪ TRANSFER AND VALIDATE DATA MODEL

This service allows the administrator to transfer the tables associated with the data model, or a table specified, to a destination area. It is assumed that origin area corresponds to the area of application data.

The user must specify the type of destination area and the information that the administrator want to transfer: structures and/or data. When the destination area (route or path) is on a server of type SQL,

tables are created through SQL statements that include the rules of validation of data that can be transferred to the server.

In addition, the service is oriented to validate the integrity of the data contained in the tables in the data model or to transfer the area of an already existing application data to the data of a new application area.

For example, used in the process of migrating an application developed using type dBASE tables to one that uses a type SQL Server. In the process of transferring OPTEX-GUI sets the order in which the data

transfer should be done to ensure that referential integrity rules are met; the possibility of existence of

circulars validation rules and the integrity of the data that is being transferred are checked. As a result of the process, a report is generated in file TRANSFER. LOG containing the performed process and found

errors.



30

▪ TRANSFER AREA DATA

OPTEX-GUI produces a detailed report of the performed process. This service allows the administrator to transfer tables located in an origin area to a destination area. The user must specify the type of area (DBF

or SQL) among which the transfer is made. In the process of transfer of tables, creating tables in the

destination area are not taking into account integrity rules that may exist in the origin area. Previously, there should be the ODBC to be used to connect to the database.

▪ IMPORT TABLES EXCEL-XML

It allows to automatically import all tables EXCEL XML which are located in the directory of permanent

data area and which are described in the data model of OPTEX-GUI. DBF or SQL tables are created from



31

an EXCEL workbook that is saved in an XML format. The book must be stored in format "Spreadsheet

XML 2003".

▪ IMPORT BOOK EXCEL-XML

It allows to automatically import all tables EXCEL XML which are located like sheets in the book selected,

located according to the convenience of the user, and which are described in the data model of OPTEX-GUI. The book must be stored in format "Spreadsheet XML 2003".

▪ FILE IMPORT TEXT (CSV)

Allows the administrator to automatically import all files text in CSV format which are located in the directory of permanent data area and which are described in the data model of OPTEX-GUI...

▪ CREATE INDEX SQL

Creates the INDEX tables on a SQL Server that is associated with the application, so has as reference the contents of indexes (ordering keys) that are stored in the indexes of OPTEX-GUI Control table.

4.3 FIELDS OF DATA TABLES

The structure of data tables is stored in a table data-dependent of Table the Control Tables.

4.3.1 DEFINITION FIELDS

For each field the administrator must define attributes that are used in the creation of the physical table in the interpretation in line of the data model, automatic generation of prototypes and connection to the

OPTEX-GUI and MS-Windows Help system. This is done from the menu of the window using the

command Open Table Related to accessing the Fields Table of Data Table.



32

The fields that must be defined are:

▪ Field code: code of the field; up to ten (10) characters are assumed by default. This limitation can be change when appropriate.

▪ Description: description of the contents of the field, which is used in the automatic generation of prototypes and the titles of the graphic.

▪ Short description: short description of the field, which is used in the automatic generation of listings

(browsers) in a window and in the headlines of the reports. ▪ Unit code: code of the unit of measure in which are stored the data for the field. This information is

used in the automatic generation of windows and reports, and in the generation of titles and axes of graphs.

▪ Class: kind of field (own OPTEX-GUI), which can be: S Simple or scalar –scalar- : table normal field.

▪ Dimension: when the field class is A (vector or array) defines the dimension of the vector or array.

▪ Type: field type, which can be one of the following: C Alphanumeric Character

N Numeric

D Date L Logical

M Memo (unlimited length text) G Graphic

T Time Series (BLOB)

O OLE: Objects Linked Embebed For fields of type G, I, S, V and T, the field will be created as an alphanumeric field which is associated

with the name of the file that stores the object as a Binary Large Object - BLOB. Depending on the data server some of these fields are adjusted in accordance with field types that manages the server. For

example, ORACLE does not handle Boolean fields. ▪ Length: length of the field. Indicates the number of characters may be used in the field, including

undescor (_), dash (-), dot (.), etc.

▪ Decimal: decimal places of the field (for numeric fields)



33

▪ Capture sequence: order in which the data is located in the process of automatic generation of

windows. ▪ Default value: an expression that defines a value by default for the field in the case of adding a new

record to the table. This expression is executed at the time of setting the field and is updated as it is capturing information in a window.

▪ Type of validation: used to ensure the integrity of the data. The different types of validation

parameters are assigned to the auxiliary fields parameter No 1 and parameter No 2. The following are the types of validation implemented:

A Referential integrity. Validation by the contents of a field in a table. Used in the fields of secondary tables. It is usually the way to validate the existence of a relational code in a master table. It

allows duplicity and empty fields. B Referential integrity and do not allow empty fields.

Y Referential integrity, not allow empty fields and the element can not be in the field of validation

indicated by the parameter 2 which must exist in the table. It corresponds to a validation between fields that contain the same type of item.

X Referential integrity and do not allow duplicity. Z Referential integrity, does not allow duplication or empty fields.

E Referential integrity and requires the existence of all the codes for the master table in the field in

the table being validated. It allows duplicity and empty fields. F Referential integrity and do not allow empty fields and requires the existence of all the codes for

the master table in the field in the table being validated. G Referential integrity and not allow duplicity and requires the existence of all the codes for the

master table in the field in the table being validated. H Referential integrity and do not allow duplication or empty fields and requires the existence of all

the codes for the master table in the field in the table being validated.

D Validation by duplicity of the contents of the field in the table. The following types of validation are oriented to ensure the accuracy of the contents of the fields in the

tables: L The existence in a predefined list. The administrator must define the associated list, separating

the elements with commas (parameter 1).

O Non-existence in a predefined list. The administrator must define the associated list, separating the elements with commas (parameter 1).

R Validates the field is in a predefined range (including boundaries). The administrator must enter the values associated with the range: minimum (parameter 1) and maximum (parameter No 2).

> Is used to ensure values greater or equal to the parameter 1

< Is used to ensure values less or equal to the parameter 1 P Is used to ensure values positive or equal to zero. It applies only to numeric values.

N Is used to ensure values negative or equal to zero. It applies only to numeric values. V Is used to ensure strictly positive values. It applies only to numeric values.

W Is used to ensure strictly negative values. It applies only to numeric values. T Is used to ensure no empty fields. Applies to characters and dates ( / / ).

C Validate the contents of the field by verifying that this corresponds to a field of a data table. There

are two possibilities for this validation (parameter 1): ? Direct addressing: the existence of the camp is verified in a table (parameter No 2) that is specified

directly and that is always the same. OPTEX-GUI validates the existence of the table. I Indirect addressing: the existence of the camp is verified in a table which is defined in the content

of a field (parameter No 2) of the table that is being defined. OPTEX-GUI verifies the existence of

this field. E In this case is used as a validation function a user defined function. The name of the function

(parameter 1) and a parameter (parameter No 2) must be given if applicable. The function coded in Visual Objects and must be linked to OPTEX-GUI through the process of linking (Publisher link).

U Validation by duplication of the contents of a key on the table, but the field does not belong to the primary key of the table.



34

When possible, the previous rules of integrity are transferred directly to the SQL Server.

▪ Parameter no. 1: auxiliary parameter whose content is defined according to the contents of other attributes of the field. It is associated with the validation functions and fields class T (time-series).

▪ Parameter no. 2: auxiliary parameter whose content is defined according to the contents of other attributes of the field. It is associated with the validation functions and fields class T (time-series).

▪ Format: defines the format that is used by default, to capture or display the field information. The

permitted formats are the same type xBASE languages accepted. The following are the types of formats used:

▪ CODE: @! (capital letters, apply for codes stored in uppercase) ▪ DATE: @d

▪ NUMERIC: depends on the length and decimal places set out in the field. For example: length: 3, decimal:1; format: 9.9

▪ Caption: message for help or clarification which appears in window status line when the cursor is

located over a control related to the field. ▪ Linking to Help MS-WINDOWS: topic associated with the field in the system of support of MS-

Windows. The topic is chained when the help command is used by context and the cursor is located on the field in a window.

▪ Help Message: help text that will be displayed when the user requests help on the field of OPTEX-

GUI help system.



35

4.3.2 MANAGEMENT OF MULTIPLE LANGUAGES

OPTEX allows management of tables oriented to be consulted by users who speak different languages.

The user should take into account the codes given to different languages (two-character code) that are stored in the table CIDIO (control language) in the area of OPTEX-GUI control. As presented in the

following table.



36

This table is defined by the user, so that the language code may vary depending on the user. The presented

table shows codes assigned as standard by OPTEX.

As a design rule, to access the OPTEX multilanguage system the name of the fields associated with the relational key and description of an entity in the master table is set as follows:

▪ CODE: COD_eee, where eee corresponds to the entity code

▪ Description: description used by OPTEX to display the description of the entity type on-screen form ("form"). The name/code of the field must be defined as Dii_eee, where ii corresponds to the language

code and eee corresponds to the entity code ▪ SHORT description: short description used by OPTEX to display the description of the entity in display

type table "form". The name/code of the field must be defined as DCii_eee, where ii corresponds to the language code and where eee corresponds to the entity code

▪ LONG description: long description used by OPTEX to deploy the additional information to the

description of the entity in support systems and documents type RTF. The name/code of the field should be defined as DLii_eee, where ii corresponds to the language code and where eee is the code

of the entity. The following table presents a table that allows the administrator to manage the information system

designed by the user in Spanish and English.

OPTEX will select description, having as reference the language specified for the user or the application.

By default, it is assumed Spanish (ES) when no language is specified and/or when the descriptions are not found in the language specified for the user.

4.4 INDEXES DATA TABLE

For effect of the order of accessing the tables, the user must specify index tables that the user wants to operate permanently in the system. These tables speed up the access to the information. It is necessary

to define the index tables for the correct operation of OPTEX.



37

TABLAS ÍNDICES

The definition of the tables indexes implies to specify the following attributes: ▪ Code of the Data Table: code of the data table that is associated with the index table.

▪ Code of the Index Table: index table code. ▪ Key Ordering: contains the ordering key of the table. Where the order involves various fields, the

concatenation of fields must be expressed in the form of sum, or separated by commas.

▪ Data Area: indicates the location of the original data table within the zones managed by OPTEX-GUI. It must correspond to the same area mapped in the master table of data tables. Fill this field is

essential for the proper functioning of OPTEX-GUI.

CONFIGURACIÓN DE TABLAS ÍNDICE

This table is filled automatically by OPTEX-GUI when using the option Generation Structures OPTEX-

GUI. It must take into account what really opens OPTEX is an index table that defines the table and order of the table.

Note: DBF tables each index table corresponds to one file type NTX. These files are automatically

maintained by OPTEX-GUI and OPTEX-EXE; however, it is important to keep in mind that if the DBF table is opened “directly” by the user using OPTEX-GUI, this is:

i) By clicking on the DBF table from MS-Windows Explorer, or



38

ii) By opening the table directly from any option of OPTEX-GUI different to tables connected to

OPTEX-GUI menus or from the related tables option, or iii) By another program,

and makes changes that affect the sorting keys, normally relational keys, they will lose control of the system and it is necessary to delete indexes and let OPTEX, rebuild them automatically, in a move that will require

the DBF table.

4.5 ENTITIES

If the user wants to exchange data with information/computer systems different from OPTEX, it is

necessary a code associated with the entities that the user wants to manage in the system of data exchange. Creating a data source involves defining:

▪ Code: code given to the entity.

4.6 DATA SOURCES NAME (DSN)

Data sources allow OPTEX to exchange data with different types of data which can be accessed via an

Open DataBase Connectivity (ODBC) that corresponds to standard access databases developed by the

SQL Access Group in 1992. An ODBC is associated with a DSN, a short word of English Data Source Name, which allows access to server data (data source) under different formats (EXCEL, text) or types of

SQL servers (Structured Query Language; ORACLE, DB2, SQL Server,...) which corresponds to the declarative structured query language of access to databases.

Creating a data source involves defining: ▪ Code ODBC/DSN: name given to the ODBC that will allow access to the data source.

▪ Description: description of the ODBC/DSN.

▪ IP: IP address of the server. When is local: localhots. ▪ Port/Socket: port of access to the remote server

▪ Type server: server associated with the data source type. Types of server they have access OPTEX, are defined in accordance with the license of the user of OPTEX.

▪ Role server: server role. Role/service provided by the data server. The alternatives are:

o ORS: OPTEX Remote Server o MDX: OLAP server

o SQL: SQL database. ▪ DataBase: database in the SQL server.

▪ User: user who will use OPTEX to access the data source.

▪ Keyword: keyword that OPTEX will be used to access the data source.

For more information on this topic the user is invited to check Network Connectivity Manual.



39

4.7 FOREIGN INFORMATION SYSTEMS

The modeling of data of OPTEX is designed so that it can be easily integrated with other information systems (computing) for which mathematical models supported by OPTEX are a complement.

▪ Foreign Computer System code: this code corresponds to the coding system of the data models

(tables and fields) that allows the user to interconnect to OPTEX with the foreign information system. ▪ Description: description of the foreign coding system.

▪ Type Server: server associated with the data source type. Types of server they have access OPTEX, are defined in accordance with the license of the user of OPTEX.

Associated with conformation systems are codes established for the entities that are part of the information system (example: SAP), or in an application (example: model MS-Project, DIGSILENT). OPTEX allows

conversion of codes maps to identify the entities and the variables that are handled inside the foreign computer application.

OPTEX applications have their own coding system that can coincide totally or partially, or which may not coincide, the coding systems of foreign information systems or foreign applications with which information

is exchanged by OPTEX. To make the exchange of information is required at OPTEX of systems of encoding foreign cases in there is no coincidence.



40

The previous coding systems are incorporated to OPTEX in the master table of the basic entities and in the

master table of variables of OPTEX. To facilitate the integration of multiple information systems, as a design standard, the name of the fields associated with the codes of the foreign coding systems (fff_eee) is

composed based on the integration of the following keys: ▪ fff code assigned to the foreign coding system

▪ eee code of the entity type.

For example, a field that stores codes of generation plants assigned in the "system of commercial

exchanges" (identified with code SIC) is referred to as SIC_CHI, where: SIC corresponds to the code assigned to the coding system of the SIC, and CHI to the code assigned to the entity Hydraulic Pant type.

4.8 FOREIGN DATA TABLES

The definition of the tables of data from foreign information/computer systems involves two steps: ▪ Logical definition of the table: is carried out through the configuration of foreign data tables

which can have names other than those defined in OPTEX. ▪ Physical table creation: is performed when a command that creates the foreign data table is

physically given either directly in a data server or foreign or through exchange of XML data files.

The definition of foreign tables of data involves determining:

▪ The attributes of the table; and ▪ The fields in the table.

The general attributes of a foreign table are:

▪ Foreign computer system code: this code corresponds to the coding system of foreign data model.

▪ Foreign data table code: code (name) associated with the table in the foreign information system. ▪ Description: description of the foreign data table.

▪ Data table OPTEX code: code (name) associated with the table in the information system of OPTEX.

Additionally, the user must set the foreign data table fields. These data are linked to fields-tables on the

model of data in OPTEX.



41

The fields that must be defined are: ▪ Field code: code of the field; by default, are assumed codes up to ten (10) characters. This limitation

can be changed when appropriate.

▪ Description: description of the contents of the field. ▪ OPTEX table code: code to the table that contains the field in the data at OPTEX model.

▪ OPTEX field code: the field code in the model data in OPTEX. ▪ Unit code: code of the unit of measure in which are stored the data for the field.

▪ Type: type of the field in the information/computing foreign system.

▪ Length: length of the field. Indicates the number of characters that may be used in the field, in the information/computing foreign system.

▪ Decimal: decimal places of the field (for numeric fields)

4.9 XML FILES

OPTEX-GUI allows the definition of XML files that can later be chained to optimization processes to be

executed, such as pre and post processes, to import or export data, possibly to other applications.

At OPTEX an XML file consists of three parts:

• Begin of File (Header)

• Data Tables

• End of File (Footer)



42

The definition of XML files implies to specify: ▪ XML code: code in the XML file

▪ Description: description of the contents of the file.

▪ Foreign computer system code: XML files are one of the means to exchange data between applications of different types. This code corresponds to the coding system of tables and fields that

contains / will contain the XML file. When left blank is assumed that the coding system is which is associated with OPTEX.

▪ Type XML: type of organization which will take the texts associated with the tables that will be

included in the XML. S corresponds to the standard scheme that is presented below which allow each record in a table associated with related records from dependent secondary tables of the main table.

▪ Date format: format to be used in the XML file for the associated date fields. ▪ Command: indicates the command that will be executed at the end of the generation of the XML

and will have as first parameter the generated XML file.

▪ Initial file: address of the file whose contents will be incorporated as the initial text of the XML file. ▪ End File: address of the file whose contents will be incorporated as a final text of the XML file.

Subsequently, the data tables that will be included in the XML file should be included in the file. There is

no limit to the number of tables to be included in the XML file. These files are defined a secondary table in such rapid as "XML Files Detail". For each associated table, the user must define:

▪ Order: order in which the table is to be inserted.



43

▪ Data table: table to be inserted in the XML file. It corresponds to the name of the table at OPTEX.

▪ Indicator records: indicates the separator of records that will be used for the table.

If the user wants to associate records from other tables, the user should set the secondary table indicated as "Detail Files XML – Tables Secondary". For each associated table, the user must define:

▪ Secondary data table: secondary table whose records are inserted in the XML file relating them

with the records in the main table. It corresponds to the name of the table at OPTEX. ▪ Indicator records: indicates the separator of records that will be used for the records in the table.

4.10 MEASUREMENTS UNITS

The definition of coding system of the measurements units of the variables, parameters and constraints is part of the design of an application, since it depends on the structuring of the selection processes of the

magnitudes of the variables, the processes of conversion in data loading and operating procedures. Below is an example of the table of measurements.



44

4.11 GENERATING OPTEX-GUI STRUCTURES

Through this service, it is possible to automatically generate a prototype for the application's user interface, it is accessed through the Tools of the Menu Browser of the Data Model.



45

The process implies that it is automatically fill the tables of the user interface from the data specified in the tables in the data model. Specifically, generated structures to the data windows, the links of data windows

and indexes tables that control the presentation of tables. OPTEX-GUI generates a report with the information for which structures have been generated, which are selected according to the contents of the

field associated with the automatic generation in the table of Control Tables. OPTEX-GUI produces a report

of the carried out process:

4.12 DATABASE INTEGRITY

Corresponds to a procedure that checks the integrity, and if possible the "veracity" of the database. The

procedure is defined as a tool in the table of definition tables of data on OPTEX model. For detailed information, is suggested reading the Administrator´s Manual of the Validation Data.

5. USER INTERFACE

The user interface refers to the different services and possibilities that are offered to the user when the

user access the application. OPTEX-GUI uses the following concepts for the interface:

▪ Navigation Menus ▪ External Programs (procedures or external programs)

▪ Data/Basic Windows ▪ Detail Data Windows (fields in the windows)

▪ Shell Windows Linking

▪ Detail of Shell Windows Links ▪ Groups of tools

Then the previous concepts and how to define are presented.



46

5.1 NAVIGATION MENUS

Navigation menus are the way of the link all the processes involved in an application and guide users

through it. It is possible to define an unlimited number of menus. A hierarchical structure in the navigation

menu settings allows users access through a specific menu control. OPTEX-GUI displays the menus in host window. To select an option, the user has two alternatives:

▪ Positioning itself on the option using the cursor keys and pressing the ENTER key. ▪ Clicking the mouse on the desired option.

The host window has its own menu of commands and its toolbar that allows the user to access other

services different of the explorer.

It must be specified in the definition of the general characteristics:

▪ Code: code of the menu ▪ Description: description of the menu that appears on the selection button when a menu connects with

another menu. This description also serves as topic of connection with the help system in hypertext

under MS-Windows, when this is set

The definition of navigation/explorer menu options or components are made from the menu of the window using the command open related table and it implies to specify the following attributes for each element:

▪ Order: order in which the option should appear in the window of the navigation menu. ▪ Program type: type of event associated with the component. The following possibilities exist:

- OPTEX Results via EXCEL



47

# Events Control Window

* Time Series Control Window > Explorer OPTEX Results

A Window display relationships B Load Databases

C Connectivity to Explorer Menu OPTEX-GUI

D Data Processing E Scenario Menu

F Family of Scenarios Menu G Report EXCEL

H Load data from Text Files I Capture files via FTP

J Master Tables Visualization Menu

K Master display window L Load Tome Series Window

M Explorer Menu N OPTEX-GUI Application

O Connectivity to Explorer Menu OPTEX-MMS

P Visual Objects Procedure Q Connection Object OLE

R External Executable Program S Shell Windows Data Tables

T OPTEX-MMS Application V Shell Windows View Tables

W Host Window Area OPTEX

X Shell Window Family of Scenarios Y Shell Window Scenarios

Z Generation Events Time Series

▪ Procedure code: code of the menu, window or special process.

The following table shows examples of connectivity obtained with each type of program.

CODE ACTION

-

Results OPTEX via EXCEL

#



48

CODE ACTION Control Event Window

*

Window control times series

>

Browser OPTEX Results

A

Window Display Relationships

B

Load Databases

C

Connectivity to host Menu OPTEX-GUI

D

Data Processing



49

CODE ACTION

E

Scenario Menu

F

Family of Scenarios Menu

G

EXCEL report

H

Load Data from Text Files

I

Capture Files via FTP

J

Master Display Menu



50

CODE ACTION

K

Display Master Window

L

Manual Load Time Series

M

Navigation/Explorer Menu

N

OPTEX-GUI Application

O

Connectivity to host menu OPTEX-MMS

P

Visual Objects procedure



51

CODE ACTION Q

Connection OLE Object

R

External Executable Program

S

Shell Window of Data Table Windows

T

OPTEX-MMS application

V

Shell Window of Data View Windows

W

Host Window Area OPTEX

W

OPTEX Area Window

X

Family of Scenarios Host Window



52

CODE ACTION Y

Scenarios Host Window

Z

Event Generation Time Series

5.2 DOCUMENT WINDOWS

5.2.1 GENERAL CONCEPTUALIZATION

The user can consult documents through a host window that allows to access multiple documents through

secondary windows associated with documents. The types of documents handled by OPTEX-GUI are: ▪ Data tables

▪ Graphics ▪ Images

▪ Time Series

▪ File text

The host window is normally associated with a data table which acts as a master table of the query. From the window associated with the main table the user can interact with the records from multiple tables and

perform processes of queries and maintenance of that table and/or other tables and/or documents

associated with the registry. Secondary windows allow access to new windows associated with related tables. In this way is set a primary-subordinated relationship between the tables, in which a subordinate

window can act as primary window of other windows. OPTEX-GUI controls the access to records in a subordinate window so that they are visible only those which are related to the record that is display in the

primary window. In the prototype interface, OPTEX-GUI automatically determines the relationships between the tables in different windows.

The linking of windows is done through two mechanisms: ▪ Through a link for windows user-defined type data tables. Subsequently is presented in greater detail

the process to follow for this type of linking. ▪ Through the association specified in the fields of the tables for type records: graphics, image, sound

and video.

▪ Through links to the systems of management of series of data, events and geographic information.

5.2.2 DATA WINDOWS

A window type data table consists of two parts: static and dynamic. The static part corresponds to the

environment that remains constant throughout the process of capture or display of the information. The dynamic part corresponds to the positions in which the user capture / displays information pertaining to the

contents of a variable of the window that can come from the contents of a field of a record in a table or calculated variables.

From the contents of the tables that define the data model, OPTEX-GUI automatically generates prototype

windows for all tables. Alternatively, the user can edit prototype windows for "custom" windows when the

demands require them. To customize the windows, the user must set: ▪ The general attributes of the window

▪ Dynamic fields



53

OPTEX-GUI allows the handling of data windows in a scheme record to record (form) or a display of all

records of the table as a list (browse). When the window is in form mode, the system and help of OPTEX-GUI can be activate it by double clicking on the description of the fields.

▪ GENERAL ATTRIBUTES

The following are general attributes for a basic/data window ▪ Code: code assigned to the table window.

▪ Description: description of the window that is used in the menus where it is called and in the header of the window – caption-. This description also serves as a topical connection under MS-Windows

hypertext help system. ▪ Data Table: table associated with the window. In case that it is associated with a prototype table will

allow access to all tables of the family; the physical data table is selected at the time of access to the

window.

ATRIBUTOS GENERALES DE UNA VENTANA BÁSICA

▪ DYNAMIC FIELDS

The definition of dynamic fields is done from the menu of the window using the command Open Related

Table accessing the table Fields Dynamic Window. Dynamic fields have the following attributes: ▪ Code: code of the dynamic field.

▪ Sequence: corresponds to the order in which should appear the field when the window is displayed. ▪ Dynamic field type: indicates the field type, it can be:

F Field in the table of data whose content can be created or modified by the user;

D Field in the table of data that only it is possible to visualize and whose content cannot change the user;

G Field does not belong to the table of data that must be supplied by the user. C Field does not belong to the data table that is evaluated based on a defined expression

▪ Expression: expression for calculated variables. ▪ Format: format for capture/deployment of the variable. Required for variable type G and C. For type

F and D by default is used in format defined in the declaration of the field in the Fields Tables for

the Data Tables.



54

5.2.3 HOST/SHELL WINDOWS (DATA WINDOWS LINKING)

To access a group of documents the user makes it through a host window (shell window). Host windows

are associated with links of data windows, so that the table associated with the first window defined

operates as a main table of the host window.

The link of windows relates the tables through the commons fields. In the prototype interface OPTEX-GUI select relationships based on common relational codes (keys) between two tables. There are no limits to

the number of levels of linking. The following attributes must be defined for a host window: ▪ Code of the host window: code or name assigned to the link.

▪ Description: description of the window, is used in the navigation menus from where access to the

window. This description also serves as topic of connection with the help system in hypertext under MS-Windows, when it is implemented.

▪ Group of tools: special tools group that are being linked to the window in the group tools via the context menu (right click) of the window associated with the table.

▪ Expression filter: corresponds to a filter of information which will be impose to the table associated

with the first table in the host window. The expression must be specified according to the data server that handles the table. If applicable to the type SQL Server expression must comply with this kind of

language, if it corresponds to a dBASE type table must be specified in terms XBase.

To define the data windows linked to the host window of tables windows proceeds from the menu of the window using the command Open Related Table. The user must set the following attributes:

▪ Order: corresponds to a number that indicates the hierarchical level of the screen. The screen basic

window of lower order determines the main table of the host window. ▪ Data Window: code of the subordinate table window. It must correspond to one of the defined data

windows codes. ▪ Index table: index table that will handle the order of presentation of the data in the table associated

with the subordinate window.

▪ Relation key: expression of relation between the tables associated with the windows. It contains common fields between tables associated with windows. For unrelated tables this expression will be

null. When considering several fields of relation, they must unite as a sum or with commas.



55

5.3 EXTERNAL PROGRAMS

OPTEX-GUI allows to link together special programs associated with specific purpose procedures. These

processes can be programmed in Visual Objects or any other computing platform. For each special process

the user must define: ▪ Code: corresponds to the special procedure code. When it is associated with a program in Visual

Objects this code determines the name of the function that will be executed when the user select the button associated with the process in a navigation menu. In this case the procedure should be linked

as type P (procedure Visual Objects).

▪ Description: this expression will be used by OPTEX-GUI to indicate the option in the navigation menu to which the process is linked. This description also serves as a topical connection under MS-Windows

hypertext help system. ▪ Command (path): to processes implemented on a platform other than Visual Objects the user must

specify the command to run to activate the process when the user select the option in a navigation menu. In this case the procedure should be chained as type R (external executable). The administrator

is responsible for ensuring access to the route when the user selects the option.



56

6. APPLICATION CONTROL

Control of applications and user’s menu allows the administrator of OPTEX-GUI and of the application define the following aspects:

▪ Users ▪ User groups

▪ Groups of tables of data

Three levels are considered to access to a table:

▪ Level 1: reading and writing (W), allows the user to query and modify the table. ▪ Level 2: only reading (R), allows the user to consult the table.

▪ Level 3: does not allow access to the table (N).

The tables are organized into groups of tables and users are assigned to groups of users for which the level

of access for each group of tables is defined. OPTEX-GUI controls permanently the access rights for users in such a way to protect the information in accordance with the rules of the business.

MENÚ CONTROL APLICACIÓN Y USUARIOS



57

6.1 USERS

Users of the application must be defined in the Control Table of Users. A user is defined as a user of OPTEX-GUI and therefore can access all applications that are controlled via OPTEX-GUI. At the level of details

access of the user are defined the applications that the user has access and access menu in the application.

For a user it must be defined:

▪ User code: code assigned to the user. The administrator controls this code and cannot be changed by the user.

▪ Keyword: keyword of the user. The administrator assigns the keyword initially but it can be changed by the user when it deems appropriate.

▪ Names: the user names

▪ Last name: last name of the user

In addition to the above information the administrator must set user access rights, which implies to determine, this process is accessed from the menu of the window using the command Open Related

Table :

▪ Application Code: the application code to which the user has access. When a user has access to multiple applications, OPTEX-GUI will generate automatically a host application window from which

the user may simultaneously access to all applications that have the right of access. ▪ Menu Access Code: code of the menu of the user access to the application. It must correspond to

one of the navigation menus defined in Navigation Menus Control Table. When access to the system, OPTEX-GUI will put at the disposal of the user this Menu from which the user can browse and

access the different options according to the structure that is generated from the access menu.

DEFINICIÓN USUARIOS

6.2 USER GROUPS



58

To easily manage the security of an application, the administrator must set user groups in which the users

are classified. The rights of access to the system tables are made by means of the classification of the tables in groups of tables and in the allocation of rights of user groups to the groups of tables.

The definition of a group of users implies the determination of the following attributes:

▪ Code: code of the user group

▪ Description: description of the user group

From the window menu using the Open Related Table command is accessible to users in the group settings and the assignment of rights of access for different groups of tables.

6.3 GROUPS OF TABLES

For the purposes of the security system the tables can be classified into groups for subsequently give access rights to the group of tables to different groups of users of the information system. For each group of tables,

the administrator must set the following attributes: ▪ Code: code of the Group of tables

▪ Description: description of the Group of tables.

For each group of tables, the tables that make up the Group of Tables must be defined. This is done from

the menu of the window using the command Open Related Table to accessing the table Detail Group Data Tables.



59

Additionally, the user must set the relations between groups of tables and user groups. This process is done from the menu of the window using the command Open Related Table to accessing the table Detail

Group Users - Group Tables and implies to define: ▪ Tables group code

▪ User group code

▪ Access level: indicates the level of access of user group to the Group of tables. It can be: R Read

W Read / Write N Do not Access



60

APPENDIX A

RESERVED WORDS

The following words cannot be used in OPTEX-GUI as names/codes of data-tables, fields OR index-tables.

ADD ALL ALTER ANALYZE AND AS ASC ASENSITIVE BEFORE BETWEEN BIGINT BINARY BLOB BOTH BY CALL CASCADE CASE CHANGE CHAR CHARACTER CHECK COLLATE COLUMN CONDITION CONSTRAINT CONTINUE CONVERT CREATE CROSS CURRENT_DATE CURRENT_TIME CURRENT_TIMESTAMP CURRENT_USER CURSOR DATABASE DATABASES DAY_HOUR DAY_MICROSECOND DAY_MINUTE DAY_SECOND DEC DECIMAL DECLARE DEFAULT DELAYED DELETE DESC DESCRIBE DETERMINISTIC DISTINCT DISTINCTROW DIV DOUBLE DROP DUAL

EACH EACH ELSE ELSEIF ENCLOSED ESCAPED EXISTS EXIT EXPLAIN FALSE FETCH FLOAT FLOAT4 FLOAT8 FOR FORCE FOREIGN FROM FULLTEXT GRANT GROUP HAVING HIGH_PRIORITY HOUR_MICROSECOND HOUR_MINUTE HOUR_SECOND IF IGNORE IN INDEX INFILE INNER INOUT INSENSITIVE INSERT INT INT1 INT2 INT3 INT4 INT8 INTEGER INTERVAL INTO IS ITERATE JOIN KEY KEYS KILL LEADING LEAVE LEFT LIKE LIMIT LINES

LOAD LOCALTIME LOCALTIMESTAMP LOCK LONG LONGBLOB LONGTEXT LOOP LOW_PRIORITY MATCH MEDIUMBLOB MEDIUMINT MEDIUMTEXT MIDDLEINT MINUTE_MICROSECOND MINUTE_SECOND MOD MODIFIES MODIFIES NATURAL NO_WRITE_TO_BINLOG NOT NULL NUMERIC ON OPTIMIZE OPTION OPTIONALLY OR ORDER OUT OUTER OUTFILE PRECISION PRIMARY PROCEDURE PURGE READ READS REAL REFERENCES REGEXP RELEASE RENAME REPEAT REPLACE REQUIRE RESTRICT RETURN REVOKE RIGHT RLIKE SCHEMA SCHEMAS SECOND_MICROSECOND SELECT

SENSITIVE SEPARATOR SET SHOW SMALLINT SONAME SPATIAL SPECIFIC SQL SQL_BIG_RESULT SQL_CALC_FOUND_ROWS SQL_SMALL_RESULT SQLEXCEPTION SQLSTATE SQLWARNING SSL STARTING STRAIGHT_JOIN TABLE TERMINATED THEN TINYBLOB TINYINT TINYTEXT TO TRAILING TRIGGER TRUE UNDO UNION UNIQUE UNLOCK UNSIGNED UPDATE USAGE USE USING UTC_DATE UTC_TIME UTC_TIMESTAMP VALUES VARBINARY VARCHAR VARCHARACTER VARYING WHEN WHERE WHILE WITH WRITE XOR YEAR_MONTH ZEROFILL