MINISTRY OF YOUTH LABOR AND EMPLOYMENT
KYRGYZ REPUBLIC
INSTITUTE OF SOCIAL DEVELOPMENT AND ENTREPRENEURSHIP
Department of Applied Informatics
GRADUATE WORK
On the topic: Automation of registration of applications in
LLC "SV Logistics" using the 1C program: IT department management 8
Completed by: student gr. PIM
Scientific adviser:
Senior Lecturer
Allowed for protection
"____"___________ 2012
head department
Candidate of Physical and Mathematical Sciences
PI Bolzhiev B.A.
_____________________________
Introduction………………………………………………………… …………………...3
1. Analytical part………………………………………………………………...8
1.1 Technical and economic characteristics of the subject area and enterprise. Analysis of the activities of LLC “SV Logistics”………………………………….…8
1.1.1 Characteristics of the enterprise and its activities……………………….….8
1.1.2 Organizational structure of enterprise management………….…… .…11
1.1.3 Software and technical architecture of the enterprise IS………….……13
1.2 Characteristics of a set of tasks, objectives and justification for the need for automation………………………………………………………………21
1.2.1 Selection of a set of automation tasks and characteristics of existing business processes………………………………………………………………...21
1.2.2 Determining the place of the projected task in the complex of tasks and its description……………………………………………………………………………………………. 24
1.2.3 Justification of the need to use computer technology to solve the problem………… ………………………………………………………..…25
1.2.4 Analysis of the information security and information protection system………………………………………………………………………28
1.3 Analysis of existing developments and choice of automation strategy LLC “SV Logistics”…………………………………………………………………….33
1.3.1 Analysis of existing developments to automate the task…………33
1.3.2 Selection and justification of a task automation strategy…………………...44
1.3.3 Selection and justification of the method of acquiring IP to automate a task
2. Configuration IT department management 8 edition 2.0……………………….51
2.1 General description...................... ................................. ..... .............................. ............... ...51
2.2 System requirements................................................................... ........................... ........................ 52
2.3 Getting started......................................................... ............. .............................. ....... ....53
2.4 Configuration accounting circuits............................................................ .............. ...............54
2.5 Warehouse circuit........................ .................................... ....... .......................... ............55
2.6 Document “Receipt” .............................................. ............... .....................58
2.7 Document “Movement” .............................................. ............... .....................58
2.8 Document “Write-off” ................................... ............... ............... ...........................59
2.9 Document “Inventory” .................................... ............... ............... ................60
2.10 Other documents................................................................... ............. .......................... .60
2.11 Repairs................................................................... ............ ......................... ........ ..........60
2.11.1 Document “Start of repairs” ............................................ ............ .................... ............60
2.11.2 Document “Completion of repairs” .................................... ............ ....... ......61
2.12 Applications to suppliers.................................................... ............. ......................... 62
2.13 User requests.................................................... ............. ...........................62
2.14 Reports.................................................... ............ ......................... ........ .............64
2.15 Uploading images to the configuration using Google and Yandex Images .................................... ......... ..................... .................................. ........................... 65
2.16 Other options................................................................... ............. ........................65
Conclusion……………………………………………………………………66
List of references……………………………..…………… 68
Introduction
In the twenty-first century, business process automation is not a luxury.
This is an event, the necessity and effectiveness of which was convinced by the heads of most successful companies not only in Europe and America, but also in Russia and the CIS countries.
Most often, the consequences of automating a company’s business processes are:
- significant increase in labor productivity and reduction in labor costs;
- increasing the speed of completing tasks related to various types of accounting;
- reducing the number of errors in documentation, reports, etc.
- increasing accounting efficiency, leading to increased profitability of the enterprise;
- ease of business processes and document flow.
Each of the points listed above is a strong argument in favor of paying attention to the possibility of automating the company’s business processes.
Naturally, taken together, these points become a reliable basis for a successful and prosperous business, no matter what industry the enterprise is involved in.
The latest global financial and economic crisis clearly showed that those enterprises that have implemented and developed an automation system are highly competitive and sustainable. For example, the precise development and competent implementation of an automatic accounting system in the Investment Company “MG Securities” (Moscow) at the end of 2008 - beginning of 2009. solved a number of problems that previously reduced the speed and efficiency of document flow, accounting processes and transaction management.
Based on the foregoing, we can safely conclude that the topic of this thesis is especially relevant in modern business conditions, especially in anticipation of the end of the global financial crisis. Indeed, in the pursuit of competitiveness, it is important to speed up the decision-making process, increase mobility in contacts with clients, and at the same time competently and timely monitor the company’s internal business processes in order to achieve greater operational efficiency. Of course, automation is a key element here.
But do not forget that each company is individual. Therefore, maximum efficiency of business process automation can only be achieved with an individual approach.
For enterprises and organizations that are actively expanding their activities, not only due to the emergence of new clients and partners, but also by increasing turnover and providing a wider range of services and cooperation options to existing clients and partners, registration automation is especially important to increase the efficiency of their activities and/or monitoring applications from such counterparties. This procedure, ultimately, not only significantly facilitates the applicant’s work, but also allows the application executor to save time in receiving/processing requests and minimize the impact of “human factor” errors. After all, no matter how highly qualified a specialist is, we must pay tribute to technological progress: machine memory and data processing speed exceed similar human indicators.
Thus, the purpose of this thesis project is to analyze the automation of registration and monitoring of applications from regular customers and partners of the enterprise. In this case, a “regular customer” or “permanent partner” of a company should be understood as any person with whom at least one contract has been executed.
The set goal predetermined the formulation and solution of a number of interrelated tasks:
In the process of solving the main task, a functional-modular (structural) approach was used. In solving secondary problems, a systematic approach, a factor analysis method, a method of expert assessments, methods for assessing financial efficiency, statistical and forecasting methods were used.
This thesis consists of two parts.
The first part reflects the analytical part of the project, which presents the technical and economic characteristics of SV Logistics LLC and the company’s existing process for registering and monitoring applications from clients and partners; characterization of a set of problems requiring solution and justification of the need to automate the described process in LLC SV Logistics; analysis of existing developments, justification of design solutions and selection of a strategy for automating the registration and monitoring of applications from regular customers and partners of SV Logistics LLC.
The second part of the work contains a direct description of the 1C: IT department management program 8, and its practical application in this organization. The advantages of this configuration are described and an analysis of its effectiveness is carried out. Methods and principles for implementing the main task of the diploma project - registration and monitoring of applications from regular customers and partners of SV Logistics LLC - are considered. The advantages and additional capabilities of the 1C information system: IT department management 8 are considered.
1. Analytical part
Technical and economic nature of the history of the subject area and enterprise. Analysis of the activities of LLC "SV Logistics"
Characteristics of the enterprise and its activities
Limited Liability Company "SV Logistics" has been successfully operating in the information technology market since 2002, operating on the basis of the Charter approved on April 16, 2002.
The mission of SV Logistics is to provide comprehensive professional computer assistance to both companies and individuals.
The main activity of the company "SV Logistics" LLC is the provision of IT Outsourcing services.
IT Outsourcing (Information Technology Outsourcing) is the transfer to a specialized company of all tasks of managing the information technology of an enterprise or its individual IT functions.
As part of IT Outsourcing, SV Logistics LLC carries out:
- services for creating the company’s IT infrastructure (organization, planning, supply, installation, full setup of local computer networks of a new office or modernization of an old system - “turnkey office”);
- services for comprehensive management of the company’s IT infrastructure;
- services for maintenance and subscription services for computers, servers, office equipment and local networks;
- administration and maintenance of computer systems, implementation and maintenance of programs;
- sale and delivery of software and computer components, assembly of computers to order;
- providing professional user support (Help Desk);
- solving information security problems.
The second most significant area of the company's activities
SV Logistics LLC is providing a wide range of services in the field of WEB technologies (flexible and multifunctional Hosting;
Web design; development, technical support and promotion (promotion) of websites).
The work of SV Logistics is based on the constant search for new rational solutions and technologies, expansion and steady growth in the quality of the services provided.
The main advantage of SV Logistics LLC is the many years of experience and high qualifications of its employees, excellent knowledge of the full range of services and products offered, and a responsible approach to business.
The main and undoubted value of SV Logistics LLC is the established trust of clients and partners, expressed in long-term, long-term and effective cooperation.
Table 1.1 Applications from regular customers and partners of SV Logistics LLC for 2009
Indicator name |
Number of transactions-applications 2009, pcs. |
% of total receipts 2009 |
Actual completed turnover of applications 2009, som. |
Potential turnover of applications 2009, som. |
Average contract price in relation to the number of applications 2009, som. |
Counterparty - Client |
|||||
in total |
|||||
executed orders-transactions |
|||||
unexecuted orders-transactions |
|||||
unread (overdue) |
|||||
deferred (overdue) |
|||||
conflicting applications |
|||||
in total |
|||||
executed orders-transactions |
|||||
unexecuted orders-transactions |
|||||
unread (overdue) |
|||||
deferred (overdue) |
|||||
conflicting applications |
|||||
Counterparty - Partner |
|||||
in total |
|||||
executed orders-transactions |
|||||
unexecuted orders-transactions |
|||||
unread (overdue) |
|||||
deferred (overdue) |
|||||
conflicting applications |
|||||
TOTAL APPLICATIONS accepted and executed |
|||||
TOTAL APPLICATIONS accepted: executed and unfulfilled |
Short description
The purpose of this thesis project is to analyze the automation of registration and monitoring of applications from regular customers and partners of the enterprise. In this case, a “regular customer” or “permanent partner” of a company should be understood as any person with whom at least one contract has been executed.
The set goal predetermined the formulation and solution of a number of interrelated tasks:
Studying the existing scheme of work with regular clients and partners of SV Logistics LLC and identifying factors contributing to a decrease/increase in work efficiency;
Description of automation of registration and monitoring of applications from regular customers and partners of SV Logistics LLC in the 1C: IT department management program 8;
Justification of the effectiveness and practical significance of using the 1C information system: IT department management 8.
Table of contents
Introduction………………………………………………………………………………………...3
1. Analytical part……………………………………………………………...8
1.1 Technical and economic characteristics of the subject area and enterprise. Analysis of the activities of LLC “SV Logistics”………………………………….…8
1.1.1 Characteristics of the enterprise and its activities……………………….….8
1.1.2 Organizational structure of enterprise management………….…….…11
1.1.3 Software and technical architecture of the enterprise IS………….……13
1.2 Characteristics of a set of tasks, tasks and justification for the need for automation……………………………21
1.2.1 Selecting a set of automation tasks and characterizing existing business processes………………………21
1.2.2 Determining the place of the projected task in the set of tasks and its description……………………………………………………24
1.2.3 Justification for the need to use computer technology to solve the problem………………………25
1.2.4 Analysis of the information security and information protection system……………………………28
1.3 Analysis of existing developments and choice of automation strategy LLC “SV Logistics”………………………33
1.3.1 Analysis of existing developments to automate the task…………33
1.3.2 Selection and justification of a task automation strategy…………………...44
1.3.3 Selection and justification of the method of acquiring IP to automate a task
2. Configuration IT department management 8 edition 2.0……………………….51
2.1 General description................................................... ........................................................ ...51
2.2 System requirements.................................................... ...........................................52
2.3 Getting started................................................... ........................................................ ....53
2.4 Configuration accounting circuits.................................................... ........................54
2.5 Warehouse circuit.................................................... ...................................................55
2.6 Document “Receipt” .................................................... ....................................58
2.7 Document “Movement” .................................................... ...................................58
2.8 Document “Write-off” .................................................... ........................................59
2.9 Document “Inventory” .................................................... ...............................60
2.10 Other documents.................................................... ...............................................60
2.11 Repairs................................................... ........................................................ ..........60
2.11.1 Document “Start of repairs” .................................................... ...............................60
2.11.2 Document “Completion of repairs” .................................................... ........................61
2.12 Applications to suppliers.................................................... ........................................62
2.13 User requests.................................................... ........................................62
2.14 Reports................................................... ........................................................ .............64
2.15 Uploading images to the configuration using Google and Yandex Images .................................................... .........65
2.16 Other options................................................... ........................................65
Conclusion…………………………………………………………………………………66
List of references……………………………..……………68
The program for accounting applications and orders is designed to automate the process of accounting for orders or receiving applications in a small commercial organization. The program fully automates the operational and management accounting of the company, significantly facilitating the work of employees and managers. Since the program is built on the platform, it is simple and intuitive for the user, like other projects created on this platform. Therefore, even a person who is not very familiar with computers will be able to work with it.
The program has a very convenient product catalog. Each product has a set of characteristics, for example: name, barcode, manufacturer, country of production, etc. The set of product characteristics can be any, i.e. You can easily and quickly add the necessary characteristics to a product or remove unnecessary ones. For each of the characteristics, you can set a filter to quickly search for the desired product in the catalog. Also, for a more convenient and quick search, the order accounting program provides a folder tree. It allows you to create your own product classification and place products in their corresponding folders. You can add an unlimited number of photos to each product. A list of products can be imported from an Excel spreadsheet and exported from the program to an Excel spreadsheet. The program supports working with a barcode scanner. The scanner is connected to the computer via a USB port and reads the barcode, the read data is inserted into the filter field and the desired product is found automatically.
Since, in addition to selling goods, organizations can also provide related services, the program for recording applications and orders also provides a list of services. Each service has the required set of characteristics, which can be changed if necessary. It is possible to search by any of the characteristics. The list of services can be downloaded from an Excel spreadsheet.
To automate payments to suppliers, the program has a supplier database. Each of them has the necessary set of characteristics: name, phone number, details, etc. The supplier's balance is automatically calculated. It is calculated as the difference between the total amount of goods supplied and the total amount of payments to this supplier. The list can be filtered by any field.
The order accounting program also contains a list of managers of your organization. Statistics are kept for each of them and the necessary information is stored. Each manager has his own percentage of sales, according to which his salary is automatically calculated and the manager’s balance is formed. There are also filters for the desired characteristics.
The buyer database is also provided in the application accounting program. Name, details, data for forming contracts - all this characterizes each buyer. The list of characteristics can be changed according to your wishes. The total amount of purchases is automatically accumulated. The list of buyers can be imported into the program from an Excel spreadsheet and exported from the program to Excel, if necessary. This list can be filtered by any of the buyer characteristics.
The arrival of goods is carried out through the operation of the same name. We select a supplier and add products from the product catalog, indicating their quantity and changing the purchase price if necessary. The list of goods can be imported into the Receipt operation from an Excel table. This is a very convenient feature. If your supplier can send you an Excel file with a list of delivered goods, then all you have to do is load this data into the program. To do this, you just need to click the Import from Excel button and select a file with a list of products, and the data will be transferred to the program automatically. The quantity of goods delivered will go to the warehouse, and the total amount of delivery will be recorded on the supplier’s balance sheet. The list of receipt transactions is equipped with filters by supplier and by date of operation.
Accounting for orders in the program is very simple. You need to select the order status and buyer from the list of buyers. The manager's last name will be entered automatically based on the username under which you are logged in.
- How a knowledge base reduces costs for scheduled repairs
- What trick motivates employees to quickly switch to working in a new information system
- Why include nurses in your help desk?
We use sophisticated imported equipment. The equipment includes 3D tomographs, laser therapy devices, electrocardiographs, dental and foundry units, and compressors. Every month the technical service receives over 100 requests for repair and maintenance of equipment. Each application must be included in the work schedule, taking into account urgency, complexity and execution time. At the same time, repairs have to be planned taking into account the workload of doctors and short intervals for carrying out work.
Three years ago we realized that it was necessary maintenance automation and equipment repair. The “manual” mode of organizing the repair of technical equipment is accompanied by four problems.
4 problems of “manual” organization of equipment repair
- Conflicts between technical service employees and medical staff. Engineers were slow to process requests, sometimes losing them altogether. They arrived late to calls, forcing doctors to interrupt their appointments with patients. The doctors complained and manipulated the management: “we didn’t do it because the equipment didn’t work for a month, no one repaired it.”
- Opacity of technical service loading. Repeated irrelevant requests paralyzed the technical service. The work of engineers has moved from the “request-repair” mode to the “I forgot about it because I was doing other complex work.”
- Opacity of repair accounting. We bought an X-ray machine. No one kept documentation on its repair. Information about equipment and methods for troubleshooting was stored in engineers' notebooks. After a while, we stopped understanding where the equipment was, what condition it was in, and why bills for its repairs came with such large sums.
- Engineers deliberately delaying inconvenient work. There was no equipment repair history database. Engineers did not carry out scheduled preventive maintenance and wrote off working spare parts.
How to choose a product for maintenance automation
We analyzed what solutions the market offers for automating medical equipment accounting and automating repair requests. We found out that Western products are expensive, difficult to implement and cumbersome, but Russian ones are not. Then we paid attention to the product “1C:ITIL Enterprise Information Technology Management”.
The 1C-Rarus integrator demonstrated the capabilities of the program. However, he warned: although the program is suitable for a medical institution, no one has used it in practice.
We were offered to buy a boxed version, they promised to provide the necessary instructions, but we would have to adapt the product ourselves. After weighing the pros and cons, we decided to take a chance. The program is compatible with other 1C products, which makes it easy to maintain databases, and its price is lower than its Western counterparts.
7 stages of technical service automation
The project team included an IT director, an executive director, an engineer, a chief physician, a head nurse, and. I acted as a curator. The project was implemented in seven stages.
Stage 1. Business process analysis. We described the path of an application for the repair of medical equipment: who creates it, to whom it transfers it, what are the requirements for registration, in what time frame engineers must complete it. The output was an “as is” process.
Stage 2. Creation of new business processes. Based on the “as is” process and the requirements of the “1C:ITIL Enterprise Information Technology Management” product, we developed the “as it should” process.
Two technical support lines. The first line includes requests that are not related to a breakdown. For example, an employee does not know how to turn on or reboot equipment. This is not a breakdown, but a violation of operating rules. Such requests are carried out by the head nurse. The second line is requests for repairs. They are performed by an engineer. Two lines of technical support made it possible not to overload engineers.
New types of reports and notifications. Some reports were not included in the program. For example, accounting for spare parts, accounting for the quality of breakdowns, accounting for repairs. They were completed on their own. We also independently added the function of sending notifications about incidents by email, etc.
Unified database of assets and knowledge. Information about equipment, components, spare parts, tools and methods for troubleshooting is contained in a single asset database. The database user receives complete information to quickly diagnose equipment (location, life cycle, technical documentation). The database accumulates examples of effective incident resolution.
Stage 3. Development of regulations for the technical service. We have created regulations for:
- breakdown management process;
- medical equipment management process;
- work on registration and processing of applications;
- scheduled repair work.
Stage 4. Installation, configuration and testing of the information system. First we installed the server. Then – a client application on the workstations of the involved employees. Set up additional reports. Filled out directories: models and manufacturers of equipment, regulatory tasks, lists of users, types of services. We checked the routes of applications.
Stage 5. Employee training. Conducted a general briefing. Then they played a business game in which they explained to the staff how to fill out and enter applications into the program. We separately worked on creating requests for unscheduled incidents. They explained that we no longer accept applications verbally or in writing.
Stage 6. Encouraging employees to work in the program. A trick helped encourage the team to quickly switch to filling out electronic applications instead of calling by phone. Requests that were not completed in the information system were not fulfilled. When an employee complained that the engineer was not responding to a request, we said that we did not see it in the program. In other words, if the doctor did not receive timely repair of equipment, this is his problem.
Stage 7. Technical and methodological support. After installing and configuring the system, the application routes were checked daily for a month (once every three days).
- Automation of document flow in an enterprise: a simple step-by-step plan
How are requests and equipment repairs accepted now?
If the equipment fails, the user seeks help. Indicates the login in the system and phone number, names the problem, describes the incident.
First, the request is received by the first line of technical support. If the first-line specialist finds a solution, he sends instructions to the employee by email.
If the problem is serious and the first line cannot help, the request is sent to engineers for a single monitor of the flow of applications.
The program assigns the corresponding status of service work to each request, and determines in color the priority of the task, the cost and time frame for eliminating the incident. Thus, scheduled maintenance work is marked in green. Red color means critical failure. An example of a critical failure: a software failure that leads to incorrect diagnosis of a patient. The engineer sees the new request on the monitor, its priority and importance, and receives an email notification. Looks for a solution to the problem in the knowledge base. Having resolved the problem, the incident is closed. He then sends a letter to the employee with an explanation and a report on the work performed.
I will add that the engineer sees the history of the application in the program. The employee receives a notification on his work computer every time the application changes status. For example, the application has been accepted, the application is in progress, the application has been completed, etc.
Engineers record equipment failures separately for each type of equipment. If it fails again, the program assigns the problem status to “system”. This helps to carry out scheduled preventive maintenance on time, identify and eliminate system errors, and prevent equipment failure.
In addition, the program warns engineers about approaching dates for preventive maintenance of equipment. A reminder is sent to the engineer’s monitor and the medical worker’s computer in charge of the equipment.
- 4 examples of how small businesses reduce costs using IT
Four Key Results
The project lasted six months. After its completion, we immediately felt the effect. The team notes that “it has become better.”
The number of unfulfilled or late applications has been reduced to zero. Now engineers are paid not for repairs, but for the uninterrupted operation of equipment. The longer the equipment does not break down, the higher the salary. To calculate engineers' bonuses, we use four KPIs:
- quality of applications;
- average rating of error resolution quality;
- the share of closed orders from those registered in the system;
- budget spent on repairs and unplanned incidents.
The cost of maintaining medical equipment and other technical systems has been reduced by up to 20%. The program shows who removed what components and parts of the equipment, what was sent for repair, etc. It used to happen that we paid for the repair of equipment when it was still under warranty. Now you can see which equipment is under warranty and which is not. Thanks to the database, there is information about the most used spare parts and components. Now we purchase only what is needed at a particular moment, or what we use most often.
The load on technical service has decreased by 15%. The regulations for scheduled preventive maintenance included the responsibility of doctors and nurses for the uninterrupted operation of equipment. Now medical personnel themselves perform part of the equipment maintenance work. It has become easier for engineers to plan their working time.
The number of unplanned incidents has decreased to 40%. The program stores the history of breakdowns and movements, repairs and maintenance, and accompanying documentation. This information allows you to plan repairs and replacements of equipment in advance.
Automation of equipment maintenance and repair:
- saved the team from conflicts;
- reduced the load on the technical service, thereby allowing employees to improve the quality of work;
- reduced the cost of repairing equipment and machinery;
- increased revenue, since now we do not cancel patient appointments.
Copying material without permission is permitted if there is a dofollow link to this page
Job number:
Year added:
Workload:
INTRODUCTION 6
1. ANALYTICAL PART 8
1.1 Technical and economic characteristics of the subject area and enterprise" Analysis of activity "AS IS" 8
1.1.1 Characteristics of the enterprise and its activities 8
1.1.2 Organizational structure of enterprise management 10
1.2 Characteristics of a set of tasks, tasks and justification for the need for automation 14
1.2.1 Selecting a set of automation tasks and characterizing existing business processes 14
1.2.2 Determining the place of the designed task in the set of tasks and its description 16
1.2.3 Justification for the need to use computer technology to solve problem 18
1.3 Analysis of existing developments and choice of automation strategy “AS IT SHOULD BE” 21
1.3.1 Analysis of existing developments for automating task 21
1.3.2 Selection and justification of the automation strategy for task 27
1.3.3 Selection and justification of the method of acquiring IP to automate task 30
1.4 Justification of design decisions 32
1.4.1 Justification of design solutions for technical support 32
1.4.2 Justification of design decisions for information support 33
1.4.3 Justification of software design decisions 35
2. DESIGN PART 37
2.1 Development of an automation project 37
2.1.1 Stages of the automation project life cycle 37
2.1.2 Expected risks at life cycle stages and their description 41
2.2 Information support for task 43
2.2.1 Information model and its description 43
2.2.2 Characteristics of regulatory, reference, input and operational information 44
2.2.2 Characteristics of the resulting information 45
2.3 Software for task 46
2.3.1 General provisions (function tree and dialogue script) 46
2.3.2 Database characteristics 48
2.3.3 Block diagram of the package (call tree of program modules) 51
2.3.5 Description of software modules 51
2.3.6 Test example of project implementation and its description 55
3 Justification of the economic efficiency of the project 61
3.1 Selection and justification of the methodology for calculating economic efficiency 61
3.2 Calculation of project economic efficiency indicators 65
CONCLUSION 71
REFERENCES 72
Appendix 1. Document forms 74
Appendix 2. Gantt chart 80
Appendix 3. Listings of program modules 81
Excerpt from the work:
Some abstracts from the work on the topic Automation of registration and accounting of client applications at Almaz-Antey OJSC
The competitive position of an enterprise in the market for serial production of integrated operational communications largely depends on the level of automation of registration and management of various applications.
The technical implementation of such automation systems is characterized by the following main aspects:
Using modern programming technologies
Using a centralized data warehouse with remote access capabilities
Using technologies from leading IT companies: MS SQL Server, Borland Delphi
The automated information system for registration and control of client orders is designed to ensure prompt acceptance and control of all stages of client requests related to the production of integrated operational communications, as well as obtaining analytical information on these orders. This system is intended for use in enterprises engaged in the production of integrated operational communications. The need to develop this AIS was due to the non-compliance of the existing information system with the requirements of information reliability, security, reliability and functionality.
The goals of creating an Automated Information System for registration and control of customer orders are:
Ensuring the efficiency and convenience of registration of a client’s application by the operator
Promptly obtaining the necessary data about the current client
In numbers, the resulting economic effect has the following expression:
1. The payback period for the created project is 19 months.
2. The design option for solving the problem is 78% more profitable in terms of labor intensity and cost than the basic one.
3. The economic effect amounted to 59,321.70 rubles.
The developed program can be used to automate the work of a manager in other organizations engaged in the same or similar type of activity.
Taking into account the obtained effect, it was decided to continue the development of the project. It is planned to develop the following areas: integration of the system with 1C Accounting, which will minimize the work of personnel in transferring data from one system to another; implementation of operational data analysis based on OLAP systems, which will provide effective and prompt support in making management decisions.
The presented educational material (in structure - Diploma technical) was developed by our expert as an example - 11/26/2010 according to the specified requirements. To download and view a short version of the technical thesis, you need to follow the link “download demo...”, fill out the form and wait for the demo version, which we will send to your E-MAIL.
If you have a deadline, fill out the form, then call us on the hotline, or send an SMS to +7-917-721-06-55 with a request to urgently consider your application.
If you are interested in assistance in writing your specific work, according to individual requirements, it is possible to order development assistance on the presented topic - Automation of registration and accounting of client applications at Almaz-Antey OJSC ... or similar. Our services will already be subject to free modifications and support until defense at the university. And it goes without saying that your work will be checked for plagiarism and guaranteed not to be published early. To order or estimate the cost of individual work, go to
The work was prepared and defended in 2017 at the Moscow Financial and Industrial University Synergy, Faculty of Information Systems and Technologies, for the specialty “Information Systems and Technologies”, for the direction “Information Systems”, for the specialty “Applied Informatics (in Economics)”.
The project describes the process of automating the accounting of warranty equipment that comes in for repair and maintenance. Automation of this process will help increase the efficiency of decision-making and minimize management complexity. It also helps to collect the required statistics on the subject of requests, which is also important for creating a sound strategy for the company.
The purpose of this work is to implement an information system that helps automate the work of the PwC LLC SC to reduce the load on its employees, minimize errors, and increase the speed of work.
The main tasks of the work are:
- Studying the work of the company being described;
- Finding controversial issues;
- Expressing the relevance of automation;
- Proof of design decisions by type of security;
- Creation of a database and programs for interacting with it;
- Calculation of the level of project effectiveness.
The main objective of the project is to study the work of the company, identify existing shortcomings in the approach used to managing the company, and create a web-based system for automating processes that are associated with accounting for equipment coming in for repairs.
As part of the study of the control technology used, the goal and purpose of the developed software version for implementing this task were prepared, a comparison was made with similar systems for implementing this task, the results of the results were formalized, design technologies were determined, and a number of decisions were made on the types of software used.
An information model was created for the system being created, and a local coding and classification system was introduced. Decisions have also been made on the method of storing and organizing data. An infological database model was built.
Within the software, a function tree and a dialogue script for the operation of the system have been created, and a block diagram of the package has been prepared: a procedure implementation tree and a diagram of the interaction of program modules and files.
Within the framework of those support, a scheme for organizing the technology for searching, obtaining, processing and issuing data for the project being developed has been prepared.
Based on the analysis of the subject area and data obtained using the software solution method, the economic efficiency of the project was determined. Its indicator allows us to talk about the benefits of the project. Minimization of both labor and cost costs was noted.
The payback period for the project was 8 months.
Further development of the created system is necessary towards increasing its functionality, as well as further integration into the existing enterprise system.
In particular, further development and expansion of the developed application is necessary in order to record repairs and warranty service, as well as the preparation of reports on the work of the enterprise service department.
The project comes with a program in PHP and a mysql DBMS.
