3D PLM PPR Hub Open Gateway

General - Product Definiton

Knowledge Advisor : Build time product for creating rules, set of equations, reactions, loops, lists, etc.

KWA : Acronym for Knowledge Advisor P2 product. Used for explaining that this license if required for certain APIs.

Concepts Relying on Application Definition

Knowledge Type : Class of V5 objects that can be used by Knowledgeware products.

Example: Hole, Length, Point

This types are created by the applications based on an implementation defined in KnowledgeInterfaces [1].

Attribute : Property of a type. A type can hold some attributes. An attribute is defined by a name and a type.

Example: a Hole has an attribute named Diameter of type Length.

Example: a Pad has an attribute named Sketch of type Sketch.

This is also created by the applications based on an implementation defined in KnowledgeInterfaces [1].

Object: An object in V5 that can be used by Knowledgeware products

Example: Hole.1, Pad.1, etc…

These are applicative implementations that are seen through a protocol defined in KnowledgeInterfaces [1].

Knowledge Core V5 Objects

Knowledge dictionary : A singleton that provides access to all the V5 types, and functions, classified in packages.

Knowledge function : A function that can be used in the Knowledge language. It describes its arguments and it knows how to be evaluated.

Example: sin (x)

Example: Message (String, String, …)

Magnitude : A particular type of values for dimensions.

Example: Length, Viscosity, etc…

 

Unit:Associated to a magnitude.

Example: mm, m, km, etc…

Enumerated Type: A particular type of values for values that take a limited list of possible values.

Example: Boolean, Severity

Literal: A persistent value, owned by a feature. It can be of type Boolean, Integer, Real, String, or of any subtype of dimensions and enumerated types that exist in the dictionary.

Volatile value: A non persistent value. It can be of the same type as persistent values.

List feature:A feature that allows to reference a set of persistent objects or literals.

Volatile list : A non persistent object that allows to reference a set of objects or values.

Knowledge expression : An object (persistent or not) that is used to describe with a text an evaluation method and that can be used to perform the evaluation on parameters.

Example: expression named exp1 that computes a distance between two points ( P1: #In Point, P2:#In Point, L :#Out Length)

body = “let x1=0mm let x2=0mm let y1=0mm let y2=0mm let z1=0mm let z2=0mm

P1.coord (x1,y1,z1)  P2.coord (x2,y2,z2) L=sqrt((x1-x2)2+(y1-y2)2+(z1-z2)2)»

Knowledge relation : A persistent feature that describes a valuation relationship between persistent parameters. Any literal can be used as output of a relation. Some objects can be used as output of relation like a list feature or a geometric datum.

Example: a formula between two literals: y=2*x

Example: a formula between two objects: Pt=centerofgravity(Body)

Design Table: A kind of relation that valuates N literals from a literal called configuration that belongs to the design table. The evaluation method is based on a table (excel or .txt file).

Equivalent Dimension: A kind of relation that valuates N literals from a literal called driving that belongs to the equivalent dimension. Each literal in output is affected with the value of the driving literal.

 Formula: A kind of relation that valuates one persistent parameter from a set of parameters used as input, based on the Knowledge language.

Rule: A kind of relation that valuates several persistent parameters from a set of parameters used as input, based on the Knowledge language.

Check: A kind of relation that produces a Boolean diagnosis from several persistent parameters used as input, based on the Knowledge language.

Set of Equations: A kind of relation that valuates several persistent parameters from a set of parameters used as input, based on the Knowledge language, with an evaluation performed by a mathematical solver.

Optimization constraints: A kind of relation that expresses a constraint between several persistent parameters used as input, based on the Knowledge language, to be integrated in the definition of optimization.

Knowledge law: A mathematical relationship between formal values that can be used by V5 features.

Knowledge Core Additional Concepts

Parameter: A parameter is a variable with a name that can be passed as an argument of an expression for its evaluation. It can be read or written inside an expression (let’s talk of its content). Several Knowledge objects are parameters (Literal, Volatile value, List feature, Volatile List, Geometric datum, Reference to V5 objects).

Persistent parameter: Only some parameters are persistent in the data model (Literal, List feature, Geometric datum, Reference to V5 persistent objects). Only those parameters can be used as input or output of a relation because a relation creates a link to the objects that it manipulates. Note that only the first 3 ones (Literal, List feature and Geometric datum) can be used as outputs.

Reference to V5 object: It is possible to create a parameter from an object to be able to use it in an expression evaluation or in a relation if it is persistent. It is used only as an input in the expression or in the relation.

Geometric datum: This object does not belong to the Knowledge Interface framework. It is provided by GSMModel. But it is a persistent parameter.

Knowledge library: It is a place where V5 applications can declare their own Knowledge types and Knowledge functions. It is a C++ code that we know how to trigger.

Knowledge Package:It is a classification for Knowledge types and functions. They are created by applications.

Parameter valuator: An object that is responsible for valuating a parameter. For example a Knowledge relations. But there may exist other applicative objects that know how to valuate parameters. They are called parameter valuator

Where To Find Each Concept In The Code

References

History

Copyright © 2004, Dassault Systèmes. All rights reserved.