1
Алексей
no recommendations
no complaints
Project title: Software development
Type of cooperation: One-time project
Section: Software development
Prepayment: without prepayment
Payment methods: Bank transfer
Acceptance of requests: from 2019-11-24 until 2019-11-29
Type of cooperation: One-time project
Section: Software development
Prepayment: without prepayment
Payment methods: Bank transfer
Acceptance of requests: from 2019-11-24 until 2019-11-29
Project description:
Programmer services are required. Software development. The main goal of the project*: to develop software that allows you to automatically create a PRKO file, as well as store created documents with the ability to automatically generate changes in them if necessary.
In addition, it is necessary to save the document change history (PRKO), provide access to each individual PRCO file, and allow viewing the current version of the PRCO file.
* Reference: in the case of the formation of the first decision on the client, it will be necessary to manually enter all information in the PRKO template. The input will be similar to the current template filling procedure except that the formation of additional rows/cells/partitions will be automated and the performer will not need to work with changing the template table. Following the results of entering data into the PRKO, the contractor will be able to form this file in word format.
The main requirements of the software:
1. The login to the program will be carried out by each user on the basis of a login and password.
2. The login and password will be stored in an encrypted database.
3. Roles with different access rights
4. Each CI has the right to access a certain pool of clients and has the right to grant / terminate access to its customers by employees of other services.
5. The program interface should be close to the CRM interface in order to ensure the comfort of using this software by the executor.
6. The technology of forming the 1st PRKO on the client will be almost similar to the current process (automation will affect only actions aimed at forming a specific PRKO template, information will be manually entered into the primary PRKO)
7. As part of creating a single platform for coordination, the services, in addition to the CPU, will also have access to the decision file for the purpose of formatting it in the program itself as part of the coordination process.
8. Each PRRO file will be assigned a status in the program that will make the current stage of work on PRRO understandable.
9. The program will not implement a mail server that provides notifications to program users about the change in the status of a separate PRKO file or changes made. This decision is due to the additional complexity of the development and configuration of such a server and insignificant attitude to the sanitary task of the software being developed.
10. Notifications will be sent to users about the origin of any changes to their customers within the program itself.
11. Within the framework of the proposed software, only the PRCO will be formed for the NCL product, i.e., the NCL will be formed. You can create an initial solution, make changes to it.
12. To make changes to the previously made decision, it will be necessary to select by check box those sections of the decision that need to be adjusted / supplemented and a new solution will be created by means of the “form” button to change the condition with the “cancellable parameters” fields already filled in, where only the “approved parameters” will remain to be filled in.
13. After the approval of the PRKO in the program and the decision is made, the CI changes the status of the decision to amend to "adopted", makes the No and the date after which the decision is embedded in the program as adopted. Additionally, the CI downloads a scan of the decision from the CA Secretary to confirm the decision.
14. The structure of the programme will provide a function of viewing the history of any PRCO, i.e. You can see when the decision was made, when the changes were made, and with the help of a “one click” you can see the essence of the changes made.
15. The obligatory function of the program will be possible to display the current version of the decision on one screen, i.e., the same. There are PRCOs on approval of the loan and 10 changes to it and to understand the current conditions you do not need to work with 11 documents, you just need to click the button “see the current conditions” and the decision to approve the loan in the version of 10 changes is displayed on the screen.
16. The program will make it possible to form in one file a decision - approval of products for several borrowers of the State Health Service. It will also be possible to make changes to several products of different customers.
17. The program will automatically determine by several IDs (product ID, NCL number, etc.) which data from new solutions will need to be attributed to the decisions already made.
18. It will be possible to leave a brief descriptive part for each PRRO file, which will give an understanding of why the change was made.
19. Navigation on the program should be convenient and intuitive to the user.
20. The program will implement a logical correspondence between: No solution, product in CRM / Exel application, client, SSZ.
21. The search for accepted PRKO will be carried out either through the No and date, or through the No of the NCL to which it refers, or through the TIN you can find all the products of the client and, accordingly, the PRKO itself.
22. The developed software should promptly respond to user actions
Programmer services are required. Software development. The main goal of the project*: to develop software that allows you to automatically create a PRKO file, as well as store created documents with the ability to automatically generate changes in them if necessary.
In addition, it is necessary to save the document change history (PRKO), provide access to each individual PRCO file, and allow viewing the current version of the PRCO file.
* Reference: in the case of the formation of the first decision on the client, it will be necessary to manually enter all information in the PRKO template. The input will be similar to the current template filling procedure except that the formation of additional rows/cells/partitions will be automated and the performer will not need to work with changing the template table. Following the results of entering data into the PRKO, the contractor will be able to form this file in word format.
The main requirements of the software:
1. The login to the program will be carried out by each user on the basis of a login and password.
2. The login and password will be stored in an encrypted database.
3. Roles with different access rights
4. Each CI has the right to access a certain pool of clients and has the right to grant / terminate access to its customers by employees of other services.
5. The program interface should be close to the CRM interface in order to ensure the comfort of using this software by the executor.
6. The technology of forming the 1st PRKO on the client will be almost similar to the current process (automation will affect only actions aimed at forming a specific PRKO template, information will be manually entered into the primary PRKO)
7. As part of creating a single platform for coordination, the services, in addition to the CPU, will also have access to the decision file for the purpose of formatting it in the program itself as part of the coordination process.
8. Each PRRO file will be assigned a status in the program that will make the current stage of work on PRRO understandable.
9. The program will not implement a mail server that provides notifications to program users about the change in the status of a separate PRKO file or changes made. This decision is due to the additional complexity of the development and configuration of such a server and insignificant attitude to the sanitary task of the software being developed.
10. Notifications will be sent to users about the origin of any changes to their customers within the program itself.
11. Within the framework of the proposed software, only the PRCO will be formed for the NCL product, i.e., the NCL will be formed. You can create an initial solution, make changes to it.
12. To make changes to the previously made decision, it will be necessary to select by check box those sections of the decision that need to be adjusted / supplemented and a new solution will be created by means of the “form” button to change the condition with the “cancellable parameters” fields already filled in, where only the “approved parameters” will remain to be filled in.
13. After the approval of the PRKO in the program and the decision is made, the CI changes the status of the decision to amend to "adopted", makes the No and the date after which the decision is embedded in the program as adopted. Additionally, the CI downloads a scan of the decision from the CA Secretary to confirm the decision.
14. The structure of the programme will provide a function of viewing the history of any PRCO, i.e. You can see when the decision was made, when the changes were made, and with the help of a “one click” you can see the essence of the changes made.
15. The obligatory function of the program will be possible to display the current version of the decision on one screen, i.e., the same. There are PRCOs on approval of the loan and 10 changes to it and to understand the current conditions you do not need to work with 11 documents, you just need to click the button “see the current conditions” and the decision to approve the loan in the version of 10 changes is displayed on the screen.
16. The program will make it possible to form in one file a decision - approval of products for several borrowers of the State Health Service. It will also be possible to make changes to several products of different customers.
17. The program will automatically determine by several IDs (product ID, NCL number, etc.) which data from new solutions will need to be attributed to the decisions already made.
18. It will be possible to leave a brief descriptive part for each PRRO file, which will give an understanding of why the change was made.
19. Navigation on the program should be convenient and intuitive to the user.
20. The program will implement a logical correspondence between: No solution, product in CRM / Exel application, client, SSZ.
21. The search for accepted PRKO will be carried out either through the No and date, or through the No of the NCL to which it refers, or through the TIN you can find all the products of the client and, accordingly, the PRKO itself.
22. The developed software should promptly respond to user actions
