最近，以 Web Service 技術(http://www.w3.org/TR/ws-arch/)為基礎的服 務導向架構(Service Oriented Architecture，SOA)開始興起(Huhns and Singh 2005; Papazoglou and Georgakopoulos 2003)，希望每一個資訊服務都能像日常 生活的電話和水電一般，能夠很方便使用它。
服務導向架構的基礎包含一個服務註冊(registry)與服務發現(discovery) 的機制，期望所有可以對外提供的資訊服務都能註冊，期望能夠自動搜尋已註冊 的服務，然後迅速開發新的服務出來，未來我們將思考如何融合軟體代理人的技 術及服務導向架構的精神，在符合企業資訊安全政策的前提下，建立一個自動化 的機制和一個整合的基礎環境，讓資訊系統可以去搜尋所有服務提供者代理人和 資訊發佈代理人的所提供的服務，並可以自動向資訊發佈代理人註冊，訂閱資訊。
另外，制定服務描述語言，透過一種標準化的語意和語法來描述服務，進一 步建立服務組裝工廠(或是智慧型決策中心)的機制，也是另一個值得研究的方 向。在這樣的理想下，當外界有新服務的需求時，服務組裝工廠就能分析需求，
然後派遣軟體代理人搜尋合適的服務介面，以完全自動化的方式組裝出新的服務 來滿足新需求，可以讓整個新服務的開發，更快、更有效率。
參 考 文 獻
1. 李瓊芬譯，2000，『新世代的客服中心趨勢』，電子化企業經理人報告，第七 期，9-17 頁。
2. 吳秀蘭，2005，『探討中華電信導入顧客關係管理之研究』，國立交通大學，
管理學院碩士在職專班經營管理組碩士論文。
3. 吳姝倩，2001，『台灣客服中心的現況發展與未來趨勢』，電子化企業經理人 報告，第二十一期，10-24 頁。
4. 陳曉開譯，Jill Dyche 著，2003，客戶關係管理手冊，台北，台灣培生教育 出版股份有限公司。
5. 黃秀媛譯，W. Chan Kim, and Renee Mauborgne 著，2005，藍海策略，開創 無人競爭的全新市場，台北，天下遠見出版股份有限公司。
6. 黃貝玲，2001，『從 Call Center 到 Contact Center』，電子化企業經理人報告，
第二十一期， 29-38 頁。
7. 覃笑風譯，Frederick F. Reichheld 著，2004，『顧客忠誠成長之始』，哈佛商 業評論中文版，第二十八期， 46-56 頁。
8. 楊鴻儒譯，日本人力資源學院(HR Institude)著，2001，CRM 戰略執行手冊，
9. 劉復苓、邱天欣譯，John G. Freeland 著，2003，CRM 關鍵 32 堂課，台北，
美商麥格羅․希爾國際股份有限公司 台灣分公司。
10. 蘇隄，1998，『資料倉儲的應用與技術』，資訊與電腦， 2 月號，78-89 頁。
11. Avison, D., and Fitzgerald, G., “Information Systems Development:
Methodologies, Techniques, and Tools”, McGraw Hill, London, UK, 1995.
12. Baek, S., Liebowiz, J., Prasad, S. Y., and Granger, M., “Intelligent Agents for Knowledge Management-Toward Intelligent Web-Based Collaboration within Virtual Teams”, Knowledge Management Handbook, Chapter 11, CRC Press, 1999.
13. Berry, M.J.A., and Linoff, G., “Data Mining Techniques for Marketing, Sales, and Customer Support”, Wiley, New York, 1997.
14. Chan, C. W., Chen, Lin-Li, and Geng, Liqiang, “Knowledge Engineering for An Intelligent Case-Based System for Help Desk Operations”, Expert Systems with Application, vol. 18, 2000, pp.125-132.
15. Chaudhuri, S., and Dayal, U., ”An Overview of Data Warehousing and OLAP Technology”, SIGMOD Record, Vol. 26, No. 1, March 1997.
16. Davenport, T. H., “Putting the Enterprise into the Enterprise System”, Harvard
Business Review, July-Aug. 1998, pp.121-131.
17. Davenport, T. H., Long, D. W. D., and Beers, M. C., “Successful Knowledge Management Projects”, Sloan Management Review, Winter 1998, pp. 43-57.
18. Davenport, T. H., and Prusak, L., “Working Knowledge: How Organizations Manage What They Know”, Harvard Business School Press, Boston MA, 1998.
19. Gillies, C., Rigby, D. K., and Reichheld, F. F., “The Story Behind Successful Customer Relations Management”, European Business Journal, vol. 14, iss. 2, 2002, pp.73-77.
20. Glushko, R. J., Tenenbaum, J. M., and Meltzer, B., “An XML framework for Agent-based E-commerce”, Communications of ACM, Vol. 42, No. 3, March 1999, pp.106-114.
21. Grover, V., and Davenport, T. H., “General Perspectives on Knowledge Management: Fostering a Research Agenda”, Journal of Management Information Systems, Vol. 18, No. 1, Summer 2001, pp. 5-21.
22. Hattori, F., Ohguro, T., Yokoo, M., Matsubara, S., and Yoshida, S., “Socialware:
Multiagent Systems for Supporting Network Communities”, Communications of ACM, Vol. 42, No. 3, March 1999, pp. 55-61.
23. Huhns, M. N., and Singh, M. P., “Service-Oriented Computing: Key Concepts and Principles”, IEEE Internet Computing, Jan./Feb. 2005, pp. 75-81.
24. Inmon, W. H., “Building the Data Warehouse”, 3rd Edition, Wiley, New York, 2002.
25. Irani, Z., Themistocleous, M., and Love, P. E.D., “The Impact of Enterprise Application Integration on Information System Lifecycles”, Information &
Management, vol. 41, 2003, pp. 177-187.
26. Jennings, N. R., “An Agent-Based Approach for Building Complex Software Systems”, Communications of The ACM, vol.44, no.4, April 2001, pp.35-41.
27. Kautz, H., Selman, B., and Shah, M., “Referral Web: Combining Social
Networks and Collaborative Filtering”, Communications of ACM, Vol. 40, No. 3, March 1997, pp. 63-72.
28. Ketler, K., “Case-based Reasoning: An Introduction”, Expert Systems with Applications, Vol. 6, 1993, pp. 3-8.
29. Kimball, R. and Ross, M., “The Data Warehouse Toolkit: The Complete Guide to Dimensional Modeling”, 2nd edition, Wiley, New York, 2002.
30. Kobayashi, T., Tamaki, M., and Komoda, N., “Business process integration as a
solution to the implementation of supply chain management systems”, Information & Management, vol. 40, 2003, pp.769-780.
31. Lee, J., Siau, K., and Hong, S., “Enterprise Integration with ERP and EAI”, Communications of ACM, Vol. 46, No. 6, Feb. 2003, pp. 55-60.
32. Maes, P., “Agents That Reduce Work and Information Overload”, Communications of ACM, Vol. 37, No. 7, 1994, pp.31-40.
33. Maes, P., Guttman, R. H., and Moukas, A. G., “Agents That Buy and Sell”, Communications of ACM, Vol. 42, No. 3, March 1999, pp.81-91.
34. Massey, A. P., Montoya-Weiss, M. M., and Holcom, K., “Re-engineering the Customer Relationship: Leveraging Knowledge Assets at IBM”, Decision Support Systems, vol.32, 2001, pp.155-170
35. Nonaka, I., “The Knowledge Creating Company”, Harvard Business Review, Vol.
79, No. 6, 1991, pp. 96-104.
36. Nonaka, I., and Takeuchi, H., “The Knowledge Creating Company: How Japanese Companies Create the Dynamics of Innovation”, Oxford University Press, 1995.
37. O’Dell, C., and Grayson, C.J., “If only we knew what we know: Identification
and Transfer of Internal Best Practices”, California Management Review, Vol. 40, No. 3, 1998, pp. 154-174.
38. Papazoglou, M. P., “Agent-Oriented Technology in Support of e-Business”, Communications of The ACM, vol.44, no.4, April 2001, pp.71-77.
39. Papazoglou, M.P., “Service-Oriented Computing: Concepts, Characteristics and Directions”, IEEE Proceedings of the Fourth International Conference on Web Information Systems Engineering (WISE’03), 2003.
40. Peppers, D. & Rogers, M., “Is your company ready for one-to-one marketing”, Harvard Business Review 1999, pp. 151-160.
41. Reichheld, F. F., and Teal, T.A., “The Loyalty Effect: The Hidden Force Behind Groeth, Profits, and Lastting Values”, Harvard Business School Press, Boston, MA, 1996.
42. Rigby, D. K., Reichheld, F. F., and Schefter, P., “Avoid the Four Perils of CRM”, Harvard Business Review, Feb. 2002, pp.101-109.
43. Sen, A., and Sinha, A. P., “A comparison of Data Warehousing Methodologies”, Communications of The ACM, Vol. 48, No. 3, March 2005, pp. 79-84.
44. Shaw, M. J., Subramaniam, C., Tan, G. W., and Welge, M. E., “Knowledge
Management and Data Mining for Marketing”, Decision Support Systems, vol.
31, 2001, pp. 127-137.
45. Watson, I., and Marir, F., “Case-based Reasoning: A Review”, The Knowledge Engineering Review, Vol. 9, No. 4, 1994, pp. 327-354.
46. “Extensible Markup Language (XML) 1.0 (Second Edition)”, W3C Recommendation, 6 Oct. 2000 (See
http://www.w3.org/TR/2000/REC-xml-20001006.)
47. “State of the CIO 2006 - Research Reports”, CIO Magazine, 2006, http://www2.cio.com/research/surveyreport.cfm?id=101
48. “Web Services Architecture”, W3C Working Group Note, 11 Feb. 2004, (see http://www.w3.org/TR/ws-arch/)
附錄、資訊系統服務介面設計參考資料
表 A- 1、請求『障礙申訴』服務的合約內容
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="Request">
<xs:complexType>
</xs:element>
<xs:element name="Head">
<xs:complexType>
</xs:element>
<xs:element name="SourceSystemID" type="xs:NCName"/>
<xs:element name="SourceMessageID" type="xs:NCName"/>
<xs:element name="DestSystemID" type="xs:NCName"/>
<xs:element name="ServiceName" type="xs:NCName"/>
<xs:element name="Body">
<xs:complexType>
</xs:element>
<xs:element name="ResourceNum" type="xs:NMTOKEN"/>
<xs:element name="ProblemCode" type="xs:NCName"/>
<xs:element name="ProblemNote" type="xs:NCName"/>
</xs:schema>
訊息範例
<Request>
<Head>
<SourceSystemID>SC</SourceSystemID>
<SourceMessageID>SC1009876</SourceMessageID>
<DestSystemID>PH</DestSystemID>
<ServiceName>RegisterTrouble</ServiceName>
</Head>
<Body>
<ResourceNum>225D825123</ResourceNum>
<ProblemCode>NOP</ProblemCode>
<ProblemNote>時斷時續</ProblemNote>
</Body>
</Request>
表 A- 2、『障礙申訴』服務回應的合約內容
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="Response">
<xs:complexType>
</xs:element>
<xs:element name="Head">
<xs:complexType>
</xs:element>
<xs:element name="SourceSystemID" type="xs:NCName"/>
<xs:element name="DestSystemID" type="xs:NCName"/>
<xs:element name="DestMessageID" type="xs:NCName"/>
<xs:element name="ServiceName" type="xs:NCName"/>
<xs:element name="Body">
<xs:complexType>
</xs:element>
<xs:element name="Result" type="xs:boolean"/>
<xs:element name="ResultNote" type="xs:NCName"/>
</xs:schema>
訊息範例
<Response>
<Head>
<SourceSystemID>PH</SourceSystemID>
<DestSystemID>SC</DestSystemID>
<DestMessageID>SC1009876</DestMessageID>
<ServiceName>RegisterTrouble</ServiceName>
</Head>
<Body>
<Result>false</Result>
<ResultNote>欠費停話</ResultNote>
</Body>
</Response>
表 A- 3、請求『查詢障礙處理進度』服務的合約內容
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="Request">
<xs:complexType>
</xs:element>
<xs:element name="Head">
<xs:complexType>
</xs:element>
<xs:element name="SourceSystemID" type="xs:NCName"/>
<xs:element name="SourceMessageID" type="xs:NCName"/>
<xs:element name="DestSystemID" type="xs:NCName"/>
<xs:element name="ServiceName" type="xs:NCName"/>
<xs:element name="Body">
<xs:complexType>
</xs:element>
<xs:element name="EnterpriseID" type="xs:NCName"/>
<xs:element name="EnterpriseName" type="xs:NCName"/>
</xs:schema>
訊息範例
<Request>
<Head>
<SourceSystemID>SC</SourceSystemID>
<SourceMessageID>SC1001234</SourceMessageID>
<DestSystemID>PH</DestSystemID>
<ServiceName>TrackStatus</ServiceName>
</Head>
<Body>
<EnterpriseID>A987654321</EnterpriseID>
<EnterpriseName>中國信託銀行</EnterpriseName>
</Body>
</Request>
表 A- 4、『查詢障礙處理進度』服務回應的合約內容
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="Response">
<xs:complexType>
</xs:element>
<xs:element name="Head">
<xs:complexType>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="SourceSystemID" type="xs:NCName"/>
<xs:element name="DestSystemID" type="xs:NCName"/>
<xs:element name="DestMessageID" type="xs:NCName"/>
<xs:element name="ServiceName" type="xs:NCName"/>
<xs:element name="Body">
<xs:complexType>
<xs:sequence>
<xs:element ref="TroubleList" />
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="TroubleList">
<xs:complexType>
<xs:sequence>
<xs:element minOccurs="0" maxOccurs="unbounded"
ref="TroubleTicket" />
</xs:sequence>
<xs:attribute name="NumOfTickets" use="required"
type="xs:integer"/>
</xs:complexType>
</xs:element>
<xs:element name="TroubleTicket">
<xs:complexType>
<xs:element name="TicketID" type="xs:NCName"/>
<xs:element name="TicketTime" type="xs:string"/>
<xs:element name="ResourceNum" type="xs:NMTOKEN"/>
<xs:element name="RootCauseID" type="xs:NCName"/>
<xs:element name="RootCauseName" type="xs:NCName"/>
<xs:element name="Status" type="xs:NCName"/>
<xs:element name="StaffName" type="xs:NCName"/>
<xs:element name="StaffMobile" type="xs:string"/>
</xs:schema>
訊息範例
<Response>
<Head>
<SourceSystemID>PH</SourceSystemID>
<DestSystemID>SC</DestSystemID>
<DestMessageID>SC1001234</DestMessageID>
<ServiceName>TrackStatus</ServiceName>
</Head>
<Body>
<TroubleList NumOfTickets="2">
<TroubleTicket>
<TicketID>TP12345678</TicketID>
<TicketTime>95-05-18 10:00</TicketTime>
<ResourceNum>02-23445678</ResourceNum>
<RootCauseID>DC</RootCauseID>
<RootCauseName>斷線</RootCauseName>
<Status>測試中</Status>
<StaffName>葉文宏</StaffName>
<StaffMobile>0933123456</StaffMobile>
</TroubleTicket>
<TroubleTicket>
<TicketID>TC23456789</TicketID>
<TicketTime>95-05-18 12:10</TicketTime>
<ResourceNum>04-22445566</ResourceNum>
<RootCauseID>DCX</RootCauseID>
<RootCauseName>時斷時續</RootCauseName>
<Status>查修人員處理中</Status>
<StaffName>文宏</StaffName>
<StaffMobile>0933654321</StaffMobile>
</TroubleTicket>
</TroubleList>
</Body>
</Response>
表 A- 5、發佈『電路服務狀態』服務的合約內容
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="Publish">
<xs:complexType>
</xs:element>
<xs:element name="Head">
<xs:complexType>
</xs:element>
<xs:element name="SourceSystemID" type="xs:NCName"/>
<xs:element name="SourceMessageID" type="xs:NCName"/>
<xs:element name="DestSystemID" type="xs:string"/>
<xs:element name="ServiceName" type="xs:NCName"/>
<xs:element name="Body">
<xs:complexType>
<xs:sequence>
<xs:element ref="ResourceNum"/>
<xs:element ref="Customer"/>
<xs:element ref="CustomerAddr"/>
<xs:element ref="ServiceState"/>
<xs:element ref="TimeOfStateChanged"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="ResourceNum" type="xs:NMTOKEN"/>
<xs:element name="Customer">
<xs:complexType>
</xs:element>
<xs:element name="CustomerAddr" type="xs:NCName"/>
<xs:element name="ServiceState">
<xs:complexType>
</xs:element>
<xs:element name="TimeOfStateChanged" type="xs:string"/>
</xs:schema>
訊息範例
<Publish>
<Head>
<SourceSystemID>BILL</SourceSystemID>
<SourceMessageID>BL12345678</SourceMessageID>
<DestSystemID>*</DestSystemID>
<ServiceName>ServiceStateChanged</ServiceName>
</Head>
<Body>
<ResourceNum>225D825123</ResourceNum>
<Customer id="A987654321">中國信託銀行</Customer>
<CustomerAddr>台北市信義路100號</CustomerAddr>
<ServiceState code="suspend">欠費停話</ServiceState>
<TimeOfStateChanged>95-05-19 10:10</TimeOfStateChanged>
</Body>
</Publish>
表 A- 6、發佈『資源調整作業資訊』服務的合約內容
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified">
<xs:element name="Publish">
<xs:complexType>
</xs:element>
<xs:element name="Head">
<xs:complexType>
</xs:element>
<xs:element name="SourceSystemID" type="xs:NCName"/>
<xs:element name="SourceMessageID" type="xs:NCName"/>
<xs:element name="DestSystemID" type="xs:string"/>
<xs:element name="ServiceName" type="xs:NCName"/>
<xs:element name="Body">
<xs:complexType>
<xs:sequence>
<xs:element ref="StartTime"/>
<xs:element ref="EstimateFinishTime"/>
<xs:element ref="ClosedTime"/>
<xs:element ref="ResourceState"/>
<xs:element ref="EffectedResources"/>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="StartTime" type="xs:string"/>
<xs:element name="EstimateFinishTime" type="xs:string"/>
<xs:element name="ClosedTime" type="xs:string"/>
<xs:element name="ResourceState">
<xs:complexType>
</xs:element>
<xs:element name="EffectedResources">
<xs:complexType>
<xs:sequence>
<xs:element maxOccurs="unbounded" ref="ResourceNum"/>
</xs:sequence>
<xs:attribute name="size" use="required"
type="xs:integer"/>
</xs:complexType>
</xs:element>
<xs:element name="ResourceNum" type="xs:NMTOKEN"/>
</xs:schema>
訊息範例
<Publish>
<Head>
<SourceSystemID>RM</SourceSystemID>
<SourceMessageID>RM12345678</SourceMessageID>
<SourceMessageID>RM12345678</SourceMessageID>