CT3158 PDF EBOM Product Structure Management for Creators Rev An

1
Module Overview
In this module, you learn some of the concepts and terms that surround products and
product structures. You learn the different part Types used at EMBRAER that are used to
describe the product structure. The purpose of this module is to provide you with a high-
level overview of products and product structures.
2
Objectives
After completing this module, you will be able to:

• Define configuration management
• What is Multi BOM?
• Data Management Objects
• Understand the eBOM and mBOM Capabilities
• Understand the Process of Product Structure Creation (VPM – PLM – SAP-Triggers)
• eBOM Creation Process
• eBOM Creation Process – Harness
• mBOM Capabilities
3
Objectives

• mBOM Creation Process - Harness
• Part Types - Manufactured Materials
• Part Types - Purchased Materials
• Understand EMBRAER Numbering
4
Configuration Management at EMBRAER
Windchill is implemented to support several areas of the product lifecycle and will be
used as an integrated part of the existing IT infrastructure.
To generate the product we have to go through several phases:

• Use CATIA to do the design.
• VPM is used to store and manage the CATIA data.
• The VPM communicates with Windchill. WdC is responsible to manage approvals,
releases, changes, effectivity, BOI (bill of information - product structure including the
describing documents), design review and collaboration.
• Windchill transfer the product structure to SAP. SAP manage the physical information
of the materials (stock, purchase order, fiscal classification, ECODE,…).
Windchill is implemented to support several areas of the product lifecycle and will be
used as an integrated part of the existing IT infrastructure.
In this course you will learn how create and manage eBOM at Windchill.
<Note> For Ipanema project, read the “CT3443 – Ipanema Deck of Slides” and the
“CT3937-QRC for Ipanema” materials to learn specific Ipanema process and functions.
5
What is Multi BOM?
Multi BOM means that each sector can develop its structure according to its needs. For example,
the structure can have the view for engineering BOM (eBOM), manufacturing BOM (mBOM) and
service BOM (sBOM). This is important for all facets of product development. The mBOM is a
derivation of eBOM that is of greatest interest to the manufacturing engineer. The mBOM forms
the basis for the creation of production plans, work instructions, and resource assignments. As
the eBOM changes, the mBOM must stay in lock-step, allowing the manufacturing engineer to
accommodate any impact on production processes, or resource allocation.
The sBOM is concerned with the serviceable components and maintenance procedures of
fielded equipment. Also, it must be inextricably linked to the eBOM. This ability to update across
BOMs is a significant source of strategic value for Embraer organization, as it ensures product
manufacturing plans and service information stays in alignment with the evolving product
design. It drives operational efficiency by ensuring all team members are acting on the most
current view of information.
eBOM features:
• Due to the flattening (horizontalization) of the product structure (only one level of CI-DS on
the eBOM), the re-identification necessity is diminished.
• Systemic vision of the designed product is capable to the engineering area.
mBOM features:
• Increased flexibility for mBOM to adapt to the best method / assembly sequence.
• Cascading manufacturing alterations, not affecting Engineering, for varying cadence.
sBOM features:
• Increased flexibility for sBOM to adapt to the maintenance structure.
• Automate associativity to product data of engineering and manufacturing to ensure up-to-
date serviceable parts information.
• Define applicability rules so the exact serviceable part, sBOM, is available for every product
configuration and operating condition.
6
Data Management Objects
One of the main purposes of Windchill is to store and manage information and content.
To do this, Windchill uses what it calls a Business Object. Because your data is often
complex, you may need to store a number of different types of information. Windchill
has several types of objects to handle these different types of information and enables
you to build relationships between them.
• Parts are used to build product structures. They do not store CAD data, but reference
other objects that do so. They can also reference each other in a hierarchy called a
product structure. Some of these objects are created manually in Windchill and
others are created automatically as a result of a data transaction from other systems
such as VPM.
• Document objects store and manage content. While document objects typically store
and manage documentation files, there is no limitation to the types of electronic files
a document object can store as content. For example, at Embraer all the Technical
Notes are created, linked and updated at VPM. They are only published from VPM to
Windchill. The Technical Notes may be Item Notes (NI), Pattern Notes (NP) or Free
Notes (NL). Later those items will be consumed by SAP.
<Note> The image above shows an example of how can we structure the objects.
7
Multi BOM Capabilities
A product structure is a hierarchical breakdown of the business and technical information that
the enterprise produces in developing a product. A good practice is to develop the product
structure with the following levels:
The “upper level” portion of the product structure is used to organize a product into its
major areas, sections, zones, etc. Generally the upper level structure is determined early on
in the program and may rarely change once it has been established.
The “configuration level” portion is made up of Configuration Items and Design Solutions
where:
• The Configuration Item (CI) collects the DS whose link indicate the DS
effectivity application for a particular aircraft configuration.
• The Configuration Control is responsible to create the CI.
A Configuration Item can have multiple Design Solutions. Effectivity is used
to select the appropriate Design Solution for a Configuration Item given an
Airplane serial number.
• A Design Solution (DS) represents a technical response to a
Configuration Item and describes an implementation that addresses
the functional requirements of an associated Configuration Item.
Lower Level: presents the design solutions to build the product respecting
the proper requirements.
• Parts build at VPM (T1, T2, T6) and RME Parts.
8
Overview of the process
The picture above shows the overview of all eBOM/mBOM process.

At this module you will see the eBOM process detailed.
<Note> The user may access an excel file with the process described by Embraer at
plm.emb portal.
9
eBOM Creation Process
All the Embraer work process inside the VPM for the Lower Level will not change.
Upper Level and Configuration Item are created inside the Windchill and transferred to VPM and SAP.
General Process:
1 – The Upper Level (UL) is created at Windchill with “In Work” state;
The user must change the state to “Ready”. At this point the object is transferred to VPM.
2- The Configuration Item (CI) is created at Windchill with “In Work” state;
The user must change the state to “Ready”. At this point the object is transferred first to SAP to generate ECODE.
The link between UL and CI is created at Windchill and transferred to VPM. All the Upper Level and CI updates are
made at the Windchill.
3- The CI is transferred from SAP to VPM
4 – The Design Solution (DS) is created at VPM;
The user must apply the trigger “Set Maturity” to change the state to “SAP Ready”. At this point the DS is transferred
to Windchill and SAP.
The Parts LL are created at VPM.
The user must apply the trigger “Set Maturity” to change the state to “SAP Ready”. At this point the Part LL is
transferred to Windchill.
The link between DS and CI is created at VPM and transferred to Windchill. All the DS and Parts LL updates are made
at the VPM, but the WdC manage this modifications.
The Effectivity codes are set between CI-DS link at Windchill and transferred automatically to VPM and SAP.
5 – All the RME Parts are created at SAP.

6 – The RME Parts are transferred to Windchill with no link at any document.
7 – The RME Parts are transferred to VPM. The user creates the link between the RME and DS or Parts at VPM.
This link is transferred to Windchill.
With this process the user have the single truth information inside WdC, all the manager of the release inside WdC
and all visualization inside WdC.
<Note> For Ipanema project, read the “CT3443 – Ipanema Deck of Slides” and the “CT3937-QRC for Ipanema”
materials to learn specific Ipanema process and functions.
10
eBOM Creation Process – Harness
The development of the Harness structure is the same as the other PNs.
All the Embraer work process inside the VPM for the Lower Level will not change.
Upper Level and Configuration Item are created inside the Windchill and transferred to VPM and SAP.
Part Lists containing E2 Harness design parts are managed in VPM in the product structure as common Part Type 1 or Type 2.
VPM requires all T1/T2 are MTS for E2- so Harness parts will be created as MTS for eBOM.
General Process:
1 – The Upper Level (UL) is created at Windchill with “In Work” state;
The user must change the state to “Ready”. At this point the object is transferred to VPM.
The Configuration Item (CI) is created at Windchill with “In Work” state;
The user must change the state to “Ready”. At this point the object is transferred first to SAP to get the ECODE and after is
transferred to VPM.
The link between UL and CI is created at Windchill and transferred to VPM. All the Upper Level and CI updates are made at the
Windchill.
2 – The Design Solution (DS) is created at VPM;
The user must apply the trigger “Set Maturity” to change the state to “SAP Ready”. At this point the DS is transferred to Windchill.
Designer creates a harness part number (-4XX or -5XX) at VPM;
The user must apply the trigger “Set Maturity” to change the state to “SAP Ready”. At this point the Part is transferred to Windchill
and SAP
Designer creates a harness part number (-2XX);
The user must apply the trigger “Set Maturity” to change the state to “SAP Ready”. At this point the Part is transferred to Windchill.
Designer link “-2XX” in “-4XX” in VPM;
Designer export part list to Windchill (eBOM).
Designer link “-4XX” in “DS” in VPM;
Designer export part list to Windchill (eBOM).
The link between DS and CI is created at VPM and transferred to Windchill. All the DS and Parts updates are made at the VPM, but
the WdC manage this modifications.
3 – The Effectivity codes are set between CI-DS at Windchill and Set atomically to SAP by “Transfer Ready”
With this process the user have the single truth information inside WdC, all the manage of the release inside WdC and all
visualization inside WdC.
<Note> For Ipanema project, read the “CT3443 – Ipanema Deck of Slides” and the “CT3937-QRC for Ipanema” materials to learn
specific Ipanema process and functions.
11
mBOM Creation Process
The mBOM is a specific BOM for the manufacturing area.
The mBOM facilitates the control of planning process, resources and enables the manufacturing area to meet their targeted production costs.
The process consists at creating a new structure consuming the eBOM structure, reorganizing the Parts and the DS. To define the mBOM you may
create new Upper Level, new CI, new Effectivity and new Manufacture Parts too.
The reconciliation process must assure the eBOM and mBOM coherence (all eBOM requirements are consumed by mBOM).
General Process for mBOM creation:
1 - mBOM process may start once eBOM is created at Windchill. The eBOM do not necessarily have to be released;
2 - Create mBOM Upper Level & CI-DS Structure;
Create Upper Levels at “ERJ 190 Type” container, sub-folder Upper Levels.
Create CI Type 8 is created at “ ERJ 190 Type” sub-folder Configuration Item.
Create DS at “190G - mBOM Final Assy ” or “190G - mBOM Structural -Assembly” containers;
Link UL, CI and DS to build the structure.
3 - Send to SAP (State Ready);
Promote the mBOM structure’s state to “Ready” to send the structure to SAP
4 - Apply Basic Effectivity;
Create a Change Directive to start the Effectivity process and link it to a CI;
5 - Export Part List;
Promote the structure state to “ Transfer Ready” to send UL structure to SAP
6 – Consuming eBOM Lower Level to mBOM;
MPSE (Manufacturing Product Structure Explorer) is used to consume an eBOM CI to a mBOM DS.
7 - Adding Manufacturing Notes;
8 - Reconciliation and OOTB Reports to check if all parts were consumed;
Use Compare to Part Structure functionality
9 - Updating SAP Part List;
Promote the structure’s state to “Transfer Ready” to update mBOM structure in SAP
10 - Updating Lower Level from VPM (new iteration is created);
If Lower Level parts attributes are edited in VPM, mBOM must be updated
MPMLink shows that the downstream parts are outdated
11 - Updating VPM from mBOM. Edit (Check-Out) the mBOM Lower Level parts’ attributes in Windchill (new iteration is created).
The eBOM parts will be updated in VPM after check-in.
<Note> The user can add Manufacturing Notes in eBOM structure ( at View Manufacturing at eBOM structure)
12
mBOM Creation Process – Harness
The development of the Harness structure is the same as the other PNs.
The mBOM process may start once eBOM is created at Windchill. The eBOM do not necessarily have to be released;
General Process for mBOM creation:
1- Create mBOM Upper Level & CI-DS Structure;
Create Upper Levels at “ERJ 190 Type” container, sub-folder Upper Levels.
Create CI Type 8 is created at “ ERJ 190 Type” sub-folder Configuration Item.
Create DS at “190G - mBOM Final Assy ” or “190G - mBOM Structural -Assembly” containers;
Link UL, CI and DS to build the structure.
2- Send to SAP (State Ready);
Promote the mBOM structure’s state to “Ready” to send the structure to SAP
The SAP create the eCODE and send to Widchill.
At this moment the PN is not structured at SAP.
The PN will be structured at EES.
3- Apply Basic Effectivity;
Create a Change Directive to start the Effectivity process and link it to a CI;
4- Export Part List;
Promote the structure state to “Transfer Ready” to send UL structure to SAP;
5- Consuming eBOM CI to mBOM;
6- Adding Manufacturing Notes; (The user can add manufacturing notes on eBOM strucutre)
7- Reconciliation and OOTB Reports to check if all parts were consumed;
Use Compare to Part Structure functionality;
8- Updating SAP Part List;
Promote the structure’s state to “Transfer Ready” to update mBOM structure in SAP;
9- Updating Lower Level from VPM (new iteration is created);
If Lower Level parts attributes are edited in VPM, mBOM must be updated;
MPMLink shows that the downstream parts are outdated;
10- Updating VPM from mBOM. Edit (Check-Out) the mBOM Lower Level parts’ attributes in Windchill (new iteration is created);
The eBOM parts will be updated in VPM after check-in;
<Note> There is no integration between EES and Windchill for transfer data. The Wiring PNs are created at VPM, transferred to eBOM and Consumed
to mBOM.
After consuming the PNs, and with the EO approved, the Harness structure is complemented by EES direct at SAP.
Windchill do not receive back the Harness information from EES or SAP.
13
Part Types - Manufactured Materials
Manufactured materials are identified as part types 1, 2, 6, 7 and 8. Each type

corresponds to the nature of the component and for types 1, 2, 6 and 7 for eBOM
are created in VPM. Types 7 and 8 are created in Windchill for mBOM.
Types of manufactured materials:
• Type 1 - Assembly / Subassembly: Material resulting from two or more pieces

assembled by a manufacturing process.
• Type 2 - Single / Primary Parts: Material produced from the machining process,
forming, molding, etc.. Without other components than the raw material.
• Type 6 - Partner Kit: It is a collector of not assembled parts from partners.
• Type 7 - Configuration Item / Installation Design Solution: Functional element of the

product.
• Type 8 - Upper level: Top collector.
14
Part Types – Purchased Materials
Purchased materials used in a product structure are defined using the part types
3, 4, 5 and 9. Each type corresponds to the nature of the component and is
created manually at SAP an transferred to Windchill and VPM.
Types of Purchased Materials:
• Type 3 - Raw materials: Materials supplied by external manufacturers that require

some processing before end use.
• Type 4 – Mechanical Hardware: Mechanical Hardware are finished materials, which

do not require processing. It is provided by external manufacturers and are used in
the mechanical systems.
• Type 5 – Equipment: Materials supplied by external manufacturers for specific

functions and the composition of aeronautical systems.
• Type 9 - Electric Hardware : Materials supplied by external manufacturers with

different functions for interconnection and / or protecting electrical circuits /
electronics aeronautical systems.
15
EMBRAER Numbering - UL
A Part needs a unique identifier in Windchill and EMBRAER part numbering process is
used to create the identity. The number is also used to identify corresponding data in
other systems and is a key component for the automated data transitions.
At eBOM UL don´t have ECODE for this reason the eBOM UL is not required to use the
EMBRAER rule. The Number and Description are alphanumeric.
Rules for Description and Numbering are described in EMBRAER DSM (Drafting Standard
Manual) chapter 12.
16
EMBRAER Numbering - CI
At eBOM CI is necessary has the ECODE, because it can be consumed.
The UL and CI will be defined by the Configuration Engineering according to the rule
established by the program.
CI naming rule:
CI: acronym for Configuration Item (CI).
MODEL: model of E2 Program (175, 190, 195).
E: acronym for eBOM PN.
RADICAL: sequential number. Defined from DS. In optional condition, using the radical of the first
DS.
-XX: dash number. CI uses 00.
Example:CI190E12345-00
17
EMBRAER Numbering – DS and Lower Level (1/4)
The DS and Parts will use the EMBRAER rule.
For the Harness DS mBOM and PNs eBOM and mBOM, the Embraer will use the Embraer
rule.
Naming rule for DS and Lower Level (Prefix 196):

196EYYYYY: Prefix 196E used in eBOM E2 Model aircraft drawings
See the drawing number ranges (Prefix 196) on table above.
COMMENTS
(1) The range 01641 to 01730 has been supplied for C&D.
(2) Unless otherwise specified, drawings issued for all aircraft models shall have the
prefix 190.
(3) If the prefix 190 numbering has been exhausted, the prefixes 191 to 199 shall be
used.
(4) Embraer’s designer shall obtain the drawing numbers with the Program Configuration
Engineering.
18

197EYYYYY: Prefix 197E used in eBOM E2 Model aircraft drawings.
COMMENTS
prefix 190.
used.
Engineering.
19

197EYYYYY: Prefix 197E used in eBOM E2 Model aircraft drawings.
COMMENTS
prefix 190.
used.
Engineering.
20

198EYYYY: Prefix 198E used in eBOM E2 Model aircraft drawings.
COMMENTS
prefix 190.
used.
Engineering.
21
EMBRAER Numbering – Reuse (1/2)
Naming rule for Reuse 190:

190YYYYY: Prefix used in 1st generation aircraft drawings.
See the drawing number ranges on table above.
COMMENTS
prefix 190.
used.
Engineering.
22
EMBRAER Numbering – Reuse (2/2)
Naming rule for Reuse 191:

191YYYYY: Prefix used in 1st generation aircraft drawings.
See the drawing number ranges on table above.
COMMENTS
prefix 190.
used.
Engineering.
23
© 2014 PTC Module 1
Module 1
Product Structure Fundamentals

Exercise 1: View / Explore eBOM Structures
Objectives
After successfully completing this exercise, you will be able to:
• View eBOM structures.
• Explore eBOM structures.
Scenario
In this exercise, you take the role of a Configuration Control and visualize the structure of eBOM.
Initial Conditions
To successfully complete this exercise, you must establish the following initial conditions:
• Log on to Windchill (https://plmtrn.embraer.com.br/Windchill).
• If you are not connected to the Embraer network, enter your Embraer username and password.
• Log on to Windchill using “confcontrol01” user and password “emb”.
• Start on the Home page.
* The training environment has no interface with the VPM/SAP, so there is no interaction with
the VPM/SAP. During this training the user will be simulating the environment related to the
eBOM process.
Task 1: Access the folder at ERJ 190 Type container
1. Open the ERJ 190 TYPE, Embraer product container. Select the symbol.
Module 1 © 2011 PTC

2. Select the Folders option. This option displays the entire folder structure and the folder contents.
3. At the root of ERJ 190 TYPE, Embraer containers are stored all eBOM Upper Levels and
Configuration Items. Also in this container there are 5 main folders:
• Changes – Store change objects like Change Directives and Engineering Orders;
• Upper Levels – Store Upper Levels for eBOM and mBOM;
• Notes – Store Technical Notes.
• Configuration Item: Store Configuration Item for eBOM and mBOM
• Documents: Store Documents for eBOM and mBOM

Task 2: Access the UL View Information page
1. At the Folder Contents > Upper Levels > Engineering folder select the View information icon
of TRAINING DATA SET UL.
2. Visualize the information inside the Details tab. This tab shows the general information, attributes,
transfer info and system info.
3. Select Structure Tab to see the UL structure.

4. Expand the Structure selecting the symbol.

Task 3: Access the CI Tabs
1. Select the 197-96066-800, CI with the right button of the mouse and select the View Information .
With this you can access the View Information of the CI from the UL View Information.
2. Select the Changes tab. You can visualize the Effectivity at Change Directive table.
3. Select Related Objects tab. You can see the related DS at Design Solution table.

Task 4: Access the DS Related Objects tab.
1. Select the 197-96066-401 DS View Information . With this you can access the View Information of
the DS from the CI View Information.
2. Select Related Object tab. You can see the related CI at Configuration Items table and the Technical
Notes at Described By documents table.

Task 5: Compare the DS Information.
1. Select the History tab and observe the Version History table. Compare the oldest version to the
latest version.
Select the versions and select Compare Information.
2. At the Compare Options dialog box select what do you want to compare. Select Attributes, Part
Usage and Related Documents. Select OK.

3. At the Comparison Report dialog box you can visualize the difference between each version. Select
Close.

Task 6: Verify where this PN is used, the Traceability and AML/AVL information.
1. Select the Where Used tab to verify which parts are using this DS.
2. Select the Traceability tab. The related upstream and downstream object tables in the Traceability tab
show how parts are related to the requirements they address and specifications that drive their
development.
3. Select the AML/AVL tab. This tab appears to allow you to add manufacturer and vendor parts to or
remove them from the Approved Manufacturer List (AML) and Approved Vendor List (AVL),
respectively. Today, this PN do not have this information.

Task 7: Verify the Product Analytics, Relationship Explorer and Integration Status tab.
1. Select the Product Analytics tab is used to ensure that cost data is synchronized correctly. Must have
the integration with the Product Analytics. It will be used in the future.
2. Select the Integration Status tab is used to verify the integration between Windchill and the other
software. You can see if the transfer failed or if was successes.
This completes the exercise.

Module Overview
In this module, you learn how to compare structures, manage filters and create reports.
1
Objectives
• eBOM Configuration: Latest

• Effectivity Management
• Setting the Serial Number Filter (Effectivity)
• Setting the Attribute Filter
• Setting the Spatial Filter
• Saving and Managing Filters
• Views
• Show/Hide Related Information (BOI)
• Managing Windchill Table Views
• Finding Components in the Product Structure
2
Objectives
• Product Structure Browser

• Product Structure Browser — Visualization Tab
• Open in Creo View
• Edit View’s Setting
• Comparing Product Structures
• Analyzing Structure Comparison
• Comparing Part Information
• Product Structure Reports
3
eBOM Configuration: Latest
The user may apply filters at the structure selecting the “Information Page”, selecting the
“Structure” tab and selecting “Edit Filter” from the “Filter” group in the command ribbon.
Windchill shows the structure based on the filter, the default filter points to Latest Working
version. A configuration specification is used when expanding a product structure to determine
which version of a child part to display.
The Latest configuration specification is selected by default when expanding product structures.
When you select Latest the configuration specification displays the most recently versions of the
parts that meet the selected criteria.
The Default filter is composed of:
• Choose a Type: Latest.
• View: Design.
• And “Include Work In Progress” selected.
The user may change the filter specifications changing the available options:
• View: define if you want to view the Design, Manufacture or Service type.
• BOM Type: define the BOM type Production, Testing or Costing. This option is not applicable
for Embraer.
• Alternate BOM: define the BOM alternate version. This option is not applicable for Embraer.
• Life Cycle State: define what state do you want to filter. In Work, Ready, Released….
• Include Work in Progress: this option is related to the files that are checked out with you. If
selected, all the child of the checked out file will be part of the filter. If not selected, all the
child of the checked out file will be hidden until the user apply the check in to this file.
• Apply to top level object: If selected, the configured filter is applied to the top-level part
(parent). If not selected, the iteration of the top-level part is preserved.
• Apply latest for unresolved dependents:to apply a Latest configuration specification filter
(with no specified view and any life cycle state) to part structure nodes for which no version
was selected.
• Life Cycle State: used to apply a filter according to selected state, for example “ In Work”,
“Released”….
4
eBOM Configuration: Latest Released
Windchill shows the structure based on the filter. The default filter points to Latest
Working version. This option shows on the structure the latest version even if not
released.
In order to filter for a Latest Released version, the filter shall be edit to: Latest, Design,
Released option.
The User can view the latest version of the Released status, if it has any released version.
The Default filter is composed of:

• Choose a Type: Latest.
• View: Design.
• Life Cycle state: Released.
At this point the system will bring the latest version released of the Part Number.
<Note> If the part number is in another state and has never been released, it does not
show.
<Note> If the part number is in another version, but is not released, the system will
show the last.
5
eBOM Configuration: Latest View
The Edit Filter "View" allows the User to choose which type of structure should be
filtered, Design or Manufacturing.
The user can configure according to the need to filter the structure.
View: Design or Manufacturing

Include Working Progress : Checked
This way the Windchill show the structure of the Design or Manufacturing and others
information about part number details.
6
Effectivity Management
Effectivity is the planned aircraft serial number at which a part versions are replaced
with new part versions in production. You can make changes to planned effectivity
settings by using a Change Directive. When the change directive has been completed,
the planned effectivity is copied over the link as actual effectivity on the given object.
For EMBRAER E2 Program the valid range for basic effectivity is from 20001 to 99999.
For Model effectivity the range (MD__ 20001/99800) must follow the Aircraft Serial
Number sequence.
For Customer effectivity the range (__ CL 00001/99999) must follow the Customer Serial
Number sequence.
7
Setting the Serial Number Filter (Effectivity)
When you select a serial number filter, only part versions with the serial number you
specify, are expanded in the part structure.
To set a serial number configuration specification, use the following procedure:
• Access the part information page and select the Structure tab. From the Filter group,
select Edit Filter.
• In Edit Filter dialog box select the Serial Number tab.
• Type the serial number or a serial number range.
• Click OK to apply the filter.
8
Setting the Attribute Filter
When you set an attribute filter, only part versions meeting the attribute criteria are
expanded in the part structure.
To set an attribute filter, use the following procedure:
select Edit Filter.
• Select the Attribute Filter tab.
• In the Attribute Query Expression window, select the desired attribute and its
corresponding value. You have the following three options when setting the attribute
values:
– Equal To
– Not Equal To
– Not Set
• You can add multiple attributes by clicking the Add button in the Edit Filter window, if
necessary. Click OK to set the filter.
9
Setting the Spatial Filter
When you set a spatial filter, only parts contained within the spatial filter coordinates are
expanded in the part structure.
There are two ways you can set a spatial filter.
select Edit Filter and then select the Spatial Filter tab.
• Alternatively, you can click the Spatial Filter icon within the Visualization tab toolbar.
There are three types of spatial filters:
• Sphere Spatial Filter – Only those parts contained within the sphere are displayed. You
can manually set the sphere size and position from the Sphere Spatial Filter
Coordinates window. Alternatively, drag the sphere center and the coordinates
dynamically and drop them within the Visualization tab to resize the sphere.
• Box Spatial Filter – Only those parts contained within a box are displayed. You can
manually set the box size and position in the Box Spatial Filter Coordinates window.
Alternatively, drag box coordinates dynamically within the Visualization tab to resize
the box.
• Proximity Spatial Filter – Only those parts within the proximity of a specific part are
displayed. You can select a part in the visualization tab and then perform the Set
Proximity Spatial Filter action to specify the proximity.
10
Saving and Managing Filters
To save the filter created in the “Edit Filter” window and used to display objects in the
structure, from the “Filter” group, click the “Saved Filters” drop-down menu and then
select “Save”. The “Save” window appears, enabling you to type a name to remember
the filter. This filter then appears when you select the “Saved Filters” drop-down menu
from the “Filter” group. If you select the “Share” check box in the “Save” window, this
filter also appears when other users select the “Saved Filters” drop-down menu.
In the “Filter” group, click the “Saved Filters” drop-down menu and then select “Manage
Filters”. The “Manage Filters” window opens. This window displays all filters you have
saved. You can then select which filters you want to display when you select the “Saved
Filters” drop-down menu and if you want to share any of your filters with other users.
11
Views
The viewing actions are used to change the display of information in the part structure
pane.
The ”Views” icon provides the ability to create table views that change the information
displayed in the structure pane. Select a previously defined view from the drop-down list
or create a new view using ”Manage Structure Views”.
At Embraer, the user may select the “Embraer Structure View” option to visualize the
structure with the configuration defined by Embraer.
To visualize the Notes and the reference component of the notes the user must apply
the “Show/Hide” function and select “Documents”, then visualizing the documents at
the structure the user must select “View > Notes Views”.
At the images above, you may see the difference between the “Notes View”, “Embraer
Structure View” and the “Default” options.
12
Show/Hide Related Information (BOI)
By default, only part objects are displayed in the product structure under the “Structure”
tab. However, you can use the “Show/Hide” icon within the “Viewing” group of the
command ribbon to display one or more related object types. The related objects may
include Documents (Technical Notes), CAD documents (won’t be used), Replacement
Parts (won’t be used), Distribution Targets (won’t be used) and AML/AVL (Approved
Manufacturer List/ Approved Vendor List). This enables you to display the Bill Of
Information.
13
Managing Windchill Table Views (1/2)
Windchill tables display objects in rows with information about each object listed in
columns. The number, content, and order of the columns and rows can help or hinder
your ability to work with large data sets. For each data table, Windchill provides a default
view and your administrator may have defined custom views for your organization.
Some of those views are available in the View drop-down menu.
If you select the “Manage Structure Views” option from the “View” drop-down menu,
the “Customize View List” window appears. This window includes the “Views” table,
which describes each of the available views.
You can use the actions available on the “Views” table to delete table views you have
created, show table views, hide table views, set an active table view, edit table views,
and create new table views.
At “Creating New View” tables you can add columns as “Referenced Component”, for
example.
14
Managing Windchill Table Views (2/2)
Selecting the “New View” option, the “New View” dialog box opens.
First, define the name of this New View.
At “Set Column Display”, at the left side choose the desired column to visualize and
select the arrow to add the columns at the right side.
After Finishing the creation of this New View, the option will be available at “View”
table.
15
Finding Components in the Product Structure
The Find in Structure field above the structure pane can be used to locate parts in a
complex product structure.
Use the following steps to find an object within a structure:
• Type a text string in the “Find in Structure” text entry field to search for parts within
the structure. The string may be a portion of any attribute value in the object identity.
For example, type in a portion of the object name or number.
• Find matches within the structure in one of the following ways:
– Click the “Find” icon to highlight all matching objects.
– Press “ENTER” to highlight all matching objects. Press “ENTER” repeatedly to select
each match down the structure.
– Click the “Previous Match” or “Next Match” arrows to search up or down the structure
tree. The structure is expanded to reveal each matching object.
16
Product Structure Browser - Attributes and Link Information
After selecting the PN at structure the user may see the attributes and the link
information of this PN at the tab at right.
Attributes: Displays important attribute information about the part.
Classification: Shows the classification attributes associated to the part.
Uses: Displays the parts that are used by the part selected in the structure pane. The
user may see the Line Number, Zone, Quantity, Effectivity…
Occurrences: Displays information about each usage of a part within an assembly. The
user may see the Quantity and Location.
17
Product Structure Browser — Visualization Tab
The “Visualization” tab contains graphic images of the parts in the product structure that
have geometry modeled in a CAD application and are published to the database using
the Windchill visualization service. The images are generated automatically and
displayed on the part information page when a CAD document is checked in from a
workspace. The “Creo Elements/View” plug-in application is used to manipulate the 3-D
images within the “Visualization” tab.
The images in the “Visualization” tab serve two purposes:

• They provide visual verification of parts selected in the part structure.
• They provide the ability to filter the part structure using geometric selection.
The following two specific icons have been added to the “Visualization” toolbar for
visualizing part structures.
• Toggle the automatic selection preferences – Used to specify the selection behavior
between the part structure pane and visualization image. Selecting a part in the part
structure pane causes the corresponding part image to be highlighted in the
Visualization tab and vice-versa.
• Spatial Filter – Used to define a part structure filter based on geometric volumes. It
contains a menu with the following choices:
– Set Box Spatial Filter
– Set Sphere Spatial Filter
– Set Proximity Spatial Filter
– Update Spatial Filter
<Note> To approve the PN, it visualization must be made using CATIA.
18
Open in Creo View (1/2)
<Note> For more information of how to visualize the Embraer PNs, read the “CT3936-
QRC Creo View Settings for Embraer” too. At this material you have information about
Sheet Metal, Composite, 2D Drawing, 3D models, etc.
The user may use the Creo View to help during the eBOM consume or approval process.
The Creo View provide functions to finding and selecting components, managing
multiple views, orienting models and drawings, changing model rendering, exploding
model components, sectioning models, creating markups, measuring distances and
displaying dimensions.
You can open the PN at Creo View by selecting the PN with the right button of the
mouse, selecting “Open in > Open in Creo View”.
19
Open in Creo View (2/2)
The user may open an PN and after open the next assembly of this PN at the current
session in Creo View.
At “Where Used” tab you may see the parent PN of that PN.
Select the version, for example /.4. The “View Information” of this PN will open.
Select the “Structure” tab and select the PN with the right button of the mouse.
Select “Open In > Open in Creo View”.
A dialog box opens with a question: “Add to the current Creo View session?”
Select “Add to Current Session” to open this PN at the same session of the it child.
20
Edit View’s Setting
If the CATIA 3D model have points and vectors representation, at Windchill, only the
vectors will be show.
If the user wants to visualize the point he must open the model at Creo View and edit
the view settings.
The user may visualize the points by clicking in the thumbnail in the “Details” tab and
opening the model in Creo View.
By clicking in the arrow in the lower corner in RH side, the user may select “View
Settings” to edit the view settings.
In the “Filters” field, activate the “Datum Points” option.
The points are turned on in the visualization area.
21
Comparing Product Structures
The Compare to Part Structure action allows users to view and compare two similar assembly part structures determine how they differ.
The user can compare the structure, for example:
• An eBOM structure version with the same eBOM structure but with another version or mBOM structure version with the same mBOM structure but with another version.
• An eBOM structure with other eBOM structure or mBOM structure with other mBOM structure too.
If the user try to compare an eBOM structure with mBOM structure, only the parent will be compared and only the attributes and notes will be compared. The equivalence will
not be compared.
The Compare to Part Structure action can be launched from multiple locations within Windchill. The locations include:
• The Ribbon – The command ribbon on the Structure tab of any part information page.
• Actions Menu – Select the Actions > Compare > Compare to Part Structure from any part information page.
Launching a part structure compare from any of the launch points causes the “Part Structure” setup window to be displayed. The “Compare to Part Structure” setup window
displays the part structures to be compared under the Left Side and Right Side headings. The Number, Name, and Version attributes identify each part. By default, the part from
which the structure compare action is launched is shown in both the left and right sides.
The “Compare to Part Structure” setup window assumes that the structure on the left or right side is replaced or filtered prior to clicking OK. Making no changes results in a
comparison between the exact same part structures and produces no differences. The best practice is to filter or replace the part structure on the right side.
In the ”Compare to Part Structure” window, under the Parts tab, modify the part versions displayed in the Left Side and Right Side if necessary. Make changes using the following
fields:
• Enter Number/Name: Enter the name or number of a part to take the place of the displayed part in the comparison. Entering a partial name or number will display
matching choices beneath the entry field. Click the “Advanced Search” icon to search for parts by type, name, and number.
• Version: Select any part version using the drop-down list. The version satisfying the current filter criteria is marked with an asterisk (*). Reduce the length of the list by
highlighting the entry in the Version field and entering part of the desired version identifier. The list is restricted to only those versions matching what has been entered.
Selecting a different version of the top part may display different first level child parts. The versions of the first level child parts, and all parts in levels beneath the first level, is
determined by the current filter criteria.
• Structure Filter: The current filter is shown just below the ”Structure Filter” field. Use the icons to the right of this field to view and change the structure filter:
• Click to view the filters currently in use. Hover your mouse over this icon to see a summary of the filter settings.
• Click the “Edit Filter” icon to open the “Edit Filter” and modify the current filters. You can filter by Configuration Specification, Spatial Filter, Attribute Filter or
Serial Number Filter (effectivity).
• Click the “Saved Filters” icon to specify a saved filter, save the existing filter, or manage saved filters.
If desired, click the Preferences tab to specify part comparison options. The following table describes the available settings:
• Select attributes to compare:
Use the drop-down object type menu and checkboxes to select attributes to compare for each object type. Follow this procedure:
• Choose an object type from the drop-down menu.
• Select the attributes to compare.
• Repeat these two steps for each object type.
The first time the Select attributes to compare is used, all attributes are selected for all object types by default. Once modified, the system retains your object type and attribute
selections for each subsequent use of the part structure compare function until you change them.
• Include related information in compare:
• Select ”Documents” to compare documents associated to the parts within the two part structures.
• Select ”Replacement Parts” to compare alternate and substitute parts associated to parts in the two structures (won’t be used).
• Select ”CAD Documents” to compare CAD documents associated with the parts within the two part structures (won’t be used).
• Select ”AML/AVL” to compare manufacturer and vendor parts associated to parts in the two structures.
<Note> The preferences selected in this step are saved as your default choices for all future part comparisons within and across Windchill sessions.
<Note> At Windchill, the Embraer PN do not have link with CAD documents. At Preferences tab, the user may select the Documents options.
<Note> The Compare Part information and Compare Product Structures may be used to generate the new DRS at Windchill.
22
Analyzing Structure Comparison
The following actions are provided in the left and right side toolbars in the “Compare to Part
Structure” window.
• Reset: Displays the Compare to Part Structure setup window to modify the compared
structures and to restart the part structure comparison.
• Previous Difference: Locates the previous part structure difference in the left or right part
structure.
• Next Difference: Locates the next part structure difference in the left or right part structure.
• Current Filter: Displays the Current Filter window.
• Edit Filter: Is used to modify part structure filters.
• Saved Filters: Is used to manage saved structure filters.
The following differences are detected when comparing part structures:

• No Equivalent Object: This icon means that no equivalent part exists in the opposite (left or
right) structure. A blank row is displayed in the structure that does not have the equivalent
part.
• Child Difference: This icon appears for an assembly where a difference in the child parts is
detected. The difference may be multiple levels beneath the assembly part.
• View attribute differences: The attributes stored on a part or related object that exists in both
structures have changed.
• Replacement: This icon indicates that the part has been replaced by an alternate or substitute
part.
• View Usage Attribute Differences: This icon means that the attributes stored on the usage link
between the part and parent assembly have changed.
The “Compare to Part Structure” window also displays the Attributes, Usage Attributes, and
Visualization information tabs below the left and right side structure.
23
Comparing Part Information
The “Compare Information” enables you to compare two or more objects or versions (also called
revisions) of an object.
The user can compare an eBOM with eBOM or mBOM with mBOM.
Use the following procedure to compare multiple parts or multiple iterations of the same part:
• On the information page of an object, select “Actions”, “Compare”, and “Compare
Information”. The “Find Object” window opens.
• Search for the objects that you want to compare, select them, and then click OK.
• The “Comparison Options” window appears. Select the check boxes to indicate what you want
to display in the comparison report.
Select All: compare using all options;
Attributes: compare the attributes;
Part Usages: compare the children of the structure;
Related CAD Documents: compare the CAD documents;
Related Documents: compare related documents as notes;
Variances: is not used by Embraer.
• Finally, click “OK” to generate the report.
If the user compare the Part Usages and the comparison have different results, the symbol with
a black dot will appear.
This symbol is the representation of the Part Master, this is the way that Windchill do the
representation inside this comparison dialog box.
<Note> The Compare Part information and Compare Product Structures may be used to
generate the new DRS at Windchill.
24
Module 2
eBOM Configurations

Exercise 1: Creating Filters
Objectives
• Create and manage filters.
Scenario
In this exercise, you take the role of a Configuration Control, and create, apply and manage filters
Initial Conditions
• Navigate to the ERJ 190 TYPE, Embraer container and start on Structure tab of TRAINING DATA
SET UL.
eBOM process.

Task 1: Create Serial Number filter.
1. Select Edit Filter.
2. Select Serial Number Filter tab and write the serial number 60000-99999.
3. Select OK.
4. At the structure you can see the filter of all DS that have the serial number 60000-99999.

5. To save the filter select Saved Filters > Save and write a name (Effectivity 60000-99999) at the
dialog box.

Task 2: Create Attribute filter.
1. Select Edit Filter.
2. Clear the text inside the Serial Number Filter tab. Select Attribute Filter tab. Select Add.
3. Select Type as Part and Criteria as Number. Write the number 197* and select OK.
4. At Edit Filter dialog box select Ok.

5. At the structure the filter shows all the parts with the number 197*.
6. Select Saved Filters > Save and write Attribute 197 at the dialog box. Select OK.

Task 3: Manage the filter.
1. Select Saved Filters > Effectivity 60000-99999. The Effectivity filter will be applied.
2. Select Saved Filters > Default to back to initial filter.
3. To visualize the Notes and the reference component of the notes, select the 197-96002-001 PN, select
Show/Hide function and select Documents, then visualizing the documents at the structure, select
View > Notes Views.
vc

4. Select Saved Filters > Default to back to initial filter.
vc
Exercise 2: Compare eBOMs and part information

Objectives

• Compare parts information.
• Generate reports.
Scenario
In this exercise, you take the role of a Configuration Control to compare structures end generate
reports.
Initial Conditions
• Navigate to the ERJ 190 TYPE, Embraer container and start on the Folders > Upper Levels >
Engineering folder page.
eBOM process.

Task 1: Access Structure tab and search parts.
1. Select the View information icon of Training Data Set UL.
2. Select the Structure tab and select the Visualization tab to visualize the model.

3. Search for the *001* at Find in Structure. Select Find . All the Parts with 001 will be highlighted.
4. Select Next Match to see the next part with *001* text.

Task 2: Compare the Parts.
1. Select the 197-96003-001 Part and select the Compare > Compare To Part Structure.
2. Select at the Right Side the version /.5 to compare with the latest version /.7 and select OK.

3. Verify the result. All the text in blue means different information between the versions.
4. Close the window.

Task 3: Generate Reports.
1. Select the TRAINING DATA SET UL and select Reports > Multi-Level BOM. This option shows an
indented list of single-level BOMs for all levels of a product structure. If a part is used more than once
at a particular level, it appears more than once.
2. Verify the report. You can see all the structure with the used versions.

3. Back to Structure tab, select the TRAINING DATA SET UL and select Reports > Multi-Level
Component List. This option shows a consolidated list of components and their quantities within an
entire product structure.
4. Verify the report. You can see all the Components used at this structure.

Module Overview
In this module, you will learn how to create Windchill parts, transfer from Windchill to
VPM and link them. You will also learn the Part attribute set for Windchill Parts that is
used at EMBRAER.
1
Objectives
• Create Upper Level

• Upper Level Attributes
• Create Configuration Item
• CI Attributes
• Edit Attributes UL and CI
• Delete UL and CI
• Transfer the UL and CI from Windchill to VPM
• Edit Attributes – Administrator
2
Create Upper Level
At Windchill the “Configuration Control” may create structures with one or more Upper
Level and may create the CI.
At Embraer the structure starts with an Upper Level part. The Upper Level is used to
organize a product into its major areas. The part type used at EMBRAER as Upper Levels
are Type 8.
All the Upper Levels are created at “ERJ 190 Type” container, subfolder Upper Levels.
To start a new structure, first create a “New Part” with “eBOM Upper Level” type.
For Experimental EO, the administrator will create the UL for test inside the container –
190 G Master Data, Embraer.
The user may be Embraer Configuration Control.
<Note> FTI Segregation of PN's in Upper Level or in Containers, are under discussion. It
will be in a future Roadmap.
3
Upper Level Attributes (1/2)
Depending of the type chosen, the user must fill different attributes.
There are 3 different ways to propagate attribute values:
• Manually Entered: Done by the user upon Part creation or when updating a part.
• Automatically populated: Done by the system and relies on data transactions from
other systems such as SAP and VPM.
• Automatically calculated: Done by the system and uses input values from other fields
to determine the attribute value.
Attributes:
Number: PN number;
English Description: English PN description;
Portuguese Description: Portuguese PN description;
Aircraft Type: automatically populated (for example 0190);
Program Code: automatically populated (for example Embraer 190G);
List ATA 100: system code per program DSM;
DBT Code: aircraft segment;
Status: automatically populated;
Spare Parts Indicator: indicator whether the part is spare or not;
Material Category: material category, automatically populated;
Drawing Group – Category: automatically populated;
4
Origin: technological origin of the PN;
Configurable Type: make to order or make to stock indicator;
Drawing Class: drawing class per program DSM;
Aero Navigability Directives: automatically populated;
Calculated Weight: automatically calculated;
Actual Weight: automatically calculated;
Design Indicator: responsible for the PN design;
Partner Design: partner responsible for the project design;
CPL (Category Part List): indication if the part number is CPL;
Traceability Indicator: traceability type;
Embraer Code: Embraer internal material code;
MTZ Indicator: do not fill this field;
Kit Indicator: do not fill this field;
Security Code: item confidentiality;
Initial Revision: at Embraer the PN starts with the “ /” revision. Automatically
populated;
Production Indicator: responsible to manufacture the part;
Partner Production: partner responsible for the production;
After completing all attributes, select “Next” to Set the “Security Labels”.
<Note> All the attributes with (*) are mandatory.

<Note> It is forbidden to use special characters to define the UL and CI attributes, for
example Number and Description attributes.
4
Upper Level Attributes (2/2)
At “Set Security Labels” tab, select the “Not Applicable” option. The “Compliance Roles”
are groups that define access restriction and this is not applicable for Multi BOM.
Select “Finish” to create the UL object.
The UL is created with “In Work” state.

5
Create Configuration Item
At Windchill the “Configuration Control Team” may create structures with one or more
Upper Level and may create the CI.
A Configuration Item (CI) represents a functional element of the product
and corresponds with a configuration management point in the product
structure.
At Embraer, the eBOM Configuration Items are the Parts used to apply effectivity range.
Configuration Item of eBOM is created at “ERJ 190 Type” container, sub-folder
Configuration Item.
After created an Upper Level the user may create a CI. Using the “New Part” function
select the “eBOM Configuration Item” type.
The CI is transferred to SAP to generate ECODE.
The CI is transferred from SAP to VPM
The CI is only released though of CD and Change Notice associated, at this moment the
task is applied the effectivity eBOM is completed.
The CI used for Test Procedure must be created at the container ERJ 190 Type
The CI used for experimental must be created at the container 190 G Master Data.
<Note> All the DS and Parts are created at VPM. The Designer may create parts and DS.
<Note> The CI have only Release status in Revision, because in CI revision don´t have
“Letter Revision”, it´s have “/”, at Windchill
<Note> At VPM the CI is not released, it stays at READY.
6
6
CI Attributes (1/2)
Depending of the type chosen, the user must fill different attributes.
There are 3 different ways to propagate attribute values:
• Manually Entered: Done by the user upon Part creation or when updating a part.
• Automatically populated: Done by the system and relies on data transactions from
other systems such as SAP and VPM.
• Automatically calculated: Done by the system and uses input values from other fields
to determine the attribute value.
Attributes:
Number: PN number;
English Description: English PN description;
Portuguese Description: Portuguese PN description;
Aircraft Type: automatically populated (for example 0190);
Program Code: automatically populated (for example Embraer 190G);
List ATA 100: system code per program DSM;
DBT Code: aircraft segment;
Status: automatically populated;
Spare Parts Indicator: indicator whether the part is spare or not;
Material Category: material category, automatically populated;
Drawing Group – Category: automatically populated;
7
Origin: technological origin of the PN;
Configurable Type: make to order or make to stock indicator;
Drawing Class: drawing class per program DSM (226);
Calculated Weight: automatically calculated;
Actual Weight: automatically calculated;
Design Indicator: responsible for the PN design;
Partner Design: partner responsible for the project design;
CPL (Category Part List): indication if the part number is CPL;
Traceability Indicator: traceability type (L – Control By Lots);
Embraer Code: Embraer internal material code;
MTZ Indicator: do not fill this field;
Kit Indicator: do not fill this field;
Security Code: item confidentiality;
Initial Revision: at Embraer the PN starts with the “ /” revision. Automatically
populated;
Production Indicator: responsible to manufacture the part (G – Ghost –
Manufactured next Assy);
Partner Production: partner responsible for the production;
Effectivity Type: type of effectivity (Basic, Model or Optional);
Position ID: Collector of DSs have the same optional; The “Position ID” must have
5 characters; The “Position ID” can be repeat for others CI(s).
Process Area: Add all applicable Process Areas by clicking on “+” sign
After completing all attributes, select “Next” to Set the Security Labels.

7
CI Attributes (2/2)
At “Set Security Labels” tab, select the “Not Applicable” option. The “Compliance Roles”
are groups that define access restriction and this is not applicable for Multi BOM.
Select “Finish” to create the CI object.
The CI is created with “In Work” state.

8
Transfer the UL and CI from Windchill to VPM (1/2)
When the UL and CI are created, the life cycle starts with “In Work” state.
When the object is in “In Work” state, it is not transferred to VPM. It is just at Windchill
and, if need, the user may update the attributes.
The link between UL and CI is created at Windchill and transferred to VPM. All the Upper
Level and CI updates are made at the Windchill.
To transfer the object to VPM the user must apply the “Set State” function. Set the state
to “Ready”. At this point the CI is transferred first to SAP to generate ECODE.
Before apply the Set State, the document must be in “Check In” status.
<Note> The message error: "Create Part (Value not authorized): 20523" and the
"CreatePart (Operation 'RenamePart' not authorized - process not found): 20528“ error
will appear if the UL or CI already exist at VPM.
<Note> The message error: "Some Error Occurred in update DB. Error Code: 110“ will
appear if use special Portuguese characters which are not supported by the VPM
database.
<Note> The Message Error "ERROR: The CI has components in its Part List and cannot be
integrated" will appear if the CI have a DS in its structure. This probably occurred
because the CI was created using the "Save As" command. Remove the component and
set state again.
<Note> These errors messages come from VPM systems, and the Integration only show
9
them.
9
Transfer the UL and CI from Windchill to VPM (2/2)
After changing the state to “Ready” the VPM status is null and the State is “Pre Ready”.
The “Pre Ready” is used to support the Interface transfer and lock user interactions.
Select “F5” to update the information at the screen. The update may last until two
minutes, it depends on VPM and Open PDM connection.
If the transfer is successful the state changes to “Ready”.

If the transfer is not successful the state goes back to “In Work”. This may happen if the
object is in “Check out” status, if the part already exists at VPM or if happens some
communication problem.
After define the set state as “Ready” the user can not back to “In Work” state.
During processing activities for the system (WdC, SAP, VPM) by OPEN PDM, if the system
falls, the IT team receives an automatic email about the system failure, and all activities
are on a waiting list, waiting the process back to normal, this behavior is managed by
"Soft-Stopped"
The User is with activity in TRANSFER READY, realizing that this transition is slower while
the process ends.
<Note>In some cases the system may presents instabilities. In some of these situations
Part Numbers stay on systemic status (intermediate) and is necessary to change the
status manually by admin. Embraer requested an enhancement to set automatically the
10
soft-stop in case of system down exceptions. This topic is in discussion.
10
Edit Attributes UL and CI
The “Edit” function show the Basic Attributes and the OOTB (Out Of The Box) Attributes.
Before selecting “Edit”, the user must apply the “Check Out” at the PN.
After editing, the user must select “Check In”.
These fields may be edited at “In Work” and “Ready” state.
The “Usage Attributes” are accessed only after created a link between the PNs.
Before select “Edit”, the user must apply the “Check Out” at the PN.
After editing, the user must select “Check In”.
These fields may be edited at “In Work” and “Ready” state.
The “Position ID” of the CI can be edited in “In Work”, “Ready” , “Released” and “In
Revision” status.
At “Edit Usage Attributes” dialog box, the user must not edit the “Unit” field.
11
Rename UL and CI
The Configuration Control can rename the UL or CI if it is at “In Work” state.

Select Actions > Rename;
At Rename dialog box fill the Name and the Number field.
The Name and Number must be equal.
12
Delete UL and CI
The “Configuration Control” just can delete de UL and CI at “In Work” state.
The “Administrator” may delete the UL an CI at any state.
Select the Delete option:

• Delete all iterations of each object included in the table: deletes all of the iterations of
the revision. For example, if you selected an object version B.3, all iterations of
revision B would be deleted and only iterations of revision A would remain.
• Delete all revisions of each object included in the table: deletes all versions of the
object. For example, if you selected an object version C.1, it would be deleted, as
would all iterations of revisions of revisions B and A. The object would no longer
exists in Windchilll.
• Delete latest iterations of each object included in the table: deletes only the latest
iteration of the revision. For example, if you selected an object version A.4 and A.5
exists, A.5 would be deleted.
13
Edit Attributes - Administrator (1/3)
The “Administrator” may edit multiple parts using an excel file.

First the admin must export a spreadsheet, for that he must select the “Export
Importable Spreadsheet” option.
At the “Export Importable Spreadsheet” dialog box, the Administrator define the “Export
Options”: Parts or BOM.
After, define the “File Name” and select “OK”.
An Excel file is created. The “Administrator” may edit the attributes and save it.
The edit roles must be followed, the “Administrator” may change only the attributes
that are available when the user apply “Check Out”. If the “Administrator” change a not
available attribute, this information will not be updated.
14
After doing the changes, the “Administrator” must import this spreadsheet. Select
“Actions > Import from Spreadsheet”.
At “Import from Spreadsheet” dialog box the Administrator must load the excel file.
At Attributes he may select “Update Only” to update the information and select “Next”.
The next dialog box will do a validation. If the attributes are Ok then the Validation is
Succeeded.
Select “Finish”.
15
To update this information at SAP, the “Administrator” must select all the Parts, then
select “Actions > Edit Multiple Objects” and select “Check In”.
You can see the a new iteration of the Part.
16
Module 3
Creating and Managing Upper Level and
CIs in an eBOM

Exercise 1: Creating UL
Objectives
• Create Upper Level.
• Transfer the UL to VPM.
Scenario
In this exercise, you take the role of a configuration control and create UL in order to create parts of
eBOM structure and transfer to VPM.
Initial Conditions
• Navigate to the ERJ 190 Type container and starts on the Folders > Upper Level > Engineering
folder page.
eBOM process.

Task 1: Create an Upper Level
1. Select the New Part function;
2. Select eBOM Upper Level and fills all the requested attributes. Fill the Number attribute with your
name and today’s date. Example: UL_YourName_Date_001.
3. Fill the attributes:
Number: UL_Treino_YourName;
English Description: DMU_Eng_Collector_E2;
Portuguese Description: Coletor_de_DMU_Eng_E2;
List ATA 100: 000-00-00 GENERAL DRAWINGS(000-00-00);
DBT Code: DBT-Configuration Control (190/195);
Production Indicator: E-Embraer-Manufactured SJK1;
Partner Production:00000-Embraer

4. Select Next, at Set Security Labels tab and select Finish to create the UL.
5. Do the steps 1 to 5 to create a new UL, but this time fill the attributes as shown below:
Number: UL_Treino_YourName_002
English Description: E2 COLLECTOR STR FUS EJETS
Portuguese Description: E2 COLLECTOR ESTRUT FUS EJETS
*The others attributes fill as the first UL.

Task 2: Transfer UL to VPM.
1. Select the UL_Treino_YourName with the third button of the mouse and apply the Set State to
change the state from In Work to Ready.
2. Select OK to close the Set State dialog box and select F5 to update the state. The Upper Level (UL)
with state Ready is transferred from Windchill to VPM.
The training environment does not have any connection with the VPM or SAP. So, after select OK, you
will see the status as Pre Ready. This status is the transfer status, the Windchill is communicating with
the other software. At production environment the state changes to Pre Ready for Ready automatically.
To simulate the Ready status at training environment, log on as user: plmtrn and password: plmtrn,
apply the Set State again and select Ready again.
3. You will see the document with the status Ready. Do the steps 1 to 2 for the
UL_Treino_YourName_002.

Exercise 2: Creating CI
Objectives
• Create Configuration Level.
• Transfer the CI to VPM.
Scenario
In this exercise, you take the role of a configuration control and create CI in order to create parts of
eBOM structure and transfer to VPM.
Initial Conditions
• Completed Exercise 1 of this module.
• Navigate to the ERJ 190 Type container and starts on the Folders > Configuration Item >
eBOM process.

Task 1: Create a Configuration Item
1. Select the New Part function;
2. Select eBOM Configuration Item and fills all the requested attributes. Fill the Number attribute with
your name and today’s date. Example: CI_YourName_Date_001.
Number: CI_Treino_YourName;
English Description: FORWARD FUSELAGE UPPER/LOWER JUNCT;
Portuguese Description: FUSELAGEM DIANTEIRA SUP/INF JUNCAO;
List ATA 100: 000-00-00 GENERAL DRAWINGS(000-00-00);
Drawing Class: 226
DBT Code: DBT-Configuration Control (190/195);
Traceability Indicator: (L – Control By Lots);
Production Indicator: G – Ghost – Manufactured next Assy;
Partner Production: 00000-Embraer;
Effectivity Type: Basic,
Position ID: 00001.
All attributes that have (*) are mandatory

4. Select Next, at Set Security Labels tab and select Finish to create the CI.

Task 2: Transfer CI to VPM and SAP.
1. Select the CI_Treino_YourName with the third button of the mouse and apply the Set State to change
the state from In Work to Ready.
2. Select OK to close the Set State dialog box and select F5 to update the state. The Configuration Item
(CI) with state Ready is transferred from Windchill to VPM.
The training environment does not have any connection with the VPM or SAP. So, after select OK, you
will see the status as Pre Ready. This status is the transfer status, the Windchill is communicating with
the other software. At production environment the state changes to Pre Ready for Ready automatically.
To simulate the Ready status at training environment, log on as user: plmtrn and password: plmtrn,
apply the Set State again and select Ready again.

Module Overview
In this module, you will learn how to create eBOM product structure.
1
Objectives
• Building Product Structures

• Create UL-UL or CI-UL Link
• Update UL and CI Attributes
• Delete UL-UL or UL-CI Link
• New Promotion Request
2
Building Product Structures
Product Structure Browser enables you to modify the existing product structure by
adding and removing objects, and also by editing the attribute values associated with
existing objects.
The “Structure” tab on the part information page contains tools for displaying and
editing the part structure.
The part structure pane is located on the Structure tab beneath the command ribbon on
the left side of the part information page. It contains an indented hierarchy of parts
representing the structure of a product.
The “Editing” group that appears under the “Structure” tab on a part information page
provides the following actions:
• Insert an existing part into the structure.
• Insert one new part (CI or UL) into the structure.
• Insert multiple new parts (CI or UL) into the structure.
• Remove a part (CI or UL) from the structure.
• Edit a part (CI or UL) in the structure.
The “Uses” tab displays the parts that are used by the part selected in the structure
pane. In a three pane display, the “Uses” tab is in the bottom pane. From this tab, you
can perform actions such as inserting new and existing parts and modifying attributes on
the parent/child association between parts.
3
3
Create UL-UL or CI-UL Link (1/3)
At Embraer the structure starts with an UL and below it you may link another UL or a CI
part. At Windchill the “Configuration Control” Team may create the
links between UL and UL or UL and CI.
The Upper Level must be at “In Work” state.

The parts that will be linked at the UL must be in state "Ready" or “Complete”.
To access the “Structure” page the user may select the UL “View Information”;
The UL that will receive the link must be in “Check Out”. When select “Insert Existing”
the UL automatically goes to “Check Out” status.
A “Search” dialog box opens to select the part.
The user may use the “Uses” tab to insert parts (CI and UL) at the structure too using the
“Insert Existing” field and write the CI or UL number.
At the Structure tab you may see the structure created UL – CI.
The CI used for Test Procedure or experimental will not be linked at the product
structure.
It must be linked in a separated collector (Upper Level – Collector EO Experimental) at
container 190 G Master Data, CI for test – ERJ 190 Type.
4
When creating a structure, the user must apply the “Check In” to finish the edition and
to update the structure at VPM.
It will change from “Transfer Ready” to:

- “Completed” if successful.
- “Ready” if not successful. This may happen if happens some communication problem.
<Note> Please, attention to the VPM status. It informs if the activity was successful and
the data was sent to VPM.
<Note> At Structure tab, if the user start to add a PN at the Structure, fill the Usage
Attributes and select Cancel, the user must select "F5" (refresh) to update the page
before apply the Check-In. If the user did not select "F5" and select the Check In a
message error will appear: "Can not ready properly ‘tM‘ of null". To correct it select "F5"
and select Check In.
5
If the Upper Level is in state “Completed” the user can not add a CI or UL link at the
Structure.
If the user try to add a CI or UL an message will appear: “Operation failed because the
user did not have the necessary permission on the following objects to perform the
operation”.
If the user must edit the Upper Level, he needs to start a “New Promotion Request”
process.
6
Update UL and CI Attributes
If the UL or CI attributes need to be updated the user must pay attention at the state.
We have two options to update the part depending on its state.
- Update the UL or CI at State “In Work”:

If the part is in “In Work” the user may update the attributes applying the “Check Out”
and “Check In”.
When applying the update in State "In Work“ there is no interface triggered, only update
in PLM.
- Update the UL or CI at State “Ready”:

If the part is in “Ready” the user may update the attributes applying the “Check Out”
and “Check In”.
When applying the update in State “Ready” the information must be updated at PLM
and VPM.
After the “Check In” the state "Transfer Ready" is set by the system.
If successful: The Upper Level state set to "Completed" - controlled by Interface and the
CI state stays in “Ready”
In case of error: The Upper Level state stays in “Ready"
- Update the UL at State “Complete”:
7
If the part is in “Complete” the user must start a workflow process applying the “New
Promotion Request”.
7
Delete UL-UL or UL-CI Link
The “Configuration Control” or “Admin” may delete the link between the UL-UL or UL-CI
if the state is in “Ready”, if the state is in “Completed” a “New Promotion Request” is
required.
To create a “New Promotion Request” the user must select with the third button of the
mouse the UL, select “New” and “New Promotion Request”. This will be explained in a
specific course about the change process.
To delete the link select the CI or UL with the third button of the mouse and select
“Remove”.
The link between the CI-DS and the link between the Lower Level and DS are made at
VPM. If necessary, these links must be removed at VPM.
8
New Promotion Request (1/3)
If the Upper Level must be edited and is in state “Completed”, the user must start a
workflow process applying the “New Promotion Request”.
This option start a process where the approver will approve the request to edit the
Upper Level.
Selecting the Upper Level with the right button of the mouse, select “New > New
Promotion Request”.
At “New Promotion Request” dialog box fill the “Description” and select “Next”.
9
At “Select Promotion Objects” you can see the Upper Level that will be edited.
Select “Next” to define the approver.
At “Select Participants” select the approver.
At Folder content you can see the “New Promotion Request” created.
The approver will receive a task to approve or not your request.
10
The Approver receives a task to “Approve Demotion Request”.

At this task, the approver must approve or reject the request of editing the Upper Level.
After choosing the “Routing Option”, the approver must select “Complete task”.
If selecting Approve, the Upper Level is set as “Ready” and the Configuration Control
may edit it.
If selecting Reject, the Upper Level state continue “Completed” and the Configuration
Control can not change it.
11
Module 4
Building eBOM Product Structures

Exercise 1: Creating Link UL-UL and CI-UL
Objectives
• Create link between UL-UL and between CI-UL.
Scenario
In this exercise, you take the role of a Configuration Control and add CI to UL, UL to UL and change the
state to complete.
Initial Conditions
• Completed Exercise 1 and 2 of the module 03.
• Navigate to the ERJ 190 Type container and starts on the Folders page.
eBOM process.

Task 1: Check out UL
1. To create the link between the UL and CI you must access the structure tab of the part that will receive
the link, in this case the UL. Open the UL_Treino_YourName_002 View Information page.
2. The link is created at the Structure tab. Select the Structure tab.
3. Select Insert Existing to create the link with the CI. The Upper Level changes to Check Out
automatically.

4. Search for the CI that you create before (CI_Treino_YourName). Select the CI and select OK.
You can see the structure UL-CI at the Structure tab.
5. At Edit Usage Attributes dialog box fill the fields:

Line Number: 10
FTI Indicator: NO
Select OK.

Task 2: Check in the UL and update the state
1. At the UL Structure tab select Actions > Check In to end the modification.
2. Select F5 to update the state to Complete. The link between the CI and UL is transferred from
Windchill to VPM.
3. You can see the state as Transfer Ready, because the training environment does not have any
interface to VPM or SAP. To simulate the state Complete, log on as user: plmtrn and password:
plmtrn.
4. Select Actions > Set State > Completed.

5. You can see the state as Completed.

Task 3: Check out UL
1. Log on as confcontrol01 to create the link between the UL and UL. You must access the structure tab
of the part that will receive the link, in this case the UL 01. Open the UL_Treino_YourName View
Information page.
2. The link is created at the Structure tab. Select the Structure tab.
3. Select Insert Existing to create the link with the UL. The Upper Level changes to Check Out
automatically.

4. Search for the UL that you create before (UL_Treino_YourName_002). Select the UL and select OK.
You can see the structure UL-UL at the Structure tab.
5. At Edit Usage Attributes dialog box fill the fields:

Line Number: 10
FTI Indicator: NO
Select OK.

Task 4: Check in the UL and update the state
1. At the UL Structure tab select Actions > Check In to complete the modification.
2. Select F5 to update the state to Complete. The link between the UL and UL is transferred from
Windchill to VPM.
3. You can see the state as Transfer Ready, because the training environment does not have any
interface to VPM or SAP. To simulate the state Complete, log on as user: plmtrn and password:
plmtrn.
4. Select Actions > Set State > Completed.

Module Overview
In this module, you will learn how to work with electrical PNs at Windchill.
1
Objectives
• How to identify if PN is a Harness?

• Understand Wiring Diagram Process
• Create Wiring Document
• Transfer Wiring Document to SAP
2
How to identify if PN is a Harness?
VPM requires all T1/T2 are MTS for E2- so Harness parts will be created as MTS for
eBOM.
The Drawing Class is the way to identify a Harness Part Number:

• For -200 part number
122-ELECTRICAL HARNESS 3D MODEL
• For -400 or -500 part number

005-SIMULATOR - ELECTRICAL WIRING
105-PRODUCT - ELECTRIC WIRING
305-REPAIR - ELECTRIC WIRING
405-TEST -ELECTRIC WIRING
505-FTI -ELECTRIC WIRING
705 705-STUDY - ELECTRIC WIRING
805 805-AGE/PNA - ELECTRICAL WIRING
905-SB - ELECTRICAL WIRING
<Note> In the link between Harness and -2xx on VPM is not necessary to include the
Position and Zone.
<Note> During the Wiring PN creation and Harness PN creation, the user must fill the
“List ATA 100” field, but must not fill with “ATA 000-00-00”. If the user add this value at
“List ATA 100”, an error will occur at EES. The EES does not recognize this value.
3
<Note> During the EO creation, for Wiring and Harness PNs, the user must fill the “List
ATA 100” field, but must not fill with “ATA 000-00-00”. If the user add this value at “List
ATA 100”, an error will occur at EES. The EES does not recognize this value.
3
Wiring Diagram Process
Wiring Diagram, WDL, SBL (Service Bulletin List) or HL are created by user first on Windchill and
transferred to SAP by automatic integration started by user. They are created as documents at Windchill.
Integration between EES, IGE-XAO and SAP maintained As-Is.
EES is the owner of Wiring Diagram, WDL, SBL and HL Structure and transfer this structure to SAP only.
General Process:
1 – The Wiring Diagram, WDL, SBL and HL are created at Windchill with “In Work” state;
The user must change the state to “Ready”. At this point the object is transferred to SAP. At SAP the
Wiring Diagram, WDL, SBL and HL are PNs.
The SAP create the eCODE and send it to Windchill.
2 – For the EES consume the Wiring PN, these PNs must be released by the EO process.
At Windchill the user creates a EO. Inside the EO the user creates a Change Activity (CA) for each
document (Wiring Diagram, WDL, SBL and HL).
The EO is created at SAP automatically.
3 – User submit the EO for approval.
Once approved, EO is transferred to SAP with Wiring Diagram, WDL, SBL and HL as Affected PNs.
4 – If the EO is approved, the Wiring Diagram, WDL, SBL and HL are available to be used at EES.
The user consume the PNs available at SAP.
User finish development of Wiring Diagram, WDL, SBL and HL in the EES.
5 – The CAs with Wiring Diagram, WDL, SBL and HL are released only at Windchill.
6 - At EES the user will structure the PNs. This structure is transferred back to SAP.
7 – To release the Wiring Diagram, WDL, SBL and HL at SAP the user must release the PN at EES. After
release at EES the PN is released at SAP.
<Note> During the Wiring PN creation and Harness PN creation, the user must fill the “List ATA 100” field,
but must not fill with “ATA 000-00-00”. If the user add this value at “List ATA 100”, an error will occur at
EES. The EES does not recognize this value.
4
<Note> During the EO creation, for Wiring and Harness PNs, the user must fill the “List
ATA 100” field, but must not fill with “ATA 000-00-00”. If the user add this value at “List
ATA 100”, an error will occur at EES. The EES does not recognize this value.
4
Create Wiring Document (1/2)
The Designer create the Wiring document at Windchill at 190G – Final Assy – Harness –
FTI Inst container.
Each document shall be created under the proper document folder under Electrical
Engineering folder.
The Wiring (Wiring Diagram, WDL, SBL or HL) are create at Windchill as Documents.
Select “New Document”;

Select “Wiring Diagram, WDL, SBL or HL”;
Fill the Number according to Embraer rules.
For “Wiring Diagram” the number is defined by prefix - radical;
For “HL”, “SBL” and “WDL” the number is defined by prefix - radical - serial number of the
aircraft;
Fill all mandatory (*) Attributes.
Select “Next”. At Security Labels, select “Next” again.
5
Create Wiring Document (2/2)
In the uBOM, Embraer have the DIP box for the Wiring Diagram PNs connected to a top
of Master Data.
For multiBOM, the user can add these information at “Set Attachments” tab.
The Wiring Document is created at “In Work” status.
6
Transfer to SAP
After creating the Wiring Document, the Designer must transfer it to SAP.
At SAP the document is recognized as a PN.
The Wiring Document is created at “In Work” state. Apply “Set State” to move to
“Ready” state and transfer it to SAP.
When the Designer set the state to “Ready”, the Wiring Document is transferred to SAP
as a PN.
7
Module 05
Managing Lower Level eBOM - Wiring
and Harness
Exercise 1: Create Wiring Document and Transfer to SAP
Objectives
• Create the wiring document;
• Transfer to SAP;
Scenario
In this exercise, you will create a wiring document.
Initial Conditions
• Log on to Windchill using “designer01” user and password “emb”.
• Navigate to the 190G - Final Assy - Harness - FTI Inst, Embraer container and starts on the
Documents->Engineering->Electrical Engineering Folder page.
eBOM process.
Task 1: Create Wiring Document
1. Select New Document to create a Wiring Document.
2. At New Document dialog box, select Type as Wiring Diagram.

At Primary Content Source, select No Content.
3. Fill the Attributes:

Number: 197_YOURNAME
Program Model: Embraer 190-E2;
English Description: AC Generation 1;
Portuguese Description: Geração 1 AC;
List ATA 100: 024-21-50 INVERTER AC GENERATION(024-21-50);
4. Select Next
5. Select Finish.
Task 2: Send to SAP
1. Select the PN with the right button of the mouse and select Set State.
2. At Set State dialog box select Target State as Ready.

3. Select OK.
4. The training environment does not have interface to SAP, so the status at this environment
appears as Pre Ready.

Module Overview
In this module, you will learn how to create and manage Lower Level PNs at Embraer.
1
Objectives
• Create DS for Test Procedure - eBOM

• Create Document Test Procedure - eBOM
• Associate DS-Document for Test Procedure - eBOM
• Create Link CI-DS for Test Procedure - eBOM
2
Create DS for Test Procedure - EBOM
The Test Procedure is created on eBOM structure to provide test requirements for
Product Engineering and Manufacturing Engineering area of E2 Embraer Program.
The user have to create a DS (eBOM Design Solution) for ETPP in WdC as “Embraer
System Engineering” role.
This part shall be created in Embraer parts from Windchill subfolder, located in 190G
Forward Fuselage (in this example), Embraer container, where option “Embraer Design
Solution” template is available.
There is a symbolism which shows Test Procedure Part “eTPP” and Test Procedure
Document “eTPD”.
eTPP needs to have Embraer ECODE.
After the user will create a ETPD to link on ETPP.
<Note:> For Test Procedure purposes its possible to use eBOM Design Solution types 1
or 7 (installation).
3
Create Document for Test Procedure - eBOM
After creating the ETPP, the user shall create a Document for test procedure – ETPD
The user have to create a Document for test procedure as “Embraer System
Engineering” role.
In “Related Objects” tab of the DS – ETPP, the user can create the ETPD in “ Described by
Document “
The user can ADD or Create New.
The ETPD shall be created as “General EMB Document” type Test Procedure.
The ETPD may have some files attached, URL Link or External Storage, but when the
ETPD is created inside of the ETPP it´s associated automatically.
4
Associate Document for Test Procedure - eBOM
The Windchill allows the user associate the ETPD inside ETPP
The user shall link the ETPD to ETPP as “Described by Documents”

The ETPD may be added as new or associated to ETPP part
When the ETPD is created inside ETPP, it´s associated automatically.
<Note>The ETPD shall be associated to ETPP while it´s not in Pre-Released/Released

State, therefore the Windchill avoid eTPD to be Deleted, Inserted or Edited if eTPP is in
Release state.
5
Create Link CI-DS for Test Procedure - eBOM (1/2)
The User must create CI within the Windchill through the Embraer Configuration Control
role at ERJ 190 Type, container.
Once the CI is created, the User must add the DS-eTPP on “Related Objects” tab in
“Design Solution” table, this operation can only happen within the Windchill
environment in 190 Type Container.
<Note> The eBOM CI and DS-eTPP linked shall be applied the same Effectivity rule eBOM
CI-DS.
<Note> A DS ETP T7 must be linked to both a mBOM CI T8 and an eBOM CI.
6
Create Link CI-DS for Test Procedure - eBOM (2/2)
The eBOM part is released within in WDC.
The CI-DS Test Procedure need to be sent in Ready state to SAP.

- Select the CI with the right button of the mouse and select the Set State.
- Select Transfer Ready.
This way the CI is ready to be released, so the user can apply the same Release rules.
<Note> Recommended to perform this action after effectivity applied.
7
Module 6
Managing Lower Level eBOM PNs
Test Procedure
Exercise 1: Create Test Procedure (eTPP) and Test Procedure Doc
(eTPD)
Objectives
• Create the DS for Test Procedure;
• Create the Doc for Test Procedure;
• Link the ETPP with ETPD;
Scenario
In this exercise, you can create Part and Doc for Test
Initial Conditions
• Log on to Windchill using “systemeng01” user and password “emb”.
• Navigate to the 190G - Forward Fuselage, Embraer container and starts on the Folder page.
eBOM process.
Task 1: Create DS for Test Procedure
1. Select EBOM Part from Windchill sub-folder.

2. Select New Part to create DS for Test Procedure
3. Fill Number (ETPP-YOURNAME) fill in the other fields in accordance with the requirements.
Type: EBOM Design Solution Type 1

English Description: ETPP_YourName;
Portuguese Description: ETPP_YourName
List ATA 100: : 000-00-00 GENERAL DRAWINGS(000-00-00);
Origin: A_0 – Tech engineering;
Drawing Class: 001 – Simulator – Detail
Calculated Weight: 10;
CPL (Category Part List): Not listed in CPL report;
Traceability Indicator: I - Individual Controls (Of);
4. Select Next
5. Select Set Security Labels
6. Select No for ITAR and Not Applicable for Security Control
7. Select Finish
Task 2: Create the Test Procedure Doc (ETPD)
1. Select View Information of the ETPP_YOURNAME
2. Select Related Objects tab and Described By Documents table

3. Select Add New Documents, but the users can Add Existing Document.
4. Select OK to confirm the Check-Out

5. Select General EMB Document in dialog box.
6. Fill the Primary Content Source as No Content.
7. Select Number/Name ETPD-YOURNAME
8. Select Test Procedure for Document Type
9. Select Next

12. Select Next
13. Select Set Attachments, the users can attach any documents.
14. Select Finish
15. The ETPD is linked with DS ETPP
16. Select Action and Check in.

Exercise 2: Update Test Procedure ETPP and ETPD
Objectives
• Update the ETPP and ETPD
• Update the ETPP IN Work state
• Update the ETPP IN Ready state
• Update the ETPP IN Revision State
• Update the ETPP IN Released, Pre-Released state
Scenario
In this exercise, if necessary the user can update ETPP and ETPD.
Initial Conditions
• Navigate to the 190G - Forward Fuselage, Embraer container and starts on the Folder page.
• The DS ETPP and ETPD must be created.
eBOM process.
Task 1: Update Test Procedure IN Work state
While the DS ETPP will be IN Work state, the User may define several changes, as:
Delete;
Create or Add other Documents;
Apply Check Out and Edit.;
1. Select with right button of the mouse the Check Out and Edit.
2. Change the English Description and Portuguese Description adding the text “Change”
3. Select Check In and OK.
4. See the ETPP updated.

Exercise 3: Create CI and Link CI - DS for Test Procedure
Objectives
• Create the CI for Test Procedure;
• Create link between CI and DS;
Scenario
In this exercise, you take the role of a configuration control to create the eBOM Test Procedure.
Initial Conditions
• Navigate to the ERJ 190 Type, Embraer container and starts on the Folder > Configuration Item >
• The user must have DS ETPP created
eBOM process.
Task 1: Create the CI for Test Procedure
1. Select New Part.
2. Select EBOM Configuration Item on TYPE field

Number: CI-ETPP_YOURNAME ;
English Description: CI-ETPP_YOURNAME;
Portuguese Description: CI-ETPP_YOURNAME;
Effectivity Type: Basic;
List ATA 100: 000-00-00 GENERAL DRAWINGS(000-00-00) ;
DBT CODE: DBT Embraer;
Position ID: 001;
3. Select Next
6. Select Finish
Task 2: Create Link CI – DS for Test Procedure
1. Select View Information of the CI-ETPP_YOURNAME
2. Select Related Objects tab.

3. Select Design Solution Table.
4. Select Add Existing to add the DS ETPP (The user may create new DS).
5. Select number and typing ETPP*

6. Select the ETPP_YOURNAME
7. Select OK
8. When was added the DS ETPP within of the CI ETPP, the system do Check –Out automatically,
But the user can doing Check – Out before.
9. Select Action and Check- IN

10. Select OK on Dialog box.
11. This moment CI – DS for Test Procedure is Linked

Module Overview
In this module, you will learn how to manage eBOM lower level at Windchill.
1
Objectives
• Design Solution
• Drawing Sheet
• Flex Parts
• Flex Filter
• PE/PNE parts process in Windchill
• Reuse process in Windchill
• RME Part Process in Windchill
• Edit Attributes at VPM
2
Design Solution
With this new process, for E2 program, the VPM communicates with WdC and it communicates
with SAP. Windchill orchestrates all info related to Change Management.
All the Embraer work process inside the VPM will not change.
The Design Solution is created at VPM as Type 1 (T1). The user apply the trigger “Set Maturity”
to communicate VPM with Windchill.
With the trigger “Set Maturity” the DS is transferred to Windchill.
All the parts are created at VPM. The link between the part and DS is created at VPM too.
Applying the trigger “Set Maturity” the structure is transferred to Windchill.
The user may link different DSs at one CI at the same time, he do not need to create the link one
by one.
The user may link the same DS at more than one CI at the same time, he do not need to create
the link one by one.
All the Part information (number, type, description, ATA code, origin, DBT, weight, etc) and the
link information (position, zone, DUMP, FTI, notes, etc) are transferred from VPM to Windchill.
Talking about the Instantiation:
DS instantiation in CI: When the user turn on the CI-DS, it should apply the instantiation at
connect time, this action will be done in VPM.
<Note> At Windchill, the Parts are visualized in a light-weight format and this feature enables
easy access from Anywhere through a browser.
<Note> For the PNs that have 3D: the VPM will put the quantity that reflect at the 3D, but, at
DUMP, put the unit value, for cases that the size is the same in all 3D "sectors”. When there are
diﬀerent values in spa<al posi<ons, put the average.
<Note> if the User does not instantiate at connect time, and if the CI is released, it will not be
possible to edit the value of instantiation. To edit, the user shall trigger the support.
<Note> For Ipanema project, read the “CT3443 – Ipanema Deck of Slides” and the “CT3937-QRC
for Ipanema” materials to learn specific Ipanema process and functions.
3
Drawing Sheet
The drawing sheet follow the same process of the PN.

The drawing sheet is created at VPM and linked at the PN.
When transfer the PN to Windchill, the Drawing Sheet will appear at “Related Objects”
tab, “Described by Document” table of the PN View Information.
At Windchill, the Drawing Sheet is a document with type “Drawing/Grafics”.
4
Flex Parts (1/2)
This object type FLEX is created at VPM to support the ability to have different
visualization for the same part number.
5
Flex Part (2/2)
Flex part is a way of representing a 3D viewable item in WDC multiple ways.

The structure of parts and “FLEX Part” are created in “VPM” allowing it to be type: T1 /
T2 / T3 / T4 / T5 / T6 / T9.
The roles are EBOM Product Structure, MBOM Product Structure.
Once the structure was created in VPM and sent to the WdC, the integration
automatically create the eBOM structure:
At Windchill, all FLEX instances are transferred with the same part number of the VPM
adding (_FLEXxxx);
The integration create a “Fake” part number adding “_1” to build the corresponding
instance 1 when the instance 1 part is used in VPM as part of the visualization.
The Flex Part are released automatically on VPM when the PN “Instance 1” is released.
To learn how to release a PN, ready the material “EMBRAER Windchill 10.2 Design
Change Management and Release”.
6
Part List Filter
The user can visualize the structure with all the parts including ARM, MBD and Flex, or
can filter the structure to visualize only the Part List.
To do that select the Structure tab, Saved Filter > Part List.
If the Part List filter did not appear, select Manage Filters and select “Show” for the Part
List filter.
At Uses tab, the user can visualize all the parts form the current structure. With the Part
List filter applied, the user will see only the part list information.
<Note> When applying any type of filter, the visualization will corresponding the filter
that was applied. To visualize the completed structure, select System Default filter
option.
7
PE/PNE Part Process
The PE/PNE will continue be created and managed by SAP.

When utilized at Product Structure at VPM, Windchill will import the PE/PNE from SAP.
At Windchill the PE/PNE (Embraer Standard) parts have a specific Library Container:
Embraer Standardized.
The Part Types 1 and 2 will come from VPM E-Library to Windchill just if starts with a PE
or PNE.
The PE/PNE visualization comes from VPM and the PE/PNE can be revised in VPM to
attach new CAD-Data to them.
At Windchill the user can visualize the VPM PE/PNE version (Details tab > VPM CAD
Versions) and the SAP PE/PNE version (Folders Content > Version).
8
Reuse Process
Re-used Parts are needed as components in the Windchill eBOM structure.

Reuse Part types must be a “MTS” and only for type 1,2 and 6.
The Reused PN are stored at containers divided by Program Type.
The latest released version is triggered from SAP to Windchill.
No structure, Notes or associated files are transferred from VPM to Windchill, except 3D
visualization.
Reuse Process, detailed steps:

1. Designer identify a necessity to reuse a part number created by another program;
• If a reused part number was created by 170/190 program, designer only need
to link this part in an E2 part list;
• If a reused part number was created by any other Embraer program, designer
need to “create” this part in the E2 VPM data base and then link it to an E2
part list.
2. Designer “export part list” to Windchill (eBOM);
3. Windchill will verify if reused part number already exist in Windchill;
• If reused part exists, the part list will be exported with the reused part
number;
• If does not exist yet, Windchill will mark the part as a “reuse” in SAP and will
export all Part number attributes to integration data base.
9
RME Part Process
The RME will continue be created and managed by SAP.

When utilized at Product Structure at VPM, Windchill will import the RME from SAP.
At Windchill the RME parts have a specific Library Container according to ATA100.
For applicability of T3, T4, T5 and T9, the consistence is verified at VPM.
The RME visualization comes from VPM and the RME can be revised in VPM to attach
new CAD-Data to them.
At Windchill the user can visualize the VPM RME version (Details tab > VPM CAD
Versions) and the SAP RME version (Folders Content > Version).
The MSDS data is not sent to Windchill. If a purchased item has the MSDS, the MSDS
information can not be visualized at Windchill. The user must visualize the MSDS
information at SAP.
10
RME Part with Alternative PN
The user create an alternate PN on SAP and then this PN may be accessed on Windchill.
The user that create on SAP system is Embraer Engineering.
The user access the Part information of the RME PN.

Select Related Objects tab.
Select Alternate table and then select the Alternative PN.
With selected Alternative PN
Select History tab and View information of the alternative PN.
11
Module 7
Flex, PE/PNE, RME, Reuse

Exercise 1: Apply Part List Filter
Objectives
• Part List Filter as: Arm, RME Flex, MF Flex and MBD
Scenario
In this exercise, you can hide some parts through Saved Filters.
Initial Conditions
• Navigate to the ERJ 190 Type, Embraer container and starts on the Folder page.
eBOM process.

Task 1: Apply Saved Filters.
1. Select View Information of the TRAINING DATA SET UL
2. Select Structure tab and expand all structure. (see some parts to filter)

3. Select Saved Filters and Part List to hide the parts.
4. The User can see that does not have a some parts (ARM)
5. If want back, just select System Default on Saved Filters

Module Overview
In this module, you learn how to manage lower level.
1
Objectives
• SPD From VPM

• Create link SPD- RME
• SPD Report
• Create ICD at VPM
• Link Technical Reports at ICD
• Generate ICD Report
2
SPD from VPM
The SPD parts are specification drawings created to be used for procurement, and after supplier
selection, they are replaced by purchased parts in Embraer manufactured part list.
The steps to create and edit the SPD PN is the same of the other Lower Level PNs.
To create the SPD PN, the designer, at VPM, create a PN with the attribute “Drawing Class” equal
to “617”.
Designer sets eBOM SPD Design Part (T1-“assy” or T2) object to status “SAP Ready” in VPM.
The eBOM SPD Design Parts (T1-“assy” or T2) with status “SAP Ready” will be transfer during the
integration process from VPM to Windchill and from Windchill to SAP to get the ECODE.
The SPD is transferred to Windchill with “Ready” state.
The SPD PN can have SPD children and the part list may send to SAP (Not relevant for production
– position=> 90000)
The SPD part is linked as children in a manufactured part list
If the creation not succeeded in SAP:
• Item is not created in SAP;
• Item returns to status "In Work" in VPM;
• Error Status Message received from SAP Interface.
To learn how to release a PN, ready the material “EMBRAER Windchill 10.2 Design Change
Management and Release”.
The system allow releasing of an SPD part with SPD children in part list.
<Note> When the Partners create the SPD part, this part need to be created in Partner specific
folder.
3
Create link SPD-RME
To create the link between the SPD and RME, the SPD should be in Released state, as
best practice.
The SPD follow the same releasing process as other PNs.
Ready the “EMBRAER Windchill 10.2 Design Change Management and Release” material
to learn how to release a PN.
The “Embraer Designer”, “Embraer Drawing Responsible Engineer” and “Embraer System
Engineer” can create and remove this link.
To create the link:

• Logon in Windchill and navigate to container where the eBOM SPD Part is stored (190
G Master Data, Embraer)
• Open eBOM SPD Part information details and navigate to “Related Objects” tab.
• In section “Alternates” select option “Add Alternate” to add alternate part.
• In new “Add Alternate” window, search for the RME part.
• Select the part from the searching results to add as alternate.
<Note> The link shall be done opened SPD part and adding RME part as alternate,
“never” add the SPD part as alternate in the RME selected
<Note> Make sure to add the RME part as one way.
<Note> The link can be created only after the SPD is in released state.
4
Generate SPD Report
The SPD Report can be generated at any moment, where the user can see all displayed field
To verify these information, the user can create a report at Windchill:
• Log in to Windchill and Navigate to Reports area, under any available project.
• Navigate to Engineering folder and open/view the "SPDs" report.
• Select all columns and generate the report.
The SPD Part State shown the column state (Released, Ready, In Work…).
The RME Link Status column shows if link exist (YES or NO).
The RME part linked to SPD part and other complementary information about the SPD part
The Product Engineering, Manufacturing Engineer and Purchase Area can verify all the SPD in order to
proceed with necessary actions, such as :
- Designer : Release part to turn it available for procurement
- Purchase area : uses the SPD drawing to search part in market and select supplier
- Designer or system engineer : link RME part to SPD part in Windchill (after supplier part defined)
- Designer : replaces SPD part by RME in eBOM next assemblies
The SPD part, containing a list with all related attributes to generate SPD Report:
- SPD Part Number;
- SPD Embraer Code;
- English Description;
- Portuguese Description;
- List ATA 100;
- Design Indicator;
- DBT Code;
- SPD Part State;
- RME Link Status;
- RME Part Number;
- SPD Created;
- SPD Last Modified;
<Note> The Purchase Area must have the SPD part released on SAP, to send the information for Suppliers,
it is done using an special command in WdC to release SPD part in SAP, it will be showed hereafter
5
Create ICD/BD at VPM
The ICD/DB part is an object that is created on VPM and transferred to WDC and SAP to generate
ECODE.
To create the ICD/BD part, the user needs to have “Designer” role. All ICD/BD parts are created
on “ 190 G Master Data Embraer ” container, inside sub folders, one for ICD Parts and other for
BD Parts on Windchill.
The ICD/BD part are PN Types 1 Sub-Assy or Type 2 Primary Part, only.
The ICD can be Created and Revised by Embraer.
Embraer designer uses VPM function “Send Context To” to involve a partner on an ICD part.
ICD/BD part shall not contain components (except models) and it shall be controlled by process.
The ICD/BD part do not need a next assembly on WDC / SAP to be released.
ICD Part Drawing codes are: 214, 714 or 814 (Mandatory).
BD Part Drawing code is: 218 (Mandatory).
<Note> The ICD/BD Part is created on SAP in status “Not Released”
<Note> When the Partners create the ICD part, it’s created in Partner specific folder.
6
Link Technical Reports at ICD
The ICD Parts (Interface Control Drawing) needs to have a ICD document (Interface
Control Document) that is Technical Report.
To add the ICD Document, the user have to be “Designer” role.
The ICD Parts have to be in status “Ready” to add a Technical Report document, this
action happen in “Related Objects tab >> Revision Child Objects.”
The User can see on both objects, Part and Documents.
7
Generate ICD Report
The ICD Report can be generated at any moment, where the user can see all displayed
field
To verify these information, the user can create a report at Windchill:
• Log in to Windchill and Navigate to Reports area, under any available project.
• Navigate to Engineering folder and open/view the “ICD" report.
• Select all columns and generate the report.
The ICD Part shown the column state (Released, Ready, In Work…).
The Product Engineering, Manufacturing Engineer and Purchase Area can verify all the
ICD in order to proceed with necessary actions, such as :
The ICD part, containing a list with all related attributes to generate ICD Report :
- ICD Part Number;
- ICD Part Ecode;
- ICD Part Description;
- ICD Part Type;
- ICD Drawing Class;
- ICD Part status;
- ICD Document Number;
- ICD Document Description;
- ICD Document Status;
- ICD Part Location;
- ICD Document Type;
The user can export the Report for different files extension
8
2014 PTC Module 8
Module 8
SPD and ICD
2014 PTC Module 8

Exercise 1: Creating SPD Report
Objectives
• Create SPD Report
Scenario
In this exercise, you take the role of a system engineer and create a SPD report to verify which SPD are
already linked to RME.
Initial Conditions
• Navigate to the 190G – Master Data, Embraer container and starts on the Report page.
eBOM process.

Task 1: Generate the SPD Report
1. Select the 190G – Master Data, Embraer container and select Report page.
2. Select Engineering folder. Select SPDs report.
3. At Report Builder dialog box (Criteria), select the attributes that you want :
• SPD Part Number;

• SPD Part State;
• RME Link Status.
2014 PTC Module 8

4. Select Generate to create the report.
5. You can see the result at Results Table.

Exercise 2: Create link RME-SPD at Windchill
Objectives
• Create link between the SPD and RME.
Scenario
In this exercise, you take the role of a system engineer to create the link between the SPD and RME PN.
Initial Conditions
• Log on to Windchill using “plmtrn” user and password “plmtrn”.
• Navigate to the 190G – Master Data, Embraer container and starts on the Folder > SPD folder page.
eBOM process.
2014 PTC Module 8

Task 1: Prepare the SPD for the exercise
1. To simulate the SPD at Released state, you will apply the save as at an existing SPD and will
apply the Set State to change the state to Released. Remember, this is only for the exercise, at
Embraer the PN is released by BR, BRS or EO process.
2. Select the PN SPD-EBOMT1-001 with the right button of the mouse.
3. Select Save As.
4. Fill the SPD New Number as SPD_YOURNAME.

5. Select OK.
6. The SPD is created as In Work state.

7. To create the SPD-RME link, the SPD must be ate Released state. To release the SPD the user
must use a BR or EO process.
8. Here we will only simulate the PN with the status Released.
9. Select the SPD with the right button of the mouse and select Set State.
10. Select Released.

11. Select OK.
12. You can see the SPD PN at Released state.
2014 PTC Module 8

Task 2: Create the SPD-RME link.
1. Log on as “designer01” user and “emb” as password.

2. Select the View Information of the SPD that you created (SPD_YOURNAME).
3. Select Related Objects tab.

4. Select Plus symbol of Alternates table.

5. Search for the RME RMEB2P106P26S0301.
6. Select the RME RMEB2P106P26S0301.
7. Select OK.
8. You can see the RME linked to the SPD PN.
2014 PTC Module 8

Exercise 3: Creating ICD Report
Objectives
• Create ICD Report
Scenario
In this exercise, you take the role of a system engineer and create an ICD report.
Initial Conditions
• Navigate to the 190G – Master Data, Embraer container and starts on the Report page.
eBOM process.

Task 1: Generate the ICD Report
1. Select the 190G – Master Data, Embraer container and select Report page.
2. Select Engineering folder. Select ICDs report.
3. At Report Builder dialog box (Criteria), select the attributes that you want :
• ICD Part Number;

• ICD Part Type;
• ICD Part Status;
4. Select Generate to create the report.
2014 PTC Module 8


Exercise 4: Link Technical Reports at ICD
Objectives

• Create a Link between ICD and Technical Report;
Scenario
In this exercise, you can create a Link between ICD Part to Tech Report
Initial Conditions
• Navigate to the 190G – Master Data, Embraer container and starts on the Folder > ICD folder page.
eBOM process.
2014 PTC Module 8

Task 1: Save As ICD Part to apply Link
1. Select ICD-Your_Name with right button of the mouse and select Save As.
2. In Common Space Save As dialog box, add new name (Your_Name).
3. Select OK.
4. Select ICD-Your_Name with right button of the mouse and select Set State.
5. In Set State dialog box, select Ready state in Target State table.
6. Select OK.
7. You can see the ICD as Pre Ready because the training environment does not have any
interface with SAP or VPM.
8. Apply the Set State > Ready again.
Note: The ICD Part must be in Ready state.

Task 2: Creating Link between ICD Part to Technical Report.
1. Log on as user: designer01 and password: emb. Select View Information of the
ICD-Your_Name.
2. Select Related Objects tab and Revision Child Objects table.
3. Select Add Existing Objects to add the Tech Report.
4. In Find Object dialog box, select Tech-Rep-Training on Name field and Search.
5. Select OK.
6. See the Link between ICD Part and Tech Report.
2014 PTC Module 8

Module Overview
In this module, you will learn how to create Symmetry part.
1
Objectives
• Symmetry From VPM

• Remove Symmetry
• Visualize Symmetry
2
Symmetry From VPM
The Symmetric part consist in Principal Part and Specular part, and ensuring that a specular PN
has a same life cycle of a principal PN.
For E2 Program, the VPM is master for Symmetry process on eBOM and the WdC shall comply.
For Ipanema Program, WdC is the master for Symmetry Process.
The Product Engineering (eBOM/mBOM) have to create Symmetric part and the user have to be
“Designer” role.
These items can be Symmetric Part:
- eBOM Design solution Types 1 or 7;
- eBOM T1 Sub Assembly;
- eBOM T2 Single / Primary part;
- eBOM T6 type;
The User must create the eBOM Symmetric part on VPM and Transfer to Windchill and SAP to
generate ECODE.
The Part List is created on VPM and Transfer to Windchill.
The Open PDM can create link between Symmetric Parts on Windchill.
The attribute Class for Symmetric parts must not be “NO SYMMETRY” on VPM.
Parts will be symmetric when they exist and their number are number + 1 (E.g. 196-54000-101
and 196-54000-102).
Exception:
The MF part can also be symmetric and rule shall also be applied (E.g. 198-25411-201_MF and
198-25411-202_MF)
<Note> The symmetry link shall be created automatically on Windchill, when the user creates
the even part (Specular Part) on VPM.
3
Remove Symmetry
The Symmetric part is applicable to Embraer Program and the Symmetric process
consists of ensuring that a specular PN has a same life cycle of a principal PN.
The Symmetry condition can be cancelled when the user (owner of the PN) changes the
Class property of the even PN (trace even) to “No Symmetry” for PNs driven by VPM.
When the user remove the symmetry relation between the even and odd part on VPM,
this action is reflected automatically on Windchill.
4
Visualize Symmetry
The user can see the Symmetric parts structure on Related Objects > Symmetric –
Specular Parts or Symmetric Principal Part.
- Symmetric - Specular Parts : The user can see the Symmetric Principal Part;
- Symmetric – Principal Part: The user can see the Symmetric Specular Part;
The User can access the Historic Symmetry part, trough customized window.
Select Customize in New Tab.
Select History > Configurable Revision Link History.
This moment the user may access history about symmetry part.
<Note> All structure is built on VPM and Transferred to Windchill.
5
Module Overview
In this module, you will learn how to manage lower level.
1
Objectives
• Engineering Requirements Process

• Visualize DSr
2
Engineering Requirements Process
The DS Req. (DSr) is differentiated by attributes Part Instance, thus can give identified as
Requirement Part, this attribute must be filled as REQ only.
To create a DS Req, the User have to be Designer role.
Product Engineering through, the user shall create a DS Req on VPM and transfer to
Windchill and SAP to generate ECODE, but in the Windchill will be show the Description
+ REQ.
Example:
English Description: DEV04 [REQ]
Portugueses Description: DEV04 [REQ]
The DSr have to be linked with other DS´s common, using Copy & Paste to build the
structure.
Once the structure has been created in VPM, the user can transfer the Part List to
Windchill.
The DSr, have to be create in T1-DS type.
<Note> The user can only break a DS, when the DS has “Engineering Control” attributes
has “NO” as value, if “YES” value, the user can not break it.
3
Visualize DSr
The user can see all DS Requirements structure, select the DSr > Requirements tab>
Requirement for table.
The User can access the DS Req by Creo View, allowing select all items, view each item in
the structure or individually.
In Creo View the user can apply some actions to get information and results of the DS
Req.
In this way the User can view the DS Req and children trough of their position in space.
The user can open two window on Creo View to see the Assembly or Single part
4
Module Overview
In this module, you will learn how to create AIC, link interior DSs to AIC DS,
collaborate AIC with non Embraer user, execute AIC search and report.
1
Objective
• Understand AIC concept

• Understand AIC Process
• Create AIC at VPM
• Understand AIC Container Strategy
• Create New AIC tab
• Link Interior DSs to AIC DS
• Collaborate AIC PN
• Create AIC Search
• Create AIC Reports
• Update Shared Information
• Remove shared information
• Understand the Abbreviations
2
Introduction to AIC
The AIC Process at Embraer consists of formalizing the interior configuration of

the aircraft by model/customer and/or serial number, for the purposes of
homologation with the certification authority ANAC, EASA, FAA.
In order for the aircraft to be certified and for each configured interior to be
approved by the certification authorities, a document with the information of the
aircraft is prepared and a smaller than 100mb 3D model is used in order for the
ANAC to view the document together with the 3D and its specifications and carry
out the approval and homologation of the aircraft.
3
4
AIC Creation Process
1 – Create Upper Level

Configuration Engineer creates the Upper Level (UL) object in Windchill below
the Master Data structure, fills all the requested attributes in Windchill and sets
Upper level object to status “Ready”;
The Upper Level (UL) with Status “Ready” will be transfer during the integration
process from Windchill to VPM.
2 – Create configuration Item

Configuration Engineer creates the Configuration Item (eBOM CI) object in
Windchill, fills all the requested attributes in Windchill, create link UL/CI and
Check In in the Upper Level object;
Configuration Engineer sets Configuration Item (eBOM CI) object to status
“Ready”;
The Configuration Item (eBOM CI) with Status “Ready” will be transferred during
the integration process from Windchill to VPM.
3 – Create AIC DS
Designer creates the AIC as eBOM Design Solution (DS) object and fill all the
5
requested attributes in VPM;
AIC name must be according to DSM chapter 12;
Drawing Class must be 212-AUX.DWG-LAYOUT;
Link the AIC Ds at AIC CI.
<Note> Link the AIC [eBOM Design Solution (DS)] with Configuration Item (CI)
collector with open effectivity;
3.1 – Create MBD

Designer creates one MBD for this configuration.
3.2 – Create AIC DS Eng Context

Designer creates the AIC DS Eng Context for each configuration.
Each installation of this configuration will have one respective CGR file.
The Designer shall collect these CGR files of the configuration under the AIC DS
Eng Context.
<Note> The Engineering Context is created at VPM. Although it may be a DS.

<Note> The Engineering Context have the same PN Name + Sulfix (Engcontext) and have
the same PN ecode.
<Note> It is only transferred to Windchill when is set to Pre-Released. At VPM the user
set the Pre Released at the PN and its contexts changes to Pre Released automatically.
<Note>Set eBOM Design Solution (DS) object to status "SAP Ready" in VPM after
link the CGR files.;
<Note> The eBOM Design Solution (DS) with Status "SAP Ready" will be
transferred during the integration process from VPM to WdC and from WdC to
SAP to get the ECODE;
<Note> Set the "Create or Update Links CI DS in Windchill“. The Configuration Item
will transfer the Part List during the integration process from VPM to WdC.
4 – Link Interior Installation to AIC DS

At Windchill the Embraer Designer must link the Interior installation to the AIC
Design Solution (DS).
<Note> AIC DS should be released by EO process.

<Note> The visualization of Installations will be available in the AIC DS using the
Creo View.
5
AIC Creation Process – Go Live Process
1 – Create Upper Level

Configuration Engineer creates the Upper Level (UL) object in Windchill below
the Master Data structure, fills all the requested attributes in Windchill and sets
Upper level object to status “Ready”;
The Upper Level (UL) with Status “Ready” will be transfer during the integration
process from Windchill to VPM.
2 – Create configuration Item

Configuration Engineer creates the Configuration Item (eBOM CI) object in
Windchill, fills all the requested attributes in Windchill, create link UL/CI and
Check In in the Upper Level object;
Configuration Engineer sets Configuration Item (eBOM CI) object to status
“Ready”;
The Configuration Item (eBOM CI) with Status “Ready” will be transferred during
the integration process from Windchill to VPM.
3 – Create AIC DS
Designer creates the AIC as eBOM Design Solution (DS) object and fill all the
6
requested attributes in VPM;
AIC name must be according to DSM chapter 12;
Drawing Class must be 212-AUX.DWG-LAYOUT;
Link the AIC DS at AIC CI.
The AIC DS must have a pdf and a 3Dxml file.
<Note> Link the AIC [eBOM Design Solution (DS)] with Configuration Item (CI)
collector with open effectivity;
4 – Link Interior Installation to AIC DS

At Windchill the Embraer Designer must link the Interior installation to the AIC
Design Solution (DS).
6
Create AIC at VPM
To learn the steps to create the AIC at VPM, follow the instructionsat IT-AIC.
In this document you will find the creation of ITs to define the AIC processes on
the VPM side.
<Note:> For AIC purposes its possible to use eBOM Design Solution types 1 or 7
(installation).
7
AIC Container Strategy
The UL for AIC are created at ERJ 190 Type container, at Upper Levels folder.
The CI for AIC are created at ERJ 190 Type container, at Configuration Item folder.
All DS and Parts created for AIC will be stored at 190G Master Data container, at AIC
folder.
8
Visualize AIC Engineering Context
The Context will not be visualized at Structure > Visualization tab.

To visualize the AIC DS and its context, the user must open the context at Creo View.
The Engineering Context Visualization will be available when the PN is at Pre Released
state.
Steps:
The Engineering Context must be opened at Creo View. Select the tab “Related Objects >
Engineering Context - Context Part” table;
Select the Engineering Context with the right button of the mouse and select “Open
Structure in Creo View”;
Load the Engineering Context visualization on Creo View.
9
Create New AIC tab
Embraer Designer must to link the Interior installation in the AIC Design Solution
(DS).
For that, at Windchill the user must create (only once) a new tab to make
available the AIC-Child and AIC-Parent tables.
Steps to create the new tab:

• Select New Tab;
• Select the New Tab with right button of the mouse and select Rename Tab;
• Rename the tab to AIC;
• Select Customize menu;
• Select Related Objects > AIC-Child;
• Select Related Objects > AIC-Parent;
<Note> These steps must be applied only once.
10
Link Interior DSs to AIC DS (1/2)
After creating the AIC tab, the Embraer Designer can search the Interior DSs to
copy and paste it at the AIC table.
To link the Interior DSs to AIC DS, the AIC DS must be at Ready or In Revision
State.
The user can apply filters at the structure to enable the necessary information,
but before it th euser can create a view with the relevant information to help
during the filter configuration.
Steps to create the view:

Select the Upper Level view information, for example;
Select the Structure tab;
If the Default View is selected you will see the Identity column;
To create a new view, select Views > Manage Structure Views;
At Customize View List dialog box, select New View;
Define a Name for the View and select the desired columns;
After complete the creation of the view, select Views > Your View;
You can see the columns added at the Structure tab.
11
At the example you can see the columns: Identity, Effectivity, Object Type, English
Description, Portuguese Description and Drawing Class.
With these options you can create a filter by effectivity or by customer's name (at
the English Description), for example.
11
Link Interior DSs to AIC DS (2/2)
1. After configuring the View, define the desired filter using the Edit Filter option.
Read the Create AIC Filter/Search to learn how to apply the filter (you can find
this information at this module).
2. You can fill the Find In Structure with the text eBOM design solution Type 1
(or Type 7);
Select Find All and Select to find all DSs and select them;
3. Select Copy;
4. Return to AIC DS view information;
Select the New AIC tab;
At AIC-Child table select Actions > Paste Selection;
You can see the DSs linked to the AIC DS.
12
Collaborate AIC PN – Option 1
Sharing one AIC Configuration by time.

You will learn how to share the AIC PN with Non Embraer Users.
The Embraer Designer can share the AIC PN with Non Embraer Users.
The Non Embraer User has a specific project container.

He will be able to consult only information that were selected to be shared with
him and will be able to manipulate models (CGR's) and MBD through Creo View.
Shared objects can only be read and downloaded; they cannot be checked out to
a workspace or modified within the project context.
Steps to Share Information:

As best practice, the AIC must be at Released state to be shared.
1. From an object information page, select Actions > Add to > Add to Project;
2. From the Add Objects to a Project window, click Find next to the Project
Name field to search for the target project;
3. Click Browse next to the Location field to specify a project subfolder in which
to add the objects. Otherwise, objects are shared to the main project folder;
4. If necessary, use the Collect Objects and Set Options to collect related objects
13
and specify the share types for each objects.
5. The Collect Related Configurable Revision Objects can be used to collect the DS
linked to AIC DS.
6. The Collect Related Documents can be used to collect the documents linked to
DS.
After sharing, the AIC Design Solution (DS) will keep on Master Data container
and Non Embraer User will have access to consult only on his container
environment.
<Note> User cannot share multiple iterations of the same AIC version.
13
Collaborate AIC PN - Option 2
Sharing multiple AIC Configurations by time.

You can share the AIC PN using other two options too:
1. Select one or more objects in the Folder Contents table and then
select Actions > Add to > Add to Project. You can also select Add to Project from
the right-click actions menu of an individual object.
2. Select one or more objects in the Search Results table and click the Add to
Project icon on the table toolbar.
14
Update and Remove Shared Information
The designer that have permission to share the AIC can update or remove it of
the Project.
The Designer can use the Update Project action to refresh the shared object.
1. At the project, select the PNs, select Actions > Update Project.
The shared object shall now reflect the latest version available in PDM.
When the project no longer needs to access the shared object information, the
designer performs the Remove Share action.
2. At the project, select the PNS, select Actions > Remove Share.
The object no longer appears in the project Folder Contents table.
15
Create AIC Filter / Search – Option 1
Filter by client’s name. This option is used to visualize the structure with the
Design Solution applied for a specific client.
Steps to consulting AIC by Client Configuration:

1. Select Edit Filter;
2. At Edit Filter dialog box, select Attribute Filter;
3. Select Add;
4. At Attribute Query Expression fill the Type as EBOM Design Solution;
Choose the English Description as Criteria an fill with the Client’s name;
5. Select OK;
6. At Edit Filter dialog box, select OK;
16
You can use the Search to find the Design Solution of a specific Client.
1. Navigate to Search -> Advanced Search and apply the following filter:
2. Type: EBOM Design Solution;
3. Context: All Contexts;
4. Criteria: English Description = *CLIENT NAME* (example *JETBLUE*);
17
Apply filter by Serial Number. This option is used to visualize the structure with
the specified effectivity number.
Consulting AIC by Basic Serial Number:

1. Select Edit Filter;
2. At Edit Filter dialog box, select Serial Number Filter;
3. Fill the Serial Number field;
4. Select OK;
18
Create AIC Reports (1/2)
The AIC reports are available to help the user to identify:

• for each AIC which installations were linked;
• configuration by client ( this information come from Description of the part);
• which installations that were linked in the AIC were revised after the link.
Steps to generate the report (Consulting Installation linked with AIC and
Consulting the update of installation after linked in the AIC):
1. Navigate to Reports area, under 190G - Master Data container;
2. Navigate to Engineering folder and open/view the "AIC Report“;
3. Select all columns and generate the report;
4. Report generated with described information for required columns.
The Delta field shows if the revision linked to AIC is the revision available or not.
When Revision Linked to AIC is NOT equal to Revision Available, then populate
with Yes. Else, populate Delta field with No.
Based on these results, the user can recreate the if needed.
19
Create AIC Reports (2/2)
5. After selecting Generate, at Results Table, you can export the result.
You can export the report results at many extensions, as:
• Pdf;
• Text;
• XLS;
• HTML.
Select Actions > Export List to File;

Select the desired extension.
20
Update the AIC DS links
After creating the link between the Interior DSs and AIC DS, the user must pay attention
in some updates information:
1 – The link created points to the selected revision, that is, if the Interior DS suffers a
new iteration, the iteration is updated at the AIC-Child table (for example A.1 to A.2).
But, if a new revision of the Interior DS is created, the new revision is not updated at the
AIC-Child table, the table will continue showing the previous revision.
2 – If the AIC DS is revised, the links will continue at the AIC-Child table.
21
Remove the old Revision and Add the New Revision of the DS
First, the user must create the AIC report to verify is there is a new revision on the DS.
If necessary, the user need to remove the old DS Revision of the AIC-Child table and add
the new DS Revision.
Steps to remove old revision and add the new revision:

1. At AIC-Child table, select the old revision and select Remove;
2. Select Add Existing to search the new DS Revision;
3. At Find Object, the user may select Latest at Revision field to facilitate the search;
4. Select the DS;
5. Select OK;
6. At AIC-Child table you can see the new revision of the DS added.
22
23
Module 11
Managing AIC

Exercise 1: Create Link between Interior DSs and AIC DS
Objectives
•Create the link between the Interior DSs and the AIC DS.
Scenario
In this exercise, you take the role of an Embraer Designer to create the link.
Initial Conditions
• Navigate to the 190G – Master Data container and starts on the AIC subfolder.
eBOM process.

Task 1: Save the data set
1. Select the 196E12345_YOURNAME DS with right button of the mouse and select Save As;
2. Fill the New Number field with “_your name” at the end. Select OK.
3. You can see the new DS created.

Task 2: Create the AIC New Tab
1. Log on as Embraer Designer. User: designer01 and Password: emb.

2. Select the View Information of the PN 196E12345_Your Name.
3. Select New Tab.
4. Select the New Tab with right button of the mouse and select Rename Tab.
5. Fill the Name field with AIC text. Select OK.

Task 3: Add the AIC-Child and AIC-Parent tables
1. At AIC tab, select Customize > Related Objects and select AIC-Child and AIC-Parent tables.
2. You can see the tables added.

Task 4: Open the Interior Structure
1. At the ERJ 190 Type container, select the Upper Levels > Engineering folders. Select the View
Information of the Upper Level AIC.
2. Select Structure tab.

3. Create a New View to visualize the Object Type field.
4. Select Views > Manage Structure Views.
5. Select New View.
6. Fill the Name field with AIC_Your Name. Select Next.

7. Add the following columns at the Selected Columns:
a. Identity;
b. Effectivity;
c. Object Type;
d. English Description.
8. Select Finish.
9. Select OK at the dialog box.
10. At Views, select the AIC_your name option.

11. You can see the View applied for the structure.

Task 5: Select the Interior DSs
1. At Find in Structure field write “ebom design solution type 1” and select Find All and Select.
2. You can see all the DS selected.
<Note> From the installation structure of the interiors, a filter by effectivity must be made that
represents the configuration of the AIC.
<Note> The filter should only select UL, CI and DS objects.
T1
3. Select any DS with right button of the mouse and select Copy.

Task 6: Paste the Interior DSs at AIC DS
1. Select the View Information of the AIC that you created before.
2. Select the AIC tab. At AIC-Child table, select Actions > Paste.
3. You can see the DSs added at the table.

Exercise 2: Share the AIC DS with Non Embraer User
Objectives
• Share the AIC DS with Non Embraer users.
Scenario
In this exercise, you take the role of an Embraer Designer to share the information.
Initial Conditions
• Complete the previous exercise.
eBOM process.

Task 1: Set the AIC state to release.
1. As best practice, the AIC must be at Released state to be shared. Select the AIC that you
created before with right button of the mouse and select Set State.
2. At Target State, select Released option.

3. Select OK.
4. You can see the DS released.

Task 2: Add the AIC to project
1. Log on as Embraer Designer. User: designer01 and Password: emb.

2. Select the 196E12345_Your Name with right button of the mouse and select Add To > Add To
Project.
3. At the Add Objects to a Project dialog box, select Find.
4. Search the Project 190G Interface Context for ANAC EASA FAA.
5. Select the Project and select OK.

6. At Add Objects to a Project dialog box, select Next.
7. Select the DS and select Collect Objects and Set Options to collect related DSs.

8. You can see all the DSs collected.
9. Select Finish.
10. You can see the message Objects successfully shared to project 190G Interface Context
for ANAC EASA FAA. Select OK.
11. Navigate to the Container 190G Interface Context for ANAC EASA FAA.
12. Select Folders.
13. You can see the AIC DS shared.

Exercise 3: Remove shared information
Objectives
• Remove the AIC DS shared.
Scenario
In this exercise, you take the role of an Embraer Designer to remove the shared information.
Initial Conditions
• Complete the previous exercises.
• Navigate to the 190G Interface Context for ANAC EASA FAA container and starts on the Folders.
eBOM process.

Task 1: Select the Project and remove the AIC DS
1. Select the DSs that you shared before (exercise 2).
2. Select Actions > Remove Share.
3. The DSs are removed from the project.

Exercise 4: Execute the search
Objectives
• Execute the AIC search.
Scenario
In this exercise, you take the role of an Embraer Designer to execute a search.
Initial Conditions
eBOM process.

Task 1: Search for the client’s DSs
1. Select Search tab > Advanced Search.

2. Fill the Type as EBOM Design Solution T1.
3. Fill Context as All Context.
4. Fill the Criteria:
5. Select English Description.
6. At this filed fill with the Client’s name (example: * jetblue*).
7. Select Search.
8. At Search Results, you can see all the DS of the client.

Exercise 5: Execute the AIC Reports
Objectives
• Create the AIC reports.
Scenario
In this exercise, you take the role of an Embraer Designer to create the report.
Initial Conditions
• Navigate to the 190G – Master Data container and starts on the Reports.
eBOM process.

Task 1: Select the Report option.
1. Select the Reports option of the 190G-Master Data container.
2. Select Engineering option.

3. Select AIC report.
4. Select all options and select Generate.

6. Select Actions > Export List to File > Export List to PDF to generate the pdf file from the
results table.

Module Overview
In this module, you will learn how to create the engineering context.
1
Objectives
• Create Engineering Context

• Edit Engineering Context
• Open Engineering Context in Creo View
• Cancel and Delete Engineering Context
2
Introduction to Engineering Context
What is Context?
• Work Context: live setting and adjacent to the product in question is necessary to
achieve the collaborative development of engineering in the light of the interfaces
'inter' and 'intra' technologies. Mingles with the very definition of DMU (digital
mock-up).
• Release Context: reference needed to "sense" the frozen product users-customers
will consume or consult downstream.
At this training you will learn how to work with Release Context.
3
Create and Edit Engineering Context
The Designer, Sub Contract Designer and Partner can create the Engineering Context.
The Engineering Context is created at VPM as type T1, T2, T6 or DS. Although it may be a
DS, will not be applied the effectivity.
The Engineering Context have the same PN Name + Sulfix (Engcontext) and have the
same PN ecode.
It is only transferred to Windchill when is set to Pre-Released. At VPM the user set the
Pre Released at the PN and its contexts changes to Pre Released automatically.
At Windchill the Engineering Context, regardless of the type chosen in VPM, is always a
Part with soft type eBOM Context.
The link between the PN and the Engineering Context is created automatically and is
stored at Windchill at “Related Objects” tab > “Engineering Context” table.
The Engineering Context is stored at Context folder of the Master Data Container.
For Partners, the engineering Context is stored at Context folder of the Partners
Containers.
The Engineering Context can only be edited at VPM by the creator before the Pre
Released maturity.
4
Open Engineering Context in Creo View
The Context will not be visualized at Structure > Visualization tab.

To visualize the PN and its context, the user must open the PN and the context at Creo
View.
Steps:
At Main Part select “Open Structure in Creo View”;
After open the PN at Creo View, the Engineering Context must be opened too. Select the
tab “Related Objects > Engineering Context - Context Part” table;
Select the Engineering Context with the right button of the mouse and select “Open
Structure in Creo View”;
At the dialog box, select “Add to Current Session”;
Open as many Engineering Context as needed;
Load the Engineering Context visualization on Creo View.
5
Cancel and Delete Engineering Context
Only the Administrator can cancel or delete the engcontext.

First, at Windchill is necessary remove the link between the engcontext and the PN at
table Related Objects.
Steps:
Searches for the main part in Windchill;
Select “Related Objects” tab;
At “Engineering Context - Context Part” table select the Engineering Context and select
“Remove Selected”.
After remove the link, the Admin can remove or delete the Engineering Context only at
VPM.
6
Module 12
Engineering Context

Exercise 1: Open Engineering Context in Creo View
Objectives
• Visualize the PN and its contexts at Creo View.
Scenario
In this exercise, you take the role of a Designer to visualize the PN and its contexts.
Initial Conditions
• Navigate to the 190G - System Installation container and starts on the Parts subfolder.
eBOM process.

Task 1: Open the Main Part
1. Select the View Information of the PN 198-74630-403.
2. Select Actions > Open Structure in Creo View.
3. You can visualize the PN at Creo View.

Task 2: Open the engineering context
1. Do not close the Creo View. Back to Windchill to open the context.
2. Select the tab Related Objects of the PN 198-74630-403.
3. At Engineering Context - Context Part table, select the 198-74630-403_ENGCONTEXT with
the right button of the mouse and select Open Structure in Creo View.
4. Select Add to Current Session.
5. The Context is loaded at Creo View. Select the check box to load the visualization of the context.

Module Overview
In this module, you will learn how to manage eBOM Notes at Windchill.
1
Objectives
• Technical Notes Visualization

• Compare Technical Notes in different PN Version
2
Technical Notes Visualization
At Embraer all the notes are created, linked and updated at VPM. They are only
published from VPM to Windchill.
The Technical Notes may be Item Notes (NI), Pattern Notes (NP) or Free Notes (NL).
To visualize the Technical Notes the user must access the Part or DS “View Information”
page and the “Embraer Table” tab.
The UL and CI does not have Technical Notes added. The Technical Notes must be at DS
and Lower Level PNs.
The edition of Drawing Notes Description or Item Notes Description is forbidden to
avoid the cascade difference of information from eBOM to mBOM.
To update note information:

At VPM, user edit the notes NI or NL.
This Part List must be exported to Windchill.
A new iteration is created at Windchill.
It shall not be possible to add/remove notes in the Part Locked states (RELEASED,
PRE_RELEASED, etc), for eBOM and mBOM parts.
3
Compare Technical Notes in different PN Version
Comparing the PN Information, the user may compare the Technical Notes.
At “History” tab, select the two PNs versions to compare and select “Compare
Information”.
At “Comparison Options” dialog box, select “Related Documents” and OK.
The “Comparison Report” dialog box opens and the user may compare the Technical
Notes.
4
Module 13
eBOM Technical Notes

Exercise 1: Compare eBOM Technical Notes
Objectives
• Compare the Technical Notes at the different eBOM PN version.
Scenario
In this exercise, you take the role of a Designer to compare the eBOM notes.
Initial Conditions
• Navigate to the 190G - Forward Fuselage, Embraer container and starts on the Folders > Parts
folder page.
eBOM process.

Task 1: Compare Information
1. Select the View Information of the 197-96002-001 PN.
2. Select History tab.

3. Select the latest and the oldest version.
4. Select Compare Information.
5. At Comparison Options, select Attributes and Related Documents.

6. Select OK.

7. At Comparison Report you can see the attributes and the documents (technical notes) of the
older version and of the new version.
8. Select Close.

Module Overview
In this module, you learn how to create effectivity.
1
Objectives

• Set Effectivity (Basic, Model and Customer)
• Create New Change Directive
• Generate Change Actions
• Update Effectivity (Edit, Undo Fulfill, No Solution Needed)
• Effectivity: Where Used Tab
• Effectivity: History Tab
• Effectivity Historic
• Effectivity Report
2
Set Effectivity
Effectivity refers to the ability to define valid configurations based on requirements.
The product structure in Windchill consists of all parts needed to define all available configurations of the product.
This means that there are more components in the structure than is needed to create the product. In order to display
one specific configuration the product structure is configured with serial number effectively information. This enables
the structure to be filtered based on a range or a specific serial number. This configuration relies on specific types of
relations between Windchill Parts.
All the DS and Parts are created at VPM. The link between the DS and CI are created at VPM too.
After created the link between the DS and CI the user may define the effectivity at Windchill.
The effectivity may be Basic, Model or Customer.
To create the effectivity is needed to create a Change Directive and after a Change Action.
- Change Directive:
Represents an intention of product structure configuration based on a change made at
the Configuration Level.
The user define the effectivity and associate the CI with it.
- Change Action:
Represents a statement of work required to address a Change Directive.
The user associate the DS with the effectivity.
The effectivity may be transferred to SAP in 2 ways:
- When the CI-DS have an effectivity and are released.
- When the CI have an effectivity and it´s transferred to SAP by transfer ready.
Whenever CD created is of type Basic Effectivity:

• Basic Effectivity is sent to SAP.
Whenever CD created is of type Model/Customer Effectivity:
• Model/Cust effectivity is sent to SAP when all CAs in one same CD are resolved by the same DS.
• When Model/Cust Effectivity is sent to SAP, attribute ReCalculation Needed is flagged as 'No‘.
• Real Effectivity is sent to SAP when NOT all CAs in one same CD are resolved by the same DS.
• When Real Effectivity is sent to SAP, attribute ReCalculation Needed is flagged as 'Yes‘.
If this attributes is set YES the CI need to be recalculated.
The user can use the Advanced Search to search for CIs that need to be recalculated. For that the user can use the
attribute ReCalculation Needed.
3
Create New Change Directive (1/3)
The users assigned to “Embraer Configuration Control” roles can create Change Directive.
For eBOM, all the Change Directive are created at “ERJ 190 Type” container.
At the folder “Changes”, select the “New Change Directive” function.
At the first tab “Set Attributes” fill the fields “Type", "Effectivity”, “Need Date” and “Description”.
• For Basic Effectivity:
Type: is the type of the effectivity. ED 0190 is the Basic Effectivity.
Effectivity: is the range of the effectivity, e.g. 20001-99999. Is the Aircraft Serial Number sequence, for E2
starts with 20001.
Need Date: agreed date to apply the effectivity.
Description: is the effectivity description.
• For Model/Customer Effectivity:

The Model / Customer effectivity, for mBOM, can be applied for all CI’s and DS’s.
Type: is the type of the effectivity. ED 0190 Model/Customer is the Model or Customer Effectivity.
Model: model code and serial number.
The model effectivity range (MD__ 20001/99800) must follow the Aircraft
Serial Number sequence.
More than one model effectivity can be set on eBOM CI-DS link and mBOM
CIt8-DSt7 link.
The Customer effectivity range (__ CL 00001/99999) must follow the Customer
Serial Number sequence.
More than one customer effectivity can be set on eBOM CI-DS link and mBOM
CIt8-DSt7 link.
Customer: customer code and serial number.
Need Date: agreed date to apply the effectivity.
Description: is the effectivity description.
Select “Next” to add the related CI.
<Note> For Ipanema project, read the “CT3443 – Ipanema Deck of Slides” and the “CT3937-QRC for Ipanema”
materials to learn specific Ipanema process and functions.
4
At the second tab “Associate Configuration Item” select the CI that will be related to this
CD.
At “Configurations Items” table, select “Add Configuration Items”.
At “Find Configurations Items” do a search for the CI. Select the CI and select “Ok”.
At “Associate Configuration Item” tab select “Finish”.
Different CIs may be linked at the same CD.
You can see the Change Directive created inside the folder “Change”.
The Change Directive is created with in “In Work” state.
<Note> Once the “CI” is configured as “Basic Type”, to be configured as

“Model/Customer” only re-identification CI.
5
The user must validate the Change Directive changing the state from “In Work” to
“Implementation”.
Inside the “View Information” of the Change Directive, select “Actions” and “Set State”.
The Set State dialog box opens. Select “Implementation” and “Ok”.
You can see the new state at the “View Information” page.
The Change Directive must be released from a release process (BR, BRS, EO).
6
Generate Change Actions (1/2)
The users assigned to “Embraer Configuration Control” roles can create Change Actions.
After changing the state at the Change Directive, the user must create the Change
Action.
Inside the “Details” tab of the Change Directive, in the “Configuration Items” table,
select the CI with the right button of the mouse. Select the “Generate Change Actions”.
Selecting “Generate Change Action”, the Model and Custom effectivity is calculated
based on PIPO.
After creating the Change Action, it is necessary to define all the DS that will be part of
this effectivity.
For that, select the Change Action with the right button of the mouse and select “Fulfill
Change Action”. This function apply the effectivity at the Windchill structure.
When applying the “Fulfill Change Action” the effectivity is transferred to VPM.
At eBOM the “Fulfill Change Action” must be applied before release the PN.
To apply the reconciliation between the eBOM and mBOM is necessary have the
effectivity with the “Fulfill change Action” applied at eBOM.
<Note> If the Configuration Item (CI) is in “Checked Out”, the user will not be able to
create a Change Actions. To be able to create the Change Action the user must apply the
“Check In” at the Configuration Item.
<Note> The system can create one or more CA (Change Action) per CI.
7
<Note> If the Fulfill is not available, check if CI is locked for CN associated to the CD
7
Generate Change Actions (2/2)
A “Fulfill Change Action” dialog box opens. Select the desired DS and select “Ok”.
Inside the “Related Object” tab, at “Design Solutions” table you can see the DS with the
related effectivity.
The user can see this information inside the “Structure” too, at the “Uses” tab.
“Related Object” tab, at “Design Solutions” table you can see the DS with the related
effectivity.
Sometimes the change actions provide complementary ranges of effectiveness, so the

same DS may be related to more than one Change Action.
8
Use ReCalculation Needed attribute
Just the model and customer effectivities are sent to SAP.

The real effectivity is transferred to SAP just in one specific case: when a CD have 2 CAs
(Change Action) for the same CI and the CAs point to different DSs or different solutions
(example: No Solution Needed , Rejected….).
The real effectivity is sent to SAP and the attribute ReCalculation Needed is set YES.
The user can use the Advanced Search to search for CIs that need to be recalculated.
For that the user can use the attribute ReCalculation Needed. If this attributes is set YES
the CI need to be recalculated.
<Note> Read the module “Managing Effectivity at eBOM” to learn how to

schedule/execute the Recalculation.
The ReCalculation Needed is available for eBOM CI, mBOM T1 CI, mBOM T8 CI and
sBOM CI.
9
Update Effectivity (Edit, Undo Fulfill, No Solution Needed)
The “Configuration Control” may edit the Change Directive:
Edit:
The user may update the Change Directive if it is “In Work” state applying the Edit option.
Select the Change Directive with the right button of the mouse and select Edit.
The user may change the attributes and the associated CI.
If the Change Directive was in “Implementation” state, the user must set the state to “In Work”
and after that select the “Edit” option.
Undo Fulfill:
The user may apply the Undo Fulfill at the Change Action if the Change Directive is in
“Implementation” state.
Select the Change Action with the right button of the mouse and select “Undo Fulfill Change
Action”.
The Undo Fulfill remove the calculation and the selected DS.
The user can apply the Fulfill again to calculate the effectivity and to select the correct DS.
Modify Change Action Status > No Solution Needed:

This status is used to establish that the defined effectivity at Change Directive do not have any
DS as solution.
Select the change Action with the right button of the mouse and select “Modify Change Action
Status”.
At “Modify Change Action Status” dialog box, define the “Available Status” as “No Solution
Needed”.
<Note> The “Fulfill Change Action”, “Undo Fulfill” and “Modify Change Action Status” options
can be found at Changes tab of the PN or at Configuration Items tab of the Change Directive (ED)
10
and in the Change Action as well.
10
Effectivity Where Used Tab
To visualize the Effectivity at “Where Used” tab, the user must select the “View
Information” of the DS or CI and select “Where Used” tab.
At this tab, at “Where Used” table, select “Latest Configuration”.
This option shows the applied Effectivity at CI-DS.
“Where Used” shall identify which effectivity belongs to each CI-DS link, once the same
DS can be linked in more than one CI and the user can see the link between CI-DS.
When DS has more than one CI associated the effectivity shows only one, but the
Effectivity must be displayed for each CI on DS line.
The CI can have one or more DS associated and the DS can have one or more CI
associated.
The “ Effectivity Type” attribute value will be displayed at the CI line, as: Model,
Optional and Basic.
Where Use should be accessed by all users.
11
Effectivity: History tab
When a CI is released, at CI History tab, the user can see the CN / CA / SAP Rev. Letter /
SAP Doc Nr.
12
Effectivity Historic
All users can visualize the Effectivity Log at the CI “View Information” page.
At the CI page, select “Actions> View Effectivity Log”.
The View Effectivity Log dialog box open with all the effectivity historic.
13
Effectivity Report
All users can create a report to display the eBOM CI-DS links with theirs specific effectivity
(Windchill calculated effectivity).
• eBOM Report Attributes:

UL Number
CI Number
CI ”bas/mod/cli flag attribute”
CEMB CI
DS Number
CEMB DS
DS State
DS description
Program
calculated effectivities (effinicial, eff final)
T: type
O: origin
P: production
D: design
DBT
To create the report, inside the “Product” container, the user is going to the “Report” page.
Select the “+” symbol of the “Reports for CI-DS link effectivity”.
Select eBOM CI-DS Report.
Select the desired fields and select “Generate’.
After the report have been generated, it is possible to export the data
14
Module 14
Creating and Managing Effectivity in an
eBOM

Exercise 1: Create Effectivity Basic
Objectives
• Create Change Directive
• Associate CI to Change Directive
• Create Change Action
• Associate DS to effectivity
Scenario
In this exercise, you take the role of a Configuration Control to create basic effectivity.
Initial Conditions
eBOM process.

Task 1: Prepare the data set - save the CI and DS with your name.
1. Inside the Folder select with the right button the CI 197-96066-800.
2. Select Save As
3. At Common space Save AS dialog box, select the CI and select Dependents > All.
4. Select all the PNs as the image.

5. Select Remove selected Objects. Only the CI and the DS will not be selected.
6. Select OK.

7. At Common space Save AS dialog box, fill the Number Filed.
New Number:
CI: 197-96066-800_effectivity_YourName
DS: 197-96066-401_effectivity_YourName
Select OK.

Task 2: Create New Change Directive.
1. Log on using “confcontrol01” user and password “emb”. Inside ERJ 190 Type container, at
Changes folder select the New Change Directive function.
2. Select Type and choose “ED 0190” to create a Basic Effectivity. Define the Effectivity with
20001-20020 and select Next to associate the CIs. (Description is optional)
3. Select Add Configuration Items.

4. Search for the CI (197-96066-800_effectivity_YourName).
5. Select the CI. Select OK.
6. Click Finish to create the Change Directive.
7. At Changes folder, select with the right button of the mouse the Change Directive that you created.
8. Select Set State and change the state to Implementation.
Task 3: Create New Change Action.

1. Select the View Information icon of the Change Directive that you created.
2. At the Details tab, inside the Configuration Items table, select with the third button of the mouse the
CI (197-96066-800_effectivity_YourName) and select the Generate Change Actions option.
Note: For the purpose of completing the exercise, we will apply the Generate Change Action,
but in the production environment, the Configuration Control will receive a task, allowing
application of the change Generate Action.
3. The View Information page of the CI opens. At the Changes tab, inside the ED E2-190 table,
Select with the third button of the mouse the Change Action and select Fulfill Change Action
option.

4. At the Fulfill Change Action dialog box, select the DS (197-96066-401-Effectivity_YourName).
5. Select Ok.
6. Access the CI (197-96066-800_effectivity_YourName) and select the Structure tab. You can see
the effectivity applied at the DS.

Exercise 2: Create Effectivity Customer
Objectives
• Create Change Directive
• Associate CI to Change Directive
• Create Change Action
• Associate DS to effectivity
Scenario
In this exercise, you take the role of a Configuration Control to create customer effectivity.
Initial Conditions
eBOM process.

Task 1: Prepare the data set - save the CI and DS with your name
1. Inside the Folder select with the right button the CI 197-96066-800.
2. Select Save As
3. At Common space Save AS dialog box, select the CI and select Dependents > All.
4. Select all the PNs as the image.

5. Select Remove selected Objects. Only the CI and the DS will not be selected.
6. Select OK.
7. At Common space Save AS dialog box, fill the Number Filed.

New Number:
CI: 197-96066-800_effectivity_YourName_02

DS: 197-96066-401_effectivity_YourName_02
Select OK.

Task 2: Create New Change Directive.
1. Log on using confcontrol01 user and password emb. Inside ERJ 190 Type container, at Changes
folder select the New Change Directive function.
2. Select Type and choose “ED 0190 Model/Customer” to create a Model/Customer Effectivity.
3. Define the Effectivity Model/Customer ES – EY with 20001-99999.
4. Select Next to associate the CIs. (Description is optional)

5. Select Add Configuration Items to add CI.
6. Search for the CI (197-96066-800_effectivity_YourName_2).

7. Select the CI.
8. Select OK

9. Select Finish.
10. At Changes folder, select with the right button of the mouse the Change Directive that you created.
11. Select Set State and change the state to Implementation.
12. Select OK

Task 3: Create New Change Action.
1. Select the View Information icon of the Change Directive that you created.
2. At the Details tab, inside the Configuration Items table, select with the third button of the mouse
the CI (197-96066-800_effectivity_YourName_02) and select the Generate Change Actions option.
Note: For the purpose of completing the exercise, we will apply the Generate Change Action,
but in the production environment, the Configuration Control will receive a task, allowing
application of the change Generate Action.
3. The View Information page of the CI opens. At the Changes tab, inside the ED E2-190 table,
Select with the third button of the mouse the Change Action and select Fulfill Change Action option.

4. At the Fulfill Change Action dialog box, select the DS (197-96000-401_Effectivity_YourName_02).
5. Select Ok.
6. Access the CI (197-96066-800_effectivity_YourName_02) and select the Structure tab.

You can see the effectivity applied at the DS.
The real serial number depends on the integration with PIPO. This integration has a scheduled
routine to recalculate the effectivity automatically. This will not be simulated.

Exercise 3: Editing Effectivity
Objectives
• Edit the Change Action
Scenario
In this exercise, the DS was released for the airplane for the effectivity range 20020-99999. The
engineer defined that this DS will not be used from the range 20051 following.
You take the role of a Configuration Control to apply the Undo Fulfill Change Action and No Solution
Needed at the Change Action.
Initial Conditions
eBOM process.

Task 1: Apply Undo Fulfill
1. Select the View Information of the CI 197-96066-800_EFFECTIVITY_YOURNAME.
2. Select Changes tab.
3. Select with the right button the Change Action that you applied the Effectivity 20001-99999.
4. Select OK to confirm the action in dialog box.

5. You can see the Status changes to “To be studied”.

Task 2: Apply No Solution Needed
1. Select with the right button the same Change Action

2. Select Modify Change Action Status.
3. At Modify Change Action Status dialog box, select No solution needed.
4. Select OK.
5. You can see the Status changes to “No solution needed”.

Exercise 4: Search for CI using Recalculation Needed
Objectives
• Search the CI that need to be recalculated.
Scenario
In this exercise, you take the role of a Configuration Control to search the CI.
Initial Conditions
• Log on to Windchill using “confeng01” user and password “emb”.
• Navigate to the Search tab.
eBOM process.

Task 1: Search the CIs
1. Select Search tab > Advanced Search.

2. Configure the Search as the image below:
a. Type:
i. Select eBOM CI, mBOM T1 CI, mBOM T8 CI and sBOM CI.
b. Context:
i. Select All Context
c. Criteria:
i. ReCalculation Needed = Yes
d. Select Search.
3. You can see the result at Search Result Table.

Module Overview
In this module, you learn how to manage the effectivity.
1
Objectives

• Understand PIPO Table and Recalculate Automatic
• Understand Manual Effectivity Recalculation Process
• Schedule / Execute the Recalculation
2
PIPO Table and Recalculate Automatic (1/3)
PIPO: It is an environment where for each serial number of the aircraft it defines which
model and which customer it will attend.
Integration Environment: Integration mechanism to be developed and convert PIPO to

AAT xml format (Aircraft Allocation Table) in Windchill server.
<Note> The real serial number depends on the integration with PIPO.
This integration has a scheduled routine to recalculate the effectivity
automatically.
3
This process are built in Change Directive, where set effectivity of the Aircraft Model and
Customer.
Code Model: Standard values will define the Models created in “New Change Directive”
(Ex: ES, ET, SV)
Code Customer: Version values will define the Customers created in “New Change
Directive” (Ex: EW, EY, EZ, CB, JB, FY)
Initial PIPO: Initial configuration of PIPO, whehe is possible see information to calculate
the real effectivity.
<Note> The Customer Serial Number (CNS) is the sequential serial number of a given
customer's aircraft.
4
Premise for Recalculation:

- All “CIs” should “NOT” be Check-out, If there “CIs” Check-out the operation
recalculation is not applied.
After the Recalculation:

The Configuration Control team receives report by email Windchill system with the
following information:
- List of CI Re-calculated, Failed and Canceled.
- Status upgrades from “OPEN PDM” with the links to “VPM” with the “LOG”.
- Status upgrades from “OPEN PDM” with links to “SAP” system with the “LOG”.
5
Effectivity Recalculation Schedule Process
The user owing the role “Embraer Configuration Recalc” has the permission to execute
this process.
6
Schedule / Execute the Recalculation (1/4)
The Embraer Configuration Recalc is the responsible to schedule and execute the
Recalculation.
Before execute the recalculation, the PIPO table must be already updated in SAP and all
CIs that require Recalculation must be checked-in.
The recalculation runs for all CIs configured by model or customer effectivity, if it is
necessary to run the recalculation for a group of CIs the user must generate a list with
those CIs.
Steps to search and copy the CIs:

Prepare a list of CIs that need ReCalculation, making sure the CIs are separated by
delimiter ";"
Navigate to Windchill and search the CIs. To facilitate the search, the user can use the
advanced search and define the necessary filters.
Execute the Search;
Select all CIs returned in Search -> Actions -> Copy.
7
A Problem Report must be used to create a new Effectivity Recalculation.

The Embraer Configuration Recalc must navigate to container where CIs are usually created for a
program (ex: ERJ 190 Type / 203 - Ipanema Upper Levels);
The Problem Report is stored at Changes > Problem Report folder.
To create a Problem Report, in container, navigate to Actions -> New -> New Problem Report.
In 'Set Attributes' section select Type: Effectivity ReCalculation, fulfill following attributes and
select next:
Name: Provide a Name
Description: Provide a Description for Effectivity ReCalculation.
Run Options:
1 - Update AAT from PIPO and Run ReCalc: Windchill connect to SAP and verify if
there is any changes at PIPO. If yes, the AAT table is updated at Windchill. After updating
the AAT table the recalculation starts and the CIs are updated with the AAT information.
2 - Run ReCalc: if the AAT table is already updated at Windchill, the user can just
run the recalculation. The CIs are updated with AAT information.
3 - Update AAT from PIPO: Windchill connect to SAP and verify if there is any
changes at PIPO. If yes, the AAT table is updated at Windchill.
Aircraft Type: Pre-Populated with Aircraft Type value inherited from container.
Program Code: Pre-Populated with Program Code value inherited from container.
Scheduled Time: Define a Time.
<Note> The CIs configured by CDs with Basic Effectivity type are excluded from Recalculation.
8
Optional Steps:
In 'Select Affected Objects' section paste all CIs previously copied (when user wishes to execute
effectivity recalculation for a list of CIs);
In 'Select Associations' section add an existing Effectivity Recalculation Problem Report (when
user wishes to link the new recalculation to a previous recalculation).
Select Finish to submit the Effectivity ReCalculation Problem Report.
9
The Effectivity Recalculation Problem Report is created at Open state.

Users in Role Embraer Effectivity Recalc receive an email informing that a new Effectivity
ReCalculation has been scheduled.
Effectivity ReCalculation state changed to 'In Work'.
When starting execution, Effectivity ReCalculation state changed to 'In Progress'.
When executed, Effectivity ReCalculation state changed to ‘Closed' or 'Failed'.
Effectivity ReCalculation logs are available in section 'Attachments'.
10
Module 15
Managing Effectivity at eBOM

Exercise 1: Schedule the recalculation
Objectives
• Schedule the recalculation.
Scenario
In this exercise, you take the role of an Embraer Configuration Recalc to create a problem report.
Initial Conditions
• Complete the exercise 01: Create Effectivity Basic from Creating Effectivity at eBOM module.
• Log on to Windchill using “confeng01” user and password “emb”.
eBOM process.

Task 1: Search the CI.
1. At Search tab, select Advanced Search.
2. Select EBOM Configuration Item at TYPE.

3. At Context, select All Context.
4. At Criteria, select Name and fill this field with the CI name that you created on exercise 01: Create
Effectivity Basic from Creating Effectivity at eBOM module.
(197-96066-800_EFFECTIVITY_YOURNAME).
5. Select Search.

6. At Search Results table, select the CI check box and select Copy.

Task 2: Create a Problem Report.
1. Navigate to ERJ 190 Type container, select Folders >Changes > Problem Report Folder.

2. Select Actions > New > New Problem Report.

a. Type: Effectivity ReCalculation
b. Name: Recalc 197-96066-800_EFFECTIVITY_YOURNAME
c. Description: recalculate the CI
d. Run Options: Update AAT from PIPO and Run ReCalc
e. Scheduled Date Time: tomorrow’s date.
4. Select Next.

5. At Set Security Labels, select Next.
6. At Select Affected End Items, select Next.
7. At Select Affected Objects, select Actions> Paste of Affected Objects table.

8. You can see the CI added. Select Finish.
9. The Effectivity Recalculation Problem Report is created at Open state.

10. Select View Information of your Problem Report (Recalc
197-96066-800_EFFECTIVITY_YOURNAME).
11. At Details tab, Effectivity ReCalculation logs are available in Attachments table.
<Notes> User receive an email informing that a new Effectivity ReCalculation has been scheduled.
Effectivity ReCalculation state changed to In Work.
When starting execution, Effectivity ReCalculation state changed to In Progress.
When executed, Effectivity ReCalculation state changed to Closed.

Module Overview
In this module, you learn how generate and consulting the Multi BOM reports.
1
Objectives
• Configure Reports
• Verify the Available Reports
2
Configure Reports
The Admin can schedule the Reports.

To configure the scheduler go to “Organization -> Embraer -> Utilities -> WVS Job
Scheduler Administration”.
At Schedule Job dialog box define:

Name: name of the Report;
Description: description of the report;
Job Type: Publish Job;
Job: choose the Report Type;
Start Job: define the date to start the Report creation;
Job frequency: define the frequency of the Report creation;
Select “Schedule”.
The Report routine will start and each report will be available on its defined folder.
The generated Report is in CSV format.
3
Available Reports
The user can visualize the following reports:

1. Equivalence Link
2. DPE Published Items
3. Part Info (MARA)
4. Drawing Info (DrawDrap)
5. Change Notice Part (PN Afetado)
6. Change Notice Info (Changes Basic Info)
7. Change Activity Approval (List of Change Activities Approval)
8. BOM (estr_engen)
9. Part Notes (NOTASDES)
10. EO Info (ZDPRNT006)
11. Multi-Level BOM (zdprpl014)
12. Change Notice Approval (List of Change Notices Approval)
13. Context Report
4
Report Path
The report will be saved in folder \\plmnfspre.sjk.emb\wdc_export\PRD (on Embraer

network).
5
1. Equivalence Link
The report file name is EquivalenceLinkReport.csv
6
2. DPE Published Items
The report file name is DPEPublishedItemsReport.csv
7
3. Part Info (MARA)
The report file name is PartInfoReport.csv
8
4. Drawing Info (DrawDrap)
The report file name is DrawingInfoReport.csv
9
5. Change Notice Part (PN Afetado)
The report file name is ChangeNoticePartReport.csv
10
6. Change Notice Info (Changes Basic Info)
The report file name is ChangeNoticeInfoReport.csv
11
7. Change Activity Approval (List of Change Activities Approval)
The report file name is ChangeActivityApprovalReport.csv
12
8. BOM (estr_engen)
The report file name is BOMReport.csv
13
9. Part Notes – Item (NOTASDES) (1/2)
The report file name are:

1. PartItemNotesReport.csv
2. PartGeneralNotesReport
14
9. Part Notes – General (NOTASDES) (2/2)
The report file name are:

1. PartItemNotesReport.csv
2. PartGeneralNotesReport
15
10. EO Info (ZDPRNT006) (1/6)
The reports file name are:

1. EngineeringOrderBasicInfoReport.csv
2. EngineeringOrderResultPartsReport.csv
3. EngineeringOrderAffectedItemsReport.csv
4. EngineeringOrderLifeCycleHistoryReport.csv
5. EngineeringOrderCommentReport.csv
6. EngineeringOrderAssociatedItemsReport.csv
16

17

18

19
10. EOInfoWDC (ZDPRNT006) (5/6)

20

21
11. Multi-Level BOM (zdprpl014)
The report file name is MultiLevelBOMReport.csv
22
12. Change Notice Approval (List of Change Notices Approval)
The report file name is ChangeNoticeApprovalReport.csv
23
13. Context Report
The report file name is contextPartReports.csv
24
Module Overview
In this module, you learn the Windchill / MultiBOM terminology.
1
2
3
4
5
6
7

CT3158 PDF EBOM Product Structure Management for Creators Rev An

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CT3158 PDF EBOM Product Structure Management for Creators Rev An

Uploaded by

Copyright:

Available Formats

1

After completing this module, you will be able to:

After completing this module, you will be able to:

To generate the product we have to go through several phases:

The picture above shows the overview of all eBOM/mBOM process.

5 – All the RME Parts are created at SAP.

Manufactured materials are identified as part types 1, 2, 6, 7 and 8. Each type

Types of manufactured materials:

• Type 1 - Assembly / Subassembly: Material resulting from two or more pieces

• Type 6 - Partner Kit: It is a collector of not assembled parts from partners.

• Type 7 - Configuration Item / Installation Design Solution: Functional element of the

• Type 8 - Upper level: Top collector.

Types of Purchased Materials:

• Type 3 - Raw materials: Materials supplied by external manufacturers that require

• Type 4 – Mechanical Hardware: Mechanical Hardware are finished materials, which

• Type 5 – Equipment: Materials supplied by external manufacturers for specific

• Type 9 - Electric Hardware : Materials supplied by external manufacturers with

Naming rule for DS and Lower Level (Prefix 196):

See the drawing number ranges (Prefix 196) on table above.

Naming rule for DS and Lower Level (Prefix 197):

See the drawing number ranges (Prefix 197) on table above.

Naming rule for DS and Lower Level (Prefix 197):

See the drawing number ranges (Prefix 197) on table above.

Naming rule for DS and Lower Level (Prefix 198):

See the drawing number ranges (Prefix 198) on table above.

Naming rule for Reuse 190:

See the drawing number ranges on table above.

Naming rule for Reuse 191:

See the drawing number ranges on table above.

© 2014 PTC Module 1

Task 1: Access the folder at ERJ 190 Type container

Module 1 © 2011 PTC

© 2014 PTC Module 1

3. Select Structure Tab to see the UL structure.

Module 1 © 2011 PTC

© 2014 PTC Module 1

Module 1 © 2011 PTC

© 2014 PTC Module 1

Module 1 © 2011 PTC

© 2014 PTC Module 1

Module 1 © 2011 PTC

This completes the exercise.

© 2014 PTC Module 1

After completing this module, you will be able to:

• eBOM Configuration: Latest

After completing this module, you will be able to:

• Product Structure Browser

The Default filter is composed of:

View: Design or Manufacturing

The images in the “Visualization” tab serve two purposes:

<Note> To approve the PN, it visualization must be made using CATIA.

<Note> To approve the PN, it visualization must be made using CATIA.

<Note> To approve the PN, it visualization must be made using CATIA.

<Note> To approve the PN, it visualization must be made using CATIA.

The following differences are detected when comparing part structures:

© 2014 PTC Module 2

Module 2 © 2014 PTC

1. Select Edit Filter.

© 2014 PTC Module 2

Module 2 © 2014 PTC

1. Select Edit Filter.

4. At Edit Filter dialog box select Ok.

© 2014 PTC Module 2

Module 2 © 2014 PTC