877 422 7381


"Our passion is for providing greater control, compliance, time-to-market and visibility for complex manufacturers managing product lifecycle execution with accurate instructions, real time data and manufacturing intelligence."


In order to achieve all the benefits of using a commercial out-of-the-box solution from iBASEt, the implementation process needs to be very different than the traditional approach used to build custom solutions. Instead of defining the desired solution and then building it, the solution is already built and needs to be evaluated to fit requirements. The general approach is to first learn of the built-in practices provided by the application and then reevaluate current practices with an open mind. We’re confident you’ll find Solumina solutions to be industry best-practice.

There is a lot of flexibility in how to organize milestones in an implementation project, but the following is a list of typical project tasks which might have some overlap. The duration of the first phase of an implementation project covering the first rollout to production can be as quick as 8-16 weeks if the spirit of using the solution out-of-the-box is maintained and the solution is found to meet the requirements. Extensive migration or customization efforts would add to that timeline.

1. Initial Setup and Plan
2. SME Training
3. Final Plan
4. Configuration
5. Test
6. Deployment


Step One: Initial Setup and Plan

Good Project Management practices should start right away and should remain throughout the project. Project plan milestones should be identified. Team members and responsibilities should be clearly identified. The project plan and goals should be revisited after the To-Be state has been finalized for an initial rollout. Project management practices should include risk mitigation practices including management of scope creep from nice-to-have functionality that is not really required to meet original business goals.

Deliverables from the first step include:
• Project plan with timelines and types of resources required
• Resources identification
• Training schedule

Tight, efficient billing cycles: Time charges are accumulated and billed within a short billing cycle providing short-term feedback of the actual expenses and labor costs.

On site, remote, or in house implementation capabilities: iBASEt has the facilities and the experience to develop and test complete Solumina implementations at our location or your facilities. We have the expertise to import and export database schemas, as well as the tools, discipline, and management mechanisms to implement remotely and export at completion.

Step Two: SME Training

This is a very important step in your implementation and is critical to ensure the team makes informed decisions in later steps. It’s critical to get all stakeholders who are participating in As-Is documentation and To-Be definition trained on the Solumina solution and the different practices and options provided out-of-the-box. It is also important to understand the functionality of the product and the aspects of the product that are configurable to adapt to your unique organizational structure, business processes, integration needs, and different types of manufacturing work centers.

This is not the final training phase. This initial training is focused on the out-of-the-box Solumina solution, versus training during the Deploy step when the configured solution is deployed at the first rollout work centers.

Step Three: Final Plan

At this step the organizations flexibility and willingness to change is tested. Therefore, it is important to always refer back to the original business goals that motivated the project in the first place. Many organizations establish some basic rules and tenants to guide process reengineering meetings. It might help to include team members who have also participated in other types of process improvements initiatives like Lean Manufacturing projects.

A good understanding of the As-Is process is critical to the development of the To-Be process. Participating in the documentation of the As-Is process is usually a real eye opener for those who might not have given much thought before to understanding the effects their operations have on processes downstream of their departments or beyond the walls of their organization.

As-Is documentation should include all information, documentation, verification and filing activity in the operational process. Each of these activities are tested to see if they are truly value-added steps from the point of view of the end-product customer.

To-Be processes are developed with the goal of eliminating wasteful activities by implementing industry best practices enabled with the new Solumina solution. Intermediate To-Be phases can also be defined on the path to an ultimate To-Be state. Each phase should have quantifiable achievements if possible.

Deliverables from this step include:
• As-Is and To-Be documentation
• Updated Project Plan
• Updated Statement of Work for implementation partners

Step Four: Configuration

If you have embraced the out-of-the-box philosophy to this point, the Configure step should be focused on integration – versus – functionality customization. Out-of-the-box integration options from iBASEt can considerably further reduce the effort and time required to implement your solution.

This project step includes:
• Application Configuration
• Application Extensions Development
• Integration Setup
• Data Migration to support Deployment at Pilot Work Centers

Step Five: Test

During this project step test scripts are finalized and executed, and pilot work centers are identified for the rollout plan. It is important to select a pilot work center that exercises the solution functionality and a work center that requires process improvement. If the work centers selected for the pilot do not have a history of issues, then it will be difficult to prove the value of the new solution to the executive management team.

Step Six: Deployment

Assigning a dedicated team to support an implementation’s transition to go-live is very important. Starting with pilot work centers during the initial deployment is best. Some organizations also identify a few employees in each work center as solution champions that will help other employees who require additional support during the learning curve period.

The deployment step includes:
• Setup Production Environment
• Complete Data Migration
• End-User Training
• Rollout Support
• Updated Rollout Plan beyond Pilot Work Centers

There are a variety of modes of transition available: Depending on deployment specifics and company philosophy, iBASEt can recommend and accommodate a suitable deployment modality from a wide range of schemes: big bang, piloted, paper-lite, or paper-parallel. The big bang scheme is a complete and sudden transition to a paperless environment, suitable for green-field sites or enterprise-wide shifts. The paper-parallel scheme is a gradual transition from full paper to a paperless environment.

Our Technical Support department is available to be introduced to the customer environment through active sharing of resources in advance of deployment and after deployment.

Database Administration Assistance Options
We can assist in the administration of the customer’s database as needed, including data conversions and data load troubleshooting.

Documentation and Training Options
If required, iBASEt has the expertise and the tools available to create custom customized documents targeting specific types of users and administrators.

Also, in-house Training Classroom with interactive instruction is available from iBASEt at our completely outfitted interactive training classroom.

New Call-to-action
New Call-to-action