A new breakout of the acronym “SAP” heard today:
SAP = Slow and Painful
A mix of crisp insight and totally random thoughts on software development, estimating techniques, political influences on technology decisions, technical team building, consulting skills, application development methodology, emerging technology trends, vendor hype, legacy system integration, and everything else that makes a credible I/T Architect and a successful I/T Architect career.
A new breakout of the acronym “SAP” heard today:
SAP = Slow and Painful
Posted by
Philip Hartman
at
8:13 AM
2
comments
Labels: SAP
If you have been a regular reader of my blog, you know that globalization is one of my favorite topics of discussion. Therefore, I would like to draw your attention to the International Conference on Global Software Engineering which will be held
Please note that if you have some thoughts to share, there is still time to submit a paper. The deadline for abstracts is
Yours truly is a member of the Program Committee for the event. However, that doesn’t mean I automatically get to attend. I still have pay the registration fee and pay to get myself there… or convince my employer of the wisdom of spending their money to send me. I had the good fortune to visit my team in Bangalore and interview a few programmers for positions back in the fall of 2004 and I would certainly enjoy a return trip for the conference. I would be curious have any of you (my readers) had success at securing funding for travel to this kind of thing? If so, I’d love to hear how you justified the expense to your employer.
Copyright © 2008 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
6:29 AM
0
comments
Labels: Career, Communication, Globalization, Leadership, Lessons Learned
This may be a silly thing, but when you write your job title, do you write it as "I/T Architect" or "IT Architect" ?
I got used to using the slash several years ago. I think that is what I saw most often inside IBM where I work.
However, now it seems that I am seeing the title written without the slash. I noticed that the Open Group certification program uses no slash. (See the Master Certified IT Architect logo on the right side of my blog.)
I'm tempted to abandon the slash. What do you think? Which do you use? Which do you like better?
Copyright © 2008 by Philip Hartman - All Rights Reserved
Posted by
Philip Hartman
at
9:30 PM
2
comments
Labels: Career, Certification
I received an email a while back from Tin Dizdarevic of the Rational User Group looking for a volunteer to lead the Tennessee Rational User Group. After much soul searching and a little procrastination, I decided to raise my hand and take this on.
If any of my readers from Tennessee would like to joint the Tennessee Rational User Group, please go to the Global Rational User Group web site, use the "Find a User Group" feature to search for the chapter in Tennessee, and register for the group.
I am also soliciting suggestions on the best (or least bad) times for the User Group to meet, how often it should meet, where it should meet, and what topics you would like to see addressed.
Posted by
Philip Hartman
at
9:14 PM
0
comments
Labels: Rational Tools
I am a little embarrassed at how long it has been since my last post. My project in China was very demanding and when I rolled off that project the end of October I went immediately into the Thanksgiving and Christmas holidays. It was January before I started feeling normal again and by then I was out of the habit. I will try to do better now.
Posted by
Philip Hartman
at
9:11 PM
0
comments
Labels: blogging
One of the things which I learned in China is that many of the young, educated, professional Chinese view having good English language skills as a prerequisite to many of the top jobs in China. Apparently, the best jobs in China all require regular interaction with foreigners like me. I found they were a lot more interested in me helping them with their English than in helping me learn Chinese.
Off topic for this blog... but for anyone who might be interested I even got to teach English in a Chinese government-registered church. See My Chinese Church Away from Home.
I decided to start a podcast equivalent to this blog at http://artsciita.podbean.com/. If English is not your native language, I hope you will check it out. This is something of an experiment so if you try it and like it, you had better let me know. It is a little extra work on me and I might lose interest if nobody seems to be paying attention. Here's an online MP3 player with links to share our subscribe to the RSS feed. I went back and added voice for the most popular posts and a few of my personal favorites.
Copyright © 2007 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
12:21 PM
4
comments
Labels: Career, China, Communication, Globalization, Internet, podcasting
About 6 weeks ago, I completed one of the most challenging 10 months of my entire 26+ year career. I helped create the Enterprise Service Bus for a major Chinese company and during that time I made six trips to China and spent a total of 4.5 months there. I joked with friends that I did not live in the "real world" anymore because I would have never believed that anyone would actually pay me to work in China for so long. I did, however, learn a lot about globally distributed teams, ESB's, SOA, and the culture clash of trying to make people from China, the US, Canada, and India all work together.
Copyright © 2007 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
12:06 PM
0
comments
Labels: Career, China, ESB, Globalization, Politics, SAP, SOA, Soft Skills, Web Services, XML
Over a year ago, I had a post in which I discussed how difficult it is for a custom application development person like myself to get adjusted to projects based on a packaged application like SAP. It had the somewhat humorous title How to Talk to an SAP Consultant (If You Must).
If you keep reading this post, you will see that I am now starting to understand some of the SAP terminology which once seemed so incomprehensible. I hope you will find this post helps accelerate your own understanding of SAP if you are thrust into it like I was.
I now have become all too familiar with the SAP interfaces for external system known by the name "IDoc".
SearchSAP.com provides the following definition:
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program.Being relatively new to the SAP world, these complex documents reminded me of database schemas generated by the old Computer-Aided Software Engineering (CASE) tools with many cryptic table names and field names that only an automated tool could keep track of.
Segments form the basic building blocks of an IDoc type and are used to store the actual data.
A segment type is the name of a segment and is independent of the SAP release.
The segment definition is the release-specific name of a segment. By combining the segment type and the release, the required segment definition can be determined: This way, you can assign segment definitions from previous releases to an IDoc type in the current release. This may be necessary if, for example, the partner is using an older release which supports your current IDoc type but not your current segment definitions. You then have to "reset" these in the
Partner profiles .

(Dec 2007) English not your native language? I've begun making podcasts of popular posts and they are available at http://artsciita.podbean.com/. Listen online at that URL, with the MP3 player below, or subscribe to the podcast using the RSS feed and listen with your favorite MP3 player.
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
7:35 PM
2
comments
Labels: Rational Tools, SAP, XML
I've been around clients for some great discussion on the perils of over-customizing SAP lately. I hope to collect some of the lessons learned here for your reading enjoyment and career enrichment.
"They told us that the new SAP system would have over 160 reports out-of-the-box that we could use to run our business and we didn't plan on having to create a lot of custom reports. Now they tell us that's not true. Almost all the out-of-the-box reports are broken. Almost every report we need must be a custom development."It seems this company made some customizations to their base SAP system (ECC) when they were only operating in a only single country and were focused only on a transactional, commodity type business model. They then moved into multiple countries and began to look closely at big, relational customers and value-added services. To support this, they planned to create a new CRM system running on top of their existing ECC. They were not happy to find out that their legacy of prior ECC customizations "broke" a lot of the standard SAP reports.
(Dec 2007) English not your native language? I've begun making podcasts of popular posts and they are available at http://artsciita.podbean.com/. Listen online at that URL, with the MP3 player below, or subscribe to the podcast using the RSS feed and listen with your favorite MP3 player.
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
6:55 PM
1 comments
Labels: Lessons Learned, Packaged Applications, SAP
As more than a casual observer of the globalization of technology (I type this from my hotel room in Beijing) I was amused to read the article "China hit by brain drain, report says" in the China Daily provided by the Beijing Hilton. The article made some pretty stark comments about the state of affairs:
Posted by
Philip Hartman
at
7:37 AM
4
comments
Labels: China, Globalization, Talent
My hotel in Beijing gave me a free copy of The Wall Street Journal Asia yesterday. The cover story got my attention with the title "Vietnam wins attention as new outsourcing hub." The article goes on to explain how companies like Harvey Nash PLC are using Vietnam to service clients such as Belgium's Belgacom SA, Honda Motor Co.'s British unit, Discovery Communications Inc.'s Discovery Channel, and NBC Universal's MSNBC. I did a little poking around on www.ibm.com's site search capability and found that my own employer is active as well. See IBM Press room - 2007-03-12 IBM Expands Global Service Delivery Capabilities - New Centers in China and Vietnam.
So which country is next?
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
8:34 AM
0
comments
Labels: Globalization, IBM
(Dec 2007) English not your native language? I've begun making podcasts of popular posts and they are available at http://artsciita.podbean.com/. Listen online at that URL, with the MP3 player below, or subscribe to the podcast using the RSS feed and listen with your favorite MP3 player.
Posted by
Philip Hartman
at
7:58 PM
0
comments
Labels: Governance, Leadership, Packaged Applications, PM, Politics, SAP
I had a subtle career milestone today. Today I became fully aware that I was now "Global" ... with a capital "G" I think.
At about 6:30 am Central time I checked email at home before leaving for the airport. I saw an email from a business leader in the UK which set off alarms in my head that an important business decision my client needed to make was not being addressed. Knowing that a politically important deadline is approaching, I fired off a "this is a big issue!" email designed to alarm my readers that something important was not happening.
About 8 am Central time today I was waiting for a flight at the airport and my cell phone went off. It was that same business leader in the UK who took notice of my alarm. I don't know about you, but I don't get cell phone calls from people I've never met from other countries every day.
Shortly after arriving at my destination on the East Coast of the US, I scheduled a web meeting for tomorrow morning between people in Baltimore, Raleigh, California, and Beijing.
Later I was on a call between the US and Canada talking about interfaces to a system in China.
Still later I discussed architecture diagrams showing system components in Rochester (NY), Boulder, Dallas, Tulsa, Phoenix, Hong Kong, Beijing, and Toronto. I tried to figure out if the component in Hong Kong was really necessary. Could it be co-located with the rest of the stuff in Beijing?
I ate a hurried dinner of Tandoori Takki with two co-workers. One is a Norwegian citizen born in China but holding an American green card and the other was born in India but has been working in the US for a while. My history is boring compared to theirs.
Five minutes after checking into my hotel, I joined a conference call between the US and China but the co-worker from China didn't make the call. My co-worker later came online in China on instant messenger later and I pinged him about the call he missed. It turned out he was double booked for that timeslot. Heavy sigh. When are we going to solve time zone issues for calendars? I made sure he had the information for the web meeting in 9 hours.
This globalization thing isn't all its cracked up to be. Exactly when is it I am supposed to have some calm moments to think? When is it I am supposed to get more exercize like my doctor told me? Will the guy in California get up to make the web meeting at 6 am his time? Did I even have a right to call a web meeting that required someone to be there at 6 am? Will the guy in Beijing who has to join at 9 pm his time have a decent Internet connection? Did I have a choice on the time given that the guy we want to talk to was available then and it was a comfortable 9 am for him? Will my flight home on Friday be on time so I can make my daughter's piano recital? How early do I set my alarm clock for tomorrow? Early enough to hit the hotel treadmill or late enough to get another hour of sleep?
I have another trip to China coming up in two weeks. It is still fun for now. I can see how this could get old. I would love to hear how my readers in similar situations are handling the demanding hours, encroachment upon personal time, cultural differences, etc.
FYI, globalization has been a frequent topic of mine. You might take a look at some previous posts such as:
(Dec 2007) English not your native language? I've begun making podcasts of popular posts and they are available at http://artsciita.podbean.com/. Listen online at that URL, with the MP3 player below, or subscribe to the podcast using the RSS feed and listen with your favorite MP3 player.
Copyright © 2007 by Philip Hartman - All Rights Reserved
Posted by
Philip Hartman
at
8:31 PM
4
comments
Labels: Career, Globalization, Leadership, Soft Skills
This isn't my usual type of post because it talks not about concepts or competence but about a stroke of unusually good professional luck.
I was one of 4700 IBMers attending the Technical Leadership Exchange in
There was some training on Sunday before the conference started on Monday. At dinner Sunday night I sat down at a table of strangers and made some IBM smalltalk with my new acquaintances. A few minutes later some other guys sat down. The guy who sat to my immediate left asked me who I was, where I was from, what I was doing, etc.
When I mentioned I was working on a project to create a canonical data model for an ESB, he casually told me "Oh, I've been working on IBM's canonical data model for IBM's ESB for two years. I'm the lead architect." At this point I just about fell out of my chair. I could not believe my good fortune.
I told him I would pick up his dry cleaning and wash his car if he'd tell me everything he knew about canonical data models. He laughed and offered to help me.
To make a long story short, he wound up showing me the canonical data model for IBM's own ESB and pointed me to where I could download XML schemas off the IBM intranet. Incidentally, IBM uses SAP for many of its back end functions. One valuable tidbit of information included was a spreadsheet linking attributes in the canonical form with specific SAP IDOC segments and fields.
In the consulting business we call this "intellectual capital" and wonderful intellectual capital it is. Obviously, this has really jumpstarted my work. I wish I could say that I was really good but in this case I must confess being really lucky (or have I been living right?... that's another discussion).
He never did make me wash his car either. As we said playing basketball after someone said we were just lucky to make a difficult shot. Luck counts!
Posted by
Philip Hartman
at
8:54 PM
0
comments
There is a yearly conference for IBM's client-facing technical leaders. During the lean years when money was in short supply for training, being selected to attend this event was especially coveted. For a long time, the only way to be guaranteed an invitation was to get selected to speak at the event. Speaker selection became quite competitive.
I am happy to report that after about four years of trying, I actually got to speak at the 2007 Technical Leadership Exchange held in
I am a firm believer in sampling something really off-the-wall every now and then to knock the cobwebs off of some unused brain cells. I saw that a favorite speaker of mine, David McDavid, the source for a previous post The Role of the Business Transformation Architect was giving a talk on the business implications of Second Life.
I naively thought that only a few crazies like me would show up for such a thing. Wrong! There must have been 500 of my peers there to check it out. The entire conference was about 4700 people and you had to arrive by
As a speaker, I was privy to the pre-registration numbers. When I sorted the 420 or so elective sessions, the Second Life presentation was the one that more of IBM's technical leaders wanted to reserve a seat to attend than any other. At the session I learned IBM is quite a land baron in the Second Life "megaverse," owning many Second Life "islands".
David talked about how he played around in Second Life and found himself wanting to set up his own place and how he intentionally chose a location with interesting neighbors including a small software company and East Coast artist. He raved about all the interesting people he had met thru Second Life. It began to sound like an endorsement of my unoriginal theory that it is good to check out off-the-wall ideas and hang out with interesting people not like me every now and then.
The message to my readers is that smart people are either taking Second Life and the business implications of it very seriously... or they are afraid they aren't taking it seriously enough and might be missing the next big thing.
I decided I must already be behind the curve. If you log into Second Life and find a boy next door looking avatar named Caleb Schumann who doesn't know what he's doing in the megaverse, it is me fumbling around trying to catch with the train that has already left the station without me.

Me over the volcano that is about to errupt and kill me if I don't do the hula for some character on a training island for newbies.The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
9:32 PM
1 comments
Labels: Creativity, Emerging Technology, innovation, Trends
I had the good fortune to make my second trip to visit my client in Beijing, China. My trip was extended twice and I wound up staying three and a half weeks.
Me at the Summer Palace in March 2007.
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
8:38 PM
0
comments
Labels: Career, China, Globalization, Lessons Learned
It has been an embarrassingly long time since I’ve posted but I recently made a huge career change and I’ve been pretty busy. I’m afraid blogging dropped off my radar for several weeks. At least it was huge for me. As a consultant, I could change projects and clients without changing employer. Not everyone is that lucky.
Here’s a little history. I was encouraged by my management back in the fall to leave my comfort zone and take on bigger challenges. I think the handwriting was on the wall that I was as high as I could go in the organization if I stayed put. At first it looked like I might become what we call an “Associate Partner” in IBM Global Business Services and take on more of a marketing role. Instead, I wound up taking on an Enterprise Architect role in a truly global project.
Me at the Temple of Heaven, Beijing, China
I did indeed raise my hand and say “Yes” I will leave the position where I was happy, effective, and comfortable. I will leave the position where I got to sleep in my own bed every night and “jump into the frying pan.”
National Software Technology Park - Beijing, China
I knew I wouldn’t be bored. But would I be happy?
This whole experience had led me to think a lot about the question “When is the right time to leave a good job?” This is not an easy question. I think it strikes at the heart of our professional identity. I had to do a lot of soul searching about my priorities. I had to face questions like:
If you look at my situation purely from a career point of view, I stayed in my previous position too long. Four years with one client on one major project using technology picked 3 or 4 years ago is too long for a technology professional. There were, however, other considerations such as the whole work-life balance issue. For me the decision to make a change came down these points:
Click here if you are interested in my commentary and pictures about my recent travels to China. Still more pictures on flickr. Don’t forget Toronto.
Copyright © 2007 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
8:48 PM
1 comments
Labels: Career, China, Globalization
Copyright © 2007 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
8:35 AM
0
comments
Labels: China, Globalization, IBM
I have been able to visit the IBM facility north of Beijing's fifth ring where teh IBM Development Lab and IBM Research Lab are housed. There is also an SOA Solution Center as well. The internet was a lot faster there too compared to the hotel and my client. I've heard again that an earthquake off Taiwan ruined and undersea fiber optick cable and much of Asia is affected. How many of you have redundancy between the US and your global operations to survive an undersea cable break? What would you do if it only was a lot slower vs. broken completely?
Below, my IBM co-workers play a hacky-sak type game at lunch. The software group development lab is to the right, the solution center is straight ahead behind them, and the research lab is to the right side.
Copyright © 2007 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
2:14 AM
0
comments
Labels: China, Disaster Recovery, Globalization, IBM
Anyone who has been a regular visitor to my humble blog has probably noticed that the globalization of software development has been a frequent topic of mine. In particular, I have been heavily involved over the last 3-4 years with software development in India. Whether you or I like it or not, it looks like I am going to continue to be immersed in the topic of globalization. I started a new assignment with a new client recently and this client has very strong ties to China. I could not believe my good fortune when I was given a golden opportunity to travel to China for about two weeks of meetings. Wow! A chance to observe the technology sector in China firsthand! I arrived in China Monday night.
Because of all the language and cultural issues, IBM has made a conscious effort to locate consultants who speak Chinese. Someitmes it seems like every Chinese speaking IBM consultant in the US and Canada is on my project! Not that this is a bad thing either. Its great to be able to hop in a taxis with a co-worker and have a co-worker act as interpreter.
Then around 10 AM this morning "it" happened. My client got passionate about a particular topic and switched from English to Chinese. Within about 10 seconds all my co-workers had joined in the discussions in Chinese too and "it" hit me. I was the only non-Chinese speaker in the room and there were three different Chinese conversations going on. I didn't take it as they were trying to exclude me. I think it was just easier for the client to express their thoughts clearly in their native language. I chose to just let the conversations go on without my interruption. My co-workers updated me later with a summary of their concerns. I have a feeling it won't be the last time either.
If you're interested in reading more about my trip to China, see my posts on China on my "Phil's Folderol" blog.
Copyright © 2007 by Philip Hartman - All Rights Reserved
The postings on this site are my own and don't necessarily represent IBM's positions, strategies, or opinions.
Posted by
Philip Hartman
at
4:46 AM
1 comments
Labels: China, Globalization, Soft Skills