Jin and vice president of software Dai KE: Local OA lags behind in Consciousness

With the rise of the Web wave, the work documents originally stored locally are gradually transferred to the network. Internet-based OA ( Office Automation ) Brings a richer user experience, but also impacts the methods and concepts of traditional OA.
Problems faced by OA

Speaking of the Internet-based OA for the current Enterprise Application Dai Ke, vice president of gold and software R & D, believes that network storage is facing this urgent problem-security problem, that is, persistent trusted storage, in addition, the access standards and formats need to be resolved.

He believes that the integrated OA suite solves the problem of front-end problems or office tools. As long as the problem is extended to backend applications, processes, and integration with other systems, users may encounter complexity issues that are difficult to solve by themselves.

Out of the box can solve some common and simple problems. Its goal is to solve the problem of improving office efficiency. Enterprise Management Software Is to solve the problem of enterprise and organization operation efficiency.

From the perspective of the entire OA field, the integration with enterprise applications is still at the theoretical level. There is still no complete solution for the existing digital islands. Product vendors that provide enterprise applications are faced with different problems. Major manufacturers have long considered open business/system interfaces similar to SOA, and integration has a high level of integration for software vendors. Cost Problem. Non-mainstream manufacturers' products can only be integrated at the data level. In addition to high costs, they also exist. Technology Risk issues.

OA and enterprise applications

Dai ke believes that the application levels of different enterprises vary greatly, but the boundaries between enterprise applications and Oa are still obvious. It can be divided into production-related applications (such as EAM, billing, finance, ERP, PLM, and SCM) and management-related content.

In implementing OA, enterprises mainly adopt bi as a tool (or similar analysis and summary) and portal display as a means of integration. Although this method allows managers to see relatively complete data of enterprise operations, it cannot be associated with control and adjustment methods or methods. It may be just a map of information islands ", instead of actual connectivity.

"This situation is very unfavorable to small OA manufacturers in China, not only is it not very small, but it is always faced with the fate of being replaced ."

World-class OA applications

Dai ke believes that local OA lags behind world-class OA applications in many places, and this lag has already exceeded one level, because the methods and strategies adopted by IBM and Microsoft in OA front-end integration have been very advanced, and they were never imagined by OA in China.

"We believe that the launch of nd8 is the development of IBM from the back-end enterprise applications to the civilian direction, but also the direct use of Lotus and the boss in this field of Microsoft in the desktop market ." From the Desktop client perspective, the transformation from nd8 to the eclipse environment makes nd8 directly a client desktop based on open standards Platform In essence, IBM has pushed SOA to the front-end. This is an important progress, mainly because of Lotus's years of user experience and technical accumulation, as for Microsoft's S + s strategy, it can be understood that the integration of "service + client + Server .

It can be seen that the intention of front-end integration is already very obvious. The difference is that IBM can be directly deployed on the notes or the eclipse platform by using external components and plug-ins, third-party applications can be directly integrated, while Microsoft's office needs to be developed on its platform.

OA presentation methods and Problems

Although the existing maturity Workflow The platform has been able to perform secondary development and maintenance at a lower cost. However, the front-end lacks a unified presentation model, which is usually presented in the form of web pages. However, this method is not as intuitive as the Client GUI, it is also far from the user experience. In fact, in most of the current products, the workflow is displayed on the rich Web client, and the effect is very close to the development and maintenance environment in the C/S mode.

Dai Ke said, "From the past implementation experience, it is concluded that there are many problems with the pure B/S structure. Currently, the selection of technical diversity (such as Ajax and plug-in technology) is a client technology running in a browser and is no longer in the previous C/S mode, the client can also achieve zero maintenance, display power, speed, and functions far exceed the pure web."