عضویت 
ورود اعضا
راهنمای خرید
Implementing Innate software0 pages
This is how we implement our software for more complex organizations, such as those with a matrix of project and resource managers. The methodology is based on 15 years experience and ensures a rapid and low risk implementation. The amount of Innate assistance required ranges from 4 to10 days for resource pools of less than 100, through to 20 plus days for larger, more complex organizations. Small, timesheet only systems require even less effort. The key steps are: >
nn1 Proof of concept
Prospective clients often wish to examine the software in some detail before making a decision to proceed. However, it is only towards the end of the Pilot phase that the software will be configured appropriately for their requirements. A proof of concept workshop examines how the software can address specific requirements or concerns; its aim is to justify a positive recommendation to proceed. >
nn2 Implementation workshop
This is the starting point for system implementation. It reviews the requirements and scopes the implementation project. Check lists are used to document decisions, software settings and action items. The issues that need to be addressed are. 1. Understanding the business objectives for the system. 2. Documenting the required process steps. 3. Clarifying roles and responsibilities, so that data access permissions can be defined, etc. 4. Identifying data requirements and sources. 5. Defining reporting requirements. 6. Integration with other systems. 7. Identify training requirements. 8. Planning the implementation project. Attendees should include representatives of the key stakeholders, typically, project, program and resource managers, and those who will administer and support the system. >
nn3 Pilot
Prior to roll out we recommend setting up a system in a test environment so that a small group of users can test the system over a limited period. This will: 1. Check that the system set up best matches the requirements, and identify any necessary changes. 2. Identify areas and processes that may need further work, prior to roll out. >
"
