2. About Config Consultants
• Privately Held; Established in 2006;
• Average Resource’s Oracle Implementation experience: 10+
years
• Head Quarters in Santa Clara, CA with Satellite offices across
the United States and India
3. Agenda
• Introduction • Steps to enable FCE • Rule development
• About Config Consultants • Converting existing models
• Introduction to FCE • Model Conversion Report
• FCE vs. Original Engine • Changes in OCD
• New Features • Rule Types and Rule Classes
• What isn’t supported in FCE • Changes in Syntax
4. What is Fusion Configurator Engine?
• New Configurator engine available since release 12.1
• FCE is based on Constraint Programming technology
Constraint programming is a programming paradigm wherein relations between
variables are stated in the form of constraints. Constraints differ from the common
primitives of imperative programming languages in that they do not specify a step or
sequence of steps to execute, but rather the properties of a solution to be found
5. FCE compared to Original Engine
• Products are allowed to be configured faster
• Leverage the use of default and search decisions
• FCE automatically finds a solution that includes the user's selections and
satisfies all of the constraints.
6. New Features in FCE
• Numeric rules are bidirectional
• Numeric input allowable ranges are displayed dynamically
• The order of execution of Defaults can be specified by the Rule designer
9. Bidirectional Rule Example
At runtime the following rules will execute
Rule#2 Default Option_C = 2;
Rule#1 Add alltrue(Option_A, Option_B) * 2 to Option_C;
Option Name Quantity Value
Option_C 2
Option_A 1
Option_B 1
10. New Features in FCE
• Numeric rules are bidirectional
• Numeric input allowable ranges are displayed dynamically
• The order of execution of Defaults can be specified by the Rule designer
11. New Features in FCE
Auto-Instantiation of Components:
Components can be instantiated automatically by constraint definitions
Instantiation no longer requires Configurator Extensions or end user
action
Auto-Completion of Configurations:
The FCE can automatically try to complete a configuration, based on the
Model's rules
12. New Feature in FCE
• Copy button on BOM Instance Management Table
13. Steps to Enable FCE
Profile Name Default Value
CZ: Configurator Engine for New Models Original
CZ: Default Max Quantity Decimal 1000.0
CZ: Default Max Quantity Integer 1000
CZ: Enable Configurator Engine Original
CZ: Use BOM Default Quantity as Domain True
Note: Configurator Engine for New Models must match Enable Configurator Engine unless Enable
Configurator Engine is set to BOTH
14. Converting Existing Model
Once you select
the “Go” button
you will get a ID
number.
Save the ID
number.
15. Converting Existing Model
Created Conversion Set with ID RequestID. Please review the output
of the Model Conversion concurrent process for important messages
about the conversion.
Concurrent Programs > Schedule>Process a Single Model Conversion
Note: “Process a Single Model Conversion” concurrent program take “Model Conversion Set
ID” as a parameter.
16. Converting Existing Model
Model Conversion Utility
• Creates copy of model
ATO
MODEL
• Converts it to FCE
OC OC OC
• Source model remains intact
• Creates a report of changes made to
the model
17. Converting Nested Models
ATO
Model Conversion Utility (MCU) MODEL 1
• Run MCU on top most parent. ATO ATO ATO
• Running MCU for each child MODEL 2 MODEL 3 MODEL 4
model will result in loss of OC OC OC
parent child relationship that
can’t be re-linked. OC OC OC
18. Model Conversion Utility Report
What will be on the report?
• Model nodes, rule, and UI object changes
• Failure, Warning, Advisory and Information messages
Note: Good document to save and reference back
19.
20. Model Conversion Utility Report
• Failure – Object could not be converted
• Warning – Object may introduce unexpected or undesirable behavior
• Advisory – Converted successfully but performance improvements can be made
• Information – Converted successfully with no issues
21. Model Conversion Utility Report
Reduce Report Page Length
• Clean up model before conversion
• Remove unused nodes
• Remove disabled rules
22. Rule Types and Rule Classes
Rule Type Constraint Default Search
Decision
Logic Rule X X X
Comparison Rule X X X
Accumulator Rule X
Property-based Compatibility X
Explicit Compatibility X
Design Chart X
Statement Rule X X X
23. Rule Types and Rule Classes
Rule Class Description Orderable
Constraint Applied at runtime while No
user selects options or
enters a value
Default Applied at runtime when Yes
configuration initializes
Search Decisions Applied during the Auto- Yes
Complete process
24. Syntax Changes
OCE FCE
NotTrue Not
Contribute…To Add…To
Contribute…From Subtract…From
ATAN2 ATAN
25. Rule Development
OCE:
Option_A Defaults AnyTrue (Option_B, Option_C)
FCE:
AnyTrue(Option_A) Implies AnyTrue(Option_B, Option_C)
Note: FCE rule will have a Class Type of Default
26. Rule Development
OCE:
CountFeature_A Implies BooleanFeature_B
FCE:
(CountFeature_A > 0) Implies BooleanFeature_B
Note: Count features are converted so that it becomes greater-than-0 (zero)
33. What’s not supported in FCE
• Telecommunications Services Ordering (TSO)
• Use of Connectors
34. Configurator Extensions
• Configurator Extension events cannot be triggered during the Auto-Complete
process.
• CX is used to modify any part of a completed configuration that was created by
Auto-Complete (including states, values, instance containments, and so on), then
Oracle throws a error.
35. Configurator Extensions
The following CX events are no longer supported in FCE
• postInstanceEditable • postConnect
• postInstanceNonEditable • postDisconnect
• onInstanceLoad • onConfigLineType
• postInstanceLoad • onConfigValidate
