Download Is there any use for Knowledge Acquisition and Modelling?

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts
no text concepts found
Transcript
Knowledge Acquisition and Modelling
Practical use in projects
Lecture Knowledge Acquisition and Modelling course
Utrecht University (30-03-2015)
© 2012 | The Logic Factory
Curriculum Vitae Roel van den Broek
• Sinds 2008: Business Consultant en lid directie van The Logic Factory
• 2001 – 2008: Management consultant bij Capgemini Consulting (IT & Consultancy bedrijf)
• 1999 – 2001: Knowledge Analyst bij Bolesian (gespecialiseerd in Artificial Intelligence and
Knowledge Based solutions)
• 1995 – 1999: Universiteit van Amsterdam: Artificial Intelligence.
– Computational intelligence and artificial life. ‘Development of LeDoux’ dual-route architecture in
artificial neural networks using genetic algorithms’.
• Eerste project gedaan in de verzekeringswereld, maar daarna snel gaan werken voor
bedrijven met echte “assets”, zoals fabrieken, treinen, vrachtwagens, schepen of
vliegtuigen.
© 2012 | The Logic Factory
History
Focus
Offices
Facts
Originate from Bolesian and Capgemini
Background in Logistics, Manufacturing, Off-shoring and Artificial Intelligence
Quintiq (Supply Chain Planning & Optimisation)
The Logic Transport (TMS & Mobile solutions)
HQ in ‘s-Hertogenbosch, the Netherlands
Development Center in Ahmedabad, India
Founded 2007, 100% privately owned by founders
Currently 35 employees
Partners
Selected
Customers
© 2012 | The Logic Factory
3
© 2012 | The Logic Factory
Our Project Methodology: combining best of both worlds
Initial
contact
Initial
meeting
Scope
discussion
(SoW)
Vision
presentation
Scan
Contract
signing
Project
Maintenance
GO LIVE
QBA
document
Project
kick-off
70%
version
100%
live SCP&O
Initiation
Analysis
Modeling
Iterative
Implement
development
Post go-live
support
Phase 0
Phase 1
Phase 2
Phase 3
Phase 5










Process analysis
Knowledge analysis
Constraint definition
Interface design
Infrastructure setup
Defining optimisers
System modelling
Interface
development
Knowledge
completion
Test plan
preparation
Modeling
optimisers
Phase 4











© 2012 | The Logic Factory
95%
version
Interactive testing
Iterative modelling
Integration testing
Implementation plan
preparation
Testing optimisers
Acceptance optimisers
Training
User test
Parallel test
Acceptance test
Going live


Supporting planners
Monitoring KPIs
CommonKADS
© 2012 | The Logic Factory
CommonKADS vs. Our Project Methodology (1)
• CommonKADS Principle ‘Not just
mining from an expert’s head, but
about constructing different aspect
models of the knowledge’
• CommonKADS Principle ‘First
concentrate on the conceptual
structure, then on the programming
details’
© 2012 | The Logic Factory
• Main goal of the analysis phase.
• First set up the planning decisions (the
structure) and the business rules. Then
move to solutions design
CommonKADS
•
vs.
CommonKADS Theory ‘KBS construction entails the construction
of a number of models that together constitute part of the
product delivered by the project’
Our Project Methodology (2)
•
•
•
CommonKADS Theory‘The number and level of elaboration of
models depends on the specific project context’
•
CommonKADS element ‘Organisational model’ -> supports
analysis of an organisation.
•
CommonKADS element ‘Task model’ -> tasks performed in the
organisational model
•
•
•
•
–
–
–
CommonKADS element ‘Agent model’ -> describes the agents
(capabilities, preferences, etc.)
CommonKADS element ‘Knowledge model’ -> implementation
independent description of the knowledge involved in a task
•
CommonKADS element ‘Communication model’ -> describes the
transaction between agents
•
CommonKADS element ‘Design model’ -> describes the design of
the system to be constructed
© 2012 | The Logic Factory
Application = software + model description(s) +
additional documentation
Although one methodology per project one
should always pragmaticaly decide what to use
or not.
Our deliverables are: QBA, QID, QAD, QDD
Quintiq Business Analysis (QBA)
Context, Business Goals, KPI Matrix (Organisation
Model)
Overview Planning decisions (Task Model)
Details Planning decisions
•
•
•
•
Business rules (Knowledge Model)
Use Cases (Agent Model)
UI (Communication Model)
Quintig Interface Document (QID)
– Interaction between all related applications
(Communication Model)
•
Quintiq Design Document (QDD) and the
model (.qproject) (Design Model)
A day in the life…
© 2012 | The Logic Factory
Travel or work from home
© 2012 | The Logic Factory
Work with the customer or the project team?
© 2012 | The Logic Factory
Work in a (internal) project, or full time detached
© 2012 | The Logic Factory
Customers and cases
© 2012 | The Logic Factory