Skip to main content
B
bwinslow241-Visitor
1-Visitor
October 16, 2018
Solved

Using Remote Database Template with Manufacturing App

  • October 16, 2018
  • 2 replies
  • 4238 views

Hi,

 

We currently are trying to create custom templates that extend the PTC.ISA95.PhysicalAssetThingTemplate so we have our Things in Manufacturing App. Most of our templates extend RemoteThingWithTunnelsAndFileTransfer. From what I can see all the functionality we need can be accomplished with the PhysicalAssetThingTemplate. However, we have one template that extends the RemoteDatabase. If we have this template extend the PhysicalAssetThingTemplate, will we be able to connect to the remote database? If not, is there any work arounds?

 

Thanks,

Brandon Winslow

 
Best answer by mthakker

Hey Brandon,

 

There's probably two different ways for you to do this.  Way #1 would be to do some form of local binding from your remote database Thing over to a new Thing with the PTC.ISA95.PhysicalAssetThingTemplate.  I wouldn't recommend this.

 

Instead, you could implement the same ThingShapes that are on the PTC.ISA95.PhysicalAssetThingTemplate - we query by those rather than by just the template.  This would also give you fine grained control over what data you want on the Remote database, rather than a big bang of getting everything.

 

Thanks,

 

Milan

2 replies

H
hrajpal5-Regular Member
5-Regular Member
October 18, 2018

Greetings Brandson,

 

PhysicalAssetThingTemplate do not have remote database template functionality.

 

Regards,

Himesh Rajpal

M
mthakker5-Regular Member
5-Regular Member
October 18, 2018

Hey Brandon,

 

Can you tell us a little bit more about the use case that you have here?  What exactly are you trying to do?

 

Thanks,

 

Milan

B
bwinslow241-VisitorAuthor
1-Visitor
October 19, 2018

Hey Milan,

 

Currently we have two separate things to represent our machines. We have our things with our custom thing template and the "Asset_" thing that is created when you create an asset in Manufacturing App. We have just upgraded to 8.3 from 8.0. We now want to eliminate this duplicate "Asset_" thing. The way we can do this is create new templates that have a base template of PTC.ISA95.PhysicalAssetThingTemplate. This is perfect for 95% of our templates because they currently have a base template of RemoteThingWithTunnelsAndFileTransfer. However, we have one template that extends RemoteDatabase. I am trying to figure out how to eliminate the Duplicate "Asset_" thing for these machines as well. Is there a Remote Database Thing Shape that I could implement in order to have our template, which will now have a base template of PTC.ISA95.PhysicalAssetThingTemplate, have the functionality of being able to query a remote database?

 

Thanks,

Brandon 

 
M
mthakker5-Regular MemberAnswer
5-Regular Member
October 19, 2018

Hey Brandon,

 

There's probably two different ways for you to do this.  Way #1 would be to do some form of local binding from your remote database Thing over to a new Thing with the PTC.ISA95.PhysicalAssetThingTemplate.  I wouldn't recommend this.

 

Instead, you could implement the same ThingShapes that are on the PTC.ISA95.PhysicalAssetThingTemplate - we query by those rather than by just the template.  This would also give you fine grained control over what data you want on the Remote database, rather than a big bang of getting everything.

 

Thanks,

 

Milan

Terms & ConditionsCookie settingsAccessibility statement