1 / 17

Introduction to OIS Display Development Standards

Introduction to OIS Display Development Standards. Presented By: Skip Hagan OIS Project Technical Lead Entergy Fossil Operations. A Moment For Safety. Look around! Listen for a second or two. Give the horn a couple of taps. ONLY THEN, Back out of your parking space. What is OIS?.

kalb
Download Presentation

Introduction to OIS Display Development Standards

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Introduction toOIS Display Development Standards Presented By: Skip HaganOIS Project Technical Lead Entergy Fossil Operations

  2. A Moment For Safety • Look around! • Listen for a second or two. • Give the horn a couple of taps. • ONLY THEN,Back out of your parking space.

  3. What is OIS? An Operations Information System! Software and hardware that gathers, stores, calculates, and displays... information from the generating units. ...used by operations personnel, engineers, and other local and corporate staff to better understand each unit’s thermal and economic performance and reliability.

  4. Before OIS Generating plants were initially provided with the traditional suite of data acquisition and control systems. Plant Data Acquisition/ Control System Control Room

  5. OIS implementation WPF interface buffer OIS server Plant Entergy’s wide area network Data Acquisition & Control System Control Room

  6. OIS at Entergy The scope of OIS 2.3 is outlined below. • Application No. of Displays (approx) Description • Plant Summary 4Production, Operations, Financials & Declarations • Controllable Losses Ov 1 Controllable Losses, Heat Rate, Costs • Controllable Losses 15 Diagnostics and Detailed Displays • Turbine Monitor 10 Performance & Efficiency,Heat Rate,Bearings • Generator Monitor 5 MVAR Advisor,Bearings,Stator • Boiler Monitor 7 Performance,Fuel Conditions,Burners,Limits • Condenser Monitor 5 Cleanliness,CWP Advisor,Assessment • Feedwater Heater Monitor 23 BFP Monitor,TTD’s,DCA’s,Status,Condition • Pump & Fan Monitor 9 Status,Bearings,Vibration • Water Chemistry Monitor 2 Advisor,Condition,Alarms,Limits • Cycle Isolation 3 Major Drain Monitor,Condition,Alarms • Transition Monitor 20 Startup and Shutdown, Turbine Roll and Load • Unit Dispatch Curve 2 Based on Ambient Temp.

  7. Diversity & perspective “Different strokes for different folks.” • Operations people want to know what their systems are doing and how best to “tweak” the plant controls for optimum performance. • Production and performance engineers need to analyze factors that affect capacity, efficiency, and reliability. • Diagnostic specialists are constantly in pursuit of the slightest hint of system and component physical degradation or declining performance.

  8. PI-ProcessBook® Entergy’s power generation team is OIS enabled! • Every OIS user is a potential developer through the ProcessBook (PB) desktop environment. • OIS users are consistently meeting their individual and site goals with the support of OIS and their own custom built displays. • Resolution of emergent and suddenly critical issues are facilitated through creative use of PB/OIS displays, for “just in time” analysis. • “Local genius” can be readily rolled out system-wide.

  9. Need for standards PI-ProcessBook® is the tool used to create our OIS displays. Displays are created by: • Our I.T. application development and support team • Plant operators and engineers • Plant monitoring & diagnostic specialists • Corporate plant support engineers • Casual or occasional users

  10. Opinions, perceptions & just good design Reality ISa perception! Individual responses to displays are based upon their experience and training. Information must be presented in a way that is quickly perceived and readily understood. • Establish the fundamental ProcessBook environmental standards for all displays: Screen resolution, toolbars, etc. • Similar displays must be consistently formatted; between displays and even between applications. • Symbols, icons, and other graphical elements must be in concert with those used and recognized by the end users.

  11. Abbreviations and acronyms • Develop an abbreviations and acronyms list to ensure consistent use throughout the application.(Gaining consensus and acceptance may prove to be a challenge.) Common Abbreviations & Acromyms NOTE: It is preferable NOT to abbreviate words marked with an asterisk (*).

  12. Display Digits • Establish a logical constraint on display digits. Display only truly significant digits.

  13. COLOR STANDARDS FOR PROCESSBOOK DEVELOPMENT Use Of Color • Color coding is more than decorative. It often carries a connotation that may be significant to the user that is not recognized by the developer. Ask questions, then, choose wisely. • Use a “web ready” color palette to facilitate web interfacing.

  14. Color and Trends • When possible, color co-ordinate your trend pens with the corresponding graphical elements. Each bearing is assigned a color The corresponding trend trace is the same color.

  15. Highlight the Index • When using an index parameter for a set of trends, assign a specific color for the index trace. Use this color in ALL your trends. • When using an index parameter for a set of trends, assign a specific color for the index trace. Use this “index color” in ALL your trends.

  16. Navigation Sense • The ability to navigate to the desired information, quickly, efficiently, and LOGICALLY can mean the difference between an application that is useful and one that frustrates the user. • Be consistent in the placement of navigation buttons. Develop a method, stick to it, and tell the users about it.

  17. In Conclusion Standards Are Vital To Success! At the earliest possible stage of the development process: • Define your proposed display standards. • Include end-user review and acceptance of the standards. • Publish the approved standards document. • Enforce compliance. • Check and adjust.

More Related