Development of management and corporate information system(CIS) introduction technique at plants of telecommunication branch
In development and introduction of CIS, specialists from consulting companies create their own technique, taking as a base the effective techniques of well-known developers of information technologies, however, at that the need arises of conformity to the national or international standards.
Consulting companies engaged in introduction of own CIS developments or systems with the world-wide name must possess not only good software product, but the well-arranged strategy for its introduction. The technique of CIS introduction in the end is a competitive advantage that differs one company from the other one.
The technique determines a list of work that can be used in process of CIS introduction in enterprises of telecommunication branch. It is intended for specialists of customer and executor′ design groups, who take part in introduction of information system. In the framework of the technique a set of requirements for design documents is generated: regulations (regulations of interaction of customer and executor′ designing groups), distribution if duties in the design introduction group, and regulations of agreement the results and etc.
Life cycle of CIS introduction project
According to PMI – the life cycle of a project is determined by phases, which connect the project start and its completion. Transition from one phase to another within the life cycle supposes the confirmation of results.
In process of work performance on the project the key results are design documents, that record obtained results. In case of information system introduction for medium and small size projects, initiation of following phase up to result ratification of the previous one has an acceptable risk. For such purposes the life cycle “Fast approach” can be used. For big companies more formal approach is preferable for ratification of results, supposing use of a classical approach for design cycle initiation.
However, this notice rather relates to software development, when the requirements for final product are specified constantly. In case of CIS introduction the project boundaries and restrictions to CIS realization are known in advance. In introduction of branch decision based on the reference model of business-processes a problem isn’t raise of inaccuracy in realization and testing a base functional of the decision, proposed by the platform developer (for example, there is no necessity of testing carefully the function of amortization evaluation of basic production assets).
Stages of CIS introduction project
A stage of a project consists of a number of connected tasks, which completion has a logically finished result. The stages are usually performed consistently, but can overlap in certain situations. Formal completion of a stage assumes confirmation of the received result from the side of customer and executor, the procedure of agreement is stated in project regulations. Initiation of following phase isn’t the task of previous one.
Division into phases is stipulated by the factors as follows: provision of transparency of project execution for management; determination of project′s control points; possibilities in case of necessity of making conservation/deconservation of a project; establishment of smoother schedule for financing.
The introduction technique is divided into the following phases::
- «Project planning»;
- «Analysis of requirements»;
- «Decision projection»;
- «Development and testing»;
- «Passing to exploitation»;
- «Industrial exploitation».
- In the framework of phase «Project planning» the organizational structure of introduction team is determined, interaction regulations and plan. The objectives and scales of the project are established. The simulation of business-processes of top level is carries out on a base of reference model. During the phase «Analysis of requirements» the familiarization of key users with standard functionality of a system is conducted, projection of future processes and collection of all detailed requirements for the system. The comparison of requirements and functionality of introduced system is carried out and architecture of CIS subsystems and integrated interaction are determined.
- The phase «Decision projection» assumes performance of system setting, creation of functional designs of extensions, projection of data conversion programs, scenarios preparation of system testing. Purchasingandassemblingofequipmentiscarriedout.
- During the phase «Development and testing» the extensions of program modules are created, conversion programs and interfaces with outward systems. In the framework of this phase two cycles are performed: system testing and development of user documentation. In the framework of phase «Passing to exploitation» the training of the end users is completed, data conversion is made and the system is getting ready for starting.
During the phase «Industrial exploitation» the system is inputted to industrial exploitation, a group is formed for maintenance arrangement, conservation of replaced systems is made. After this phase completion the analysis and comparison of actual results with tasks of a project is made.
CIS introduction processes
Each of the introduction processes represents a connected set of tasks, recourses, inputs and results. Onetaskcanbehabitualonlyfor oneprocess.
CIS introduction processes :
I)«Simulation of business-processes»;
II)«Development of requirements»;
III) «Creation of technical architecture»;
IV) «System setting»;
V)«Data conversion»;
VI)«Testing»;
VII)«Training».
Consulting companies engaged in introduction of own CIS developments or systems with the world-wide name must possess not only good software product, but the well-arranged strategy for its introduction. The technique of CIS introduction in the end is a competitive advantage that differs one company from the other one.
The technique determines a list of work that can be used in process of CIS introduction in enterprises of telecommunication branch. It is intended for specialists of customer and executor′ design groups, who take part in introduction of information system. In the framework of the technique a set of requirements for design documents is generated: regulations (regulations of interaction of customer and executor′ designing groups), distribution if duties in the design introduction group, and regulations of agreement the results and etc.
Life cycle of CIS introduction project
According to PMI – the life cycle of a project is determined by phases, which connect the project start and its completion. Transition from one phase to another within the life cycle supposes the confirmation of results.
In process of work performance on the project the key results are design documents, that record obtained results. In case of information system introduction for medium and small size projects, initiation of following phase up to result ratification of the previous one has an acceptable risk. For such purposes the life cycle “Fast approach” can be used. For big companies more formal approach is preferable for ratification of results, supposing use of a classical approach for design cycle initiation.
However, this notice rather relates to software development, when the requirements for final product are specified constantly. In case of CIS introduction the project boundaries and restrictions to CIS realization are known in advance. In introduction of branch decision based on the reference model of business-processes a problem isn’t raise of inaccuracy in realization and testing a base functional of the decision, proposed by the platform developer (for example, there is no necessity of testing carefully the function of amortization evaluation of basic production assets).
Stages of CIS introduction project
A stage of a project consists of a number of connected tasks, which completion has a logically finished result. The stages are usually performed consistently, but can overlap in certain situations. Formal completion of a stage assumes confirmation of the received result from the side of customer and executor, the procedure of agreement is stated in project regulations. Initiation of following phase isn’t the task of previous one.
Division into phases is stipulated by the factors as follows: provision of transparency of project execution for management; determination of project′s control points; possibilities in case of necessity of making conservation/deconservation of a project; establishment of smoother schedule for financing.
The introduction technique is divided into the following phases::
- «Project planning»;
- «Analysis of requirements»;
- «Decision projection»;
- «Development and testing»;
- «Passing to exploitation»;
- «Industrial exploitation».
- In the framework of phase «Project planning» the organizational structure of introduction team is determined, interaction regulations and plan. The objectives and scales of the project are established. The simulation of business-processes of top level is carries out on a base of reference model. During the phase «Analysis of requirements» the familiarization of key users with standard functionality of a system is conducted, projection of future processes and collection of all detailed requirements for the system. The comparison of requirements and functionality of introduced system is carried out and architecture of CIS subsystems and integrated interaction are determined.
- The phase «Decision projection» assumes performance of system setting, creation of functional designs of extensions, projection of data conversion programs, scenarios preparation of system testing. Purchasingandassemblingofequipmentiscarriedout.
- During the phase «Development and testing» the extensions of program modules are created, conversion programs and interfaces with outward systems. In the framework of this phase two cycles are performed: system testing and development of user documentation. In the framework of phase «Passing to exploitation» the training of the end users is completed, data conversion is made and the system is getting ready for starting.
During the phase «Industrial exploitation» the system is inputted to industrial exploitation, a group is formed for maintenance arrangement, conservation of replaced systems is made. After this phase completion the analysis and comparison of actual results with tasks of a project is made.
CIS introduction processes
Each of the introduction processes represents a connected set of tasks, recourses, inputs and results. Onetaskcanbehabitualonlyfor oneprocess.
CIS introduction processes :
I)«Simulation of business-processes»;
II)«Development of requirements»;
III) «Creation of technical architecture»;
IV) «System setting»;
V)«Data conversion»;
VI)«Testing»;
VII)«Training».
- 0
- 8 октября 2010, 23:50
- комментировать
Управление знаниями в современной ИТ-компании: место и роль проектирования
Тушавин В.А.
ассистент кафедры экономики и финансов Санкт-Петербургского государственного университета аэрокосмического приборостроения
Вопрос управления знаниями на современных российских предприятиях в настоящее время стоит достаточно остро. Как показывает практика, несмотря на то, что западные методологи уделяют все большое внимание этому виду активов (МСФО даже предусматривают, при соблюдении определенных условий, их отражение на балансовых счетах организации), в отечественной практике данный вид деятельности, как правило, игнорируется. Не составляют исключения и предприятия, работающие в области информационных технологий. Как известно, ИТ-специалисты относятся к категории интеллектуальных работников (knowledge workers): их нанимают ради знаний, теоретических и аналитических познаний, которыми они владеют, для обработки и преобразования информации и знаний. В то же время, одной из общемировых проблем в данной отрасли является кадровая проблема — нанять и удержать хорошего специалиста в области ИТ достаточно сложно, а с уходом специалиста для предприятия теряются все его знания и навыки. Именно поэтому решение задачи управления знаниями для ИТ-компании является жизненно важным.
( Читать дальше )
ассистент кафедры экономики и финансов Санкт-Петербургского государственного университета аэрокосмического приборостроения
Вопрос управления знаниями на современных российских предприятиях в настоящее время стоит достаточно остро. Как показывает практика, несмотря на то, что западные методологи уделяют все большое внимание этому виду активов (МСФО даже предусматривают, при соблюдении определенных условий, их отражение на балансовых счетах организации), в отечественной практике данный вид деятельности, как правило, игнорируется. Не составляют исключения и предприятия, работающие в области информационных технологий. Как известно, ИТ-специалисты относятся к категории интеллектуальных работников (knowledge workers): их нанимают ради знаний, теоретических и аналитических познаний, которыми они владеют, для обработки и преобразования информации и знаний. В то же время, одной из общемировых проблем в данной отрасли является кадровая проблема — нанять и удержать хорошего специалиста в области ИТ достаточно сложно, а с уходом специалиста для предприятия теряются все его знания и навыки. Именно поэтому решение задачи управления знаниями для ИТ-компании является жизненно важным.
( Читать дальше )
- 0
- 29 апреля 2010, 11:42
- комментировать
