【正文】 rfaces it might be possible to develop I/O controllers which implement a field bus interface which allow the integration with mercial control systems. Once this level of integration is not possible custom frontend controllers like VME crates e into play. Besides the decision whether special I/O requires dedicated custom solutions one has to decide who will do which part of the work? Does for instance the necessity of VME crates prohibit the delivery of a ?turn key? system built by industry? Or does a PLC based frontend system require a mercial SCADA system for high level controls? Turn Key Systems It is a clear trend in industry to deliver turn key systems. It allows a modular design of the whole system. Individual ponents can be subcontracted to several panies and tested locally. Once delivered to the construction site the primary acceptance tests have already been passed and the second phase, to integrate the subsystem into the global control system begins. While the detailed specification of control loops etc. is now part of the subsystems contract, the customer has to specify clearly how much information of the subsystem must be made available, what the data structures will look like and which connection (field bus/ Ether) will be used. Most turn key systems are delivered with PLC?s. The construction of the Swiss Light Source (SLS) has shown that also a VME based I/O system running a CCS – in this case EPICS – can be successfully missioned [6]. PLC Based Systems 9 PLC based systems are a consequence of the turn key ansatz. The next obvious approach might be to look besides mercial PLC?s also for mercial SCADA systems. The advantage is clearly the same like for the PLC: stable software, no programming – only configuration, support and good documentation. At DESY we have successfully established a relation between the controls group which provides a CCS service based on EPICS and the utility group which uses the EPICS configuration tools to set up their control environment. The big advantage though being that the EPICS code can be adjusted to the special requirements from both sides. Industrial Solutions The difference between CCS solutions and mercial solutions is fading away as soon as industry starts to deliver and support collaborative control systems. At KEK a pany was contracted to supply programmers for the KEKB upgrade. These programmers were trained in writing drivers and application code for EPICS. As a result the KEKB control system is a mixture of software developed partly by industry and partly in house. This is another example for an industrial involvement for a CCS implementation. COST The question: “Was is the total cost of ownership (TCO) of a PC?” has kept people busy since PC?s exist. The answers vary to all extremes. The question what is the TCO of a control system might give similar results. If you go mercial you have to pay for the initial licenses the implementation which is typically carried out by the supplier or by a subcontractor, and you pay for the on going software support which might or might not include the update license fee. If you go for a collaborative approach, you might contract a pany or implement everything on your own. A question of ?time and money? as industry says. You will have more freedom and flexibility for your implementations but also a steeper learning curve. You can rely on the collaboration to provide new features and versions or you can contribute yourself. A major difference calculating the long term costs for a control system. At DESY one can roughly estimate that the (controls application)support for a mercial approach – here D/3 and the support for a collaborative approach – here EPICS is nearly the same. The software support and upgrade license fee is equivalent to one and a half FTE?s – which is about the manpower necessary to support new hardware and to upgrade EPICS. CONCLUSIONS Depending on the size and the requirements for a controls project the bination of mercial solutions and solutions based on a collaborative approach is possible in any rate between 0 and 100 percent. This applies for all levels from implementation to 10 long term support. Special requirements on safety issues or a lack of manpower might turn the scale mercial. The necessity to interface special hardware, special timing requirements, the ?having the code in my hands? argument or the initial costs for mercial solutions will turn the scale collaborative. As long as collaborative approaches like EPICS stay up to date and run as stable and robust as mercial solutions, both will keep their position in the controls world in a plementary symbiosis. 11 外文資料翻譯 外文翻譯譯文 工業(yè)控制系統(tǒng)和協(xié)同控制系統(tǒng) 當(dāng)今的控制系統(tǒng)被廣泛運(yùn)用于許多領(lǐng)域。 control records like PID etc.。而且，實(shí)踐表明，經(jīng)濟(jì)和社會(huì)因素也對(duì)此很重要。能夠親自接觸源碼并可以更快速地解決問(wèn)題是家庭控制系統(tǒng)的要求。 引言： 80年代早期，隨著為 HERA(HadronElektronRingAnlage)加速器安裝低溫控制系統(tǒng)，德國(guó)電子同步加速器研究所普遍開(kāi)始研究過(guò)程控制。 有必要增加接口解決總線問(wèn)題并增加運(yùn)算能力，以便于低溫控制。 由于對(duì)它的應(yīng)用相當(dāng)成功，其還被運(yùn)用于正在尋找一個(gè)通用的解決方案以監(jiān)督他們的分布式 PLC的公共事業(yè)管理。制約系統(tǒng)的大小的因素不是 I / O的總數(shù)，通信網(wǎng)絡(luò)的暢通與否。該項(xiàng)目包括安裝功能的完全更換。在供應(yīng)商網(wǎng)站上的最后驗(yàn)收測(cè)試又出現(xiàn)了戲劇性的性能問(wèn)題。每個(gè)數(shù)字和模擬輸入和輸出通道在 D / 3系統(tǒng)里的自身報(bào)警限值也被低估了。升級(jí)的 D / 3系統(tǒng)是唯一可能的解決辦法?，F(xiàn)有的系統(tǒng)是由 H1 合作組的幾名成員開(kāi)發(fā)的，而現(xiàn)在卻難以維持了。它收集的數(shù)據(jù)主要是由 I/ O設(shè)備提供。 SCADA 系統(tǒng)的一個(gè)主要缺點(diǎn)是其中的兩個(gè)數(shù)據(jù)庫(kù)，一個(gè)為 PLC’ s 服務(wù)，另一個(gè)為 SCADA系統(tǒng)服務(wù)，這兩個(gè)數(shù)據(jù)庫(kù)必須維持。此外，通過(guò) Industry Pack（ IP）模塊的手段，它還能運(yùn)用于通過(guò) VME板卡的任何數(shù)據(jù)。 IOC向客戶提供接口并采集數(shù)據(jù)。所有的配置文件（圖形工具，報(bào)警處理程序和歸檔）提供了一種靈活的配置方案。 IOC提供所有功能 DCS系統(tǒng)要求，如：實(shí)施每個(gè)記錄的標(biāo)準(zhǔn)的屬性；執(zhí)行每個(gè)記錄時(shí)的報(bào)警檢查過(guò)程；控制記錄，如 PID。 13 PLC’ s： PLC’ s 同樣提供豐富的功能，因?yàn)橐郧八仟?dú)一無(wú)二的控制系統(tǒng)。 PLC’ s對(duì)于分布式 I / O已不再重要。在這里，我們?cè)噲D總結(jié)不同控制方法的基本功能。例如確定通信協(xié)議和最后在顯示、報(bào)警和歸檔方案，一個(gè)控件的所有屬性像 P， I和 D參數(shù)，還有報(bào)警限制及其他附加的屬性必須得到解決。 頻率 /國(guó)家計(jì)劃 在控制系統(tǒng)中，頻率程序可以運(yùn)行任何處理器。國(guó)家機(jī)器的基本功能在 IEC 61131中得到了落實(shí)。配置特定驅(qū)動(dòng)器和數(shù)據(jù)轉(zhuǎn)換器的集成硬件在商業(yè)環(huán)境中是一個(gè)難點(diǎn)