This document discusses strategies for maximizing the value of an Allegro software implementation after go-live. It recommends stabilizing the system and ensuring full adoption by users. It also provides guidance on tools and best practices for ongoing support, innovation, and upgrades. Key aspects include leveraging Allegro support resources, providing detailed issue reports, collaborating on new requirements, and coordinating upgrades according to Allegro's release schedule.

1. Maximizing the Value of Allegro
After Implementation
Vanja Bogdanovic
Services Director, Allegro

2. Contents
Introduc)on
Customer Business
Innova)on
Allegro / Customer
Support Tools
Stabiliza)on
&
Full System
Adop)on
Allegro System
Innova)on
Q & A
Working with
Allegro Support
Allegro Upgrades
Allegro Support
Tasks & Usability
Improvements

3. Introduction

4. • Transition to self-supported Support
• Completion of onboarding all end users
• Adapting to ‘new reality’
• Reality check against real life situations
• Fine tuning internal processes and procedures
• Streamlining the system usage
Stabilization and Full System Adoption

5. • Knowledge Base
• Allegro University (Allegro U)
• Allegro User Group (AUG)
• Allegro Support organization, including access to:
• Services
• Product Management
• R&D
• Allegro Account Management
Allegro Support Tools

6. • Customer Internal issue tracking and management system
• Customer Internal knowledge base
• Customer Internal training and onboarding program
Customer Support Tools

7. • When logging a support request
• Provide as much detail as possible
• Provide as much data as possible
• Provide detailed recreation of steps and analysis
• Use a customer internal issue tracking and management system
• Log steps taken to replicate issue
• Log Allegro CRM number against issue
• Log response from Allegro
• Keep regularly in touch with Allegro Support to maintain the issues
status current
Working with Allegro Support

8. • Performance / Scalability
• Allegro
• Oracle / MS SQL
• OS
• Data archiving
• Class Event method
• Stored Procedure method
• Trigger method
• Automation of recurring tasks
• Valuation / Settlement
• Market data import
• Creation of Reports en mass
Allegro Support Tasks and Usability Improvements

9. • Keep in touch with the Allegro upgrade schedule
• Perform a comprehensive upgrade feasibility analysis
• Enhancements
• Fixes
• Impact on existing Class Events
• Work with Allegro AM/AE/SD to schedule upgrade activities
Allegro Upgrades

10. • Expanding into new markets within the existing business (e.g. new
Power markets)
• Additional system configuration
• More users
• Opening up new business streams (e.g. starting a new gas desk)
• New products
• Additional system configuration
• More users
Customer Business Innovation

11. • Tell us what you need that you currently do not have
• New configuration
• Custom development
• Core code enhancements
• Provide market intelligence
• Where are the markets going
• What are the new regulations
• Team up with Allegro and/or other customers to drive system
innovation via established communication channels
• AUG
• Product Management
• Account Management
Allegro System Innovation (1)

12. Allegro System Innovation (2)
Iden&fy gap
Discuss gap
Log Support &cket
Viable gap?
Review gap / AUG
Cross-reference gaps
Same or
similar gap
exists?
Feedback as to why not
Customer Services / Tech Desk Product Mgmt R&D
Feedback as to why not
Viable gap?
Implementa&o
n?
Log Support &cket
Record new gap
Include in
Roadmap?
Schedule according to
the Allegro release
schedule
Agree schedule with
Customer
Func&onal
Specifica&on
Design Regional
Element
Func&onal / Technical
Specifica&on
Development QA
Deployment Valida&on
START
Technical Specifica&on Development QA
Release
END
Release
No
Yes
Yes
Yes
Yes
Yes
No
No
No
No
No
END
END
Enhancement Request and Delivery Process

13. Q & A