rfid project data sheet

KM of 10 January 10,

2013

Project Data Sheet

RFID KNOWLEDGE MANAGEMENT

Program Name

Author: KM

Revision/Date:

Purpose

The project goals are to establish a Knowledge Management (KM) system to intelligently accumulate and distribute RFID knowledge

Objectives

The objectives of the KM system are (1) Accumulate knowledge about RFID Technology. (2) Catalog, collate and package this knowledge into

best practices and business cases. (3) Set up a protocol for access, control and update

knowledge within the system.

Scope

What’s in scope (1) Limited to RFID (2) Based on previous implementations, work done

by other COEs, vendor interactions, and core team knowledge

What’s not in scope

Assumptions

EX CO has already implemented KM systems. This project will use the tools, models and methodology from those systems to build the RFID KM system

Key Partnership and Roles

Key Stakeholders: Director, LGT & PPO IT Manager Strategy and Planning Technology Architecture and RFID RFID IT Program Manager. Related Projects RFID IT COE

Resource Requirements

1. One Time Design: $k Development: $k Deployment: $k Total $k

2. On going Maintenance:

Return on Investment

$k per year savings in start up and training costs. Every one involved in RFID will have a common knowledge baseline to start from.

Cost is $k

Payback is

Roles & Responsibilities

ROLES RESPONSIBILITIES FTE PERSON MONTHS

Program Manager

Overall management and delivery of results.

0.25

Project Manager

Acquire resources, create and execute on plan, and deliver results. Perform all other responsibilities as needed-

1.50

Architect

Design and architect system including information and data flows, interfaces, security and communication.

1.50

Developer Develop and deliver specified systems.

4.50

Functional Define requirements, perform gap analysis and test completed deliverables.

15.00

Issues/Risks

None at this time

Contingency Options

N/A

Deliverables & Timeline

Task Date

KM Project Data Sheet April 20, 2005

Program Project Plan April 22, 2005

Program Resource Plan April 25, 2005

Implementation Plan April 25,2005

Measurement of Success

Project Data Sheet- RFID IT COE

KM of 10 1/10/2013

1. Fully functional KM system which allows access to relevant information on RFID

2. Designation of system owner with a clear cut set of rules for publishing, accessing, sharing, updating information in the system.

Sponsorship/Approvals

Director, LGT & PPO IT Manager Strategy and Planning Technology Architecture and RFID


KM of 10 1/10/2013

KM Project Plan:

Scope

Determine Project Scope Determine Boundaries

What Information is available?

Presentations,

Whitepapers,

Conference Proceedings,

Research Findings,

Reports,

E mail

Drawings, etc. Where does the Information reside?

On-line,

Off-line,

Type of Media,

e-room, Sharepoint,

Physical location,

Server Designation How will Information be collected?

Requests to owners

Designate persons to acquire information

Methods for owners to provide information

Designated posting locations How will Information be collated?

Business Rules for data o Sorting o Tabulation o Ordering o Importance o Versioning

Subject matter referencing and cross-referencing How will it be catalogued?

Taxonomy

Hierarchy How will the Information be stored?

Database

Links

PDF Files How will the Information be accessed?

Browser based

Inside Portal

Physical Storage Media How often will the Information be updated?

Scheduled update mechanism

Automated mechanism

Rules for override


KM of 10 1/10/2013

Who will update the Information?

Designated owners for content

Criteria for update

Criteria for deletion What will be the mechanism for updating content?

Governance body

Clearing house mechanism

Update Method o Publish o Alerts o E mail

Who will do all of this?

Project ownership

Resource ownership

Determine initial baseline

Starting Point

Ending Point

Acceptable error levels

Requirements Analysis

Business Case

Why do we need this system?

Business Drivers

Technology Drivers Who will use it?

Target user profile o Work done

Job Position Role Hierarchy

o How often need to consult KM arises Who will benefit from it, and how?

Target user profile, as above

How will the user benefit o Steps eliminated in workflow o Time reduction in job completion o Ability to perform better, faster, cheaper

Who will be burdened by it?

Extra effort required to package information for publication

Extra effort required for vetting and cleaning information

Extra effort required for setup, maintenance and support. Can we do without it?

Weren’t we doing fine so far?

What ‘workarounds’ did we use until now?

Why are they not valid anymore? What will it cost?

Design, development and deployment

Extract, transform and load


KM of 10 1/10/2013

On going maintenance and support Who will pay for it?

Budgeted item

Capital expenditure item

Operations cost What is the funding mechanism?

For design and development

Deployment

Maintenance and support

Upgrade Develop preliminary budget

Staffing requirements

Capital outlay

Operating outlay

Spending timeframe Present budget to management Obtain approval from management

KM System Specifications

Develop KM System Specifications

Architecture

Hardware

Software

Operating System

Browser

Development Platform

Database

Application

Access and control Review software specifications with RFID IT team

Development methodology

Architecture review Review software specifications with users Incorporate feedback on software specifications

Benchmark

Determine Features of ‘Best of Breed’ KM Systems

EX CO based systems

Systems at companies in peer group

Systems acknowledged as ‘Best” by 3rd

parties.

Perform a ‘Gap Analysis’ between ‘Best of Breed’ and KM System to be developed.

Features

Functions

Access and Control Prioritize gaps based on business needs and budget

Absolute necessity

Cannot live without

Nice to have

Incorporate in later versions


KM of 10 1/10/2013

Not needed in our context Incorporate into Design specifications

Choose Appropriate Delivery System for KM-

Sharepoint,

eroom,

@EX CO, etc Develop delivery timeline Obtain approvals to proceed

concept,

timeline,

budget Identify required resources

Internal RFID Team

LGTIT

TSG

External Analysis complete

KM System Design

Review preliminary design specifications for

Integrity

Elegance

Security

Robustness

Extensibility

Referential Transparency

Develop functional specifications, a ‘Blueprint’ for the system

What will it do

How will it do it

What will it look like

Who will use it

How will they use/interact with it

What will it not do

Prepare mock up, data flows, diagrams Review functional specifications with users

Is this what they had specified?

Where are the gaps?

What can be added to make it more useful?

Go back through Analysis and Design to change functional specifications.

Obtain functional specifications signoff from users

Develop models to distill information gathered so far

Convey understanding through information models o User’s conceptual model-

Use cases, user personas o Designers model


KM of 10 1/10/2013

Interface components Relationships to be seen and experienced Details of available objects and classes

o Programmer’s model- review user and designer models with programmer to see what changes are required due to programming environment limitations and constraints.

Define the Information Flow

Define navigational elements from the user’s perspective o Buckets into which the application will be divided o What will fill those buckets o Global, local and hierarchy

Diagram the information organization o Create a thorough Flowchart of the application

Develop prototype based on functional specifications

Working model to test ideas o Key application functions and user interfaces o Big picture look at potential finished product

Test prototype against specifications

Allow stakeholders to provide input

Something more than flowchart shapes that can be tested against specifications

Create Mock ups Wireframes

Use graphic designs and UI concepts to create mockups

Create Wireframes, a skeleton, or schema of the system o Look and feel

Make sure to design for o Functional requirements o Business requirements o User requirements

Incorporate feedback into functional specifications Create detailed design document

A functional spec document about everything we know so far about the system

Allows stakeholders opportunity to review and provide input

Bring application into focus and highlight user functionality Write the design document Obtain approval to proceed

Design complete


KM of 10 1/10/2013

KM System Build

Review functional specifications Evaluate existing Off-the-Shelf KM Systems at EX CO

e Room

Sharepoint

Others

Determine which system will best meet RFID IT COE KM Needs

Gap analysis

Fit analysis

Techniques to accomplish this o Joint Application Design o Rapid Application Design

Determine modifications to be made to meet needs Make required modifications

Build the system

Build system to desired specifications

Tools and platform to be used

PAR methodology

Approved Architectural concepts to be followed Configure the system

Prioritize components

Stage build, test deploy components of the system

Iterative compile, test, debug process

Resolve errors o Design o Logic o Executables o Commands o Prompts o Syntax o Interfaces

Test developed system to ensure it does what it was supposed to do Test objectives should be

Software and system reliability

Software system quality

System performance

Capacity utilization

Develop, design and implement a robust testing plan

Testing methodology- waterfall, incremental, etc.

Black/white box testing


KM of 10 1/10/2013

Prepare and document test scripts Set up test environment Test developed system until acceptable error- level is reached

Acceptable level was decided in consultation with users and system sponsor at the ‘Scope’ stage

Develop unit test plans using product specifications o Develop Test Case scenarios o Test component modules to product

specifications o Identify anomalies to product specifications o Modify System o Re-test modified system o Unit testing complete

Develop integration test plans using product specifications

o Test system integration o Identify anomalies to specifications o Modify system o Re-test modified system o Integration testing complete

Training

Develop training specifications for end users Develop training specifications for helpdesk support staff Identify training delivery methodology (computer based training, classroom, etc.) Develop training materials Conduct training usability study Finalize training materials Develop training delivery mechanism Training materials complete

Documentation

Develop Help specification Develop Help system Review Help documentation Incorporate Help documentation feedback Develop user manuals specifications Develop user manuals Review all user documentation Incorporate user documentation feedback Documentation complete

Pilot

Identify test group Develop delivery mechanism Install/deploy system Obtain user feedback Evaluate testing information Pilot complete


KM of 10 1/10/2013

Deployment

Determine final deployment strategy Develop deployment methodology Secure deployment resources Train support staff Deploy software Deployment complete Post Implementation Review Document lessons learned Distribute to team members Create software maintenance team

Post implementation review complete

rfid project data sheet

Documents