Data, data everywhere... As with the Samuel Taylor Coleridge poem " Water, water everywhere ..." these lines describe situations where we sometimes find ourselves, like becalmed sailors surrounded by water but unable to drink a drop. Business owners might find themselves in a place where they are unable to move forward, even though surrounded by a sea of Data. The powerless feeling of not being able to take advantage of the business-nourishing "Information" Data can provide is real for far too many businesses. Data to Information Business Intelligence (BI) is like a desalination plant for Data, making the Data readily usable by your business. Just like drinking salt water at sea can make a desperate sailor hallucinate, and even die, Data run amok  and consumed incorrectly or out of context can produce similar effects in business. Now that we are aware of the importance of BI in Businesses, Large and Small, I will run through a few quick supporting scenario...

Business Intelligence is necessary for small business, and doesn’t need to be confusing. When I started my career in Business Intelligence, only big companies with big IT budgets and large IT departments dared an implementation. Nearly twenty years later, lots of technological changes and advancements have transpired. Everyone knows about these changes, they’re relatively obvious; from low cost high power computers to mobilization, to social media and more... tech is broad reaching and prolific. Much like the realization of the mid 1990’s that a business must be on the web, to be taken seriously and compete, the same realization is being made by small businesses with respect to Business Intelligence. Although technology and marketing has made it possible for small business to seriously consider a Business Intelligence solution, the sheer number of options and confusing buzzwords and claims can confound even the most tech-savvy CEO or CFO. I have witnessed more misdirected, m...

Passing Parameters to a Scripted DataSet;or any DataSet for that matter The first time I heard the phrase "parameter binding to a data set" cold chills shot down my spine. I was thrust right back into my first OO Programming Class, where concepts like "pointers", "polymorphism" and others were thrown around like we were all just born to understand these abstract descriptions. Why not call it something simpler... like Parameter "place-holder" or "access point" ? Using the word "parameter binding" just makes it sound more complicated than it has to be. ...Maybe that's the idea? We are talking about nerdy techie types after all. That said, I will try to make sure I don't needlessly try to impress with my cryptic verbage. So, here it goes. If you are both new to BIRT and have to use a scripted source the way IBM’s Maximo implementations do, you might not know where to begin right off the bat. I will break it down into sm...

The Better Pathway to a Successful Business Intelligence Implementation. Like Raw Chicken, Raw Data is NOT usually good for you: More and more companies are jumping on the Big Data, Data Analytics, Data Mining, Data Science, Data-Driven bandwagon(s). Nothing like stating the obvious, but I made reference to the first five "Data" buzzwords I hear throughout the course of any given day. Why only five? After all, there are plenty more "Data" buzzwords out there... and lets not forget "Analytics"!    The point is, that it's no secret that businesses recognize what they need to stay in business; Data! Actually it is my belief that data in an unto itself is not inherently good. Consuming raw data, much like consuming raw chicken is not all that good for you. In fact trying to consume it raw is likely to produce sick behavior at best and could lead to the death of your business.  Business Intelligence is a mind-set: As companies go, I hav...

How to create a Histogram with BIRT You'll find my example and post on the Actuate Developer Forum .

Working while traveling?   So, I've been referring to myself as a sort of Digital Gypsy for a few years now. Until this past year, this was not a completely accurate statement. I had a condo, home base, paid property taxes; what ever would constitute as "normal everyday American" typical living. Enter, moving onto the sailboat and just leaving the rented condo behind for someone else to worry about, and taking off! So how do you maintain enough stability, without loosing freedom? To maintain a place to receive paychecks, paper correspondence, and simply ensure that you have the things necessary to provide a prospective client that you're not a vagabond, get a mail service. We use St. Brendan's Isle mail service (http://sbimailservice.com) another service if you'd like to comparison shop, is Mail Forwarding Services in Oregon (http://www.mailforwardingservices.com). Having these services even if you have a permanent home address is wonderful for anyone wh...

Never Confuse Selling with Implementing I just heard these words said for the second time in as many weeks.I've recently been involved in my first sales / POC engagement, and it was an eye opener. I think we all have some responsibility to "sell" our product, skills, ideas, etc... No matter if we're the technical help, or the sales professionals. The issue as I've seen it comes in when a techical person is asked to perform in a sales capacity. Sales by nature, doesn't seem to focus on the technical aspect of anything outside the "FAB" talk. "FAB" "Features, Advantage, and Benefit" are usually decided upon by marketing and the talking points are well established. This is why it is probably a little easier to "Sell" an idea or product this way. As a technical resource, the only selling and marketing information we are privy too or care to study are the standard set of specs. Then we're off to try and figure the "t...

So you've been on a project for three weeks, and it becomes apparent that things are not going well. What should you do? As an implementation specialist, developer, or integrator do you have any more responsibility than to "just do your job"? Though some if not most projects are full of political motives and egos. Trying to point out flaws is almost never met with a welcoming attitude. You have perhaps a very few set of options, but options none the less; so, what are you to do? Plug along, and let the project manager blame you for being slow or ill prepared. This option does nothing for anyone involved, you look bad, your project manager is stressed, and the client is loosing faith all the way around. Point a finger, and highlight the flaws in the plan. This option will surely make your project manager defensive at best and down-right hostile at worst. In either case the client might get what they want, but depending on how highlight the flaws you might alienate your PM....

So you're going to upgrade your Actuate iServer implementation. After you read this, you might consider moving to the 'Cloud' with your deployment. Then again, it really isn't to difficult to do but you'll need to know how to apply version specific jar files and recompile. On the topic of moving your reporting enterprize to the 'Cloud' check this article, where Actuate's CEO talks about being architected to 'move from the warehouse to the cloud'. http://www.v3.co.uk/v3/news/2273651/actuate-birt-open-source Now the secret to upgrading the iServer RSSE... Really it is a matter of first simply extracting your iServer installation and deploying the iServer. Then you will have a folder named /acrsse/. Here you'll find a few example Security Extensions. Pick the one that you have implemented for your custom RSSE, then pull all the bin/jars out and use those in your RSSE project. Compiling against those, and changing the version number in your conf...

If I've been asked once I've been asked a thousand times; "how long will it take to create / convert / build / etc... ?" So, how do you answer this question? For example each report request is like a custom implementation of a one-off design. Sure, a report request is rather limited by what a user is asking for. Sometimes it is a request that the user wants some information based on how some other information is reported. For example; "I'd like a report that looks like the Marketing and Sales Report, telling me how many inquiries my reps are answering per hour.? Sounds simple enough; basically locate the source of the data, do some simple math and use the template (or the Marketing and Sales Report as a template) to build the report. Ultimately you'll be asked "so, when do you think I'll have it?" What they want to hear is probably expressed in minutes or hours. And some tools and frameworks can make this happen ( BIRT Report Studio ) but yo...

So, I'm logging out to catch a flight. Code freeze is tomorrow, and code release is scheduled for next week. Why then, do some users wait until NOW to tell me about corrections and tweaks to reports? -- (...yes, a couple... even I am not perfect!) -- My answer; they just don't care until they're reminded of the code freeze and impending release. Procrastination at its finest! It's a good thing I am using something as flexible and easy to modify as the BIRT Reporting Application. Changing things like column header names, some data type formatting, even script logic on various report elements is not a big deal (most of the time). This reminds me, that it is always a good thing to take the responsibility as a developer, to create a 'sign-off' check list. Trouble is, I HATE lists! But worse than that, I REALLY HATE being late to the Airport! I think I'll create a check-list and post it here (later)... why not procrastinate? everyone else does!

In Canada again! Longterm assignments are good, but they do have their drawbacks. First and possibly the biggest drawback is the "boredom factor". Secondly, it seems to me (possibly related to boredom factor), they longer I go, the longer the weeks seem to get. Now that I have gotten that off my chest, this is not a bad assignment at all. I most certainly have had worse. The best assignments are usually a blend of three things; 1-Location, 2-interesting / cool people, and 3-technology of interest. There is nothing worse than being on an assignment where you can't stand the location, if for no other reason than the office is just plain crappy. But, even in a nice location, with very cool geographic and environmental surroundings if the people suck, the job sucks. And finally if the first two items on the list are okay, I can live with the technology being boring or sucky... at least for a little while.

Often I find myself struggling with "where to start" issues. The simple answer is: 1- my own experiences 2- JFGI 3- groups and forums The problem is that my experiences are extreemly difficult to sort out as I am becoming older and am collecting more experiences. JFGI will only take me so far, eventually I need to apply a real answer and there is rarely a "perfect fit". and finally by the time I am looking through forums, I am just about at the end of my rope. So, where can I go from here? I find that networking with "real-people" is probably my best next place to build on. The problem is that this industry seems to be non-people related, in other words people who tend to go into IT are not very people-oriented. With the industry becoming seasoned and older, and the down-turn in overall markets one would think this will be something soon to be overcome. Lets see...

So, when it comes to building a reporting solution why is it that users just want to "Automate" their already overly complex and convoluted Excel or Power Points? Almost every engagement requiring a "Report" seems to start out the same way. There are two primary trains of thought, the first is to "Get Everything" and the second is to "Automate Everything". Business Analyst say they want "everything" when they don't know exactly what a "Reporting Application" is or they don't know exactly what they want in a Report or Report Application. It's kind of like the General Contractor, who'll tell you he does "anything" when you contact him/her to build you a Deck or replace your Roof. Anytime I see ambiguity at this level, I question the understanding level of the individual making the claim or request. There are two tactics I find very helpful when faced with a request that seems to be less than well though...

So, it's Saturday... Why am I still thinking about work? Disconnecting is probably the second biggest challenge behind Keeping Up. If I'm working on one, I am not working on the other. In effect, disconnecting is one of the attributes of "Keeping Up". Just like sleep rejuvinates the mind from a day of stimulation, disconnecting gives you time to rejuvinate your professional mind. Remember the addage "... All work and no play..." So disconnect today, it'll help you keep up in the long run.

So, one of the many challenges in this thing called consulting is "Keeping Up". Or at least this is the case from my point of view. "Keeping Up" encompasses so many different aspects; Keeping up with new trends, Keeping up with best practices, Keeping up with schedules, Keeping up with clients, generally keeping UP when everything is working to keep you down. It has been my experience that it is best in all of these cases to keep up by slowing down. This might seem a bit counter intuitive, but it can work. By slowing down I don't mean to become complacent and lazy, I mean to achieve heightened awareness through clearing and centralizing. Clear the clutter, and you'll be able to find things with greater efficiency. Having a clear spot or two on your calendar will open the door to introspection and recovery. Clear your mind of the excessive "noise" so the important things can be heard and seen. ...You get the idea, in other words Relax and Receive. W...

I've arrived at the end of a new day, and yet again there was just not enough time to do it all. As usual, more demands, less time. Clients pushing dates back as a result of not knowing what a "Report" is not to mention a "Report Requirement". Other clients, coming to the conclusion that they actually do need some guidance. Pushed and Pulled in multiple directions seems to be the way... Feast and Famine, when it rains it pours, etc... you name it. But, I don't think I could have it any other way. Where else can you work on some custom servelets one day, ORACLE the next, MS SQL Server Stored Procedures after that, then an IBM WebSphere installation for some custom web apps and SSO? I think I'd be bored anywhere else. So, with all of my extra time, here to the new blog