Posting operational work (posting differences) – part 5

What is a main difference between using Output Order and Job & Position Journals?

As I wrote in my first post for this theme, we can post the operational work on next ways:

  • Using ‘Output Order’ – posting of Construction Position output work and Resource and Item consumption per Project in the same time;
  • Using ‘Position Journal’ – posting only Construction Position output work per Project; we need to post consumption separately;
  • Using ‘Job Journal’ (standard NAV functionality with some specific customizations) – posting only Resource and Item consumption per Project; we need to post output separately;

Advantage of the first method is that we can post all entries with the one document. We get posted document with ‘Navigate’ functionality. Also, this method enables us to have complete statistic of cost per every Construction Position for each Project.

As we look up in Construction Position Statistic for position posted using Output Orders, we can see Using (position cost), Sales (position revenue) and Profit:

Image

On previous picture we see position cost for each period.

Image

Image

In previous example, I presented Construction Position Statistic from NAV, and this is shown only costs, revenue and profit, without analytics. Also, if we use Output Orders for posting, we can make deeper analysis with complete analytics of resources and items cost or quantities, as picture bellow (from BI4CONS):

Image

Failing of this method is that if we have many complex position works per day, it is too complicated to make evidence and post it.

If we choose posting without ‘Output Order’, we get simply procedure for posting. We use ‘Position Journal’ for evidence of work per all Construction Position we have and separately we use ‘Job Journal’ for evidence of consumption all Items and Resources, not linked with Construction Positions. On this way we get simpler method, but we lose connection of consumption with Construction Position output. Using this method of posting, we know revenue for each position on project, but we don’t know position cost and profit. We could know cost and profit only per complete project or combination project and project task, and of course we will know this data per required period. As we look up in Construction Position Statistic for position posted using Position and Job Journals, we can see only Using (quantity, not a position cost) and Sales (position revenue):

Image

On previous picture, we cannot see position cost.

Image

Position sales data (previous picture) are the same as when we use Output Orders. But when we try to see profit, we will get a wrong data with 100% margins.

Image

We cannot get all things and we must to decide what method we want. Good thing is that we can choose different method for each project, depend of complexity and project requirement. Good thing is also that we can set filter on Position Statistic and we can see complete data for position posted using Output Order on each project.

Bill of Quantities – (Q&A) part 7

I get few questions about work in Bill of Quantities from my friends, and I will try to give answers.

Questions:

1)    When we have too much construction positions (I speak about thousands), how we can import the fast. This is usually case in building construction.

2)    When our customers/investors require from us quote in special file, how we can prepare that. We would not refuse big job because of that.

Answers:

1)    We have two solutions. If we already have this positions in our construction positions code-list, we can use command ‘Import from Excel’; we need prepare file with codes and quantities and NAV will import them. If we have not these positions (usually we have not them), we have specific function we call ‘Massive positions import’. This function import all positions from Excel; if we have this position in our code-list it is fine, but if we have not, NAV will create them in Construction Position code-list and add them Unit of Measure. Depends of description length, system will fill only description fields or will create extended text. Also, system will create Cross-reference code for this specific project and if we want create Normative Headers. Except creating in Cons.Position code-list, NAV will fill all BoQ lines.

2)    All users or partners can modify or make new Quote report. But, if this is not enough, because come customers can require that you must fill their Excel files, we have command ‘Export to Excel’. This is not perfect solution and system is not magical L, but it can help to reduce time to prepare document. We can export all important data to Excel file. You need to repack in required document design.

I am not explain all BoQ functionalities in my posts, but this is enough to understand way of working. If you have some other questions, I expect them and I will try to give you an answer.