ALP 1C

RusEng

Project Approach in the Creation of Mass-Marketing Solutions

The project approach to the creation of standardized replication solutions includes all the elements of the “classic project approach”, plus also:

  • development of a standardized accounting policy (if it hasn’t been developed previously);
  • adaptation of technical requirements (TR) to the specifics of the standardized accounting policy (If necessary);
  • creation of a pilot zone, consisting as a rule of leading branches;
  • organization of a competency centre (CC) (consisting as a rule of the most competent authorities and heads of the most successful branches in the pilot zone);
  • organization of a management committee with representatives from among the functional managers from the central office and the branches participating in the pilot (procedures
  • described in the Project charter);
  • creation of a Service Desk at the replication stage;
  • organization of a Change Committee.

Based on ALP Group’s experience in the development and implementation of standardized solutions, the following operations are carried out as a rule at each stage of the project life cycle:

  • At the project preparation stage:
    • potential risks are evaluated;
    • a project outline indicating primary stages and control points is composed;
    • the most important resources needed in the course of the project (competency centre work groups and methodologists) are planned;
    • the project charter is developed;
  • At the automated system (AS) conceptual planning stage:
    • interviewing and collection of information is conducted on the financial and economic activities of the companies and their level of IT support
    • the technical mission and technical plan are developed;
  • At the AS prototype development stage:
    • higher priority functionality development (includes automation of functions, documents, reports and processing with the shortest possible periodicity);
    • lower priority functionality is developed at the pilot production stage;
  • Developed at the pilot production stage:
    • completion and implementation of lower priority functionality upgrade to the first support line;
    • implementation of developed prototype;
    • closing of first accounting period (monthly) and preparation of reports for the month;
    • quarterly closing and preparation of quarterly accounts.

    The table below provides standard types of operations for multi-branch implementations and parameters influencing project costs.

    Name of Stage

    Type of Operations

    Parameters Influencing the Volume and Cost of Operations

    Initialization


    Briefing on platform installation and rollout of the 1C server

    Preparation of peripheral base (PB) schema for branches

    Briefing on database upgrade at branches, connection of subsystems to central bases (CB), test exchange of information

    Number of branches participating in the briefing

    Number of subsystems implemented

    Number of branches participating in upgrade simultaneously

    Number of branches participating in upgrade simultaneously

    Training

    Preparation of training course and test database

    Briefing on rollout of test database, preparation of training requirements

    Long-distance training

     


    Number of branches participating in upgrade

    Significant configurational differences between the prototype (standard configuration) and the production configurations

    Number of branches participating in upgrade simultaneously

    Training capabilities of users, considering the variety of accounting systems in use

    Briefing on input/output of initial data


    Briefing on the order for completion of work by stage

    Briefing on preparation of data for input to branch accounting systems

    Briefing on output of data to accounting systems (when impossible to download from existing accounting systems)

    Recommendations for the organization of Automated Work Spaces (AWS) for users, with consideration for the functional particulars of the subsystems

    Briefing on setting up users’ work (access rights, user registration in database)


     

    Variety of current accounting systems in branches

    Absence of accounting systems for objective quantitative accounting at individual branches

    Pilot Production Stage


    Briefing on the order for completion of work by stage

    Briefing on preparation of data for input to branch accounting systems

    Briefing on output of data to accounting systems (when impossible to download from existing accounting systems)

    Recommendations for the organization of Automated Work Spaces (AWS) for users, with consideration for the functional particulars of the subsystems

    Briefing on setting up users’ work (access rights, user registration in database)


     

    Number of branches participating in the Pilot Production Stage simultaneously

    Variety of current accounting systems in branches

    Number of modification requirements set at implementation. Existing modifications in new releases of typical subsystem configurations using the standard configuration as a prototype

    Number of requirements for modification set at implementation

    Time period for agreement on requirements for TRs and modification with the functional client

    Project Management

    Project Management


    Number of branches participating in the implementation simultaneously

    Time period for implementation