General introduction

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

Agenda • Basics • Approach • Design • "Demo" • "Prototype"

Approach Innovative, unitary design "Prototype" ≡ Security-related and distributed aspects Distributed questionnaire Operating DB "Demo" Remote OpClient Organization ≡ ICT Processes ≡ data Specification ≡ execution User interface ≡ DB Complete functional emulation Org X Local OpClient Front-end Org A Org B SpecClient "Twists" in process specification to boost language power Company servers "Normal" implementation Heavily communication-oriented distributed storage Database access Editing & update Shared platform servers YBN three pillars

Web Classical YBN Rationale • Thin client • Browser • Thin client • Presentation • Local temp storage • Communic. • Fat client • Presentation • Application • Local temp storage • Communic. Excess computing power available • Fat server • Web application • Storage • Fat server • Communic. • Application • Storage • Slim server • Communic. • Storage Other functions to be provided: - Fractal storage redundancy - Proactive recovery Client-server relationships

DB "logical levels" • Business processes • User interface Close link Legacy ERP YBN (–> EAI / SOA) Limited integration "Operations-oriented" DB "Accounting quality" DB Application- oriented DB's Lack of integration

YBN value proposition Implementing process rethinking in a snapshot • "Native" workflow in distributed environment • Users write company or whole value-chain process specifications in an almost natural, spreadsheet-like language • 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

SIMPLIFIED Organization analyst Users Shared nation-wide platform Core routers Official DB Operating DB Common servers YBN architecture Company N Company 2 Scope of YBN "demo" 1 Company Process specification Instance execution Draft process specs Internet Validated process specs Company servers Temporarily surrogated Companies' Operating DBs Ongoing and terminated execution instances Official registrations

Today YBN project status System design [completed] "Demo" [language emulator] "Prototype"w/ distributedaspects Productindustria-lization Product / servicecommercia-lization Search for development andcommercialization partners Partnership agreements

Today's limitations End-users • Lack of really user-oriented process specification languages: continuing need for IT people • Ensuing software development burden: delays, risks, costs, incompleteness, rigidities IT • Layered software: seldom with a comprehensive perspective; often "spaghetti bowl" / "gas guzzler" • Process software conceived in terms of graphs: focus on process "paths" rather than "contents" Software gets slower faster than hardware gets faster Niklaus Wirth

...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 An activity graph(flow-chart, Petri net)...

...generate new data... ...stored 1:1 as a tree... ...to update then the official DB Distributed questionnaire Operating DB Official DB and the activity flow streamlined Full Empty YBN approach The operating activities... Operating activities and business data gathering are dealt with as a sole and undivided matter ≡ Data gathering is optimized and The distributed questionnaire is a process data model+process model The operating DB is an execution instance program, state and archive ≡

Standardized storing Official DB Operating DB • Processes- Specifications / versions- Ongoing execution instances- Terminated execution instances • Registers- Counterparts- Products / services- Agreements / contracts- Company assets • Accounts- Entries- Debit / credit positions- Objects / valuables

YBN features End-users • "Distributed questionnaire" process representation, focused on process contents • User-friendly, spreadsheet-like interface, for both process specification and execution ICT • Compiler-free language, with 1:1 link to database • Immediate distributed execution, with built-in access security and service continuity Simplicity is the ultimate sophistication Leonardo da Vinci

YBN design principles • Green-field / zero-based • Heavy delayering / streamlining • Close link to TLC / truly "ICT" • "Everything the same"≡- Organization ≡ ICT- Process ≡ data- Specification ≡ execution- User interface ≡ database- IT ≡ TLC

Native workflow on distributed architecture Users / users' HW End-to-end inter-company workflow Simpler, inexpensive, more robust, flexible and transparent IT layer, serving users directly Common, simple, natural workflow language, native on the server platform and interfaced to the users' hardware SOA / XML / web services (for external links) SOA / XML / web services (for external links) Shared server platform Action forwarding Access security Storage redundancy • Bandwidth allocation • Phone calls (priority) • VPN's (predefined) • Platform communications (remaining) • Internet (left from above;requisitioned for recovery) Coordinated support by TLC layer + +

Software de-layering Server Client Presentation / input + access security Action forwarding + access security Operating system Redundant storage for service continuity Operating system

"Distributed questionnaire" process representation • Process is specified like a questionnaire • Each line represents a process step • A different actor, wherever located,is responsible for each step • The data to be provided in each step are indicated by names of variables and data collecting mode: New input; DB access; Compute / execute • 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 • Depending on input data, some steps may be skipped

Aux spec matrix detail Comp specs Result Formula Papa Oscar Quebec Oscar * 2 Eco Oscar * 2 Fox Papa / 3 Golf Quebec Spreadsheet-like interface- specification Main flow specification Step NewIn DBaccess Comp 1 Alfa;AIL(Bravo) 2 TCA(Charlie);Delta Vector detail Data list detail Input list detail Aux spec matrix detail Alfa Delta Bravo Charlie Hotel Eco Fox Golf Mike Action Mike <null> GT(XX) NewIn Comp Oscar Papa;Quebec AIL = Acquire Input List; TCA = Table-Conditioned Action

Instance execution Process specification Organization analyst Users Operating DB Official DB Operating DB Sequence Specs Data Registra-tions

Process specification Instance execution Organization analyst Users Operating DB 1:1 1:1 link to database Sequence Data Specs • Execution tables • Main process flow • Detailed data (vectors, lists) • 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)

A number of connected machines... Session / business case XYZ Much more simple user interface for dedicated machine Org A Org B Org C Session / business case XYZ File Edit Format Filter ...or a single PC which emulates all of them... Org A Org B Org C Spec client A Official DB Ctp PS AC ...with the need to develop an articulated and dynamic user interface Oper client group Op Cli1 Op Cli2 Op Cli3 Operating DB OffDB OpDB SpCliA OpCliGr "Demo" - complete functional emulation

Session / business case XYZ File Edit Format Filter Org 1 Org 2 Org N Spec client A Official DB Ctp PS AC Oper client group Op Cli1 Op Cli2 Op Cli3 Operating DB OffDB OpDB SpCliA OpCliGr "All in one screen" user interface (1 PC; or 1 client, 1 server) Main window Menu bar Command bar Org sheets Data groupings Data sheets Data matrices Spec matrices Exec matrices Data groups show / no show

OVERVIEW Remote OpClient Org X Local OpClient Front-end SpecClient Company servers Shared platform servers "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 • 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

General introduction