PROJECT MANAGEMENT TECHNOLOGY
The process of complex automation of a medium enterprise, a large enterprise or a holding significantly differs from a standard accounting system implementation. The main difference is the demand for more complex accounting system or consolidation system for the entire branch structure. Such systems are the «1Ñ:Manufacturing Enterprise Management for Kazakhstan» and «1Ñ:Consolidation».
The specifics of project design on the automation of a large-scale enterprise is as follows:
Definition of scales:
from 30-40 up to 500-700 users
from 500-1000 up to 5000-7000 employees on automated enterprises
Definition of the automation process sequence of steps and the schedule for each step (averagely the period of execution is 4-9 months)
Involvement of the customer’s specialists with gradual transfer of knowledge from the contractor’s specialists
«1C-Rating» project team is a team of qualified specialists, competence of which is certified by the following certificates: PMI (Project Management Institute), «1C:Project Manager» and «1C:Specialist». The projects are managed within 34 GOST. Standards compliance improves projects quality and significantly reduces the risks.
The specifics of an enterprise is always taken into account and used to make an individual project map. The scheme of a project is provided below.
A project cycle includes the following steps:
Definition of project requirements.
Definition of technical solutions.
At this initial stage automation approaches are defined, enterprise’s general information is gathered, priority tasks and key requirements are defined, the effect of the system is evaluated. The end of this stage is the development of the Strategic Plan of project works. The entire project life cycle is attentively studied and a decision on the feasibility and possibility of project start is made.
This stage involves gathering of the enterprise’s detailed information, modeling of enterprise’s business processes «AS IS», evaluation of functioning quality of the enterprise of its business processes.
Problems that can be solved by means of automation are identified for the implementation and sustainable operation of the automated system. «TO BE» model’s general concept is offered (its detail is available in the next step).
Output document is the Impact Analysis report that is conducted in the following purposes: documenting of enterprise-customer’s business processes for the quality analysis; detailing the processes to be automated; decision-making about the necessity to reorganize allocated business processes to enable their automation or effectiveness improvement.
Definition of project requirements and technical solutions
At these stages a requirements to the projected system are formed, a detailed list of automated functions is compiled. Functions of subsystems, the info base concept of building and algorithms for problem solving are defined.
Development, design, coordination and approval of the Terms of Reference are carried out. Terms of Reference discloses the functional, related to the functionality of the system that is developed specifically for this project.
At this stage, specific solutions are implemented in the form of applications, hardware and documentation. The result is a complete system, which after preliminary tests is accepted as ready for the trial operation.
The following working documents may be created on the output of this stage: User Guide and Allocated subsystems technological instructions. These documents can be used by the Customer at workplaces for staff training.
Putting into operation is the preparation of the enterprise (including staff training) and also the automated software and hardware debugging, the data uploading into the info base, a comprehensive adjustment of all tools of the system, the trial operation.
This step creates the Test Example that is the emulation everyday user activity in the established information system. The emulation is approached to the real work as much as possible.
The result of these works is the system commercial operation, launched after the acceptance testing.
Maintenance and further development
The maintenance stage is the analysis of additional requirements occurred during the commercial operation.
The logic of system enhancements determines the necessary phases, that a new project will go through. The following exceptions are possible:
increase of the amount of stages or recurrence of steps. Example: repetition of steps for each enterprise in a holding and addition of steps for an information consolidation;
decrease of the amount of stages. Example: Customer’s IT-service can maintain the system independently.
Detailed information about the completed projects is available in the section «Examples of implementations».