OntologySummit2011: Application and Use Cases synthesis (2LKI)
Ontology, semantics, and knowledge technologies benefit and add value across a very broad spectrum of applications: (2SD0)
- At one end of the solution spectrum, is the low-hanging fruit. Here applications exist with proven benefits, low risk, and real value that can be realized with off-the-shelf tools and solutions used by subject matter experts, business users, and consumers. Simple solutions to the right problem can bring great value. (2SD1)
- In the mid-range we find categories of applications that address bigger needs and have characteristics best addressed with knowledge-centric approaches. Case examples exist that show solution patterns delivering substantial value. Multiple providers of technologies (products, services) and services have expertise in these areas. Mid-spectrum applications often involve: (2SD2)
- Discovering, connecting, integrating and interpreting information of different kinds, from multiple sources, and at varying scales (2SD4)
- Aggregating, connecting and orchestrating services, applications, processes, and families of systems (2SD5)
- Modeling and automating decision rules and decision-making processes (2SD6)
- Methodologies that realize value from different stages of the solution life cycle. (2SD7)
- At the other end of the spectrum are cutting edge opportunities, tough problems, and grand challenges that cannot be solved with current information technology approaches. At the frontier, problem characteristics, including issues of scale, systemics, autonomics, security, dynamics, extent and depth of knowledge, and complexity of reasoning as well as time and mission criticality, etc. demand capabilities only possible or economically feasible with knowledge technologies, semantics, and ontologies. When using case examples to make the case for ontology, place emphasis first and foremost on communicating the value to the business. Our template for summarizing the value delivered includes the following topics: (2SD8)
- Challenge What is the problem or opportunity being addressed? What is its significance? (2SD9)
- Solution What is the solution? What role do knowledge technologies, semantics, and ontology play in it? (2SDA)
- Screen shot and key features Give a flavor of the use of ontology in this case. (2SDB)
- Benefits What measures were used to demonstrate the value delivered? (2SDC)
- Resource What commercial or non-profit entities provided technology products and services used in the case example? Case examples reveal that ontologies solve a broad range of real-world problems. Summit sessions presented twenty case examples of mainstream applications where knowledge technologies, semantics, and ontology are being applied and delivering benefits. This represents only a small sample of available deployments. (2SDD)
The following lists the case examples documented in the supporting materials, and highlights value delivered.. (2SDE)
Apple SIRI (2SDF)
Ontology-driven virtual assistant: as a next generation assistance paradigm for smart consumer applications: Ontology-based UI focuses is on task completion, with intent understanding via conversation in context, and where the virtual assistant learns and applies personal information. Key roles for ontology include interface intelligence, unification of domain and declarative task models, semantic autocompletion, and service orchestration. (2SDG)
Smart knowledge-driven citizen-centric services separate the know from the flow, data, and function; everything is a knowledge model and a business rule, no exceptions; business users create rules, application modelers create and configure services, administrators deploy applications. The design is the model, is the application, is the documentation. Fast, lean development. dynamic context-aware processes, operational savings, flexibility, and greatly improved life cycle economics (2SDI)
Cambridge Semantics (2SDJ)
Do it yourself data exploration and analytics a semantic collaboration platform for operational intelligence and advanced analytics; deploys rapidly, integrates with tools that professionals already use, and enable teams to quickly connect all of the data sources and model the workflow needed to and analyze data, investigate processes, and answer questions; empowering subject matter experts and business users leads to 2-10x improvement in time to solution plus flexibility to evolve it rapidly and cost-effectively. (2SDK)
Connotate (2SDL)
Do-it-yourself semantic agents to discover, aggregate, analyze & report information; anything pointed to in a browser, you can teach a semantic agent to monitor and intelligently process. Agents speak HTML, XML, RSS, RDF, PDF, database and Excel. Mash-ups create new data by element and schema, in time periods, across sources and time periods, and put data into context. Productivity increases can exceed 2X. (2SDM)
Department of Homeland Security (2SDN)
(a) DHS infrastructure taxonomy; (b) Complex event modeling, simulation and analysis (CEMSA) (2SDO)
Ontologies resolve semantic differences across sources of information and domains allowing reasoning and inference to identify for example, for a given emergency situation, default actions, resources, roles/ responsibilities of relevant agencies. (2SDP)
EDM Council (2SDQ)
Standardization of terms and definitions for financial services and a pilot test of the semantic resource as applied to mortgage-backed securities. Automated semantic tagging, indexing and systemic publishing of factual reference data is feasible systemically and vastly more consistent, accurate, and cost-effective than pre-financial meltdown processes. PIlot test demonstrates the viability of tagging financial contracts using standard semantics and identifiers in support of risk analytics. (2SDR)
Franz | AMDOCS (2SDS)
Ontologies for telecom customer relationship management: semantic technology enabled, closed-loop, self-learning system lets customer service see what happens, when it happens, understand what it means to the business, and take action and enforce business policy automatically, intelligently and in business real time. Eliminated system and agent diagnosis time; decrease average handling time; improve agent and customer satisfaction. (2SDT)
IBM & U Maryland (2SDU)
Dr. Watson Project After Jeopardy, Watson goes to med school: Previous applications of expert systems and AI in medicine have been impressive, but limited. In the post-Watson era potential for broad enhancement of medical practice seems likely, if challenges can be overcome. (2SDV)
Innovative Query (2SDW)
(a) Content intelligence and smart applications; ontology integrates structured and unstructured information, improves search, discovery and collaboration; and filters information to user need and context. (b) Semantic BI for blogging: ontology used to semantically index information from structured and unstructured sources, both internal and external, enabling custom alerts, and more precise and rapid response to social media. (2SDX)
Mayo Clinic (2SDY)
Relationships among biomedical ontologies and classifications: Ontologies bridging and interrelating medical and scientific disciplines will play an integral role in the evolution of medicine from practice-based evidence to evidence-based practice. (2SDZ)
Model-driven Development (2SE0)
Architectures and ontologies for business value: Architectures and ontologies are mutually supportive. (2SE1)
Recognos Financial (2SE2)
Better information access with semantics for search, navigation, query & question answering case example from the mutual fund industry: Concept-based, faceted navigation uses semantic analysis of content to reduce cognitive burden for users including extract specific data from tables (e.g., the amount of a specific type of fee). Question answering allows users to express questions in their own words and get the right answer. Automated semantic indexing and analysis is more consistent, accurate, and cost-effective than comparable manual methods. Since, 80% of all data in organizations is unstructured, semantic applications within government and industry are massive. (2SE3)
Revelytix (2SE4)
DoD knowledge-centric information webs & process interoperability: DoD attempted to build a data warehouse to connect HR systems and information across the Department. After 11 years and $1B dollars expended, had nothing to show for it. After everything else had failed, they decided to build a semantic information web to connect existing systems of record using a common domain ontology connected to relational mapping and source (metadata) ontologies. After 9 months (and very modest dollars expended), DoD demonstrated a solution. (2SE5)
Sallie Mae (2SE6)
Integration of multiple systems from multiple companies: ontology provides unifying model across diverse systems while supporting tailored views and facets of this subject matter to different subject matter experts. (2SE7)
Sandpiper (2SE8)
Semantic technology in rental product marketing: ontologies power semantic search and search engine optimization to improve user experience and business outcomes. (2SE9)
Semantic Arts (2SEA)
Applying semantics to enterprise systems - Proctor and Gamble case study: Ontologies provide a practical way to integrate research findings across disciplines. (2SEB)
Top Quadrant (2SEC)
Valuing the harvest from using ontologies (a medley of case examples): Ontology used for enterprise vocabulary management, semantic-xml message building, data integration, and enterprise architecture. Graph data model (subject, predicate, object) provides canonical data for connecting data silos into information webs. (2SED)
Trigent Software (2SEE)
(a) Ontology and rules provide rapid natural language understanding; (b) Ontology and rules drive mass customization of vehicles -- Ontology and rules driven configurator and custom manufacturing process identifies best parts, assemblies, availabilities, and plant schedule to meet promised delivery date error-free. Fast rules engine handles 600K rules with average of 24 condition elements and can configure a truck in under 10 seconds on a laptop. (2SEF)
Visual Knowledge (2SEG)
Policy-driven compliance, risk, and change management pilot: captures regulatory mandates, maps them to policy documents, then to semantic models defining schemas, processes, and decision-making rules, to deployed operational systems and procedures, to analytics that track, assess, and report human and system behavior and ensure compliance. (2SEH)
zAgile (2SEI)
Model-driven framework for process deployment with extreme traceability: Executable knowledge models specify project goals, roles, methods, activities, deliverables, quality, and resources and enable tool interoperability, process automation, and end-to-end traceability at the level of individual concepts. Result can be up to 3-10X faster concept to deployment, with up to 3-10X reduction in project costs. (2SEJ)
Where do case examples show knowledge technologies, semantics, and ontology add value? (2SEK)
Patterns of value delivery that emerged from these case examples have several dimensions worth noting: (2SEL)
- Knowledge-centric approaches and ontology-driven solutions were associated with both development and operational gains in performance and lifecycle economics. (2SEM)
- Knowledge technologies and knowledge-centric approaches to knowledge work accelerated the time from idea (or need) to a solution. (2SEN)
- Knowledge technologies enabled new methodologies and concepts of operation that resulted in significant productivity gains. Fewer people could accomplish the same work significantly faster and do-it-yourself empowerment of subject matter experts and business users resulted in huge improvements in cycle times and service levels. (2SEO)
- Knowledge technologies enabled new solution concepts Knowledge-driven solutions could be documented where the design is self-documenting, the execution is self-explaining, the solution can be easily modified, simulated and updated, and total cost of ownership decreased by more than 50% compared to current IT solutions. (2SEP)
- Knowledge technology based solutions were more flexible and agile than IT-based solutions when it comes to making changes and evolving capabilities. (2SEQ)
- Knowledge technologies and ontology were used to add intelligence to the user interface (UI) in order to increase relevance, helpfulness, utility, and pleasure as experienced by the user. (2SER)
Case Study Summaries (2SES)
Each Case Study participant was asked to provide a grid on one slide, outlining the business problem, the solution, key features (or screen shot) and business benefits. The aim of this was to be able to identify what sort of "Ontology" this was in terms of the application framework once this was completed, and what metrics (if any) were avilable to determine the business benefits. (2OR6)
Each Case Study (2OR7)
- Challenge (2OR8)
- What business problem the Ontology set out to address (2OR9)
- Solution (2ORA)
- What we mean by ontology in this case e.g. application, conceptual model (2ORB)
- Screen shot or key features (2ORC)
- Give a flavor of the ontology (2ORD)
- Benefits (2ORE)
- What metrics if any were used to demonstrate the benefits of this ontology. (2ORF)
Virtual assistant as a next UI paradigm Apple Siri From the following presentation: Harvesting the Business Value of Ontologies: Recent Case Examples (2SCZ)
Challenge (2S91)
- If your computer were really smart (2S92)
Key Ontology Features (2SA2)
- Ontology-driven virtual assistant: as a next generation assistance paradigm for smart consumer applications: (2SA3)
- Ontology-based UI focuses is on task completion, with intent understanding via conversation in context, and where the virtual assistant learns and applies personal information. (2SA4)
- Key roles for ontology include interface intelligence, unification of domain and declarative task models, semantic autocompletion, and service orchestration (2SA5)
Solution (2S9B)
- Virtual assistant leveraging semantic technologies (2S9C)
- Domain and Task models (2S9D)
- Speech + Semantics + APIs (application interfaces) (2S9E)
Business Benefit (2S9F)
- Virtual assistants that complete tasks for you (2S9G)
- Usability (2S9H)
- Context sensitivity for services (2S9I)
Integration of Multiple Systems from Multiple Companies YefimZhuk, Sallie Mae (2OT1)
Challenge (2ORH)
- Multiple systems and sources of knowledge in different parts of the enterprise, owned by different communities of practice. (2ORI)
- Gaining time and commitment from subject matter experts to ensure completeness of the model. (2ORJ)
- Different groups see different shades of meaning and application for similar terms, in different contexts. (2ORK)
- Needs a unifying approach supporting local views (2ORL)
Key Ontology Features (2ORM)
Solution (2ORN)
- Facilitation of knowledge gathering using ontology engineering methods. (2ORO)
- Formal ontology notation for single ontology, while presenting views and facets of this to subject matter experts. (2ORP)
- Curation of the ontology (2ORQ)
Benefits (2ORR)
- Best use of subject matter experts¡¯ time and resources (2ORS)
- Curatorship of Enterprise Semantic Architect ensures quality, consistency and completeness of the ontology (2ORT)
- Collaboration in industry standardization efforts (e.g. EDM Council), via common semantics (2ORU)
- Ensures that the knowledge captured at Sallie Mae is taken forward to industry-wide standardization efforts which we can then use (2ORV)
Standardization of Terms and Definitions for Financial Services MikeBennett, EDM Council (2OT2)
Challenge (2ORX)
- Industry standardization of terms and definitions (2ORY)
- Integration of multiple sources and feeds into disparate database structures (2ORZ)
- Even a small financial firm has 50 ¨C 100 separate systems each with its own data model (2OS0)
- Tried: XML (MDDL); UML data models (ISO 20022) (2OS1)
- Industry response: ¡°We need semantics (2OS2)
Key Ontology Features (2OS3)
- Domain model (2OS4)
- UML Tool based Editor (2OS5)
- OWL Constructs (2OS6)
- Spreadsheet View (2OS7)
- Simple Diagram View (2OS8)
Solution (2OS9)
- Semantic (conceptual) model of terms, definitions (2OSA)
- OWL/ODM metamodel with UML tool (2OSB)
- Adapted for readability (2OSC)
- Present draft to business SMEs for input (2OSD)
- Explained format to SMEs as set theory (2OSE)
- Reviewed via webcast, direct input to model (2OSF)
Benefits (2OSG)
- SMEs understood the format and contributed new knowledge on e.g. exotic structured finance (2OSH)
- Answered industry call for standardization of meaning (2OSI)
- Industry applications including mapping, master data models, messaging (2OSJ)
- Atomic building blocks means flexibility in defining novel financial products (2OSK)
- Traction from regulators, for tagging of documents at source, reporting, systemic risk oversight (2OSL)
Semantic Tech in Rental Product Marketing JimRhyne, Sandpiper (2OT3)
Challenge (2OSN)
Key Ontology Features (2OSQ)
- Complex, multi-entity ontology (2OSR)
- Lots of restriction axioms, not subclass hierarchy (2OSS)
- Classification and realization part of application process (2OST)
Solution (2OSU)
Business Benefit (2OSY)
- Current project is a pilot - stay tuned (2OSZ)
- Progress in discussions with Search Engine Providers (2OT0)
Ontology and Rules provide rapid Natural Language Understanding ChuckRehberg, Trigent Software (2OT5)
Challenge (2OT6)
- Parsing natural language is complex (2OT7)
- Identify specific text within a large set of a (2OT8)
- documents that contains the same or similar (2OT9)
- meaning as a given natural language description (2OTA)
- of interest. (2OTB)
- How do we use and grow Ontologies? (2OTC)
- How do we map Natural Language to Ontology? (2OTD)
Key Ontology Features (2OTE)
- Language-independent Ontology (2OTF)
- The Ontology represents concepts, instances, relationships, roles, generalizations, instantiations, characteristics, attributes, and units of measure (2OTI)
Solution (2OTJ)
- Given some Natural Language text (one or more sentences or questions), parse and map the various valid constructs to semantic items in an Ontology (we call this mapping the "meaning" of the text) (2OTK)
- Generate (non-statistical) "reader rules" to recognize all combinatorics of language constructs that represent the mapping as having an equivalent ¡°meaning map¡± (2OTL)
- Apply the high speed "reader rules" to a large corpus of text to identify possible meaning matches (2OTM)
- Verify text identified as having the same ¡°meaning map¡± (2OTN)
- Generate a report showing the information found and how it relates to the original text along with hyperlinks (2OTO)
Business Benefit (2OTP)
- Changing the Dictionary has immediate effect (2OTQ)
- Changing the Ontology has immediate effect (2OTR)
- Ontology grows with use (2OTS)
- Ontology curation is widely leveraged (2OTT)
- Sifts through a large amount of text to find and return just what you are looking for without the need to read the individual files yourself. (2OTU)
Ontology and Rules provide Mass Customization of Vehicles ChuckRehberg, Trigent Software (2OTY)
Challenge (2OTZ)
- Mass Customization of Trucks and Busses (2OU0)
- Customers describe the desired vehicle by selecting the base model and a wide range of attributes (e.g. vehicle length) and features (e.g. number of exits) (2OU1)
- Combinatorics of parts and assemblies (2OU2)
- More than 480,000 combinations of parts, assemblies, and locations for a given vehicle ¨C Each vehicle off the assembly line can be one-ofa- kind. (2OU3)
- Given an order that may never have been previously built, identify the best set of parts, assemblies and component locations for the vehicle (the Vehicle Configuration) (2OU4)
- Different parts and assemblies will be available at different plants at different times. So, need to select a configuration that can be built at a plant prior to the promised delivery date. (2OU5)
Key Ontology Features (2OU6)
Solution (2OU9)
- Solution Ontology (2OUA)
- Ontology defined both bottom-up and top-down (2OUB)
- Solution Rules Engine (2OUC)
Business Benefit (2OUL)
- Ontology allows quick and reliable specification of new variations (2OUM)
- Rules are specified in terms of the Ontology (incl. features and attributes) (2OUN)
- Changes in Ontology and Changes in Rules can take effect immediately (or at designated times and plants) (2OUO)
Content Intelligence and Smart Applications GregBardwell, Innovative Query Inc. (2OUR)
Challenge (2OUS)
- Content Intelligence: the ability to generate insights to improve business outcomes with content. (2OUT)
Key Ontology Features (2OUU)
- Proactively serving up needed information (2OUV)
Solution (2OUW)
Business Benefit (2OUY)
- Improved search, discovery and collaboration (2OUZ)
- Pushing the right information to the right users to do their job (2OV0)
- Improved information and content publishing (2OV1)
- Mashups of and with content for new classes of BI and publishing applications (2OV2)
- Unlocking information for actionable insights (2OV3)
Semantic BI for Blogging Bardwell - see above (2OV4)
Challenge (2OV5)
- Utilize data obtained from news, (2OV6)
- social media, and internal sources (2OV7)
- Optimize and personalize search (2OV8)
- Work with open sources (2OV9)
- Respond quickly to chatter (2OVA)
Key Ontology Features (2OVB)
- see above (2OVC)
Solution (2OVD)
- NLP and Semantic index for unstructured sources (2OVF)
- Custom scoring/alerts for results (2OVG)
- Authoring tools to expedite content creation and analysis tasks (2OVI)
Business Benefit (2OVJ)
- Save time on analysis of content (2OVK)
- More complete intel from text sources (2OVL)
- Quicker and more precise responses to social media (2OVM)
- Better and faster content creation (2OVN)
Valuing the Harvest from using Ontologies RalphHodgson, TopQuadrant (2OVQ)
Challenge (2OVR)
- Complex information spaces (2OVS)
Key Ontology Features (2OVV)
Solution (2OVZ)
- Enterprise Vocabulary Management (2OW0)
- Flexible solutions for managing business vocabularies in support of content delivery, search, navigation, data integration and disambiguation of terms (2OW1)
- Semantic-XML Message Builder Workbench (2OW2)
- Enables XML-based data exchanges that are specific to the local context while remaining compliant with industry and enterprise standards (2OW3)
Business Benefit (2OW8)
- Canonical data - Subject-Predicate-Object Triples (2OW9)
- Identifiers - Composition Construct for Aggregations (2OWA)
- Schemas are also expressed in Triples and can be queried using same query language - SPARQL (2OWB)
- Evolvability¨Cschemas, vocabs and datasets can readily evolve (2OWC)
Architectures and Ontologies for Business Value CoryCasanave - Model Driven Solutions (2OWP)
Challenge (2OWQ)
- Fragmented architecture domains (2OWR)
- Business and systems financial architecture for a government agency (2OWW)
- Understand the business needs in terms of business processes, information and business services (2OWX)
- Specify the data, technology processes and SOA services of the systems to meet business needs (2OWY)
Key Ontology Features (2OWZ)
Solution (2OX2)
- Requirements, processes & services are less often captured as ontologies (2OX3)
- Yet the ontology of a domain must include these viewpoints (2OX4)
- Better support for other viewpoints with architecturally focused ontologies would provide increased value (2OX5)
- Links between architectural an ontological tools provides a bridge between these related approaches (2OX6)
Business Benefit (2OX7)
- Architectures and ontologies are mutually supportive (2OX8)
- Ontological precision and the ability to federate ontologies brings value to architecture (2OX9)
- Architectural tools can provide a more friendly way to express ontological information to stakeholders (2OXA)
- Automating parts of systems from models and ontologies using MDA (model driven architecture) provides the much of the value without runtime overhead (2OXB)
- The strategic opportunity is to bring all of this information into focus for the enterprise ¨C we are only starting to do so. (2OXC)
Model-driven Framework for Process Deployment, eXtreme Traceability SanjivaNath, ZAgile (2OXI)
Problem (2OXJ)
- Project Mgmt is Costly (2OXK)
- Siloed Tools (2OXL)
- Distributed Environment (2OXM)
- Lack of Formal Processes (2OXN)
- Lack of Traceability (2OXO)
Solution (2OXP)
- Integration of People, Tools and Processes (2OXQ)
- Application Integration Platform & Connectors (2OXR)
- Methodology and Process Modeling (2OXS)
- Integrated BI (2OXT)
- Model-driven Architecture (2OXU)
Technology (2OXV)
- Semantic Technology-based Architecture (2OXW)
- Domain and application-specific Ontologies (2OXX)
- Jena-based Framework (2OXY)
- RESTFul Interfaces (2OXZ)
- SPARQL support (2OY0)
Business Benefit (2OY1)
- Reduced Costs and Increased Visibility (2OY2)
- Effective Collaboration (2OY3)
- Efficient Project Tracking (2OY4)
- Rapid Knowledge Access (2OY5)
Applying Semantics to Enterprise Systems - Proctor and Gamble Case Study DaveMcComb, Semantic Arts (2OYV)
Challenge (2OY7)
- Large consumer products company (2OY8)
- Looking for ways to integrate research findings across disciplines (2OY9)
- Over 10,000 researchers in nearly 100 disciplines (2OYA)
- Each discipline has its own language (2OYB)
- Traditional key word search not useful when searching across domains (2OYC)
- Problem compounded by departure of many key researchers (retirement, re-organization, etc.) (2OYD)
Key Ontology Features (2OYE)
Solution (2OYI)
- Enterprise Ontology for the R&D domain. (2OYJ)
- Interviews with retiring researchers. (2OYK)
- Re-use of terms from GIST upper ontology (2OYL)
- Semantic Wiki built based on ontology (2OYM)
- Two additional domains have been modeled (feminine care and baby care) and both reinforce the original abstractions (2OYN)
- Additional domains planned for this year (2OYO)
Business Benefit (2OYP)
- Of the nearly 600 classes in the R&D ontology (2OYQ)
- Most R&D data is findable without needing to know the specialized dialect of each subdomain. (2OYU)
Ontologies and CRM for Telecoms BillGuinn, MikeLurye, SusanMacCall, Amdocs (2OYX)
Challenge (2OYY)
- Customer Relationship Management (2OYZ)
Key Ontology Features (2OZ4)
Solution (2OZ8)
Business Benefit (2OZB)
- Eliminates system and agent diagnosis time (2OZC)
- Provides consistent and efficient call handling (2OZD)
- Increases agent and customer satisfaction (2OZE)
- Anticipated benefits based on 100K actual accounts assessment: (2OZF)
- AHT reduction of 10-15 (2OZG)
Additional Case Studies The Case Studies below come from the following presentation: Harvesting the Business Value of Ontologies: Recent Case Examples (2SCY)
Do it Yourself Data Exploration Cambridge Semantics (2S9L)
Challenge (2S9M)
- When events trigger action, researchers and analysts examine the data. Combining information from multiple spread sheets and databases is tedious and manual. Desktop tools do not know the categories and properties expressed by column (or row) headings. Moreover, for IT to create a new database or data warehouse is time-consuming, costly, and assumes that all requirements are knowable in advance.. (2S9N)
Key Ontology Features (2S9O)
- Sever based semantic model (2S9P)
- Used to provide drop down selections in spreadsheets (2S9Q)
- Filters and lenses for populating and visualizing data (2S9R)
Solution (2S9S)
- Knowledge-centric solution for data exploration links source data from spreadsheets, files, or database tables to a standard (semantic) model stored on a server. (2S9T)
- Theres an app for that. (2S9U)
- Works on desktop or via browser. (2S9V)
- Selecting data to add to a spreadsheet is a pull-down menu option. Filters apply easily. Numerous lenses for visualizing data (2S9W)
Business Benefit (2S9X)
- Focuses on ease of use for end-users with tools they know how to use; minimum IT involvement, if at all. (2S9Y)
- Rapid and low-cost to solution (hours/days), vs. slow and time-consuming for RDBMS, data warehouse, or manual (2S9Z)
- Flexibility in the face of inevitable change: rapid, low-cost, incremental modification vs. time-consuming costly, and difficult revision of conventional stores. (2SA0)
- "Low-hanging fruit" for many agencies and programs (2SA1)
Better access with semantic search, navigation, query & question answering Recognos Financial (2SA7)
Challenge (2SA8)
- Mutual fund industry rules change requires consumer friendly interactive access to 250,000 mandated plan documents. (2SA9)
- While the industrys trade association has developed a standard taxonomy for key topics, (a) buyers do not know industry jargon, (b) often related data is not adjacent to topic, and (c) buyer lacks a way to hone in on answers to questions. (2SAA)
- Conventional DB and CMS approaches are labor intensive, error prone and costly to update. (2SAB)
Key Ontology Features (2SAC)
- Structuring of unstructured data (specifically, documents in the Edgar database) enhances citizen access to information (2SAD)
- Example is a Mutual Fund Prospectus that was filed with the SEC. (2SAE)
- Uses a taxonomy associated with Mutual Funds. It is widely used and was developed by the Investment Company Institute. (2SAF)
- User screen displays the actual filed document with the selected field value highlighted within the body of the document itself. (2SAG)
- The taxonomy maps to the point in the document where the topic occurs. (2SAH)
- This mapping is automated. Semantic processing of the text results in clean data (as received directly from the source of the data) with all standard data elements identified and extracted from the document without being touched by human hands (no data entry). Automated semantic extraction maintains the integrity of the data. (2SAI)
Solution (2SAJ)
- Knowledge-centric solution semantically analyzes and indexes the database corpus using deep linguistics and domain knowledge to extract data, link information to topics, and find answers to questions. (2SAK)
- Consumers can navigate by topic (faceted search) pose questions in natural language, and query data contained in documents as though it were a database. (2SAL)
Business Benefit (2SAM)
- Concept-based faceted navigation uses semantic analysis of content to reduce cognitive burden for users including extract specific data from tables (e.g., the amount of a specific type of fee). Question answering allows users to express questions in their own words and get the right answer. (2SAN)
- Automated semantic indexing and analysis is more consistent, accurate, and cost-effective than comparable manual methods. Since, 80% of all data in organizations is unstructured, applications within government and industry are massive. (2SAO)
Knowledge-centric information webs & process interoperability Revelytix (2SAP)
Challenge (2SAQ)
- DoD attempted to build a data warehouse to connect HR systems and information across the Department. After 11 years and $1B dollars expended, had nothing to show for it. (2SAR)
- "Weve tried everything else and failed." - DoD CTO for Business Mission (2SAS)
Key Ontology Features (2SAT)
- Uses a domain ontology in conjunction with a number of other ontologies: (2SAU)
- These are mapped via relational mapping ontologies, to individual relational databases. (2SB0)
Solution (2SB1)
- Built a semantic information web that connected existing systems of record using a common domain ontology connected to relational mapping and source (metadata) ontologies (2SB2)
- After 9 months (and very modest dollars expended), DoD had demonstrated a solution (2SB3)
Business Benefit (2SB4)
- Semantic information web ontology patterns enable federated search, information sharing, and SQL-like querying across heterogeneous business databases. (2SB5)
- Basic to very complex analytics and reporting across all systems become end-user generated queries that reference analytics ontology(s) connected to the domain ontology. (2SB6)
- Development, extension, and upgrades to the system of systems is rapid, incremental, iterative, non-invasive and low-risk. (2SB7)
Do-it-yourself semantic agents to discover, aggregate, analyze & report information Connotate (2SB8)
Challenge (2SB9)
- Agencies need to find, monitor, aggregate and make sense of information from a great many sources across the web as well as internally within government. (2SBA)
- The manual effort involved can consume 25-45% of an analysts time. (2SBB)
- Also, it is costly to custom program and update searches and analytics as needs change (2SBC)
Key Ontology Features (2SBD)
- Several components of the solution: (2SBE)
- Agent Studio (2SBF)
- Agent Library (2SBJ)
- Agent Portal (2SBO)
- Integrates with a number of other applications (email, spreadsheet, database, alerts, mobile apps etc.). (2SBP)
Solution (2SBQ)
- Intelligent semantic software agents to access, harvest, tag, and standardize information that are easy to create by anyone and can be shared and reused. (2SBR)
- Train agents to capture site information, content elements, and take action to extract specific data, capture files, define schemas. (2SBS)
- Agents "speak" HTML, XML, RSS, RDF, PDF, database and Excel. (2SBT)
- Mash-ups create new data by element and schema, in time periods, across sources and time periods, and put data into context (2SBU)
Business Benefit (2SBV)
- 360 degree views on topics, issues, etc. combining information from internal and external sources including web pages, blogs, local news, message boards, social media, databases, email, intranets, enterprise applications, etc. (2SBW)
- Productivity improvements from automated gathering, monitoring, and alerting for needed information events that is 24/7/365 or other frequency (2SBX)
Smart knowledge-driven citizen-centric services BeInformed (2SBY)
Challenge (2SBZ)
- Permitting site synthesizes requirements, processes, and information across multiple jurisdictions and 14 independent institutions into a unified user experience. (2SC0)
- Immigration site helps new arrivals solve varied problems of relocation. It combines information, and decision logic from 12 agencies into an easy to use single point of service delivery. (2SC1)
Key Ontology Features (2SC2)
- Integrates process flow, applications and sources, via a layer of knowledge models (2SC3)
- Citizen centric: (2SC4)
Solution (2SCA)
- Knowledge-centric solution separates the know from the flow and the function to create declarative applications configured by users with semantic models of legislation, knowledge, processes, data, and UI. (2SCB)
- The core infrastructure consists of an ontology, which is enriched with business rules. (2SCC)
- All functions use the same ontology, e.g., semantic search, information access, automated decision making, decision support, and dynamic processes. (2SCD)
Business Benefit (2SCE)
- Open knowledge as a service bridges the gap between government and citizens and facilitates effective cooperation between independent institutions both public and private. (2SCF)
- Provides automated decisions and decision support; means for agencies to manage their knowledge / rules; ability to quickly adapt to external events / implement new legislation; improved decision making, guaranteed compliancy, less errors; improved service delivery to the public; and substantial cost reductions. (2SCG)
Policy-driven compliance, risk, and change management ''Visual Knowledge' (2SCH)
Challenge (2SCI)
- Global financial services firm was $600B behind in M&A because it could not keep up with compliance requirements. Knowledge to track and report regulatory mandates comprehensively across the business was fragmented in separate documents, systems, and data stores, thus slow, prone to error, and difficult to change. (2SCJ)
- "Our only solution is to add more belly buttons, which means committing thousands of people to compliance." (2SCK)
Key Ontology Features (2SCL)
- Risk, compliance and policy-driven processes include situation awareness, exceptions, fraud, case management, emergency response. (2SCM)
- Semantic technologies map the external (legal) requirements to policies (expressed as documents) to semantic models (defining information structures, processes, and user responsibilities) to system infrastructure, behaviors, and analytics (measures of performance). This provides visibility and traceability from mandate to manifestation to compliance reporting. (2SCN)
- Uses semantic technologies to specify, interrelate, and manage knowledge at the level of individual concepts and relationships independently of its source artifact, whether this knowledge comes from: (2SCO)
- Documents via natural language or visual language understanding, and semantic tagging; (2SCP)
- Models including file formats, database schema, object models, content semantics, policies, event and process models, context models, domain ontologies, etc. (2SCQ)
- Behaviors including software source libraries, directories, frameworks, methods, subroutines, objects, semantic agents, and infrastructure standards. (2SCR)
Solution (2SCS)
- Knowledge centric collaborative solution that captures all of the regulatory mandates, maps them to policy documents, then to semantic models defining schemas, processes, and decision-making rules, to deployed operational systems and procedures, to analytics that track, assess, and report human and system behavior and ensure compliance (2SCT)
Business Benefit (2SCU)
- Development of knowledge-centric compliance solution requires fewer resources, is more rapid, less costly, quicker to show value. (2SCV)
- Operation of knowledge-centric solution requires less labor, is more reliable and less error prone. (2SCW)
- Maintenance and upgrades are less costly and time consuming. Assessing impact of changes on documentation, systems, and procedures is more automated. Change management and version control is automated. (2SCX)
-- maintained by the Track-2 champions ... please do not edit (2LKJ)