Answer Stations

Answer Stations

FactoryTalk Historian, FactoryTalk Batch, FactoryTalk Scheduler, FactoryTalk Metrics

• FAQs
• What's New
• Resources

• FactoryTalk Historian

  • How is FactoryTalk Historian licensed?

    The FactoryTalk Historian server is licensed by the total number of time-series reporting tags. A time-series reporting tag is a data point that is sampled over time and can be reported on by FactoryTalk Historian; for example, a temperature of a vessel. Data for that reporting tag can be stored in the FactoryTalk Historian database or in an external database. The smallest FactoryTalk Historian Server license is for 150 reporting tags, and the largest is for 70,000 tags. Each server license contains one FactoryTalk Historian Authoring Client license and a CAL for SQL Server 2000. Users who access FactoryTalk Historian reports must have FactoryTalk Runtime licenses.  Users who configure FactoryTalk Historian data collection or author reports must have an FactoryTalk Historian Authoring Client License.

  • How do I know how large a tag license I need?

    This subject should be carefully considered before purchasing. You should count all of the process parameters for all the machines that you want to collect and allow extra tags for future expansion.

    Keep in mind when considering how many reporting tags to buy:

    If you will be using FactoryTalk Historian to report on external data, reporting tags that refer to external data count against the FactoryTalk Historian license.

    Once in the database, the tag counts against the license even if you stop collecting data for that tag.

    Many customers approach this question by commissioning a small area of the plant for a pilot application and then make a determination on tag count from that experience.

  • What is the difference between an FactoryTalk Historian Authoring Client license and an FactoryTalk Single-User Runtime Client license?

    Users with FactoryTalk Runtime licenses can only view FactoryTalk Historian (and FactoryTalk Metrics) reports that have been created and stored in a FactoryTalk database. They can do this through the FactoryTalk Production Client, a Web browser, or an application with an embedded FactoryTalk ActiveX control. Clients with Runtime licenses cannot create or modify reports or components of reports. They cannot change the FactoryTalk Historian or FactoryTalk Metrics applications in any way. An FactoryTalk Historian Authoring Client license is required to create, save, or change reports, or to configure any aspects of the FactoryTalk Historian application. Authoring licenses are also assigned to specific users, while Runtime license are concurrent (assigned dynamically to users as they access the system).

    Note: There is also an FactoryTalk Metrics Authoring Client license, which is needed to configure a FactoryTalk Metrics application. FactoryTalk Runtime licenses can be used with both FactoryTalk Historian and FactoryTalk Metrics.

  • Can I run FactoryTalk Historian on a workstation/desktop operating system?

    FactoryTalk Historian and other FactoryTalk products are only supported on server operating systems. These include:

    • Windows NT® Server
    • Windows® 2000 Server
    • Windows 2003 Server Standard Edition

    FactoryTalk Historian can be used on a workstation operating system (Windows XP or Windows 2000 Professional) for demonstration purposes only. FactoryTalk Historian cannot be deployed in a production environment on a workstation operating system.

    Note: The included SQL Server Standard Edition will not install on a workstation operating system.

  • What is required for users to view FactoryTalk Historian reports with a Web browser?

    All reports created with the FactoryTalk Production Client are Web-enabled. Users can view these reports provided:

    • They have Internet Explorer v6.0 SP1 installed.
    • They are running a supported operating system (Windows NT 4 SP6+, Windows 2000 SP3+, Windows 2003 Server SE, or Windows XP SP1+).
    • They have downloaded the xxx.cab file from the FactoryTalk server (this is done automatically the first time they access the FactoryTalk QuickWeb).
    • They have a valid FactoryTalk user id and password.
    • There are available FactoryTalk Runtime Client licenses assigned to the FactoryTalk server.  That is, the number of users currently accessing reports does not exceed the number of Runtime Client licenses.

  • How is FactoryTalk Historian different from FactoryTalk Metrics?

    FactoryTalk Historian and FactoryTalk Metrics use similar software tools, but collect and analyze fundamentally different data. FactoryTalk Historian collects process parameters, which is chiefly analog values collected over time for the purpose of documenting a process for later reporting or analysis. FactoryTalk Metrics collects data on the performance and efficiency of the machines on the manufacturing floor — production counts, downtime events, etc. So FactoryTalk Historian monitors the process, and FactoryTalk Metrics monitors the equipment.

    Despite the fact that they collect different kinds of data, the data from each application can be presented together. For instance, it is possible to combine FactoryTalk Metrics and FactoryTalk Historian reports together on the same Web page.

• FactoryTalk Metrics

  • How is FactoryTalk Metrics licensed?

    The FactoryTalk Metrics server is licensed by the number of active workcells or plant model units (PMU) that are configured to collect data. What constitutes a "workcell" or PMU on the plant floor is up to you — it can range from a single operation to an entire line. The important thing to remember is that a configured workcell is monitored as a single unit by FactoryTalk Metrics, so it will have a single cycle time and OEE score (for example).

    FactoryTalk Metrics is available in 5, 10, 25, 50, 100, and 200 workcell licenses. Each server license contains one FactoryTalk Metrics Authoring Client license and a Client Access License (CAL) for SQL Server 2000.

  • How do I know how large a workcell license I need to buy?

    This subject should be considered carefully before purchasing. The easy answer is to say you should buy one workcell license for every machine on the factory floor, but often this is not necessary. Some machines may not be connected to a control system that FactoryTalk Metrics can use for data collection, while other machines may not be considered critical enough for detailed monitoring.

    For a machine to be configured for FactoryTalk Metrics data collection, the following must be true at a minimum:

    • There is a production counter register in the control system for the machine.
    • There is an ideal cycle time, either fixed or by part number.
    • You are interested in reporting on the standard KPI’s (like OEE) for this machine.
    • When considering how many workcell licenses to buy, keep in mind:
    • Data collection for custom events is not licensed. If you are not interested in the standard KPIs for a machine but would like to gather some custom events, that machine does not have to be configured as a FactoryTalk Metrics workcell and consume a license. However, the custom events have to be associated with another workcell that is licensed.
    • Workcell licenses can be re-deployed as workcells are disabled or enabled. The total number of workcells enabled at any time cannot exceed the license count.
    • Many customers approach this question by commissioning a small area of the plant for a pilot application, and then make a determination on workcell count from that experience.

  • What is the difference between an FactoryTalk Metrics Authoring Client license and an FactoryTalk Single-User Runtime Client license?

    Users with FactoryTalk Runtime licenses can only view FactoryTalk Metrics (and FactoryTalk Historian) reports that have been created and stored in a FactoryTalk database. They can do this through the FactoryTalk Production Client, a Web browser, or an application with an embedded FactoryTalk ActiveX control. Clients with Runtime licenses cannot create or modify reports or components of reports. They cannot change the FactoryTalk Metrics or FactoryTalk Historian applications in any way, nor can they use the manual data entry capabilities of FactoryTalk Metrics. An FactoryTalk Metrics Authoring Client license is required in order to create, save, or change reports; to configure any aspects of the FactoryTalk Metrics application; and to perform manual data entry. Authoring licenses are also assigned to specific users, while users who do not have an Authoring license are automatically issued a Runtime license.

    Note: There is also an FactoryTalk Historian Authoring Client license, which is needed to configure an FactoryTalk Historian application. FactoryTalk Runtime licenses can be used with both FactoryTalk Historian and FactoryTalk Metrics.

  • What default Key Process Indicators (KPIs) does FactoryTalk Metrics provide? Can more be added?

    FactoryTalk Metrics provides 15 KPIs by default. Depending upon how the application is configured, some may not be available, but the complete list is:

    • OEE (Overall Equipment Effectiveness)
    • Availability %
    • Performance %
    • Quality %
    • MTBF (Mean Time Between Failure)
    • MTTR (Mean Time To Repair)
    • Failure Frequency Rate
    • Failure Rate
    • Available % (vs. Schedule)
    • Good Parts %
    • Scrap Parts %
    • Ideal Capacity
    • Running %
    • Downtime %
    • Fault %

    It is possible to add other KPIs that are based upon data that FactoryTalk Metrics collects. There are capabilities built into the product to add reporting fields that can be derived from collected FactoryTalk Metrics data.

  • What is required for users to view FactoryTalk Metrics reports with a Web browser?

    All reports created with the FactoryTalk Production Client are Web-enabled. Users can view these reports provided that:

    • They have Internet Explorer v6.0 SP1 installed
    • They are running a supported operating system (Windows NT 4 SP6+, Windows 2000 SP3+, Windows 2003 Server SE, or Windows XP SP1+)
    • They have downloaded the xxx.cab file from the FactoryTalk server (this is done automatically the first time they access the FactoryTalk QuickWeb)
    • They have a valid FactoryTalk user ID and password
    • There are available FactoryTalk Runtime Client licenses assigned to the FactoryTalk server

  • Is FactoryTalk Metrics applicable only to discrete manufacturing?

    FactoryTalk Metrics has a discrete bias in its terminology (e.g., part count and cycle time), but it can be used for continuous processes and has been used to monitor batch processes. The important element is to be able to determine a production count (which may be a calculation of gallons or square meters or pounds) and to be able to correlate the production count to an ideal cycle time (how many seconds to produce a gallon/square meter/pound).

  • Is FactoryTalk Metrics just an "OEE tool"?

    No, although it is a common misconception that FactoryTalk Metrics is just an "OEE tool." If this were the case, it would not be very useful. If all it did was report on the OEE score for the machines it monitored, it would not help you improve the performance of any of the machines.

    But FactoryTalk Metrics does far more than report on OEE scores. For starters, it reports on 14 other Key Performance Indicators (KPIs) by default. OEE and KPIs will tell you what your current machine performance is, but they will not tell you why your machines are inefficient. OEE data alone will not help you find and fix your problems and improve your processes. FactoryTalk Metrics can also collect and report on machine events of any type that occur on the manufacturing floor. So it can tell you definitively what your machines are doing and help you determine how to make them run more efficiently. This is where the real power of FactoryTalk Metrics lies. It is important to note that the events that FactoryTalk Metrics can monitor are not pre-determined, pre-configured, or limited in number. The events that are monitored are unique for each customer, simply because each plant has its unique requirements and problems. FactoryTalk Metrics events can also be added, deleted, or changed over time as problem areas are discovered and resolved. The most successful FactoryTalk Metrics applications are evolutionary in nature, and the product is intended to support your improvement efforts over the long haul.

• FactoryTalk Scheduler

  • What is FactoryTalk Scheduler?

    FactoryTalk Scheduler is a finite-capacity scheduling application that determines a detailed schedule for production resources. FactoryTalk Scheduler provides high-value solutions by considering constraints such as materials, tools, labor, bottlenecks, etc., when creating a schedule. Taking constraints into consideration allows for the creation of a realistic production schedule, rather than an impossible-to-meet schedule generated using theoretical infinite capacities. To name a few of the benefits, FactoryTalk Scheduler’s high-value solutions typically reduce inventories, reduce WIP, decrease cycle times, increase throughput, and reduce the need for overtime labor. Greater control of the production environment and greater visibility of the events on the plant floor will result in an increase in the most telling statistic —customer satisfaction.

  • What is S95?

    S95 is a standard from ISA that gives a common language and defines some standard data flows for Manufacturing Execution System (MES) functionality. FactoryTalk has standardized on S95 terminology and will adhere to future S95 XML schemas for integration with other enterprise systems.

  • What is the difference between the Professional and Standard Editions?

    The Professional Edition provides the full FactoryTalk Scheduler functionality and includes two viewers. The Standard Edition does not include the VB object models at the server side, which means that users cannot develop customized sequencing rules. It also does not include any viewers.

• FactoryTalk Batch

  • What is FactoryTalk Batch?

    FactoryTalk Batch captures, incorporates, and analyzes batch event data to help make consistent, high-quality batches.
    FactoryTalk Batch includes a comprehensive data model that provides customers with a simple way to analyze batch data. FactoryTalk Batch captures data and stores it in relational database format in the FactoryTalk database. From this database, customers can quickly generate and distribute reports on the data of production batches.

    FactoryTalk Batch can generate reports such as batch yields, material consumption, batch cycle times, and genealogy. Reports are built in HTML, so they can be generated and distributed automatically on Web pages or through email. By analyzing a wide range of process data, such as phase start and stop times and operator actions with temperatures, pressures, and flow rates, you can use the data to reduce process variability.

    FactoryTalk Batch comes with preconfigured reports that provide out-of-the-box reporting, and that can also be used as templates for customizing your own reports. FactoryTalk Batch will help reduce regulatory compliance costs by quickly and easily generating the process data reports required to meet industry standards.

  • What hardware, software, and services are included?

    FactoryTalk Batch includes:

    • FactoryTalk Historian tag license
    • 9358-BHIST01ENE 150 tags
    • 9358-BHIST02ENE 300 tags
    • 9358-BHIST03ENE 1500 tags
    • A Reporting Tag limited license for the FactoryTalk Production Server
    • License for Microsoft SQL Server 2000 Standard Edition
    • Embedded version of FactoryTalk Transaction Manager
    • License for one FactoryTalk Historian Authoring Client, which includes a SQL Server Client Access License (CAL)
    • FactoryTalk Batch Archiver license for the units or FactoryTalk Batch server size purchased. Includes a SQL Client Access License (CAL)

  • How does FactoryTalk Batch collect and store data?

    FactoryTalk Batch generates event files for every batch that is executed. The FactoryTalk Batch Archiver in FactoryTalk Batch reads these files and writes them to a table in the FactoryTalk database. The stored procedures in FactoryTalk Batch take this data and organize it into tables. From these tables, the data can be easily queried and retrieved using the FactoryTalk reporting tools or third party analysis packages.