Send the link below via email or IMCopy
Present to your audienceStart remote presentation
- Invited audience members will follow you as you navigate and present
- People invited to a presentation do not need a Prezi account
- This link expires 10 minutes after you close the presentation
- A maximum of 30 users can follow your presentation
- Learn more about this feature in our knowledge base article
Transcript of Context Accumulation
the incremental process of relating new data to previous data and remembering these relationships, for improved data accuracy.
It is an advanced computing process related to entity analytics in which a system is able to predict relevance and importance dynamically, based on the accumulation and persistence of context produced by ingested data. Algorithms are generated using this contextual data and then employed to determine whether newly introduced data have a place or relationship with historical data.
Once this determination is made, the system then saves and uses this new observation when evaluating other introduced data.
Improving understanding of something by taking into account the things that surround it.
aka the Jigsaw theory of Big Data
- Jeff Jonas, IBM Chief Data Scientist
Situational Context, a general definition:
Observation Space = sum of (available data sources)
= Company + Personal + Social Media + Location Data + Public Records + ? +
Smarter Analytics as “Context Accumulates”:
Moving from batch to (near) real-time
Entity (product) matching to individual interests based upon personal profile
Processing of “big data” information streams to inform operational decision making
Predictive based upon acquired knowledge, heuristics, probability, and other mathematical models
Context Accumulates as a function of the OBSERVABLE data space
Business Value Context
Rate and rank candidate projects
Define roadmap based upon business priorities
Model Process Improvements
Define IT Architecture
Define Business Value
TRUZIGN provides strong dual channel 3 factor
authentication for all users by signing the user’s mobile device. The 3 factors consist of:
you have ? (Mobile phone or tablet device)
you know ? (5 digit PIN Code)
you are ? (GEO location identity)
1. A self-evident or universally recognized truth that requires no proof
2. An established rule, principle, or law.
3. Logic, Mathematics. a proposition that is assumed without proof for the sake of studying the consequences that follow from it.
the same person cannot be in two different places at the same time
Personal Context Accumulation: Axiom
Common NEEDs for BPM:
1. Process Standardisation
2. Knowledge worker productivity
3. Process variation and agility
End-end horizontally integrated process(es) for sharing and reuse
Scanned paper documents
"Case" based workflow management
Paper intensive manual processes
Human Task Workflows
Knowledge worker application
"Window" on the process
Mask process complexity
Rapid time to value for error prone processes
Easy way to find the "happy path" process
Need a better way to implement, support, and change processes: (Key Point: PROCESS AGILITY & VARIATION)
Business opportunity is being lost because leadtime for new projects is too long, largely due to IT request backlog.
There are frequent changes to business policies, and each change has to be made by request to IT.
Line of Business & IT do not communicate clearly with each other, causing friction over requirements and a failure to meet expectations.
Product and service release dates are being missed.
Need to better understand who is performing the work and how. (Key Point: KNOWLEDGE WORKER PRODUCTIVITY)
Manual tasks are not always performed accurately or consistently, but manual workloads are increasing rapidly.
What people are actually doing at any given time is not very clear.
It is difficult for employees to collaborate effectively on the documents they are processing.
The cost & time required to train employees is too high.
Highly-productive employees are overburdened while lower-skilled employees are often idle.
There is limited data to indicate how to reduce bottlenecks caused by work assignments, flows, and escalations.
Need to better manage what work is being done.
(Key Point: PROCESS STANDARDISATION)
Business is being lost due to customer dissatisfaction with slow processing of orders, policies, requests for quote, etc.
Visibility into causes of processing problems is inadequate, and it is difficult to identify which processes could be improved.
Transactions require multiple steps as well as links to different systems, e.g. databases, applications.
Significant time spent identifying and working on exceptions, but the quantity and causes of exceptions are poorly understood.
Service levels are frequently missed, and transactions may actually be lost.
There is no visual documentation of how processes occur, e.g. activities, sequences, decisions.
5W Context Model
Fundamental Requirement for
Situational Based Services
Ability to disambiguate an individual
one can relate to a particular (
) product or service based upon a reason/propensity to buy (
) at a particular time and place (
Product or Service
Loyalty based incentives or offers
Market of ONE specific individual
Product/Service offer becomes relevant at this particular
Product/Service is relevant at this particular
Rationale or propensity to buy
Compelling reason to act
Available systems of interaction / engagement
Confidence in brand and technology
Availability of currency to fund purchase
Ease of transacting
The Future of Work
New Era Computing
Geo Location Services
Systems of Record
Systems of Engagement
Systems of Interaction
5W Context Model
Business Value Context
Market, Industry, Business, Process, Application, IT & Personal Context.
Context Accumulation with Code Halos:
Roadmap to Business Agility PREZI
Cognitive Computer systems
3 Traditional "V"s...
Trusted ? Truth ?
Depends on context
Typical "process" challenges
Current operational “fire”
One Sigma quality ...a 32% error rate
Individual or group heroics make the process work
Poorly understood end-to-end process within LOB
Process workflows operating over e-mail, with spreadsheets etc.
Process Models documented in static “diagramming” and “modelling” tools
Failure to “actualise” the process as documented
Process Volatility – with changes required 3-8 times per year
Investment in existing BPM technologies and formal methodologies like “Lean Six Sigma” not yielding anticipated results
No governance or process lifecycle management
Process Discovery & Analysis
- as easy as "post-it" notes
- execute WYSIWYG
- moved beyond static Visio and Powerpoint diagrams
- transition from static "models" to executable processes