step 203 vs step 214

[JR2112]

Can anyone please give me a quick explination of the difference between step 214 and step 203? Mysmart a** co-worker said "11" but I think there's more to it.





When downloadingfiles from vendor sites, which format do you guys prefer?


I find I can't seem to do much with iges, but can add features to parts created with step files. I'm using WF 3.0





Thanks, John.

 

[dr_gallup]

<h2>STEP Application Protocols</h2>



A list of the STEP Application Protocols (AP) as of June 2004 is
given in Fig.2. The ability to support many protocols within one
framework is one of the key strengths of STEP. All the protocols are
all built on the same set of Integrate Resources (IR's) so they all
use the same definitions for the same information. For example, AP-203
and AP-214 use the same definitions for three dimensional geometry,
assembly data and basic product information. Therefore CAD vendors can
support both with one piece of code.

<blockquote>
<table border="0" cellpadding="0" cellspacing="0">
<t><tr><td>Part 201</td> <td>Explicit Drafting</td></tr>
<tr><td>Part 202</td> <td>Associative Drafting</td></tr>
<tr><td>Part 203</td> <td>Configuration Controlled Design</td></tr>
<tr><td>Part 204</td> <td>Mechanical Design Using Boundary Representation</td></tr>
<tr><td>Part 205</td> <td>Mechanical Design Using Surface Representation</td></tr>
<tr><td>Part 206</td> <td>Mechanical Design Using Wireframe Representation</td></tr>
<tr><td>Part 207</td> <td>Sheet Metal Dies and Blocks</td></tr>
<tr><td>Part 208</td> <td>Life Cycle Product Change Process</td></tr>
<tr><td>Part 209</td> <td>Design Through Analysis of Composite and Metallic Structures </td></tr>
<tr><td>Part 210</td> <td>Electronic Printed Circuit Assembly, Design and Manufacturing </td></tr>
<tr><td>Part 211</td> <td>Electronics Test Diagnostics and Remanufacture </td></tr>
<tr><td>Part 212</td> <td>Electrotechnical Plants </td></tr>
<tr><td>Part 213</td> <td>Numerical Control Process Plans for Machined Parts</td></tr>
<tr><td>Part 214</td> <td>Core Data for Automotive Mechanical Design Processes </td></tr>
<tr><td>Part 215</td> <td>Ship Arrangement </td></tr>
<tr><td>Part 216</td> <td>Ship Molded Forms </td></tr>
<tr><td>Part 217</td> <td>Ship Piping </td></tr>
<tr><td>Part 218</td> <td>Ship Structures </td></tr>
<tr><td>Part 219</td> <td>Dimensional Inspection Process Planning for CMMs </td></tr>
<tr><td>Part 220</td> <td>Printed Circuit Assembly Manufacturing Planning </td></tr>

<tr><td>Part 221</td> <td>Functional Data and Schematic Representation for Process Plans</td></tr>
<tr><td>Part 222</td> <td>Design Engineering to Manufacturing for Composite Structures </td></tr>
<tr><td>Part 223</td> <td>Exchange of Design and Manufacturing DPD for Composites </td></tr>
<tr><td>Part 224</td> <td>Mechanical Product Definition for Process Planning </td></tr>
<tr><td>Part 225</td> <td>Structural Building Elements Using Explicit Shape Rep </td></tr>
<tr><td>Part 226</td> <td>Shipbuilding Mechanical Systems </td></tr>
<tr><td>Part 227</td> <td>Plant Spatial Configuration</td></tr>
<tr><td>Part 228</td> <td>Building Services</td></tr>
<tr><td>Part 229</td> <td>Design and Manufacturing Information for Forged Parts</td></tr>
<tr><td>Part 230</td> <td>Building Structure frame steelwork</td></tr>
<tr><td>Part 231</td> <td>Process Engineering Data</td></tr>
<tr><td>Part 232</td> <td>Technical Data Packaging</td></tr>
<tr><td>Part 233</td> <td>Systems Engineering Data Representation</td></tr>
<tr><td>Part 234</td> <td>Ship Operational logs, records and messages</td></tr>
<tr><td>Part 235</td> <td>Materials Information for products</td></tr>
<tr><td>Part 236</td> <td>Furniture product and project</td></tr>
<tr><td>Part 237</td> <td>Computational Fluid Dynamics</td></tr>
<tr><td>Part 238</td> <td>Integrated CNC Machining</td></tr>
<tr><td>Part 239</td> <td>Product Life Cycle Support</td></tr>
<tr><td>Part 240</td> <td>Process Planning</td></tr>
</t></table>
</blockquote>



Each Application Protocol includes a scope describing its purpose,
an activity diagram describing the functions that an engineer needs to
perform within that scope, and an Application Requirement Model
describing the information requirements of those activities. These
information requirements are then mapped into the common set of
Integrated Resources and the result is a data exchange standard for
the activities within the scope.



The ultimate goal is for STEP to cover the entire life cycle, from
conceptual design to final disposal, for all kinds of
products. However, it will be a number of years before this goal is
reached. The most tangible advantage of STEP to users today is the
ability to exchange design data as solid models and assemblies of
solid models. Other data exchange standards, such as the newer
versions of IGES, also support the exchange of solid models, but less
well.



STEP led the way with three dimensional data exchange by organizing
an implementation forum for the CAD vendors so that they could
continually improve the quality of the solid model data exchanges. The
history of this success is relatively interesting because it show that
the initial reluctance of vendors to implement user-defined standards
can be overcome with enough perseverance.



At first, in 1996, there was a significant body of opinion that
solid model geometry data could not be exchanged between systems using
a neutral standard. However, in 1997 Ford, Allied Signal and STEP
Tools, Inc. demonstrated the first successful data exchange of 3D
geometry using STEP. Once this basic capability had been demonstrated
a pilot project, called AeroSTEP, was organized by Boeing and its
Aircraft engine vendors to test the first translators by exchanging
data about where an engine fits onto the airframe. This project
started out by exchanging simple faceted models but eventually
demonstrated the exchange of models with great complexity.



The AeroSTEP project made it clear that STEP data exchange of solid
model data was both feasible and valuable. As a result, vendor neutral
implementation forums were formed in Europe, the Far East and the USA
and the quality of the translators was raised to the level that
allowed anyone, including ordinary users in small organizations, to
use STEP for data exchange of solid models after about 2001.