Licensing Deep Dive March Matthias Faeh Sales area engineer

Transcription

1 Licensing Deep Dive March 2011 Matthias Faeh Sales area engineer

2 Goals of this presentation We presume you are already familiar with general WW licensing principles and products This webex is short and only covers several frequent license questions and configurations

3 What we will cover today is: Server based offerings System Platform Information Server Historian (Historian Server & Information Server) Client based offerings InTouch/InTouch for System Platform clients Information Server clients Active Factory clients

4 Existing InTouch Runtimes Q: I have some existing InTouch Runtimes and Factory Focus 9.5 and/or 10.0 nodes. How do I license them to connect to my new System Platform Galaxy? A: Purchase an AS Platform for each existing node. Can run InTouch 9.5 in a 3.0 Galaxy, but recommend upgrading InTouch to 10.0 to take advantage of new features (Configuration, however, must be done using components that are at the same version level. For example, you cannot use the Galaxy Browser in InTouch on a non-upgraded node to view or select attributes from an upgraded Galaxy. You can, though, view or modify run-time data using an InTouch window or the Object Viewer.) A: Purchase a Platform and version/functional upgrade InTouch RT to InTouch for SP10.0 May continue to use the InTouch RT license until application is fully evolved to System Platform Requires re-engineering of application

5 Platforms

6 Platforms Basic Rules An Application Server Platform is required when: A computer is hosting or accessing any Object within the executing Galaxy. An Application Server Session is required when: A terminal services session is accessing any Object within the executing Galaxy.

7 Platforms what is it? An Application Server Platform/Session Is the license to interact & communicate within a single Galaxy Provides access to the global Galaxy name space Allows deployment of objects to a node Allows Objects to work on those nodes AS Session is same function as AS Platform but for InTouch Terminal Services clients

8 Platforms required for? Nodes that require an AS Platform/Session GR (Galaxy Repository stores your Applications and Objects) Terminal Server (and each TSE client requires an AS Session license) Any node hosting or accessing an Object (including DIObject) AOS (Automation Object Server, where on-line Objects reside) Information Server SCADAlarm MES / Performance Software and Operations Software Dev Studio To connect to Galaxy and interact with and test Objects. (See Dev Studio Special Case)

9 Products that include a Platform? System Platform (# of included Platforms depends on size) InT4SP InT4SP TSE (includes a Session same function as a Platform but on TSE) Historian Server (as an add-on to System Platform) Information Server (as an add-on to System Platform) So most products that require a Platform can be purchased including one A platform includes a WWCAL and MSCAL!

10 Platforms- not required when? Nodes that do not need a Platform Any node that is not hosting or accessing any Object within the executing Galaxy. Stand-alone InTouch not accessing any Object within the executing Galaxy. Published InTouch not accessing any Object within the executing Galaxy. DAServer only installed on a node with no Objects running on that node. Just a point of data entry objects will be running in a separate AOS node. Active Factory (alone, not as part of InT4SPw/Trend) Information Server Client

11 Platforms Dev Studios For a Dev Studio node to connect to a Galaxy and interact with and test Objects (Object Viewer/WindowViewer), a Platform must be allocated to the Dev Studio node. This consumes one Platform in the GR. If this Platform allocation exceeds the number of licensed Platforms for the GR, a warning message will display. However, engineers should ignore warnings that arise from the need to allocate a Platform to the Wonderware Dev node for interacting and testing purposes. WW will be changing this in a future release so warnings will not need to be ignored. Note: Without a Platform, a Dev Studio can create, edit, deploy, and delete Objects, but cannot interact with or test Objects in the Galaxy using the Object Viewer or WindowViewer.

12 Platforms Nodes that should have a Platform? Benefits of a Platform on a Historian database With a Platform on a Historian database you can display and monitor system health including CPU, disk and memory and alarm when needed. Use the Platform to display ArchestrA graphic for viewing Historian health. You can run the Alarm Logger on the Historian node For high availability History data and Alarm data (Using 2 Historians, each with Alarm Logger and a Platform, See High Availability History configuration example) Another, though less robust alarm redundancy, is to have the Alarm Logger running in an AOS node, separate from the Historian node. Alarm Logger has a small cache to temporarily store alarms. So if the Historian Server node goes down, the Alarm Logger will continue to run and cache alarm data until the Historian node comes back on line (or until cache is full). Platform for Historian database is recommended (but not necessary)

13 CALs

14 Client Access License (CAL) What s a CAL? A CAL is not a software product It is a paper license that gives a user the right to access the services of a database server. Purpose of CALs? To license the connection to a database Server WW Historian Server (WWCAL) Information Server (WWCAL) MS SQL Server (MSCAL) A client always needs a WWCAL when connecting to a WW Historian and always needs a MSCAL when connecting to a MSSQL database.

15 Client Access License (CAL) 4 Types of WW CAL with MS CAL WW Basic CAL for per device, per user, per seat WW Basic CAL per processor WW Enterprise CAL for per device, per user, per seat WW Enterprise CAL per processor Same 4 types but without MS CAL

16 CALs when needed? Active Factory or InTouch to connect to Historian Server IS Standard and Advanced Client to connect to Information Server Any node (WW node or third party software) connecting to Historian Server or MS SQL Server InTouch, Active Factory, Info Svr Client InBatch Server InTrack Server An AS Platform includes WWCAL and MSCAL

17 CALs Products that include a WWCAL/MSCAL (most of these include WWCAL because they are sold with a Platform which includes a WWCAL & MSCAL) System Platform (# Platforms depends on SP size) InT4SP InT4SP TSE (includes a Session same function as a Platform but on TSE) Historian Server Information Server Information Server Clients (Per User, Per Device, but not PerServer/Concurrent) Active Factory clients do not include a CAL, purchase CAL separately!

18 Enterprise CALs? Enterprise CAL is used when connecting to a MS SQL Server Enterprise edition. Enterprise CALs can be: Per Device, Per User, Per Seat Per Processor

19 InTouch TSE

20 InTouch RT & InT4SP TSE Order and install an InTouch TSE license file (soft license) on each Terminal Server (could have multiple servers for redundancy) This enables one TS Client session (either for client or Console on TS server) TSE Part Number ends in T for soft license file on the TS server T License must license enough tags for largest tag count app the server will run T License must be with IO if terminal server will run IOServers (most will) T License must be InT4SP with Trend if any clients require Trend Cannot mix Read-only with read/write on the TS server. If T License is Read-only, then all clients on that TS server must be Read-only. Use separate TS server for Read-only clients.

21 InTouch RT & InT4SP TSE Order an InTouch TSE license (paper license) for each additional TSE Client TSE Part Number ends in TP This licenses one additional TS Client session This is a paper license and does not need IO (TS server acts as IO Server) Till 10.0, session count (# of sessions actually running) is NOT enforced with license file, but from 10.1 TSE sessions are enforced. Customers can unknowingly become illegal if you do not help them. Each InT4SP includes a Platform which includes a WW Basic CAL and a Microsoft CAL. But for TS you also need a Microsoft TS CAL for each TS client.

22 InTouch TSE (Terminal Services Environment) For Terminal Services, there is just one product software installed and one license file installed on the TS server The TP paper license is for each additional TS client session Make sure the T license file on the TS server Licenses enough tags for largest tag count app the server will run Has IO, if needed. Currently, you can t mix PerNamed Device, Per Named User, and Concurrent licenses

23 Active Factory

24 Active Factory v10 Server based licensing Uses the License Manager License is installed on one node for use by many clients Per Named Device allows specific named Devices connection to any Historian database using one session Per Named User allows specific named Users connection to any Historian database using one session Per Server/Concurrent allows connection to one Historian database using one session

25 Active Factory Active Factory v9.2 and beyond uses the new ArchestrA server based license model (ArchestrAServer.lic) and supports terminal services. This includes: Per Named Device (Computer network name in TS environment) Per Named User Per Server/Concurrent Do not use Active Factory Per Device for terminal services applications. (AF Per Device uses the ArchestrA.lic license file) The Active Factory ArchestrAServer.lic license file (Per Named Device, Per Named User, and Per Server/Concurrent) is installed on a license server (usually the Historian database node or a dedicated License server) and can be used by a terminal server to allow a TSE client to start an Active Factory session.

26 Active Factory You can mix PerNamed Device, Per Named User, and Per Server Concurrent Active Factory licenses. Server License Manager will handle that. Example: Want 1 Supervisor to always be able to connect high priority access (Per Named User ) and want 10 devices to be able to casually connect periodically low priority access (Per Server/Concurrent) WW Basic CAL is needed by every instance of Active Factory running on a PC or in a terminal services session.

27 Which License Type to use? Situation Lic Type Value Few nodes Local or Per Device Easy Managemet, Dedicated, High Availability Many Nodes a few Specific Users Many Users on several Specific Nodes Many Casual Users on many Nodes Server Based - Per Named User Server Based - Per Named Device Server Based - Per Server/Concurrent Central Managebility, Cost effective Central Managebility, Cost effective Central Managebility, Cost effective

28 System Platform

29 System Platform License Set All the products delivered as part of a System Platform License are tied together and can only be used within a single Application Server (AS) Galaxy. 1 System Platform license set Application Server with # I/O and # AS Platforms (GR) Historian Server with _#_ Tags Device Integration Servers Information Server portal 1 System Platform License Certificate paper documenting the license set above and documents paper licenses such as WW Basic CALs, MS SQL CALs, AS Platform TSE Sessions

30 System Platform Sizing Terms What s the difference between Galaxy IO, InTouch Tags, and History Tags? Galaxy IO are the IO that are connected through any Device Integration Object in a Galaxy Galaxy IO are the sum of all individual data values moving through all DIObjects DIObject is the only Object that can access real time data outside of the Galaxy e.g. from a DAServer InTouch Tags are internal to an InTouch or InTouch for System Platform application (do not count towards total Galaxy IO) History Tags are the number of individual data items you want to store in the Historian database

31 SP Sizing - IO needed InTouch Only system: InTouch Tags are consumed for data IO plus other attributes like calculation results, averages, etc. So it is sometimes difficult to figure out how many Tags are necessary for an application. System Platform system: Galaxy IO are counted as the number of IO configured in DIObjects which could be coming from an OPCserver, IOServer, Proxy Object, DAServer, FSGateway or any external data source. So it is simpler to determine the total number of Galaxy IO needed to size the System Platform. How many data IO are you using? Experience has shown that an SP application uses about 70% as many Galaxy IO as an InTouch Tag based application. Example: IT Tag based app uses 1000 Tags, SP app would use about 700 IO. This is because UDAs are not counted in the same way as InTouch Tags

32 What s a Galaxy Repository (GR)? Uses ArchestrA technology and is the central database containing all persistent configuration information such as : Objects and Applications for the entire network of ArchestrA-enabled nodes. InTouch view client applications Security settings Objects do not run in Production in the GR. Objects run on AOS nodes. GR is sized by Galaxy I/O count. Best Practices is to have the GR on-line at all times in Production!

33 GR Node and Platform Best Practices GR Node should run on-line as part of the Production Galaxy On-line GR requires an AS Platform User log-on is stored in GR so GR needs to be on-line for first time user log on authentication; Security reasons On small systems, GR is typically on the same node as one of your other Server nodes (in this order of preference): AOS node Information Server Historian Server (though not recommended, performance issues) GR is not CPU intensive most of the time. But can be during deployment or heavy object development work! On large systems, >25K IO, GR should be on a separate node, with AS Platform, best practices.

34 Development Studio

35 System Platform/Dev Studio/GR Can I run my Dev Studios separately from my GR node and why? Yes, typically run the GR separately or on one of the System Platform Servers (AOS, Information Server) Dev and GR nodes can be in different locations Multiple Dev nodes (TSE) Centralized MS SQL Server Can use RDP remote connection (low bandwidth) Q: Can I run my Dev Studio and my GR on the same node and why would I? Yes, large System Platforms typically have a separate on-line node containing the GR with a dedicated Dev Studio and a second separate off-line Dev Studio.

36 System Platform Q: Where do I run my Application Objects Wherever there is a Platform In small systems, Objects can be on any node with a Platform In large systems, usually have dedicated AOS nodes to host Objects Q: Where do I store/engineer my Application Objects? A: GR Node Q: How many AOS nodes do I need? (extra Platforms) A: Depends on how many objects/engines/historization, scan rates, etc.. Q: Can I run my Application Objects on my Historian node, InfoSvr node, GR node, InT4SP nodes? A: Yes

37 Need more Platforms? I m adding more nodes to my existing system and need more AS Platforms, what do I order, receive, and why? The System Platform Application Server license file licenses the # of Production Platforms Platform_Count feature line Our current licensing does not enable incrementing (adding more Platforms to an existing license file) So, you order more Platforms and provide Serial# of the existing AppSvr license file. WW will regenerate and you will receive a new Application Server license file with the new total # of Platforms Customer destroys old license file. New License file Serial Number sequence is incremented )

38 SP Device Integration Licensing Device Integration licensing for System Platform is offered four ways: DAServer DIObjects Objects come with Application Server Objects that encapsulate a DAServer software Require a Platform and DI Server license DIObjects Objects come with Application Server Objects that enable connection to other IO sources Nodes running the DIObjects but not running a DAServer require a Platform, do not require a DI Server license DAServers Require a DI Server license FSGateway DAServer Does not require a Platform or a DI Server license

39 FSGateway DAServer Does not require a Platform or a DI Server license FS Gateway allows Windows application programs access to data from a variety of data sources. FS Gateway is a Microsoft Windows application program that acts as a communications protocol converter. It was built with the ArchestrA DAS Toolkit. FS Gateway can be used to link clients and data sources that communicate using different data access protocols.

40 InTouch for System Platform InTouch for System Platform (InTouchView) is only a client to a System Platform Application Server. When creating the InT4SP application, check the View application checkbox in WindowMaker This assigns certain functionality specific to InTouch for System Platform InT4SP does everything InTouch does except: Cannot use any other access name but Galaxy: Can not directly access anything outside of the Galaxy. Cannot be an alarm provider (no alarm generation) Attributes of Objects are how alarms are implemented in System Platform Cannot log data to InTouch local History Cannot act as a Tag Server

41 InTouch for System Platform (InT4SP) InT4SP w/ Trend The Trend is an Active Factory Per Device license InT4SP w/ Trend TSE The Trend is an Active Factory Per Named Device license Typically Install the Active Factory license on the Terminal Server or the Historian Server. It uses the Server based License Manager.

42 InTouch for System Platform InT4SP w/ Trend TSE Example Order 5 InT4SP w/ Trend TSE Receive: One InT4SP TSE T license files (wwsuite.lic), enabling InTouch for System Platform, runs on the Terminal Server, and receive four TP paper licenses. One Active Factory Per Named Device license file (ArchestrAServer.lic),enabling five Active Factory Per Named Device Sessions. The one license file is installed on one node along with the License Manager software. This licensing is due to combining the old type of licensing (wwsuite.lic for InTouch) with the new type of server based licensing (ArchestrAServer.lic) for Active Factory.

43 Information Server & Clients

44 Information Server and Clients Q: What s the difference between InfoSvr Standard and Advanced Clients? The Standard level provide web access to: published ActiveFactory Trends and Workbooks, Microsoft SQL Server 2005 Reporting Services integration, SmartSymbol integration, Web Part integration, Table Weaver displays basic InTouch process graphic screens (without InTouch Write Back capability). The Advanced level provide the same capabilities as the Standard level plus InTouch Write Back, InBatch and QI Analyst integration. Write back capability means the operator is able to interact with application.

45 Information Server and Clients Can I mix PerNamed Device, Per Named User, and Per Server Concurrent InfoSvr Clients on the same server? Yes, the Server License Manager will handle that. Can I mix InfoSvr Standard with Advanced licenses on the same server? No, Write-back capability is Server enabled for all clients connected to that server. All IS client licenses on a server must be same type, either all Standard or all Advanced clients, you cannot mix. To have both types of clients, the Customer must deploy 2 separate Information Servers. VMWare may be a viable solution to reduce the hardware requirements.

46 Information Server and Clients An InfoSvr Client includes an AF trend plot (for viewing a Trend published on the IS portal). But to Publish a Trend or Workbook (push it to an InfoSvr Portal), you need an Active Factory Trend Client license.

47 Industrial Computer Licensing

48 Industrial Computer licensing? Touch Panels, BoxPC, and OIC panels Standard License file is pre-installed on computer at WW. License file is locked to the computer MAC address. Can order functional upgrade license files for more tags Thin Client Computers Thin client T license runs on a TS server, not on the panel. So not locked to a MAC address. Thin client TP licenses are paper. Compact Panels License file is pre-installed on computer at WW. License is specific to the Compact Panel hardware and can only be used on our panels.

49 MES/EMI

50 Typical Filling Line So how many pieces of Equipment is this? IT DEPENDS...

51 Depends On What? Definition of Equipment WHERE : Something you can touch (small process lower # of equipment lower value) (large process higher # of equipment higher value) HOW : information used by features a given software component (you can have large IO in System Platform even with low Equipment count for modules) WHAT : does the customer really want to know (aka what is the resolution of data the customer needs when looking at reports)

52 Back to the Filling Line Ex. #1 REQUIREMENTS Utilization of filler EQUIPMENT COUNT 1

53 Back to the Filling Line Ex. #2 REQUIREMENTS Utilization of filler + OEE for filler + Downtimes of labeler + Downtimes of cartoner EQUIPMENT COUNT 3

54 Back to the Filling Line Ex. #3 REQUIREMENTS Utilization of filler OEE for filler Downtimes of labeler Downtimes of cartoner + OEE for line EQUIPMENT COUNT 4

55 Merci