ASt provides a proven implementation methodology to meet your business requirements by involving you in all stages of the process. Our methodology includes solution configuration, project management, and knowledge transfer activities created to ensure the smooth implementation of our IWMS solution. Our process allows for the application of best practices, based on our experience, weighed with your needs to define a solution that meets your defined requirements and goals.

FM:Systems implementation phases are:

Discovery Phase:
  • Part 1: Needs Analysis

    The first step in our implementation methodology is a thorough Needs Analysis session which will establish the expectations, high level business requirements, goals, costs, and schedule for the entire IWMS project.

    Our consultants bring years of IWMS and technology knowledge to your implementation. We will work with key players in your organization to identify project goals and develop an implementation plan and schedule which will provide the roadmap for your IWMS implementation.

  • Part 2: Needs Solution Design

    The second step in our implementation methodology is a more detailed requirements gathering session of the application user interface and material requirements, which will be exposed and leveraged by the end users. Over several remotes sessions, the project team will establish the specific contents of forms and views, including specific fields, which will be reflected in the final configuration. This is an extension of the preliminary requirements gathering session meant to iron out final details of the user experience, and to remove any remaining open issues and ambiguities.

Development Phase
  • Configuration and Solution Variation

    During this phase your solution is established by FM:Systems based on the functional requirements and data sources gathered in the Needs Analysis phase. FM:Systems will create your solution within our virtual environments. Your FM:Systems Project Manager will then schedule a series of rolling presentations, which will be used to validate the solution as it is developed. Each session will focus a specific area of the solution, and the Client will have the opportunity to confirm and comment on specific configurations.

Deployment Phase
  • Part 1: Testing and Training

    The purpose of the testing and training phase is to ensure the proper functionality of the developed and validated solution within your internal infrastructure. If your organization hosts FM:Interact internally the configuration of the hosted environment can impact the functioning of the platform. During this testing period, the completed solution is migrated from the FM:Systems development environment into your test environment, and your organization’s FM:Interact administrator ensures proper functionality by developing and executing a series of test cases against the system.

    At the conclusion of testing, acceptance of the solution is obtained to allow the solution to go into production. To prepare your internal resources for use of FM:Interact, comprehensive training on the modules your organization is utilizing is scheduled to coincide with the beginning of the testing period. This allows FM:Systems to properly train your team and ensure accurate testing and platform use can be properly executed.

  • Part 2: Live Production Server

    This phase consists of deployment of the solution into a production environment. Training of end users by your internal systems administrators and power users begins.

Support Phase
  • Transition to Customer Support

    As an integral part of the implementation, knowledge was transferred to your organization from our consulting organization. As part of the transition to our customer support team, we conduct a formal hand-off of information regarding your solution configuration. This is to ensure that your new solution is moved into everyday activities within your organization while being provided ongoing support. A project wrap up is created to ensure all project activities and responsibilities are ready to be closed. As part of this formal sign off, the day-to-day communications are transferred to the customer support group.