C620-1普通车床的数控化改造设计【含3张CAD图纸】
收藏
资源目录
压缩包内文档预览：(预览前20页/共73页)
编号：11488529
类型：共享资源
大小：518.19KB
格式：ZIP
上传时间：2018-11-30
上传人：机****料
认证信息
个人认证
高**（实名认证）
河南
IP属地：河南
20
积分
- 关 键 词：
-
含3张CAD图纸
c620
普通
车床
数控
改造
设计
cad
图纸
- 资源描述：
-
- 内容简介：
-
附录2原文Agent-based collaborative product design engineering:An industrial case studyAbstractGlobalization and rapid evolving of Internet and Web-based technologies have revolutionized the product development process. Engineering a product is a complex process involving the integration of distributed resources, such as human beings, engineering tools, and a large variety of product-related information systems. Software agents have been playing an increasingly important role in this area to reduce the need for large,complex, and centralized systems. This paper presents the results of an industrial case study in the development of a collaborative e-Engineering environment for mechanical product design engineering by applying intelligent software agents, Internet/Web, workflow, and database technologies. A software prototype system has been implemented on a FIPA-compliant agent platform, with a wheelaxle assembly being used as a test case for system validation.Keywords: Collaboration; Product design engineering; Internet-aided design; Software agents; Workflow1. IntroductionTo survive in an increasingly competitive business environment, manufacturing enterprises are under unprecedented pressure to become leaner and more agile. Innovation and utilization of advanced information and communication technologies (ICT) are becoming more and more important to an enterprise, because agile manufacturing can only be achieved through the re-engineering and continuous improvement of ICT infrastructures. A collaborative environmentintegrating diverse information systems can enable the creation of virtual enterprises with competencies to effectively and efficiently share their knowledge and collaborate with each other in order to compete in a global market.Product design engineering, not alone, consists of design and engineering activities that should be shared among a multidisciplinary team distributed within or beyond organizational boundaries. Complex engineering design projects generally require the cooperation of multidisciplinary design teams and the readily accessibility to various engineering tools (such as CAD, FEA, dynamic and kinematics analysis, simulation, and optimization packages), databases and knowledge bases. In order to coordinate multiple engineering design activities in a design project and to guarantee the integration of different engineering tools, it is very important to have an efficient collaborative engineering environment. The environment should not only automate individual tasks in the manner of traditional computer-aided engineering tools, but also mediate between individual tasks to promote collaboration within thecontext of a product design project. Multi-agent system (MAS) represents one of the most promising technological paradigms for the development of open, distributed, cooperative, and intelligent software systems. During the past several years, we have been working on the development of collaborative environments for multidisciplinary design optimization (MDO) and have developed a prototype software environment called WebBlow (a Web/agent-based blow molded parts design and optimization environment). In WebBlow, a multi-agent system was developed to integrate blow molding process simulation, performance simulation, and optimization algorithms. In a recent effort, we further extended the agent-based architecture of WebBlow to a service-oriented framework and validated its feasibility and advantages for application in the automotive blow molded parts design and optimization 3.This paper reports the results of our recent international collaborative research project on the development of an agentbased collaborative e-Engineering environment for product design engineering. The primary objective of this project was to develop a prototype software system based on the Web and software agents and demonstrate its viability through an industrial case studythe design and optimization of a wheelaxle assembly (part of a bogie system). Based on our comprehensive research of the FIPA specifications 4, agent development platforms, and other MAS applications, right weight FIPA-compliant agent framework called Autonomous Agent Development Environment (AADE) was developed and applied to support our engineering design application. The rest of this paper is organized as follows: Section 2 presents a literature review on the application of agent and Web-based technologies in engineering product design and development; Section 3 discusses the proposed system architecture for the agent-based e-Engineering environment,its major components and the AADE MAS platform; Section 4 describes the prototype implementation with an industrial case study; Section 5 concludes the paper and discusses future considerations.2. Literature reviewWeb- and agent-based approaches have been dominant during the past decade for the implementation of collaborative product environments. An extensive review can be found in 13. This section provides a brief updated review of the applications of agents and Web-based technologies to collaborative product design engineering.2.1. Agent-oriented collaborative designIn agent-oriented collaborative design systems, intelligent software agents have mostly been used to enable cooperation among designers, to provide wrappers to integrate legacy software tools, or to allow better simulations. An earlier review of multi-agent collaborative design systems can be found in ref. 5. Shen et al. 6 provide a detailed discussion on issues in developing agent-oriented collaborative design systems and a review of significant, related projects or systems.The use of agents in product design engineering has been demonstrated by a large number of R&D projects. PACT 7 is one of the earliest successful projects in this area. The interesting aspects of PACT include its federation architecture using facilitators and wrappers for legacy system integration. SHARE 8 was concerned with developing open, heterogeneous, network-oriented environments for concurrent engineering, particularly for design information and data capturing and sharing through asynchronous communication. SiFAs 9was intended to address the issues of patterns of interaction,communication, and conflict resolution using single function agents. DIDE 10 was a typical autonomous multi-agent system and was developed to study system openness, legacy systems integration, and geographically distributed collaboration. Co-Designer 11 was a system that can support localized design agents in the generation and management of conceptual design variants. A-Design 12 presented a new design generation methodology, which combines aspects of multiobjective optimization, multi-agent systems, and automated design synthesis. It provides designers with a new search strategy for the conceptual stages of product design, which incorporates agent collaboration with an adaptive selection of designs. Multi-agent systems provide a ooperative environment for the sharing of design information, data, and knowledge among distributed design team members. However, this data sharing mechanism could only be easily achieved by using the Web technology.2.2. Internet and Web-based collaborative designInternet and Web-based technologies have created an information utility that is accessible, ost-effective, and useful for a broad range of applications. These echnologies have been adopted by the manufacturing industry, particularly in collaborative product development environments. Areas of successful migration to Web-based environments have ranged from collaborative engineering design, shop floor automation, manufacturing execution systems, to enterprise resource planning, customer management, supply chain management, and even B2B e-commerce 14. With the globalization of manufacturing, there is an ever-increasing need for collaborative design environments over the Web in order to utilize the widely available computational resources and enable collaboration among eographically distributed design teams. Shen 15 presented an overview of eb-based infrastructures for collaborative design engineering. A number of frameworks have been proposed for Web-based collaborative design systems 1620, however, most of them either support fundamental aspects of collaborative design or are proof-ofthe-concept prototypes. Other attempts are based on standalone applications, e.g., Web-based DFX tools 21 and WebCADET22. In addition, there are a few commercial software tools for collaborative product developments, such as ipTeam 23 by NexPrise Inc. and aWeb tool for civil engineering projects 24. A number of CAD vendors have recently released Internet/Web-based functionalities to their products, e.g., AutoDesksAutoCAD2005 25, PTCs Pro/Engineer 26, and EDSProduct Lifecycle Management solutions 27. CoCreates OneS 28 supports online design collaboration, data and project management, and specialized modeling techniques which support translating, visualizing and exploring precise engineering data (including the import and export of IGES,STEP, ACIS, DXF, and DWG files and optional CAD converters for SolidWorks1, Solid Edge1, Inventor1,CATIA1, I-deas1, Pro/ENGINEER1, and Unigraphics1).However, the Internet- and Web-based technologies only provide fundamental infrastructures for collaborative design systems by standardizing communications between individual systems. The interaction among components is predefined and falls short of supporting the integration of multidisciplinary design environments, where collaboration is established through non-deterministic ad hoc interaction patterns. Nevertheless, intelligent software agents, Internet and Webbased technologies are all very useful in developing collaborative design engineering environments. The combinationof these technologies has a greater potential to bring advantageous characteristics, such as autonomy, cooperative, flexibility, adaptability, interoperability, scalability, and loosely coupled message based architecture.3. Architecture of the agent-based e-Engineering environmentA collaborative research project on the development of an agent-based e-Engineering environment for product design engineering was carried out between the Korea Institute of Machinery and Materials (KIMM) and the National Research Council Canadas Integrated Manufacturing Technologies Institute (NRC-IMTI) since 2003. The engineering tools to be integrated in this system include:- IRONCAD v 6.0;- DADS v 9.6 (for dynamic analysis);- ANASYS v 7.1 (for structural analysis);- AFAP (a program developed in KIMM for fatigue analysis).Q. Hao et al. / Computers 28More information about this project as well as our long-term strategies of e-Engineering services paradigm can be found in.3.1. Terminologies and data analysisFor the clarity of representation, we need to define the terminologies used in this paper. Fig. 1 illustrates some of the data objects, user roles, and relationships.A workflow is composed of a group of nodes and descriptions about node relationships. There are 21 types of commonly recognized workflow patterns for workflow management 30. Among these patterns, only a small number of them were presented, recognized, and executed in the workflow engine. In particular, we introduced the concept of workflow in this project to describe a design project template, including aspects of user roles, design activities, and execution conditions along a design project.A project is an abstract (not concrete) specification of the design jobs. A project inherits a workflow and specifies the project template embedded in the workflow. According to each node in the workflow, there is a corresponding project task in the project definition with minor modifications against the workflow, i.e., enable/disable a node. Although the resulting project may not be exactly the same as the original workflow, it can be called an active instance of the workflow.A project is defined, controlled, and managed by the project manager.All concrete project working data (parameters, files) are related to the design jobs defined under a project. A design job is made up by a number of tasks. Because a job contains an individual data set for a project, it also can be viewed as a design version of a project. Thus, in a job, there are job/task identification, job/task status, job parameters, task files, etc., but not the task sequence, because the sequence information is already defined in the workflow and then in the project.A job is defined, controlled, and managed by the project designer. Jobs can be monitored by both the designer and project manager.In order for tasks in a job to be executed one by one automatically, the transformation and transportation of parameters and files between these tasks are also required to be accomplished automatically. Hence, the parameter/file requirements of design tasks, parameterfile, ileparameter, and filefile relationships are designed as basic information in database tables accordingly. These basic data tables are maintained by the system administrator and can be queried to dynamically link the tasks at run time. The system dministrator is also responsible for other system level management issues, i.e.,user/role management, system configuration, monitoring, andcontrol of agents in the system. 3.2. System architectureThe system architecture of the agent-based e-Engineering environment for product design engineering is shown in Fig. 2.System functions include project management, design job management, user management, engineering data management, and system integration with different kinds of commercial or self-developed engineering software tools. A number of software agents have been designed.We describe the composed agents and their functions below briefly.3.2.1. e-Engineering server agent (ES)It is the gateway that users must get through to define, manage, and monitor the information about a design project and its affiliated design jobs. Therefore, all the engineering data related to the project, workflow, design job, and tasks are passing through the ES agent, though they are manipulated by the EDM agent (see below). Every time when a design job starts running, the ES agent generates a job agent dynamically. The reverse process happens when the ES detects that a job has been finished. Other functions of ES include:- collecting data from job agents (JA);- locating interface agents (IA) request to EDM or the correct JA;- updating data/files through the EDM agent when necessary;- coordinating activities of multiple design jobs in multi-project multi-job situations.3.2.2. Engineering data management agent (EDM)The EDM agent is a proactive engineering data service agent. EDM has the knowledge of database location,connection configuration, table structures, location and con-figuration of the FTP server, directories of engineering files, etc.It provides database and file system operation services, such as creating data sets for a new job, updating design data, retrieving design tasks, and helping sending data files proactively to the target agents before a job starts.3.2.3. Job agent (JA)A job agent communicates with the EDM agent for storing and retrieving job data; with the DF agent for searching matched PS agents; and with the problem solving (PS) agents for negotiation based design tasks allocation. A job agent is created and dissolved dynamically by the ES agent to control the design job it represents. In some occasions, the user requests about a job must be directed to the corresponding job agent (rather than EDM) through the ES, because neither ES nor EDM knows all the details about an executing job.3.2.4. Directory facilitator agent (DF)The DF provides registration services for other agents residing in this system; keeps up-to-date agent registration information; and provides lookup and matchmaking services to job agents. In Fig. 2, there is one and only one such DF agent in the whole agent platform. In the future, we could consider an architecture composing of multiple DFs, in which the distributed DFs residing on different physical networks register with each other and form a much more complex MASarchitecture.3.2.5. Interface agent (IA)In this agent-based e-Engineering environment, user requests (user refers to project manager or designer) enter the system through the Web-based user interfaces. There are several Servlets responsible for receiving these requests on the Web server. The IA then catches the user requests from Servlets, translates the requests to messages, and initiates corresponding conversations to related agents. On the other hand, when the system reaches a result, the IA receives reply messages from other agents and creates updates to related user interfaces. So, the IA is a kind of application that functions mainly as a two-way bridge connecting the Web-based user interfaces and the back-end multi-agent system.3.2.6. Problem solving agent (PS)PS is the actual engineering problem-solving agent. A PS agent not only carries out the communication and negotiation functions for an engineering software tool, but also executes the related analysis, imulation or optimization based on the parameters (and/or input files) provided by the EDM agent. In this project, four engineering software tools were required to be integrated: IRONCAD, DADS, ANASYS, and AFAP. Since IRONCAD is a standalone interactive 3D modeling software tool, which is difficult to execute automatically, its epresentative PS agent is treated differently as an empty node (shown as a dark shade circle in Fig. 2). In this special case, IRONCAD software must be installed on the designers local site. Its representing PS agent does not have the execution interface as other PS agents and the IRONCAD task is manipulated and submitted manually by its human user.3.2.7. Monitoring agent (MA)The MA is specially designed to facilitate the monitoring of agent behaviors behind the user interfaces so that agent activities could be visible to users. In a distributed computing system like MAS, because information is distributed and controlled by each individual agent, it is necessary to have an agent that can accumulate information from various resources when required. Through this monitoring agent, the conditionof the system, the behavior of this MAS environment as well as all individual agents can be conveniently monitored or reviewed through a graphical tool provided to the user.In Fig. 2, there are also some other non-agent components that are designed mainly for supporting the engineering application problems of product design engineering.3.2.8. User interfacesA Web-based user interface is very convenient for multiple members of a design project or a design job to work collaboratively. Web-based technology is very popular, and in reality, is almost a must choice for distributed, collaborative applications. In our system, the project manager can define, control and monitor a design project, while a designer can define, control, and monitor a design job by using Web-based user interfaces. Another kind of user interfaces isthe application clients of a traditional client/server (C/S) architecture. They are designed for the system administrator to maintain basic information in the database, i.e., users, roles, tasks, files, parameters, and relationships. Theoretically, the second type of user interfaces could also better be designed as Web-based; however, for the readiness of system implementation, we simplify some part of information maintenance since this part of data is not critical to major purposes of this system.3.2.9. Database (DB)MySQL is used in this project as the database management system (DBMS). Because we use the multiple-layered system architecture, the business logics manipulating database tables are carefully organized and developed in the middle layer agents, such as EDM and ES, rather than sending SQL queries directly from the user interfaces. However, according to our design, only the EDM agent has a permanent onnection with the database; all other agents either get their results through the EDM or connect to DB dynamically by using the authorization and SQL scripts given by the EDM.3.2.10. XML filesAll the files used by this system are in XML format,including agent configuration files, registration data files,message record data files, and system logging files. The system generated parameter input/output files of design tasks are also XML files conformed to their DTD definitions.3.2.11. ServletsSince the Web-based user interfaces are developed as Java Applets, Servlets are needed to reside on theWeb server side for catching user requests. User requests are then directed to the interface agent and are packed into messages to back-end system by the interface agent.3.2.12. Messages linkMessage links are depicted as dashed lines to show roughly the interactions between agents. Some examples are: agents register with DF; JA searches the registration data in DF for matched PSs; JA negotiates a task with PS agents.3.2.13. Data linkData links are bolded lines to illustrate the connections of agents with information in database or files in the file system. EDM agent has permanent connections with the database;while other agents (JA, ES, and IA) may only connect to the database dynamically with the permission of the EDM agent.Another kind of data link is drawn between the EDM and PSs.In order for a PS to run a design task, all the input files required by its external engineering program must be available to this PS agent. Similarly, the output files are required to upload to the FTP server behind the EDM agent for other design tasks to utilize. Therefore, between the EDM agent and the PS agent in Fig. 2, there is a link standing for the input/output file transportation over the network.3.2.14. Control linkControl links stand for the control or management flow of this system originated from the application point of view.3.3. AADE agent platformThe development of an agent-based industrial application is not an easy task. In building a multi-agent system (MAS) application, developers unavoidably face the challenge of insufficient support of agent-level infrastructures. In addition to the technical difficulties in developing multi-agent systems, the interoperability between heterogeneous agents and agent systems also has to be considered. For the above reasons, an agent platform is required for implementing multi-agent systems. Sound planning and design of basic infrastructures of an agent platform can greatly enhance the systems scalability, flexibility, and interoperability.In this research, we chose to design and develop a lightweight FIPA-compliant agent framework that supports applications especially in engineering fields. The engineering-oriented agent platform called autonomous agent development environment (AADE) 31 provides programmers with reusable agentoriented classes (templates), which share useful relationships. The current AADE only implements a semantically closed agent community in which all agents communicate within the agent framework using a dedicated content language expressed in XML. The major characteristics of AADE include:- A loosely coupled agent communication infrastructure is adopted based on lower level peer-to-peer communication protocol (TCP/IP socket), rather than the tightly coupled RMI invocation.- The agent-level and domain dependant issues are identified and programming modules (classes) are encapsulated in multiple levels of abstractions.- Multi-layered support for agent communication, message handling, and conversation management.- Multiple message queues and conversation lists that facilitate the buffering and scheduling of agent behaviors.- A very closely related agent community with the common understanding of domain ontology.- Providing reusable software libraries, interfaces and agent development templates that can be specified for agent implementation.- Multiple threads execution and central conversation management handling concurrent conversations.These characteristics provide a foundation for the development of open, dynamic, flexible, and reliable (fault tolerant) multiagent systems. In particular, this platform includes an EDM agent along with a Batabase server, a FTP server, and an engineering file management mechanism, which are specifically designed for engineering pplications. The architecture of agent abstract model in AADE is discussed in details in 31. Although AADE currently does not have so many features as other FIPA-compliant open source platforms such as, JADE 32 and FIPA-OS 33, it is believed to be more engineeringoriented and therefore more suitable for eveloping collaborative e-Engineering environments. It is also easier to be accepted by industries since it avoids some open source concerns.4. Prototype implementation and case studyThe software prototype environment has been implementedon a network of PCs with Windows 2000/XP and Linux operating environments as well as SUN workstations with the SUN UNIX operating environment. Java is the primary programming language for system implementation. Other programming languages including C/C+, FORTRAN, and Visual Basic, are also used for legacy systems integration. All agents are implemented on AADE. The EDM agent is implemented to integrate MySQLTM as the primary database for the entire system. Server side modules are implemented onApacheTM and TomcatTM.In the following subsections, we will demonstrate the developed system using an industrial case study.4.1. Wheelaxle design problemIn this project, we chose the wheelaxle design as our case study. The axle shown in Fig. 3 is a real component taken from the wheelaxle assembly of a bogie system. The process of axle design and optimization (project) is illustrated in Fig. 4.The process of axle design and optimization needs to undergo five consecutive steps: 1. Parametric geometric modeling: User inputs initialCADdata of the axle (as shown in Fig. 3)which include: (1) diameter and distance of each zone; (2) section type: hollow or solid; (3) hollow dimension: constrained by minimum and maximum value of hollow percentage; and (4) notch dimensions. The IRONCAD parametric modeling wrapping program will generate an IGES model file with the specified variants.2. Dynamic analysis: The mass and lateral inertia of the car body, car frame, and wheel set are inputted as job parameters to simulate the dynamic performance of the assembly with different loading conditions (full load/condition, braking/traveling). Some output data files are created for conducting structural analysis.3. Structural analysis: Structural analysis is then carried out for verifying the stress spectrum of components. Under the selection of three zones on the axle and the application of two predefined load conditions, the resultant stress simulation can be obtained as the basis for design parameters optimization.4. Fatigue analysis: Fatigue analysis is done for life cycle analysis of structural components. The results of fatigue analysis include the SN curves, life and damage calculation,and fatigue spectrum.5. Optimization: In order to synthesize the results getting from the above steps and make the whole design loop close, the design optimization needs its built-in intelligence (knowledge,experience, decision support, and learning mechanisms)and human interruptions to iteratively refine the design and analysis of the axle component.From the above description, we can see that the requirements of axle design and optimization are quite complex. In order for the process to be automated and intelligent, critical decisions are made at the optimization block and its related control mechanisms for refining the design process (A5 and dashed lines). So, this part should be implemented with more specified strategies for the specified ngineering problem under question. However, from the system architecture point of view, the design and optimization environment should at least provide an integrated solution of the first four steps, because these design and analysis activities have more common characteristics and need more engineering tools support. Actually, the project workflow implemented in the prototype system includes only four sequential steps with specifications of all detailed parameters and input/output data files defined by KIMM. Although this is not a good case scenario for an agent-based collaborative product design system, it shows how the technology can be applied to real industrial applications. It is evident that agent-based approaches will show more advantages for more complicated scenarios.4.2. Project definitionThe workflow of the design process of the axle can be divided into four nodes in a sequential order: geometric design (CAD), dynamics analysis (DYN), structural analysis (STR), and fatigue analysis (FAT). The axle design project is defined based on this workflow. Based on the above project definition, we define the project using theWeb-based GUI in Fig. 5. Currently, in this prototype, a project manager can only define the workflow of a design project (including its composed tasks, control points, and their relationships) by specifying a project template predefined in the workflow database. In the next version of the system, this definition interface could combine advanced graphic manipulationtechnologies to build a real project workflow from reusable graphical components.4.3. Job definitionWe defined several jobs under this axle design project, each with a different set of input files and output files. Each design task (done by one PS agent) has to obtain a set of input files to execute the specified engineering software. Input files are either the XML files constructed by job parameters (entered through the Web GUI in Fig. 7) or data files getting from output data files of previous tasks. After task execution, a set of output data files and some output job parameters are generated as required.Fig. 6 is a screen shot for the job definition process. A description of the job, including project, job, task, input files and output files, is displayed as a tree list on the left side. In this way, it is very convenient for the user to browse a job. The system can quickly locate a user to information that he is interested in. The window on the right side is a file viewer.Input/output files can be opened in this indow in textual or graphical (2D plot graph only) formats. There are a total of 32 input parameters and 12 output parameters defined for the case job of wheelaxle design. For the convenience of integration, all required parameters are packed into XML input files before the execution of each design task. For the convenience of user, we developed some Web-based GUIs (such as the one shown in Fig. 7) for the user to enter the initial job (input) parameters. Each task (including CAD, DYN, STR, and FAT) has its own set of design parameters. Fig. 7 shows one of the three pages for job parameters definition. After the user submits the job, the definition of job, status, together with job parameters and job tasks are created into the Job and Task tables in database (NewJobDef conversation in Fig. 8).4.4. Agent interaction scenarioFig. 8 represents a scenario of agent interactions in the backend system for executing a design job. In Fig. 8, a bold solid line stands for a complete conversation between two agents.Currently, all conversations between agents are implemented using the FIPA Request protocol. Other protocols could be added later on easily because we have already developed an open and flexible AADE agent platform. So behind one conversation, there are actually many messages (at least three:request, agree and inform) flow back and forth between agents,although only one link (bold line) is shown. Other non-boldlines (solid or dashed) stand for data flows or control flows(Fig. 8).To further simplify our implementation, we omit the JA andcombine its functionalities to ES because of the time concernsof this project. The steps of agent nteractions in this scenario are explained as follows: Step 1: IA catches user inputs about job and job parameters and initiates NewJobDef conversation to EDM. Job definition is thus stored in the database.Step 2: User starts a design job from the user interface, and IA initiates the Request of StartJob to ES.Step 3: ES requests and gets the information about the job by initiating conversation GetJob to EDM.Step 4: ES gets the next executable task of the job and findsout the matched PS agent to do the task (either from its local copy of agent registration table or by initiatinganother conversation SearchRegistry to searchin DF).Step 5: Before the task execution, the ES updates job and task status in the database through ChangeJobStatus to EDM.Step 6: ES sends out conversation PrepareFiles with job-id, task_id as the content payload in the Request message to EDM. EDM creates all the input files required by the task to the corresponding input file directory and finally replies ES with an Inform message of repareFiles.Step 7: ES asks the PS agent to execute a task by RunTask.Step 8: PS gets the location of its input files and the FTP information through conversation GetTaskFiles.Step 9: PS connects to the FTP server and downloads the input files to its local directory.Step 10: PS executes the Java wrapper of the external software program and gets the execution results.Step 11: PS gets the location of its output files and the FTP information through conversation SetTaskFiles.Step 12: PS uploads its output files to the FTP server.Step 13: PS return conversation RunTask by sending an Inform message to ES.Step 14: ES initiates PrepareParas to EDM. EDM extracts parameters from output files and saves them in the database if necessary relationships defined in base tables).Step 15: ES updates job status and checks whether the design job meets any failure or whether it has been finished:a. Not finish, go to 4.b. Job end or failure situation, go to 16.Step 16: ES informs EDM to finally update job status by Change Job Status.Step 17: ES returns an Inform message of StartJob conversation to IA.Anytime during the task execution, the PS agent either gets the status of external execution through GetRunningStatus upon user requests (Step 18) or checks the running status regularly by its own schedule thread (Step 19).A separate thread in the PS agent is used to execute the Java wrapper for the external engineering software tool. Considering there may be some running errors from the external software, a failure detecting thread is implemented in the PS agent for catching external errors from the wrapper.Whenever an error is detected, the PS agent will exit from its wrapper thread and stop the RunTask conversation by sending an Inform message with failure status in its content.5. ConclusionsAn agent-based collaborative e-Engineering environment for product design engineering has been designed and developed based on the facilities provided by the AADEa FIPA-compliant agent platform. The design and optimization of a wheelaxle assembly is used as an industrial case study to validate the prototype software system. Thisprototype system can be extended to the whole bogie system design or even to the design engineering of a more complicated mechanical system. However, some challenging problems (including efficient and effective coordination, multi-project/user management, and dynamic workflow composition) need to be carefully addressed and further development efforts are required before the technology can be widely deployed in an industrial setting. In the short to medium term, we will be devoting our efforts in the followingareas:- improvements on multi-project and multi-user management;- intelligent problem solving capabilities built in each agent;- intelligent load balancing for design jobs;- intelligent computing load balancing for problem solving agents;- general wrapping technologies for easy integration of legacy engineering tools;- dynamic composition of workflows;- practical and efficient coordination mechanisms;- Web services-oriented agent architecture for product design engineering.Acknowledgements We would like to acknowledge the important contributions of Mr. Kewei Li for developing the database and user interfaces of the software prototype system.译文产品设计工程师基于代理人的合作：一个工业案例的研究摘要国际互联网络和基于万维网技术的全球化和急速进化的发展，已经大大改革了产品加工过程。一个整体化的工程产品是一个复杂过程，其中包括了整体化的资源分配，比如：人类资源、工程工具和大批有关产品的信息系统。软件代理人已经在减少对复杂的并且集权制需要的领域里，起到了一个重要的角色。这篇个工业案例的研究主要是介绍，在一个工程合作发展的环境中，机械产品设计工程师是如何应用：智能的软件代理人、国际互联网络和数据库技术。一个软件原型体系已经应用在代理人平台上、并且伴随着轴装配作特性试验系统的确认。关键字 合作；产品设计工程师；国际互联网络辅助设计；软件代理人；工作流程。1. 介绍 为了在一个竞争日益加剧的商业环境中生存下来，制造企业在空前的压力下变得更加灵活和更加贫乏。革新和利用的先进通信技术对于企业来说已经变得越来越重要，为灵活的制造系统，不仅可以通过再设计来完成，并且可以连续的改善通信技术的基础结构。一个协同环境综合变化多的信息系统经验可以启动那创造的企业同资格到有效地和有效地均分他们的学问和与彼此为了在一个全球市场方面竞争合作。一个协同合作的环境综可以综合各种信息系统，能够为企业创造有竞争资格的并且可以有效地分享他们的学问，彼此合作为了参与到全球市场竞争合作中。产品设计工程师不仅负责设计与施工活动还有拥有一个多学科的梯队用来分配机构内外的事物。复杂的工程设计计划通常要求有规律的设计组和那些容易获得的多样工程工具合作的，（比如计算机辅助设计、故障影响分析、动力的和运动学分析、模拟，并且最佳化包装）、数据库和知识库。在一个设计项目为了协调许多工程设计活动并且还要保证不同工程工具的整体化、拥有一个效率的工程合作环境是重要的。这个环境不仅仅是单个按传统的计算机辅助工程方式来自动完成任务，而且还要在产品设计计划范围内调解单个任务，促进其合作。 多代理人制度在开放、分配、合作，智能的软件系统发展中主要表现在工艺样式的判断。在过去的几年里，我们已研制和发展出多学科的设计量优化协同环境，已经研制出一个原型软件环境“”（网络代理人基于模制件设计和最佳优化环境）。在 webblow 中，一个多代理人制度的发展是综合了吹塑法模拟, 性能模拟，和最优化算法。在近来的研究中，我们更加扩大了基于东方结构建筑的服务并且确认了它在汽车的应用吹模制件设计和最佳化设计中的可能性和利益。 这篇论文主要报道近来我们的国际合作研究项目，产品设计工程师基于代理人在工程环境中的合作。这个计划的主要目标是在网络和软件代理人上发展一个原型软件体系，通过研究设计和优化一个工业案例来证明它的可行性。根据我们对 FIPA 规格，代理人发展平台和文学硕士应用的综合研究，一个重量较轻的 fipa 代理人顺从结构，被称为自主开发环境主体，被发展和应用到我们的工程设计应用中。接下来的文章是由以下组成的：第二部分展现和综述了一个参考文献在代理人基于万维网技术在技术产品的设计和发展中应用；第三部分讨论了代理人基于工程环境的系统构造的建议；第四部分描述了实现工业模型的个案研究；第五部分是该报道的结束以及对将来的考虑。参考文献综述在过去的十年里，基于网洛和代理人已经在履行产品环境的合作中起到了支配作用。可以在一个广泛的评论中找到，本节供应一个摘要，评估了对于更新代理人基于万维网技术在的产品设计工程师的合作中的应用。2.1.定向代理人的合作设计在定向代理人的合作设计系统中、智能的软件代理人有主要习惯同设计师进行合作、为了供应传统综合软件工具的包装纸，或者进行更好的模拟。可以发现一个较早地对代理人设计系统的合作进行评估，供应一个细节讨论关于讨论定向合作设计系统的发展和对有关计划或体系重要的评估。代理人通过利用产品设计工程师已经被很多 R& D 计划所证明。协定是这方面最原始的成功计划之一，协定有利的方面包括它的使用服务商的联邦构造和传统系统整体化的包装纸和分享异步通信。SiFAs 被用来说明发行图案的交互作用，流通和判决使用单函数代理人的冲突， dide 是一个典型的自治多代理人制度，同时也是研究开放体系, 系统整体继承化的发展，并且从地理分配上进行合作。共同设计师是一个被用来定位设计代理人的生产和管理的多变化概念的设计体系。一个新式样新世代的方法论、它可以联合多对象优化方面、多代理人制度和自动化综合设计。在产品设计的概念阶段方面，它供应给设计师一个新的思考方式，它在一个适应的设计选择中同代理人进行合作。多代理人制度在设计分配会员组中，提供了分享设计资料、设计数据和经验的合作环境。然而，这个数据共享机构只能被使用网洛技术的人所获得。2.2.国际互联网络和基于万维网合作的设计国际互联网络和基于万维网技术已经创造了一个“高效的信息时代”，它容易接近、有效的代价，并且拥有大量的应用信息。这个技术已经采用到制造业、特别在产品合作发展的环境中。万维网洛环境已经成功的移植到工程设计的合作、普通工厂的自动化、执行制造体系、企业资源计划和客户管理当中。随着制造业的全球化，不断的增加对合作设计环境的需要通过网络，广泛地利用计算资源。沈介绍了对于工程合作设计中基于万维网基础结构的概观，然而，大多数人支持基本的合作设计方面，有的则同意原型概念。其他的企图是以独立申请为基础的、例如、基于万维网工具。总之，在产品合作发展中存在许多商业工具软件，比如 nexprise公司，土木工程计划网洛工具，许多计算机辅助设计卖主最近已经把他们的产品释放国际互联网络基于万维网上、例如，AutoDesk公司的AutoCAD2005 , PTC公司的Engineer。然而，国际互联网络和基于万维网技术仅仅通过个体体系之间的标准化流通来提供设计系统的基本的基础结构合作。元件之间的互作用是预先确定的，不符合支持多学科的环境整体化的设计，在哪里合作是建立在非确定的特别交互作用图案中。然而，智能的软件代理人、国际互联网络和基于网洛技术对工程发展设计环境的合作都很有用。这个综合技术对于产生有利的特征有一个更大的潜力、比如自治、合作的、挠性、适应性、互用性、可量测性，和基于松散耦合的信息构造。代理人基于工程环境的体系结构自从2003年，一个基于工程师产品设计环境的合作的研究项目就在朝鲜机器学会，国家工业三废的科研委员会和和加拿大的集成制造技术学会之间开展了。这个工程工具体系包括如下：3.1.技术名词和数据分析显而易见，我们需要定义那些被用于这篇论文的技术名词。图1解释了数据对象中的一些用户角色与关系。一个工作流程是由一群结点和关于结点的描述关系所组成的。对于工作流程的管理这里有21种常用的工作流程图案。在这些图案之中，只有一些少量的被设定制作和应用在工作流程的引擎中。特别是我们在介绍工作流程的概念中，描述这个项目计划的摸板时，包括了用户角色方面，设计活动和一个设计项目的施工条件。计划是工程设计的祥述摘要。设计继承了一个工作流程并且把计划模板嵌入到工作流程中。按照工作流程中的各分支、有通信设计任务中定义修改和反对工作流程，那就是说、启动或使一个分支无效。虽然那结果可能和原始的工作流程的投影图如出一辙，但是它可以被调用在活性工作流情况中。一个工程的定义、控制是通过项目经理来做到的。工作数据的所有具体物计画被讲到在一个计画之下被定义的设计工作. 一个设计工作被若干工作组成. 因为一个工作包含一笔为一个计画被设定的个别数据, 它也能被看如计画的一个设计版本. 因此，在一个工作中，有工作确认，工作状态，工作叁数，工作申请, 及其他., 但是不是工作序列, 因为序列数据已经被在工作流程中然后在计画中定义。一个工作被计画设计者定义,控制, 而且处理. 工作能被检测被两者的设计者和计画经理。以使一个工作在一点之前被自动地运行，变形和在这些工作之间的叁数和文件的运输也自动地是完成的所必要者. 因此,设计工作的叁数需求,叁数申请,申请叁数, 而且申请关系被适当地设计如数据库桌子的基本数据的文件. 这些基本的数据桌子被维护被系统管理人而且能被质疑动态地在奔跑时间联编工作. 系统管理人也负责其他的系统水平管理议题.,系统的代理人的使用者/角色管理，系统结构，监听和控制.。3.2.系统总体结构代理人的总体系统结构基于产品设计工程工程环境如图所示。系统函数包括项目管理、设计作业管理、使用单位主管、技术管理资料，并且系统综合同各种商业的或自我发展工程软件工具。许多软件代理人已经表明.我们所描述那组成代理人和他们的功能过于简短。3.2.1.工程服务代理人正是这种途径用户必须明白定义、管理，监视器关于项目设计和它的分支机构设计的介绍。所以、全部与设计有关系的工程师资料、工作流程、设计工作和任务都要通过工程服务代理人，虽然他们是通过电子测距来操作，每当一个设计工作撒下时、工程服务代理人产生一个工作代理人动力地。相反的工艺发生在工程服务代理人发觉那一个工作已经结束的时候，工程服务代理人的其他功能包括：-收集资料从工作代理人（共同帐户）；-更新数据锉刀穿过那电子测距代理人必要时；-配合教学的工作的多重设计在多作多道作业位置的投影图。3.2.2.技术资料经营代理商（电子测距） 电子测距代理人是一笔积极的工程数据服务代理人。电子测距有数据库位置的知识,连接结构, 桌子结构，位置和骗局文件传送协议伺候器的定形,工程学的目录申请,及其他.资讯科技提供数据库而且申请系统行动服务, 如此的当做为一个新的工作创造数据组,更新设计数据,取回设计工作, 而且帮助积极地送数据文件到那在一个工作前的目标代理人开始.3.2.3.工作代理人（共同帐户）一个工作代理人为储存与放电加工代理人沟通而且取回工作数据; 与主任代理人在一起对于搜索相配了附言代理人; 而且由于解决问题为被建立设计工作的配置谈判的代理人. 一个工作代理人动态地被回声测试代理人产生而且溶解控制它表现的设计工作. 在一些场合中,那关于一个工作的使用者请求一定指向那对应的工作代理人 ( 并非放电加工) 经过那回声测试,因为没有回声测试也不放电加工到处知道所有的细节一个运行工作。3.2.4.目录服务商代理人目录服务商代理人提供登记服务给其他的代理人归这一个系统所有; 保存最新代理人登记数据; 而且提供查询和火柴制造服务给工作代理人.如图2所示, 有一和只有一个如此的目录服务商代理人代理人在整个的代理人月台. 未来，我们可以考虑一多样目录服务商代理人的建筑学构成哪里那分配了目录服务商代理人在不同的实际网络寄存器上住藉由彼此和形式一个较加复杂的文学硕士建筑学。3.2.5.接触面代理人在这个基于代理人的工程师环境里、用户请求进入系统通过万维网洛用户界面。在网络服务器上有许多负责接受这个请求。接触面代理人然后从服务器上捕捉用户请求、转化那要求到信息，并且开始通信会话到有关代理人。另一方面，当体系到达一个结果时、接触面代理人承受复电从其他的代理人和创造更新到有关用户界面。所以、接触面代理人是一种功能主要在于地两路的电桥连接那基于万维网用户界面和背面结束多代理人制度的应用。3.2.6.问题解决代理人问题解决代理人是解决实际工程问题的代理人。问题解决代理人对于一个工程软件工具来说不但具有交流和谈判功能、而且执行有关模拟分析或优化以根据电子测距代理人供应的参数。3.2.7.监视器代理人监视器代理人特别地被设计促进监听在使用者接口以便代理人后面的代理人行为活动对使用者可能是看得见的. 在一分配计算机因为数据被分配，所以系统喜欢监视器代理人每个个别的代理人控制, 有是必需的一能累积来自各种不同的资源数据的代理人当需要. 经过这一个监听代理人,情况系统，监视器代理人环境的行为和所有的个别代理人能方便地被检测或检讨过一个被提供对使用者的图解式的工具。 在图中，还有其它的非代理人元件还有为支持工程师应用问题的产品工程设计师。3.2.8.用户界面一个网络的使用者接口对复是非常方便的一个设计计画或一个设计工作的成员工作协同合作地. 网络的技术非常流行,和事实上, 几乎是必须选择为分配,协同合作的申请. 在我们的系统中,计画经理能定义, 控制而且检测一个设计计, 当一的时候设计者能定义,控制, 而且藉由使用检测一个设计工作网络的使用者接口. 使用者接口的另一个类型是传统的客户/ 伺候器的申请客户输入输出系统，他们为系统管理人而设计到维持数据库的基本数据使用者,角色,工作，文件，叁数和关系. 理论上,那使用者接口的第二个类型可以也更被设计当做网络的; 然而,对于系统落实的预备,我们自从后单一化一些数据维护的部份数据的这一个部份不紧要关头的主修这一个系统的目的。3.2.9.数据库 Mysql用于作当做为数据库管理系统，因为我们使用许多的分层系统结构、那商行逻辑操作数据库表格小心地被组织和发展半层代理人、比如电子测距和接地开关、而不是派遣结构化查询语言查询直接地从那用户界面。然而，依据我们的设计、唯一的那电子测距代理人有一个固定连接同那数据库；全部的其他的代理人了结他们的结果那电子测距或接于分贝动力地由使用那授权和结构化查询语言手写体由那电子测距给那电子测距的。3.2.10.XML文件 全部的XML文件使用经由这个体系处于收上位置格式、包括代理人配置文件在内、登记资料锉刀、信息记录资料锉刀，并且体系记录文件那体系产生参数输入输出文件的设计任ervlet务是也锉刀符合他们的文件类型定义定义。3.2.11.服务器 既然那基于万维网用户界面是发展当做小应用程序，要保存在那网络服务器侧面因为捕捉用户请求.用户请求然后被指向那接触面代理人和是挤入信息到后头体系由那接触面代理人，需要服务器。3.2.12.报文链接信息链接被描写成短划线到显示粗糙地那交互作用在客户之间.一些例子是：代理人留下印象去能因子；共同帐户调查那登记资料在去能因子因为相配猪应激症候群；共同帐户谈判附言的任务代理人。3.2.13.数据链接数据链接是粗线到图解那关系的代理人同情报在数据库在文件系统。电子测距代理人的或有固定连接同那数
- 温馨提示:
1: 本站所有资源如无特殊说明，都需要本地电脑安装OFFICE2007和PDF阅读器。图纸软件为CAD,CAXA,PROE,UG,SolidWorks等.压缩文件请下载最新的WinRAR软件解压。
2: 本站的文档不包含任何第三方提供的附件图纸等，如果需要附件，请联系上传者。文件的所有权益归上传用户所有。
3.本站RAR压缩包中若带图纸，网页内容里面会有图纸预览，若没有图纸预览就没有图纸。
4. 未经权益所有人同意不得将文件中的内容挪作商业或盈利用途。
5. 人人文库网仅提供信息存储空间，仅对用户上传内容的表现方式做保护处理，对用户上传分享的文档内容本身不做任何修改或编辑，并不能对任何下载内容负责。
6. 下载文件中如有侵权或不适当内容，请与我们联系，我们立即纠正。
7. 本站不保证下载资源的准确性、安全性和完整性, 同时也不承担用户因使用这些下载资源对自己和他人造成任何形式的伤害或损失。
人人文库网所有资源均是用户自行上传分享，仅供网友学习交流，未经上传用户书面授权，请勿作他用。
川公网安备: 51019002004831号