Tag: IT assessment

  • Migrating And Upgrading Systems

    Migrating And Upgrading Systems

    One of the challenges of software solutions is that, sooner or later, you end up migrating and upgrading systems. The two activities may seem separate, but often, you must do both. A good solution provides an easy path, whether to a new version of the solution or one created by another vendor. However, there are often some expectations on the part of the customer for smooth upgrades. That includes limited customizations and timely updates. It is unrealistic to expect a vendor to build a product you can easily migrate off of ten or more years in the future. Technology changes too quickly.

    Migrating And Upgrading Systems Are The Same

    The difference between a migration and an upgrade is in expectations more than reality. An upgrade almost always requires some amount of migration. That is due to modern systems working with and storing so much data. A smooth upgrade will provide a migration path that is invisible to the administrators and users. Unfortunately, that is often challenging to accomplish. At times, new features and even performance improvements or tuning can require substantial architectural changes.

    Your phone applications and the simpler forms of desktop applications tend to stick with solving less complex problems. That allows for a less complicated solution and easier upgrades. On the other hand, Software As A Service (SAAS) solutions are often very complex, and even the abstracted SAAS approach can require a migration or upgrade that impacts users. In particular, you will run into this when the solution integrates with other systems or allows for imports and exports of data.

    Architecture Is Critical

    One way that software is like a building is that the foundation is an essential part of how it handles the passage of time. Software architecture gives us a foundation we can assess to help determine how easy (or difficult) migrating and upgrading will be. It is a facet that often requires a highly technical eye to evaluate it. On the other hand, some intelligent questions can often quickly unearth architectural weaknesses. Think of them as ways to take it for a test drive. The bonus for us is that the requirements we want from an assessment are also a way to examine an upgrade.

    Questions To Answer For Your Solution

    The following list provides some questions to ask about a solution you are considering and the ones you need to answer for a successful migration or upgrade.

    • How do we back up our data and settings for the system?
    •  Can users and their environments be transferred/maintained?
    •  What integrations will require an update or reset? (Do I need to find that old user ID and password?)
    •  How are the users handled during a migration? (Training? Online Help?)
    •  Can a migration be done in steps or all at once?
    •  Can the migration be done in parallel with the old system?
    •  What happens to historical/past transaction data?
    •  How hard or easy is it to “swap out” the platform? (Operating System, Database, Core Frameworks)

    These questions are an essential part of planning for any form of migration or upgrade. Thus, they are also an excellent way to assess a product before performing one of those actions. It is hard to think about future upgrades during the selection process. However, that is the best time to educate yourself on the effort you will need when that day comes.

    Next Steps

    If the questions above have you stumped, then now is the time for you to get answers. Migrating and upgrading systems is one of those tasks where you are better off forewarned than finding out amid the activity where the risks are. You can avoid critical issues with some planning and adjustments. If nothing else, you can plan for the worst and minimize the costs and risks of a troublesome upgrade.

    About RB Consulting

    Please schedule a time to discuss your next project with us and see if we are your perfect partner. We take these relationships seriously and are happy to point you in the right direction if we are not a good fit. Years of being on both sides of these relationships have taught us a lot. That initial call is free, and there are no obligations. You have nothing to lose. 

    Our experience has taught us a lot about the pitfalls and challenges of custom software. Likewise, we have an e-book that can help you explore all the steps in building software, including a few templates. However, we ask that you share an e-mail address so we can send you a copy. We will add you to our monthly newsletter, but you can unsubscribe anytime. Your data is not shared with anyone else. Learn more about our book here.

  • Native Mobile vs. Mobile-Friendly

    Native Mobile vs. Mobile-Friendly

    Mobile devices are becoming more popular every day.  Thus, it is more important to have a mobile strategy.  If you are delivering a service or product via the Internet, then you need to decide whether to go the native approach deliver a mobile-friendly solution.

    What’s The Difference?

    The first thing to clarify is the difference between a native and mobile-friendly approach.  A native mobile application is installed on the device.  It runs on the mobile device and potentially has access to everything on the device.  This access includes storage, cameras, and sound.  Since the application is on the device, it can run without an Internet connection.

    A mobile friendly solution is a website that works fine with mobile devices.  The application is run in a browser and requires an Internet connection, but otherwise, can look and feel like any other application on the device.

    Why Native?

    Native applications can be advertised and marketed through vendor stores.  This is the Apple App Store and Google Play for some devices.  Thus, getting your solution on the right stores can quickly expose it to millions of potential users.

    A native solution does not need to be connected, so it potentially has a greater use.  Unless a user is in a situation where they always have robust and reliable Internet access, there will be times the application lags or is unavailable.  Native solves that problem and can even sync back up to the Internet when needed.  Think about a painter that goes to provide estimates.  They want to be able to enter data for a job even when there is no connectivity available.

    Native applications also have deeper access to the device.  Thus, they are much more capable of utilizing the screen, camera, and other features.  This includes other applications.  Thus, a native app can take a picture and email it from your email app to someone on your contact list.

    Why Mobile-Friendly?

    To be honest, most of the mobile-friendly arguments center around cost and resources.  A mobile-friendly solution is built for the web and mobile standards.  This means that when Apple or Samsung release a new device the app will still work on them.  There is no need to spend time coding a solution for every device (or family of devices) out there.

    Although the application stores are an excellent way to market a solution, they can be time-consuming to use.  There are also restrictions on application certification for updates after the application is released.  This can put more pressure on developers and testing to be as feature complete as possible for each release.  Thus, it takes longer to get your solution in front of your customers.

    Native applications typically cost more to develop.  There are tools to help target multiple devices with a single codebase, but there are still implementation and testing considerations that make native development more expensive.  This also includes creating the app in a way that it will get accepted into a store.

    A single method of delivery (the web) makes it easier to provide a consistent experience for all users.  Whenever a user goes to the site, they will have all the functionality and not have to worry whether the mobile solution has the same features as the web.

    Which One Should I Choose?

    In general, there is no clear winner with either of these options.  The best path to take requires several considerations.

    • Do my customers need the application even without the Internet?
    • Do my clients have mobile devices or typically use a browser?
    • Can I need to support one (or a small number) device or will many brands need to be addressed?
    • Is time to market a critical factor?
    • Is this an application that app stores will automatically reject?
    • What resources and budget do I have available?
    • Is native a goal I can work towards rather than hit it in version 1.0?
    • What are the key features/functions of the solution?
    • Are the essential functions possible with a web solution?

    These are just a few of the questions and decisions that go into a mobile strategy.  The import of mobile has grown to the point that it is a sound investment to consult with professionals.  The best experts to ask may already be in your company IT department, or there are a lot of good providers available within a wide range of budgets.

    Delivering a mobile solution is big business.  It is also a big decision.  Therefore, it is worth your time and resources to plan out a strategy.  The old days of “lets build a mobile app” as a strategy are long gone.  Set your mobile strategy and move into the future with confidence.

  • IT Assessments Defined

    IT Assessments Defined

    We mention IT assessments as part of the work we do at RB Consulting.  Unfortunately, this is a new concept to some people.  Thus, it may help to look at what one is, and why anyone would want one performed.  A good start is to think about an accounting

    A good start is to think about an accounting audit or similar assessment process.  A financial audit is done to help you get a picture of your financial state on paper and in reality.  An IT assessment is similar; it helps you get a view of the state of your IT situation on paper and in reality.

    The evaluation of IT strategy and implementation is becoming more common as IT has grown to be more critical to the success of companies in any industry.  We now have the quick answer to the question of why one would want to do an IT assessment.  IT is a critical factor in the success of a company so knowing whether IT is a strength or weakness is an essential piece of proper management and decision making.

    (more…)