logo.png
                                                                                                      russia.png Azerbaijani version English version

                                            +994 12 599 88 25
                                            office@icgroup.az                                     
                                   
                                              instagram-logo.png   facebook.png    VK   twitter  Whatsapp                           

Conditions and order of work

                                                                                                                                                                                     russia.png Azerbaijani version English version


List


The sequence of actions (or the order of work on the project) and the results of the stages of work:

Stage 1: Preparation for the project

1. Tasks of the stage:

1.1 Formation of the Joint Working Group (hereinafter JWG), the Joint Project Management (hereinafter OMP) and the Joint Control Commission (hereinafter JCC).


1.2 Preparation of working documentation


1.3 Conducting a seminar "Introduction to project technology (Part 1)"


1.4 Conducting a survey of the enterprise, the "CUSTOMER" -a for the purpose of identifying compliance and readiness for automation of accounting


1.4.1 Technology and communication


1.4.2 Trainability of employees


1.4.3 Degree of formalization and documentation of the organizational chart


1.4.4 Degree of formalization and documentation of the management scheme


1.4.5 Staff time allocated to the project


1.4.6 Responsible and Competent Persons


1.4.7 Motivation of staff


1.4.8 Equal conditions for project participants


1.4.9 Ability to adjust organizational charts to the system


1.5 In case of detection of incomplete readiness of the enterprise, the "CUSTOMER" to automate accounting, develop a list of measures to bring to a state of full readiness for automation of accounting


1.6 Develop a schedule for the implementation of measures to bring the enterprise, "CUSTOMER" to a state of full readiness for automation of accounting


1.7 Develop an overall work plan



2. The result of the stage: 

2.1 Formed ORG, OMP, OCC


2.1.1 Approved (signed) documents "Functions and Responsible Persons" (FIOL) and "List of Responsible Competent Operating Persons" (SOKOL) reflecting the composition of the ORG, OMP, OCC on both sides, defining the roles of each key employee and indicating qualifications and experience each key employee


2.1.2 Act on the beginning of work on the Project "1C: ERP 2.0"


2.1.3 Act on the beginning of work on the stage "Project Preparation"


2.2 Recording the presence or absence of deviations at the beginning of work on the "1C: ERP 2.0" Project and at the "Project preparation" stage, indicating the reasons, results and outcomes.


           2.2.1 Approved (signed) document "Record of deviation sheet 1" at the beginning of the Project "1C: ERP 2.0"


2.2.2 Approved (signed) document "Deviation Statement 2 Record" at the beginning of the "Project Preparation" stage


2.3 Schedule of seminars "Introduction to the project technology"


2.3.1 Approved (signed) document "Schedule of seminars introduction to project technology";


2.4 A seminar was held on the topic "Introduction to project technology" and a log of visits by employees of the ORG, OMP, OCC to the seminar "Introduction to project technology" was compiled


2.4.1 Approved (signed) document "Journal of visits by employees of the ORG, OMP, OKK seminars introduction to the technology of the project."


2.5 The tasks of the stage "Project Preparation


2.5.1 Approved (signed) document "Tasks of the Project Preparation Stage":


2.5.2 Developed a schedule of contacts between the parties for the stages of "Project Preparation"


2.5.3 Approved (signed) document "Schedule of contacts at the stage of Preparation


project "


2.6 Verification procedure developed


2.6.1 Approved (signed) document "Description of the verification procedure for the stage" Project Preparation "".


2.7 System requirements developed


2.7.1 Approved (signed) document "System Requirement"


2.8 A survey was carried out to determine the conformity and readiness of the enterprise, the "CUSTOMER" to automate accounting


2.9 If full compliance and complete readiness is found, then the document "Act on full compliance and full readiness of the enterprise," CUSTOMER "for accounting automation" is approved (signed)


2.10 If incomplete compliance and incomplete readiness is found, then the document "Act on incomplete compliance and incomplete readiness of the enterprise," CUSTOMER "for accounting automation" is approved (signed)


2.11 If 2.9.2 takes place, then a list of measures is developed to bring the CUSTOMER enterprise to full compliance and to full readiness. "


2.11.1 The document "List of measures to bring the enterprise" CUSTOMER "to full compliance and to full readiness" is approved (signed).


2.12 If 2.9.2 and 2.10.1 take place, then a schedule is drawn up for the implementation of the "List of measures to bring the CUSTOMER enterprise to full compliance and to full readiness."


2.12.1 The document "Schedule for the implementation of the list of measures to bring the CUSTOMER enterprise to full compliance and to full readiness" is approved (signed).


2.13 The General Work Plan (hereinafter the PIU) has been developed;


2.13.1 Approved (signed) document "General Work Plan"


3. Completion of the stage

3.1 A notification from the "CONTRACTOR" has been drawn up that he has completed the tasks of the "Project preparation" stage and has been submitted for verification by the "CUSTOMER".


3.1.1 Approved (signed) document "Notification that the" CONTRACTOR "has completed work on the tasks of the stage" Preparation of the project "and handed them over to the" CUSTOMER "for verification".


3.2 A notification from the "CUSTOMER" has been drawn up, stating that the "CUSTOMER" has accepted the performance of work from the "CONTRACTOR" on the tasks of the "Preparation of the Project" stage for verification and has begun verification.


3.2.1 Approved (signed) document "Notification that the" CUSTOMER "has accepted the execution of work from the" EXECUTOR "-th on the tasks of the stage" Preparation of the Project "for verification and began verification".


3.3 According to the document "Description of the Check procedure for the" Prepare Check "stage", both Parties carried out a check for the compliance of the work performed with the tasks of the stage.


3.3.1 The document "Protocol of the verification procedure, which reflects the progress and results of the verification" was approved (signed).


3.4 If incomplete correspondence of the completed work to the task by stages is found.


3.4.1 The document "Interim Act on the incomplete compliance of the completed work with the tasks of the" Project Preparation "stage" was approved (signed).


3.5 A list of detected inconsistencies is compiled.


3.5.1 Approved (signed) document "List of nonconformities for the stage" Project Preparation ".


3.6 A schedule for the elimination of nonconformities is drawn up.


3.6.1 Approved (signed) document "Schedule for elimination of inconsistencies".


3.7 The next verification procedure was carried out "Protocol of the verification procedure at the stage of Project Preparation"


3.7.1 Approved (signed) protocol "Verification procedure at the stage of Project Preparation".


3.8 If full compliance of the work performed with the tasks of the "Project preparation" stage is found


3.8.1 Approved (signed) the document "Interim Act on the full compliance of the work performed with the tasks of the stage" Preparation of the Project at the stage of Preparation of the Project "".


3.9 Fixation of the presence or absence of deviations in the completion of work at the stage "Project Preparation at the Project Preparation stage"


3.9.1 Approved (signed) document "Record of variance statement 3" indicating the reasons, results and outcomes.


3.10 The activity of the Project participants is recorded at the "Project Preparation" stage


3.10.1 Approved (signed) document "Journal of participation activity" allocated to the Projects employees of both Parties

Stage 2: Design

    1. Tasks of the stage

1.1 Conducting a workshop 2.


1.2 Drawing up the tasks of the stage


1.3 Development of a verification procedure for the "Design" stage


1.4 Drawing up a detailed work plan (PDWP) for the "Design" stage


1.5 Request to the "CUSTOMER" -y to provide information to the TZP


  1. Stage results

2.1 Act on the beginning of work on the stage "Design"


2.2 Fixing the presence or absence of deviations at the beginning of work on the "Design" stage, indicating the reasons, results and outcomes.


2.2.1 Approved (signed) document "Record of deviation sheet 1" at the beginning of the work of the "Design" stage


2.3 A seminar was held on the topic "Introduction to project technology" and a log of visits by employees of the ORG, OMP, OCC to the seminar "Introduction to project technology" was compiled


2.4 Approved (signed) document "Journal of visits by employees of the ORG, OMP, OKK seminars" Design ".


2.5 Formed the tasks of the stage "Design"


2.5.1 Approved (signed) document "Design Stage Tasks"


2.6 Developed a schedule of contacts between the parties for the stages "Design"


2.6.1 Approved (signed) document "Schedule of contacts at the Design stage"


2.7 The verification procedure for the "Design" stage has been developed


2.7.1 Approved (signed) document "Description of the verification procedure for the" Design "stage

       

2.8 Information received on request to "TZP"


2.8.1 Functionality (detail)


2.8.2 Access rights and roles


2.8.3 Interfaces


2.8.4 Output printable forms


2.8.5 Data Migration


2.8.6 System Resiliency


2.8.7 Physical data security


2.8.8 Protection against unauthorized access


2.8.9 Conflict with other software


2.8.10 Developed and Approved (signed) document "TZP", which displays information from clauses 2.8.1 - 2.8.9


      3. Completion of the stage

2.9 A notification from the "CONTRACTOR" has been drawn up that he has completed the tasks of the "Design" stage and has been submitted for verification by the "CUSTOMER".


2.9.1 Approved (signed) document "Notification that the" CONTRACTOR "completed work on the tasks of the" Design "stage and handed them over to the" CUSTOMER "for verification".


2.10 A notification from the "CUSTOMER" has been drawn up, stating that the "CUSTOMER" has accepted the performance of work from the "CONTRACTOR" on the tasks of the "Design" stage and has begun verification.


2.10.1 Approved (signed) document "Notification that the CUSTOMER accepted the execution of work from the" CONTRACTOR "-th on the tasks of the" Design "stage and began checking.


2.11 According to the document "Description of the verification procedure for the" Design "stage", both Parties carried out a check for compliance of the work performed with the tasks of the stage.


2.11.1 Approved (signed) document "Protocol of the procedure for the stage" Design ", which reflects the progress and results of the design".


2.12 If an incomplete correspondence of the completed work to the task by stages is found.


2.12.1 The document "Interim Act on the incomplete compliance of the work performed with the tasks of the" Design "stage was approved (signed).


2.13 A list of detected inconsistencies is compiled.


2.13.1 Approved (signed) document "List of nonconformities at the stage" Design ".


2.14 A schedule is drawn up for eliminating inconsistencies.


2.14.1 The document "Schedule for eliminating inconsistencies" was approved (signed).


2.15 The next verification procedure was carried out "Protocol of the verification procedure at the" Design "stage"


2.15.1 Approved (signed) protocol "Verification procedure at the design stage".


2.16 If full compliance of the performed work with the tasks of the "Design" stage is found


2.16.1 Approved (signed) the document "Interim Act on the full compliance of the work performed with the tasks of the" Design "stage".


2.17 Fixation of the presence or absence of deviations in the completion of work at the stage "Preparation of the Project at the stage" Design ""


2.17.1 Approved (signed) document "Record of variance statement 3" indicating the reasons, results and outcomes.


2.18 The activity of the Project participants at the "Design" stage is recorded. "


2.18.1 The document "Journal of Participation Activity" of the employees of both Parties allocated for the Projects was approved (signed).

Stage 3: Implementation

3.1 Tasks Stage

3.1 Conducting a seminar


3.2 Processing Stage Tasks


3.3 Development of a procedure for verification in the "Sales" stage


3.4 Drawing up a detailed work plan (DRPS) at the "Sales" stage


3.5 Work on TZP


3.6 Demonstration of the TZP


3.2 Stage results

3.1 Act on the beginning of work on the stage "Implementation"


3.2 Fixation of the presence or absence of deviations at the beginning of work on the stage "Implementation", indicating the reasons, results and outcomes.


2.2.1. The document "Record of the deviation sheet 1" was approved (signed) at the beginning of the work of the "Implementation" stage


3.3 A seminar on the topic "Introduction to project technology" was held and a log of visits by employees of the ORG, OMP, OCC to the seminar "Introduction to project technology" was compiled


2.3.1. Approved (signed) document "Journal of visits by employees of the ORG, OMP, OKK seminars" Implementation ".


3.4 The tasks of the stage "Implementation" are formed


3.5 Developed a schedule of contacts between the parties for the stages "Implementation"


2.5.1. Approved (signed) document "Schedule of contacts at the Implementation stage"


3.6 A verification procedure for the "Implementation" stage has been developed


2.6.1. Approved (signed) document "Description of the verification procedure for the stage" Implementation "



3.7 Completed work on "TZP"


2.7.1. Functionality (detail)


2.7.2. Access rights and roles


2.7.3. Interfaces


2.7.4. Output printing forms


2.7.5. Data migration


2.7.6. System resiliency


2.7.7. Physical data security


2.7.8. Protection against unauthorized access


2.7.9. Conflict with other software


2.7.10. The document "Collection of ZIOZI" on the implementation of clauses 2.8.1 - 2.8.9 is approved (signed)


2.7.11. The document "Conducting a demonstration of the System Prototype" is approved (signed) in accordance with the document "Description of the verification procedure for the" Implementation "stage, on test data.

3. 3. Completion of the stage

3.8 A notification from the "CONTRACTOR" has been drawn up stating that he has completed the tasks of the "Implementation" stage and has been submitted for verification by the "CUSTOMER".


2.8.1. Approved (signed) document "Notification that the" CONTRACTOR "completed work on the tasks of the" Implementation "stage and handed them over to the" CUSTOMER "for verification".


3.9 A notification from the "CUSTOMER" has been drawn up, stating that the "CUSTOMER" has accepted the performance of work from the "CONTRACTOR" on the tasks of the "Implementation" stage and has begun verification.


2.9.1. The document "Notification that the CUSTOMER" accepted the execution of work from the "CONTRACTOR" on the tasks of the "Implementation" stage was approved (signed) and began checking.


3.10. According to the document "Description of the verification procedure for the stage" Implementation "", both Parties carried out a check for compliance of the work performed with the tasks of the stage.


2.9.2. The document "Protocol of the procedure for the stage" Implementation ", which reflects the progress and results of the design, was approved (signed).


If an incomplete match of the completed work to the task by stages is detected.


2.9.3. The document "Interim Act on the incomplete compliance of the completed work with the tasks of the" Implementation "stage was approved (signed).


3.10 A list of detected inconsistencies is drawn up.


2.10.1. The document “List of inconsistencies for the stage“ Implementation ”was approved (signed).


3.11 A schedule for the elimination of nonconformities is drawn up.


2.11.1. The document "Schedule for eliminating inconsistencies" was approved (signed).


3.12 The next verification procedure was carried out "Protocol of the verification procedure at the stage" Implementation "


2.12.1. Approved (signed) protocol "Verification procedure at the design stage".


3.13 If full compliance of the work performed with the tasks of the "Implementation" stage is found


2.13.1. The document "Interim Act on the full compliance of the performed works with the tasks of the" Implementation "stage was approved (signed)


3.14 Fixation of the presence or absence of deviations in the completion of work at the stage "Preparation of the Project at the stage" Implementation "


2.14.1. The document "Record of the deviation sheet 3" was approved (signed), indicating the reasons, results and outcomes.


3.15 The activity of the Project participants is recorded at the stage "Implementation"


2.15.1. The document "Journal of Participation Activity" of the employees of both Parties allocated for the Projects was approved (signed).


Stage 4: Implementation

1. Tasks of the stage:

1.1 Installing 1C on the server


1.2 Installing 1C on workstations


1.3 Remote access (distributed bases / terminal)


1.4 Preparing Excel Forms for Loading Data


1.5 Completing and Submitting Excel Forms


1.6 Checking the correctness of data in Excel


1.7 Loading data


1.8 Testing the correctness of the loaded data


1.9 Testing for Compliance with Enterprise Requirements


1.10 Drafting clarifications


1.11 Refinement


1.12 Testing the System


1.13 Data Testing


1.14 Testing the System (throughput, fault tolerance, protection, etc.)


1.15 Individual user settings (interface, access rights, convenience)


1.16 Translation into Azeri


1.17 Staff training


1.18 Escort


1.19 Finding and fixing bugs


1.20 Preparation of audit reports


1.21 Instructions and other documentation


1.22 Preparation for use

2. The result of the stage:

2.1 Act on the beginning of work on the stage "Implementation"


2.2 Fixation of the presence or absence of deviations at the beginning of work on the "Implementation" stage, indicating the reasons, results and outcomes.


2.2.1 Approved (signed) document "Record of deviation sheet 1" at the start of work of the "Implementation" stage


2.3 A seminar was held on the topic "Introduction to project technology" and a log of visits by employees of the ORG, OMP, OCC to the seminar "Introduction to project technology" was compiled


2.3.1 Approved (signed) document "Journal of visits by employees of the ORG, OMP, OKK seminars" Implementation "


2.4 The tasks of the "Implementation" stage have been formed


2.5 Developed a schedule of contacts between the parties for the stages of "Implementation"


2.5.1 Approved (signed) document "Schedule of contacts at the Implementation stage"


2.6 A verification procedure has been developed for the "Implementation" stage


2.6.1 Approved (signed) document "Description of the verification procedure for the stage" Implementation "



2.7 Checked and adjusted the system landscape (server, domain, MS SQL, network, cluster, remote connections, equipment connections)


2.8 Installing 1C programs and licenses on servers and workstations, connecting remote servers and workstations, equipment, mobile devices


2.9 Distribution of interfaces and access rights by roles


2.10 Collecting and verifying data for loading history or residuals


2.11 The downloaded data has been verified


2.12 Checked the "System Prototype, drafting the Clarifications to the Terms of Reference (TOR)"


2.13 Completed prototype refinement Prior to the System


2.14 The system was checked on real data and corrections were made


2.15 User documentation has been compiled (user instructions, description of capabilities and limitations)


2.16 Delivery of training


2.17 Storage of completed work



3. Completion of the stage:

3.1 A notification from the "CONTRACTOR" has been drawn up that he has completed the tasks of the "Implementation" stage and has been submitted for verification by the "CUSTOMER".


3.1.1. The document “Notification that the“ CONTRACTOR ”has completed work on the tasks of the“ Implementation ”stage was approved (signed) and handed them over to the“ CUSTOMER ”for verification."


3.2 A notification from the "CUSTOMER" has been drawn up that the "CUSTOMER" has accepted the performance of work from the "CONTRACTOR" on the tasks of the "Implementation" stage and has begun verification.


3.2.1. The document "Notification that the CUSTOMER" accepted the execution of work from the "CONTRACTOR" on the tasks of the "Implementation" stage was approved (signed) and began checking.


3.3 According to the document "Description of the verification procedure for the stage" Implementation "", both Parties carried out a check for compliance of the work performed with the tasks of the stage.


3.3.1. The document "Protocol of the procedure for the stage" Implementation ", which reflects the progress and results of the design, was approved (signed).


3.4 If incomplete correspondence of the completed work to the task by stages is found.


3.4.1. The document "Interim Act on the incomplete compliance of the work performed with the tasks of the" Implementation "stage was approved (signed).


3.5 A list of detected nonconformities is compiled.


3.5.1. The document “List of inconsistencies for the“ Implementation ”stage was approved (signed).


3.6 A schedule for rectifying inconsistencies is drawn up.


3.6.1. The document "Schedule for eliminating inconsistencies" was approved (signed).


3.7 The next verification procedure was carried out "Protocol of the verification procedure at the stage" Implementation "


3.7.1. Approved (signed) protocol "Verification procedure at the design stage".


3.8 If full compliance of the performed work with the tasks of the "Implementation" stage is found


3.8.1. Approved (signed) document "Interim Act on the full compliance of the work performed with the tasks of the" Implementation "stage"


3.9 Fixing the presence or absence of deviations in the completion of work at the stage "Preparation of the Project at the stage" Implementation ""


3.9.1. The document "Record of the deviation sheet 3" was approved (signed), indicating the reasons, results and outcomes.


3.10 The activity of the Project participants at the "Implementation" stage is recorded


3.10.1. The document "Journal of Participation Activity" of the employees of both Parties allocated for the Projects was approved (signed).


Stage 5: Experimental Operation

1. Tasks of the stage:

1.1 User support


1.2 Experienced control of AISU


1.3 Control of compliance of the AISU with the prescribed tasks


1.4 Control of compliance of real tasks with the declared capabilities of AISU


1.5 A document "List of errors and shortcomings of both Parties" has been drawn up


1.6 The document "List of additional works free of charge and paid" has been drawn up


1.7 Controlling unforeseen problems of the 1C platform


1.8 Controlling unexpected SQL problems


1.9 Controlling unforeseen IT problems


1.10 Drawing up a passport of the AISU working environment and a service card


1.11 Storage of completed work



2. The result of the stage:

1.12 Act on the beginning of work on the stage "Experimental Operation"


1.13 Fixation of the presence or absence of deviations at the beginning of work on the "Experimental Operation" stage, indicating the reasons, results and outcomes.


1.13.1 The document "Record of the deviation sheet 1" was approved (signed) at the beginning of the work of the "Experimental Operation" stage


1.14 A seminar was held on the topic "Introduction to project technology" and a log of visits by employees of the ORG, OMP, OCC to the seminar "Introduction to project technology" was compiled


1.14.1 Approved (signed) document "Journal of visits by employees of the ORG, OMP, OKK seminars" Experimental Operation "


1.15 The tasks of the "Experimental Operation" stage are formed


1.16 Developed a schedule of contacts between the parties for the "Pilot Operation" stages


1.16.1 Approved (signed) document "Schedule of contacts at the stage of" Experimental Operation "


1.17 A verification procedure for the "Experimental Operation" stage has been developed


1.17.1 Approved (signed) document "Description of the verification procedure for the stage" Experimental Operation "


1.18 User support


1.19 Experienced control of AISU


1.20 Control of compliance of the AISU with the prescribed tasks


1.21 Control of compliance of real tasks with the declared capabilities of AISU


1.22 A document "List of errors and shortcomings of both Parties" has been drawn up


1.23 The document "List of additional works free of charge and paid" has been drawn up


1.24 Control of unforeseen problems of the 1C platform


1.25 Controlling unexpected SQL problems


1.26 Controlling unforeseen IT problems


1.27 Drawing up a passport of the AISU working environment and a service card


1.28 Storage of completed work



3. Completion of the stage:

1.1. A notice was drawn up from the "CUSTOMER", that the "CUSTOMER" accepted the execution of work from the "EXECUTOR" on the tasks of the "Experimental Operation" stage and began checking.


1.1.1. The document "Notification that the CUSTOMER" accepted the execution of work from the "CONTRACTOR" on the tasks of the "Experimental Operation" stage was approved (signed) and began checking.


1.2. According to the document "Description of the verification procedure for the" Experimental Operation "stage, both Parties carried out a check for the compliance of the work performed with the tasks of the stage.


1.2.1. The document "Protocol of the procedure for the" Experimental Operation "stage, which reflects the progress and results of the design, was approved (signed).


1.3. Incomplete correspondence of the completed work to the task by stages was detected.


1.3.1. The document “Interim Act on incomplete compliance of the performed works with the tasks of the“ Experimental Operation ”stage” was approved (signed).


1.4. A list of detected inconsistencies is compiled.


1.4.1. The document “List of discrepancies in the“ Experimental Operation ”stage was approved (signed).


1.5. A schedule is drawn up for resolving inconsistencies.


1.5.1. The document "Schedule for eliminating inconsistencies" was approved (signed).


1.6. The next verification procedure was carried out "Protocol of the verification procedure at the stage" Experimental Operation "


1.6.1. Approved (signed) protocol "Verification procedure at the design stage".


1.7. Full correspondence of the work performed to the tasks of the "Experimental Operation" stage was found


1.7.1. Approved (signed) document "Interim Act on full compliance of the work performed with the tasks of the stage" Experimental Operation "


1.8. Fixing the presence or absence of deviations in the completion of work at the stage "Preparation of the Project at the stage of" Experimental Operation ""


1.8.1. The document "Record of the deviation sheet 3" was approved (signed), indicating the reasons, results and outcomes.


1.9. The activity of the Project participants is recorded at the "Experimental Operation" stage


1.9.1. The document "Journal of Participation Activity" of the employees of both Parties allocated for the Projects was approved (signed).


List