Model Home Process (SOP)

Owned by Sean Connaghan (ITD)
Last updated: Mar 03, 2019
4 min read

The purpose of this page is to answer questions about the model home process.  This will be a living document and will change overtime. 


Standard Operating Procedures


  • What is the process for kicking off a model?
    • There will be a model kick off meeting with (DM,SM and RSS)  At the conclusion of this meeting the RSS should start the process of getting the schedule in the system. 
  • How soon does a schedule need to be in SchedulePro prior to start?
    • For a schedule to be effective, it should be added as soon at all details are confirmed and not expected to change.  For maximum effect this should be done 90 days prior to the start of construction.  
  • Who is going to monitor/enforce it schedule creation?
  • Who is responsible for updating the template with model tasks?
    • All model tasks are required to be in all templates so no action is needed from the RSS. However the default sequence date can be edited. 
  • How is a model loaded into SchedulePro?
    • Division decides to build a model for a given DCLU, they will coordinate with that division's RRS.  That will kick off the process of configuring and executing the SchedulePro Model Home Schedule with Model tasks. This will require the SPEC-ing of a lot and adding an Estimate Settlement Date
  • When are the model tasks added? Who adds them?
    • Model tasks are triggered by the UCS option code XXXXXXXX.  The presence of that option in the nightly feed will populate the schedule with ALL MODEL tasks.  The adding of the option happens when the Sales Manager or RSS communicates that the specific DCLU is a model and added to Atlas.
  • What do we do if we have to purge a schedule prior to start?
    • Purging a schedule will erase ALL date from the schedule.  The expectation is that the person managing the model process RELOAD documents, notes and dates back to the tasks.  
  • Who is going to monitor/enforce it? 
  • How is the PJM going to be notified and involved?
    • Since the models are executed prior to start, the PJM will not be involved.  The PJM should be notified at the pre-construction meeting when options are reviewed and the plan is set.  
  • What do all of the tasks represent? 
    • Please see the section below
  • Who is responsible for their updates?
    • Model tasks have a special flag that only allows RSS's to update.  That means that PJMs will not be able to update these tasks and vice versa.  PJM have the ability to add notes, documents and Issues.  RSS have the same access for NON MODEL tasks.
  • What information should be captured and who should retrieve it?
    • This is still being worked out but the basic function of this process is to give more visibility to all parties involved.
  • How is the Community vendor table (CVT) updated?
    • The CVT is critical for give visibility to our vendors to model tasks.  This needs to happen around the same time as the schedule is loaded.
    • The following needs to be added for this to work.
      • 555 D (Sales center design): 52399  JON D DEUTSER(Quest)
      • 555 F (Furniture): 57301 Bulldog Office Supply
      • 555 K (Model Sales office L/M): 14415 MHI
      • 555 M (Model Decorating):
        • 57871 UBS
        • 14415 MHI
    • Who does it?
      • This is either the CCM or the Production Admin who has access to the CVT (Link to Training) 

Training Guideline

  • How will RSS’ be trained?
    • New RSS's will go to the center for sales excellence or contact Krista Peterson.
  • How will vendors be trained?
    • New vendors will go to SJ and he will provide direction
  • How will the PJMs be trained on the process?
    • During the Pre-construction meeting the RSS will share process with PJM and provide link to support page training. 
  • Who will perform training?
    • No formal training but more of a information sharing.
  • How will it be distributed?
    • Documentation will be available on support site.
  • Who will be POC for training related questions?

Initial Roll-out (Q1 2019)

  • How will this be communicated? And who?
    • SJ Honacki to communicate with RSS's on training dates. This will be done via email. 
  • Who will be involved in the roll-out from a support perspective?
    • SJ Honacki to be the POC with first line questions from users.
  • Who is going to update the CVT?
    • SJ has divisions update UCS.
  • Who is going to be the POC during the Roll-out?
    • SJ Honacki to be the POC with first line questions from users.
  • What is the timeline of events for the roll-out?
    • Roll-out will consist of 4 training session and a monitoring for 30 day.
  • What is the criteria for the roll-out to be over and transition to maintenance?
    • Once all initial users are trained and the system is configured

Maintenance

  • Where are the SOP documents stored? Who maintains them?
    • SOP and training materials will be stored on the SchedulePro Support Site. Beth Hnatio and SJ Honacki will provided content and SchedulePro Support will make changes.
  • How do we inboard new RSS/vendors? Train them?
    • New RSS users will contact Beth Hnatio She will provide links to training site and guidance on process
  • What will the formal model process look like? Do we have a timeline template that will be followed?
    • Model tasks will populate into the schedule based on a default sequence. Users will have the ability to update the templates if they choose but are not required. 
  • Are there any reports that will be used for maintenance? Any for planning?
    • Users wanting task information will pull it from the DART table SchedulePro_ Schedules.  
  • How will intake of requests or bugs be logged? Who will prioritize them?
    • All information will go through SJ and Beth. Tickets will be logged on the User portal and prioritized against current projects and bugs.