Metadata Browser

• The metadata browser describes the S3D type system.

• The sniffers start with a selected object and use the type system to view the actual values on an
object. That is:
o The Interface that are implemented.
o The values of the attributes
o The actual relationships between object
• The type system was built for the programming environment. The object sniffer works over this
model

Schema Browser Tool

• A regular folder represents a package i.e. metadata of a service

• A red pyramid represents a class. A red pyramid overlayed by a yellow crown represents a first
class, i.e. a class that is a leaf in the BOC (Business Objects Classification) hierarchy

• A green box represents a property.

 Relationships

• Relations are binary

• A relation is between two and only two entities.

• These entities are known as origin and destination of the relation

Example: SOtoSI relationship (There is a relation between smart occurrence and the smart item).

• A single magenta sphere represents a relationship. A single magenta sphere overlayed by a

fence represents a private relationship.

• Double magenta/purple spheres represent a relationship collection (a role).

• An orange diamond represents an Edge, i.e a virtual relationship that "bridges" several
relationships.

• Double Orange diamonds represent an edge collection (a role).

Example: Interference Relationship

• A yellow sphere represents a codelist table.

• A yellow domino with a number and a letter represents a codelist value.

• A brown sphere overlayed by a blue human outline represents a parent codelist table.

• A brown domino with a number and a letter overlayed by a blue human outline represents a
parent codelist value.

• Any icon overlayed by a tombstone represents a metadata object marked as deleted.

• Under View -> Units of measure, you can see the units for each Unit type. For each Unit type,
the blue unit represents the (SI) Database unit (DBU). Right click on any unit allow you to
convert a value in DBU.

• Under view -> Enumerations, you can know the different values of all the enumerations used by
the metadata.

• If you re-open often the same schema, you should choose "Auto open DB dialog" in Options.

• You can switch from displaying metadata object internal Names (System) to Usernames (User).
Property Category

Business Object Classification (BOC)

Piping Entities Data Model

Pipe Run Pipe Run

1 2
A PipeRun identifies one or more path features that share a
common pipe specification, flow direction, size, temperature,
pressure, etc. One or more runs make up a pipeline.
6 NPD
4 NPD

PipeRun and Pipeline Relationship

System Hierarchy Relation

The system hierarchy relationship is used to specify
that a run (IJSystemChild) has a parent system
(JDesignParent)

Pipeline is a high-level grouping of Pipe

Runs that are created in System and Spec
Task environment.

Example: SQL query to return pipe runs and pipeline names

Select x4.ItemName as PipeRunName,

x3.ItemName as Parent_System
from JRtePipeRun x1
join JNamedItem x4 on x4.oid = x1.oid
join XSystemHierarchy x2 on x2.oiddestination = x1.oid
join JNamedItem x3 on x3.oid = x2.oidorigin
 PipeRun and Spec Relationship

• PathRunUsesSpec relationship allows the run to retrieve the specification object located in the
catalog database

Relation
Collection

Relation

Relation
Collection

PipeRun and Features Relationship

Path Specification Relation

All path features are related to a run. This
relationship allows the path feature to
retrieve the specification and rules that it
needs to meet from the run.

Along Leg
Feature:
Turn RUNCHANGE
Feature
Straight Feature

Features define the geometry path of the run and

your design intent that occurs along the path. When End Feature
Along Leg
you route a pipe run, you place features. Feature:
End
COMPONENT
Feature

PipeRun and Parts Relationship

Owns Parts Relation

The OwnsParts relationship is used to specify that a
part occurrence is a child of a run.
Feature and Part Relationship

PathGeneratedParts Relation
This relationship identifies the part occurrences that are
generated from a given feature based on specifications.
For a feature representing a component, there may be
one or more generated parts. For a pipe, there may be
multiple features associated with a single generated
part.

Along Leg Feature

Parts:
- Mating Flanges
- Gate Valve
- Gaskets/Bolts/Nuts

Distribution Connection Relationship

GeneratesConnectionItems Relation
This relationship identifies
the connection items that are generated from a given
distribution connection.

Logical Distribution Connection Relationship

LogicalDistPorts Relation
This relationship identifies
the connection between an equipment nozzle
and the end feature of a path leg.