Laserfiche WebLink
Change Identified and Documented : A Change is usually initiated via the Change Order . When <br /> a request is deemed to be a change , the Project Manager enters this change process . <br /> Change Owner Assigned : Through project meeting discussions , a single Change Owner is <br /> identified ( normally a Project Manager) . This person speaks to the change , ensures it is analyzed <br /> by the appropriate team members and works through any approval processes to determine final <br /> disposition . <br /> Change Logged : An Access database will be established to control/log changes . The Project <br /> Manager logs a new change into the database where the change is given a control number . <br /> Included in this document is a copy of the Change form showing the information collected . <br /> Change Communicated to Impacted Team Members : The Project Manager will ensure that <br /> each new Change is communicated ( electronically where possible ) to all impacted team <br /> members . The Change Owner will determine who these people are . <br /> Change Impact Assessed and Documented : Each Project Manager is responsible for analysis <br /> of any change that may impact their project deliverables . Impact is documented in the Change <br /> database . <br /> Project Schedule Impacted : If the change impacts the Project Schedule , the Change must <br /> receive Arvada approval . <br /> Project Costs Impacted : If the Change impacts project costs , the change must receive Arvada <br /> approval . <br /> No Cost/Schedule Impact : If the change does not result in any revisions to either costs or <br /> schedules , the change will be implemented as per the next step . <br /> Schedule and Implement Change : If all necessary approvals are received (or none were <br /> required ) , the change is scheduled and implemented . If the project schedule is impacted , a new <br /> revised project schedule is created . <br /> Change Deferred/Cancelled : If the change is not approved , the reasons are to be documented <br /> and it will be cancelled or deferred until after the project is completed . <br /> Regular Status Update : Project Managers must be provided with any new information related to <br /> Change Status so that the database is kept current and the Change Summary form reflects <br /> current information . Project Managers will create a Change Summary report on request only . <br /> Regular Status Review : Review of the ongoing status of changes is a mandatory item on each <br /> project management meeting agenda . <br /> 63 <br />