WO2000008574A1 - Systeme d'ingenierie assistee par ordinateur et procedes d'exploitation de ce systeme - Google Patents

Systeme d'ingenierie assistee par ordinateur et procedes d'exploitation de ce systeme Download PDF

Info

Publication number
WO2000008574A1
WO2000008574A1 PCT/AU1999/000614 AU9900614W WO0008574A1 WO 2000008574 A1 WO2000008574 A1 WO 2000008574A1 AU 9900614 W AU9900614 W AU 9900614W WO 0008574 A1 WO0008574 A1 WO 0008574A1
Authority
WO
WIPO (PCT)
Prior art keywords
component
defining
components
connection points
attribute
Prior art date
Application number
PCT/AU1999/000614
Other languages
English (en)
Inventor
Dermot Terrence Kennedy
Steven David Jones
Joshua Roland Urs Petrig
Original Assignee
I & E Systems Pty. Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from AUPP4995A external-priority patent/AUPP499598A0/en
Priority claimed from AUPQ1261A external-priority patent/AUPQ126199A0/en
Priority claimed from AUPQ1260A external-priority patent/AUPQ126099A0/en
Priority claimed from AUPQ1769A external-priority patent/AUPQ176999A0/en
Application filed by I & E Systems Pty. Ltd. filed Critical I & E Systems Pty. Ltd.
Priority to AU51405/99A priority Critical patent/AU5140599A/en
Publication of WO2000008574A1 publication Critical patent/WO2000008574A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F30/00—Computer-aided design [CAD]

Definitions

  • the present invention relates to a computer engineering design system and aspects thereof, which have particular, but not exclusive, utility in the design, maintenance and upgrading of large scale reticular systems of components, such as large scale electrical circuits incorporating instrumentation for industrial plants.
  • as-built is used in the engineering industry to refer to a component as it exists on a site. The term is used to distinguish such components from proposed changes to a component that are currently being planned by a project but which have not yet been effected and to distinguish such components from new components that are being proposed as part of a project but which have not been installed Throughout this specification "as-built” will be used in this context.
  • a component definition system for defining components for an application wherein the component definition system is adapted to define component instances having specification level attributes and instance level attributes and wherein the component definition system is adapted to define values for said specification level attributes whereby defining component specifications having at least one specification level attribute from which said instances of said component are defined.
  • Another aspect provides a computer aided engineering system for modelling reticular systems of inter-connected components wherein said system comprises a library of classification elements; each said element having at least one attribute; specification means for selecting a sub-set of said classification elements and for defining a value for at least one of said attributes whereby said system comprises component specifications having at least one specification level attribute; and instancing means for selecting component specifications and defining values for instance level attributes whereby said system models said components of said reticular system.
  • both aspects further comprise a library of classification elements and a specification means wherein each said classification element has at least one attribute and the specification means is adapted to select a set of classification elements from said library and to define an attribute value for at least one attribute of said set of classification elements whereby forming a component specification with at least one specification level attribute.
  • the systems comprise an instancing means adapted to define values for attributes of said component specification other than said at least one specification level attribute whereby defining a component instance.
  • the systems are adapted such that said library of classification elements comprises a hierarchical structure adapted such that in response to selection of an element by said specification means said element inherits parent elements from said hierarchy.
  • the systems are adapted such that said attributes of said library of classification elements are pre-defined as either specification level attributes or as instance level attributes.
  • the systems are adapted such that said specification means is prevented from defining values for instance level attributes.
  • the systems are adapted such that said instancing means is prevented from defining values for said specification level attributes.
  • the systems are adapted such that said component definition system is adapted to define component specifications and component instances for, in use, modelling components of a reticular system and connections between said components of said reticular system whereby said definition system is adapted to define loops of connected components within said reticular system.
  • the systems are adapted such that said definition system is adapted to define said components of said reticular system as having connection points and to define connections between said components of said reticular system as a set of connections data.
  • said systems are adapted such that said connections data represents connections between connection points of inter-connected components.
  • the systems are adapted such that said system is further adapted to define said components as comprising multi-point connection points containing a plurality of said connection points whereby said definition system is adapted to define said loops as comprising components inter-connected by multi-point connection points.
  • the systems are adapted such that said definition system defines said components as comprising groups of connection points wherein said groups identify connections between connection points internal to a component.
  • the systems are adapted such that said internal connections comprise logical connections between connection points in said group.
  • the systems are adapted such that said system is adapted to model said connection points as having left hand and right hand fields and wherein said left hand and right hand fields designate the number of connections with said connection point to its left and to its right with respect to the loop containing said connection point.
  • the systems are adapted such that said left hand and right hand fields indicate left hand and right hand direction in the loop which the connection point is a part.
  • a method of defining a component for an application comprising a library of classification elements; the method comprising the steps of: 1 ) selecting a set of classification elements from said library; 2) defining an attribute value for at least one attribute of said set of classification elements whereby forming a component specification having at least one specification level attribute and at least one instance level attribute: 3) selecting said component specification and defining attribute values for said at least one instance level attribute whereby defining said component.
  • Another aspect provides a method of operating a computer aided engineering system adapted to model a reticular system of inter-connected components wherein a set of inter-connected components comprises a loop; the engineering system comprising a library of classification elements; the method comprising the steps of: 1 ) selecting a set of classification elements from said library; 2) defining an attribute value for at least one attribute of said set of classification elements whereby forming a component specification having at least one specification level attribute and at least one instance level attribute; 3) selecting said component specification and defining attribute values for said at least one instance level attribute.
  • the library of classification elements comprises a hierarchical structure wherein an element selected according to step 1 ) inherits predetermined attributes.
  • the methods are further adapted such that said attributes of said library of classification elements are pre-defined as either specification level attributes or as instance level attributes and wherein step 2) further comprises defining attribute values for specification level attributes selected at step 1 ).
  • step 2) excludes definition of values for said instance level attributes.
  • the methods are further adapted such that step 3) is excluded from defining values for said specification level attributes.
  • the methods are further adapted such that said application comprises a set of components for modelling reticular systems of inter-connected components and wherein a set of inter-connected components comprises a loop; said method further comprising the step of 4) of defining said components as comprising connection point data for representing inter-connections between said components.
  • the methods further comprise the step 5) of defining connections data for representing inter-connection of connection points of components.
  • the methods further comprise the step 6) of defining said components as comprising multi-point connection points containing a plurality of connection points; and the step 7) of defining connections between multi-point connection points as comprising inter-connection of connection points contained in said multipoint connection point.
  • the methods further comprise the step 8) of defining each said connection point contained in said multi-point connection point as being associated with one of a number of sets of associated connection points; and step 9) of defining said inter-connection of said multi-point connection points as comprising the connection of corresponding sets of associated connection points in said multi-point connection points.
  • the methods further comprise the step 10) of defining said components as comprising groups of connection points wherein said groups identify connections between connection points internal to a component.
  • the methods are further adapted such that said group data defines logical connections between connection points internal to a component.
  • FIG 1 shows in diagrammatical form a computer aided engineering (CAE) system
  • Figure 2 shows in diagrammatical form a data structure used in the CAE system of Figure 2:
  • Figure 3 shows a flow chart of a component definition procedure
  • Figure 4a is a screen of a GUI 190 for defining a specification level attributes of a component
  • Figure 4b is a component classification screen for adding specification level attributes into a component specification defined in Figure 4a;
  • Figure 5 is a connection points screen for defining connection points of a component specification defined in Figure 4a;
  • Figure 6 is a general details screen of a component instancing screen in the GUI of Figure 1 ;
  • Figure 7 is a specific details screen of a component instancing screen of the GUI in Figure 1 ;
  • Figure 8 is a loop design screen of the GUI in Figure 1.
  • the present embodiments are directed towards a computer aided engineering system 100 for instrumentation and electrical components, although it should be appreciated that the Computer Aided Engineering System is also applicable to areas, such as communications systems and piping systems.
  • the embodiments are directed towards a Computer Aided Engineering system that uses a database to model reticular systems of interconnected components.
  • the embodiments provide particular advantages in the design of components for populating the database in that they enable component specifications to be designed that have specification level attributes and instance level attributes.
  • the embodiments also provide particular advantage in the design of reticular systems as they provide multi-point connection points. These enable components to be designed that model components that have multiple numbers of connection points, such as a cable that bundles together multiple numbers of wires. It also
  • SUBST ⁇ J ⁇ SHEET (Rule 26) (RO/AU) enables the inter-connections between these components to be modelled. This enables users of the Computer Aided Engineering system to design components in the database that closely resemble the physical components of the system they are designing.
  • the computer aided engineering system of the embodiment utilises a data instantiation technique to minimise duplication of data entry in relation to components. This data instantiation is achieved by defining component specifications from which component instances are instantiated.
  • a component specification specifies the data attributes related to that component, and whether each data attribute is a specification level attribute or an instance level attribute.
  • Specification level attributes are attributes which are common to all instances of a component.
  • Instance level attributes are attributes that are dependent upon the particular instance of a component in question.
  • a component specification for a control card may include the number of input ports: the name of the card; the number of output indicators. Each of these attributes are common to all control cards of that type and are therefore specification level attributes.
  • Instance level attributes include what is connected to each of the input ports, the tag name of the particular control card; where the particular control card is installed.
  • a component specification defines the attributes of a specific type of component in an abstract manner. An instance of a component relates to a particular component. Referring now to Figure 1 , a preferred embodiment of a computer aided engineering (CAE) system 100 is depicted.
  • CAE computer aided engineering
  • the CAE system 100 comprises a data store 105 which stores data generated by the CAE system 100.
  • the CAE system 100 also includes a database management system (DBMS) 140 for generating and managing the data stored in the data store 105.
  • DBMS database management system
  • the DBMS achieves this by use of several tools, including a revision control and conflict management tool 145, a component specification and instance definition tool 150, a component connections tool 155, a project definition tool 160, and a drawing tool 165, a classification elements store 112 and a set of graphical symbols in component shape data store 114.
  • the CAE system 100 of the present embodiment is a networked version that provides the DBMS 140 with access to the data store 105 by means of an applications server tool 135 which communicates with a data server tool 115.
  • the data server tool accesses the data store 105 by means of a transaction management tool 110.
  • the CAE system also includes a client 185 which is in communication with a CAE graphical user interface (GUI) 190.
  • GUI graphical user interface
  • the client tool 185 communicates with the network 175 by means of a Public Switched Telecommunications network using preferably an ISDN line that feeds into a wide area network that connects to the network 175.
  • the CAE system however is not limited to having single user access.
  • the CAE system 100 may be arranged according to standard networking procedures so that it can be accessed by a number of users each by means of a separate CAE client 185 and CAE GUI 190.
  • the CAE system 100 may also be implemented in a freestanding version that is not networked.
  • CAE system 100 may be adapted to run on a number of different hardware platforms, including Unix TM platforms and Windows NT TM platforms.
  • the CAE client 185 and CAE GUI 190 may also be installed on a number of different hardware platforms, including personal computers (PC) running windows TM, Unix TM or Apple TM operating systems.
  • PC personal computers
  • FIG 2 is a diagrammatic representation of some of the various data types stored in the data store 105.
  • Some of these data types stored in the data store 105 include Area hierarchy data 200, component specification data 270, component instance data 230, project data 215, user data 210; revision level data 260, and component connections data 250.
  • Area hierarchy data 200 stored in the data store 105 shall now be described.
  • the Area hierarchy data 200 is a hierarchal definition of various physical locations with different engineering facilities, sites and/or systems which are modelled by the CAE system 100.
  • the engineering facilities may be an offshore facility called Off_Shore_Facility_A 202 and a refinery facility called Refinery_Facility_A 203.
  • Both Off_Shore_Facility_A 202 and Refinery_Facility_A 203 are one level down from a root level, called a root facilities level 201.
  • the root facilities level 201 contains data common to every engineering facility, site and/or system modelled by the CAE system 100.
  • Off_Shore_Facility_A data 202 One level down in the hierarchy from the Off_Shore_Facility_A data 202 is a number of sub areas (or zones) into which the Off_Shore_Faciiity_A data 220 is logically divided. Typically these sub areas will be modelled on the area tag names actually used on the facility that the CAE system 100 is modelling. In this example the name attributable for Off_Shore_Facility_A 202 has been designated as OSFA. Similarly a Power Generation building 235 on OSFA 220 has been designated name attribute PGB 204. Hence the unique tag for the power generation building 204 of OSFA 203 would be OSFA_PGB 204. Similarly a control room 205 in the PGB 204 may be assigned name attribute CR205. Hence its unique identifier in the Area hierarchy data 200 is OSFA_PGB_CR 205.
  • SIJBSTITUTE SHEET (Rule 26) (RO/AU)
  • Each level in the hierarchy may be viewed as a container.
  • the OSFA 202 level contains the power generation building level 204 and all of its sub levels including the control room 205 and the generation room 206.
  • the control room 205 and generation room 206 are each in turn contained within the power generation building 204.
  • User data 210 stored in the data store 105 shall now be described. It details a list of user identification (Id) attributes 211. There is provided one Id attribute 211 for each user. These Id attributes 211 serve to identify each user to the CAE system 100.
  • the user data 210 also includes an Authority level attribute 212 which defines the maximum authorisation level that a user can be assigned within a Project 215. Other data such as e-mail addresses 213 may also be contained in user data 210.
  • Project data 215 stored in the project data store 105 shall now be described.
  • Each project in the project data 210 serves to model a particular project being performed on one of the facilities that is modelled by the CAE system 100.
  • a project may be a maintenance project 217 to the control room 205 of the Power Generation building 204 on OSFA 202.
  • it may be installation project 218 for the installation of an additional generation plant in generator room 206 in the generation building 204 of OSFA 220.
  • Each of the projects in the project data 215 contains a project name 219 which uniquely identifies the project within the context of the project data 219.
  • a sub set of users from the user data 210 are assigned to each Project.
  • Each user in this sub set is assigned a user project Id attribute 221. This attribute uniquely identifies the user within the context of the project. It is a security measure allowing users to have different authority levels on different projects.
  • Each user assigned to a project is assigned a user approval level attribute 223. This provides each user with a certain level of authority within the context of the project for approving changes to design data.
  • Each project instance also has an authorised area attribute 224 which designates areas in the hierarchy data 200 which a project has access to.
  • the maintenance project 217 for the control room 205 may only be designated as having access to the actual control room 205 (as opposed to other rooms in the Power Generation Building 204).
  • the installation project 218 may be designated as having access to all rooms in the power generation building 204.
  • the authorised area data 224 for the control room maintenance project 217 will reference area data for OSFA_PGB_CR 205 in the area hierarchy data 200.
  • the authorisation area data 224 for the installation project 218 will need, only reference the Power_Generation_Building tag 204 (namely OSFA_PGB 204) in order to authorise access of the installation project 218 to every room in the power generation building 204.
  • Project data 215 may be viewed as a set of containers for the various components and connections (detailed further below) within the CAE system 100. In this regard each component and connection is reserved against a project.
  • Components and connections that are reserved against the "As Built Common" project are free to be reserved by any project, such as the maintenance project 217 or the installation project 218. Components and connections reserved against a project other than the "As Built Common" project can not be reserved against any other project. This means that only one project can access and amend a particular instance of a component or connection at any one time.
  • SUBS ⁇ TUTE SHEET (Rule 26) (RO/AU)
  • Each revision (amendment/change) of a component 231 and a connection 251 is provided with a name using a revisions Name Attribute 267.
  • An attribute called next revision 269 indicates the next revision level 269 in the sequence of revision levels 260 assigned to a project.
  • An "As Built” 268 flag in the revisions level data 260 when set to “TRUE” indicates that the component or connection will move to the "As Built Common” project when it issues at the "As Built” revision level.
  • the pre-defined set of revision levels 260 conforms to standard engineering methodology such as ""As Built”” revision, "Revision A”, “Revision B” etc
  • Each revision level is assigned a minimum approval level Only users 211 nominated on a project with an appropriate approval level 223 (or higher) can authorise that a particular revision to a component or connection in the CAE system 100 can be marked off as approved.
  • Revisions data 250 also contains a set of approval levels 220, such as client level, chief engineer level, engineer level, maintenance level, commissioning engineer level etc A sub set of these approval levels may be selected for the different revision levels 260 of a project. This enables the revisions process for different projects eg a maintenance project, to have different sets of authorisation levels than eg an installation or retro-fit project.
  • approval levels 220 such as client level, chief engineer level, engineer level, maintenance level, commissioning engineer level etc
  • Each approval level 220 in a revision 260 corresponds with one of the approval levels 223 assigned to the users of the project.
  • Component instance data 230 stored in the data store 105 will now be described
  • Each component instance 231 in the component instance data 230 identifies a unique component such as a field device or cable within one of the engineering facilities modelled by the CAE system 100.
  • a component instance 231 may be one of many indicator lights each of which is installed on one of several switch boards Each of the switch boards being located in the control room 205 of the power generation building 204 on the OSFA 202.
  • Each component instance 231 in the component instance data 230 has a component instance Id attribute 237 which serves to uniquely identify each component of each facility modelled by the CAE system 100.
  • Each component may exist several times within the set of component instances 215 so as to represent the component at different revision levels. This is because some of the components data may change as it progresses from revision level to revision level.
  • the component history Id attribute 238 operates as an alternate key for the component instances. It allows the various instances of a component at different revision levels to be distinguished from each other as well as from different components.
  • Each component instance 231 has an Area attribute 235 which references an area attribute in the Area hierarchy data 200.
  • This area attribute 235 such as OSFA_PGB_CR 205 identifies the location of the component on the modelled facility.
  • Each component may also have a component container Id attribute 239 which identifies whether or not a component is contained by another component.
  • component container Id 239 for the indicator lights will reference the panel on the switchboard on which the light is located and the component container Id 239 for each panel will reference the switch board cabinet in which they are located.
  • the component container Id 239 for the switch board cabinet will typically be "null", unless it is itself contained within another component.
  • Each component instances 231 has a project attribute 236.
  • the project attribute 236 references a project in the project data 215 which has reserved the component instance 231 thereby preventing access to the component by all other projects. Only one project instance may reserve a particular component instance 231 at any one time. If the component instance 231 is not reserved by a project instance then the project attribute 236 references an "As Built Common" project 215. This component instance reservation feature has application in revision control and conflict management procedures of which greater detail is provided below.
  • a revisions attribute 234 identifies the revision level which a component instance has been approved to within a project.
  • a component instance may represent an "As Built” component in which case the component is referenced as belonging to the "As Built Common” project 216 for the facility on which the component is located.
  • it may be authorised at "revision level A” or at “revision level B" within the project against which the component instance 231 is reserved.
  • a new instance of the component be created that is, at least in part, identified by its revision level attribute. This enables a component, as it was issued, at various revision levels throughout a project's history to be reviewed.
  • the component and its connections to other components may be issued by different projects.
  • each component instance 231 may have one or more connection point attributes 240.
  • a connection point is a point where a component physically inter connects with another.
  • a connection point may refer to an electrical connection or it may refer to a mechanical or hydraulic connection.
  • Connection point attributes 240 include a multi-point attribute 245. This attribute specifies whether or not the connection points 241 of the component instance 231 are grouped together or whether they are regarded as individual connection points.
  • An example of a multi-point connection point is a three pin power plug for domestic power.
  • the three pin plug has three terminals, positive, neutral and ground. Each of these terminals is a connection point within the CAE system 100. However the three terminals operate as a single unit as mechanically it is not possible to connect any one of the terminals to a power outlet without also connecting the other two at the same time. In this sense a three pin plug is a component that has a multi-point connection attribute.
  • a multi-point connection attribute 245 of connection data 240 may be used to check that design data for inter connecting components specifies two components that are mechanically capable of forming an inter connection.
  • connection point data 240 of the component specification also has a label attribute 242 which is a unique name assigned to each connection point of a component. It also has a ferrule attribute 243 which corresponds to the ferrule name of a component.
  • the CAE system 100 has a further data set, namely a connections data set 250.
  • This data set details which connection points 241 inter connect to form an instance of a connection 251.
  • the connection data set 250 can be seen to reference connections 251 between components 231.
  • connection data set 250 details for each connection 251 which connection point 241 of which component 231 is on the left of the connection 251 with respect to the loop of component which the connection 251 is in. It also specifies which connection point 241 is on the right hand side of the connection 251. This is achieved using two attributes, namely a "connection point on the left” attribute 254 and a "connection point on the right” attribute 255.
  • connection 251 is also flagged against the project data 215 and revisions data 260 in a similar manner to component instances 231.
  • a revision control process and a conflict management process used by the revisions control and conflict management tool 145 computer aided engineering system 100 will be now be described.
  • FIG. 3 details a process by which component specifications may be defined from a set of pre-defined classification elements.
  • the process instantiates component instances using the component specification.
  • a pre-defined set of classification elements from the classification elements store 112 are displayed, by means of a GUI 190.
  • Each element represents a portion of a component specification.
  • the component specification is a class definition of the component that is stored in the component specification data 220.
  • An instance of the component may be created from a component specification.
  • this combining of classification elements is achieved in the GUI 190 environment by use of a drag and drop procedure well known in the art.
  • a user selects a set of specification elements sufficient to define a component specification. The user then combines the selected elements.
  • the GUI 190 prompts the user for data values in respect of specification level attributes. The user enters these values and at step 315 the component specification is stored in component specification data 270.
  • a user decides to create an instance of a component. Accordingly the GUI 190 displays a set of component specifications that have been stored in the component specification data 270 and the user selects the desired component specification.
  • the GUI 190 prompts the user, to enter instance related data into the component specification.
  • the component specification with instance related data is instantiated by being stored in the component instance data 230.
  • a list of component instances may then be displayed by the GUI 190 to confirm that the instance has been created.
  • FIG. 4a is a component specification screen 400 of the GUI 190.
  • the component specification screen 400 is used for defining component specifications within component specification data 270.
  • a component specification defined by use of the component specification screen 400 may later be instantiated by use of an instancing means.
  • a component specification is a class definition of a component.
  • a component specification that is instantiated by use of an instancing means forms a component instance that is part of the component instance data set 230.
  • the component specification screen 400 has a description window 405 that corresponds with description attribute 232 of the component specification data set.
  • the description of the component specification comprises three elements which are, in order of left to right in the window 405, a field defining the type of component, a field defining the manufacturer of the component and a field defining the model number of the component.
  • the component specification is of a type that is an R/O Module that is manufactured by a company called Triconex and its model number is 3636R.
  • the component specification screen 400 also has a detail screen 430 and a connection point screen 445.
  • the detail screen 430 is shown in Figure 4 and the connection point screen in Figure 5.
  • the detail screen 430 has an attributes window 407.
  • the attributes window 407 lists the attributes of the component specification referred to in the description window 405.
  • the various attributes of a component specification will typically assume a hierarchical structure. Each attribute representing a node in this hierarchy.
  • instance level attributes 415 and specification level attributes 420 are attributes that are assigned a value at the specification level, ie the class level.
  • Specification level attributes preferably cannot be changed when instantiating a component instance from a component specification. It should be noted that it is preferable that a user cannot enter attributes into instance level attributes 415 from the component specification screen 400. The values for these instance level attributes 415 are defined when a component instance is instantiated from a specification by use of an instancing means.
  • the component specification screen 400 is a specification means.
  • the detail screen 430 comprises an add classification button 435 and a remove classification button 440. These buttons enable additional classification elements from a library of classification elements to be added to the component specification. Similarly the remove button 440 enables attributes to be removed from the component specification.
  • the GUI 190 prompts the user with a component classification hierarchy screen 470 that is shown in Figure 4b.
  • This component classification screen 470 displays a library of classification elements. These elements are preferably a hierarchical set of attributes 472, defined according to an Object Oriented technique referred to as an Inheritance/Specialisation/Generalisation technique.
  • the hierarchy of classification elements 472 has a number of root level classifications 495 that include a component classification 410. This component classification 410 is used by an operator when defining a component specification 406 within the component specification screen 400.
  • the root level classifications may also include additional classification information, such as electrical data, process information, process connection and reference drawing classifications. These additional classifications enable additional information to be associated with a component without the information becoming an attribute of the component.
  • This attribute hierarchy 472 comprises a number of root attributes including root level specification attributes 420 and root level instance attributes 425.
  • the Connecting Component sub-classification 475 has two specification level attributes 480 that relate to the length of the connecting component and the power distribution circuit that the connecting component is connected to.
  • the connecting component sub-classification 475 also has a further two sub- classifications namely a cable sub-classification 485 and a tubing sub- classification 486. Within each of these sub-classifications there will be further instance level attributes and specification level attributes, there may also be further sub-classifications. Similarly the cabinet sub-classification 490 has a further hierarchical definition of sub-classification folders and of instance level attributes and of specification level attributes. Accordingly each attribute forms a node in the hierarchy of classification elements.
  • the component classification screen 470 is displayed by the GUI 190 when an operator of the CAE system 100 selects the add classification button 435 of the component specification screen 400.
  • the hierarchy of classification elements 472 a user selects classifications that are required to be incorporated within the component specification that is being defined within the component specification screen 400.
  • the cable sub-classification 485 has been selected by a user. This selection maybe indicated by the GUI 190 highlighting the word Cable of the Cable sub-classification 485.
  • the Cable sub-classification 485 ail of the attributes and sub-classifications that are within the cable sub-classification 485 are imported into the component specification 406 presently being defined in the component specification screen 400.
  • the hierarchical structure of the attributes and sub-classifications are retained.
  • the Cable sub-classification 485 also inherits all of the attributes that are on its level or higher in the hierarchy of component attributes.
  • Cable sub-classification 485 will import into the component specification the instance level attributes 480 of the connecting component sub-
  • the component specification folder 410 When importing sub-classifications into a component specification 406 only those attributes that do not already exist within the component specification are imported. Hence for the first sub-classification that is selected for a specification all of the root level attributes 420 and 425 are imported.
  • the component specification folder 410 will preferably be imported and displayed in the attribute screen 407.
  • the root level attributes 420 and 425 should be suspended from the component specification folder 410.
  • the Cable sub-classification 485 is imported into a specification, then the component specification displayed in the attribute screen 407 will display a component folder which has suspended therefrom in the hierarchy of attributes a Connecting component folder 475 and the length and power attributes 480 along with the cable sub-classification folder 485 and any attributes within that folder.
  • Cabinet sub-classification 490 is selected to be imported into the component specification 406 then a user will preferably see the Cabinet sub- classification folder 490 appear on the attribute window 407. The imported Cabinet sub-classification 490 will retain the same hierarchical relationship with the component classification folder 410.
  • the attributes within the hierarchy of classification elements 472 are predefined as either being specification level attributes or instance level attributes.
  • An alternate embodiment may allow an operator to define which of its attributes are specification level and which of its attributes are instance level.
  • quality assurance procedures used in design of engineering facilities prefer that the specification level attributes and the instance level attributes are pre defined for the user.
  • the component specification screen 400 contains a further five control buttons mainly a new button 450. a clone button 455, an update button 460, a delete button 465. and a close button.
  • the new button 450 is selected by an operator when a new component specification is to be defined
  • the clone button is used to generate a copy of a component specification which may then be modified to create a new specification.
  • This button is a short cut button that provides an easier method of generating a component specification once a similar component specification has been defined.
  • the update button enables an existing component specification to be amended by means of inserting or removing attributes or by means of changing data values entered into specification level attributes.
  • the delete button 465 deletes a component specification from the component specification data 270.
  • connection points screen 445 of the component specification screen 400 contains the description window 405 as seen within the detail screen 430 and it also contains the new button 450, the clone button 455, the update button 460, the delete button 465, and the close button.
  • connection points screen 445 is used for defining the connection point data 275 of a component specification 271.
  • the connection point screen 445 contains three data sets that relate to connection point data 275 of a component specification 271
  • connection point data 505 A first of these three data sets is connection point data 505.
  • a connection point of a component is a point where the component is inter connected with another component
  • a power outlet of a domestic power circuit typically contains three connection points namely a positive connection point, a neutral connection point, and an earth connection point.
  • each of these connection points are connected with a corresponding connection point of a three pin plug when a power cord containing the three pin plug is connected to the power outlet.
  • a user may enter the name "positive terminal” against data item #1 , 506 of the connection point data 505, "neutral terminal” against data item #2, 506 and "earth terminal” against data item #3, 507, of the connection point data 505.
  • connection point data 240 of component specification 271 there are three connection points named respectively, "positive”, “neutral” and “earth” within a "power outlet”.
  • connection point data 505 For example a user may define that connection point four 509, is a positive terminal, that connection point five 511 is a neutral terminal and that connection point six 512, is an earth terminal. The user again selects the insert button so as to enter these connection points into connection point data 240 of component specification 271.
  • connection points for the power outlet Before defining the connection points for the power outlet the user will be aware that the power outlet contains three connection points. The user will also be aware that these three connection points operate mechanically as a single unit that can only receive compatible three pin plugs. This mechanical nature of a three pin power outlet is captured within connection point data by defining a multipoint connection within the multi-point connection data set 565.
  • the first three pin plug is a multi-point connection called cable socket A and the second three pin plug a multi-point connection called cable socket B.
  • connection point data 240 of the component specification 271 After selecting the insert button 510 for the connection point data that relates to connection points 1 , 2 & 3, the user selects a "No. to insert” window 520. The user then details within this "No. to insert” window 520, the individual connection points within the connection point data 505 that are to be inserted into a multi- point connection. The user then selects one of the previously defined multi-point connections within the multi-point connection data 565. Upon selecting the insert button 510 the connection points that are highlighted in the "No. to insert" window 520 are defined within the connection point data 240 of the component specification 271 as being associated with the selected multi-point connection.
  • first set of three connection points may be associated with the cable socket A multi-point connection so as to represent a first three pin power outlet within the component specification.
  • second set of three connection points may be associated with the cable socket B multi-point connection so as to represent a second power outlet within the component specification.
  • sets of individual connection points 505 are associated with multi-point connections 565 so as to represent that a set of connection points physically exist within a multi-point connection device.
  • Additional multi-point connections maybe inserted or removed from connection data 240 of a component specification 271 by use of insert button 555 and remove button 560 respectively.
  • insert button 555 When the insert button 555 is selected, a new data element appears within the multi-point connection data set 565. The user is required to enter a name into this new data element within the multi-point connection data 565.
  • Multi-point connections enable operators of the CAE system 100 to connect components having multiple numbers of connection points together.
  • connection points within a multipoint are ordered in some manner so that corresponding connection points of connecting multi-points are connected together.
  • the multi-points model the operation of real world multi-point connectors. This allows operators of the CAE system 100 to connect components in the same way they would real world components.
  • the remaining set of data within the connection points screen 545 is the grouping data.
  • Grouping data represents that a number of connection points are physically connected or logically associated internally to a component. It is typically used where a component has more than two connection points.
  • An example of a simple device where groups of connection points are logically connected is a relay.
  • a typical relay has input terminals that receive a control current. The control current is used to trip the contactors of the relay.
  • the contactors of the relay are typically connected to a separate circuit to that of the control current. Typically the contactors of the relay are used to activate and deactivate a power circuit.
  • connection points 1 and 2 are connection points 1 and 2 in connection point data 505 and that the contactor terminals of the relay component are connection points 3 and 4 in connection point data 505.
  • the control terminals, namely connection points 1 and 2, and the contactor terminals, namely connection points 3 and 4 will form a group of connection points within the connection point data 240 of the component specification data 271.
  • Group data is used in modelling circuits (often referred to as loops) of components by the CAE system 100.
  • the relay components connected to the contactor terminals of the relay namely components connected to connection point 3 and connection point 4 of the relay will form part of a loop that is controlled by the relay controls.
  • that loop will include the control terminals, namely connection points 1 and 2 of the relay component.
  • a group of connection points may contain connection points from different multipoint connection points.
  • An example where this may occur is an electrical termination panel (ETP).
  • ETP electrical termination panel
  • An electrical termination panel often contains a series of individual terminals where individual cores (wires) are terminated. These individual cores are often associated by means of control logic and power circuitry, with one or more connection points of a multi-point connection terminal.
  • a multi-point connection terminal may receive data input on several of its pins that in turn cause a control current or a power current to be activated on two or possibly three of the individual connection points. This may occur where for example the electrical termination panel receives data input on three channels from some form of control device.
  • These data channels may be converted by means of control logic internal to the electrical termination panel into a power current that appears on two connection points terminated individually within the series of individual terminals.
  • a loop involving the electrical termination panel would see a multi-point connection on say, the right-hand side of the electrical termination panel.
  • This multi-point connection would also be seen as activating two individual connection points on the corresponding left-hand side of a loop containing the electrical termination panel.
  • an electrical termination panel that receives three input channels on three pins of a multi-point connection socket. These three channels activate two separate sets of terminals. Each separate set of terminals operates a separate control circuit. These control circuits operate individually of each other. In this sense the electrical termination panel may be regarded as a branch element in a loop as it has one input on, say, the right-hand side of the loop which branches into two outputs on the corresponding left-hand side of the loop.
  • connection points that are driven by the three channel input are located on separate multi-point connections.
  • three sets of connection points (one input set and two output sets) are associated with three different multi-point connections.
  • each of these connection points are contained within the one group as they all form part of the one loop.
  • a multi-point connection may contain connection points that belong to several different groups of connection points.
  • the multi-point connection referred to above that has the three channel input may also contain further sets of connection points that receive separate input data streams. These connection points that receive separate input data streams preferably form a separate group within the multi-point connection point.
  • To define a group of connection points an operator selects "Group name" window 535 and enters a group name. This defines a new group within group data 545. The operator then inputs a connection point into a connection point tile 541 , along with a group number in a corresponding group tile 546 that the connection point is to be associated with.
  • the multi-point connection, if any, that the group is also to be associated with is entered into a corresponding multi-point tile 547.
  • a component specification may have a multitude of different groups as demonstrated by group data 545.
  • groups of connection points maybe disassociated within connection point data 240 by selecting a group name within the group name window 535 and selecting the ungroup button 530.
  • an individual connection point 540 within the group data 545 may be removed from a group by selecting the ungroup button 530.
  • individual connection points maybe inserted into a group in a similar manner using the group button 525.
  • connection points may also be associated with a multi-point connection point.
  • connection point 1 is associated with group 1 and group 1 is associated with a multi-point connection point called "CblScktA.”
  • connection point 2 is associated with group 2 and group 2 is associated with a multi-point connection point called "CblScktA”.
  • each group of components only contains a single connection point, however, groups may contain a greater number of connections points.
  • This association of groups of connection points with multi-point connection points operates to define the connections between connection points in two multi-point connection points that will occur when the multi-point connection points are connected.
  • group data When associated with multi-point connection points, assume that two multi-point connections points each having three groups of connection points are connected. Each group will be assigned a unique name within the multi-point connection point.
  • corresponding groups in the two multi-point connection points are defined as being connected. It is convenient that the groups be named in a sequential numerical or alphabetical order so that each group of connection points labelled as "group 1" in the two multi-point connection points will be defined as corresponding groups. Hence the two corresponding groups of connection points are defined as being connected.
  • these connections will be recorded in connections data 250.
  • a user may be prompted to define which groups of the two multipoint connection points are to be connected together when a connection between two multi-point connections is requested.
  • connection points This association of groups of connection points with multi-point connection points enables a loop to be identified from a set of components with multi-point connection points. This is because the groups allow the connections and connection points that form part of a loop to be identified separately from the other connections and connection points with each multi-point connection point.
  • FIG. 6 is an instancing means for generating component instances 231 from component specifications 271.
  • the instancing means comprises a component instancing screen 600 which has two sub screens within it namely a General Detail screen 670 and a Specific Detail screen 675. Both screens have three windows namely a TAG No / ITEM window 605. an area window 610 and a component specification window 615.
  • the component instancing screen 600 also contains a new button 620 for use in generating new component instances 231 from a component specification 271.
  • a clone button 625 for generating a new component instance from an already existing component instance.
  • An update button 630 for use in amending attribute data of an existing component instance 231.
  • a delete/demolish button 635 for use in deleting component instances.
  • the delete/demolish button demolishes causes component instances to be deleted from the data store 105 when they are reassigned to the "As Built Common" project.
  • a revisions button 605 for use in approving a component specification at a revisions level.
  • a transfer button 650 for use in transferring a component specification from one project to another, and a close button for closing the component instancing screen 600.
  • the TAG No. / ITEM window 605 is a window that defines a unique name for the component being instantiated. Within the component instance data set 230 the tag name 606 entered into the TAG No. / ITEM window 605 constitutes the component instance Id attribute 237.
  • the area tag 611 entered into the area window 610 constitutes the area attribute 235 of the component instance 231 that is being instantiated by the component instancing screen 600. This attribute identifies the location of the component instance 231 relative to the area hierarchy data 200.
  • the general detail screen 670 comprises a containership window 656.
  • the containership window 656 contains a graphical display of the area hierarchy data 200.
  • the hierarchy data 200 maybe expanded to show the location of components within each area of the area hierarchy data 200.
  • an area icon 655 that represents the area attribute 235 of the component 660 that is being instantiated by the component instancing screen 600 is displayed. Suspended from the area icon in a hierarchical manner is the component 660 presently being instantiated by the component instancing screen 600. This relationship indicates that the component 660 is located within an area of a facility indicated by its area icon 656
  • component 660 has its component container Id attribute 239 set to null. This is because the component is not contained within any other components within the area indicated by area icon 656.
  • each of the child components is graphically indicated as being suspended from their parent component 660. This indicates that each of the child components has their component container Id attribute 239 set to indicate that they are contained within their parent component 660.
  • a switchboard chassis may be represented by parent component 660 and each of the child components may represent items such as rails, relays, terminal blocks, controllers, switch gear, and panels that are commonly found within a switchboard chassis
  • the series of child components 665 may also have a hierarchical structure.
  • a first child component in the series may have its component container Id attribute 239 set so as to indicate a parent component that is itself a child component of the parent component at the root level of the component hierarchy
  • the parent component of the first child component will have its component container Id 239 set to indicate the parent component 660 at the root level of the component hierarchy
  • the containership window 656 contains a check box called show demolished 667 and a resequence button 666
  • the resequence button 666 enables a user to change containership relationships between components displayed within the containership screen 656. For example a user will select a component. The user will then select resequence button 666 and this will enable the user to move the icon of the selected component into a new containership relationship with another component. Once the component has been moved into its new containership relationship the update button is selected and the changes are stored within the data store 105.
  • the show demolished check box 667 indicates that a component is to have its project tag 236 set to a demolished project when the component issues at the "As Built" level. This is achieved by an operator selecting a component that is to be demolished then selecting the delete/demolish button 635. Upon selecting the delete/demolish button 635, the user is prompted as to whether they wish to delete the component or demolish the component. When the user selects that they wish to demolish the component the check box 667 is then marked to indicate that the component will be demolished when it is approved at the "As Built" level.
  • This demolished feature will typically be used to indicate that a component on the facility has been decommissioned and removed from the facility.
  • FIG. 7 shows the specific detail screen 675 of the component instancing screen 600.
  • the specific detail screen 675 has a hierarchical list of component attributes 700. These component attributes correspond with the attributes defined by the component specification 616 detailed in the component specification window 615.
  • the hierarchical attributes 700 have instance level attributes 415 and specification level attributes 420
  • the data values for the specification level attributes 420 were entered into the specification when the specification was defined using component specification screen 400.
  • instance level attributes so as to instantiate a component a user selects, in turn, each instance level attribute 415. Upon selecting an instance level attribute the GUI 190 prompts the user to enter data values for that attribute. This process is repeated for each specification level attribute in the component specification. When completed the component may be instantiated by selecting the update button 630 which stores the component instance with instance level attributes in the component instance data 230.
  • FIG. 8 is a loop design screen 800 for use in defining connections between components.
  • Connections between components are defined using connections data set 250.
  • the connections data set 250 references connection point data 240 in the set of component instances 230.
  • Connections data 250 contains a connection name attribute 251 , a revisions attribute 252, a project attribute 253, a connection point on left attribute 254, a connection point on right attribute 255, and a demolished attribute 256.
  • connection name attribute 251 uniquely identifies connections between two connection point attributes 241 of two different component instances 231.
  • the revision attribute 252 of the connection data defines a set of revision levels through which a connection must pass in order to be issued at the "As Built" level.
  • the project data 253 of the connection point data 250 reserves each connection against a project in the project data 215. This enables connections between connection points to be defined by separate projects to those that have reserved the component instance 231 containing the connection points.
  • the loop design screen 800 is used to define connections between components.
  • a series of components that are connected together to form a circuit are commonly referred to as a loop of components.
  • a component such as a control unit that is located in a switchboard is referred to as a system component.
  • a field device such as a sensor, a power outlet or a light globe
  • Convention also dictates that when a loop is drawn, system components are on the right hand side of the loop and field devices are on the left hand side of the loop.
  • Different embodiments may choose to follow a different loop definition convention. In the convention of the present embodiment a loop is depicted graphically as a sequence of components one adjacent to the other.
  • the order of components in a loop is dictated by the sequence of components that extend between field devices on the left of a loop and system components on a right of the loop. This sequence can be determined by 1) identifying the components in a loop; 2) identifying field devices and system components in the loop; and 3) identifying the connections between all of the components so that the relative positions of the components is determined.
  • the loop design window has seven component windows namely a first component window 801 , a second component window 804, a third component window 805, a fourth component window 808, a fifth component window 810, a sixth component window 813, and a seventh component window 815.
  • An unrestricted number of component windows and connection point panels may be added to the loop design screen 800. Scroll bars may be used to view the different component windows and connection point panels.
  • Each component window has a corresponding connection point panel.
  • the first component window 801 has a first connection point panel 819.
  • the second component window has a second connection point panel 820
  • the third component window 805 has a third connection point panel 821
  • the fourth component window has a fourth connection point panel 822
  • the fifth component window has a fifth connection point panel 823
  • the sixth component window 813 has a sixth connection point panel 824
  • the seventh component window 815 has a seventh connection point panel 825.
  • Each component window details one or more icons that represent one or more components and their containership hierarchy.
  • the connection points detailed in the connection point panel correspond to the component selected in the component window. More than one component and its containership hierarchy may appear in a component window.
  • Components are preferably located in a connection point panel by a drag and drop procedure well known in the art. For example, a component specified in the general details screen 600 may be dragged onto and then dropped into a component window. This results in the component and its containership hierarchy appearing in the component window.
  • connection point panel details the connection points of the component selected in the component window.
  • the connection points are detailed under a column of elements called the label column 831. Adjacent to the label column are two further columns namely a #L column 832 and a #R column 833.
  • the entries across a row of a connection point panel relate to one individual connection point. Hence a #L element indicates the number of components that are connected to the connection point on the left hand side of the loop. Similarly a #R element 833 indicates the number of components that are connected to the connection point on the right hand side of the loop. Hence by summing the entries in the #L element and the #R element the number of components connected to a connection point can be determined.
  • the number of components connected to the left and the number of components connected to the right of the connection point can be determined.
  • an operator will select those components that are to be connected together. These components will then be displayed within component windows of the loop design window 800. The user organises these components so that field devices are on the left and so that system components are on the right of the window. The user then selects the connection points of each component that are to be connected together.
  • the visual layout of the loop design screen it is preferably if only connection points in adjacent panels can be connected together. Other visual layouts for the loop design screen 800 may be used. Such alternative layouts may require different rules for the connecting of connection points.
  • a user will highlight a first connection point in the first connection point panel 819 and select a second connection point in the second connection point panel 820.
  • a connection 251 is formed within the connections data 250. This connection indicates that the selected connection point in the first connection point table is connected to the connection point selected in the second connection point table 820.
  • connection point has a value of 2 or greater in its #L or #R element, it indicates that the connection point is a branch in a loop.
  • the component window on the left there may be two or more separate components that the branch is connected to.
  • each connection from the branch element to its connecting components on the left or right be made separately. This may require two or more components to be located in a component window adjacent a branch element. These two or more components may be located in a component window at any one time by dragging for example a second or a third component, as required, into the component window adjacent the branch.
  • a connection point in a connection point tile it may be a multipoint connection point.
  • the CAE system 100 preferably operates to check that the connection point that the multi-point is being connected to is also a multi-point connection point. Some embodiments may also check that the multi-point connection points are mechanically compatible. This may be achieved by assigning a label to the multi-point connection point when being defined. A compatibility list may then be used to cross check multi-point connection points with different labels as to their compatibility.
  • connection points are defined being connected.
  • connection points are defined so that corresponding connection points in the multi-points are connected together.
  • the groups are preferably treated in an identical manner as individual connection points so that a single connection point in one multi-point is connected with a group of connection points in their connecting multi-point.
  • each connection point in a multi-point is assigned to a group.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Evolutionary Computation (AREA)
  • Geometry (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Cette invention se rapporte à un système de définition de composants, qui sert à définir les composants d'une application et qui est conçu pour définir des instances de composants ayant des attributs de niveau de spécification et des attributs de niveau d'instance, ce système de définition de composants étant conçu pour définir les valeurs de ces attributs de niveau de spécification en définissant des spécifications de composants ayant au moins un attribut de niveau de spécification à partir duquel les instances de ce composant sont définies.
PCT/AU1999/000614 1998-07-31 1999-07-30 Systeme d'ingenierie assistee par ordinateur et procedes d'exploitation de ce systeme WO2000008574A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU51405/99A AU5140599A (en) 1998-07-31 1999-07-30 Computer aided engineering system and methods of operation therefore

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
AUPP4995A AUPP499598A0 (en) 1998-07-31 1998-07-31 Computer aided design system and aspects thereof
AUPP4995 1998-07-31
AUPQ1261A AUPQ126199A0 (en) 1999-06-28 1999-06-28 Revision control system
AUPQ1260 1999-06-28
AUPQ1261 1999-06-28
AUPQ1260A AUPQ126099A0 (en) 1999-06-28 1999-06-28 Computer aided engineering system
AUPQ1769 1999-07-22
AUPQ1769A AUPQ176999A0 (en) 1999-07-22 1999-07-22 Dynamic loop generation system

Publications (1)

Publication Number Publication Date
WO2000008574A1 true WO2000008574A1 (fr) 2000-02-17

Family

ID=27424471

Family Applications (3)

Application Number Title Priority Date Filing Date
PCT/AU1999/000615 WO2000008575A1 (fr) 1998-07-31 1999-07-30 Systeme et procede de controle des revisions dans une application
PCT/AU1999/000614 WO2000008574A1 (fr) 1998-07-31 1999-07-30 Systeme d'ingenierie assistee par ordinateur et procedes d'exploitation de ce systeme
PCT/AU1999/000616 WO2000008576A1 (fr) 1998-07-31 1999-07-30 Systeme et procede pour generer des representations graphiques de boucles de composants

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/AU1999/000615 WO2000008575A1 (fr) 1998-07-31 1999-07-30 Systeme et procede de controle des revisions dans une application

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/AU1999/000616 WO2000008576A1 (fr) 1998-07-31 1999-07-30 Systeme et procede pour generer des representations graphiques de boucles de composants

Country Status (1)

Country Link
WO (3) WO2000008575A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8595201B2 (en) 2011-10-27 2013-11-26 International Business Machines Corporation Version visualization

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0344497A2 (fr) * 1988-05-13 1989-12-06 Hitachi, Ltd. Méthode et système d'aide à la procédure de conception
JPH08153131A (ja) * 1994-11-28 1996-06-11 Hitachi Ltd 情報ネットワークの設計支援システム
JPH0954799A (ja) * 1995-08-17 1997-02-25 Nec Corp マシン構成決定支援システム
WO1998012655A1 (fr) * 1996-09-17 1998-03-26 Hitachi, Ltd. Procede de configuration d'un circuit integre a semi-conducteur

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4939668A (en) * 1987-08-24 1990-07-03 International Business Machines Corp. System for designing intercommunications networks
US5617327A (en) * 1993-07-30 1997-04-01 Xilinx, Inc. Method for entering state flow diagrams using schematic editor programs
WO1995032481A1 (fr) * 1994-05-24 1995-11-30 Imp, Inc. Circuit integre comportant des modules analogiques programmables avec des interconnexions configurables entre eux
US6120550A (en) * 1996-10-28 2000-09-19 Altera Corporation Design file templates for implementation of logic designs

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0344497A2 (fr) * 1988-05-13 1989-12-06 Hitachi, Ltd. Méthode et système d'aide à la procédure de conception
JPH08153131A (ja) * 1994-11-28 1996-06-11 Hitachi Ltd 情報ネットワークの設計支援システム
JPH0954799A (ja) * 1995-08-17 1997-02-25 Nec Corp マシン構成決定支援システム
WO1998012655A1 (fr) * 1996-09-17 1998-03-26 Hitachi, Ltd. Procede de configuration d'un circuit integre a semi-conducteur

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
DATABASE WPI Derwent World Patents Index; Class T01, AN 1996-331078/33 *
DATABASE WPI Derwent World Patents Index; Class T01, AN 1997-199033 *
DATABASE WPI Derwent World Patents Index; Class T01, AN 1998-217507/19 *

Also Published As

Publication number Publication date
WO2000008575A1 (fr) 2000-02-17
WO2000008576A1 (fr) 2000-02-17

Similar Documents

Publication Publication Date Title
JP6388682B2 (ja) グラフィック・プログラミング言語オブジェクトを編集及び報告する方法及び編集・報告システム
US6473762B1 (en) System and method to automatic equipment placement at remote sites
US5293479A (en) Design tool and method for preparing parametric assemblies
US7143341B1 (en) Method and apparatus for concurrent engineering and design synchronization of multiple tools
US7765529B1 (en) Transforming graphical objects in a graphical modeling environment
CA2235366A1 (fr) Procede et appareil permettant la configuration automatique et interactive de produits personnalises
US20080115104A1 (en) Software development system and method for intelligent document output based on user-defined rules
US6098050A (en) System and method for recording, maintaining and viewing configuration and placement of equipment in field sites
CN101520657A (zh) 在过程控制系统中用于绑定属性的方法及设备
CN107368043B (zh) 配方管理控制系统
CA2211592A1 (fr) Procede et dispositif de constitution d'une base de donnees d'un reseau de telecommunications
WO1995034866A1 (fr) Procede et systeme de manipulation de representations intelligentes de materiel reel dans un systeme informatique graphique
WO2011146309A1 (fr) Interface utilisateur graphique basée sur des feuilles de calcul et permettant une modélisation et une simulation d'un système dynamique
US8160843B2 (en) Device and method for planning a production unit
WO2000008574A1 (fr) Systeme d'ingenierie assistee par ordinateur et procedes d'exploitation de ce systeme
US7505821B2 (en) Layout-oriented recording of automation information
Bougouffa et al. Visualization of variability analysis of control software from industrial automation systems
US6141016A (en) Method for inputting and acquiring requirement
JP2001195255A (ja) オブジェクトの生成支援方法および装置
Heino Comparing commercial engineering program for DCS-systems
Gračanin et al. Implementation of a dynamic scheduler for apparel computer integrated manufacturing systems
CN117608524A (zh) 一种基于图形化方式的项目需求信息架构管理系统
Dobrescu et al. Dedicated software for fieldbus control applications
HIDDE Management of information in a system of heterogeneous distributed data bases using the example of a PCB assemblage
Scott et al. A Knowledge-Based System for the Configuration and Pricing of Network Management Systems

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG US UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SL SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: CA