Design process

The

Application Code Manager

(ACM) design process introduces a modular, object-based approach to the creation of ACD controller code,

FactoryTalk® View Site Edition (SE)

or

FactoryTalk® View Machine Edition (ME)

display content,

FactoryTalk®

Historian Tags and Alarms import configuration.

The

Studio 5000

ACM design process separates function and configuration into two separate layers of data, and divides the design process into two distinct workflows, library management and project execution.

The design process involves a suite of applications:

Library management workflow:

Studio 5000 Logix Designer

The library management workflow begins when a specific instance of ACD controller code is created in the

Logix Designer

application. The specific instance is a single project containing a single controller. The project includes a logical structure containing these Logix objects:

Each Logix object has an internal hierarchy of elements. For example, a task may contain one or more programs, each of which may contain one or more routines.

Every project has one controller. There may be one, many, or no instances of any type of Logix object in the project when the specific instance is created. This single instance of controller code is saved to an ACD file.

Traditionally, controller code was designed and configured for a specific project. In the library management workflow, content is not designed for a specific project, but to provide a widely applicable set of functions known as project components that are then used to create library objects. Each library object is an independent functional entity that can be easily configured to meet a wide range of applications and can be used in many projects.

Use the

Library Designer

to assign the project, the controller, and any of the Logix objects to one or many library objects. Each library object defines a set of functions, capabilities, and connections. For example, those that support the function of the valve, motor, and controller modules. Rather than being tied to one application, library objects can be configured to meet the needs of multiple applications. The

Library Designer

allows the publishing of a library directly into an ACM database. Options include the ability to specify the location where the library will be published in the ACM database, and the ability to specify the status of the library, either Published or Pending.

Custom properties called "Decorations" can be added to a library object using the

Library Designer

. Decorations include parameters, subobjects, functions, substitutions, and external references. Decoration lets the library object be configured when it is implemented in a project in the ACM application.

Logix objects can be restricted to a single library object or assigned to multiple library objects, each with a different set of decorations. A library object can contain a single Logix object, or a Logix object can be added as an element of a more complex library object. For example, a P_Alarm Add-On Instruction can be assigned to a valve library object and can also be an element of a Motor or Pump library object.

Each ACD file can support multiple projects, controller libraries, and library objects. The ACD is not required to contain a project or controller library. While the decoration is stored as part of the ACD file, it is treated as a separate layer of information from the base controller code and does not affect code execution.

Decoration controls how the library object is instantiated, including configurations such as naming, tag values, conditional inclusion, and connections to other library objects. One or many distinct instances of a library object can be instantiated within an ACM project and each instance can be separately configured. Using

Library Designer

, each Logix object can be published directly to the ACM database or to a file in HSL4 format.

The library management workflow continues by opening the decorated ACD file in the

Library Object Manager

application. The

Library Object Manager

application can be used to publish each library object, either directly to the ACM database or to a file in HSL4 format. HSL4 files can be distributed individually or as part of a repository.

Use

Library Object Manager

to add HMI displays (

FactoryTalk View SE

or

FactoryTalk View ME

),

FactoryTalk® Alarms and Events

configurations,

FactoryTalk View ME

Alarms and Historian (

FactoryTalk® Historian Site Edition

) components to the library object. This can only be done after the library object has been published from the ACD file to a folder or ACM database. The features added in the

Library Object Manager

application are saved to the individual HSL4 file or database entry for the library object and are not saved to the original ACD file.

Each library object file saved from the

Library Object Manager

application is classified within a four-level hierarchy:

For example, an analog input module might be classified as:

Each library object file must have a distinct version number per solution. Just as the same Logix object can be used to create one or many library objects within the

Library Designer

, the same library object can be used to create one or many distinct library object files (versions) within the

Library Object Manager

application.

Library objects can be quickly distributed, then registered into and configured for multiple Projects in multiple locations. Library objects are available to any project that requires the functionality the library object provides.

Using

Library Object Manager

new library objects can be created and distributed rapidly to meet the needs of specific applications.

FactoryTalk View

Studio

Use

FactoryTalk View

Studio to create Site Edition (SE) and Machine Edition (ME) graphic displays. When the graphic displays are exported to XML, they are called "Symbol objects." The XML files can be imported into the

Library Object Manager

application and the graphic displays added as non-Logix content to library objects.

The Project Execution Workflow:

Application Code Manager

In the

Application Code Manager

application, library objects become the building blocks used to create and deploy projects rapidly.

Execution is simply a matter of registering, adding, and configuring the library objects. Projects can be completed without requiring high-end programming support.

In the project execution workflow, library objects are selected in the ACM application and then the library object parameters are configured to meet the requirements of the current application. The workflow is complete when the Project to ACD controller code is created.

During the project, new library objects can be created using

Library Designer

, library objects from previous projects can be reused, or library objects can be shared from other databases.

After the project is complete, it can be used to create library objects so that future projects can use the solutions developed.