ENTERPRISE KNOWLEDGE

BUSINESS SOLUTIONS/PROCESS-BASED ORGANIZATIONS

• Data Warehouse Alliance
• Balanced Scorecard Process
• Intelligent Enterprise

Questions companies must answer in the process of defining and planning their business:

• What is our mission, in 25 words or less?
• What are our core competencies and skill sets?
• Where do we make money, and where do we lose it?
• What support and infrastructure do we have in place?
• To whom do we lose deals or customers?
• What growth rate are we seeking?
• What financial resources are available?  How readily?
• What is our business model?  Do we want to keep it?

• Zachman Institute
• Enterprise Architecture - A Framework
• Enterprise Architecture - The Issue of the Century
• Zachman's Framework (original)
• Zachman's Framework( pdf)
• General Enterprise Architectures

BUSINESS INTELLIGENCE

• Data Warehousing Information Center
• The Data Mining Institute
• The Meta Data Coalition
• The OLAP Council
• Knowledge Discovery & Data Mining Foundation
• IBM Business Intelligence

• DB2 Universal Database Home Page
• DB2 Service and Support
• IDUG Solutions Journal
• Transaction Processing Performance Council
• IBM Benchmarks

• Internet.com's Electronic Commerce Guide
• IBM E-Business Solutions
• Electronic Commerce Resources

• Association for Information and Image Management
• Lotus Development Corp. Knowledge Management
• IBM Content Management
• Knowledge Management World
• Enterprise Knowledge Architectures

• Relationships

• How IP and Web technologies are changing business

ERP Resources

• ERP Market Share - 1998
1. SAP - 37%
2. Otherrs - 28%
3. Oracle - 13%
4. JD Edwards - 7%
5. PeopleSoft - 9%
6. Baan - 6%

• Ptak, Carol. (1999). ERP: Tools, Techniques and Applications for Integrating the Supply Chain. Boca Raton, FL: St. Lucie Press

• Lead by looking
• Lead by example - others are watching
• Lead with questions
• Lead from below
• Pair up for problem solving
• Slow down to speed up
• Paint pictures
• Support synergy
• Manage meetings
• Improve by inspection
• Work with tehbest
• Work yourself out of work.

• People are far more important than technology
• Understand teh technology that you are desigining for
• Humility is a qualification
• Requirements are a requirement
• Requirements rarely chnage, but your understanding of them often does
• Read constantly
• Reduce the coupling withn yoru software
• Increase the cohesion within your software
• Expect to port yoru software
• Accept that change happens
• Never underestimate the need to scale
• Performance is only one of many design factors
• Manage the seams
• Shortcuts always take longer
• Trust no one
• Show that your design works in practice
• Apply known patterns
• Learn each model's strengths and weaknesses
• Apply several models to a given task
• Educate your audience
• A fool with a tool is still a fool
• Understand teh entire process
• Test often and early
• Document your work
• Technology changes, fundamentals don't.

• Design for real work
• Don't get concrete too quickly
• Avoid innovation for innovation's sake, but don't be a slave to fashion
• Strive for efficient interaction
• Try out the interface for real work

• A tool is not a process
• Expect the groupto pass through a sequence of forming, storming, norming, and performing when it adopts new tools
• Ask "What's in it for us?," not "What's in it for me?"
• Tools affect quality directly, productivity indirectly
• Weigh the price of the tool against the costs of not using it
• CASE Tools
• Use CASE tools to design, not just to document
• No one wants to go through an idle change exercise just because someone else had a cool idea
• Align the team on the spirit of the method and the tool, not on "The Rules"
• Keep the information in the tool alive
• Fitting Tools into Teams
• Support the new tools with training in the underlying approaches, such as testing concepts or project estimation principles
• When comes to preneting project fiascoes, the best defense is a good offense.

• Understand the problem domain
• Make sense of the data
• Make sense of the processes
• Identify application interfaces
• Identify the business events
• Identify the data transformation scenarios
• Map information movement
• Apply technology
• Test, Test, Test
• Consider performance
• Define the value
• Create maintenance procedures
• Method or madness?