![Page 1: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/1.jpg)
12/05/2004 1
ISO: ISO: intégration intégration Web et Web et gestion documentaire gestion documentaire
Alexander [email protected]
ISO Central Secretariat,Geneva, Switzerland
Documation, Paris, March 2001
![Page 2: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/2.jpg)
12/05/2004 2
INTERNATIONAL ORGANIZATIONINTERNATIONAL ORGANIZATIONFOR STANDARDIZATIONFOR STANDARDIZATION
![Page 3: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/3.jpg)
12/05/2004 3PLPL
PLPLPLPL PROJECT LEADERSPROJECT LEADERS
EXPERTSEXPERTS
TECHNICAL COMMITTEESTECHNICAL COMMITTEESBISBIS
IndiaIndia
ii
DINDIN
GermanyGermany
SNVSNV
SwitzerlandSwitzerland
ANSIANSI
USAUSA
Int. Int. OrgOrg
ISO CENTRAL SECRETARIATISO CENTRAL SECRETARIAT
SS CHCH
TCTCPP
PPPP
PPPPPP
OO OOLL LL
SS
SCSCPP PPPP PPOO OOLL LL
WGWGEE EE
EE EEEE
EgyptEgypt
EOSEOS
MEMBERSMEMBERS
![Page 4: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/4.jpg)
12/05/2004 4
EXTENT OF ISO SYSTEMEXTENT OF ISO SYSTEM
ISO CENTRAL SECRETARIATISO CENTRAL SECRETARIAT
SS CHCH
TCTCPP
PPPP
PPPPPP
OO OOLL LL
SS
SCSCPP PPPP PPOO OOLL LL
WGWG
11 30011 300ISO StandardsISO Standards
128 128 Member Member bodiesbodies
587 587 SubCommitteesSubCommittees
2 020 2 020 Working Working GroupsGroups
771 771 secretariatssecretariatshostedhosted byby
35 countries35 countries
AroundAround 7000 active 7000 active projectsprojects(~200 000 participants)(~200 000 participants)
184 184 Technical CommitteesTechnical Committees
![Page 5: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/5.jpg)
12/05/2004 5
The Central Secretariat in Geneva The Central Secretariat in Geneva
Monitors development of International Standards, clarifies technical points with technical bodies, coordinates the document flow and the planning of meetings
Edits and submits draft International Standards for voting, supervises balloting and publishes the resulting International Standards
Supports and promotes the complete ISO system
![Page 6: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/6.jpg)
12/05/2004 6
DMS backgroundDMS background
Between 1990 and 1996: we were using a DMS in our office environment
1994: we started looking for a DMS for our production (publishing)
Since 1994: we attended all Documationconferences in search of a solution
![Page 7: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/7.jpg)
12/05/2004 7
Great idea … difficult usersGreat idea … difficult users
After Documation’96 we initiated the project “Feasibility study of a DMS for the ISO/CS”
The main point: all functionality should be available from the Internet (to make available the same services to both internal and external users)
ISO/CS internal users (about 150) were to select a system for many external users (> 10 000)
![Page 8: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/8.jpg)
12/05/2004 8
System requirements for the DMSSystem requirements for the DMS
The business requirements- DMS should facilitate distributed business processes
The user requirements- The users do not know what they want until they
“use it”
The IT requirements- DMS must work in the current and future IT
environments
![Page 9: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/9.jpg)
12/05/2004 9
The most important features The most important features for the DMSfor the DMS
Integration with the main production tools
Openness and connectivity with other IT tools
Intranet / Internet capability and availability
Support of SGML and compound documents
Enable workflow and collaboration
![Page 10: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/10.jpg)
12/05/2004 10
The major dream of the IT departmentThe major dream of the IT department
New DMS must be a tool for the users, an open system which can be maintained without a programmer’s assistance
The users shall be able to carry out administration, some customisation and maintenance tasks by themselves
The users should feel ownership on the DMS
![Page 11: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/11.jpg)
12/05/2004 11
General approach for General approach for a feasibility studya feasibility study
Do not trust what you read or hear (from glossy magazines and consultants)
Believe only half of what you see(in demonstrations)
Accept only what you can experienced (i.e. try it for yourself)
Test vendors responsiveness in practice
![Page 12: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/12.jpg)
12/05/2004 12
Project milestonesProject milestones
Definition of the system requirements for the DMS
Selection of two vendors for further investigation
Implementation of prototypes for selected ISO/CS applications
Drafting of a recommendation for the final choice before the end of 1996
![Page 13: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/13.jpg)
12/05/2004 13
Interfaces for the ISO/CSInterfaces for the ISO/CS
ISO policy development
General Assembly, Council, etc.
ISO/CSMemberbodiesTechnical
groups
General public
Standards deliveryStandards development
![Page 14: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/14.jpg)
12/05/2004 14
IT architectural principlesIT architectural principles
Functional (or business process-based) decomposition of the system services to loosely connected components (e.g. DMS servers)
Establishment of well-defined interfaces between these components, other IT services and external resources
Use of workflow as the glue between the components of the system or within a component
![Page 15: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/15.jpg)
12/05/2004 15
Architecture of IT system Architecture of IT system at the ISO/CSat the ISO/CS
ISOPROD
ISOCS
ISODOCISO/CS
PMDB
ISOOnline
ISO
TD
ISOTC
SSGML-based production chain
TWDBSales
![Page 16: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/16.jpg)
12/05/2004 16
Advantages of using Advantages of using of many DMS serversof many DMS servers
Better fit to the real business processes
Increase manageability
Quicker deliverables — business agility
Many users are more comfortable with their “own” DMS server
Creates pressure to improve the IT infrastructure
![Page 17: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/17.jpg)
12/05/2004 17
Challenges of using Challenges of using of many DMS serversof many DMS servers
Need for consistency, i.e. determine and implement coherent decisions and solutions
Parts of the system (DMS, database, OS, desktop, etc.) have to be systematically migrated to be compliant with a vendor-certified configuration
Maintenance of the user community outside DMS
Develop inter-DMS integration (exchange?) tools
![Page 18: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/18.jpg)
12/05/2004 18
LiveLinkLiveLink Intranet (LLI) servers:Intranet (LLI) servers:name,name, # users,# users, volume in volume in gBgB
ISOSTD 100 53Role: Published Standards storeLLI parts: Library, LAPI
ISODOC 2 000 0,8Role: Policy development collaborative toolLLI parts: Library, discussion, workflow
ISOCS 150 5,5Role: Internal storage and ISO/CS quality systemLLI parts: Library, LAPI, workflow
![Page 19: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/19.jpg)
12/05/2004 19
LiveLinkLiveLink Intranet (LLI) servers (2):Intranet (LLI) servers (2):name,name, # users,# users, volume in volume in gBgB
ISOTC 9 000 16Role: Hosting of “intranets” for ISO workgroupsLLI parts: Library, discussion, project, LAPI
ISOPROD 200 2Role: Production storage and automation engineLLI parts: Library, LAPI, workflow
ISOPORTAL 10 0,5Role: Official web-site infrastructureLLI parts: Library, another (XML-based) interface
![Page 20: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/20.jpg)
12/05/2004 20
Ladder of collaborationLadder of collaborationStandardization process is a collaboration between people, applications and business systems
The DMS provides a collaborative environment for distributed groups which have different needs
There are several different patterns in the current configurations — the “steps” of the ladder
Functionality may be added to respond to needs evolution
![Page 21: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/21.jpg)
12/05/2004 21
The “steps” of the ladderThe “steps” of the ladder
Classic web-site
Project web-site
Team dream-web-site
Internet-based business system
![Page 22: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/22.jpg)
12/05/2004 22
Principles which could helpPrinciples which could helpto climb the ladder (1)to climb the ladder (1)
Full administration and control by a group nominee
Use of structural (user allocation) and functional (granting permissions) groups
Connection to the Internet and an Internet Browser are the only prerequisites
API is the preferable way to add extra functionality
![Page 23: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/23.jpg)
12/05/2004 23
Principles which could help Principles which could help to climb the ladder (2)to climb the ladder (2)
Differentiate content between a known user, a self-registered user and a user from the Internet
Implement for the Internet traditional (for OS) maintenance procedures such as:- service announcement, - urgent shutdown, - message that the service is not available, etc.
Consider using a BSP (business service provider) model
![Page 24: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/24.jpg)
12/05/2004 24
No longer any serious No longer any serious technical problemstechnical problems
First: design carefully the architecture of the system (“where” and “how” to use “which”technology or tool)
Second: adapt the business processes to permit automation
Third: move common information and tasks to the infrastructure, e.g. (re)design your corporate LDAP
![Page 25: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/25.jpg)
12/05/2004 25
Classic webClassic web--sitesite
One writer / manager and many readers
Simple library with read-only access
Possibly use of notifications
Example: ISODOC
![Page 26: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/26.jpg)
12/05/2004 26
Project webProject web--sitesite
One manager and many writers / readers
Library with protected documents/folders to keep project-related information and documentation
Task assignment (for advanced projects)
Discussion (depends on group culture)
Example: some internal projects at ISO/CS
![Page 27: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/27.jpg)
12/05/2004 27
Team dreamTeam dream--webweb--sitesite
Role-dependant functions and permissions
Document management is good for ISO 9000 certification
Typical business procedures (e.g. voting) are formalized and executed as workflows
Some automation
![Page 28: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/28.jpg)
12/05/2004 28
InternetInternet--based business systembased business system
DMS is an interface to the business system
Workflow is the business process integration tool
Access to centralized restricted information
Integration with the existing applications
![Page 29: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/29.jpg)
12/05/2004 29
Business process automation Business process automation architecturearchitecture
DMS
Workflows
JavaJpythonApplications
JavaBusiness objects
DMSData repositories
![Page 30: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/30.jpg)
12/05/2004 30
Lessons learnt (1)Lessons learnt (1)
Build user ownership of the DMS
Accept user requirements — some of them may disappear later
Deploy for top management first
Check that your infrastructure is ready for the Web
![Page 31: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/31.jpg)
12/05/2004 31
Lessons learnt (2)Lessons learnt (2)
Necessary to migrate systematically all parts of your IT system, but not everything at the same time
Add general-purpose functionality to the system and convince the vendor to add it to the standard configuration
Add customer-specific functionality to the system only using APIs
![Page 32: ISO: intégration Web et gestion documentaire · IT architectural principles QFunctional (or business process-based) decomposition of the system services to loosely connected components](https://reader034.vdocument.in/reader034/viewer/2022050213/5f5f1796ec35ef1b6d1e3233/html5/thumbnails/32.jpg)
12/05/2004 32
Lessons learnt (3)Lessons learnt (3)
Automation requires a high quality of servicefrom the IT infrastructure and other services —each recovery is too costly
Automation reduces the cost of business practices (old and new). Exceptions complicate (and sometimes preclude) automation, and increase cost of automation