B48495C
Author: Tianyou Bin 2004-10-15 17:51:36 blog China (Blogchina.com) This year I have the opportunity to be responsible for the development of a provincial bureau office automation systems, and recently in the province's nearly 60-point application. The development has been in two and a half months. In the process, the "known as the name" OA system has been analyzed. Today, there have been several questions today, and they will discuss with everyone. Please give pointers.
Question 1: What is the core of the government office automation system?
Before we developed, our team has collected many different manufacturers OA systems, and the analysis found that most widely promoted OA system functions are relatively abundant, such as document management, meeting management, archive management, vehicle management, Personnel management, etc., but these OA systems really make government customers use effect? Customers care about the function? I found that many OA manufacturers have not analyzed precise! This is actually the most critical issue in the development of government OA system. If this problem can not be solved, other functions have been deepen, and then improved, and it is no harmonious. We analyzed the needs of many departments of government customers and found the following answers: The core of government OA system is document management, the core of document management is the process management and document editor.
Some customers begin to require manufacturers to develop OA systems, for functional richness, propose a number of functional modules, such as vehicle management, meeting management, and other auxiliary office management modules. However, after a period of operation, 90% of government staff will only apply the official document management module, so this module is the most problematic, and the customer's custom demand is most. Other functional modules will eventually become a furnish (unless the leaders have special requirements, even if the leadership requires, because when they start to develop, there is no in-depth investigation of relevant business sectors, these function modules are finally used.). Therefore, the author recommends that customers and OA developers should take 80% of the energy to place in the official document management module to meet the most users' needs of the OA system. As for other functional modules, such as vehicle management, meeting management, in fact, as a business management system to customize development, not attributed to OA systems, separate research, separately. The author may have some inverse trends, because the current OA concept is "collaborative OA", requiring OA system to solve all Government office needs. But the author believes that "collaborative OA" is OA system all business management system basic data management unified authority management. Therefore, the main construction purpose of the core OA system is to solve the problem of official traffic, solve paperless work problems, and solve the problem of electronic law.
Question 2: Process Process Questions, is the application workflow, or let the customer dynamically define the process?
I found that IT is a field of fried concepts. I have a hot "workflow system" in the first two years, and it has been calm. I don't believe it, or I don't believe that domestic IT companies can make a "universal, general system" that can solve all business functions. If this system can be made, it is certainly Microsoft, if Microsoft is not Do this system, do you think it is necessary to do it? I think the starting point of this concept is good, I want to abstract the system's process logic part, reduce the workload of secondary development. But when I arrived in China IT Colleague, I like some to walk, turned into a universal, and the general area can solve all the problems. Ok, don't say it, I don't understand the workflow, I'm talking, the inner people don't want to see it. The words retired, asked questions: "You said, can the government's workflow can define in advance?" I feel that at least in China is not defined because it varies too much. For example, an official document is a document of ordinary staff, requiring departmental leadership review; but if it is a department leadership itself? This is just the simplest example, other special examples, especially in the process, even if the handful government staff may sometimes do not know how the next step should be handled, so often please ask the leaders. Therefore, I think that government customers don't need, and it is impossible to define a procedures for the process of processes. Instead, it is necessary to have a dynamic process office automation system that can be dynamically selected for their own operations and objects every step. Question 3: How to make OA system maintenance, system management is more convenient?
In fact, this has returned to a question, is "centered technology", or "customer-centric", government customers of course require "customer-centered". Therefore, many bidding documents are required to be "simple and easy to use, and easy to maintain". This is also, spend money, who wants to buy a burden. But what is the current mainstream OA system? I can give an example. At present, many government OA systems are developed based on Domino. From the previous use of this OA, customers must require customers to train Notes. Now, it is based on Domino B / S version of the OA system. The convenience of end customers is improved, but the system administrator still has no professional Notes training without departure, user management, and system configuration. It is not used up. So I think a good government OA system, to solve the convenience of various end users. Solutions are: Applying other development platforms, such as J2EE or .NET. This can only solve the convenience of the ultimate user, the convenience of the system administrator maintained.
