Eclipse Community Forums: Vorto » Ideas for transfer process of Vorto specifications along the value chain

Home » Eclipse Projects » Vorto » Ideas for transfer process of Vorto specifications along the value chain(Integration, Tooling)

Show: Today's Messages :: Show Polls :: Message Navigator

Ideas for transfer process of Vorto specifications along the value chain [message #1707107]

Wed, 02 September 2015 11:48

Henning Groenda

Messages: 11
Registered: July 2009

Junior Member

There is the current process that final specifications can be shared in the Model R
Repository. Companies can create and use their own, separate Model Repositories.

There are two points where i think an alignment could be a benefit:
1) Alignment of IDE and remote Repositories
In the IDE, each model artifact is stored in an own project. Interaction with repositories is (supposedly) realized via an import/export context menu. Why not using a single repository for an IDE storing all the models at one place?

2) Alignment along value chain
Background: A typical process will probably start with an early prototype and several iterations refining the models. This prototype will then receive proper engineering to become a device, further refining the models. The result will go in (mass) production with final and assigned models. Future revisions of the device may have altered models.

I'd like to see a process that uses the same tools and allows to work with the same (versioned) artifacts during the whole process. The models would move along the chain from a repository for a single developer, development department, company, to the Vorto Model Repository. The number of versions for 'the same' model will reduce per step. Linking between those artifacts provides the advantage of proper change history management instead of versions.

Looking forward to your ideas.

Report message to a moderator

Re: Ideas for transfer process of Vorto specifications along the value chain [message #1707380 is a reply to message #1707107]

Fri, 04 September 2015 11:54

Olaf Weinmann

Messages: 29
Registered: May 2015

Junior Member

Indeed the public Vorto repository is currently inteded to only share final versions of Information models, Functionblocks and Entities. However the technology of the repository allows also a change history management.

1) The interaction of the toolset with the Vorto repository is not realized via the import & export menu. The toolset provides a specific Model Repository - view that allows to browse the repo, to download models, and to check models in, provided that the user has the corresponding access rights. Does this integration fulfill your requirements or do you have additional ones?

2) This is an interesting point and such a process would definitely be useful. Do you have a process in mind? I would suggest that we create a page in the Vorto Wiki and collect some ideas. Would you be willing to contribute your ideas there?

Cheers,

Olaf

Report message to a moderator

Previous Topic:	Definition of Arrays in Datatype / Function Block Models
Next Topic:	"the thing is not enough"

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Dec 12 16:56:18 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter