AUDI CAx Business Scenario

From ONTORULE Show Case

Jump to: navigation, search

Description

The scenario described on this page is partially fictional and based on the M24 show case. A more advanced version can be found in Deliverable D4.3.

Car properties, such as safety or comfort, are linked via a function with different methods that test a desired behaviour. Relevant input data, e.g., EU legislation documents, describe necessary requirements that parts of a car or whole car models have to fulfil. For example, seat belt regulations can be found in sources including:

  1. Automotive Directive 77/541/EEC and 76/115/EEC
  2. UNECE Vehicle Regulations No. 16

The required solution should provide the user with answers to the following questions:

Q: Which tests are required to give clearance for some property?

(A: In the use case there is some information on the tests for frontal protection)

Q: Which tests have a low quality and what are the alternatives available?

(A: The simulated seat belt twist test has a low quality but the trolley test is a high quality alternative.)

Audi m24 diagram.png

ONTORULE Approach

We illustrate the ONTORULE approach for the AUDI Business Orchestration Scenario in a sequence of typical tasks performed by the Personas involved with the scenario.

Concrete Implementation

  1. Luis, an IT expert, installs Terminae on Marc´s PC.
  2. With the aid of the business analyst Marc, the senior business expert Gary, loads all relevant and accessible texts into Terminae. He creates an ontology and annotates the text with the ontological entities. This step is semi-automatic.
  3. Luis installs SemEx on the PC of the domain expert Alice.
  4. Alice gets the generated ontology and the annotated text from Marc (or from the webdav repository). She creates candidate rules based on the document using SemEx. This step is semi-automatic.
  5. Marc checks with the Platform Management Component the contact information of the person responsible for installing OntoStudio, finds that it is Luis and delegates the task.
  6. Luis installs OntoStudio on Marc´s PC.
  7. Marc gets the generated ontology, the annotated text and the candidate rules from Gary (or from the webdav repository). He formalizes the candidate rules in ObjectLogic. Additionally, he creates queries, the system should answer.
  8. Luis installs OntoStudio on Alice´s PC.
  9. Alice, a domain expert, gets the ontology, the candidate rules and the formalized rules from Marc (or from the webdav repository). She makes some changes in the ontology and rules and formalizes additional rules. Additionally, she creates queries, the system should answer.
  10. Together with Marc Alice creates a documentation of the ontology using Parrot.
  11. Luis installs OntoStudio on Gary´s PC.
  12. Gary checks the correctness of the system by posing the defined queries. If he gets the expected results everything is fine, if not, he proceeds with step 6 and 8.
  13. Luis implements the final system containing an intuitive user interface.
  14. Joana, an operational user, uses the web-based system.
AudiBusinessProcess-Concrete.png
Facts about AUDI CAx Business ScenarioRDF feed
Scenario Description The scenario described on this page is partially fictional and based on the M24 show case.

It can be regarded as a part of the Audi Business Orchestration Scenario, and but needs to be extended and adopted.

For additional information see ONTORULE D4.3.
Scenario Name AUDI CAx Business Scenario  +
Scenario Use Case Partner AUDI  +
Personal tools
sitemap