In Reply to Gisela Attadia:
Thanks again for all the recommendations but I was asking about
non-conventional methods of training. I understand that you can
build know how with time and the known paths of doing so, but the
problem here is different.
An example of an application that tried to tackle
this problem is what the Gehry Technologies did at one
point in time with the CATIA V5 client (Digital Project 3D). They
packaged the application to host all the products and licenses they
understood their users needed. By doing so, they did provide all
options to the user from the start by enabling a UI with all
commands and functions available but they lost scalability in
Preserving the possibility of running any supported piece
of code in the 3DX Native Client (CATIA, ENOVIA, DELMIA,
SIMULIA...) at any given time is part of the objective here. But
what you gain flexibility you lose in usability. You end up with a
highly versatile tool that is very hard to use and is
not intuitive at all. If you add to that a group of users that
motivated by innovation, change and creativity, which pursue not
defining rigid workflows and design requirements that change
on a daily basis, then you reach the question I'm presenting
In my opinion if you want to make good trainings, first of all, you
should stop thinking as a trainer/teacher and start thinking as the
I personally found all catia trainings, I've participated in,
extremely boring and inadequate.
To cite Miguel de Icaza (creator of Gnome, Xamarin, Mono,
"Coming up with the ideas to try out what you have just learned
is difficult. As you think of things that you could do, you quickly
find that you are missing knowledge (discussed in further chapters)
or your ideas are not that interesting. In my case, my mind drifts
into solving other problems, and I go back to what I know best.
Please, build exercises into your books. Work with teachers to find
the exercises that match the material just exposed and help us get
in the zone of Flow".
The Flow, is very important if you want to make your training
"attractive" to the trainees. You should understand more about
them. Learn their interests, learn what other software they know,
you have to know the advantages of Catia over these software. But
don't go too hard as catia has a lot of disadvantages too.
Separate the trainees in groups if you have to according
to what you've learned about them.
It is my opinion, that the best and the worst thing about CATIA
is its strong parameterization. That both attracts and repulse
people (as it does me) depending on how they use modeling software.
Another thing that repulses, especially about catia is the mouse
controls (zoom and rotation with multiple button clicks). Yet
another is the lack of terminal where you can quickly enter command
or value (like Autocad, Rhinoceros, etc.), power input is just not
You really have to explore your audience. Make appropriate
examples that tease them, that trigger them to get "into the
Last but not least, don't use the same trainings for people
in different age groups. That's just wrong. People who've lived in
different times (with this rate of technological progress) are
interested in different things. For youngest people I suggest build
examples that relate to video games. For a bit older,
try examples that relate to 3d printing and practical objects
and mechanisms. For older professionals with experience in other
software, prepare examples that reflect their industry.
I believe 2 days is enough for a training to get started working
with catia, in case there's more knowledgeable person they can ask
while working. If you plan to teach them 2 days and drop them in
the ocean with two punctured life-rafts like DS Online
Documentation and the companion, then they are doomed to
drown. They will get frustrated by catia be reluctant to ever try
I hope this is helpful.