Topic Thread

Viewpoint Vista use of subjobs

  • 1.  Viewpoint Vista use of subjobs

    Posted 7 days ago
    Is anyone currently using the sub job functionality in Viewpoint Vista?
    For example, contract with an owner to build 6 buildings.  One contract 12345, one job 12345, 6 sub jobs 12345-01, 12345-02, 12345-03, etc.
    If so, are you also using Procore and how does this interface?


    Carmen Agra-Boitnott CPA
    Subsidiary Controller
    Branch Builds/The Branch Group
    Roanoke VA
    (540) 982-1678

  • 2.  RE: Viewpoint Vista use of subjobs

    Posted 5 days ago
    ​Hi Carmen -

    While it's possible to have multiple jobs attached to one contract, the sub-job "functionality" is not the same in Viewpoint as what you might be used to in other packages. Before going that route, I would consider the reason for segregating the costs into separate jobs. Data security might be one, but aside from that, I'm not sure the benefits will outweigh the frustrations. If you're using Project Management, for example, the PCOs would be numbered by individual project. So in theory, you could have 3 PCO #1 if you had 1 main job and 2 sub job. This is just one minor example and someone might have discovered/created a workaround for this by now. I'm not aware of one currently.

    I would consider if there is another way to segregate the cost within one job that still meets everyone's needs. Do you have additional characters available in your phase code structure? If you have phase code 123456 currently, you can use 123456-01 and 123456-02, etc with the 01 and 02 being the sub jobs. If you're utilizing any budget import functionality, this modification would have little impact on the front end. Should you decide to go that route, you may want to create a Crystal or Excel report that would group JC detail by the 01 or 02 subjobs. This would mean adding a grouping condition to an existing report and is a relatively minor change. Additionally, if you're using PM Projections, you can create Projection Codes for each sub job. So if you have different PMs managing different portions, they can segregate their forecasts from others so as not to overlap or key in a different sub job accidentally.

    As for the original question of integration with Procore, the "sub job" as Viewpoint defines it is a separate job/project, so the sub job would not work any differently in a package that integrates based on project number.

    Sarah Stegman
    Director - Construction Software Consulting
    CohnReznick LLP

    (469) 371-7209