Architecting a Manufacturing Intelligence System, RSTechED 2012, Session MI02

Agenda Goals of Manufacturing Intelligence Key benefits of Manufacturing Intelligence in the Plant FactoryTalk VantagePoint is Your MI Infrastructure Wrap-up Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 2

The Goal of Manufacturing Intelligence Go beyond Automation Meaningful Users KPIs Ad-Hoc Ability to Analysis “dig in” Easy to find InformationOrganized Content Templatized Reports Security Abstraction Many data sources Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 4

What are the goals of MI?Provides Data Connectivity Connecting to your data sources Providing access to information enabling Users to make informed decisions  For solutions for today and tomorrow Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 6

What are the goals of MI?Provides Infrastructure and Organization MI is for the long haul – you are building an infrastructure upon which to solve various problems of a business Now and in the future  For solutions for today and tomorrow Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 7

What are the goals of MI?Provides tools and capabilities to solve problems MI is providing tools for your Users and Systems, enabling them to solve problems Encourages Ad-Hoc analysis Allows Users to bring together data from disparate data enabling problem solving  For solutions for today and tomorrow Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 8

Agenda Goals of Manufacturing Intelligence Key benefits of Manufacturing Intelligence in the Plant FactoryTalk VantagePoint is your MI Infrastructure Wrap-up Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 9

Typical Single Source ArchitectureThe Layers Data Specific Report Expert / SQL Server Reports and Analysis Reporting Services Data FTM Engine Transformation SQL Data Source Time Series - Live and/or Historical Transactional Controllers Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 10

Not just combining raw data…The ManufacturingIntelligence Layer  Consume existing reports  Leverage existing data transformations  Connect and consume data directly from the raw data source Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 11

What happens when you add moresources? Area 1 Area 2 Area 3 Vendor A Vendor B Vendor C Still want to leverage the data source elements  Reports and Information  Engineering configuration  Need to combine the data Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 12

What we really need is… The Manufacturing Intelligence Layer Area 1 Area 2 Area 3 Vendor A Vendor B Vendor C As you combine data, its value grows 1+1 = 3 Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 13

The MI LayerA quick overview of FactoryTalk VantagePoint EMI  An EMI framework  Ability to connect to various data sources  Provides the capability to model and organize your data  Out of the box client tools  Provides the ability to extend the framework at all levels within the system (connectors >> reports) Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 16

The MI LayerFactoryTalk VantagePoint EMI is a Type Repository  Every item within the VantagePoint system is based on a Type  Types are grouped together as Packages  VantagePoint comes with many out of the box types  You can add your own or extend types Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 17

The MI LayerItems within FactoryTalk VantagePoint EMI  An item can consist of the following properties  Reference  Collection  Enumeration  SimpleValue  A Property abstracts the User from having to know the underlying Friendly Name Actual data source source ID (like a Tag) Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 18

The MI LayerAn Expanded View of FactoryTalk VantagePoint EMI Make it look good Presentation Rules Portal System modeling VantagePoint and Logical Model Logical ModelThe Manufacturing Re-usable trends,Intelligence Layer dashboards, Equipment Template Reports reports… (1+1=3) modeling and abstraction Items based on Types Program Engine And Calc Tag Item Creation Configuration Data Connectors Rules Physical Model Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 19

Data ConnectorsThe Physical Model  Connect or wire-up to various Data Sources  Utilizing industry standard connectors  OPCDA, OPCHDA, Database  Utilizing specific Vendor connectors  OSI PI, Invensys Historian (InSQL) Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 20

Improving the MI ArchitectureAt the control layer  Typically when designing this layer, we are not thinking about the presentation layer, except for the HMI, but we should be  The more we leverage, or can leverage, standard structures (UDTs and AOIs) we benefit  Standard Tagnaming conventions with meaningful descriptors can now propagate throughout the system  Standardization at this level can be taken advantage off at all other layers  Consistent: Reports, Analysis, Displays…  Engineering re-use Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 22

Item CreationThe various ways of creating items  Manual (Manager > New…)  Import / Export  Using Mapped Types  Using Model Builder  Using scripts  Imported from Controllers Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 24

Item CreationUDTs within the Controller  Pre-defined Data Types with instances  Engineering effort already done  Naming, descriptions…  How to leverage in MI layer? UDT Definitions Instances of UDTs VantagePoint Type Import Rules Import Process Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 27

Item CreationFactoryTalk VantagePoint Type Definition  Type can extend existing definition  Include properties not available in Controller UDT Definitions Instances of UDTs VantagePoint Type Import Rules Import Process Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 28

Item CreationRules for Importing UDTs from Controllers UDT Definitions Instances of UDTs VantagePoint Type Import Rules Import Process Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 29

Item CreationUsing Model Builder  Assumes all values needed to create items are in a database or can be defined within a SQL script  Can perform sequenced item creation SpeedReference, System.Sources.FactoryTalk.local host.Applications.PlantPAx.Area1. L63_Util.Online.MTR1506A.Spee dReference, Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 32

Item CreationGreenfield vs Brownfield…  We rarely get the opportunity of being in a position to design from the ground up (Greenfield), it is more likely that we will get an existing facility (Brownfield)  Leveraging the model / items to “abstract” the data sources allows us to replace when convenient - growing at your own pace MI MI Layer Layer (A) (B) Migration Vendor A Vendor B Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 33

Item CreationPros and Cons of each method Criteria Manual Import / Mapped UDT Model Script Export Type Import Builder Can be Automated Portable (reuse in other systems) Good for large systems Requires Database No No Yes No Yes No Can create complex structures Can create directly in the Logical Model Good for Backup / Restore Can create items from any data source Comes with FTVP v4.0 There are various ways to create your items, pick the one that best matches your requirements /and your skill set Increasing Capability Complexity Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 34

Event HandlingWhat are these?  Component of the Program Engine  Provided in Beta in v4.0 as Type Handlers  Encapsulate standard event logic to be used for every item of type “X”  Allows the developer to create custom scripts (Iron Python) to perform various actions  Use Cases:  Item Creation  Property Updates (non volatile) Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 35

Calculation TemplatesWhat are these?  Component of the Incuity Connector (aka Calculation Tags)  Encapsulate standard calculation tag logic to be used for common calculation tags  Single place to change calculations  Allows tag referencing up and down the model tree  Use Cases:  Standard Calculation Expressions Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 37

Improving the MI ArchitectureWhere should we perform calculations?  One of the most common questions asked to Commercial EngineeringThe ManufacturingIntelligence Layer  Always a concern when scoping projects  “Do I mold my data to fit my reports or make my reports fit the shape of my data?”  Where within the architecture should you perform calculations? Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 40

Improving the MI ArchitecturePerforming calculations Criteria to consider when determining where to perform Higher (MI) or Lower calculations within the MI architecture (Data Source) More data sources availableThe Manufacturing Ability to add Time context, Historical Data, AggregationsIntelligence Layer Ability to trim or validate data Provide context to data More advanced calculations with more tools Handle Vendor nuances Supports restricted systems (CFR…) Additional data sources can benefit and leverage the results Consistency as you move closer to the MI layer Typically real-time focused Try to perform your calculations as close to the data source as possible Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 41

Items in the ModelNow what?  Items are configured  Properties are defined and have values  How can I leverage these items in reports? Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 42

Type or Parameter Based ReportsWhat are they?  Reports that are associated with a Type as opposed to hard coded items (tags, properties, queries…) Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 43

Type Based ReportsBenefits… Criteria Type Based Hard Coded Reports Reports Doesn’t require type and instance creation One report used for many items (standard / consistent) Can be used in Portal Configuration Rules (auto display based on type) Reduced maintenance (fix it in one place only) Less effort to extend capability (modify one report) Reuse / Migration to other systems (other plants, facilities…) Reduced complexity (only one report to store) Simpler version control (track one report as opposed to many) Agnostic to TagName changes Configure items not reports Whenever possible use Type Based Reports Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 45

Improving the MI ArchitecturePresentation considerations  Always rule out “out of the box” features before you start down the path of developing custom solutions  Regardless of what presentation you plan to provide, an organized model is critical (Mobile / Thick / Thin)  How to make it easier for both standard reports and ad-hoc analysis (which is at the heart of MI)  Understand whether the client will be Excel on the Desktop or published Excel reports  The more you can model and organize your data the better Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 46

The Logical ModelOrganizing your information  Process of organizing your physical model into the logical views or groupings that will benefit your Users and Applications • By Area Facility • By Equipment Operations • Consumables • WAGES Corporate • Compare Vendors • Compare Facilities Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 48

The Logical ModelNot just equipment…  The model is not only equipment but…  Reporting items  Excel Reports, Dashboards, Trends and XY Plots  StatusItems and Hyperlinks to additional content  Lists of parameters for reports  Query items and Tags  Time Periods (absolute and relative)  Shift Patterns  Collections of Shifts, Batches…  Links to other systems  ViewPoint Displays  SOPs and Document Management Systems  Corporate and Vendor Sites  Extensions  Custom web pages to suit a specific purpose Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 49

The Logical ModelYou decide the level of detail  The logical model does not need to be complex  should assist users in finding information  can be organized in more than one configuration And / Or Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 50

The Logical ModelHow to build the logical model – methods  Manually via Manager  Create items directly or use shortcuts  Automatically via Model Builder  Automatically via External or Program Engine script Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 52

The Logical ModelBuilding the logical model – tips and tricks  Leverage the “Solutions” folder  Invisible to most Users  Staging area for generic items  Reports, equipment, configurations…  Easily exported / imported  Provide User’s their own sandbox  Balance of structure with flexibility Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 53

The Logical ModelBuilding the logical model – tips and tricks  Leverage available types (Base.ModelTree), provides..  a basic heirarchial model  folder based structure  predefined icons You can always build your own Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 54

Portal ConfigurationPresentation and Usability Rules  How do I want to present type or parameter based reports associated with items within the model?  How do I want Users to navigate to locations in the model? Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 56

Portal Configuration - ReportsOption 2: Use Content Type Rules  Content Type Rules  Define what content to provide when items of specific types are displayed Viewable Content Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 58

Portal Configuration - ReportsOption 2: Use Content Rules – but…  VantagePoint only displays folders containing content From Manager From Portal Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 59

Portal Configuration - ReportsOption 2: Use Content Container Rules  Content Container Rules  Inform VantagePoint to treat this item as something that contains content Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 60

Portal Configuration - ReportsReport Navigation Options No Content Rules With Content Rules Same result, different way of navigating to the report – note that you can have both! Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 61

Portal ConfigurationUsing Model Views  How do I want Users to navigate to locations in the model?  Use Model Views and Menus as a way to help Users navigate quickly to areas within the logical model Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 62

Portal ThemeMake it look professional  Portal Theme Configuration  The look and feel of the application  Use corporate logos and color schemes  Make it yours! Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 63

Portal ThemeMake it look professional  Configuration folder on the Web Server contains…  All images, Header configuration (SKIN)  Menu and Portal Style Sheet (css)  Can move to other systems Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 64

Voila! Go beyond Automation Users Easy to find Ad-Hoc Information Analysis Organized Content Ability to Security “dig in” Abstraction Meaningful KPIs Many data sources Templatized Reports Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 65

The MI LayerThe benefits  Ability to access more data sources providing one version of the truth VantagePoint  Easier access to data due to the commonThe Manufacturing layer of securityIntelligence Layer  Users able to do more as a result of being able to find more information due to data modeling and organized views  Consistent values through a common set of calculations Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 66

The MI LayerThe benefits  Reduced IT and Automation services due to type based reports VantagePoint  A variety of additional tools to be used toThe Manufacturing perform analysisIntelligence Layer  The ability to re-use the engineering effort at other facilities  The ability to extend the framework Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 67

Wrap-up / Take-awaysBuild it and they will come  MI is not youryourself it should enable problem solving.model Follow an iterative design process, providing guidance Your Don’t design Users will develop Ad-Hoc reports. Assume just reports, into a box – allow to growth.The and examples along help an is everything, provide answer way for your users solutions should the way easythe next question. to find information. Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 69

Additional Resources Use the Rockwell Automation Discover Portal to learn more!  Presentations, white-papers, videos, product profiles, and partners  http://discover.rockwellautomation.com/IS_EN_Information_Solutions.aspx Take advantage of these upcoming events!  Process Solutions User Group (Nov. 5-6th) & Automation Fair (Nov. 7th & 8th) 2012  http://www.rockwellautomation.com/events/automationfair/  Rockwell Automation’s premier education event Copyright © 2012 Rockwell Automation, Inc. All rights reserved. 70

Try these other MI sessions this week at RSTechEd 2012 (Confirm the day and time in your selection guide) MI01 Manufacturing IntelligenceThank You Presentation, George Peters, 10-11 am, Monday, Tuesday, and Wednesday MI03 What’s New with Manufacturing Intelligence in Action: Interactive Demo Presentation/Demo, Matt Giordano, 9-10am Tuesday, 2-3pm Wednesday, 10-11am Thursday, 9-10am Friday MI14 Build an Information System on Your Integrated Architecture System Lab, Jen Moceri, 4-5pm Monday, Wednesday, Thursday, 10-11am Friday MI15 Factory Talk VantagePoint EMI Advanced Lab: Exploring the Possibilities Lab, Rob Prashad, 9-11am, Monday, Tuesday, Wednesday, 11am-1pm ThursdayFollow ROKAutomation on Facebook & Twitter.Connect with us on LinkedIn.www.rockwellautomation.com Copyright © 2012 Rockwell Automation, Inc. All rights reserved.

Thank you for participating!Please remember to tidy up your work area for the next session.We want your feedback! Please complete the session survey! Copyright © 2012 Rockwell Automation, Inc. All rights reserved.

Architecting a Manufacturing Intelligence System, RSTechED 2012, Session MI02

by Rockwell Automation on Jun 09, 2012

Accessibility

Categories

Upload Details

Usage Rights

Statistics

Architecting a Manufacturing Intelligence System, RSTechED 2012, Session MI02 Presentation Transcript