1 / 11

DCOR and SCOR Modeling Conventions

DCOR and SCOR Modeling Conventions. John Nyere. Overview. Why tools? This brief will discuss tool methods, conventions, objects, appearance etc. Why tools?. Reason one: time to publication Faster, more accurate model development NO FLIPPING AROUND IN BOOKS

badu
Download Presentation

DCOR and SCOR Modeling Conventions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DCOR and SCOR Modeling Conventions John Nyere

  2. Overview • Why tools? • This brief will discuss tool methods, conventions, objects, appearance etc

  3. Why tools? • Reason one: time to publication • Faster, more accurate model development • NO FLIPPING AROUND IN BOOKS • Everyone involved is accessing the same model, not waiting for publication of documents • Provides traceability to actions/efforts (CM) • Provides for Identification and management of needed changes • Using tools is a self-organizing function • Allows independent efforts of severable tasks (while giving visibility to others in parallel efforts) • Can rapidly publish from the model, by either: • Web publish different types of models for users • Document publication

  4. Why tools? • Reason two: Quality • Provides traceability to actions/efforts (CM) (self documenting) • Identifies and manages needed changes • Model restricts error making • Powerful utilities e.g. semantic checks • Facilitates a common vocabulary • Provides by using templates and methods a common look and feel • Provides a historical indexing of earlier models and revisions to working models

  5. Conventions • Operate as if there was a meta model • A combined DCOR/SCOR/CCOR model Are all of the parts identifiable? No. Do they look and feel the same? No. Are objects defined the same? No • Work needs to be done in this area. • Some examples.

  6. Value Chains Recommended model Current model SHOULD BE REFLECTED SCOR model differentiated from DCOR or CCOR models…. Important for interlock…. Important for USAF who wants a Combined DCOR and SCOR model For System Integrator who delivers Products to the sustainment organization

  7. Another Value chainwhat do you want it to look like? Current SCOR model EP Recommended model Or what’s below? The above? Same comments on previous slide

  8. FADs (Process Elements) Recommended model Current SCOR model EP.1 Metric type and number clearly identified shows source or destination of i/o This object is a technical Term…. Not the classic object used in a FAD Short description shown Don’t know source or destination of i/o But see next page…. Design differentiated from Supply Chain Don’t know what metric type or number

  9. FADs (Process Elements) Current SCOR model EP.1 You do know source of i/o When you look at the occurences of the object “business Plan” this is the self organizing part.

  10. Other improvements • Looking at the previous examples: • Names of objects could be shorter….. • Many names are larger than the object

  11. Conclusion • The models need to look and feel the same • Same objects • Use cluster not technical item • Same form for value chains • Same form for FADs • Same markings of objects • Be able to differentiate SCOR from DCOR & CCOR • Shorter names • BUT in all cases, use the tool (ARIS)

More Related