R NASA STEP for Aerospace Workshop at Jet Propulsion Laboratory January 27, 2000 Thomas Thurman Rockwell Collins Inc. AP 210 Foundations for Electrical-Mechanical Integration

R AP 210 Foundations for EE/ME Integration Configuration Management Geometry Datum System Reference Designator Features Explicit Pin-mapping

R Exchange of data independent of process or tools. Frequency controlled by unique Business needs. Exchange of intelligent data. Requirements Circuit Board Assembly Product Package ECAD MCAD Quality Product STEP Data AP 210 AP 203/ AP 210 Electrical Mechanical Interface Integrated 3D/2D EE/ ME library

R AP 210 Foundations for EE/ME Integration Configuration Management STEP Configuration Management is the result of 50+ person years of research into exchange and sharing of quality PDM models. AP 210 Extends this with Net Change Capability

R AP 210 Foundations for EE/ME Integration Geometry STEP Geometry is the result of 200+ person years of research into exchange and sharing of quality geometric models. STEP Geometry supports both 2d and 3d geometric and topological requirements allowing end-users to select the model best suited to their needs. AP 210 integrates STEP Geometry into the feature model to provide even higher data quality.

R AP 210 Foundations for EE/ME Integration Datum System Datum System provides a functional view of the geometric model requirements and design intent. –Provided for both part and design data Supports data pre-defined in GD&T standards. Supports direct data feed to factory automation. Supports explicit integration of simulation models with geometric model eliminating need for drawings to identify model parameters.

R

R AP 210 Foundations for EE/ME Integration Reference Designator Reference Designator provides alternative representation for the location of a component in a design at one level. A component may be identified by its location in the geometric model of that assembly. Components in sub assemblies are located by combining reference designators in a path from the highest level to the lowest level of interest.

R AP 210 Foundations for EE/ME Integration Features AP 210 uses features as explicit objects in a design to eliminate the need to query geometric models for product data –Attachment point for simulation models –contact surfaces for assembly purposes Rich feature classification based on functional and physical characteristics Rich feature relationship structures available, pre-defined and user-defined

R AP 210 Foundations for EE/ME Integration Explicit Pin-mapping Uses the feature capabilities to explicitly relate the part mechanical layout view features to the part electrical layout view features and to the part electrical functional view features.

R AP 210 Foundations for EE/ME Integration Example use of 210 for package definition The next two charts illustrate how AP 210 integrates the use of Datum System and features in order to define an unambiguous package definition. The objects represented on the two charts are the same objects. There are two shapes for each object, one 3d and one 2d. The two shapes are tightly coupled geometrically. Unambiguous means that different CAD systems will be able to read/write this data without human intervention resulting in an automated assembly process that is correct by construction. CC14 is a reference to Conformance Class 14 of AP 210 which supports this data definition

R Building a Library Package Definition (CC14) (This page is a presentation of a 3d representation) Primary Reference Terminal 3d representation Primary orientation feature 3d representation Seating Plane 3d representation Package Geometric Origin 3d representation

R Building a Library Package Definition (CC14) The associated 2d representation for the package on the previous slide. Primary Reference Terminal representation Primary orientation feature representation Seating Plane is in the plane of the 2D Model, Which is always “Viewed” from the “Top”. Package Geometric Origin representation

R AP 210 Foundations for EE/ME Integration Example use of 210 for packaged part definition The next chart illustrates how AP 210 builds on the previous chart adding an explicit pin map to the functional view of the part. The explicit pin map does not rely on the naming conventions of any system as the pin map is not file based. Both the Functional view and the package are available as explicit objects in the definition. The result is the end-user has flexibility in naming conventions while retaining control of pin-mapping tasks.

R Primary Reference Terminal ina1 ina2 outa inb1 inb2 outb inc1 inc2 outc ind1 ind2 outd pwr1 pwr2 Functional_usage_view_to_part_terminal_assignment Using Pin MAP A Functional_usage_view_to_part_terminal_assignment ARM application object provides the pin map capability in AP 210 Role is physical_usage_view_terminal Role is functional_usage_view_terminal Building a Library Packaged Part Definition Functional_unit_usage_view Package

R AP 210 Foundations for EE/ME Integration Example use of 210 for connector definition The next chart illustrates how AP 210 supports the definition of a connector. A connector has all the functionality of a packaged part as shown on the previous slides, but adds explicit knowledge that a connector is supposed to connect something, actually two things: an external interface and an internal interface. The combination of features, Datum System, pin mapping and connector functionality provides an elegant solution to connector mis-orientation problems.

R Join Terminals Interface Terminals Packaged_connector in AP 210 Packaged_connector has additional functionality over Packaged_part: There is a short between an Interface Terminal and a Join Terminal Interface Terminals Mate with Other Interface Terminals in an Assembly Join Terminals mate with some interconnecting material in a Layout