Jump to content
Dan G

The New "Seamless" Website

Recommended Posts

Okay all you IT guru's, help me understand the process of the migration to a new website. I'll list the steps as I would think it should be done, let me know what I've missed as I'm not an IT person.

Step1. Developed new website offline on a server with database.

Step 2. Bring in small group for website testing online. Seperate from main server.

Step 3. Fix problems.

Step 4. Migrate new website online after weekend starting Sunday night 11:00pm until complete.

What did I miss?

Share this post


Link to post
Share on other sites
1 hour ago, mworkman said:

Okay all you IT guru's, help me understand the process of the migration to a new website. I'll list the steps as I would think it should be done, let me know what I've missed as I'm not an IT person.

Step1. Developed new website offline on a server with database.

Step 2. Bring in small group for website testing online. Seperate from main server.

Step 3. Fix problems.

Step 4. Migrate new website online after weekend starting Sunday night 11:00pm until complete.

What did I miss?

You are right  with  the steps but there are more to it :

1. Decide the migration method (everything on the same time or in groups) if you decide the second method you need to create some  bridging application so it can route you to the right application (new and old) and allow the customer cares to find you in the right DB . Also you need to think about catch-up process  (if you migrate history data first and just migrate the online data during the rollout window)

2. Non functional testing to the new site - will it be handle the required load , how to operate it , security , security etc ...

3. interface testing - test no issues to connect to the external interfaces (for example credit cards) and no handshake  issues.

4. Roll-out testing - test how long all the migration and interfaces pointing process is taking , do try runs, repeat it until your team know what they are doing and you are ngetting it done in the time which the business can agree with. I have the feeling here the RC upgrade process was lacking 

5.Train your CSRs and help desk people with the new site so they will be able to handle the support.

6. Bring more help in the first few weeks post migration to handle the extra load on your call centers as many people will call with issues , check that your current facilities (switchboard, PCs, office space) is enough to support the extra load.

7. Rollback method - decide on your rollback method , practice it , decide when is your no rollback point and most important , do not be afraid to take the call to do rollback.

8. BCP - Business continuity plan - decide how the business will  continue to work , messages on the website for people what to expect , manual operation during the transition period, catch up if needed , etc (actually point 5,6 is part of it) 

9. End user training - create a videos , demo site, FAQ  and other materials to explain the end user how to work with the system , whatever you can to reduce the questions and calls.

 

 

There are much more things that need to be done , but ,well not sure if this is the forum :-)  , usually such projects ct can take many month, mainly if the system is very old.

Things starting to change now with DEVOPS methodology but still tons of work to do.

 

Share this post


Link to post
Share on other sites

As I was on the phone with CR (Casino Royale) booking a Deluxe Drink Package  ($45PP/DAY, not bad IMO)  I asked about the website. I find the CR operators are a bit more open about answering my sometimes bizarre questions(compared to the regular RCCL phone line). In this case, I was told web site things are going to start getting better Monday, but not completely fixed. Of course everything we are hearing on RCCL end should be taken with a grain of salt...as they are trying hard to do damage control, I am sure. Like @Matt said above, give it a day or two. Although I myself am heavily addicted to the casual browsing (and purchasing of cruises) on the website,  I find logging into my "Cruise Countdown Calendar" app almost as satisfying as seeing it on the official website. That seems to be holding off the withdrawals for now. When my cruise does come, I'll be at the port @10:15am with a smile & valid passport.. even if the website doesn't think I exist. #YOLObookitByCalling  *After watching @Matt on Facebook live today, I was excited to hear about the coverage at the upcoming media event Wednesday.

royalExterior.jpg

Ship-size-comparison.jpeg

Share this post


Link to post
Share on other sites

I have a friend that did database work for them a few years ago.  Its a beast.  I'm sure they modeled all they could off line but at some point you need to need to migrate production and sometimes to make significant leaps forward you need to take a hit.  Migrating a database that contains every record for hundreds of thousands of guests and for all things on all ships is no small task and it's constantly changing.  

I'm imagining they are finally migrating off that old, open source database platform and moving to something that can scale.    While these few days are ugly, it will all be worth it in the end and going forward that old baggage won't be holding them back, preventing them from doing all the awesome things they want to do. 

The tech they want to implement can't be done with the old backend systems.  Just wait.  Be patient. 

Share this post


Link to post
Share on other sites
1 hour ago, twangster said:

I have a friend that did database work for them a few years ago.  Its a beast.  I'm sure they modeled all they could off line but at some point you need to need to migrate production and sometimes to make significant leaps forward you need to take a hit.  Migrating a database that contains every record for hundreds of thousands of guests and for all things on all ships is no small task and it's constantly changing.  

I'm imagining they are finally migrating off that old, open source database platform and moving to something that can scale.    While these few days are ugly, it will all be worth it in the end and going forward that old baggage won't be holding them back, preventing them from doing all the awesome things they want to do. 

The tech they want to implement can't be done with the old backend systems.  Just wait.  Be patient. 

I agree with you , we do not know the complexity of the data base and the old system , not how many records and what is the size , I Will give them that .

Yes , it might take 4,5 days , and since it is being done rarely it can also be acceptable , but they could at least send people an email before explaining the system will be under upgrade for the next few days so if anyone want to reserve something he better do it before.

Well even if they planned that it will be only for one day and something happened and now it is 5 days then they could put some message on the site or even send an email .

Lets hope that the issue will be gone soon and we can all enjoy from a new wonderful site that will help us to enjoy the to cruise on our favorite cruise line  

Share this post


Link to post
Share on other sites
3 hours ago, twangster said:

I have a friend that did database work for them a few years ago.  Its a beast.  I'm sure they modeled all they could off line but at some point you need to need to migrate production and sometimes to make significant leaps forward you need to take a hit.  Migrating a database that contains every record for hundreds of thousands of guests and for all things on all ships is no small task and it's constantly changing.  

I'm imagining they are finally migrating off that old, open source database platform and moving to something that can scale.    While these few days are ugly, it will all be worth it in the end and going forward that old baggage won't be holding them back, preventing them from doing all the awesome things they want to do. 

The tech they want to implement can't be done with the old backend systems.  Just wait.  Be patient. 

I totally can allow for the complexity of migrating a database to a new architecture, especially if they were previously using an open-source system and now migrating to a proprietary / commercial / enterprise system. BUT...

As @Traveler noted in his comment, part of any big migration like that also should include having parallel systems in place in production, or even entire redundant data centers, so you can migrate data to the new system / center while the old one stays online. Don't bring the new one online until everything is migrated and tested; if it takes longer than expected, have a process in place to do nightly transfers of new data from the old system to the new so data stays in sync.

But above all else, keep the main system online and don't cut over until it's ready for cut over. For a big job like this, send out an announcement and maybe even plan for full outages that last a day or two.

I realize this isn't a Wall Street financial system that requires five-nines uptime and has service level agreements to uphold. But it's still a system that thousands of travelers need reliable access to every single day when their trip is coming up. This rollout is nothing short of a gigantic bungle on Royal's part, and whoever was responsible for planning it and executing it needs to be disciplined at a minimum, possibly fired for the clear lack of process on display here.

Share this post


Link to post
Share on other sites

I haven't even visited the homepage since I heard about the seamless website.....as I knew It would lead to frustration and aggravation!

 

I am glad I am not cruising soon or trying to book something soon with them, as then I would be "royally" pissed...lol

 

Been a week now or longer since is started?

Share this post


Link to post
Share on other sites
1 hour ago, mworkman said:

Question of the day...When will we know that the New Official Website  is completed?  Has anyone seen what the finished product is supposed to look like? For all we know it could be completed :4_joy:  

 

When will we know? That's easy, you'll know when you can log in. Has anyone seen? Yes and no. It could be completed......maybe, maybe not.

Hope my insightful comments have helped.:3_grin: 

Share this post


Link to post
Share on other sites
Guest toodle68

I have migrated lots of DB's and hundreds of systems/websites.. I have never, never, had production down for several days or removed functionality for a week. Fork the data, build an entire new infrastructure, write and test migration programs.. there is a solution to everything that, no matter how old and complex, does not result in loss of production for days.

I can log in now, but all I can do is make a blind payment or look at my cabin details. The UI sucks too.

 

Share this post


Link to post
Share on other sites

I just asked RCI on facebook if they had a projected end date for the new website, a week , two weeks?  The response that i was given was....None at this time... It would be nice if the IT department would have published a completion timeframe for all its customers.  What was i thinking? 

Share this post


Link to post
Share on other sites
37 minutes ago, toodle68 said:

I have migrated lots of DB's and hundreds of systems/websites.. I have never, never, had production down for several days or removed functionality for a week. Fork the data, build an entire new infrastructure, write and test migration programs.. there is a solution to everything that, no matter how old and complex, does not result in loss of production for days.

I can log in now, but all I can do is make a blind payment or look at my cabin details. The UI sucks too.

 

Agree with Toodle68!  I have migrated DBs at least as complicated as RC's (like NASA's space object DB) and you never simply take down the old.  DB complexity is irrelevant to process & risk mitigation.  In my line of business folks get fired for snafus like this!

Share this post


Link to post
Share on other sites
19 minutes ago, jce2 said:

Agree with Toodle68!  I have migrated DBs at least as complicated as RC's (like NASA's space object DB) and you never simply take down the old.  DB complexity is irrelevant to process & risk mitigation.  In my line of business folks get fired for snafus like this!

Trim the bottom 5% every year. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...