Migrating On-Premise Applications to the Cloud

One of my current projects is to migrate some of our on-site applications to the Cloud. This is a complex process and project that involved technical, strategic and operational considerations.

I will list some steps that were taken as part of the project here as you may find them useful.

Project Scope and Goal

What is your reason for the project, cost reduction, increase in scalability or performance or security improvements?

Assessment:

  • Compile a list of all the on-premise applications.
  • Agree which applications, infrastructure and data will be migrated as part of the project. This information helped identity applications that would fall into the categories listed in the migration strategy section below.
  • Interdependencies between infrastructure and applications need to be clear
  • Consider security, compliance and regulatory factors (data privacy) as some applications may not be suited for the cloud.

Choose the Cloud Provider

We already had the decision on our Cloud provider. I will assume you have also identified your provider, if not contact me and I can provide some information you may find useful.

Migration Strategy:

  • Will your approach be lift & shift (transferring as is), re-platforming, or cloud deployment
  • Will the data need to be adjusted, transformed or cleansed as part of the move
  • How will you migrate. Incremental, real time or bulk transfer
  • How will you ensure data remains secure throughout the process
  • Have clear expectations on phases and timelines.
  • How will you test the applications and validate functionality post migration
  • What is the rollback plan if there are issues

Provision Cloud Systems and Infrastructure

  • Design the architecture, storage, network and security
  • Implement monitoring, logging and troubleshooting tools

Project Team:

  • The team will be made up if IT, any affected or relevant Business areas, Operations and Security
  • Identify all Stakeholders

Training:

  • Identify training requirements for end users and IT operational teams

System Monitoring:

  • Tools for monitoring, performance alerts, security and utilization need to be in place.
  • Operations teams may need to be re-trained.

Communication:

  • All Stakeholders need to have timelines, risks and benefits.
  • They need to be kept informed on progress, challenges and issues.

Cost Review and Management:

  • Keep a close eye on costs, you can right-size resources and manage costs effectively.
  • Cloud Provider tools like Autoscaling will help keep this in check

These are some items to consider if you are plan on moving your services to the Cloud.

How Predictive Analytics is used in Healthcare.

I am currently working on a Predictive Analytics Project so uncovered some facts that you may find useful.

Let me start by explaining what Predictive Analytics is.

It is a field of data analytics that uses sophisticated algorithms, machine learning and artificial intelligence to analyze vast amounts of data to make predictions about trends or future events.

In a healthcare setting since the institutions have access to and can use data from Electronic Health Records (EHR) and Insurance claims, they can use real-time and historical data to forecast future heath trends and patient needs which would help the organization run more efficiently.

So how exactly does Predictive Analytics benefit the institution.

Prediction or Early Detection

The models can analyze patient data, lab results and risk factors which can help to identify individuals at risk of developing specific diseases. Their providers are notified and can intervene with preventative measures.

Personalization

The models can help develop treatment plans specific to the patients needs based on the medical and genetic data.

Resource Planning

Analytics can help the organizations predict and plan for a surge in demand for specific services and develop plans to resource as required allowing for more efficient resource utilization.

Readmission Reduction

By reviewing patterns, it can be used to identify patients more likely to be readmitted. Clinicians can then intervene and implement programs to avoid this happening.

Operational Benefits

It can be used to predict systems failures, allowing the maintenance teams to address issues early.

Seems like a win win for all doesn’t it.

Are you Integrating Systems with Other Institutions…What to Look Out For.

Are you in a position where you need to integrate your systems and infrastructure with other institutions. Have you thought through all the challenges you may encounter and how to prepare yourself and your team for what is to come.

I have listed a few items to consider as these would help you develop your plan and manage the change.

Company Vision:

  • Are there cultural differences between institutions, and if so how can this be bridged as this could lead to resistance or conflict.
  • Are there any regulatory challenges. Are the goals aligned across the institutions.

Managing Stakeholders:

  • Once identified, determine interest and level of influence within their institution.
  • Maintain regular progress updates with all.
  • Identify the executives that are always willing to help address concerns and challenges as they arise.
  • Ensure the right people (decision makers) are on the steering committee.
  • Always keep all stakeholders in the communication loop (based on the communication matrix).
  • Is management buy-in universal or are some still on the fence.
  • Try to keep all stakeholders engaged, especially if there are some that demonstrate resistance to change.

Maintaining Communication:

  • Keeping channels of communication open with all stakeholders can be cumbersome across the institutions but vital for success.
  • The key is to have regular meetings and updates with a centrally accessible document repository.

Technical Challenges:

  • Carry out a full systems assessment documenting overlaps, compatibility and migration challenges.
  • Ensure there is a clear and achievable integration plan.
  • Plan should list all systems, infrastructure, data and their dependencies.
  • Plan should be in phases based on complexity with clearly defined risks from each institution with mitigation strategies.
  • Agree on the validation, migration and testing plan always with security and compliance in mind.
  • Agree on the plan to manage vendors, reviewing and updating contracts if necessary.

Silos of Information:

  • There is often a risk of institutions hoarding information as “information is power”.
  • Silos need to be broken down by promoting the sharing of knowledge and information.

Interpersonal Friction (Politics):

  • Different working styles with conflicting personalities can hinder collaboration.
  • Could the Manager’s struggle for increased visibility and power affect the project.
  • How does ego play out and how will you manage this.
  • Relationships could be more difficult in situations where there are job security concerns post integration.

I have not listed any possible solutions here as it would depend on your circumstances. However I am happy for you to contact me if you would like to discuss or have questions..

How to Build Trust with Remote Team Members

I received a few comments related to my last post about the remote team and decided to do a follow up.

We need to remember that trust is vital to team work especially for effective collaboration and productivity, but we all have to make extra effort when working remotely. Here are a few strategies to consider:

Have multiple communication channels: Emails, instant messaging (Teams), video and voice calls will help compensate for the lack of face to face interaction.

Honest and open communication: Regular communication is essential, share progress, updates and challenges.

Be Responsive and Transparent: If the Manager is open and honest the team will follow suit. Being dependable, responsive and encouraging the team to do the same would help address any feelings of isolation.

Virtual Team Building Activities: Virtual “Water Cooler” moments would help maintain rapport

Lastly be sincere and show that you care. I have had many interactions with Managers where they ask “How are you?” but do not wait for a reply before moving on to the reason they called. Why bother asking then?. This is sad as they don’t seem to realize that people notice and remember.

Scourge of COVID

 

The rising costs of COVID treatment is causing many organizations to consider raising health insurance premiums on their workers that refuse to get vaccinated. Employers are searching for ways to minimize the risk of breakout infections when they reopen offices as the virus continues to spread across cities, hospitals start to run out of beds again and the vaccination rates continue to slow down.

 

Some may see this in a negative light but how is this really different from higher car insurance premiums on careless drivers, increased tax on cigarette and alcohol or sugar products

The cost for COVID treatment varies around the world. FAIR Health in New York USA average it out at $38,221. CNBC report that America’s Health Insurance Plans, a trade group for insurers puts the cost also in that range.

Healthcare Finance, however average out that the cost of hospital care for COVID-19 much higher ranging from $51,000 to $78,000, based on age.

Company Leadership always has to keep their eyes on the bottom-line, regardless of whether it is increased insurance premiums or impact to productivity due to absence. Now they have to consider mandating COVID vaccination which may also cause staff to leave, however they have to decide which side of the double edged blade cuts deeper. Google, Disney, Walmart and McDonalds in US have made it clear that their staff must be vaccinated as has the publishers Bloomsbury over in UK.

I think everyone needs to do what they can to limit the increasing financial damage being caused by COVID so you either take the vaccine or understand that there may be a premium to be paid.

What are some technical differences between Microsoft, AWS and Google Cloud services

Microsoft Azure, Amazon Web Services (AWS), and Google Cloud Platform (GCP) are major cloud computing providers, but there are some technical distinctions between them:

Services Offered:

  • All three providers offer a wide range of cloud services including compute, storage, databases, networking, and analytics.
  • AWS  has an extensive selection with over 200 services, while GCP is well known for its data analytics and machine learning strengths, Azure on the other hand excels in the integration with existing Microsoft products.

Infrastructure:

  • All three providers have global networks of data centers.
  • AWS currently has the most geographically spread data centers, while GCP focuses on high-performance network design for low latency.
  • The three providers have their on variation of virtual machine options, storage solutions, and management tools.

Pricing:

  • They all use a pay-as-you-go model, but pricing structures can differ based on resource usage and instance types.
  • GCP may have a slight edge in upfront costs for some configurations.

 

The best choice for you will clearly depend on your specific needs and priorities. However you can consider factors like.

  • Existing IT environment (balance between Microsoft vs others)
  • Applications you intend to use
  • Importance of data analytics and machine learning
  • Budgetary constraints

This list does not cover all items however I hope you still find this useful.