130 likes | 266 Views
S1000D User Forum Futuroscope, May 2003. Complications in the Re-Use of DM Stand-in: Svante Ericsson. The story. There is a product (i.e. Materiel) … and there are a few variants … and there are several customers … who all work in their own environment …
E N D
S1000D User ForumFuturoscope, May 2003 Complications in the Re-Use of DMStand-in: Svante Ericsson
The story... • There is a product (i.e. Materiel) … • and there are a few variants … • and there are several customers … • who all work in their own environment … • and who partly speak different languages.
The story... • Furthermore, there is a colleague of mine, Mr M, … • who has a customer, Mr C, … • who - in turn - has a customer, Mr C2.
Mr C2A Mr C2B PublIssue 001 PublIssue 001 UpdatedUpdated PublIssue 002 PublIssue 003 Update Different update cycles for every Mr C2 PublIssue 002
So what does Mr X and Mr C do? data modules idstatusMr C2A content
Information items per data module • For instance, • Applicability • Version • All located in <idstatus> • Might be customer specific • <idstatus> – <content> split!
Change marks per Mr C2 Mr C2A Mr C2B PublIssue 001 PublIssue 001 UpdatedUpdated PublIssue 002 PublIssue 003 PublIssue 002 Update
Change marks per Mr C2 Mr C2A Mr C2B Issue 001 Issue 001 Issue 002changes Issue 003changes Issue 002changes
Different terminologi Mr C2A Mr C2B PublIssue 001 PublIssue 001 Screw driver B Screw driver A PublIssue 002 Screw driver A PublIssue 003 PublIssue 002 Screw driver A Screw driver B
So what do Mr X and Mr C do? Mr C2B ILS-db Tool n Tool n - A – Screw driver ATool n - B – Screw driver B
Filtering on <applic>, etc? • Model not quite stable today • Mr C doesn’t want to include all Mr C2 specifics into the data modules • There should be an intergalactic identity for every single ”data module”!!
Mr C XX-X-00-00-00-00X-000X-X XX-X-00-00-00-00X-000X-X Mr C2A Mr C2B ! We’re all talking to each other!
Murphy’s Law If something can go wrong, it will go wrong! Thanks for your attention!