Sipal
Information System to Assist Aquaculture
Planning in Latin America and the Caribbean Reference Manual

Aquila II Project staff

Project Publications

Field Documents :

Memorias del III Curso Básico Regional de Capacitación en Planificación y Gerencia en Acuicultura (Caracas, 5/10–20/11/1992)

Reports on the Project's Activities:

1. Marzo – agosto de 1992

2. Septiembre '92 – febrero '93

3. Marzo – agosto de 1993

4. Septiembre '93 – marzo '94
   [includes: Informe de la l Mesa Redonda Regional sobre el SIPAL (México, D.F., 14 a l6 de marzo de 1994)]

Informe Final - Resultados y Recomendaciones del Proyecto

1. INTRODUCTION

This document, the second of the series dedicated to Sipal, gathers all the system information needed by a qualified user — e.g. the national Sipal Coordinator in the various countries — in order to configure the Sipal National Center according to the needs, requirements, and particular national specifications.

To this end, in the following pages the documentation typical of a Reference Manual is presented, structured in such a way as to give easy access to consultation for the installation and start-up phase as well as for the subsequent maintenance and reviewing activities. Moreover, for consistency concern, the technical documentation to support the maintenance and the system design has been concentrate in a single volume. The information contained in this document consists of the technical specifications (general and detailed) necessary to enable the user to respond quickly to the dynamic changes that such a system requires. In particular, it was considered important that Sipal be supported by appropriate documentation, considering the strategic function that the system design plays in the life cycle of an information system (Figure 1).

Figure 1. Life Cycle of The System Development

ALSO, the didactic significance or this manual needs to be emphasized. This is an aspect that has been constantly taken into account when developing the system. In the preparation of the manual, some repetitions have occurred which were intentionally maintained for the sake of clarity and easy understanding.

Finally, the importance of the regional standardization of the aquaculture industry technical terminology generated and applied during the development of Sipal should be acknowledged. A large part of the manual is dedicated to this by including the whole codification system, regionally agreed upon, and the methodology developed and followed by the Sipal development team and the national coordinators in designing (definition, structure, functions etc…) all the databases which compose the system.

2. GENERAL DESCRIPTION OF SIPAL

2.1. An Outline of The System

Sipal can be defined as an instrument designed to allow, within pre-established subsystems, the management of data and information of different kind (though always relevant to the aquaculture sector) retrieved and assembled from various national, regional and international sources. Its objective is to assist in aquaculture planning.

It must be emphasized that the system has been developed with the direct contribution of the national teams of Chile, Colombia, Cuba, Mexico and Trinidad & Tobago. This involvement has produced, among other things, a transfer of technology from FAO to all the participants and has generated a flow of information and familiarization at the regional level.

In order to rationalize Sipal development and implementation, to enhance its possibility of success, and to increase its use and interest by all the concerned parties, the system will be composed of five main and two accessory modules, i.e.:

The National Module, will provide Sipal with direct access to national databases. However, this latter option will be available only in those countries where a national information system exists and the national coordination staff is able to develop the appropriate communication protocols. Alternatively, this module will contain the same software as the Regional Module but will manage data at a lower level of aggregation and have all the typical functions of data entry. This option is at any rate reserved for the country's own use and management

The Regional Module is a corporate system which summarizes the information supplied by countries according to a given methodology. It is a collection of all the selected databases, customized to allow the typical retrieval functions: Select, Search, Print, Save, Export, Configure.

Both the National module and the Regional Module contain the following databases:

• Production Statistics.
• Import Statistics.
• Export Statistics
• Pathology.
• Farming Technology.
• Directory of Importers.
• Directory of Exporters.
• Directory of Suppliers.
• Directory of Projects.
• Directory of Production Centers.
• Directory of Legislation.
• Directory of National Experts.
• Bibliography.

The FAO Module will contain some of the officially published software and data bases obtainable from FAO HQs and relevant to Sipal. Most of them are part of the FAO Computerized Information Series.

The Extended Module will contain an abstract prepared by Sipal of information collected through the linkage with worldwide commercial and non-commercial networks. As far as networking with remote sources is concerned, Sipal will contract access and authorization to redistribute data.

The Analytical Module will contain various programs for the analysis of the data/information processed through Sipal and gathered from other sources specifically obtained or developed to assist in the technical and financial management of aquaculture production projects. In particular, this module contains the software package APS (Aquaculture Planning Simulator) specifically developed for the technical and financial analysis of aquaculture projects, through a dynamic matching with existing real data from similar projects in similar areas.

The Data Processing Module will enable the user to process and critically analyze the in-formation retrieved through Sipal. In fact, one of the characteristics of the system is that it will not be dependent upon pre-determined models. This Module will therefore contain all the commercial software which the user might need for carrying out analytical studies (word processor, spreadsheet, DBMS, project management tool, graphics, statistical package, etc…). Sipal will allow all the users to establish their own personalized research procedures tailored each time to suit their requirements ac-cording to their decision-making process.

The System Configuration Module will assist in configuring Sipal according to the different hardware/software platforms where it is installed.

Sipal end users are classified by group according to their position and fields of interest The primary end user is the staff of the fisheries and aquaculture services in the various national offices in the Region, who will be using Sipal mainly for reporting and planning purposes, but it will also be able to answer queries from the private sector. This group is also the most important one for data supply. Among a second group of end users are aquaculturists, economists, fishery specialists, traders and investors in the industry, trade and educational institutions, in both the public and private sectors. Each Sipal national management unit will organize its own national end user group.

The end users will be called upon to actively contribute not only to the common user activities but also and most significantly to propose new applications as well as modifications to existing ones through the national coordinator. Such initiatives may materialize by submitting to Sipal a detailed report containing:

• description and objectives;
• identification of interested users;
• data manipulation required;
• output format;
• possible sources of data;
• data entry format;
• data retrieval format;
• suggestions and limitations.

It should be highlighted that all countries adhering to Sipal, regardless of whether they are data suppliers or just information recipients, will be provided with the same tool.

Sipal has been developed by in compliance with a few basic criteria:

• avoid burdening participating countries with a demand for additional data collection activities to be carried out specifically for Sipal

• loading the system only with national data/information which exist and are obtainable in the majority of the countries, which are of regional interest and which are not considered confidential;

• ensuring that all data/information feeding the system be specifically and officially authorized as appropriate.

In order to facilitate the exchange of data within and between countries, the Regional Module, in addition to the automatic data transfer from national data banks to Sipal, will provide the data entry and management procedures for each of the application databases. These databases will be structured according to a standardized regional format. For each database, the characteristics, definition, units, directories, etc…, will be documented.

2.2. How Sipal Works

This system is designed as an integrated information system, i.e. a homogeneous system of which the end-user is not aware that it is built of different basic elements. It is important to note that in designing this system the end-user and his needs, and not the wish to produce one more instrument of data dissemination without a pre-established target, are the main considerations.

The system has been developed, both at the Center and at the periphery with the same hardware/system software in order to optimize productivity and ensure network compatibility.

The system architecture has been designed on a “star” pattern a with non-rigid connection where the center of the star represents the manager/server and the points represent the users.

The System has two operational levels, one at the center and one at the periphery. For an easier understanding of the above pattern a chart follows (Figure 3). In this particular case the system is developed around a network in which the center of the star is represented by the Aquila project head-quarters where the System Manager/Server pilots all the applications at the regional level. At the edges of this star are the countries and other end-users in the Region. The Network is complete with two more connections, one representing the link to the FAO Fisheries Department Sipal back-stopping team as Data/Information Supplier/Receiver, and a second one to an ideal node to connect remote databases and Networks.

The development of the software is strongly influenced by the structural design of this network (star) which has been conceived to allow the integrated system to be developed in a modular way independently from the two levels of implementation. To make full use of the above structure a slightly unconventional approach has been chosen in the development of the system. The first level network which covers the project headquarters, FAO-HQ and the remote centers applies a so-called “top-down” strategy. This strategy is typical of a vertical initiative in which, without taking too much account of the final characteristics of the user, the application is developed and imposed. For the application of this strategy the initial components (FAO databases and other software with their “known” specifications and environments) of the system are known beforehand. The FAO information module will be developed and implemented using this strategy and will be distributed by the project headquarters to the end-user centers.

The national centers will manage the flow of the data between the various national sources of data and themselves and will be responsible for the interfacing procedures (installation, training, setting-up, etc…) to the Regional Module. This Module, to be developed at the Sipal Headquarters (regional information module), will have the dual task of interacting with the project headquarters and with the country. Since this module is strongly dependent on the various national contexts, a “bottom-up” strategy is applied. For this, a methodology which permits the identification of many simple problems and their solution independently is used. This module will therefore be developed by consolidating and expanding the system, both in dimension and application, as new blocks are added from the bottom upwards. This is a strategy where the analyst does not need to know initially all the situations he will be faced with (different national contexts).

One of the most interesting features of this program of work at the cooperation level is the direct involvement of national personnel and the end-users in the development and system enhancement of the Interfacing Modules. This approach (to use national staff) is considered a basic condition for the success of the program of work during and after project implementation.

Because of its modular structure, Sipal allows the users to establish their own research and interrogation process, tailored each time to fulfill their own needs and according to a pre-established decision making process.

The developed software was limited to that for the management of the FAO and regional information modules and the input/output protocols for uploading/downloading FAO and regional databases, maintenance systems and the interfaces with the various and different national systems. Towards the end of the project procedures for tele-maintenance and tele-updating via modem through a “carbon copy” approach, both from Rome FAO-HQ and from the project headquarters, should be in place. This approach will allow the System Manager to temporarily control the remote work station through a modem and special software.

The processing function of the system, as well as the word processing, statistical analysis, graphics, project management, etc., will be carried out in one area of the system (Data Processing Module) which will make use of commercial software possibly standard within the FAO family. This Module may also contain programs and procedures developed by the project to allow standardized and repetitive data processing, report generation, etc. The commercial software may be integrated with built-in macro instructions to perform certain operations.

The analytical and modeling area is to be covered by specific software to be developed once Sipal is in an advanced phase for modeling type of investments, simulating intervention, assisting in formulating and evaluating aquaculture projects. At the moment of printing this manual, APS is being tested and finalized.

The data/information flow will be constructed around a “star-like” organization of the National Centers set up according to the following channels:

Import/Export Data will also follow a pre-established time pattern. Data should be captured, compiled, normalized and distributed for three different time schedules:

1. Yearly/monthly, for static and little dynamic data;

2. Weekly/daily, for dynamic data;

3. Occasionally, for permanent data (Reference Files), occasional data, etc.…

and constitute three different uploading/downloading procedures. Data uploading and downloading must be done according to type, frequency and use of the information, regardless of whether it is aquaculture data, fishery data or complementary data.

The architecture of the whole system was based on dedicated software developed using a commercial package specialized for such application. “Menu Works® Advanced 2.12¹”. Through this software the end-user interface was developed which also included all the typical Disk management functions. Through the menu the user, totally driven and assisted, can access any part of the system for consultation, selection, output or exporting of information. Also he can construct a document by extracting and depositing several search results, and therefore by using a word processor or any other available package associated to Sipal (always from the Sipal menu) put his work in final format In Figure 2, a chart indicates the search and processing technique foreseen in Sipal.

Schematically speaking, the system is based on the following path:

1. Access to the required database though a menu option.

2. Consult and search in the database using an internal menu.

3. Visualize, printout of the results or creation of several export files containing the retrieved information in a given format

4. Access to a processing or analytical software though Sipal Menu appropriately customized.

5. Data management of all export files created during the search process (point 3). The data management may be carried out using one or more software packages as required.

6. Creation of a final document file which can be printed, or even electronically distributed via modem.

Figure 2. Sipal Search and Processing Technique

This process can be repeated several time, accessing different databases within Sipal. From the user point of view, he will navigate through the various modules of Sipal, always guided by the user interface Menu.

The export files as well as the final product of the search process are automatically saved in a given directory (D:\SIPBANK). The commercial and analytical software associated to Sipal have been customized to read/write from the same directory using given formats. For those centers that can access remote databases, the process of accessing, selecting and processing retrieved data is the same. They will access remote databases through the Sipal menu appropriately configured and therefore will aggregate data/information collected remotely with those collected locally for further processing.

An example of the use of Sipal could be the production of a report or bulletin of aquaculture production statistics. Through the Menu select “Statistical Database” then in sequence select “Production Statistics”. The user is now in the database Production Statistics with all the typical database management functions activated (Data entry, Search, Print, Export, etc…). Once the search selection is made, the software will save the results in a file deposited in D:\SIPBANK. Afterwards using an Electronic sheet software or advanced word processor, the data can be rearranged, and some text added. Also a graphical presentation can be added to the extracted data. The user can use the same method to access other databases included legislation and bibliographic, and add more information to the open document.

¹ Registered trade mark of PC Dynamics, Inc.

3. DEVELOPMENT PROCESS

3.1. General Criteria

The design and subsequent development of Sipal was the output of a joint effort of the various components that interacted at different moments of the operative phases. Basically there are three essential aspects that need some attention: in the first instance, the need to structure the system in such a way as to satisfactorily respond to the requirements identified for the future beneficiaries in terms of information related to aquaculture; in the second instance the wish to create a modular information system which may easily be adapted to local conditions of participating countries and to be modified, subsequent expanded or even reduced according to objective situations and the interaction with other similar systems.

All the applications were designed by a team composed of the Sipal System Management (Aquila II - FAO/Fisheries Dept.), National Aquila Coordinators from member countries, national researchers from both member and non-member countries. In the future, for any further development the above group must be integrated with selected representatives from the Public Sector, selected representatives of producers and suppliers, as well as any other qualified end-users.

According to the conceptual design any future application must be decided collectively by this group of experts, coordinated by the Sipal Data Manager. The data definition and the data flow, form in which the data are to be produced and submitted, their frequency of production, and how they are to be processed and analyzed needs to be discussed and agreed to at interest group level.

Once an application is identified, the design unit will prepare in detail the application specifications as a project format which should contain inter alia:

• Description and objective: Stating why that item was considered to be of particular interest

• Variables to be considered: Type of data, units, collection method, reporting frequency.

• Source of Data: Identify secure and accessory sources of data.

• Users of Particular Interest: List all expected interested end users, and try to have their involvement in the data and functions definition exercise.

• Data Entry Format: Design by hand(or computer assisted) the data entry forms including instructions, notations, keywords, reference codes etc.

• Data Manipulation: List all the manipulation and treatment foreseen to achieve the proposed results.

• Data Retrieval Functions: List all possible and interesting retrieval functions that the software must allow.

• Data Output Format: Design by hand (or computer assisted) the layout that the output format must have to present the results.

• Suggestions: List any suggestions that may be of use to developers.

• Constraints: The developers should inform the end-users of any constraints that may exist and help on how to bypass the problem whenever possible.

During the period of the development, the analysis of the data and the functions were carried out as well as analysis of the information, structure, contents of the archives and their management Also data/information models and their integration were deeply analyzed with all the parties concerned. This was possible only thanks to the capillary action and die presence of Aquila II Project in the Region. Because of this presence it was possible to organize meetings and seminars where all the various phases of the Sipal Development were presented, discussed and therefore accepted. From this interaction the reaction of the regional entities to the FAO request emphasized the urgent and primarily necessity to include three families of databases in the system: (i) Statistical databases; (ii) Directories; and (iii) Databases covering technological aspects.

Moreover, the importance of having in the System selective software (commercial or not) for processing and analyses the obtained results was highlighted. It should be emphasized that the flexibility of the system was decided not only to foresee future development needs and aggregation of other countries, but also to facilitate the inquiry process. Effectively capturing the data contained in Sipal may be organized in two ways: horizontally, by accessing each application separately — i.e. import statistics of one or many countries or evolution of the industrial production of air conditioning for aquaculture — and vertically, where the search is applied to the whole Sipal, starting with a common key such as a cultivated species, its production statistics, imports, exports, detected diseases, technology applied, etc… Also, the search may be directed towards a component useful to the aquaculture sec-tor such as factories producing feed, food nutrition experts, importers of basic needs for basic foods, etc…

3.2. Software Characteristics

Each of the applications developed (elements) are stand-alone applications containing all the typical input/output functions, linkage constraints and selective processing requirements to be fitted into each of the Modules. There are three types of the same software developed for three different uses:

1. Regional Read Only Use (RROU). This version will reside in the Regional Module of Sipal distributed to the countries. It will contain all the retrieval/output functions of the application.

   Peculiarity: It does not contain the data entry procedures and cannot be modified.

2. Regional Write Read Use (RWRU). This version will reside in the Regional Module of Sipal installed at Sipal Headquarters and at FAO Rome. It is very similar to the previous one (RROU) but will contain all the functions available, including data entry.

   Peculiarity: In its final version, once the dataflow is stabilized, it will also contain the data entry, data uploading and data security functions discriminator activated according to the data capturing protocols defined (established) for each of the contributing countries.

3. National Write Read Use (NWRU). This version will reside in the Sipal National Module distributed to the countries. For the time being, it will be similar to the first one (RROU) with the data entry functions incorporated, but countries will be invited, and possibly assisted, to expand the data coverage to be closer to their realities and at the same time be colloquial, compatible, and comparable with Sipal.

   Peculiarity: This set of programs will be given to the countries free of charge, and even include the source codes if requested. However, for the use in Sipal, in order not to lose consistency and control of the performances of the software, all the modifications should be made by the Sipal programmers. Sipal management, from its part should favor as much as possible the tailoring of the programs for national use to make the national data management under Sipal attractive and hence the uploading process easier.

For reasons of compatibility with FAO standards, and for other technical and operative reasons, the network hardware is configured around a platform based on the Intel 80486 micro-processor family. The elements that need to be integrated to constitute the network through non-rigid connections are of a different nature and effort.

• At the system architecture level national, international and FAO environments used have to be made colloquial.

• At the structural, level different connecting protocols (interfaces) to manage products coming from different environments need to be developed both for the input/output procedure and for the format and structure of the data.

• At the function/service level data format interchange with application software (standard commercial software) and connection to different peripherals such as printers, scanners, modems, as well as electronic mail, must be foreseen. At this level the different national working languages to be used in the system must also be taken into account For the prototype development Spanish was selected as the first language, and an English version was also prepared. In its final version, the system will be provided with a multi-language data dictionary to allow quick and standardized user interfacing.

For the Sipal software development, dBASE IV was selected for the Relational Database Management System, not only because it is an internationally accepted de facto standard, but also because many FAO applications, as well as national applications, have already been developed using dBASE engine.

3.3. Work Plan

During the preparatory work for the design of Sipal, it was decided to launch a program of work starting with the development of a prototype taking into account the available resources to better respond to the project idea: (i) high involvement of the end users; (ii) clear data and function definitions to be achieved with a high level of interaction between the design team, the development team and the end users; and (iii) tasks distributed among the developers in order to facilitate integration, errors debugging and to speed up the development process taking into account the limited available time.

The approach made it possible to complete the assigned task within the given time (the Aquila II project life) through:

• developing the methodology and providing a tool to collect and process in a systematic way information useful for aquaculture development in the Region. In addition to their own compiled data, the countries will have direct access (from the same National Center work-station) to regional data and FAO data

• designing and implementing a Regional Module to put regional information at the disposal of the countries in a readable and comparable format The Regional Information System will be fed with non-confidential national data of regional interest which each country has put at the disposal of the Project

• designing and implementing an FAO Information Module which will incorporate some of the available authorized FAO databases and other software of interest to this program of work

• designing and implementing a network linking remote sources of data and networks with the Sipal Extended Module through automatic data transmission

• preliminary evaluation on the utility to design and develop an analytical tool for aquaculture planning

• assisting the selected countries in the use and maintenance of the system

• extending the network whenever possible to other countries and other selected end-users, and individuating the best network approach taking into account all the various possibilities and constraints.

The time Schedule was drawn according to the following pattern:

Preparatory Work - Four months with the following objectives:

• Discussion, review and approval of the conceptual design.

• Ordering of the computer equipment

• Identification of the few countries to be included in the pilot Regional Information System.

• Complete delivery and installation of the work stations.

• Identification of a retrieval approach (terminology, function, logic data selection flow, etc…) most commonly used in a Desk Information System in the selected countries.

• Inventory of all pertinent national, regional and international data/ information available for possible inclusion in Sipal.

• Analysis of the immediate needs and the available national data in the selected countries.

Phase I - System Design and Development- six months:

• Design and implementation of the pilot FAO Information Module.

• Design of the Regional Information Module.

• National coordinators of the selected countries reorganize output from national data/information systems into the Sipal National Information Module structure (with advice from the Aquila Project).

• Development of interfacing protocols to integrate national systems into the Regional Information Module.

• Revision and implementation of the Regional Information Module.

• Preliminary testing, evaluation and validation of the two modules.

• Integration of all the work into a prefixed architecture, and preparation of the prototype which was presented at two International Fishery Exhibition in the Region for information and comments.

Phase II - Evaluation of the output of Phase I, completion of the Sipal Prototype - nine months:

• Nomination of the Data Manager.

• Recruitment of the Analyst/Programmer.

• Setting up the pilot Extended Module through arrangements and contracts with governmental and non-governmental institutions for direct access to their on-line databases and networks. The information captured from these systems will be treated according to the agreed contract and processed with the same logic as for the other two modules.

• Termination of all pending work involving participating countries and project staff.

• Delivery to and installation of the full configuration in the selected centers and countries (training, etc…, included).

• Evaluation of the delivered system.

• Revision and improvement of the system.

• Delivery of associated documentation.

Phase III - Evaluation/Revision/Improvement and ensure continuity of the System - five months:

• Analysis and evaluation of the entire work program.

• Formulation of development proposals for future technical development of Sipal.

• Delivery of final documentation.

• The Project will organize and hold meetings, correspond, undertake technical evaluation, present proposals, find solutions, implement ideas to ensure the future of Sipal.

• All the parties concerned: the FAO, the Donor, the countries involved in the development and installation of Sipal may consider that an additional phase be envisaged to complete delivery of the system.

Consolidation/Expansion - six months (approx.):

• Expansion of the coverage of the system.

• Re-elaboration of the whole system by introducing innovative and advanced programming to produce commercial-type user interfaces.

• Installation of the system in an other center and/or country.

• Completion of the system by finalizing the Extended Module.

Re-elaboration of the system taking in to account its expansion and consolidation has been envisaged as a future development to be carried out under the Windows® environment The main objective is to provide the users with a better user interface with all the functions the new platform may allow especially in terms of data/information integration, and data communication. In particular exploitation of the dynamic data linkages throughout the system should greatly improve production of automated multi-disciplinary reports directly “linked” to internal databases. Moreover, the whole search process may be replaced by a global system interface using SQL (Structured Query Language) which should lead to a reduction of redundant data associated with a faster and wider search capability.

4. SYSTEM CONFIGURATION

4.1. Hardware Configuration

Hardware configuration for the workstations forming the Project Network

Server/Manager Workstation, 1st level (Project HQ)

IBM PC or 100% compatible with the following characteristics:

• desktop type;
• CPU 80486 at 33 MHz, 4 MB RAM expandable;
• color monitor 14" VGA card;
• 1 floppy disk drive unit 1.44 MB 3.5";
• 1 floppy disk drive unit 1.2 MB 5.25";
• 1 hard disk drive 300 MB or greater, access time < 30 ms;
• International advanced 102-key keyboard;
• 2 parallel ports;
• 1 serial port RS 232C;
• bus mouse Microsoft or Microsoft compatible;
• 1 Bernoulli box 90-MB removable disk unit;
• 1 modem Hayes compatible 960/1200/2400 baud rates;
• 1 advanced Spanish keyboard;
• 1 wide-carriage (136 chrs) matrix dot printer with NLQ capability, 24 pins, 260 cps, IBM-EPSON compatible, parallel interface;
• 1 laser printer HP Laserjet III compatible, parallel interface;

• 1 scanner HP Scanjet compatible.

System Development, 2nd level workstations (Project HQ)

It is strongly advisable to pair the above microcomputer with another one similar in characteristics but lower in performance (and thus cheaper) to be used for system development, as a server back-up unit, and for other duties to be assigned.

IBM PC or 100% compatible with the following characteristics:

• desktop type;
• CPU 80386SX at 16 MHz 2 MB RAM expandable;
• color monitor 14" VGA card;
• 1 floppy disk drive unit 1.44 MB 3.5";
• 1 hard disk drive 100 MB or greater, access time < 30 ms;
• 1 international advanced keyboard;
• 1 parallel port;
• 1 serial port RS 232C;
• 1 bus mouse Microsoft or Microsoft compatible;

• 1 printer sharing device interface.

Backstopping, Training, Seminars, Demonstrations etc…, 2nd level workstations (Project HQ)

IBM PC or 100% compatible with the following characteristics:

• portable type;
• CPU 80386 at 25MHz, 1 MB RAM expandable;
• 1 backlit liquid crystal display VGA compatible;
• 1 floppy disk drive unit 1.44 MB 3.5";
• 1 bard disk drive 60 MB, access time < 30 ms;
• 1 parallel port;
• 1 serial port;
• travel accessories (bag, batteries, etc…)
• 1 Diconix or Canon portable printer with travel accessories;

• 1 Bernoulli 90-MB removable disk external unit.

Typical configuration suggested for National Centers

IBM PC or 100% compatible with the following characteristics:

• desktop type;
• CPU 80386xX at 20 MHz, 2 MB RAM expandable;
• color monitor 14" VGA card;
• 1 floppy disk drive unit 1.44 MB 3.5";
• 1 hard disk drive 100 MB or greater, access time < 30 ms;
• 1 international advanced keyboard;
• 1 parallel port;
• 1 serial port RS 232C;
• 1 bus mouse Microsoft or Microsoft compatible;
• 1 modem Hayes compatible 960/1200/2400 baud rates;

• 1 wide-carriage (136 chrs) matrix dot printer with NLQ capability, 24 pins, 260 cps, IBM-EPSON compatible, parallel interface; or laser printer HP type.

4.2. Commercial Support Software

All work-stations were provided with identical software covering:

• DOS operating system (Rel 6.xx);
• word processing;
• spreadsheet;
• database management system;
• high-level language;
• data communication software;
• utilities;

• specific application software.

During the prototype phase, the following commercial software packages were used mainly to be consistent with FAO software standards:

The software used for the development of all the databases was Clipper 5.1, dBASE IV Rel 1.5, Turbo C, MenuWorks.

4.3. FAO Software

The FAO software, directly accessible from the Sipal FAO Module, has been selected among that officially distributed by FAO which is directly or indirectly of interest of the aquaculture sector. The first Sipal release will then contain the following software:

Updating the FAO databases was the responsibility of the Aquila II Project up to its termination; in the future, the Regional Center should act as intermediary between FAO and the countries of the Region. Users are strongly advised not to change the Sipal directory structure when installing the above software. It must be located as defined in the installation phase of Sipal.

The outlines of this software are given in annex 4.

4.4. Databases Developed Within Sipal

At present, the nucleus of Sipal is made up of a set of databases related to selected themes to which a development priority was given by the national counterparts of the Region.

Statistics:

• Production.
• Imports.

• Exports.

Directories:

• Importers.
• Exporters.
• Suppliers.
• Projects.
• Production Centers.
• Legislation.
• National Experts.

• Bibliography.

Technological Aspects:

• Pathology.

• Technology of Cultivation.

As previously stated, those countries that intend to use the databases developed under Sipal for their national use may request Sipal management to modify the structure and the software accordingly. However, precise directions will be issued by Sipal administrators on how to submit such request, which should be expressed in an official letter from the national coordinator, specifying reasons, field to be added, relationships with other fields, type of variable, length, ranges, constraints, etc…

4.5. The Sipal Directory Structure

The menu architecture was developed taking into account a rigid directory structure. This approach permitted to develop the system simultaneously using different programmers, and to replace the developed software whenever required. This will also allow the countries to use their own software and databases without having to modify the menu.

Sipal databases and the system itself can reside in any Directory; D: has been used only as an example (Figure 3). The meaning of the acronyms utilized is the following:

Each subdirectory contains one application only. This will allow the System Manager as well as the users to modify, reorganize and even replace one application with another whenever required without upsetting the menu architecture.

Figure 3. Present Structure of Sipal Directories

To equip Sipal with an instrument for easy consultation on the World Statistics concerning food and agriculture, it was decided to include the FAO software The State of Food and Agriculture (SOFA). This package, which is released to member countries, provides easy access to updated information on agriculture and food status in the world. For those countries that already have Agrostat, or intend to acquire it in the future, Sipal equally allows for its use.

4.6. Guidelines for Software Documentation

Each new software will be provided with a set of documents, prepared according to the following guidelines:

1. Data on the country and the experts in charge of the software development This category will include the name of the Code Developer and the Project Director.

2. Name of the software and clear description of its objectives.

The description of databases will contain the following information.

For each main database (i.e. those databases different from reference banks) the information contained in sections (c), (d) and (e) will be included.

3. Name of the data file (DBF format) and a clear description of the data it contains, objectives, etc.

4. For each field the following information will be given:

   -   field name (name assigned in the database);

   -   field type (according to the xBASE standard - C, N, L, M, D);

   -   field length (total length);

   -   number of decimals of the field;

   -   description of the field contents, objectives, etc…;

   -   if the field contains a code, the name of the reference file containing the list of codes will be given; to indicate that the list of codes is in the file NOMBREARC.REF the notation “==> NOMBREARC.REF” will be used.

5. The documentation on the index files related to the database must include the following information:

   -   name of the index file;

   -   expression of the index key;

   -   indication whether the index created is unique or not (see SET INDEX Expression to cFile UNIQUE).

In the case of a reference database the following information must be included:

6. name of the reference database (DBF format) and description of the data contained therein, objectives, etc.

7. For each field the following information will be given:

   -   field name (name assigned in the database);

   -   field type (according to the xBASE standard - C, N, L, M, D);

   -   field length (total length);

   -   number of decimals of the field;

   -   description of the field contents, objectives, etc…;

   -   if the field contains a referenced code, which is included in the global codification defined in the First Regional Round Table on Sipal, the name of the reference file will be indicated; it should be highlighted that all the reference databases must include at least two fields: the referenced code and its name (or description); to indicate that the list of codes is in the file GLOBAL.REF the notation “==> GLOBAL.REF” will be used.

8. The documentation on the index files related to the database must include the following information:

   -   name of the index file;

   -   expression of the index key;

   -   indication whether the index created is unique or not (see SET INDEX Expression to cFile UNIQUE).

4.7. The Codification System

The codification system created during the development of Sipal has been discussed and agreed upon by the participating countries at meetings and working groups. At the present it is considered the standard to be used for information on aquaculture in the Region. This does not mean that all the countries must adopt the codification; however, the progress reached can be considered an important starting point, especially due to the lack of any agreement on terminology, definitions, units of measure, etc., when the development of Sipal started.

The codification system is divided into two main components: global codification and sector codification. The global codification cannot be modified at national or regional level as it has been obtained from FAO databases or other information systems already accepted at the global level. On the contrary, sector codification could be revised and modified by regional experts.

With respect to the national codification already in use in some countries, Sipal — whose aim is not to impose a new one — will facilitate the interfacing of national with regional terminology (adopted by the system) through the data dictionary established and agreed upon by the participants.

4.7.1. Global Codification

4.7.1.1. National Level

Fishing Area

Country

State (Administrative division) code (2), name (30)

Municipality (optional)

Species Group

Species

Date (dd/mm/yyyy)

Sector reference tables of the country

4.7.1.2. Regional Level

Fishing Area

Country

State (Administrative division) code (2), name (30)

Species Group

Species

Date (dd/mm/yyyy)

Trade (US$)

Quantity (metric tons, if not otherwise specified)

Number (unit, if not otherwise specified)

Sector reference tables of the Region.

4.7.1.3. Summary

For the Fishing Area the FAO codes will be used.

For the Country the FAO codes from Agrostat will be used

For the State the original codification from each country will be used.

For the Group of Species the Sipal codification derived from Aquadab/Speciesdab (FAO) will be used.

For the Species the codification from Aquadab/Speciesdab (FAO), integrated by the 3-Alpha codes and the taxonomic codes of FISHSTAT (FAO) will be used.

4.7.1.4. Contents of Global Reference Files

(*) Source Agrostat (FAO)

(‡) Source Aquadab/Speciesdab (FAO)

(‡) Source Aquadab/Speciesdab (FAO)

4.7.2. Sector Codification

4.7.2.1. Relationship Between Developed Databases and Reference Files

This is a description of the Databases developed, followed by the Reference Codes and the key to identify the correct Reference File.

4.7.2.2. Reference Files Contents

² Limited to the development phase. Afterwards, may be purchased separately by the countries.