“Every company in every location wants their own instance of the software installed because of things like performance and control of data, says Steve Bashada, vice president of TeamCenter Applications with Siemens PLM. “But it’s very expensive having to synchronize all that data and back it up.”
Bashada peer-to-pee的普遍性r approach over the past decade or more is leading all the top tier manufacturers he’s worked with recently to focus on the reduction of their total software instances, to get to between three and eight. In such reduced- instance deployments, one site typically serves as the lead site with all relevant options deployed, and the other sites have specific portions of the software deployed as needed, based on their role in the collaboration.
A more extreme option is to have one central site where the instance is deployed and the other sites simply have relevant access to it. “In these cases, the data has to be very open, with high levels of connectivity performance,” Bashada says. “The use of Cisco routers helps with this, so only a minimal amount of data needs to be transferred when changes take place.”
尽管中央地点方法具有明显的优势，但巴沙达说，大多数公司不会走那么远，而是采用中间地面方法，以便他们可以对特定实例有更多的控制权。
但是，随着该位置控制的水平，同步问题。由于大多数跨地理合作都涉及以24/7/365全球运营的大型公司，因此系统同步的时间很少。
巴沙达说：“您甚至无法在一夜之间同步数据。”
侧边栏：阅读2011年12月号的“成功合作制造业的障碍”。访问www.myenum.com/roadblocks-successful-collaborative-manufacturing
