applications – Page 4 – Cooper Mann Consulting

October 3, 2013

Giving Credit Where Credit Is Due | Accounting and Business Technologies

Giving Credit Where Credit Is Due

or – That was then, but this is now…

It constantly amazes me, seeing the number of conversations, forums, talkbacks, emails, etc. flurrying about the Internet that are focused on finding the way to “win” against Microsoft and Intuit – both companies, in certain circles, being referred to as “big brother”. Well, the 800lb gorillas, anyway.

There are the Linux community members, very appropriately using TCO (total cost of ownership) and security messages to get the attention of the market… you’ve got the Mac devotees who believe that computers can and should have good fashion sense… and then there are the Windows users who use it, but complain nonetheless.

With Intuit, you have a clear market-share leader in SMB accounting. As for the other market segments – it’s anybody’s guess who wins there. It’s arguable.

But what do these two companies have in common? In a word – success.

Let’s face it. Without them, there wouldn’t be a world of computer users representing a potential customer base for new products. Walk with me – let’s talk.

Computers were once quite expensive, unintuitive, and basically unavailable for most businesses. Then PCs emerged, Microsoft hit the market – and Windows opened across the world. (Yes, I realize the timeline here is seriously compressed, and DOS lived for a long time and we liked it). First, businesses broadly became computer users. Then consumers became computer users. Then everyone became a computer user. Granted, the guy at home playing “Flight Simulator” was a driving force in getting the mouse and better graphics into mainstream computing. But let’s remember that accounting and finance was among the first primary applications of general computing technology (the BETTER adding machine).

Changes in the accounting industry were also occurring at this point. Professional accounting practices began to move away from business bookkeeping, being a low-margin and labor intensive task. Intuit hit the market with QuickBooks, marketing based on the concept that “if you can write a check, you can do your own books”. While this was in direct opposition to the professional accountants’ belief that businesses need professional assistance with their accounting, it solved the dilemma of doing the books directly. So, many accounting practices at this point actually became focused on selling and supporting accounting software – looking at the technology as both a means to avoid direct bookkeeping as well as introducing additional revenue-earning services for the practice.

Both Microsoft and Intuit recognized a need in the market, and filled those needs quite nicely. They earned their market share largely based on useability and the concept of empowerment. This is what it took to build the size of market we see today. And let’s face it. They did it very well.

Today’s computer user is more savvy – more aware of the options and choices. But choice often seems like complexity. With Microsoft and Intuit being viewed by many as the defacto standards for small businesses, the choice seemed like it was already made and therefore the complexity of making the right purchasing decision was removed. This is not as true today as it once was.

There are other options available. Will they gain the same levels of adoption that their predecessors did? Doubt it. The concept of “one size fits all” isn’t true any more. People want tools that are specific to their requirements. Businesses want their computing platform and applications to do more for them than simply maintain status quo.

But we must always remember how we got here. Kudos to the big guys who built the market for the rest of us. We should revere these companies, and acknowledge the great thing they did – they created potential customers for all of us. Lots of ’em.

via Accounting and Business Technologies | Joanie Mann: Giving Credit Where Credit Is Due.

September 18, 2013

CIO, CFO, IT and Procuring the Cloud | buildingUp.biz

CIO, CFO, IT and Procuring the Cloud

For as long as there has been high technology use in business, there has been a struggle between the enterprise CFO and CIO for the power to make IT purchase decisions. It isn’t rocket science… the reasons for the challenge are fairly straightforward. The CFO wants to know what the expected return on the investment will be. The CIO, on the other hand, recognizes that there is rarely a straight line to be drawn between IT expenditures and near-term positive business outcomes. Sometimes it takes a while to fully realize the benefits of an IT project… and sometimes it’s necessary to spend the money just to maintain status quo.

While there may be indicators that the CFO’s influence in the enterprise is extending into areas where the CIO traditionally ruled (due – at least in part – to SaaS and the Cloud) there are also indicators that the role of the CIO is evolving rather than losing relevance.

A survey performed in 2011 by Gartner and Financial Executives International revealed a number of interesting results which indicated that the balance of IT procurement power was shifting within the enterprise. 344 senior financial executives were surveyed, and they revealed that:

in 45% of organizations, the CFO makes or leads IT investment strategy
about 75% of surveyed CFOs said they have little confidence in their own IT departments

A CFO.com article on the subject also mentioned a KPMG study from April 2011, in which it was reported that “73% of CFOs identified IT as the greatest risk to finance meeting its objectives”.

With the emergence of “cloud” computing solutions and the plethora of application and service options now available to businesses, some businesses have concluded that “the CFO is better equipped for the cloud world”. The belief is that the CFO is more attuned to the processes of vendor management and contract term and condition negotiations, which are primary areas of focus when looking to obtain outsourced IT and application services. The process of comparing pricing and service level agreements is more of a business process than a technology process, placing it squarely in the realm of the CFO.

The real issue here isn’t a struggle for power and influence; it’s a change in business priorities fueled by changes in technology and service models. IT and the role of the CIO must focus on innovation and improvement of processes and profitability through efficiencies gained with technology, not on defragging hard drives and running software updates. Brocade.com discusses this evolution of roles and focus with enterprise CIOs and CFOs in the release entitled The CIO Is Dead. Long Live the CIO. The Cloud Redefines the Role of the CIO

“ … the CIO role will evolve and policy enforcement, technology evangelism and mediation between business units and their services providers will become the key responsibilities for the CIO by 2020…. And rather than being replaced by the CFO in this shift in IT provisioning, two-thirds of respondents predicted that the roles of COO and CIO will merge as technology continues to become more operationally vital. http://newsroom.brocade.com/press-releases/the-cio-is-dead-long-live-the-cio-the-cloud-rede-nasdaq-brcd-977455

Who understands better than the internal IT department the time-consuming and frustrating nature of maintaining user environments and applications? Who in the organization has the technical understanding, coupled with a direct business understanding, sufficient to explore new ways of approaching various process or workflow problems? I think most business IT managers would agree that addressing issues that have a potential to radically improve the way a business operates is much more challenging and interesting than selecting the right make and model of server.

via CIO, CFO, IT and Procuring the Cloud | buildingUp.biz.

September 16, 2013May 18, 2017

Better QuickBooks Access, Management and Security – QuickBooks Licensing and Hosting Models

Whether hosted in-house or offsite, licensing models for hosting QuickBooks can be very confusing.

driving1-ANIMATION The demand for solutions to address user mobility, better collaboration and improved information security is increasing as connectivity improves and cloud services and threats evolve. Server-based computing models and application hosting are increasingly popular as businesses seek to embrace teleworking and telecommuting models for their entrenched applications and systems, creating a foundation for improved productivity and work/life balancing (or integration). On the technical side, the benefits of centralizing applications and data include improved efficiency in managing, maintaining and securing systems. For many small businesses, this means centralizing the installation and maintenance of core business applications like Intuit QuickBooks Pro, Premier or Enterprise.

Whether it be offsite with a commercial hosting provider or on a co-located server somewhere, or an onsite installation on the in-house server, hosting Intuit QuickBooks licenses can be straightforward or complicated depending on what you are trying to do with them. Because QuickBooks was designed as a standalone single-user application, there are a number of challenges when it comes to preparing it for server-based use. The primary issue is often simply understanding the QuickBooks licensing model, which is not particularly INTUITive (sorry).

Licensing hosted QuickBooks applications comes with two different sets of implementation issues: the technical implementation (the installation and setup) and the logical allocation of licenses to users (the licensing rules).

When it comes to the technical implementation, many an experienced engineer has beaten their head against the wall trying to get QuickBooks to work properly in a workspace or session-based system (e.g., terminal server), all because they expect the product to implement like a “normal” client/server application. While QuickBooks may use the Sybase database manager guts to handle multi-user access to QuickBooks data files (I think it is still Sybase), the architecture required to properly service a networked QuickBooks installation does not necessarily mimic what would be used with, for example, a .NET desktop client application with an MS SQL back-end. First, the QuickBooks data files cannot be remote to the application, meaning that both the client and the database manager (which is actually working as an adjunct to the client) must exist on the local network; it will not work over a WAN connection, which is why so many folks get frustrated when they put their server “in the cloud” and attempt to connect from a local client using a VPN. It just won’t work that way with QuickBooks; it all has to be on the local network – client, server, data… all of it.

It is notable that many businesses use Dropbox and other file sync solutions because they want to be able to get to their data from multiple locations, but the data they’re getting must be “local” to the apps that use it. It doesn’t allow for simultaneous multi-user access, but it can be an effective way to share a file. The caveat is that the file (at least in the case of a QuickBooks file, or Outlook PST file, etc.) should not actually be used from the sync folder. Sync folder should contain copies of data files that users wish to sync or share with other devices. But I digress…

With a server-based implementation of QuickBooks, technicians will install the QuickBooks desktop software on the server, and will determine whether or not that same machine will also handle the company data files. The QuickBooks DB manager is part of the installation of QuickBooks, and the file system and drive where the QB files are to be managed must be recognized as a local drive on the server running the QBDB manager. The overhead used by the database manager isn’t huge, but it can impact the performance of users on the server. For this reason, some techs will decide to implement a separate file server to manage the QB data files, taking that load off the app server.

The QuickBooks software uses the database manager to “host” access to company files. This simply means that a single server with the data on it is providing managed access to QuickBooks application users.
When QuickBooks application software and data is installed and centrally managed on a server (instead of QuickBooks being installed on individual PCs), that means QuickBooks application is being “hosted” on that server.
When a 3rd party provider supplies the server, the QuickBooks installation, data storage, and your way of connecting to it all, that provider is a “host” providing hosting services for your QuickBooks.

In a dedicated hosting environment, the data is often stored on the same server as the applications, whereas in a shared hosting environment, the data is often stored on central file servers which serve multiple customers. This is why, in some shared hosting situations, one bad data file can take down the database manager services for all the customers using that same file server.

Users open the QuickBooks application on the server instead of having the application installed on individual PCs. The single server-based installation of the software is able to be used concurrently by all users logging in to that computer. With the database manager running, the file is essentially “hosted” on that machine, and the file may then be opened in multi-user mode. OK so far. The problem generally comes about when a second user on the same computer/server wants to open the same QB data file as the first user.

Because the QB database manager is looking at the license of the client application accessing the data file, it will recognize when two different users/sessions with the same license key attempt to open the company data file. If that license key is a single-user key, then the database manager knows it should allow only 1 concurrent user in the file. QuickBooks doesn’t get installed for each user on a computer or server; it is installed one time on the machine and each user on that machine runs from that single shared installation. Any particular version of the QuickBooks application may be installed only once on a single computer, but it is possible to install multiple editions, year versions, and “flavors” of QuickBooks on a single machine (cannot be more than one installation of each unique product). There will be more than a few annoyances when running a variety of QBs on the same computer, but it is technically possible.

In order to allow multiple users to simultaneously access the same data file from a central installation of QuickBooks, the license key installed on the computer must be a multi-user key. QuickBooks Pro, for example, can be keyed to 3 concurrent users, meaning that the license will allow up to 3 users with that same license key to simultaneously access the same company file. Technically (but not lawfully) this installation of QuickBooks on the machine could allow a virtually unlimited number of users to launch the QuickBooks application simultaneously, limited only by machine resources. This is where the logical allocation of licensing comes in.. the rule of licensing QuickBooks.

The logical allocation of unique licenses for each QuickBooks user is a little easier to understand than the technical implementation. The rule is simply that each user of QuickBooks is required to have a valid registered/activated license. That valid license is a license purchased and activated for that business.

total-business Making QuickBooks desktop editions more useful by adding secure remote access and centralized management makes a lot of sense. For companies who rely on the functionality and features of the desktop products (QuickBooks Pro, Premier and Enterprise), a hosted approach is the only way to really address mobility and multi-location requirements. Remember that hosting doesn’t necessarily mean offsite, although that could make sense for the business, too.

Centrally-managing QuickBooks applications and data creates greater efficiency and improves overall IT management capability for the business. At the same time, a centralized model introduces a better strategy for mobilizing the workforce and connecting remote users and offices. The struggles of understanding and implementing proper QuickBooks licensing begin to seem very small when compared to the benefits of deploying a centralized system that’s easier to access, manage and secure.