<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://thewiki.builtplainly.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Andrew+langstone</id>
	<title>SynWiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://thewiki.builtplainly.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Andrew+langstone"/>
	<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/wiki/Special:Contributions/Andrew_langstone"/>
	<updated>2026-11-05T04:32:48Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.35.6</generator>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1723</id>
		<title>List of Content</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1723"/>
		<updated>2023-09-06T16:34:23Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Operations Guide Table of Contents&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&amp;lt;blockquote&amp;gt;&amp;lt;big&amp;gt;'''''“Rocks in my path? I keep them all.'''''&amp;lt;/big&amp;gt; &lt;br /&gt;
&lt;br /&gt;
&amp;lt;big&amp;gt;'''''With them I shall build my castle.”'''''&amp;lt;/big&amp;gt; &lt;br /&gt;
&lt;br /&gt;
'''&amp;lt;big&amp;gt;''– Nemo Nox''&amp;lt;/big&amp;gt;'''&amp;lt;/blockquote&amp;gt;&lt;br /&gt;
&lt;br /&gt;
==Project Management Items (what is/how to) ==&lt;br /&gt;
&lt;br /&gt;
=== Viewpoint Fundamentals===&lt;br /&gt;
&lt;br /&gt;
*[[Introduction to Viewpoint]]&lt;br /&gt;
*[[Cost Item vs Cost Code]]&lt;br /&gt;
*[[Viewpoint Quick Reference]]&lt;br /&gt;
*[[Viewpoint Terminology]]&lt;br /&gt;
*[[Viewpoint Report Module]]&lt;br /&gt;
&lt;br /&gt;
===Operation / PM Duty Items ===&lt;br /&gt;
*[[Budget Upload]]&lt;br /&gt;
*[[Subcontract Management]]&lt;br /&gt;
**[[Generating Subcontract Using Template]]&lt;br /&gt;
**[[Sending Subcontract using DocuSign]]&lt;br /&gt;
*[[Project Change Management]]&lt;br /&gt;
*[[Document Controls]]&lt;br /&gt;
**[[Document Controls#RFI management|RFI management]]&lt;br /&gt;
**[[Document Controls#Submittal Management|Submittal management]]&lt;br /&gt;
*[[Project Cost and Forecast]]&lt;br /&gt;
*[[Cash Flow Projection]]&lt;br /&gt;
**[[Using Provided Template to Set Up Cash Flow Projection]]&lt;br /&gt;
*[[Viewpoint Reports]]&lt;br /&gt;
**Change Order Log&lt;br /&gt;
**Submittal and RFI log&lt;br /&gt;
**JC Cost Totals Drilldown&lt;br /&gt;
**Project Cost and Forecast&lt;br /&gt;
*[[Project Close Out]]&lt;br /&gt;
*&amp;lt;del&amp;gt;[[Creating Projection Codes]]&amp;lt;/del&amp;gt;&lt;br /&gt;
*&amp;lt;del&amp;gt;[[How to Complete a Cost Forecast using PM Cost Projections|Forecasting with PM Cost Projections]]&amp;lt;/del&amp;gt;&lt;br /&gt;
*[[Finance Calendar]]&lt;br /&gt;
&lt;br /&gt;
===Sequence Diagram for Typical Processes===&lt;br /&gt;
&lt;br /&gt;
*[[Development and Building Permits]]&lt;br /&gt;
*[[Demo Permit Process]]&lt;br /&gt;
*[[How to: Get Utility - Gas]]&lt;br /&gt;
*[[How to: Get Utility - Water]]&lt;br /&gt;
*[[How to: Get Utility - Power]]&lt;br /&gt;
*[[Project Close Out Process]]&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
==Estimating Items (what is/how to)==&lt;br /&gt;
&lt;br /&gt;
=== SGC Submission Review Procedures ===&lt;br /&gt;
&lt;br /&gt;
* [[SGC Submission Review Procedures]]&lt;br /&gt;
&lt;br /&gt;
=== Converting PDF to Excel ===&lt;br /&gt;
&lt;br /&gt;
* [[Converting PDF to Excel]]&lt;br /&gt;
&lt;br /&gt;
===Estimate 2.0 (Software) ===&lt;br /&gt;
*[[Download Tutorial]]&lt;br /&gt;
*[[Tutorial]]&lt;br /&gt;
*[[General Help Manual]]&lt;br /&gt;
*[[How-to: Quick Guide]]&lt;br /&gt;
*[[FAQ]]&lt;br /&gt;
&lt;br /&gt;
===Estimating Timecard===&lt;br /&gt;
*[[Timecard - Initial Setup|Initial Setup]]&lt;br /&gt;
*[[Timecard - Requesting|Requesting a Timecard]]&lt;br /&gt;
*[[Timecard - Submitting|Submitting a Timecard]]&lt;br /&gt;
*[[Timecard - Report|Viewing the Timecard Report]]&lt;br /&gt;
&lt;br /&gt;
=== [[Estimating Submission Summary (Software)]] ===&lt;br /&gt;
&lt;br /&gt;
* [[Download and Install]]&lt;br /&gt;
* [[Load report and printing report]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
==Business Technology==&lt;br /&gt;
*[[Demonstration of File Management]]&lt;br /&gt;
===&amp;lt;s&amp;gt;TimeLapse (obsolete)&amp;lt;/s&amp;gt; ===&lt;br /&gt;
*[[Set-up Tutorial | &amp;lt;s&amp;gt;TimeLapse Set-up Tutorial&amp;lt;/s&amp;gt;]]&lt;br /&gt;
===Power BI===&lt;br /&gt;
*[[Power BI|Power BI Summary]]&lt;br /&gt;
*[[Columns and Measures]]&lt;br /&gt;
*[[Power BI - Visualizations|Visualizations]]&lt;br /&gt;
*[[Power BI - Other Features|Other Features]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
[[Category:List Of Content]]&lt;br /&gt;
&lt;br /&gt;
== Operations Guide ==&lt;br /&gt;
&lt;br /&gt;
=== Project Startup ===&lt;br /&gt;
&lt;br /&gt;
* [[Getting a Job Number]]&lt;br /&gt;
* [[Project Execution Plan]]&lt;br /&gt;
* [[Project Quality Plan]]&lt;br /&gt;
* [[Project Safety Plan]]&lt;br /&gt;
* [[Job Start Meeting]]&lt;br /&gt;
* [[Budget Creation and Upload]]&lt;br /&gt;
* [[Awarding Subcontracts]]&lt;br /&gt;
* [[Permits, Licenses, and Utilities]]&lt;br /&gt;
* [[Project Insurance and Bonding]]&lt;br /&gt;
&lt;br /&gt;
=== Ongoing Project Management ===&lt;br /&gt;
&lt;br /&gt;
* [[Pre-mobilization Meetings with Trades]]&lt;br /&gt;
* [[Owner and Consultant Coordination Meetings]]&lt;br /&gt;
* [[Progress Claims and Billing]]&lt;br /&gt;
* [[Change Management]]&lt;br /&gt;
* [[Project Scheduling]]&lt;br /&gt;
* [[Shop Drawings and Submittals]]&lt;br /&gt;
* [[RFI Management]]&lt;br /&gt;
* [[Ongoing Quality Management]]&lt;br /&gt;
* [[Monthly Cost Forecasting]]&lt;br /&gt;
&lt;br /&gt;
=== Project Close Out ===&lt;br /&gt;
&lt;br /&gt;
* [[Deficiency Management (Punchlists)]]&lt;br /&gt;
* [[O&amp;amp;M Manuals and As-Builts]]&lt;br /&gt;
* [[Commissioning]]&lt;br /&gt;
* [[Warranty Management]]&lt;br /&gt;
&lt;br /&gt;
=== Memos (files) ===&lt;br /&gt;
&lt;br /&gt;
* [[Morley Hoppner - Costing and Forecasting Fundamentals Memo]]&lt;br /&gt;
---------------------&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Cost_Item_vs_Cost_Code&amp;diff=1213</id>
		<title>Cost Item vs Cost Code</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Cost_Item_vs_Cost_Code&amp;diff=1213"/>
		<updated>2022-11-15T22:46:19Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== cost items (contract item) vs cost code (phase code) ==&lt;br /&gt;
Cost Item sometimes in Viewpoint is called Contract Items, these terms are interchangeable in Viewpoint. For easiness, they will be called Cost Items in this help manual.&lt;br /&gt;
Cost Code sometimes in Viewpoint is called Phase Code/Phase Items, these terms are interchangeable in Viewpoint. For easiness, they will be called Cost Code in this help manual.&lt;br /&gt;
&lt;br /&gt;
In general terms, Cost Code is a place where the costs or commitments reside. Cost Items are a place Cost Codes reside (mostly cases) - as a summary of cost total under a group (or one) Cost Code. Another items that sometime used is called Billing Groups, which can be used to further summarize Cost Items. See examples on the right.&lt;br /&gt;
[[File:Bill Cost Item and Bill Group.png|thumb]]&lt;br /&gt;
[[File:Bill Cost Code and Cost Item.png|thumb]]&lt;br /&gt;
By principle, each cost code should only be mapped to 1 cost item. Each cost items can have multiple cost code mapped to&lt;br /&gt;
[[File:Multiple code to one item.png|center|Multiple code to one item]]&lt;br /&gt;
&lt;br /&gt;
In reality each cost code can also be mapped to multiple cost items, only can happen in LS-change orders. '''However, avoid doing this on CM projects, it would be a nightmare to reconcile'''&lt;br /&gt;
[[File:One code to multiple item.png|thumb|center|One Cost Code can be mapped to multiple Cost Items]]&lt;br /&gt;
&lt;br /&gt;
cost item is billing related. cost items can be further summarized and grouped by billing groups&lt;br /&gt;
[[File:Multi phases project with bill group.png|thumb|center|Multi phases project with bill group]]&lt;br /&gt;
&lt;br /&gt;
Cost Items can be added thru: JC Contract, Change Orders, Budget Upload&lt;br /&gt;
[[File:Viewpoint JC Cost Item to Bill Group.gif|frame|center|Viewpoint JC Cost Item to Bill Group]]&lt;br /&gt;
&lt;br /&gt;
Cost code can be added thru: JC Project Phases, Change Orders, Budget Upload.&lt;br /&gt;
'''Cost code can only be added on project level under parent code. Master code is controlled under JC Phases, avoid changing items in there.'''&lt;br /&gt;
[[File:Viewpoint JC Job Phases.gif|frame|center|Job Phases Module show location of where Cost Code mapped Cost Items]]&lt;br /&gt;
&lt;br /&gt;
== See Also ==&lt;br /&gt;
* [[Revenue_(Contract_items)_vs._Cost_(Phase_Codes)]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Revenue_(Contract_items)_vs._Cost_(Phase_Codes)&amp;diff=1212</id>
		<title>Revenue (Contract items) vs. Cost (Phase Codes)</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Revenue_(Contract_items)_vs._Cost_(Phase_Codes)&amp;diff=1212"/>
		<updated>2022-11-15T22:45:30Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are three fundamental types of codes used to track project finances: '''contract items''', '''phase codes''', and '''subcontract ledger items'''. It is important to understand the difference between each of these three and how they are used to manage project financials.&lt;br /&gt;
&lt;br /&gt;
=== Contract Items ===&lt;br /&gt;
'''Contract items''' are the line-item breakdowns that make up the prime contract between the project owner and the operating company. Contract items represent revenue elements that are paid to us during the course of the project. Simple projects may be set up with a single contract item, although it is far more common for a project to have many contract items. In general, the format, naming convention, and order of contract items is established by the owner in the project documents, or by mutual agreement between the Synergy project manager the owner and/or prime consultant prior to the first progress claim.&lt;br /&gt;
&lt;br /&gt;
The primary [[Companies,_Modules,_Programs,_and_Reports#Programs|program]] used in Viewpoint to create and modify contract items is the [[PM Contracts]] program.&lt;br /&gt;
&lt;br /&gt;
=== Phase Codes ===&lt;br /&gt;
'''Phase codes''' represent the cost centres of a project and are made up of one or more cost types.  Phase codes are the management codes used day-to-day to track original budgets, actual and committed costs, and final forecast costs for specific elements of work. As the project progresses, costs accrue to the phase codes as actual costs and committed costs, and project management teams forecast a final expected cost for each phase code at regular reporting intervals. The sum of all forecasted phase code values represents the project cost forecast at that time.&lt;br /&gt;
Phase codes must be tied to a corresponding contract item when they are created. This connects our work elements with revenue from the owner and creates an internal link inside Viewpoint between cost and revenue.&lt;br /&gt;
&lt;br /&gt;
The primary [[Companies,_Modules,_Programs,_and_Reports#Programs|programs]] used in Viewpoint to create and modify contract items are the [[PM Project Phases]] and [[PM Projects]] programs.&lt;br /&gt;
&lt;br /&gt;
=== Subcontract Ledger Items ===&lt;br /&gt;
'''Subcontract ledger (SL) items''' are the individual line items on a subcontract between the operating company and a trade contractor. Each subcontract has its own ledger of items and, when summed, the SL items form the total subcontract value. Subcontractors should bill against the SL items as their scope of work progresses.&lt;br /&gt;
SL items are analogous to contract items if we were acting as the owner and the subcontractor were the prime contractor.  &lt;br /&gt;
SL items are useful for providing insight into a specific subcontract that is taken out of the larger project context. &lt;br /&gt;
As SL items represent actual and/or committed costs, they are tied to a specific phase code in the project. If you want to spread subcontract costs between multiple phase codes, you will first need to create that breakdown in the SL items.&lt;br /&gt;
&lt;br /&gt;
The primary [[Companies,_Modules,_Programs,_and_Reports#Programs|programs]] used in Viewpoint to create and modify contract items are the [[PM Subcontracts]] and [[PM Subcontract Detail]] programs.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Revenue_(Contract_items)_vs._Cost_(Phase_Codes)&amp;diff=1211</id>
		<title>Revenue (Contract items) vs. Cost (Phase Codes)</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Revenue_(Contract_items)_vs._Cost_(Phase_Codes)&amp;diff=1211"/>
		<updated>2022-11-15T22:40:47Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Created page with &amp;quot;There are three fundamental types of codes used to track project finances: '''contract items''', '''phase codes''', and '''subcontract ledger items'''. It is important to unde...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;There are three fundamental types of codes used to track project finances: '''contract items''', '''phase codes''', and '''subcontract ledger items'''. It is important to understand the difference between each of these three and how they are used to manage project financials.&lt;br /&gt;
&lt;br /&gt;
=== Contract Items ===&lt;br /&gt;
'''Contract items''' are the line-item breakdowns that make up the prime contract between the project owner and the operating company. Contract items represent revenue elements that are paid to us during the course of the project. Simple projects may be set up with a single contract item, although it is far more common for a project to have many contract items. In general, the format, naming convention, and order of contract items is established by the owner in the project documents, or by mutual agreement between the Synergy project manager the owner and/or prime consultant prior to the first progress claim.&lt;br /&gt;
&lt;br /&gt;
=== Phase Codes ===&lt;br /&gt;
'''Phase codes''' represent the cost centres of a project and are made up of one or more cost types.  Phase codes are the management codes used day-to-day to track original budgets, actual and committed costs, and final forecast costs for specific elements of work. As the project progresses, costs accrue to the phase codes as actual costs and committed costs, and project management teams forecast a final expected cost for each phase code at regular reporting intervals. The sum of all forecasted phase code values represents the project cost forecast at that time.&lt;br /&gt;
Phase codes must be tied to a corresponding contract item when they are created. This connects our work elements with revenue from the owner and creates an internal link inside Viewpoint between cost and revenue.&lt;br /&gt;
&lt;br /&gt;
=== Subcontract Ledger Items ===&lt;br /&gt;
'''Subcontract ledger (SL) items''' are the individual line items on a subcontract between the operating company and a trade contractor. Each subcontract has its own ledger of items and, when summed, the SL items form the total subcontract value. Subcontractors should bill against the SL items as their scope of work progresses.&lt;br /&gt;
SL items are analogous to contract items if we were acting as the owner and the subcontractor were the prime contractor.  &lt;br /&gt;
SL items are useful for providing insight into a specific subcontract that is taken out of the larger project context. &lt;br /&gt;
As SL items represent actual and/or committed costs, they are tied to a specific phase code in the project. If you want to spread subcontract costs between multiple phase codes, you will first need to create that breakdown in the SL items.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Companies,_Modules,_Programs,_and_Reports&amp;diff=1210</id>
		<title>Companies, Modules, Programs, and Reports</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Companies,_Modules,_Programs,_and_Reports&amp;diff=1210"/>
		<updated>2022-11-14T17:57:09Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Created page with &amp;quot;=== Companies === The company dropdown allows you to change the active company File:Viewpoint Modules, programs, reports.png|thumb|Ide...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== Companies ===&lt;br /&gt;
[[File:Viewpoint Companies.png|thumb|The company dropdown allows you to change the active company]]&lt;br /&gt;
[[File:Viewpoint Modules, programs, reports.png|thumb|Identifying modules, programs, and reports in the Viewpoint interface]]&lt;br /&gt;
Before any broad discussion of the Viewpoint interface, it is important to note that Viewpoint is built to allow multiple businesses and legal entities to operate in the same umbrella application.  The Synergy Group of Companies includes several core operating companies (Synergy Group of Companies, Synergy Projects, Morley Hoppner, and Innerspaces), and several project specific holding companies that have been set up for a short duration on a single project.  &lt;br /&gt;
&lt;br /&gt;
Each of these legal entities is its own &amp;quot;company&amp;quot; in Viewpoint with a separate set of accounting books and independent tax filing requirements.  The Viewpoint application interface will remain exactly the same regardless of the company you are working in.   When you change the Company drop down, you will be working with the set of books related to the company you chose.  You can only ever work in one company at a time.&lt;br /&gt;
&lt;br /&gt;
=== Modules ===&lt;br /&gt;
The Viewpoint application is broken down into three core interface components - modules, reports, and programs.&lt;br /&gt;
&lt;br /&gt;
Modules are high level groupings of features and each module shows up on the main tree in the left side of the application.  Commonly used modules are:&lt;br /&gt;
* Project Management and Job Cost (For project managers)&lt;br /&gt;
* Accounts Payable, Accounts Receivable, and Payroll (for project accountants)&lt;br /&gt;
&lt;br /&gt;
When expanded, each module is contains two sub-folders - Programs and Reports&lt;br /&gt;
&lt;br /&gt;
=== Programs ===&lt;br /&gt;
Programs provide the interface for adding and editing data that is saved within Viewpoint.  Some programs are very targeted towards a specific task or data table (example - PM Phase Codes deals specifically with the creation and management of project cost centers), while others will cover several different job functions in one place (example - PM Projects includes areas to manage phase codes, contract items, general project information, and contact information)&lt;br /&gt;
&lt;br /&gt;
Viewpoint uses a system of user level permissions set up by the company administrator.  These permissions are generally created based on the job title of the individual user.  Viewpoint permissions restrict which programs are accessible to you - programs in black are accessible, programs in grey are not.  If there is a program that you require access to, please contact the Viewpoint administrator in your office to gain access. &lt;br /&gt;
&lt;br /&gt;
=== Reports === &lt;br /&gt;
The other subfolder in each module is the Reports folder.  Reports are used to extract and format data into a coherent document that can be used outside of the application in the day-to-day needs of the business.  Each report available to a module produces very specifics insights about a certain facet of the project.  Reports generally have a pop-up that allows you to set up parameters on data ranges to include, or specific formatting options. &lt;br /&gt;
&lt;br /&gt;
There are many reports available across the system, and most are used infrequently (if at all).  The key reports for each job function are highlighted in the relevant sections of this guide.  Similar to the programs list permissions restrict which programs are accessible to you - programs in black are accessible, programs in grey are not.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=File:Viewpoint_Modules,_programs,_reports.png&amp;diff=1209</id>
		<title>File:Viewpoint Modules, programs, reports.png</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=File:Viewpoint_Modules,_programs,_reports.png&amp;diff=1209"/>
		<updated>2022-11-14T17:56:36Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Identifying the modules, programs, and reports in the viewpoint interface.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=File:Viewpoint_Companies.png&amp;diff=1208</id>
		<title>File:Viewpoint Companies.png</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=File:Viewpoint_Companies.png&amp;diff=1208"/>
		<updated>2022-11-14T17:47:56Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The company dropdown allows you to toggle the active company&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Introduction_to_Viewpoint&amp;diff=1207</id>
		<title>Introduction to Viewpoint</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Introduction_to_Viewpoint&amp;diff=1207"/>
		<updated>2022-11-14T17:42:06Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Created page with &amp;quot;Viewpoint Vista is the core accounting suite used by the Synergy Group of Companies to manage our business.  While Viewpoint is fundamentally for accounting, it is a construct...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Viewpoint Vista is the core accounting suite used by the Synergy Group of Companies to manage our business.  While Viewpoint is fundamentally for accounting, it is a construction specific tool that includes project management functions to assist in managing document control on projects. &lt;br /&gt;
&lt;br /&gt;
Viewpoint is at times quirky - the interface is not always intuitive and there is a learning curve for first time users of the application.  Once you learn your way aroudn the program, however, it is a very powerful reporting tool that can provide actionable insight for effective project management.&lt;br /&gt;
&lt;br /&gt;
If you are using Viewpoint for the first time, it can be helpful to read through the following articles that cover the core concepts of the Viewpoint application:&lt;br /&gt;
* [[Companies, Modules, Programs, and Reports]]&lt;br /&gt;
* [[Revenue (Contract items) vs. Cost (Phase Codes)]]&lt;br /&gt;
* [[Helpful Shortcuts]]&lt;br /&gt;
* [[Interfacing Project Managemeent with Accounting in Viewpoint]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1206</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1206"/>
		<updated>2022-09-09T19:56:15Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Forecasting phase codes in Viewpoint */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Initializing a new projection ===&lt;br /&gt;
[[File:Initializing a cost projection.gif|thumb|How to initialize a new cost projection in PM Cost Projections - Click the image to view a larger size]]&lt;br /&gt;
To start a new forecast, open the PM Cost Projections program inside the Project Management module in Viewpoint.  This will open a blank cost projection screen.  Enter the projection date by clicking the calendar button next to the projection date to open a calendar and choose a data, or you can type it manually as MM/DD/YY.  Then enter your project number by hitting F4 and choosing from the project list, or by typing the number in manually.&lt;br /&gt;
&lt;br /&gt;
Once you have entered both a projection data and project number, a dialog window will open with options for how to handle [[#Viewpoint Forecasting Terminology|Plugged Values]].  Choose the first option (&amp;quot;Never&amp;quot;) and click the Initialize button to populate the cost projection grid.&lt;br /&gt;
&lt;br /&gt;
'''''HINT:''''' ''If you have previously started a forecast and want to pick up where you left off - hit the F4 key while in the Projection Date box to bring up a list of all open cost projections that are associated with you. ''&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint ===&lt;br /&gt;
Once your project has been set up with projection codes based on phase codes (for more information how to do this - see the [[Creating Projection Codes]] article), you are able to go line by line through each phase code of your project and provide an estimate of the final financial position of each line.  Once complete, the sum of each of these lines adds up to the total project cost forecast. &lt;br /&gt;
&lt;br /&gt;
Viewpoint's forecasting module is flexible in that you can forecast each individual line using one of the following methods:&lt;br /&gt;
* Percent Complete Cost&lt;br /&gt;
* Remaining Cost&lt;br /&gt;
* Projected Final Cost&lt;br /&gt;
* Over / Under Cost&lt;br /&gt;
&lt;br /&gt;
* Percent Complete Hours&lt;br /&gt;
* Remaining Hours&lt;br /&gt;
* Projected Final Hours&lt;br /&gt;
* Over / Under Hours&lt;br /&gt;
'''''Note:''''' ''In order to be able to forecast based on hours, the phase code requires an budget of the number of hours required to complete the task which occurs during the estimate upload step.  If you did not set up your project with hours on labour phase codes, you will not be able to forecast using hours and will need to forecast using costs.''&lt;br /&gt;
&lt;br /&gt;
When you update any one of the fields, Viewpoint will automatically calculate the impact on the other columns in the same row.  For example, changing Percent Complete Cost will result in Viewpoint automatically updating the Remaining Cost, Projected Final Cost, and Over / Under Costs to reflect the change, as well as the equivalent hour columns if you have set up your phase codes with hours.&lt;br /&gt;
&lt;br /&gt;
To complete the forecast in Viewpoint, you can work through each phase code on your project from the first to last.  Determine the final value for each line and update the column most relevant to your calculation.  Hitting the enter key while in the cell, or navigating out of the cell will recalculate all other columns in the same row and save changes.  Lines that have been edited will highlight in yellow to help you keep track of your progress (sometimes it will not highlight immediately and you may need to close and reopen the PM Cost Projections program to see changes).&lt;br /&gt;
&lt;br /&gt;
For a detailed guide on how to forecast accurately using Viewpoint, see the [[Forecasting Phase Codes Detailed Guide]] article.&lt;br /&gt;
&lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Viewpoint Forecasting Terminology ===&lt;br /&gt;
Viewpoint has a set of terminology used inside the application that relates to costing and forecasting.  Some of the terminology used within the Viewpoint software is different that the terms we use day-to-day at Synergy to describe the same thing.  Here is a list of terms used in Viewpoint, their meanings within the application, and an equivalent synonym that you may hear at the office&lt;br /&gt;
&lt;br /&gt;
* '''Cost Projection''' - This refers to the estimate of final costs for a project.  A cost projection is completed for a specific date and a specific project.  We often refer to this as a forecast, a project forecast, or a cost forecast.&lt;br /&gt;
&lt;br /&gt;
* '''Plugged Values''' - This refers to any value on a projection code that has been manually changed by a human user.  Viewpoint will automatically generate estimates for forecast values , and when you overwrite one of these automatically generated values with a manual input you have created a plugged value.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1205</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1205"/>
		<updated>2022-09-09T19:34:27Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Forecasting phase codes in Viewpoint */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Initializing a new projection ===&lt;br /&gt;
[[File:Initializing a cost projection.gif|thumb|How to initialize a new cost projection in PM Cost Projections - Click the image to view a larger size]]&lt;br /&gt;
To start a new forecast, open the PM Cost Projections program inside the Project Management module in Viewpoint.  This will open a blank cost projection screen.  Enter the projection date by clicking the calendar button next to the projection date to open a calendar and choose a data, or you can type it manually as MM/DD/YY.  Then enter your project number by hitting F4 and choosing from the project list, or by typing the number in manually.&lt;br /&gt;
&lt;br /&gt;
Once you have entered both a projection data and project number, a dialog window will open with options for how to handle [[#Viewpoint Forecasting Terminology|Plugged Values]].  Choose the first option (&amp;quot;Never&amp;quot;) and click the Initialize button to populate the cost projection grid.&lt;br /&gt;
&lt;br /&gt;
'''''HINT:''''' ''If you have previously started a forecast and want to pick up where you left off - hit the F4 key while in the Projection Date box to bring up a list of all open cost projections that are associated with you. ''&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint ===&lt;br /&gt;
Once your project has been set up with projection codes based on phase codes (for more information how to do this - see the [[Creating Projection Codes]] article), you are able to go line by line through each phase code of your project and provide an estimate of the final financial position of each line.  Once complete, the sum of each of these lines adds up to the total project cost forecast. &lt;br /&gt;
&lt;br /&gt;
Viewpoint's forecasting module is flexible in that you can forecast each individual line using one of the following methods:&lt;br /&gt;
* Percent Complete Cost&lt;br /&gt;
* Remaining Cost&lt;br /&gt;
* Projected Final Cost&lt;br /&gt;
* Over / Under Cost&lt;br /&gt;
&lt;br /&gt;
* Percent Complete Hours&lt;br /&gt;
* Remaining Hours&lt;br /&gt;
* Projected Final Hours&lt;br /&gt;
* Over / Under Hours&lt;br /&gt;
'''''Note:''''' ''In order to be able to forecast based on hours, the phase code requires an budget of the number of hours required to complete the task which occurs during the estimate upload step.  If you did not set up your project with hours on labour phase codes, you will not be able to forecast using hours and will need to forecast using costs.''&lt;br /&gt;
&lt;br /&gt;
When you update any one of the fields, Viewpoint will automatically calculate the impact on the other columns in the same row.  For example, changing Percent Complete Cost will result in Viewpoint automatically updating the Remaining Cost, Projected Final Cost, and Over / Under Costs to reflect the change, as well as the equivalent hour columns if you have set up your phase codes with hours.&lt;br /&gt;
&lt;br /&gt;
To complete the forecast in Viewpoint, you can work through each phase code on your project from the first to last.  Determine the final value for each line and update the column most relevant to your calculation.  Hitting the enter key while in the cell, or navigating out of the cell will recalculate all other columns in the same row and save changes.  Lines that have been edited will highlight in yellow to help you keep track of your progress (sometimes it will not highlight immediately and you may need to close and reopen the PM Cost Projections program to see changes).&lt;br /&gt;
&lt;br /&gt;
For a detailed guide on how to forecast accurately using Viewpoint, see the [[Forecasting with Viewpoint Guide]] article.&lt;br /&gt;
&lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Viewpoint Forecasting Terminology ===&lt;br /&gt;
Viewpoint has a set of terminology used inside the application that relates to costing and forecasting.  Some of the terminology used within the Viewpoint software is different that the terms we use day-to-day at Synergy to describe the same thing.  Here is a list of terms used in Viewpoint, their meanings within the application, and an equivalent synonym that you may hear at the office&lt;br /&gt;
&lt;br /&gt;
* '''Cost Projection''' - This refers to the estimate of final costs for a project.  A cost projection is completed for a specific date and a specific project.  We often refer to this as a forecast, a project forecast, or a cost forecast.&lt;br /&gt;
&lt;br /&gt;
* '''Plugged Values''' - This refers to any value on a projection code that has been manually changed by a human user.  Viewpoint will automatically generate estimates for forecast values , and when you overwrite one of these automatically generated values with a manual input you have created a plugged value.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1204</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1204"/>
		<updated>2022-09-09T19:32:37Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Forecasting phase codes in Viewpoint */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Initializing a new projection ===&lt;br /&gt;
[[File:Initializing a cost projection.gif|thumb|How to initialize a new cost projection in PM Cost Projections - Click the image to view a larger size]]&lt;br /&gt;
To start a new forecast, open the PM Cost Projections program inside the Project Management module in Viewpoint.  This will open a blank cost projection screen.  Enter the projection date by clicking the calendar button next to the projection date to open a calendar and choose a data, or you can type it manually as MM/DD/YY.  Then enter your project number by hitting F4 and choosing from the project list, or by typing the number in manually.&lt;br /&gt;
&lt;br /&gt;
Once you have entered both a projection data and project number, a dialog window will open with options for how to handle [[#Viewpoint Forecasting Terminology|Plugged Values]].  Choose the first option (&amp;quot;Never&amp;quot;) and click the Initialize button to populate the cost projection grid.&lt;br /&gt;
&lt;br /&gt;
'''''HINT:''''' ''If you have previously started a forecast and want to pick up where you left off - hit the F4 key while in the Projection Date box to bring up a list of all open cost projections that are associated with you. ''&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint ===&lt;br /&gt;
Once your project has been set up with projection codes based on phase codes (for more information how to do this - see the [[Creating Projection Codes]] article), you are able to go line by line through each phase code of your project and provide an estimate of the final financial position of each line.  Once complete, the sum of each of these lines adds up to the total project cost forecast. &lt;br /&gt;
&lt;br /&gt;
Viewpoint's forecasting module is flexible in that you can forecast each individual line using one of the following methods:&lt;br /&gt;
* Percent Complete Cost&lt;br /&gt;
* Remaining Cost&lt;br /&gt;
* Projected Final Cost&lt;br /&gt;
* Over / Under Cost&lt;br /&gt;
&lt;br /&gt;
* Percent Complete Hours&lt;br /&gt;
* Remaining Hours&lt;br /&gt;
* Projected Final Hours&lt;br /&gt;
* Over / Under Hours&lt;br /&gt;
'''''Note:''''' ''In order to be able to forecast based on hours, the phase code requires an budget of the number of hours required to complete the task which occurs during the estimate upload step.  If you did not set up your project with hours on labour phase codes, you will not be able to forecast using hours and will need to forecast using costs.''&lt;br /&gt;
&lt;br /&gt;
When you update any one of the fields, Viewpoint will automatically calculate the impact on the other columns in the same row.  For example, changing Percent Complete Cost will result in Viewpoint automatically updating the Remaining Cost, Projected Final Cost, and Over / Under Costs to reflect the change, as well as the equivalent hour columns if you have set up your phase codes with hours.&lt;br /&gt;
&lt;br /&gt;
To complete the forecast in Viewpoint, you can work through each phase code on your project from the first to last.  Determine the final value for each line and update the column most relevant to your calculation.  Hitting the enter key while in the cell, or navigating out of the cell will recalculate all other columns in the same row and save changes.  Lines that have been edited will highlight in yellow to help you keep track of your progress (sometimes it will not highlight immediately and you may need to close and reopen the PM Cost Projections program to see changes).&lt;br /&gt;
&lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Viewpoint Forecasting Terminology ===&lt;br /&gt;
Viewpoint has a set of terminology used inside the application that relates to costing and forecasting.  Some of the terminology used within the Viewpoint software is different that the terms we use day-to-day at Synergy to describe the same thing.  Here is a list of terms used in Viewpoint, their meanings within the application, and an equivalent synonym that you may hear at the office&lt;br /&gt;
&lt;br /&gt;
* '''Cost Projection''' - This refers to the estimate of final costs for a project.  A cost projection is completed for a specific date and a specific project.  We often refer to this as a forecast, a project forecast, or a cost forecast.&lt;br /&gt;
&lt;br /&gt;
* '''Plugged Values''' - This refers to any value on a projection code that has been manually changed by a human user.  Viewpoint will automatically generate estimates for forecast values , and when you overwrite one of these automatically generated values with a manual input you have created a plugged value.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1203</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1203"/>
		<updated>2022-09-09T17:15:20Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Forecasting phase codes in Viewpoint */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Initializing a new projection ===&lt;br /&gt;
[[File:Initializing a cost projection.gif|thumb|How to initialize a new cost projection in PM Cost Projections - Click the image to view a larger size]]&lt;br /&gt;
To start a new forecast, open the PM Cost Projections program inside the Project Management module in Viewpoint.  This will open a blank cost projection screen.  Enter the projection date by clicking the calendar button next to the projection date to open a calendar and choose a data, or you can type it manually as MM/DD/YY.  Then enter your project number by hitting F4 and choosing from the project list, or by typing the number in manually.&lt;br /&gt;
&lt;br /&gt;
Once you have entered both a projection data and project number, a dialog window will open with options for how to handle [[#Viewpoint Forecasting Terminology|Plugged Values]].  Choose the first option (&amp;quot;Never&amp;quot;) and click the Initialize button to populate the cost projection grid.&lt;br /&gt;
&lt;br /&gt;
'''''HINT:''''' ''If you have previously started a forecast and want to pick up where you left off - hit the F4 key while in the Projection Date box to bring up a list of all open cost projections that are associated with you. ''&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint ===&lt;br /&gt;
Once your project has been set up with projection codes based on phase codes (for more information how to do this - see the [[Creating Projection Codes]] article), you are able to go line by line through each phase code of your project and provide an estimate of the final financial position of each line.  Once complete, the sum of each of these lines adds up to the total project cost forecast. &lt;br /&gt;
&lt;br /&gt;
Viewpoint's forecasting module is flexible in that you can forecast each individual line using one of the following methods:&lt;br /&gt;
* Percent Complete Cost&lt;br /&gt;
* Remaining Cost&lt;br /&gt;
* Projected Final Cost&lt;br /&gt;
* Over / Under Cost&lt;br /&gt;
&lt;br /&gt;
* Percent Complete Hours&lt;br /&gt;
* Remaining Hours&lt;br /&gt;
* Projected Final Hours&lt;br /&gt;
* Over / Under Hours&lt;br /&gt;
'''''Note:''''' ''In order to be able to forecast based on hours, the phase code requires an budget of the number of hours required to complete the task which occurs during the estimate upload step.  If you did not set up your project with hours on labour phase codes, you will not be able to forecast using hours and will need to forecast using costs.''&lt;br /&gt;
&lt;br /&gt;
When you update any one of the fields, Viewpoint will automatically calculate the impact on the other columns in the same row.  For example, changing Percent Complete Cost will result in Viewpoint automatically updating the Remaining Cost, Projected Final Cost, and Over / Under Costs to reflect the change, as well as the equivalent hour columns if you have set up your phase codes with hours.&lt;br /&gt;
&lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Viewpoint Forecasting Terminology ===&lt;br /&gt;
Viewpoint has a set of terminology used inside the application that relates to costing and forecasting.  Some of the terminology used within the Viewpoint software is different that the terms we use day-to-day at Synergy to describe the same thing.  Here is a list of terms used in Viewpoint, their meanings within the application, and an equivalent synonym that you may hear at the office&lt;br /&gt;
&lt;br /&gt;
* '''Cost Projection''' - This refers to the estimate of final costs for a project.  A cost projection is completed for a specific date and a specific project.  We often refer to this as a forecast, a project forecast, or a cost forecast.&lt;br /&gt;
&lt;br /&gt;
* '''Plugged Values''' - This refers to any value on a projection code that has been manually changed by a human user.  Viewpoint will automatically generate estimates for forecast values , and when you overwrite one of these automatically generated values with a manual input you have created a plugged value.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1202</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1202"/>
		<updated>2022-09-09T16:28:06Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Viewpoint Forecasting Terminology */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Initializing a new projection ===&lt;br /&gt;
[[File:Initializing a cost projection.gif|thumb|How to initialize a new cost projection in PM Cost Projections - Click the image to view a larger size]]&lt;br /&gt;
To start a new forecast, open the PM Cost Projections program inside the Project Management module in Viewpoint.  This will open a blank cost projection screen.  Enter the projection date by clicking the calendar button next to the projection date to open a calendar and choose a data, or you can type it manually as MM/DD/YY.  Then enter your project number by hitting F4 and choosing from the project list, or by typing the number in manually.&lt;br /&gt;
&lt;br /&gt;
Once you have entered both a projection data and project number, a dialog window will open with options for how to handle [[#Viewpoint Forecasting Terminology|Plugged Values]].  Choose the first option (&amp;quot;Never&amp;quot;) and click the Initialize button to populate the cost projection grid.&lt;br /&gt;
&lt;br /&gt;
'''''HINT:''''' ''If you have previously started a forecast and want to pick up where you left off - hit the F4 key while in the Projection Date box to bring up a list of all open cost projections that are associated with you. ''&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Viewpoint Forecasting Terminology ===&lt;br /&gt;
Viewpoint has a set of terminology used inside the application that relates to costing and forecasting.  Some of the terminology used within the Viewpoint software is different that the terms we use day-to-day at Synergy to describe the same thing.  Here is a list of terms used in Viewpoint, their meanings within the application, and an equivalent synonym that you may hear at the office&lt;br /&gt;
&lt;br /&gt;
* '''Cost Projection''' - This refers to the estimate of final costs for a project.  A cost projection is completed for a specific date and a specific project.  We often refer to this as a forecast, a project forecast, or a cost forecast.&lt;br /&gt;
&lt;br /&gt;
* '''Plugged Values''' - This refers to any value on a projection code that has been manually changed by a human user.  Viewpoint will automatically generate estimates for forecast values , and when you overwrite one of these automatically generated values with a manual input you have created a plugged value.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1201</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1201"/>
		<updated>2022-09-09T16:27:55Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Initializing a new projection ===&lt;br /&gt;
[[File:Initializing a cost projection.gif|thumb|How to initialize a new cost projection in PM Cost Projections - Click the image to view a larger size]]&lt;br /&gt;
To start a new forecast, open the PM Cost Projections program inside the Project Management module in Viewpoint.  This will open a blank cost projection screen.  Enter the projection date by clicking the calendar button next to the projection date to open a calendar and choose a data, or you can type it manually as MM/DD/YY.  Then enter your project number by hitting F4 and choosing from the project list, or by typing the number in manually.&lt;br /&gt;
&lt;br /&gt;
Once you have entered both a projection data and project number, a dialog window will open with options for how to handle [[#Viewpoint Forecasting Terminology|Plugged Values]].  Choose the first option (&amp;quot;Never&amp;quot;) and click the Initialize button to populate the cost projection grid.&lt;br /&gt;
&lt;br /&gt;
'''''HINT:''''' ''If you have previously started a forecast and want to pick up where you left off - hit the F4 key while in the Projection Date box to bring up a list of all open cost projections that are associated with you. ''&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;br /&gt;
&lt;br /&gt;
== Tips and Tricks ==&lt;br /&gt;
=== Viewpoint Forecasting Terminology ===&lt;br /&gt;
Viewpoint has a set of terminology used inside the application that relates to costing and forecasting.  Some of the terminology used within the Viewpoint software is different that the terms we use day-to-day at Synergy to describe the same thing.  Here is a list of terms used in Viewpoint, their meanings within the application, and an equivalent synonym that you may hear at the office&lt;br /&gt;
&lt;br /&gt;
* '''Plugged Values''' - This refers to any value on a projection code that has been manually changed by a human user.  Viewpoint will automatically generate estimates for forecast values , and when you overwrite one of these automatically generated values with a manual input you have created a plugged value.&lt;br /&gt;
* '''Cost Projection''' - This refers to the estimate of final costs for a project.  A cost projection is completed for a specific date and a specific project.  We often refer to this as a forecast, a project forecast, or a cost forecast.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1200</id>
		<title>Creating Projection Codes</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1200"/>
		<updated>2022-09-09T16:11:18Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* How to add a cost type to an existing projection code */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== What are Projection Codes ===&lt;br /&gt;
Viewpoint uses '''Projection Codes''' to assist in completing project forecasts.  Projection codes allow different work elements, phase codes or cost types, to be grouped together into large &amp;quot;bundles&amp;quot; of scope that can be forecast together.  At Synergy, we don't bundle our phases together and our monthly forecasts look at each phase code individually every month.   Nevertheless, we need to create one projection code for each phase code in order for the Cost Projection module to work in Viewpoint.   &lt;br /&gt;
&lt;br /&gt;
=== Creating Projection Codes ===&lt;br /&gt;
[[File:Create Projection Codes.gif|thumb|Create projection codes using PM Projection Codes]]&lt;br /&gt;
Fortunately there is an easy way to quickly create projection codes on your project.&lt;br /&gt;
&lt;br /&gt;
# Open PM Projection Codes &lt;br /&gt;
# Click the &amp;quot;Tasks&amp;quot; menu&lt;br /&gt;
# Choose &amp;quot;Create Projection Codes From Phases&amp;quot;&lt;br /&gt;
# In the pop-up modal, click &amp;quot;Start&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you are using the [[How to Complete a Cost Forecast using PM Cost Projections|PM Cost Projections to complete cost forecasts]], you will need to create projection codes prior to completing your first forecast to capture all of the phase codes of your original project budget.  It is often the case that new phase codes will be created during the course of construction for unforeseen items, and owner changes.  Whenever a new phase code is added to the project, a projection code will also need to be added in order to complete future forecasts.  For this reason, it is a good idea to create projection codes as the step at the start of every forecast period.  You can use the same process as above to create projection codes for new phases that did not exist at the last forecast period.&lt;br /&gt;
&lt;br /&gt;
=== How to add a cost type to an existing projection code ===&lt;br /&gt;
If a projection code already exists on your project and a new cost type is added to the phase code associated with the projection code, then an error will arise when you try to create projection codes from phases:&lt;br /&gt;
&lt;br /&gt;
[[File:Projection Codes Error - Cost Type cannot be added.png|Error: Projection Code already exists.  Cost Types cannot be added]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
[[File:Add cost type to existing phase projection code.gif|thumb|Add a new cost type to an existing projection code]]&lt;br /&gt;
&lt;br /&gt;
To resolve this issue, you need to add the new cost type to the existing projection code.  &lt;br /&gt;
&lt;br /&gt;
# From the Grid tab, find the relevant projection code that requires updating and click the row to highlight it&lt;br /&gt;
# Click the icon with a + and three lines next to the Tasks dropdown&lt;br /&gt;
# Choose the unassinged cost type from the &amp;quot;Available Phases&amp;quot; column.  Click to highlight it&lt;br /&gt;
# Click the &amp;quot;Add&amp;quot; button to assign it to the projection code. &lt;br /&gt;
# Click the &amp;quot;Apply&amp;quot; button to svae changes&lt;br /&gt;
# Click the &amp;quot;Close&amp;quot; button to return to PM Projection Codes&lt;br /&gt;
&lt;br /&gt;
'''''Note:'''''  ''If there are multiple lines listed in the &amp;quot;Available Phases&amp;quot; column, repeat the first four steps until the column is empty.''&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1199</id>
		<title>Creating Projection Codes</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1199"/>
		<updated>2022-09-09T16:09:56Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Creating Projection Codes */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== What are Projection Codes ===&lt;br /&gt;
Viewpoint uses '''Projection Codes''' to assist in completing project forecasts.  Projection codes allow different work elements, phase codes or cost types, to be grouped together into large &amp;quot;bundles&amp;quot; of scope that can be forecast together.  At Synergy, we don't bundle our phases together and our monthly forecasts look at each phase code individually every month.   Nevertheless, we need to create one projection code for each phase code in order for the Cost Projection module to work in Viewpoint.   &lt;br /&gt;
&lt;br /&gt;
=== Creating Projection Codes ===&lt;br /&gt;
[[File:Create Projection Codes.gif|thumb|Create projection codes using PM Projection Codes]]&lt;br /&gt;
Fortunately there is an easy way to quickly create projection codes on your project.&lt;br /&gt;
&lt;br /&gt;
# Open PM Projection Codes &lt;br /&gt;
# Click the &amp;quot;Tasks&amp;quot; menu&lt;br /&gt;
# Choose &amp;quot;Create Projection Codes From Phases&amp;quot;&lt;br /&gt;
# In the pop-up modal, click &amp;quot;Start&amp;quot;&lt;br /&gt;
&lt;br /&gt;
If you are using the [[How to Complete a Cost Forecast using PM Cost Projections|PM Cost Projections to complete cost forecasts]], you will need to create projection codes prior to completing your first forecast to capture all of the phase codes of your original project budget.  It is often the case that new phase codes will be created during the course of construction for unforeseen items, and owner changes.  Whenever a new phase code is added to the project, a projection code will also need to be added in order to complete future forecasts.  For this reason, it is a good idea to create projection codes as the step at the start of every forecast period.  You can use the same process as above to create projection codes for new phases that did not exist at the last forecast period.&lt;br /&gt;
&lt;br /&gt;
=== How to add a cost type to an existing projection code ===&lt;br /&gt;
If a projection code already exists on your project and a new cost type is added to the phase code associated with the projection code, then an error will arise when you try to create projection codes from phases:&lt;br /&gt;
&lt;br /&gt;
[[File:Projection Codes Error - Cost Type cannot be added.png|Error: Projection Code already exists.  Cost Types cannot be added]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
To resolve this issue, you need to add the new cost type to the existing projection code.  &lt;br /&gt;
&lt;br /&gt;
# From the Grid tab, find the relevant projection code that requires updating and click the row to highlight it&lt;br /&gt;
# Click the icon with a + and three lines next to the Tasks dropdown&lt;br /&gt;
# Choose the unassinged cost type from the &amp;quot;Available Phases&amp;quot; column.  Click to highlight it&lt;br /&gt;
# Click the &amp;quot;Add&amp;quot; button to assign it to the projection code. &lt;br /&gt;
# Click the &amp;quot;Apply&amp;quot; button to svae changes&lt;br /&gt;
# Click the &amp;quot;Close&amp;quot; button to return to PM Projection Codes&lt;br /&gt;
&lt;br /&gt;
'''''Note:'''''  ''If there are multiple lines listed in the &amp;quot;Available Phases&amp;quot; column, repeat the first four steps until the column is empty.''&lt;br /&gt;
&lt;br /&gt;
[[File:Add cost type to existing phase projection code.gif|Add a new cost type to an existing projection code]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1198</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1198"/>
		<updated>2022-09-09T16:08:00Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Opening a new projection */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Initializing a new projection ===&lt;br /&gt;
[[File:Initializing a cost projection.gif|thumb|How to initialize a new cost projection in PM Cost Projections - Click the image to view a larger size]]&lt;br /&gt;
To start a new forecast, open the PM Cost Projections program inside the Project Management module in Viewpoint.  This will open a blank cost projection screen.  Enter the projection date by clicking the calendar button next to the projection date to open a calendar and choose a data, or you can type it manually as MM/DD/YY.  Then enter your project number by hitting F4 and choosing from the project list, or by typing the number in manually.&lt;br /&gt;
&lt;br /&gt;
Once you have entered both a projection data and project number, a dialog window will open with options for how to handle [[Plugged Values]].  Choose the first option (&amp;quot;Never&amp;quot;) and click the Initialize button to populate the cost projection grid.&lt;br /&gt;
&lt;br /&gt;
'''''HINT:''''' ''If you have previously started a forecast and want to pick up where you left off - hit the F4 key while in the Projection Date box to bring up a list of all open cost projections that are associated with you. ''&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=File:Initializing_a_cost_projection.gif&amp;diff=1197</id>
		<title>File:Initializing a cost projection.gif</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=File:Initializing_a_cost_projection.gif&amp;diff=1197"/>
		<updated>2022-09-09T16:06:08Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A step-by-step guide to initializing a new cost projection in the PM Cost Projections module inside Viewpoint&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1189</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1189"/>
		<updated>2022-09-06T20:49:23Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Creating a cost projection */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Opening a new projection ===&lt;br /&gt;
&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1188</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1188"/>
		<updated>2022-09-06T20:47:01Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Before you start */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all cost commitments have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Purchase Orders (POs) represent the last form of cost commitment that needs to be accounted for when preparing for your forecasts.  Ensure that all verbal orders placed with suppliers have been captured with written purchase orders and that these POs have been entered and interfaced in Viewpoint.  &lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontracts, subcontract change orders, and purchase orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
The last step before starting on the project forecast is to create projection codes.  You should complete these step each month prior to starting a new forecast to ensure that any phase codes or cost types opened since the last forecast period have been captured.  For more information on how to create projection codes, see the [[Creating Projection Codes]] article.&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1187</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1187"/>
		<updated>2022-09-06T20:42:15Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Ensure all subcontracts and subcontract change orders have been completed and interfaced */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all subcontracts and subcontract change orders have been completed and interfaced ===&lt;br /&gt;
Subcontracts generally make up 80%+ of the total value of the prime contract with the owner.  For a project forecast or project cost report to be reliable, it is important that subcontract values be constantly up to date in Viewpoint.  Once subcontract terms have been negotiated with the trade contractor, the terms should be formally documented in a subcontract in Viewpoint, issued to the subcontractor for signature, and [[Introduction to Viewpoint|interfaced]] to record the committed costs on the project.  &lt;br /&gt;
&lt;br /&gt;
Similarly, when a subcontractor change order is required - either as the result of an approved change order from the owner, or as a result of an internal change issued to the subcontractor for a change in their scope - it is important that subcontractor change orders be issued promptly and interfaced in Viewpoint.&lt;br /&gt;
&lt;br /&gt;
Keeping up to date with subcontract change orders ensures that cost commitments are accurately captured and reflected in reports, leading to a more informed and accurate project forecast.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all purchase orders have been issued and interfaced ===&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1186</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1186"/>
		<updated>2022-09-06T20:37:48Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Ensure all owner changes have been processed into Viewpoint */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed in Viewpoint ===&lt;br /&gt;
Owner change orders that alter the contract value of the prime contract have an impact on the financial forecast of the project as they change the expected revenue, costs, and fee for the project.  These change orders are only known to the accounting team when they are processed by the project manager, or delegate, for the project and as as result are not included in any financial reporting or calendars.  It is critical that change orders be processed as soon as approval is received, including issuing change orders to subcontractors and purchase orders to vendors.  Remember to [[Introduction to Viewpoint|interface]] approved changes, and cost commitments after they are made so that they reflect on your project reports.&lt;br /&gt;
&lt;br /&gt;
=== Ensure all subcontracts and subcontract change orders have been completed and interfaced === &lt;br /&gt;
=== Ensure all purchase orders have been issued and interfaced ===&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1185</id>
		<title>List of Content</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1185"/>
		<updated>2022-09-06T20:36:51Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Viewpoint Fundamentals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;List of Pages/Categories&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Viewpoint Fundamentals == &lt;br /&gt;
* [[Introduction to Viewpoint]]&lt;br /&gt;
* [[Cost Item vs Cost Code]]&lt;br /&gt;
* [[Viewpoint Quick Reference]]&lt;br /&gt;
* [[Viewpoint Terminology]]&lt;br /&gt;
&lt;br /&gt;
== Project Management Items (what is/how to) ==&lt;br /&gt;
* [[Project Cost and Forecast]]&lt;br /&gt;
* [[Budget Upload]]&lt;br /&gt;
* [[Project Change Management|Project Change Management]]&lt;br /&gt;
* [[Creating Projection Codes]]&lt;br /&gt;
* [[How to Complete a Cost Forecast using PM Cost Projections|Forecasting with PM Cost Projections]]&lt;br /&gt;
* [[Finance Calendar]]&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Sequence Diagram for Typical Processes ==&lt;br /&gt;
* [[Development and Building Permits]]&lt;br /&gt;
* [[Demo Permit Process]]&lt;br /&gt;
* [[How to: Get Utility - Gas]]&lt;br /&gt;
* [[How to: Get Utility - Water]]&lt;br /&gt;
* [[How to: Get Utility - Power]]&lt;br /&gt;
* [[Project Close Out Process]]&lt;br /&gt;
---------------------&lt;br /&gt;
== Estimate 2.0 (Software) ==&lt;br /&gt;
* [[Download Tutorial]]&lt;br /&gt;
* [[Tutorial]]&lt;br /&gt;
* [[General Help Manual]]&lt;br /&gt;
* [[How-to: Quick Guide]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
---------------------&lt;br /&gt;
== TimeLapse ==&lt;br /&gt;
* [[Set-up Tutorial | TimeLapse Set-up Tutorial]]&lt;br /&gt;
&lt;br /&gt;
== Business Technology ==&lt;br /&gt;
* [[Amer page here]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
needs update for new pages and new formatting.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Viewpoint_Quick_Reference&amp;diff=1184</id>
		<title>Viewpoint Quick Reference</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Viewpoint_Quick_Reference&amp;diff=1184"/>
		<updated>2022-09-06T17:21:22Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Cleaned up / reorganized content&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Useful Programs ==&lt;br /&gt;
=== Job Cost ===&lt;br /&gt;
* '''JC Cost Projections''' – Where the PM completes their project forecast&lt;br /&gt;
* '''JC Contracts''' – Contract items + contract item/bill descriptions are created and assigned here. Fee % (during COQ generation) is calculated here. This module receives changed pushed from PM module, this process is called &amp;quot;Interface&amp;quot;.&lt;br /&gt;
* '''JC Change Orders''' – This is where you go to un-interface approved change orders when you mess them up (Tax code, phase code, $ amounts, incorrect subtrade)&lt;br /&gt;
&lt;br /&gt;
=== Subcontract Ledger ===&lt;br /&gt;
* '''SL Compliance''' – Subtrade signed contracts, insurance policies, and WCB documents are uploaded here to allow for accounting to pay the subcontractors &lt;br /&gt;
* '''SL Change Order Entry''' – This is where you go to un-interface subcontract change orders when you mess them up (Tax code, phase code, $ amounts, incorrect subtrade)&lt;br /&gt;
* '''SL Subcontract Entry''' - Not sure when to use this one?&lt;br /&gt;
&lt;br /&gt;
=== Project Management ===&lt;br /&gt;
* '''PM Firms''' – A list of all consultants, clients/owners, vendors, suppliers, subcontractors company wide&lt;br /&gt;
* '''PM Project Firms''' - A list of all consultants, clients/owners, vendors, suppliers, subcontractors specific to each individual project (project directory)&lt;br /&gt;
* '''PM Projects''' – See note above for JC Job Master&lt;br /&gt;
* '''PM Contracts''' – See not above for JC Contract Master&lt;br /&gt;
* '''PM Subcontract Detail''' – Starting point for a subcontract. Phase code, cost type, vendor, SL #, contract amount, holdback %, and tax code are assigned here &lt;br /&gt;
* '''PM Subcontracts''' – Additional detail for subcontracts added here, including scope of work, contract documents, execution date, and subcontract approval. If your subcontract change orders are giving you incorrect values for the subcontract amount, this is the place to check. This section can be used to directly add line items to subcontracts or subcontract revisions, one might find this helpful as it saves other steps.&lt;br /&gt;
* '''PM Issues''' – Mostly useless. A leger of all potential cost impacts/problems with the project&lt;br /&gt;
* '''PM Change Orders''' - Not sure when to use this one?&lt;br /&gt;
* '''PM Subcontract Change Orders''' – Create revisions to subcontractor’s contract amount &lt;br /&gt;
* '''PM Pending Change Orders''' – Create COQs/PCOs for the client. Can be used as a leger for replacing the issues log&lt;br /&gt;
* '''PM Approved Change Orders''' – Where approved COQs/PCOs go and become ACOs &lt;br /&gt;
* '''PM Interface''' – This is the bridge between the project team and accounting. Subcontracts, subcontract change orders, and approved change orders can be interfaced&lt;br /&gt;
* '''PM Submittal Register''' – List of all shop drawings, samples, mock-ups etc.  that are required for the project&lt;br /&gt;
* '''PM Request for Information''' – List of all questions raised by the contractor/subcontractor to the client/consultants&lt;br /&gt;
&lt;br /&gt;
== Useful Reports ==&lt;br /&gt;
=== Accounts Payable === &lt;br /&gt;
* '''AP Job/WO Transaction Drilldown''' – Find each invoice by vendor/subtrade/employee per project &lt;br /&gt;
&lt;br /&gt;
=== Job Cost ===&lt;br /&gt;
* '''JC Original Estimate''' – Shows a breakdown of the initial estimate uploaded to VP&lt;br /&gt;
* '''JC Phase Codes''' – Shows the master code list used for all projects&lt;br /&gt;
* '''JC Jobs''' – Lists important project information such as PM, Super, reviewing consultant/owner, job phase codes, contract items (how is this different from PM Projects?)&lt;br /&gt;
* '''JC Job Phases''' – Shows code list for all projects (How is this different from JC Phase Master?)&lt;br /&gt;
* '''JC Details''' – Not sure exactly what this one is for&lt;br /&gt;
* '''JC Committed Cost Drilldown''' – Breakdown of all committed costs by project phase code&lt;br /&gt;
* '''JC Cost Totals Drilldown''' – Ability to pull backup for each cost recorded under the project&lt;br /&gt;
&lt;br /&gt;
=== Subcontract Ledger ===&lt;br /&gt;
* '''SL Subcontract Status Report''' – A breakdown of a subcontractor’s contract amount, and changes paid to the subcontractor to date &lt;br /&gt;
&lt;br /&gt;
=== Project Management ===&lt;br /&gt;
&lt;br /&gt;
=== Purchase Order === &lt;br /&gt;
* '''PO Drilldown''' – Each individual PO for the specified project is listed in alphabetical order by vendor&lt;br /&gt;
&lt;br /&gt;
== Non Viewpoint Reference ==&lt;br /&gt;
* '''Synergy ACA Form (A-2013)''' – The standard Alberta Construction Association contract template. The template pulls information from PM Subcontract Detail and PM Subcontracts&lt;br /&gt;
* '''Project Cost and Forecast''' and '''Project Cost and Forecast Letter Size''' – The project forecast report at a certain specified time interval&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Finance_Calendar&amp;diff=1183</id>
		<title>Finance Calendar</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Finance_Calendar&amp;diff=1183"/>
		<updated>2022-09-06T16:52:58Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Synergy's accounting functions operate on a regular cadence, with many of the activities following a monthly schedule.  Every year, a finance calendar is created that highlights key dates for starting or completing specific tasks so that accurate financial information is available across the business. &lt;br /&gt;
&lt;br /&gt;
The finance calendar dates are important to both project accountants and project management teams.  Your project accountant can share a copy of the current finance calendar for your reference if you need it. &lt;br /&gt;
&lt;br /&gt;
[[File:Finance Calendar example.png|2022 Synergy Projects Finance Calendar]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Finance_calendar&amp;diff=1182</id>
		<title>Finance calendar</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Finance_calendar&amp;diff=1182"/>
		<updated>2022-09-06T16:52:39Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Redirected page to Finance Calendar&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Finance Calendar]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Finance_Calendar&amp;diff=1181</id>
		<title>Finance Calendar</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Finance_Calendar&amp;diff=1181"/>
		<updated>2022-09-06T16:52:37Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Created page with &amp;quot;Synergy's accounting functions operate on a regular cadence, with many of the activities following a monthly schedule.  Every year, a finance calendar is created that highligh...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Synergy's accounting functions operate on a regular cadence, with many of the activities following a monthly schedule.  Every year, a finance calendar is created that highlights key dates for starting or completing specific tasks so that accurate financial information is available across the business. &lt;br /&gt;
&lt;br /&gt;
The finance calendar dates are important to both project accountants and project management teams.  Your project accountant can share a copy of the current finance calendar for your reference if you need it. &lt;br /&gt;
&lt;br /&gt;
[[File:Finance Calendar example.png|frame|2022 Synergy Projects Finance Calendar]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1180</id>
		<title>List of Content</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1180"/>
		<updated>2022-09-06T16:51:04Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Project Management Items (what is/how to) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;List of Pages/Categories&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Viewpoint Fundamentals == &lt;br /&gt;
* [[Cost Item vs Cost Code]]&lt;br /&gt;
* [[Viewpoint Quick Reference]]&lt;br /&gt;
* [[Viewpoint Terminology]]&lt;br /&gt;
* [[Navigating Viewpoint]]&lt;br /&gt;
&lt;br /&gt;
== Project Management Items (what is/how to) ==&lt;br /&gt;
* [[Project Cost and Forecast]]&lt;br /&gt;
* [[Budget Upload]]&lt;br /&gt;
* [[Project Change Management|Project Change Management]]&lt;br /&gt;
* [[Creating Projection Codes]]&lt;br /&gt;
* [[How to Complete a Cost Forecast using PM Cost Projections|Forecasting with PM Cost Projections]]&lt;br /&gt;
* [[Finance Calendar]]&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Sequence Diagram for Typical Processes ==&lt;br /&gt;
* [[Development and Building Permits]]&lt;br /&gt;
* [[Demo Permit Process]]&lt;br /&gt;
* [[How to: Get Utility - Gas]]&lt;br /&gt;
* [[How to: Get Utility - Water]]&lt;br /&gt;
* [[How to: Get Utility - Power]]&lt;br /&gt;
* [[Project Close Out Process]]&lt;br /&gt;
---------------------&lt;br /&gt;
== Estimate 2.0 (Software) ==&lt;br /&gt;
* [[Download Tutorial]]&lt;br /&gt;
* [[Tutorial]]&lt;br /&gt;
* [[General Help Manual]]&lt;br /&gt;
* [[How-to: Quick Guide]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
---------------------&lt;br /&gt;
== TimeLapse ==&lt;br /&gt;
* [[Set-up Tutorial | TimeLapse Set-up Tutorial]]&lt;br /&gt;
&lt;br /&gt;
== Business Technology ==&lt;br /&gt;
* [[Amer page here]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
needs update for new pages and new formatting.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Finance_calendar&amp;diff=1179</id>
		<title>Finance calendar</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Finance_calendar&amp;diff=1179"/>
		<updated>2022-09-06T16:50:31Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Created Finance Calendar page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Synergy's accounting functions operate on a regular cadence, with many of the activities following a monthly schedule.  Every year, a finance calendar is created that highlights key dates for starting or completing specific tasks so that accurate financial information is available across the business. &lt;br /&gt;
&lt;br /&gt;
The finance calendar dates are important to both project accountants and project management teams.  Your project accountant can share a copy of the current finance calendar for your reference if you need it. &lt;br /&gt;
&lt;br /&gt;
[[File:Finance Calendar example.png|frame|2022 Synergy Projects Finance Calendar]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=File:Finance_Calendar_example.png&amp;diff=1178</id>
		<title>File:Finance Calendar example.png</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=File:Finance_Calendar_example.png&amp;diff=1178"/>
		<updated>2022-09-06T16:48:32Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;An example of the annual finance calendar for Synergy Projects (example year - 2022)&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1177</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1177"/>
		<updated>2022-09-06T16:44:16Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Added content&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
In order to complete an accurate forecast, it is important that the cost inputs are complete and inclusive of all known actual and committed costs incurred by the project on the date of the forecast.&lt;br /&gt;
&lt;br /&gt;
To ensure that the costs recorded in Viewpoint are accurate, it is important to understand and pay attention to accounting cut off dates on the [[finance calendar]] and ensure that payables are reviewed prior to the monthly deadline.  It is also important to stay on top of processing paperwork such as owner change orders, subcontract change orders, and vendor purchase orders as soon as practical as these alter the financial position of the project and will reflect on the final output of your cost forecast.&lt;br /&gt;
&lt;br /&gt;
=== Start forecasting no sooner than PM start date on finance calendar ===&lt;br /&gt;
Synergy Projects publishes a [[finance calendar]] for the year that details all of the important cut-off dates for financial activities within the organization.  Each month a specific date is identified that marks the start of the forecasting period for that month.  Do '''NOT''' start your monthly forecast prior to this date, as this ensures that all accounting functions leading up to forecast (vendor payables, subcontract payables, payroll, etc.) have been completed and batches have been closed.  If you begin your forecast ahead of the start date, you risk not having complete cost information posted to Viewpoint which reduces the accuracy of the forecast. &lt;br /&gt;
&lt;br /&gt;
=== Keep up to date with payable approvals and progress invoices === &lt;br /&gt;
The finance calendar also identifies dates for approving vendor invoice payables, for submitting personal expenses, and for submitting monthly progress claims to owners.  It is critical that these functions remain up to date and that due dates for these activities are enforced.  Respecting the cut-off dates for these activities ensures that the costs and revenues are captured in the correct month leading to forecast accuracy and smooth functioning of the business overall. &lt;br /&gt;
&lt;br /&gt;
=== Ensure all owner changes have been processed into Viewpoint === &lt;br /&gt;
&lt;br /&gt;
=== Ensure all subcontracts and subcontract change orders have been completed and interfaced === &lt;br /&gt;
=== Ensure all purchase orders have been issued and interfaced ===&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1176</id>
		<title>List of Content</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1176"/>
		<updated>2022-09-06T15:58:03Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Project Management Items (what is/how to) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;List of Pages/Categories&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Viewpoint Fundamentals == &lt;br /&gt;
* [[Cost Item vs Cost Code]]&lt;br /&gt;
* [[Viewpoint Quick Reference]]&lt;br /&gt;
* [[Viewpoint Terminology]]&lt;br /&gt;
* [[Navigating Viewpoint]]&lt;br /&gt;
&lt;br /&gt;
== Project Management Items (what is/how to) ==&lt;br /&gt;
* [[Project Cost and Forecast]]&lt;br /&gt;
* [[Budget Upload]]&lt;br /&gt;
* [[Project Change Management|Project Change Management]]&lt;br /&gt;
* [[Creating Projection Codes]]&lt;br /&gt;
* [[How to Complete a Cost Forecast using PM Cost Projections|Forecasting with PM Cost Projections]]&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Sequence Diagram for Typical Processes ==&lt;br /&gt;
* [[Development and Building Permits]]&lt;br /&gt;
* [[Demo Permit Process]]&lt;br /&gt;
* [[How to: Get Utility - Gas]]&lt;br /&gt;
* [[How to: Get Utility - Water]]&lt;br /&gt;
* [[How to: Get Utility - Power]]&lt;br /&gt;
* [[Project Close Out Process]]&lt;br /&gt;
---------------------&lt;br /&gt;
== Estimate 2.0 (Software) ==&lt;br /&gt;
* [[Download Tutorial]]&lt;br /&gt;
* [[Tutorial]]&lt;br /&gt;
* [[General Help Manual]]&lt;br /&gt;
* [[How-to: Quick Guide]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
---------------------&lt;br /&gt;
== TimeLapse ==&lt;br /&gt;
* [[Set-up Tutorial | TimeLapse Set-up Tutorial]]&lt;br /&gt;
&lt;br /&gt;
== Business Technology ==&lt;br /&gt;
* [[Amer page here]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
needs update for new pages and new formatting.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1175</id>
		<title>How to Complete a Cost Forecast using PM Cost Projections</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=How_to_Complete_a_Cost_Forecast_using_PM_Cost_Projections&amp;diff=1175"/>
		<updated>2022-09-06T15:57:32Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Initial page layout.  Content to follow&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Before you start ==&lt;br /&gt;
=== Start forecasting no sooner than PM start date on Financial calendar ===&lt;br /&gt;
=== Keep up to date with payable approvals and due dates === &lt;br /&gt;
=== Ensure all owner changes have been processed into Viewpoint === &lt;br /&gt;
=== Ensure all subcontracts and subcontract change orders have been completed and interfaced === &lt;br /&gt;
=== Ensure all purchase orders have been issued and interfaced ===&lt;br /&gt;
=== Create projection codes ===&lt;br /&gt;
&lt;br /&gt;
== Creating a cost projection ==&lt;br /&gt;
=== Forecasting phase codes in Viewpoint === &lt;br /&gt;
=== Forecast cover page === &lt;br /&gt;
=== Sanity check ===&lt;br /&gt;
=== Submitting your Forecast ===&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1174</id>
		<title>Creating Projection Codes</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1174"/>
		<updated>2022-09-06T15:52:00Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: add line break&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== What are Projection Codes ===&lt;br /&gt;
Viewpoint uses '''Projection Codes''' to assist in completing project forecasts.  Projection codes allow different work elements, phase codes or cost types, to be grouped together into large &amp;quot;bundles&amp;quot; of scope that can be forecast together.  At Synergy, we don't bundle our phases together and our monthly forecasts look at each phase code individually every month.   Nevertheless, we need to create one projection code for each phase code in order for the Cost Projection module to work in Viewpoint.   &lt;br /&gt;
&lt;br /&gt;
=== Creating Projection Codes ===&lt;br /&gt;
Fortunately there is an easy way to quickly create projection codes on your project.&lt;br /&gt;
&lt;br /&gt;
# Open PM Projection Codes &lt;br /&gt;
# Click the &amp;quot;Tasks&amp;quot; menu&lt;br /&gt;
# Choose &amp;quot;Create Projection Codes From Phases&amp;quot;&lt;br /&gt;
# In the pop-up modal, click &amp;quot;Start&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[File:Create Projection Codes.gif|Create projection codes using PM Projection Codes]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you are using the [[How to Complete a Cost Forecast using PM Cost Projections|PM Cost Projections to complete cost forecasts]], you will need to create projection codes prior to completing your first forecast to capture all of the phase codes of your original project budget.  It is often the case that new phase codes will be created during the course of construction for unforeseen items, and owner changes.  Whenever a new phase code is added to the project, a projection code will also need to be added in order to complete future forecasts.  For this reason, it is a good idea to create projection codes as the step at the start of every forecast period.  You can use the same process as above to create projection codes for new phases that did not exist at the last forecast period. &lt;br /&gt;
&lt;br /&gt;
=== How to add a cost type to an existing projection code ===&lt;br /&gt;
If a projection code already exists on your project and a new cost type is added to the phase code associated with the projection code, then an error will arise when you try to create projection codes from phases:&lt;br /&gt;
&lt;br /&gt;
[[File:Projection Codes Error - Cost Type cannot be added.png|Error: Projection Code already exists.  Cost Types cannot be added]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
To resolve this issue, you need to add the new cost type to the existing projection code.  &lt;br /&gt;
&lt;br /&gt;
# From the Grid tab, find the relevant projection code that requires updating and click the row to highlight it&lt;br /&gt;
# Click the icon with a + and three lines next to the Tasks dropdown&lt;br /&gt;
# Choose the unassinged cost type from the &amp;quot;Available Phases&amp;quot; column.  Click to highlight it&lt;br /&gt;
# Click the &amp;quot;Add&amp;quot; button to assign it to the projection code. &lt;br /&gt;
# Click the &amp;quot;Apply&amp;quot; button to svae changes&lt;br /&gt;
# Click the &amp;quot;Close&amp;quot; button to return to PM Projection Codes&lt;br /&gt;
&lt;br /&gt;
'''''Note:'''''  ''If there are multiple lines listed in the &amp;quot;Available Phases&amp;quot; column, repeat the first four steps until the column is empty.''&lt;br /&gt;
&lt;br /&gt;
[[File:Add cost type to existing phase projection code.gif|Add a new cost type to an existing projection code]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1173</id>
		<title>Creating Projection Codes</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Creating_Projection_Codes&amp;diff=1173"/>
		<updated>2022-09-06T15:51:15Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Created page with &amp;quot;=== What are Projection Codes === Viewpoint uses '''Projection Codes''' to assist in completing project forecasts.  Projection codes allow different work elements, phase codes...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;=== What are Projection Codes ===&lt;br /&gt;
Viewpoint uses '''Projection Codes''' to assist in completing project forecasts.  Projection codes allow different work elements, phase codes or cost types, to be grouped together into large &amp;quot;bundles&amp;quot; of scope that can be forecast together.  At Synergy, we don't bundle our phases together and our monthly forecasts look at each phase code individually every month.   Nevertheless, we need to create one projection code for each phase code in order for the Cost Projection module to work in Viewpoint.   &lt;br /&gt;
&lt;br /&gt;
=== Creating Projection Codes ===&lt;br /&gt;
Fortunately there is an easy way to quickly create projection codes on your project.&lt;br /&gt;
&lt;br /&gt;
# Open PM Projection Codes &lt;br /&gt;
# Click the &amp;quot;Tasks&amp;quot; menu&lt;br /&gt;
# Choose &amp;quot;Create Projection Codes From Phases&amp;quot;&lt;br /&gt;
# In the pop-up modal, click &amp;quot;Start&amp;quot;&lt;br /&gt;
&lt;br /&gt;
[[File:Create Projection Codes.gif|Create projection codes using PM Projection Codes]]&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If you are using the [[How to Complete a Cost Forecast using PM Cost Projections|PM Cost Projections to complete cost forecasts]], you will need to create projection codes prior to completing your first forecast to capture all of the phase codes of your original project budget.  It is often the case that new phase codes will be created during the course of construction for unforeseen items, and owner changes.  Whenever a new phase code is added to the project, a projection code will also need to be added in order to complete future forecasts.  For this reason, it is a good idea to create projection codes as the step at the start of every forecast period.  You can use the same process as above to create projection codes for new phases that did not exist at the last forecast period. &lt;br /&gt;
&lt;br /&gt;
=== How to add a cost type to an existing projection code ===&lt;br /&gt;
If a projection code already exists on your project and a new cost type is added to the phase code associated with the projection code, then an error will arise when you try to create projection codes from phases:&lt;br /&gt;
&lt;br /&gt;
[[File:Projection Codes Error - Cost Type cannot be added.png|Error: Projection Code already exists.  Cost Types cannot be added]]&lt;br /&gt;
&lt;br /&gt;
To resolve this issue, you need to add the new cost type to the existing projection code.  &lt;br /&gt;
&lt;br /&gt;
# From the Grid tab, find the relevant projection code that requires updating and click the row to highlight it&lt;br /&gt;
# Click the icon with a + and three lines next to the Tasks dropdown&lt;br /&gt;
# Choose the unassinged cost type from the &amp;quot;Available Phases&amp;quot; column.  Click to highlight it&lt;br /&gt;
# Click the &amp;quot;Add&amp;quot; button to assign it to the projection code. &lt;br /&gt;
# Click the &amp;quot;Apply&amp;quot; button to svae changes&lt;br /&gt;
# Click the &amp;quot;Close&amp;quot; button to return to PM Projection Codes&lt;br /&gt;
&lt;br /&gt;
'''''Note:'''''  ''If there are multiple lines listed in the &amp;quot;Available Phases&amp;quot; column, repeat the first four steps until the column is empty.''&lt;br /&gt;
&lt;br /&gt;
[[File:Add cost type to existing phase projection code.gif|Add a new cost type to an existing projection code]]&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=File:Add_cost_type_to_existing_phase_projection_code.gif&amp;diff=1172</id>
		<title>File:Add cost type to existing phase projection code.gif</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=File:Add_cost_type_to_existing_phase_projection_code.gif&amp;diff=1172"/>
		<updated>2022-09-06T15:50:37Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A step-by-step animated gif showing the steps required to add a new cost type to an existing projection code using the Viewpoint PM Projection Codes module&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=File:Projection_Codes_Error_-_Cost_Type_cannot_be_added.png&amp;diff=1171</id>
		<title>File:Projection Codes Error - Cost Type cannot be added.png</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=File:Projection_Codes_Error_-_Cost_Type_cannot_be_added.png&amp;diff=1171"/>
		<updated>2022-09-06T15:38:42Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Error message that arises in the Viewpoint PM Projection Codes module when you attempt to run Create Projection Codes from Phases on a phase code with a newly opened cost type that already has a projection code associated with it.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=File:Create_Projection_Codes.gif&amp;diff=1170</id>
		<title>File:Create Projection Codes.gif</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=File:Create_Projection_Codes.gif&amp;diff=1170"/>
		<updated>2022-09-06T15:29:53Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Step-by-step animated gif file showing how to create projection codes from phases in Viewpoint's PM Projection Codes module.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1169</id>
		<title>List of Content</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1169"/>
		<updated>2022-09-06T15:23:46Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Project Management Items (what is/how to) */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;List of Pages/Categories&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Viewpoint Fundamentals == &lt;br /&gt;
* [[Cost Item vs Cost Code]]&lt;br /&gt;
* [[Viewpoint Quick Reference]]&lt;br /&gt;
* [[Viewpoint Terminology]]&lt;br /&gt;
* [[Navigating Viewpoint]]&lt;br /&gt;
&lt;br /&gt;
== Project Management Items (what is/how to) ==&lt;br /&gt;
* [[Project Cost and Forecast]]&lt;br /&gt;
* [[Budget Upload]]&lt;br /&gt;
* [[Project Change Management|Project Change Management]]&lt;br /&gt;
* [[Creating Projection Codes]]&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Sequence Diagram for Typical Processes ==&lt;br /&gt;
* [[Development and Building Permits]]&lt;br /&gt;
* [[Demo Permit Process]]&lt;br /&gt;
* [[How to: Get Utility - Gas]]&lt;br /&gt;
* [[How to: Get Utility - Water]]&lt;br /&gt;
* [[How to: Get Utility - Power]]&lt;br /&gt;
* [[Project Close Out Process]]&lt;br /&gt;
---------------------&lt;br /&gt;
== Estimate 2.0 (Software) ==&lt;br /&gt;
* [[Download Tutorial]]&lt;br /&gt;
* [[Tutorial]]&lt;br /&gt;
* [[General Help Manual]]&lt;br /&gt;
* [[How-to: Quick Guide]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
---------------------&lt;br /&gt;
== TimeLapse ==&lt;br /&gt;
* [[Set-up Tutorial | TimeLapse Set-up Tutorial]]&lt;br /&gt;
&lt;br /&gt;
== Business Technology ==&lt;br /&gt;
* [[Amer page here]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
needs update for new pages and new formatting.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1153</id>
		<title>List of Content</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1153"/>
		<updated>2022-08-30T20:40:41Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Viewpoint Fundamentals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;List of Pages/Categories&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Viewpoint Fundamentals == &lt;br /&gt;
* [[Cost Item vs Cost Code]]&lt;br /&gt;
* [[Viewpoint Terminology]]&lt;br /&gt;
* [[Navigating Viewpoint]]&lt;br /&gt;
&lt;br /&gt;
== Project Management Items (what is/how to) ==&lt;br /&gt;
* [[Project Cost and Forecast]]&lt;br /&gt;
* [[Budget Upload]]&lt;br /&gt;
* [[Project Change Management|Project Change Management]]&lt;br /&gt;
* [[Viewpoint Quick Reference]]&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Sequence Diagram for Typical Processes ==&lt;br /&gt;
* [[Development and Building Permits]]&lt;br /&gt;
* [[Demo Permit Process]]&lt;br /&gt;
* [[How to: Get Utility - Gas]]&lt;br /&gt;
* [[How to: Get Utility - Water]]&lt;br /&gt;
* [[How to: Get Utility - Power]]&lt;br /&gt;
* [[Project Close Out Process]]&lt;br /&gt;
---------------------&lt;br /&gt;
== Estimate 2.0 (Software) ==&lt;br /&gt;
* [[Download Tutorial]]&lt;br /&gt;
* [[Tutorial]]&lt;br /&gt;
* [[General Help Manual]]&lt;br /&gt;
* [[How-to: Quick Guide]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
---------------------&lt;br /&gt;
== TimeLapse ==&lt;br /&gt;
* [[Set-up Tutorial | TimeLapse Set-up Tutorial]]&lt;br /&gt;
&lt;br /&gt;
== Business Technology ==&lt;br /&gt;
* [[Amer page here]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
needs update for new pages and new formatting.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=Viewpoint_Terminology&amp;diff=1152</id>
		<title>Viewpoint Terminology</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=Viewpoint_Terminology&amp;diff=1152"/>
		<updated>2022-08-30T20:36:05Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: Definitions of key viewpoint terminology: contracts, contract items, projects, phase codes, cost types, and subcontract items.&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Viewpoint uses certain nomenclature, and concepts throughout the application and it can be helpful to understand each of these items and what they mean.  &lt;br /&gt;
&lt;br /&gt;
The key distinction to understand is that Viewpoint separates Revenue from Costs. &lt;br /&gt;
&lt;br /&gt;
== Revenue Terminology ==&lt;br /&gt;
&lt;br /&gt;
Revenue is money that comes into Synergy from our clients over the course of a project.  Viewpoint primary calls to this side of the equation as '''Contracts''', referring to the prime contract between Synergy and the owner.  &lt;br /&gt;
&lt;br /&gt;
'''Contracts''' are set up in the [[PM Contracts]] module and contain information relating to the prime contract as well as billing information for our progress claims.&lt;br /&gt;
&lt;br /&gt;
'''Contract Items''' are the billing line items that the owner will see on our progress claims.  '''Contract Items''' use and independent scheme from the cost codes we use to track costs on our projects and should be aligned to customer expectations for invoicing purposes&lt;br /&gt;
&lt;br /&gt;
== Cost Terminology ==&lt;br /&gt;
&lt;br /&gt;
Costs are the money that Synergy pays out during the course of construction to our employees, subcontractors, and suppliers.  In Viewpoint, there are four important named concepts: projects (jobs), phases, cost types, and subcontract items.&lt;br /&gt;
&lt;br /&gt;
=== Projects (Jobs) ===&lt;br /&gt;
'''Projects''' are the entirety of the scope required to complete our work on a given project.  A '''Project''' in viewpoint contains basic information about the physical address of the jobsite, change order markups, as well as all of the phases codes and their associated cost types (defined below).  &lt;br /&gt;
&lt;br /&gt;
Viewpoint doesn't use the term ''Project'' consistently, in some places of the software you may find ''Job'' used.  These are interchangeable within Viewpoint and refer to the same thing.&lt;br /&gt;
&lt;br /&gt;
=== Phase Codes ===&lt;br /&gt;
'''Phase Codes''' (sometimes called ''cost codes'' outside of Viewpoint) are the individual elements of work that make up the project.  An example of a '''phase code''' could be rough carpentry, skidsteer rental, or painting.  When costs are incurred on our projects, they are charged to a '''phase code''' either on an employee time card, purchase order, or subcontract.&lt;br /&gt;
&lt;br /&gt;
=== Cost Types ===&lt;br /&gt;
At Synergy, we use three '''Cost Types''' (labour, material, and subcontract) to differentiate different types of costs that can be incurred on a phase code.  '''Cost types''' provide an additional level of detail that can be reported on separately from the base phase code.  Each phase requires at least one cost type to be active, but may have two or all three cost types active, as a project management team, we can select which cost types apply to any given phase code.  For example, the Mechanical phase code may only have the subcontract cost type active, while the superintendent phase code may only have the labour cost type active, and the temporary power code has all three labour, material, and subcontract.&lt;br /&gt;
&lt;br /&gt;
=== Subcontract Items ===&lt;br /&gt;
When issuing subcontracts, it is possible to have multiple items listed on a subcontract to help clearly define the subcontractor's scope.  These are called '''Subcontract Items''', and they provide an added layer of detail when issuing subcontracts.  '''Subcontract Items''' must tie back to a phase code, but do not need to use individual phase code for each subcontract item.  &lt;br /&gt;
&lt;br /&gt;
For example, if we had a mechanical prime contract that included:&lt;br /&gt;
&lt;br /&gt;
* $100,000 for plumbing&lt;br /&gt;
* $80,000 for HVAC&lt;br /&gt;
* $50,000 for sprinklers&lt;br /&gt;
* $30,000 for controls&lt;br /&gt;
* $15,000 for mechanical trenching and backfill&lt;br /&gt;
&lt;br /&gt;
On our project, we wanted to track the first four line items under a mechanical supply and install phase code and the trenching in a separate phase code, we could do the following:&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ ''' Mechanical Subcontract Schedule of Values '''&lt;br /&gt;
|-&lt;br /&gt;
! Subcontract Item !! SI Description !! Amount !! Phase Code !! PC Description&lt;br /&gt;
|- &lt;br /&gt;
| 1 || Plumbing || $100,000 || 220000 || Mechanical&lt;br /&gt;
|- &lt;br /&gt;
| 2 || HVAC || $80,000 || 220000 || Mechanical&lt;br /&gt;
|- &lt;br /&gt;
| 3 || Sprinklers || $50,000 || 220000 || Mechanical&lt;br /&gt;
|- &lt;br /&gt;
| 4 || Controls || $30,000 || 220000 || Mechanical&lt;br /&gt;
|- &lt;br /&gt;
| 5 || Mechanical Trenching || $15,000 || 312400 || Trenching &amp;amp; Backfilling&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
	<entry>
		<id>https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1151</id>
		<title>List of Content</title>
		<link rel="alternate" type="text/html" href="https://thewiki.builtplainly.com/index.php?title=List_of_Content&amp;diff=1151"/>
		<updated>2022-08-30T20:17:01Z</updated>

		<summary type="html">&lt;p&gt;Andrew langstone: /* Viewpoint Fundamentals */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;List of Pages/Categories&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Viewpoint Fundamentals == &lt;br /&gt;
* [[Cost Item vs Cost Code]]&lt;br /&gt;
* [[Viewpoint Terminology]]&lt;br /&gt;
&lt;br /&gt;
== Project Management Items (what is/how to) ==&lt;br /&gt;
* [[Project Cost and Forecast]]&lt;br /&gt;
* [[Budget Upload]]&lt;br /&gt;
* [[Project Change Management|Project Change Management]]&lt;br /&gt;
* [[Viewpoint Quick Reference]]&lt;br /&gt;
---------------------&lt;br /&gt;
&lt;br /&gt;
== Sequence Diagram for Typical Processes ==&lt;br /&gt;
* [[Development and Building Permits]]&lt;br /&gt;
* [[Demo Permit Process]]&lt;br /&gt;
* [[How to: Get Utility - Gas]]&lt;br /&gt;
* [[How to: Get Utility - Water]]&lt;br /&gt;
* [[How to: Get Utility - Power]]&lt;br /&gt;
* [[Project Close Out Process]]&lt;br /&gt;
---------------------&lt;br /&gt;
== Estimate 2.0 (Software) ==&lt;br /&gt;
* [[Download Tutorial]]&lt;br /&gt;
* [[Tutorial]]&lt;br /&gt;
* [[General Help Manual]]&lt;br /&gt;
* [[How-to: Quick Guide]]&lt;br /&gt;
* [[FAQ]]&lt;br /&gt;
---------------------&lt;br /&gt;
== TimeLapse ==&lt;br /&gt;
* [[Set-up Tutorial | TimeLapse Set-up Tutorial]]&lt;br /&gt;
&lt;br /&gt;
== Business Technology ==&lt;br /&gt;
* [[Amer page here]]&lt;br /&gt;
&lt;br /&gt;
---------------------&lt;br /&gt;
needs update for new pages and new formatting.&lt;/div&gt;</summary>
		<author><name>Andrew langstone</name></author>
	</entry>
</feed>