Teamcenter’s Service

Oriented Architecture

White Paper
Integrating Teamcenter-managed product design and
development with your mainstream business processes

Today’s companies are discovering they can more flexibly perform

their business processes with less IT intervention if they use a
service oriented architecture (SOA) as the technological foundation
for their digital product design and development environment.
Teamcenter® software’s SOA services provide an open, high-
performance, coarse-grained interface to the Teamcenter system’s
Business Logic Server. These services enable you to access
Teamcenter-driven capabilities and integrate them with your
existing business processes – as well as to create customized,
task-specific programs to meet your business needs.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 2

Contents

Executive summary .............................................................................3  

Why a service oriented architecture is important ...............................3  

What you can do with Teamcenter’s SOA services..............................4  

Gaining Teamcenter’s SOA advantage...............................................4  

Introducing Teamcenter’s SOA ............................................................5  

What is a service oriented architecture? ............................................5  

A technical look at Teamcenter’s SOA ...............................................6  

Using Teamcenter’s SOA services ........................................................9  

Logical deployment architecture ......................................................9  

Teamcenter’s SOA service areas .....................................................10  

Teamcenter’s SOA service invocation..............................................10  

Using Teamcenter’s SOA client-side libraries ...................................11  

Using Teamcenter’s SOA from WSDL-based applications ..................11  

Supported configurations ..............................................................12  

A final evaluation ..............................................................................13

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 3

Executive summary

The biggest challenge for today’s corporate IT • Embed Teamcenter-managed information and
organizations is to provide improved real-time status results into existing clients, portals and
visibility into their company’s business operations. IT executive dashboards.
leadership is especially concerned with managing the
• Integrate the Teamcenter portfolio and its
software application lifecycle and controlling its cost.
application solutions with diverse external
Research indicates that the vast majority of IT functionality, including CAD systems, collaborative
executives and other senior managers are convinced design management tools (such as Teamcenter’s
that a service oriented architecture (SOA) is the right own community collaboration capabilities),
technology approach for improving IT agility and manufacturing planning solutions (such as
lowering that portion of the IT budget (40 percent) Tecnomatix® software) and highly popular
associated with application integration. Increasingly business applications (such as Microsoft Office). As
companies are discovering that their business a result, you can establish a single cohesive
becomes more nimble and their processes become environment capable of supporting all of your
more flexible when they implement SOA as the digital lifecycle management initiatives.
technological foundation for key computing envi-
Teamcenter’s SOA is based on industry standards for
ronments (such as the product design and develop-
Web Services, primarily adhering to WS-1 and other
ment environment). Equally important, SOAs are
WS-x standards and best practices. SOA services also
able to facilitate these improvements with less IT
are accessible through numerous language-specific
intervention than was previously possible.
libraries that make it easy for programmers with C,
To address these rising IT requirements, Siemens PLM C++, C# and Java experience to incorporate Teamcen-
Software has developed an SOA infrastructure for ter functionality into new and existing applications.
Teamcenter, Siemens PLM Software's flagship
software for facilitating product lifecycle manage-
ment (PLM) and supporting the PLM-driven business Why a service oriented architecture
processes adopted by its customer base. is important
Teamcenter is industry’s most widely used PLM
solution with an integrated suite of applications that Teamcenter’s SOA services provide new capabilities
leverage technologies such as 3D visualization, that allow you to deploy higher performing and more
community collaboration, supplier management and scalable WAN-friendly and firewall-friendly applica-
collaborative product data management (cPDM) to tions in a Teamcenter environment. Because these
drive business productivity. capabilities adhere to industry standards and
established best practices, Teamcenter services are
Teamcenter’s SOA services provide a new coarse- now accessible to a wider development community.
grained interface to Teamcenter’s Business Logic
Server. Teamcenter’s SOA services represent Siemens In turn, wider accessibility increases the likelihood-
PLM Software’s go-forward strategy for enabling that more robust and comprehensive services will
client and external applications to access a evolve at a faster rate. Similarly, the worldwide
Teamcenter-managed environment. These services development community will be able to access and
can be used to: leverage these services without having to learn how
to use a proprietary language or protocol; no special
• Integrate Teamcenter capabilities into your training is required.
existing business processes, as well as for creating
custom, task-specific client programs.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 4

What you can do with Teamcenter’s batch, or non-interactive applications, as well as

SOA services highly interactive end-use applications on the
desktop.
Teamcenter’s SOA is a coarse-grained API that
openly exposes Teamcenter’s Business Logic Server
capabilities to Web Services, as well as to language- Gaining Teamcenter’s SOA advantage
specific programs. This provides an ideal solution for
enabling a wide range of applications to access your Organizations that adopt Teamcenter’s SOA gain the
Teamcenter environment’s product design and advantages inherent in the use of a consistent,
development information. comprehensive set of interfaces that leverage
Teamcenter’s powerful product design and develop-
Teamcenter itself functions as the engine and ment services. Regardless of what language you use
repository that connects all of your environment’s to call these services (and that choice is entirely up to
design and product development information in a you), the business logic and results received from
flexible and loosely coupled manner – while provid- Teamcenter’s SOA will be the same.
ing your entire global environment with a single
point of access to these connected assets. You no longer need to worry about your project
teams’ skill sets or any language-related dependen-
Because Teamcenter’s SOA services are exposed as cies. Teamcenter’s SOA provides a single set of entry
1
WS-1 compliant WSDL and language-specific points for use by all clients and applications –
interfaces, project teams are able to leverage an regardless of their heritage.
interface that best meets their own needs while
assuring that the Teamcenter operations being called As new services are exposed via Teamcenter’s SOA,
are the same – and that their results will be the they will be immediately available in all supported
same – regardless of the language or binding being programming languages, as well as through industry-
used. In addition, Teamcenter’s SOA easily supports standard WSDL.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 5

Introducing Teamcenter’s SOA

What is a service oriented architecture? Teamcenter’s SOA embodies all of these principles
and characteristics. It is built upon a framework
A service oriented architecture is a system design consisting of the entire client and service infrastruc-
pattern that emphasizes the following attributes – ture that contributes to consistent, reliable and high-
along with other considerations: performance interaction between the application
clients, service consumers and Teamcenter Business
• Appropriate functional granularity appropriate to
Logic Server (the service provider in this scenario).
the task at hand
This framework enables application developers to
• Separation of the interface definition from its
concentrate on creating specific business functional-
implementation ity rather than worrying about the low-level
• Support for the concept of service providers and communications and data management activities
service consumers who are distinct from each going on beneath them.
other Teamcenter’s SOA characteristics reflect two addi-
• Standards-driven compliance tional factors:

Service-oriented architectures also reflect a specific: • Messaging via standard protocols

• Software framework • Message content formats

• Set of policies Like the implementations of most service oriented

architectures, Teamcenter’s SOA uses standard HTTP/S
• Set of best and accepted practices

Figure 1: Teamcenter SOA framework components.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 6

communications protocols to send XML documents A technical look at Teamcenter’s SOA

back and forth between the service provider and the
service consumer. Use of these standards contributes Teamcenter’s SOA consists of the following client-side
to the openness, flexibility and scalability necessary and server-side components that follow well-defined
for both the local and global deployment of patterns using standards-based protocols, languages
Teamcenter. It is this open, standards-based messag- and data formats.
ing environment that allows service providers and
• SOA Framework provides the communications and
service consumers to be implemented in differing
technologies while retaining their interoperability. infrastructure functionality that enables
application developers to concentrate on creating
This messaging environment also allows existing business solutions rather than dealing with
applications in one technology to be quickly adapted underlying communications/messaging issues
so that they can interact with newer and richer
• SOA Language Bindings provide language-specific
technologies and programming languages – which
helps your company preserve its investments in functions (.NET, C++, and Java) used by service
existing programs and processes. consumers to invoke an SOA service and properly
handle the ensuing response
As a result of this flexibility, you can incrementally
• SOA Client Data Model (CDM) and Data Model
enhance your product design and development
environment at a speed that virtually matches your Manager provide managed type-safe storage on
business’ real-world evolution. This alignment is the service consumer side for all data returned by
largely facilitated by the arms-length, loosely coupled service responses from Teamcenter’s Business
relationship that exists between service providers Logic Server
(like Teamcenter’s Business Logic Server) and service • SOA Toolkit provides tools that enable Teamcenter
consumers (like Teamcenter clients, CAD systems, developers to auto-generate all of the artifacts
Microsoft Office and your own portal and dashboard necessary for exposing new Teamcenter business
applications). logic as SOA services

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 7

In addition to these major components, Teamcenter’s The relationships between the environment and its
SOA environment also includes documentation on major components are illustrated in Figure 2.
each of the language bindings, WSDL and various
The accompanying table describes the major compo-
XML Schema Definitions (XSDs) used throughout the
nents in Teamcenter’s SOA in more detail.
system.

Teamcenter’s SOA’s major components

Capability Function

SOA Framework Consists of the client-side libraries, as well as the communications infrastructure and
Key capabilities for a best-practice portfolio management solution
server-side libraries that make up a full-featured request/response pipeline. All SOA
Framework components are auto-generated by the SOA Toolkit and are completely
opaque to both the author of the service and consumer of the service.

SOA Language Represents the client-side components required to execute a service request from an
Bindings application. Because the SOA Toolkit auto-generates these components, the compo-
nents are functionally equivalent across all supported languages. Initially, Siemens PLM
Software provides bindings for C++, .NET and Java.

Teamcenter’s Populates and updates the client-side data store with objects returned from
Data Model Teamcenter’s Business Logic Server on each SOA service call. Object identity is main-
Manager tained so that when an existing object is returned, its properties are updated in the
data store rather than creating a new/identical item.
Data Model Manager is also responsible for maintaining the meta-model of type and
property information. Optionally, it can fire events on object creation, deletion or
modifications. Client applications can register listeners for these events and react to
them as appropriate.

Teamcenter’s Generated from Teamcenter’s Data Model formally defined within Teamcenter’s
Client Data Model Business Modeler/IDE, Teamcenter’s SOA supports two types of CDM for client applica-
(CDM)
tion use – a generic model and a type-safe model.
The generic model consists of simple objects and their properties. Utility functions are
provided to determine an object’s Teamcenter type, to query the type hierarchy and to
access the characteristics of each property on an object.
Derived from the generic model, the type-safe model adds strongly-typed accessors for
all objects and their properties. This model’s class hierarchy matches Teamcenter’s
Business Logic data model formally defined in Teamcenter’s Business Modeler/IDE. The
accessors for each property return the language-specific equivalent of the native
Teamcenter type of property.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 8

autotest framework
Client
TestTcFooService .xxx
Client data model Client service binding

TcBar .xxx FooRestBindingStub .xx

WS Presentation

Client binding management FooService .xid

Event management
Client data model populator FooService .xsd

Schema binder

Wire schama
Model binder Schema binder Service binder
SOABase .xsd

TcFooServie .xsd

Server

xsd binding

T2LServices

FooCorbaBindingSkel

svc implementations svc definitions

FooImpl .cxx Foo .hxx

Core metamodel Core

bar .cxx

Figure 2: Teamcenter SOA functional components.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 9

Using Teamcenter’s SOA services

Logical deployment architecture

Organizations typically deploy the Teamcenter

environment using a four-tier logical architecture that
consists of:
• Client application

• Web application server

• Enterprise Tier

• Resource Tier

Figure 3: Teamcenter SOA runtime deployment.

Client application Most client applications, including Web application server Teamcenter deployments
applications developed by Siemens PLM Software and use web application servers to expose the SOA service
its partners, are language-based, rather than WSDL endpoints for all client types. Both REST-style
based. As a result, they typically incorporate one of (standard HTTP POST) and SOAP-style requests are
Teamcenter’s SOA client libraries along with the CDM. supported by Teamcenter components executing on
Custom integrations developed using the WSDL industry-standard application servers, such as
approach usually do not use client libraries or the Microsoft IIS, as well as servers based on Java and
CDM. Since both types of clients are HTTP/S based, J2EE technology. SOA Framework components
they can easily and effectively access Teamcenter running on these application servers are responsible
across low or high latency network connections – as for normalizing the request into a single common
well as securely traverse corporate firewalls without format, which is passed directly onto Teamcenter’s
needing to open additional application-specific ports Business Logic Server that resides in the Enterprise
in those firewalls. Tier.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 10

Applications Application integration

Classification : : Classification AI : : AI
Core : : DocumentManagement CAD : : DataManagement
DocumentManagement : : DocumentTemplates CAD : : StructureManagement
ProjectManagement : : ScheduleManagement
RequirementsManagement : : RequirementsManagement

Application support
Allocations : : Allocation MultiSite : : ObjectDirectory
Query : : SavedQuery MultiSite : : Transfer
Reports : : BOMRollup Workflow : : Workflow
Reports : : CRFReports System administration
StructureManagement : : Restructure
StructureManagement : : GlobalAlternates
StructureManagement : : Redinining System definition
CalendarManagement : : CalendarManagement

Platform
Core : : Session
Core : : DocumentManagement
Core : : FileManagement
Core : : Reservation
Core : : ManagedRelation

Figure 4: Teamcenter services functional areas.

Enterprise Tier Teamcenter’s Business Logic Server – as well as the representative library and service
along with Teamcenter’s SOA server-side compo- names that pertain to key areas.
nents, resides in the Enterprise Tier. All of the actual As the diagram illustrates, services are provided for
SOA services are implemented in C++ as part of fundamental needs (such as session and file man-
Teamcenter’s Business Logic Server. agement), for supporting capabilities (such as queries
Resource Tier The Resource Tier houses the and reporting), and for specialized services (such as
Teamcenter database and bulk-data file repositories. PLM system definition and administration). Over
No SOA components are part of the Resource Tier. time, Siemens PLM Software will introduce additional
libraries and services for each of these areas –
especially in the application and application support
Teamcenter’s SOA service areas areas.

Teamcenter’s SOA services are organized into the

following six functional areas. Teamcenter’s SOA service invocation
• Platform Before discussing how Teamcenter’s SOA services are
• Application support invoked, it is helpful to understand some of the basic
principles that drive the design of Teamcenter’s SOA
• Applications services.
• Application integration First, Teamcenter’s SOA provides set-based services –
• System administration meaning that virtually all services accept multiple
input objects that can be operated on by the Business
• System definition Logic in a single call. On both inbound and outbound
Each of these functional areas is further broken down sides of a request/response cycle, it is advantageous
into one or more libraries that contain the actual to be able to submit or respond with more than one
services and operations exposed by Teamcenter’s item at a time. This flexibility is especially important
Business Object Server. The accompanying diagram when invoking services over high-latency wide-area
indicates how the six functional areas are organized, network connections.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 11

Adopting a set-based default design for all services client framework instantiates the connection object
also supports a loose-coupling and infrequent and returns it to the application – where subse-
communications pattern. At the same time, it reduces quently it can be used to invoke appropriate services.
the overall size of the service set by eliminating the
Authentication Since Teamcenter is a secure
requirement for both single item and multi-item
environment, any service invocation must be
interfaces for the same operation. A set-based
preceded by an authentication request. Successful
operation can easily handle a set-of-one without
authentication returns a token that is used on all
requiring a separate interface.
service requests across the established connection.
Second, Teamcenter’s SOA services are coarse- Teamcenter’s SOA supports all Teamcenter authenti-
grained services – meaning that they perform opera- cation models, including single sign-on (SSO) and
tions that, from a developer and end-user perspec- synchronized LDAP.
tive, are relatively complete in and of themselves. The
Service invocation Before invoking a service, the
service consumer asks for something to be done and
client application must build the necessary input
Teamcenter’s Business Logic Server does it. Teamcen-
structures required by the service, as well as set
ter’s SOA services eliminate intermittent network
parameters on each item being input as part of the
chatter that plagues many ordinary client/server
set-based call. Once all of the data has been properly
applications.
structured, it is passed to a service stub for submis-
Siemens PLM Software designed Teamcenter’s SOA sion to the Business Logic Server.
services so that the response to a user operation (for
Over-the-wire The service stub works in conjunction
example, highlighting a set of objects or hitting the
with the SOA Framework to marshal the service
“delete” button) is performed in a single request/
request into a REST XML document and sends it over
response cycle. In other architectures and system
HTTP/S to the Web Tier.
designs, an operation like this might take hundreds of
request/response cycles to individually submit and Web Tier SOA Framework forwards the request to an
acknowledge the deletion of each highlighted or available/assigned instance of the Business Logic
selected object. Server.
Third, Teamcenter’s SOA services support the “partial Enterprise Tier SOA Framework forwards the request
errors” concept – meaning that a set-based operation to the appropriate services skeleton, where the XML
can be only carried out on a subset of the input items document is un-marshaled. Then, the service
when an error condition arises. Again, drawing on the endpoint or implementation is called and the service’s
“delete” button example, if some of the items business logic is executed. Once the business logic’s
selected for deletion are locked or have outstanding execution is complete, the service skeleton marshals
dependencies or relationships, it often is neither the results (including any information on exceptions
wise nor possible to delete these items as requested. or partial failures) to a REST XML document and
In these cases, it is important to tell the service passes it back through the Web Tier.
consumer which items were not operated on and the
Web Tier SOA Framework receives the service
reasons why. Efficient and consistent partial error
response and properly formats it for an HTTP/S POST
handling is a crucial principle that drives Teamcen-
response.
ter’s SOA Framework and Business Logic Server – as
well as the client libraries and data model. Client framework The service stub un-marshals the
response, uses the SOA Framework to process it into
the Client Data Model (including any error informa-
Using Teamcenter’s SOA tion), and returns control to the client application.
client-side libraries

Regardless of what specific language binding is used Using Teamcenter’s SOA from
in the application, developers perform the following WSDL-based applications
consistent steps when they leverage Teamcenter’s
SOA client-side libraries. With just a few adjustments to the components, you
can use the same set of steps described above
Connection The client application first requests a
(in the “Using Teamcenter’s SOA client-side libraries”
connection object, which contains the parameters
discussion) to invoke an SOA service from a
that can be used to connect to the server. The SOA

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 12

WSDL-based web services application. These adjust- Once the response is received, utilities in the web
ments include the following differences. services toolkit (i.e. in the toolkit is being used to
build the client application) un-marshal the response
First, WSDL-based applications generally do not make
into structures directly usable by the client applica-
use of the Teamcenter client-side libraries. Instead,
tion. Since the Client Data Model and the Data
they use utility functions within each of the major
Manager Model are part of the SOA Framework, no
web services toolkits to automatically build the
additional processing is necessary for handling the
necessary connection objects and input/output
business objects returned on the response.
structures for a service directly from the Web Services
Description Language (WSDL). As you might expect,
tools such as Microsoft’s Visual Studio can greatly
assist the developer by reading the WSDL for a service
Supported configurations
and auto-generating the necessary artifacts transpar-
ently. Teamcenter’s SOA services are fully supported on all
standard four-tier Teamcenter deployments as
Second, the only other difference between the REST discussed throughout this white paper. In addition,
and SOAP paths is the entry point into the Web Tier. Teamcenter’s SOA services also are supported in
Unlike the REST entry points (described earlier), the Teamcenter’s “two-tier” configuration sometimes
SOAP request is processed by the SOAP engine on the used by Teamcenter users migrating up from
Web Tier. The SOAP engine un-marshals the SOAP Teamcenter Engineering.
XML document and forwards it to the Web Services
endpoint that is auto-generated by Teamcenter’s SOA Two-tier deployments combine the Teamcenter client
Toolkit. and a Business Logic Server instance on each end-
user’s computer; the shared database and file stores
At the service endpoint, the request is marshaled to a remain on a centralized resource tier. Typically, this
REST XML document and routed to Teamcenter’s configuration uses CORBA/IIOP communications
Business Logic Server in the same manner as the REST rather than HTTP/S and eliminates the Teamcenter
example described earlier. Information about Web Tier altogether. As a result, client implementa-
whether the request came through a SOAP endpoint tions in this type of deployment must use one of the
or a REST endpoint is never passed to the Business supplied language binds rather than a WSDL-based
Logic Server. This practice helps ensure that service client implementation.
innovations are always processed in the same manner
regardless what type of client invokes the request.
With respect to the service response, the Web Service
endpoint returns control to the SOAP engine, where it
is properly formatted for a SOAP-over-HTTP response.

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 13

A final evaluation

By applying an effective SOA to their PLM processes, facilitates lower cost of ownership, as well as greatly
companies can support more business capabilities, improved integration between your business systems
reduce IT complexity and accelerate IT implementa- and the technical systems that power your product
tion – as well as re-use more applications (via web design/development initiatives.
services) and better align their PLM initiatives with
Siemens PLM Software has initially focused
other business activity.
Teamcenter’s SOA on the robust capabilities and high
Teamcenter’s SOA services provide a robust, flexible performance required to deliver a core architecture
and highly-scalable interface into your digital design and service-based design capable of supporting both
and development processes and their related large and small deployments. The services exposed by
information assets. The SOA’s secure, WAN-friendly Teamcenter’s SOA cover a broad range of Teamcenter
and firewall-friendly attributes are especially appro- functionality with particular attention to streamlining
priate for meeting the most rigorous demands of your product design and development processes.
both large and small companies.
Future releases of Teamcenter’s SOA will add value to
On the technical side, Teamcenter’s SOA is a state- your organization by exposing additional Teamcenter
of-the-art implementation that is based on – and functions, supporting more language bindings,
compliant with – the latest industry standards invoking additional tiers in the Teamcenter stack and
for web services interoperability. By adopting facilitating interoperation with other external
Teamcenter as the backbone for your digital enter- application offerings as these programs converge
prise, you can immediately reap the benefits of web toward accepted industry standards.
services technology through an infrastructure that

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
White Paper | Teamcenter’s Service Oriented Architecture 14

References

1. Web Services Description Language (WSDL).

Issued by: Siemens PLM Software. © 2010. Siemens Product Lifecycle Management Software Inc. All rights reserved.
About Siemens PLM Software

Siemens PLM Software, a business unit of the Siemens Industry

Automation Division, is a leading global provider of product
lifecycle management (PLM) software and services with nearly
6.7 million licensed seats and 63,000 customers worldwide.
Headquartered in Plano, Texas, Siemens PLM Software works
collaboratively with companies to deliver open solutions that
help them turn more ideas into successful products. For more
information on Siemens PLM Software products and services,
visit www.siemens.com/plm.

© 2010 Siemens Product Lifecycle Management

Siemens PLM Software Software Inc. All rights reserved. Siemens and the
Siemens logo are registered trademarks of Siemens AG.
Headquarters Americas Europe Asia-Pacific D-Cubed, Femap, Geolus, GO PLM, I-deas, Insight, Jack,
Granite Park One Granite Park One 3 Knoll Road Suites 6804-8, 68/F JT, NX, Parasolid, Solid Edge, Teamcenter, Tecnomatix
5800 Granite Parkway 5800 Granite Parkway Camberley Central Plaza and Velocity Series are trademarks or registered
Suite 600 Suite 600 Surrey GU15 3SY 18 Harbour Road trademarks of Siemens Product Lifecycle Management
Plano, TX 75024 Plano, TX 75024 United Kingdom WanChai
USA USA 44 (0) 1276 702000 Hong Kong Software Inc. or its subsidiaries in the United States and
972 987 3000 800 498 5351 Fax 44 (0) 1276 702130 852 2230 3333 in other countries. All other logos, trademarks,
Fax 972 987 3398 Fax 972 987 3398 Fax 852 2230 3210 registered trademarks or service marks used herein are
the property of their respective holders.
www.siemens.com/plm
X6 11319 11/10 C