Grandpa Ham – Grandpa Can do IT!

Spent the morning today reviewing the OASIS Customer Information Quality (CIQ) specification. Good work. CIQ is set of XML Schemas designed manage names, addresses, and locations related to organizations and individuals across the globe or in your back yard. For CIQ, at least, “flexible structure” is not an oxymoron. I am researching this for the OASIS Emergency management Technical Committee, but it has implications for the Virginia DMV as well. A basic structure for accessing the “360 view.” Good stuff. Here is the link to the OASIS download page.

The DMV work continues to go well. It is truly a joy to work with the team that they have assembled for BPR activities. These folks are the cream of the crop. This is one project where the taxpayers are getting their money’s worth. For the vendors out there who might be reading this: These folks know what they are doing. You are advised to work with them honestly, directly, as true collaborative partners. This will not be a “pull the wool over their eyes” procurement. Be prepared to work with them and you will do well. Try the stereotypical contractor shenanigans and you will have no end of difficulty.  To paraphrase the old Oldsmobile commercial, this is not your father’s DMV!

My current work definitely keeps me on my toes. The folks assigned to the BPR team were hand-picked across the DMV to NOT fit the stereotype we sometimes attribute to DMV employees. They learn, and they make me learn. They work hard, and they make me work hard. And I appreciate them. Here is a group picture on the DMV reengineering site. I am in in the middle row, toward the left side.

I am using the following text in my e-amil to friends and constacts letting them know of my change in situation:I have been a Battelle employee for 12 out of the last 13 years, but I am moving on. Battelle is a good organization to work for. I have enjoyed it, and will always value the experience that I gained.

For now, I am acting as an individual IT consultant. I am working full time on a contract with the Virginia DMV as an IT process consultant to a major cross-agency BPR effort. My primary function is helping the various BPR teams put together coherent scenario driven requirements within a model that will drive a future-state SOA and will provide full life cycle traceability from initial requirements through code and test. The process works. I get to see the evidence every day.

My part in this activity is as a mentor, trainer, and general enabler to the teams doing the actual BPR activity. I love the work, but it is not secure. It may last three months, or it may last three years. A lot depends on the vagaries of state budgets. My best guess is that I will be almost full time for a while, and gradually move toward occasional training and “reinforcement” visits.

You may ask what “almost” full time means. It means that I am separately maintaining my membership on the OASIS Emergency Management Technical Committee. It also means that I can take a week or so per month for other activities. For example, assuming that DM-OPEN survives as promised in the transition from Battelle to the DHS CIO (or some other provider), I can still help with connectivity. Similarly, if a company or government agency wants to put any of the experience I have gained over the years to work for them, I may be able to help. It would have to be limited hours initially, but could grow bigger over time, depending on the situation.

At any rate, you can find me, my resume, what I can do, and what I am currently doing at http://grandpaham.com

I am mentoring a group Business Process Reengineering (BPR) teams, using a scenario-driven requirements development process that features business scenarios written by SME’s for SME’s. Formal requirements, consistent terminology, and agreed-to scenarios are captured real-time in the Enterprise Architect CASE tool. I am also mentoring formal software design for one of the process improvements that has come from the BPR activity. In other words, I am helping the actual development team formalize and implement a design process based on the ICONIX process that will make “requirements to code” a consistent, streamlined, and productive activity. It just does not get any better than that for an “ORF” like me.