ArchiOffice Migration to Core and Additional Services

After you migrate from ArchiOffice/EngineerOffice to Core, you will notice a change in your project structure. We added the Additional Services phase and sub-phases under them because the object model and data model in ArchiOffice is different than in Core.

In ArchiOffice, we use a concept of Job Codes (services): ‘Basic Service’ and ‘Additional Service’. This design allows ArchiOffice users to generate invoices that separate fees by job codes: Basic Service fees and Additional Service fees. One of the shortcomings of this method is that you are unable to manage additional services with contract types other than Hourly. Firms using Fixed Fee or Hourly to a Cap contract types are forced to use workarounds to handle this need.

Core addresses this shortcoming by eliminating the need for job codes entirely. Every phase can have its own contract type. In order to migrate our ArchiOffice users to Core, we came up with the most effective option: convert all Additional Services job codes to sub-phases and group them under the Additional Services phase. When you expand this group (phase), you see a list of all your additional service job codes.

Here is an example of the Core project structure with Additional Services phase expanded:

2017-35: BRADFORD LAKE HOUSE

 

Schematic Design

 

Design Development

 

Construction Documents

 

Bidding & Negotiation

 

Contract Administration

 

CONSULTANTS

 

 

 

Civil Engineering

 

 

 

Structural Engineering

 

 

 

MEP Engineering

 

ADDITIONAL SERVICES

 

 

Change Order #1

 

 

Change Order #2

Was this article helpful?
0 out of 1 found this helpful