InOut variables in TIA (S7_m_c)

Dear colleagues,

First off all I'm wondering if there's some comparing functionality in TIA Portal, to the FB attribute S7_m_c?
As we are developing a new standard for TIA Portal, I'd like to know the bestway to do it.

In S7 V5.5 you have the posibility to add attributes to the In, Out and InOut variables in a FB. One of this attributes is S7_m_c,it allows you to compile yourtag's automatic to WinCC.
Now it'snot possible to addan attribute to aStat variable, so we used InOut's to clear the job for the commands and visualisation bits (as well for treshholds, setpoint,...).
This bitsaregrouped in one IQ_Cmd DWORD and one IQ_Visu DWORD.

IQ_Cmd {S7_m_c := 'true'} : DWORD; //InOut: Command DWORD from SCADA
IQ_Visu {S7_m_c := 'true'} : DWORD; //InOut: Visualization DWORD from SCADA

I explain you the flow of the IQ_Cmd and IQ_Visu more in detail:
We need to copy the IQ_Cmd and IQ_Visu DWORD's tothe Temp Structures Cmd and Visu, but the IQ's and Temp Structures aren't the same data type. So you need and additional "copy" step using the AT instruction.
In the beginningof the code we copied the IQ_Cmd and IQ_VisuInOut variables to the Cmd and Visu Structure.
This allows you to work symbolic in the code (Cmd.Auto, Visu.Sim,...). For the visu bits there's even a third copy step to seperate Stat variables. The advantage of doing this is when you reach for a motor status in you normal programming logic, outside the FB, it's more compact "P100.FbkFwd" instead of "P100.Visu.FbkFwd".
At the end of thecodewereset the IQ_Cmd DWORD, because all commands comming fromSCADA are SET instructions. And copy the Visu struct back onto the IQ_Visu variable, allowing SCADA to see the updated motorstatuses.
(see example FB SCLsource code in attachment)

Long story for a small question, but is there a comparing way of doing things in TIA Portal?
If the attribute S7_m_c story ends, is it still needed touse InOut's or can we switch over to Stat variabeles (also allowing to mark it asvisible HMI, setpoint,...) and making the FB visualy more compact as well.
Is there a way of automatic compilation of tag's to a WinCC Pro Server, instead of browsing to it?
What would be a good TIA Portal flow for IQ_Cmd and IQ_Visu?

I hope my questions are clear and I want to think and share some ideas about it.

Thanks

Thanks for the answer uel123,

As I can conclude and thought, we'll have to do it the "old" WinCCFlex way, using manual created structures (now HMI UDT's).
I'm wondering who's already using a WinCC Pro V12 Server???

I've to tell that I like the general approach of the TIA Portal platform, but the more "advanced" functionality is poor, like you indicated (or should I say, I like the new S7 1500 controller).
In V12 there's no VBA to create custom development functionality in WinCC, no automatic tag generation, ...

Also our clients start to know TIA Portal's existens as well, especialy when the prices arelower, the need of those things is getting more urgent. Or will it never be as advanced as WinCC V7?

I heard form a Siemens software support engineer, that Siemens is pushing the development division to have a first "PCS7" in TIA Portal V16 (2016).
As I can see in some disabled parameters en checkboxes they'll probebly use CFC's for this (as they do now). I hope the customer developers will get full access to this tools and functionality as well.

Any news on added programming functionality in V13. Except for the multi-user, import/export, new drives,... things?

Thanks