Myanmar Banking System solution providers and examples

Hello friends,

As I am researching on Myanmar Banking System and solutions, anybody knows any references that I can get on the following?

- Existing Myanmar Banking System using IT solutions (in which kind of particular areas)

- Existing Myanmar IT solutions for Banking system (eg. Core Banking System by MIT). any digital solution from other providers that a bank (private/public) can use? So I can include those providers in my documentations.

- any other useful references

Thanks,

Grace

▶ Reply to This

Replies to This Discussion

Permalink Reply by John Moe on January 12, 2012 at 3:40pm

Hi Grace,

Regarding about solution provider, let's discuss more about from hardware point of view which is critical to run core banking software.

I can help you to explain about how to plan, design, operate the solution.

▶ Reply

Permalink Reply by Grace on January 12, 2012 at 3:46pm

Hi John,

Thanks for the reply. Yes. Hardware point of view is essential for Banking System. But for my case, I want to focus on the kind of Digital/Software Solutions that Myanmar Banks are using. But as you are offering the opportunity to discuss on planning, designing, operating the solution, please let me know because I don't have domain knowledge or previous experiences on that area.

Thanks.

▶ Reply

Permalink Reply by John Moe on January 12, 2012 at 5:36pm

Sure, there are many critical components depends on each others.
We called it stack. It consists of hardware like servers, router and switches, for software like operating system, application, databases, middle ware such as fusion, etc.

Attached is sample topology. Depend on the size of the bank. The system will expand into either Centralised and Distributed.

For Centralised model is easier to manage than Distributed model. But it is difficult to scale.

▶ Reply

Permalink Reply by John Moe on January 12, 2012 at 6:10pm

This is very basic high level view and will discuss more about each modules.

▶ Reply

Permalink Reply by Grace on January 13, 2012 at 7:56am

It gave me a general insight. Thanks for sharing the knowledge. Looking forwards to more details on each modules :)

John Moe said:

This is very basic high level view and will discuss more about each modules.

▶ Reply

Permalink Reply by John Moe on January 13, 2012 at 12:30pm

Sure.. all modules are dependent each others and have to work together for reliable Information system.

There are many approaches from High Level towards Detailed levels..
Today in Market, there are many vendors to support for each individual modules..

For Workstations,
1) Dell
2) HP
3) Cisco - thin client - VXI
4) Oracle - thin client - VDI

For Network,
1) Cisco
2) Juniper
3) Huawei

For Web,
1) Apache
2) MS-IIS
3) Oracle- Weblogic

For Application,
1) Java based - Oracle / Sun
2) Dot Net based

For Database,
1) Oracle DB Enterprise version
2) MySQL
3) MS-SQL

Also Every Information System have life cycles.

After analysis the graph.. it will divide based on the colour..

We need to avoid above graph.. i will discuss more.

We should have the graph below..

The most important is exit strategies..

Do you know why exit strategies is important?

None of system can last forever.
some of them can run at least 5 years. some of them can run even longer.
But there will be time, Organisation need to think for new system base on internal and external forces..

Due to Regulator & Compliance.
Due to OpEX cost ( Operation cost too high)
Due to many other reasons.

There are fews parameter you need to think even before you design..
1) Open
2) Scalable
3) Security
4) Reliability

In order to accomodate the change, you need basic 4 parameters is compulsory.
It must meet atleast 4 parameters.
Then your system are safe and ready for Exit Strategies..

Everyone afraid of Change. But Changes are always there.
Current system must not lock and we need to avoid the system that difficult to change.

Even price are different..

Every changes need resources.

▶ Reply

Permalink Reply by Grace on January 13, 2012 at 2:38pm

Yes,I agree that changes are important, yet we are still afraid of that.

I checked the term "exit strategies" on the web. Thanks for that.

Like you said, None of the system can last forever. Totally true, even my web application(just small app) hits Perm Gem Error if the system is too overloaded and lead to system down. I can see how important will it be for the larger system.

Thanks again for sharing.

John Moe said:

Sure.. all modules are dependent each others and have to work together for reliable Information system.

There are many approaches from High Level towards Detailed levels..
Today in Market, there are many vendors to support for each individual modules..

For Workstations,
1) Dell
2) HP
3) Cisco - thin client - VXI
4) Oracle - thin client - VDI

For Network,
1) Cisco
2) Juniper
3) Huawei

For Web,
1) Apache
2) MS-IIS
3) Oracle- Weblogic

For Application,
1) Java based - Oracle / Sun
2) Dot Net based

For Database,
1) Oracle DB Enterprise version
2) MySQL
3) MS-SQL

Also Every Information System have life cycles.

After analysis the graph.. it will divide based on the colour..

We need to avoid above graph.. i will discuss more.

We should have the graph below..

The most important is exit strategies..

Do you know why exit strategies is important?

None of system can last forever.
some of them can run at least 5 years. some of them can run even longer.
But there will be time, Organisation need to think for new system base on internal and external forces..

Due to Regulator & Compliance.
Due to OpEX cost ( Operation cost too high)
Due to many other reasons.

There are fews parameter you need to think even before you design..
1) Open
2) Scalable
3) Security
4) Reliability

In order to accomodate the change, you need basic 4 parameters is compulsory.
It must meet atleast 4 parameters.
Then your system are safe and ready for Exit Strategies..

Everyone afraid of Change. But Changes are always there.
Current system must not lock and we need to avoid the system that difficult to change.

Even price are different..

Every changes need resources.

▶ Reply

Permalink Reply by John Moe on January 15, 2012 at 2:21pm

Great.. you got message that Change is important.
So we need to align at least (always) 4 parameters (open/scalable/secure/reliable).

Let's try to align for Reliable.
The bank need non-stop system to facilitate the users with 24x7x365 up time.
How do you design the system that non-stop?

There is new terms called Virtual System which run Virtually on top of Physical (Hardware).
Industry is moving away from physical. due to scale issue. Let me show you how..

if system is running with one server. if server down, then system up time will get affected.