Start using KARREN?

KARREN’s look and features are evolving. Your screen probably looks different than this quick start guide but tey concepts remain the same. This is a short walk through of the getting started phase.

1. Create you first project & activities

 

First to start using KARREN, create a project: 

  1. Click on the « Create Project » button in the Homepage

  2. Fill the necessary information in the project creation pop up

  3. Click on the « Create » button once all the required fields have been filled

When the project is created, it is shown in the list of projects of the Homepage.

You can configure further the newly created project (managing roles and permissions, creating activities, …) by opening the project (click on the card of the project in the Homepage).

To create your first activity :

  1. Go to the « Management » tab of the project

  2. Click on the « Create an Activity » button

  3. Fill the necessary information in the activity creation pop up

  4. Click on the « Create » button once all the required fields have been filled

The newly created activity appears in the list of activies of the project. Similarly to a project, an activity can be further configured by opening it (managing roles and permissions, creating branches, …)

 

2. Define your system & collaborations

2.1. Define your system & collaborations

To create a branch for an activity :

  1. Go to « Management » tab of the activity

  2. Click on the « Create a Branch » button

  3. Fill the necessary information in the branch creation pop up

  4. Click on the « Create » button once all the required fields have been filled


The newly created branch appears in the list of branches of the activity.


A branch can be further configured by opening it (managing roles and permissions, creating products, requirements, defining the connection map, creating candidates …)

A branch can be also created by coping another branch. To do so, select the branch to be copied from the list and click on the « Copy from » button.

2.2. Define Products, Requirements & Viewpoints

Products, requirements, viewpoints and the connection map are created inside a branch.

 

To create products :

  1. Go to « Products » tab of the branch

  2. Click on the « Create a Product » button

  3. Fill the necessary information in the product creation pop up

  4. Click on the « Create » button once all the required fields have been filled
     

The newly created product appears in the list of products of the branch.

 

* A product can be also imported from an Excel file

To create requirements:

  1. Go to the « Requirements » tab of the branch

  2. Click on the « Create a Requirement » button

  3. Fill the necessary information in the product creation pop up

  4. Click on the « Create » button once all the required fields have been filled


The newly created requirement appears in the list of requirements of the branch.


* A requirement can be also imported from an Excel file

* The requirements can be also viewed as a tree by selecting the « Tree View »

To define viewpoints for a branch :

  1. Go to the « Viewpoints » tab of the branch

  2. Click on the « Create a Viewpoint » button

  3. Fill the necessary information in the viewpoint creation pop up

  4. Click on the « Create » button once all the required fields have been filled


The newly created viewpoint appears in the list of viewpoints of the branch.

2.3. Define your Engineering Collaboration Process

The engineering collaboration process is defined in the « connection map » tab of the branch.  It describes how the viewpoints use the products & requirements and collaborate with them.

 

3. Do a collaborative work & optimize your product

At the branch level, once the engineering problem is translated into products, requirements, viewpoints and the template of collaboration is defined, candidates can be created (template).


A candidate is a space  for consolidating the collaborative work of the engineers from different fields and checking that the requirements are met. The work of an engineer is done in a Viewpoint where he evaluates the parameters of the products ( and check the constraints associated with those parameters). When an engineer is satisfied with his work, he can published the Viewpoint. At the candidate level, the published viewpoints are consolidated to produce a solution.

3.1. Create a Candidate

To create a candidate for a branch :

  1. Go to the « Management » tab of the branch

  2. Click on the « Create a Candidate » button

  3. Fill the necessary information in the candidate creation pop up

  4. Click on the « Create » button once all the required fields have been filled


The newly created candidate appears in the list of candidates of the branch.

3.2. Work in a Viewpoint

To evaluate parameters in a Viewpoint :

  1. Go to the « Parameter Evaluation » tab of the Viewpoint

  2. Select the products whose parameters are to be evaluated

  3. Fill out the values (and units) of the parameters

 

 * Parameters can be evaluated using connectors. In such a case, the engineer can directly synchronize the values from an engineering software (ex : CATIA) to KARREN

The table of requirements of the « Parameter Evaluation » tab displays whether the constraints (requirements) are verified. The status of the constraints are updated  every time a parameter is evaluated.

3.3. Consolidate Engineering Work & Find Best Product Solutions

As previously stated, when engineers are satisfied with their work they publish their Viewpoints. The published viewpoints are then consolidated to produce a solution. That consolidation is done in the « Consolidation » tab of the candidate. At the end of the consolidation process, a single value is chosen for every parameter of the candidate and the requirements are checked according to those chosen values. The chosen value for a parameter can be either a value that was proposed by an engineer (when he published his Viewpoint) or a trade-off between values proposed by many engineers.

Once a candidate is consolidated, it can be proposed as a solution by publishing it. It is the responsibility of the « Branch Manager » to validate the proposition (then the candidate is recognized to be a solution) or to reject it.

When many solutions are available, they can be compared using the dashboard to choose the most suitable according to some design criteria.

Go further

We hope you found it useful. Should you still have questions simply contact our crew and we will happy to help you.

108, avenue Jean Moulin

78170 LA CELLE SAINT-CLOUD

  • LinkedIn
  • YouTube

01 30 08 22 80

© Digital Product Simulation 2020