understanding the new content modeling framework

Content Modeling Framework


Objective

Overview of the Content Modeling Framework (CMF)

Review FMEA Example Configuration


Content Modelling Framework (CMF)Overview

Purpose

▫ Creates a data model of independent elements that are collectively treated as a single entity (CMF Document).

▫ Provides Viewers/Editors for creating and modifying Document content

Used to define the Documents and Views used in Quality Planning (QMS R1)

▫ CMF contains a single Viewer/Editor for the tabular-based content of a Quality Document


CMF Document ExampleProcess Quality Document


Operation

Tool

Product Char.

Process Char.

Eval. Meas. Tech.

Function

Failure Mode

Effect

Cause

Prevention

Detection

Action

Name

Number

Descr.

Descr.

Name

Descr.

Descr.

Descr.

Descr.

Descr.

Descr.

Descr.

Model View (Tabular)

PFMEA

“Operation”

<Element Type> <Property Type> <View>

<Column>

“Function”

“Failure Mode”

“Effect”

“Cause”

“…”

Style

Editor

Header

Width

Control Plan

<View>

Process Flow

<View>

“…”

“…”

Process Quality Document

<Content Type>

Content Modeling FrameworkOverview

Data Model

▫ Content Types, Element Types, Property Types

▫ Referencing / Bindings

▫ Structure Mapping

Views

▫ Tabular for now…

▫ Other View Types in the future

Export Settings


Content Type

Content Modeling FrameworkConcept of Operations


Model Definition

<ItemType>

Process Quality Doc

<ItemType>

ImplementationDefines Instance DataInstantiated As

Name: “Operation”

Element Type

Name: “Number”

Property Type

Type: Integer

<RelationshipType>

<RelationshipType>

Name: “Description”

Property Type

Type: String

parent

Linked ItemType:

Operation

…

Descriptionvalue: String

<RelationshipType>

Numbervalue: Integer

…value: Type

<RelationshipType>

element_ref_id

parent_ref_id

Process Quality Doc

<Item>

Operation<Relationship>

Numbervalue: 5

Descriptionvalue: “Mix”

<Relationship>

…

…

Content Modeling Framework Content Type

Purpose

▫ Defines a CMF Document

How it works

▫ Identifies an existing Target ItemType, onto which a number of Relationships will be attached for Document Elements and their Properties

▫ Assigns one or more Views for displaying/editing Document content


Content Modeling Framework Element Type

Purpose▫ Define the Objects of a CMF

Document

How it works▫ Similar in function to an ItemType

Implemented as Null Relation on Target ItemType

▫ Can be linked to a single ‘parent’ Document Element Forms Element hierarchy

parent_ref_id links to Element

▫ Can be bound to a single ‘Business Object’ (Bus. Obj.)


Content Modeling FrameworkProperty Type

Purpose▫ Defines properties for a Document

Element

How it works▫ Similar to a Property ItemType

Implemented as Null Relation on Target ItemType

element_ref_id links to Element

Types:

▫ Boolean, Date Time, Double, Integer, String, Text, File, Image, List

▫ Can be bound to a single Bus. Obj. Property

▫ Can specify a Method for automatic value calculation or style setting


Content Modeling FrameworkView – Column configuration

Purpose

▫ Configure Header, Cell Styles

▫ Set Cell Editor

How it works▫ Header and Cells styling by cmf_Style

▫ Editors Property default

List

Combo List


List Editor

Default Property Editor

Combo List

Content Modeling FrameworkItem (Business Object) References / Binding

Purpose▫ Allows CMF Documents to have an

indirect association with other PLM Items (Business Objects) Document Element becomes a ‘proxy’ to the Bus.

Obj.

How it works▫ ‘Soft Link’ between CMF Document

Item and Business Object Relationship will not show in ‘Where-Used’

CMF Doc. Item and Bus. Obj. can be removed w/o restriction

▫ Changes to Business Object Properties can be identified/flagged in Editor


Content Modeling FrameworkItem (Business Object) References / Binding

Referenced Type: ItemType to map to

Tracking: How to handle discrepancies in content

▫ Show, Ignore

Resolution: Mapped Item Instance to check

▫ As Saved, Current

New Element: Reference Options

▫ Pick, Create, Both

Reference Required: Can there be ‘unmapped’ Document Elements?


Content Modeling FrameworkExample: Item Reference / Binding


Number

Name

Model Items (Business Objects)

<Element Type>

<Property Type>

MPP Operation

String: Operation Name

Integer: Operation Number

Tool

Name

…

MPP Tool

String: Tool Name

Integer: Item Number

<ItemType>

Operation

Process Quality DocumentExample: Operation Reference


Content Modeling FrameworkStructure Mapping

Purpose:

▫ Provide a mechanism to map, and track, the structure of Document Elements in a CMF Document to a structure of referenced Business Objects Will be used in QP to map Quality Documents to Mfg Process Plans

How it works:

▫ Methods return a list of Item instances that are associated with a given bound Document Element Identifies order (when needed)


Structure MappingExample Quality Planning -> MPP

QP - Process Quality Document

▫ Mapped to Process Plan

▫ Requires PQB Binding application

QP – Operation

▫ Mapped to MPP Operation

▫ Order is tracked

QP – Tool

▫ Mapped MPP Tool

▫ Order is not tracked


Process Quality Document

Operation

Tool

Process Plan

MPP Operation

Op. Resource

MPP Tool

CMF (QP) MPP

Reference

Reference

Reference

Document Element

RelationshipType

ItemType

<Track Order>

Content Modeling FrameworkStructure Mapping

Candidate Document Element:

▫ A Document Element that refers to a Business Object in a bound structure that has not been accepted into a document

Flagged Document Element:

▫ A Document Element that does not represent its mapped structure either because: It is out of place based on ordering

It doesn’t refer to a referenced Business Object that exists in its parent’s hierarchy




Candidate Document Elements

Structure MappingExample Quality Planning -> MPP – Mismatched Content


Structure MappingExample Quality Planning -> MPP – Business Object Removed


understanding the new content modeling framework

Technology