• 沒有找到結果。

An XML based supply chain integration hub for green product lifecycle management

N/A
N/A
Protected

Academic year: 2021

Share "An XML based supply chain integration hub for green product lifecycle management"

Copied!
10
0
0

加載中.... (立即查看全文)

全文

(1)

An XML based supply chain integration hub for green product lifecycle management

Fataneh Taghaboni-Dutta

a,*

, Amy J.C. Trappey

b,c

, Charles V. Trappey

d

a

Department of Business Administration, College of Business, University of Illinois at Urbana-Champaign, 350 Wohlers Hall, MC-706, 1206 S. Sixth Street Champaign, IL 61820, USA

b

Department of Industrial Engineering and Management, National Taipei University of Technology, Taipei 10608, Taiwan c

Department of Industrial Engineering and Engineering Management, National Tsing Hua University, Hsinchu 300, Taiwan d

Department of Management Science, National Chiao Tung University, 1001 Ta Hsueh Road, Hsinchu 30010, Taiwan, ROC

a r t i c l e

i n f o

Keywords: Green design Green component

Product lifecycle management XML

Mapping hub

a b s t r a c t

The emergence of new regulations for the disposal of electrical and electronic equipment, directives on the use of certain hazardous substances, and the Kyoto Protocol are changing industries approach to product design and manufacturing. Traditionally, product lifecycle management systems provide a plat-form for the management of data related to the creation and disposal of products. These systems assist the participants of the products’ life cycle processes (manufacturers, suppliers, customers, and regulators) to use data efficiently for planning and control. However, most data collected do not resolve the environ-mental issues which arise when selling the products or arranging the products to be replaced and dis-posed. In this paper, we present an Integrated Green Parts Information Platform (IGPIP) framework (The frame work revisited here was published as ‘‘A Framework for a Green Product Lifecycle Manage-ment System”, Issues in Information Systems, Vol. IX, No. (2), 2008, 123–131.) and a working prototype of the system. This system uses XML file transmission to improve the quality, cost and time-to market issues for green designs.

Ó 2010 Elsevier Ltd. All rights reserved.

1. Introduction

In June of 1992, the United Nations held a conference on Envi-ronment and Development in Rio de Janeiro. The goal of this con-ference was to gather policy makers and arrive at a general consensus to limit pollution at its source which includes product inception and manufacture. Thus, the environmental scientists’ task is no longer limited to the post event management of environ-mental pollution, but also to determine sources, control, repair, and effectively stop environmental pollution. The Society of Man-ufacturing Engineers (SME, 1996) also supports green technology with the aim of controlling pollution by taking into account the im-pact of products on the environment during the design phase. The environment is not only impacted by the use of resources to man-ufacture the product but also by its use by the consumer and finally its disassembly and disposal. On July of 2006 the Restrictions of Hazardous Substances directives (RoHS, 2006) went into effect. Although this law only applied to the European industries, its implication on supply chain is global. The RoHS regulations will re-quire all manufacturers in Europe to evaluate their supply chain; thus complicating the supplier selection problem. Sony spent more than $80 million to replace its playstation cables which had higher

cadmium than permitted by the Netherlands environmental laws – which is very close to the RoHS standards (Busch, 2007). In the push to become green, researchers have expanded the multi-crite-ria decision model for supplier selection to include the green per-formance criteria (Lee, Kang, Hsu, & Hung, 2009).

The US Environmental Protection Agency (US Environmental Protection Agency website, 2009) describes green engineering as the design, commercialization, and use of processes and products which are feasible and economical while minimizing (1) genera-tion of pollugenera-tion at the beginning and (2) the risk to human health and the environment. Green engineering embraces the concept that decisions to protect human health and the environment have the greatest impact and cost effectiveness when applied early in the design and development phase of a process or product. From another perspective, Hamner (1996) describes environmental management as a staircase where the underlying concepts of the practice make up the steps. The lower steps include waste disposal, pollution control, recycling and pollution prevention and higher steps include cleaner production and industrial ecology. The envi-ronmental factors to be considered when designing green products include material, production methods, packaging and transporta-tion, usage, waste, and recovery.

In addition to governments, corporate and academia interest in improving the environmental impact of manufactured goods has increased significantly. The literatures for sustainable supply chain management covering topics of product development, design for

0957-4174/$ - see front matter Ó 2010 Elsevier Ltd. All rights reserved. doi:10.1016/j.eswa.2010.04.025

* Corresponding author.

E-mail addresses:fataneh@illinois.edu(F. Taghaboni-Dutta),trappey@ie.nthu. edu.tw(A.J.C. Trappey),trappey@faculty.nctu.edu.tw(C.V. Trappey).

Contents lists available atScienceDirect

Expert Systems with Applications

(2)

environment, supplier selection, packaging, among others has been increasing at a significant rate since 2000 (Seuring & Müller, 2008). The Environmentally Conscious Business Practice (ECBP) model is a valuable framework to use for evaluating and selecting green strategies. The ECBP model integrates several factors of enterprise decision making related to environment. The factors defined by the model are design for the environment, life cycle analysis, total quality environmental management, green supply chain manage-ment, and ISO 14000 environment management system require-ments. The detailed components of ECBP are listed inTable 1.

2. Product data management (PDM)

According to the definition ofCIMdata (1997), PDM is used to organize, save and control all information related to the product design, manufacturing and its life cycle management. Managing the product data is a complicated challenge for the manufacturing industry, which needs to frequently design, re-design and manu-facture products to better satisfy changing market demand. The re-lated information includes the component list, the classifying rules, multi-layered bill-of-materials (BOM), all engineering files (CAD/ CAE/CAM), electronic documents and other information related to product life cycle. The product data needed to integrate the rel-evant information among the prime manufacturers, sub-contrac-tors, suppliers, customers and other partners (Trappey, 2001), particularly for the design teams to manage product information electronically. PDM also integrates, exchanges, and facilitates the management of all product-related data and procedures across heterogeneous platforms and organizational boundaries.

Product lifecycle management (PLM) further expands the scope of PDM.CIMdata (2002)defines the experience to include a strate-gic business approach, support for the extended enterprise, and integrate people, processes, business systems, and information. The data management is a very complex issue since manufacturers

routinely manage thousands of products. Thus, there is a need for a system which facilitates the upload and management of product information without too much human interaction. One solution is to use XML files to upload the manufacturer’s products informa-tion. The XML file is generated by the enterprise system or component information system and typically conforms to the man-ufacturer’s schema definition. This paper reviews the Integrated Green Parts Information Platform (IGPIP) first proposed by Trap-pey, Taghaboni-Dutta, and Trappey (2008). The paper then dis-cusses the prototype hub implemented for XML supply chain integration and green product lifecycle management.

3. Integrated Green Parts Information Platform (IGPIP) Companies are pursuing environmentally sound product devel-opment either due to regulation or for reaching out to customers who have become more conscious about their buying habits and the impact on environment. In 1994 when Sony received a ‘‘rea-sonable” buy rather than ‘‘best buys” only due to its environmental performance from a Dutch consumer magazine, its market share plummeted by 11.5%. Following this, Sony launched the ‘‘Green-house Project” which focused on improving the environmental im-pact of its products. Sony’s performance was rated higher and it began to improve its market share (Elwood & Case, 2000). How-ever, while the environmental performance is important, compa-nies will have to grapple with what can be achieved in a cost effective manner. By using Life Cycle Analysis (LCA) tools which in-cludes environmental performance of the product through using multi-criteria decision-making methodologies, one could achieve a cost effective product while meeting environmental objectives (Choi, Niels, & Ramani, 2008) or address the green impact by revis-iting the modular design practice (Tseng, Chang, & Li, 2008).

To achieve a cost effective way of improving the environmental impact companies have developed a corporative relationship with their supply base by sharing information (Cheng, Yeh, & Tu, 2008). However, the knowledge sharing is organized around software sys-tems that are used by these organizations and does not allow the companies to easily evaluate any alternative outside of the known supplier base. While research shows that much of the potential for improving the environmental performance of products is through the supply chain (Rai, Patnayakuni, & Seth, 2006; Yang & Sheu, 2007), the ease by which all alternatives (i.e. those outside of the firm’s current supply chain partners) can be considered is hindered due to the absence of data interoperability among the software systems.

The proposed Integrated Green Parts Information Platform (IGPIP) presented in this paper enables companies to share and manage product information, including environmental related (green) data, among multiple users in the supply chain network. This system can work across differing platforms since the users will send and receive the green parts information effectively via an XML-based exchange module.

3.1. IGPIP system architecture

IGPIP is built around three layers, i.e., the user interface layer, the functions layer, and the data layer (Fig. 1). The user interface provides a web-based interface for executing system functions. The functions layer includes the XML schema exchange module which automatically generates the eXensible Stylesheet Language Transformations (XSLTs) files allowing two parties to exchange data across platforms. Finally, the data layer contains the green part database and the XSLT database. The green part database stores information related to the green part. The XSLT data-base holds data which has been parsed from the XML files,

Table 1

ECBP components and sub-components.

ECBP components ECBP sub-components

Design for the environment Design for recyclables Design for reuse

Design for re-manufacturability Design for disassembly Design for disposal

Life cycle analysis Inventory analysis

Life cycle costing Impact analysis Improvement analysis Total quality environmental

management (TQEM)

Leadership

Strategic environmental quality planning

Environmental quality management systems Human resources development Stakeholder emphasis Environment measurements Environment quality assurance Green supply chain management Inbound logistics/procurement

Materials management Outbound logistic/transportation Packaging

Reverse logistics ISO 14000 EMS requirements Environmental policy

Planning

Implementation and operation Checking and corrective action Management review

(3)

information from test reports, and the schema mapping rules for each company.

The function layer contains four major modules: Member Man-agement Module, XML Schema Hub Module, Search and Survey Module, and Green Part (GP) Data Management Module.Table 2 shows the relationship between the modules, their functions, and the members.

3.2. IGPIP process flow

When green products are designed and developed, a large quan-tity of parts information is provided. The availability of green parts information allows designers to effectively select substitutes and alternatives that can substantially lower the cost of development and production of environmentally friendly products. Most compa-nies use an enterprise management system or a component infor-mation system which contain parts specifications. The products’ designers use these systems to locate parts that can be included in new products. If the designers cannot find suitable parts, then they reference vendors’ databases. When a green part is located, it is added to the enterprise or component information system. In these systems, the interfirm information exchanged is through point-to-point (i.e. customized) interfaces and routines. These un-ique interfaces are developed to allow for the data transfer; the number of these interfaces increase at a rate of n(n 1) thus a sys-tem with 20 software entities would have 380 interfaces (Li, Gao, & Zhang, 2002).Li et al. (2002)introduced a ‘‘plug and play” model which will replace the one-to-one relationship to a many-to-one relationship. In another research, an agent-based system addresses the data interoperability within the supply chain (Xu, He, & Qiu, 2005). However, these proposed systems while by using XML cre-ate data interoperability; they don’t allow information from other suppliers (i.e. outside of the current partners) to be evaluated when looking for alterative green components. The IGPIP platform developed in this research uses XML to accommodate data interop-erability but, additionally, the web-based hub allows any

manufac-turer and supplier to enter their green data. Thus, by using IGPIP, the search for suitable replacements is easily extended beyond current suppliers in the PLM’s Component Information System (CIS) to a large web-based repository of all suppliers community, called the Approved Material List (AML).

First, the user enters the system homepage and activates the lo-gin interface. The system reads the account number and password

System Functions User Interface Supplier Member General Member Database XSLT Database Data OEM Member U Delete Green Product Modify Green Product Test Report Management Add Green Product Green Product

Search System Survey SystemGreen Product Green Product XML File

Download XML Mapping Register Register XML XSLT Scheme Administrative Member

User Verification Ascertain Authority s e r I n t e r f a c e

Fig. 1. The three layers of IGPIP system.

Table 2 IGPIP function list.

Module name Function name Member level

authority Member Management Module Add member Administrator

Member management Administrator Maintain member data General member

Log-in General member

Log-out General member

XML Hub XML file upload Supplier, OEM

member XML file download Supplier, OEM

member Registry schema Supplier, OEM

member Schema mapping

service

Supplier, OEM member Search and Survey Module Green part search General member

Green part survey General member Green Part Data Management

Module

Add green part Supplier, OEM member Maintain green part Supplier, OEM

member Delete green part Supplier, OEM

member Test report upload Supplier, OEM

member Test report

download

(4)

and ascertains the user’s appropriate level of authority. The user can access the part of the system appropriate for their role and level of authority. The four different role classifications include general members, supplier members, OEM members, and adminis-trators.Table 3summarizes the authority levels of the different roles. The general members use the Search and Survey Module to access green part data from the information platform. Suppliers have the same authority as the manufacturers, and as the primary users of the system, they also have authority to execute the schema mapping service and use the XSLTs to upload and download the XML green parts files. Using their own schemas, suppliers can up-load their green parts to the system and manufacturers can down-load parts data. The administrators maintain the member data and the system.

The Green Part Data Management Module enables the suppliers to add green parts information and let others access their informa-tion. This function is limited to the suppliers. The suppliers upload their XML files from their own systems and the IGPIP then auto-matically translates the uploaded XML files and saves the green part information into the database. If a supplier cannot automati-cally generate an XML file for their green parts, then they can add parts information using the web-based interface. The Green Part Data Management Module and the XML hub Module facilities all these transactions seamlessly.

The Test Report function, performed within the Green Part Data Management Module, enables the suppliers to upload test reports for green parts. These test reports are generated by the interna-tional organizations which verify that the green parts follow envi-ronmental regulations. The Search and Survey Module provides a search interface for the manufacturers. OEM members log in, enter the search interface, and input the supplier’s name, green part’s name and their restrictions. The system lists all green parts that fit the search which significantly reduces the time and effort

re-quired to find suitable green parts early in the design stage. The XML Schema Mapping service is to be used by suppliers and man-ufacturer; members log into the system and then access the Schema Mapping interface. The green part XML schema, including data elements of material compositions, is generated using the international product material composition declaration standard, RosettaNet 2A13 (2005). The green part XML schema uses this intermediary XML standard to simplify translation and exchange. From the Schema Mapping Interface, the users upload an XML schema and the system parses the document and displays a struc-ture tree. Supply chain members check the rules and save the XSLT document and generate the XSLT files.

Fig. 2shows the architecture of the XML (schema and transla-tion) hub. The schema combines manufacturing process informa-tion, green part information, suppliers information, and information for related test reports. The green part information in-cludes part ID, material composition (e.g., metal, PCA, recycled/non-recycled plastic, glass, wires), RoHS chemical substances (e.g., Pb, Cd, Hg, Cr6, PBB, PBDE), weight/size, sub-part list, and 3R (recovery, reuse and recycle) level.

The XML schema and translation hub provides members with XML mapping services. The mapping interface is a web-based map-ping tool which allows the users to finish their XML schema and, afterward, XML data mapping over the web. To accommodate a seamless data sharing platform, the IGPIP provides capabilities to automatically translate and map data between different XML sche-mas. The interface provides the rules for mapping and allows users to define their own rules. After the relations between schema files are linked and defined, the mapping services generate two XSLTs: company-to-hub XSLT and hub-to-company XSLT. These two hubs execute the translations based on the generated XSLTs. The archi-tecture of the mapping interface is shown inFig. 3.

There are three major tasks performed by the Mapping Service (Table 4). As the first step, the suppliers register their green parts XML schemas. As members request mapping services, the system automatically loads the source and the target XML schema into the Schema Parser. The Schema Parser performs the analysis based on the definition inside the schema which regulates the content and structure shown in XML documents. The Schema Parser re-cords the properties of the tags defined in schema documents for future reference. The tag properties include element type, name, data type, name space, occurrence, default value, fixed value, lim-itation and description. First the Schema Parser records the tag data, and then the data is used to build a tree for representing

Table 3

Authority levels of different users.

Roles Limit of authority

General member Modify members own data. Search and survey green parts and suppliers

Suppliers and Primes (OEM)

Manage information related to green parts. Execute the XML schema mapping services

Administrator Manage all members data and set their assess authority levels

Supplier OEM

XML Schema Translating Hub

XML XML Generate Upload Database Internet Internet Mapping Interface XSLT XML File Upload XML File Download XML Generate

(5)

the XML document. The tree helps members understand the struc-ture of XML documents and enables the analysis of the element de-tails. When mapping is completed, the schemas are sent to an XSLT generator which generates XSLT files and stores them in the database.

4. Prototype demonstration

A prototype was developed to test the proposed Integrated Green Parts Information Platform (IGPIP) and additional technical details of the system are included inAppendix A. Consistent with the proposed system described above, the system provides three basic services: registry, mapping, and exchange services. As the first step, the suppliers register their green parts’ XML schemas. As the second step, the supplier members use the system functions to map their schemas with the schema of the system. As the third step, the definitions are checked, the XSLT files are previewed and the mapping services are completed.Fig. 4shows the main process flow.

4.1. The registry services

Before requesting mapping services, supplier and OEM mem-bers register and upload their XML schema and XML documents. Fig. 5is a screen capture of the interface showing that members se-lect the document type to be registered and then upload the doc-ument from their computer. Members file the version and description of this document before submitting.

As discussed in Section3.2, the member’s registration depends on their roles. The users enter the registration page and fill in the blanks with data relevant for the system administrator’s manage-ment tasks.Fig. 6depicts the information flow general members and Fig. 7 depicts the information flow for manufacturers and suppliers.

Suppliers are enabled to add green parts information and to al-low other members to access this information. The process flow for adding a green part is shown inFig. 8. This function is limited to the suppliers. The suppliers provide XML files from their systems and upload. The system translates the XML file and saves the green part information into the database. If the supplier cannot generate an XML file of their green parts, they can add parts information using the web-based interface.

Suppliers can also upload the test reports for green parts. These test reports are generated by the verification organization and certify that the green part follows environmental regulations. The

Company

Schema Mapping Service

Log-in Request for Mapping

Parser Java/C++ Mapping Interface Company XML Schema A Company XML Schema B XSLT Generator A to B XSLT B to A XSLT System Database Control

Fig. 3. The schema mapping and XSLT generating services architecture.

Table 4

The Mapping service functions. Functions Descriptions

Schema parser Reads schemata’ definitions, structures a presentation, and then sends the data to the Mapper

Mapper Provides several methods for users to map their business documents. Mapper stores the mapping definitions created by the users, and finally sends it to XSLT generator

XSLT generator Generates XSLT documents following the formulation of mapping definitions

Enter System Homepage

Enter Login Interface

not correct Judge the Account

and Password

Judge the Member's Limits of Authority

correct

Member Data Management

Green Parts Information Management XML File Management Search and Survey Test Report Management XML Schema Mapping

(6)

process flow for uploading test reports is illustrated inFig. 9. The system provides a search interface for manufacturers. Fig. 10 shows the search process flow. OEM members log in, enter the search interface, and input the supplier’s name, green part name, and the restrictions. The system then lists all green parts that fit the search.

4.2. The mapping interface

A major obstacle in information exchange is the differences in taxonomies used by various members of a supply chain (Jung, 2008). This service will allow for data interoperability among het-erogeneous platforms among the organizations. As members re-quest mapping services, the system automatically loads the source and target XML schema into the schema parser. The task of the schema parser is to analyze the definition inside the schema

that regulates the content and structure shown in XML documents. The schema mapping service is used by suppliers and manufactur-ers. Members log into the system, then enter the schema mapping interface. From the interface, the users upload an XML schema and the system parses the document and displays a structure tree. Members check the rules and save the XSLT document. In order to exchange green part information, the different XML schemas must be translated. A schema mapping service enables the mem-bers to define the rules for translating schemas. After the schema parser records the properties of the tags and the data of the tags, the tree constructor uses the data to build a tree for representing the XML document. The tree helps members understand the struc-ture of XML documents and enables the analysis of element details. The system lists the member’s schema tree on the left side and the system’s schema tree on the right side of the interface (Fig. 11). When members click on an element listed in the tree, the system uses the information to define the mapping rules. Fig. 11 also shows the source element’s information and the rules used for mapping.

The prototype system provides six rules for mapping: mapping the source content to the target, mapping the calculated source content to the target, separating the content into target tags, merg-ing the content of source tags to one target tag, definmerg-ing constant values to fill in the target tags, and setting conditions. As members define the mapping rules, the system records the information so that it can be used for editing and review. Users can define, edit, and review the XSLT content. The system also provides examples of common business documents for reference. Once the user click the ‘‘finish” button, the system will generate the XSLTs for auto-matic mapping of green product data from one XML format to an-other XML format when requested. The mapping service provides six main functions. The following explanations describe how the main functions work. All six functions have been implemented in the web-based IGPIP prototype.

1. Direct mapping: The direct mapping function enables the direct mapping of source content to the target elements.

Fig. 5. The interface of registering and uploading.

Enter System Homepage Enter Register Page Fill in the Correct Data

Check if All the Blanks Must be filled are filled

Register Complete

(7)

Enter System Homepage

Enter Register Page

Fill in the Correct Data

Check if All the Blanks Must be filled are filled Send Register Request System Administractor Vertify Register Complete pass no pass no pass pass

Fig. 7. Manufacturer and supplier registration.

Supplier Member enter System Home Page

Supplier Member Log in

Enter Green Parts Data Management Interface

Member Upload XML File

Get the XSLT File of the Member

Schema Translate

Enter Adding Green Part Web Interface

Fill in Blanks with Green Part Information

Green Parts Information be Saved into Database Does Member Have the

Green Parts XML Files?

yes

no

Fig. 8. Adding green parts into the IGPIP database.

Supplier Member enter System Home Page

Supplier Member Log in

Enter Test Report Management Interface

Input Green Part's Name to Search Green Parts

Does System have The Green Parts

Select the Green Part

Choose the Test Report Wanted to Upload

Save the Test Report into Database yes

no

(8)

OEM Member Enter System Home Page

OEM Member Login

Enter Green Part Searching Interface Input Restriction on Substance Content Select the Green Part Input Supplier’s Name Survey the Information on Green Part Download the XML File Input Green Part’s Name Does System has the

Green Part?

Yes

No

Fig. 10. The process flow and activity diagram of Search and Survey Module.

(9)

2. Calculation function: This function enables the mapping of source elements with additional calculation and conversion to target elements.

3. Separation function: The Separation function places separate content into seperate target tags. For example, an element representing a complete date (specify year, month and day in one 8-digit element) can be separated into three elements (one 4-digit and two 2-digit) representing year, month and day.

4. Constantvalue function: This function enables users to place con-stant values into the target tags.

5. Combination function: This function enables the merging of con-tent from several source tags into one target tag, i.e., the reverse of Separation Function.

6. Set the ‘‘For-Each”condition function: This function enables mem-bers to put a ‘‘for-each” rule into a specific target tag with a spe-cific value. If the value of a source tag matches the condition, the rule for the target tag is executed. In general, the XSLT gen-erator can set the ‘‘for-each” loop automatically. This function serves as a condition filter.

In addition to the above defined functions, the user can review, revise, and delete the mapping rules.Fig. 12is a screen capture of the rule definition interface.

5. Conclusion

This paper prototypes an information exchange platform to enable manufacturers and designers to increase the usage of green parts to satisfy the requirements for environmentally regu-lated products with minimized effort. To achieve this goal and to include all members of the supply chain with enterprise resource planning systems, the platform is built on an XML-based hub with a web-based interface. The prototype was designed and

implemented to demonstrate the viability of the platform to a electrical equipment manufacturers association. The XML Hub is based on the RosettaNet 2A13 standard and it enables suppliers and manufacturers to translate their part data for efficient Inter-net-based data exchange. The proposed platform provides the ability to integrate, exchange, and manage all product-related data and procedures across heterogeneous platforms and organi-zational boundaries. The proposed design of this platform elimi-nates the need for members to use different data standards than what is used internally within each company. The requisite advantage of the prototype data exchange system is the ability to accommodate differing resource planning platforms. The platform satisfied the participating companies (members) goal to reduce overall green product development cost by shortening lead time in product design and manufacture as well as minimizing human data entry. Additionally, a public information platform better en-abled members to find and select green parts for manufacturing. The web-based platform system described and developed in this research provided a tool for members that satisfied both the de-sign goals and the system implementation budget. Finally, as a public information platform, the hub facilitates the sourcing of suitable green alternatives and provides more choices to OEM members. Increased part choices impact cost effectiveness, facili-tate the creation of products, and minimize negative environmen-tal impact of products.

Acknowledgement

This paper was partially supported by a National Science Coun-cil grant. Yu-Xing Huang, a graduate student at National Tsing Hua University, worked with the co-authors to implement the proto-type for Taiwan Electrical Equipment Manufacturer’s Association (TEEMA) and their corporate members in electrical and electronic industries.

(10)

Appendix A

The technical details of the Integrated Green Parts Information Platform (IGPIP) Prototype.

The technical specification of the prototype developed in this research:

 Operation System: Microsoft Windows XP Professional Version 2002 Service Pack2.

 Web Server: JSP Server Tomcat 5.0.  Java Platform: J2SDK1.4.2.

 Database: Oracle 9i.

 Java Server Page: The subset of java language used for develop-ing web-based thin-client applications.

 Jdom: The java package for XML application development.  XML schema 1.0: The definition language for specifying the

for-mat of XML documents. It follows the XML specification and is more flexible than DTD.

 XSLT: A kind of XML language used to translate the format of XML documents to other formats.

 XML Spy 2006 SP2: It provides an easy compile interface to edit the XML Schema and DTD.

 RosettaNet 2A13 Standard is used for the implemented system.

Reference

Busch, D. (2007). Is your supply base changed without you? Medical Design Technology, 9(February), 22–26.

Cheng, J. H., Yeh, C. H., & Tu, C. W. (2008). Trust and knowledge sharing in green supply chains. Supply Chain Management, 13(4), 283–296.

Choi, J. K., Niels, L. F., & Ramani, K. (2008). A framework for the integration of environmental and business aspects toward sustainable product development. Journal of Engineering Design, 19(5), 431–446.

CIMdata (1997). Product data management: The definition, an introduction to concepts, benefits, and terminology, A CIMdata report, CIMdata, Inc.

CIMdata (2002). Product lifecycle management – Empowering the future of business, A CIMdata report, CIMdata, Inc.

Elwood, H., & Case, S. (2000). Private sector pioneers – How companies are incorporating environmentally preferable purchasing. GMI, 29, 70–94. Hamner, B. (1996). What is the relationship among cleaner production, pollution

prevention, waste minimization, and ISO 14000. In The 1st Asian conference on cleaner production in the chemical industry, Taipei, Taiwan, December 9–10.

Jung, J. (2008). Taxonomy alignment for interoperability between heterogeneous virtual organizations. Expert Systems with Applications, 34, 2721–2731. Lee, A. H. I., Kang, H. Y., Hsu, C. F., & Hung, H. C. (2009). A green supplier

selection model for high-tech industry. Expert Systems with Applications, 36, 7917–7927.

Li, J., Gao, Z., & Zhang, H. C. (2002). Plug and play information sharing architecture and its application in green supply chain management. IEEE International Symposium on Electronics and the Environment, 157, 162.

Rai, A., Patnaykuni, R., & Seth, N. (2006). Firm performance impacts of digitally enabled supply chain integration capabilities. MIS Quarterly, 30(2), 225–246. RoHS (2006).<http://www.rohs.gov.uk/>. Also see<http://www.rohs.gov.uk/Docs/

NWML%20Year%20One%20Report%20-%20November%202007.pdf> Accessed March 2008.

RosettaNet (2005). Description of 2A13 message – Distribute material composition information. Validated 11.01.00. <http://www.RosettaNet.org> Accessed December 2009.

Seuring, S., & Müller, M. (2008). From a literature review to a conceptual framework for sustainable supply chain management. Journal of Cleaner Production, 16, 1699–1710.

SME (1996). CASA/SME blue book: Green manufacturing, January 01.

Trappey et al. (2001). Product data management. Taiwan: Chan-Hai Publishing, ISBN957-2079-34-4.

Trappey, A. J. C., Taghaboni-Dutta, F., & Trappey, C. V. (2008). A framework for a green product lifecycle management system. Issues in Information Systems, IX(2), 123–131.

Tseng, H. E., Chang, C. C., & Li, J. D. (2008). Modular design to support green life-cycle engineering. Expert Systems with Applications, 34, 2524–2537.

US Environmental Protection Agency (2009). <http://www.epa.gov/>. Also see

<http://www.epa.gov/opptintr/greenengineering/whats_ge.html.ing>Accessed December 2009.

Xu, Q., He, F., Qiu, R. (2005). Heterogeneous information integration for supply chain systems. In International conference on systems, man and cybernetics (Vol. 1, pp. 97–102) October 10–12.

Yang, C. L., & Sheu, C. (2007). Achieving supply chain environmental management: An exploratory study. International Journal of Technology Management, 40(1/2/3), 131–156.

數據

Fig. 1. The three layers of IGPIP system.
Fig. 2. The architecture of XML schema and translation hub.
Fig. 3. The schema mapping and XSLT generating services architecture.
Fig. 5. The interface of registering and uploading.
+4

參考文獻

相關文件

The main purpose of this study is applying TRIZ theory to construct the Green Supply Chain management (GSCM) strategies for the international tourist hotel1. Based on the

The scenarios fuzzy inference system is developed for effectively manage all the low-level sensors information and inductive high-level context scenarios based

Lastly, using Voting Analytic Hierarchy Process (VAHP) model to estimate manufacturers and consumers’ green camping product design, and furthermore construct service

“fumes / smoke Management”, followed by “waste recycling”, and finally “green energy”. Mean value of the Green restaurant on the degree of cognition are agreeing to

The methodology involved in the study is based on the theory of innovation adoption, including the fact proposed by Holak (1988) that product attributes, consumer characteris- tics

Due to the high technology change and rigorous global competition environment, the dynamic customer preference needs and short product lifecycle intensify the

In view of it, this research is based on the foundation with the companies that check and approve to manage property of VoIP business of general bureau of telecommunication in

With a full range of digital information products and consumer electronics applications universal, TFT-LCD with the key components of flat panel display supply chain strategic