POSCCAESAR Association

1
POSC/CAESAR Association

• Data Model Status Plans for Year 2000
• 30th September 1999
• Presented by Jan Sullivan

2
Status of co-operation

• EPISTLE core model V3
• One model
• Replaces AP221 ARM models, POSC/CAESAR models
• Maintained on a CASE tool, from which EXPRESS and
  documentation is generated (Word and HTML)
• POSC/CAESAR data model workgroups replaced by
  EPISTLE activities
• Version management
• Model development and use
• Issue resolution

3
Status of deliverables

• EPISTLE Core Model V3.0 delivered July 13th
• replaced planned Version 1.0
• ISO 15926 Part 2 CD documents signed off 15
  September
• ECM V3.1 delivered 21 September
• fixes for documentation errors
• includes HTML documentation
• Training course preparation 26/27/28th October
• Synergy data model review
• RDS upgrade to browse reference data in V3

4
Plans for next year
Man days

• Data model maintenance
• Reference data system maintenance
• Development proposals

85
80
500
Total
665
5
Y2000 Data model maintenance

• Issue log process
• Two releases (June December)
• minor changes
• response to issues raised
• joint EPISTLE solutions
• Improvements to use examples
• Training course delivery
• Total 85 man days

6
Data model schedule
7
Model maintenance process

• Issues log (feedback_at_posccaesar.com)
• registration and publication
• Next release and selection of issues
• EPISTLE management and joint DM team
• Issue solution
• joint data modelling team
• Solution documentation
• Solution review
• Model changes and documentation release

8
Y2000 RDS maintenance

• Updates for model V3 releases
• Provide restricted write access over web
• Provide HTML reporting tool for offline access of
  reference data
• Total 80 man days

9
Y2000 Development proposals

• Model extensions for geometry information
• Scope from Part42, OPENGis, AP227
• Specification of user templates, business
  objects, application views
• RDS data maintenance interface migration to V3
  model
• RDS Synergy components