Practice - Creating Rules for a Configuration or Sub-configuration

Distribution
Oracle Complex Maintenance, Repair, and Overhaul

Job Title*

Ownership
The Job Title [list@YourCompany.com?Subject=LABxxxxx] is responsible for ensuring that
this document is necessary and that it reflects actual practice.
Practice - Creating Rules for a Configuration or Sub-configuration
Overview
In this practice, you will learn how to define rules for a master configuration, sub-configuration
or position.

Assumptions
 You must have access to an Oracle Application Vision database or comparable training
or test instance at your site on which to complete this practice.

 You need to replace XX with a unique identifier.

 Position references must already have been set up during implementation.

 You must have defined a master configuration.

 You must have defined positions in the master configuration.

Tasks
Create a rule

Rules control the allowable items that can be installed into the configuration. The definition of
configuration rules enables the enforcement of regulations for equipment configurations issued
by OEM’s and regulatory institutions such as the FAA. You can create rules for:

 Restricting items for a position

 Restricting configurations for a position

 Restricting positions based on other positions

Note the following rule controls:

Conguration Rule Control

For the configuration rule control the following apply:

Subject: Configuration

Objects: Positions and Instances

Using a configuration as the subject, the direct object pointers are one or many positions or the
percent of instances to plan. The rule will include a chain or sub-construct of the other rule
controls. Referencing Positions it requires, excludes, or negates though the use of Necessity -
mandatory, optional, and optional with a rule (containing Empty/Is Null, Installed/Is Not Null,
Same As). Referencing Instances it implies the minimum and maximum percent or quantities by
state/condition per configuration.

The outcome produces the following:

 Installation Allowed

 Installation Not Allowed

 Configuration Not Valid

 Configuration Valid

Position Rule Control

For the Position Rule Control the following apply:

Subject: Position

Objects: Sub-configurations/Alternate Sub-configurations, and Items

Using positions as the subject it will be in a sub-construct, if configuration control, or as a stand

alone which contain sub-constructs, if node specific. Referencing Sub-configurations/Alternate
Sub-configurations it implies allowed by the association, excludes allowed by adding a rule, and
requires by the use of mandatory or a rule. Referencing Items though the item group association
it implies allowed and excludes or requires through a rule.

The outcome produces the following:

 Installation Allowed

 Installation Not Allowed

 Configuration Not Valid

 Configuration Valid

Sub-conguration/Alternate Sub-conguration Rule Control

For the Sub-configuration/Alternate Sub-configuration Control the following apply:

Subject: Sub-configuration/Alternate Sub-configuration

Object: Position and Instances

Referencing Positions it requires, excludes, or negates though the use of Necessity - mandatory,
optional, and optional with a rule (containing Empty/Is Null or Installed/Is Not Null).
Referencing Instances it implies the minimum and maximum percent or quantities by
state/condition per configuration.
The outcome produces the following:

 Installation Allowed

 Installation Not Allowed

 Configuration Not Valid

 Configuration Valid

Item Rule Control

For the Item Control the following apply:

Subject: Item or Item #

Object: Item #, Is Installed, Previously Installed, Interchangeability

Type, Interchangeability Code, and Instances

Referencing the item number it excludes, requires, or negates based on the hierarchy for which
the rule is contained. Referencing Item # and Is Installed or Previously Installed requires,
excludes, or negates based on the current or historical reference. Referencing Interchangeability
Type and Interchangeability Code with the item # requires, excludes, negates, or implies based
the type, code, or combination. Referencing the priority with the item # provides defaults.
Referencing Instances it implies the minimum and maximum percent or quantities by
state/condition per configuration. This rule is not evaluated.

The outcome produces the following:

 Installation Allowed

 Installation Not Allowed

 Configuration Not Valid

 Configuration Valid

Instance Rule Control

For the Instance Control the following apply:

Subject: Instance (Implied)

Object: Minimum, Maximum, Percent, Quantity, State/Condition

Referencing the object combination implies the instance quantity allowed per condition. This
rule is not evaluated. The following table includes examples of some legal rule statements:
 Subject Predicate Object Outcome
Position is installed/is not installed T/F
Position has/does not have item T/F/U if uninstalled
Position has/does not have sub-master configuration T/F/U if uninstalled
Position must have/must not have item T/F

The outcome of each rule evaluation is as follows:

• Success (T)

• Unable to determine true or false (U)

• Rule failed in evaluation (F)

When a rule is applied, the units affected by the configuration are validated. Once a list of
applicable rules is defined for each position, then each rule is evaluated individually. The
statements will require mapping position path to UC item instance and comparing instance
properties against the rule requirements. The result of validation is either status “S” for success
or a table of rule violations. If the validation fails the status of the configuration changes to
incomplete.

1. Create a rule for the FCV-CS-5000 Radiator Assy position using the following details:
Field Name Value
Rule Name NLG Rule 1
Rule Type Mandatory
Sequence 10
Subject 32-02, Nose Landing Gear
Operator Has the same
Object Type Item as position
Object FCV-CS-5000 Radiator Assy
Solution - Creating Rules for a Configuration or Sub-configuration
Creating rules

Responsibility = Oracle Complex Maintenance, Repair, and Overhaul; Vision

Operations

1. Navigate to the Search Master Configuration page for the configuration that you created.

 (H) Configuration > (T) Master Configuration > (B) Go

2. Query for the configuration that you defined. Click the Edit icon to navigate to the Edit
Master Configuration page.

3. Select the FCV-CS-5000 Radiator Assy position reference. Choose Rules from the drop-
down menu and click Go.

4. Define a rule with the following information:

 Field Name Description Value
Rule Name User-defined Rule name. NLG Rule 1
Rule Type Can be Mandatory or Fleet. A Mandatory
rule type of mandatory indicates
that the rule will be evaluated
during installations, and a rule
type of fleet indicates that the
rule is created only as a reference
to the fleet percentages.
Sequence User defined value to determine 10
the order of the rules defined.
Subject Use the search icon to launch the 32-02, Nose Landing Gear
‘Select Positions’ page where
you can select the position path
for which you are defining the
rule.
Operator Conditions in a rule. The Has the same
possible values are: is installed,
is not installed, has, does not
have, must have, must not have,
has same sub-configuration
installed, does not have same
sub-configuration installed.
Object Type You can select from the Item as position
following Object types: item,
configuration, configuration as
position, item as position (1), or
item as position.
Object Select value based on object type FCV-CS-5000 Radiator Assy
5. Click Apply. The Rule record is added to the database.