Embed Size (px)
Citation preview
Programming Manual
Catalog Numbers 1756-L1 1756-L551756-L61 1756-L62 1756-L63 1769-
L31 1769-L32C 1769-L32E 1769-L35CR 1769-L35E 1789-L60 1794-L34
PowerFlex 700SSE
Logix5000 Controllers Produced and Consumed Tags
Important User InformationSolid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls (publication SGI-11 available from your local Rockwell Automation sales office or online at httpliteraturerockwellautomationcom) describes some important differences between solid state equipment and hard-wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable
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
Allen-Bradley Rockwell Automation and TechConnect are trademarks of Rockwell Automation Inc
Trademarks not belonging to Rockwell Automation are property of their respective companies
WARNINGIdentifies 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
IMPORTANT Identifies information that is critical for successful application and understanding of the product
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
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
Table of ContentsPreface Purpose of this Manual 5
How to Use this Manual 5
Chapter 1Produce and Consume a Tag Introduction 7
Controllers and Networks that Support ProducedConsumed Tags 7Connection Requirements of a Produced or Consumed Tag 8Organize Tags for Produced or Consumed Data 9
Adjust for Bandwidth Limitations 10Produce a Tag 10Consume Data That Is Produced by Another Controller 11
Additional Steps for a PLC-5C Controller 14Verify Consumed Tag Requested Packet Interval (RPI) Limitations 15
Chapter 2Producing a Large Array Introduction 17
Produce a Large Array 18
3Publication 1756-PM011B-EN-P - July 2008 3
4Publication 1756-PM011B-EN-P - July 2008 4
Preface
Purpose of this Manual This manual shows how to configure and use produced and consumed tags 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 Logix 5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
bull CompactLogix controllersbull ControlLogix controllersbull DriveLogix controllersbull FlexLogix controllersbull SoftLogix5800 controllers
How to Use this Manual Some text is formatted differently from the rest of the text
Text that is Identifies For example Means
Italic the actual name of an item that you see on your screen or in an example
Right-click User-Defined hellip Right-click the item that is named User-Defined
courier information that you must supply based on your application (a variable)
Right-click name_of_program hellip
You must identify the specific program in your application Typically it is a name or variable that you have defined
enclosed in brackets a keyboard key Press [Enter] Press the Enter key
5Publication 1756-PM011B-EN-P - July 2008 5
Preface
Notes
6 Publication 1756-PM011B-EN-P - July 2008
Chapter 1
Produce and Consume a Tag
Introduction A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags
Controllers and Networks that Support ProducedConsumed Tags
These combinations support produced and consumed tags
controller_2
controller_3
controller_4
consumed tag
consumed tag
consumed tag
controller_1
produced tag
Term Definition
Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume (receive) the data A produced tag sends its data to one or more consumed tags (consumers) without using logic The produced tag sends its data at the RPI of the consuming tag
Consumed tag A tag that receives the data of a produced tag The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag The RPI of the consumed tag determines the period at which the data updates
This controller Can produce and consume tags over this network
Backplane ControlNet EtherNetIP
SLC 500 E
PLC-5 E
CompactLogix(1) E E
ControlLogix E E E
DriveLogix E E
FlexLogix E E
SoftLogix5800 E
7Publication 1756-PM011B-EN-P - July 2008 7
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Important User InformationSolid state equipment has operational characteristics differing from those of electromechanical equipment Safety Guidelines for the Application Installation and Maintenance of Solid State Controls (publication SGI-11 available from your local Rockwell Automation sales office or online at httpliteraturerockwellautomationcom) describes some important differences between solid state equipment and hard-wired electromechanical devices Because of this difference and also because of the wide variety of uses for solid state equipment all persons responsible for applying this equipment must satisfy themselves that each intended application of this equipment is acceptable
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
Allen-Bradley Rockwell Automation and TechConnect are trademarks of Rockwell Automation Inc
Trademarks not belonging to Rockwell Automation are property of their respective companies
WARNINGIdentifies 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
IMPORTANT Identifies information that is critical for successful application and understanding of the product
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
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
Table of ContentsPreface Purpose of this Manual 5
How to Use this Manual 5
Chapter 1Produce and Consume a Tag Introduction 7
Controllers and Networks that Support ProducedConsumed Tags 7Connection Requirements of a Produced or Consumed Tag 8Organize Tags for Produced or Consumed Data 9
Adjust for Bandwidth Limitations 10Produce a Tag 10Consume Data That Is Produced by Another Controller 11
Additional Steps for a PLC-5C Controller 14Verify Consumed Tag Requested Packet Interval (RPI) Limitations 15
Chapter 2Producing a Large Array Introduction 17
Produce a Large Array 18
3Publication 1756-PM011B-EN-P - July 2008 3
4Publication 1756-PM011B-EN-P - July 2008 4
Preface
Purpose of this Manual This manual shows how to configure and use produced and consumed tags 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 Logix 5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
bull CompactLogix controllersbull ControlLogix controllersbull DriveLogix controllersbull FlexLogix controllersbull SoftLogix5800 controllers
How to Use this Manual Some text is formatted differently from the rest of the text
Text that is Identifies For example Means
Italic the actual name of an item that you see on your screen or in an example
Right-click User-Defined hellip Right-click the item that is named User-Defined
courier information that you must supply based on your application (a variable)
Right-click name_of_program hellip
You must identify the specific program in your application Typically it is a name or variable that you have defined
enclosed in brackets a keyboard key Press [Enter] Press the Enter key
5Publication 1756-PM011B-EN-P - July 2008 5
Preface
Notes
6 Publication 1756-PM011B-EN-P - July 2008
Chapter 1
Produce and Consume a Tag
Introduction A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags
Controllers and Networks that Support ProducedConsumed Tags
These combinations support produced and consumed tags
controller_2
controller_3
controller_4
consumed tag
consumed tag
consumed tag
controller_1
produced tag
Term Definition
Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume (receive) the data A produced tag sends its data to one or more consumed tags (consumers) without using logic The produced tag sends its data at the RPI of the consuming tag
Consumed tag A tag that receives the data of a produced tag The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag The RPI of the consumed tag determines the period at which the data updates
This controller Can produce and consume tags over this network
Backplane ControlNet EtherNetIP
SLC 500 E
PLC-5 E
CompactLogix(1) E E
ControlLogix E E E
DriveLogix E E
FlexLogix E E
SoftLogix5800 E
7Publication 1756-PM011B-EN-P - July 2008 7
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Table of ContentsPreface Purpose of this Manual 5
How to Use this Manual 5
Chapter 1Produce and Consume a Tag Introduction 7
Controllers and Networks that Support ProducedConsumed Tags 7Connection Requirements of a Produced or Consumed Tag 8Organize Tags for Produced or Consumed Data 9
Adjust for Bandwidth Limitations 10Produce a Tag 10Consume Data That Is Produced by Another Controller 11
Additional Steps for a PLC-5C Controller 14Verify Consumed Tag Requested Packet Interval (RPI) Limitations 15
Chapter 2Producing a Large Array Introduction 17
Produce a Large Array 18
3Publication 1756-PM011B-EN-P - July 2008 3
4Publication 1756-PM011B-EN-P - July 2008 4
Preface
Purpose of this Manual This manual shows how to configure and use produced and consumed tags 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 Logix 5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
bull CompactLogix controllersbull ControlLogix controllersbull DriveLogix controllersbull FlexLogix controllersbull SoftLogix5800 controllers
How to Use this Manual Some text is formatted differently from the rest of the text
Text that is Identifies For example Means
Italic the actual name of an item that you see on your screen or in an example
Right-click User-Defined hellip Right-click the item that is named User-Defined
courier information that you must supply based on your application (a variable)
Right-click name_of_program hellip
You must identify the specific program in your application Typically it is a name or variable that you have defined
enclosed in brackets a keyboard key Press [Enter] Press the Enter key
5Publication 1756-PM011B-EN-P - July 2008 5
Preface
Notes
6 Publication 1756-PM011B-EN-P - July 2008
Chapter 1
Produce and Consume a Tag
Introduction A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags
Controllers and Networks that Support ProducedConsumed Tags
These combinations support produced and consumed tags
controller_2
controller_3
controller_4
consumed tag
consumed tag
consumed tag
controller_1
produced tag
Term Definition
Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume (receive) the data A produced tag sends its data to one or more consumed tags (consumers) without using logic The produced tag sends its data at the RPI of the consuming tag
Consumed tag A tag that receives the data of a produced tag The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag The RPI of the consumed tag determines the period at which the data updates
This controller Can produce and consume tags over this network
Backplane ControlNet EtherNetIP
SLC 500 E
PLC-5 E
CompactLogix(1) E E
ControlLogix E E E
DriveLogix E E
FlexLogix E E
SoftLogix5800 E
7Publication 1756-PM011B-EN-P - July 2008 7
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
4Publication 1756-PM011B-EN-P - July 2008 4
Preface
Purpose of this Manual This manual shows how to configure and use produced and consumed tags 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 Logix 5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
bull CompactLogix controllersbull ControlLogix controllersbull DriveLogix controllersbull FlexLogix controllersbull SoftLogix5800 controllers
How to Use this Manual Some text is formatted differently from the rest of the text
Text that is Identifies For example Means
Italic the actual name of an item that you see on your screen or in an example
Right-click User-Defined hellip Right-click the item that is named User-Defined
courier information that you must supply based on your application (a variable)
Right-click name_of_program hellip
You must identify the specific program in your application Typically it is a name or variable that you have defined
enclosed in brackets a keyboard key Press [Enter] Press the Enter key
5Publication 1756-PM011B-EN-P - July 2008 5
Preface
Notes
6 Publication 1756-PM011B-EN-P - July 2008
Chapter 1
Produce and Consume a Tag
Introduction A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags
Controllers and Networks that Support ProducedConsumed Tags
These combinations support produced and consumed tags
controller_2
controller_3
controller_4
consumed tag
consumed tag
consumed tag
controller_1
produced tag
Term Definition
Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume (receive) the data A produced tag sends its data to one or more consumed tags (consumers) without using logic The produced tag sends its data at the RPI of the consuming tag
Consumed tag A tag that receives the data of a produced tag The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag The RPI of the consumed tag determines the period at which the data updates
This controller Can produce and consume tags over this network
Backplane ControlNet EtherNetIP
SLC 500 E
PLC-5 E
CompactLogix(1) E E
ControlLogix E E E
DriveLogix E E
FlexLogix E E
SoftLogix5800 E
7Publication 1756-PM011B-EN-P - July 2008 7
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Preface
Purpose of this Manual This manual shows how to configure and use produced and consumed tags 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 Logix 5000 Controllers Common Procedures Programming Manual publication 1756-PM001
The term Logix5000 controller refers to any controller that is based on the Logix5000 operating system such as
bull CompactLogix controllersbull ControlLogix controllersbull DriveLogix controllersbull FlexLogix controllersbull SoftLogix5800 controllers
How to Use this Manual Some text is formatted differently from the rest of the text
Text that is Identifies For example Means
Italic the actual name of an item that you see on your screen or in an example
Right-click User-Defined hellip Right-click the item that is named User-Defined
courier information that you must supply based on your application (a variable)
Right-click name_of_program hellip
You must identify the specific program in your application Typically it is a name or variable that you have defined
enclosed in brackets a keyboard key Press [Enter] Press the Enter key
5Publication 1756-PM011B-EN-P - July 2008 5
Preface
Notes
6 Publication 1756-PM011B-EN-P - July 2008
Chapter 1
Produce and Consume a Tag
Introduction A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags
Controllers and Networks that Support ProducedConsumed Tags
These combinations support produced and consumed tags
controller_2
controller_3
controller_4
consumed tag
consumed tag
consumed tag
controller_1
produced tag
Term Definition
Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume (receive) the data A produced tag sends its data to one or more consumed tags (consumers) without using logic The produced tag sends its data at the RPI of the consuming tag
Consumed tag A tag that receives the data of a produced tag The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag The RPI of the consumed tag determines the period at which the data updates
This controller Can produce and consume tags over this network
Backplane ControlNet EtherNetIP
SLC 500 E
PLC-5 E
CompactLogix(1) E E
ControlLogix E E E
DriveLogix E E
FlexLogix E E
SoftLogix5800 E
7Publication 1756-PM011B-EN-P - July 2008 7
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Preface
Notes
6 Publication 1756-PM011B-EN-P - July 2008
Chapter 1
Produce and Consume a Tag
Introduction A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags
Controllers and Networks that Support ProducedConsumed Tags
These combinations support produced and consumed tags
controller_2
controller_3
controller_4
consumed tag
consumed tag
consumed tag
controller_1
produced tag
Term Definition
Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume (receive) the data A produced tag sends its data to one or more consumed tags (consumers) without using logic The produced tag sends its data at the RPI of the consuming tag
Consumed tag A tag that receives the data of a produced tag The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag The RPI of the consumed tag determines the period at which the data updates
This controller Can produce and consume tags over this network
Backplane ControlNet EtherNetIP
SLC 500 E
PLC-5 E
CompactLogix(1) E E
ControlLogix E E E
DriveLogix E E
FlexLogix E E
SoftLogix5800 E
7Publication 1756-PM011B-EN-P - July 2008 7
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 1
Produce and Consume a Tag
Introduction A Logix5000 controller lets you produce (broadcast) and consume (receive) system-shared tags
Controllers and Networks that Support ProducedConsumed Tags
These combinations support produced and consumed tags
controller_2
controller_3
controller_4
consumed tag
consumed tag
consumed tag
controller_1
produced tag
Term Definition
Produced tag A tag that a controller makes available for use by other controllers Multiple controllers can simultaneously consume (receive) the data A produced tag sends its data to one or more consumed tags (consumers) without using logic The produced tag sends its data at the RPI of the consuming tag
Consumed tag A tag that receives the data of a produced tag The data type of the consumed tag must match the data type (including any array dimensions) of the produced tag The RPI of the consumed tag determines the period at which the data updates
This controller Can produce and consume tags over this network
Backplane ControlNet EtherNetIP
SLC 500 E
PLC-5 E
CompactLogix(1) E E
ControlLogix E E E
DriveLogix E E
FlexLogix E E
SoftLogix5800 E
7Publication 1756-PM011B-EN-P - July 2008 7
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 1 Produce and Consume a Tag
For two controllers to share produced or consumed tags both controllers must be attached to the same network (such as a ControlNet or EthernetIP network) You cannot bridge produced and consumed tags over two networks
Connection Requirements of a Produced or Consumed Tag
Produced and consumed tags each require connections As you increase the number of controllers that can consume a produced tag you also reduce the number of connections the controller has available for other operations like communications and IO
Each produced or consumed tag uses these connections
(1) For ControlNet use a 1769-L32C or 1769-L35CR controller For EtherNetIP use a 1769-L32Eor 1769-L35E controller
IMPORTANT If a consumed-tag connection fails all of the other tags being consumed from that remote controller stop receiving new data
And this type of tag Uses this many connections
Produced tag number_of_consumers + 1
Consumed tag 1
EXAMPLE Connection Requirements of a Produced or Consumed Tag
bull A FlexLogix controller producing a tag for 5 controllers (consumers) uses 6 connectionsbull A ControlLogix controller producing 4 tags for 1 controller uses 8 connections
ndash Each tag uses 2 connections (1 consumer + 1 = 2)ndash 2 connections per tag x 4 tags = 8 connections
bull Consuming 4 tags from a controller uses 4 connections (1 connection per tag x 4 tags = 4 connections)
8 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Produce and Consume a Tag Chapter 1
Organize Tags for Produced or Consumed Data
As you organize your tags for produced or consumed data (shared data) follow these guidelines
Guideline Details
Create the tags at the controller scope
You can share only controller-scoped tags
Use one of these data types
bull DINT
bull REAL
bull array of DINTs or REALs
bull user-defined
bull To share other data types create a user-defined data type that contains the required data
bull Use the same data type for the produced tag and corresponding consumed tag or tags
To share tags with a PLC-5C controller use a user-defined data type
To This Then
Produce Integers Create a user-defined data type that contains an array of INTs with an even number of elements such as INT[2] (When you produce INTs you must produce two or more)
Only one REAL value
Use the REAL data type
More than one REAL value
Create a user-defined data type that contains an array of REALs
Consume Integers Create a user-defined data type that contains these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
Limit the size of the tag to pound 500 bytes
bull If you must transfer more than 500 bytes create logic to transfer the data in packets
bull If you produce the tag over a ControlNet network the tag may need to be less than 500 bytes Refer to Adjust for Bandwidth Limitations on page 1-10
Use the highest permissible RPI for your application
If the controller consumes the tag over a ControlNet network use a binary multiple of the ControlNet network update time (NUT) For example if the NUT is 5 ms use an RPI of 5 10 20 40 ms etc
Combine data this goes to the same controller
If you are producing several tags for the same controller
bull Group the data into one or more user-defined data types (This uses less connections than producing each tag separately)
bull Group the data according to similar update intervals (To conserve network bandwidth use a greater RPI for less critical data)
For example you could create one tag for data that is critical and another tag for data that is not as critical
Publication 1756-PM011B-EN-P - July 2008 9
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 1 Produce and Consume a Tag
Adjust for Bandwidth Limitations
When you share a tag over a ControlNet network the tag must fit within the bandwidth of the network
bull As the number of connections over a ControlNet network increases several connections including produced or consumed tags may need to share a network update time (NUT)
bull Since a ControlNet network can only pass 500 bytes in one NUT the data of each connection must be less then 500 bytes to fit into the NUT
Depending on the size of your system you may not have enough bandwidth on your ControlNet network for a tag of 500 bytes If a tag is too large for your ControlNet network make one or more of these adjustments
Produce a Tag 1 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (You can produce only controller-scoped tags)
2 In the Controller Tags window right-click the tag that you want to produce and choose Edit Tag Properties
Adjustment Description
Reduce your network update time (NUT) At a faster NUT less connections have to share an update slot
Increase the requested packet interval (RPI) of your connections
At higher RPIs connections can take turns sending data during an update slot
For a ControlNet bridge module (CNB) in a remote chassis select the most efficient communication format for that chassis
Are most of the modules in the chassis non-diagnostic digital IO modules
Then select this communication format for the remote CNB module
Yes Rack Optimization
No None
The Rack Optimization format uses an additional 8 bytes for each slot in its chassis Analog modules or modules that are sending or getting diagnostic fuse timestamp or schedule data require direct connections and cannot take advantage of the rack optimized form Selecting ldquoNonerdquo frees up the 8 bytes per slot for other uses such as produced or consumed tags
Separate the tag into two or more smaller tags
1 Group the data according to similar update rates For example you could create one tag for data that is critical and another tag for data that is not as critical
2 Assign a different RPI to each tag
Create logic to transfer the data in smaller sections (packets)
See the next chapter Producing a Large Array
10 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Produce and Consume a Tag Chapter 1
3 Click the Produced option button
4 Select the Connection tab and specify the number of controllers that will consume (receive) the tag
5 Click OK
Consume Data That Is Produced by Another Controller
1 In the controller organizer IO Configuration folder add the controller that is producing the data (the other Logix5000 controller or PLC-5C controller)
2 In the controller organizer right-click the Controller Tags folder and choose Edit Tags (Only controller-scoped tags can consume data)
3 In the Controller Tags window right-click the tag that will consume the data and choose Edit Tag Properties
Publication 1756-PM011B-EN-P - July 2008 11
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 1 Produce and Consume a Tag
4 Select Consumed for the type
5 Specify the data type
If the producing controller is
Then the data type should be
Logix5000 controller Same data type as the produced tag
PLC-5C controller User-defined data type with these members
Data type Description
DINT Status
INT[x] where x is the output size of the data from the PLC-5C controller (If you are consuming only one INT omit x)
Data produced by a PLC-5C controller
12 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Produce and Consume a Tag Chapter 1
6 Click the Connection button to define the consumed tag
bull Select the controller that produces the databull Type the name or instance number of the remote produced data
bull Type or select the requested packet interval (RPI) for the connection
7 Click OK
8 If you consume the tag over a ControlNet network use RSNetWorx for ControlNet software to schedule the network
If the producing controller is
Then type or select
Logix5000 controller Tag name of the produced tag
PLC-5C controller Message number from the ControlNet configuration of the PLC-5C controller
Publication 1756-PM011B-EN-P - July 2008 13
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 1 Produce and Consume a Tag
Additional Steps for a PLC-5C Controller
If you are sharing data with a PLC-5C controller you need to
Action Details
In the ControlNet configuration of the PLC-5C controller scheduled a message
If the PLC-5C This Then in RSNetWorx software
Produces Integers In the ControlNet configuration of the PLC-5C controller insert a Send Scheduled Message
Consumes Integers In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter the number of integers in the produced tag
REALs In the ControlNet configuration of the PLC-5C controller
A Insert a Receive Scheduled Message
B In the Message size enter two times the number of REALs in the produced tag For example if the produced tag contains 10 REALs enter 20 for the Message size
If the PLC-5C controller consumes REALs reconstruct the values
When you produce REALs (32-bit floating-point values) for a PLC-5C controller the PLC-5C stores the data in consecutive 16-bit integers
bull The first integer contains the upper (left-most) bits of the value
bull The second integer contains the lower (right-most) bits of the value
bull This pattern continues for each floating-point value
14 Publication 1756-PM011B-EN-P - July 2008
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Produce and Consume a Tag Chapter 1
This example shows how to re-construct a REAL (floating point value) in the PLC-5C controller
Verify Consumed Tag Requested Packet Interval (RPI) Limitations
Your consumed tags must operate within specified limitations
To verify that your consumed tags are requesting packets at acceptable intervals of time perform this procedure
1 In the controller organizer right-click on Controllers and choose Properties
EXAMPLE Re-construct a floating point value
The two MOV instructions reverse the order of the integers as the integers move to a new location Because the destination of the COP instruction is a floating-point address it takes two consecutive integers for a total of 32 bits and converts them to a single floating-point value
42354
Publication 1756-PM011B-EN-P - July 2008 15
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 1 Produce and Consume a Tag
The Controller Properties dialog appears
2 Click the Advanced tab
Under Consumed Tag Requested Packet Interval (RPI) you can verify the minimum and maximum requested packet interval for your controller
If you need to changed the intervals do so offline
3 To save these limitations as the default RPI settings for new projects click Save RPI Defaults
16 Publication 1756-PM011B-EN-P - July 2008
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 2
Producing a Large Array
Introduction The Logix5000 controller can send as many as 500 bytes of data over a single scheduled connection This corresponds to 125 DINT or REAL elements of an array To transfer an array of more than 125 DINTs or REALs use a producedconsumed tag of 125 elements to create a packet of data You can then use the packet to send the array piecemeal to another controller
When you send a large array of data in smaller packets you must ensure that the transmission of a packet is complete before the data is moved into the destination array
bull Produced data over the ControlLogix backplane is sent in 50 byte segments
bull Data transmission occurs asynchronous to program scan
The logic that this section includes uses an acknowledge word to make sure that each packet contains new data before the data moves to the destination array The logic also uses an offset value to indicate the starting element of the packet within the array
Because of the offset and acknowledge elements each packet carries 123 elements of data from the array as depicted below
array
0packet
offsetacknowledge
arraypacket
offsetacknowledge
Producer Consumer
17Publication 1756-PM011B-EN-P - July 2008 17
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 2 Producing a Large Array
In addition the array must contain an extra 122 elements In other words it must be 122 elements greater than the greatest number of elements that you want to transfer
bull These elements serve as a bufferbull Since each packet contains the same number of elements the buffer
prevents the controller from copying beyond the boundaries of the array
bull Without the buffer this would occur if the last packet contained fewer than 123 elements of actual data
Produce a Large Array 1 In the Controller Tags folder of the controller project that produces the array create these tags
2 Convert array_ack to a consumed tag
3 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
4 In the array_size tag enter the number of elements of real data (The value of x from step 3 minus the 122 elements of buffer)
5 Create or open a routine for the logic that will create packets of data
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is receiving the packet
Remote Tag Name array_ack
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
array_size DINT
array_transfer_time DINT
array_transfer_time_max DINT
array_transfer_timer TIMER
18 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Producing a Large Array Chapter 2
6 Enter this logic
Times how long it takes to send the entire array
When the offset value in array_ack[0] is not equal to the current offset value but array_ack[1] equals -999 the consumer has begun to receive a new packet so the rung moves -999 into the last element of the packet The consumer waits until it receives the value -999 before it copies the packet to the array This guarantees that the consumer has new data
When the offset value in array_ack[0] is equal to the current offset value the consumer has copied the packet to the array so the rung checks for more data to transfer If the offset value plus 123 is less than the size of the array there is more data to transfer so the rung increases the offset by 123 Otherwise there is no more data to transfer so the rung resets the offset value logs the transfer time and resets the timer In either case the rung uses the new offset value to create a new packet of data appends the new offset value to the packet and clears the acknowledge element of the packet (packet[124])
Publication 1756-PM011B-EN-P - July 2008 19
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 2 Producing a Large Array
7 In the Controller Tags folder of the controller project that consumes the array create these tags
8 Convert array_packet to a consumed tag
9 In either the Controller Tags folder or the tags folder of the program that will contain the logic for the transfer create these tags
10 Create or open a routine for the logic that will move the data from the packets to the destination array
If the current transfer time is greater than the maximum transfer time updates the maximum transfer time This maintains a record of the longest time to transfer data
42355
P Tag Name Type
array_ack DINT[2]
array_packet DINT[125]
For Specify
Controller Name of the controller that is sending the packet
Remote Tag Name array_packet
Both controllers use the same name for this data
Tag Name Type
array DINT[x] where x equals the number of elements to transfer plus 122 elements
array_offset DINT
20 Publication 1756-PM011B-EN-P - July 2008
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Producing a Large Array Chapter 2
11 Enter this logic
When the offset value in array_packet[123] is different than the offset value in array_ack[0] the controller has begun to receive a new packet of data so the rung checks for the value of -999 in the last element of the packet
If the last element of the packet equals -999 the controller has received an entire packet of new data and begins the copy operation
bull The offset value moves from the packet to array_offsetbull The COP instructions copies the data from the packet to the destination array starting at the offset valuebull The offset value moves to array_ack[0] which signals that the copy is completebull Array_ack[1] resets to zero and waits to signal the arrival of a new packet
If the last element of the packet is not equal -999 the transfer of the packet to the controller may not be complete so -999 moves to array_ack[1] This signals the producer to return the value of -999 in the last element of the packet to verify the transmission of the packet
42356
NotEqualSourceAarray_packet[123]
0SourceBarray_ack[0]
0
NEQ
EqualSourceAarray_packet[124]
0SourceB-999
EQUMoveSourcearray_packet[123]
0Destarray_offset
0
MOV
CopyFileSourcearray_packet[0]Destarray[array_offset]Length123
COP
MoveSourcearray_packet[123]
0Destarray_ack[0]
0
MOV
ClearDestarray_ack[1]
0
CLR
NotEqualSourceAarray_packet[124]
0SourceB-999
NEQMoveSource-999
Destarray_ack[1]0
MOV
Publication 1756-PM011B-EN-P - July 2008 21
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Chapter 2 Producing a Large Array
Transferring a large array as smaller packets improves system performance over other methods of transferring the data
bull Fewer connections are used than if you broke the data into multiple arrays and sent each as a produced tag For example an array with 5000 elements would take 40 connections (5000125=40) using individual arrays
bull Faster transmission times are achieved than if you used a message instruction to send the entire array
ndash Messages are unscheduled and are executed only during the ldquosystem overheadrdquo portion of the Logix5550 execution Therefore messages can take a fairly long time to complete the data transfer
ndash You can improve the transfer time by increasing system overhead time slice but this diminishes the performance of the continuous task
22 Publication 1756-PM011B-EN-P - July 2008
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
Rockwell Automation Support
Rockwell Automation provides technical information on the Web to assist you in using its products At httpsupportrockwellautomationcom you can find technical manuals a knowledge base of FAQs technical and application notes sample code and links to software service packs and a MySupport feature that you can customize to make the best use of these tools
For an additional level of technical phone support for installation configuration and troubleshooting we offer TechConnect Support programs For more information contact your local distributor or Rockwell Automation representative or visit httpsupportrockwellautomationcom
Installation Assistance
If you experience a problem with a hardware module within the first 24 hours of installation please review the information thats contained in this manual You can also contact a special Customer Support number for initial help in getting your module up and running
New Product Satisfaction Return
Rockwell tests all of its products to ensure that they are fully operational when shipped from the manufacturing facility However if your product is not functioning it may need to be returned
United States 14406463434Monday ndash Friday 8am ndash 5pm EST
Outside United States
Please contact your local Rockwell Automation representative for any technical support issues
United States Contact your distributor You must provide a Customer Support case number (see phone number above to obtain one) to your distributor in order to complete the return process
Outside United States
Please contact your local Rockwell Automation representative for return procedure
Publication 1756-PM011B-EN-P - July 2008 24Supersedes Publication 1756-PM011A-EN-P - July 2007 Copyright copy 2008 Rockwell Automation Inc All rights reserved Printed in the USA
| PackagingOrdering Unit Of Measure | ||||
| EA = Each | ||||
| PK = Pack | ||||
| PD = Pad | ||||
| RL = Roll | ||||
| BK = Book | ||||
| CT = Carton | ||||
| BX = Box | ||||
| ST = Set | ||||
| Multiple Order Qty | ||||
| Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn) | ||||
| Business Group | ||||
| The business group that the publication supports Your choice here determines the list you choose from for Cost Center | ||||
| CorporateBusiness Development | ||||
| Finance | ||||
| Human Resources | ||||
| IT | ||||
| Logistics | ||||
| Manufacturing | ||||
| Marketing Commercial | ||||
| Marketing Europe | ||||
| Marketing Other | ||||
| Operations | ||||
| Order Services | ||||
| Other | ||||
| Process Improvement | ||||
| Procurement | ||||
| Quality | ||||
| Sales | ||||
| Max Order Quantity | ||||
| Presale items = 100 | ||||
| Postsale items = 5 | ||||
| NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it | ||||
| Item Category - Form (F) or Book (B) | ||||
| Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form | ||||
| Book (B) = Any publication that contains 3 or more pages | ||||
| BindingStitching | ||||
| For a Form (F) use | ||||
| CARBONLESS | ||||
| CUTSHEET | ||||
| ENVELOPE | ||||
| For a Book (B) use | ||||
| LOOSE | LOOSE -Loose Leaf | |||
| PERFECT | PERFECT - Perfect Bound | |||
| PLASTCOIL | PLASTCOIL - Plastic Coil | |||
| SADDLE | SADDLE - Saddle Stitch | |||
| STAPLED1 | STAPLED1 -1 position | |||
| STAPLED1B | STAPLED1B - bottom 1 position | |||
| STAPLED2 | STAPLED2 - 2 positions | |||
| THERMAL | THERMAL - Thermal bound | |||
| THERMALO | THERMALO - Thermal Bound - offline | |||
| Sides Printed | ||||
| Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page | ||||
| Simplex = Single-sided printing | ||||
| Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page | ||||
| Number of Forms to a Sheet | ||||
| Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4 | ||||
| Number of Sheets Required to Print | ||||
| Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of four 85 x 11 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4 | ||||
| Paper Stock Type | ||||
| Description | ||||
| PLAIN | Bond | |||
| ACNTCVR | Accent Cover | |||
| BOND3H | Bond (3-hole) | |||
| BOOKENV | Booklet Envelope | |||
| C1SGLOSS | C1S Gloss Finish | |||
| C1SMATTE | C1S Matt Finish | |||
| C2SGLOSS | C2S Gloss Finish | |||
| C2SMATTE | C2S Matt Finish | |||
| CARD | Card Stock | |||
| CATLGENV | Catalog Envelope | |||
| CATLGENV6 | 6 Catalog Envelope | |||
| COVERCOLOR | Color Cover Copy | |||
| CRCKPEEL | Crack N Peel Label | |||
| CUSTOM | Custom | |||
| CVRFUTURA | Futura Cover | |||
| ENV6x9 | Standard 6X9 Envelope | |||
| ENV9X12 | Standard 9X12 Envelope | |||
| ETHCERT | Ethicon Certificate | |||
| GLOSSCOVER | Gloss Cover | |||
| GLOSSTEXT | Gloss Text | |||
| HOTSTEXT | Hots Text | |||
| INDEX | Index | |||
| LABEL80 | 80 Up Label | |||
| MICROPRT | Micro Print | |||
| OFFSET | Offset | |||
| PART2 | 2 Part | |||
| PART3 | 3 Part | |||
| PART4 | 4 Part | |||
| PART5 | 5 Part | |||
| PART6 | 6 Part | |||
| PERF | 12 inch Perfed | |||
| PERMMAT | Perm Mat Ad | |||
| PRECUTTAB | Pre-Cut Tab | |||
| PREPERF | Pre-Perforated | |||
| RECYL | Recycled | |||
| SE10ENV | 10 Standard Envelope | |||
| SE10ITENV | 10 Inside Tint Envelope | |||
| SE9ENV | 9 Stanard Envelope | |||
| TAG | Tag | |||
| TEXT | Text | |||
| TEXTCOLOR | Text Color Copy | |||
| TEXTFUTURA | Futura Text | |||
| TEXTLASER | Text Laser Print | |||
| TRANSPRNCY | Transparencies | |||
| VELLUM | Vellum | |||
| VELLUM3HP | Vellum 3HP | |||
| WE10ENV | 10 Window Envelope | |||
| WE9ENV | 9 Windor Envelope | |||
| WE9ITENV | 9 Inside Tint Window Envelope | |||
| Paper Stock Color | ||||
| Black | ||||
| Blue | ||||
| Buff | ||||
| Canary | ||||
| Cherry | ||||
| Clear | ||||
| Cream | ||||
| Custom | ||||
| Goldrenrod | ||||
| Gray | ||||
| Green | ||||
| Ivory | ||||
| Lavender | ||||
| Manilla | ||||
| NCRPinkCanary | ||||
| NCRWhiteBlue | ||||
| NCRWhiteBlueCanary | ||||
| NCRWhiteCanary | ||||
| NCRWhiteCanaryPink | ||||
| NCRWhiteCanaryPinkGoldenrod | ||||
| NCRWhiteGreen | ||||
| NCRWhiteGoldenrodYellow | ||||
| NCRWhitePink | ||||
| NCRWhiteWhite | ||||
| Opaque | ||||
| Orange | ||||
| Orchid | ||||
| Peach | ||||
| Pink | ||||
| Purple | ||||
| Salmon | ||||
| Tan | ||||
| Violet | ||||
| White | ||||
| Finished Trim Sizes (listed - width x length) | ||||
| 11 x 17 | ||||
| 18 x 24 Poster | ||||
| 24 x 36 Poster | ||||
| 3 x 5 | ||||
| 36 x 24 Poster | ||||
| 4 x 6 | ||||
| 475 x 7 | ||||
| 475 x 775 | ||||
| 55 x 85 | ||||
| 6 x 4 | ||||
| 7 x 9 | ||||
| 7385 x 9 (RSI Std) | ||||
| 85 x 11 | ||||
| 825 x 10875 | ||||
| 825 x 11 (RA product profile std) | ||||
| 8375 x 10875 | ||||
| 9 x 12 | ||||
| A4 | ||||
| A5 | ||||
| Other - Custom size listed below | ||||
| Drilling Locations | ||||
| 1CENTER | ||||
| 1LEFTTOP | ||||
| 1TOPCENTER | ||||
| 2LEFT | ||||
| 2LEFT2TOP | ||||
| 2TOP | ||||
| 2TOP2LEFT | ||||
| 2TOP3LEFT | ||||
| 2TOP5LEFT | ||||
| 2TOP5RIGHT | ||||
| 3BOTTOM | ||||
| 3LEFT | ||||
| 3LEFT2TOP | ||||
| 3LEFT3TOP | ||||
| 3RIGHT | ||||
| 3TOP | ||||
| 3TOP5LEFT | ||||
| 5BOTTOOM | ||||
| 5CENTER | ||||
| 5LEFT | ||||
| 5RIGHT | ||||
| 5RIGHT2TOP | ||||
| 5TOP | ||||
| Fold Type | ||||
| For TRI fold - select Z or C type | Description | |||
| HALF | Half | |||
| C | C Fold | |||
| DBLEPARLL | Double Parallel | |||
| OFFSETZ | Offset Z | |||
| SAMPLE | See Sample | |||
| SHORT | Short Fold | |||
| V | V Fold | |||
| Z | Z Fold | |||
| Number of Pieces per Poly Wrap | ||||
| Publication length | Number per Poly Wrap | |||
| 77 or more pages | NA | |||
| 33 to 76 pages | 25 | |||
| 3 to 32 pages | 50 | |||
| 1 or 2 pages | 100 | |||
| Comments | ||||
| CoverText Stock | Spine | |||
| 100 Gloss Cover | If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Also do not include that page as part of the publication page count | |||
| 100 Gloss Text | ||||
| 100 Text | ||||
| 10pt C1S Cover | ||||
| 10pt C2S Cover | ||||
| 10pt C2S Text | ||||
| 10pt Text Stock | ||||
| 110 White Index | ||||
| 12pt C1S Cover | ||||
| 20 White Opaque Bond | ||||
| 50 Colored Offset | ||||
| 50 White Offset | ||||
| 50 White Opaque | ||||
| 60 Cover Stock | ||||
| 60 White Offset | ||||
| 80 Gloss Cover | ||||
| 80 Gloss Text | ||||
| 8pt C1S White | ||||
| 90 White Index | ||||
| CoverText Ink | ||||
| Black | ||||
| Black + 1 PMS color | Type in PMS color | |||
| Black + 2 PMS colors | Type in PMS colors | |||
| 4 color | ||||
| 4 color over black | ||||
| 4 color + 1 PMS color | Type in PMS color | |||
| 4 color over black + 1 PMS color | Type in PMS color | |||
| 4 color + 2 PMS colors | Type in PMS colors | |||
| 4 color + aqueous | ||||
| 4 color + varnish |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Cannot use quote symbol that is---- | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | 825 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | NA | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | GLOSS TEXT | 80 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 825 | 11 | NA | NA | NA | NA | HALF | 85 x 11 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| EA | 1 | 1 | See DocMan for the Cost Center selections associated with each Business Group | Black amp White | B | PERFECT | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | 2 | PLAIN | 20 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 85 | 11 | NA | 516 | 3LEFT | NA | NA | NA | NA | RRD must provide this information | Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1756-PM011B-EN-P | Logix5000 Controllers Produced andConsumed Tags | EA | 1 | 1 | Marketing Commercial | CMKMAY IA ControlVisNet - 19021 | 07012008 | 5 | Black amp White | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | 4 | 24 | 10 | PLAIN | 20 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 85 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information | Text Stock = 20 White Opaque BondText Ink = BlackCover Stock = 90 White IndexCover Ink = Black |
| Corp | 17501 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bill To | 69 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See DocMan for the Cost Center selections associated with each Business Group | RRD must provide this information | RRD must provide this information | RRD must provide this information | RRD must provide this information |
| Details of the Rockwell Automation Print Specifications sheet | |||
| This print specifications sheet is designed with multiple purposes- It is a vehicle to get the most accurate print specifications to RA-approved print vendors- It provides authors with an explanation of all necessary fields to complete before attaching the sheet to your PDF- It provides separate tabs so that an author can fill in all fields related to the publication on the Generic tab or publication-specific template-type tabs to minimize the number of fields an author must completeTo facilitate the most efficient use of this sheet we recommend that you click on the publication-specific tab that most closely fits you publication and use that to complete the print specificationsIMPORTANT Because this sheet was constructed using a sheet that RR Donnelley (RRD) uses to load print specifications there are some columns hidden For example the first field you must complete is Column E or Publication Number Columns A to D are used for RRD purposes and with information only representatives of that RA-approved printer can completeDO NOT delete any hidden columns from the tab you choose to use | |||
| Definitions of Each Tab in Sheet | |||
| Generic pub print specs | Single sheet with all required columns for necessary specifications None of the columns are completed All must be completed before attaching the sheet to your PDFThis tab has 39 blank fields you must complete via free text type or pull-down menus | ||
| IN RN pub type specs | Templates with many fields already completed according to typical default settings Use this tab with publications similar to installation instructions (IN) and release notes (RN) However you can use this sheet for other publications that are similar to INs and RNsThis sheet has several fields already completed with default values which you can change You must complete the additional fields | ||
| UM RM PM pub type specs | Templates with many fields already completed according to typical default settings Use this tab with publications similar to user manuals (UM) reference manuals (RM) and programming manuals (PM) However you can use this sheet for other publications that are similar to UMs RMs and PMsThis sheet has several fields already completed with default values which you can change You must complete the additional fields | ||
| AP PP pub type specs | Templates with many fields already completed according to typical default settings Use this tab with publications similar to application solutions (AP) and product profiles (PP) However you can use this sheet for other publications that are similar to APs and PPsThis sheet has several fields already completed with default values which you can change You must complete the additional fields | ||
| BR pub type specs | Templates with many fields already completed according to typical default settings Use this tab with publications similar to brochures (BR) However you can use this sheet for other publications that are similar to BRsThis sheet has several fields already completed with default values which you can change You must complete the additional fields | ||
| Field definitions | Description of information fields used throughout the spreadsheet tabs that may not be immediately obvious to a user | ||
| Attach Print Specs to PDF | |||
| For Acrobat 80 follow these steps1 Open the PDF2 Click on DocumentgtAttach A File A new section appears at the bottom of the PDF3 Browse to the MS Excel file with the print specs and add it to the PDFFor Acrobat 70 follow these steps1 Open the PDF2 Click on the Attachments tab next to the publications bookmarks A new section appears at the bottom of the PDF3 Click on the Add button in the bottom section of the PDF4 Browse to the MS Excel file with the print specs and add it to the PDFFor Acrobat 60 follow these steps1 Open the PDF2 Go to the backcover of the PDF3 Click on the Tools pull-down menu4 Click on this sequence of menu options - Advanced Commenting Attach Attach File Tool A paper clip appears5 Click to put the paper clip somewhere on the backcover The browse window appears6 Browse to the MS Excel file with the print specs and add it to the PDFIMPORTANT If you are using Acrobat 50 or earlier please upgrade | |||
| RA-QR005B-EN-E 308 |
| PackagingOrdering Unit Of Measure | ||||
| EA = Each | ||||
| PK = Pack | ||||
| PD = Pad | ||||
| RL = Roll | ||||
| BK = Book | ||||
| CT = Carton | ||||
| BX = Box | ||||
| ST = Set | ||||
| Multiple Order Qty | ||||
| Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn) | ||||
| Business Group | ||||
| The business group that the publication supports Your choice here determines the list you choose from for Cost Center | ||||
| CorporateBusiness Development | ||||
| Finance | ||||
| Human Resources | ||||
| IT | ||||
| Logistics | ||||
| Manufacturing | ||||
| Marketing Commercial | ||||
| Marketing Europe | ||||
| Marketing Other | ||||
| Operations | ||||
| Order Services | ||||
| Other | ||||
| Process Improvement | ||||
| Procurement | ||||
| Quality | ||||
| Sales | ||||
| Max Order Quantity | ||||
| Presale items = 100 | ||||
| Postsale items = 5 | ||||
| NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it | ||||
| Item Category - Form (F) or Book (B) | ||||
| Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form | ||||
| Book (B) = Any publication that contains 3 or more pages | ||||
| BindingStitching | ||||
| For a Form (F) use | ||||
| CARBONLESS | ||||
| CUTSHEET | ||||
| ENVELOPE | ||||
| For a Book (B) use | ||||
| LOOSE | LOOSE -Loose Leaf | |||
| PERFECT | PERFECT - Perfect Bound | |||
| PLASTCOIL | PLASTCOIL - Plastic Coil | |||
| SADDLE | SADDLE - Saddle Stitch | |||
| STAPLED1 | STAPLED1 -1 position | |||
| STAPLED1B | STAPLED1B - bottom 1 position | |||
| STAPLED2 | STAPLED2 - 2 positions | |||
| THERMAL | THERMAL - Thermal bound | |||
| THERMALO | THERMALO - Thermal Bound - offline | |||
| Sides Printed | ||||
| Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page | ||||
| Simplex = Single-sided printing | ||||
| Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page | ||||
| Number of Forms to a Sheet | ||||
| Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4 | ||||
| Number of Sheets Required to Print | ||||
| Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of four 85 x 11 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4 | ||||
| Paper Stock Type | ||||
| Description | ||||
| PLAIN | Bond | |||
| ACNTCVR | Accent Cover | |||
| BOND3H | Bond (3-hole) | |||
| BOOKENV | Booklet Envelope | |||
| C1SGLOSS | C1S Gloss Finish | |||
| C1SMATTE | C1S Matt Finish | |||
| C2SGLOSS | C2S Gloss Finish | |||
| C2SMATTE | C2S Matt Finish | |||
| CARD | Card Stock | |||
| CATLGENV | Catalog Envelope | |||
| CATLGENV6 | 6 Catalog Envelope | |||
| COVERCOLOR | Color Cover Copy | |||
| CRCKPEEL | Crack N Peel Label | |||
| CUSTOM | Custom | |||
| CVRFUTURA | Futura Cover | |||
| ENV6x9 | Standard 6X9 Envelope | |||
| ENV9X12 | Standard 9X12 Envelope | |||
| ETHCERT | Ethicon Certificate | |||
| GLOSSCOVER | Gloss Cover | |||
| GLOSSTEXT | Gloss Text | |||
| HOTSTEXT | Hots Text | |||
| INDEX | Index | |||
| LABEL80 | 80 Up Label | |||
| MICROPRT | Micro Print | |||
| OFFSET | Offset | |||
| PART2 | 2 Part | |||
| PART3 | 3 Part | |||
| PART4 | 4 Part | |||
| PART5 | 5 Part | |||
| PART6 | 6 Part | |||
| PERF | 12 inch Perfed | |||
| PERMMAT | Perm Mat Ad | |||
| PRECUTTAB | Pre-Cut Tab | |||
| PREPERF | Pre-Perforated | |||
| RECYL | Recycled | |||
| SE10ENV | 10 Standard Envelope | |||
| SE10ITENV | 10 Inside Tint Envelope | |||
| SE9ENV | 9 Stanard Envelope | |||
| TAG | Tag | |||
| TEXT | Text | |||
| TEXTCOLOR | Text Color Copy | |||
| TEXTFUTURA | Futura Text | |||
| TEXTLASER | Text Laser Print | |||
| TRANSPRNCY | Transparencies | |||
| VELLUM | Vellum | |||
| VELLUM3HP | Vellum 3HP | |||
| WE10ENV | 10 Window Envelope | |||
| WE9ENV | 9 Windor Envelope | |||
| WE9ITENV | 9 Inside Tint Window Envelope | |||
| Paper Stock Color | ||||
| Black | ||||
| Blue | ||||
| Buff | ||||
| Canary | ||||
| Cherry | ||||
| Clear | ||||
| Cream | ||||
| Custom | ||||
| Goldrenrod | ||||
| Gray | ||||
| Green | ||||
| Ivory | ||||
| Lavender | ||||
| Manilla | ||||
| NCRPinkCanary | ||||
| NCRWhiteBlue | ||||
| NCRWhiteBlueCanary | ||||
| NCRWhiteCanary | ||||
| NCRWhiteCanaryPink | ||||
| NCRWhiteCanaryPinkGoldenrod | ||||
| NCRWhiteGreen | ||||
| NCRWhiteGoldenrodYellow | ||||
| NCRWhitePink | ||||
| NCRWhiteWhite | ||||
| Opaque | ||||
| Orange | ||||
| Orchid | ||||
| Peach | ||||
| Pink | ||||
| Purple | ||||
| Salmon | ||||
| Tan | ||||
| Violet | ||||
| White | ||||
| Finished Trim Sizes (listed - width x length) | ||||
| 11 x 17 | ||||
| 18 x 24 Poster | ||||
| 24 x 36 Poster | ||||
| 3 x 5 | ||||
| 36 x 24 Poster | ||||
| 4 x 6 | ||||
| 475 x 7 | ||||
| 475 x 775 | ||||
| 55 x 85 | ||||
| 6 x 4 | ||||
| 7 x 9 | ||||
| 7385 x 9 (RSI Std) | ||||
| 85 x 11 | ||||
| 825 x 10875 | ||||
| 825 x 11 (RA product profile std) | ||||
| 8375 x 10875 | ||||
| 9 x 12 | ||||
| A4 | ||||
| A5 | ||||
| Other - Custom size listed below | ||||
| Drilling Locations | ||||
| 1CENTER | ||||
| 1LEFTTOP | ||||
| 1TOPCENTER | ||||
| 2LEFT | ||||
| 2LEFT2TOP | ||||
| 2TOP | ||||
| 2TOP2LEFT | ||||
| 2TOP3LEFT | ||||
| 2TOP5LEFT | ||||
| 2TOP5RIGHT | ||||
| 3BOTTOM | ||||
| 3LEFT | ||||
| 3LEFT2TOP | ||||
| 3LEFT3TOP | ||||
| 3RIGHT | ||||
| 3TOP | ||||
| 3TOP5LEFT | ||||
| 5BOTTOOM | ||||
| 5CENTER | ||||
| 5LEFT | ||||
| 5RIGHT | ||||
| 5RIGHT2TOP | ||||
| 5TOP | ||||
| Fold Type | ||||
| For TRI fold - select Z or C type | Description | |||
| HALF | Half | |||
| C | C Fold | |||
| DBLEPARLL | Double Parallel | |||
| OFFSETZ | Offset Z | |||
| SAMPLE | See Sample | |||
| SHORT | Short Fold | |||
| V | V Fold | |||
| Z | Z Fold | |||
| Number of Pieces per Poly Wrap | ||||
| Publication length | Number per Poly Wrap | |||
| 77 or more pages | NA | |||
| 33 to 76 pages | 25 | |||
| 3 to 32 pages | 50 | |||
| 1 or 2 pages | 100 | |||
| Comments | ||||
| CoverText Stock | Spine | |||
| 100 Gloss Cover | If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Also do not include that page as part of the publication page count | |||
| 100 Gloss Text | ||||
| 100 Text | ||||
| 10pt C1S Cover | ||||
| 10pt C2S Cover | ||||
| 10pt C2S Text | ||||
| 10pt Text Stock | ||||
| 110 White Index | ||||
| 12pt C1S Cover | ||||
| 20 White Opaque Bond | ||||
| 50 Colored Offset | ||||
| 50 White Offset | ||||
| 50 White Opaque | ||||
| 60 Cover Stock | ||||
| 60 White Offset | ||||
| 80 Gloss Cover | ||||
| 80 Gloss Text | ||||
| 8pt C1S White | ||||
| 90 White Index | ||||
| CoverText Ink | ||||
| Black | ||||
| Black + 1 PMS color | Type in PMS color | |||
| Black + 2 PMS colors | Type in PMS colors | |||
| 4 color | ||||
| 4 color over black | ||||
| 4 color + 1 PMS color | Type in PMS color | |||
| 4 color over black + 1 PMS color | Type in PMS color | |||
| 4 color + 2 PMS colors | Type in PMS colors | |||
| 4 color + aqueous | ||||
| 4 color + varnish |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Cannot use quote symbol that is---- | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | 825 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | NA | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | GLOSS TEXT | 80 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 825 | 11 | NA | NA | NA | NA | HALF | 85 x 11 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| EA | 1 | 1 | See DocMan for the Cost Center selections associated with each Business Group | Black amp White | B | PERFECT | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | 2 | PLAIN | 20 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 85 | 11 | NA | 516 | 3LEFT | NA | NA | NA | NA | RRD must provide this information | Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1756-PM011B-EN-P | Logix5000 Controllers Produced andConsumed Tags | EA | 1 | 1 | Marketing Commercial | CMKMAY IA ControlVisNet - 19021 | 07012008 | 5 | Black amp White | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | 4 | 24 | 10 | PLAIN | 20 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 85 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information | Text Stock = 20 White Opaque BondText Ink = BlackCover Stock = 90 White IndexCover Ink = Black |
| Corp | 17501 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Bill To | 69 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| See DocMan for the Cost Center selections associated with each Business Group | RRD must provide this information | RRD must provide this information | RRD must provide this information | RRD must provide this information |
| PackagingOrdering Unit Of Measure | ||||
| EA = Each | ||||
| PK = Pack | ||||
| PD = Pad | ||||
| RL = Roll | ||||
| BK = Book | ||||
| CT = Carton | ||||
| BX = Box | ||||
| ST = Set | ||||
| Multiple Order Qty | ||||
| Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn) | ||||
| Business Group | ||||
| The business group that the publication supports Your choice here determines the list you choose from for Cost Center | ||||
| CorporateBusiness Development | ||||
| Finance | ||||
| Human Resources | ||||
| IT | ||||
| Logistics | ||||
| Manufacturing | ||||
| Marketing Commercial | ||||
| Marketing Europe | ||||
| Marketing Other | ||||
| Operations | ||||
| Order Services | ||||
| Other | ||||
| Process Improvement | ||||
| Procurement | ||||
| Quality | ||||
| Sales | ||||
| Max Order Quantity | ||||
| Presale items = 100 | ||||
| Postsale items = 5 | ||||
| NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it | ||||
| Item Category - Form (F) or Book (B) | ||||
| Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form | ||||
| Book (B) = Any publication that contains 3 or more pages | ||||
| BindingStitching | ||||
| For a Form (F) use | ||||
| CARBONLESS | ||||
| CUTSHEET | ||||
| ENVELOPE | ||||
| For a Book (B) use | ||||
| LOOSE | LOOSE -Loose Leaf | |||
| PERFECT | PERFECT - Perfect Bound | |||
| PLASTCOIL | PLASTCOIL - Plastic Coil | |||
| SADDLE | SADDLE - Saddle Stitch | |||
| STAPLED1 | STAPLED1 -1 position | |||
| STAPLED1B | STAPLED1B - bottom 1 position | |||
| STAPLED2 | STAPLED2 - 2 positions | |||
| THERMAL | THERMAL - Thermal bound | |||
| THERMALO | THERMALO - Thermal Bound - offline | |||
| Sides Printed | ||||
| Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page | ||||
| Simplex = Single-sided printing | ||||
| Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page | ||||
| Number of Forms to a Sheet | ||||
| Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4 | ||||
| Number of Sheets Required to Print | ||||
| Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of four 85 x 11 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4 | ||||
| Paper Stock Type | ||||
| Description | ||||
| PLAIN | Bond | |||
| ACNTCVR | Accent Cover | |||
| BOND3H | Bond (3-hole) | |||
| BOOKENV | Booklet Envelope | |||
| C1SGLOSS | C1S Gloss Finish | |||
| C1SMATTE | C1S Matt Finish | |||
| C2SGLOSS | C2S Gloss Finish | |||
| C2SMATTE | C2S Matt Finish | |||
| CARD | Card Stock | |||
| CATLGENV | Catalog Envelope | |||
| CATLGENV6 | 6 Catalog Envelope | |||
| COVERCOLOR | Color Cover Copy | |||
| CRCKPEEL | Crack N Peel Label | |||
| CUSTOM | Custom | |||
| CVRFUTURA | Futura Cover | |||
| ENV6x9 | Standard 6X9 Envelope | |||
| ENV9X12 | Standard 9X12 Envelope | |||
| ETHCERT | Ethicon Certificate | |||
| GLOSSCOVER | Gloss Cover | |||
| GLOSSTEXT | Gloss Text | |||
| HOTSTEXT | Hots Text | |||
| INDEX | Index | |||
| LABEL80 | 80 Up Label | |||
| MICROPRT | Micro Print | |||
| OFFSET | Offset | |||
| PART2 | 2 Part | |||
| PART3 | 3 Part | |||
| PART4 | 4 Part | |||
| PART5 | 5 Part | |||
| PART6 | 6 Part | |||
| PERF | 12 inch Perfed | |||
| PERMMAT | Perm Mat Ad | |||
| PRECUTTAB | Pre-Cut Tab | |||
| PREPERF | Pre-Perforated | |||
| RECYL | Recycled | |||
| SE10ENV | 10 Standard Envelope | |||
| SE10ITENV | 10 Inside Tint Envelope | |||
| SE9ENV | 9 Stanard Envelope | |||
| TAG | Tag | |||
| TEXT | Text | |||
| TEXTCOLOR | Text Color Copy | |||
| TEXTFUTURA | Futura Text | |||
| TEXTLASER | Text Laser Print | |||
| TRANSPRNCY | Transparencies | |||
| VELLUM | Vellum | |||
| VELLUM3HP | Vellum 3HP | |||
| WE10ENV | 10 Window Envelope | |||
| WE9ENV | 9 Windor Envelope | |||
| WE9ITENV | 9 Inside Tint Window Envelope | |||
| Paper Stock Color | ||||
| Black | ||||
| Blue | ||||
| Buff | ||||
| Canary | ||||
| Cherry | ||||
| Clear | ||||
| Cream | ||||
| Custom | ||||
| Goldrenrod | ||||
| Gray | ||||
| Green | ||||
| Ivory | ||||
| Lavender | ||||
| Manilla | ||||
| NCRPinkCanary | ||||
| NCRWhiteBlue | ||||
| NCRWhiteBlueCanary | ||||
| NCRWhiteCanary | ||||
| NCRWhiteCanaryPink | ||||
| NCRWhiteCanaryPinkGoldenrod | ||||
| NCRWhiteGreen | ||||
| NCRWhiteGoldenrodYellow | ||||
| NCRWhitePink | ||||
| NCRWhiteWhite | ||||
| Opaque | ||||
| Orange | ||||
| Orchid | ||||
| Peach | ||||
| Pink | ||||
| Purple | ||||
| Salmon | ||||
| Tan | ||||
| Violet | ||||
| White | ||||
| Finished Trim Sizes (listed - width x length) | ||||
| 11 x 17 | ||||
| 18 x 24 Poster | ||||
| 24 x 36 Poster | ||||
| 3 x 5 | ||||
| 36 x 24 Poster | ||||
| 4 x 6 | ||||
| 475 x 7 | ||||
| 475 x 775 | ||||
| 55 x 85 | ||||
| 6 x 4 | ||||
| 7 x 9 | ||||
| 7385 x 9 (RSI Std) | ||||
| 85 x 11 | ||||
| 825 x 10875 | ||||
| 825 x 11 (RA product profile std) | ||||
| 8375 x 10875 | ||||
| 9 x 12 | ||||
| A4 | ||||
| A5 | ||||
| Other - Custom size listed below | ||||
| Drilling Locations | ||||
| 1CENTER | ||||
| 1LEFTTOP | ||||
| 1TOPCENTER | ||||
| 2LEFT | ||||
| 2LEFT2TOP | ||||
| 2TOP | ||||
| 2TOP2LEFT | ||||
| 2TOP3LEFT | ||||
| 2TOP5LEFT | ||||
| 2TOP5RIGHT | ||||
| 3BOTTOM | ||||
| 3LEFT | ||||
| 3LEFT2TOP | ||||
| 3LEFT3TOP | ||||
| 3RIGHT | ||||
| 3TOP | ||||
| 3TOP5LEFT | ||||
| 5BOTTOOM | ||||
| 5CENTER | ||||
| 5LEFT | ||||
| 5RIGHT | ||||
| 5RIGHT2TOP | ||||
| 5TOP | ||||
| Fold Type | ||||
| For TRI fold - select Z or C type | Description | |||
| HALF | Half | |||
| C | C Fold | |||
| DBLEPARLL | Double Parallel | |||
| OFFSETZ | Offset Z | |||
| SAMPLE | See Sample | |||
| SHORT | Short Fold | |||
| V | V Fold | |||
| Z | Z Fold | |||
| Number of Pieces per Poly Wrap | ||||
| Publication length | Number per Poly Wrap | |||
| 77 or more pages | NA | |||
| 33 to 76 pages | 25 | |||
| 3 to 32 pages | 50 | |||
| 1 or 2 pages | 100 | |||
| Comments | ||||
| CoverText Stock | Spine | |||
| 100 Gloss Cover | If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Also do not include that page as part of the publication page count | |||
| 100 Gloss Text | ||||
| 100 Text | ||||
| 10pt C1S Cover | ||||
| 10pt C2S Cover | ||||
| 10pt C2S Text | ||||
| 10pt Text Stock | ||||
| 110 White Index | ||||
| 12pt C1S Cover | ||||
| 20 White Opaque Bond | ||||
| 50 Colored Offset | ||||
| 50 White Offset | ||||
| 50 White Opaque | ||||
| 60 Cover Stock | ||||
| 60 White Offset | ||||
| 80 Gloss Cover | ||||
| 80 Gloss Text | ||||
| 8pt C1S White | ||||
| 90 White Index | ||||
| CoverText Ink | ||||
| Black | ||||
| Black + 1 PMS color | Type in PMS color | |||
| Black + 2 PMS colors | Type in PMS colors | |||
| 4 color | ||||
| 4 color over black | ||||
| 4 color + 1 PMS color | Type in PMS color | |||
| 4 color over black + 1 PMS color | Type in PMS color | |||
| 4 color + 2 PMS colors | Type in PMS colors | |||
| 4 color + aqueous | ||||
| 4 color + varnish |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Cannot use quote symbol that is---- | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | 825 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | NA | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | GLOSS TEXT | 80 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 825 | 11 | NA | NA | NA | NA | HALF | 85 x 11 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| EA | 1 | 1 | See DocMan for the Cost Center selections associated with each Business Group | Black amp White | B | PERFECT | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | 2 | PLAIN | 20 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 85 | 11 | NA | 516 | 3LEFT | NA | NA | NA | NA | RRD must provide this information | Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 1756-PM011B-EN-P | Logix5000 Controllers Produced andConsumed Tags | EA | 1 | 1 | Marketing Commercial | CMKMAY IA ControlVisNet - 19021 | 07012008 | 5 | Black amp White | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | 4 | 24 | 10 | PLAIN | 20 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 85 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information | Text Stock = 20 White Opaque BondText Ink = BlackCover Stock = 90 White IndexCover Ink = Black |
| PackagingOrdering Unit Of Measure | ||||
| EA = Each | ||||
| PK = Pack | ||||
| PD = Pad | ||||
| RL = Roll | ||||
| BK = Book | ||||
| CT = Carton | ||||
| BX = Box | ||||
| ST = Set | ||||
| Multiple Order Qty | ||||
| Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn) | ||||
| Business Group | ||||
| The business group that the publication supports Your choice here determines the list you choose from for Cost Center | ||||
| CorporateBusiness Development | ||||
| Finance | ||||
| Human Resources | ||||
| IT | ||||
| Logistics | ||||
| Manufacturing | ||||
| Marketing Commercial | ||||
| Marketing Europe | ||||
| Marketing Other | ||||
| Operations | ||||
| Order Services | ||||
| Other | ||||
| Process Improvement | ||||
| Procurement | ||||
| Quality | ||||
| Sales | ||||
| Max Order Quantity | ||||
| Presale items = 100 | ||||
| Postsale items = 5 | ||||
| NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it | ||||
| Item Category - Form (F) or Book (B) | ||||
| Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form | ||||
| Book (B) = Any publication that contains 3 or more pages | ||||
| BindingStitching | ||||
| For a Form (F) use | ||||
| CARBONLESS | ||||
| CUTSHEET | ||||
| ENVELOPE | ||||
| For a Book (B) use | ||||
| LOOSE | LOOSE -Loose Leaf | |||
| PERFECT | PERFECT - Perfect Bound | |||
| PLASTCOIL | PLASTCOIL - Plastic Coil | |||
| SADDLE | SADDLE - Saddle Stitch | |||
| STAPLED1 | STAPLED1 -1 position | |||
| STAPLED1B | STAPLED1B - bottom 1 position | |||
| STAPLED2 | STAPLED2 - 2 positions | |||
| THERMAL | THERMAL - Thermal bound | |||
| THERMALO | THERMALO - Thermal Bound - offline | |||
| Sides Printed | ||||
| Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page | ||||
| Simplex = Single-sided printing | ||||
| Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page | ||||
| Number of Forms to a Sheet | ||||
| Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4 | ||||
| Number of Sheets Required to Print | ||||
| Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of four 85 x 11 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4 | ||||
| Paper Stock Type | ||||
| Description | ||||
| PLAIN | Bond | |||
| ACNTCVR | Accent Cover | |||
| BOND3H | Bond (3-hole) | |||
| BOOKENV | Booklet Envelope | |||
| C1SGLOSS | C1S Gloss Finish | |||
| C1SMATTE | C1S Matt Finish | |||
| C2SGLOSS | C2S Gloss Finish | |||
| C2SMATTE | C2S Matt Finish | |||
| CARD | Card Stock | |||
| CATLGENV | Catalog Envelope | |||
| CATLGENV6 | 6 Catalog Envelope | |||
| COVERCOLOR | Color Cover Copy | |||
| CRCKPEEL | Crack N Peel Label | |||
| CUSTOM | Custom | |||
| CVRFUTURA | Futura Cover | |||
| ENV6x9 | Standard 6X9 Envelope | |||
| ENV9X12 | Standard 9X12 Envelope | |||
| ETHCERT | Ethicon Certificate | |||
| GLOSSCOVER | Gloss Cover | |||
| GLOSSTEXT | Gloss Text | |||
| HOTSTEXT | Hots Text | |||
| INDEX | Index | |||
| LABEL80 | 80 Up Label | |||
| MICROPRT | Micro Print | |||
| OFFSET | Offset | |||
| PART2 | 2 Part | |||
| PART3 | 3 Part | |||
| PART4 | 4 Part | |||
| PART5 | 5 Part | |||
| PART6 | 6 Part | |||
| PERF | 12 inch Perfed | |||
| PERMMAT | Perm Mat Ad | |||
| PRECUTTAB | Pre-Cut Tab | |||
| PREPERF | Pre-Perforated | |||
| RECYL | Recycled | |||
| SE10ENV | 10 Standard Envelope | |||
| SE10ITENV | 10 Inside Tint Envelope | |||
| SE9ENV | 9 Stanard Envelope | |||
| TAG | Tag | |||
| TEXT | Text | |||
| TEXTCOLOR | Text Color Copy | |||
| TEXTFUTURA | Futura Text | |||
| TEXTLASER | Text Laser Print | |||
| TRANSPRNCY | Transparencies | |||
| VELLUM | Vellum | |||
| VELLUM3HP | Vellum 3HP | |||
| WE10ENV | 10 Window Envelope | |||
| WE9ENV | 9 Windor Envelope | |||
| WE9ITENV | 9 Inside Tint Window Envelope | |||
| Paper Stock Color | ||||
| Black | ||||
| Blue | ||||
| Buff | ||||
| Canary | ||||
| Cherry | ||||
| Clear | ||||
| Cream | ||||
| Custom | ||||
| Goldrenrod | ||||
| Gray | ||||
| Green | ||||
| Ivory | ||||
| Lavender | ||||
| Manilla | ||||
| NCRPinkCanary | ||||
| NCRWhiteBlue | ||||
| NCRWhiteBlueCanary | ||||
| NCRWhiteCanary | ||||
| NCRWhiteCanaryPink | ||||
| NCRWhiteCanaryPinkGoldenrod | ||||
| NCRWhiteGreen | ||||
| NCRWhiteGoldenrodYellow | ||||
| NCRWhitePink | ||||
| NCRWhiteWhite | ||||
| Opaque | ||||
| Orange | ||||
| Orchid | ||||
| Peach | ||||
| Pink | ||||
| Purple | ||||
| Salmon | ||||
| Tan | ||||
| Violet | ||||
| White | ||||
| Finished Trim Sizes (listed - width x length) | ||||
| 11 x 17 | ||||
| 18 x 24 Poster | ||||
| 24 x 36 Poster | ||||
| 3 x 5 | ||||
| 36 x 24 Poster | ||||
| 4 x 6 | ||||
| 475 x 7 | ||||
| 475 x 775 | ||||
| 55 x 85 | ||||
| 6 x 4 | ||||
| 7 x 9 | ||||
| 7385 x 9 (RSI Std) | ||||
| 85 x 11 | ||||
| 825 x 10875 | ||||
| 825 x 11 (RA product profile std) | ||||
| 8375 x 10875 | ||||
| 9 x 12 | ||||
| A4 | ||||
| A5 | ||||
| Other - Custom size listed below | ||||
| Drilling Locations | ||||
| 1CENTER | ||||
| 1LEFTTOP | ||||
| 1TOPCENTER | ||||
| 2LEFT | ||||
| 2LEFT2TOP | ||||
| 2TOP | ||||
| 2TOP2LEFT | ||||
| 2TOP3LEFT | ||||
| 2TOP5LEFT | ||||
| 2TOP5RIGHT | ||||
| 3BOTTOM | ||||
| 3LEFT | ||||
| 3LEFT2TOP | ||||
| 3LEFT3TOP | ||||
| 3RIGHT | ||||
| 3TOP | ||||
| 3TOP5LEFT | ||||
| 5BOTTOOM | ||||
| 5CENTER | ||||
| 5LEFT | ||||
| 5RIGHT | ||||
| 5RIGHT2TOP | ||||
| 5TOP | ||||
| Fold Type | ||||
| For TRI fold - select Z or C type | Description | |||
| HALF | Half | |||
| C | C Fold | |||
| DBLEPARLL | Double Parallel | |||
| OFFSETZ | Offset Z | |||
| SAMPLE | See Sample | |||
| SHORT | Short Fold | |||
| V | V Fold | |||
| Z | Z Fold | |||
| Number of Pieces per Poly Wrap | ||||
| Publication length | Number per Poly Wrap | |||
| 77 or more pages | NA | |||
| 33 to 76 pages | 25 | |||
| 3 to 32 pages | 50 | |||
| 1 or 2 pages | 100 | |||
| Comments | ||||
| CoverText Stock | Spine | |||
| 100 Gloss Cover | If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Also do not include that page as part of the publication page count | |||
| 100 Gloss Text | ||||
| 100 Text | ||||
| 10pt C1S Cover | ||||
| 10pt C2S Cover | ||||
| 10pt C2S Text | ||||
| 10pt Text Stock | ||||
| 110 White Index | ||||
| 12pt C1S Cover | ||||
| 20 White Opaque Bond | ||||
| 50 Colored Offset | ||||
| 50 White Offset | ||||
| 50 White Opaque | ||||
| 60 Cover Stock | ||||
| 60 White Offset | ||||
| 80 Gloss Cover | ||||
| 80 Gloss Text | ||||
| 8pt C1S White | ||||
| 90 White Index | ||||
| CoverText Ink | ||||
| Black | ||||
| Black + 1 PMS color | Type in PMS color | |||
| Black + 2 PMS colors | Type in PMS colors | |||
| 4 color | ||||
| 4 color over black | ||||
| 4 color + 1 PMS color | Type in PMS color | |||
| 4 color over black + 1 PMS color | Type in PMS color | |||
| 4 color + 2 PMS colors | Type in PMS colors | |||
| 4 color + aqueous | ||||
| 4 color + varnish |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Cannot use quote symbol that is---- | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | 825 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | NA | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | GLOSS TEXT | 80 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 825 | 11 | NA | NA | NA | NA | HALF | 85 x 11 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| EA | 1 | 1 | See DocMan for the Cost Center selections associated with each Business Group | Black amp White | B | PERFECT | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | 2 | PLAIN | 20 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 85 | 11 | NA | 516 | 3LEFT | NA | NA | NA | NA | RRD must provide this information | Cover Stock = 90 White IndexText Stock = 20 White Opaque BondCover Ink = BlackText Ink = BlackSpine = If included as last page of PDF |
| PackagingOrdering Unit Of Measure | ||||
| EA = Each | ||||
| PK = Pack | ||||
| PD = Pad | ||||
| RL = Roll | ||||
| BK = Book | ||||
| CT = Carton | ||||
| BX = Box | ||||
| ST = Set | ||||
| Multiple Order Qty | ||||
| Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn) | ||||
| Business Group | ||||
| The business group that the publication supports Your choice here determines the list you choose from for Cost Center | ||||
| CorporateBusiness Development | ||||
| Finance | ||||
| Human Resources | ||||
| IT | ||||
| Logistics | ||||
| Manufacturing | ||||
| Marketing Commercial | ||||
| Marketing Europe | ||||
| Marketing Other | ||||
| Operations | ||||
| Order Services | ||||
| Other | ||||
| Process Improvement | ||||
| Procurement | ||||
| Quality | ||||
| Sales | ||||
| Max Order Quantity | ||||
| Presale items = 100 | ||||
| Postsale items = 5 | ||||
| NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it | ||||
| Item Category - Form (F) or Book (B) | ||||
| Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form | ||||
| Book (B) = Any publication that contains 3 or more pages | ||||
| BindingStitching | ||||
| For a Form (F) use | ||||
| CARBONLESS | ||||
| CUTSHEET | ||||
| ENVELOPE | ||||
| For a Book (B) use | ||||
| LOOSE | LOOSE -Loose Leaf | |||
| PERFECT | PERFECT - Perfect Bound | |||
| PLASTCOIL | PLASTCOIL - Plastic Coil | |||
| SADDLE | SADDLE - Saddle Stitch | |||
| STAPLED1 | STAPLED1 -1 position | |||
| STAPLED1B | STAPLED1B - bottom 1 position | |||
| STAPLED2 | STAPLED2 - 2 positions | |||
| THERMAL | THERMAL - Thermal bound | |||
| THERMALO | THERMALO - Thermal Bound - offline | |||
| Sides Printed | ||||
| Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page | ||||
| Simplex = Single-sided printing | ||||
| Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page | ||||
| Number of Forms to a Sheet | ||||
| Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4 | ||||
| Number of Sheets Required to Print | ||||
| Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of four 85 x 11 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4 | ||||
| Paper Stock Type | ||||
| Description | ||||
| PLAIN | Bond | |||
| ACNTCVR | Accent Cover | |||
| BOND3H | Bond (3-hole) | |||
| BOOKENV | Booklet Envelope | |||
| C1SGLOSS | C1S Gloss Finish | |||
| C1SMATTE | C1S Matt Finish | |||
| C2SGLOSS | C2S Gloss Finish | |||
| C2SMATTE | C2S Matt Finish | |||
| CARD | Card Stock | |||
| CATLGENV | Catalog Envelope | |||
| CATLGENV6 | 6 Catalog Envelope | |||
| COVERCOLOR | Color Cover Copy | |||
| CRCKPEEL | Crack N Peel Label | |||
| CUSTOM | Custom | |||
| CVRFUTURA | Futura Cover | |||
| ENV6x9 | Standard 6X9 Envelope | |||
| ENV9X12 | Standard 9X12 Envelope | |||
| ETHCERT | Ethicon Certificate | |||
| GLOSSCOVER | Gloss Cover | |||
| GLOSSTEXT | Gloss Text | |||
| HOTSTEXT | Hots Text | |||
| INDEX | Index | |||
| LABEL80 | 80 Up Label | |||
| MICROPRT | Micro Print | |||
| OFFSET | Offset | |||
| PART2 | 2 Part | |||
| PART3 | 3 Part | |||
| PART4 | 4 Part | |||
| PART5 | 5 Part | |||
| PART6 | 6 Part | |||
| PERF | 12 inch Perfed | |||
| PERMMAT | Perm Mat Ad | |||
| PRECUTTAB | Pre-Cut Tab | |||
| PREPERF | Pre-Perforated | |||
| RECYL | Recycled | |||
| SE10ENV | 10 Standard Envelope | |||
| SE10ITENV | 10 Inside Tint Envelope | |||
| SE9ENV | 9 Stanard Envelope | |||
| TAG | Tag | |||
| TEXT | Text | |||
| TEXTCOLOR | Text Color Copy | |||
| TEXTFUTURA | Futura Text | |||
| TEXTLASER | Text Laser Print | |||
| TRANSPRNCY | Transparencies | |||
| VELLUM | Vellum | |||
| VELLUM3HP | Vellum 3HP | |||
| WE10ENV | 10 Window Envelope | |||
| WE9ENV | 9 Windor Envelope | |||
| WE9ITENV | 9 Inside Tint Window Envelope | |||
| Paper Stock Color | ||||
| Black | ||||
| Blue | ||||
| Buff | ||||
| Canary | ||||
| Cherry | ||||
| Clear | ||||
| Cream | ||||
| Custom | ||||
| Goldrenrod | ||||
| Gray | ||||
| Green | ||||
| Ivory | ||||
| Lavender | ||||
| Manilla | ||||
| NCRPinkCanary | ||||
| NCRWhiteBlue | ||||
| NCRWhiteBlueCanary | ||||
| NCRWhiteCanary | ||||
| NCRWhiteCanaryPink | ||||
| NCRWhiteCanaryPinkGoldenrod | ||||
| NCRWhiteGreen | ||||
| NCRWhiteGoldenrodYellow | ||||
| NCRWhitePink | ||||
| NCRWhiteWhite | ||||
| Opaque | ||||
| Orange | ||||
| Orchid | ||||
| Peach | ||||
| Pink | ||||
| Purple | ||||
| Salmon | ||||
| Tan | ||||
| Violet | ||||
| White | ||||
| Finished Trim Sizes (listed - width x length) | ||||
| 11 x 17 | ||||
| 18 x 24 Poster | ||||
| 24 x 36 Poster | ||||
| 3 x 5 | ||||
| 36 x 24 Poster | ||||
| 4 x 6 | ||||
| 475 x 7 | ||||
| 475 x 775 | ||||
| 55 x 85 | ||||
| 6 x 4 | ||||
| 7 x 9 | ||||
| 7385 x 9 (RSI Std) | ||||
| 85 x 11 | ||||
| 825 x 10875 | ||||
| 825 x 11 (RA product profile std) | ||||
| 8375 x 10875 | ||||
| 9 x 12 | ||||
| A4 | ||||
| A5 | ||||
| Other - Custom size listed below | ||||
| Drilling Locations | ||||
| 1CENTER | ||||
| 1LEFTTOP | ||||
| 1TOPCENTER | ||||
| 2LEFT | ||||
| 2LEFT2TOP | ||||
| 2TOP | ||||
| 2TOP2LEFT | ||||
| 2TOP3LEFT | ||||
| 2TOP5LEFT | ||||
| 2TOP5RIGHT | ||||
| 3BOTTOM | ||||
| 3LEFT | ||||
| 3LEFT2TOP | ||||
| 3LEFT3TOP | ||||
| 3RIGHT | ||||
| 3TOP | ||||
| 3TOP5LEFT | ||||
| 5BOTTOOM | ||||
| 5CENTER | ||||
| 5LEFT | ||||
| 5RIGHT | ||||
| 5RIGHT2TOP | ||||
| 5TOP | ||||
| Fold Type | ||||
| For TRI fold - select Z or C type | Description | |||
| HALF | Half | |||
| C | C Fold | |||
| DBLEPARLL | Double Parallel | |||
| OFFSETZ | Offset Z | |||
| SAMPLE | See Sample | |||
| SHORT | Short Fold | |||
| V | V Fold | |||
| Z | Z Fold | |||
| Number of Pieces per Poly Wrap | ||||
| Publication length | Number per Poly Wrap | |||
| 77 or more pages | NA | |||
| 33 to 76 pages | 25 | |||
| 3 to 32 pages | 50 | |||
| 1 or 2 pages | 100 | |||
| Comments | ||||
| CoverText Stock | Spine | |||
| 100 Gloss Cover | If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Also do not include that page as part of the publication page count | |||
| 100 Gloss Text | ||||
| 100 Text | ||||
| 10pt C1S Cover | ||||
| 10pt C2S Cover | ||||
| 10pt C2S Text | ||||
| 10pt Text Stock | ||||
| 110 White Index | ||||
| 12pt C1S Cover | ||||
| 20 White Opaque Bond | ||||
| 50 Colored Offset | ||||
| 50 White Offset | ||||
| 50 White Opaque | ||||
| 60 Cover Stock | ||||
| 60 White Offset | ||||
| 80 Gloss Cover | ||||
| 80 Gloss Text | ||||
| 8pt C1S White | ||||
| 90 White Index | ||||
| CoverText Ink | ||||
| Black | ||||
| Black + 1 PMS color | Type in PMS color | |||
| Black + 2 PMS colors | Type in PMS colors | |||
| 4 color | ||||
| 4 color over black | ||||
| 4 color + 1 PMS color | Type in PMS color | |||
| 4 color over black + 1 PMS color | Type in PMS color | |||
| 4 color + 2 PMS colors | Type in PMS colors | |||
| 4 color + aqueous | ||||
| 4 color + varnish |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Cannot use quote symbol that is---- | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | 825 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Item Description | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | NA | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | GLOSS TEXT | 80 | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | NA | 825 | 11 | NA | NA | NA | NA | HALF | 85 x 11 | RRD must provide this information |
| PackagingOrdering Unit Of Measure | ||||
| EA = Each | ||||
| PK = Pack | ||||
| PD = Pad | ||||
| RL = Roll | ||||
| BK = Book | ||||
| CT = Carton | ||||
| BX = Box | ||||
| ST = Set | ||||
| Multiple Order Qty | ||||
| Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn) | ||||
| Business Group | ||||
| The business group that the publication supports Your choice here determines the list you choose from for Cost Center | ||||
| CorporateBusiness Development | ||||
| Finance | ||||
| Human Resources | ||||
| IT | ||||
| Logistics | ||||
| Manufacturing | ||||
| Marketing Commercial | ||||
| Marketing Europe | ||||
| Marketing Other | ||||
| Operations | ||||
| Order Services | ||||
| Other | ||||
| Process Improvement | ||||
| Procurement | ||||
| Quality | ||||
| Sales | ||||
| Max Order Quantity | ||||
| Presale items = 100 | ||||
| Postsale items = 5 | ||||
| NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it | ||||
| Item Category - Form (F) or Book (B) | ||||
| Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form | ||||
| Book (B) = Any publication that contains 3 or more pages | ||||
| BindingStitching | ||||
| For a Form (F) use | ||||
| CARBONLESS | ||||
| CUTSHEET | ||||
| ENVELOPE | ||||
| For a Book (B) use | ||||
| LOOSE | LOOSE -Loose Leaf | |||
| PERFECT | PERFECT - Perfect Bound | |||
| PLASTCOIL | PLASTCOIL - Plastic Coil | |||
| SADDLE | SADDLE - Saddle Stitch | |||
| STAPLED1 | STAPLED1 -1 position | |||
| STAPLED1B | STAPLED1B - bottom 1 position | |||
| STAPLED2 | STAPLED2 - 2 positions | |||
| THERMAL | THERMAL - Thermal bound | |||
| THERMALO | THERMALO - Thermal Bound - offline | |||
| Sides Printed | ||||
| Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page | ||||
| Simplex = Single-sided printing | ||||
| Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page | ||||
| Number of Forms to a Sheet | ||||
| Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4 | ||||
| Number of Sheets Required to Print | ||||
| Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of four 85 x 11 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4 | ||||
| Paper Stock Type | ||||
| Description | ||||
| PLAIN | Bond | |||
| ACNTCVR | Accent Cover | |||
| BOND3H | Bond (3-hole) | |||
| BOOKENV | Booklet Envelope | |||
| C1SGLOSS | C1S Gloss Finish | |||
| C1SMATTE | C1S Matt Finish | |||
| C2SGLOSS | C2S Gloss Finish | |||
| C2SMATTE | C2S Matt Finish | |||
| CARD | Card Stock | |||
| CATLGENV | Catalog Envelope | |||
| CATLGENV6 | 6 Catalog Envelope | |||
| COVERCOLOR | Color Cover Copy | |||
| CRCKPEEL | Crack N Peel Label | |||
| CUSTOM | Custom | |||
| CVRFUTURA | Futura Cover | |||
| ENV6x9 | Standard 6X9 Envelope | |||
| ENV9X12 | Standard 9X12 Envelope | |||
| ETHCERT | Ethicon Certificate | |||
| GLOSSCOVER | Gloss Cover | |||
| GLOSSTEXT | Gloss Text | |||
| HOTSTEXT | Hots Text | |||
| INDEX | Index | |||
| LABEL80 | 80 Up Label | |||
| MICROPRT | Micro Print | |||
| OFFSET | Offset | |||
| PART2 | 2 Part | |||
| PART3 | 3 Part | |||
| PART4 | 4 Part | |||
| PART5 | 5 Part | |||
| PART6 | 6 Part | |||
| PERF | 12 inch Perfed | |||
| PERMMAT | Perm Mat Ad | |||
| PRECUTTAB | Pre-Cut Tab | |||
| PREPERF | Pre-Perforated | |||
| RECYL | Recycled | |||
| SE10ENV | 10 Standard Envelope | |||
| SE10ITENV | 10 Inside Tint Envelope | |||
| SE9ENV | 9 Stanard Envelope | |||
| TAG | Tag | |||
| TEXT | Text | |||
| TEXTCOLOR | Text Color Copy | |||
| TEXTFUTURA | Futura Text | |||
| TEXTLASER | Text Laser Print | |||
| TRANSPRNCY | Transparencies | |||
| VELLUM | Vellum | |||
| VELLUM3HP | Vellum 3HP | |||
| WE10ENV | 10 Window Envelope | |||
| WE9ENV | 9 Windor Envelope | |||
| WE9ITENV | 9 Inside Tint Window Envelope | |||
| Paper Stock Color | ||||
| Black | ||||
| Blue | ||||
| Buff | ||||
| Canary | ||||
| Cherry | ||||
| Clear | ||||
| Cream | ||||
| Custom | ||||
| Goldrenrod | ||||
| Gray | ||||
| Green | ||||
| Ivory | ||||
| Lavender | ||||
| Manilla | ||||
| NCRPinkCanary | ||||
| NCRWhiteBlue | ||||
| NCRWhiteBlueCanary | ||||
| NCRWhiteCanary | ||||
| NCRWhiteCanaryPink | ||||
| NCRWhiteCanaryPinkGoldenrod | ||||
| NCRWhiteGreen | ||||
| NCRWhiteGoldenrodYellow | ||||
| NCRWhitePink | ||||
| NCRWhiteWhite | ||||
| Opaque | ||||
| Orange | ||||
| Orchid | ||||
| Peach | ||||
| Pink | ||||
| Purple | ||||
| Salmon | ||||
| Tan | ||||
| Violet | ||||
| White | ||||
| Finished Trim Sizes (listed - width x length) | ||||
| 11 x 17 | ||||
| 18 x 24 Poster | ||||
| 24 x 36 Poster | ||||
| 3 x 5 | ||||
| 36 x 24 Poster | ||||
| 4 x 6 | ||||
| 475 x 7 | ||||
| 475 x 775 | ||||
| 55 x 85 | ||||
| 6 x 4 | ||||
| 7 x 9 | ||||
| 7385 x 9 (RSI Std) | ||||
| 85 x 11 | ||||
| 825 x 10875 | ||||
| 825 x 11 (RA product profile std) | ||||
| 8375 x 10875 | ||||
| 9 x 12 | ||||
| A4 | ||||
| A5 | ||||
| Other - Custom size listed below | ||||
| Drilling Locations | ||||
| 1CENTER | ||||
| 1LEFTTOP | ||||
| 1TOPCENTER | ||||
| 2LEFT | ||||
| 2LEFT2TOP | ||||
| 2TOP | ||||
| 2TOP2LEFT | ||||
| 2TOP3LEFT | ||||
| 2TOP5LEFT | ||||
| 2TOP5RIGHT | ||||
| 3BOTTOM | ||||
| 3LEFT | ||||
| 3LEFT2TOP | ||||
| 3LEFT3TOP | ||||
| 3RIGHT | ||||
| 3TOP | ||||
| 3TOP5LEFT | ||||
| 5BOTTOOM | ||||
| 5CENTER | ||||
| 5LEFT | ||||
| 5RIGHT | ||||
| 5RIGHT2TOP | ||||
| 5TOP | ||||
| Fold Type | ||||
| For TRI fold - select Z or C type | Description | |||
| HALF | Half | |||
| C | C Fold | |||
| DBLEPARLL | Double Parallel | |||
| OFFSETZ | Offset Z | |||
| SAMPLE | See Sample | |||
| SHORT | Short Fold | |||
| V | V Fold | |||
| Z | Z Fold | |||
| Number of Pieces per Poly Wrap | ||||
| Publication length | Number per Poly Wrap | |||
| 77 or more pages | NA | |||
| 33 to 76 pages | 25 | |||
| 3 to 32 pages | 50 | |||
| 1 or 2 pages | 100 | |||
| Comments | ||||
| CoverText Stock | Spine | |||
| 100 Gloss Cover | If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Also do not include that page as part of the publication page count | |||
| 100 Gloss Text | ||||
| 100 Text | ||||
| 10pt C1S Cover | ||||
| 10pt C2S Cover | ||||
| 10pt C2S Text | ||||
| 10pt Text Stock | ||||
| 110 White Index | ||||
| 12pt C1S Cover | ||||
| 20 White Opaque Bond | ||||
| 50 Colored Offset | ||||
| 50 White Offset | ||||
| 50 White Opaque | ||||
| 60 Cover Stock | ||||
| 60 White Offset | ||||
| 80 Gloss Cover | ||||
| 80 Gloss Text | ||||
| 8pt C1S White | ||||
| 90 White Index | ||||
| CoverText Ink | ||||
| Black | ||||
| Black + 1 PMS color | Type in PMS color | |||
| Black + 2 PMS colors | Type in PMS colors | |||
| 4 color | ||||
| 4 color over black | ||||
| 4 color + 1 PMS color | Type in PMS color | |||
| 4 color over black + 1 PMS color | Type in PMS color | |||
| 4 color + 2 PMS colors | Type in PMS colors | |||
| 4 color + aqueous | ||||
| 4 color + varnish |
| dPrint | ContentComp | Split Shipment Indicator Flag | WCSS Item Number | Customer Item Number | Cannot use quote symbol that is---- | Producing Plant | Job Number | Replenishing Plant | Plant Code | Product Code | PackagingOrdering UOM | Qty per PackagingOrdering UOM | List Price Per Ea | Transfer Cost per Ea | Sell Price per Ea | Standard Cost (per Ea) | Min Order Qty (in eaches) | Multiple Order Qty (in Eaches | Chargeback Price | Item Reference 1 | Item Reference 2 | Revision Field | Max Order Qty (in eaches) | Sequentially Numbered Item | Sequentially Numbered Item - Details | Priced for Digital or Offset | Content File Location | Item Category Form (F) Book (B) | Item Subtype | Orientation | Sides Printed | CSSJLS Stock Componet | Paper Size Width | Paper Size Length | No of Forms to a Sheet | Page Qty | Sheets Qty | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | of Tabs | Binder Size | Binder Color | Binder Ring Type | Binder Transparency (clearview or matt) | Thermal Tape Color | Trim Size Width | Trim Size Length | Stitching Location | Drilling Size | Drilling Location | Glue Location | Pad | Fold Type | Fold At | Poly | Box | Comments | Cross Reference Item Number 1 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Number | Publication Title | PackagingOrdering Unit Of Measure | Qty per PackagingOrdering Unit of Measure | Min Order Qty | Multiple Order Qty | Business Group | Cost Center | Revision Date | Max Order Qty | Black amp Whiteor Color | Item CategoryForm (F) or Book (B) | BindingStitching | Orientation | Sides Printed | Printing Paper Size Width | Printing Paper Size Length | Number of Forms to a Sheet | Page Count of Publication | Number of Sheets Required to Print | CSSJLS Production Stock | Paper Stock Type | Paper Stock Weight | Paper Stock Color | Stack Offset | Tab Size | Number of Tabs Needed | Binder Size | Binder Color | Binder Ring Type | Binder Transparency | Thermal Tape Color | Finished Trim Size Width | Finished Trim Size Length | Stitching Location | Drill Hole Size | Number and Location of Drill Holes | Glue Location | Number of Pages per Pad | Fold Type | Fold At | Number of Pieces per Poly wrap | Number of Pieces per Box | Comments | Part Number | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Are these items being setup on dPrint (Yes or No) If yes Inv Mgmt to check Print Management flag on item setup | The contentComp will be provided by the CSC once the spec files are loaded to the DAS (the files must be named with the WCSS item ) The contentcomp must be hardcoded to the Item message Field in WCSS Must be a 10 Digit number that starts with an 8 | Required Setting this to yes will allow warehouse product to ship out before the JIT item is completed Setting this to no will hold all warehoused items until the printing of this item is complete Please indicate Y or N Note Each item with a Y will always ship separately even if produced at the same time as like items | Optional 15 Characters Max If the WCSS number provided already exists in the system then Inventory Management will assign a random WCSS number | 30 characters maximum | Cannot use quote symbol that is---- | Required Which plantPrint Center will produce this item | Required To be provided from the producing plant for JIT su | Required What is the plant code of the plant that has owning rights to the dPrint files If produced at multiple plants there can be only one owning plant | Required What is the plant code of the facility that will produce this item (see Plant and Whse Codes tab below) | Required Enter one of the applicable product | Method of packaging for publication shipmentClick here for explanation of each value in the pull-down | Required This field auto-calculates (transfer cost divided by 5) Used to determine Standard Cost on WCSS (which is 50 of the list price for these product codes) | Required Transfer Cost per orderingpackaging unit of measure | Required Price that will be billed to customer upon order If Price Breaks enter Price Breaks and note them on separate spreadsheet | Required Replacement Cost per Packagingordering UOM | Click here for an explanation of this field otherwise type NA | Optional Used to assist customer with internal Chargebacks to end users (per packagingordering UOM) | IMPORTANT This information must match the DocMan recordClick here for explanation of each value in the pull-down menu | IMPORTANT This information must match the DocMan record | IMPORTANT This information must match the DocMan recordDate on the publication | Click here for explanation of each value in the pull-down menu | Indicate Yes or No Enter Yes if the item is a sequentially numbered item | Describe the details behind the sequentially numbered item such as- Record Sequence Shipped whse will record the sequence numbers that shipped- Ship in Sequence Record required to ship products in particular sequence and the whse records the numbers | Required If PDF is to be retained in the DAS enter DAS in this field if item is part of eCreate or Custom Docs put CUSTOM in this field | Typically a BookClick here for explanation of each value in the pull-down menu | Click here for explanation of each value in the pull-down | Click here for explanation of each value in the pull-down menu | Optional Use when finished product stored in the warehouse is to be inserted into the construction of a JIT book | IMPORTANT Not Trim Size widthThis is the width of the paper on which the publication is printed | IMPORTANT Not Trim Size lengthThis is the length of the paper on which the publication is printed | Click here for explanation of how to determine the information required | Click here for explanation of how to determine the information required | Optional Use when product is being printed on Shell Stock Provide warehoused WCSS Item number of product to be used in the production of JIT item | Click here for explanation of how to determine the information required | The pull-down menu lists the most common choicesClick here for a full list of the available choicesIf you use a choice not in the pull-down list type the value in the cell below the pull-down menu | If item uses tabs otherwise NA | If needed otherwise type NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If item used in a binder otherwise NA | If publication is thermal tape bound otherwise NA | Click here to see the available finished trim sizesThe sizes are listed - width x length | Click here to see the available finished trim sizesThe sizes are listed - width x length | If publication is Book [B] and stapled otherwise NA | Click here for a list of possible drill locations | If publication uses padding otherwise NA | If publication is a notepad or message pad otherwise NA | Click here for explanation of each value in the pull-down menu Folding of final document optional | The location(s) of the fold | Click here for explanation of each value in the pull-down menu | Use this column to list- Cover Stock- Text Stock- Cover Ink- Text Ink- Spine if necessaryAlso use to indicate any other production or finishing requirements not provided in previous columnsClick here for an explanation of the available Cover Stock Cover Ink and Text Ink values | List only if pubication is used in manufacturing otherwise leave blank | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| PK | 1 | See DocMan for the Cost Center selections associated with each Business Group | Color | B | SADDLE | PORTRAIT | HEAD2HEAD | RRD must provide this information | RRD must provide this information | White | RRD must provide this information | NA | NA | NA | NA | NA | NA | 825 | 11 | SIDE | NA | NA | NA | NA | HALF | 85 x 11 | 50 | RRD must provide this information |
| PackagingOrdering Unit Of Measure | ||||
| EA = Each | ||||
| PK = Pack | ||||
| PD = Pad | ||||
| RL = Roll | ||||
| BK = Book | ||||
| CT = Carton | ||||
| BX = Box | ||||
| ST = Set | ||||
| Multiple Order Qty | ||||
| Separate methods of ordering same item For example if an item is packaged 50 per pad 5 pads per carton You can set the order qty as 50 each (one pad) or 250 each (1 ctn) | ||||
| Business Group | ||||
| The business group that the publication supports Your choice here determines the list you choose from for Cost Center | ||||
| CorporateBusiness Development | ||||
| Finance | ||||
| Human Resources | ||||
| IT | ||||
| Logistics | ||||
| Manufacturing | ||||
| Marketing Commercial | ||||
| Marketing Europe | ||||
| Marketing Other | ||||
| Operations | ||||
| Order Services | ||||
| Other | ||||
| Process Improvement | ||||
| Procurement | ||||
| Quality | ||||
| Sales | ||||
| Max Order Quantity | ||||
| Presale items = 100 | ||||
| Postsale items = 5 | ||||
| NOTE You can use other quantities but the delivery may take a bit longer because a system admin must approve it | ||||
| Item Category - Form (F) or Book (B) | ||||
| Form (F) = Any publication that is a single sheet (ie 1 or 2 pages) an envelope or carbonless form | ||||
| Book (B) = Any publication that contains 3 or more pages | ||||
| BindingStitching | ||||
| For a Form (F) use | ||||
| CARBONLESS | ||||
| CUTSHEET | ||||
| ENVELOPE | ||||
| For a Book (B) use | ||||
| LOOSE | LOOSE -Loose Leaf | |||
| PERFECT | PERFECT - Perfect Bound | |||
| PLASTCOIL | PLASTCOIL - Plastic Coil | |||
| SADDLE | SADDLE - Saddle Stitch | |||
| STAPLED1 | STAPLED1 -1 position | |||
| STAPLED1B | STAPLED1B - bottom 1 position | |||
| STAPLED2 | STAPLED2 - 2 positions | |||
| THERMAL | THERMAL - Thermal bound | |||
| THERMALO | THERMALO - Thermal Bound - offline | |||
| Sides Printed | ||||
| Head2Head = Most common Double-sided printing with headers on both pages lining up at the top of the page | ||||
| Simplex = Single-sided printing | ||||
| Head2Toe = Least common Double-sided printing with header on one page lining up with the footer on the other page | ||||
| Number of Forms to a Sheet | ||||
| Number of publication pages printed on a sheet of paper at the printerFor example if a 4-page 85 x 11 publication is printed on the front and back sides of an 11 x 17 sheet of paper that is folded in half the Number of Forms to a Sheet = 4Example 2 If a 4-page 55 x 85 publication is printed on the front and back sides of an 85 x 11 sheet of paper that is folded in half the Number of forms to a Sheet = 4 | ||||
| Number of Sheets Required to Print | ||||
| Number of sheets of paper required to print the publicationFor example if a 16-page 85 x 11 publication is printed on the front and back sides of four 11 x 17 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4Example 4 If a 4-page 55 x 85 publication is printed on the front and back sides of four 85 x 11 sheets of paper that are folded in half and saddle stitched together the Number of Sheets Required to Print = 4 | ||||
| Paper Stock Type | ||||
| Description | ||||
| PLAIN | Bond | |||
| ACNTCVR | Accent Cover | |||
| BOND3H | Bond (3-hole) | |||
| BOOKENV | Booklet Envelope | |||
| C1SGLOSS | C1S Gloss Finish | |||
| C1SMATTE | C1S Matt Finish | |||
| C2SGLOSS | C2S Gloss Finish | |||
| C2SMATTE | C2S Matt Finish | |||
| CARD | Card Stock | |||
| CATLGENV | Catalog Envelope | |||
| CATLGENV6 | 6 Catalog Envelope | |||
| COVERCOLOR | Color Cover Copy | |||
| CRCKPEEL | Crack N Peel Label | |||
| CUSTOM | Custom | |||
| CVRFUTURA | Futura Cover | |||
| ENV6x9 | Standard 6X9 Envelope | |||
| ENV9X12 | Standard 9X12 Envelope | |||
| ETHCERT | Ethicon Certificate | |||
| GLOSSCOVER | Gloss Cover | |||
| GLOSSTEXT | Gloss Text | |||
| HOTSTEXT | Hots Text | |||
| INDEX | Index | |||
| LABEL80 | 80 Up Label | |||
| MICROPRT | Micro Print | |||
| OFFSET | Offset | |||
| PART2 | 2 Part | |||
| PART3 | 3 Part | |||
| PART4 | 4 Part | |||
| PART5 | 5 Part | |||
| PART6 | 6 Part | |||
| PERF | 12 inch Perfed | |||
| PERMMAT | Perm Mat Ad | |||
| PRECUTTAB | Pre-Cut Tab | |||
| PREPERF | Pre-Perforated | |||
| RECYL | Recycled | |||
| SE10ENV | 10 Standard Envelope | |||
| SE10ITENV | 10 Inside Tint Envelope | |||
| SE9ENV | 9 Stanard Envelope | |||
| TAG | Tag | |||
| TEXT | Text | |||
| TEXTCOLOR | Text Color Copy | |||
| TEXTFUTURA | Futura Text | |||
| TEXTLASER | Text Laser Print | |||
| TRANSPRNCY | Transparencies | |||
| VELLUM | Vellum | |||
| VELLUM3HP | Vellum 3HP | |||
| WE10ENV | 10 Window Envelope | |||
| WE9ENV | 9 Windor Envelope | |||
| WE9ITENV | 9 Inside Tint Window Envelope | |||
| Paper Stock Color | ||||
| Black | ||||
| Blue | ||||
| Buff | ||||
| Canary | ||||
| Cherry | ||||
| Clear | ||||
| Cream | ||||
| Custom | ||||
| Goldrenrod | ||||
| Gray | ||||
| Green | ||||
| Ivory | ||||
| Lavender | ||||
| Manilla | ||||
| NCRPinkCanary | ||||
| NCRWhiteBlue | ||||
| NCRWhiteBlueCanary | ||||
| NCRWhiteCanary | ||||
| NCRWhiteCanaryPink | ||||
| NCRWhiteCanaryPinkGoldenrod | ||||
| NCRWhiteGreen | ||||
| NCRWhiteGoldenrodYellow | ||||
| NCRWhitePink | ||||
| NCRWhiteWhite | ||||
| Opaque | ||||
| Orange | ||||
| Orchid | ||||
| Peach | ||||
| Pink | ||||
| Purple | ||||
| Salmon | ||||
| Tan | ||||
| Violet | ||||
| White | ||||
| Finished Trim Sizes (listed - width x length) | ||||
| 11 x 17 | ||||
| 18 x 24 Poster | ||||
| 24 x 36 Poster | ||||
| 3 x 5 | ||||
| 36 x 24 Poster | ||||
| 4 x 6 | ||||
| 475 x 7 | ||||
| 475 x 775 | ||||
| 55 x 85 | ||||
| 6 x 4 | ||||
| 7 x 9 | ||||
| 7385 x 9 (RSI Std) | ||||
| 85 x 11 | ||||
| 825 x 10875 | ||||
| 825 x 11 (RA product profile std) | ||||
| 8375 x 10875 | ||||
| 9 x 12 | ||||
| A4 | ||||
| A5 | ||||
| Other - Custom size listed below | ||||
| Drilling Locations | ||||
| 1CENTER | ||||
| 1LEFTTOP | ||||
| 1TOPCENTER | ||||
| 2LEFT | ||||
| 2LEFT2TOP | ||||
| 2TOP | ||||
| 2TOP2LEFT | ||||
| 2TOP3LEFT | ||||
| 2TOP5LEFT | ||||
| 2TOP5RIGHT | ||||
| 3BOTTOM | ||||
| 3LEFT | ||||
| 3LEFT2TOP | ||||
| 3LEFT3TOP | ||||
| 3RIGHT | ||||
| 3TOP | ||||
| 3TOP5LEFT | ||||
| 5BOTTOOM | ||||
| 5CENTER | ||||
| 5LEFT | ||||
| 5RIGHT | ||||
| 5RIGHT2TOP | ||||
| 5TOP | ||||
| Fold Type | ||||
| For TRI fold - select Z or C type | Description | |||
| HALF | Half | |||
| C | C Fold | |||
| DBLEPARLL | Double Parallel | |||
| OFFSETZ | Offset Z | |||
| SAMPLE | See Sample | |||
| SHORT | Short Fold | |||
| V | V Fold | |||
| Z | Z Fold | |||
| Number of Pieces per Poly Wrap | ||||
| Publication length | Number per Poly Wrap | |||
| 77 or more pages | NA | |||
| 33 to 76 pages | 25 | |||
| 3 to 32 pages | 50 | |||
| 1 or 2 pages | 100 | |||
| Comments | ||||
| CoverText Stock | Spine | |||
| 100 Gloss Cover | If your publication uses a spine make note of that in the comments field Be sure to include the spine as the last page of your PDF Also do not include that page as part of the publication page count | |||
| 100 Gloss Text | ||||
| 100 Text | ||||
| 10pt C1S Cover | ||||
| 10pt C2S Cover | ||||
| 10pt C2S Text | ||||
| 10pt Text Stock | ||||
| 110 White Index | ||||
| 12pt C1S Cover | ||||
| 20 White Opaque Bond | ||||
| 50 Colored Offset | ||||
| 50 White Offset | ||||
| 50 White Opaque | ||||
| 60 Cover Stock | ||||
| 60 White Offset | ||||
| 80 Gloss Cover | ||||
| 80 Gloss Text | ||||
| 8pt C1S White | ||||
| 90 White Index | ||||
| CoverText Ink | ||||
| Black | ||||
| Black + 1 PMS color | Type in PMS color | |||
| Black + 2 PMS colors | Type in PMS colors | |||
| 4 color | ||||
| 4 color over black | ||||
| 4 color + 1 PMS color | Type in PMS color | |||
| 4 color over black + 1 PMS color | Type in PMS color | |||
| 4 color + 2 PMS colors | Type in PMS colors | |||
| 4 color + aqueous | ||||
| 4 color + varnish |
