In this master work has been passed in review theory material of database and database management system. In addition, has been analysed the main parts of information system of business companies. Microsoft Office Access 2003 is the database management program that gives an improved user experience and an expanded ability to import, export, and work with XML data files. Working in Access 2003 is easier because common errors are identified and flagged for you with options to correct them. Additionally, a new feature to Access 2003 also helps database developers view information on dependencies between database objects. Therefore, Microsoft Office Access 2003 was used to created database management system of company, which sells products of food. In addition, has been explored how influence relations between tables, number of records, number of fields and length of text fields on the rate. Business management system is the main part of comapany information system. Microsoft Office Access 2003 could use small companies, which have no more than 20 computers. This program has some advantages, because it isn‘t cost a lot and everyone could install it without any problem. Examinations show that relations between tables and length of text fields don‘t influnce on the rate. But the rate depends on the number of records and the number of fields.

This work investigates the problem of company not able to handle it’s data analysis using Navision Attain tools alone. A more powerful system is needed, and Microsoft SQL Server OLAP tools are selected as such. The work carried out covers data extraction, transformation and loading (ETL) for analyzing Navision Attain data using OLAP data analysis tools. Different integration architectures, as well as needed transformations and most often encountered problems are covered, together with possible solutions to them.. After completing business process analysis, and identifying user roles and required data, four different data cube were created on data from Navision Attain. Namely cubes for sales analysis, purchase analysis, item inventory tracking and customer debt analysis. In addition, an example schedules for cube updating are created, and wider usage guidelines are provided. The complete system is then optimised to provide efficient performance and low main system load. The optimisation results are compiled into generic suggestions for further analysis system development.

Atlikus kritinių sėkmės faktorių, taip pat charakteristikų, naudojamų pasirenkant verslo valdymo sistemą, analizę siūlomas verslo valdymo sistemų pasirinkimo procesas. Aptariami reikalavimų nustatymo žingsniai, taip pat išskiriami pagrindiniai kriterijai sistemoms specifikuoti ir atrinkti. / Enterprise resource planning (ERP) software selection is problematic nowadays. It was performed analysis on critical success factors and characteristics usage during enterprise resource planning software selection. It was proposed enterprise resource planning software selection process. Discussed steps to identify software requirements and extract main criteria to specify and select system.

Tai yra verslas verslui užsakymų valdymo architektūrinių sprendimų tyrimas. Sukurtoje platformoje kompanijos gali komunikuoti tarpusavyje, sudaryti užsakymus, keistis bylomis bei dokumentais, ieškoti kitų paslaugų tiekėjų ir gauti informaciją apie juos. Pasitikėjimas tarp įmonių yra labai svarbus, o ši platforma padeda tai pasiekti. Bendravimas su klientais ir tiekėjais paprastai užima daug laiko ir reikalauja naudoti daug skirtingų įrankių, pavyzdžiui, el. paštą, telefoninius skambučius, Skype, ryšių su klientais valdymo sistemas ir t. t. Šio sprendimo idėja yra į vieną vietą sutraukti visus svarbiausius įrankius ir palengvinti kasdienį vadybininkų darbą. Aukštos kokybės paslaugų užtikrinimui reikalinga integracija su kitomis išorinėmis verslo valdymo sistemomis, o kad tai būtų pasiekta, reikalingos saityno tarnybos. Siekiant išsiaiškinti, kokios tarnybos ir jų konfigūracijos geriausiai tinka šiam tikslui pasiekti, buvo atliktas tyrimas ir eksperimentas, kurie aprašyti šiame dokumente. Šį dokumentą sudaro trys pagrindinės dalys. Pirmojoje dalyje aprašoma galimų sprendimų analizė ir saityno tarnybų savybių tyrimas. Antrojoje dalyje aprašoma sukurta platforma, jos aktualumas ir funkcionalumas. Taip pat pateikiamos vartotojo sąsajos, panaudojimo atvejų schemos ir klasių diagrama. Šioje dalyje atsakoma į klausimus, kodėl vartotojai turėtų pasirinkti būtent šią platformą ir kokias problemas ji sukurta spręsti. Paskutiniojoje dalyje aprašomas eksperimentas, kuriuo buvo nustatomas... [toliau žr. visą tekstą] / This is a research on architectural solutions of business to business orders management systems. It’s a B2B platform where different companies can communicate, exchange orders and documents and search for other providers. Trust building is important for all companies and this platform can help to make it happen. Communication between companies requires a lot of time and use of different tools, e.g. email, phone calls, Skype, file storage places, CRMs and so on. Idea is to implement all necessary equipment in one place and let managers to do their daily work easier. To provide high quality services it’s important to ensure good communication between platform and outside business management systems. There was made a research for which are the best fitting solutions to be integrated as web services. This document is consisted of three major parts. First part describes analysis of available solutions and research of web services technology. Second part describes developed project and its features. There is user interface, use case, data structures and competitors review. This is whole about project and why it would be good choice for our targeted audience. The last part describes the research that was done during this project. It was essential to determine which protocol and data models are most efficient. For this project there were created two additional applications - one as web service and other one as a client. Client application sent requests to service and calculated its... [to full text]

Verslo valdymo sistemos (VVS) Lietuvoje jau gana ilgą laiką yra intepretuojamos kaip būtina inovacija įmonėms, norinčioms konkuruoti šiuolaikinėje ekonominėje terpėje. Todėl šiuo metu vis daugiau įmonių pasiryžta įdiegti VVS, o tai didelių investicijų reikalaujantis projektas, kuris nevisada sulaukia norimų rezultatų. Tokių situacijų atsiradimas didina poreikį atlikti nesėkmingų VVS diegimo priežasčių išsamų tyrimą. Šiame darbe išanalizuota verslo valdymo sistemų raida, diegimo modeliai, svarbiausi veiksniai, lemiantys diegimo projekto sėkmę. Atlikta Lietuvos ekspertų ir vartotojų apklausa padėjo įvertinti esamą VVS diegimo projektų situaciją Lietuvoje ir išanalizuoti veiksnių svarbumą atsižvelgiant į respondetų pateiktus atsakymus. Tai įgalino pasiūlyti Lietuvos smulkaus ir vidutinio verslo (SVV) įmonėms naująjį VVS diegimo modelį, kuriame sukaupta geriausia VVS diegimo praktika panaudojus užsienio literatūrą ir Lietuvos ekspertų patirtį. Darbą sudaro 6 dalys: įvadas, verslo valdymo sistemos įmonės valdyme, verslo valdymo sistemų diegimo procesas ir lemiantys veiksniai, verslo valdymo sistemų diegimo modelis, išvados, literatūros sąrašas. Darbo apimtis – 73 p. teksto be priedų, 9 iliustr., 13 lent., 71 bibliografiniai šaltiniai. / Enterprise resource planning (ERP) systems in Lithuania have been already used for a long time and they are interpreted as a necessary innovation for enterprises which want to compete in the contemporary economic environment. Thus, currently more enterprises resolve to implement ERP systems. This project requires large investments and it does not always produce the desired result. Situations like this increase the necessity to do a proper research of reasons for unsuccessful implementation of ERP systems. In this final work enterprise resource planning system‘s development, models of implementation, most important factors which influence project’s success are analyzed. Performed Lithuanian specialists’ and consumers’ survey helped to evaluate an existing situation of ERP systems implementation in Lithuania and to analyze the importance of factors according to respondents’ answers. That enabled to offer a new ERP system’s implementation model which contains the best ERP system’s implementation practice in foreign scientific literature as well as the experience of Lithuanian experts for Lithuanian small and medium enterprises. The Master Thesis consists of 6 parts: introduction, enterprise resource planning systems in enterprise‘s management, the process of enterprise resource planning system implementation and influencing factors, enterprise resource planning systems implementation model, conclusions, references. The length of the Thesis is: 73 pages of text without appendices... [to full text]