Anhang B – Unterschiede zur vorherigen Dokumentation
Bei der Erstellung der Kapitel 5.4 und 5.5 wurden Inhalte aus einem früheren costeo/DLC-Dokument verwendet. Dieses Dokument beschreibt eine frühere Version der Schnittstelle, und einige der darin enthaltenen Details stimmen nicht mehr mit der Anwendung überein. Die nachstehend aufgeführten Abweichungen müssen geklärt werden, bevor dieses Handbuch veröffentlicht wird.
|
Area |
Previous documentation |
Current application |
Action required |
|
Cost planning header |
Cards for Project VAT, Main Categories, Cost Groups with Budget, Planning Completion |
Cards for Cost calculation, Contracted companies, Invoices, Supplements, Project status |
Confirm whether the earlier cards were removed or relocated. |
|
Cost planning columns |
Cost Calculation, Forecast Completion incl. Risk, Difference, % |
Cost calculation, Effective, Forecast, Difference |
The Effective column is new and undocumented. Obtain a definition. |
|
Cost tracking header |
Budget, Supplements, Actual (Invoiced), Measured, Status |
Contract sum (budget), Award, Supplements approved, Invoiced (actual), Measured (approved), Deviation |
Labels and card count both differ. Adopt current labels. |
|
Cost tracking columns |
Company and Trade/Work as separate columns; no column for open supplements |
Single Trade / Company column; separate Suppl. open column |
Structure has changed. Current structure documented. |
|
Deviation / Difference formula |
Difference = Actual (Invoiced) − Award |
Captured data is consistent with Contract sum − Measured, not with the earlier formula |
CONTRADICTION. Must be confirmed with development before publication. |
|
Forecast formula |
Forecast Completion = Contract Sum + Risk |
Consistent with the manual entry dialog |
Appears still valid. Confirm. |
|
Controls |
Add Manual, Download, Refresh |
Manual entry, Download report, Live / snapshot selector |
Renamed. Confirm whether Refresh was replaced by the snapshot selector. |
|
Trades |
Called Ticket Category; created via an Add Category form |
Called Trade; created via the Add trade dialog |
Renamed. Confirmed by the QA team. Field mapping is close to one-to-one. |
|
CAPMO import |
Central CAPMO IMPORT page with Sync All, Sync Projects, and Sync Users, reporting Created / Updated / Deleted / Merged counts |
Per-project pull-and-review sync under Project settings > Sync, with per-field Keep local / Use CAPMO |
Workflow replaced. Current process documented in 5.3.4. |
|
Security basis |
Separate Net / Gross basis choice per security |
Single Basis dropdown offering Calculated or Fixed |
Confirm whether net/gross was removed or moved. |
|
Supplement terminology |
With / without supplements |
With / without amendments |
Same concept, two labels. Standardise. |
|
BoQ warning |
Not present |
BoQ warning threshold, default 85% |
New field. Obtain a definition. |
|
Bill of quantities |
Called Service Specifications; document called an LV |
Called Bill of quantities; document called a BoQ (LV still used in the editor) |
Renamed. Confirmed by the QA team. |
|
Creating a BoQ |
Single Add LV form: name, file upload, ticket category, Save |
Two steps: create an empty BoQ (trade, name), then import a file or use the editor |
Workflow changed. Current process documented. |
|
BoQ editor |
Not present — upload only |
Full editor with groups, subgroups, positions, note text, OZ numbering, GAEB check, Finalize |
Entirely new. Needs its own documentation and a populated screenshot. |
|
Supplements |
Created in CAPMO, then appear in costeo after a refresh |
Created directly via the Create as supplement toggle, with an explicit status |
Confirm whether both routes exist. |
|
Supplement status |
Approved / not approved only |
Draft, Internal review, Client review, Approved, Rejected |
Expanded. Confirm which statuses permit an upload. |
|
Invoice workflow |
Invoice, Measurement, Supplier Info |
Invoice, Measurement, Payment, Finalize |
Changed. Confirm where supplier information now sits. |
|
Creating an invoice |
Select ticket category, then a single Add Invoice page |
Three-step wizard: Trade, History, Details, then a draft |
Workflow changed. Current process documented. |
|
Invoice precondition |
Category must have an uploaded main LV |
Trade must have a finalized BoQ, and no other open draft |
Tightened. Upload alone is no longer sufficient. |
|
Quantity entry |
Enter the quantity billed in the current invoice only |
Field is labelled New cumulative, with prior quantity and cumulative percentage shown |
CONTRADICTION. Must be confirmed before publication or training. |
|
Historical baseline |
Not present |
Captured during invoice creation, once per trade, and not insertable later |
Entirely new. Documented. |
|
Position classifications |
New Position, Carried Forward, Modified Carried Forward, colour coded |
Status, Type, and Source filters |
Confirm whether the classifications survive and how they map. |
|
Rejected invoices |
Toggle inside the new invoice form |
Separate Record rejected invoice button |
Moved. Fields need re-confirming. |
|
Measurement trigger |
Measurement begins once the invoice has been finalised |
Measurement is stage 2; the invoice is still a draft. Finalisation is stage 4 |
Sequencing reversed. Do not carry the earlier wording across. |
|
Measurement columns |
LV Items, Invoice Items, Measured Items, INV Amount, Measured Amount, INV Calc, Aufmass Calc, Warnings |
Check, Position, Invoice vs measured, Measured, Amount, Comment |
Restructured. Current columns documented. |
|
Measurement detail |
Add a new measurement line via a plus icon |
Measurement groups and lines with calculation formulas and calculated quantities |
Substantially expanded. Documented. |
|
Supplier information |
Separate process, tickets created in CAPMO |
Supplier info opens the payment calculation, which is the cover sheet |
Relocated rather than removed. |
|
Product name |
DLC |
costeo |
Renamed. Retire the earlier document once this manual is approved. |
Achtung: Führen Sie das frühere Dokument nicht mit diesem zusammen, ohne jeden der oben genannten Punkte zu überprüfen. Die Veröffentlichung einer Formel, die von der Anwendung nicht verwendet wird, würde den Benutzern fehlerhafte Finanzdaten liefern.