Rockwell Automation 20D-DL2-CL3 User Manual

Programming Manual

Logix5000 Controllers Import/Export Project Components

Catalog Numbers 1768-L43, 1768-L45

Important user information

Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.

Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice. If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited.

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence

Important:

Identifies information that is critical for successful application and understanding of the product.

Labels may also be on or inside the equipment to provide specific precautions.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).

Allen-Bradley, Rockwell Software, Rockwell Au tomation, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are prope rty of their respective companies.

Summary of changes

This manual contains new and updated information. This table contains the changes made to this revision.

Topic Page

Introduction: Added a description of Library Management. See Introduction on page 9.

Export Components: Updated procedure to explain the difference between exporting programs from the Logical Organizer versus the Controller Organizer.

Export Considerations: Added a bullet to explain the difference between exporting programs from the Logical Organizer versus the Controller Organizer.

Configure Component Import: Updated dialog box graphic. See Properties for imported components on page

Configure Multiple Components: Added new section to describe importing multiple components.

Online Import Considerations: Added explanation for new 'Preserve existing tag values in offline project checkbox.

Multiple Components Considerations: Added considerations for importing multiple components.

Search and Replace: Updated procedure to explain the new Replace All option.

Equipment Phases: Added new import considerations. See Import considerations on page 43.

Tags: Added new import considerations. See Import considerations on page 43.

See Export logic components on page 11.

16.

See Configure multiple component properties on

page 21.

See Online import on page 12.

See Multiple components on page 15.

See Find and replace on page 35.

Rockwell Automation Publication 1756-PM019E-EN-E - October 2014 3

Preface

Import and export logic

Additional considerations for

components

Studio 5000 environment ..................................................................................... 7

Chapter 1

Introduction ............................................................................................................ 9

Export considerations .......................................................................................... 10

Export logic components..................................................................................... 11

Import considerations .......................................................................................... 12

Online import ................................................................................................ 12

Motion ............................................................................................................. 14

Safety ................................................................................................................ 15

Security ............................................................................................................ 15

Multiple components ................................................................................... 15

Import logic components .................................................................................... 15

Configuration properties for import ................................................................. 16

Properties for imported components ......................................................... 16

Configure multiple component properties ............................................... 21

Configure program connections ................................................................. 24

Configure component references ............................................................... 29

References configuration example .............................................................. 31

Undefined references .................................................................................... 32

Attention flags ................................................................................................ 33

Errors and warnings on import ................................................................... 33

Project documentation ........................................................................................ 33

Find and replace .................................................................................................... 35

compatibility .................................................................................................. 36

rungs

routines

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 5

Chapter 2

Introduction .......................................................................................................... 39

Export considerations .......................................................................................... 39

Import considerations .......................................................................................... 39

Chapter 3

Introduction .......................................................................................................... 41

Export considerations .......................................................................................... 41

Import considerations .......................................................................................... 41

Table of Contents

Additional considerations for Additional considerations for

Import and export Add-On

Additional considerations for Index

programs and equipment phases

user-defined types

Instructions

Chapter 4

Introduction .......................................................................................................... 43

Export considerations .......................................................................................... 43

Import considerations .......................................................................................... 43

Chapter 5

Introduction .......................................................................................................... 45

Export considerations .......................................................................................... 45

Import considerations .......................................................................................... 45

Chapter 6

Introduction .......................................................................................................... 47

Create export files ................................................................................................. 47

Export to separate files .................................................................................. 48

Export to one file ........................................................................................... 49

Import an Add-On Instruction ......................................................................... 50

Import considerations .................................................................................. 50

Import configuration .................................................................................... 52

Update an Add-On Instruction to a later revision using import ................. 53

Studio 5000 environment

Preface

Use this manual to become familiar with importing and exporting project components for Logix5000 controllers. The project components covered in this manual include the importing and exporting of rungs, routines, programs and equipment phases, user-defined types, tags, and Add-On Instructions.

This manual is one of a set of related manuals that show common procedures for programming and operating Logix5000 controllers.

For a complete list of common procedures manuals, see the

Common Procedures Programming Manual, publication 1756-PM001.

The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system.

The Studio 5000 Automation Engineering & Design Environment™ combines

engineering and design elements into a common environment. The first element is the Studio 5000 Logix Designer™ application. The Logix Designer application is the rebranding of RSLogix™ 5000 software and will continue to be the product to program Logix5000™ controllers for discrete, process, batch, motion, safety, and drive-based solutions.

Logix5000 Controllers

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 7

The Studio 5000® environment is the foundation for the future of Rockwell Automation® engineering design tools and capabilities. The Studio 5000 environment is the one place for design engineers to develop all elements of their control system.

Introduction

Chapter 1

Import and export logic components

This chapter explains import and export of logic components.

You use the Logix Designer application to perform online edits for the Logix family of controllers.

The import/export functionality provides a greater degree of flexibility during development and deployment of projects. It supports the ability to export a component of a Logix Designer project and then import that component into either the same, or a different project, offline or online (even in Remote Run mode). It lets you import components to create something new in a project, or to update something that exists.

You can export and import these logic components offline and online:

• Rungs

• Routines

• Programs and equipment phases

• User-defined data types (UDT)/user-defined string types

• Add-On Instructions

• Trends

Changes or additions to a project that may be impractical to do with online editing can be completed offline and then imported in one operation into a running controller by using the extended import/export feature. Engineering collaboration is also facilitated because many engineers can work on one or more of the project components independently offline and then use import to merge the changes into one project.

With online editing, you modify or create a component and then modify other components referenced by that component in the project sequentially. Importing online differs from online edits in that it provides the ability to create and delete components, as well as update referenced components, in one step.

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 9

ATTENTION: All Rockwell Automation XML files are encoded in UTF-8 file format. Users editing XML files

must use a text editor like Notepad that supports UTF-8 encoding. If you save the edited file by using a nonUTF-8 compatible editor after making changes, the encoding breaks, resulting in a non-valid XML file.

Chapter 1 Import and export logic components

Export considerations

Keep the following considerations in mind when exporting components.

• You may get more than you expected in an .l5x file. Some components

referenced by the exported component are also exported.

• Starting with version 24 of Logix Designer, you can use program parameters

to share data directly between programs in addition to Controller-scoped tags. For more information on program parameters, see the

Logix5000 Controllers Program Parameters Programming Manual publication 1756PM021.

When exporting a

Set of rungs Rungs Controller-scoped tags, program-scoped tags,

Routine Routine Controller-scoped tags, program-scoped tags,

Program

(For considerations when exporting multiple programs using multi-

Multiple

select, see

components on page 15.

Equipment Phase Equipment phase, routines, phase-

User-defined data type User-defined data type User-defined data types, user-defined string

User-defined string type User-defined string type

Add-On Instruction Add-On Instruction, Logic routine and

Trend Trend

The exported component includes the

Program, routines, and program-scoped tags

scoped tags, and controller-scoped PHASE tag

any scan mode routines, and parameter and local tags

The exported file also includes referenced

user-defined data types, user-defined string types, Add-On Instructions

Controller-scoped tags, user-defined data types, user-defined string types, Add-On Instructions

When you export a program from the Logical Organizer, the program logical hierarchy is exported in addition to the program specified. See the online help for information about the Logical Organizer.

Controller-scoped tags, user-defined data types, user-defined string types, Add-On Instructions

types, Add-On Instructions

User-defined data types, user-defined string types, Add-On Instructions

10 Rockwell Automation Publication 1756-PM019E -EN-E - October 2014

For example, if you export a rung with an instruction that uses (references) a bit in a tag that is a user-defined type tag, the export content includes the referenced tag and the referenced user-defined type, along with the rungs. When you import the rung, you can choose whether to also import the referenced tag and user-defined type.

Import and export logic components Chapter 1

Export logic components

• Only the offline data values of tags are exported to the .l5x file, even when

the project is online with the controller. When exporting components that include tags while online, the software prompts you to upload tag values before exporting the component.

Important:

Whether exporting while offline or online with the controller, only offline data values of tags are exported to the .l5x file.

• You can export a component that has Test Edits, but the resulting file

cannot be imported. If an .l5x file with Test Edits is selected for import, then the import aborts.

Follow these steps to export logic components.

1. In the Logix Designer Controller Organizer, select the logic component to

export.

Tip:

You can select multiple programs, Add-On Instructions, and user-defined data types for export. See

Import and export Add-On Instructions on page 49 for detailed information.

You can also export logical components from the Logical Organizer, where you can select multiple programs and include child folders and programs in their hierarchical levels. See the Logix Designer application online he lp for instructions.

2. Right-click and select Export <logic component> as explained in the

following table.

To export a Choose

Set of rungs (For rung export, select the rungs in the ladder routine editor.)

Routine

Program

Equipment Phase

User-defined data type

User-defined string type

Add-On Instruction

Trend

Export Rungs

Export Routine

Export Program

Export Equipment Phase

Export Data Type

Export Add-On Instruction

Export Trend

3. In the File Name box, type a file name for the export file.

Tip:

You can export multiple Add-On Instructions to a single file or to multiple files. See

component properties on page 21 for detailed information.

Configure multiple

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 11

Chapter 1 Import and export logic components

The timeout is caused by the (scan time) x (number of changed rungs). You could have a large program with

Import considerations

4. (Optional) In the File description, edit the default description or type a

description, if desired.

A default description is supplied for some component exports.

Tip:

The file description can be viewed in a tooltip during import when selecting which file to import.

5. Click Export.

This section covers general considerations for all component-type imports. See the

chapters for specific components (program, routine, rungs, Add-On Instructions, user-defined data types, and tags) for additional export and import considerations for that component, whether it is imported directly or as a reference during another component import.

Important:

Tip:

When editing online, if the program scan time is large, or the number of modified rungs is large, you might see HMI and Logix Designer communication timeouts when edits are finalized.

a very fast scan, or a lot of rungs (but you modified only a few), and you do not see a timeout.

Starting with version 24 of Logix Designer application, you can use program parameters to share data between programs in much the same way that you use controller-scoped tags. Program parameters are imported and exported in the same way as tags in most instances. For more information on program parameters, see the

Logix5000 Controllers Program Parameters Programming Manual, publication 1756-PM021

Online Import

Topic Consideration

Tag data values When overwriting tags while online, data values are not written to the online project. Data

values for overwritten tags while online are written only to the offline project.

Data values for tags created while online are written to the offline and online project.

Select the Preserve existing tag values in offline project check box to prevent tag values from being overwritten in the offline project.

Locking controller edits When performing an online import, the controller is locked, preventing other workstations

connected to the controller from making edits until the import completes. If another workstation has the controller locked, an online import cannot be initiated.

Tag attributes

12 Rockwell Automation Publication 1756-PM019E -EN-E - October 2014

Tag attributes (for example, External Access, Constant, and Style) are written to the online project and the offline project.

If existing tags are to be overwritten with new attributes that are incompatible with existing user logic, the import is not allowed.

Import and export logic components Chapter 1

program, or routine properties that are modified are downloaded immediately. These changes

Topic Consideration

Online options When importing programs, equipment phases, routines, or rungs online, the logic can be

imported as:

• Pending Edits that exist only in the offline project and are not downloaded to the

controller.

• Accepted Edits that are downloaded to the controller where they can be tested, accepted,

or canceled.

• Finalized Edits that are downloaded to the controller, assembled, and cannot be canceled.

As with normal online editing, with any online option chosen, any tags, data types, or Add-On Instructions that are created or modified are downloaded immediately. In addition, any task,

remain in the controller, even if logic edits are later canceled. Pending Edits and Accepted Edits options do not apply to Add-On Instructions and user-defined types, so Online Options are not presented during an Add-On Instruction or user-defined type import.

Under the following conditions, only the Finalize All Edits in Program option is available.

• When you are online with t he controller and you import a program that contains

connections to InOut parameters and:

− You change the final connection of an InOut parameter online.

• When the connections are different than what is currently downloaded to the controller.

Finalize All Edits In Program is your only option because you chose to overwrite the program on Import. You must configure the InOut connections such that the InOut parameter connection is taken not from the destination controller but from the Import file, or from a new final name for the connection entered by the user.

• When you import a program or programs with connections online and in Remote Run

mode, and:

− A connection is changed from connect to disconnect.

− A connection is changed from disconnect to connect.

− The final name of a connection is changed.

− A connection is added and its operation is set to connect.

• When you import program hierarchies or multiple programs online and in Remote Run

mode.

External access If the External Access is changed, it may change the behavior of your running HMI.

Changed External Access attributes for overwritten tags can cause changes to HMI behavior, regardless of whether logic changes are tested, accepted, or finalized.

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 13

Chapter 1 Import and export logic components

ne (choosing Finalize Edits) does not cause the communication timeout,

Topic Consideration

Asynchronous import Import operations are not synchronized with the Program Scan (just as online editing

operations are not synchronized). For most objects, this does not matter because:

• Existing online tag data values are never overwritten.

• New tags and their initial data values are written to the controller before the new logic

runs.

• The switch-over to the new logic is synchronized with the program scan (just like online

editing).

In general, although online tag data values are not overwritten, some object attributes can change asynchronously to the Program Scan. Some examples:

• Changed attributes of existing programs or equipment phases (such as changing the Initial

Step Index of an equipment phase) are written to the controller before switch-over, so old logic can run with the new configuration.

• An existing program without a main routine could become configured with a main routine

as part of import, and that main routine runs immediately even though the new logic for that routine has not yet been accepted.

• Changing Logix-based alarm tag configuration (such as alarm messages or associated tag

definitions) can go into effect while the old alarm trigger logic is still active, resulting in alarm messages that do not match the condition.

Communication timeouts Communication timeouts may occur when rungs are deleted online in Run mode if the

program scan time is long or the number of rungs being deleted is large.

If you use Partial Import Online and choose Pending or Accept edits, when you later Finalize those edits, a timeout can occur. This timeout can occur as HMI or Logix Designer communication timeouts. Keep the following timing considerations in mind.

• Finalizing online edits while in Run mode causes brief interruptions to communication,

which are usually unnoticeable.

• The length of the communication interruption is related to the product of the (task scan

time) x (the number of changed rungs).

• When very long program scans or large quantities of changed rungs occur, the

communication interruption can be long enough to cause timeouts.

• The timeout of a Rockwell Automation HMI is typically 8 seconds, while a Logix Designer

online session typically has a 30-second timeout.

• It does not matter whether the edits came from individual online edits or from a Partial

Import Online (choosing Pending or Accepted edits).

• Partial Import Onli

due to the use of asynchronous transaction commit processing.

Motion

Topic Consideration

Motion components limitations while online

14 Rockwell Automation Publication 1756-PM019E -EN-E - October 2014

Motion tags (Axis, Coordinate System, and Motion Group) cannot be created, modified or deleted during an online import, however, existing motion tags can be referenced. When doing an offline import, motion tags can be created and modified.

Import and export logic components Chapter 1

Import logic components

Safety

Topic Consideration

Safety components limitations while online

Safety components limitations while offline

Scheduled location In a Safety project, Safety programs cannot be imported into a Standard task and vice

Safety programs imported into a standard project

Controller Fault Handler and Power-Up Handler

Safety components cannot be created, modified or deleted during an online import.

Safety components cannot be created, modified or deleted during an offline import. If a Safety Signature exists, the project is Safety locked. A non-recoverable safety fault is present if the Safety Partnership status between the primary controller and the safety partner is any value other than ‘OK’, or if Safety modify permissions are denied.

versa.

Safety programs imported into a Standard project are converted to Standard programs during the import processing and a warning appears in the Errors/Results Pane during initial parsing of the .l5x file. In this case, imported logic does not verify after import if it contains instructions that are only valid in a Safety routine.

A Safety program cannot be scheduled in the Controller Fault Handler or Power-Up Handler folders.

Security

Topic Consideration

Project is secured If the project is secured, the import process may not be able to create, delete, or modify some

components, depending on the security actions that have been granted or denied for those components.

Multiple components

Topic Consideration

Importing multiple Userdefined types (UDTs) and Add-On Instructions.

Controller Fault Handler and Power-Up Handler disabled

Follow these steps to import logic components. You can import components from

the Controller Organizer and from the Logical Organizer.

When User-defined types (UDTs) and Add-On Instructions are imported using the Multiple Components option, all UDTs and Add-On Instructions are treated as references. Unlike child components, referenced components can be configured independently from the import target.

When you import multiple target programs, the Controller Fault Handler and Power-Up Handler are unavailable in the Schedule In list.

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 15

Importing components into a controller while online can affect controller operation. Use caution when modifying logic while online in Remote Run or Run mo de.

1. Right-click the item and choose the import component menu item as

described in the following table.

Chapter 1 Import and export logic components

Configuration properties

To import a Right-click And choose

Set of rungs A rung or set of rungs within a Ladder routine

editor

Routine A program or equipment phase

Program A task, the Controller Fault Handler folder, the

Power-Up Handler folder, or the Unscheduled Programs/Phases folder

Equipment Phase A task or the Unscheduled Programs/Phases folder

Import Rungs

Import Routine

Import Program

Import Equipment Phase

for import

User-defined data type User-Defined folder

User-defined string type Strings folder

Add-On Instruction Add-On Instructions folder

Trend Trends folder

Import Data Type

Import String Type

Import Add-On Instruction

Import Trend

2. Select the file to import.

You can select multiple components for import. See

Configure multiple

component properties on page 21 for information.

3. Click Import.

4. Continue by selecting the configuration options described in Configuration

properties for import.

This section describes configuration options for importing components.

Tip:

Trends do not require any import configuration, so the Import Configuration dialog box does not appear and the trend is imported immediately.

16 Rockwell Automation Publication 1756-PM019E -EN-E - October 2014

Properties for imported components

When you import components, the previously exported information is brought into the project based on the import configuration you select. You determine how the imported component (a program, for example) connects to the existing project either by overwriting an existing component of the same type, or by creating a new one.

Import and export logic components Chapter 1

The following screen capture shows a typical Import Configuration dialog box. Your dialog box might contain options different than those shown here, depending on the component you import.

An import component collides with an existing component if a component of the same type, scope, and with the same name exists in the project. By configuring the Final Name of the imported component, you determine whether the imported component collides with an existing component, or it does not (if a component of the same type, scope and with the same name does not exist in the project). For a collision, you can use the existing project component or you can overwrite it. For a non-collision, you can create a project component or you can discard, and not import, the component from the import file. In any case, any imported logic references are updated to be the same as the Final Name.

By configuring the Operation for the component, you determine whether it is imported from the file or an existing component is used. Incompatibility of a

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 17

Chapter 1 Import and export logic components

collision or other situations, for example, project security privileges, may affect what Operations are permitted for a component.

The following table describes the configuration options.

Configuration Description

Import Name

Operation

Final Name

Description

The Import Name is read-only and shows the name of the component as read from the import file.

The Operation determines whether the component from the import file is imported. Not all operations are applicable to a given component in all situations. Sometimes there is only one possible operation permitted in a particular situation.

Choose from these options:

• Use Existing (collisions) to use the existing component in the project. The component

definition in the import file is not imported. If the component collides and there is no definition for the component in the import file, then this is the only Operation available.

• Overwrite (collisions) to import the component definition from the import file and

overwrite the existing component definition in the project.

Important: If you select Overwrite for a reference tag, the tag data that is different is written to the offline project only, even if you are online with the controller.

• Create (non-collisions) to import the component from the import file creating a new

component in the project.

• Discard (non-collisions) to discard the component and abort import. If the main

component from the import file (the program during a program import, for example) is discarded, the references can still be imported. If a referenced component is discarded, any imported logic references are not defined in the project and might not verify after impor t.

• Undefined (non-collision) is the only Operation available if the component does not

collide and there is no definition for the component in the import file. The imported logic is not verified after import.

• Delete (non-collision) indicates that this component will be deleted from the project

on import.

The Final Name determines the name of the component that shows in the project after the import (except in the case of a Delete Operation).

You can create or avoid collisions by changing the Final Name. If you change the Final Name to differ from the Import Name, all logic references in the import content are updated.

If you change the Final Name of a component during configuration so that it collides with a different existing component after it was colliding with another, any changes you made to the Operation are preserved.

The Description shown depends on the Operation. If the Operation is:

• Overwrite or Create, the description is initially the description from the import file.

You can edit it during import configuration.

• Discard, the description is initially the description from the import file. It is read-only

and may not be edited.

• Use Existing or Delete, the description is the existing component description. It is

read-only and may not be edited.

• Undefined, no description is shown.

The description for members of an expanded tag follow the same rule the tag follows. Only members of the tag that have descriptions are shown when the tag is expanded.

18 Rockwell Automation Publication 1756-PM019E -EN-E - October 2014

Import and export logic components Chapter 1

Configuration Description

Schedule In

Preserve scheduling for child programs that already exist

The Schedule In setting determines the task in which the imported component is scheduled.

The default setting for Schedule In depends on the Operation setting and whether you import the component into the Controller Organizer or the Logical Organizer.

If you import the component into the Controller Organizer:

• When you select a task or handler, and Operation is set to Overwrite, Schedule In is

set to the selected task or handler.

• When you select a task or handler and Operation is set to Use Existing, Schedule In

is set to the task or handler where the program is scheduled in the destination project.

• When the selection in Controller Organizer is not a task or handler, Schedule In is set

to Unscheduled Programs/Phases.

If you import the component into the Logical Organizer:

• When you set Operation to Create or Disca rd, Schedule In is set to Unscheduled

Programs/Phases.

• When you set Operation to Use Existing or Overwrite, Schedule In is set to the Task

or Handler for which the program is scheduled in the destination project.

You can adjust the S chedule In setting when:

• Operation is set to Create (the target component is being created).

• Operation is set to Overwrite and you are not online in Remote Run mode.

You cannot change the Schedule In setting when:

• You import a program folder.

• Operation is set to any setting other than Create or Overwrite.

When you select this setting, any child programs that exist in the destination project remain scheduled as configured in the project. When you clear this setting, all imported programs are scheduled in the task specified by the Schedule In setting.

This setting is available when Operation is set to Create or Overwrite; otherwise it is read-only. When enabled, this setting is selected by default. The setting is not preserved between import sessions.

Rockwell Automation Publication 1756-PM019E -EN-E - October 2014 19

+ 43 hidden pages

Rockwell Automation 20D-DL2-CL3 User Manual

Logix5000 Controllers Import/Export Project Components

Important user information

Summary of changes

Table of contents

Studio 5000 environment

Preface

Introduction

Export considerations

Export logic components

Import considerations

Import logic components