ControlNet Network Configuration (Publication CNET-UM001H-EN-P)
ControlNet NetworkConfiguration1756 ControlLogix, 1756 GuardLogix, 1769 CompactLogix,1769 Compact GuardLogix, 1789 SoftLogix, Studio 5000Logix EmulateRockwell Automation Publication CNET-UM001H-EN-P - March 2022Supersedes Publication CNET-UM001G-EN-P - September 2020User ManualOriginal Instructions
ControlNet Network ConfigurationImportant User InformationRead this document and the documents listed in the additional resources section about installation, configuration, andoperation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarizethemselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required tobe carried out by suitably trained personnel in accordance with applicable code of practice.If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may beimpaired.In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the useor application of this equipment.The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables andrequirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability foractual 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 softwaredescribed in this manual.Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., isprohibited.Throughout this manual, when necessary, we use notes to make you aware of safety considerations.WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injuryor death, property damage, or economic loss.ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentionshelp you identify a hazard, avoid a hazard, and recognize the consequence.IMPORTANT Identifies information that is critical for successful application and understanding of the product.Labels may also be on or inside the equipment to provide specific precautions.SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will causesevere injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for PersonalProtective Equipment (PPE).Rockwell Automation recognizes that some of the terms that are currently used in our industry and in this publication are not inalignment with the movement toward inclusive language in technology. We are proactively collaborating with industry peers tofind alternatives to such terms and making changes to our products and content. Please excuse the use of such terms in ourcontent while we implement these changes.2Rockwell Automation Publication CNET-UM001H-EN-P - March 2022
Summary of ChangesThis manual includes new and updated information. Use these referencetables to locate changed information.Grammatical and editorial style changes are not included in this summary.Global changesThis table identifies changes that apply to all information about a subject inthe manual and the reason for the change. For example, the addition of newsupported hardware, a software design change, or additional referencematerial would result in changes to all of the topics that deal with that subject.SubjectReasonUpdated the Legal notices.Legal information changed.New or enhanced featuresNone in this release.Rockwell Automation Publication CNET-UM001H-EN-P - March 20223
Table of ContentsSummary of ChangesPrefaceStudio 5000 environment . 9Additional Resources . 10Legal Notices . 10Chapter 1ControlNet OverviewUse ControlNet Communication Modules in a Control System. 11Bridge Across Networks . 12Exchange Information on a ControlNet Network . 15Network Update Time (NUT) . 16Requested Packet Interval (RPI) . 17Actual Packet Interval (API) . 18Understand the Effect of the NUT on the API . 18Schedule the Network . 18Control of Scheduled I/O. 19Understand the Network Keeper . 19Default Parameters . 20ControlNet Network Capacity and Topology . 21Topology . 21Number of Nodes .23Lengths.23Chapter 2Connect a Computer to theControlNet NetworkConfigure the ControlNet Communication Driver in RSLinx ClassicSoftware . 25Configure a ControlNet ModuleChapter 3Use Logix Designer Application . 27Configure the I/O Configuration Tree in Your Project . 27Add and Configure a Local ControlNet Module . 27Add and Configure a Remote ControlNet Module . 31Communication Format. 33Download the Project to the Logix 5000 Controller . 35Electronic Keying .36Exact Match . 37Compatible Keying . 38Disabled Keying . 40Use RSNetWorx for ControlNet Software. 41Schedule a ControlNet Network for the First Time. 41Schedule the Network Offline . 42Schedule the Network Online . 46Rockwell Automation Publication CNET-UM001H-EN-P - March 20225
Table of ContentsReschedule a ControlNet Network that has Previously beenScheduled. 50Control I/OProduce and Consume Tags(interlock controllers)Messaging6Chapter 4Set Up the Hardware . 53Requested Packet Interval (RPI) . 54Communication Format .54Direct or Rack-optimized Connections.55Direct Connections for I/O Modules .56Rack-optimized Connections for I/O Modules . 57Ownership . 58Choose the Type of Ownership for a Module .59Add a Remote Adapter .59Add Distributed I/O . 60Distributed I/O Communication Formats . 61Access Distributed I/O . 62Validate Connections . 64Chapter 5Terminology . 67Set Up the Hardware . 67Determine Connections for Produced and Consumed Tags . 68Organize Tags for Produced or Consumed Data . 70Adjust for Bandwidth Limitations . 70Produce a Tag. 71Consume a Tag .74Chapter 6Set Up the Hardware . 79Guidelines for MSG Instructions . 80Determine Connections for Messages. 81Guidelines for Caching Message Connections . 81Enter Message Logic . 81Add the ControlNet Modules and Remote Devices to the LocalController’s I/O Configuration . 81Enter a Message . 82Configure a Message Instruction. 82Stagger the Messages . 84Rockwell Automation Publication CNET-UM001H-EN-P - March 2022
Table of ContentsCommunicate with PanelViewTerminalsIndexChapter 7Set Up the Hardware . 85Determine Connections to PanelView Terminals . 86Add a PanelView Terminal . 86Organize Controller Data for a PanelView Terminal . 90Rockwell Automation Publication CNET-UM001H-EN-P - March 20227
PrefaceThis manual describes how you can use ControlNet communication moduleswith your Logix 5000 controller.Use this manual if you program applications that use a ControlNet networkwith one of these Logix 5000 controllers: CompactLogix controllerControlLogix controllerPowerFlex 700S with DriveLogix controllerSoftLogix5800 controllerAlso be familiar with the following: Studio 5000 environmentNetworking conceptsLogix Designer softwareFactoryTalk Linx or RSLinx Classic softwareRSNetWorx for ControlNet softwareRockwell Automation recognizes that some of the terms that are currentlyused in our industry and in this publication are not in alignment with themovement toward inclusive language in technology. We are proactivelycollaborating with industry peers to find alternatives to such terms andmaking changes to our products and content. Please excuse the use of suchterms in our content while we implement these changes.The Studio 5000 Automation Engineering & Design Environment combinesengineering and design elements into a common environment. The firstelement is the Studio 5000 Logix Designer application. The Logix Designerapplication is the rebranding of RSLogix 5000 software and will continue tobe the product to program Logix 5000 controllers for discrete, process,batch, motion, safety, and drive-based solutions.The Studio 5000 environment is the foundation for the future ofRockwell Automation engineering design tools and capabilities. The StudioRockwell Automation Publication CNET-UM001H-EN-P - March 20229
Preface5000 environment is the one place for design engineers to develop allelements of their control system.Additional ResourcesThese documents contain additional information concerning relatedproducts from Rockwell Automation.ResourceDescriptionControlNet Modules Installation Instructions,publication CNET-IN005Industrial Automation Wiring and GroundingGuidelines, publication 1770-4.1Describes how to install 1756-CN2, 1756-CN2R, 1756-CN2RXT,1756-CNB, 1756-CNBR, 1768-CNB, and 1768-CNBR ControlNetmodules.Provides general guidelines for installing a RockwellAutomation industrial system.Product Certifications website,http://www.ab.comProvides declarations of conformity, certificates, and othercertification details.You can view or download publications athttp://www.rockwellautomation.com/literature. To order paper copies oftechnical documentation, contact your local Rockwell Automation distributoror sales representative.Legal NoticesRockwell Automation publishes legal notices, such as privacy policies, licenseagreements, trademark disclosures, and other terms and conditions on theLegal Notices page of the Rockwell Automation website.End User License Agreement (EULA)You can view the Rockwell Automation End-User License Agreement ("EULA")by opening the License.rtf file located in your product's install folder on yourhard drive.Open Source LicensesThe software included in this product contains copyrighted software that islicensed under one or more open source licenses. Copies of those licenses areincluded with the software. Corresponding Source code for open sourcepackages included in this product are located at their respective web site(s).Alternately, obtain complete Corresponding Source code by contactingRockwell Automation via the Contact form on the Rockwell m/global/about-us/contact/contact.pagePlease include "Open Source" as part of the request text.A full list of all open source software used in this product and theircorresponding licenses can be found in the OPENSOURCE folder. The defaultinstalled location of these licenses is C:\Program Files (x86)\CommonFiles\Rockwell\Help\ Product Name \ReleaseNotes\OPENSOURCE\index.htm.10Rockwell Automation Publication CNET-UM001H-EN-P - March 2022
Chapter 1ControlNet OverviewThe ControlNet network provides high-speed transmission of time-criticalI/O and interlocking data and messaging data. This data transfer capabilityenhances I/O performance and peer-to-peer communication in any system orapplication.The ControlNet network is highly deterministic and repeatable and remainsunaffected as devices are connected or disconnected from it. This ensuresdependable, synchronized, and coordinated real-time performance.The ControlNet network is most often used in these ways: As the default network for the ControlLogix platform As a backbone to multiple distributed DeviceNet networks As a peer interlocking networkThis chapter describes how you can use ControlNet modules in a networkcontrol system.Use ControlNetCommunication Modules ina Control SystemTopicPageUse ControlNet Communication Modules in a Control System on page 119 on page 11Bridge Across Networks on page 12Exchange Information on a ControlNet Network on page 15ControlNet Network Capacity and Topology on page 2111 on page 1214 on page 1521 on page 21You can fit various ControlNet modules into your control system.Figure 1 on page 10 shows the following: The controllers produce and consume tags among themselves. The controllers initiate MSG instructions that send/receive data orconfigure devices. The computer uploads and downloads projects to the controllers. The computer configures devices on the ControlNet network andconfigures the network itself.Rockwell Automation Publication CNET-UM001H-EN-P - March 202211
Chapter 1ControlNet OverviewFigure 1 - ControlNet Modules and the Control System OverviewItemDescription1Personal computer running SoftLogix5800 controller with 1784-PCICS card23456781756-CNB module (as an adapter) with 1756 I/O modulesPowerFlex 700S drive1794-ACN15 adapter with 1794 I/O modules1734-ACNR adapter with 1734 I/O modulesPanelView terminalCompactLogix 1769-L35CR controller with local 1769 I/O modulesControlLogix controller with 1756-CN2, 1756-CN2R, 1756-CNB, or 1756-CNBR module as the scannerIMPORTANT For an enhanced redundancy system, you must use a 1756-CNB,1756-CNBR, 1756-CN2 series B, or 1756-CN2R series B communication module. The 1756-CN2or 1756-CN2R series A module does not support enhanced redundancy. For moreinformation, refer to the ControlLogix Enhanced Redundancy System User Manual,publication 1756-UM535.Bridge Across Networks12Some ControlNet modules support the ability to bridge or routecommunication to and from different networks, depending on thecapabilities of the platform and communication devices.Rockwell Automation Publication CNET-UM001H-EN-P - March 2022
Chapter 1ControlNet OverviewIMPORTANT You can only bridge across networks to communicate with devices. You cannot bridgeacross networks to control I/O, even though Logix Designer software can accept such aconfiguration in the I/O Configuration folder. All I/O control must originate and end on thesame physical network.The following table describes how communication can bridge acrossnetworks.Table 1 - Bridging Across NetworksA device on this networkCan communicate with a device on this esYesNoYes(2)YesYesYesYesNoYesIn Figure 2, a workstation configures a drive on the DeviceNet network. Theworkstation bridges from the ControlNet network to the DeviceNet networkto reach the drive. The bridge is a ControLogix chassis with ControlNet andDeviceNet modules.Figure 2 - Drive Configuration on a DeviceNet ivePanelView terminalDeviceNet networkBridgeControlNet networkIMPORTANT The performance of a CompactLogix controller on a ControlNet network degradessignificantly if you use the controller as a bridge. Target bridging over a CompactLogixcontroller on a ControlNet network toward applications that are not real-time dependent,such as Logix Designer software program downloads.In the example shown above, you can transfer messages from the DeviceNetnetwork through the Logix 5000 controller to an RSView32 operator interface.Rockwell Automation Publication CNET-UM001H-EN-P - March 202213
Chapter 1ControlNet OverviewWith a CompactLogix controller as a bridge, you can map the data into theDeviceNet I/O image and then use RSLinx OPC to send the data to the Logix5000 controller over the ControlNet network. This method conserves thelimited bridging resources of your CompactLogix controller.The following example shows how a DeviceNet bridge links to an EtherNet/IPnetwork in RSLinx Classic software.Figure 3 - EtherNet/IP Bridge Linking to a ControlNet NetworkItemDescriptionItemDescriptionEtherNet/IP networkControlNet Bridge in 1756 systemEtherNet/IP bridge in 1756 systemControlNet networkThe following tables list the possible bridges between communicationnetworks. Note that you can bridge from a ControlNet network to an Ethernetnetwork and from an Ethernet network to a ControlNet via a SoftLogix virtualchassis. However, the products and methods you must use to do so are moredetailed than can be effectively described in the following tables. For moreinformation on how to bridge from one network to another via a SoftLogixvirtual chassis, see the SoftLogix5800 System User Manual, publication1789-UM002.Table 2 - Bridges from a ControlNet Network14DestinationNetworkModules for a 1768 CompactLogix SystemModules for a 1769 CompactLogix SystemModules for a ControlLogix ChassisDeviceNet 1768-L43 or 1768-L45 controller 1768-CNB(R) module 1769-SDN scanner 1769-L32C or 1769-L35CR controller 1769-SDN scanner or 1788-CN2DN module(1) Rockwell Automation Publication CNET-UM001H-EN-P - March 20221756-CN2 module1756-CN2R module1756-CNB module1756-CNBR module1756-DNB module
Chapter 1ControlNet OverviewDestinationNetworkModules for a 1768 CompactLogix SystemModules for a 1769 CompactLogix SystemModules for a ControlLogix ChassisEtherNet/IP 1768-L43 or 1768-L45 controller 1768-CNB(R) module 1768-ENBT moduleNot applicable 1756-CN2 module1756-CN2R module1756-CNB module1756-CNBR module1756-ENBT module1756-EN2T module1756-EN2TR module1756-EN3TR moduleTable 3 - Bridges from an EtherNet/IP NetworkDestinationNetworkModules for a 1768CompactLogix SystemModules for a 1769CompactLogix SystemModules for a ControlLogixChassisControlNet 1768-L43 or 1768-L45 controller 1768-ENBT module 1768-CNB(R) moduleNot applicableDeviceNet 1768-L43 or 1768-L45 controller 1768-ENBT module 1769-SDN scanner 1769-L32E or 1769-L35E controller 1769-SDN scanner or 1788-EN2DNmodule(1) Exchange Information on aControlNet Network1756-CN2 module1756-CN2R module1756-CNB module1756-CNBR module1756-ENBT module1756-EN2T module1756-EN2TR module1756-EN3TR module1756-DNB module1756-ENBT module1756-EN2T module1756-EN2TR module1756-EN3TR moduleModules for a 1769CompactLogix PackagedController SystemNot applicable 1769-L23E-QB1B controller1769-L23E-QBFC1B controller1769-L23-QBFC1B controller1769-SDN scannerControlNet communication modules use a message-based protocol thatimplements a relative path to send a message from the producing module in asystem to the consuming modules. This protocol also lets you communicatebetween devices on a ControlNet, DeviceNet, or EtherNet/IP network withoutwriting additional application code.With unscheduled data, the device from which a message originates, such as aLogix 5000 controller, contains the path information that makes sure themessage reaches its consumers.For a full explanation of unscheduled and scheduled data, see NetworkUpdate Time (NUT) on page 16 on page 16.Because the producing module holds this information, other modules alongthe path simply pass the information along and do not need to store it. Thesignificant benefits include the following: You do not need to configure routing tables in the bridging module,which greatly simplifies maintenance and module replacement. You maintain full control over the route taken by each message, whichenables you to select alternative paths for the same end module.Scheduled data in Logix-based systems use the producer/consumernetworking model instead of a source/destination (master/slave) model. TheRockwell Automation Publication CNET-UM001H-EN-P - March 202215
Chapter 1ControlNet Overviewproducer/consumer model reduces network traffic and increasestransmission speed.In traditional I/O systems, controllers poll input modules to obtain their inputstatus. In a Logix system, digital input modules are not polled by a controller.Instead, they produce (multicast) their data either upon a change of state(COS) or periodically. The frequency of update depends upon the optionschosen during configuration and where on the network the input moduleresides. The input module, therefore, is a producer of input data and thecontroller is a consumer of the data.The controller can also produce data for other controllers to consume. Theproduced and consumed data is accessible by multiple controllers over theLogix backplane and the ControlNet network. This data exchange conforms tothe producer/consumer model.A ControlNet network link’s most important function is to transporttime-critical control information, such as I/O data and control interlocking.Other information that is not time-critical, such as program uploads anddownloads, is also transported but does not interfere with time-criticalmessages because a ControlNet network can transmit scheduled andunscheduled data.On a ControlNet network link, nodes transfer information by establishingconnections. Each message sent by a producer contains a Connection ID(CID). Nodes that have been configured to recognize the CID consume themessage, becoming consumers themselves.Media access to the network is controlled by a time-slice access algorithm,Concurrent Time Domain Multiple Access (CTDMA), which regulates a node’sopportunity to transmit in each network update interval (NUI). You configurehow often the NUI repeats by selecting a network update time (NUT) inmilliseconds.Network Update Time (NUT)The network update time (NUT) is the shortest interval in which data can besent on a ControlNet network. It represents the fastest possible update ratefor scheduled data transfers on that network. For example, a network thatruns with a five ms NUT cannot send scheduled data at a rate faster than fivems. It can, however, send data at a slower rate. The minimum NUT you canspecify is two ms. The NUT is divided into a three-part structure.Table 4 - NUT Structure16Parts of NUTFunctionsScheduledOn a sequential, rotating basis, every scheduled node can transmit data once per NUT.Time-critical information is sent during this part of the interval.Rockwell Automation Publication CNET-UM001H-EN-P - March 2022
Chapter 1ControlNet OverviewParts of NUTFunctionsUnscheduledAll nodes transmit on a sequential, rotating basis, the rotation repeating itself until the time allotted for this portion is used up.The number of scheduled transmissions determines the time available for unscheduled transmissions. On a ControlNet network, at least onenode can transmit unscheduled data every NUT.Information that can be delivered without time constraints is sent during this part of the interval.MaintenanceThe node with the lowest address transmits information to keep the other nodes synchronized. This time is automatically subtracted from yourNUT. However, the time required for network maintenance is brief (microseconds) when compared to that used for the scheduled andunscheduled portions of the NUT.Figure 4 - NUT StructureItemDescriptionBoundary moves according to scheduled traffic loadUnscheduled trafficNetwork maintenanceScheduled traffic. Each device transmits only onceStartRequested Packet Interval(RPI)The RPI is the update rate specified for a particular piece of data on thenetwork. By using a rack-optimized connection, the RPI can specify the ratefor an entire rack of I/O. With a direct connection, the RPI can specify therate for a particular module or peer-to-peer data. When you add a module tothe I/O configuration of a controller, you must configure the RPI, specifyinghow often to produce data for that module. For example, if you specify an RPIof 50 ms, every 50 ms the I/O module sends its data to the controller or thecontroller sends its data to the I/O module.Set the RPI only as fast as needed by the application. The RPI also determinesthe number of packets per second that the module will handle on aconnection. Each module has a limit of how many packets it can handle persecond. If you exceed this limit, the module cannot open any moreconnections.A faster RPI consumes more network bandwidth. So, to avoid wastingnetwork bandwidth, set the RPI only as fast as is necessary. For example, ifRockwell Automation Publication CNET-UM001H-EN-P - March 202217
Chapter 1ControlNet Overviewyour application uses a thermocouple module that has data change every 100ms, do not set the RPI for that node at 5 ms because the network bandwidth isused to transmit mostly old data.IMPORTANT You cannot set the RPI to a rate faster than the NUT. The network cannot send data at a ratethat is faster than the NUT.When you run RSNetWorx for ControlNet software, an Actual Packet Interval(API) is calculated. The API is equal to or faster than the RPI.Actual Packet Interval (API)The API is the actual update rate for a particular piece of data on the network.A ControlNet network sets this rate equal to or faster than the RPI, based onthe binary multiple of the NUT, which is the next fastest rate at which amodule can send data. If this cannot be done, a ControlNet network providesreports that it cannot support the configuration.Understand the Effect ofthe NUT on the APIThis example illustrates how the NUT affects the API. A module on thenetwork can produce data only at binary multiples of the NUT to a maximumof the NUT multiplied by 128. These multiples are referred to as rates on aControlNet network. Therefore, with a NUT of 5 ms, the module can send dataat these rates.Table 5 - NUT Example Data RatesNUTMultipleRate at Which Module Can Send Data5 ms15 ms210 ms4816326412820 ms40 ms80 ms160 ms320 ms640 msIn this example, if you specify an RPI of 25 ms, then the network produces anAPI of 20 ms, which is the next fastest rate at which the module can send data.The module places the data on the network at every fourth network updateinterval to produce the 20 ms API. Similarly, if you specify an RPI of 150 ms,the network produces an API of 80 ms.Schedule the NetworkConnections over a ControlNet network can be one of the following: Scheduled—Data transferred at specific times. Unscheduled—Data transferred when the network can accommodatethe transfer.To use scheduled conn
Rockwell Automation Publication CNET -UM001H-EN-P - March 2022 9 Preface This manual describes how you can use ControlNet communication modules with your Logix 5000 controller. Use this manual if you program applications that use a ControlNet network with one of these Logix 5000 controllers: CompactLogix controller
Chapter 7: Set Up the Hardware . Exchange Information on a ControlNet Network . 14 . ControlNet Network Capacity and Topology . 21 . Use ControlNet Communication Modules in a Con
Feb 26, 2013 · CNET TV All Videos Apple Byte Buzz Report CNET Top 5 Loaded Prizefight More About CBS Interactive About CNET CNET Deals CNET Forums CNET Mobile CNET Site Map CNET Widgets Corrections Help Center Permissions Follow us via. Facebook LinkedIn Twitter YouTube Newsletters RSS Ads Android Market
ControlNet Cable System Planning and Installation Manual CNET-IN002 ControlNet Cable System Component List AG-PA002 DF1 Protocol and Command Set Reference Manual 1770-RM516 Industrial Automation Wiring and Grounding Guidelines 1770-4.1 PLC-5 Family Programmable Controllers Hardware Installation Manual 1785-6.6.1
Feature Lite Full Configure the communications port Yes Yes Connect to a local device using an RS-232 DF1 serial connection Yes Yes Connect to a single device via a DeviceNet or ControlNet network No Yes Connect to multiple devices on a DeviceNet or ControlNet network No Yes Monitor parameters Yes Yes Edit parameters Yes Yes
Anybus Communicator ControlNet User Manual Doc: HMSI-27-303, Rev. 3.12 Important User Information This document contains a general introduction as well as a description of the technical features provided by the Anybus Communicator, including the PC-based configuration software. The reader of this document is expected to be familiar with PLC and software design, as well as communication systems .
Documentation consulted: Allen Bradley PowerFlex 40 User Manual (Publication 22B-UM001B-EN-E), AnyBus Communicator Manual ver. 1.60 (Doc ID SDN-7061-059), AnyBus-S ControlNet Appendix Allen Bradley ControlNet Coax Cable, Taps and Terminators Appropriate Programming Cables Serial Cabling The serial interface between the Allen Bradley PowerFlex and the AnyBus Communicator is .
ControlNet-to-DeviceNet Linking Device 3 Rockwell Automation Publication 1788-IN052E-EN-P - December 2014 SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or moto
Tourism is not limited only to activities in the accommodation and hospitality sector, transportation sector and entertainment sector with visitor attractions, such as, theme parks, amusement parks, sports facilities, museums etc., but tourism and its management are closely connected to all major functions, processes and procedures that are practiced in various areas related to tourism as a .
