Windows XP Support is ending soon

On April 8, 2014, support and updates for Windows XP will no longer be available. Don't let your PC go unprotected.

FactoryLink  System Requirements

FactoryLink ECS 6.0.1

Windows 95

Windows NT 3.51

OS/2 WARP 3.0 / Connect

HPUX 10.10

SUN Solaris 2.5.1

FactoryLink 6.6.0 / Monitor Pro 2.1.

Windows NT

Windows 95

FactoryLink 7.0 / Monitor Pro 7

Microsoft NT 4.0, Service Pack 4

Microsoft Windows 2000

FactoryLink 7.1 / 7.5 / Monitor Pro 7.2 / 7.6

Microsoft Windows 2000

Microsoft Windows XP

FactoryLink 8.0

Windows 2000 Professional SP4

Windows XP Professional SP2 (x86, x64)

Windows 2000 Server SP4 (x86, x64)

Windows Server 2003 SP2 (x86, x64)

Windows Vista Business (x86, x64) – for One-Click Client only 

SCADA FactoryLink / Monitor Pro Basic migration service

for design teams which has no FactoryLink professionals in staff

Many system integrators want to migrate from FactoryLink / Monitor Pro to the new SCADA / DCS using own team power. Why not? 

To do this, you need to have the FactoryLink application data. 

We offer a 

BASIC migration service

With this service, we provide the FactoryLink application data in the Excel table format for migration to new SCADA:

Data properties - Tags, Alarms, Historian, PLC Communication configuration and items, Objects animation decoding/Graphical screens etc.

Latest SCADA and DCS systems support vector graphics. We can save your time and manpower by the converted ECS Graphic screens into SVG vector graphics. Link

Data supported by "How to ..." manual and our technical assistance for your team (development/commision phase).

CONTACT

factorylink.migration@gmail.com

our knowledge on service of your business

Migration service to Vijeo CITECT → Smarter than starting from scratch

→ for FactoryLink and Monitor Pro users

A special migration utility gives FactoryLink and Monitor Pro users a engineering advantage of migrating legacy application to the Schneider Electric company’s SCADA VijeoCitect.

Migration Startup comes from a combination of ideas of people already working in the area of SCADA/HMI application design.

SCADA migration is provided for users as an outsourcing service.

Service allows users upon upgrading their legacy control systems to VijeoCitect SCADA:

•  minimize Cost of Ownership

•  fewer manpower

•  faster commissioning

Proceeding from your business requirements, we can expand a functionality of automated control system. For extension of a zone of process automation, we suggest to develop in addition the custom application 

→ Download service overview

CONTACT

factorylink.migration@gmail.com

our knowledge on service of your business

Dynamic visualization in the HMI of the movement of liquid products in the extensive pipeline system

Description of problems.
often HMI displays only the status of valves.
At the same time, the direction of movement of the product in the pipes do not visible for operator. 
He expects opened properly fitting/valves.

- extensive pipeline system
- different products at the same pipeline

Possible incidents 
- a mixture of products 
- part of the product goes in the other direction
The operator takes the time to analyze the situation - human factor.

http://youtu.be/Q6c19y3kvL0 

I hope the presentation clearly shows the issue. 
Note the example screens at the end of the presentation.

To migrate or not to migrate: that is the upgrade question?

Constantly in the network the discussion about system migration rises and each time the antithesis battle begins.


So, does anyone have or had any requests in the past for SCADA migrations from your customers? - The typical answer - Yes, but “customer postponed this question” or “the longer we talked to the customer about it the more and more questions arised, and as a result we haven’t undertaken this project”. As strange as it is the main reason is not financial. 

It's all about “cruft”, that stuff that builds up over time and relationships with industrial automation partner. Cruft includes systems functions you no longer use, preferences you don't really remember setting, bits and pieces scattered around your system that accumulate with use. 



If you are not scared about “cruft”, the next hurdle for you - Choosing a Migration Partner.  The choice is simple: a) Vendor b) System Integrator c) Customers own team. The pros and cons of each will not describe here. They are clear to all.
Choosing a Migration Partner addressed the issue - Types of migration: 1. Migrate within a legacy systems vendor family  2. Migrate from one legacy systems vendor to another  Proven solutions are most often based on products as they normally are a part of a supplier (Vendor or SI) migration plan. If the supplier has no proven solutions – do not choose this way. You expose yourself to consider a guinea pig.

Whatever you choose the answer to the question - Who should take the lead role a) b) or c)? On the other hand, may be exists choose d)? Why not create a multidisciplinary team consisting of people that are trained on these solutions? It is normally relatively easy to find people who have the knowledge and solutions in parts of migration. Sure, it's a much harder process, but what is the migration goal? I believe it is cheaper and technically elegant solution.

To migrate or not to migrate? - is not a question. The question is: How to migrate to avoid late for your plant/business? You can evaluate the Risks based on your requirements for each of the options before making a right choose.