Hi Issam,
I've seen quite a few interesting responses to your question and I agree to most of the opinions.
Having handled quite a few E2E BSS migrations (or say transformations), I would love to add a few more steps:
- Understand the need for transformation before you plan out the end-to-end architecture -
The operator/customer already knows (in most cases) the pain-points with their existing systems. Some may have a lot of issues with turn-around-times; others may have problems related to process efficiency or TTM (time-to-market) or some want an upgrade just because their competitors are upgrading and the stakeholders are getting anxious.
As a vendor, you need to hit the sweet spot by tackling their most important problem. E.g. If the issue is time-to-market, you need to ensure efficiencies in all your business process designs.
Almost all operators/customers are skeptical at the start of a transformation - this exercise will actually make them believe that they are on the right track.
2. Understand the vision of the customer -
Whenever an operator undergoes a transformation, there is always a vision attached to it. Unfortunately, these visions just get featured in public articles and stay among the top management and serve as a confidence builder for key stakeholders. There are cases where the operator's IT team is itself unaware of why they are undergoing such a huge change.
Quite evidently, there will be cases where the IT team themselves get distracted from their vision.
Citing a very recent example for an operator where their major pain-point was revenue-assurance and reconciliation. The IT team still kept on sharing requirements with no mention of ways to reconcile revenue. As a trusted vendor, it should be us who should bring them back on track keeping their core mission in mind.
Also, as correctly pointed out by Raman, data migration strategy should be dealt a bit earlier in the project phase than it normally is. Data migration issues are the most common reasons for <g class="gr_ gr_1233 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" id="1233" data-gr-id="1233">delay</g> in any complex project. With the invent of stronger EU GDPR rules (or similar ones in other parts of the world), there should an elaborate strategy for data migration which must include security implementation, data transfer techniques, data retention scheme and data privacy policies.
Keep yourself updated with the latest policies like ASC 606, IFSC 15, etc (these are just examples of recent updates in revenue reconciliation in the US) and its implication on your transformation. Even if it might entail additional cost and time, it might be worthwhile to bring these topics during any phase of the project.
Let me know if you want to know more about this topic.
Cheers!
------------------------------
Shashank Singh
Cerillion Technologies Limited
------------------------------
Original Message:
Sent: Dec 19, 2018 05:21
From: Issam BOUDANE
Subject: B/OSS migration
Dear Community,
I'm involved in a B/OSS migration project as End to End Solution Architect and I need some guidelines and "smart ideas" :) to achieve this mission.
WHat do you think of this steps ?
- Identify the business processes and applications .
- Collect Requirements from different System Users.
- Define Target Business Architecture based on scope/requirements
- Define Roadmap to reach Business Architecture.
- Define an Implementation strategy
Best regards
#TMForumGeneral
------------------------------
Issam BOUDANE
NHB MS
------------------------------