Re: Generic Modeling

In article <a6e74506.0201011016.42738ff1_at_posting.google.com>, James says...
>
>How do you model the utility requirements of various manufacturers (ie
>GM)? Each Manufacturer has operations in various Regions of the world
>(North America). Each Region has various countries (USA). Each Country
>has various states (Michigan). Each State has various cities
>(Detriot). Each City has various manufacturing complexes (Vortex
>Engine Complex). Each Complex has various plants (Plant1). Each Plant
>has various floors (Floor1). Each Floor has various manufacturing
>areas (Piston Area). Each Area has various cells (Forging Cell). Each
>Cell has various production lines (Line1). Each Line has various
>equipment (Equip1). Each Equipment has various standard components
>(Comp1). Each Component has various point of connections (ePoc1). Each
>ePoc has a utility requirement (Elec=400W). Each ePoc can connect to a
>utility source point of connection (sPoc)
>
>Equipment are utimately powered by utility sources. A Source routes
>its utility via laterals that fan out like the branches of a tree.
>Each Lateral has a maximum capacity rating. Each Lateral has various
>Point of Connections (sPoc). Each Utility Source Point of Connection
>(sPoc) can connect to various Equipment Point of Connections (ePocs).
>
>Although an equipment is typically placed on a production line, it can
>be at any level between Manufacturer and Line inclusive. Allow
>location levels (ie Cell, Area, Floor, Plant, etc) to be omitted.
>Although a Utility Source is typically located at the plant level, it
>can at any level between Complex and Line inclusive.
>
>Sub class utilities as shown below:
>Utility
> Gas
> Air
> Nitrogen
> Liquid
> Water
> Ultra Pure
> Cold
> Hot
> Electricity
> Regulated
> Unregulated
> Uninterruptable
>etc...
>
>Allow any class (or sub class) of utility to be rolled up for any part
>to tree.
>
Therefore, when you want to search for all broken standard components you write:

for( Country a = countries.first(); a!=null; a.next() ) { State[] states =a.states;
for( State s = states.first(); s!=null; s.next() ) { City[] cities = s.cities;
// 10 more levels to get to standard equipment }
}

..

Writing object database is easy, the only thing you need to master is recursion. No query parser, no optimization, no concurrency. After serializing the whole memory to disc you just claim that you have (yet another) object database! Received on Wed Jan 02 2002 - 19:29:48 CET