Centerline Summary and Overview

This information is specific to the latest release of PARCview:

7.2.x

PARCview’s Centerline display type can be used to build a report of filtered run-based statistics.

Centerline displays present an information-rich, easy-to-read tabular report of key process information. Statistics are calculated for the last several instances of a specific period of time or “run”, like an hour, grade run, or production day. These statistics are displayed alongside current values and control and/or spec limits. Tag limit integration causes values to change color when limit violations occur.

PARCSecurity Permissions

PARCSecurity plays no major role in controlling access to Centerlines. In order to limit access to a Centerline Display you would want use Windows folder and file rights.

Configuration

Like most displays, a centerline needs data tags, which can be grouped into sections in the display. The centerline’s startup behavior, tag limit settings, appearance, and other settings must be configured. Right-click anywhere on the centerline and select Configure or go to the Display tab in the ribbon bar and select Configure to open Centerline Configuration.

Tags Tab

The Tags tab contains the centerline’s tag set. Group tags into logical sections, give tags custom descriptions, enable tag limits, and more.

Settings Tab

The Settings tab contains miscellaneous properties of the centerline that affect its functionality and appearance.

Startup Tab

Use the Startup tab to configure the centerline’s load behavior.

Limits

Use the Limits tab to configure tag limit integration.

Time Periods

Use the Time Periods tab to configure the types of time periods or runs available for selection from the centerline’s settings panel.

Overrides

Use Overrides to override a process area’s settings when generating runs.

Run Browser

The Run Browser tool allows users to view data over relevant time periods (“runs”). First the user supplies the run criteria, then Run Browser searches for the periods of time that fit that criteria. Most PARCview displays use Run Browser to display run-based data.

Log Files

PARCview on the specific computer where PARCmessage is running.

Errors can also be stored in the PARCview install directory both on the server and clients ...\Capstone\PARCView\LogFiles

Required Server Applications

Anything needed for PARCview to be open/running is required for trends to work and populate with data.

• UA Server: All PARCview vr 7 functionality requires a Universal Access (UA) server.
• GDS: All PARCview vr 7 functionality requires a Global Discovery Server (GDS).

Additionally, anything that pulls or collects data also needs to be running so that users can have real time data. Of note these applications play a major role in using Trends:

• PortIO/PortIO File copy: Depending on how your site is setup and how your server/clients collect data you may need PortIO to be running.
• PARCIO: Depending on how your site is setup and how your server/clients collect data you may need PortIO to be running.
• PARCfile copy client/server: Depending on how your site is setup and how your server/clients collect data you may need PARCfile copy to be running.
• PARCtag Sync: Needed so that tags are constantly synced as Trends get their data from tags.
• PARCcalc Server: Some tags come from the PARCcalc server, additionally if you use a script combining a production tag and a PARCcalc tag this will be needed.
• PARCAlarm Server: The server application generates Alarm events based on the Alarm Rules defined in the Alarm Configuration area.