Custom name examples

The following simple examples show how you might use custom names.

Change "Unit" to "Reactor"

Company X is a traditional batch-oriented production company. Most of the batch terms used in PI BatchView apply to Company X’s processes, but it would be helpful to change a few of the terms. For example, Company X would like to use Reactor instead of Unit. They can use custom names to change the label for every instance of the term "Unit" and its counterparts so that these terms appear as "Reactor." Such terms include: Unit, Units, Unit Name, and Unit Heading.

Change "Still Starting" to "Still Running"

Company Y is a power generation company that does not do traditional batch processing. PI BatchView is still useful to a part of the company because they monitor the startup process of each turbine. Treating each startup as a PIUnitBatch allows them to compare them with previous startups. Traditional batch terms that appear in PI BatchView are not very helpful. They can use custom names to rename several of their terms to more appropriate nomenclature. For example, they would like to use Still Starting in place of Still Running in the results table or Turbine in place of Unit Name in the attributes search component.

Change Product to Stadium

Organization Z runs an annual, company-wide tennis tournament and uses PI BatchView to compare games, matches, and so on. This is an example where not only do they not want to see the PI BatchView standard batch terms, but they are using properties for things that have completely different meanings from the original batch term. For example, they chose to use the Product field of the PIUnitBatch to store the name of the stadium hosting each set; therefore, using the word Product in the user interface does not make much sense. Following are views of the PI BatchView QuickSearch window without and with terms customized for a tennis tournament: