Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.
-
Upload
bertha-miller -
Category
Documents
-
view
220 -
download
0
Transcript of Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.
![Page 1: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/1.jpg)
Copyright c 2004 OSIsoft Inc. All rights reserved.
Bryan S Owen PE
System Management Best Practices
![Page 2: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/2.jpg)
Richness & Reliability“Value Coefficients” • Quality
– Across operations and data systems
• Quantity– Across business needs and over time
• Utilization– Across enterprise and just in time
![Page 3: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/3.jpg)
It all Starts with Great Software …and the Right
Architecture• Visualization
Tools
• Availability
• Reliability
• Security
![Page 4: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/4.jpg)
Integrated Data Collection
Proven:Integrated Interface
Cutting Edge:Embedded Historian
![Page 5: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/5.jpg)
Embedded PI Historian• Continuous Historian for DeltaV
Application Stationhttp://www.easydeltav.com/pd/PDS_ApplicationStation.pdf
• “56SAM” Historian for Allen-Bradley ControlLogix
www.oldi.com
• “Promoted” Interface Node
• Also visit: www.echohistorian.com
![Page 6: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/6.jpg)
Fault Tolerant vs Redundant
Incident Tolerant Redundant
Environment Fault
Hardware Fault
Software Fault
Administrative Error
Scheduled Down
“Smile” Points: 15/30 22/30
![Page 7: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/7.jpg)
Redundant Architecture
• Reliability– Build from the Data Up
• Availability– Build from the Users Down
You decide what comes first!
![Page 8: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/8.jpg)
Redundant Data Collection
Dual Gateways Interface Node Failover
![Page 9: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/9.jpg)
Redundant Data ServiceDual PI Servers Dual PI Clients
![Page 10: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/10.jpg)
Redundant Architecture
No single point of failure sounds great, what’s the catch?
• Interface Support
• History Recovery
• Gap Filling
• Client Impact
• Fugitive Data
![Page 11: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/11.jpg)
Fugitive Data Capture
Essential for rich content but…
1% of the data causes 99% perspiration! • Manual Entry Systems• Custom Applications• Isolated Point to Point Links
Solution: Standard Interfaces / Flat Files• Demo – Excel Entry Form
![Page 12: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/12.jpg)
Secure Architecture
• Domain Membership
• Internet Access
• “Stateful” Firewall
PI Server Security White Paper:http://www.osisoft.com/whitepapers.aspx
![Page 13: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/13.jpg)
Domain Membership
Shared resources and tools
MS client network protocol required
Central policy administration
Potential deployment conflict
Single logon support PI trust authenticates w/ domain controller
Pro Con
Hint: Make friends with your domain admin!
![Page 14: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/14.jpg)
RtPM Internet Access
Reliability:• Documentation• Online Updates• Time Servers• Remote Support
Richness:• Fugitive Data
– PI HTML Interface
• Data Replication– PItoPI Interface
Strategy:Outbound internet connectivity for administrators. Bidirectional connectivity for secure applications.Interactive users over VPN, intranet or RtPortal.
![Page 15: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/15.jpg)
Internet Time Synchronization
• At Least One Time Server on Inside– Default: AD Domain controller– Setup: gpedit.msc “Computer Configuration”
• Browse Administrative Templates\System\Windows Time Service\Time Providers
• Enable Windows NTP Client and/or Server
• Standalone Computers– NTP is most robust (n/a on W2K and NT)
• Select “Internet Time” from Adjust Time Dialog– See MS KB ID 816043 for diagnostic help
– SNTP from console (w32time.ini file on NT)• Net Time /SETSNTP:mytimeserver.com
– Test W2K with W32TM –test –once –v
![Page 16: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/16.jpg)
“Stateful” Firewall
Source: Cisco PIX 6.3 Command Reference
![Page 17: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/17.jpg)
“Securing Control Systems: WHAT YOU NEED TO KNOW” By Jay Abshier and Joe Weiss www.controlmag.com February/2004
![Page 18: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/18.jpg)
PI Trusts and FirewallsMultiple Trust Records are Required• API Interface Node
-View credentials from PI server (netstat)
1. Reverse name lookup (case sensitive)
2. IP after firewall address translation
• SDK Interface Node-View credentials from source (pidiag -host)
3. Computer name
4. IP bound to primary NIC
OPC Demo
![Page 19: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/19.jpg)
2003 Enterprise Survey• Triggered Outputs / RLINK
Custom Applications• RtSQC / Process
Templates / OleDBPI-OPC HDA
• ACE / Sigmafine(RtAnalytics)
• Batch File• PI-OPC INT Gather
Assign Context
Analyze
Distribute
Visualize
Act
Highly valued RtPM application deployments.
![Page 20: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/20.jpg)
Survey “MVPs”
• Processbook– Trending– Custom Applications
• Datalink– Analysis– Data Scrubbing
Best Practice:Automate Displays and Reports.
![Page 21: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/21.jpg)
Enterprise Scalability
• Real Time Data– Local, Remote and Global!
• Diverse User Community– Desktop to Corporate “Nerve” Center– Mobile Experts and Support Centers
• More Visualization Ergonomics too…– High Density Multi-Head workstations– Overhead “Big Picture” Displays
![Page 22: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/22.jpg)
Enterprise DeploymentRisk: Deployment activities increase overall failure rate by introducing infant mortality back into otherwise stable systems.
High incidence of infant mortality, followed by a constant probability of failure, then by a wear-out zone.
High infant mortality, then constant or slowly decreasing probability of failure.
“Center On Reliability: Space-Age Failure Patterns” By Rich Merrit www.controlmag.com June/2003
Pattern A: ~4% of failures.
Pattern F: ~68% of failures.
![Page 23: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/23.jpg)
Typical Maintenance Tasks
“Hot” Database Change
Daily Verify data before and after.
“Warm” Restart Service
Monthly Verify data flow before and after.
“Cold” Software Upgrade
Annual Perform acceptance test.
Class Activity Period Review
![Page 24: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/24.jpg)
Deployment Strategy
• Architecture (Minimize Scope)– Distributed and Redundant
• Standardization (Minimize Burn-In)– Technology and Procedures
• Scheduling Execution– Operations Stable (Best Feedback)– Down (if Deployment > Burn-in)– Never on a Friday!
![Page 25: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/25.jpg)
Desktop DeploymentReliable Methods
Scope of Roll-Out:• Individual
– Organize media & downloads in proper order
• Small– Shared Media, customize “ini” files
• Medium– Active Directory Published Application
• Large– System Management Server (see white paper)
![Page 26: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/26.jpg)
Shared Media LayoutA. Windows Components
1-MDAC, 2-Scripting, 3-.NET FrameworkB. OSISoft Components (ie Combo Pak)
4. SDK – modify setup.ini answer file.5. DataLink6. ProcessBook
C. Custom Extras (readme.txt or script)7. Copy INI files, patches, add-ins8. Known server registry
Strategy:Installation by user, numbered shortcuts.Install one at a time, reboot if required.
![Page 27: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/27.jpg)
Active Directory “Publishing”
• Targets ZAP File or MSI– ZAP required as “setup.exe” wrapper
• “Published” Application– Appears in “Add/Remove Programs”– Installation is manual
• Available after next logon, must have rights
• “Assigned” Application (MSI only)– Automatic install on boot or first use
![Page 28: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/28.jpg)
“ZAP File”
![Page 29: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/29.jpg)
Group Policy for Software Installation Demo
![Page 30: Copyright c 2004 OSIsoft Inc. All rights reserved. Bryan S Owen PE System Management Best Practices.](https://reader035.fdocuments.us/reader035/viewer/2022062304/56649ed25503460f94be267c/html5/thumbnails/30.jpg)
Rich and Reliable RtPMSummary
• Redundancy works
• Be Secure
• Leverage domains and the internet
• Seek out and capture fugitive data
• Inspire action on the right data
• Automate reliable methods
• Use 80% to improve, 20% to sustain!