Oracle Policy Automation (OPA) Modeling

Oracle Policy Automation is an end-to-end solution for capturing, managing, and deploying legislation and other document-based policies for improved customer service and automated decision making.

Oracle Policy Automation Components:
– A desktop modeling experience for policy experts (Oracle Policy Modeling)
– Advice for customers and agents (Interviews)
– A management console for tracking, analyzing and deploying policy versions (OPA Hub)
– Built-in connectivity with Oracle Service Cloud
– APIs, Frameworks and SDKs for integrating policies into other applications and processes

  • Oracle Policy Modeling is the tool Policy Experts use to create rules and interviews.

  • Oracle Policy Modeling: Rules: Rules are modeled directly in Microsoft Word and Excel. Apply appropriate styles and save the document to create executable rules. The Policy Modeling toolbar in Word and Excel has all the styles you need. Click Show Styles to see the styles in use. Use the Rule Assistant or OPM – conclusion style for conclusions, OPM – level 1 for the first set of conditions. Separate conditions with and or or.
  • Policy Modeling: Attributes Attributes are a single unit of data or fact. When you write a rule in Word or Excel, Policy Modeling will automatically create a corresponding attribute with the text you have used in the rule.
  • Writing Rules: A rule is an assertion that a conclusion can be drawn from a particular state of affairs. By default, Oracle Policy Modeling assumes all rules contain an alternative conclusion. That is, if the conditions are not satisfied, you can infer the opposite of the conclusion.
  • Oracle Policy Modeling: Interviews: An interview is a web-based application which collects information from a user and provides interactive advice based on rules. Interviews are created in the Policy Modeling – Interview tab.
  • Oracle Policy Automation Hub: Policy Models are deployed to the Policy Automation Hub where they can be used by other applications.

Policy Modeling has automatically created the attribute, including creating a question form is the person a full-time employee, negation the person is not a full-time employee and uncertain it is uncertain whether the person is a full-time employee. Policy Modeling uses an in-built list of verbs to create these phrasings. The verb list is editable in the Policy Modeling Project: language sub-tab. These phrasing can also be manually overridden. Policy Modeling uses an in-built list of verbs to create the question and negation for Boolean (true/false) attributes. All Boolean attributes must therefore contain at least one verb. The verb in the sentence is the action word. A complete statement: Does the sentence have a verb, and does the sentence make sense? Able to be sensibly negated: Does the sentence make sense if you add the word? Policy Modeling creates the question form for these attributes by simply asking “what is” before the attribute text (eg. “what is the person’s job?”). This can be helpful to remember when phrasing non-Boolean attributes.


These are advanced components of Policy Automation Modeling: Conclusions and Conditions, Negations and Linking Rules, Grouping Operators and Intermediate Attributes, Testing Rules, Comparisons in Rules, Calculations in Rules, Rule Tables in Word, Rule Tables in Excel, Entities, Relationships, Reasoning with Entities, When to Use Entities, Entity and Relationship Screens, Improving Attribute Text, Data Validation, Audit Reports, Forms, Data Mapping, Enhancing Interviews.

Leave a Reply

Your email address will not be published.