A formal description of open distributed processing (ODP) trading based on guidelines for the definition of managed objects (GDMO)

New requirements of growing computer networks and information systems have an influence on extended client/server models with increased functionality. This forms the basis for service management in distributed systems which is realized by a service trading concept. This paper studies the requirements derived from the Open Distributed Processing (ODP) Reference Model in order to consider an open service market. Furthermore, it examines management possibilities for describing the service trading scenario. Because of similar architectures and properties ODP services, service offers, types, exporters and traders are mapped onto management components and modeled as managed objects. Therefore, the Guidelines for the Definition of Managed Objects (GDMO) are used. The final concept allows a precise and unambiguous study of the service trading scenario and provides means for exporting and importing of service offers in a distributed environment.     

浅谈如何搞好加油站的风险评价

阐述了加油站实施HSE管理，进行加油站风险评价的必要性，介绍了评价方法及其应用范围，评价组织的建立和工作流程及注意事项，指出：进行加油站风险评价，在选择评估方法时应从加油站的生产实际出发，针对不同的区域，采用适当的，可操作的方法；找出身边存在的危害因素，采取适当的措施来控制和化解风险，提高加油站安全管理水平，才能适应加入WTO后所面临的挑战。     

国有基层水管单位困境及其出路

针对贺州地区基层水管单位存在的农业水价低、水费征收难和经济困难等现状,对基层水管单位的出路进行了一些探索,提出了一些解决对策。     

在协议集成测试系统上开展路由协议测试

在分析路由协议的特性及其测试需求的基础上，提出利用窗口黑盒来描述被测协议，利用多通道测试方法扩展对被测实现的控制和观察，通过扩充参考实现增强系统的测试能力。将这些理论，技术应用于系统中，对路由协议开展了有效的测试活动，为国产高性能路由器的开发提供了有力的支持，也进一步增强了PITS系统的功能和适用性。     

军事科研项目中软件项目管理方法研究

列举分析了目前软件开发中存在的问题，提出了在军事科研项目中，对软件项目实施管理的方法，应用先进的软件项目管理理论和方法，有效的提高软件开发效率，确保软件质量。     

对流域水电建设档案科学管理的研究

介绍清江公司从流域水电建设的特点出发,研究流域水电建设工程档案的完整性、准确性,确保工程质量,提高工程管理水平,将大量的档案信息资源转化为科学知识,为流域水电开发服务,取得显著的经济和社会效益的情况。     

WLAN网管系统的现状和发展

2001年以来，全球WLAN（无线局域网）市场应用的瓶颈被打破，中国也迎来了WLAN商业化运作和服务的春天，WLAN为我们带来了一种全新的、灵活的工作方式，同时也带来了新的挑战，本文将对WLAN网络管理的主要内容和具体指标进行阐述，并对各大厂商的WLAN网管产品进行简单介绍和比较。     

关于化粪池几个问题的探讨

探讨化粪池在设计布置及使用管理中应注意的几个问题，以充分发挥化粪池在保护环境，减轻污染方面的作用。     

Spare parts inventory management with demand lead times and rationing

We study an inventory system that consists of two demand classes. The orders in the first class need to be satisfied immediately, whereas the orders in the second class are to be filled in a given demand lead time. The two classes are also of different criticality. For this system, we propose a policy that rations the non-critical orders. Under a one-for-one replenishment policy with backordering and for Poisson demand arrivals for both classes, we first derive expressions for the service levels of both classes. The service level for the critical class is an approximation, whereas the service level for the non-critical class is exact. We then conduct a computational study to show that our approximation works reasonably, the benefits of rationing can be substantial, and the incorporation of demand lead time provides more value when the demand class with demand lead time is the critical class. The research is motivated by the spare parts service system of a major capital equipment manufacturer that faces two types of demand. For this company, the critical down orders need to be satisfied immediately, while the less critical maintenance orders can be satisfied after a fixed demand lead time. We conduct a case study with 64 representative parts and show that significant savings (as much as 14% on inventory on hand) are possible through incorporation of demand lead times and rationing.     

Object-oriented DBMS requirements

The requirements on an object-oriented DBMS for management of information in a large, complex enterprise are presented. These requirements aid in the achievement of an environment characterized by data sharing, open architectures, application and data portability, and assurance of data integrity. They were defined from the point of view of a user of the DBMS; therefore they describe the expected functionality of the DBMS and do not specify the method of implementation to achieve this functionality. They encompass requirements on the data model, query and data manipulation languages, the system architecure, interfaces to the system, change management, and transaction management.