Outdoor dreamland

Price is often considered the many factor influencing the decision to implement a business brain (Bi) system.

Don’t despair. You can implement Bi on a shoestring budget. However, to do so requires literal, discipline and adherence to a religious doctrine that may be contrary to the guidance of huge (read: expensive) global consulting firms. Following our shoestring religious doctrine will not only make success possible but likely; and at a cost well below typical expectations.

Dreamland

At times every person is willing to tell you what not to do, or to divulge the pitfalls to avoid in your Bi implementation. Experts may even be willing to talk in vague generalities about the things you should do as long as they don’t give away too many “trade secrets.” Here are 10 specific keys to successfully implement your Bi scheme on a shoestring budget:

1 Stick to a Well-Established Methodology

Selecting a vendor that utilizes a clearly defined, repeatable process for ideas amelioration will impact the victorious achievement (or implementation) of the Bi project. The ideas integration or software amelioration vendor you adopt should have a methodology that clearly defines the processes considerable to yield quality, usable software that meets your business needs and goals and is competitively priced.

Continuous improvement should be the mantra of a vendor with a well developed, clearly defined methodology. You can be a wee more sure in a vendor’s commitment to methodology if you see an emphasis on continually improving, cleaning up, clarifying, and solidifying their processes.

Carefully evaluate a possible vendor’s processes and methodology to settle if it is a) repeatable, b) well defined, and c) focused on continual improvement. If you adopt a vendor that has wee or no process or methodology in place you run the risk of paying for it in slipped schedules, cost overruns, scope creep and outright failure – all of which are costly to both your scheme and your career.

2 Clearly Define Requirements Up Front

In his book capability Without Tears, Philip Crosby notes that the cost of rework is the “price of nonconformity (Ponc)” because “it is what administration chooses to pay for not ensuring work is right the first time.” Lofty words from a giant in the capability revolution. In dollars and cents rework typically costs double (or more) the actual price of doing it right the first time. It only makes sense from an intuitive perspective, since you paid to do it wrong, and then pay again (at least once) to do it over. There is an whole business that has sprung up nearby unscrupulous vendors who offer low, fixed price scheme estimates to win your business. These vendors then inundate their buyer with unnecessary change orders at k and k per order, or more. But let’s save that consulation for a later point.

In a well-established methodology (see point 1 above) requirements are a considerable asset to be managed with great care. In fact, “The capability Maturity Model: Guidelines for improving the Software Process” by the Software Engineering establish says, “the purpose of requirements administration is to establish a coarse understanding in the middle of the buyer and the software scheme of the customer’s requirements that will be addressed by the software project.” Quite obviously this also entails setting and maintaining agreed upon requirements for the scheme and clearly defined expectations for all parties involved.

Expect to pay for an first evaluation of your requirements. This is only due diligence and fees paid for a scoping or requirements convention phase should be applied to the cost of the scheme if you and the vendor agree to move forward.

3 Go With a Fixed Price Vendor

We all have budget constraints. We all feel the stress of trying to second guess “time and material” vendors in an exertion to spend what is unmistakably considerable to do the job. We all hope to find that 95th percentile vendor who will be above the board and honest in time and material billing.

You can eliminate a lot of the guess work by going with a fixed price vendor. A fixed price vendor offers you a predictable expenditure, one that can be budgeted ahead of time or that can be planned for well in enlarge with few if any surprises. With a fixed price vendor you also eliminate the adversarial nature of the relationship that may be fostered by the constant vigilance of billing statements and scheme reports that try to prove their worth.

There are, however, a few points of attention to be noted when working with a fixed price vendor. First and foremost, beware the needless change order. The unscrupulous fixed price vendor will agree to a low price to win the work and then will continue to issue change orders that run the price up. Here are a few ways to insulate against this most unprincipled supplier. Offer to engage the vendor for a requirements convention or scheme scoping exertion up front. This provides some things including well established requirements that minimize changes, clearly defined scope to give the vendor an chance to establish a fair price proposal, reduced risk, and time for your team to inspect issues and roadblocks that need more attention on your part.

The second powerful point when working with a fixed price vendor is to find one that can point to specific, successful, similar projects. A similar scheme does not necessarily mean one in the same specific business (or even within the same sector – federal vs. State/local vs. Commercial). It’s important to look for a vendor who has successfully implemented a Bi of comparable or larger size and complexity. Size is typically a measure of the amount of users and queries and volume of data. Things begin to come to be more involved when you think things like global footprint, 24/7 user operation (meaning that there is essentially no down period in which to perform disposition ideas tasks), complexity of the Etl (extract, transform and load) needs, amount of data sources or data feeds, and other factors.

4 Insist On Rack-Grade Hardware

Moore’s Law (named after Gordon Moore, co-founder of Intel) states that the computing power of processors practically doubles annually. Hardware regularly represents a considerable division of expenditures for any Bi project, and the wise use of hardware dollars can be a absorbing decision for any organization. Inspecting Moore’s Law in your decision can simplify your choices. Rely on the high value, low cost of typical rack-grade hardware, and upgrade every 2-3 years to improved machines. Furthermore, the modern amelioration of blade servers allows for many servers to be packaged in a single, inexpensive, rack mountable unit that takes full advantage of scalable architecture (more in point 5), providing for rapid increase and increased business line adoption – building today for tomorrow’s expansion. Server vendors offer blade servers in a range of configurations and price points to match your needs.

A similar axiom to think is Kryder’s Law – named after Mark Kryder, whose observations about the increases in hard disk storehouse are astonishing. Since the amelioration of the disk drive in 1956 storehouse per square inch has soared more than 50 million fold. This has resulted in ever-increasing storehouse capability at ever-decreasing cost, which indicates a clear direction toward low cost storage.

A well known small systems developer was asked by a federal buyer to build a transitional ideas that would only be used until the global vendor could get a convenient ideas built on large, expensive, possession hardware and software. After some years the small vendor’s low cost, high value ideas prolonged to grow and enlarge to service thousands of users using rack grade equipment and other ideas outlined in this article. By the way, the customer’s former plan to build the large costly ideas was scrapped and the small vendor’s “shoestring” ideas became the “official” source for data in its functional domain – a role it continues to fill to this day.

5 Start Small and Scale Out as Needed

Traditionally, projects have purchased large, muscular database servers – TeraData, Oracle or Db2, which is fine if you need that kind of horse power. But to build on a shoestring we have to stick to the rack grade equipment outlined above. The key is scalability – how well a explication to a problem works if the problem increases in scope or scale. If you build a superlative ideas that meets your needs today but a year from now is not able to meet the increased demands, it lacks scalability.

Over time business needs change, challenges get more complex, businesses grow, employees increase in numbers, reporting needs expand, analysis needs intensify, and so on. You must build today with tomorrow in mind. Taking into consideration the use of rack-grade equipment (see point 4 above), a scalable architecture makes more sense than ever. The key to scalability is to focus initially on the area of “greatest pain” and work outward from there. Focus on a small section of your business, a singular line of business, or an area or function that has high reporting or analysis needs. In time you can add other areas of your business or further whole lines of business. This approach allows your first hardware requirements to be smaller, and lets you prove the value of the system. This approach opens the door for gradual increase and expansion of the ideas until it is an enterprise-wide tool valued and used by virtually the whole organization. This modular approach allows for expansion by scaling horizontally, adding further servers to accommodate the further load of integrating other business areas.

An further advantage of this “scale out” approach is that scaling typically produces redundancy. Redundancy equates to a less disruptive migration or transition of users to a new service as you grow and scale the system.

The example cited in point 4 began with a 2-server ideas supporting 200-300 users. The same ideas “scaled out” to a global ideas that now supports 15,000 users worldwide processing 600k ad hoc queries a month – with 85% of all queries answered in 10 seconds or less. The former architecture never had to be redesigned since it was built with scale-out or horizontal increase in mind from the outset. Production scalability a establish highlight from the start eliminated the need for possession “band-aid” fixes. While your first requirements amelioration establish scalability as an uncompromising requirement.

6 adopt a High Value, highlight Rich User Interface

There are two basic categories of Bi user interface toolsets available today: those that are free and those that cost money. Both categories have pros and cons, and each has its own set of features and benefits.

The high end (expensive) tools have a place and I advise them for customers who unmistakably need them and have the budget in place to comprise them in their project.

In a shoestring approach, however, the price tag on most Bi tools is prohibitive. In these instances i advise one of the free or nearly free Bi solutions. Microsoft® bundles their Reporting Services and analysis Services with Sql Server. Sql Server carries the prestige for lacking the vigor considerable to be competing as a “serious” data storehouse product. This is a misconception that is ordinarily proliferate by those who either don’t understand the drive and value of Sql Server or who are in a position to behalf from its competitors. In the example used in old points the global ideas servicing 15,000 users is built on Microsoft® Sql Server.

On the other hand, you may opt to go with a possession explication advanced by your prime vendor. some vendors offer powerful, feature-rich, fully-integrated Olap tools, dashboards, ad hoc reporting, managed reporting and more, specifically designed to withhold large data warehouses and data marts at no further cost to their customers. Simply ask your vendor what they offer – and ensure you check references to validate the value of the tool offered.

There are also exquisite tools out there like The Pentaho Bi scheme that provides enterprise-class reporting, analysis, dashboard, data mining and workflow capabilities that help organizations operate more efficiently and effectively, all from an Open Source project.

In short, there are options for selecting a high-value, feature-rich Bi toolset that won’t break the bank.

7 Focus on ideas improvement from the Outset

Just as you must focus on scalability from the beginning, it’s as important to focus on ideas improvement. ideas improvement means enhancements to carrying out tuning, changes and clarifications to business rules, adoption of technological advancements, etc. This is your chance to take a cue from your vendor. When we discussed methodologies above we mentioned that the best of these emphasizes continual improvement and refinement of processes. You should strive to implement a Bi scheme that does just that: continually improves itself. Things that are important to you today may not be in six months. Queries that your analysts rely on today may be meaningless next year. Techniques like rescue and analyzing historical query statistics help you to understand your data and how your customers need to use it. This knowledge is invaluable in helping you tune your ideas for peak performance. Build farranging internal analysis into your ideas and then establish the processes to use it faithfully to evaluate your customers’ usage of the system.

Tracking and analyzing usage allows you to benchmark and quantify your carrying out improvements, to identify trends and advise enhancements and improvements to your customers and users. Possibly most important, this analysis gives you a great story tell as you sell your newly built capability to more users. Agreeing to a modern Gartner study, of the 50% of Bi initiatives that were deemed a failure the amount one reason was lack of use by its intended audience. Begin now determining how you can avoid becoming part of this statistic by planning to have a finely tuned explication that continues to come to be more considerable to its user base over time. improvement in carrying out and capability increases the amount of users that rely on the solution, improving your system’s possible and perceived value.

8 Leverage Internal Functional Expertise

We cannot say sufficient about leveraging your own internal functional experts. There are many advantages, but the former rewards are cost control, keeping of internal expertise, and maintaining intimate experience with the user community.

The cost savings are obvious: external consultants cost serious money. Other less sure costs comprise paying outsiders to come to be familiar with your processes only to take that knowledge and leverage it against you with your competition (non-disclosure agreements notwithstanding). The proper vendor should minimize impact to your staff. Also, the professional increase chance this offers your team members should motivate them to participate eagerly.

In addition, if you “farm out” the expertise in any given area over the long term you will at last inspect that you’ve lost any organic capability to address that need. It’s a coarse convention in some industries for consultants to gently replace the organic assets and human capital with ageement personnel, with the intent to at last own all of the expertise in that area. This effectively guarantees a persisting wage stream while you – the buyer – have run low on options for regaining that organic expertise. Outsourcing ancillary, non-core and non-critical services and functionality is a great business move – do what you’re unmistakably good at and outsource the rest is a coarse business approach today. However, care should be taken when Inspecting releasing your grasp on those areas that are key to your business or relate a considerable functional domain.

Finally, it is crucial that your internal, organic functional experts contend close experience with the end users. The private or group with the closest experience and interaction with end users will have the many affect with them as well. Should you wholly outsource that functional expertise, you may lose your capability to interact on an considerable level with your former buyer – the users. Never give up your capability to affect your customer.

9 Ensure You Implement the proper Solution

If your business works fine, but just needs the reporting and analysis capability that Bi offers, then why let an costly global consulting firm convince you to re-engineer the basic foundational processes that are key to the success you’ve been enjoying? Many times, a business process re-engineering (Bpr) exertion stems from a advisor recommending a singular stock or ideas that fits technically and functionally but does not fit well within the work flow of the business. Rather than adopt a separate stock or system, an business may be persuaded to change its core business processes so they align with the process flow of the system. In some instances this is a valid approach and ultimately improves the carrying out of the business, addition its productivity and value. However, this is rarely an easy undertaking and involves broad, sweeping, costly changes in the business culture at its core philosophical level. One reason vendors may push for Bpr is that they are paid on a time and materials (T&M) basis. It is in their interest to expand the distance and/or scope of the scheme (see point 3 above).

If your business unmistakably needs a Bpr engagement, then a Bi implementation is not going to settle your issues. If, on the other hand, you need to simplify and improve your operational reporting and analysis, or have data on disparate systems that needs to be presented homogeneously, then you may unmistakably need a Bi solution, not a Bpr effort.

Ensure you’re fixing the real problem and not being sold an costly exertion that will drive up your cost of doing business while not addressing your uncomplicated reporting and analysis needs.

10 Drive Down Price Performance

What are the former factors that affect price performance? There are many technical factors but a small handful hold the most sway. Database systems inherently have built-in aspects such as indexed views, materialized views, partitioning, and clustering that impact their performance. While these and other technical points do greatly impact the carrying out of the ideas and the subsequent cost of that performance, the way in which they are designed and implemented is the former determining factor. The most considerable factor to driving down the price your carrying out is the prime vendor. This may seem sure on the face but probably for the wrong reason. I don’t advocate selecting the vendor who quotes the bottom price, but the vendor who offers the many value.

Let me divulge a short story about Bbq ribs and Southern culture. I’m located near Birmingham, Alabama, and have been told that we have more rib joints per capita than any other Us city (no, I have no data to back this up). One of these rib joints of some renown is Dreamland Barbeque. Dreamland began as a shack by the side of the hasten tracks in rural Tuscaloosa County about an hour west of Birmingham. For years they had a sign that read, “We don’t serve: baked beans, cole slaw, mashed potatoes, potato salad, green beans…” and went on and on naming the things they did not serve. What’s the point? Dreamland served Bbq ribs, period. And did it good than anything else. Since they specialized they were (and still are, by the way) very, very good at it. They became adept at doing it for a uncostly price. If you want ribs, go to Dreamland. They offer a great, value-priced stock and do it very, very well.

If you need a business brain implementation make a list of vendors that meet all of the other qualifications we’ve outlined here for a vendor. Then go straight through your list and look for the one that specializes in business intelligence. Find the “Dreamland Barbeque” of data. Find that vendor that is small sufficient to be agile, large sufficient to be sound, experienced sufficient to deal with the complexity of your implementation, and focused sufficient to learn your data intimately. Pick a vendor that does business brain and does it highly well.

Following these 10 key steps does not guarantee success. Ignoring them, however, will practically unmistakably guarantee failure.

10 Keys to Implementing business intelligence Projects on a Shoestring

See Also : Freedom beach resort Pheromone Interactive PDA GPS compare

Comments are closed.