![\"\"](\"http:\/\/navision-beratung.de\/wp-content\/uploads\/2017\/10\/Baubranche.png\")
<\/p>\n<\/p>\n
In our series of reference projects by bartolome r\u00f6der AG, we would like to present a project from the construction industry to you today.
\nThe company currently has around 250 employees, of which around 25 are Microsoft Dynamics NAV users. The goal was defined in advance to replace the interface-intensive AS\/400 process landscape and transfer it to a homogeneous process landscape. The following five company divisions were affected by the changeover to Microsoft Dynamics NAV:<\/p>\n
Highlights of the project<\/strong> were the system presentation of down payment processing and the construction diary.<\/p>\n What the Down payment processing<\/strong> As far as the invoice is concerned, it should be possible to create any number of down payment invoices from any number of customer orders or purchase orders, both on the outgoing and incoming side, which should then flow into a final invoice at the end. Another challenge was the Construction diary<\/strong>which includes the recording of events during the implementation of a project with the option of creating various forms\/documents. In this way, events such as fault messages or change messages can be used during the project phase, e.g. for preparing quotations. The project was completed within a tight schedule of four months from commissioning to go-live. After \"Go Live\", continuous improvements were made to the system and processes were optimized.<\/p>\n The customer can now build on a customized process landscape that has optimized and accelerated daily work processes.<\/p>\n
\nCross-document down payment processing was therefore implemented.<\/p>\n
\nThe construction diary consists of two components:
\n1. the construction diary itself for recording events such as additional services, disruptions, changes to the construction process, etc.
\n2. supplementary management, which manages the documents and forms for the respective events. The content of these documents can be, for example, the duration of an incident, type of incident, comments, notes on offers already received, approvals and much more.<\/p>\nRealization of the project<\/u><\/strong><\/h2>\n