Frequently Asked Questions

Questions and Answers

1. How many PI tags does RtDuet consume?
   • Approximately five (5) tags per machine centre, plus an additional tag for each sub equipment and reason.
2. Does ADM install RtDuet and/or design and implement downtime and OEE projects?
   • Yes. Just contact us for implementation quote.
3. With the purchase of RtDuet can I get software maintenance, installation and system integration support?
   • Yes.
4. Can we split an event in two or can we merge two events into one?
   • The current version allows for a split into finite events however the merge capability will not be available until fall 2006.
5. Would you only apply this to bottle-neck steps in your process?
   • No, RtDuet can be used to monitor any aspect of a plant. Standalone, in process, or even non process related machine centres can be defined. Because our system offers the ability of creating and defining a machine centre without PI Tags in combination with the manual input capability we have no limitations to what we can use our system for. One good example is to define a machine centre for Safety infractions and manually put in the individual events. RtDuet then offers very nice reports on all events and keeps the record within PI. RtDuet can be adapted to any event tracking system. Also, because of the flexibility of our DTM module we can synchronize this data with other MDAC compatible data sources thus removing the limitation of database programming while standardizing the user interface and access via a web browser.
6. How many contexts can be created?
   • There is no fixed limit to what RtDuet allows. The limit is really what your PI System will allow if you have sufficient tag licensing for the contexts. We are currently running a system in Phoenix with over 500 contexts running.
7. Can validation be operator specific - via password?
   • Yes, users and access restrictions can be made user by user or by NT group. Each record also records who validated it and when.
8. Can lost time be also calculated as lost equivalent production?
   • Yes, if there is a theoretical rate for when the equipment is scheduled to run we can calculate the lost production.
9. Where are the reason trees stored?
   • The reason tree is currently stored within the PI-Module database reason tree under the %OSI.
10. What if I just want to buy the software and use a local integrator?
    • That is fine. RtDuet is sold as a product and we offer support options for local integration programs.
11. Is it possible to link with SAP?
    • Yes, we have the DTM module which offers synchronization to any offline copy of an MDAC Compatible database. This database can then be used as a staging ground for linking with SAP. Also, ADM is working with OSI to develop a standard interface to SAP using their RLink interface.
12. How can we track set-up time or events prior to the equipment running that are not easily tracked by a PI tag?
    • RtDuet allows for the manual input of events. All records are created exactly the same if they are created manually via the Web Base screens or by the ACE Modules. The system allows for the transition of manual events to auto events for the same machine centre. So if there is a machine that currently has no connection to PI and will in the future then there will be no recognizable difference between the records other than the fact they will be flagged as Manual vs. Auto. All manual events get reports thru the same reporting engine and all calculations are done on these events as well.
13. Can downtime reasons be tagged automatically from a PLC? Also, if tagging manually, is the length of the downtime tagged automatically?
    • Yes, RtDuet allows for the tracking of unlimited auxiliary reporting tags. At the start of an event, RtDuet captures the value of these tags and then again at the closing of an event. This feature is very useful for automatically capturing items like reason codes in a PLC, production numbers, scrap numbers, and other data maybe not related to the machine centre directly.
14. How would you record a cause for a production rate reduction?
    • Depending on how much detail is required if the tag event triggering the RtDuet record is the true cause then we have it at that level, we record the trigger tag name its value. RtDuet also allows for operator inputs to indicate what the cause was. RtDuet allows for the recording of auxiliary tags for things like PLC Reason codes, and other tag values surrounding an event.
15. When quality data is entered, does the OEE just get calculated after the fact?
    • Because of the nature of ACE, OEE is calculated every time an event occurs and then gets recalculated if out of order events arrive like lab values. So the OEE number will continuously adjust itself until all data had arrived.