Introduction []

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
<div 100%>
====== Introduction ======
<WRAP 1200px left>
The **Performed Works** module (hereinafter referred to as **PW**) is designed to create supporting documents for invoicing work carried out on a construction site. Each construction site has an itemized budget, where each item represents a specific type of work or material. Items contain basic information such as a textual description, quantity, unit of measurement, and unit price.

Performed works serve as the basis for interim invoicing and should document the current state of work progress on the construction site as of a specific date.

In practice, RCWs are most commonly prepared monthly. In very exceptional cases, a different time period may be used.

PWs are prepared at all levels of the contractor structure on a construction site. The highest level is between the main contractor (contractor) and the investor (client). Subcontractors also prepare PWs for the main contractor. This hierarchy may consist of an even greater number of levels.

=====What Buildary Enables and What Its Advantage Is=====
**The aim of the Performed Works module is to cover the first two levels of contractor relationships, i.e. PWs between the contractor and the client, and between subcontractors and the contractor.**

{{ :en:performedworks:diagram_vztahu2.png |}} <WRAP clear /> </WRAP>

<WRAP 1200px left>

* Buildary therefore does not only address the highest-level contractor relationship, where only one Record of Completed Work is created each month. When used correctly, it also brings order and systematic processes to relationships with subcontractors, where dozens of records may be created each month, often in several versions. Buildary allows all participants to collaborate online using shared data, making communication easier and more transparent.

* Buildary supports the entire process of preparing and modifying PWs through to their approval, across all contractor relationships.

* The application provides clear entry, approval, and modification of PWs at the individual item level. The history of corrections is visible, and approval can be verified for each individual item.

* The output of the process is a PDF file protected against changes by an electronic signature. The file contains all information about the completed work and includes metadata in its attributes that is useful when importing and checking the data in an ERP system.

====Buildary Enables:====

* Any number of clients, contractors, and subcontractors on a single construction site.

* User permissions can be configured so that, although users work with shared data for a single construction site, each user sees only their own data and can perform only the operations they are authorized to perform.

* The time period covered by the records can be set freely. It is configured by the construction site administrator and is shared by all participants. When integrating with other applications, however, it is advisable to respect any limitations resulting from the logic of those applications (e.g. in RSV, the period must not exceed one month).

* Each participant creates their own **Measurement Report (MR)** for the given period. The report then progresses through individual statuses (**Proposal, Approved, Changed, Rejected, Negotiated**). The functions available to different users also depend on the current status of the MR.

* Users are notified by e-mail of changes to the status of the Measurement Report.

* Gradual approval of records of completed work at the individual item level. Each item quantity has its own status (**Proposal, Approved, Changed, Rejected, Negotiated**), so some items may already be approved while the correct quantity for others is still being negotiated.

* Users have a continuous overview of the volume of completed work that has already been approved and the volume that is still undergoing the approval process.

* The history of a given period can be viewed at any time, allowing users to see for each item what quantity was originally proposed for billing, how the proposal was modified, and what quantity was ultimately approved.

<WRAP clear />
</WRAP>

<WRAP 1200px left>
=====Who the Records of Completed Work Module Is Intended For=====

* For investors who want to use a modern method of communication with contractors.

* For contractors who want to gain control over their subcontractors' performed work and, instead of dealing with a multitude of Excel files, have one reliable database accessible to all participants.

* For anyone who wants to speed up, make more transparent, and better document the process of reporting and approving completed work on their construction sites.

<WRAP clear />
</WRAP>
</div>