- ISO 15926 Primer
- ISO15926 Standard Structure
- IDS-ADI Coordination Structure
- IDS-ADI Infrastructure
- The AVALON Project
- Core Modelers Projects
- Core Implementers Projects
- Core Compliance Project
- Core Methodology Project
- IDS-ADI Matrix Master (login)
- IDS-ADI Matrix 1,2,3 activity
- IDS-ADI Matrix 4 activity
- IDS-ADI Matrix 8 activity
- IDS-ADI Part3 Harmonization
- IDS-ADI BIDG (aka Handover Guide)
- IDS-ADI Proteus Project
POSC Caesar FIATECH IDS-ADI Projects
Intelligent Data Sets Accelerating Deployment of ISO15926
Realizing Open Information Interoperability
IDS-ADI Project Infrastructure
This page exists to describe the scopes, organization, deliverables and status of the IDS-ADI Projects.
For the technology infrastructures associated with IDS-ADI Project Execution and with ISO15926 Implementation refer to the Technology Infrastructure Page
The IDS-ADI Projects, like the ISO15926 standard itself, are in several inter-related parts. These workscopes range from creation of the standard docouments for ISO publication, data modelling, reference data creation, implementation software and services, training, and support for special interest groups around business areas & engineering disciplines and around extending modelling approaches and technologies.
This page therefore itemizes all the workscopes and deliverables as undertaken by IDS-ADI Projects and provides each with a current status, a responsible party and links to further on-line information about each project / task / sub-project.
IDS-ADI relies on cooperation between member organizations and individuals. Individual groups teams and tasks are largely autonomous subject only to steering inputs and compliance with core deliverables. The coordination is achieved through the following :-
Regular Coordination Meetings
- Steering Group - Meets Ad-Hoc, quarterly or to address specific issues.
- General Management Coordination - Meets 8:30am-10:00am EST Thursdays (15-20 regular attendees)
- Modeling, Methodologies & Content - Meets 8:30am-10:00am EST Mondays (6-10 regular attendees)
- Implementation & technology - Meets 8:30am-10:00am EST Wednesdays (4-8 regular attendees)
- Other Core IDS-ADI & Matrix Sub-Projects - Ad-Hoc to suit team needs.
Editorial - Add appropriate links & bookmarks.
Coordination Documents & Information Sharing
- IDS-ADI Overall Plan - Defines overall schedule and dependencies of main IDS-ADI activities and deliverables.
- IDS-ADI Project Roster - Defines the existing membership / invitations / distributions / contacts of each group, team or meeting.
- IDS-ADI Notes of Meeting - Notwithstanding other documents and deliverables created and shared by each team, notes of meetings are recorded here.
- IDS-ADI In-Person Exchanges - Comprising many part-time "volunteers" and few full-time individuals collaborating at many locations around the world, there are few IDS-ADI-specific events arranged in one location. Occasions when company, consortium or industry conferences or other events are organized are treated as opportunties for sub-sets of IDS-ADI teams to meet in-person, and IDS-ADI meetings and workshops are often appended to such events.
- IDS-ADI Shared Document Repository - In addition to these wiki pages, all deliverables of IDS-ADI teams are published in an on-line document repository.
- IDS-ADI On-Line Collaboration - In addition to these wiki pages, extensive use is made of Wiki-page discussions, Topic-specific wiki discussion pages, e-mail and real-time messaging in order to progess ongoing project activities and resolve current issues.
For help with wiki (TRAC), file repository (Subversion) and file client (TortoiseSVN) software refer to Technology Infrastructure pages - or direct to sub-pages when available.
Editorial - Add appropriate links & bookmarks.
(Whole Elephant WBS - In progress)
Project Work Scopes
- IDS-ADI Steering Group
- IDS-ADI General Management Coordination
- IDS-ADI Core Deliverables
- IDS-ADI Modeling, Methods & Content Team
- IDS-ADI Implementation & Technology Team
- IDS-ADI Matrix Sub-Projects
- SIG's (Special Interest Groups)
IDS-ADI Steering Group
The IDS-ADI Steering group currently consists of :- Robin Benjamins (Chair), Magne Valen-Sendstad, Onno Paap, Adrian Laud, Manoj Dharwadkar, Julian Bourne and Ian Glendinning.
Periodically co-opted into the steering group for liaison purposes are representatives of POSC Caesar, FIATECH or other industry intiatives :- eg Mark Palmer, Ric Jackson.
The scope of the steering group is to set policies and priorities for IDS-ADI projects, to resolve any conflicts or issues arising between IDS-ADI Projects, or with external initiatives, that cannot be solved by ongoing management coordination. A further role of the steering group is management reporting (eg of deliverable progress and budgets) to the sponsoring consortia and their member organisations.
IDS-ADI General Management Coordination
(Coordination of all IDS-ADI Projects, ISO Standard publication process, Liaison with and representation at industry conferences and other industry standardization initiatives.)
IDS-ADI Core Deliverables
(Modelers & Impelementors per below - plus ISO Standard Parts, Compliance Spec, Public Communications / Web-pages / Presentations ....)
IDS-ADI Modeling, Methods & Content Team
Also known simply as the "Modelers". Team Lead is Ian Glendinning.
itemize and link to main activity streams
IDS-ADI Implementation & Technology Team
Also known simply as the "Implementors". Team Lead is Julian Bourne.
itemize and link to main activity streams
IDS-ADI Matrix Sub-Projects
itemize all identified sub-projects, identify and link to active sub-projects.
SIG's (Special Interest Groups)
SIG's by definition have special interests that are not limited to the current scope of IDS-ADI and ISO15926. SIG's have scopes that are above and beyond IDS-ADI and ISO15926, but which may overlap significantly with IDS-ADI and ISO15926.
For POSC Caesar SIG's refer to [wiki/Sig PCA SIG's Page].
SIG's which overlap significantly with IDS-ADI and ISO15926 are :-
- PCA-MMT-SIG (Modeling, Methods & Technology SIG)- which overlaps significantly with both IDS-ADI-Modelers and IDS-ADI-Implementors, but which has additional interests beyond the current IDS-ADI and ISO15926 scopes and industrial applications, in the areas of researching formal logical methods and their potential exploitation.
- PCA Industrial Domain SIG's - some of which overlap significantly with IDS-ADI Matrix Sub-Projects, where the interests of business-domain-specialists or subject-matter-experts coincide. Currently such PCA-SIG's are relatively inactive, and it is foreseen that they may evolve from the equivalent active IDS-ADI Matrix Sub-Project team membership, to form the domain expert SIG's required for ongoing quality management of RDS/WIP content defined by ISO15926 Part 6.
The general understanding is the PCA-SIG's with scopes overalpping with IDS-ADI and ISO15926 will create and document original metarials only where over and above IDS-ADI and ISO15926 scopes, and collaborate with and make referenece IDS-ADI where they overlap.
All below holding extract from previous pages - subject to further editing and/or moving to other subsidiary pages
These are Standing web conference meetings:
8:30am-10:00am EST Thursdays - general meeting (15-20 regular attendees) 8:30am-10:00am EST Mondays - modeling, methodologies & content meeting (6-10 regular attendees) 8:30am-10:00am EST Wednesdays - implementation and technology meeting (4-8 regular attendees) Core ADI-IDS & Matrix Projects
All core project and subproject documentation is kept in the "Subversion" Document Repository.
Folders are organised according to project / content / subject types. These include scopes / specifications / methodologies / notes-of-meetings / action-lists etc. (ie folders are NOT organised according to file types.)
The projects include
Core IDS-ADI Projects ... documentation common across all sub-projects (organised primarily by core project area - management / modelling / content / implementation, etc) Matrix-Sub-Projects ... documentation specific to each sub-project. Wiki pages should link to individual documents or folders directly wherever relevant. Browsing and accessing any and all documents is via your browser links to documents and via the repository link above.
Uploading new and revised folders and documents should be done using the Tortoise SVN Client (See XXXX for SVN set-up and use). Notification of updates is recommended by RSS subscription to the Timeline page. (Ref XXXX)
Status of Deliverables
The status of some of the infrastructure-related deliverables undertaken by this umbrella group are detailed on the IDS-ADI Infrastructure Status Page.
Compliance (or compliancy) is the subject of an IDS-ADI project that is developing a [ComplianceSpecification?].
Status: some business and engineering collateral available
Next Release: no date set
Engineering Lead: Gord Rachar
Business Lead: Jeff Bonnell
Technical Lead: Julian Bourne
Business, technical and engineering users all require focused introductory collateral. Some of this collateral exists but is not necessarily easy to find or collected all in one place. Some of this collateral is at a far too detailed or abstracted level to be generally useful to someone first coming into contact with the standard.
There is substantial engineering collateral available in different forms, from power point presentations to web sites. This material addresses the underlying need for ISO 15926 as a neutral model and definitional space (reference data library); and it also addresses how to go about (methodology).
What may be missing is a guide for the kind of engineer who deals in concrete things, not in abstract concepts; and secondly for the kind of engineer who has the right sort of outlook to bridge the gap between the concrete and the less totally abstract, but is not interested in the completely abstract.
Gord Rachar recently joined the IDS-ADI group (2008-06-26) - with an Engineering and Technical Writing background from the EPC arena, he has signaled that he will have a go at tackling this material.
Some of the high level engineering collateral targeted at explaining the need for ISO 15926 can be re-purposed for business; and there is some existing collateral under the FIATECH ADI project site addressing business and technical at a (very) high level. Jeff Bonnell has volunteered to lead the initiative in providing a more complete business view of the standard.
Technical introductory collateral targeted at implementation is thoroughly scant at this stage: there is a need to provide almost a "path" or "plan" to integrated ISO 15926 into vendor tools in a meaningful way. Julian Bourne had volunteered to lead that initiative.
Status: somewhat operational
Next Release: manually operational, end of June 2008
Following Release: fully operational, no date set
Lead: Julian Bourne
The RDS/WIP project provides the software and Internet-accessible services for publishing both the standard and contributions to its associated reference data library. There are two exposed forms of this data: one is intended for machines, expressed in OWL/RDF and delivered via SPARQL; the other is intended for humans and is presented using HTML in a web browser.
The existing deployment is only partially operational: it does not reach the necessary mark in aspects such as performance and standards conformance and is missing machine-driven mechanisms for submitting new contributions. Also, its internal structure is far too rigid and requires a great deal of coordination between different parties to effect change.
The next stage (RDS/WIP 1.0) will be to move that solution to a more robust and faster technical framework, dropping the support for direct editing in the interim, but adding much more flexible support for incorporating bulk contributions, with some administrator intervention.
The following stage (RDS/WIP 2.0) will be to provide a completely automated path to incorporate bulk contributions and the administration features needed to manage that; along with recreating a direct editing feature for ISO 15926 data only.
The main advantage of the revised platform, apart from performance and conformance, is that it will allow any RDF to be published, which leaves a great deal of flexibility in structure and representation - allowing the structures and representation to change quickly and without much need for coordination. It also provides a lower barrier to entry when starting a collaborative project to harmonize standards against one another. These features are inherent in the architecture and to the technology choices and will be available from the outset of RDS WIP 1.0.