Specifications.

A specification is an explicit set of requirements to be satisfied by a material, product, or service. Specifications are a component of product data. Specifications, as experienced users of SCOR know, are critical inputs in the Supply Chain. In Make we produce to specification, or in Repair we return the item to specification. Specifications originate and are managed and changed in the Design Chain. This section defines the types of specifications in the DCOR model and how they are used commercially in Design, Engineering and Manufacturing. Additionally a brief discussion of software specifications is essential since virtually no complex product is realized without embedded systems. In the DCOR Model. The three execution processes of the model generate the following forms of specifications: Research Specifications: Product Description, Raw Materials, Equipment Required, Production Consideration, Production Process, Merchandising Considerations, Estimated Shelf-Life result from the Research execution processes. Design Specifications: Design Specification, which result from the Design executions processes, will: a. Define the technical scope of the product. b. Define the expected use and purpose of the product. c. Define relationships with existing products. d. Describe the design of the product. Product Specifications: Finally from the integrate processes come detailed product information including, but not limited to key features, compatible options, part numbers, and technical specifications. How all three types of specifications come to bear in the DCOR reference model is in Integrate (see below example for Product Refresh, Figure 1 below). What is key is that Requirements (the What) is realized by the Product Specification (the How) and that any specified documentation (Product Data) is provided per the requirement.

Inputs: Product Requirements (customer or S&O) Research Specifications R1.4 Design Specifications D1.5 Research Documents (Product Data) R1.3 Design Documents (Product Data) D1.4 Integrate Integrate (Refresh) (Refresh)

Outputs: Product Specifications Product Documents (Product Data)

Figure 1 What is key for the Design Chain Reference model is that Specifications for products, assemblies, subassemblies, components, parts, processes, and materials are outputs of the three execution processes (Research, Design and Integrate). In creating a complex product, either existing product specifications or new specifications go into the make up of a product decomposed as follows: Product Specifications System Specifications Subsystem Specifications Component Specifications Part Specifications Material Specifications [and associated software specifications (see below)] In General Definition and usage. Specifications are used in design, manufacturing and engineering and they are critical for suppliers, purchasers and users of materials, products and services to understand and agree on all requirements (again refer to Figure 1 above). A spec may also be a type of a standard which is often referenced by a contract or procurement document. It provides the necessary details about the specific requirements. Specs can be written by the government (e.g. Mil Std), standards organizations (ATSM, ISO, CEN, etc), trade associations, corporations and others. A spec might include:

Descriptive title and scope of the spec Date of the last revision and revision designation Person, office or agency responsible on the spec for updates, deviations The significance or importance of the spec and its intended use Terminology and definitions to clarify the meaning of the spec Test methods for measuring all specified characteristics Material requirements: physical, mechanical, electrical, chemical etc Targets and tolerances Drawings, photos, or tech illustrations Workmanship Certifications required Safety considerations and requirements Environmental considerations and requirements Quality requirements, sampling (statistics), inspections, acceptance criteria Person, office, agency responsible for the enforcement of the spec Completion and delivery Provisions for rejection, re-inspection, rehearing, corrective measures

Specifications can: be performance based by stating what performance must be achieved in each section of work. be prescriptive indicating specific products, components, vendors or contractors. also apply to software. Embedded Systems and Software specifications. It is hard to imagine a complex product existing today without embedded systems/software. There are specifications associated with same as follows: Functional Specifications Functional specifications describe the necessary functions at the level of units and components; these specifications are typically used to build the system exclusive of the user interface. The functional specifications document might have implications about the design of the user interface, but these implications are typically superseded by a formal design specification and/or prototype. Design Specifications The design specifications address the "look and feel" of the interface, with rules for the display of global and particular elements. Technical Specifications Technical specifications are typically written the by developers and coders, and describe how they will implement the project. The developers work from the

functional specifications, and translate the functions into their actual coding practices and methodologies.