« April 2006 | Main | June 2006 »

May 23, 2006

Thoughts about Japan: Part 2

I've been waiting to write about Japan again in my blog, knowing that I was going to visit again this spring. I have only been off the plane a few hours and decided to capture my thoughts before the jet lag really kicks in.

I visited our UniPress business partner in Japan, Macnica Networks, in Shin-Yokohama (30 minutes from Tokyo) and went to several meetings in Tokyo. I then attended the first Japanese User Conference for FootPrints in the Shinagawa Conference Center in suburban Tokyo.

I had a great trip. First, I got to see so many of the Macnica people who I had met before, as well as some new faces. I had technical meetings with Macnica’s FootPrints programmers and support people. We discussed some language issues with supporting Footprints in double-byte kanji, and also discussed the future direction of the FootPrints product line.


While in Japan I also met with various System Integrator partners of Macnica. These are large companies who sell products such as FootPrints, and include various services like customization, training, and integration with other applications. Often these System Integrator partners manufacture or distribute other product lines which can be used successfully with FootPrints.

In one case, I met with the division of a large partner who is the developer of the largest Network Management system used in Japan, and they are planning to integrate FootPrints with their tool; so their 10,000 customer sites can get the benefit of both products working together.

The User Conference was the high point of the trip. Macnica gathered 100 customers and prospects into the Shinagawa Conference Center. I spoke about using FootPrints for Compliance and Change Management. This is a big topic in Japan, as the government is planning a J-SOX compliance law for business, comparable to the Sarbanes-Oxley (SOX) law here in the US. People are very interested in how to use FootPrints to keep track of issues using approval processes, and of course, with an uneditable audit trail. I got a very nice reception at the event, and my sense is that the people were appreciative of learning how FootPrints can help them address compliance and change management initiatives.

Several customers gave talks as well. They talked about how FootPrints helps their companies and how useful it has been to them. Macnica also talked about novel uses of FootPrints, which is always interesting to me as I get to learn how people are configuring and customizing the system to address all types of activities and projects.

I was very happy during the cocktail party on Friday night when several current customers -- unsolicited -- got up to say how much FootPrints helps their companies.
You might wonder how I could understand anything. Yes, a majority of the conversations were in Japanese, and I only know about 50-75 words. Macnica provided me with a person who could do simultaneous translation. This not only helped me to understand the talks, but also helped me in one-on-one discussions with customers so they could communicate with me.

If you ever go to Japan, here is a useful tip: Business people have a formal way of exchanging business cards before doing anything else. They turn the card 180 degrees so the recipient can directly examine it as it is presented with both hands. They introduce themselves. "Hello, my name is Kawahara, glad to meet you," for instance.

You should do the same: "Hello, my name is Krieger (note the last name reference), glad to meet you." Even better, here is a useful Japanese phrase, it puts people at ease: "Hello my name is Krieger, 'hajimeymashtey.'" -- phonetically, that means 'nice to meet you' in Japanese.

Of course I had wonderful food in Japan. Whether it was sushi or tempura or a bento box (a box with various delicacies) or beef or shrimp, the food was wonderfully prepared and beautiful to look at and delicious.

My hosts at Macnica were so thoughtful, they even took me to the Sumo matches which were going on in Tokyo last week. What an experience! First, the color in the Sumo stadium was unbelievable. I've seen Sumo on TV, but actually being there was very different. The vivid colors stand out in the outfits that the referee wears; the outfits worn by the people who sweep the ring; the advertisements which people walk around the ring between matches; the banners and paintings of past champions on the walls. All of this was very colorful and interesting.

And the Sumo wrestlers themselves are giants. It's not only their girth, yes, they are large in the middle -- I resist calling them fat, because they are not. But they are also very tall. They tower over everyone else, and the foreigners who've reached the top of the Sumo ranks, including wrestlers from Mongolia and Eastern Europe are 6' 6" and taller, and weigh 350 pounds of muscle or more. What a sight.

All in all, I had a great time. I learned a lot, and hopefully gave some helpful tips and hints to my hosts and their customers and prospects. As always, I enjoyed the great hospitality of the Japanese people, and look forward to going back soon.


Sayonara,

Mark

May 04, 2006

Why LDAP is Important to the Service Desk

I've been thinking about technologies which are important to the Service
Desk, especially in integrating with the organization's existing
infrastructure.

One of the most widely used and accepted methods today for centrally
managing Address Book contact information is LDAP or Lightweight
Directory Access Protocol.

LDAP allows any organization to record, in one place, all Address Book
information about their employees or customers, and use this information
in a variety of applications. Since there is one data store for this
information, and since this data is generally managed by one group in
the IT department, other applications can generally use this LDAP in
read-only mode.

This protocol is so important that Microsoft, SUN, Novell, Lotus, and a
variety of other vendors have made the LDAP server a centerpiece of
their respective offerings. In Microsoft's case, Active Directory, which
is their LDAP product, is an integral part of Exchange. And login
services are a part of LDAP, since a user's password is stored in LDAP.

So what's this got to do with Service Desk?

Every Service Desk needs to have an Address Book of employees and
customers. It needs to have some way of logging people in and tracking
activity relevant to the Service Desk interactions. Therefore, if the
organization as a whole has an existing LDAP repository, the Service
Desk would be very remiss to not use the existing LDAP data, either for
login or for Address Book, or for both.

Here are some of the benefits I was thinking about when the Service Desk
tightly integrates with the LDAP service:

1) Customers and Agents both get the benefit of having one userid and
one password if the Service Desk can authenticate through the LDAP
authentication system.

2) Customers get the benefit of having their contact data
automatically put into the ticket when they use self service to
create a Service Desk ticket.

3) Agents get the benefit of quick lookup of customer data when
filling out a ticket, directly from the LDAP repository.

4) Everything is always up to date if a Dynamic lookup of LDAP data
queries the actual LDAP repository, not a copy – eliminating
manual data synchronization processes

What are the technical challenges to implementing this kind of LDAP
integration?

1) LDAP authentication calls to/from a database need to be dynamic --
a call to the LDAP service needs to be at the heart of the
integration, so that the current userid and password are used in the
Service Desk authentication, not a two week old version of this date
which was imported then.

2) LDAP Address Book lookup needs to be dynamic too -- a call to the
LDAP Address Book lookup needs to be at the heart of this
integration, so that 'importing' LDAP data into the ticket (or
listing Address Book data) is done via a dynamic call to the LDAP
server.

Importing data from LDAP on a regular basis might seem like a good
idea, but the work needed to setup an import, and the likelihood that
the data is out of date are serious flaws in a real 'import' of the
full LDAP database.

3) Setting up the LDAP authentication and the LDAP Dynamic Address
Book lookup have to be easy from an Administrative point of view. And
making changes to the setup has to be easy too. Having an excellent
LDAP integration, but one which took 3 months and cost an extra
$30,000 (plus additional thousands whenever a change is needed) is
not a good solution.

4) The LDAP integration should work for a lot of different kinds of
LDAP servers.

The good news for you FootPrints users is that we've implemented the
FootPrints to LDAP link as a true dynamic integration, for all LDAP
servers which we've tested against (and we were given an Open Group LDAP
certification), and it is very easy to setup. It can take a few minutes
or hours through a Admin Web page without any programming required.

What interesting LDAP projects are we thinking about?

First, we sometimes hear about writing to the LDAP address book (it is
an infrequent request). I think that most organizations do not want
'other' applications to write to their LDAP address book: The owner of
the LDAP is responsible for writing it, not the Service Desk. But if this
requirement grows, we will implement it.

Second, we occasionally hear from a site who wants FootPrints to manage
a single address book consisting of two or more separate LDAPs at
different locations and with different LDAP 'urls.' We are thinking
about this one. It might benefit more than just a few people, but there
might be LDAP methods outside of FootPrints to give two or more LDAP
sources a single access point. We'll see if this can easily be done.

I'm really glad we did a fine LDAP integration. It is so helpful to our
customers and provides additional capabilities and possibilities for the
Service Desk. Let me know if you have comments or questions, I'll be
happy to answer.

Mark
msk@unipress.com