Building an inter–generational knowledge transfer system (part 9)

Web services: flexible and powerful but most importantly the overall technology view must be platform independent. If the solution is bound to a specific platform ultimately it will not provide the flexibility required for the solution.

The web service offered as part of the initial system must support the following:

· On-line and Off-line use

· PC/Table and Mobile use

· Easy upload of new materials

· Easy download of new materials

· Integration with the DLM© Libraries

· Integration with various feedback loops for class improvement, new classes

· Integration with the brainstorming system

· Integration with the parking lot system

Based on this there are additional technology beyond the web service that are needed. The first is a directory structure that will support the device checker and the rights assignment for users. The simple model for this would use groups within the directory to manage the security application. If you are in the off-line, some training group than all training authorized for your group would be available to you, and all authorized off-line training would be available. The reverse, the no off-line training group would have all training available to that group when on-line, but none that can be transferred.

The device checker application would reside with the web service on the server system. It would determine both the device being connected, the total available storage on the device (this would be set by the user creating a top utilization percentage say 95% of storage consumed) taking the percentage of usable storage and not exceeding that. IE if you are asking for 10 gig of training to be downloaded notify the user that they only have 5 gig available, and that based on the connection of the device the download would take 2 hours. (or 15 minutes or a week you get the idea). Finally, the device checker would also if needed create the secure container on the device consuming the training. This would allow all users to easily consume training that is public or openly available. But only those users with rights would get training that was secure. If the training was secure the device checker would manage the secure container for the training. The TTL of the certificate given the user could be determined based on a number of factors. When the TTL expires the user has to enter their password, or has to connect to the server system, enter their password etc. Depending upon the security requirements for the device and for the training.

During a course a user needs the ability to offer comments and offer new thoughts. Beyo9nd specific to a course there needs to be an easy uploading of linked and unlined content. Linked content would be a user podcast or vlog or blog focused on the content and information in a training course. Either nuisances or additional material. New would be something there isn’t currently a training module for or something that isn’t currently considered. This allows for parking lot ideas to being creating training content. Additionally, this allows for off-line interaction with brain storming sessions and feedback on new ideas and potential areas of organizational growth.

Often new materials such as the ones uploaded above have an incubation period and a review period. Users in this system would be able to select “known good sources” that would bypass the review period for specific users they have selected. This allows information to flow quickly throughout the system. It also allows the SME’s to see who is next up.

One of the things that I have always advocated is that SME’s have to be rotational. I’ve seen great community and KM systems that fail over time because the same people are doing the leadership jobs year after year. At some point, normally after a year, the been there done that experience is no longer valid. So rotational SME’s is a critical component with the DLM© system. If you spend more than a year in a SME role there has to be a uniqueness about that role that requires your presence. Otherwise, every SME in the system should be looking for the next SME!

.doc

Knowledge Management Geek