Supply Chain Council releases Design Chain Operations Reference Model

The Supply Chain Council Inc. (SCC) has issued its newest model, the Design Chain Operations Reference model (DCOR), version 1.0, which captures the SCC Technical Development Steering Committee's consensus view of design chain management. While much of the underlying content of the model was originally developed by practitioners, the DCOR model provides a framework that links business process, metrics, best practices and technology features into a unified structure to support communication among design chain partners and to improve the effectiveness of the extended supply chain.

The model's structure is inspired by that of the Supply Chain Operations Reference Model (SCOR).

DCOR is organized around the five primary management processes of Plan, Research, Design, Integrate and Amend. It spans product development, research and development, but does not attempt to describe every business process or activity. Where SCOR addresses the process categories of Make to Stock, Make to Order and Engineer to Order product, DCOR is focused on Product Refresh, New Product and New Technology as its key execution processes.

DCOR is posted for SCC members only at www.supply-chain.org in three formats. A Microsoft WORD document provides the user a black and white 244 page documented draft of the DCOR Model. The file can be used like any Microsoft Word document and includes an introduction and glossary.

There are two web-published versions of the DCOR Model also posted solely on the SCC members-only website. No software or license is needed to access these models and the software used to develop them was used only because it was available to the project team; the SCC does not recommend any particular software over another. The next release of this model will be as a vendor-neutral database this summer (2006).

The first web-published DCOR is a Java Runtime Environment (JRE) web-published version of the model. Using the JRE model allows the reader to view content like one would in a modeling tool. The second web-published file is a less capable HTML based file. It does not have the same ability (to move around the model and zoom in and out to better view the model diagrams) as the JRE model.

Hide comments

Comments

  • Allowed HTML tags: <em> <strong> <blockquote> <br> <p>

Plain text

  • No HTML tags allowed.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Lines and paragraphs break automatically.
Publish