CA1271843A - Automated design of structures using a finite element database - Google Patents

Abstract

ABSTRACT

A design and analysis system uses an engineering database in which Finite Element Models of structural components, such as offshore structures are stored, The database is controlled by a network type database management system to provide input of "finite element"
model data into the database from an external design engineering source and output of model data to non-design engineering sources with all sources having concurrent access to the database.

Description

~43 - 1 - Caae 4790 AUTOMATED DESIGN OF STRUCTURES USINC
A FINITE ELEMENT DATA~ASE

J ~"ACKGROUND OF THE INYENTION

1) Field of the Inventlon ~he pre~ent lnvention ls generally drawn to an automated de~lgn system for structures uslng a "Flnite Ele0ent~ databa~e, which syJtem has been particularly adapted to the desl6n Or offshore en6ineering structures. The databa~e ls controlled by IDMS, a general-purpose 1~ Jophl~tlcated database management control system.

2) De~crlption of the Prlor Art For msny decade~, the sclence of sdvanced stress anslysl~ remalned es~entlslly stagnant. Thls was not due to a lack Or theoretl¢al understandlng but because of the llmltatlon~ of numerlcal comp,utatlon. Thus, lf the shape of the stres~ed workplece or the system or applled load dld not ¢onform to a standard set of known solutlonJ, the ~tress analy~t had to then make lt flt as best as he could by a~umlng some ~lmpllfled shape or loadlng system that 2~ approxlmated the case at hand.

- 2 - Case 4790 Nowadays, by using the Finite Element Method (FEM), stress analysts do not have to modify the problem to conform to available solutions. No matter how complex the shape or system of loads may be, the (FEM) treats a loaded structure as being built of numerous tiny connected substructures or elements as are shown in Figure 8. Since these elements can be put together in virtually any fashi-on, they can be arranged to simulate exceedingly complex shapes. Thus, the (FEM) can be used to determine ~tresses for structural parts where no mathematically closed form solution exists.
-The rellable accuracy of the (FEM) has renderedsome Or the mo8t elegant experimental techniques, for example, two-dimenslonal photo-elastlcity, obsolete. Another important aspect of the (FEM), for example, is that it is not limited to ordinary stress analysis, Non-linear material propertles, plasticity and dynamics are all -within the scope of the method. Furthermore,(FEM) can be applied to a broad class of problems called field problems, which include topics like electrical potential, heat flow, and nuclear fusion, to name but a few.
-The idea of modelllng complex structures as acollectlon of well-defined structural elements, such as BEAMS, PL~TES, and SHELLS, was put forward and received much attention. The (FEM), did not first appear until the 1960's. Computer systems available at that time did not provide the capacity required to model and solve practical design problems within the realistic time and cost restrictions of most production design schedules.

,~
~ , .

3~
- 3 - Case 4790 Most of the development activity centered not only on the generation of large-scale structural computer programs as NASTRAN, but also on the development of sophisticated numerical methods for solving large sets of linear simultaneous equations.

The second milestone in the development of the (FEM) occurred in the mid-sixties with the advent of third generation computers. For the first time the computer power ~ required to solve complex engineerinB problems became available. Time-sharing computers, which aIlowed for more efficient interactlon with the stress analyst, and faster solution of engineering design problems were also introduced.

In its simplest form the FEM process is done according to the followlng steps:

. The structural part is divided into discrete ~Finite Elements", selected from the available library of fully developed and teæted elements _f as shown in Figure 8.

. These "Flnite Elements" are assumed to be connected together at discrete points called Nodes. Each Node usually has 6 degrees of freedom for its possible displacements: 3 translatlons and 3 rotations.

~,Z7~
_ 4 _ Case 4790 . The position of the~e Nodes in space is defined by specifying their coordinates relative to some reference point using a rectangular, cylindrical or spherical i 5 reference coordinate system.

. For each "Finite Element" a matrix, called the B matrix, is constructed from its geometrical properties.

_J . For each ~'Finite Element" another matrix, ¢alled the D matrix, is constructed from the elastic properties of the materials used.

. For each "Finite Element", a stiffness matrix k, is constructed by applying simple mathematical transformations to both the B and D matrices; k is always symmetric and consists of n2 submatrices, - where n is the number of Nodes ln the "Flnite Element". Furthermore, each submatrix in k is of order d, where d is the number of degrees of freedom of the relevant Node.

. A global stiffness matrix K is then Gonstructed using the individual matrices ~5 k, such that displacements are compatible at each common Node.

~ 3 - 5 - Case 4790 . The loads applied to the structure are then represented by equivalent loads applied on the relevant Nodes of the Finite Element Model. This results S in the set of simultaneous equations K r = R, (1~
where K is the global stiffness matrix, r is the displacement vector, and R
ls the load vector.
J
10 K is always symmetric, thus only it's upper or lower triangle need be stored or processed; it consists of N2 submatrices, where N is the total number of Nodes in the "Finlte Element" Model. As with the "Finite Element"
stirrness matrix k, each submatrix in K is of order d.

Some Node~ are usually constrained against movement, in order to support the loaded structure. To take account of this, the appropriate degrees of rreedoms in the relevant Nodes are ~-J set to zero.

' . The above equations, l.e. (1), are then solved, giving the final displacements for all of the degrees of freedoms of the Nodes ln the Model.

. The state of strain, and hence the state of stress, in each "Finite Element" is then -- 6 - Case 4790 fully obtained from the displacements of each "Finite Element".

The global stiffness matrix K may refer to more degrees of freedom than is required for the problem in hand. In this case, a technlque called static condensation can be used to condense K by eliminating the unwanted degrees of freedom:
these are usually called internal or dependent degrees of freedom.

j ~f The resulting condensed or reduced stiffness matrix, K', expre8se8 the stlffness of the structure in terms of the reduced number of degrees of freedom chosen; these are usually referred to as external, boundary or independent degrees of freedom. Thus, static condensation is essentially a process of partial elimination of the unknown internal dlspla¢ements. The resulting reduced stiffness equations may be wrltten as K' r' = R' , (2) where K' ls the reduced stlffness matrix, r' is the reduced 1 displacement vector, and R' is the reduced load vector.
I ~ 20 Static condensation ls essentlally the process oi computing , K'and R~, as follows:
I
j . Assemble the stiffness equations.

I . Partltlon the coefflcient matrlx of ¦ these equatlons into dependent and ! 25 $ndependent submatrices corresponding to the set of dependent and independent ' _ 7 _ Case 4790 degrees of freedom.

. Compute K'. This process usually involves a matrix inversion (or equivalent), which9 for large problems, may require considerable computer resources.

By way of example, the simply-supported, loaded, continuous beam, as shown in Figure 7, which consists of several spans, each having it's own cross-sectional properties, may be modelled as an eqivalent system at the two extreme Nodes only, using static condensation. The resulting reduced stiffness matrix K' may be viewed as the equivalent beam stiffness matrix in terms of lts end displacements and rotations, and similarly, the reduced load vector R' as the equivalent fixed end beam forces and moments of the applied load.

The static condensation method can be applied to condense any structural Model containing any number of Nodes.
Although there ls a lot of similarity betwen K' and k, there are two basic dlfferences:
J
, . For a given "Finite Element" type, the order of k is fixed and predeflned by the total number of degrees of freedom Or the "Finlte Element". On the other hand, the order of K' is variable and ls equal to SN, where SN ls the total number of lndependent degrees of freedom chosen.

~7,.8~
- 8 - Case 4790 . The k matrix is automatically generated by the "Finite Element" solver used (either in closed form or by numerical integration), whereas K' is obtained by static condensation.
The similarity between k and K' suggests that K' may be viewed as the stifness matrix of some Super Finite Element, which has no particular geometrical shape and whose Nodes are those designated as independent.
1~ This idea of a Super Finite Element has led to the more common name of "Super Element", and to the independent Nodes being called Super Nodes.

Once a solver is used to compute the independent di8placement vector r', it is then possible to re-apply these dlsplscements as boundary conditions to the Super Element Super Nodes and solve for the internal (i.e. dependent) dlsplacements.
i ~J Flnally, simple (or single-level) Super Elements are those consist1ng of the basic "Finite Elements" known to the solver, which is belng used to perform the static ¢ondensation. Nested (or multl-level) Super Elements, however, may consist of some Or the basic "Finite Elements", together wlth one or more other Super Elements at the tlme of statlc condensation. Usually, there 1s no limit to the number of nesting levels, and the only problem is keeping track of the data and matrices in the forward pass (i.e.

.~,............. .

~3 - 9 - Case 4790 static condensation) and the backward pass (recovery of Super Element internal resultA).

Turning to very particular structures, namely offshore platforms, we see that they must be structurally adequate for operational and environmental loading, practical to con~truct, and be cost effective. The selection of a configuration is based on functional requ$rementA and methods of installation. This is especlally true for structures ; situated in extreme water depths, such as the North Sea.
On¢e the configuration has been selected by the design engineer, trial member slzes (e.g. tube diameter, thickness and length) mu~t be assigned. These trlal ~izes are e~senti~lly educated guesses based on operational loads developed from equipment and materials layout, and estimated environmental loads. Estimates of the environmental loads are usually derived from experience with previous designs having similar environmental criteria. When assigning these trial sizes, consideration is given to the magnitude of the anticipated member forces, material used, local and overall 0ember instability, overall buoyancy requirements, and hydrostatic considerations.

The horlzontal and vertical forces exerted by wave action on individual members of the structure are calculated u~lng the well known "Morison" equation,in con~unction with any of the available wave theories~ These forces are functions of wave height, wave period, water depth and elevation above the mudline. In addition, the "Morison"
equation includes empirical coefficients which depend on the - ~zns~3 - 10 - Case 4790 size and shape of the member under consideration, and on the wave theory used.

In evaluating wave loads, the crest of the wave must be positioned relative to the structure, so that the loads have their maximum effect. Wind loads on the structure are developed using standard air flow theory. Sustained wind velocities are normally used for the computation of overall wlnd loads on the structure, but individual structural elements must be designed for instantaneous gusts.
~J
If the structure is to be installed in very cold or seismically active regions, lt may be sub~ect to ice or earthquake loads, ln which case more elaborate design and analysis procedures are used.

Once environmental loads are determined, they are combined with operational loads, and an estimate is made of the re~ulting plle mudline moments and axial forces. These approximate moments and forces are used in con~untion with foundation data to set trial values for pile penetration ~_J and make-up.

The desiBn of ma~or structural components of the superstructure and ~acket 18 based on member forces determlned in a 3-dimensional "Finite Element" analysis, whlch yields the resulting internal element forces, ~ode displacements and support reactions.

The pile analysis procedure employs a beam-column ..... . .

.. . . .

~ Case 4790 analysis using a finite difference technique to account for the non-linearity Or lateral deflection of the pile and the natural variations in soil profiles along the length of the pile. The design penetration is based on the capacity of the soil to absorb the maximum design pile load with apropriate safety fa¢tors. Furthermore, to ensure that the pile can be driven to the design penetration without damage, pile driveability studies are performed for the available hammers.

~efore the deslgn solution of either the 3-~J 10 dimensional nFinite Element~ analysls of the superstructureand ~acket, or the beam-column analysls of the pillng can be con~idered rlnlshed, lt ls necessary to determine compatible conditlon~ at the pllehead-structure interface. These equlllbrium condltions are usually obtained uslng an lnteraction analysls procedure whlch ylelds the combined response Or the llnear structure and lt's non-linear soil-plle foundatlon for any lmposed static load condition.

The equllibrium condltlons determlned from the interactlon analysls are now imposed on the structural Model ln co0bination wlth appropriate design loads, and a static analy~ls 18 performed. The internal member forces determlned ln thls analysls are employed to check the stress levels ln the ~e~.bers. The stresses are compared to allowable ~tre~es~ as set forth ln the deslgn basls, and members are re~ized accordingly. Submerged members of the ~acket must be ¢hecked for hoop stres~es lmposed by the hydrostatic head actlng alone or ln con~unctlon with axlal stresses from the deslgn cycle. If member resizlng lnvolves changes in outside , ~ ' .

~ j~,~

~3 ~
- 12 - Case 4790 diameter for a significant number of members, the overall waveload on the structure can be considerably different from that used to analyze the structure. In this case, the environmental loads must be determined based on the revised member sizes and the subsequent design steps must be performed again. The experlenced structure designer can usually avoid this complicatlon by the ~udicious assignment of trlal member sizes. If the environmental loads are not slgniflcantly affected by the resizing of the structural members, the revised plle deslgn can proceed using the 10 boundary conditlons from the interaction analy~is. When dynamlcs do not become a conslderatlon, thls phase constltutes the flnal foundation deslgn. However, deep water structure~ lnvarlably requlre detailed assessment of response to dynamla loadlng~ whlch necessltates further analysls of the foundation.

After the no0inal sizes for maln structural members have been finalized, it is necessary to design the ¢onnections of these members in accordance with the assoclated stress dlstrlbutlon. Geometrlc studies must be .J 20 made to deflne ~olnt layouts and to ellmlnate Joints which mlght prove difflcult to fsbrlcate. At the intersection of tubular member~, the chords or through members must be analyzed for punchlng shear stresses. Slnce the controlllng stre~s levels at many of these ~oints are caused by loads whlch are cycllc ln nature, due conslderatlon must be given to hlgh and low cycle fatlgue. For some structures, the deJlgn of these ~olnts may requlre speclal analysls to assess the cumulatlve fatlgue damage, includlng consideration of ~.. ~............................................................ .

,.., ~ ., ~ .. ..
... ..

- 13 - Case 47gO

dynamic amplification of stress levels for structures with slgnificant dynamic response. Complex joints require detailed stress analysi^c to determine the appropriate stress concentration factors for use in a fatigue analysis and the correct distribution of loads. These joints are studid using "Finite Element" analysis.

Upon completion of the structural analysis and the sizing of the maln members of the structure, the design of the deck and ~acket detail steel begins and the final routing J lO of piping, electrical, and instrumentation systems required on the stru¢ture ¢an be completed. The design of these detall steel items and auxiliary systems are carefully ¢oordinated with the layout of equipment and materials for drilling and produ¢tion. Also, prlor to designing the deck section, a lifting study must be carried out to ensure that the welght of the deck se¢tion with associated piping and equipment is within the lifting ¢apacity of the derrick barge to be u~ed on installation. To meet these criteria, the deck ~ust often be fabri¢ated in multiple ~e¢tions and a lifting sequen¢e is pres¢ribed, J
Once the ~a¢ket i8 fully designed, marine analysls can be perrormed for both towing and lnstallation of the fabricated ~acket. In the towing analysis, the stability and stren6th Or the launch barge/~acket assembly is evaluated for environmental conditlons due to wind, waves, and current expectet to occur along the towing route. For¢e~ caused by the barge response to these expected environmental conditions are used to design tiedown braces ror rixing the jacket to - 14 - Case 4790 the barge and to verify the structural integrity of the barge/jacket during tow. Towing analysis are also performed for the deck structure, piles, and any structure-related equipment that must be towed to the installation site.

When the barge i9 on location, the jacket is launched and then maneuvered from the horizont-al free-floating position to a vertical orientation on the bottom. An installation analysis computes the forces on the barBe and ~acket durlng launch and simulates the behavior of the jacket from launch through upending~

Dependlng on the functlon Or the offshore structure, plpelines may need to be installed for carrying the products to or frGm the structure. Analyses are performed for the design and lnstallatlon Or these pipelines and for the 8electlon Or associated laying equipment.

Small and medium size Finite Element Models usually pre~ent no real problems to the design of offshore platforms.
It 18 only when dealing with large Models that the real ~J dlfflcultles, ln using the Flnlte Element Method, are rèvealed. In general, these may be split lnto four categories: solver-related issues; data management l~sues;
"Flnite Elementn modelling issues; and offshore engineering issues.

It is extremely difficult to select the most suitable ~Finite Elementn solver for a given problem, particlarly when Users and/or Organizations have access to more than one _,, .

~,a~3 - 15 - Case 4790 solver. The suitability of a solver for a given problem is a matter of ~udgment and experience, and is usually related to:
it's ease of use, it's cost of use, and on it's modelling and analysis capabilities.

Some solvers are user-friendly and easy to use, others are not. In any case, Users have to be proficient in the use of the solver used in order to avoid costly mistakes and erroneous result~. Slnce it is not practical to expect U~ers to master the use of several solvers, more often than ;~J 10 not, U~ersfind themselves using inadequate solvers simply because they know how to use them. This usually results in U~er~ belng for¢ed to make varlous modelllng compromises and a~umptlons whi¢h may very well lnvalidate the analysi~
re~ultJ. A good example here is the Multiple Point 15 Con~tralnts feature of the "NASTRAN" solver programused to mathemati¢ally define the dependency Or certain degrees of freedom ~DOF~s) of one or more Nodes on the (DOF's) of other Nodes. Slnce some solvers do not support this basic modelllng requlrement, Users have to resort to various 20 almulation techniques (e.g. by connecting these DOFIs using J dummy nFlnlte Element~" Or inflnlte stifrness) t~ get around thlJ problem. These dummy "Finlte Elements~, however, are very undeslrable to have in the Model, particularly if the Model 1~ to be used for Materlal Take-Orr purposes.

Flnally, once a solver has been selected, the modelllng pro¢ess and the Model data become totally dependent on that ~olver. This makes it virtually impossible to switch later to another solver, due to unforseen circumstances, such ~;2~8J~
- 16 - Case 479~

as system bugs or internal ~ize limitations (e.g. exceeding the maximum number of Nodes or Load Cases). This is a very common problem which faces Users all the time, and the ability to switch over to another solver with minimal effort would be very advantageous.

Data Management Issues are related to the handling, management, and control of large amounts of data. Large Finlte Element Models require strict human control and excessive human and computer resources. Mistakes are, 10 therefore, very costly ln terms of time and money. The preparatlon, storage, and control of the masslve Model data are alway~ error-prone. It is vlrtually impossible to maintaln data consistency between $ndividuals working on the same Model. It is extremely dlfflcult to obtain accurate 15 estimates of the computer resources required. For example, the CPU tlme needed to condense a Super Element is, amongst other thing~, dependent on the bandwidth. Unfortunately, this is not known until the Super Element has been scanned and/or processed by the solver. Inputtlng and modifylng the 20 Model data i8 usually done on a card-image basis rather than on a logical basis. For example, lf a Node is t~ be deleted, it i8 usually up to the User to delete any addltional data associated with that Node, such as: all the Elements connected to it and all it's applied loads; this process is 25 very tedious and is certainly error-prone.

Finite Element Modelling problems are related to the lack of desirable modelling capabilities. It is virtually impossible to arrive at a near-optimum analytical Model (e.g.

- 17 - Case 4790 the best way to ~plita Model into Super Elements or the best Element or Node numbering scheme). The amount of work required to make a major modelling change is prohibitive.
This discourages the User from making changes which are otherwise desirable. For example, the problem of splitting a Super Element into two or more smaller Super Elements involves tedious Node and Element renumbering operations. It i8 not always possible to perform various useful operations on the Model before it is ready for processig by a solver.
For example, it i9 crucial that the incidences of certain Finite Element" types are deflned in a specific order (e.g.
clockwlse or antl-clockwise), otherwise, applied load~ may be mlslnterpreted and may lead to erroneous results.

All the issues dlscussed so far apply to any large-~oale Finite Element problem. Working ln an offshoreengineering design and construction environment, however, glves rise to even more problems.

The structural Models are usually very large, and hence, all the problems associated wlth large-scale Finite ~J 20 Element modelllng apply. For example, although a global Model of an offshore structure may consi~t of a moderate number Or BEAM Finite Elements, lt may have to be analyzed under several hundred loading conditions representing different wave directions and characteristics Typically, the equivalent of some 100,000 - 200,000 card-images of di8trlbuted Finlte Element loads could be stored in the database by one Application Program in one run unit (e.g. to oonduct a fatigue analysls).

_,..-.....

~2~84~
- 18 - Case 4790 The structural analysls and design cycle requires the use of a large number of programs (e.g. pre-processors, solvers and post-processors), all of which operate on the same basic data. This raises the obvious need for a central f~le or database.

The structural design data is usually needed by several disciplines, all requiring concurrent access. This _,~ raises the need to support a multi-user online environment, wlth the necesary automatic recovery facllities.

10Weather wihdows in hostlle areas, such as the North Sea, usually mean extremely tight schedules. This raises the need for Pro~ect Managers to obtain progress reports reflecting the status of the design and analysis at any moment in tlme.

15Structural modelling of offshore structures requires speciflc modelling capabilities which are unlikely to be ~J supported by any of the general-purpose structural analyAis systems (e.g. proper modelling of cutback values, insert plles, grouted piles and ungrouted piles).

2~It is very seldom that new offshore structures are ever designed from scratch. It is quite customary to use previously designed structures as a starting point. This raises the need to have intelligent access to historical data of previous structures.

'' ~2n~43 - 19 - Case 4790 It is important to have controlled archiving and restoring facilities in order to archive Models and restore them at a later date (this could be several months or years later, say, in order to do repair work). More important still, is that the archived database should include all information pertinent to the design codes wich were used for the initial design of the stucture. For example, if a structure had been designed according to the 9th Edition of l~ the API code, say several years ago, it may not pass today~s more stringent 15th Edition code; hence, the need to be able to reoonstitute the entire design and analysis environment.

From the foregoing, it will be seen that there is a deflnite need for properly addressing the issues of engineering databases particularly for offshore platform design and appropriate database management systems (DBMSs).
Thls englneerlng design requires more dynamic and more powerful DBMS' 9 than usual.

SUMMARY OF TH~ TNVENTTON

The present invention solves the problems associated with prlor art finite element deslgn systems and methods as well as other problems by providing a particular method of modelling an offshore structure using finite element analysls as well as a unique control system which communicates data to and from a unlque database using a network-type database manaBement system.

- 20 - Case 4790 The control system allows data to be communicated between a source of outside data and a unique database under the control of a network-type database management system.
~, The database of the control system becomes the ~J depository where the model of the offshore structure is deslgned and checked by one part of the source Or outside data, nanlely the design engineering input. Data on tllis developlng n~odel is concurrently available to other non-design engineering disclplines such as construction, n~aterlals nlanagement, etc.Thus va~ious disciplines are provided ¢on¢urrent access to the same up to date data which is being developed resulting in an efficient and speedy design and constructlon of any structure such as an offshore oil platform.
i The actual method of designing the offshore structure utllizes "finlte element" analysis and comprises the followlng steps, The structure is analyzed in terms of flnite elements and nodes which connect these finite element~. This plurality of finite elements and nodes is then condensed lnto a smaller number of super elements and super nodesby combining certain of the flnite elements and nodes.
Next, the equilibrium conditions of the super elements and ~...~.....

~2n~43 - 21 - Case 4790 super nodes is determined at interface points such as the water and mud lines to define boundary conditions. The static structure is then analyze using these boundary conditions to determine the forces and stresses on the structure.

The modelled structure may then be checked against industry standards and codes and then checked against anticipated environmental loading such as waves occurring at the wateP line of the structure.

J lO It will thus be seen that one aspect of the present lnvention is to provide a control system for communicating data between a database having a finite element model and sources of outside data utilizing a database management system. Another aspect of the present invention is to provide a database for modelling an offshore structure using finite element analysis where a ~ingle transaction may result inadding/deleting or modifying of over 200,000 finite element load records.

Yet another aspect Or the present invention is to 2~ provlde a method of modelling an offshore structure by combining finite elements and nodes into super elements and super nodes to provide a more manageable structure for design, analysis or construction.
These and other aspects of the present invention will - 25 be more fully understood after a review of the following description of the preferred embodiment when considered along with the figures.

g~3 - 22 - Case 4790 Figure 1 depicts the relationship between design areas of the present design system.

Figure 2 deplcts the database management system with S it~s lnputs as per the design system Or the present inventlon.

Figure 3 depl¢ts a sample problem solution using flnlte element analysis.

Figure 4 depicts typlcal finite element and node relation~ of the present de~ign system.

Flgure 5 depiots segments and sections connecting nodes Or the present design system Or the present invention.

Flgure 6 deplcts a schematic of the design system used for ~tructural analysis of an orfshore platform.

Flgure 7 depicts static condensation of nodes to super nodes ln the design system of the present invention.

,;;,,.,,~., ~"~43 Case 4790 Figure 8 depicts typical "finite element~ types usedin the database of the design system of the present invention.

Figure 9 depicts the program input and output files of the present design system.

Figure 10 depicts further the program input and output files of the present system.

Figure 11 depicts program space input and output .~j files of the present design system.

Figure 12 depicts the components of the database 1~ management system of the present design system.

FlgureS13(a)~depict~ a schematic representation of one part of the total database of the present invention ~ J/3~) f~ ~ ~ /3~ J_~C/`, FigureS13(b)~depict~ a schematic representation of a second part of the database of Figurel3(a)~ ~- /3(6) ~

v ~3(b) ~

. ... .
~i7~

~.~3 Case 4790 DETAILI;~ pTToN OF TH~ P~FERRED EMBODIM~NT

Referrlng now to the drawings in general, and Fig. 3 ln partl¢ular, it will be seen that in a usual offshore stru¢ture engineering environment, it i~ qulte normal for indlvidual engineering dlsclplines, such as Design 10, Marine 12, Drafting 14, and Material Take-Off 16, to maintain their own version~ of the Pro~ect they are working on. These different verslons may take different forms, such as drawlngs, reports and ¢omputer files. In such an V 10 environment, ¢onslderable resources are usually expended just to ensure conslstency between these different versions, and to keep tra¢k of the ongoing changes. Thls is no longer required using the present automated design system. Here, the Engineerlng Design group 10 is responsible for modelllng the ~tru¢ture under ¢onsideration using di~crete Finite Elements, down to any desired level of detail. Once this task has been completed, and the Model of the structure has been verified, thi~ one copy of the design be¢omes the database 18 Case 4790 - ~5 -and becomes instantly available to all other disciplines lO, 12, 14, 16, a~ shown in Figure 2. For example, the Material Take-Off group 16 may instantly get the current weight and center of gravity of the entire structure or any part of it;
the Drafting group 14 may produce detailed plots of complex ~oints; and the Project Mana~er may produce progress reports on the design/analysis phase of the Project from the design group lO.

A typical structural analysis ¢ycle usually consists of three distinct stages: Pre-processing; Analysis; and Po8t-pro¢essing.

Pre-processlng starts with modelling the structure in terms Or geometry, properties and loads, and ends with definlng all the environmental loads such as wave, wind and gravity. The analysis stage starts with a static ¢ondénsation to reduce the stru¢ture into a Super Element with Super Nodes formed from Nodes of the structure. This is then followed by a non-linear intera¢tion anaiysis to determine the equilibrium ¢onditions at the mudline. This stage ends with a full-s¢ale stati¢ analy~is on the structure usine the boundary ¢ondltions obtained from the non-linear interactlon analysls; this yields all the internal Node dlspla¢ments and Element forces and stresses. Flnally, the post-pro¢esslng stage lncludes applylng some of the industry codes (e.g. API, AISC, NPD, etc. ...) to ¢he¢k the integrity of the Nodes and Elements If such checks are passedt the analysis cycle is ¢on~idered complete; ir not, design changes .

lZ718~3 - 26 - Case 479Q
are effected and the whole process is repeated.

The above cycle is now explained in more detail.

Stage 1: Pre-Processing Modelling: Here, blue prints or sketches are used to idealize the structure in terms of discrete Nodes and Elements by using any of the following methods:

_~ . Manual lnput Or nodes and elements into the database 18 by known methods and languages.

. Inputting some basic dimensions, of framing panel types from a llbrary of horizontal and vertlcal panels. Also specification of some basic parameters, such as the number Or legs, bays and levels.

. Partial or full modelling of the structure from an lnteractive graphics work station by using known programs such as SUPERTAB.

Once the Model ha~ been generated, by using the above methods, various two- and three- dimensional graphical dlsplays are produced interactively, or in batch, by using ....

~3 ~

Case 4790 any of the folowing facilities:

One-line plots.

Joint (i.e. Node) detail plots.

. General three-dimensional plots-using SUPERTAB.

J These plots, as well as being of great documentary value, are essential for highlighting any modelling errors.
Minor errors are usually rectified using on-line correction technlques, but ma~or errors may require having to start all 10 over again.

At this stage, a typical offshore structure Model may optionally go through a sophisticated eccentricity generator to introduce clearances between each group of tubular members meeting at a given Node. These 3-dimensional clearances may 15 be specifled by the design engineer or may default to the ~_) values defined in industry codes. Global and local - geometrical ¢hanges resulting from the introduction of eccentricities can only be appreciated uslng graphical di8plays.

Another optional step here would be to split the Model into several Super Elements (unless this had already been done at the Mo~el generation stage). This may be achieved by:

~18q3 - 28 - Case 4790 At the end of this modelling stage, the database 18 would contain the following information:

~asic Model identification, Project control infor~ation and Users.
, . Reference data (e.g. RCS, materials and cross-sectional properties).

Node data (e.g. coordlnates, RCS, release or support codes).

. Finite Element data (e.g. incidences, types, cross-sectional properties and Element materials).

Environmental Loading of the model would then be started. Here, initial wave, wind and gravity loads are applied to the model structure in two steps:
~,~
. Generation of a wave pressure grid, u~ing any of the theories available, and storing it in a special wave profile file.

. Executing a sophisticated wave loading program to generate wave, wind and gravity loads and store them in the ~2~.~3 Case 4790 _ ~9 _ database 18, as applied Finite Element and/or Node loads.

An option exisSs here to go through the motions of load generation without actually storing any loads in the database 18. This is useful in order to select the most ¢ritical wave position and direction before attempting to update the database. Wave loads usually consume a significant amount of the database space, the extent of which depends on the number of wave directions, the number of ~ 10 Elements, and on the required combinations, based on maximum and minimum ~hesr forae and bending moment at the mudline.

In general, input loads may be defined using any of She rollowing methods:

. Wave generators, such as WAVELOAD for BEAM Elements, and MNI WAVE for other ; Finite Elements (this is the most common method).

! - . Manual input, (ror small I volumes only)-.
¦ 20 At the end of this loading stage, the system database 18 would contain the following additlonal information:

. Primary load case entries.

..........
. . _ .

8*3 Case 4790 Combinatlon load case entries.

Element loads.

. Node loads.

The next step would involve the analysis of the 5 loaded model. This oonslsts of extracting the data from the databa~e 18 by u~lng the appropriate interfaoe for the J ~ele¢ted solver or analysis program. Here, the User is not requlred to know the lnput data format for such solvers, whlch ls one of the maln features of the present design 10 8ystem Any Statlc Condensatlon technlques used in the Model's data and loads would be extracted by using the approprlate lnterface for the chosen solver program. The interface creates a formatted file containing the structure 15 a~ a Super Element with Super Nodes at the plleheads at the mudline. Thls is then processed by the solver uslng the J statl¢ condensatlon method, ln order to reduce the structure into a Reduced Stlrfness Matrlx (RSM) and a Reduced Force Matrlx (RFM). Both the RSM and RFM are then stored lnto the 20 sy~tem database 18 using known interface programs.

Structure Pile Interaction Analysis entails executlng a spohislcatd non-linear Structure Pile Interactlon Analysls (SPIA) known program. SPIA is an lterative solver used to match the equllibrium mudline deflections for the llnear \~
~3 Case 4790 structure with the non-linear foundation Model. These equilibrium displacements are then stored back in the database using other known interface programs.

Static Analysis is accomplished by taking the Super Node displacements produced by SPIA and applying them as boundary Node displacements for the structure, and the entire problem is analyzed again using the preferred solver (this need not be the same as that used for static condensation).
Here again, the appropriate interface i8 used to extract the f 1~ Model data, loads and applied displacements and feed them lnto the solver. The final results, which usually consist of Node displa¢ements, Element forces and stresses and support reactions, are stored back into the database l~ using the appropriate interface.

The next staBe is the Post-Processing Stage.
At this stage, the Model is ready to be checked against one or more of the lndustry ¢odes, such as API, AISC, NPD, etc.
... Here, there are four maJor de~ign-check cri~eria:

. Member check.

. Jolnt check.
. Submergence pressure check, . Fatigue check.

- lzns43 - ~2 -Case 4790 Graphics are used extensively during the post-processing phase. Typically, results (e.g. Node displacements and Element stresses) are extracted u~ing an interface to SUPERTAB, and then displayed in a variety of forms, such as deformed shapes and stress contours.

We will now cover the operational procedures a~so¢iated with initializing the ~ystem database 18 from _~ scratch, initiallzing a new Model, dumping a Model onto an ar¢hive tape and restoring it back to the system database.

1~ Database Initlalization To initialize the database 18 from scratch, the System Database Administrator proceeds a~ follows:

Initialize and format the physical dlsk space.
-.,~
. Populate the databa~e 18 with certain Model-independent information, such as: the global Finite Element library, the global database material properties and the global database Units Croups.
At this stage, the database 18 becomes ready to ,~_ ... .

- 33 - Case 4790 accept the first User Model.

Model Initialization To initialize a Model, the user si~.ply runs a known program such as MIP (Model Initialization Program), which adds a new Model entry, together with some default information. At the same time, the MASTER User and associated password are defined.

~_~ At this stage, the database 18 becomes ready to be populated with the Model data in batch, using known MDLP
(Model Definition Language Processor), or online, using OLU
(Online Update) programs.

Model Dump Once a Model has served it's purpose, and is no longer needed, the user runs a known MDP (Model Dump Program) ln order to archive the Model onto tape in MDL format. If thls is successfully completed, he then erases the Model uslng the MIP mentloned esrlier.

Model Restore Should there be a need to restore a Model from an archive tape, the user runs the MDLP program in order to load the Model from it's MDL format into the system database 18.

Access to System ~3 - 3~ - Case 4790 The system database 18 can be accessed in four different ways: via MDL, for batch update; via CULPRIT, for batch retr~eval; via OLU, for online update; and via OLQ for online retrieval. These are explained below.

Model Definition Language (MDL) may be viewed as a flat-file tabular representation of it's corresponding network view withln the database 18. It provides total independence of j ~olvers and gives a consistent format for interfacing with external programs. It provides a uniform method for creating ; 10 a Model, storing it ln the database, and extractlng it for archiving purposes. It is free-format, driven by headers and keywords, and in¢ludes some user-friendly features, such as an auto-increment facility, with zero, positive, or negative lncrements~ to be applled to numeric identifiers.

,. . .

EXAMPLE: The followlng MDL entries a~slgn materlal propertles mat#3 to all the even-numbered Finite Elements between 200 and 400:
!IJ
ELEMENT MATERIALS
' 20 3 200 TO 400 BY 2 i, , f'. . A global ALL facility to apply some ~ value to all entitie~ of a certaln kind.
~, .. .
~? ,, ~' ~,.~..

~I..

~8~3 - 35 - Case 4790 EXAMPLE: The following MDL entries assign material properties mat#3 to all Finite Elements itl the Model:

ELEMENT MATERIALS

. It provides powerful Model manipulation operations aimed at eliminating most of the tedlous manual functions, such as EXAMPLE: The followlng MDL entries merge 10 . three Super Elements (se# 3,4,5) into a new Super Element (se# 6):

SE DEFINITION
6 'SE 6 consists of se# 3,4,5' SE LEVELS

Onllr,e Query (OLQ) This system lncludes a comprehensive catalogue of predeflned online queries which offers the User instant lnformation on any part of the database. The more experienced User, however, may formulate his own out-hoc - 36 - Case 4790 queries online. To do so, the User must be very familiar with the structure and content of the system database 18, and must have database navigational experience.

Bat¢h Retrieval (CULPRIT) Batch retrieval is achieved almost exclusively using CULPRIT, as a report generator. CULPRIT is extremely powerful and has full acce~s to the databa~e 18 Integrated Data Dlctlonary, IDD, in order to obtaln detalled information on w~ the Records, Sets, data ltems, etc. .... The major drawback Of CULP~IT is that lt has to compile the source code at run time, thus adding a certain overhead to each run. Those most frequently-used reports are usually better written in a high-level language, ~uch as PL/1.

Onllne Update (OLU) Thls online mode is menu-driven and gives full-screen acceJ~/update capabllities to system database OLU offers the following reatures:
~f ' It provldes full-~creen editin8 capabi-litles to add, delete or modify any data item in the database.
. Each primary ~creen may have one or more secondary screens for extended data entry and additional User lnformation.

. ,. ~ ,....... ..

~P7~43 _ 37 _ Case 4790 It can be used in conjunction with color screens (e.g. IBM 3279), to improve screen readability and User productivity.

. Each screen has an associatd HELP
screen for online User help faci-lities.

. It offers a STEP mode of operation for beglnners and a FAST mode for experienced Users.

The entire OLU system is independent of the Operating System or the TP
monitor: these are taken care of by IDMS/UCF.

Finlte Element Modelling Features Next we will describe the various modelling features in the system which allow the User to fully ¢onstruct a Model, in terms of Finite Elements, Nodes, Super Elements, properties, loads, etc. ....

Models The Model is the highest level entry in the system database. A single Model could represent a Finite Element ~2~E~3 - 38 - Case 4790 idealization of any structual component, such as a complete - offshore structure. Another Model within this same system database 18 could represent a Finite Element idealization of a single tubular junction within the same structure. The maximum number of Models which could be stored in the same system database depends on the total space allocated. The system, as we have seen, has a range of utilities to:

. Init~alize a new Model.

. Dump a Model from the database lô
onto an archive tape in MDL format.

Restore a previously archived Model from tape to the database.

Copy selected data from one Model to another.

Cro88-8e~ctional Properties Cross-sectional propertles depend on the Finite Element types used. For example, BEAMs need about a dozen properties, PLATEs usually need one thickness property, TUBEs need a diameter and thickness, while SOLID Elements have no cro8s-8ectional properties at all. The User may define his ~7~3 ~ 39 ~ Case 4790 own cros-sectional properties or may simply refer to standard properties which are stored globaliy to the system database, suoh as standard pipes or wide flange profiles.

Reference Coordinate Systems A Reference Coordinate System (RCS) is an orthogonal set of right-handed axes located at any desired point in space, When a new Model i5 first created, a global default Reference Coordinate System, located at (O,O,O), is automatlcally generated ~rcs~ this may be rectangular, 10 cyllndrlcal or spherical ~ dditional local Reference Coordinate Systems may be ea~lly created by the User vla any three linearly independent polnts in space, or via a transformation matrix.

Once a Reference Coordinate System has been deflned, 15 it may be referred to by any of the following:

. Node coordlnates.

Node output displacements.

Node relesses.

. Element releases.

. Orientation of Super Elements.

~,.~

~18~3

- 4~ - Case 4790 . Orientation of Super Element Images.

Nodes A Node is a theoretical point with fixed coordinates in space. Nodal coordinates and displacements may refer to the same or to dlfferent Reference Coordinate Systems. Each Node usbally has six Degrees of Freedom (DOF), some of which may be suppres~ed, or released, relative to any RCS. Node ¢oordinates are ~tored in the system databa~e in exactly the same way a~ they are inputted by the User. This means that coordlnates with respect to a local RCS are not automatically transformed to the global Reference Coordinate System before they sre physically stored in the system database. Thus, it ~8 qulte acoeptable to have a group of Nodes using a rectangular Reference Coordinate System at the origin, and another group using some other, say, cylindrical Reference Coordlnate System located somewhere else in space. It is left to the Application Programs to do any necessary coordlnate transrormations at run time.

The system allows for a given Node to belong to more than one Super Element, but all Nodes must belong to at least the globsl Super Element.

Deleting a Node from any Super Element, other than the global one, simply terminates lt's participation in that Super Element without physically deleting it from the ", ^~, ~

~3 - 41 - Case 4790 databa~e 18.

Node Releases~Supports: Node releases and/or supports are defined at the Super Element level ln order to allow a given Node to have different release or support conditions in different Super Elements. Releases are defined by simply associating a Node with a predefined reference Release Code, which, in turn, defines which of the six Degrees of Freedom are to be released Each Release Code is usually associated with 80me Reference Coordinate System, J10 thus makinB lt possible to define local and global Node releases or supports.

K-Nodes: K-Nodes are ordinary Nodes used as reference points to define the orientation of BEAM Elements, and hence, their cross-se¢tional properties in spa¢e.

Inter-Node Relationships: Any Node may be asso¢iated wlth one or more other Nodes via a general purpose Bill of Material8-type of relationship, such as that needed to define Multl-Polnt Constraints (MPC) in the known NA~ïRAN program.

Finlte Elements The Finite Element (FE) is the smalle~t buildlng block in the structural Model. Each Finite Element must have a unique identification number wlthin the Model, and must be Or one of the types which are defined global to the system database in the so-called Finite Element library. The system .._ .,~, ~:5'1M3 - 42 - Case 4790 has no built-in limit on the number of Nodes per Element.

Finite Elements may be grouped to form Super Elements. The system allows a given Finite Element to belong to more than one Super Element, but all Element~ must belong to at least the global Super Element.

Finite Element Types: Finite Elements vary in their name, type, number of Nodes, cross-sectional properties, load ¢arrylng capabillty, and ln their output result3. A global Finlte Element library is maintained in the database 18 and lb may thus be referenced by any Model. Thls library contains the ¢ommon types, such as BEAMS, TUBES, PLATES, SHELLS and SOLIDS, which are supported by most solvers (other types, such as heat transfer, may be added to the library using OLU). Furthermore, it is quite possible to add special purpose Psuedo-Elements, such as whole conical shells, ring ~tiffeners, buoyancy tanks, etc., to be used for drafting, arine or Material Take-Off applications.

The deslgn system supports non-unlform concentric BEAM elements uslng the concept of segments and sections. A
Finlte Element may consist Or one or more segment3, and a segment may contain one or more sections. Both segments and sections may be assoclated with different material and cross-sectlonal properties.

Finlte Element Properties: Each Finite Element must be a~soclated with a ~et of material and cross-sectional .

......

~2ns43 - 43 - Case 4790 properties. These properties, together with the geometr~cal shape defined by the Node coordinates, fully define the Element Stiffness Matrix (ESM), which may be optionally stored in the database 18. Cross-sectional properties vary from one type of Element to another (e.g. PLATES may have a single thickness property, whereas BEAMS may need a dozen properties to define moments of inertia, area, etc.).

Finite Element Releases: Finite Element Releases ~restricted to BEAM Elements only) are defind at the Super Element level in order to allow a given Finite Element to have dlfferent release conditions in different Super Elements. Releases are defined by simply selecting one of the reference Release Codes, which in turn derines which of the 8iX Degrees of Freedom are to be released. Each Release Code is usually associated with some Reference Coordinate System, thus making it possible to define local and global BEAM releases.

Super Elements ~_J The concept of Super Elements (SE) plays a major role in the deJign system. In it's simplest form, a Super Element ~or sub-structure, as it i~ sometlme~ referred to) is a collection of Finite Elements. Super Elements are used to ~plit a large Finite Element Model into smaller, more manageable unlt~ and perhap~, more importantly, lnto units ~uch a~ Support Frame, Bottle Legs, Jacket, or piles, which correspond to the way in which the design, analysis or fabrication of an offshore structure would be carried out in a .,~.....

:D Z7~43 _ 44 _ Ca~e 4790 real life cituation.

Another useful application for Super Elements i5 to allow different idealizations of a given structual component.
For example, in a crude analysis of an offshore structure, a Bottle Leg may be idealized as a Super Element consisting of a single BEAM with some equivalent cross-sectional and material properties. Subsequently, in a more accurate analysls of the same Model, another Super Element containing hundreds of Finite Elements may be used instead.
_~ .
The present design system requires that each Node must have at least one global Super Element, which ls automatically stored in the system database when a new Model ls rirst initialized. This global Super Element may be used in problems whlch do not necessarily require the use of Super Elements in thelr proper sense.

A Super Element may be viewed as a generalized Finite Element wlth a variable number of Nodes called Super Nodes.
It may ¢onslst of any comblnation of Finlte Elements and/or Super Elements. Thls means that Super Elements may be nested down to any level.

Another useful way of defining a Super Element is by specifying the region lt occupies in space. For example, a Super Element for the Support Frame could be easlly created by statlng that lt lncludes everythlng above elevation 110 meters ~3 _ 45 _ Case 4790 In general, sensible use of Super Elements reduces - the cost of data preparation, validation and analysis, and offers greater scope for making local design changes to one or more Super Elements without impacting the rest of the Model.

Super Element Types: There are two types of Super Elements stored in the database 18: internal and external.-; An lnternal Super Element has all the data of it~
con~tituents (i.e. Nodes, Elements and properties) explicitly ; 10 stored ln the database 18. An external Super Element, on theother hand, only has its Super Nodes and Redu ced Stiffness ~j Matrlx ~RSM) stored ln the database 18. Such a matrix could i have been 0anually calculated, or more usually, would have been produced by using static or kinematlc condensation te¢hniques, which are avallable in most solvers.

Super Element Properties: These consist of three reduced matrices: the Reduced Stiffness Matrix (RSM), the Reduced Has~ Matrix (RMM), and the Reduced Damping Matrix (RDM). Although these matrices are normally Benerated by Appllcation Programs or solvers, it is also yossible to ~ .
~ manually define them using MDL. Another useful Super Element ,j property is it's connectivity matrix, which has many uses, b parti¢ularly in the areas of topological validation and ; bandwidth optimizatlon.
,. ~
Super Element Super Nodes: Each Super Element must ~i have a set Or Super Nodes (SN) which may be thought of as ~i incidences of the Super Element. Super Nodes have all the ~"
~, , ,,:
~,.
,~

_ ~....

lZ718~3 ~ 45 - Case 4790 attributes of normal Nodes, such as coordinates, Reference Coordinate Systems, supports and Release Codes.

Super Element Images: One of the most powerful Finite Element modelling tecniques is that of Super Element Images used to define repetitive structures. For example, in a four-legged structure, only one of the-four bottle legs needs to be fully defined in terms of Finite Elements, Nodes, properties, etc.; the other three could be simply defined as belng identical or mirror images of the flrst.

Applied Loadings Before a Model can be analyzed, all external envlronmental effects acting on the structure must be defined as a serles of Load Cases (LC), which may include any comblnation of applied Node or Element loads and imposed Node dl8placements.
Each Load Case is given a unique numeric identifier, together with some descriptive text. There is no built-in j limit on the maximm number Or Load Cases a~l~wed. Load Cases are deflned at the Model level for each Super Element.

There ls provision in the database 18 to store wave 2n profiles in which a given wave ls represented by a pressure grld for one full wave, and which vary from one location to ! another (e.e. Culf of Mexico vs. North Sea). This library of wave profiles may be referenced at run time by the wave load geoeration program for a given model.

, ~71~3 - 47-i_ Case 4790 Prlmary Load Cases: These are sometimes called independent Load Cases. Here, all the load components (Node and Element loads) are explicitly defined and stored in the database 18. Node loads consist of concentrated forces and moments, imposed displacements and rotations; Finite Element loads include concentrated forces and moments, distributed edge forces or moment~, surface pressures, temperatures, strain, as well as body-type loads such as gravity and lnertia.

Combinatlon Loading Cases: These are sometimes called dependent Load Cases since they are defined as linear combintions of previously defined Load Cases. Nested comblnations (i.e. Combination Load Cases that are made up of other Combinatlon Load Cases) are allowed, and there ls no built-in limit on the level of nesting. The system only stores the rélations defining Combination Load Cases and does not re~olve the loads into their equivalent prlmary Load Cases (this is left to the individual Application Programs).
i Clobal Super Element Loads: Global Super Element Loads are simply a convenient way for defining a global load value for a given Super Element wlthout having to expiicitly define it ~and physically store it) for each individual Finite Element. For example, this could be effectively used to specify, for a Super Element, an overall gravlty load in the negative y-direction or a unlform pressure load.
i i Foundation Modelling Features ,, ., ~r . . ~

~Z7~3 - 4~ _ Case 4790 These include features for soil modelling1 pile modelling, and soil/pile group modelling.

Soil Properties The database 18 contains sufficient data structures needed to fully define linear and non-linear soil properties for a given Model. These consist of the following:

P-Y Curves: Each curve applies to a given depth below the mudline and consists of a series Or pairs of values for lateral load ~P) and lateral deflection (Y).

T-Z Curves: Each curve applies to a given depth below the mudline and conslsts of a series of pairs of J 15 values for torsional load (T) and rotation (Z).

Skin Friction Table: This gives the distribution of skin friction along the depth of the pile.

2~ . Shear Strength Table: This is a single table defining the soil shear strength ,, ~

-_ ~9 _ Case 4790 values at different depths.

Piles A plle $s a segmented tube comprising a variable number of segments wlth varying segment lengths, cross-sectional properties, and material properties. Furthermore, a pile may consist of one or more concentric piles, e.e. one primary plle enclosing one or more insert piles.

There are two methods for modelling piles in the system database 18:

io . Method 1: In this method, each segment is defined as a proper 2-noded ~EAM element. Typically, this could result in about 50 Nodes and Finite Elements, which may then be grouped a~ a single Super Element. Also, the physical making of the _J pile may be properly defined using the inter-FE r~lationships mentioned later (e.g. physical Elements and enclosed Elements).

. Method 2: In this method, the entire pile i8 defined as a single Element. Here, the entire combination of primary pile and ln~ert plles, if any, would be defined as a single 2-noded segmented BEAM Element, consisting of several segmentsand sections, each with it's own cross-sectional and material .. . ~ ....

~3 - 50 ~ Case 4790 properties.
. .
Whether Method 1 or 2 is used, the entire pile configuration must be defined as a single Super Element with one Or it's Super Nodes at the pilehead.

In most structures, indiv~dual piles-are identical in their physical making, but have different orientation in space ln relatlon to the structure. In such cases, only one parent plle Super Element need be defined at some convenient orlentation and location (e.g. vertical at (0,0,0)), and all the other piles would be defined as Super Element Images.
This i8 a very userul feature since lt is not uncommon to have off~hore structures with 32 or 48 piles, for which only a single pile informatlon is stored.

Soll/Plle Groups A Soil/Pile Group ls slmply a convenient facllity for associating a pilehead Node with a given set of soil propertles. Once the ~acket Super Element is de~ined, it is connected to the piles at the corresponding pilehead Nodes.
As mentioned earlier, the pilehead Node should coincide with the plle Super Element Supe Node at the mudline. The soil propertles may consist of an combination of P-Y curves, T-Z
curves, and shear strength values. The association between each pile Super Element and it's corresponding soil properties is needed to perform the non-linear structure/pile ,~ 25 lnteraction analysis, as well as to complete the pile t~ , ,, .
:`

~,Z~3 - 51 - Case 1~790 analysis and design. Since soil properties are Model-dependent, it is possible to use the same soil values in different Soil/Pile Groups.

Next, we will describe some of the physical, as opposed to analytical, modelling capabilities, which have been speclfically incorporated in order to effectively meet the requirements of offshore structure~.

Finite Element Eccentricities Finlte Element eccentricities (restricted to BEAM
Elements) may be deflnEd at each end of a BEAM Element. Thi~
faclllty ls used to improve the modelling of tubular connectlons by includlng minlmum gap clearances between brace~ at connectlons. This produces more accurate data for the purpose of wave loads, gravity loads, buoyancy, lnstallation forces, preliminary Material Take-Off, and graphical displays of the structure. The actual information stored in the system database 18 to support this facility consi~t~ of:

l- Original center-line to center-line geometrical information.

2- Modifled geometry as a result of introducing minimum clearances.

~718~3 - 52 - Case 4790 3- Information needed to model the shortening of the tubular BEAM
Elements, due to their inter-section with chord Elements of finite size.

Inter-Finite Element Relationships Any Finite Element may be associated with one or more other Finlte Elements via a general purpose Bill of Materlals-type of relationship. This iq effectively utilized to slmulate the following requirements:

. Colllnèar Elements: these are a geometrical/design requirement, namely, that two or more Elements should remain on a straight line, irrespective of any geometrical ¢hanges to their surrounding Nodes or Elements.
. Physlcal Elements: these result from a fabrication requirement, namely, the identification of all the collinear Finite Elements which make up a single physlcal component, such as a ~acket leg.

. Enclo~ed Elements: the concept of enclosed Elements i~ essentlally an analysls requirement, wherein one or more tubular Elements are enclosed within other tubular Elements; for example, a pile enclosed wlthin a ~acket leg.

,__,..

JZ5~
- 53 - Ca~e 4790 Psuedo-Elements Although Finite Element types are building blocks with specific force-displacement relationships, the design system allows the definition and use of Psuedo-Elements which may be used for a variety of non-structural applications.
For example, a CONE Element may be defined to give an accurate graphical representatlon of a conical shell with known dlmenslons. The type of this Element would be CONE.
It would have two Nodes at lt's two center polnts, and it's cross-sectional properties would conslst of the top and bottom dlameters and the height. Thu~, such a Pseudo-Element could be used to accurately calculate the weight, volume, and ¢enter of gravity of a conical shell, instead of obtaining them from it~s corresponding Finite Element idealization.

Similarly, one could think of a Psuedo-Element called RINC for a ring stlffener, TANK for a buoyancy tank, and FILLER for water, grout or alr between two tubular Elements.

Next, we wlll descrlbe some of the mlscellaneous feature~ of the deslgn system, which are fully integrated with the modelllng featureq. These lnclude: Units Groups;
Comments; Group Types; and Hlstory log.

Unlts ~Z71843 - 54 - Case 4790 Internal Units within the design system may vary from one Model to another and need not be consistent within a given Model. A set of predefined Units Groups are available on a global ba~is. Each Units Group defines the exact Units used for certaln database entities, such as coordinates, cross-sectional properties, material properties, etc. For example, the system allows the cross-sectional diameter and cross-sectional thickness to be in different units (e.g.
lmperlal dlameter and 0etric thickness).
When the user lnitializes a new Model, he must select some convenlent Unit~ Croup from the global set. If none of the available Units Groups are appropriate, the user may deflne a new Units Group, which then becomes available to all other Models and Users.

Croup Types J It i~ sometimes required to group certain database entitie~ into one or more identifiable groups ror subsequent reference. For example, the User may be interested in grouping all Nodes whlch are above the elevation of 110 meter~, or all Finite Elements in the x-y plane. Another example i~ the 'weight per ~oint' report required by the Materlal Take-Off group 16, which requires grouping all the Element~ assoclated with a given Node. The system allows such arbitrary groupings using the Group Type facility. Each Group ....

lZ;~.843 ~ 55 ~ Case 4790 Type is assigned a unique 8-character identifier, and may consist of an arbitrary list of Nodes, Finite Elements, Super Elements, Load Cases, or even other Group Types. This means that ~roup Types may be nested down to any level.

The Group Type relationship is many to many; meaning that, for example, a Group Type may consist of any number of Nodes, and that a given Node may participate in many Group Type~.

Although most Group Types would be user-defined, some Application Programs would generate their own Group Types needed by other parts of the system. For example, some of the Appllcation Programs would automatically generate hundreds of Group Types which are needed to identify specific frames, bays or trusses within an offshore structure.

Comments This system allow~ the User to define any number of comments for any Or the main entlties, such as: ~odel; User;
Croup Type; Node; Flnlte Element; Super Element; Soil/Pile Group; and Load Case.

Each comment conslsts of a text portion of up to 64 characters long, the date and tlme stamps, together with the Model, User, and Super Element identlflers (m#, u#, se#).

~_..

- 56 - Case 4790 Database History A special Area ls reserved in the system database 18 for storing historical data on all active Models. This consists of certain identification data, date and time stamps, together with any useful comments. Once the database 18 history Area becomes near full, the- System Database Administrator runs HDP (History Dump Program) to dump this Area onto an archive tape and release the disk space. He then reinitializes the aforesaid Area before it can be used l~ again. Also available ls a series of CULPRIT programs to produce hlstory reports, sorted by Model, User I.D., date and time. These reports show all the transactions that have taken place for each Model ln the system database 18 and are of great value to Pro~ect Managers.

Database Security Features There are four levels of security in the database 18.

. Operating System Level: This level refers to the User I.D., password, accounting information, etc. needed to slgn-on to the Operating System's TP monitor. This is usually the responsibility of the Systems group. Auditing requirements require that passwords are changed at random intervals.

. Dataset Level: This level refers to the security offered by special software packages such as ACF2. Here, ~27~843 - 57 - Case 4790 the system prevents unauthorized access to datasets (files), whether such files are data files or program files. For example, this level could be used to prevent anyone but the System Database Administrator from running the DIP, or anyone but the Engineering Database Administrator from running the MIP.

. DBMS Level: Here, each authorized User must be registered by the Syste0 Database Administrator in the Integrated Data Dictionary.

l~. Appllcation System Level: This level is ¢ontrolled by the ~ystem Appllcation Programs accordlng to the control lnformatlon stored ln the database 18 ltself.

When the Englnering Database Administrator first ~nltializes a new Model, a special User entry, with a special MASTER password, is stored giving the Pro~ect Manager unrestrlcted access to the system databa~e 18 (only one unrestrlcted User i8 allowed per Model). Later, this MASTER
i User may add any number ofU~ers, specirying for each of them whether or not they are allowed to store, modify, or delete Super Elements or Croup Types. Thereon security is on a Super element basis. All Application Programs call a ~peclal authorization routlne which checks the User I.D., pas~word, Model, and Super Element. This routine would abort l~medlately in the event of an unauthorized User attempting to galn access to the Model.

_ .

- 53 - Ca~e 4790 Illustrative Problem In this Section, a simple example to illustrate the use of the Modei Definition Language (MDL), for defining a Finite Element structural Model, is presented. In general, the data required to fully describe any Finite Element Model consi~ts of three parts:

1. Topology: This describes the connectivity of the Model, which consists of a list of Element identifiers, Element types, and Node identlfiers.

2. Properties: These assign numeric values to each Nodal and Elemental property, such as Element cross-sectional properties and material properties.

3. Load~: These define the external load~
acting on the Model, such a~ Node forces, Element pressures and temperatures.

Problem Definition . The problem represents a hypothetical offshore structure, modelled as a two-dimensional frame in the X-Y plane (Figure 3). It consists of ~B~3 Case 4790 7 Finite Elements (fe# 1 to 7) and six Nodes (n# 1 ~to 6).

The entire Model is to be viewed as a single Super Element (se# 2) whose Super Nodes are the two mudline Nodes (n# 5 and 6).

There are no support Nodes for this problem, since it is assume,d that all that is required is a static condensation on the entire Super Element.

. All Finlte Elements have the same material properties (mat# 1).

. Two unique sets of cross-sectional properties are used: xsec#1 has a diameter and thickness of 16.0 and 0.5, respectively. The corresponding values for xsec# 2 are 30.0 and 1Ø

Only one Load Case i~ to be considered. This consists of two simple concentrated locds applied at nodes n# 1 and 3.

In what follows is a section of the MDL input needed to define the problem. MDL-type comments are used to improve readability, and to provide the reader with addtlonal explanatory remarks.

- 60 - Case 4790 ------------------------INITIALIZATION-----------------------Initialize a new Model.
_____________________________________________________________ MODEL INITIALIZATION
PROJEGT 'sample' MANAGER 'Shebini' PLANE 'xy' ----------------------------TOPOLOGY--------------_-_-_____-_ Define the x,y,z coordiates for each Node _______________________________________________________..._____ NODE COORDINATES

5 X -175 Y O

6 X 175 Y O
_____________________________________________________________ Define the connectivity of the Model ____________________________________.__________ _____________ ELEMENT INCIDENCES TYPE TUBE
' 15 1 1 2

7 6 4 ____________________________________________________________ Define Super Element (se#2) consisting of everything , .. .

~:~3 - 61 - Case 4790 above Y=O
____________________________________________________________ SE DEFINITION
2 TEXT IAll Elements and Nodes above Y=O.' SE REGION
Y1 0.0 ____________________________________________________________ Specify the Super Node~ of the Super Element _____________________________________________________________ SE SN
i 5 6 ~ ------------------PROPERTIES----------------------------Deflne the reference material~ to be referred to later ________________________________________________~____________ MATERIAL PROPERTIES
1 E 29000.0 NU 0.25 _____________________________________________________________ Select a previously-defined set of material properties for each FE
__ _____________________________________________ ____________ ELEMENT MATERIALS

_________________________________________.__________________ Define the reference cross-sectlonal properties to be referred to later ____________________________________________________________ S~CTION PROPERTIES
1 D1 16.0 T1 0.5 2 D1 30.0 T1 1.0 ____________________________________________________________ ~zn~3 - 62 - Case 4790-Select a previously-defined set of cross-sectional properties for each FE
____________________________________________________________ ELEMENT PROPERTIES

---------------------------LOADS-------------__________ ____ Deflne the Loading Case lc#1 _______________________________________________________._____ LOADING 1 'Load Case 1: Horizontal Loads at Nodes 1,3' _____________________________________________________________ Define the applied loads for the required Loading Case .
_____________________________________________________________ NODE LOADS

--------------------------FINISH-------______________________ End of MDL input data _____________________________________________________________ J FINISH
_________________________________________ ___________________ End _____________________________________________________________ ,"~", .

' ::,`. -, r _ ~Z~3 - 63 - Case 4790 Typical User Operations Once a Model has been successfully processed by the Model Definition Language Processor (MDLP), and ~tored in the database 18, the User would normally validate it using a variety of tools at his disposal. One such tool is OLQ, used to exe¢ute any of the extensive library of catalogued quer~es (QFILES). For example, in order to check that there are only two Super Nodes (snt 5 and 6) for set 2, the User would lnvoke a defined query Q335, which lists all the Super Nodes 1~ for a given Super Element for a given Model. This is acco~plished by slgning on to IDMS, then signing on to OLQ, and then enterlng:

Q335 sample 2 or ALL-SUPER-NODE-FOR-SE# sample 2 15 where , Q335 : is the short-code query identifier ALL-SUPER-..: is the long descriptive query identifier sample : is the Model identifier 2 : is the Super Element identifier . ,~.. .. .. .

~q3 - 64 - Case 4790 In response to the above query, OLQ would display the following information, thus confirming that the Model has been correctly defined:

ALL SUPER NODES FOR SE# 2 OLQ is ~ust one of many tools for the validation and manlpulation of structural Models. The following is a representative list of some of the more valuable operations and queries which can be used by any system User ln order to ascertaln the correctness of a given Model before proceeding with a costly anaiysis, thus improving his productivity and savlng time and money. The system ls a live and intelligent database:

J 15 . Llst all Nodes, internal Nodes, support Nodes, Super Nodes, etc.

List all Elements.

List all cross-sectional properties.

Llst all materlal properties.

., .
, ~a*3 - 65 - Case 4790 List all Super Elements.

List all Elements connected to a given Node.

List all floating Nodes (~.e. those not connected to Finite Elements).

. List all Elements having a given set of ¢ross-sectional properties (e.g. all TU~E
Elements having an outer diameter of 24 inahes, or all 2-inch thick PLATE Elements).

. List all Nodes between two elevations (e.g. all Nodes at the mudline).

List all Super Elements within a given Super Element.

Merge two or more Super Elements into one.

. Split a Super Element into two or more j ~5 Super Elements.

Check that all PLATE Elements are numbered counter-clockwise.

Check if two or more Elements have the same incidences.

. Copy selected date from one Model to another.

~....

~271843 - 66 - Case 4790 Calculate weight and center of gravity.

Calculate principal moments of inertia and orientation of principal axes.

. Calclate length, surface area or- volume of specific Element types.

. Calculate welding volume for each Node.

Calculate direction cosines for a given BEAM Element (e.g. check lr a given Element ls truly vertical).

. Calculate the maximum bandwidth, average bandwidth and standard deviation.

Calculate the computer resources needed to perform a complete analysis.

. List all the ¢hanges made to a given Model or Super Element.

When was a given Super Element last modified?
Who modified it? What was the nature of the modiflcation?

. Count the number Or Nodes, Finite Elements.
Super Elçments, etc.

~2~843 - 67 - Case 4790 Are there any properties which are not referenced by any Element?

Has a certain User completed his assigned task?

. Has a given Super Element been condensed?
Has it been analyzed?

Is there a Units Group already defined which allows diameters to be in inches, and thickness to be in mm?

. Are there any Models in the database for 8-pile structures in over 800 ft. of water?

DATABASE DESIGN

There are 0any criteria by which the system may qualify for being a database system. For ex~mple, the following definition of a database may be used:

",.. a generalized, common, integrated ¢ollection of company or installation-owned data, which fulfills the data requirements of all appllcations whi¢h access it, and which is structured to model the natural data relationships ~Z7~43 - 68 - Case 4790 which exist in a company ~l The system certainly satisfies the above definition, and possibly any of the other definitions that may have emerged over the years. Following this introduction, we briefly explain the approach taken in designing the database, and the constraints which were taken into consideration.

Database Design Approach J

At thls stage, we note the practical constraints under whlch the ~ystem database 18 has to be designed and lmplemented. For example, it is important to recognize that the system database is managed by IDMS, which ls a CODASYL-type ~i.e.network-type) DBMS (database management system, which obviously favors the use of a network data model as a starting point. In practice, the system database design process followed a combined network/relational approach, sometimes starting with a relatlonal view and mapping it onto a network view, and sometimes the other way around. The fact _~ that the network model, andthe relational model, are inherently related; and that it can be shown that a unique mapping from one onto the other without loss of data always exists, renders the distin¢tion between the two data models, at least for our design purposes, of little significance. It ls also worth mentloning that the approach adopted here ls a pra¢tl¢al one in which intuition and known constraints have played a ma~or role. For example, although most Schema Records in the system are, indeed, in Third Normal Form, Jl~

a43 - 6~ - Case 4790 there are certain cases where practical considerations prevailed, thereby resulting in some Schema Records having repeating groups, thus disqualifying the~ from being even in First Normal Form. However, there has recently been a trend to extend the relational model so that it can cope with repeating groups. This may, in the future, obviate the need for a relation scheme to be in First Normal Form.

The main considerations that had to be taken into ac¢ount when designing the system database 18, covered the ! 10 basic Schema components, such as Areas, Records, Sets, etc.

Areas Area Allocation: Although this is mainly done on logl¢al and natural grounds, it also involves considerations of run tlme performance. This is so because increasing the total number of Areas defined in the global DMCL is known to have an adverse effect on IDMS performance.

In the database 18, there are two types of Areas:
i Model-Independent Areas: These contain Schema Records which are not linked to other Schema Records in other Areas in any way, and hence, may be archived or restored lndependently of the rest of the database 18 (e.g. global materlal propertieæ and global cross-sectional properties).

- ` -lZ~7~843 _ 7~ _ Case 4790 Model-dependent Areas: These contain Schema Records which are associated with other Schema Records in other Areas, via Schema Set pointers.

Area Names: Wherever possible, meaningful Area names are used, prefixed by SDB (Structural Database) for ease of identification within the global DMCL, and to conform to the user's standards.

Records Record Names: Meaningful Schema Record names are used wherever possible. This is particularly useful when using the online query facility OLQ.

Record Length Mode: Most of the Schema Records are of fixed length. Only seven are of variable length, and this is due, mainly, to the presence of repeating groups (OCCURS...DEPENDING ON...clause). Although the corresponding relations Or such Schema Records would not be in First Normal Form, the declsion to retain repeating groups is essentially a matter Or ~udgment and efficiency.

2~ Sets Set Linkage Options: Since NEXT pointers are mandatory in IDMS, the choice is whether or not to include PRIOR and/or OWNER pointers as well. In addition to being 12'7~84:~
- 71 - Case 4790 able to traverse Schema Set occurrences in the reverse direction, PRIOR pointers allow IDMS to perform the ERASE DML
command quickly and efficiently. The penalty for each additional PRIOR pointer is 4 bytes of storage space per Schema Record occurrence, which, after careful consideration, is comparatlvely negligible. Accordingly, all Schema Sets have PRIOR pointers.

OWNER pointers, on the other hand, have been included in 69 out Or the 122 Schema Sets, where it was felt they were needed ln order to ~peed up certain queries or transactions.
As a general rule, however, all Schema Sets used in asso¢latlon w~th LINK Records rOr m:n and Bill of Materials relatlonshlps have OWNER pointer~.

_ .

lZ7~843 Case 4790 Set Membership Options: Most Schema Sets (98 out of 122) are MANDATORY AUTOMATIC, i0plying the existence of certain constraints to be automatically applied by IDMS. For example, data describing a Finite Element Model must be stored into the database 18 in a specific order (e.g.
Reference Coordinate Systems must be defined before Nodes, and Nodes ~u~t be defined before Finite Element~). The MANDATORY AUTOMATIC option may thus be used to guarantee such dependency wlthout having to rely on the Application Programs.

The Schema Set statistics given earlier show that there are only six MANDATORY MANUAL Schema Sets. These correspond to half of the 12 Bill of Materials relationships which always ¢ome in pairs of MANDATORY AUTOMATIC and MANDATORY MANUAL.

Flnally, OPTIONAL MANUAL is used i~ cases where a member occurrence is allowed to chan6e it's owner. For exsmple, changing the material properties of a Finite Element after lt has been stored.

Set Order: ~ost Schema Sets are ordered NEXT.
Although this gives Application Programs more freedom for establishing currencies anywhere along a given Set occurrence, this is not of any particular significance to the system Application Programs.

- `~
l2~a43 _ 73 _ Case 4790 SORTED Sets, however, are extensively used and play a ma~or role in accessing a Schema Record occurrence based on it's key value. They are also extremely useful in guaran-teeing uniqueness of keys, using the DUPLICATES NOT ALLOWED
option in the Schema DDL. For example, in order to prevent a Super Element containing the same Finite Element more than once, the LINK Record employed to model the m:n relationship between Super Element and Finite Element contains the Finite Element key identifier (fe#) on which the Schema Set, from Super Element to Finite Element, is sorted with DUPLICATES
NOT ALLOWED.

Data Items Data Item Types: Since the system is an Engineering database, it ls no surprise that certain data types, which are normally used in commercial systems, are absent (e.g.
flxed point declmal data items). In fact, the ma~ority of data ltems are floatlng point numbers which are needed to tore extremely large and extremely small numbers within the same number Or bytes. All floating point numbers used in the system database 18 are in single precision, the exception being the SE stiffness, mass and force matrices, which are stored in double precision.

Full-word integers are used extenslvely as key identifiers. One of the main rea30n~ behind choosing IDMS
is the fact that it's Schema structure supported all the baslc data types, such as : integers, fixed decimals, bits, -~2718~3 Case 4790 floating point n~mbers, strings, and single~double precision.

Planned Redundancy As with any practical database design, that of the system database 18 involves a certain amount of redundancy. This manifests itself in two different ways: -By storing key identifiers in the LINK
Record Or an m:n relationship, 80 as to avoid havlng to access it' 8 owner.

. By deflning addltional Schema Recorts and Schema Sets only to provide alternative, faster access paths to infor~ation which may be fully obtained by other, though much longer, paths.

A good illustrative example of this is that given in Figure 4, which shows three m:n relationships, namely, those between Super Elements and Finite Elements, between Super J Element~ and Node~, and between Finite Elements and Nodes.
The LINK Record FE-NODE and the two Sets FE-NODES and NODES-FE represent the m:n relationship between FE and NODE, in which a ~ingle FE may have one or more UODEs and a single NODE may belong to more than one FE. Similarly, the m:n relationship between SE and FE is represented by the LINK
Record SE-FE, and the two Sets SE-FES and FE-SE. Finally, the LINK Record SE-NODE represents the m:n relationship between SE and NODE. Also shown is the SE-LEVEL Record, ,........

~27i843 - 7S - Case 4790 which is just a special case of a LINK Record, required in this case to represent an m:n relationship between a Schema Record and itself (usually referred to as a Bill of Materials-typè of relationship). In this instance, it is used to define multi-level (i.e. nested) Super Elements.

The first form of redundancy in this example is the storage of the value of the following primary keys within the LINK Records:

. The SE-NODE LINK Record ¢ontains both 1~ se# and n#.

The SE-FE LINK Record contains fe~.

The FE-NODE LINK Reocrd contains both fe# and n#.

The se¢ond form of redundancy results from the existence of the SE-FE and SE-NODE Records, although only one of them is really needed In this particular case, the need J to get all Nodes in a Super Element, or all ~inite Elements in a Super Element, is equally important to Application Programs and relevant queries. It is worth mentionlng here that this form of redundancy could, if not properly controlled, lead to inconsistencies in the database. In the system database 18, the Application Program responsible for creating the two Sets of LINK Records treats the whole operatlon of creating a Super Element as one transaction, and is essentially a matter of either all or nothing. This means i27~843 - 76 - Case 4790 that if, and only if 9 all the LINK Records are successfully stored, does the appropriate Application Program issue an IDMS COMMIT, otherwise it nullifies the entire transaction by lssuing an IDMS ROLLBACK.

ERASE Control The system database 18 is so designed as to allow eraslng whole groups of related data wlth minlmal effort, by uslng the ERASE....ALL DML command and applying lt to the Sche0a Record owning all the related data. For example:

. The entire system database may be erased by deletlng the one and only occurrence of the SD~ Schema Record.

. An entlre Model may be erased by deletlng the correspondlng oc¢urrence of the MODEL
Record All offshore related data may be erased by delet~ng the OFFSHORE-CNTRL Record occurrence of a glven Model.

. All foundatlon data may be erased by deletlng the SOIL-CNTRL Record occurrence of a glven Model.

"",...

~27~343 77 Ca~e 4790 Furthermore, the structure of the system database 18 is such that under no condition would any Schema Record occurrences be left behind, after an application of an ERASE
ALL or ERASE command, with no apparent access route to them.
This has been achieved by careful database design and suitable Schema Set membersh~p options Database Admlnlqtratlon Aids At the very outset of the system database design stage, Schema, DMCL and Sub-schema modules were manually coded and Data Structure Dlagrams were plotted by hand.
Also, the re¢ommended clock rule method, for keeping track of Set polnter posltlons needed ln the Schema DDL source, was very cumbersome indeed. It thus became clear that the complexity Or the system database 18, would have made it very dlfricult to continue lt's development using the afore~aid methods. Consequently, several database j ad0inistration tools were developed in order to automate the above onerous and tedious tasks. They include:

. EBN: An Extended Bachman Notation.

. DBA/DDL Program: A DDL generator for Schema, DMCL and Sub-schema source code.

DBA/DOC Program: A documentation generator . . .

~27~843 - 78 - Case 4790 for each Schema Record and Schema Set.

DBA/SPACE Program: A utility to calculate the physical disk space requirements.

. DBA/PLOT Program: A plotting program for Data Structure Diagrams.

We now describe the above tools in more detail.

Extended Bachman Notation (EBN) This is an extension of the well-known Bachman notation, in which a stru¢tured naming, identification and 1~ ¢ross-referenclng ~ystem has been devised in order to make the automation of various database administration functions possible.

DDL Generator (DBA/DDL Program) This program is wrltten PL/l, and ls now one of the 00st u~eful software tools available to Database Ad0inistrators.

~2~843 - 79 - Case 4790 This program has two input files (Figure lO):

l. Schema definition file: This is a simple fixed-format file in which all the Schema components are defined.

?. Run control file: Thls is a free-format flle in which all the run-time parameters and options are defined.

The program produces three output files:

. Schema DDL source code.

DMCL source code.

. sub-8chema DDL source code.

The DDL source code generated by the program includes all Files, Areas, Records and Sets contained in the Schema, as well as all pos~ible options allowed by the DDL syntax.
Although this, in general, re~ults in the source code being much more than may be aotually needed for a given design, it i8 a farily ~imple task to use any online text editor to delete any unwanted code and/or options.

~.
#~-- 80 - Case 4799 - The DBA/DDL Program offers the following major features and/or benefits:

. The Schema, DMCL and Sub-schema DDL source code is guaranteed to be syntactically correct.

. Extensive validation checks are carried out by the program to ensure that the Schema DDL source code ls error-free before lt ls passed to the IDMS Schema compller, thu~ saving considerable processlng time without clutterlng the IDMS data dictlonary with ~seless information.

. The automatlc calculatlon and tracking o~ Set polnter posltlons obviates the need to use the cumbersome ¢lock rule method mentloned J earlier. Thl~ also makes subsequent Schema deslgn changes ln whlch Sets are added, modlfied or deleted. A
slmple task, partlcularly at the early design stages.
s . Calls for the databas e Procedures, IDMSCOMP and IDMSDCOM, are automatlcally lncluded ln ~s ',, ,,~
,:
~s.i !

12~1~343 - 81 - Case 4790 the 5chema DDL source code for all Fixed Compressed (FC) and Variable Compressed (VC) Schema Records. For example, IDMSCOMP is invoked to compress a Schema Record occurrence before a STORE or MODIFY operation, whereas IDMSDCOM is called a~ter a GET
or O~TAIN operation to decompress a Record occurrence.

. Absolute page numbers are automatically computed and generated, based on relative Page numbers or Area sizes defined by the Database Administrator. This eliminates some tedious manual calculations and guarantees the correctness of the resulting values.

. Alias Area names, based on a one-letter sufflx defined by the Database Adminlstrator, may be automatially generated, thus providing a simple, error-free procedure for creating multiple database environments, basd on some reference Schema. This particular feature is extremely useful for distinguishing between a production database and one or more test databases, all running ~27~8~3 - 82 - Case 4790 under one IDMS DC/CV.

. A minimum space option allows the Database Administrator to go through the motions of generating the entireDDL source code without having to worry about the exact Page nu~bers or Area size~, which is extremely useful at the early stages of the Schema design. In this case, the program simply defaults all Area sizes to the mlnimum allowed, which for IDMS
i8 two Pages.

. The program uses a ver y ¢onvenient ldentlflcation system based on 4-dlgit numbers, prefixed by a unique one-letter prefix to refer to Files (F), Areas (A), Records (R), Sets (S), and Members of Sets (M).

f . The program includes options for the generation of DDL source code statements required to deflne different synonyms , to be used for dlfferent DML languages such as COBOL, PL/l, FORTRAN, ASSEMBLER, as well as different headers for OLQ or CULPRIT. These may be later edited using any available online text `-~

127i843 - ~3 - Case 4790 editor.

Record and Set Documentation Cenerator (DBA/DOC Program) This program, written in PL/l, is essentially part of the previous DBA/DDL Program, which may be invoked by an optional run-time parameter (Figure 10). If selected, the program produces valuable, properly-formatted documentary material for use by the Database Administrator, or indeed, by anyone lnterested in the system database. This documentary material consists of two components:

1. Record documentation: Thls ls one page per Schema Record, using Extended Bachman Notation.

2. Set documentatlon: This is one page per unique Schema Set, using Extended Bachman ~15 Notatlon; multi-member Sets would appear on multlple pages.

Both riles contain necessary INCLUDE statements tor equlvalent), in order to iDclude any documentary text created by the Database Administrator, and stored externally in a source library, which may be created and maintained using any onllne text edltor. Furthermore, the program has a SCRIPT option, which outputs the above two files ln a form compatible with the IBM mainframe text processing system, ;;;:;; .

,s~ !
~27~843 - 84 - case 4790 SCRIPT/VS This particular option makes it possible to automatically generate page numbers, as well as a usful index based on certain keywords.

Finally, the simple 4-digit identification system mentioned earlier is fully utilized here for producing the appropriate page headers and for the automatic generation of index keyword~ used in SCRIPT.

Dlsk Space Reporter (DBA/SPACE Program) Thls utlllty program uses the CULPRIT report generator in order to assist the Database Administrator in calculatlng the exact number of Pages and Page sizes for each S¢hema Area.

The program has two lnput files (Figure ll):

l. Record Definltion Flle: This is a slmple fixed-rormat flle which contalns one line per Schems Record, together wlth some identiflcation data. Except for the flrst two flelds in each line, the rest of the entries are automatically generated as a byproduct of the DBA/DDL Program.
All the Database Admlnlstrator has to do ls to edlt the flle online and lnsert the appropriate values in the two undeflned rields, which are simply: the expected number Or Record occurrences 12~8~:~

- 85 - Ca~e 479O

and the per¢entage probability of this number.

2. Run control file: This contains only a few optional parameters in order to control the run.

The program produces two output reports:

. Space requirements for each Schema Record:
this shows the actual Schema Record data length and the Record overhead (due to Set pointers).

. Space requirements for each Schema Area:
this shows the total number of Pages needed by each Area to accomodate the various Schema Record~, together with the total space required by the database itself.

The DBA/SPACE Program orfers the following major features j 15 and/or benefits:

. The space taken by the Set pointers, depending on the pointer options chosen (i.e. NEXT, PRIOR, OWNER) is automatically included.

. The space taken by the hidden CALC Set pointers, maintained internally by IDMS, is automatically accounted for.

. . .

', ,, "' ............. ...

127~8~3 - ~6 - Case 4790 . The Space Management Information (SMI) Pages (87) which are reserved by IDMS at the beginn1ng of each Area are included and properly identified.

. The Page overhead reserved by IDMS (e.g. Page header, footer and line index) is al-~o accounted for.

. Any Schema Area, which, because of the chosen Page siZe, cannot accommodate a minimum number of Schema Record occurrences, is flagged for the attention of the Database Administrator, thus hlghlighting a potential design inefficiency.

. Similarly, any Area Page, which cannot be fully utillzed, is flagged for the Database Administrator. This i9 usually the case when a large Page size i8 used to store very short Schema Record ocurrences, since IDMS can only store 8 maximum of 255 llnes ~i.e. Schema Record occurrences) per Page, no matter how large the PaBe i5-Data Structure Diagram Plotter (DBA/PLOT Program) This program, written in PL/l and FORTRAN, is a great ~27i843 - Case 4790 productivitysoftware tool and is used to plot Data Structure Diagrams using the Extended ~achman Notation.

~he input to the program consists of three files:

- 1. Schema definition file: This is the same file referred to earlier in the DBA/DDL
Program.

2. Plot deflnition file: Thi~ is a fixed-format file definlng the general lsyout of the Schema Records and Sets to be plotted.

3. Run control file: This is a free-format flle in which all the run-time parameters and options are defined, (e.g. overall scallng factor and color asslgnment).

The output from the program usuaily consists of a plot tape ready for plottlng on any Calcomp-compatlble multl-pen drum plotter. It ls also posslble to produce slmllar plots on a Tektronix graphics display unit by uslng the appropriate software interface.

The DBA/PLOT Program offers the followlng ma~or features and/or benefits:

. The program ls driven by the same Schema , . , ~27~843 - 88 - ~ase 4790 definition file used by the DBA/DDL Program to generate the Schema, thus eliminating any possible lnconsistencies between the Schema and the corresponding Data Structure Diagram.

. The program includes options to plot the entire Data Structure Diagram or selectd portions or views of it (e.g. Sub-Schemas).

. The physical size of the plot can be determined by the Database Administrator by choosing the appropriate scaling factors, or may be automatically generated by the program.

. Records, Sets, titles, grid llnes, etc.
may be optionally plotted in any one of four different colors. For example, this facility may be used to distinguish LINK Records from others by plotting them in red, and everything else in black.

. Although the IDMS/SPF facility (secondary indexlng) ls not used in the system database, the program automatically recognizes indexed sets, and it ls thus able to plot the approprlate triangular symbols used to identlfy such Sets.

~ \
~2~843

- 8~ - Case 4790 . In addition to plotting the basic information of a Data Structure Diagram, the program alsa plots the 4-digit identifiers mentioned earlier for convenience and ease of cro~s-referencing with the Schema DDL source code or other documentation.

. Optional summary plots may be produced on small slze paper for quick reference. These are skeleton Bachman plots, on which only the Schema Record and Schema Set names are shown.

. The program includes various run-time options for annotating the Data Structure Diagram with titles, summary of abbreviations and border line~. Such annotation is fully controllable in terms of positioning orientation, size and color.

J Samples of a full and ~ummary Data Structure Diagram produced by the DBA/PLOT Program are given at the end of the report.

127~8~3 - 90 - Case 4790 Choice of DBMS

The inventor after experlmenting with two types of DBMSs: MRVSYSTEM 2000 (Hierachic) an~ XEROX/EDMS ~Network).
It was concluded that the complex network data structures inherent ln Finite Element Models would have been difficult, if not imposslble, to model using a hierarchic DBMS. This can be easily visualized from the example given earlier in Figure 4~ showing the m:n relationships between Nodes and Finite Elements; between Super Elements and Finite Elements; and between Super Elements and Nodes. Although that example is only a small portion of the overall Data Structure Diagram, lt i9 very typical of the complex network-type rlationships in the system.

Having eliminated hierarchical DBMSs for the system, lt was also fairly s$mple to eliminate the possibility of using any relational DBMSs, mainly due to their inefficiency ln handllng extremely large databases such as the system.

The lnventor conducted a survey of the available network-type DBMSs. This indicated that Cullinet~s IDMS was ~0 the most suitable network-type DBMS for implementing the system database. Other factors in favor of IDMS were: it's data dictionary-driven concepts; it's apparent ease of lnstallatlon; it's comprehensive range of complementary products; and it~s good track history as indicatd by it's ¢Onslstent appearance in the Datapro Honor Roll.
Furthermore, the fact that IDMS followed some industrY

12718~3 - 91 - Ca~e 4790 standards ti.e. CODASYL), was considered to be important.

DBMS Components The following components of IDMS a-re needed for the implemenation of the system (Figure 12):

; IDMS/CV: This is the Central Version of IDMS, whlch also includes the DBMS executive.

. IDMS/IDD: Thls 19 the InteBrated Data Dictionary, whlch drlves the entire system.

. IDMS/OLQ: Thls is the Online Query, which provides an English-like online query facility.

. IDMS/CULPRIT: This is IDMS's own batch retrieval system for produclng batch reports.

) . IDMS/ADSO: Thi~ is IDMS's Application Development System, which is used to develop onllne Appllcation Programs.

. IDMS/UCF: This is a Universal Communicatlons Faclity, which allows ADSO appllcations to run under any teleprocesslng monitor without alteration.

~Z7~343 ~ 92-Case 479n A CRITICAL ASSESSMENT OF THE SYSTEM

From the foregoing it will be seen that the benefits of the system to the various User ~roups and discipl,ines within an offshore engineering construction 5 Organization have been clearly shown. Managing large-scale Finite Element Models of o~fshore structures is no longer a chore. The system now makes it possible to design sa~er structures at less cost and in shorter times.
1~) The system database is schematically re~resented as a data structure diagram in Figure 13(a) and 13(b).
Link Records are shown as dotted blocks in the Figure 13.

, This schema along with the following schema J 15 listing utilizing the schematic of Figure 13 details the system sufficiently to enable one skilled in the art to construct the present system. Certain modifications and improvement6 have been deleted herein for the sake of conciseness and readability but are clearly intended to 20 be within the scope of the following claims, As an example, although the database has been described with respect to offshore structure modelling and design, it could just as well be applied to other applications such as aerospace vehicle modelling and design, 25 shipbuilding, etc.
.

_ W 1~ 0 ~ (1~ 0 0 q r.~ N r~ ' J N , I V
6 ~;

cL -- r~ r~ r -- L'. L'\ U~ L'l U. L! ~ ~`. C~
"

.
.
W W ~
O O O

,_ w 2 L'l Vl ~ V L1 _ _ ~ o _ _ -- -- _ O
C ~ W C~ .` ~ O C~ C q ~ -- C
L, .. . Lr ~ ` ~ r ~r > ~
U~ o . r Ct ~ ' C ~ Vl T Z ' <r~

. N . N

_ ~ ~ V

r c W ~ . w O ZO 1 Cll O ZO 1 0 ZO
n ,.

' ~ ~ ~ ~ ~ J ~ ~ W W J L~
Vl V CL CL CL ~ CL eL C CL ~ ~ zO zO C CL CL L V V~ o 1 w ~ o o o 8 0 0 0 0 ~ 1.1 ~ 8 ~ o o w, o ~ w ~ .. .. . .
'o ::
W ~ W W ~
o ~ ,w o z ~ o .
8 ~ ~ m 8 ~ ~ ~ ~ J g _ w . o ~ 0 8O,-- 0 L~ 3 cc ~ _ o L. o Ln z a~ :~ -- o -- ~ L' Z
. .... 3 . .3 3 ,, z , , , ~, Oz . . O ~ W ' -- ' ' . O T o . C~
z ~ ~ J 3 cc w ~ J c~ w ~ z ~ , z c z o w w ~ w ~ c~ z o w z ~ v~

Co CO O Co < --~ W ~'1 0 0 ~ V~ IL CL ~ W Ct ~n IL J IJ ~-- L'. Ct Ct Ct Ct ~ -- V~ Ct Ct Cg Ct T
X W L - W W i ~ O O O O O O O O O O O 1~ 0 0 0 0 W Cw Cwc Cwc ~ CC CC CC Ct J i ~1 ~3LZ~8~3 _ r,~ 7 r~ r~ 7 r ~1: r~ r~
o r o~ r. ~ r Ll u~ L. u L- Ir. ~ ~. r r r u~ ~ L. ~r~
r ~ ~ r~ r r~ r~ ~ r ri r t~ ~ r~ r; r r r r~ r r~ r r~
L'~ .

o w OJ
<
~ zo Q

W
~ rn ~r-- n -- ~ -- ~r r~ w c o ~ o --_ g c, c,-- a-L ~ L'l > ~ ,: L^

O~
::

w i .~ z o i .~ 4 a; c J ' -- < ~ ~ c~ ,.. o -- c O . ~ Ll L~ r-- ~L -- O~ ~ 71 L~ L'~
Z i i i -- V l.J -- Z -- -- r W O~ Lo ~ ~ W ~- ~ X
.
r r - O O - -- O O O O O O
~ o ~ 8 9 . o o . ~ v 1 .~ 8 ~ .~ 8 --o U ~~

~n z C
w ~` ~w ~ O w L w L Z J w ,~ Z C
0 4, z v ~^ n ~ r~ ~ ~ w , ~ C J ~Z L~l w w w i ~ ~ t:l ~t O~ _~. V~ O L ~_ ~L ~- ~ J J w -- _ L Z ~ O
r, W w--J ~; ~ .J Z Z Z Z Z o o L~ w w . ~. J ~ ~ ~ J w -, ~ O O O O O O O C~ 0 O~ ~D ~10 ~ ~ ~O ~ O ~ ~ I O ~ ~O r ~. ' ~27'1~3,43 r~ r~ r.~ r~ q Ip r~l ¢ ~ r~ o~ ~ ~ r~ ¢ rL~
' 1` !' '' ~ î C 0: r. r r~ r. ~ r ~ O

c c o c q ~ r r o~ rJ ~ ~ ~ r. ; r _ O .

~ w .
tr z ' cr~

u~

o J Z W
J ~ ~ , C
Z ~ ~
O O . . ~ ~ < < -- O ZO <

C~ < <<<<< C 1<<<<
z aO vi ~ ~ O O za 0 ~ O zO ~ t v _ 0 ~
ol~o800~ ~ 8 ~ o ~ OOoC~00 w~o~ooooo , Z ::
e z > o W O--W W ~ O W
o ~ . r~ ~ ~ o O -- ~5----O W
c .
Z Z ~ o o O O ~W W D T W
J W I I ~ < O W W V- ~ 0 1- W
W W W W ~ ~ Vl W < W ~ ~-- W ~ ~J ~ ~ ~ Z ~ J Z ' ~ W Z W
~ ~ W Z W t- I g ~ ~ < I ~ w W O ~ ~ 0 ~
-g-~ . < ,, z ~Z< <~ ,o~ ,o~a~o"~z~-_c~ ~w z ~ w vl ~ c z ~ o o ~- ~ 8 ~
r,~ t~ 1'71'~ rr~ ~ ¢ r4 m r4 r,~ rrJ rr~ ~ rr~ rr~ r,~ ,r~ . W w w W O _ O < r~ r~l ,r~ r,~ ,r~ r.~ r~
OOOOOOr4 rrJ r4 0 0 r.~l rrJ 000000 ~ OOOOOOOO

~,~

-~ 7~43 ~ m m ~ r ~D

~ --r, ~.--L~ r. r .
V

J
J
W ~ ~ o ~
~: g _ .
~ ~ O

V ' 11 , U `
O, ~ , 0 ~ ~ ~ _ _ I W CO 7 r/ ~ - 7 V - ---- ~ ~ m m ~ m ~ _ r~ o ' C~ a O ~ c --C
~' r ~ .
C ~ O ~ I

U ' U ' a~
~ W . ~:
-~: æ -~:
W W
Z . . . ~ :
. ~ W
U U Z ~ J
rO 0~ . . O
.. .

WWJ ~ ~JJJJJ~J~ , WWJ JJJ--~ ~ C'. ~ ~ Z ~,, V V~ ~ ~ ., ~ ~^ V~ V~ ~ V O
W~O 00 ., .. 0000000000 W~O~OOOOO
:: ::
W ~ . . .
~:: ::
Vl g . W W Z
? ~: Z ,, ~ z w a--w w ~ o w r o--w w . o w o r~ Q x ~ ~ c w ~ ~ ~ o --g 1 o v~ O t~ v~--o----:~ w ...... . ...... .

._ . ...... _ i ~ O Wi ~1 ~ O ~ W ~ -- ~ O -- ~ t O T ~1 _ .
WV~ ~ 1 I w ~W ~,W ~ ~ w v~ ~, C ~ , w Z--> J Z ~ O~ w ~ ~ 2 Z, O w ~ v ~ Z o ~ Z v ~ O r ~
oo~o--iv~--w V~-- I y Jl-~Jql~l~wJ tOC~O--ZV--70J'-:'XW
OOOO-_W-~ ~Vl Y Z ~Z80w~tv~ OOOO~-W~YV~LOOI-~
U w w w o--U < rl r.~ ~ 0 3t r~ ~ r~ ~ ~ r~ r~ w w ~ w o _ U ~ rl r r r r r r~
J~-OO 00 0 ~ 0000000000 ~ CtlYJ~-OOClOOOS-O

8~3 r ~r r~ T 0~ ~ 0 r~ r~
J
_ _ Ln tr ~ r ~ r r r~. r r r: - r-v. ~.

O C
o . J
e e rw 0 rs z v, c v. r r ~ C
w ~ w v, v .
O O ~
rr--0 0 _ _ ~ 0 ` 0 C C
c v, C~ ~q > ~ ~ n. ~ v.
r~ o rq G
~n 0! ~n r r~ 0 w ~ r~ Z
Z ~ ,_ Z
r~ rO r~
r~ D r~ Z
r~i . w r~
r~ ~ ~o r.~ o -w r Z 0 2 rlr y r O ~ ~ ~ ~ rt w r~ ~ J ' :~ ' Z J ~ r~ Z ~ ~ ~ ~ w~ v~ w c c ~, _ ~ _ C ~ ~ rz ~ J w w '< c w~8 800 w,o 808 8 8 8 8 8 8 uo :: ::

J Vi J V~
O 0 ~ rs IL ~ o r.) ~ rs o--u~ w ~ o w 1- Q-- ~ w . o w O ~~ g x C 0 1' W W r~ 8 X r O ~ W
c--~5 ~ o v 0 IY ~ _ o - o 0 0 r~
,..... . ...... .
, ~ ~ v O ~ W . ~ O T o ' C 0 w ~nr~o ~- w 0r50 w- o w Z ~ w ~ Z ,XZ r~ IJt r Z ~ n xZ w w Z -- Z ~ Z , r~

~ ~ U < ~ ~ ' ~ r~ ~ r~ < Y ~ ~ r n w 0 rn z Sr ~ .

~271843 O O ~r V ~ I ~ ~ V
r~ v r~ -- r.

r --r r, r r~ r~ r rl --~ - q ~ O) C~ r~ C

W . ~_ C~ Z
_ ~ O
V
O
O ' r - ~0 ~
V ~ ~ r 8 ~
~ ~ . a C ~
tn .

o ' ' a~
. .
V ~ g g "- .
J

y V ~ ~ ; r~ I 1 r _ r o < w ~ ~ 8 ' o ~ o v~ v ., ~ Z,~ ... ...... oo o : ~ ~ ~ < ~ ., wv '~ Z C ~ Z Q o ~ ~ o ~- ~ r ~ ~ h r ~
~o ~ w ~ 8 8 0 8 8 v o o v v 8 v v 8 o o v v v u ., u o v v v v v a z wg w ~ "
~V V~ ~ w~ w w g ~ ~0 3~
wJ V V ~ i ~ 0 W
O ~ ~- w ~ O O V ~--g - r7~ 'r~ w '~ w X ~ v O w 8 o ~ ~ r ~ ~ ~ O
w g --O O O C z w .,,,,,,,, O
......... z .
.. ...~ . ~ O
~ z ~ ~ w ~ ~ w V
~ w _ ~ rO ~" ~w , _ wO ~ ~
Z O C~ Z ~0 jU ;~ ~ w r~ j~ Z Z O J ~ w w 1 ~ ~ _ ~ Y cr Z ~ ~ c O O g O ~ ~ < _ J ~ o ~ ~ Z < 7 W O ~ r _ ~ r O z ~i~ z rJ _ _ ~ ~
~J v v v z _ uO I ~ v O o o o 2 2 2 o o a~ ~ G i~ 2 o o o o o o 8 G o o g o o o .sJ

-,~

~27~8~3 v t V ~ 1 ~ v v v ~ v ~ v v ~ v 'J v ~ v v v ~ v ~ ~D v ~ I v .
r. ~ e r ~ . r~ o r ~ r. ~ r 1- - r : _ _ - - r; ~. r~ r. r - ~ r. ~ ~ r.. r~
_________________________ ~, _ r z V ~

o J
C~ C ~ C W
. ~ c ~ -- r r ' .

_ r z , O
l_ 0 ' Q
r~ ~ S
~} W ' J
O
V ~ ~ o r r~ ~ w ~J
O O O o c w Z
J, , ,,,,,,,,,,,~,,,,,,J,,J ,,J , ,_. ~. ww _oooooooooooooooooooo oo_ooo_oo ZOO1-~O
O U ~ U ~ O U ~) O ~ ~ O ~ U ~ ~O w w . r~ r r~ . .
c e S w w c J ~ 0 :E Z O ~ Z
W t ~ ' ' ~
8 8 ~e ~ ct rO ~ O O O w C S-- ~ O "~ Z _ _ _ Z ~

w ...... ,,, O, ~ z r r~ ~ z w w v w r~ o o (Y z v7 ~ z o ~ ~ w ~
C~ y y 5 ~ v ~ z ~ z ~ E 3 ~Y Z zo C ~ N 1~ L V~ r O O O Q O O--Z C~
w Y ~- N >~ ~ O O V V ~ J 1~ 0 0 Z J ~1 0 ~ ~ 01~ ~ tt r~ r~ tY E 1 0 ~ N 7- N 3 ~ w w ~ V--1~ O O ~ m Vl O Vl ; O V V V Z Z O ~-- J w r~ r~ ~ rl rl o rl r~ rl r~ r~ r~ > r~ r7 rl w w w w o c v c r~
0000000000000000000000000000000 ~ 7r. J~ 00 i27~1843 `~ ~q ~ ~ 7 ~ q 'J r 7 ' `~ ~ oD ~ ~ ~

-- r'. ~ S ~ q 11 ~' ID ~ Cl 1' 1` 0 '` W ~ O- O -- q m C ce O

-- -- -- ~ 0 ~
r~ ~ r o c o ~
U-1, o ~, ~

z tD ID 1" 1" ~D
l- J
w w ~ ~ r~ r r w ~,~
w ~ u u u u u ~ o w z ~ J J J . ~ . , ... I J J J . ~ . W W
o'^z ~ ooo~oooioooo___ooooo w~ ~E rE
0 0 O U ~ U U ~ U U ~ U ~ O O ~ U U ~ ~ O W ~ ~ U U
~Y W W
U t.~ W 1~
a 3 T W W
~ ~ - O O O u ~
v O O r -- -- r ~ O
r --O > O ~ Z ----Z

. . 5 Y Y _ w o ~ < Y ~ _ ~ o ~ ' _ u _ Z ~, _ 5 g o ~ o o 000 0 00 oo80808800080808000000 ; rW ww - ~o_~ uqO O

i.2'7~L843 -- N -- -- r . T
J
~. O c ~ ~ r> r ( r c ~ u u~ I c u. ~ u~

O Z
u o w q o " c~ ~ c L~ O~ -- ^
C~ --G-- w ~ C
0 0 ~ o r c~ :
.

~ 0 ~

c,~
W ~ J
c ~ D ~
. w g tr ~ g c w ~.1 g W W t. ZO O ~ O O O O J U o O O O O O O L, Z :1. V l O

> > > > _ O > W ' <
Q O O O D ~ O O O t~ CL ~ ~ C ~ ~ W IL 0 ~ C 0, ~ ~ O O
o ~ o o ooooooo Z~o~ O0 W W t~ L~ ~
--W ,, ~ W
W < ~ W W
J ~ O ~ :1 0 g _ ~ ~ ~ U ~ W V~ L' o W
O r. g, O o Z G o D w W

C~ C ~ ' Z' ~- v- ~ , , D ,_ ,_ ~ o , ~ t~ . o J W
Z V Ct _ -- J L' O O O ~ E o L Z O t~ E WU W :E O ;~
C W Z Cl: ~W o Z ZJu.~OZZ<Z OOOO~Z_Z~ ~n ~ VI~UU O
_ w U O u~ ~ ZO UO ~ U--W W O ~ ~ O 0~ g O O g----< I ~ V- ~ o Ct O J J ~5 7 ~ OD - 0 0 0 '1 ~ ~ ~ 0 N 0 ~ N W W W W -- -- O -- < D 1 ~ t`~ ~ ~ 0 0 O C~ C~ 0 ID 0 ~ 00 0 0 0 0 0 0 0 0 0 ~ J ~ S O O O O O ~

~Z7~843 s ~ Q q 'I T ~r ~ ~ a~ n 7 ~
J ' , ~
L~ t~ r: r ~ --- L~ ' 1;.1` L'l G~ ' _ _ _ t~
L~ Lr~

C
J
J
tt O Ct U U
W ' Z
U ~
V- t'~ Vl CC . _ O
O U " O-- O L' C'-- C O C' 10 C' ~ -- -- u e~ _ t~ _ _ _ _ _ -- O ~ -- C ~
t~ ~0 _ o, U ~ ' ~ U ~
~- O ' I , t~ Z, I
V tC ' U
O

O ' - ' -- W ' J ~
w 2 w t~ t~ ~ w U ; i U t~ w O O O O ~ ~ ~ ~ O O C

< ~ ~ ~
CL 2 ~ Z Z _ ~ O U O O

w w ~ 2 ~ ~ w Z ~, ~ 8 ~ tt r O U 8 U U o W
. . . ~ Z ' . ., . ~ O
, . . . - - _ ' ' z tc ~ Z--> J z ~ ~ w o z w w r- z O ~ J z, tt 2 zO Ct 1 ~ tc w O o o o--i V7 _ ~ . Ct tt cc tt ~ --a 1 W L~
N N . w w w w O ~ 0 t~ ~ ~ . O O O O a :r w - y ~ o O r-lX71843 -- - r, _ _ _ _ _ _ v v v O
J
c w w ~
o o o o z r ~, v v w z w w V~ o . ~ O ~ D Z
~5 X:
.~ ~ . c ~ ~ ~ r.
r.. o ~ o ~

c~ ~ C ~ C
~ . ~;
_ r , ~ C ~ Ul O
W ~ . _ ~ V Y ~ V
J Z ~ J ~ W W ~
O V ~ O ~ V ct o 0 ~1 r~ ~, 'r- 1 1 w 0g , O . 00 ~ ~
_ w ~, ~ . r~
w _ D Z ~ D Z ~ ~ ~ D Z ~ w V- ' Z

~w ~ J w v ~ r O zQ c c i w~80 ~ o8 8 ~ ~ 8 w, . w:: ::
~ .............. ~ ................... ..
<

~x~ _o ~ox o O~~=OO ~O--ww ZO ~ ~ ~ ' , Z, ... . - O

o ~ ~ ~ D Z ~ ~ Z ~ Z ' D Z D ~ t 8 ~ ~ o ~ ~ ~ . ~ v ~ ~ ~ ~ ~ ~ ~ = , V V V ~ ~ t ~ ~ V
~' `~,~, ~2718~1~

r~ r T r,~ r~ r.~ r~
~ . o . o - o .......
c r c~

O ~ o o C ~ ' W ~- W 1- W _ ~u o ' Z~ ~ ' ; t~ ZO
L~ ' -- o _ o -- o -- -W W W U
' W ~ W 7Z U
O ~ O L~ o o X W ~7 W ~7' W ~7' ~ C -- C --O ~ O ~ . W ~-~ 7 c ~ m r ' ~ ,~ , "
-- C ~ --O ~ -- O ~ -- C C "
U 3 ~ _ o ~- ~ ~, L L~ L7 L'. ~.7 "71 . ~7 ~ . m o .
8: o: ~ ~
.
W , ~ w : , ~': . , U
o .
g : g : 'o 2 , _ o _-- o ~- w ~ ~ W _W _ W
o ~ o~ : o C
C W ~ ~ WU ~ W ., C W
o . w o~ ,~ o o < w o Q .-~ ~ r7 ~ Z ~

o C ,w, ow W W W W
w ~ U w 3 ~ w ~ U w ~ U U U ~' .. .. .. _ ..
< < ~ ~, ; ~ -7 ~ ~.7 a ~ . J -7 o Zw o Wz o Zw W W ZW
O C~ 1~ W O ~ O e~ ~ U O r.J 1~ ~ T O 1,~
0~ o O L7 0 ~ W W ~ o W ~ O--O W W o Wo ~7 o 0 W Cw 7 o WO
o _ w ' m g----o z w O _ g ~ O ~~ Z c o--g ~ o 7 C O
.7 . .O, .,,,,._, ,..... _ .
V Z ~ U Z U Z U
o w - _ _ o ~ _ _ wO
O W ' ~ ~ ' L~ ~ O ~ W~ z ' c~ ~ J ~

T W _ O O O O ~ W L7 ' O O O O 7 W ~ J . o o o o a ~-. ~

127~8~3 ~ r~ q q q q q ~I r~ q r~ r~ 0 r~i q 0 ~ . J
~ - r~ r r - ~r. r) I o I ~ r ~ -- -- r. . r; h ~-- 0 u~
v . ~

. ~ w ~r Oz~ 0 ~, r v ~_ . o '~ ' U
Z z o ' w 0 o v.
h -- w O-- ~ '~ C
. r ~ ~.. v. . v. ~
~ c . -- o ~ ~0 ~ r. S 2 g ' C, . s O, o a z ~ v J
Z ~ o ~ o ~y I
v.
u~ ~ v l_ 0g v J . -- w ~
v 2 ~5 n ~ o v~ v.
2 0 a w ~ o o v~ z ~ v~ O ,~ _ , v w c ---------- -- c ~ a a a à vz vJw ww~ J~JJJ
Z :! Z Z Z S V~ (~ ~ m ~ Vh n vn, v~, n V~ V7 vo QoB8BBv V~B o ~' ~o~ ooooo z :: ::
. . ~,. . .
ZZ, J
W VJ ~ ' VJ
O ~ Z o s . z VV o V~
o ~ Q ~. v~ aw- o u o--O w v . o w ~ o--v w 2 ~ O v o R o VW~ z r~ oo ~ o R z ~vu z r~ o u. ~

O V~ ~VY VJ ~V J Z ~,) Z ~ z 1') '_) - 1- ~ 1- :- ~- 0 V~ 0 V~ --~- O
C C w ~! v~ Z 5 v~ o z ~j v~ :~ ~ v~ Z e o X ~ r~ / v z ~w wJ z vW2 w ~ O D ~w wJ z vw w Z w ~- . z O w w ,, 1~ v~ ~ v~ ~- O D O O--i v~ _ O o O O O O--i vU--Z o J 7 ~ w O O O O--o o g w o ~ O O ~ c z u O o o o c r w ~I Y v~ v O o ~ ~ ~ B B o ~
oc~ooood : v~wvwv-w'vuJ3oo 0 ; VJ~w~w~w~Jo3~00oororooro : Wtwt~wC~J
,~

... . . . ... . _ . .

127~8~3 ~ r N S 7 N I ~r ~ .^) ^7 - r ~ n o o (^
t~

.
w o J
rwô ~ rWô, r ~ z w A . ~A . rA c u . v . v, z v~ o o w o u ~, v ~ vA ~ u o . ~A o o w c r - w 7 r~ ~ ~A 3 o-- ~ A^~
r^ ^; I` o r C - _ ,,p , V 2 ' r~ ^
C ~ , W ~
" ' V ~ ' ~- . . ,_ U ~ < ~ U,~ U, u a ~ u ,~
g ~ AA ^ ) r ~ r~ ^ O
- w 8- 8 W J ~ t r~ ~ O ~
W ~ ~W~ ~ Z W
' O e ~, W ~A W~ C~~A W ~ A
O ~ ~ O ~0. ~ O O ~ < W 0 ~0 W

W W J J ~ W W J ~W W ' J J ~ W
< ~ rA ~A rA A ~A rA V~
c< v~ ô ~ _ o r ~n ô ~ ~ O ~<
wA~oo o w~ov w~-~ vo ou w < t ~ ~

' ~ < ~^ O ' 2 ~ W W .
-- '-- 'W i-- O ~ A O O ~ rA
r ca ^7 ô ~ A c 8 ~ A o " ~
~ZA w. 2 g ~ ~ ~~ ~ 7 ,. r~ 8 ~A ô v~ z ~AWA ~ " ~ ~ O ~A O
'A^. ' ^7 Z ' O

U i U i 'U ~^A ' Z -~
~: :oswO :~-: a o wO ~- ~OA AOArsAwo W ~ ~ 0 r r^ g W ~ rA y O y ~ 0 AW ~J o, ~ ~ ~ o Z--~ .7 o ~ ~ W ZO ~-- r ~ Cz C W W Z W
Z.^-W;J ~ @@aa zv.-~tl . a@@,o,-z,,- ,-~ "0~ ~ ~o~oa@~
_wu<v~o~ UV8v~ UW< vv8var-v-- : vUv8-_Wu i-~aOoo ~ a~J~<OOO : WW~W~WJ~oro oo oo WW ~o~ v !

~71~343 _ ~ r~ r~ 0 rc 0 ~ I r~ q N . _ -- V r~ r~
r_ _ _ ~ r- c. L ~ c -- -- r~ ~, r r- _ _ L7 t~ _ L,, .

o ,J , C
w w r~ o w rJ
tL O tL O ~l7 ~u O t~ - - - a ~ t~ rS o~ ; C ~' ~ C
t. ~ Lr ~ , t, ~ ~ ~ Cs C t~ L~
~ O r. c~ .
--q 1 ~ - _ w- :E g < ~ U ' _ ~ W
_ r-- O ' ~ Z ' ~ I
OV ~ O ~J ~ I~
O
0 '' r~
LO ~ w o : 8 ~:
_ W ~u ~
~ o Z
,.................. ,., W J C ... ..
~ o ~ o ~
tJt :~ , , ZO
'~: '':
w J J J J J J r~ w w J J 8 w w J
t5 C r tL tL r~ vl ~ , c 1 E L~7 0 0 ~ ~w tr L~) O O O ~--~otJooooo ~ w~tJOtJ tJ O L~ w~tJ~tJ O
:: ::

~ . . .
Ul r,~
J O ~ W w ~- ' Z
r~ ~ O-- L'J I O W O O L'~ L~. rY L
L~ L~J L'l O--~ O L1J L~ L7 0--_ tg w tr r~ r~ :~ r~l 2 C SL r~ L~ L'~ Z tr z z . r_ . , , ' ~ ~ t7 O T W -- -- O T W
,.,w ", v : .'~ o t~ w r~ ~ 8: ~: c :~ O . ~ tr 2 Z ~ J w ~ tL Z ~ O w Z t~ -- -- Z W> WJ Z tWr W Z ~ o zv "~ Z _ ~ J Z tr LV O ~ W
--Z-C J >~ W O O O O ~ Z L7 ~ O ~- rJ J J O O Q O ~ Z ~ ~ Z Q O J
'I Y ~ w O O ~- ~ o o ~o g q T 1'7 I r'7~ 0 W rJ -- O O O rO ~ ~r LV <I ~V Z Z "
~ r~ r~ r~ r~ r~ r~ r~ w w w w O--O q N r~ 0 0 r~ w w w w C~ C ri r~ r~ r~
oooooooo ~rt~t~J:~ooo~ r.~ O C~trttJ:~COOOO O

~ lZ71843 _ ~ 7 ' _~ ' ~ .
~ _ _ ~ J
CL C~ .
~') V

' O
O ' O
J . <
~ O W

O
W W W
O ' O
~ X: ~_ V l,t~

W ~ U
~ ~ W ~ o W
" -- ~ W ` ~ W
~o Q

~ o . . 8 U ,, , ,U, j ~ ~ Z
o v 8 ~ c ~ W ~o W
8 : - ~ : - 8 ~ . J ~ . , W
W W , W
~5 Z y : o U. ~
W
O ~ w O Q < w U O ,0 Z
- O _ Z
W WW -- ~ W W -- ~. W
Z O ` ~ ~ ~ ~0 0 W
I~ W ~ V<~ w ~ u u ~n ~ w ' W WZ W W, ~ ~ W W ' W W
z ~ 3 .~
~w w --w V ;~ ~ 0 Z w _ U G Q z o W W W tt-- W ~ U~ . U V o C~ ,W, C ::~
v 8 ~w . c ~o o ~ o ~--- ~W ~ W! ~ Z ~, w g ~ ~ w . w v~ o w .0 --O w w (o O < --O < O O ~ w ~ I~ O < --o e G C~ O
,.. ~ ca ~L~0~ O~Z-_-ZC~ W~0~ O.~Z---o , _ . , , , . . ~_ . . . _ . . . . , . _ . . . _ z : o :: z:: w:: vw~ ~ :: ~:: 3:: ~ v O S Q ~ ~ - ~ 0 ~ a o - . ~ w ~ lr ~ Z O ~ ~ w v~ W ~ o a lQ Q ~
< o w w. w ~ ~ ~ O ' ~ w :I zO Q ~ O ' ~ C~ ) tt ~y ~--Z 1~--W W . ~Y CO~ ~ Z ~ ~ W o . t~ ct ~
88-~uW-~ J :8~88-zza~SJ ~W-~ U :88~8-zza-J u ~yaWoW~aWO~yOO O ,W~W~wyaW3~o~ UaO O : wwww-_O_< U

T ~ ~ ~ 718~L3 ~
-- -- r. L'. _ --_ -- -- - r~ ~ -- r. ~ ~ ~ C V G r L

O
O

;` ~ C
j~ W
~I ' U ~ W
~,~, L~
W W
~ ~ C ~ ~. C, ~ ~ C C ~ C
C V` ~
C~ ~ O

U
~- 0 ~ 0 O~

. rl ~ S
U~ ~ ~ . W
8~
~ . W .
W" W

<~ ~aO Zo-', " O ZO ~ ~ " '' Z

8 ~ o ~ G ~i? ~L
~,88.,88 8~oo w~~ 80 8 v 8 o .

z~ ZW W W
~ W W . W~ --W W ~ O W
G 0 80 ~ ~Y w- o 8 o ~ c w~ o g _ _ O w ~o ~ 8 o v 0 ~

- . . . w, I . . o Z _ - - - ~_ Xo T W wl J ~ O T W
W L~ ~,7 0 ~ y W J Z V' W V 15 0 ~- W

' ~ O-- ~ ' ~ Z ~ J W--Z lU Z ~ ~y Z ~ ~n ~
w~,w~ zow~z ~WovwoTwJJJJJw zo~wJW2 ~W~Wo zw ~ ~ w ~ O Z ~ W Z Z I J J O O O O w Z V~ W ~ W ~ ~ Z o ~ r - :8 8 8 ~ ~ ~ ~ ~ .) 8 ~, . ~J ~ . ~
~D O O o W W W W O--> e r~ c rO O C~ r r C~ C r w W W W o ~ ~ o o o C~ 0 V0~ W C

~~" 1 Z7184 q a~ q q ~ ~ ~ ~ ~ r~ q ~ N ~ T q r~ r~
r . r rw ~ r o ~ u~ tn L~ r c r o c.
c~ ~ ~ r. ~ ~ cl ~ Q c r~ r. ~ L5 r~ r u _ r~ ~ _ _ _ _ _ _ O
q~ C L~ - C O C O ~C Q _ V C~ 0-- O C~ C~ ~.C C~
., . . L~ L~ . L~ L~ L~ C . L~

. I
8 0 r I
u o ~, J ; W r ; w Z W ~ L Z O o oZ ~

3 ~ 3 oz ~ ~ o 3 ~o ~o 3 3 3 3 ~ o ~o ~o cc 3 o 3 3 3 3 ou o~ u u ~ ouuoooo~uuu w~ouooooo Z W . ~
o W U U o W
L' 1'10 W 0 L'~ o r.~
o , .... o .
-- . W O W O ~ LA Z U
z z z o Z z ~ ~ u c o cc t ~ Q r~ z ~ ~ ~ c~ c 5~ c~
-- WL~ ~ ~ < ~ ~ K O ~ ~ < ~ Z ~ O O ~ Z ~ r w w 0 0 r~ 0 0 0 51 0 0 O O O rO O O g O O O ; w ew~ rWC cwC ~ ~ ,U~ <O O O O g O O O

, ' , ,, . . ~

~` '12''718~3 ~ r r~ q J J ' ~
--r.
v ~ r :
r o, w ~ ~
~W5 @ ~
~L o . ~ o ~ o ~ r ~ ~ a ^
L L ~ ' _, _ --2 C~ ~ 8 3 8 u ~ u . ~ u, . u, r-l o u ~ o u ~ o u . I
~ ~ r~ ~r~
C
!,e: ~ ~p <~, O . w .
~7 o w ~ ZO < ~
z. . o z ~ w , w . ~ . o c zo zo ~ c c v~ z 2 ~u ~ V _ ~ ~ U~ _ W ~ ~n _ o V~ W~ o , W~OU U ~ W~OU U
, : : : : : :
,, ~W ::
:: . ~ . ~ . .
W ~ o W ' o wz W ~ o W
W 2 O V~ L o ~ o IY L ~ O o Vl w o 8 _ _ ~ wG ? r~ 8 >~ < ~ w O g _ -, O w ", , . . O V~ r~ 7 z a D ~ Z ~ O
:: 3 s w _ : :: D w _ W D ~ w a w V~ ~5 o ~ ~ w V o o ~ <

. ~ z ~ Z q~ r Z ~ ~ ~ U
z~--~ J z ~ aW ~ C~ a z--~ J ~ . ~w C _ D z ~ ~ J z aw ~ _ a~or~a~zV~-wJ . a~oao~ . a~oaa~
888.. , u~ : 8888-~ua~ a 888uu ~ ucy--wwwwO--0~ ~ wwww~--U---0 W ~ WWWWO~U-~r,~
~a~J~ooo ~la~<oo~ at~aaJ~-12~8~3 _ q ~ q N r~ r~ r T, ~ ~ _ r~ r~

---- u rr ~ c. _ -- L^. c ~-- r ~,A L', o o , O

W ~ W -- W ~ _ ~ O ô ~ ~. r ~ ' z ' z w U ~ ~ L^ W
0 ~^. O r~ o ~
W o _ _ _ -- -- _ ,~ L~ C' C -- _ r ' W --L~ . L~l ~ . L~ L ~ L ~ ~ _ r~ 2 , , 3 . r ~ .
z . , 8 ~ w~ ~
~ ~ ~ 4 a , ~ z r-l rD ~ ~D
W J D ~ W ' . W
8W '~ . O _cW

3 o w ~ Z ~ ~ w --' ,8 'I 3, , - i o ~ o w w o w o ~ v E-- -- ~
W ~ 8 ~ 01~^ Z rA~~^ o w o ^. Z A n ~ ~ ~ ~ Za Zo .
.... c .

~ ~ 8 _ ~ o o O o O n ~ ~; y ~ ;

~27~8~3 J
r. _ -- r. ", o , o ~ . u .
o ' o ~
X: X
o o ~t a^-1,~ 0 o ~~ . O, o 8 . Q c y ~ o V ' g~ ~ . T
~_ ~ 1_ 0 ~-.

_ "
.5 : ' ~ : ~ ' w ~ a ~~ w 2 J ~ u o o o Zo < O ~ o Z ~ ~0, 0 4. ~ ~, .

o ~ -- o .
7. w w ~ w w ~- W 1~ G g ~- w ~ g 1~ g zgc--2~Zooo zoo--a~o30 ~ ~0 ~ w ~ U O ~ 1 ~ w ~ ~
~ a ~ ~ a a a a ~ a a a z o o w ~z o o w ~ u < a a < ~ ~ ~ < a < <
~ ~S~ a ~2~0'Z WJS~ ~og~O~z ~WSs O
8 ~~ o ~ o ~a 1 t ~ ~
o g ~ a ~ ~ aW tO ~ ' W W :1~ 8 ~ ~ _ o < o O 20 ,o ~ Ul O tt ~ r~ a wO
~ ~ o~ --ot~ ~ ar~ ~ ov~Z--__Oa ~ a~ ov :: ;: C ~L J ;~
o ~w~,~aw ....... ,, O, .....
-Z v~ ~ g vlz w _ ,_ O S ~!u wO r W ~ Zo S ~W w aw ~ O S ~ w ~ ~ a v> v ~ ~ ~ a . _ . . ~
11 0 ~a Z a tY ' ~W~ W ,2 2 ~ O ILYU Z a a ~ W 2 LOU C < ~ O ~Y ~ a aZ ~ ~ J Z ' o w - - Z--~ J Z ' O t~ W L~ Z--~ J
0 ~ ~ Z g ~ g g~ ~ o o o o l 2--i g ~ J tO o o o o Ct lY a tt 2 2 tL t~ a a 2 1 -- vl o o ~ ~ a ~ a a 88~zioS~ U~ 88~ZZ~SJ ~I<a~ 88----<~
ttwt~wt~J-ayOOOgg twtgwatw~J:l~a ~OOgO tttWt~t~u~wt2~J~

S r- ' lS ~ ~3 C, V
. .
, :
W W W
o . o . o .

W ~ U .
o . , o . o .
,,, U V -o . o o .
W ~ W
~ ~ e~ ~, G 0~ ~ ~ r ~ o e r, ~, _ O . _ O .
~ 1 0~ .
8 g .
_ . ~ . ~ .
U ' ~ ~Z ' ~, . ' u . 8 . . I
~ . In ~o .n :
8 ~
8~: z o: -- o --~5 o o ,~ . 'S ~ G Z
~ < ~ V <
g ~ ~ ~ o ~ U ~-~ , .
O ~ ~
. w ~ W ~ W ~ ~ W ~ r. rL ~ r. e.
~ g ~ ~ w ~ U V ~ o ol O e~ ~ o o o a ~ u o ~ W W ~ W W
o W ~i o g ~W ~ w w 'Y ~w ~ Y Y~ S W ~W ~ ~ Y Y ~::
al ~ . ,a ~ a ~ ,~
l o wz w s ~ ~ i o wz ~ w 7 u z 5 8 o a ~ r~ r~ o vW~ o 8 c w u m u w _ ~, O ~ ,, Wo o - _ ~ a w ~ w ~ ~ o w O r o 8 ~ 00 ~~ W
~-----Oa ~m ~ o~nZ__-O um ~ omz o 0 :::::: ., z .
_: ::::,::: _: :::: :_ . ._ .
~ ~ z ~ 2 ~J Ic O s ~ w u ~c o ~r ~W W U
a . _ .__. ~o :~ e~ ~ o o O ~ ~ ~ ~W ~ ~ 3 a a ~ ol z 3 e~ ~ o g ~- ~ Jo ~. ao co~ o ao ~ z g v o o ~l o a o o ~ ~ ; Z ~" ~ O ~ o o v. o o O O o o o 8 2 z ~ ~ . " o o o o . ~ ~ Z Z o ~ U--No o o o o ~r.
..~

12~8~L3 I q q ~ ~ q C ~ ~ :
~ ~, ~ C
c - r. ~
~^ ,~

o ~ ~ o o w - Z v~
~ol o c.
W 41 >
u a--a e ~ - c~ o _ c _ o L ~ r > v, _ I ~ _ C
~:: 8: ,g - .
~,, ~ .
Z ~ ~ ;' ~ l I ~
u ~ Q .
~ o C- ~ ~ ~ 2 r 1~ ' ~. ~ o ,_ , . . .
W ~ Z ,1 i' ', C-:! J o C1 d ~ ~ o `!,;,. 1, .

W ~ Jl W W ~ J -8 ~o w~8 o8080 88 ' ' ' ~ '^ v, v, u a tt ct w ~J ~1 w ~ w Q ~ c Ii~ ' w O Q 4 I C ~ O
J Cc'~ C,, W ~W 1~ 40 oWJ t o ~y ri~ ~ ~ ~ 40 o J O--_ r~ r~ 4' ~ .
J1~ o ~ Z r~~ O ~ O C~ ~ D v~
, 2. . . D ~
O S w _O 1 5 ~ _ ; o T 5 w w 1~1 ~Z 0 a': w 1/1 C; o '5 g: '1 : w w V~ ~ 0 ~5 g w ~ ~ ~ ~ ~ C~ Z O t~ ~ ~ ~ Z o ts ~
~1 _ ~ Jw z Iwy Z t~ o ~w wJ r z ~ ~ w zo ~ z ~ ~ ~ o 4` W 4 z -~ O D O O--Z 1~--J D D D D ~ O--Z Vl-- ~ X o J ~ o O O O O O--Z
~8 o o o ~ W C 4 ~O O 0 8 z z o ~ o ~ ~ 8 1. o 1~ r r r 5 Z
8 ;~ O~ fi O O w~ ~ ~ww5 a J ~ O o do d c~ G O ~

.~, --` 127i8~3 .

,~

o : O
W 1~1 :- O
~ . . . ~
o . Z W .
' O ,_: O

O S~ #O
~ O U ~ ~
0 ~ o W
W ~ W ~
V ~--~ C C ~ ' , U ~, o ~O C ~' ~
, ~ _ " ~ ~, _ ~ 0 ,~
: 2. .
V U
g # ' ~D
2 . ol o V o oo ~ U

~ ~ ~ . ~ ~ >, "~ W ~ ~ ~ J ~ W W ~ ~ ~ ~ ~ J
< < ~ V ~ 2 ~ ~ ~ Q ~ ~ 2 w~ o80~uo 8~ wg8 oo8u ~ 8 oo8 8 u8808u~u . . ~ . .
w w ~ ~
~J w w j3 u ~ ~ z < ~ u o ~
' Q ~ _ t~ lo ~ o ~ o ~ o C ! C

_ o _ , . . o S ~, W, U ~ w - W WV '3 e ~ ~
W ~ Z o o~ ~ Z - W ~ '~ W ~ o ~_ Z ~_ ~ ~ S < Z o ~w W~ ~ Z . ~ W ~ ~ Z ~ S ~ o >. _ ~, W . ~ W . J;
V~ ~ ~ w O J w ~ . Q O ~ -- Z O--w w ~. O O J--J ~ lu Z w J tt w O (~
W ~ > r`' ~ ' Z Z ~ O O O ~ ~ O o ~ o o o O O o o ~ O C

---` lZ7184~
T ~ '-1 ~t C ~ ' ~ ~ C' ~ O~ , r ; , 1 O ~n ~ ~

O
W .
o ~ Z o Z
U U~ . ~

D ~ -- D w U ~ '' _ U C - ~ C C

E~
U ~

~ ~ . J g ~Z -" C' Z ' ~ W ; J - Z Z
O ~ ~, W O Z ~ J Z Z

w ~ 1~ D 8 8 1 1 8 ~ 3 ~ z ~ ~ Z8 o 8 u 8 u i v I~ .. ..
w ~ ~ ~

, o--~ a C~ ' ~ O g 8 'O ~ a D ~
O O Zo l~ W Q Vl Z Dt ~ ~ O O--D ~
UUOUZZo'l~U~ UUUUUo-Uu<

~Z71843 , ~ ~ N N I ~ N N ~
OJ ~
_ - ~ r. C ~ r _-- rl r~ r. r~ ~ I
O~ -- r- 0 V V~

W W ~ I , W ., V V ~ ~
Z
X ~ X
_ 1~ 0 r O
r c.~ ~ 0 ~ ~ ~ o G ~

8 ~ . . ~ . . ~ c ~ ~"
., . ., . . . V
~ ~ Z ~ 0 l~ o 8, g W , w o o o ~5 ,5 Zo C
W ~ , .. ~.
o Cz ~ Zo . V~ ~ ~ ~ o ~ _ ,. _ ,.

: . < . .: ~
W o ~ ~ ~ IL 0~ G 1- V V ~ ~ z z 5~ ~ O g W, o o o o o o o 0 w ~ o o u 8 v v 0 W
.

z~ s ~
o v v ~ ~ v~ o vwl o o, ~,~ ~ w ~~ ~ Y ~ 'W~ 3 8 ~< < 8 o C~ - W ~ o ~:::::o: ::::::o: :~ :o ~ ~ z ~ z ~
. w ~ O z O, w 3 ~ ~ zO ~ < . zo z e, w ~
w w O ~ .. w 8 S ~ O ~ u ~ ~ , O O O ~ <~ s w ~IL2~8~L3 r rl r~ e ; ~ r~ r~ r~
~.~
r " ~ r ~ L.
r~ Ir c c c '- ~ 3 C
J
_ ~ o ' Z
C V r V~ rL
3 " o 3 Z -:
" ~o~
.1 _ . . C _ .
.. o - ~, o Z
rs ^ ~ ^ C~ r~ c~ r,l~-- v ~.1 1: ~ - C ~ ~ -- r~ C 1 --r~ L _ G ' --'- ~ _ cr ~ _ ~.`, _ _ ~ Z
W W C ~ .
<I L . ~ I
~ Z ~ L I T Z ~
o 8 ., o ,. . , ~
o , o . . o "
W-- W -- LU
g . _ o , J-- w ~ J -- L'J J
~0 C~ O ~5 o Z~ Z L~
oC ~ ~0 r,~ lu ~' C W O r < W # ~ O O C W

r~ Z

g ~ r r~ n g r r r~ o o z ~ m ~ r rL r~

~ u o 8 v~ w ~ 8 o 8 8 8 8 ~ ~ ~ L~ o :: ::
w w ., _w ., T t ' YrO ~ ~
W J 1~'1 W JVl LzU
W O W ' i-- vlo L~ r~ ri .
W g ID ~0" # C rD L~ O g ~- g > I L'. O
O L'' 'I O L ~ L'l Z r~
Zo ~ ' ' ' Z
' ,_ ,_ Z ~ ~~L ~ ~ W . Vl ~ ~ Z
i r~rr r~ c o w w ~ w z o ~ c ~ O W W W ~ rr ~
U 3~ W Z Z-- ~ J o r~ ~W Z r~ rS Z ~ > J Z r~ LU Z W z _ O J ~~, r r rt _ ~ W ~' ~ V~ ~ O O ,_ Z ~ W --Y
O O C~ C~ ; W ~W ~W~ ~W~ J ~ ," o o o ~ rD rn o ~ W L~U ~L~U OJ '~ o o c~ c~

-- ~718~3 T ~ ~ T ~ ~ ~ ~ ~
q~ J
-- Lq o. o o. ----ui r nl ~- r. ~ - -ct U.~ tc --r. 1 ~
V-.

. .~ .
W - W . ~ .
Oz 0 ~ o L' ~
- ~ O
W ~ W ~ W

O _ '' ~-- o " "~ o~ -- C - ~ _ r ~ - c~ _ r, ~ .

_ ~ T ~ O U ' U ~
v . o ~ ~ . 8 " . o , _ <

5 ~ o o ~ ~ c v o o o o o J _ ~ V

~ ~ ~~ j ~ - 80 ~ o z :1 ~' ~ ~ ~
- Z

~ ~ 0 ~ O _ W -- O - W -- -Z--~ J ' ~Y W ZO W ~W W Z _ ~ ~ o ~ w ~ w ~ ~ Ct l O w W ' W ~

W W ~ ~ ~ _ ~-- , t ~ W ~ j W, o o ~ ~ O C --Z ~--U

~;' .~

1 2~843 J J
--- ^ c ~ . r r ~ r. r r o W
o Z :
1~ C
~ Q ~
Zz ' Z
O ~ U~ o -O ~ ~ O ~
~~r.,r~
o ~ 0 V J __ _ V ~ ~
8 : , wg ~, . , . ~ .
W . ~ J W ~
g : , N . W N
~ W ~ J-- W
~: --z V
W ~,~ ~ W
w ~ o J i~ O N

J : . . .
W ~ O G ~L Z ~i? Z QZ ~ ~ 2 J w :~ o D o o 8 ~ o 8 8 8 8 ., ~o, v o-- ~ J r~ ; ~ O _ o 0 J ~ ~ c u ' ' Z ~ ' ~ ' ' Z ' ~ ' S

aO aO 0 aO a T w < ~ a g g a " S W c y wO ~7 o o a o o o o J 8 8 8 8 u a ~ ~ :~ ~' o O O O a ~r a a ~ o O ~ O o 0 0 0 0 0 ~ O aw a CL a ~

~ ~2~8~3 -- 7 S . T ~

_ _ J

o <
W . W ' v In O ~_ ~' 7- ~.
117 . O -- ' O ' W W ~ W

L v ~
O
C "

O
8~: ~ 8. ~: 8 ~ . ~, . ~ .
Z O ' 15 2 ~ 0 .

W ~ V ~ W ~ ~
i o o w i o o w ~, Y < ~ W W ~ O U U _ W W ~
- wg< Z, ~< :~ a ~g ~stD~
2 _ -- ~ q v W V U o W w o--~ o 30 ~w Z 8 < --o C Z _ _ o 3 W Z ~n 8 ~ o V- _ ---- 2 o 3 .. ...... c _ 3 s . ~ w . _ . . . o T 3~ W
Z o < ~0 3 , . ~ ~ o o C ~ . C

W, S o Z O ~ W ~ ~ z o ~w w Z O w~ w l~ z U ~Y W Vl i V -- O O O O ~ ~--i Q Vl--~ 0 0 0 C ~g 0 _ Z g ~ _ 9 S w - ~ g O g g ~ W ' O O O O O l ~ < ~ J W ~ J
~ ~ o o . ~ ~ ~ o ~ y o g . W W W W -----< C O O

~L27~843 -- ~ `T r1, r O r~ ~ r~
C ~5 V~

C

J
. 1_ ~,,,1 .
o ~ Z o, ,_ . O ~ ' O ~
O ' O W _ _ _ n ~ W ~ ~ ~ ~ c-~ c~ -C r O ~

æ .

W ~ J W O Z

O O . O Oz ~ . . ~ ~ ~ V. t. ..
~, .

W = ~ ,, O o U .~ ~ o : ~ W

, g O ~ ", o 7 ~

o ~ ; u ~Y 8 ~ o ~ '' O o ~ Z Z o ~

..~

1271~343 , o~
o _:
V V
W W .
.,: o V . V~ -o: o W ~
, ~,, C
_ ~ _ o~ o .. o . .. C
~ ~o . ~ ~:
8 g .
~J V ~
W . , W . ~, U
X : ~:
: ~ :
8 ~ o o o ~, o o Z . U _ ~ ~ _ : : <
O O ----O O ~ ~ ~ ~ <
U U ~, oovu W~ W~) . . V V Z

-o-~oW --o-_~WoW -o-_~
w .. ~ _ _ 8 w ' rl g ~ -- o W w .7 oO .
.. ~ ~ .. o ~ o ~ ,. ~ ~ o .
::::: :3: ::::::: :3: :::::

, Z , :
o s w v : 0 : ~w w: ~: tt :: 3 ,:
--~ W V- ~ o ~ o ~ ~ W V~ ~ C
~y ~ z S O w w z . 2 ~ Z _ ~ J Z ' ~t ~ ~ < w w V O O ~- V ~ U O ~ V Z Z V ~- O ~- O ,' O V Z
lo ~ ~ 880~ w~r~wo~uoo ww~wCw~ ~S ,Voooo :wwww_ ` 1271843 N N ~

J ' .^ ~'' ' U.
O
J
~. W
r~ C~ O C~ .
0 0 = 0 0 _ W~ ~. W . ~

O ~ D ' O O
r~ Wo W
~ O
.J C C~ Z
~ _ V, ~ ~ ~ h V 1~ _ L 1,.
D ~ G
O ~ --O - O
8 o c V
2 ~ ' ~ Z, ~ r Z, -- 2 ~ o o_ ~5 J -- o ~ -- W
W ~ O ~
w ~Y Z ~
E _, oWo ~~ ~ ~ a z o ~z 1 :
.
< ~ 3~ o ~ E n waoou w~o woo w a e w ~ w 1~ ~ o o; ~ ~ ~ o ~>
u ~ .. o o 8 g ~ .. o o ~n 8 -- -- o W c~ U 8 ; ~ ~

O~ZO~ Z~ ol,ov~zO~Zmol~o~O~ Zu-o~o~z Zo o o o a ~ , o . . ~ o ~ Z ~ w u z ~w~ z_~Jz r~woz_~JZ ~w z_~Jz r.~
~ ~ w ~ 9 ~ 8 u ~ ~ ~ ~ ~ u ~ ~ r ,~.j'l ` 127i.~343 a . T r~
_ _ _ _ _ _ tr~ ~r. cl, _ r, _ ~ ~n ``

W

W . W ~ W
. 3 ~/

V , ~ ~ _ W
. o .
. o . o ~- 2, , Z ~ w c~
o 8 ~ 0 8 ~ 8 ~ .

: ,. 7. -3 o ~ ~ o ~ i o 3 o -- = 8--w w o _ ~ ~ Z -- ~
w W D g----C W W ~ O----O W ~ ~ Z C~
' ' o ~ O ',, , .

o, e~9 ~ a~ o ~ I

~2~718~3 C - -- -- -- u. -- - r Q C~ _ F ;: ~
C

C
W W ; W
0 0 . 7 V' ~ ~
3 ., W . W ~
Z o, o .
(~ . V 1. V) .
o o _ o .
W W o W
o- Z C ^
_ ~ -- G ~ ~ c. V ~
-- O ~ O ~ C
1g c , O _ ., Z ' ~ -- ' ~ T Z
0 - 0 ~ 1- 0 ' o W
8 ~: 8~
W . ~ . o W .
W " , .. W
C. ~ ~ . W
~ Z ~~ oJ ~ .
.
Z
W,w ~~ ~ ~~ W ~ ~ ~ 1 V~
" w ~ 8 w ~ 8 8 , o~ W ~, ,. o W W Z o o W . .
Wr W W ~.
W O ~ W --O ~ W W T I O Q Q ~ ~ w o ~ OO " ~ ~ ~ , ~w 8 ~ O ~ L~
' I' O Y ~ tD L'. -- 8 Q w w o W ~ o Q ~ L ~ ~ O
a _ _ L'l U~ C~ L~ O Vl Z C'' g 1 O-- V Z O C~ O Z CWr ' ' ' ' ' O ' ' ' ' ' ' ' O ' ' ' ' ' ' ' ' ,' O ' Z V) ~r w ~ -- ~ w ~ ~ o I o ~ o ' ~ ~ o ~ O W ~ ~ W i Z q O W W W i C O W W IL W 0 ' W
t~ Z _ 1- J o W < Z 0 ~ Z ~ 0 C~ ~ w . w ~ oooo_z~ 0000_ZU _ . V- oooo22--Z~ v --CJ
8 8 8 u ~ O ~ . ., 8 8 a T W I J O O O O O _ _ q J ~ Z --g ~ IWy~tW~WcJ~oc~ ~W~WW~WyOJ~og g ~w~W~W~oJ~a ~0OO

1~18~3 ", ~ o~ o o~ . ~
~, C

J
W ~ o W
o o . Z - o , . . . o V U . W

V~ ~ X . W C
O C ~ Q
~IC' VC~ C ~ ~

g , ' '' O

O
-- W

5 ' o -- 15 V ~~ U

o W ~ ~ Z U Z ; U o W

:: :: :
J
a w . . <
z Q : ~ t W 1~, Z ~, ,-- ~ . W O Z , 3 o~o~. z o o~ z o~o~
-- 8 Q K ~ O ? 8 O X O ~ O W ? O -- W O
< ~ O _ ~ o, w O ~ 8 ~ < ~ 3 w o ~ 8 ~ 3 ::::: :_: ::::: :_ < , o z ~ i u ~ ~ o ~ ~z u o w -- ~~ orw -- ,ow t~ --w ~ O~w ~~
W ~ O ~W ~' Z ~ ---- ~ ~
w z _ ~I J O ~ w w z _ ~ ~ z ~wy w z ~ z _ w w z w O ~ICOC~OY~O~Z~l J colaaa z'.~w? ~ . .w~
,'': 8888aS.... <'' 8888u~W~ ~ : 8888~-v o ~ W~ J~Yoo ~~W~c~Yao ~ 0 G~ ~ o w~wy~wowJ~

i27~8~3 '1 F. U' F. Il` U. L'' U' C' O' O~ O tt 0 r~

_ O

C ~ C O C
L ~

~ .
O
W
o t~
o , . ,~, . ~ ...... .......
W ~' V Vl J 1- Z 1- O ~t tO -- O t5 Z Z ~ O 0/ u~
< w ~ J Y - Y Z Y 1 J ~ Y Y V~ O t~ ~
V '''' . ~ . ' ..... .......

W J J J J < < ~ C ~
V)0VlVZZZZZZ0ZooZZZZ0ZZZZ0ZVZZ0Z
O O O O ~ V ~ V O U ~ ~ U V O ~ O ~ O ~J V O

V~
W
W

W W W

"~ -- -- W W Z ~ 1 Z Vl ~ V~ V Z' Z
2 ~ V ~ W ~ O W O ?z ww Z~ ?w _ _ _ _ Z w ct J Z ~_ vl vl ~ v~ ~ tr :1~ ~ tL J W O J ~ _ ~L
~ ~ W W _ W w ~D -- O C~ w Z ~ O It~ j~ -- -- --w Z w w ~I
o o o o o 5 t0 t0 0 co t 8 0 5 tO 0 5 0 0 8 0 ~ 0 ~ C~ ~ 8 0 0 o 0 ~, ~;271~3~

y ~ 7 ~ G ~ 0 0 q--s ~: ~n Cl O ~r. U ~ r~ C O t~ C ~ . C C. ~. _. _ _ _ _ _ _ _ O
O
W
O

O ' 't ~ 7 ~ '~ 7 ~ _ _ _ _ C.~ocoo.,- U8~o ~;c~ ;a~

O . .
O

.
1~ .
W

" O
W
~ W ~, W ", ~ ~ W
W ~ ~ . J ~ W ~
~. .
O
J W -- ~ W W ~ J J J J J
~ W~ a ~ C~
888 'B8 o ~o~w~o ooo8 8 8 8 8 8 oo8888 W ~W U ~ U ' ' w s----~ ~ w v ~ o ~o ~ o . 8 c li ~ w v~ o w 808, ~,Rz__z .

::::::::: o 2 v W ~ S W Uw ~ ~ W
~o ~ w .~ 8: ~ ~: ~,, ~
--o o i o "~ ~ o W W ~ ~ ~ W ~ o ~ ZW ,, ~w -- ~ ~ " W ~ ' ~ Z ~ ", o W W ~ ~ o ~ W ~ ~ " Z W Y
~ J ~ 8 8 8 Z Z S ~ ~ o , W y ~, ~ W . < ~ ~ ~ zo Z
7~ wwww----O-- ~~ ~ ~ ~ ~ ~ ~ ~r~qq~
OO O O O O O O O ~ ~ J ~ U O O C~ O O ~ G 0 0 CO ~ O O O O O O

., ' 127~ 843 .

.
-- r~ ~ r rr ~ ~ rr ~ V V ~ V V ~ ~ V ~ V V V ~ r ~rr V ~r V ~ V ~D q V

o~ oC~ t~ ~ C rr' rr' ~ l r~r r;; r~ r r r ~ -- r, c -- -- u _ _ _ _ _ _ _ _ _ _ r~, r~ r~ r. r~ . r~ ~ r~

C ~ G O!
c rl tr rr, G
C' ., r~ r~ g -V ~ h ~' O ' Cr -- ~1 '-- -- -- -- -- d -- -- _ -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- d -- -- rrr -- -- 1 -- r_ ~ 8 o ~ ~ ~ g o o u o o o o u o o o o o o o 3 o u t o o u o o o Q 8 ~ o o 8 o o W L~ d d d U
d d Z ~I
rr w ~
5~ 8 o c~ ,V r~ ~ tt o o rr 8 ~ " ,~
rr o Q :~ Q C~ ~L ~ ~ Z W ~ -~'7 ' t~ ~-- Q L'J Q' O d cr Z r-- ~ ' 1 r r o O ctct tr ~ ,7 r rQ h-- J 1 Vh~ Z O d ~0 ~r w ww z J C~ tY <I t t Z O W r t e ~ ~ - r~7 cr h~ ~ c~ o o o o ~ ~ _ z _ z --;~ ~, w ~ ~t ~ 7 ~ " ~ ~ '' Ct ct W W ~ 8 ~ .. o g ~ ~7 07 g ~ . 8 8 8 8 z z ., ~
~r~r1r)~7r7r~t7r~r~r7o~r>~r~r7r7t7r7r7r7r7r7r7r7r7r7r~r7r,r7r~r~r7r7r7~r7rl L'JWWW----O
O O O O O O O O O O O O O O O O O O O O C~ O O O O O O O O O O O O O O O O O O tt tr. Q h' 5 ~ J 31 ~Z7~L8~3 - 0 '~ q ~ 7 -; ~1; 7 - r~ ~7 7 ~I r~ r~ ~1 ; T 0 C
--O - ~7 u7 a- r~ r~
- u~ U- ~ r7 ~ - u~ ~~ r~ r C r ~q r ~- r7 l7 --- rJ
1~ ; r ~ o~ C ~ 7 ~- - u~ u~ u~ r~ Q
~ v.

lu w J
w - w ~ l r~ ~zo ~ z O W ' ~ . O -U V ' V7 ~7 .
_ _ ~ O
~ rC o o ~J u~
; C. ` V ~ L >~
- r o7 ~ o . ~
w ~ w O ' ~ '~
u ~ ~ o ~ ~
V7 ~L7 r~ r7 u7 c7 ~
w r~
o--o ~ O w ~ r~
z . v~ u7 v7 ~ ~ o W V ~ O ~ W

~ w ~ ~ c ~ ~ ~ Q ~ ~ r o ~ ~ r ~ ~ ~

~ww Z o C, ~W ::
~ w w l~ ~u i 0 Z ' ~w O r;7 u ~ o rO ~w ~ cJ--w ~ c, O w 2 0 0 q &-- o~ z rw Z ' ' ' ' Zo v, ' ' ' ' ':
o ~ ' ~ ~ ~ ~ o o < O O O 0 0 0 0 0 0 rO 00 rO 8 00 8 0 0 rO rG O 00 O O r7 0 r7 0 Qw~ Q, c~ Q~ J ~ ~ O O

i~718~3 o~ ~ O ~ ' C~ C C c G G C ~ r~
- ~ v o~ o~ o, ~ ~, r r ~n .

w ~
O O

' z , ~O ~ O ~
~5 X ~
O ~ 0 O ~t _ ~ ~ ~
c~ ~, g ~' C~ J C; ~ O-- C- O C`
G . ~ , V ~ O -- r~
~0 ~ ~0 r. ~
O O
w --J ~ w ~ ~ w ~
O ~- O
O <~
O
E , o~ o o ~ r~ w 0 ~- 0 1 ~_1 . ~. W ~ W ~ W :~ --O W C- ~ ~ ~ O V- ID O O
~. . ~. .
' V~ C~ :

zo zO zO ~ ~ ~0 0 ~ r o. ~
o w ~ Cs O ~ ~ O O ~ g v ~ o ~ ~ o ~ o o O O
w ~_ w ~
- W Z ~ In w ~_ ~ zw ~ W
w rD ~ _ w c _ w ~I ~ O w ~ O ~ ~ O w ~ U~ O _ ~ O ~, o r~ O tt ~ o ' ~ '''O' '''~ w~
...... _ . ... ~ .. _ ~ 011 W ~n o ~ ~OSw ~_ O~w ~_ w J J
w ~ O g ~ w ~ 5 ~ O O w ~ ~ ~ Z ~ ct z ~
Z-- > J Z ~ w w _ O w w W ~ w O W w Z ~- Z ~ O ~-o a ,, O ,o, i v~ , O, ~ " ZO . W~ C . , ~ ~, # 'O 00 'O w o O
oooo.lsw~-. ooooasw<lo Y~ ~ o~ ,n w O m ~z~z 0,.,~
~' ~' w w o--~J a ~ w w w w o--o ~ ~ ~ w o ., 0 ." r~ r~ r~ r~ r~ r~ r~ r~
1~ ~ tl ~ ~ ~ O O (~ ~Y Ct J 3 ~1 0 0 0 r~ r~ r.~ ~ 0 ~O r~ O O O O O O O O O O

1;;:71~3~3 o ~ , ~.

~o. ~. o~.
:

o o o Z
.
~ .

o w ; '~ Z
. o . .

,. > ~ ,. .. ..
< ~ <
~ ~ ~ ~o o o o o o U .. o ., o ~ o o o ~. U 2 o--< ~ W ~ U W W
--~ o-- ~ ~ oo ~, J W C ~ W o o g W o W j~ J --W W
1~ ~ r r~ 0 0 r~

i271843 w s v <
v ~ v v ~ u v ~r, ~ w ~ 'i 2 ~ ~ 20 z ~ 0 ~ V~ n -- O ~- G -- ~0 -- O -- ~0 -- O -- O -- O -- O -- O
~ ~ W Z O ~ Z O ~ Zo Z ~ot Zo Z IY ~ O a ~o ~ O zO z ~ zO z O zO
:~ aO ~' :! g ~' ~ O ~ o ~~ 20 ~^ 2 0 :~ O
. ., , ~

o a g Z tr U ~ ~ a Z ~y a Z t~ a Z ~ U Z U tl Z a a Z a a Z 1 a Z U
~o ~:OO VOo Voo voO VOO ~oO ooo voo vOO OO
Z ~ Z ~ _ w Z U ~L 5 Z w e' ~LZ w r- ~ Z U ~L ~ z v ~ c. z ., ~ c _ W c IL Z U ~
,~yZ~e~z~ zz~5z~zz~zz,v~zz~O~zv~

Y Y Y w ~ Y w Y ~ w z z 0 ~ ~ z 0 ~ z z 0 ~ z z o Z Yz C ~ Z O ~ Z
0 ~ 0 ~ 0 ---- ~0 ~ 0 ~ 0 ---- ~G J
8 8 g 8 : 8 : :
O ~ 0 g o o o o o o, o . o o o o o < o ~ w o ~ w ~ Zo ~ '^ ~ O--~ L~ o V ~ ~t O ~ ~ L~ O Z w O Z v~ 3 z_ o z w ~ w w_ o ~ ot Z J o ~ Zo ~ W o ~ ZW O w ~ o w ~ O O O 0~ ~ 20 0 Iw o o w 3 Z o W--~'7 W O --~t O O--1~ 0 J-- C J 2 -- C ~
,.,3, otuo o~o o~Wyo ~ww wvww v~ _u~_ _v~ ., ma 08 o~ oo ~ W~ , W ~ W z ~ 2~ Z~r Z0 ~ W ~ wC~ W
W W W W V, V~ W
. ~ w . ~n w . (n ~ w . ~ ~y w ~ Iy w ~ r w ~ L~ ~ w ~ ~n ~ w . ~n ~ w ~ W ~ V ~
.ww~ ~wwm .wwm .wwm ww~ wwm .wwr~ ~wwr~ ~wwr~ .WW~D .ww w U ~ w w ~ ~ w w rJ ~Z w w ~ ~ w w V w w ~ ~ w w ~ ~ w w ~ w w U 3Z w w ~ ~ w w o ~
<~ v c o ~ L -t O ~ L~ ~ O ~ o ~ L~ ~ O ~ o ~ 0 ~ t o ~ o ~ v) a o ~ o ~ L3 ..

V V V .. V V ., V .;
2 2 ~ i 7 i~ < ~ < W ~ z < z ~ Z ~ 2 < W < W ~ W
~ C -- O -- O -- O -- O -- O -- O -- O -- O
< llt Q ~ Gl O < O < C O < Cl Q < CC O < Ct O < ~ ~ ~I Ct O < C G
2 o 2 ~2 o Z QZ C; ~ C - Z O Z Z o Z ZQ Wo Z ~ o - C ' e O z Gz 0 ~ [ 0 i o 2 . O 2 O i 0 ~ O ;i O ~ O ~ O
q~ _ O~ _ _ _ 1~
V V ~ -- V Z v Z IJ Z 'J z V 2 V -- ~J
2 Wo o jW~ o;} o ;; 3 WZ Z wz o 2 O Il~ Ct ~ :1~ C 3 O~O tl~ O ~I O Ot ~ O ~ ~ O tl~ ~ O C~ ~
O VCO~.'00 UCO ~/00 V00 ~QO VQO V00 VOO V~Q
_ _ _ _ _ _ _ W V C C 5 V C ~ C Z V C C, Z V C C _ W Z o CL C.
# S, z t~, y Z ~T ~ i Z ~ Z ~ ~ 5 ~ C Z ~ ~t r _ >~ ~! z ~ r z )~ ,~
z O ww1~owz VOww~Vzz __O~O VOww VOzw __OO __OO VOww w www O zz Owwwc XyOwwwwwC Z~ _-- www w Yz J ~ J ~ J ~ ~ J J J ~ J - ~ J ~ J J ~ ~
I ' Q ~ 8 ~ 8 2 o 8. 8 8 . 8 1n 8 ~8 8 0 ~n n 0 m 1~ ,n ~ n :n Ci ~ ~ J J
Q g Vl J O o o o o Z . Z ~I ~O Z v OV) Z Jg Z ~ ZCt1~ z z z ~ ~" z z U~ -V C V~o O O t Z ~ ~ g U W O V V~ C --z ~ O I~L C --z Q --z O O O O ~ ~ O ~W O ~ J O O w O W O ' O O O O ~ O
w u w w ~ u w w ~ v u- ~ z u u w 3 z " v w w w w z w o 2-- V U V
w 2 2 0 ct v v J ' ~ ' v ~ w u v 8 ~J u w ~ u z u ~ u ~. u ~ v v Z ~ Z Z~Z Z J~n JV J~ JZ '~ JII~ JV~Z J"''' J~ JV ~ JO~ J~ J J
. ' W W . . . W ' ' ' W . . W . . W . . . W ~ . . W . . W . ' W ' ) W~ V Ir w~ wV w~ IY w V w ' V~ w ~ w It~ IY W V~
g~ ~-V ~_UZ~~-UZ~2_uW3?~,.WVW~ ~,VW~2 ~ww~ .WW ww~?
W WY~W W~ W W~;O~ ~YZQ~W V~- O1W v,V~O~W V,VaW~ v.Y3W~ v~<VO~w V~OOa ~r ~ 27~843 o o ~ C ~, G ` C l -- C C
J
e C C C
-- _ Z
L L
O - O G C

O O O
W ~ ~U W W

._ _ _ _ _ o ~ W O -- ~ tS ~ tS ~ ~S ~ X ~ W ~

~'~ t V) o V) o Vl tt ~ c> v trv~ tr V~ o ~0 J V~ I
t ~ t ~ ~ t O o tt Z o tt Z o tS Z q U 2~, tr 2 C~ o rr Z O tS O

w ~ w ~ z ~ ~ ~ Z ~W ~ Z ~ o 8 o z O ~ tt O tt tS O tS tt O tr tt O Ct tS O tr tC O g t~ t g O St g O g g O g 2 ~ g _ z --W--W--W Z O t~ t.Z O t, t~ Z 1.1 tl ~ Z U t~ t~ 7 0 t~
~ ~ w w I 2 ~ ~ 2 Z o Z Zo 2 ZO Z ZI z x x ~ o zw zw ~ Z o o w w o o w o ~ z w z w ~ ~w z z w Y zo Y z o Y ~ w 2 2 w Y z w ~ g s~ ~ o ~ o 8 ~ o G' o 8 ~ 8 o . N S~ ~ ~ ~

O o ti o tt O tS ti o o O 1- ~ D 1- ~ w ~ W ~ ~ ~ ~ ~ ~ t~ ~ ~ ~ ~ ~ ~ ~ ~ V~ ~ ~ L _ O ' ~ ' O tS O tJ O ti O O O t~ O ~O tr O 1_ 4 tt L L t. tS t~ t~ 4 t~ L L tt t~ 4 g 4 tC g t~ ~- t~ L W y tt O
J J J J ~`- J JJ J J J J C~ Vl ~ ~ V~ V~ ~ V~ V~ V~ V~ V Vt V~ U V~ V~ V~
W W W tWr tW~ tt tr tt .V~CiW ~V~tiW .VVltSW V~tiW .VttiW .~VOtiW 'V~tiW ~V~tiW 'V~tiW 'V~tiWi .V~ti w ~ Z :1 ~- O 3 ~ ) Z ~ 1- ~ Z ~ W ~ 3 ~ ~ ~ Z ~ ~ ~ 2 ~ ~ ~. z m ~ ~, 2 ~ ' ~ Z ~ W z .. _ ... _ . .. .. ..
t 127184~

C C o W W

,. ~ C C ~ C ~ e r r _ 1_ O O G a G C G

' ''` ' Ç~ ~, tr 2 y o, U J
V~ V~ ~ ~ c U ~ U U U ~ U ~ U Ot~
r. ~ r~ ~- r- r-0 1 0 :~i O :~ O i 0 ~ O :1 0 o o o o w O W O w O w O w O w O w O
:~ z~ ~ z a z ~ O ~ O < O < O < O ,~ O . O, <
" ~ V~ V ~ V~ ~ V
o -- o -- o -- o -- o -- o -- o -- o -- o -- o, 2 wo 2 z O ~ O 0 5 ' ~ ~ ~ w - ~ O z z ~ O ~ ct z ~ O ~2 za ~Ow 2 z . ~ .3 C :~ o ~ o ~ o 2 o 2 o 2 o S o 2 c o :~
~t ~ ~
w ~- w _ w . ~ -- _ r. r. ~ -- w r- w w ~ w ~ u~ S w w w w w V S U 12 O ~ o z o } O ~ a~ } ~ z2 ~z O z O
O O O O O O O O O OC: tY O ~7 O O ~ 0 0 ~_ r. U ~ - tt ~~ ~Y _ Ct ~. ~ C ~- tt tlt r- ~ r- 0 Z ~ ~Z ~ IL 7 ~ Z U ~Z (.~ O Q Z ~ IL Z ~ Q 1~ Z ~J C ~
r.q Z ~_ ~-- 2 ~_ r. 2 r. r.< Z ~ q Z r. r_ < ~ r- ~-- < Z r- r. < Z r- r- q 2 r_ r_ Z r- ~_ X1 Z X X :~ Z ~ XS r X ~ U O w w<O O w w O X X 3 5 ~ X O O w w J O w w O O w w Z ~ ;' Z ~ ~ O O~--Q O ~ ~ O O~ ~ O O ~--O O 'J Z ~ ~ ~ O O ~--O O ~ ~ O O
w o w w w y Y w 2 Y a Y 2 3 z z 3 z z ~ 5 Z 3 z O O

v~ O u O ' ' o O g O ' O O, O ~o o o o r7 o u O o o o O o o~ o v7 o o o Z _ < .v ~ v7 ,. ~ ~ ~ vw7 ~ - v~
y z _ _ ~ zO z ~ o O ~ O, , O ~ w o J ~ 7 Z
Ov7 C 7 o O--r- OO --~L O r O ~ r~ _ V r_ w ~ ~ w v~ ~ ~ ) V~ w Z w o G w ~ v V~ C -- V7 W -- W W W ~ W 0 w >- W W
v7 a~ O c- ~_ r_ ~ v7lL -- 1~7 V7V7 r_ 1~7 v7 V7~ v7 r- V7 1~7 V7 r- ~7 V7 w w w w ~ w w V7 . W . ~ . W ~ ~ . w . .~ W ~ ~ . W ~ ~ ~ w . . w ~ . W ~ ~ ~ W ~ .
~ ~ ~ ~
1~7 1~7 VI V~ V~ V7 Ir7 ~ 7 ~ ~ 1~7 ~
w r_ U Z ~? ' w w ~ z ~w w ~,~ w w ~ w w 7 ~ w w ~? ~ w w ~ ~ w w _ w w w ~r 3 W V7 Y O SV7 Y O ~ V~ q O ~ W ~J O 2w ~7 < O 2 w C' 1~ ~w w O ~ 1~7 q O V q O 2 `` lZ7i.~

o o CJ o Z Z _ C ~ C C

z Q z o ~ ~ J ZO
V V U

' O ~ ~- Z o W ~
~ v O v ~ _ tt ~ O _ O _ O _ O ~

2 0 ~ O ~i 0 ~ 2 0 IL ~ Z ~, Z -- Z Z Z o Z z w z U ~ ~ Z Z U Z ~ Z o U W W W W Z W
~ 8 0 0 U 08 0 0 V o o V 0 g Z tt Z
ZUgg Z~g~ wgg wgg zug Eg~ zwu~g zwg~ ZV~Y Z~g ZU~
U O Z Z U O Z Z ~ O Z y U Z _ U O Z Z U o u 8 8 8 ~ ~ 8 ~ g~ 8 ~ ~ ~ o ~ 0 G~ 0 0 0 0~ 8 O z Z '' ~ " ~ O O O
O 0 Y W 0 U G o ~. w 3z o z z o z o o o o o 0 0 OW 0 0 ~ 0 ~ --0 ~ 2--0 2~ 22 ~ 2 ~ Z W W _ Y 0 V Z Z
Z U Z W Z U Z O ~ 0 8 8 ., .., U W ~5 U Zt~ V
WWO W~1:WzO W~WZ ~YWzOW~:WW W~WW W~WW WYWWWYW~- W~WW W~rw ~t w w w w w w w w w . v~ ~ w . tJI ~ w ~1~ w . v~ Y w ~ vl ti w ~ v~ w ~ tn t~ w ~ tn Y w ~ tn Ci w ~ t ty w ~ t , t 'V~ < O 1V I~ O ~ O ~ W U 3 ~ W ~ ~Z ~ W ~ ~Z ~ ~ U Z ~ V Z ~ ~ U Z ~ t_ ~ ~W

1~843 O Q O
W W W
O O J
< ~
o O O O

w Sl ~ _ U ~ ~
V ~ U U U ~ U ~J
~ t-- ~-- _ 1. _ _ _ _ ~ o O ~ 3 o ~ _ 3 ~ ~ g ~ o ~ g V~ o ~ o V~ o ~ o _ o _ o _ o g o ~. Q~ G-- Z O ~ ~ o-- ~ Wo ~ ~i? O Z !2 W Ç Q Q o Q Q ~u W ~ z ~ w W ~ w Z ~
2 g ~5 O Ç O O gCu O O O O g C O o ~J C O

~ ~w~ g g Z ~w g gZ ~wJ g g- ~w g g Z w g ~ - w g g Z ~J ~ g 2 ~ g ~ Z ~I ~ C Z ~ C ~
z ~ o z z u o z w o z zv o z zu o w w 3 o z w u o w w o z w u o z z o u~ wz W o y Y W Y Y W Y Y W Y Y W W W W y W W y W W W W Y Y W

o . g o ~ 8 ~ : g C o o . ~
e O O _O# ~ol o o o o cZ o o o - 3 ~ 3 3 zo o Z Z
w w ~ _ o ~ - U - w w _ ~ w ~ W W W ~ W W W ~ ~ ~ V~W ~ W ~W ~t W V~ ~ W ~ ~r w o, w ~ w U w w w w w w ',y w w~ lwy ~ ~w ~ w . ~ ~w ~ ~ ) < i ~ ~ ~ 0 5 ~ s v i l ~ v< z ~1 ~ v z ~ w ~ z ~

8~3 o 2 L L

C C
U~
'"

Z ~Z a Z ~ Z Z ~, ~ O ~ O ~ Z ~ Z ~Z
V) g V o ~O ~ _ g _ g _ o _ g _ g _ o -- C~
o _ z o z 4W Z z Z Z ~ ;? o Z ~ ~ ~ u ozu zo < ~Y zo U _ _ -- d g--g-- -- -- --u g D 1 O 0 ~I O ~' ~/ ~ ~J g g ~I g g ~ ~ g g ~J g _W _W--W--W --W --W --W--W --W _W W
2 Zo X X7 Z ~, KZ K X~ Z X C ~ Z ~ ~ Zz X X~ Z ~-- C Z ~-- C Z Z -- Z~ X ZW ZW~J ~, Z ZU ~, W W U O ZW Z U X ZW ZW~ ZW ZW ~ UO~ ZW ZW o ZW W U O W W U O ZW W U O Z~

W Z Z W Y YW Y YW Y Y W Y Y W Y YW y Y W y Y W y y O W W O W
~ J J :~ J J 2 J J
~o, 8 8 ' g C ~ c- ~ g ~ ~ 8 G 8 ' ' g-- ' Ct Oo~ g O O O g g ~ g g g g W ~ ~ ~
W Z Z W -- --~ O W O W ~- O`
o O ~ ~W _ ~ J O W ~ _W cWW 2 ~W~ b. Z, C ~ o o O w O
2 ~,) Z W 8 ~ 8 w w w w ts J ~ z v z w _ w v u w ~ w w u w w w v w w ~ ~ ~ w ~ w w ~Y w w w :r w w W ~ W ~- W ~t W W w ~: w w w ~Y w ~ w ~f w w 8 ~ o o o ~r o W ~ . w~~. V2 Z Z Z Z

w ~Wr W ~y ~W ~W ~ W W W W
v~ ~ w ~ Iy w~ v ot w I~ ~Y w ~ w . ~n ~ W . ~n ~ w Vl t~ w ~ r w . ~h Cl~ ~U ' V- ~It W ~ V ~V ~ w V ~ w W v W ~ U u W V ~Z ~ -- V Z
v- q o ~ 0 ~ 0 Z V~ ~ o ~ o ~I o :~~ ~ 0 ~ c o ~ <1 O I ~ a O ~ o ~ ' 4:~

D G G O
~ W W W
Cl C C G
~: q C C
C O C ..
C O C C

w ~ Q E
ZO W W ,.
.. , ,. ,. ~.
< < <

:~ C ~ o :1 o ~ o ~ o o ;~ o W o W o W o W o Z o ~ W < ~ ~ ~ O ~ O ~ o ~ W Z ~ X C >~
-- ~ _ o ~ o -- o -- o ~ o -- o -- ~ .. o _ . _ ~ zO Ot Gz 1 ;? ~ zO ~ a~ zO < C: zO I tl e o ~ zO tt O O Ir O
w z w _ z w Oz w z 0 3 c z O z O -- -- O Oz w z _ w z O Z O :It O 1 0 :E O :E O :~ O 1 G O O ~ O O O

W 11 W ~ W I W ~t W ~i W ~ W 3 W :~ W 3 W
O Z O Zz O Z O Z O Z O Z O Z O Z O Z O Z
o c~ ~r o o ~ o t~ o u o ~ u o 1~ o at o 1~ ~Y o o ~00 UOO VOO UOO ~00L~OO VOO ~00 ~00 UOO JO
E w w ~ w w w ~ w w w w ~ Z X X~, Z X ~ ~ Z '~, Z ~ ~ 'Z >: ~ ~ o K >~ ~ Z K Y. _ Z K K I Z K ~ Z K ~ Z >~
~.,zz ~8zz~XZz ''xzWz~xzzw xzwzw ~xzwzw vxzwzw vOww ...... Oww ~Ow _OOO ----OooOww Oww OwwOww Oww Oww Oww ~Oww ~~
0 z z wO z Y 0 _ _ 00 z z 0 z z 0 z . O z ~ 0 z z 00 ~, 0 z z 0 z 8 8 . 8 8 ~, 8 8 g 8 8 ~0D . 8 0 8 8 8 0 0 0 0 0 ~ 0~ 0 0 0 ~ 0 ~ ~ I~ r~
:
g _g g wOO g g g g g g g 1~ . ,. ,~ O ~ w ... w ,~ . ~ . . w .. .
o z z z z .. z v~ z . z v~ z w v~ z w c .~ z w z z O w z O wO w w O w~w O ~ w O w w O w ~ O w O w O O
< ~ '~ J~ Za ~~ ' W ~~ tY' ' ` ~ ~ Zo '~ C w O J W a, ~ ZW W~ O
V O J V V O J ~ V O ~ O o O ,Z o V o W V O ~ ~ v ~ V W ~ z U V a W c V a . -~-a-- I-U~ u~ uw ~uu~- ~- au-- oaow wow wvo ov V~ ~ ~ J ~ Z v ~ ~ v ~ a V~ o Z ~
w w w ~w~ ~w~aw ~w~ aw : cw~ c~ a v- IY v ~r v) a ~ fr v~ IY v IY ~n u ~n a v~ a v~ v-vl tt w~ ~ ~ w . I~ w~ m w ~ r w ~ m w ~ ct w ~ w v w ~n w ~
V Z ~1- v Z ~11~ v ~Z ~zw3 ~ 1~ V Z 5~ ~- v z ~ ~- V Z ~ ~ w w w w w w tl~ w ' ~ w y 3 w w y 3~ ww ~; w w y ~w w y ~ ~w w V O ~w w ~ O y Vl V O wE ~ y O ~w v <V O E V~ cV O

~12'7'18~3 ~, .

. .

,. 2 _ C, ~ 2 ~ ~ c W i z ~ z ~ z 5 :~ z :~ z :~ z :i z ~ z ~ ~ J Vl ~ ~ J ~ J V J Vl J '~ J ~- J ~ J
O C~ ~ _ o z _ Q ~ ~ o Z _ o Z ~ o ~ ~ o ~ ~ ,, ~ ~ ~., G
O O O O - - O O O O O O O O O O C O O O O O O
W _ W ~ U
O ~ O Z Z Z ~ O Z O ~ O ~ O ~ O Z O
1, o g ~ o o BJ ~ _ u o o ~ o B o o ~, o o ,. o o ~
~t g ;; ~ g g Z U g g 5 J g g;~ ~ g g _ W g W g g _ ~J g ~ - W

Z UOZWz V~WzWz U~WzWz VOWZ UOWzWz UOWZ VOWW VOWW UOWW VOWW
O W W y ~ 3~ y W ;~ Y W X y W ~ ~ W y Wy W y y W Y Y W ~ Z
O _-- ~ ~ ~ ~ ~ ~ J J ~1 J J ~ ~ J ~ J J

0 D ~ D0 J 0 ID ', g N8 ', ~8 VgN , N ' 8 8 ~ 8 ~ N
O O ~ O :~ O O O O O
~ O O O ~ O O O z ~ Z O o --z O 2 ' O ~' O U O W 2 W W 0 _ 0 0 1W--~ V W o o ~ Z W W 0 W W V W -- UO o-- U -- ' V W ' V W V~ ' U W 1~ C V C ~ U ~ ~
o ~Y v o w ~l u ww u w W U W ~ ~ a w ~ ~ ~ w ~ ~ ~ w g ~ w w g ~ w W u a w u.
w w ~w Ow~ wa : aW : aW a ~ ~ , a ~, o ~ < O ~ o ~ u ~ a lZ7~8~3 .

G O Q C
W W W W
O ~ O
e C .~ C
C O C O
~ L L L
O O ~ C

C U~
-- ,0 0 0 ~ O ~ C
a .~^ v~ L' _. _ _ _ J ~ < ~ < < ~
Zo ~ o o o o o w o w o w o w W ~ z il z I z I z z C D I D 'I O 1 0 <I O
Z Z -- -- O -- O
Q o ~t Q o c~ Q q u Q u Q ~1 u Q c Q 1 u o < u o ~I tt o a u o -- o Z ~, W Z ZO W Z Z Cl 4 3 W Z Q Z z w Z zQ w z z O z z o z o o O o o :~ o 1 0 :1 0 0 :~ O :E O .~ O :~ O
w~ z ~ w zw Z O Z2 0 ~W zzW io Z O zw zW zW z zW W
~ o o ~ ~ o O o o ,O~ o o IJ o ~ (O~ o o ~ o ~ ~ o o ~0~ o o ~0 _W ._W _W _W --W --W _W _W _W _W --W
~ ~ z z ~ o z z ~ o z 3z ~ o z z ~ o z zw o o z zw o o z z o o z w o w w o z z o o w ~Ooo oo ~ oo -- oo -- oo oo oo oo oo oo o Wo Z YZWo Z Z o W W o W W o yw yw o W yw o W W o Z Wo Z Z Wo Z Z Wo , Z
zO '---- ~0 ~ 0 ----~0 ~ C ~ 0 ~ 0 ---- ~ ~ ~- 2 ' ~ ~--00 0000 00 00 00 00 00 00 C~ O 0 ~ O~ r~ ~ . r~ ~O r~ O ' ~ ~ ' - r ' u ' O o ~ o o O O o o o o o w v~ o 3 0 ~t Zw o IY o u ~ o ~u o u o o o ~ o u. o w o o wo o ~ o o ~ t~ w o ~ ~ ~J 3 8~ Zo ~ ~. o v. 3 ~ O g O
0 ~ Q ~- Oy-- y ~',; w v/ _ ~ ~w~ ~ ~ ~ JJ ~ J ~ O ~ Jc ~ J ~ ~ ~U ~- ~
~4~ Zwow w4Wo? wUoW? 0400o400w ~_owO~, 1-40~-IwowOw ~Ow ~wwoaow v~o~ ~Uo~ w ottoo oUoow~oow~ow ~uO-I wuo ~w . . ~w ~ ~ ~w . . .w ~ .~w ~ ~ .w . ~ ~w . ~.w . . ~w ~ . ~w . . ~w .
t w ~ ~ ~ w ~ r w ~ I~ ~ W ~ ~ W ~ ~ ~ W~ v~ ot w~ v ~ w ~n ~t w ~ ~ ~ w z ~ ~- 4 ~ ~, u z z ~ z ~ Z w w ~ w w~ z 2 z ~ z Y o z n Y o ~ ~n Y o z u. y O wr ", y 0 2W ", y O wE vw~ ~ O ~w w y w w 3~ w w y w .

~2~7~8~3 o o o o o o o o w , 3 3 I 3 ~ 3 _ _ _ ~ _ J J
O ~ Z ZO ~ O O :~ C
C. C. L t. ~ L L L C
o 3 o o ~ 3 o o o w W W ~ 8 ., V U U ; V U ~, ., ~Z
., .. ., U U .. .. ., . U .. ~ ~o o a o O ~ ~ ~ ~ w ~ W ~
O ~ O ~ o, < ~ ~ Vl ~ & ~ o ~ o v O ~ O _ o _ c L' o o o Q oZ ~ Z o ~ ~ 3 o '~ ~ o 1~ ~ w Z ~ ~ :
g zvgg z~lgg 2-W~ ~wg _wg~ Zwo ~ _v~g _wg 'wgg :
wz~ o wz z s O wz z v ~ z z v o wz ~wz v o z z ~:i o wz z v o z wz u o z W2 s O w w woywoww o w oww oww owwoww oww oww g' g go 8 8 8 8 8 8 : 8 g o o J o o z o ~ o o o o v O V-W O WV O U O W o 3W o o ~,, o ~ o ~~ O , O w _ w o w c 3 ~ v.

$ ~~ 3 8 ~ O ~ ~ Oz IY ~ z - 1~ ~ w ~ ~ ~ w~ w = ~ wO ~ ~ ~v3 ~ o w w w w ~ w ~ - ~ ~ ~ w V 3 ~3 ~ ~< ~ ~ V< 3 ~ < Z ~ ~ v~ Z~ <

Claims (25)

- 147 - Case 4790 THE EMBODIMENTS OF THE INVENTION IN WHICH AN EXCLUSIVE
PROPERTY OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:

1. A method of modelling an offshore structure using a finite element method comprising the steps of:
analyzing the structure in terms of finite elements and nodes;
condensing the finite elements and nodes into super elements and super nodes;
determining equilibrium conditions of the super elements and super nodes at interface points of the structure to provide boundary conditions; and analyzing the condensed structure using the boundary conditions to provide all node displacements and forces and stresses of the structure on the elements.

2. A method as set forth in claim 1 further including the steps of:
checking the node displacements and forces and stresses on the elements against industry code standards to determine in they conform with such standards; and - 148 - Case 4790 changing the design of the structure in areas where there is a lack of conformity with the standards.

3. A method as set forth in claim 2 futher including the steps of:
applying environmental loads to the elements and nodes produced by estimated loads due to waves and winds to determine the maximum shear forces and bending moments on the structure at points of discontinuity of the structure.

4. A method as set forth in claim 3 including the further step of:
reducing the environmentally loaded model into a reduced stiffness matrix and a reduced force matrix to allow condensation of the model.

5. A control system for controlling the input and output of data from a database by a database management system comprising:
a source of outside data;
a database having a finite element structural model formed therein; and a database management system for communicating data between said database and said source of outside data;

6. A control system as set forth in claim 5 wherein said database is an engineering database having floating point numbers.

- 149 _ Case 4790

7. A control system as set forth in claim 5 wherein said database has a finite element model of an offshore structure.

8. A control system as set forth in claim 7 wherein said finite elements model is structured by said database management system to include super elements and nodes.

9. A control system as set forth in claim 8 wherein said database includes relational links between super elements and nodes.

10. A control system as set forth in claim 9 wherein said database includes relational links between super elements and finite elements.

11. A control system as set forth in claim 10 wherein said database utilizes an Extended Bachman Notation.

12. A control system as set forth in claim 5 wherein said source of outside data includes a design engineering data source linked to said database for inputting a finite element model into said database and a plurality of non-design engineering data sources connected to said database for obtaining model data from said database without being able to input any data into said database.

13. A control system as set forth in claim 12 wherein said plurality of non-design engineering data sources are - 150 - Case 4790 concurrently connected to said database with said design engineering data source.

14. A control system as set forth in claim 13 wherein said database includes environmental data associated with said model.

15. A control system as set forth in claim 14 wherein said model is an offshore oil platform and said environmental data includes soil condition curves for the soil in which said oil platform is located.

16. A control system as set forth in claim 7 wherein said database includes instance of all finite elements comprising data items into a record by virtue of some data items sharing a geometrical design requirement.

17. A control system as set forth in claim 16 wherein said database includes a listing of all finite element data items into a record by virtue of some data items having a common fabrication requirement.

18. A control system as set forth in claim 17 wherein said database management system includes a security code preventing unauthorized access of said database.

19. A control system as set forth in claim 18 wherein said security code includes a single MASTER User allowing unrestricted access to one model in said database.

Case 4790

20. A control system as set forth in claim 19 wherein said security code includes limited access to data in said database with no ability to input data into said database.

21. A control system as set forth in Claim 5 wherein said database management system is a network type database management system.

22. An engineering database being controlled by a database management system comprising:
data means for containing in excess of 200,000 Finite Element Load data records; and means for changing the records of said data means with a single transactional entry into said data means.

23. An engineering database as set forth in claim 22 wherein said data means includes extremely large finite element models having finite element records in excess of 200,000.

24. An engineering database as set forth in claim 23 wherein said changing means includes a single input to said database controlled by a database management system.

25. An engineering database as set forth in claim 24 wherein said database management system is a network type database management system.