EcoStruxure Foxboro DCS Control Editors products



EcoStruxure Foxboro DCS Control Editors products

Product positioning and core values

EcoStruxure Foxboro DCS Control Editors is a professional configuration and development tool launched by Schneider Electric for Foxboro distributed control systems (DCS). Its core positioning is to provide full lifecycle control strategy design, editing, configuration, deployment, and operation support for industrial automation projects. Relying on the AVEVA intuitive user interface and Microsoft Visio rendering engine, complex control logic is transformed into visual operations, greatly reducing engineering difficulty and improving configuration quality and efficiency.

The core value of this tool lies in breaking the limitations of traditional DCS configuration and achieving integrated management from strategy design to deployment and operation: on the one hand, it supports multi scenario adaptation, which can not only meet the initial engineering design of new projects, but also support the expansion and technological upgrading of existing systems; On the other hand, through standardization, templating, and automation functions, it reduces repetitive labor, ensures consistency and reliability of control logic, and has strong compatibility and scalability to meet the control needs of different scale industrial scenarios.

Core concepts and architecture system

Before using Control Editors for configuration, it is necessary to clarify its core concepts and architectural hierarchy to ensure the standardization of policy design and system deployment

（1） Core level definition

Control Station: The hardware platform core responsible for executing the adjustment, sequence, logic, and supervisory control strategies assigned to it. It is the physical carrier for the operation of control strategies.

Compound: The top-level logical unit that needs to be bound to a specific control station and contains multiple user designed control policies. It is the intermediate layer of association between policies and hardware.

Control Strategy: A functional reusable control entity composed of multiple control blocks and internal sub strategies, which can be instantiated as specific control circuits and other control units.

Control Block: The most basic control element, corresponding to specific control functions (such as signal acquisition, logic operation, regulation control, etc.). Foxboro DCS supports over 100 different types of control blocks, divided into two categories: basic templates and user derived templates.

（2） Architectural design features

Modular architecture: All control logic is based on "blocks" and "strategies" as basic modules, supporting free combination, reuse, and expansion. The control system can be flexibly built according to project requirements.

Hierarchical deployment logic: Following the hierarchical allocation mechanism of "policy → composite object → control station", ensuring precise matching between control logic and hardware resources, facilitating system management and maintenance.

Open compatibility architecture: supports integration with ArchestrA industrial application servers, third-party systems, and various fieldbus devices, follows standardized communication protocols, and ensures system interconnectivity.

Core functions and operational features

（1） Control Strategy Design and Editing

Graphic visualization design: The strategy editor provides a visual canvas, where users can drag and drop basic control blocks or derived templates onto the canvas, connect exposed parameters of the blocks through lines, and quickly build control logic. Support user-defined rendering styles for policy components, including Scientific Apparatus Makers Association (SAMA) standard symbols, to meet industry standards.

Flexible configuration of control blocks:

Basic control block: covering core functions such as signal input, logical operation, and regulation control, and can directly call configuration;

Derivative control block: Users can customize based on the basic block, such as deriving the basic analog input block (AIN) into an iron constantan thermocouple input block, or modifying the appearance and functional exposure of the PIDA block to generate control entities that comply with SAMA standards.

Programmable logic support: For complex control scenarios, multiple types of programmable blocks and exclusive editors are provided:

Text editor: used for High Level Batch Language (HLBL) programming, adapted to batch control scenarios;

Graphic Editor: Supports Sequential Function Charts (FoxSFC) and Ladder Logic Diagram (LLD) programming, visually presenting sequential control and logic control processes;

Universal computing blocks: including MATH, LOGIC, Calc, CalcA and other calculator blocks, to meet various mathematical operations and logical judgment needs.

（2） Data interaction and debugging optimization

Multi dimensional data interface:

Report interface: Supports exporting configuration data from Microsoft SQL Server and Excel for easy data archiving and analysis;

Editing interface: Provides an intuitive Excel interface that allows for direct editing of configuration parameters in Excel, improving batch editing efficiency.

Real time debugging capability: Control strategy drawings can overlay and display real-time updated parameter values, allowing for intuitive observation of control logic operation status without relying on human-machine interface (HMI); Support uploading real-time data from the controller directly to the database, or downloading configurable parameters from the database to the controller, without the need for a complete deployment process, greatly reducing the debugging cycle.

（3） Batch operation and migration upgrade

Batch generation strategy: Supports batch generation of control strategies based on predefined templates and external project data (such as Excel, CSV, SaveAll, IACC Export, SysDef Export, or proprietary XML documents). Users can use Visual Basic scripts to perform targeted editing on imported data grids, such as batch modifying policy parameters and adjusting composite object assignments, to quickly complete large-scale project configurations.

System migration compatibility: Provides the ability to batch migrate control strategies from installed I/A Series systems and Foxboro DCS, seamlessly migrating the control logic and intellectual property of existing systems to new systems, protecting users' existing investments, and reducing upgrade costs.

Import and export function: Supports the import and export of control strategy design files, facilitating cross project reuse, backup, and sharing, and improving engineering efficiency.

（4） System and equipment configuration

System topology construction: Users can instantiated hardware units such as control stations and fieldbus modules (FBMs) and customize their names. These hardware units can be allocated to designated factory unit areas (such as centrifuge area, purification area, reaction area, solvent recovery area, storage tank area, etc.) through a network view, visually presenting the system hardware layout and ownership relationships.

Intelligent device lifecycle management: supports comprehensive management of digital field devices using FOUNDATION Fieldbus, HART, and PROFIBUS technologies, including device access, parameter configuration, operation monitoring, fault diagnosis, debugging, and troubleshooting, ensuring stable linkage between field devices and DCS systems.

ArchestrA platform deployment: ArchestrA IAS platform, engine, and application objects (such as OLEDB database applications) can be created and deployed to the Foxboro DCS control software application environment to expand the system's functional boundaries.

（5） Security and Collaboration Management

Role based permission control: ArchestrA's role-based security model is adopted, where users subscribe to corresponding roles based on job responsibilities, and roles are associated with specific access permissions (such as operations, secure writes, configuration modifications, etc.) and security groups (corresponding to factory areas). Supports three authentication methods: local authentication, host operating system binding authentication, and Microsoft Active Directory authentication (it is recommended to configure at least two redundant domain controllers to enhance security).

Change Tracking and Traceability: Deeply integrated with Foxboro DCS' System Advisor change tracking function and FoxCTS change tracking software, all control configuration modifications (such as parameter adjustments) and program changes (such as HLBL, FoxSFC, LLD program modifications) will be recorded and synchronized to associated software, meeting industry regulatory requirements and facilitating fault tracing and auditing.

Multi client concurrent access: The server supports multiple clients to access the configuration database simultaneously through remote desktop services, with a record locking mechanism to prevent concurrent operation conflicts. The client runs independently and only communicates with the server when the session is open or closed, fully utilizing network resources and ensuring smooth operation.

Deployment process and operation mechanism

（1） Deploy core processes

Strategy design and configuration: Complete the graphical design, parameter configuration, and logical correlation of control strategies;

Hierarchical allocation: Assign control strategies to composite objects, and then bind the composite objects to the target control station;

Deployment execution: Select the corresponding object through the deployment view, execute the deployment command, and the system automatically completes the following operations:

Download the composite object and control block to the designated control station and Compound Summary Access (CSA);

Load the security access settings of the composite object and control block into the ArchestrA security system;

Update ArchestrA historical database and synchronize the configured collection point information;

Change deployment: After modifying the strategy or composite object, it is necessary to redeploy. The system only updates the affected targets and modified parameters to avoid resource consumption and downtime risks caused by full deployment.

（2） Operation guarantee mechanism

Resource isolation: Client and server resources are isolated, with the client only providing an operating interface and core computing relying on server resources to ensure operational stability;

Fault tolerance: Supports redundant configuration of critical hardware, combined with change tracking and fault diagnosis functions, to quickly locate and handle operational anomalies;

Real time synchronization: Configure data and run data to be synchronized in real-time, ensuring that modified parameters take effect in a timely manner and guaranteeing the accuracy of control logic.

Software and hardware specification requirements

（1） Minimum configuration requirements

Device/Role Memory (RAM) Hard Disk Capacity Special Instructions

Remote desktop services require a minimum of 16GB, with a recommended minimum of 32GB and 150GB for controlling HMI. Virtual machines based on remote desktop services require additional reserved space, with each user requiring 3GB of C drive space for managing applications

Control software Galaxy minimum 16GB, recommended 32GB minimum 250GB for storing system configuration and policy data

The control software Historian has a minimum of 16GB, with a recommended minimum of 32GB and 500GB for storing historical operational data, which needs to be expanded according to the data volume

All other roles require a minimum of 16GB, with a recommended minimum of 32GB and 150GB, covering regular clients, configured workstations, etc

（2） System and hardware compatibility

Operating System: Supports Windows Server IoT 2022 or Microsoft Windows 10 IoT Enterprise LTSC 2021 (64 bit version);

Computer hardware: Hardware devices that require Foxboro DCS certification, such as D96, H90, H92, H94, V91, V95, etc;

Communication network: Require 100 Mbps TCP/IP switched Ethernet to ensure stability and real-time data transmission.

Product advantages and applicable scenarios

（1） Core advantages

Engineering efficiency improvement: Through graphic design, template reuse, batch operation and other functions, the initial design and expansion transformation cycle of the project is significantly shortened, reducing repetitive labor;

Configuration quality assurance: standardized design process, role-based permission control, and change tracking function to ensure consistency, security, and traceability of control logic;

Strong system compatibility: Supports migration from legacy systems (I/A Series, old Foxboro DCS), compatible with multiple fieldbus devices and third-party systems, reducing system upgrade and integration costs;

Full lifecycle support: covering the entire process of project design, deployment, debugging, operation, and upgrade, providing one-stop configuration and management tools to adapt to the needs of different stages of the project.

（2） Applicable scenarios

New industrial automation projects: suitable for new projects in industries such as chemical, power, pharmaceutical, petroleum, etc., quickly build Foxboro DCS control system;

Existing system upgrade and renovation: Provide a technical upgrade path for existing users of Foxboro DCS to achieve smooth migration of control logic and functional expansion;

Large scale project expansion: supports batch generation and configuration strategies, adapting to the control requirements of large factories or cross regional projects;

Multi project reuse scenario: The control strategy and intellectual property of one project can be transferred to other projects, and the new scenario can be adapted through editing tools to improve the efficiency of multi project implementation.