ARIES
8Pages

Enterprise Systems ARIES METHODOLOGY OVERVIEW

ARIES is a methodology for rapidly implementing complex large-scale enterprise software systems, including multifacility, regional, and national systems. Many large-scale IT projects fail for a very simple reason: they take too long. They get mired in complexity and overly bureaucratic processes, costs escalate, and the client loses confidence. Often, the result is that a fraction of the system goes live and is declared a success, but the scope of what is implemented is too limited to provide the intended benefits. Another common cause of failure is that methodologies and schedules are too...

Adaptability. While it is natural to want to change some client processes during the implementation of a new product, extensive client procedure changes are best performed either before or after the implementation — not during it. The key to ARIES is a product that can rapidly adapt to the way the client operates, rather than forcing the client to change. Thereafter, the adaptability allows the system to grow and evolve as the client evolves. Client Executive Involvement. The very definition of an enterprise system implies that it will have a dramatic impact on the enterprise. Without...

APPENDIX I: ARIES IMPLEMENTATION STEPS The steps in an implementation are as follows: 1. The first meeting with the client is used to build a relationship, establish the overall expectations of the client, and identify client resources. This meeting should include the executives who participated in the purchase of the system as well as the key client personnel involved in implementing it. The user adoption campaign is introduced at this point, and a joint team is identified to roll it out. 2. The Country Edition of the product (or another version close to the client’s needs) is shown to the...

APPENDIX II: ARIES MILESTONES The following is an example of a set of milestones for a single-facility ARIES project. (A similar set is used for a multi-facility project.) The iterative and parallel nature of activities means that milestones will not always be completed in a predicted order. 1. Project commencement 2. Major specifications are obtained and agreed upon (with sign-off by the client) 3. System environment is ready, including all IT infrastructure 4. Configuration is completed 5. Reports and dashboards are completed 6. Integration and data migration routines are completed and...

APPENDIX III: ARIES RESPONSIBILITIES OF PARTIES The following chart provides an overview of joint responsibilities in a large-scale implementation for a healthcare client. This may be different for different countries and different clients. InterSystems Responsibility Application Configuration n Configure: Workflows Screen layouts Menus Security groups n Populate most code tables n Create special reports and dashboards, if needed l l l l Data Migration and Integration n Develop migration processes n Perform data migration n Provide interfaces to other applications/systems System Setup n...

Determine client organizational and workflow changes, if any Define and review configuration requirements Specify special reports and dashboards, if needed Create clinic schedules Populate some code tables, working with InterSystems’ staff Arrange with current vendors for: Data migration automated output (flat file) with adequate documentation Interface documentation for all systems with which we must integrate Be available to explain meaning and relationships of transmitted data Provide access to other systems for testing as needed Provide any required 3rd party content, e.g., drug...

InterSystems Corporation World Headquarters One Memorial Drive Cambridge, MA 02142-1356 Tel: +1.617.621.0600 Fax: +1.617.494.1631 InterSystems.com