Discussion about SV_FORM1 - Way to present AA

11 Posts
7 Users
0 Likes
41 Views
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
Topic starter
 

The question is simple: Do we still have to continue the training as it is in term of design method?

Today we are starting all configurations using the old way then on the middle of training we introduce the AA saying something like “You see, everything you did manually can be done using a fabulous tool”!
Some of you say: No, we must start directly with the AA.
Both ways have pros and cons and it’s quite difficult to decide actually.

After thinking about I had an idea: Why not mixing? For example Module 6 is for Variables. Why not teaching the manual way first then by AA (or reverse) in the same module. Then same for OPC after, etc…
What do you think?

 
Posted : 05/12/2013 11:00 am
LM
 LM
(@l-micaudarcinfo-com)
Posts: 383
Member Admin
 

In my opinion only AA is a solution to develop a PcVue project.

It is import to know what is possible to do with AE, but all that can be done with AA must be donne with AA.

 
Posted : 05/12/2013 7:31 pm
e.mahaut
(@e-mahautarcinfo-com)
Posts: 270
Member Moderator
 

Hi guys,

In my opinion, Pros AA brains (I am talking about trainees, not us) will be able to understand both ways. But Cons AA brains will be completely lost if we start directly with AA.

I don't know how it is in foreign countries but even after the training, some trainees (let's say 10%) are not efficient with PcVue. If we start directly with AA, I guess it could climb up to 20% or more.

I vote for continuing like it is now.

KR
Edouard

 
Posted : 05/12/2013 10:22 pm
(@s.epaillard@arcinfo.com)
Posts: 0
New Member Guest
 

I agree with Edouard.

Trainees need to understand PcVue's spirit before start with AA.

 
Posted : 05/12/2013 10:29 pm
BO
 BO
(@b-olombelarcinfo-com)
Posts: 196
Reputable Member
 

Hey buddy !

Many customers that we met in training are not developpers but only mainteners. These customers don't need to know what is AA in PcVue but just need to modify fastly the mapping of a variable or to add a variable on site.
And, depending of the PcVue configuration right, maybe they won't be able to access to AA...so they need to know how to make modifications with AE.

As I explain in training AE, AA and SG are not competing functionalities but complementaries.

 
Posted : 05/12/2013 10:56 pm
n.kunzer
(@n-kunzerarcinfo-com)
Posts: 1236
Member Moderator
Topic starter
 

The fact is that we have an heterogeneous public.

So, what do think about my idea to mix?

For example on Module 6 (Variables):
- First we show how to do everything by AE
- Second we show the same thing by AA

Module 12 (Alarms)
- Create alarms in AE
- Create alarms in AA

Module 13 (label, attributes)
- Create label then apply with AE
- Apply with AA

Module 15 (Automated application generation)
- Introduce parameters in AA

and so on...

Good or bad idea?

 
Posted : 06/12/2013 8:47 am
(@r.buisson@arcinfo.com)
Posts: 0
New Member Guest
 

Hello all,

Nicolas your mix idea is good.

We know that due to heterogenous public we must adapt the training in real time, so mixing classic and AA is a good way to do the training.

 
Posted : 06/12/2013 2:05 pm
e.mahaut
(@e-mahautarcinfo-com)
Posts: 270
Member Moderator
 

Hi all,

Go ahead for mixing 😉

Edouard

 
Posted : 06/12/2013 2:48 pm
LM
 LM
(@l-micaudarcinfo-com)
Posts: 383
Member Admin
 

Yes Nico it is a good idea to mix.

Once again I think it is important to know how to work with AE.
But to create a project (what we do during training) only AA should be used.

It is not more complex than AE. Even PLC programers evolved during last years to object language with structures. We should not wait version 15 to start learning good way.

 
Posted : 06/12/2013 2:58 pm
(@admin_doc72)
Posts: 493
Member Admin
 

I prefer to teach the Application Architect after.

Like most of you I agree that the basic configuration elements in PcVue are best presented by using the Application Explorer. For me it does not make much sense to exclusively interpret a database variable as a configuration element in an AA-template. Before I actually need to know how to configure that individual variable and where is its place in the PcVue data flow (variable tree, source, archiving...).

What I am usually doing on training is to set a up a project in the traditional manner (AE), let's say for the first two days or so. And on the third day I am saying: "Imagine now that what we have done during the past two days you can do in 30 minutes in a much more sustainable manner... let's take a look at the Application Architect". This has usually the same "wow-effect" as when showing how to create generic symbols in branch-contexts instead of copy/pasting graphics and modifying animations.

Consequently, I am not really in favor of creating mixed modules.

 
Posted : 06/12/2013 6:23 pm
RM
 RM
(@r-martinarcinfo-com)
Posts: 56
Estimable Member
 

I also agree with Edouard. In the UK we say that "you need to be able to walk before you can run"

Robin

 
Posted : 09/12/2013 9:27 pm