Overview

Composer ™

Features and Benefits

■ Configuration Viewing and Monitor-
ing: Provides wide access to
Composer configuration data
without the risk of accidental
configuration changes.
■ Integrated suite of configuration
tools: Develop control strategy
using standard and user defined
function codes; Batch 90 for
batch and sequential applica-
tions; batch recipes; custom C
programs; and HSI
configurations.
■ Reduced engineering time: Base
applications share a configura-
tion database to validate data
and provide a single point of
data entry.
■ Compatibility with Symphony
systems: Easily imports configu-
TC01000B
rations from previous
Symphony and INFI 90® OPEN Composer provides a comprehensive set of engineering and
system tools. maintenance tools for the Symphony Enterprise Manage-
■ Engineered to operate on the latest ment and Control System. Composer is designed to operate
platforms: Designed to operate on the Microsoft® Windows 2000 (Service Pack 2) or Win-
on Windows® 2000 Service Pack dows NT 4.0 (Service Pack 6A or later) platform.
2 or Windows NT® 4.0 Service
Pack 6A or later. The working environment provided by Composer simplifies
■ Multiple user client/server architec- the configuration and maintenance of Symphony systems.
ture: Projects are accessible by The base product contains all the functionality necessary to
multiple users and locations create and maintain control system configurations. Applica-
simultaneously. tions provide users with the ability to graphically develop
■ Object exchange (enhanced library control system strategies, develop and maintain global con-
support): Central location for figuration databases, and manage system libraries of
storing control logic templates, reusable software components.
macros, and shapes.
Composer is designed to be compatible with INFI 90 OPEN
■ Revision control: Maintains previ-
system configurations and is capable of importing existing
ous revisions of control
strategies in a system wide con- WinTools configurations. Once imported, these configura-
figuration database. tions can be fully integrated into Composer and utilize all its
features.
■ Advanced troubleshooting: Moni-
toring and tuning functions of
the automation architect and the
batch data manager’s dynamic
debugger provide powerful
online diagnostics.
■ System oriented navigation: Users
point and click through configu-
ration organized by system
architecture.
Composer

Additional Features
■ Configuration Viewing and Monitoring: View and Monitor is an add-on Composer option which
allows control logic documents (CLD) to be viewed and monitored from a Web browser in
read-only mode. It extends the functionality of Composer to publish CLDs in SVG format
and to populate/create Web sites on an Internet Information Server (IIS) virtual directory for
remote viewing via a browser. The capability of publishing CLDs to SVG format is in the base
product. Viewing and monitoring is a separately licensed feature which allows the monitor-
ing of block output values read from control systems.

■ Multiuser, client/server architecture: Composer applications use client/server technology to

support multiple users operating in a networked environment. Configuration information
which is managed by Composer’s configuration server can be accessed simultaneously by
multiple users. In addition to interacting with configuration information, users can access
online data from a running Symphony or INFI 90 OPEN system by using Composer’s com-
munication server. The Composer architecture supports one configuration server per system
and multiple communication servers.

■ Configuration database: A configuration server can support up to ten simultaneous client con-
nections and provide users with shared access to a system’s configuration information.
Composer’s configuration server manages and stores configuration data in one configuration
database per project or system. This configuration database eliminates duplication of data
entry, simplifies database management, and automates many configuration tasks. Informa-
tion can be imported and exported in many formats.

■ Shared network interface devices: Communication servers provide users with the ability to com-
municate with a running Symphony or INFI 90 OPEN system by accessing the Control
Network (Cnet) via the Operations Network (Onet). Network couplers or computer interface
devices can be simultaneously shared by Composer clients via the Onet.

■ Object exchange: Composer introduces a single, system-wide component database which is

called the object exchange. Object exchange provides a multiuser repository for all standard
symbols, macros, control strategies and control logic templates that are used to generate con-
trol system strategies. The object exchange is a prominent part of Composer client
applications. Users are encouraged to use system and project standards when creating auto-
mation strategies. In addition to presenting standard system objects, the object exchange
enables users to add components they have created in the object exchange.

■ Custom C programs: Load custom C programs to the controllers. Composer’s base client pro-
vides the ability to load custom C programs without the need for an additional utility.
Examples of custom applications include foreign device interfaces and performance
calculations.

■ Batch data manager: Batch data manager (BDM) is a family of engineering tools for creating,
editing, managing, downloading and debugging batch, sequential, and user defined function
(UDF) code configurations. BDM supersedes and provides migration from all previous batch
and UDF tools. BDM is comprised of three product options: Batch 90 for phase execution,
batch tools for batch sequencing, and UDF codes which are discussed in more detail in the
Optional Client Applications section of this overview.

2 WBPEEUS270001F3
 Composer

Composer Applications
The base Composer product contains all the functionality necessary to develop and maintain Sym-
phony control system configurations. There are two primary applications: explorer and
automation architect.

Explorer

The primary application of Composer is the explorer. Explorer presents the Symphony system
architecture and provides an intuitive means for organizing, navigating and locating system
configuration information. Explorer presents a user with two main windows: system architecture
and the object exchange.

System Window

The system architecture window functions similarly to Microsoft’s file explorer. The left pane of
the window displays a hierarchical representation of the Symphony system. When a system object
is selected, the right pane displays a detailed view for the selected object.

The system window supports two views: the document view (Fig. 1)and the data browser view
(Fig. 2). When the system window is in the document view, it will show the configuration docu-
ments that are associated with the system object that the user has selected. Configuration
documents support long file names and can include control logic documents, human system inter-
face displays, or documents created by other applications such as CAD packages or spreadsheets.

TC00988A

Figure 1. System Architecture - Document View

The ability to associate any documents with the system architecture is an important feature. This
allows any information, such as P&IDs, cabinet arrangement drawings or field wiring drawings,
to be managed by the configuration server and therefore accessed by Composer client applica-
tions. All that is required to edit any of these documents is to double click on the document.
Composer’s explorer will automatically launch the appropriate application for the document
selected.

WBPEEUS270001F3 3
Composer

TC00989A

Figure 2. System Architecture - Data Browser View

When the system window is in the data browser view, the right pane of the system architecture
window will display tag information associated with the system object the user has selected. All
tag information presented is retrieved from the configuration server database that is managed by
the Composer server.

When working in the data browser view, users can view, define, and modify tag data for the whole
system. This central repository of data is managed by Composer’s configuration server for all tag
data in the entire system. The data for each tag is added to the configuration server database as
each tag is defined. This eliminates the need for users to enter the same information more than
once. Some notable features of the data browser view are the ability to:

■ Edit tag objects in a datasheet or property page view.

■ Filter the database. Filtering makes configuration easier and faster by eliminating unneces-
sary information from view.

■ Import and export tag data.

■ Navigate directly from a tag to its related configuration document.

■ Perform automatic search and replace operations based on complex queries.

Object Exchange

The object exchange (object library) window presents the user with a view of the reusable compo-
nents that can be used to create control system configurations (Fig. 3). Objects are organized in
folders. Standard system components such as function codes and standard shapes and symbols
are organized under the system folder. Users are able to use these components, but they are not
permitted to delete them from the object exchange because they are part of the standard system
objects supported by Composer.

Users can define their own folders within object exchange. User-defined folders can be nested as
deeply as the user desires and provide a container for user-defined objects. User-defined objects
can include macro logic, shapes, symbols, standard drawings or control logic templates. In addi-

4 WBPEEUS270001F3
 Composer

TC00990B

Figure 3. Object Exchange

tion, user-defined folders can contain references or shortcuts to system defined objects. This
enables users to effectively organize standard system objects to best suit their needs.

To support reuse, the object exchange provides library management features such as cutting, copy-
ing, and pasting of objects between different projects. This makes it easy for systems engineers to
share objects among projects.

Automation Architect

The automation architect provides for the visual creation, editing, monitoring, and tuning of con-
trol logic. High-level control strategies can be created by dragging and dropping function codes
from the object exchange to the control logic document.

Control strategies are represented graphically by the automation architect. Rather than textually
programming strategies, the automation architect represents predefined control strategies as func-
tion blocks. By connecting function blocks (Fig. 4), users are able to specify the signal flow of a
control strategy and visually define the control strategy.

The automation architect stores configuration information in control logic documents. Control
logic documents support grouping of multiple logic sheets in a single document. This permits
users to group sheets of logic together using process partitions. For example, a single control logic
document could be used to define the control strategy for a mix tank. Each control loop or motor
control sheet associated with the mix tank could be assigned to the control logic document.
Partitioning control logic in this manner is more process object oriented and intuitive to process
engineering personnel (Fig. 5).

The monitoring and tuning capabilities (Fig. 6) of the automation architect provide the ability to
troubleshoot and maintain an operational system using the same information used to create the
system. By using the monitoring functionality, it is possible to obtain dynamic operating values
from the Symphony system. These values are automatically presented on the same control logic
documents that were used to configure the module. Composer’s tuning functionality allows the
change of logic parameters as permitted by the controller. The control logic document in the
Composer application and in the module are dynamically updated when tuning changes are
made so that the documentation for the system accurately reflects the current configuration of the
controller.

WBPEEUS270001F3 5
Composer

TC00991A

Figure 4. Automation Architect

TC00998A

Figure 5. Control Logic Document Sheets

DY N A M IC VA L U E S
T 0 26 06A

Figure 6. Monitoring and Tuning Capabilities

6 WBPEEUS270001F3
 Composer

Control Logic Templates

Two of the primary goals of Composer are to reduce the cost of implementing control strategies
and to improve the quality of Control strategy software. To realize these goals, Composer supports
a new type of document called a Control Logic Template.

Control Logic Templates (Fig 7.) define reusable standard control strategies that are typically used
to develop a process automation system. They can be thought of as blueprints that define the
structure of a control strategy. They are maintained by the object exchange and can be used to
quickly define control logic documents.

The Control Logic Template Linking functionality allows users to define logic that is controlled by
the template or can be modified within a logic document. Any subsequent changes made to a tem-
plate can then be propagated to logic documents. When a template updates its documents, it will
preserve logic additions that the user has made to the document. This template management func-
tionality provides efficient maintenance and utilization of reusable standard control logic.

TC00993A

Figure 7. Control Logic Templates

WBPEEUS270001F3 7
Composer

Optional Client Applications

HSI Options

Graphic configuration applications are options that can be added to the base Composer product.
These applications create interactive operating views of the process being controlled using stan-
dard and custom symbols and shapes. These views are used to operate processes controlled by the
Symphony system. The graphical display configuration (GDC) application is used when creating
displays for the Conductor VMS™ or INFI 90 OPEN human system interfaces. The graphic con-
figuration application (GrafX) is required when creating Operate IT™ or Conductor NT displays
(Fig. 8).

TC00994A

Figure 8. Graphic Configuration Application (GrafX)

OLE Interface

All of the controller configuration and tag configuration information is available via the OLE
interface client option of Composer. Using the OLE interface, users can access, extract and replace
configuration information stored in the Composer configuration server. Any application that is
capable of communicating via OLE/COM can access information from the Composer
configuration server via the OLE interface. Examples of applications that are capable of accessing
information via OLE include Visual Basic™, Visual Basic for Applications in Microsoft Office, or
web pages using VBScript of JScript®.

The primary advantage of accessing data via Composer’s OLE interface is allowing users to
extend the capabilities of Composer with custom scripts or add-on applications. At the same time,
users are able to rely upon the extensive data concordance rules provided by the Composer con-
figuration server.

8 WBPEEUS270001F3
 Composer

Batch Data Manager

Batch data manager (BDM) is a family of engineering tools for creating, editing, managing, down-
loading and debugging batch, sequential and user defined function code configurations.

The heart of BDM is the Batch 90 programming language. Batch 90 enables the engineer to create
batch and sequential control applications using clear, concise, natural syntax control statements.
Batch 90 is layered on top of regulatory and discrete device control function code logic. Batch 90
programs can be used to change controller set points, turn discrete devices on and off, change
modes, and perform a host of other supervisory operations. In effect, function codes execute base
regulatory and discrete device control while the Batch 90 program performs supervisory control
and process operation.

A Batch 90 program is comprised of all the phases that can be run on a specific class of equipment.
A phase is the smallest element of control that can accomplish a process-oriented task on a specific
class of equipment.

A Batch 90 phase provides a structured, modular approach to batch design by including distinct
logic sections for:

■ Normal logic executes standard sequential control.

■ Continuous control logic continuously executes a set of interlocks.

■ Fault logic executes if a stop command is issued or if a fault is detected in normal logic or
continuous control logic.

■ Hold logic executes if a hold command is issued.

■ Restart logic executes return-to-normal logic from the held or stopped states.

Batch 90 supports parallel execution of up to 32 phases, unit relative programming that allows
Batch 90 programs to be written for classes of equipment, abort logic specific to each class of
equipment, and synchronization between batch programs running in different areas of a plant.

Recipes are used to determine the procedure and formulation of the batch. A procedure deter-
mines the order in which the Batch 90 phases are executed. Formulation is the set of data that
defines the requirements for a specific product. For example, formulation could include target
flow rates, quantities, temperatures and times.

BDM applications reference their configurations in projects. This is similar to the Composer con-
cept of a project, but BDM projects are managed separately from Composer projects. A BDM
project can be located on the computer local to the user, or it can be accessed remotely over a net-
work to a mapped drive if a file server is used. A project typically encompasses a process area. A
UDF project includes the required UDF programs for a process area. A batch project references a
class library that includes a class for each type of equipment in a process area. Each class contains
the Batch 90 program associated with the class of equipment plus the unit definition files if unit
relative programming is implemented. If the unit procedure editor or master recipe editor is used,
recipes are created and managed in a separate window of the same project.

BDM is comprised of three product options:

■ Batch 90 for Phase Execution. Batch 90 for phase execution includes a full-featured text editor
to create and compile Batch 90 programs that are downloaded to the phase execution
(PHASEX) function code (Fig. 9). In this batch execution model, recipes are created and run
using ABB batch management software. The batch manager sends the phase name and

WBPEEUS270001F3 9
Composer

formulation data of the active phase in the recipe to the PHASEX function block and issues a
start command. The PHASEX block executes the phase logic. The batch manager monitors
the state of the PHASEX block and then automatically transitions to the next phase defined in
the recipe when the complete state is detected for the phase. This execution model provides
flexible configuration and easy modification of recipes. It is especially useful where many dif-
ferent products are produced, frequent product formulation changes occur, or different units
can be used to make a specific product.

285. P H A S E S U B R W AT E R
286.
287. D E C LA R AT IO N S
288. M O N ITO R IN IT _M IX E R
289. M O N ITO R AU TO _VA LV E S
290. IN T E G R ATO R TOTA L_W AT E R (F IC x04.P V,M IN )
291. N O R M A L LO G IC
292. 01 S E T F IC x04.M O D E = AU TO
293. 01 W A IT U N T IL (F IC x04.M O D E = AU TO )
294. 01 S TA RT TOTA L_W AT E R
295. 01 S E T F IC x04.S P = 60
296. 01 S E T A N D W A IT H S x04.C O = O P E N
297. 01 S E T A N D W A IT H S x05.C O = O P E N
TAG N A M E : K 10X 1411_P 1
298. 01 W A IT U N T IL (TO TA L_W AT E R .VA L> =A M N T _W AT E R )
TAG D E S C : K E T T LE 10
299. 01 S E T A N D W A IT H S x05.C O = C LO S E D
300. 01 S E T A N D W A IT H S x04.C O = C LO S E D
PHASEX
(218) 301. 01 S E T F IC x04.M O D E = M A N UA L
S1 LE A D
B LO C K S TAT E 302. 01 W A IT U N T IL (F IC x04.M O D E = M A N UA L)
S2 PHASE 303. 01 S E T F IC x04.C O =0
S PA R E ID
S3 F LT
304. 01
S PA R E
CODE 305. FAU LT LO G IC
S4
S PA R E A B O RT 306. 01 C A LL C LO S E _ VA LV E S
S5
A B O RT AQ RD
S TAT
307. 01
308. H O LD LO G IC
S PA R E
309. 01 C A LL C LO S E _ VA LV E S
S PA R E 310. 01
S PA R E 311. ENDSUBR

T 035 20A

Figure 9. PHASEX Function Code

■ Batch Tools for Batch Sequencing. Batch tools for batch sequencing include a full-featured
text editor to create and compile Batch 90 programs that are downloaded to the batch
sequence (BSEQ) function code. Also included are the unit procedure editor (Fig. 10) and the
master recipe editor which are respectively used to create unit procedures and master recipes
in a graphical format. Creation of master recipes is optional; they provide a method of linking
unit procedures for a specific production train. In this batch execution model, recipes are cre-
ated using BDM and downloaded to the controller in their entirety before the batch begins.
This execution model provides high system integrity since all the information needed to exe-
cute the batch is self-contained in the controller. It is especially useful where a limited number
of products are produced or for sequence control applications where the sequence is rarely
modified.

■ User Defined Function Codes. User defined function (UDF) codes includes a full-featured text
editor to create and compile UDF programs using natural syntax control statements similar to
Batch 90. UDF programs can be downloaded to UDF-specific function codes (Fig. 11) and
incorporated into control strategies in the same manner as any other function code. The UDF
program does not require a recipe or an operator input; it begins executing when the control-
ler begins executing. This product is especially useful for users who need to create function
codes unique to their process or for sequence control applications that execute continuously
and do not require a recipe.

The dynamic debugger, the primary troubleshooting tool for Batch 90 and UDF programs, is used
with all three product options. The dynamic debugger (Fig. 12) enables engineers to:

■ Observe process data such as variables and set points, as well as intermediate computational
values from the program including timers, ramps and integrators.

10 WBPEEUS270001F3
 Composer

TC02023A

Figure 10. Unit Procedure Editor

F U N C T IO N LoadS trap
81.
82. E X E C U TA B LE
83. 0 1
84. 0 1 C tr= 0
85. 0 1
86. 0 1 {scan R RT blo cks until C tr=9 or R r tS trapLevel.va l= -1}
87. 0 1
88. 0 1 W H IL E (C tr< = 9)
89. 0 2 IF (R rtS trapLevel.val< 0 O R (C tr= 9) T H E N
90. 0 3 M axIn dex= C tr-1
91. 0 3 BREAK
UDF1 92. 0 2 E LS E
S1 (191) 93. 0 3 S trapLevel(C tr)= R rtS tra pL evel.val
94. 0 3 S trapB bls(C tr)= R r tS trapVolum e.val
S2 95. 0 3 C tr= C tr+ 1
S3 96. 0 3 S E T R rtIndex.val= C tr
S4 97. 0 2 E N D IF
98. 0 1 E N DW H ILE
S5 99. 0 1
S6 100. 01 C tr= 0
S7 101. 01 S E T R r tIn dex.val=C tr
102. 01
S8
103. 01
S 15 104. ENDSUBR
S 17 105.

T0 3 51 9A

Figure 11. User Defined Function Code

■ Override normal operation of pumps, valves and control loops, and direct their activities
from the debugger.

■ Stop normal program operation and single-step the program to analyze data without affect-
ing other programs or function block execution.

WBPEEUS270001F3 11
Composer

■ Assign breakpoints. The program can be designed to run to a certain point and then stop exe-
cution, allowing engineers to systematically analyze logic.

■ Perform online recipe parameter editing when used with the unit procedure editor or the
master recipe editor.

TC02022A

Figure 12. Dynamic Debugger Depicting Online Recipe Parameter Editing

System Architectures

Composer can be applied to existing system architectures or new system architectures. Figure 13
shows a possible application of Composer in an existing system to replace an INFI 90 OPEN engi-
neering workstation. In this configuration the Composer client and server applications can be
loaded onto the same physical machine. Configuration files that are managed by the configuration
server are resident on the hard drive of the composer machine. Access to the local ICI is achieved
via the Composer communication server that is loaded and running on the Composer
communication server. Client applications provide users with the ability to view and edit configu-
ration information from this machine.

The Composer architecture is expandable to meet users’ changing needs. If a user wanted to
expand the architecture to accommodate additional users, it could be expanded as shown in Fig-
ure 14. In this setting the user has purchased two additional clients and expanded the server
license to accommodate three client connections. In addition, the user has purchased an additional
ICI coupler, networked the machines via TCP/IP on Ethernet™, and added a new Symphony
PCU. In this architecture, any of the client machines must be able to access the configuration
server to display configuration information. All clients can access the configuration server simul-
taneously. Clients can select the communication server that they wish to use to interact with the
run-time server. Even client machines which do not have a local connection to the ICI coupler can
access the run-time system by connecting the ICI coupler of another machine via the Ethernet.

12 WBPEEUS270001F3
 Composer

C O M P O S E R S E RV E R
C O N F IG U R AT IO N
S E RV E R
C O M M U N IC AT IO N
S E RV E R
C O M P O S E R C LIE N T A P P LIC AT IO N S
• O N -L IN E C O N T R O L M O N ITO R IN G
• O N -L IN E C O N F IG U R AT IO N C H A N G E S
• IN T E R FAC E TO C O N F IG U R AT IO N S E RV E R

C IU C O U P LE R

IN F I 90 O P E N P R O C E S S
C O N T R O L U N IT

T 03 52 1 A

Figure 13. System Architecture - Single User

International Language Support

The base Composer applications have been developed to support international languages. Config-
uration documents developed using Composer applications will accept and preserve user inputs
in any language supported by the Windows 2000 or the Windows NT operating system (Fig. 15).
When a user creates a project, Composer’s configuration server sets the default language for the
project to match the default language of the user creating the project. Once the project is created,
users can enter text into the documents and database records presented by Composer client appli-
cations. While Composer supports any of the languages supported by Windows 2000 or Windows
NT, users that require international language support should consult their regional ABB office to
ensure that the specific products they want to configure supports a specific language.

Online Documentation

Composer provides users with standard Windows help. In addition to this, all Composer docu-
mentation is provided in electronic form (Fig. 16). The instruction manuals for Composer are
provided on the product CD disk in Adobe® PDF format along with an enhanced version of
Adobe Acrobat® reader that supports a sophisticated search engine.

WBPEEUS270001F3 13
Composer

C O M P O S E R C L IE N T

C O M M U N IC AT IO N COMPOSER
S E RV E R S E RV E R
A N D C L IE N T A N D C L IE N T

C IU C O U P L E R C IU C O U P L E R

SYMPHONY IN F I 9 0 O P E N P R O C E S S
C A B IN E T C O N T R O L U N IT

T 03522B

Figure 14. System Architecture - Multiple Users

14 WBPEEUS270001F3
 Composer

TC00996A

Figure 15. International Language Support

TC00997A

Figure 16. Online Documentation

WBPEEUS270001F3 15
Composer

® Acrobat and Adobe are registered trademarks of Adobe Systems, Incorporated.

® Composer is a registered trademark of ABB.
™ Ethernet is a trademark of Xerox Corporation.
™ Symphony, OperateIT, and INFI 90 are trademarks of ABB.
® Microsoft, Windows, JScript, and Windows NT are registered trademarks of Microsoft Corporation.
™ Visual Basic is a trademark of Microsoft Corporation.
® VMS is a trademark of Digital Equipment Corporation.

For more information on the OperateIT suite of products, contact us at OperateIT@us.abb.com

For the latest information on ABB visit us on the World Wide Web at http://www.abb.com/control

WBPEEUS270001F3 Litho in U.S.A. Oct2003

Copyright © 2003 by ABB, All Rights Reserved
® Registered Trademark of ABB.
™ Trademark of ABB.

Automation Technology Products Automation Technology Products Automation Technology Products

Wickliffe, Ohio, USA Västerås, Sweden Mannheim, Germany
www.abb.com/processautomation www.abb.com/processautomation www.abb.de/processautomation
email: industrialitsolutions@us.abb.com email: processautomation@se.abb.com email: marketing.control-products@de.abb.com