Koneksys provides consulting and software services to connect data silos using the Data Web (Linked Data on the World Wide Web). They create open-source software, promote data integration standards like OSLC, and help clients integrate their data from different sources and systems for improved traceability, transparency, collaboration and analytics. Connecting data using web technologies avoids vendor lock-in and proprietary solutions, allowing organizations to establish relationships between related data to facilitate sharing and decision making across silos.

1. Koneksys
Offering Services to Connect Data using the Next Web
September 2017

2. Creating solutions to connect data silos using
the Web for improved traceability,
transparency, collaboration, and analytics
Providing consulting and research services
Creating open-source software
Promoting the Data Web
Koneksys
2

3. Clients Located in San Francisco.
In business since 2012.
Koneksys
3
And John Deere, Delligatti Associates, Stottler Henke
Associates, and more

4. Koneksys Team
4
Hector Axel Mikhail
JeromeOctavio Victor Brian
Ricardo Dennis Gabriel
Loyda

5. “When you have data coming at you from too many different sources,
you run into a data integration challenge. As near as I can tell, that is what
is causing problems for nearly every major enterprise on the planet. Most
enterprises are siloed, meaning they have independently constructed
data stores, perhaps for each business unit. The problem comes
when these business units want to integrate their
data”
“Benefit we expect from Big Data depends on seamless data integration.
Solving the problem of how to improve data
integration is going to be key in getting the most
benefit from all the data being created”
Why Data Integration Matters
Michael Ralph Stonebraker
Computer scientist specializing in
database research. 2005 IEEE John
von Neumann Medal and 2014 ACM
Turing Award Winner.
5

6. Why Choose the Web for Data Integration?
No license costs
No vendor lock-in
Mature and widely adopted
infrastructure
Abundance of Web
specialists/developers
6
Freedom

7. Benefits of Connecting Data Silos
● Integrated dataset
● Traceability
● Transparency
● Collaboration
● Better decisions
● Knowledge sharing
7
*
* Icon by madebyoliver from www.flaticon.com are licensed by CC 3.0 BY
*
*
*

8. Why is Data Integration Complicated?
Different APIs
Different Data Formats Different Data IDs
Java, REST, query languages
integer, path, guidXML, JSON, CSV, binary
8
Different Data Models
Relational, Graph, Document

9. Why is Data Integration Expensive?
Your Data Your Data Integration
Solution Vendor
Proprietary APIs
and Data Formats
9
$ $

10. Cost of Data Integration
Healthcare: “Data integration problems cost government care providers $342
billion annually”
http://solustaff.com/2015/10/19/the-cost-of-data-integration-challenges/
Business Intelligence: “data integration is a significant cost for any BI project, inthe
implementation phase estimates of almost 80%; compared to the analytics
component of 20%”
https://tdwi.org/articles/2013/08/20/true-cost-of-integration.aspx
Enterprise Resource Planning (ERP): Gartner Says Through 2018, 90 Percent of
Organizations Will Lack a Postmodern Application Integration Strategy
http://www.gartner.com/newsroom/id/3233217
10

11. Current Data Integration Solutions in Engineering
Proprietary data integration solutions
end up being new data silos
11
Product Lifecycle
Management
(PLM)/ Mechanical
Engineering
Application
Lifecycle
Management
(ALM)/ Software
Engineering
Business
Intelligence/
Analytics
Enterprise
Resource Planning
(ERP)/
Manufacturing etc.
Where is the
integration?

12. Current Data Integration Solutions in Engineering
12
Product Lifecycle
Management
(PLM)/ Mechanical
Engineering
Application
Lifecycle
Management
(ALM)/ Software
Engineering
Business
Inteligence/
Analytics
Enterprise
Resource Planning
(ERP)/
Manufacturing etc.
How can I
establish
traceability
How do I know
what is related
to what?
How can I assess
the impact of a
change?
How can I manage
changes/updates?

13. Hypertext + Internet = Web
13
Hypertext System 1 Hypertext System 2
Problem: No Compatibility between hypertext
systems + different protocols to access and
connect documents on the internet (Gopher,
WAIS, etc...)
BEFORE THE WEB
One global hypertext system = Web
One protocol to access and connect documents
WITH THE WEB

14. Private/public
Web
Web Server
Web Server
Requirement
id = 112
text = “Only authorized users shall access the
system”
<!DOCTYPE html>
<html>
<head>
<title>Requirement 112</title>
</head>
<body>
<p>type = Requirement</p>
<p>id = 112</p>
<p>text = “Only authorized users shall
access the system”</p>
</body>
</html>
http://example.com/req112
HTTP
URL
HTML
Doc
14

15. HTTP
URL
RDF
Data
Private/public
Web
Data Web Server
Data Web Server!
Requirement
id = 112
text = “Only authorized users shall
access the system”
Only Change
between
regular Web
and Data Web
15
Requirement
id = 112
text = “Only authorized users shall access the
system”
{
"@context": {
"text": "http://myvocab.com/text",
"id": "http://myvocab.com/id",
"Requirement": "http://myvocab.com/Req"
},
"@id": "http://example.com/req112",
"@type": "Requirement",
"id": "112",
"text": "Only authorized users shall access
the system"
}
http://example.com/req112

16. Linked Data = Next Web = Web of Data = Data Web
Examples
● Engineering: IBM - Jazz applications integrated through OSLC
● Open Initiative: Open Services for Lifecycle Collaboration (OSLC)
● Public knowledge graph: DBpedia
● Improving search results: Schema.org
● Media: BBC Things API
16

17. Data Web Interoperability Example
17
PLM
System
Data Web Server
Data Web Client
RDF
ALM
System
HTTP
GET
HTTP
POST
Reading Data Writing Data
Web-based
Export/Import
Scenario between
data stores
…
"@id":
"http://example.com/req112",
"@type": "Requirement",
"id": "112",
...
Data Web Server

18. Requirement
id = 112
derived_from= “Requirement 113”
"@context": {
"Req113": "http://example.com/Req113"
}
...
"id": "112"
"@derived_from": "Req113"
http://example.com/req112URL
RDF
Data
Reference to
related data
Requirement
id = 113
...
"@type": "Requirement",
"id": "113"
...
http://example.com/req113
HTTP
Navigable
to related data
Link
18
Data Web Integration Example

19. Data Repository 1
Data Web Server 1
Private/
public
Data
Web
Distributed
Data Silos
Data Web Server 2 Data Web Server 3
HTTP
Data Web
Applications
Search Visualize CRUD Analytics Link Creator
Link
19
HTTP HTTP
Link
RDF
RDF RDF
Data Repository 2 Data Repository 3

20. New Data Management Application Architecture
Traditional
App Logic
Integrated Dataset
Specific API
Data
Multiple Data
Sources
HTTP
New
20
Specific API
App Logic

21. Open Services for Lifecycle Collaboration (OSLC)
Standard for Linked Data
RESTful APIs
Domain-specific standards for
data interoperability
Adopted so far mainly for
Application Lifecycle
Management (ALM), systems
and requirements engineering
Open Community
21
Data
OSLC Adapter (Data
Web Server)
REST API (HTTP)
Linked Data (RDF)
Different Data Formats
XML, JSON, CSV, binary
Different Data Models
Relational, Graph, Document
Different Data IDs
integer, path, guid
Different APIs
Java, REST, query languages
Standardized
Web API

22. OSLC Community
We are remaking the OSLC website!
22

23. Summary
Let’s collaborate to make better decisions
Let’s connect data with the Web
Let’s create new data web servers and clients
Let’s create new data web apps
23
Contact us to learn more about our services
at info@koneksys.com