Running ThinManager in the Office and on the Plant Floor. Ed Hofferber, IT/Control Leprino Foods Allendale, MI

Transcription

1 Running ThinManager in the Office and on the Plant Floor Ed Hofferber, IT/Control Leprino Foods Allendale, MI

2 Who am I I m currently the IT Supervisor for Leprino Foods in Allendale and Remus MI. Been with LFC for 15 years. Providing end- user support to over 700 users and ten processing areas in two faciliqes in Michigan. With over 25 years experience in computer end user support, server configuraqon for terminal services, plant wide Cisco networking, copier/printer support, IP based cameras, and phone system support. Over 7 years working with Wonderware in a server based environment.

3 Leprino Foods Leprino Foods Company is a world leader in innovaqve dairy food ingredient manufacturing.

4 Leprino Foods The largest mozzarella producer in the world, Leprino Foods is the exclusive supplier to three of the largest pizza chains in the world and supplies nine of the top 10 frozen pizza/entrée market leaders. Leprino Foods is also the number one producer of lactose in the world and a top producer of whey protein and sweet whey.

5 Leprino Foods Leprino Foods is located: Corporate offices in Denver, Colorado Plants located in Allendale, MI Greeley, CO Two plants in the United Kingdom Singapore, ExporQng to over 40 countries Fort Morgan, CO Lemoore (East), CA Lemoore (West), CA Ravenna, NB Remus, MI Tracy, CA Roswell, NM Waverly, NY

6 Before ThinManager Prior to 2001 all of our plants were computer based or stand alone off the shelf thin clients. Over 100 devices per plant. Problems Needed to visit each computer\thin client to make updates and changes. UpdaQng Wonderware applicaqon was also a computer by computer process. Most of every day was spent on upkeep and not very much future development.

7 Started using ThinManager In 2001 our Tracy, CA plant received ThinManager with a major controls upgrade. Lemoore West was the next plant, but again with a controls upgrade It was only used in the controls environment at the beginning. Plants were up and running on ThinManager within hours, very easy to setup and get started. In 2006 Allendale started using ThinManager, once again within hours we were up and running.

8 The Next Step the Office Area The office area at this Qme was using off the shelf thin clients that were setup before they were deployed and if changes were needed, we went to the area to make changes. With very liele fail over, problems caused immediate acqon, stopping all work in process. Only two employees in the plant knew how to make changes. This took a lot of manpower. In 2010 we were upgraded to a enterprise license in most plants, as part of a controls upgrade to MES.

9 The Next Step the Office Area In that same year, the office side was being upgraded to SAP and we found that our off the shelf thin clients were inadequate. A test was setup using a ACP compliant thin clients. I added the office servers, new groups, modules needed to the groups, and 10 test device to ThinManager in a few minutes. In the training area, I had end users run SAP transacqons on both the off the shelf thin client and ACP compliant thin client.

10 Results Every transacqon in SAP was faster on the ACP thin client. Seconds vs. Minutes. We also found that MS Office 2007 performed beeer as well as our E- mail program. I then recommended moving all our office thin clients to ACP compliant thin clients, with the following as my reasoning.

11 Reason Why Cost for an off the shelf thin client that would perform the same was higher or the same. I already had the licenses to add more to ThinManager. I can view status of all thin clients in the plant from one plagorm, allowing IT and Controls to cross train on both controls and office. ConfiguraQon changes can be made from desk real Qme. Fast easy replacement of a thin client by Maintenance staff Remote end user support.

12 Moving Forward Gehng no arguments to move forward from Management or IT we started replacing thin clients. Changing out the thin clients was easy as staging them in ThinManager, and swapping them out on the floor/ office. Any issues in the first configuraqon were fixed remotely without a second visit to the floor/office.

13 Implemented Plagorm We uqlize Microsoj Server 2003 / 2008 with our 3200 Arista thin client connecqng through naqve RDP Using both MulQMonitor and MulQSession within both the controls and office environments. We have found a cost saving in MulQSession, no need to always have a second terminal on the producqon floor. MulQSession allows us to access both the office and controls servers from one staqon. One staqon can have Wonderware and SAP at the same Qme.

14 MulQSession Saves

15 How has ThinManger Helped Since we started with ThinManager in 2006 we have Replacing Terminal Servers Off the shelf Thin Client - poinqng to the new server required a visit to the thin client. This process would take weeks to finish. ACP Thin Clients Add new servers to ThinManager, create group, moved clients to group and restart terminal, done. Within a day over 100 clients can be moved.

16 This Year In February we moved to Wonderware 2012 and all new virtual terminal servers This move took very liele Qme Pre- build of servers and groups the day before in ThinManager. On the go live day I switched 37 HMI from three physical servers to three virtual servers in under 30 minutes. Any ConfiguraQon changes were corrected and deployed without a trip to the producqon floor.

17 This Year Any Wonderware problems were easily viewed and screen shot can be created again without going to the producqon floor. Any Wonderware program changes can be viewed and tested again without visiqng the floor Remote the session without losing resources that Microsoj Terminal Servers Manager uses. View client status on the terminal before any deployments or restarts.

18 This Year Completed an office virtual terminal server upgrade, moving thin clients from one server to another easily. Time sqll for planning, the need to work around producqon schedule is easier when you can remote in and make changes to ThinManager, restart and see the results. Changes can be made even if the thin client is powered off.

19 With a xli license: ThinManager Add- ins TermSecure - so we need to make configuraqon changes and cannot control who sees what at a terminal PXE Boot We must use ACP Compliant Thin Client WIN TMC We use Windows Remote Desktop to connect to a terminal server from a computer, with no control over the connecqon.

20 Post ImplementaQon We have found that ThinManager is preey much the only product out there offering the level of management and funcqonality our business requires. Our cost savings were more from a labor standpoint as this gave us the ability to centrally manage our thin client based environment. This plagorm is used by all plants, which also allow Corporate to remote in and cover when plant personal are out of the office.

21 Our ThinManager

22 Our ThinManager

23 Our ThinManager

24 Top Five IT Tools My top five client tools used daily Thin Manager Thin Client Management Used on a daily basis to help End- Users. vsphere Client Virtual Server Management Watching the status of the Secure CRT Network Switch EdiQng Make changes to out network switches

25 Top Five IT Tools SolarWinds Engineering Toolset To look at how things are running within the switches, IP being used, which ports are up or down at current Qme SNMPc OnLine Is setup by our network team in Denver, but it is a map view of all imports equipment, and in one view I can see if I have down equipment. The toolset used above allow me to respond to plant problem fixed 95% from my desk, allowing me to conqnue working on projects.

26 Support\Upgrades We started with version 3 and are now on 6.0 service pack 3. Support has always been outstanding. We just had performance problems with scanners dropping numbers. The ACP help desk was able to point me into the right direcqon and gave me the quesqon to ask the scanner vendors. Went to this years TMUG (ThinManager User Group) and found this to be a great source of informaqon regarding how others are using the product, best pracqces from ACP as well as ACP learning how to make it beeer from the end users.

27

28