RTPPM - How to use in manual mode?

[Sathishkumar_C]

In RTPPM, I have configured following models by simulating tags from Kepware.

• Models Configuration
• Downtime Model
• Production Model
• Waste Model
• Job Order Model
• Product Change Model

But, I have an usecase. I have machine running status from Kepware. The partcount, product is manually fed in to the system. Then how to configure RTPPM to support completely manual mode? And, I have only Product not Job Order. 

[mstarnaud · Accepted solution]

Hi Satishkumar

For all the models, you're required to create the properties and subscriptions even if you don't use tags. But when you're supposed to link the tag (on ProductRemoteTag for example), just leave the tag empty. This is because part of the code might still try to read or write in those properties, if the property does not exist then it could throw an error.

For the quantity tags, this should work fine : there's buttons to manually adjust the quantity in the Operator Dashboard screen.

However, for the Product and Joborder, I think it can work but I have never tried it before. Here is my suggestion. First, if you don't use Joborders in your server, I suggest that you go on Thing PTC.FSU.CORE.GlobalConfiguration.GlobalConfiguration_TG and check the RunWithoutWorkOrderInformation box. This makes all equipments run on "DefaultWorkOrder" instead of one provided by the tag, but most importantly it changes the Operator Dashboard screen so that the "Change joborder" button becomes "Change product" instead.

So you should now have a button in the Operator Dashboard screen to manually change products. And to create new products, you can go in the Configuration -> Products screen. And you may need to use the Equipment Assignment tab in that screen to link the products to your equipment : I'm not sure if the Operator Dashboard lets you choose any product or just the ones assigned to the equipment.

I'm sorry I won't have time to test this soon as the xmas vacations are starting - please be aware that there will be minimal support in the following days.

[Sathishkumar_C]

Thanks for the response.

• Marked "RunWithoutWorkOrderInformation" check box, it is running with DefaultJobOrder . But I'm not able to switch to other product (I'm able to see the 3 products assigned to this equipment).
• Since job order is not there, which tag I can use it for "Production Event" tag (ProductionEventRemoteTag) or how to approach this scenario? 
• If it is manual, downtime tag also needs to be removed from Kepware machine status?

[mstarnaud]

Marked "RunWithoutWorkOrderInformation" check box, it is running with DefaultJobOrder . But I'm not able to switch to other product (I'm able to see the 3 products assigned to this equipment).

I'm confused. Normally in the Operator Dashboard, it should change the top panel : it won't show the Joborder information and just show the product, and also the Start/Stop Joborder button should become Change Product. It should open a popup that allows you changing product. Which part of this is not working? Here is an example of what it should look like : 

Please not that in order for the buttons in the Operator Dashboard to work correctly, you still need the properties (like RunningJobOrder and JobOrderRemoteTag) in Composer. It's just that the tag (like the one for JobOrderRemoteTag) will not be bound. This is because part of the manual logic will simulate sending a tag value in those properties. If the button throws an error, it's probably because part of the configuration is missing.

Since job order is not there, which tag I can use it for "Production Event" tag (ProductionEventRemoteTag) or how to approach this scenario? 

 You can think of "Producton Event" like a batch. A batch has a name and a quantity. The ProductionEventRemoteTag is the name.

In the documentation, we explain that for this tag you have 2 choices. Choice #1 is to use the joborder as the batch name. Since you don't have joborders, I don't expect you to do this. Choice #2 is to have different tags : one for Productionevent and one for Joborder (and also, since you don't use Joborder, you can leave that one empty). If you are running completely manual and don't have a batch name tag, you can leave the tag empty but you still need the property & subscription to exist. Also if you don't regularly have tag values in ProductionEventRemoteTag, I suggest that you enable ProductionCompletionModel_Subscription. This will split your production events every 24h and avoid having very long events (very long events severely slow down the KPI calculations).

If it is manual, downtime tag also needs to be removed from Kepware machine status?

You can run manually, without the tag binding : there's buttons to create and modify downtimes in the Events -> Downtime screen and in the Operator Dashboard. I expect you will still need the configuration (properties, subscrptions) but can leave DowntimeByTag_DowntimeTag with no tag binding.

I still have not had time to test the Manual Mode button of the Operator Dashboard. But I expect it should work the same as leaving the tag empty.

[slangley]

Hi @Sathishkumar_C 

If you feel your question has been answered, please mark the appropriate response as the Accepted Solution for the benefit of others in the community.

Regards.

--Sharon