The best practice to supporting multiple sites for Thingworx SCO

[seanccc]

Hi, 

My customer has 5 factories , he has purchased one ThingWorx SCO and deployed it in factory A1.  

Now the customer wants to use the ThingWorx in the other 4 factories(A2 ~ A4),  the options could be : 

1.   Reuse the single ThingWorx Server 

Buy more licensed users for the current ThingWorx SCO , deploy the SDK agent in the 4 factories to collect data and  all of the factories share the single ThingWorx server in factory A1.  The data of the 5 factories are visible to each other . 

2.   Deploy separated ThingWorx Servers w/o Federation

Buy more licensed users for the current ThingWorx SCO , deploy the SDK agent and ThingWorx server in the 4 factories as well.   The data of the 5 factories are separated . 

3.   Deploy separated ThingWorx Servers with Federation

Buy more licensed users for the current ThingWorx SCO , deploy the SDK agent and ThingWorx server in the 4 factories as well, meanwhile, use ThingWorx Federation to share some data.

4.   Buy another 4 suites of ThingWorx SCO.  

I wonder if  #1, #2, #3 are in compliance , or only #4 is in compliance ? 

Regards,

Sean

[slangley · Accepted solution]

Hi @seanccc.

There are many things to consider in making a decision such as this:  volume, # of users, etc.  And it would require more analysis than that which can be performed through a community post. 

Please reach out to your Partner or Sales rep to guide you in making the appropriate decision for your customer.

Regards.

--Sharon