From 5dbc22da2ab75ac8059dcc84b936f09697a061ae Mon Sep 17 00:00:00 2001
From: rkv <rkv@opencascade.com>
Date: Tue, 7 May 2013 08:33:10 +0000
Subject: [PATCH] Config scripts for CEA and EDF are created.

---
 Workspace/Siman-WS/WebContent/conf/my.xml     |  11 +
 Workspace/Siman-WS/build.xml                  |  42 ++-
 Workspace/Siman-WS/conf/cea_som.properties    |  19 ++
 Workspace/Siman-WS/conf/cea_som.xml           | 270 ++++++++++++++++
 Workspace/Siman-WS/conf/cea_som_en.properties |  19 ++
 Workspace/Siman-WS/conf/customer.txt          |   1 +
 Workspace/Siman-WS/conf/edf_som.properties    |  23 ++
 Workspace/Siman-WS/conf/edf_som.xml           | 300 ++++++++++++++++++
 Workspace/Siman-WS/conf/edf_som_en.properties |  21 ++
 .../Siman-WS/conf/templates/som.properties    |  52 +++
 .../Siman-WS/conf/templates/som_en.properties |  53 ++++
 Workspace/Siman/WebContent/conf/my.xml        |  11 +
 Workspace/Siman/build.xml                     |  46 ++-
 Workspace/Siman/conf/cea_som.properties       |  19 ++
 Workspace/Siman/conf/cea_som.xml              | 270 ++++++++++++++++
 Workspace/Siman/conf/cea_som_en.properties    |  19 ++
 Workspace/Siman/conf/customer.txt             |   1 +
 Workspace/Siman/conf/edf_som.properties       |  23 ++
 Workspace/Siman/conf/edf_som.xml              | 300 ++++++++++++++++++
 Workspace/Siman/conf/edf_som_en.properties    |  21 ++
 Workspace/Siman/conf/templates/som.properties |  52 +++
 .../Siman/conf/templates/som_en.properties    |  53 ++++
 22 files changed, 1617 insertions(+), 9 deletions(-)
 create mode 100644 Workspace/Siman-WS/conf/cea_som.properties
 create mode 100644 Workspace/Siman-WS/conf/cea_som.xml
 create mode 100644 Workspace/Siman-WS/conf/cea_som_en.properties
 create mode 100644 Workspace/Siman-WS/conf/customer.txt
 create mode 100644 Workspace/Siman-WS/conf/edf_som.properties
 create mode 100644 Workspace/Siman-WS/conf/edf_som.xml
 create mode 100644 Workspace/Siman-WS/conf/edf_som_en.properties
 create mode 100644 Workspace/Siman-WS/conf/templates/som.properties
 create mode 100644 Workspace/Siman-WS/conf/templates/som_en.properties
 create mode 100644 Workspace/Siman/conf/cea_som.properties
 create mode 100644 Workspace/Siman/conf/cea_som.xml
 create mode 100644 Workspace/Siman/conf/cea_som_en.properties
 create mode 100644 Workspace/Siman/conf/customer.txt
 create mode 100644 Workspace/Siman/conf/edf_som.properties
 create mode 100644 Workspace/Siman/conf/edf_som.xml
 create mode 100644 Workspace/Siman/conf/edf_som_en.properties
 create mode 100644 Workspace/Siman/conf/templates/som.properties
 create mode 100644 Workspace/Siman/conf/templates/som_en.properties

diff --git a/Workspace/Siman-WS/WebContent/conf/my.xml b/Workspace/Siman-WS/WebContent/conf/my.xml
index e14a992..986e5f4 100644
--- a/Workspace/Siman-WS/WebContent/conf/my.xml
+++ b/Workspace/Siman-WS/WebContent/conf/my.xml
@@ -10,6 +10,17 @@
         <mapping extension="med"    executable="runSalome"/>
         <mapping extension="py"    executable="runSalome"/>
         <!--mapping extension="xml"    executable="runSalome"/--> <!-- for YAKS activity -->
+
+        <!-- CASTEM -->
+        <mapping extension="model"  executable="runSalome"/>
+        <!-- MECA -->
+        <mapping extension="syd"    executable="runSalome"/>
+        <mapping extension="bz2"    executable="runSalome"/>
+        <!-- SYRTHES -->
+        <mapping extension="comm"    executable="runSalome"/>
+        <mapping extension="resu"    executable="runSalome"/>
+        <mapping extension="mess"    executable="runSalome"/>
+        <mapping extension="rmed"    executable="runSalome"/>
     </modules>
 
     <viewers extension="pdf,brep,med" />
diff --git a/Workspace/Siman-WS/build.xml b/Workspace/Siman-WS/build.xml
index de5a654..8839463 100644
--- a/Workspace/Siman-WS/build.xml
+++ b/Workspace/Siman-WS/build.xml
@@ -36,6 +36,10 @@
 		<sequential>
 			<echo message="Generating configuration in @{mode} mode" />
 			<!-- Copy files from config source directory according to the given mode -->
+            <loadfile property="customer" srcfile="${config.src.dir}/customer.txt"/>
+            <loadfile property="som" srcfile="${config.src.dir}/${customer}_som.properties"/>
+            <echo message="som: ${som}"/>
+            <loadfile property="som.en" srcfile="${config.src.dir}/${customer}_som_en.properties"/>
 			<copy todir="${basedir}/${config.@{mode}.dir}" overwrite="true">
 				<fileset dir="${config.src.dir}/templates">
 				</fileset>
@@ -108,8 +112,8 @@
 	<!-- ================================================= -->
 	<target name="prepare-postgres" description="prepare configuration for Postgress">
 		<echo message="Prepare configuration for Postgress..." />
-		<copy file="conf/debug_pg.properties" tofile="conf/debug.properties" overwrite="true"/>
-		<copy file="conf/release_pg.properties" tofile="conf/release.properties" overwrite="true"/>
+		<copy file="${config.src.dir}/debug_pg.properties" tofile="${config.src.dir}/debug.properties" overwrite="true"/>
+		<copy file="${config.src.dir}/release_pg.properties" tofile="${config.src.dir}/release.properties" overwrite="true"/>
 		<antcall target="debug-config"/>
 	</target>
 
@@ -118,8 +122,38 @@
 	<!-- ================================================= -->
 	<target name="prepare-mysql" description="prepare configuration for MySql">
 		<echo message="Prepare configuration for MySql..." />
-		<copy file="conf/debug_mysql.properties" tofile="conf/debug.properties" overwrite="true"/>
-		<copy file="conf/release_mysql.properties" tofile="conf/release.properties" overwrite="true"/>
+		<copy file="${config.src.dir}/debug_mysql.properties" tofile="${config.src.dir}/debug.properties" overwrite="true"/>
+		<copy file="${config.src.dir}/release_mysql.properties" tofile="${config.src.dir}/release.properties" overwrite="true"/>
 		<antcall target="debug-config"/>
 	</target>
+
+    <!-- ================================================= -->
+    <!--    prepare-customer: Prepare config for the given customer -->
+    <!-- ================================================= -->
+    <macrodef name="prepare-customer">
+        <!-- Parameter "customer" can be equal to "cea" or "edf" -->
+        <attribute name="customer" />
+        <sequential>
+            <echo message="Prepare config for the customer @{customer}" />
+            <echo message="@{customer}" file="${config.src.dir}/customer.txt"/>
+            <copy file="${config.src.dir}/@{customer}_som.xml" tofile="WebContent/conf/som.xml" overwrite="true"/>
+            <antcall target="debug-config"/>
+        </sequential>
+    </macrodef>
+    
+    <!-- ================================================= -->
+    <!--    prepare-cea: Prepare config for CEA            -->
+    <!-- ================================================= -->
+    <target name="prepare-cea" description="prepare configuration for CEA">
+        <echo message="Prepare configuration for CEA..." />
+        <prepare-customer customer="cea" />
+    </target>
+
+    <!-- ================================================= -->
+    <!--    prepare-cea: Prepare config for EDF            -->
+    <!-- ================================================= -->
+    <target name="prepare-edf" description="prepare configuration for EDF">
+        <echo message="Prepare configuration for EDF..." />
+        <prepare-customer customer="edf" />
+    </target>
 </project>
diff --git a/Workspace/Siman-WS/conf/cea_som.properties b/Workspace/Siman-WS/conf/cea_som.properties
new file mode 100644
index 0000000..49e8a96
--- /dev/null
+++ b/Workspace/Siman-WS/conf/cea_som.properties
@@ -0,0 +1,19 @@
+menu.step.1   = Spécifier l''étude
+menu.step.2   = Concevoir le scénario
+menu.step.3   = Créer la géométrie
+menu.step.4   = Générer le modèle d''analyse
+menu.step.5   = Entrer les conditions de calcul
+menu.step.6   = Analyser les résultats
+menu.step.7   = Définir le schéma de calcul
+menu.step.8   = Capitaliser ce cas d''étude
+menu.step.9   = Finaliser l''étude
+
+folder.step.1 = Spécification de l''étude
+folder.step.2 = Description du scénario
+folder.step.3 = Géométrie
+folder.step.4 = Modèle d''analyse
+folder.step.5 = Conditions de calcul
+folder.step.6 = Résultats
+folder.step.7 = Schéma de calcul
+folder.step.8 = Élements de connaissances
+folder.step.9 = Rapport final
diff --git a/Workspace/Siman-WS/conf/cea_som.xml b/Workspace/Siman-WS/conf/cea_som.xml
new file mode 100644
index 0000000..3115e34
--- /dev/null
+++ b/Workspace/Siman-WS/conf/cea_som.xml
@@ -0,0 +1,270 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<project-structure>
+
+
+<!-- 1. Database physical location
+     -->
+    <database>
+		<repository disk="/home/siman/Repository" />
+    </database>
+
+
+<!-- 2. Formats
+     -->
+    <formats>
+
+<!-- 2.1 Project elements identification scheme
+     Studies, Knowledges and Documents are identified by unique user references. The structure of these references is customizable.
+     You customize references through patterns.
+     A reference's pattern is a character string including format directives. These format directives allow you to insert
+     some information into the reference. The following directives are available:
+     - %yy or %yyyy for inserting the entity creation year on 2 or 4 digits
+     - %0000 for inserting a unique index, the number of digits being defined by the number of 0
+     The above index is unique in the scope of cycle defined by the first format directive (year). In other words, this index
+     restarts every new year. As such, for making references unique on this application server, both format directives (cycle
+     and index) must be present in the pattern.
+     Other characters are simply inserted as is in generated references. They can be used for extending the reference uniqueness
+     beyond application servers, by adding a prefix specific to a given server (for example, a company department name).
+     Given that these references may be used as directory or file names of the repository vault, the pattern must not include
+     illicit characters such as '/', '?', '<' etc.
+     -->
+        <references  study="DER%yy%0000"/>
+
+<!-- 2.2 Physical files naming scheme
+     The physical data files stored into the repository vault can be named as follows:
+     - By the user-defined title of corresponding documents ("title" name attribute below)
+     - Encoded by a built-in scheme ("encoded" name attribute)
+     - As is, that is, by keeping the name of the imported file ("asis" name attribute - not yet supported)
+     Remarks:
+     - When using the title scheme, as file names may include accent characters, client browsers must be configured for
+       NOT encoding URLs as UTF-8.
+     - Whatever is the naming scheme used, in order to avoid name clashes, file names are anyway suffixed by an index
+       unique in the scope of the owner study.
+     -->
+        <files name="asis"/>
+
+<!-- 2.3 Document versions format
+     -->
+        <versions pattern="%M.%m[-%s]"/>
+    </formats>
+
+
+<!-- 3. Document types
+
+     Warning: Articles must be ordered in a way that used document types (uses attribute values) must previously be defined.
+     Example: "requirements" type must be defined before "specification" because "specification" uses "requirements".
+     Remarks:
+     - "knowledge" is a reserved word qualifying Knowledge Elements. So, it must not be used as a document type name.
+     - "default" and "built-in" are also reserved words used for defining validation cycles.
+     - In this version, the "uses" attribute is limited to 1 document type only.
+     -->
+    <documents>
+        <article type="requirements"/>
+        <article type="specification" uses="requirements"/>
+        <article type="design"        uses="specification"/>
+        <article type="geometry"      uses="design"/>
+        <article type="model"         uses="geometry"/>
+        <article type="loads"         uses="model"/>
+        <article type="script"        uses="loads"/>
+        <article type="log"           uses="script"/>
+        <article type="results"       uses="script"/>
+        <article type="report"        uses="results"/>
+        <article type="schema"/>
+        <article type="memorandum"/>
+        <article type="minutes"/>
+        <article type="coparisonResult"/>
+        <article type="visualisation"/>
+    </documents>
+
+
+<!-- 4. Simulation Context types
+
+     Warning: The Simulation Context type "product" is mandatory as it is used by at least one application.
+     -->
+    <contexts>
+
+    <!-- General information -->
+        <article type="customer"/>
+        <article type="product"/>
+        <article type="phase"/>            <!-- Phase of the product                                 -->
+        <article type="need"/>             <!-- Customer needs                                       -->
+        <article type="purpose"/>          <!-- Objective of the study                               -->
+        <article type="physic"/>           <!-- Structure analysis, Thermal-hydraulics, Neutronic... -->
+
+    <!-- Geometry characteristics               Examples:                 -->
+        <article type="object"/>           <!-- Car, Plane, Equipment...  -->
+        <article type="part"/>             <!-- Crankcase, Outer layer... -->
+        <article type="geometry"/>         <!-- Surface, Volume           -->
+
+    <!-- Model characteristics                  Examples:            -->
+        <article type="model"/>            <!-- CSG, FEM...          -->
+        <article type="element"/>          <!-- Bar, Surface, Volume -->
+        <article type="shape"/>            <!-- (Surface) Triangle, Quadrangle... (Volume) Tetrahedron, Hexahedron... -->
+        <article type="order"/>            <!-- First-order, Second-order... -->
+
+    <!-- Analysis type                          Examples:          -->
+        <article type="analysis"/>         <!-- Static, Dynamic... -->
+
+    <!-- Software tools used -->
+        <article type="platform"/>
+        <article type="module"/>
+        <article type="component"/>
+    </contexts>
+
+
+<!-- 5. Knowledge Elements types
+
+     Warning: The Knowledge Elements type "usecase" is reserved for internal use.
+     -->
+    <knowledges>
+        <article type="bestpractice"/>
+        <article type="limitation"/>
+        <article type="inconsistency"/>
+        <article type="metrics"/>
+        <article type="improvement"/>
+    </knowledges>
+
+
+<!-- 6. User activities
+
+     Remarks:
+     - Step names must naturally be unique.
+     - Simulation Contexts must be attached to one classification step only.
+     - Result document types must be results of one step only and be part of contents of the corresponding step.
+     -->
+    <activities>
+        <step name="specification">
+            <classification context="customer,product,phase,need,purpose,physic"/>
+            <flow contents="requirements,specification,minutes" result="specification"/>
+            <storage path="1.Study"/>
+        </step>
+      <scenario>
+        <step name="design">
+            <flow contents="design,memorandum,minutes" result="design"/>
+            <storage path="1.Study"/>
+        </step>
+        <step name="modeling">
+            <classification context="object,part,geometry"/>
+            <flow contents="geometry,memorandum,minutes" result="geometry"/>
+            <storage path="2.Geometry"/>
+            <module name="GEOM"/>
+   	    </step>
+        <step name="meshing">
+            <classification context="model,element,shape,order"/>
+            <flow contents="model,memorandum,minutes" result="model"/>
+            <storage path="3.Mesh"/>
+            <module name="SMESH"/>
+        </step>
+        <step name="solving">
+            <classification context="loads,script,platform,module,component"/>
+            <flow contents="loads,model,log,results,minutes" result="results"/>
+            <storage path="5.Result"/>
+            <module name="CASTEM"/>
+        </step>
+        <step name="postprocessing">
+            <flow contents="memorandum,minutes,coparisonResult,visualisation" result="coparisonResult"/>
+            <storage path="6.Report"/>
+            <module name="VISU"/>
+        </step>
+        <step name="schema">
+            <flow contents="schema" result="schema"/>
+            <storage path="7.Schema"/>
+            <module name="YACS"/>
+        </step>
+        <step name="capitalization">
+            <flow contents="knowledge"/>
+            <storage path="8.Summary"/>
+        </step>
+      </scenario>
+        <step name="reporting">
+            <flow contents="report,minutes" result="report"/>
+            <storage path="1.Study"/>
+        </step>
+    </activities>
+
+
+<!-- 6. Document validation cycles
+     Validation cycles define the actors involved in the validation steps of documents. These steps can be
+     "review", "approval" and "acceptance".
+     Remarks:
+     - Each validation cycle is defined by a tag corresponding to the type of an activity result document.
+     - The actors of validation steps can be
+       "manager", referring the responsible of study,
+       "Nx1", referring the manager of the department (see User definition for more information),
+       "Nx2", referring the boss of the department manager,
+       "customer" (most likely involved in the acceptance step).
+     -->
+    <validations>
+        <specification  review="Nx1"  approval="Nx2"/>
+        <report         review="Nx1"  approval="Nx2"/>
+        <default        review="manager"            />
+    </validations>
+
+<!-- 3. Check-in check-out information
+     Defines the way documents involved in the check-in check-out operations must be processed.
+     Files with import formats are automatically imported into SALOME during check-out if they are uptodate.
+     Other files are downloaded.
+     -->
+    <mappings>
+        <document type="geometry">
+            <import format="brep"/>     <!-- Result Shape                             -->
+        </document>
+        <document type="model">
+            <import format="med"/>      <!-- Result mesh without input parameters     -->
+        </document>
+        <document type="loads">
+            <import format="model"/>    <!-- Input data created interactively         -->
+        </document>
+        <document type="results">
+            <import format="med"/>      <!-- Calculation results source file          -->
+        </document>
+        <document type="schema">
+            <import format="xml"/>      <!-- Calculation results source file          -->
+        </document>
+    </mappings>
+    
+    <default-doctypes>
+        <step number="1">
+            <mapping extension="pdf"    type="requirements"/>
+            <mapping extension="doc"    type="specification"/>     <!-- Microsoft Word 2003 and earlier -->
+            <mapping extension="docx"   type="specification"/>     <!-- Microsoft Word 2007 and later   -->
+            <mapping extension="xml"    type="specification"/>     <!-- Microsoft Word 2007 Open XML    -->
+        </step>
+        <step number="2">
+            <mapping extension="doc"    type="design"/>
+            <mapping extension="docx"   type="design"/>
+            <mapping extension="xml"    type="design"/>
+        </step>
+        <step number="3">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="sldprt" type="geometry"/>          <!-- SolidWorks Part                 -->
+            <mapping extension="sldasm" type="geometry"/>          <!-- SolidWorks Assembly             -->
+            <mapping extension="part"   type="geometry"/>          <!-- GEOM Part                       -->
+            <mapping extension="py"     type="geometry"/>          <!-- GEOM Python script              -->
+            <mapping extension="brep"   type="geometry"/>          <!-- GEOM Part                       -->
+        </step>
+        <step number="4">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="med"    type="model"/>
+            <mapping extension="py"     type="model"/>             <!-- SMESH Python script             -->
+        </step>
+        <step number="5"> <!-- execute the calculations -->
+        	<mapping extension="med"    type="model"/>
+        	<mapping extension="model"  type="loads"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="6">
+            <mapping extension="srd"    type="coparisonResult"/>
+            <mapping extension="py"     type="visualisation"/>
+        </step>
+        <step number="7">
+            <mapping extension="xml"    type="schema"/>
+        </step>
+    </default-doctypes>
+    
+</project-structure>
\ No newline at end of file
diff --git a/Workspace/Siman-WS/conf/cea_som_en.properties b/Workspace/Siman-WS/conf/cea_som_en.properties
new file mode 100644
index 0000000..2dc696a
--- /dev/null
+++ b/Workspace/Siman-WS/conf/cea_som_en.properties
@@ -0,0 +1,19 @@
+menu.step.1   = Specify the study
+menu.step.2   = Design the scenario
+menu.step.3   = Create the geometry
+menu.step.4   = Generate the analysis model
+menu.step.5   = Enter the boundary conditions
+menu.step.6   = Analyze the results
+menu.step.7   = Define the calculation schema
+menu.step.8   = Capitalize this use-case
+menu.step.9   = Finalize the study
+
+folder.step.1 = Specification of the study
+folder.step.2 = Description of the scenario
+folder.step.3 = Geometry
+folder.step.4 = Analysis model
+folder.step.5 = Boundary conditions
+folder.step.6 = Calculation results
+folder.step.7 = Calculation schema
+folder.step.8 = Knowledge elements
+folder.step.9 = Final report
diff --git a/Workspace/Siman-WS/conf/customer.txt b/Workspace/Siman-WS/conf/customer.txt
new file mode 100644
index 0000000..b1121e1
--- /dev/null
+++ b/Workspace/Siman-WS/conf/customer.txt
@@ -0,0 +1 @@
+cea
\ No newline at end of file
diff --git a/Workspace/Siman-WS/conf/edf_som.properties b/Workspace/Siman-WS/conf/edf_som.properties
new file mode 100644
index 0000000..b3971c8
--- /dev/null
+++ b/Workspace/Siman-WS/conf/edf_som.properties
@@ -0,0 +1,23 @@
+menu.step.1   = Spécifier l''étude
+menu.step.2   = Concevoir le scénario
+menu.step.3   = Créer la géométrie
+menu.step.4   = Générer le modèle d''analyse
+menu.step.5   = Effectuer le CASTEM
+menu.step.6   = Effectuer le MECA
+menu.step.7   = Effectuer le SYRTHES
+menu.step.8   = Analyser les résultats
+menu.step.9   = Définir le schéma de calcul
+menu.step.10   = Capitaliser ce cas d''étude
+menu.step.11   = Finaliser l''étude
+
+folder.step.1 = Spécification de l''étude
+folder.step.2 = Description du scénario
+folder.step.3 = Géométrie
+folder.step.4 = Modèle d''analyse
+folder.step.5 = Exécution de calcul CASTEM
+folder.step.6 = Exécution de calcul MECA
+folder.step.7 = Exécution de calcul SYRTHES
+folder.step.8 = Résultats
+folder.step.9 = Schéma de calcul
+folder.step.10 = Élements de connaissances
+folder.step.11 = Rapport final
diff --git a/Workspace/Siman-WS/conf/edf_som.xml b/Workspace/Siman-WS/conf/edf_som.xml
new file mode 100644
index 0000000..affa0b6
--- /dev/null
+++ b/Workspace/Siman-WS/conf/edf_som.xml
@@ -0,0 +1,300 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<project-structure>
+
+
+<!-- 1. Database physical location
+     -->
+    <database>
+        <repository disk="/home/siman/Repository" />
+    </database>
+
+
+<!-- 2. Formats
+     -->
+    <formats>
+
+<!-- 2.1 Project elements identification scheme
+     Studies, Knowledges and Documents are identified by unique user references. The structure of these references is customizable.
+     You customize references through patterns.
+     A reference's pattern is a character string including format directives. These format directives allow you to insert
+     some information into the reference. The following directives are available:
+     - %yy or %yyyy for inserting the entity creation year on 2 or 4 digits
+     - %0000 for inserting a unique index, the number of digits being defined by the number of 0
+     The above index is unique in the scope of cycle defined by the first format directive (year). In other words, this index
+     restarts every new year. As such, for making references unique on this application server, both format directives (cycle
+     and index) must be present in the pattern.
+     Other characters are simply inserted as is in generated references. They can be used for extending the reference uniqueness
+     beyond application servers, by adding a prefix specific to a given server (for example, a company department name).
+     Given that these references may be used as directory or file names of the repository vault, the pattern must not include
+     illicit characters such as '/', '?', '<' etc.
+     -->
+        <references  study="DER%yy%0000"/>
+
+<!-- 2.2 Physical files naming scheme
+     The physical data files stored into the repository vault can be named as follows:
+     - By the user-defined title of corresponding documents ("title" name attribute below)
+     - Encoded by a built-in scheme ("encoded" name attribute)
+     - As is, that is, by keeping the name of the imported file ("asis" name attribute - not yet supported)
+     Remarks:
+     - When using the title scheme, as file names may include accent characters, client browsers must be configured for
+       NOT encoding URLs as UTF-8.
+     - Whatever is the naming scheme used, in order to avoid name clashes, file names are anyway suffixed by an index
+       unique in the scope of the owner study.
+     -->
+        <files name="asis"/>
+
+<!-- 2.3 Document versions format
+     -->
+        <versions pattern="%M.%m[-%s]"/>
+    </formats>
+
+
+<!-- 3. Document types
+
+     Warning: Articles must be ordered in a way that used document types (uses attribute values) must previously be defined.
+     Example: "requirements" type must be defined before "specification" because "specification" uses "requirements".
+     Remarks:
+     - "knowledge" is a reserved word qualifying Knowledge Elements. So, it must not be used as a document type name.
+     - "default" and "built-in" are also reserved words used for defining validation cycles.
+     - In this version, the "uses" attribute is limited to 1 document type only.
+     -->
+    <documents>
+        <article type="requirements"/>
+        <article type="specification" uses="requirements"/>
+        <article type="design"        uses="specification"/>
+        <article type="geometry"      uses="design"/>
+        <article type="model"         uses="geometry"/>
+        <article type="loads"         uses="model"/>
+        <article type="script"        uses="loads"/>
+        <article type="log"           uses="script"/>
+        <article type="resultsMeca"   uses="script"/>
+        <article type="resultsSyrthes" uses="script"/>
+        <article type="report"        uses="results, resultsMeca, resultsSyrthes"/>
+        <article type="schema"/>
+        <article type="memorandum"/>
+        <article type="minutes"/>
+        <article type="coparisonResult"/>
+        <article type="visualisation"/>
+    </documents>
+
+
+<!-- 4. Simulation Context types
+
+     Warning: The Simulation Context type "product" is mandatory as it is used by at least one application.
+     -->
+    <contexts>
+
+    <!-- General information -->
+        <article type="customer"/>
+        <article type="product"/>
+        <article type="phase"/>            <!-- Phase of the product                                 -->
+        <article type="need"/>             <!-- Customer needs                                       -->
+        <article type="purpose"/>          <!-- Objective of the study                               -->
+        <article type="physic"/>           <!-- Structure analysis, Thermal-hydraulics, Neutronic... -->
+
+    <!-- Geometry characteristics               Examples:                 -->
+        <article type="object"/>           <!-- Car, Plane, Equipment...  -->
+        <article type="part"/>             <!-- Crankcase, Outer layer... -->
+        <article type="geometry"/>         <!-- Surface, Volume           -->
+
+    <!-- Model characteristics                  Examples:            -->
+        <article type="model"/>            <!-- CSG, FEM...          -->
+        <article type="element"/>          <!-- Bar, Surface, Volume -->
+        <article type="shape"/>            <!-- (Surface) Triangle, Quadrangle... (Volume) Tetrahedron, Hexahedron... -->
+        <article type="order"/>            <!-- First-order, Second-order... -->
+
+    <!-- Analysis type                          Examples:          -->
+        <article type="analysis"/>         <!-- Static, Dynamic... -->
+
+    <!-- Software tools used -->
+        <article type="platform"/>
+        <article type="module"/>
+        <article type="component"/>
+    </contexts>
+
+
+<!-- 5. Knowledge Elements types
+
+     Warning: The Knowledge Elements type "usecase" is reserved for internal use.
+     -->
+    <knowledges>
+        <article type="bestpractice"/>
+        <article type="limitation"/>
+        <article type="inconsistency"/>
+        <article type="metrics"/>
+        <article type="improvement"/>
+    </knowledges>
+
+
+<!-- 6. User activities
+
+     Remarks:
+     - Step names must naturally be unique.
+     - Simulation Contexts must be attached to one classification step only.
+     - Result document types must be results of one step only and be part of contents of the corresponding step.
+     -->
+    <activities>
+        <step name="specification">
+            <classification context="customer,product,phase,need,purpose,physic"/>
+            <flow contents="requirements,specification,minutes" result="specification"/>
+            <storage path="1.Study"/>
+        </step>
+      <scenario>
+        <step name="design">
+            <flow contents="design,memorandum,minutes" result="design"/>
+            <storage path="1.Study"/>
+        </step>
+        <step name="modeling">
+            <classification context="object,part,geometry"/>
+            <flow contents="geometry,memorandum,minutes" result="geometry"/>
+            <storage path="2.Geometry"/>
+            <module name="GEOM"/>
+   	    </step>
+        <step name="meshing">
+            <classification context="model,element,shape,order"/>
+            <flow contents="model,memorandum,minutes" result="model"/>
+            <storage path="3.Mesh"/>
+            <module name="SMESH"/>
+        </step>
+        <step name="meca">
+            <classification context="loads,script,platform,module,component"/>
+            <flow contents="loads,model,log,minutes,resultsMeca" result="resultsMeca"/>
+            <storage path="5.Result"/>
+            <module name="SALOME_MECA"/>
+        </step>
+        <step name="syrthes">
+            <classification context="loads,script,platform,module,component"/>
+            <flow contents="loads,model,log,minutes,resultsSyrthes" result="resultsSyrthes"/>
+            <storage path="5.Result"/>
+            <module name="SYRTHES"/>
+        </step>
+        <step name="postprocessing">
+            <flow contents="memorandum,minutes,coparisonResult,visualisation" result="coparisonResult"/>
+            <storage path="6.Report"/>
+            <module name="VISU"/>
+        </step>
+        <step name="schema">
+            <flow contents="schema" result="schema"/>
+            <storage path="7.Schema"/>
+            <module name="YACS"/>
+        </step>
+        <step name="capitalization">
+            <flow contents="knowledge"/>
+            <storage path="8.Summary"/>
+        </step>
+      </scenario>
+        <step name="reporting">
+            <flow contents="report,minutes" result="report"/>
+            <storage path="1.Study"/>
+        </step>
+    </activities>
+
+
+<!-- 6. Document validation cycles
+     Validation cycles define the actors involved in the validation steps of documents. These steps can be
+     "review", "approval" and "acceptance".
+     Remarks:
+     - Each validation cycle is defined by a tag corresponding to the type of an activity result document.
+     - The actors of validation steps can be
+       "manager", referring the responsible of study,
+       "Nx1", referring the manager of the department (see User definition for more information),
+       "Nx2", referring the boss of the department manager,
+       "customer" (most likely involved in the acceptance step).
+     -->
+    <validations>
+        <specification  review="Nx1"  approval="Nx2"/>
+        <report         review="Nx1"  approval="Nx2"/>
+        <default        review="manager"            />
+    </validations>
+
+<!-- 3. Check-in check-out information
+     Defines the way documents involved in the check-in check-out operations must be processed.
+     Files with import formats are automatically imported into SALOME during check-out if they are uptodate.
+     Other files are downloaded.
+     -->
+    <mappings>
+        <document type="geometry">
+            <import format="brep"/>     <!-- Result Shape                             -->
+        </document>
+        <document type="model">
+            <import format="med"/>      <!-- Result mesh without input parameters     -->
+            <import format="mmed"/>      <!-- Result mesh without input parameters     -->
+        </document>
+        <document type="loads">
+            <import format="model"/>    <!-- Input data created interactively         -->
+            <import format="comm"/>      <!-- Input data created interactively         -->
+            <import format="syd"/>      <!-- Input data created interactively         -->
+        </document>
+        <document type="resultsMeca">
+            <import format="resu"/>      <!-- Calculation results source file          -->
+            <import format="mess"/>      <!-- Calculation results source file          -->
+            <import format="rmed"/>      <!-- Calculation results source file          -->
+            <import format="bz2"/>      <!-- Calculation results source file          -->
+        </document>
+        <document type="resultsSyrthes">
+            <import format="bz2"/>      <!-- Calculation results source file          -->
+        </document>
+        <document type="schema">
+            <import format="xml"/>      <!-- Calculation results source file          -->
+        </document>
+    </mappings>
+    
+    <default-doctypes>
+        <step number="1">
+            <mapping extension="pdf"    type="requirements"/>
+            <mapping extension="doc"    type="specification"/>     <!-- Microsoft Word 2003 and earlier -->
+            <mapping extension="docx"   type="specification"/>     <!-- Microsoft Word 2007 and later   -->
+            <mapping extension="xml"    type="specification"/>     <!-- Microsoft Word 2007 Open XML    -->
+        </step>
+        <step number="2">
+            <mapping extension="doc"    type="design"/>
+            <mapping extension="docx"   type="design"/>
+            <mapping extension="xml"    type="design"/>
+        </step>
+        <step number="3">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="sldprt" type="geometry"/>          <!-- SolidWorks Part                 -->
+            <mapping extension="sldasm" type="geometry"/>          <!-- SolidWorks Assembly             -->
+            <mapping extension="part"   type="geometry"/>          <!-- GEOM Part                       -->
+            <mapping extension="py"     type="geometry"/>          <!-- GEOM Python script              -->
+            <mapping extension="brep"   type="geometry"/>          <!-- GEOM Part                       -->
+        </step>
+        <step number="4">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="med"    type="model"/>
+            <mapping extension="mmed"   type="model"/>
+            <mapping extension="py"     type="model"/>             <!-- SMESH Python script             -->
+        </step>
+        <step number="5"> <!-- execute the calculations -->
+        	<mapping extension="med"    type="model"/>
+        	<mapping extension="model"  type="loads"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="6">
+            <mapping extension="comm"    type="loads"/>
+            <mapping extension="resu"    type="resultsMeca"/>
+            <mapping extension="mess"    type="resultsMeca"/>
+            <mapping extension="rmed"    type="resultsMeca"/>
+            <mapping extension="bz2"     type="resultsMeca"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="7">
+            <mapping extension="syd"    type="loads"/>
+            <mapping extension="bz2"    type="resultsSyrthes"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="8">
+            <mapping extension="srd"    type="coparisonResult"/>
+            <mapping extension="py"     type="visualisation"/>
+        </step>
+        <step number="9">
+            <mapping extension="xml"    type="schema"/>
+        </step>
+    </default-doctypes>
+    
+</project-structure>
\ No newline at end of file
diff --git a/Workspace/Siman-WS/conf/edf_som_en.properties b/Workspace/Siman-WS/conf/edf_som_en.properties
new file mode 100644
index 0000000..9687ac2
--- /dev/null
+++ b/Workspace/Siman-WS/conf/edf_som_en.properties
@@ -0,0 +1,21 @@
+menu.step.1   = Specify the study
+menu.step.2   = Design the scenario
+menu.step.3   = Create the geometry
+menu.step.4   = Generate the analysis model
+menu.step.5   = Execute MECA
+menu.step.6   = Execute SYRTHES
+menu.step.7   = Analyze the results
+menu.step.8   = Define the calculation schema
+menu.step.9   = Capitalize this use-case
+menu.step.10   = Finalize the study
+
+folder.step.1 = Specification of the study
+folder.step.2 = Description of the scenario
+folder.step.3 = Geometry
+folder.step.4 = Analysis model
+folder.step.5 = MECA calculation execution
+folder.step.6 = SYRTHES calculation execution
+folder.step.7 = Calculation results
+folder.step.8 = Calculation schema
+folder.step.9 = Knowledge elements
+folder.step.10 = Final report
diff --git a/Workspace/Siman-WS/conf/templates/som.properties b/Workspace/Siman-WS/conf/templates/som.properties
new file mode 100644
index 0000000..fea4d6b
--- /dev/null
+++ b/Workspace/Siman-WS/conf/templates/som.properties
@@ -0,0 +1,52 @@
+name.module   = Centre d''études
+
+size.format   = #,##0 Ko
+date.format   = dd/MM/yyyy
+dd/MM/yyyy    = jj/mm/aaaa
+
+@som@
+
+type.document.requirements   = Cahier des charges
+type.document.specification  = Document de spécification
+type.document.design         = Document de conception
+type.document.geometry       = Géométrie
+type.document.model          = Modèle d''analyse
+type.document.loads          = Conditions de calcul
+type.document.script         = Script d''exécution
+type.document.log            = Log d''exécution
+type.document.results        = Résultats de calcul
+type.document.resultsMeca    = Résultats de calcul MECA
+type.document.resultsSyrthes = Résultats de calcul Syrthes
+type.document.report         = Rapport final
+type.document.memorandum     = Note technique
+type.document.minutes        = Compte rendu
+type.document.coparisonResult= Study comparison result
+type.document.schema         = Calculation schema
+type.document.visualisation  = Visualisation of the results
+
+type.context.customer        = Client
+type.context.product         = Produit
+type.context.phase           = Phase du produit
+type.context.need            = Besoin client
+type.context.purpose         = Finalité de l''étude
+type.context.physic          = Type de physique
+type.context.object          = Objet étudié
+type.context.part            = Objet modélisé
+type.context.geometry        = Type de géométrie
+type.context.model           = Type de modèle
+type.context.element         = Type d''éléments
+type.context.shape           = Géométrie des éléments
+type.context.order           = Degré des éléments
+type.context.analysis        = Type d''analyse
+type.context.platform        = Plate-forme logicielle
+type.context.module          = Module de calcul
+type.context.component       = Brique technologique
+
+type.knowledge.usecase       = Use case
+type.knowledge.bestpractice  = Bonne pratique
+type.knowledge.limitation    = Limitation
+type.knowledge.inconsistency = Incohérence
+type.knowledge.metrics       = Métrique
+type.knowledge.improvement   = Amélioration
+
+history.creation = Document créé par
\ No newline at end of file
diff --git a/Workspace/Siman-WS/conf/templates/som_en.properties b/Workspace/Siman-WS/conf/templates/som_en.properties
new file mode 100644
index 0000000..be64dae
--- /dev/null
+++ b/Workspace/Siman-WS/conf/templates/som_en.properties
@@ -0,0 +1,53 @@
+name.module   = Study Manager
+
+size.format   = #,##0 Kb
+date.format   = MM.dd.yyyy
+MM.dd.yyyy    = mm.dd.yyyy
+
+@som.en@
+
+type.document.requirements   = Customer requirements
+type.document.specification  = Specification document
+type.document.design         = Design document
+type.document.geometry       = Geometry
+type.document.model          = Analysis model
+type.document.loads          = Boundary conditions
+type.document.script         = Execution script
+type.document.log            = Execution log
+type.document.results        = Calculation results
+type.document.resultsMeca    = MECA calculation results
+type.document.resultsSyrthes = Syrthes calculation results
+type.document.report         = Final report
+type.document.memorandum     = Technical report
+type.document.minutes        = Minute meeting
+type.document.coparisonResult= Study comparison result
+type.document.schema         = Calculation schema
+type.document.visualisation  = Visualisation of the results
+
+type.context.customer        = Customer
+type.context.product         = Product
+type.context.phase           = Product phase
+type.context.need            = Customer needs
+type.context.purpose         = Purpose of study
+type.context.physic          = Physics
+type.context.object          = Studied object
+
+type.context.part            = Modeled object
+type.context.geometry        = Geometry type
+type.context.model           = Type of analysis model
+type.context.element         = Element type
+type.context.shape           = Geometry of elements
+type.context.order           = Order of elements
+type.context.analysis        = Analysis type
+type.context.platform        = Software platform
+type.context.module          = Solver
+type.context.component       = Software component
+
+type.knowledge.usecase       = Use case
+type.knowledge.bestpractice  = Best practice
+type.knowledge.limitation    = Limitation
+type.knowledge.inconsistency = Inconsistency
+type.knowledge.metrics       = Metrics
+type.knowledge.improvement   = Improvement
+
+history.creation = Document created by
\ No newline at end of file
diff --git a/Workspace/Siman/WebContent/conf/my.xml b/Workspace/Siman/WebContent/conf/my.xml
index e14a992..986e5f4 100644
--- a/Workspace/Siman/WebContent/conf/my.xml
+++ b/Workspace/Siman/WebContent/conf/my.xml
@@ -10,6 +10,17 @@
         <mapping extension="med"    executable="runSalome"/>
         <mapping extension="py"    executable="runSalome"/>
         <!--mapping extension="xml"    executable="runSalome"/--> <!-- for YAKS activity -->
+
+        <!-- CASTEM -->
+        <mapping extension="model"  executable="runSalome"/>
+        <!-- MECA -->
+        <mapping extension="syd"    executable="runSalome"/>
+        <mapping extension="bz2"    executable="runSalome"/>
+        <!-- SYRTHES -->
+        <mapping extension="comm"    executable="runSalome"/>
+        <mapping extension="resu"    executable="runSalome"/>
+        <mapping extension="mess"    executable="runSalome"/>
+        <mapping extension="rmed"    executable="runSalome"/>
     </modules>
 
     <viewers extension="pdf,brep,med" />
diff --git a/Workspace/Siman/build.xml b/Workspace/Siman/build.xml
index 82494cf..d585c6d 100644
--- a/Workspace/Siman/build.xml
+++ b/Workspace/Siman/build.xml
@@ -59,12 +59,18 @@
 		<sequential>
 			<echo message="Generating configuration in @{mode} mode" />
 			<!-- Copy files from config source directory according to the given mode -->
+            <loadfile property="customer" srcfile="${config.src.dir}/customer.txt"/>
+            <loadfile property="som" srcfile="${config.src.dir}/${customer}_som.properties"/>
+			<echo message="som: ${som}"/>
+            <loadfile property="som.en" srcfile="${config.src.dir}/${customer}_som_en.properties"/>
 			<copy todir="${basedir}/${config.@{mode}.dir}" overwrite="true">
 				<fileset dir="${config.src.dir}/templates">
 				</fileset>
 				<!-- Transform the files from templates substituting properties values -->
 				<filterset>
-					<filter token="datesimple" value="${datesimple}" />
+                    <filter token="som" value="${som}" />
+                    <filter token="som.en" value="${som.en}" />
+                    <filter token="datesimple" value="${datesimple}" />
 					<filter token="time" value="${time}" />
 					<!-- Get properties to substitute according to the given mode -->
 					<filtersfile file="${config.src.dir}/@{mode}.properties" />
@@ -151,8 +157,8 @@
     <!-- ================================================= -->
     <target name="prepare-postgres" description="prepare configuration for Postgress">
         <echo message="Prepare configuration for Postgress..." />
-        <copy file="conf/debug_pg.properties" tofile="conf/debug.properties" overwrite="true"/>
-        <copy file="conf/release_pg.properties" tofile="conf/release.properties" overwrite="true"/>
+        <copy file="${config.src.dir}/debug_pg.properties" tofile="${config.src.dir}/debug.properties" overwrite="true"/>
+        <copy file="${config.src.dir}/release_pg.properties" tofile="${config.src.dir}/release.properties" overwrite="true"/>
         <antcall target="debug-config"/>
     </target>
 	
@@ -161,8 +167,38 @@
     <!-- ================================================= -->
     <target name="prepare-mysql" description="prepare configuration for MySql">
         <echo message="Prepare configuration for MySql..." />
-        <copy file="conf/debug_mysql.properties" tofile="conf/debug.properties" overwrite="true"/>
-        <copy file="conf/release_mysql.properties" tofile="conf/release.properties" overwrite="true"/>
+        <copy file="${config.src.dir}/debug_mysql.properties" tofile="${config.src.dir}/debug.properties" overwrite="true"/>
+        <copy file="${config.src.dir}/release_mysql.properties" tofile="${config.src.dir}/release.properties" overwrite="true"/>
         <antcall target="debug-config"/>
     </target>
+
+    <!-- ================================================= -->
+    <!--    prepare-customer: Prepare config for the given customer -->
+    <!-- ================================================= -->
+    <macrodef name="prepare-customer">
+        <!-- Parameter "customer" can be equal to "cea" or "edf" -->
+        <attribute name="customer" />
+        <sequential>
+            <echo message="Prepare config for the customer @{customer}" />
+            <echo message="@{customer}" file="${config.src.dir}/customer.txt"/>
+            <copy file="${config.src.dir}/@{customer}_som.xml" tofile="WebContent/conf/som.xml" overwrite="true"/>
+            <antcall target="debug-config"/>
+        </sequential>
+    </macrodef>
+	
+    <!-- ================================================= -->
+    <!--    prepare-cea: Prepare config for CEA            -->
+    <!-- ================================================= -->
+    <target name="prepare-cea" description="prepare configuration for CEA">
+        <echo message="Prepare configuration for CEA..." />
+        <prepare-customer customer="cea" />
+    </target>
+
+    <!-- ================================================= -->
+    <!--    prepare-cea: Prepare config for EDF            -->
+    <!-- ================================================= -->
+    <target name="prepare-edf" description="prepare configuration for EDF">
+        <echo message="Prepare configuration for EDF..." />
+        <prepare-customer customer="edf" />
+    </target>
 </project>
diff --git a/Workspace/Siman/conf/cea_som.properties b/Workspace/Siman/conf/cea_som.properties
new file mode 100644
index 0000000..49e8a96
--- /dev/null
+++ b/Workspace/Siman/conf/cea_som.properties
@@ -0,0 +1,19 @@
+menu.step.1   = Spécifier l''étude
+menu.step.2   = Concevoir le scénario
+menu.step.3   = Créer la géométrie
+menu.step.4   = Générer le modèle d''analyse
+menu.step.5   = Entrer les conditions de calcul
+menu.step.6   = Analyser les résultats
+menu.step.7   = Définir le schéma de calcul
+menu.step.8   = Capitaliser ce cas d''étude
+menu.step.9   = Finaliser l''étude
+
+folder.step.1 = Spécification de l''étude
+folder.step.2 = Description du scénario
+folder.step.3 = Géométrie
+folder.step.4 = Modèle d''analyse
+folder.step.5 = Conditions de calcul
+folder.step.6 = Résultats
+folder.step.7 = Schéma de calcul
+folder.step.8 = Élements de connaissances
+folder.step.9 = Rapport final
diff --git a/Workspace/Siman/conf/cea_som.xml b/Workspace/Siman/conf/cea_som.xml
new file mode 100644
index 0000000..3115e34
--- /dev/null
+++ b/Workspace/Siman/conf/cea_som.xml
@@ -0,0 +1,270 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<project-structure>
+
+
+<!-- 1. Database physical location
+     -->
+    <database>
+		<repository disk="/home/siman/Repository" />
+    </database>
+
+
+<!-- 2. Formats
+     -->
+    <formats>
+
+<!-- 2.1 Project elements identification scheme
+     Studies, Knowledges and Documents are identified by unique user references. The structure of these references is customizable.
+     You customize references through patterns.
+     A reference's pattern is a character string including format directives. These format directives allow you to insert
+     some information into the reference. The following directives are available:
+     - %yy or %yyyy for inserting the entity creation year on 2 or 4 digits
+     - %0000 for inserting a unique index, the number of digits being defined by the number of 0
+     The above index is unique in the scope of cycle defined by the first format directive (year). In other words, this index
+     restarts every new year. As such, for making references unique on this application server, both format directives (cycle
+     and index) must be present in the pattern.
+     Other characters are simply inserted as is in generated references. They can be used for extending the reference uniqueness
+     beyond application servers, by adding a prefix specific to a given server (for example, a company department name).
+     Given that these references may be used as directory or file names of the repository vault, the pattern must not include
+     illicit characters such as '/', '?', '<' etc.
+     -->
+        <references  study="DER%yy%0000"/>
+
+<!-- 2.2 Physical files naming scheme
+     The physical data files stored into the repository vault can be named as follows:
+     - By the user-defined title of corresponding documents ("title" name attribute below)
+     - Encoded by a built-in scheme ("encoded" name attribute)
+     - As is, that is, by keeping the name of the imported file ("asis" name attribute - not yet supported)
+     Remarks:
+     - When using the title scheme, as file names may include accent characters, client browsers must be configured for
+       NOT encoding URLs as UTF-8.
+     - Whatever is the naming scheme used, in order to avoid name clashes, file names are anyway suffixed by an index
+       unique in the scope of the owner study.
+     -->
+        <files name="asis"/>
+
+<!-- 2.3 Document versions format
+     -->
+        <versions pattern="%M.%m[-%s]"/>
+    </formats>
+
+
+<!-- 3. Document types
+
+     Warning: Articles must be ordered in a way that used document types (uses attribute values) must previously be defined.
+     Example: "requirements" type must be defined before "specification" because "specification" uses "requirements".
+     Remarks:
+     - "knowledge" is a reserved word qualifying Knowledge Elements. So, it must not be used as a document type name.
+     - "default" and "built-in" are also reserved words used for defining validation cycles.
+     - In this version, the "uses" attribute is limited to 1 document type only.
+     -->
+    <documents>
+        <article type="requirements"/>
+        <article type="specification" uses="requirements"/>
+        <article type="design"        uses="specification"/>
+        <article type="geometry"      uses="design"/>
+        <article type="model"         uses="geometry"/>
+        <article type="loads"         uses="model"/>
+        <article type="script"        uses="loads"/>
+        <article type="log"           uses="script"/>
+        <article type="results"       uses="script"/>
+        <article type="report"        uses="results"/>
+        <article type="schema"/>
+        <article type="memorandum"/>
+        <article type="minutes"/>
+        <article type="coparisonResult"/>
+        <article type="visualisation"/>
+    </documents>
+
+
+<!-- 4. Simulation Context types
+
+     Warning: The Simulation Context type "product" is mandatory as it is used by at least one application.
+     -->
+    <contexts>
+
+    <!-- General information -->
+        <article type="customer"/>
+        <article type="product"/>
+        <article type="phase"/>            <!-- Phase of the product                                 -->
+        <article type="need"/>             <!-- Customer needs                                       -->
+        <article type="purpose"/>          <!-- Objective of the study                               -->
+        <article type="physic"/>           <!-- Structure analysis, Thermal-hydraulics, Neutronic... -->
+
+    <!-- Geometry characteristics               Examples:                 -->
+        <article type="object"/>           <!-- Car, Plane, Equipment...  -->
+        <article type="part"/>             <!-- Crankcase, Outer layer... -->
+        <article type="geometry"/>         <!-- Surface, Volume           -->
+
+    <!-- Model characteristics                  Examples:            -->
+        <article type="model"/>            <!-- CSG, FEM...          -->
+        <article type="element"/>          <!-- Bar, Surface, Volume -->
+        <article type="shape"/>            <!-- (Surface) Triangle, Quadrangle... (Volume) Tetrahedron, Hexahedron... -->
+        <article type="order"/>            <!-- First-order, Second-order... -->
+
+    <!-- Analysis type                          Examples:          -->
+        <article type="analysis"/>         <!-- Static, Dynamic... -->
+
+    <!-- Software tools used -->
+        <article type="platform"/>
+        <article type="module"/>
+        <article type="component"/>
+    </contexts>
+
+
+<!-- 5. Knowledge Elements types
+
+     Warning: The Knowledge Elements type "usecase" is reserved for internal use.
+     -->
+    <knowledges>
+        <article type="bestpractice"/>
+        <article type="limitation"/>
+        <article type="inconsistency"/>
+        <article type="metrics"/>
+        <article type="improvement"/>
+    </knowledges>
+
+
+<!-- 6. User activities
+
+     Remarks:
+     - Step names must naturally be unique.
+     - Simulation Contexts must be attached to one classification step only.
+     - Result document types must be results of one step only and be part of contents of the corresponding step.
+     -->
+    <activities>
+        <step name="specification">
+            <classification context="customer,product,phase,need,purpose,physic"/>
+            <flow contents="requirements,specification,minutes" result="specification"/>
+            <storage path="1.Study"/>
+        </step>
+      <scenario>
+        <step name="design">
+            <flow contents="design,memorandum,minutes" result="design"/>
+            <storage path="1.Study"/>
+        </step>
+        <step name="modeling">
+            <classification context="object,part,geometry"/>
+            <flow contents="geometry,memorandum,minutes" result="geometry"/>
+            <storage path="2.Geometry"/>
+            <module name="GEOM"/>
+   	    </step>
+        <step name="meshing">
+            <classification context="model,element,shape,order"/>
+            <flow contents="model,memorandum,minutes" result="model"/>
+            <storage path="3.Mesh"/>
+            <module name="SMESH"/>
+        </step>
+        <step name="solving">
+            <classification context="loads,script,platform,module,component"/>
+            <flow contents="loads,model,log,results,minutes" result="results"/>
+            <storage path="5.Result"/>
+            <module name="CASTEM"/>
+        </step>
+        <step name="postprocessing">
+            <flow contents="memorandum,minutes,coparisonResult,visualisation" result="coparisonResult"/>
+            <storage path="6.Report"/>
+            <module name="VISU"/>
+        </step>
+        <step name="schema">
+            <flow contents="schema" result="schema"/>
+            <storage path="7.Schema"/>
+            <module name="YACS"/>
+        </step>
+        <step name="capitalization">
+            <flow contents="knowledge"/>
+            <storage path="8.Summary"/>
+        </step>
+      </scenario>
+        <step name="reporting">
+            <flow contents="report,minutes" result="report"/>
+            <storage path="1.Study"/>
+        </step>
+    </activities>
+
+
+<!-- 6. Document validation cycles
+     Validation cycles define the actors involved in the validation steps of documents. These steps can be
+     "review", "approval" and "acceptance".
+     Remarks:
+     - Each validation cycle is defined by a tag corresponding to the type of an activity result document.
+     - The actors of validation steps can be
+       "manager", referring the responsible of study,
+       "Nx1", referring the manager of the department (see User definition for more information),
+       "Nx2", referring the boss of the department manager,
+       "customer" (most likely involved in the acceptance step).
+     -->
+    <validations>
+        <specification  review="Nx1"  approval="Nx2"/>
+        <report         review="Nx1"  approval="Nx2"/>
+        <default        review="manager"            />
+    </validations>
+
+<!-- 3. Check-in check-out information
+     Defines the way documents involved in the check-in check-out operations must be processed.
+     Files with import formats are automatically imported into SALOME during check-out if they are uptodate.
+     Other files are downloaded.
+     -->
+    <mappings>
+        <document type="geometry">
+            <import format="brep"/>     <!-- Result Shape                             -->
+        </document>
+        <document type="model">
+            <import format="med"/>      <!-- Result mesh without input parameters     -->
+        </document>
+        <document type="loads">
+            <import format="model"/>    <!-- Input data created interactively         -->
+        </document>
+        <document type="results">
+            <import format="med"/>      <!-- Calculation results source file          -->
+        </document>
+        <document type="schema">
+            <import format="xml"/>      <!-- Calculation results source file          -->
+        </document>
+    </mappings>
+    
+    <default-doctypes>
+        <step number="1">
+            <mapping extension="pdf"    type="requirements"/>
+            <mapping extension="doc"    type="specification"/>     <!-- Microsoft Word 2003 and earlier -->
+            <mapping extension="docx"   type="specification"/>     <!-- Microsoft Word 2007 and later   -->
+            <mapping extension="xml"    type="specification"/>     <!-- Microsoft Word 2007 Open XML    -->
+        </step>
+        <step number="2">
+            <mapping extension="doc"    type="design"/>
+            <mapping extension="docx"   type="design"/>
+            <mapping extension="xml"    type="design"/>
+        </step>
+        <step number="3">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="sldprt" type="geometry"/>          <!-- SolidWorks Part                 -->
+            <mapping extension="sldasm" type="geometry"/>          <!-- SolidWorks Assembly             -->
+            <mapping extension="part"   type="geometry"/>          <!-- GEOM Part                       -->
+            <mapping extension="py"     type="geometry"/>          <!-- GEOM Python script              -->
+            <mapping extension="brep"   type="geometry"/>          <!-- GEOM Part                       -->
+        </step>
+        <step number="4">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="med"    type="model"/>
+            <mapping extension="py"     type="model"/>             <!-- SMESH Python script             -->
+        </step>
+        <step number="5"> <!-- execute the calculations -->
+        	<mapping extension="med"    type="model"/>
+        	<mapping extension="model"  type="loads"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="6">
+            <mapping extension="srd"    type="coparisonResult"/>
+            <mapping extension="py"     type="visualisation"/>
+        </step>
+        <step number="7">
+            <mapping extension="xml"    type="schema"/>
+        </step>
+    </default-doctypes>
+    
+</project-structure>
\ No newline at end of file
diff --git a/Workspace/Siman/conf/cea_som_en.properties b/Workspace/Siman/conf/cea_som_en.properties
new file mode 100644
index 0000000..2dc696a
--- /dev/null
+++ b/Workspace/Siman/conf/cea_som_en.properties
@@ -0,0 +1,19 @@
+menu.step.1   = Specify the study
+menu.step.2   = Design the scenario
+menu.step.3   = Create the geometry
+menu.step.4   = Generate the analysis model
+menu.step.5   = Enter the boundary conditions
+menu.step.6   = Analyze the results
+menu.step.7   = Define the calculation schema
+menu.step.8   = Capitalize this use-case
+menu.step.9   = Finalize the study
+
+folder.step.1 = Specification of the study
+folder.step.2 = Description of the scenario
+folder.step.3 = Geometry
+folder.step.4 = Analysis model
+folder.step.5 = Boundary conditions
+folder.step.6 = Calculation results
+folder.step.7 = Calculation schema
+folder.step.8 = Knowledge elements
+folder.step.9 = Final report
diff --git a/Workspace/Siman/conf/customer.txt b/Workspace/Siman/conf/customer.txt
new file mode 100644
index 0000000..b1121e1
--- /dev/null
+++ b/Workspace/Siman/conf/customer.txt
@@ -0,0 +1 @@
+cea
\ No newline at end of file
diff --git a/Workspace/Siman/conf/edf_som.properties b/Workspace/Siman/conf/edf_som.properties
new file mode 100644
index 0000000..b3971c8
--- /dev/null
+++ b/Workspace/Siman/conf/edf_som.properties
@@ -0,0 +1,23 @@
+menu.step.1   = Spécifier l''étude
+menu.step.2   = Concevoir le scénario
+menu.step.3   = Créer la géométrie
+menu.step.4   = Générer le modèle d''analyse
+menu.step.5   = Effectuer le CASTEM
+menu.step.6   = Effectuer le MECA
+menu.step.7   = Effectuer le SYRTHES
+menu.step.8   = Analyser les résultats
+menu.step.9   = Définir le schéma de calcul
+menu.step.10   = Capitaliser ce cas d''étude
+menu.step.11   = Finaliser l''étude
+
+folder.step.1 = Spécification de l''étude
+folder.step.2 = Description du scénario
+folder.step.3 = Géométrie
+folder.step.4 = Modèle d''analyse
+folder.step.5 = Exécution de calcul CASTEM
+folder.step.6 = Exécution de calcul MECA
+folder.step.7 = Exécution de calcul SYRTHES
+folder.step.8 = Résultats
+folder.step.9 = Schéma de calcul
+folder.step.10 = Élements de connaissances
+folder.step.11 = Rapport final
diff --git a/Workspace/Siman/conf/edf_som.xml b/Workspace/Siman/conf/edf_som.xml
new file mode 100644
index 0000000..a1e84ae
--- /dev/null
+++ b/Workspace/Siman/conf/edf_som.xml
@@ -0,0 +1,300 @@
+<?xml version="1.0" encoding="UTF-8"?>
+
+<project-structure>
+
+
+<!-- 1. Database physical location
+     -->
+    <database>
+        <repository disk="/home/siman/Repository" />
+    </database>
+
+
+<!-- 2. Formats
+     -->
+    <formats>
+
+<!-- 2.1 Project elements identification scheme
+     Studies, Knowledges and Documents are identified by unique user references. The structure of these references is customizable.
+     You customize references through patterns.
+     A reference's pattern is a character string including format directives. These format directives allow you to insert
+     some information into the reference. The following directives are available:
+     - %yy or %yyyy for inserting the entity creation year on 2 or 4 digits
+     - %0000 for inserting a unique index, the number of digits being defined by the number of 0
+     The above index is unique in the scope of cycle defined by the first format directive (year). In other words, this index
+     restarts every new year. As such, for making references unique on this application server, both format directives (cycle
+     and index) must be present in the pattern.
+     Other characters are simply inserted as is in generated references. They can be used for extending the reference uniqueness
+     beyond application servers, by adding a prefix specific to a given server (for example, a company department name).
+     Given that these references may be used as directory or file names of the repository vault, the pattern must not include
+     illicit characters such as '/', '?', '<' etc.
+     -->
+        <references  study="DER%yy%0000"/>
+
+<!-- 2.2 Physical files naming scheme
+     The physical data files stored into the repository vault can be named as follows:
+     - By the user-defined title of corresponding documents ("title" name attribute below)
+     - Encoded by a built-in scheme ("encoded" name attribute)
+     - As is, that is, by keeping the name of the imported file ("asis" name attribute - not yet supported)
+     Remarks:
+     - When using the title scheme, as file names may include accent characters, client browsers must be configured for
+       NOT encoding URLs as UTF-8.
+     - Whatever is the naming scheme used, in order to avoid name clashes, file names are anyway suffixed by an index
+       unique in the scope of the owner study.
+     -->
+        <files name="asis"/>
+
+<!-- 2.3 Document versions format
+     -->
+        <versions pattern="%M.%m[-%s]"/>
+    </formats>
+
+
+<!-- 3. Document types
+
+     Warning: Articles must be ordered in a way that used document types (uses attribute values) must previously be defined.
+     Example: "requirements" type must be defined before "specification" because "specification" uses "requirements".
+     Remarks:
+     - "knowledge" is a reserved word qualifying Knowledge Elements. So, it must not be used as a document type name.
+     - "default" and "built-in" are also reserved words used for defining validation cycles.
+     - In this version, the "uses" attribute is limited to 1 document type only.
+     -->
+    <documents>
+        <article type="requirements"/>
+        <article type="specification" uses="requirements"/>
+        <article type="design"        uses="specification"/>
+        <article type="geometry"      uses="design"/>
+        <article type="model"         uses="geometry"/>
+        <article type="loads"         uses="model"/>
+        <article type="script"        uses="loads"/>
+        <article type="log"           uses="script"/>
+        <article type="resultsMeca"   uses="script"/>
+        <article type="resultsSyrthes" uses="script"/>
+        <article type="report"        uses="resultsMeca, resultsSyrthes"/>
+        <article type="schema"/>
+        <article type="memorandum"/>
+        <article type="minutes"/>
+        <article type="coparisonResult"/>
+        <article type="visualisation"/>
+    </documents>
+
+
+<!-- 4. Simulation Context types
+
+     Warning: The Simulation Context type "product" is mandatory as it is used by at least one application.
+     -->
+    <contexts>
+
+    <!-- General information -->
+        <article type="customer"/>
+        <article type="product"/>
+        <article type="phase"/>            <!-- Phase of the product                                 -->
+        <article type="need"/>             <!-- Customer needs                                       -->
+        <article type="purpose"/>          <!-- Objective of the study                               -->
+        <article type="physic"/>           <!-- Structure analysis, Thermal-hydraulics, Neutronic... -->
+
+    <!-- Geometry characteristics               Examples:                 -->
+        <article type="object"/>           <!-- Car, Plane, Equipment...  -->
+        <article type="part"/>             <!-- Crankcase, Outer layer... -->
+        <article type="geometry"/>         <!-- Surface, Volume           -->
+
+    <!-- Model characteristics                  Examples:            -->
+        <article type="model"/>            <!-- CSG, FEM...          -->
+        <article type="element"/>          <!-- Bar, Surface, Volume -->
+        <article type="shape"/>            <!-- (Surface) Triangle, Quadrangle... (Volume) Tetrahedron, Hexahedron... -->
+        <article type="order"/>            <!-- First-order, Second-order... -->
+
+    <!-- Analysis type                          Examples:          -->
+        <article type="analysis"/>         <!-- Static, Dynamic... -->
+
+    <!-- Software tools used -->
+        <article type="platform"/>
+        <article type="module"/>
+        <article type="component"/>
+    </contexts>
+
+
+<!-- 5. Knowledge Elements types
+
+     Warning: The Knowledge Elements type "usecase" is reserved for internal use.
+     -->
+    <knowledges>
+        <article type="bestpractice"/>
+        <article type="limitation"/>
+        <article type="inconsistency"/>
+        <article type="metrics"/>
+        <article type="improvement"/>
+    </knowledges>
+
+
+<!-- 6. User activities
+
+     Remarks:
+     - Step names must naturally be unique.
+     - Simulation Contexts must be attached to one classification step only.
+     - Result document types must be results of one step only and be part of contents of the corresponding step.
+     -->
+    <activities>
+        <step name="specification">
+            <classification context="customer,product,phase,need,purpose,physic"/>
+            <flow contents="requirements,specification,minutes" result="specification"/>
+            <storage path="1.Study"/>
+        </step>
+      <scenario>
+        <step name="design">
+            <flow contents="design,memorandum,minutes" result="design"/>
+            <storage path="1.Study"/>
+        </step>
+        <step name="modeling">
+            <classification context="object,part,geometry"/>
+            <flow contents="geometry,memorandum,minutes" result="geometry"/>
+            <storage path="2.Geometry"/>
+            <module name="GEOM"/>
+   	    </step>
+        <step name="meshing">
+            <classification context="model,element,shape,order"/>
+            <flow contents="model,memorandum,minutes" result="model"/>
+            <storage path="3.Mesh"/>
+            <module name="SMESH"/>
+        </step>
+        <step name="meca">
+            <classification context="loads,script,platform,module,component"/>
+            <flow contents="loads,model,log,minutes,resultsMeca" result="resultsMeca"/>
+            <storage path="5.Result"/>
+            <module name="SALOME_MECA"/>
+        </step>
+        <step name="syrthes">
+            <classification context="loads,script,platform,module,component"/>
+            <flow contents="loads,model,log,minutes,resultsSyrthes" result="resultsSyrthes"/>
+            <storage path="5.Result"/>
+            <module name="SYRTHES"/>
+        </step>
+        <step name="postprocessing">
+            <flow contents="memorandum,minutes,coparisonResult,visualisation" result="coparisonResult"/>
+            <storage path="6.Report"/>
+            <module name="VISU"/>
+        </step>
+        <step name="schema">
+            <flow contents="schema" result="schema"/>
+            <storage path="7.Schema"/>
+            <module name="YACS"/>
+        </step>
+        <step name="capitalization">
+            <flow contents="knowledge"/>
+            <storage path="8.Summary"/>
+        </step>
+      </scenario>
+        <step name="reporting">
+            <flow contents="report,minutes" result="report"/>
+            <storage path="1.Study"/>
+        </step>
+    </activities>
+
+
+<!-- 6. Document validation cycles
+     Validation cycles define the actors involved in the validation steps of documents. These steps can be
+     "review", "approval" and "acceptance".
+     Remarks:
+     - Each validation cycle is defined by a tag corresponding to the type of an activity result document.
+     - The actors of validation steps can be
+       "manager", referring the responsible of study,
+       "Nx1", referring the manager of the department (see User definition for more information),
+       "Nx2", referring the boss of the department manager,
+       "customer" (most likely involved in the acceptance step).
+     -->
+    <validations>
+        <specification  review="Nx1"  approval="Nx2"/>
+        <report         review="Nx1"  approval="Nx2"/>
+        <default        review="manager"            />
+    </validations>
+
+<!-- 3. Check-in check-out information
+     Defines the way documents involved in the check-in check-out operations must be processed.
+     Files with import formats are automatically imported into SALOME during check-out if they are uptodate.
+     Other files are downloaded.
+     -->
+    <mappings>
+        <document type="geometry">
+            <import format="brep"/>     <!-- Result Shape                             -->
+        </document>
+        <document type="model">
+            <import format="med"/>      <!-- Result mesh without input parameters     -->
+            <import format="mmed"/>      <!-- Result mesh without input parameters     -->
+        </document>
+        <document type="loads">
+            <import format="model"/>    <!-- Input data created interactively         -->
+            <import format="comm"/>      <!-- Input data created interactively         -->
+            <import format="syd"/>      <!-- Input data created interactively         -->
+        </document>
+        <document type="resultsMeca">
+            <import format="resu"/>      <!-- Calculation results source file          -->
+            <import format="mess"/>      <!-- Calculation results source file          -->
+            <import format="rmed"/>      <!-- Calculation results source file          -->
+            <import format="bz2"/>      <!-- Calculation results source file          -->
+        </document>
+        <document type="resultsSyrthes">
+            <import format="bz2"/>      <!-- Calculation results source file          -->
+        </document>
+        <document type="schema">
+            <import format="xml"/>      <!-- Calculation results source file          -->
+        </document>
+    </mappings>
+    
+    <default-doctypes>
+        <step number="1">
+            <mapping extension="pdf"    type="requirements"/>
+            <mapping extension="doc"    type="specification"/>     <!-- Microsoft Word 2003 and earlier -->
+            <mapping extension="docx"   type="specification"/>     <!-- Microsoft Word 2007 and later   -->
+            <mapping extension="xml"    type="specification"/>     <!-- Microsoft Word 2007 Open XML    -->
+        </step>
+        <step number="2">
+            <mapping extension="doc"    type="design"/>
+            <mapping extension="docx"   type="design"/>
+            <mapping extension="xml"    type="design"/>
+        </step>
+        <step number="3">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="sldprt" type="geometry"/>          <!-- SolidWorks Part                 -->
+            <mapping extension="sldasm" type="geometry"/>          <!-- SolidWorks Assembly             -->
+            <mapping extension="part"   type="geometry"/>          <!-- GEOM Part                       -->
+            <mapping extension="py"     type="geometry"/>          <!-- GEOM Python script              -->
+            <mapping extension="brep"   type="geometry"/>          <!-- GEOM Part                       -->
+        </step>
+        <step number="4">
+            <mapping extension="doc"    type="memorandum"/>
+            <mapping extension="docx"   type="memorandum"/>
+            <mapping extension="xml"    type="memorandum"/>
+            <mapping extension="med"    type="model"/>
+            <mapping extension="mmed"   type="model"/>
+            <mapping extension="py"     type="model"/>             <!-- SMESH Python script             -->
+        </step>
+        <step number="5"> <!-- execute the calculations -->
+        	<mapping extension="med"    type="model"/>
+        	<mapping extension="model"  type="loads"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="6">
+            <mapping extension="comm"    type="loads"/>
+            <mapping extension="resu"    type="resultsMeca"/>
+            <mapping extension="mess"    type="resultsMeca"/>
+            <mapping extension="rmed"    type="resultsMeca"/>
+            <mapping extension="bz2"     type="resultsMeca"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="7">
+            <mapping extension="syd"    type="loads"/>
+            <mapping extension="bz2"    type="resultsSyrthes"/>
+            <mapping extension="py"     type="loads"/>
+        </step>
+        <step number="8">
+            <mapping extension="srd"    type="coparisonResult"/>
+            <mapping extension="py"     type="visualisation"/>
+        </step>
+        <step number="9">
+            <mapping extension="xml"    type="schema"/>
+        </step>
+    </default-doctypes>
+    
+</project-structure>
\ No newline at end of file
diff --git a/Workspace/Siman/conf/edf_som_en.properties b/Workspace/Siman/conf/edf_som_en.properties
new file mode 100644
index 0000000..9687ac2
--- /dev/null
+++ b/Workspace/Siman/conf/edf_som_en.properties
@@ -0,0 +1,21 @@
+menu.step.1   = Specify the study
+menu.step.2   = Design the scenario
+menu.step.3   = Create the geometry
+menu.step.4   = Generate the analysis model
+menu.step.5   = Execute MECA
+menu.step.6   = Execute SYRTHES
+menu.step.7   = Analyze the results
+menu.step.8   = Define the calculation schema
+menu.step.9   = Capitalize this use-case
+menu.step.10   = Finalize the study
+
+folder.step.1 = Specification of the study
+folder.step.2 = Description of the scenario
+folder.step.3 = Geometry
+folder.step.4 = Analysis model
+folder.step.5 = MECA calculation execution
+folder.step.6 = SYRTHES calculation execution
+folder.step.7 = Calculation results
+folder.step.8 = Calculation schema
+folder.step.9 = Knowledge elements
+folder.step.10 = Final report
diff --git a/Workspace/Siman/conf/templates/som.properties b/Workspace/Siman/conf/templates/som.properties
new file mode 100644
index 0000000..fea4d6b
--- /dev/null
+++ b/Workspace/Siman/conf/templates/som.properties
@@ -0,0 +1,52 @@
+name.module   = Centre d''études
+
+size.format   = #,##0 Ko
+date.format   = dd/MM/yyyy
+dd/MM/yyyy    = jj/mm/aaaa
+
+@som@
+
+type.document.requirements   = Cahier des charges
+type.document.specification  = Document de spécification
+type.document.design         = Document de conception
+type.document.geometry       = Géométrie
+type.document.model          = Modèle d''analyse
+type.document.loads          = Conditions de calcul
+type.document.script         = Script d''exécution
+type.document.log            = Log d''exécution
+type.document.results        = Résultats de calcul
+type.document.resultsMeca    = Résultats de calcul MECA
+type.document.resultsSyrthes = Résultats de calcul Syrthes
+type.document.report         = Rapport final
+type.document.memorandum     = Note technique
+type.document.minutes        = Compte rendu
+type.document.coparisonResult= Study comparison result
+type.document.schema         = Calculation schema
+type.document.visualisation  = Visualisation of the results
+
+type.context.customer        = Client
+type.context.product         = Produit
+type.context.phase           = Phase du produit
+type.context.need            = Besoin client
+type.context.purpose         = Finalité de l''étude
+type.context.physic          = Type de physique
+type.context.object          = Objet étudié
+type.context.part            = Objet modélisé
+type.context.geometry        = Type de géométrie
+type.context.model           = Type de modèle
+type.context.element         = Type d''éléments
+type.context.shape           = Géométrie des éléments
+type.context.order           = Degré des éléments
+type.context.analysis        = Type d''analyse
+type.context.platform        = Plate-forme logicielle
+type.context.module          = Module de calcul
+type.context.component       = Brique technologique
+
+type.knowledge.usecase       = Use case
+type.knowledge.bestpractice  = Bonne pratique
+type.knowledge.limitation    = Limitation
+type.knowledge.inconsistency = Incohérence
+type.knowledge.metrics       = Métrique
+type.knowledge.improvement   = Amélioration
+
+history.creation = Document créé par
\ No newline at end of file
diff --git a/Workspace/Siman/conf/templates/som_en.properties b/Workspace/Siman/conf/templates/som_en.properties
new file mode 100644
index 0000000..be64dae
--- /dev/null
+++ b/Workspace/Siman/conf/templates/som_en.properties
@@ -0,0 +1,53 @@
+name.module   = Study Manager
+
+size.format   = #,##0 Kb
+date.format   = MM.dd.yyyy
+MM.dd.yyyy    = mm.dd.yyyy
+
+@som.en@
+
+type.document.requirements   = Customer requirements
+type.document.specification  = Specification document
+type.document.design         = Design document
+type.document.geometry       = Geometry
+type.document.model          = Analysis model
+type.document.loads          = Boundary conditions
+type.document.script         = Execution script
+type.document.log            = Execution log
+type.document.results        = Calculation results
+type.document.resultsMeca    = MECA calculation results
+type.document.resultsSyrthes = Syrthes calculation results
+type.document.report         = Final report
+type.document.memorandum     = Technical report
+type.document.minutes        = Minute meeting
+type.document.coparisonResult= Study comparison result
+type.document.schema         = Calculation schema
+type.document.visualisation  = Visualisation of the results
+
+type.context.customer        = Customer
+type.context.product         = Product
+type.context.phase           = Product phase
+type.context.need            = Customer needs
+type.context.purpose         = Purpose of study
+type.context.physic          = Physics
+type.context.object          = Studied object
+
+type.context.part            = Modeled object
+type.context.geometry        = Geometry type
+type.context.model           = Type of analysis model
+type.context.element         = Element type
+type.context.shape           = Geometry of elements
+type.context.order           = Order of elements
+type.context.analysis        = Analysis type
+type.context.platform        = Software platform
+type.context.module          = Solver
+type.context.component       = Software component
+
+type.knowledge.usecase       = Use case
+type.knowledge.bestpractice  = Best practice
+type.knowledge.limitation    = Limitation
+type.knowledge.inconsistency = Inconsistency
+type.knowledge.metrics       = Metrics
+type.knowledge.improvement   = Improvement
+
+history.creation = Document created by
\ No newline at end of file
-- 
2.39.2