© 2001 Johnson Controls, Inc. www.johnsoncontrols.com Code No. LIT-653820
APPLICATION NOTE
CF Dashboard Offering
Creating the CF Dashboard Offering ...3
Introduction... 3
Key Concepts... 4
CF Dashboard Offering ...4
Customer Involvement...5
CF Dashboard Components ...7
CF Dashboard System Design ...12
Customer Needs and Expectations Checklist ...15
Facility Infrastructure Checklist ...16
Creating the
CF Dashboard Offering
Introduction
The CF Dashboard offering is a customized solution for the telecommunications market and other large enterprises. This system gathers, calculates, and displays information in one graphical interface using standard products from Johnson Controls and other companies. The CF Dashboard offering provides unparalleled facility information access, analysis, and management for the systems in a facility that are critical to its operation.
Using components from the Metasys Building Automation
System (BAS), the CF Dashboard offering provides a flexible decision support system customized specifically for the business needs of each enterprise. Various systems are displayed in a single interface to aid the customer in making management decisions quickly and accurately in response to any infrastructure-based event. The CF Dashboard system can improve a customer’s business performance by reducing costs and ensuring reliability through the monitoring and collection of realtime information.
This application note describes the CF Dashboard components and design and provides checklists for:
• customer needs and expectations • facility infrastructure
Key Concepts
CF Dashboard Offering
The CF Dashboard offering is a management information system that displays various subsystems within a facility or facilities, such as Heating, Ventilating, and Air Conditioning (HVAC), power, fuel, and lighting, in one interface. The CF Dashboard system directs
management focus to areas needing attention. Facility information from any location is gathered and displayed in a format that promotes understanding, analysis, and management efficiency.
The CF Dashboard system is a unique method of using the Metasys M5 Workstation, M-Graphics, and/or M-Web software to address the management of multiple locations. The system not only gathers and displays current data about the customer’s facility, it can also analyze and interpret that data. A user can monitor multiple facilities or buildings, each with its own customized screen. The customer is able to decide which mission critical systems are monitored and displayed. Target systems are not limited to traditional Building Automation Systems (BAS) such as HVAC, lighting, fire, and security. Any system containing mission critical information that needs to be monitored can be presented on the CF Dashboard screens. Figure 1 is an example CF Dashboard screen.
Algorithms for the CF Dashboard system are computed in the network supervisory controllers or can be embedded in the local
M5 Workstation’s ActiveX controls. The necessary calculations needed for monitoring a facility can also be made via JC-BASIC and Graphic Programming Language (GPL) programming. Instead of calculating the algorithms individually, the user is able to spend time on other tasks such as viewing the output presented on the
CF Dashboard screens and making appropriate decisions for that facility.
The CF Dashboard system can be accessed locally via workstations in each building or from anywhere using centrally located Enterprise servers and Internet browsers such as Microsoft Internet Explorer or Netscape Navigator software.
Figure 1: Sample CF Dashboard Screen
Customer Involvement
Involve the customer in the preparation and creation of their
CF Dashboard system. Information gathered from the customer and their staff about how they manage their facility and how they look at critical conditions determines the design and layout of the
CF Dashboard system. Work with the customer to determine: • critical infrastructure components (i.e., HVAC)
• available intranet infrastructure
• network and data security requirements
• system maintenance roles and responsibilities (service level agreements)
• alarm monitoring and management interfaces (determine what to do with the data received)
Survey Customer’s Employees from All Levels
Survey the needs of the customer’s employees from all levels of the organization to aid in the CF Dashboard system preparation. Surveying a cross-section of the organization lets you know what information is important to which people. From the data collected, different screens may be needed for different levels of employees. For example, engineers or production personnel may need to monitor different information than senior management personnel.
Analyze the Facility Infrastructure
Be prepared to visit the facility and gather information relevant for the CF Dashboard system creation. Visiting multiple sites may be
required. For example, note information such as the make, model, and service provider of target equipment. See the Facility Infrastructure Checklist (Table 3) for other items that require analysis.
When monitoring more than one building, determine the network infrastructure (i.e., Metasys Network, Ethernet network, Transmission Control Protocol/Internet Protocol [TCP/IP] network, etc.). Figure 2 shows a typical network for a customer with more than one facility.
Workstation Management Engineering Support Remote Access Service Corporate Headquarters Remote Facility Remote Facility Operation/ Management Centers Application Servers Corporate Intranet Remote Facility App overview Figure 2: Typical Corporate Network Structure
CF Dashboard Components
The CF Dashboard system consists of a network of information gathering devices such as field controllers, integration gateways, and supervisory controllers. Ethernet based supervisory controllers are connected individually to the Local Area Network (LAN). From here, information is shared with the local server and/or Enterprise server via the customer’s Wide Area Network (WAN). The Enterprise server provides authorized users with valuable infrastructure information utilizing standardized graphic templates. Figure 2 shows a typical network structure for a CF Dashboard system setup via a corporate intranet.
Components used to create a CF Dashboard system include: • existing Ethernet network (LAN or WAN)
• existing intranet
• Enterprise servers or M5 Workstations • M-Web
• Web browsers • M-Graphics • M-Trend
• supervisory controllers/Network Control Modules (NCMs) • field controllers/Application Specific Controllers (ASCs) • integration gateways
• third-party products
Other Metasys components, Johnson Controls products, and
third-party products can be used as required to collect the data needed for presentation on the customer’s CF Dashboard screens.
Communications Network
The CF Dashboard system is set up over the customer’s existing Ethernet/Internet Protocol (IP) network. Using an Ethernet/IP network promotes high-speed operation using industry standard
communications protocol.
Remote Access—M-Web Enterprise Server and Web Browsers
The CF Dashboard system can be installed on central Enterprise servers. M-Web installed on an Enterprise server provides the customer with remote access to their system via their corporate intranet. M-Web allows users to easily, confidently, and remotely access and review the current operational conditions of their entire facility. CF Dashboard screens consist of M-Graphics displays converted to HyperText Markup Language (HTML) pages in the M-Web environment.
All that is required for remote access is a computer or other device that supports HyperText Markup Language (HTML) pages and has
Microsoft Internet Explorer or Netscape Navigator software.
Local Access—M5 Workstation and M-Graphics
M5 Workstations and M-Graphics are the main components of the CF Dashboard system. The system can be customized for each facility and provides local monitoring and control for communication with the facility’s supervisory control networks. The CF Dashboard system can be installed on one or more M5 Workstations in each building.
CF Dashboard screens consist of M-Graphics displays on the local M5 Workstations. An advantage of the local access configuration is the ability to incorporate M-Graphics ActiveX controls in the screens, providing dynamic display capabilities.
M-Trend
M-Trend provides superior graphics and text-based trending
capabilities at the local facility. M-Trend software is available for use in local M5 Workstations. The M-Trend component provides a powerful management tool to analyze a breadth of historical operational characteristics of a facility.
Through tabular or graphical trend views, a user reviews any combination of data sources from an integrated database. Graphical displays are single or stacked graphs with selectable display
characteristics. In addition, any graphical display provides detailed trend source information and supports zooming for precise analysis.
Supervisory Controllers
Supervisory controllers such as Network Control Modules (NCMs) monitor and control field controllers and other infrastructure related equipment within a facility. The supervisory controller uses powerful data gathering and energy management tools to help make the facility economical and cost effective.
Field Controllers
Field controllers perform the control function of the mechanical items in a building. These controllers also gather data. Field controllers can be highly programmable or can be specialized like the Application Specific Controllers (ASCs). The ASC devices focus on particular control functions. Highly programmable devices are designed to handle unique or difficult control schemes. These devices are the working end of a control system and perform much of the data collection.
Integration Gateways
Johnson Controls has many years of experience in providing integrated systems. The Metasys BAS can connect over 700 different devices from over 125 different companies. One of the tools used in delivering integrated systems is the Metasys Integrator unit.
In addition, the Metasys system can integrate competitive systems. The integration of legacy systems provides investment protection and reduces the cost of upgrading control systems.
These gateways provide connections to hundreds of products and systems. Therefore, the CF Dashboard offering is an integrated system accessing all critical information no matter where it comes from. For more information, refer to the literature in Table 1.
Table 1: Related Information
Product Literature
M5 Workstation
M5 Workstation Product Bulletin (LIT-641050)
M5 Workstation Product Positioning Technical Bulletin (LIT-641150) M5 Configuration and Estimating Guidelines Technical Bulletin (LIT-641200) M5 Workstation System Overview Technical Bulletin (LIT-1153250)
Installing the M5 Workstation Technical Bulletin (LIT-1153300) M5 Workstation User’s Guide (LIT-1153800)
Metasys M-Web
Metasys M-Web Server Product Bulletin (LIT-641055)
Metasys M-Web Product Positioning Technical Bulletin (LIT-641155) Metasys M-Web Configuration and Estimating Guidelines Technical Bulletin (LIT-641205)
Metasys M-Web User’s Manual
M-Graphics
M-Graphics Product Bulletin (LIT-6420060) M-Graphics User’s Manual
M-Trend
M-Trend and M-Historian Product Bulletin (LIT-6420070) M-Trend User’s Manual
Application Specific Controllers
Application Specific Controllers Technical Manual
N1 Ethernet/ IP Network
N1 Ethernet/IP Network Product Bulletin (LIT-635033)
N1 Ethernet/IP Network Product Bulletin Supplement (LIT-635033a) N1 Ethernet/IP Network Technical Bulletin (LIT-6360175)
Network Control Module
Network Control Unit/Network Expansion Unit Product Bulletin (LIT-635045) NCM Software Options Technical Bulletin (LIT-636023)
Network Control Module 200 Series Technical Bulletin (LIT-636025) Network Control Module 300 Series Technical Bulletin (LIT-6360251)
Metasys Integrator
Metasys Integrator Product Bulletin (LIT-629006)
Metasys Integrator Product Bulletin Supplement (LIT-6290061) Metasys Integrator 300 Series Product Bulletin (LIT-629070)
Metasys Integrator 300 Series Product Bulletin Supplement (LIT-629075) Metasys Integrator 300 Series Installation Technical Bulletin (LIT-6295122) Metasys Integrator 300 Series Commissioning Technical Bulletin (LIT-6295124) Metasys Integrator 300 Series Point Mapping Technical Bulletin (LIT-6295125) Metasys Integrator Technical Bulletin (LIT-6295130)
Product (Cont.) Literature Graphic Programming Language
Graphic Programming Language Product Bulletin (LIT-635095) GPL Programmer’s Manual
JC-BASIC Programming Language
JC-BASIC Product Bulletin (LIT-635100) JC-BASIC Programmer’s Manual
Metasys Data Visualization
Metasys Data Visualization User’s Manual M-Applications Manual
Metasys Historical Data Visualization
Metasys Historical Data Visualization User’s Manual M-Applications Manual
Competitive Interfaces from Johnson Controls Centaurus Systems, Inc.
CF Dashboard System Design
Customer needs drive the overall design and layout for the
CF Dashboard system. A wide variety of systems and points may be represented graphically on the CF Dashboard screens. The system may consist of multiple screens at different levels of detail. Site Data Summary screens (higher level or main screens) should contain summary information with few details. Detail view screens (lower levels) contain more detailed information. Figure 3 is an example of possible design for a CF Dashboard system.
Map with Facility Locations (i.e., USA)
List of Facilities or Buildings for that Geographic Location (i.e., State, City, or Campus)
Shelters Detail View
Individual Building or Facility Main Page with Site Data Summary View
HVAC Detail View Electric Detail View Site Plan Detail View Fire Security Detail View display flowchart
Site Data Summary View
Site Data Summary View allows displays realtime information about the health of the entire facility. Users visually scan the major
components being monitored without being bombarded with
unnecessary detailed information. There is no need to navigate through several screens to obtain relevant information. This is an advantage of the CF Dashboard offering because a user does not need to view the details of the facility unless one of the components indicates a potential problem. If a problem is indicated, the user can view the component’s detailed view. Figure 4 is an example Site Data Summary View screen.
Detail View
Detail View allows a user to gain access to more detailed information on the current realtime conditions of systems or points by navigating through one or more levels of CF Dashboard screens. Each Detail View screen contains additional information on a specific component or subsystem represented in the Summary View screen.
For example, Figure 4 shows a Summary View screen that contains a graphic for Heating, Ventilating, and Air Conditioning (HVAC) plant status on the left side of the screen. Figure 5 shows a Detail View screen that contains a site floor plan that provides physical locations of various equipment. If the Summary View graphic indicates that there is a problem with the HVAC plant, a user can look at the site’s floor plan to see where the problem occurs.
Customer Needs and Expectations Checklist
Be sure to survey the needs of employees from all levels of the customer’s organization to analyze what information is important to which people. Use the checklist in Table 2 to determine customer needs and expectations.
Table 2: Customer Needs and Expectations Checklist
Step Task Completed
1 Ask the customer what keeps him/her up at night when it comes to their buildings.
2 Review situations where ill-informed decisions cost the customer money and time.
3 Ask what systems and subsystems contain information regularly accessed by staff to promote efficiency.
4 Ask what would be the perfect operator platform for managing business efficiently and impacting the customer’s bottom line.
5 Discuss the graphical design, navigation standards, and layout options with the customer.
6 Ask what is the relationship between the data that is collected from the different systems.
7 Ask if there are any data conversions, calculations, algorithms, or reference resources that need to be used to make the data collected useful.
8 Document what value the customer expects to receive by investing in the CF Dashboard offering (i.e., improved MTTR [Mean Time To Repair], increased MTBF [Mean Time Between Failures], lower staffing, etc.).
9 Request copies of all relevant customer standards and policies and be sure they are understood.
10 Determine the customer’s requirements for any system redundancy or high availability options (i.e., Duty Standby NCMs, etc.)
11 Determine if the customer wants the CF Dashboard system only for monitoring purposes or if the system should deliver alarms to a monitoring station.
Facility Infrastructure Checklist
When analyzing the infrastructure of the customer’s facility, be prepared to visit the facility to survey and gather relevant information. Visiting multiple sites may be required. Be honest with the customer regarding what can and cannot be achieved. Do not set false
expectations. Use the checklist in Table 3 to analyze the facility’s infrastructure.
Table 3: Facility Infrastructure Checklist
Step Task Completed
1 Record the make and model of target equipment being monitored.
2 Record the name and phone number of the current service provider for the target equipment. (This information is often accessed through building maintenance personnel.)
3 Determine if the target equipment is compatible with the Metasys system.
• If so, include the appropriate interfaces for both target equipment and the Metasys system in the CF Dashboard system design.
• If not, analyze the ability of the target equipment to use a serial interface. Notes: If the target equipment does not have any serial interface capabilities,
replacement of the equipment or the addition of discrete devices may be the only solution for monitoring the equipment.
The customer may be required to obtain the assistance of the vendor’s technical department. Also engage the Johnson Controls System Integration Services organization to evaluate and quote any new integrations needing development.
4 Define the customer’s existing network infrastructure (Intranet).
Note: If the customer has an existing nationwide Ethernet network, networking is required to a central location.
5 Determine network and data security requirements.
6 Determine Local Area Network (LAN) and Wide Area Network (WAN) traffic loads and whether the customer’s network has the capacity to support the load.
7 Evaluate if integration with the target system will cause interference in customer’s processes (i.e., acceptable down time).
8 Determine if the customer needs to replace existing infrastructure elements that are desired for integration with the Metasys system, but are outdated or incompatible. Note: Contact Systems Products to verify the course of action if no drivers
currently exist for the target system. Do not make assumptions.
9 Determine if the M-Web servers supporting the CF Dashboard system are installed as Enterprise servers at a central location or local to each facility or building.
Detailed Proposal Checklist
Use the checklist in Table 4 to prepare a detailed proposal to present to the customer.
Table 4: Detailed Proposal Checklist
Step Task Completed
1 List the monitored buildings.
2 List target systems in each building.
3 List points monitored for each system.
4 List deliverables provided by customer (i.e., escorts for building access, internal coordination, 120 VAC UPS [Uninterruptible Power Supply] circuits, special training for Johnson Controls employees, etc.).
5 Include a division of responsibility matrix that defines what is expected from Johnson Controls and the customer.
6 List the limitations of the various interfaces that Johnson Controls intends to use for the CF Dashboard system setup (i.e., maximum number of points, performance characteristics such as update time, etc.).
7 List any impact to the customer during and after the installation of infrastructure equipment required for the CF Dashboard system.
8 Provide a set quantity of graphics that are included in the price (include some preliminary graphics based on the discussions with the customer).
9 Include the method of delivery for the CF Dashboard system (i.e., M5 Workstation, M-Web, etc.)
10 Remind the customer that they must participate in the CF Dashboard system creation.
IMPORTANT: Johnson Controls may have to secure the help from the vendors that installed or currently service the target systems. This may be very costly. In some cases, the customer’s employees or the vendor may not be familiar with the system.
Be sure to make proper provisions in the proposal to qualify such a situation. An estimate budget may be included in the proposal if no firm pricing is available.
Notes
Controls Group www.johnsoncontrols.com
507 E. Michigan Street FAN 653
P.O. Box 423 M-Applications Manual
