Compatibility Decision
The available evidence does not establish that FLSmidth ECS can import screens created in Vijeo Citect. Treat the two environments as incompatible until FLSmidth confirms a supported exchange format or migration tool for the installed ECS system. Similar-looking displays do not prove compatibility because screen objects, tag references, navigation, scripts, alarms, and runtime configuration may use product-specific definitions.
| Question | Evidence status | Required decision |
|---|---|---|
| Can ECS import a Vijeo Citect project? | Unknown | Obtain written confirmation for the installed ECS release. |
| Can individual display files be exchanged? | Unknown | Identify the native ECS display format and supported import formats. |
| Will tags, scripts, alarms, and navigation transfer? | Unknown | Test each object type in a non-production ECS environment. |
| Is ECS engineering software required? | The project team does not have it. | Confirm the required engineering package, license, and authorized integration method. |
Information Required Before Engineering
Record the installed ECS release, available engineering tools, screen-file format, and any documented import or export functions. Also inventory the proposed displays by object type: static graphics, process tags, commands, navigation links, alarm objects, trends, scripts, and security-dependent controls. The evidence supplies none of these compatibility details, so committing to direct export would create an uncontrolled integration risk.
Controlled Validation Procedure
- Ask FLSmidth through an official support channel whether the installed ECS system supports importing Vijeo Citect displays, and request the supported file formats and migration procedure.
- If a supported path exists, build one small representative display containing every required object type rather than converting the complete project.
- Import the representative display into a non-production copy of the target ECS configuration using the approved engineering software.
- Verify graphic rendering, tag binding, command behavior, navigation, alarms, trends, scripts, permissions, and persistence after saving and reopening the project.
- If ECS has no supported import path, recreate the displays in the native ECS engineering environment using the Vijeo Citect design only as a visual specification.
Do not modify the production ECS project until the representative display passes functional testing and the existing configuration has been backed up through the site's approved procedure.
FAQ
Can Vijeo Citect screens be exported directly to FLSmidth ECS?
The evidence does not confirm direct compatibility. Verify a supported ECS import format or migration tool for the installed release before developing screens in Vijeo Citect.
What should be tested after importing a SCADA screen into ECS?
Verify rendering, tag binding, commands, navigation, alarms, trends, scripts, permissions, and persistence after reopening the project in a non-production environment.
What is the fallback if ECS cannot import Vijeo Citect displays?
Recreate the displays with the native ECS engineering software and use the Vijeo Citect work only as a visual specification. Confirm the required ECS software and licensing through an official FLSmidth support channel.