Dmitry R. , Lead, 1C developer

Development (construction)

1. Formation of the project team, development of architecture, technical supervision, formation and control of the development and integration process.
2. Formation and management of the development team (up to 10 people). Development of the target architecture. Modeling, designing, managing architecture, integration, development based on systems on the basis of 1C УХ/ДО. Technical supervision, task setting for developers. Code review and formation of the project's technical knowledge base. Development of data migration mechanisms from historical systems. Interaction with architects and the customer's PM.
3. Various types of metadata objects 1C УХ.
4. Formation of the team and full development cycle. Delivery of work stages to the customer.
5. Project solution, functional model, technical project solution, technical tasks, integration flow map.
6. Stopped staff turnover, formed stable work processes in a complex management environment.
7. BPMN.
8. Yandex-Wiki.
9. Refinement of seamless integration 1C УХ, 1C ДО.
10. Task setting: Yandex-tracker, Redmine.

Oil and gas, investments (corporation)

1. Block "Investment Programs" (Corporate Budgeting).
2. Design, prototyping, and development of non-standard functionality for the Corporate Budgeting subsystem in terms of investment programs. Interaction with the customer's working group.
3. Directories (investment objects, funding sources), documents (budget requests, funding limits), registers (budget movements, plan-fact), reports (plan-fact analysis).
4. The goal of the project is the implementation of a non-standard complex corporate-level budgeting subsystem with data migration from the historical system. Started with the survey and data migration from UPP. Came to the creation of a full-fledged contour of investment program management, allowing planning, agreeing, and controlling project budgets. Optimized the process of collecting and consolidating investment applications.
5. Technical project for the refinement of the subsystem, prototypes of interfaces and reports, methodology and regulation of data migration, user instructions.
6. Proud of designing and implementing complex non-standard functionality in a short time (5 months), which fully met the customer's needs. Strengthened my competencies in the field of investment planning.
7. Used for modeling business processes of approval, the customer's toolkit.
8. Requirements were recorded in meeting protocols, later in Confluence in the form of FT (functional requirements).
9. Main integration - migration of historical data from UPP. Also developed mechanisms for loading planned data from Excel. The complexity was in cleaning and normalizing "obsolete" data from UPP.
10. Task setting: Jira / internal customer systems.

Chemical industry (corporation)

1. Blocks OS/VNA/IFRS, Treasury, Budgeting, Contracts in DO.
2. Development of additional functionality in ERP.УХ in terms of accounting for fixed assets (OS), international standards (IFRS), treasury, and budgeting. Development of functionality in 1C DO for contract approval mechanisms and task execution control.
3. Documents on OS (modernization, disposal), IFRS registers, payment documents (payment requests), budget scenarios and limits, business processes of approval and tasks in DO.
4. The project started to deepen the automation of the financial block and create an end-to-end process "contract - budget - payment". Started with the analysis of "bottlenecks" in OS accounting and treasury. As a result, seamless integration between ERP and DO was ensured, which reduced the time for contract approval and increased payment discipline.
5. Technical tasks for the development of functionality in УХ and ДО, integration interaction schemes (business processes of approval), user instructions.
6. Proud of the implementation of a complex ERP-DO bundle. Gained experience in deep integration of two different configurations to ensure a closed cycle of contract and finance management.
7. Modeling of business processes of contract approval was carried out in BPMN notation.
8. Requirements were recorded in Confluence, task structure - in Jira.
9. Main integration - seamless between 1C ERP.УХ and 1C ДО. Technically, the task was not very difficult, but required careful synchronization of directories and document statuses.
10. Task setting: Through Jira.

Telecommunications (corporation)

1. Development of functional mechanisms for internal accounting.
2. Development of new functional mechanisms for internal accounting (nomenclature, services, contractors) in a non-standard configuration created on the basis of BSP. Development of additional functionality for the international subsidiary company of the reserve and bonus calculation system in ZUP KORP / BP KORP.
3. Directories, documents, registers, use of various BSP mechanisms.
4. The project was initiated to expand the functionality of the accounting system and migrate from the morally outdated 1C 7.7. Started with data analysis in 7.7 and external systems.
5. Development of regulations and mechanisms for data migration, technical documentation on new metadata objects.
6. Proud of the successful data migration from platform 7.7, which is often associated with encoding and data structure issues. Managed to maintain data integrity and historicity.
7. In this project, my role was more technical, business processes were not modeled.
8. Requirements were recorded in Jira.
9. Integration consisted of data migration from 1C 7.7 (via OLE/COM) and external sources. The complexity was in "polishing" the data, bringing them to the structure of the new configuration.
10. Task setting: Jira/Confluence.

Logistics, Foreign Economic Activity (corporation)

1. Development of functional mechanisms for internal accounting.
2. Development of new functional mechanisms for internal accounting (nomenclature, services, contractors) in a non-standard configuration created on the basis of BSP.
3. Directories, documents, registers, use of BSP mechanisms.
4. The project was initiated to expand the functionality of the accounting system in terms of logistics chains of cargo movement and transportation.
5. Development of regulations and mechanisms for data migration, technical documentation on new metadata objects.
6. Successful implementation of complex mechanisms for the movement of document chains for international activities of Foreign Economic Activity.
7. In this project, my role was more technical, business processes were not modeled.
8. Requirements were recorded in Jira cards.
9. Integration consisted of data migration from external sources.
10. Task setting: Jira/Confluence.