+994 055 505 05 37
office@icgroups.az
1. Tasks of the Stage:
1.1 Formation of the Joint Working Group (JWG), Joint Project Management (JPM), and Joint Supervisory Commission (JSC).
1.2 Preparation of Project Documents
1.3 Conducting the "Introduction to Project Technology (Part 1)" Seminar
1.4 Conducting a Survey at the "CUSTOMER" Organization to Assess Suitability and Readiness for Automation of Accounting
1.4.1 Technology and Communication
1.4.2 Training of Personnel
1.4.3 Formalizing and Documenting the Organizational Diagram to a Degree
1.4.4 Formalizing and Documenting the Management Diagram to a Degree
1.4.5 Time Allotment for the Project
1.4.6 Responsible and Authorized Individuals
1.4.7 Motivation of Personnel
1.4.8 Equal Conditions for Project Participants
1.4.9 Possibility to Adapt Organizational Diagrams
1.5 When Incomplete Readiness for Automation of Accounting Is Detected, the "MEASURE" Develops a List of Measures to Bring It to Full Readiness.
1.6 Prepare a Schedule for Implementing Measures for Full Readiness for Automation of Accounting for the "CUSTOMER."
1.7 Prepare a Comprehensive Work Plan
2. Stage Outcome:
2.1 ORG, OMP, JSC are Formed
2.1 Documents "Functions and Responsible Persons" (FIOL) and "List of Responsible Authorized Operations Personnel" (SOKOL) are approved (signed) by both parties, reflecting the composition of ORG, OMP, JSC and specifying roles of each key employee and their expertise and experience.
2.1 Document "On Commencement of Work on the "1C: ERP 2.0" Project"
2.1 Document "On Commencement of Work in the "Project Preparation" Stage"
2.2 Determine whether there is any deviation by presenting reasons, results, and consequences at the beginning of the "1C: ERP 2.0" Project and in the "Project Preparation" Stage.
2.2.1 Document "Record of Drafting 1" is approved (signed) at the beginning of the "1C: ERP 2.0" Project.
2.2.2 Document "Record of Drafting 2" is approved (signed) at the beginning of the "Project Preparation" Stage.
2.3 Schedule of "Introduction to Project Technology" Seminars is prepared.
2.3.1 Document "Schedule of Introduction to Project Technology Seminars" is approved (signed);
2.4 A seminar on the topic of "Introduction to Project Technology" has been conducted, and a travel log for the "Introduction to Project Technology" seminar has been prepared for ORG, OMP, JSC colleagues.
2.4.1 Approved (signed) document "Travel Log of OWG, OMP, JSC Employees for Introduction to Project Technology Seminars."
2.5 Tasks for the "Project Preparation" stage have been formulated
2.5.1 Approved (signed) document "Tasks for the Project Preparation Stage":
2.5.2 Schedule of contacts between parties for the "Project Preparation" stage has been prepared
2.5.3 Approved (signed) document "Schedule of Contacts for the Project Preparation Stage"
2.6 Verification procedure has been prepared
2.6.1 Approved (signed) document "Description of Verification Procedure for the Project Preparation Stage."
2.7 System requirements have been prepared
2.7.1 Approved (signed) document "Requirements for the System"
2.8 A survey has been conducted at the "CUSTOMER" to assess suitability and readiness for automation of accounting.
2.9 When full compliance and full readiness are discovered, the document "Act on the Full Compliance and Full Readiness of the "CUSTOMER" for the Automation of Accounting" is approved (signed)
2.10 When partial compliance and partial readiness are discovered, the document "Act on the Partial Compliance and Partial Readiness of the "CUSTOMER" for the Automation of Accounting" is approved (signed).
2.11 If there is a place for 2.9.2, a list of measures is prepared to bring the "CUSTOMER" to full compliance and full readiness.
2.11.1 Approved (signed) document "List of Measures for Bringing the "CUSTOMER" to Full Compliance and Full Readiness"
2.12 If there is a place for 2.9.2 and 2.10.1, then a schedule is arranged for implementing the "List of Measures for Bringing the "CUSTOMER" to Full Compliance and Full Readiness."
2.12.1 Approved (signed) document "Schedule for Implementing the List of Measures for Bringing the "CUSTOMER" to Full Compliance and Full Readiness"
2.13 A Comprehensive Work Plan (TIP) has been prepared;
2.13.1 Approved (signed) document "Comprehensive Work Plan"
3. Completion of the Stage
3.1 A notification has been prepared by "CONTRACTOR" regarding the completion of tasks in the "Project Preparation" stage, and it is presented to the "CUSTOMER" for inspection.
3.1.1 Approved (signed) document "Notification Regarding the Completion and Inspection of Work on Tasks in the "Project Preparation" Stage by "CONTRACTOR"
3.2 A notification has been prepared by the "CUSTOMER" regarding the acceptance and commencement of inspection of the execution of tasks in the "Project Preparation" stage by the "EXECUTOR" -I.
3.2.1 The "CUSTOMER" approved (signed) the document "Notification by the "CUSTOMER" about the "EXECUTOR's" Acceptance of the Execution of Tasks in the "Project Preparation" Stage and the Commencement of Inspection" and started the inspection.
3.3 According to the description of the "Inspection Procedure for the "Project Preparation" Stage," both Parties verify the alignment of the performed work with the tasks of the stage.
3.3.1 Approved (signed) document "Protocol of the Inspection Procedure Reflecting the Progress and Results of the Inspection" based on the description of the "Inspection Procedure for the "Project Preparation" Stage."
3.4 If deviations from the tasks of the "Project Preparation" stage are identified in completed work on stage.
3.4.1 Approved (signed) document "Interim Act Regarding the Non-Conformity of Completed Work with the Tasks of the "Project Preparation" Stage."
3.5 A list of identified non-conformities is prepared.
3.5.1 Approved (signed) document "List of Non-Conformities in the "Project Preparation" Stage."
3.6 A schedule for resolving non-conformities is prepared.
3.6.1 Approved (signed) document "Schedule for Resolving Non-Conformities."
3.7 The protocol of the "Inspection Procedure for the "Project Preparation" Stage" is used to carry out the next inspection procedure.
3.7.1 Approved (signed) "Protocol of the Inspection Procedure for the "Project Preparation" Stage."
3.8 When full compliance with the tasks of the "Project Preparation" stage is discovered in the performed work.
3.8.1 Approved (signed) document "Interim Act Regarding the Full Compliance of Performed Work with the Tasks of the "Project Preparation" Stage."
3.9 Determine whether there are any deviations in the completion of work in the "Project Preparation" stage.
3.9.1 Approved (signed) document "Record of Drafting 3" is approved (signed) and shows reasons, results, and consequences.
3.10 The activities of project participants are recorded in the "Project Preparation" stage.
3.10.1 Approved (signed) document "Participation Activity Log" for both parties' employees assigned to projects has been prepared.
1. Stage tasks
1.1 Seminar 2.
1.2 Compilation of stage tasks
1.3 Preparation of the verification procedure for the "Design" stage
1.4 Compilation of a detailed work plan (DPWP) for the "Design" stage
1.5 Survey for informing TRP about "CUSTOMER"
2.1 Act on the start of work in the "Design" stage
2.2 Determine the presence or absence of a deviation at the beginning of work in the "Design" stage, indicating the reasons, results, and consequences.
2.2.1 Approved (signed) document "Note on the record of deviations at the beginning of work in the "Design" stage".
2.3 A seminar on the topic of "Introduction to Project Technology" has been conducted, and a travel log for the "Introduction to Project Technology" seminar has been prepared for ORG, OMP, OCC colleagues.
2.3.1 Approved (signed) document "Travel Log of ORG, OMP, OCC Employees for the "Implementation" Seminars."
2.4 Tasks for the "Implementation" stage have been formulated
2.5 Schedule of contacts between parties for the "Implementation" stage has been prepared
2.5.1 Approved (signed) document "Schedule of Contacts for the "Implementation" Stage"
2.6 Verification procedure has been prepared for the "Implementation" stages
2.6.1 Approved (signed) document "Description of the Verification Procedure for the "Implementation" Stage"
2.7 Information has been entered into "TZP" with a survey
2.7.1 Functionality (detailed)
2.7.2 Access rights and roles
2.7.3 Interfaces
2.7.4 Output print forms
2.7.5 Data migration
2.7.6 System responsiveness
2.7.7 Physical data integrity
2.7.8 Protection from unauthorized access
2.7.9 Non-conflict with other software
2.7.10 Document "TPP" reflecting the information in sections 2.7.1 - 2.7.9 has been prepared and approved (signed)
2.7.11 The document "Procedure for Demonstrating the Prototype of the System" and the document "Experience" on test data are approved (signed) in accordance with the description of the "Verification Procedure for the "Implementation" Stages".
3. Completion of the Stage
2.8 Notification has been prepared by "CONTRACTOR" regarding the completion of tasks in the "Implementation" stage, and it is presented to the "CUSTOMER" for inspection.
2.8.1 Approved (signed) document "Notification Regarding the Completion and Inspection of Work on Tasks in the "Implementation" Stage by "CONTRACTOR".
2.9 Notification has been prepared by the "CUSTOMER" regarding the acceptance and commencement of inspection of the execution of tasks in the "Implementation" stage by the "EXECUTOR" -I.
2.9.1 The "CUSTOMER" approved (signed) the document "Notification by the "CUSTOMER" about the "EXECUTOR's" Acceptance of the Execution of Tasks in the "Implementation" Stage and the Commencement of Inspection" and started the inspection.
2.10 According to the description of the "Inspection Procedure for the "Implementation" Stage," both Parties verify the alignment of the performed work with the tasks of the stage.
2.10.1 Approved (signed) document "Protocol of the Inspection Procedure Reflecting the Progress and Results of the Inspection" based on the description of the "Inspection Procedure for the "Implementation" Stage."
2.11 If deviations from the tasks of the "Implementation" stage are identified in completed work on stage.
2.11.1 Approved (signed) document "Interim Act Regarding the Non-Conformity of Completed Work with the Tasks of the "Implementation" Stage."
2.12 A list of identified non-conformities is prepared.
2.12.1 Approved (signed) document "List of Non-Conformities in the "Implementation" Stage."
2.13 A schedule for resolving non-conformities is prepared.
2.13.1 Approved (signed) document "Schedule for Resolving Non-Conformities."
2.14 The protocol of the "Inspection Procedure for the "Implementation" Stage" is used to carry out the next inspection procedure.
2.14.1 Approved (signed) "Protocol of the Inspection Procedure for the "Implementation" Stage."
2.15 When full compliance with the tasks of the "Implementation" stage is discovered in the performed work.
2.15.1 Approved (signed) document "Interim Act Regarding the Full Compliance of Performed Work with the Tasks of the "Implementation" Stage."
2.16 Determine whether there are any deviations in the completion of work in the "Implementation" stage.
2.16.1 Approved (signed) document "Record of Drafting 3" is approved (signed) and shows reasons, results, and consequences.
2.17 The activities of project participants are recorded in the "Implementation" stage.
2.17.1 Approved (signed) document "Log of Participation Activities" for both Parties' employees in projects.
3.1 Stage tasks
3.1 Conducting the seminar
3.2 Defining stage objectives
3.3 Preparation of the verification procedure for the "Execution" stage
3.4 Compilation of a detailed work plan (DPWP) for the "Execution" stage
3.5 Work on "TZP"
3.6 Demonstration of completed TSP
3.2 Stage results
3.1 Act on the start of work in the "Execution" stage
3.2 Determine the presence or absence of a deviation at the beginning of work in the "Execution" stage, indicating the reasons, results, and consequences.
2.2.1 Approved (signed) document "Note on the record of deviations at the beginning of work in the "Execution" stage".
3.3 A seminar on the topic of "Introduction to Project Technology" has been conducted, and a travel log for the "Introduction to Project Technology" seminar has been prepared for ORG, OMP, OCC colleagues.
2.3.1 Approved (signed) document "Travel Log of ORG, OMP, OCC Employees for the "Execution" Seminars."
3.4 Tasks for the "Execution" stage have been formulated
3.5 Schedule of contacts between parties for the "Execution" stage has been prepared
2.5.1 Approved (signed) document "Schedule of Contacts for the "Execution" Stage"
3.6 Verification procedure has been prepared for the "Execution" stages
2.6.1 Approved (signed) document "Description of the Verification Procedure for the "Execution" Stage"
3.7 Work on "TZP" has been completed
2.7.1 Functionality (detailed)
2.7.2 Access rights and roles
2.7.3 Interfaces
2.7.4 Output print forms
2.7.5 Data migration
2.7.6 System responsiveness
2.7.7 Physical data integrity
2.7.8 Protection from unauthorized access
2.7.9 Non-conflict with other software
2.7.10 Document "ZIOZI Group" reflecting the execution of sections 2.7.1 - 2.7.9 is approved (signed)
2.7.11 The document "Procedure for Demonstrating the Prototype of the System" and the document "Experience" on test data are approved (signed) in accordance with the description of the "Verification Procedure for the "Execution" Stages."
3. 3. Completion of Stage
3.8 Notification has been prepared by "PODRATÇI" about the completion of tasks in the "Execution" stage and is handed over to the "CUSTOMER" for verification.
2.8.1. "PODRATÇI" has approved (signed) the document "Notification of completion of tasks in the Execution stage" and handed it over to the "CUSTOMER" for verification.
3.9 A notification has been prepared by the "CUSTOMER" regarding the acceptance and commencement of the execution of the tasks by the "Executor" from the "Executor" for the "Execution" stage.
2.9.1. The "Notification" document regarding the "CUSTOMER's" acceptance of the execution of the tasks by "PODRATÇI" has been approved (signed) - I has started executing the tasks for the "Execution" stage and commenced the verification.
3.10 According to the description of the verification procedure for the "Execution" stage, both Parties verify the compliance of the performed tasks with the stage's instructions.
2.9.2. The protocol for the implementation of the verification procedure for the "Execution" stage, reflecting the progress and results of the project, has been approved (signed).
If incomplete conformity with the tasks is identified for completed stages.
2.9.3. The interim report regarding the incomplete conformity of the performed tasks with the instructions of the "Execution" stage has been approved (signed).
3.10 A list of identified inconsistencies is compiled.
2.10.1. The document "List of inconsistencies in the Execution stage" has been approved (signed).
3.11 A schedule for the elimination of inconsistencies is prepared.
2.11.1. The document "Schedule for the elimination of inconsistencies" has been approved (signed).
3.12 The protocol for the verification procedure for the "Execution" stage is executed.
2.12.1. The protocol "Verification procedure for the Project stage" has been approved (signed).
3.13 When full conformity of the completed tasks with the instructions of the "Execution" stage is identified.
2.13.1. The interim report regarding the full conformity of the completed tasks with the instructions of the "Execution" stage has been approved (signed).
3.14 Determining whether there are deviations in completing the "Implementation" stage of the project.
2.14.1. The document "Record of Notes 3" has been approved (signed), indicating the reasons, results, and consequences.
3.15 The activity of project participants in the "Execution" stage is documented.
2.15.1. The document "Activity Journal of Participants" for both Parties' collaborators designated for the projects has been approved (signed).
1. Stage tasks:
1.1 Installation of 1C on the Server
1.2 Installation of 1C on Workstations
1.3 Remote Access (distributed databases/terminal)
1.4 Preparation of Excel forms for data loading
1.5 Filling out and submission of Excel forms
1.6 Checking data in Excel
1.7 Data loading
1.8 Checking the accuracy of loaded data
1.9 Enterprise Compliance Test
1.10 Preparation of clarifications
1.11 Refinement
1.12 System Test
1.13 Data Test
1.14 System test (bandwidth, resolution, security, etc.)
1.15 Individual user parameters (interface, access rights, comfort) Individual user parameters (interface, access rights, comfort)
1.16 Translation to Azerbaijani
1.17 Preparation of staff
1.18 Supervision
1.19 Identification and correction of errors
1.20 Preparation of control reports
1.21 Instructions and other documents
1.22 Operational readiness
2. Stage outcome:
2.1 Act on the commencement of work in the "Execution" stage
2.2 Determine whether there was a deviation at the beginning of the work in the "Implementation" stage, showing the reasons and consequences.
2.2.1 Approved (signed) document "Record of Notes 1" at the beginning of the "Execution" stage.
2.3 A seminar on "Introduction to Project Technology" was held and a travel journal for ORG, OMP, OCC collaborators for the seminar was compiled.
2.3.1 A seminar on "Introduction to Project Technology" was held, and a travel journal for ORG, OMP, OCC collaborators for the seminar was compiled.
2.4 Formulation of the tasks for the "Execution" stage
2.5 Preparation of the contact schedule between the parties for the "Execution" stages
2.5.1 Approved (signed) document "Contact Schedule for Execution Stage"
2.6 Preparation of the verification procedure for the "Execution" stage
2.6.1 Approved (signed) document "Description of the Verification Procedure for the Execution" stage
2.7 The system's management was reviewed and adjusted (servers, domain, MS SQL, network, cluster, remote connections, device connections)
2.8 Installation of 1C programs and licenses on servers and workstations, connection of remote servers and workstations, devices, mobile devices
2.9 Allocation of interfaces and access rights by roles
2.10 Collection and approval of data for loading historical or balance data
2.11 Checking the loaded data
2.12 "Prototyping System, Preparation of Specifications for Technical Assignments (UTZ)" was reviewed.
2.13 The prototype system was improved
2.14 The system was tested with real data and adjustments were made
2.15 Preparation of user documents (user manuals, description of features and limitations)
2.16 Conducting training
2.17 Storage of completed tasks
3. Completion of the Stage:
3.1 A notification has been prepared by "PODRATÇI" about the completion of tasks in the "Execution" stage and handed over to the "CUSTOMER" for verification.
3.1.1 "PODRATÇI" has approved (signed) the document "Notification of completion of tasks in the Execution stage" and handed it over to the "CUSTOMER" for verification.
3.2 The "CUSTOMER" has prepared a notification about the "Executor" accepting the execution of tasks from the "Executor" and commencing the verification for the "Execution" stage.
3.2.1 The "Notification" document regarding the "CUSTOMER's" acceptance of the execution of the tasks by "PODRATÇI" has been approved (signed) - I has started executing the tasks for the "Execution" stage and commenced the verification.
3.3 According to the description of the verification procedure for the "Execution" stage, both Parties verify the compliance of the performed tasks with the stage's instructions.
3.3.1 The protocol for the implementation of the verification procedure for the "Execution" stage, reflecting the progress and results of the project, has been approved (signed).
3.4 If incomplete conformity with the tasks is identified for completed stages.
3.4.1 The interim report regarding the incomplete conformity of the performed tasks with the instructions of the "Execution" stage has been approved (signed).
3.5 A list of identified inconsistencies is compiled.
3.5.1 The document "List of inconsistencies in the Execution stage" has been approved (signed).
3.6 A schedule for the elimination of inconsistencies is prepared.
3.6.1 The document "Schedule for the elimination of inconsistencies" has been approved (signed).
3.7 The protocol for the verification procedure for the "Execution" stage is executed.
3.7.1 The approved (signed) protocol "Verification procedure for the Project stage".
3.8 When full conformity of the completed tasks with the instructions of the "Execution" stage is identified.
3.8.1 The interim report regarding the full conformity of the completed tasks with the instructions of the "Execution" stage has been approved (signed).
3.9 Determining whether there are deviations in completing the "Implementation" stage of the project.
3.9.1 Approved (signed) document "Record of Notes 3", indicating the reasons, results, and consequences.
3.10 The activity of project participants in the "Execution" stage is documented.
3.10.1 The document "Activity Journal of Participants" for both Parties' collaborators designated for the projects has been approved (signed).
1. Stage tasks:
1.1 User Interaction
1.2 Experienced supervision of AIS
1.3 Control of AIMS compliance with prescribed tasks
1.4 Control of real tasks' compliance with declared AIMS capabilities
1.5 The document "List of errors and shortcomings of both Parties" was prepared
1.6 The document "List of additional works for free and paid" was compiled
1.7 Control of unforeseen problems of the 1C platform
1.8 Monitoring unforeseen SQL issues
1.9 Control of unforeseen IT problems
1.10 Preparation of AIMS working environment passport and service card
1.11 Storage of completed works
2. Stage result:
1.12 Act on the commencement of work in the "Pilot Operation" stage
1.13 Determining whether there was a deviation at the beginning of the work in the "Pilot Operation" stage, showing the reasons and consequences.
1.13.1 Approved (signed) document "Record of Notes 1" at the beginning of the "Pilot Operation" stage.
1.14 A seminar on "Introduction to Project Technology" was held, and a travel journal for ORG, OMP, OCC collaborators for the seminar was prepared.
1.14.1 Approved (signed) document "Travel journal of ORG, OMP, OCC employees" for the "Pilot Operation" seminar
1.15 Formulation of tasks for the "Pilot Operation" stage
1.16 Preparation of contact schedule between the parties for the "Pilot Operation" stages
1.16.1 Approved (signed) document "Contact Schedule for Pilot Operation Stage"
1.17 Preparation of the verification procedure for the "Pilot Operation" stage
1.17.1 Approved (signed) document "Description of the Verification Procedure for the Pilot Operation Stage"
1.18 User Interaction
1.19 Experienced supervision of AIS
1.20 Control of the determined compliance of AIS
1.21 Control of real tasks' compliance with declared capabilities of AIS
1.22 The document "List of errors and shortcomings of both Parties" was prepared
1.23 The document "List of additional works for free and paid" was compiled
1.24 Control of unforeseen problems of the 1C platform
1.25 Monitoring unforeseen SQL issues
1.26 Control of unforeseen IT problems
1.27 Preparation of AIMS working environment passport and service card
1.28 Storage of completed works
3. Completion of the Stage:
1.1. A notification has been prepared by "PODRATÇI" about the completion of tasks in the "Pilot Operation" stage and is handed over to the "CUSTOMER" for verification.
1.1.1 "PODRATÇI" has approved (signed) the document "Notification of completion of tasks in the Pilot Operation stage" and handed it over to the "CUSTOMER" for verification.
1.2. A notification has been prepared by the "CUSTOMER" regarding the acceptance and commencement of the execution of the tasks by the "Executor" from the "Executor" for the "Pilot Operation" stage.
1.2.1 The "Notification" document regarding the "CUSTOMER's" acceptance of the execution of the tasks by "PODRATÇI" has been approved (signed) - I has started executing the tasks for the "Pilot Operation" stage and commenced the verification.
1.3. According to the description of the verification procedure for the "Pilot Operation" stage, both Parties verify the compliance of the performed tasks with the stage's instructions.
1.3.1 The protocol for the implementation of the verification procedure for the "Pilot Operation" stage, reflecting the progress and results of the project, has been approved (signed).
1.4. If incomplete conformity with the tasks is identified for completed stages.
1.4.1 The interim report regarding the incomplete conformity of the performed tasks with the instructions of the "Pilot Operation" stage has been approved (signed).
1.5. A list of identified inconsistencies is compiled.
1.5.1 The document "List of inconsistencies in the Pilot Operation stage" has been approved (signed).
1.6. A schedule for the elimination of inconsistencies is prepared.
1.6.1 The document "Schedule for the elimination of inconsistencies" has been approved (signed).
1.7. The protocol for the verification procedure for the "Pilot Operation" stage is executed.
1.7.1 The approved (signed) protocol "Verification procedure for the Project stage".
1.8. When full conformity of the completed tasks with the instructions of the "Pilot Operation" stage is identified.
1.8.1 The interim report regarding the full conformity of the completed tasks with the instructions of the "Pilot Operation" stage has been approved (signed).
1.9. Determining whether there are deviations in completing the "Pilot Operation" stage of the project.
1.9.1 Approved (signed) document "Record of Notes 3", indicating the reasons, results, and consequences.
1.10. The activity of project participants in the "Pilot Operation" stage is documented.
1.10.1 The document "Activity Journal of Participants" for both Parties' collaborators designated for the projects has been approved (signed).