Does AVEVA have guidelines or documentation on how to convert an InTouch for System platform application to an OMI application?
Does AVEVA have guidelines or documentation on how to convert an InTouch for System platform application to an OMI application?
As David says, the first thing to do is to get training on how OMI works, because the way applications are developed is totally different from how they are developed in IT4SP. Depending on how the IT4SP application was created, this migration to OMI can be relatively simple or it can involve a total revamping of the graphical part. If you already have all the graphics as Industrial Graphics and all the screens created as Industrial Graphics, you really have a lot of work done. The next step would be to link all this content to the different assets if you don't have it that way already and using the default navigation it should be pretty straightforward.
The first project or two with OMI is usually a bit traumatic, because naturally we try to develop as we would in InTouch and that generates a feeling of frustration, but once we understand how it works and we really adapt to its way of working, we see that creating applications with OMI is really much simpler and faster.
As David says, the first thing to do is to get training on how OMI works, because the way applications are developed is totally different from how they are developed in IT4SP. Depending on how the IT4SP application was created, this migration to OMI can be relatively simple or it can involve a total revamping of the graphical part. If you already have all the graphics as Industrial Graphics and all the screens created as Industrial Graphics, you really have a lot of work done. The next step would be to link all this content to the different assets if you don't have it that way already and using the default navigation it should be pretty straightforward.
The first project or two with OMI is usually a bit traumatic, because naturally we try to develop as we would in InTouch and that generates a feeling of frustration, but once we understand how it works and we really adapt to its way of working, we see that creating applications with OMI is really much simpler and faster.