28
General introduction AEROGRAFO S.a.s. / the YBN team May 2011 YBN≡ Your Business Networked [www.ybnd.eu]

© 2011 – p.0 of 27 A EROGRAFO S.a.s. / the YBN team General introduction A EROGRAFO S.a.s. / the YBN team May 2011 YBN ≡ Your Business Networked []

Embed Size (px)

Citation preview

© 2011 – p.1 of 27AEROGRAFO S.a.s. / the YBN team

General introduction

AEROGRAFO S.a.s. / the YBN team

May 2011

YBN≡Your Business Networked[www.ybnd.eu]

© 2011 – p.2 of 27AEROGRAFO S.a.s. / the YBN team

• Basics

• Approach

• Design

• "Demo"

• "Prototype"

Agenda

© 2011 – p.3 of 27AEROGRAFO S.a.s. / the YBN team

YBN three pillars

"Demo"Complete functional

emulation

Org B

Org A

"Prototype"Security-related and distributed aspects

Org X

Remote OpClient

SpecClient

Local OpClient

Front-end

Company servers

Shared platform servers

Innovative, unitary design

Distributed questionnaire

Operating DB

Organization ≡ ICTProcesses ≡ dataSpecification ≡

executionUser interface ≡ DB

Approach

"Normal" implementation

Database access

Editing & update

Heavily communication-oriented distributed storage

"Twists" in process specification to boost

language power

© 2011 – p.4 of 27AEROGRAFO S.a.s. / the YBN team

Excess computing power available

Other functions to be provided:- Fractal storage redundancy- Proactive recovery

Rationale

Client-server relationships

Thin client• Browser

Fat server• Web

application• Storage

Web

Thin client• Presentation• Local temp

storage• Communic.

Fat server• Communic.• Application• Storage

Classical

Fat client• Presentation• Application• Local temp

storage• Communic.

YBN

Slim server• Communic.• Storage

© 2011 – p.5 of 27AEROGRAFO S.a.s. / the YBN team

DB "logical levels"

Application- oriented DB's

"Accounting quality" DB

"Operations-oriented" DB

Legacy ERP YBN

Lack of integration

Lim

ited in

tegra

tion

• Business processes• User interface

(–> EAI / SOA) Clo

se lin

k

© 2011 – p.6 of 27AEROGRAFO S.a.s. / the YBN team

"Native" workflow in distributed environment

• Users write company or whole value-chain process specifications in an almost natural, spreadsheet-like language

Implementing process

rethinking in a snapshot

YBN value proposition

• Specs are directly executed- No compilation, code generation, superfluous SW layer, traditional development burden- Important functions provided built-in: end-to-end process integrity; activity tracking / certification; access security; service continuity; reduction of the processing load of the clients' information systems

Users are provided with the same action independence, level of control and intervention flexibility on business processes which they enjoy today in writing with a word processor, or in performing computations with a spreadsheet

© 2011 – p.7 of 27AEROGRAFO S.a.s. / the YBN team

Scope of YBN "demo"

YBN architecture

Company 2

Company N

Shared nation-wide platform

Core routers

Common servers

Temporarily surrogated Companies' Operating DBs

Company 1

Process specification Organization

analyst

Instance execution

Users

Company servers

Official DB

Operating DB

Internet

Draft process specs

Validated process specs

Ongoing and terminated execution instances

Official registrations

SIMPLIFIED

© 2011 – p.8 of 27AEROGRAFO S.a.s. / the YBN team

YBN project status

Product / servicecommercia-lization

Productindustria-lization

"Prototype"w/ distributedaspects

"Demo" [language emulator]

Search for development andcommercialization partners

Partnership agreements

System design[completed]

Today

© 2011 – p.9 of 27AEROGRAFO S.a.s. / the YBN team

• Basics

• Approach

• Design

• "Demo"

• "Prototype"

Agenda

© 2011 – p.10 of 27AEROGRAFO S.a.s. / the YBN team

End-users

IT • Layered software: seldom with a comprehensive perspective; often "spaghetti bowl" / "gas guzzler"

• Lack of really user-oriented process specification languages: continuing need for IT people

• Process software conceived in terms of graphs: focus on process "paths" rather than "contents"

• Ensuing software development burden: delays, risks, costs, incompleteness, rigidities

Software gets slower faster than hardware gets faster

Niklaus Wirth

Today's limitations

© 2011 – p.11 of 27AEROGRAFO S.a.s. / the YBN team

An activity graph(flow-chart, Petri net)...

...updates a different data graph (Entity-Relationship scheme)

Official DB

Operating activities and business data storage are matters tackled in a fundamentally different way

"Original sin" of IT

© 2011 – p.12 of 27AEROGRAFO S.a.s. / the YBN team

...generate new data...

Distributed questionnaire

...stored 1:1 as a tree...

Operating DB

The operating activities...

...to update then the official DB

Official DB

The distributed questionnaire is a process data model + process model

The operating DB is an execution instance program, state and archive

Data gathering is optimized and and

the activity flow streamlined

FullEmpty

Operating activities and business data gathering are

dealt with as a sole and undivided matter

YBN approach

© 2011 – p.13 of 27AEROGRAFO S.a.s. / the YBN team

Operating DB

Standardized storing

Official DB

• Registers- Counterparts- Products / services- Agreements / contracts- Company assets

• Accounts- Entries- Debit / credit positions- Objects / valuables

• Processes- Specifications / versions- Ongoing execution instances- Terminated execution instances

© 2011 – p.14 of 27AEROGRAFO S.a.s. / the YBN team

End-users

ICT • Compiler-free language, with 1:1 link to database

• "Distributed questionnaire" process representation, focused on process contents

• Immediate distributed execution, with built-in access security and service continuity

• User-friendly, spreadsheet-like interface, for both process specification and execution

Simplicity is the ultimate sophistication

Leonardo da Vinci

YBN features

© 2011 – p.15 of 27AEROGRAFO S.a.s. / the YBN team

• Basics

• Approach

• Design

• "Demo"

• "Prototype"

Agenda

© 2011 – p.16 of 27AEROGRAFO S.a.s. / the YBN team

•Green-field / zero-based

•Close link to TLC / truly "ICT"

•Heavy delayering / streamlining

YBN design principles

•"Everything the same"≡- Organization ≡ ICT- Process ≡ data- Specification ≡ execution- User interface ≡ database- IT ≡ TLC

© 2011 – p.17 of 27AEROGRAFO S.a.s. / the YBN team

Native workflow on distributed architecture

SOA / XML /web services

(for external links)

SOA / XML /web services

(for external links)

Simpler,inexpensive,more robust,flexible and transparentIT layer,serving usersdirectly

Users / users' HW

End-to-end inter-company workflow

Common, simple, natural workflow language, native on the server platform and interfaced to the users' hardware

Shared server platform Action forwarding

Access security

Storage redundancy

+ +

Coordinatedsupport byTLC layer

Bandwidth allocation•Phone calls (priority)•VPN's (predefined)•Platform communications

(remaining)•Internet (left from above;

requisitioned for recovery)

© 2011 – p.18 of 27AEROGRAFO S.a.s. / the YBN team

Server

Action forwarding+ access security

Redundant storagefor service continuity

Operating system

Client

Presentation / input+ access security

Operating system

Software de-layering

© 2011 – p.19 of 27AEROGRAFO S.a.s. / the YBN team

"Distributed questionnaire" process representation

Process is executed by filling the questionnaire

• The responsible of each process step, wherever located, inserts the indicated data by inputting the values of the indicated variables

Process is specified like a questionnaire

• Each line represents a process step

• Depending on input data, some steps may be skipped

• The data to be provided in each step are indicated by names of variables and data collecting mode: New input; DB access; Compute / execute

• A different actor, wherever located, is responsible for each step

© 2011 – p.20 of 27AEROGRAFO S.a.s. / the YBN team

Spreadsheet-like interface - specification

Vector detail

Alfa

Hotel

Mike

Data list detail

Delta

Eco Fox Golf

GT(XX)<null>

ActionMike

Aux spec matrix detail

Charlie

Alfa;AIL(Bravo)

TCA(Charlie);Delta

DBaccessNewIn Comp

Main flow specification

1

2

Step

Input list detail

Bravo

NewIn Comp

Oscar Papa;Quebec

AIL = Acquire Input List; TCA = Table-Conditioned Action

Aux spec matrix detail

Comp specs

OscarPapaFormulaResult

Oscar * 2QuebecOscar * 2EcoPapa / 3FoxQuebecGolf

© 2011 – p.21 of 27AEROGRAFO S.a.s. / the YBN team

Spreadsheet-like interface - execution

Alfa.Hotel

Delta

Inst1 Inst2Instance Inst3

Alfa.Mike

Bravo

abc

|open|

ttt

|open|

xyz

|open|

ppp

|open|

wwt

|open|

qqq

|open|

Step 2

Step 1||||

NewIn

Comp |close|

|close||close|

Inst3.Bravo

3Oscar

3 6Papa Quebec

|close|Inst1.Bravo

1227

Oscar12 2427 54

Papa Quebec|close|

Inst2.Delta

12 2 12Eco Fox Golf

18 3 1830 5 30

|close|

© 2011 – p.22 of 27AEROGRAFO S.a.s. / the YBN team

Operating DB

Process specification

Organization analyst

Instance execution

Users

Operating DB

Official DB

Sequence

DataSpecs

Registra-tions

© 2011 – p.23 of 27AEROGRAFO S.a.s. / the YBN team

1:1 link to database

Process specification

Organization analyst

Instance execution

Users

Operating DB

Sequence

Data

Specification tables• Main process flow• Auxiliary specification

matrices (e.g. decisional)• Detailed data (vectors, lists)

Database tables• Main process flow• Auxiliary specification

matrices (e.g. decisional)• Detailed data (vectors, lists)

Execution tables• Main process flow• Detailed data

(vectors, lists)

1:1

Specs

© 2011 – p.24 of 27AEROGRAFO S.a.s. / the YBN team

• Basics

• Approach

• Design

• "Demo"

• "Prototype"

Agenda

© 2011 – p.25 of 27AEROGRAFO S.a.s. / the YBN team

"Demo" - complete functional emulation

...with the need to develop an articulated and

dynamic user interface

...or a single PC which emulates all of them...

Org C

Org B

Org A

A number of connected machines...

Session / business case XYZ

OrgA

OrgB

OrgC

File Edit Format Filter

Official DB

OffDB OpDB SpCliA OpCliGr

Ctp PS AC

Operating DB

Session / business case XYZ

Oper client group

OpCli1

OpCli2

OpCli3

Spec client A

Much more simple user interface for

dedicated machine

© 2011 – p.26 of 27AEROGRAFO S.a.s. / the YBN team

Session / business case XYZ

Org 1 Org 2 Org N

File Edit Format Filter

Official DB

OffDB OpDB SpCliA OpCliGr

Ctp PS AC

Spec client A

"All in one screen" user interface (1 PC; or 1 client, 1 server)

Operating DB

Oper client group

OpCli1

OpCli2

OpCli3

Main window

Menu bar

Org sheets

Data groupings

Data groups show / no show

Data sheets

Data matrices

Spec matrices

Exec matrices

Command bar

© 2011 – p.27 of 27AEROGRAFO S.a.s. / the YBN team

• Basics

• Approach

• Design

• "Demo"

• "Prototype"

Agenda

© 2011 – p.28 of 27AEROGRAFO S.a.s. / the YBN team

"Prototype" - security-related and distributed aspects

Access security• Systematic encryption of all remote communications and

out-of-company storage (with possible extension to in-company communications and storage)

• Systematic authentication of people and machines accessing a(nother) resource

• Shared platform of servers, to reduce the operating load of company information systems

• Unified operating authentication in company front-end

Org X

Remote OpClient

SpecClient

Local OpClient

Front-end

Company servers

Shared platform servers

OVERVIEW

End-to-end process integrity• Interleaved timeouts to control performance of expected

people inputs and machine operations• Intrinsic data duplication in action forwarding along the

process course

Service continuity• Duplicated authentication resources• Systematically redundant storage

- Fixed triplet of company servers- Run-time "fractally" allocated triplets of common servers

• Data recovery of malfunctioning company server after reset• Proactive data recovery of malfunctioning common server

on other platform servers, before machine reset / reuse