Implementation Process
The iOffice Implementation plan includes seven major steps with each defined in the Implementation Process link below. Each step is a milestone in the implementation of the project and will be mutually defined in the overall project plan.
The initial steps, Pre-Kickoff and Kickoff, are the most critical and will establish the baseline for the project plan. The customer, prior to moving to the next phase, must sign off on each phase or milestone.
The implementation plan is estimated to be 60 to 90 days depending on the overall complexity of the site. Formal implementation plans are developed upon contract execution. The formal process may be found by using the following link:
Note: If you would prefer a PDF of iOffice's Implementation process, click here.
If you would like more information about the assorted user rights (permissions), use the following link:
User Rights By Title (Permissions)
The iOffice Implementation Process is listed below. For your convenience, we have included "Next Steps" at the bottom of each page that allows you to progress step-by-step through the Implementation process. Or if you prefer, you may select any of the steps by using the links below.
Note: If you would prefer a PDF of iOffice's Implementation Process, click here.
Overview
iOFFICE recommends setting up scheduled weekly calls. Representation on the call includes the iOffice Project Manager and Implementation designee’s as well as the customer’s Project Manager and other designees necessary representing Facilities, Administration, IT, Security, etc. iOFFICE will set up a re-occurring webex to support the call.
The Implementation Process includes the following seven steps:
Step One: Pre-Kickoff
-
Designated for the customer Project Sponsor / Manager and the iOffice Implementation Manager to identify team members for the project and review project objectives and desired timeframe for implementation.
-
Each party defines team members and their specific roles and responsibilities during implementation.
-
Expectations for project participation and associated risks for non-compliance are clearly communicated to customer team members.
Step Two: Kickoff
-
All team members (Customer and iOffice) are introduced with their specific roles and responsibilities defined.
-
Project objectives are restated.
-
Initial project objectives are restated.
-
Initial project plan with critical dates and team assignments is presented, reviewed, and approved.
-
Expectations for project participation and associated risks for non-compliance are reviewed.
-
Formal customer sign-off required.
Step Three: Planning
-
Data gathering conducted based on the specific modules to be implemented but typically includes occupant data, asset data, or AutoCAD / Revit drawings.
-
Requirements workshops conducted to clearly define current workflow processes and desired workflow enhancements.
-
Formal customer sign-off required.
Step Four: Design
-
iOffice recommends design configuration based on requirements workshop, customer objectives, and iOffice leading practices.
-
Formal customer sign-off required.
Step Five: Build
-
iOffice configures modules based on approved design recommendation.
-
Customer reviews and validates data and workflow.
-
iOffice updates data and makes configuration adjustments based on customer feedback.
Step Six: Validate
-
iOffice and customer review and test final design.
-
Formal customer sign-off required.
Step Seven: Training
-
iOffice will train the customer administration and operations team on final configuration.
-
Formal customer sign-off required.
Next Steps: Pre-Kickoff
Related Topics