New task based mobile application delivered

New task based mobile application delivered

This demo is an example implementation of the new Wincom mobile platform. In this scenario the client had a requirement for a mobile based application to assist on-site service technicians to quickly and easily access drawings and documents. The interface is designed to be very task oriented and requires only limited training, so the technician simply has to enter the product number and then with a small number of interactions can navigate to the parts of interest. They immediately have access to the specific information they require without having to access a complex enterprise system. The interface is designed to be highly ergonomic, and implemented to be easy to use with a touch screen tablet interface.

The new Wincom mobile platform allow us to quickly create task based applications that run on any mobile platform unlocking access to PLM information for the extended enterprise.

Features include

  • Compatible with desktop, tablets…
  • No client installation required
  • Fast structure browsing
  • Quick access to information such as attributes, PDFs…


[vsw id=”sd8UScwVg0Q” source=”youtube” width=”425″ height=”344″ autoplay=”no”]



New Creo Parametric application delivered

New Creo Parametric application delivered

We have just released a new Creo Parametric 2.0 Application for a major European manufacturer.

This application is installed both on the server and the Creo clientNew Creo Parametric Application

  • A Windchill PDMLink side component (10.1).
  • A Creo Parametric 2.0 client application

This component allows actions directly from Creo Parametric

  • Windchill parts + CAD dependencies creation
  • Promotion
  • Save As
  • Part editing
  • […]

Key features

  • Seamless integration of Creo Parametric and Windchill
  • Automatic Creo installation and updating
  • Fully configurable

This first phase of this project has been delivered and additional features will be added in the coming weeks.




Getting start with Creo® Parametric J-Link – Part 1

Getting start with Creo® Parametric J-Link – Part 1


J-Link is a Java toolkit for Creo® Parametric. It makes possible the development of Java programs which can be used to interact with Creo Parametric.

J-Link comes with Creo® and is free of charge. In order to install It, make sure to select the “API Toolkits” component during Creo® installation.




  • Java language
  • Creo® Parametric

1.2.Synchronous J-Link application

A synchronous J-Link application is started and managed by Creo® Parametric.Control belongs to either Creo® Parametric or the application, but not both at the same time. This tutorial covers this type of applications.

1.3.Asynchronous J-Link application

An asynchronous application is started independent of Creo® Parametric with the option to start or connect to Creo® Parametric processes. This tutorial does not covers this type of application.


Term Description
<CREO_LOADPOINT> The location where the Creo® applications are installed,such as :C:\Program Files\PTC\Creo 2.0
<DATECODE> CREO® datecode such as M010, M020….
<JLINK_LOADPOINT> The location where J-Link is installed:<CREO_LOADPOINT>\CommonFiles\<DATECODE>\jlink
<JLINK_APP_TEXT> J-Link application resources directory


1.5.Additional resources

J-Link comes with very usefull resources, such as a documentation, examples…. These resources are available under the <JLINK_LOADPOINT> directory.

2.Java application

2.1.J-Link synchronious application jar

The J-Link synchronious application jar is located at :


2.2.Entry points

A J-Link java application must provide a class with two public static methods:

  • The start method : Called by Creo® parametric to start the application
  • The stop method : Called by Creo® parametric to stop the application

Both methods must be contained in a single public class with the following declaration :

public static xxxx();

Where xxxx is the method name.

3.J-Link resources

A J-Link application should provide a directory containing text resource bundles, images…Localized or not.This directory is designated as <JLINK_APP_TEXT>.

Note that in this tutorial, we consider non-localized resources as It is simplier.

Text files should be under <JLINK_APP_TEXT> and images should be under <JLINK_APP_TEXT>\resource

3.1.J-Link text resource bundle

A text resource bundle consists on a text file defining keys and values, as follow:










Text resource bundles are used by the J-Link APIs in order to render text.

4.Registry file

In order be loaded by Creo® parametric a J-Link application must be described in a registry file, which is a simple text where evey line consists on a predefined key and a value. The name of this file may be important (Depending on how It is registered) , please refer to 4.1.

Predefined key Description
name The name of the application
startup For J-Link application, the value must be java
java_app_class The java class of the application (including eventual packages)
java_app_classpath Extra Java classpath of the application, may be separated by ; (on Windows) and : (on Unix)
java_app_start The start method name. The signature must be public static XXXX();
java_app_stop The stop method name. The signature must be public static XXXX();
allow_stop Boolean defining if the application can be stopped.
delay_start Defines if the application is loaded on startup or not (value can be true or false)
text_dir The resource directory, more information will be provided later on this chapter.
end The end keyword, It does not needs value.

Note that more than one application can be declared in one registry file.

4.1.Registry file registration

There are various ways to make Creo® Parametric registering an application registry file (Not all ways are presented here, for more information, please refer to the J-Link User’s Guide).

  1. Define the registry file (Full path) in a creotkdat, protkdat, prodevdat, or toolkit_registry_file statement in the Creo Parametric configuration file.
  2. Put the registry file under <CREO_LOADPOINT>\Common Files\<DATECODE>\text and rename it to creotk.dat, protk.dat, or prodev.dat.
  3. Save your file with a dat extension and register It manually throught the user interface (Utilities >> Auxiliary Applications >> Register).

Option 1 is preferred for production, Option 3 is useful for development.

On the second part, we are going to develop a simple “Hello world” J-Link application.

Drive Mapping for Windchill™ prototype ready

Drive Mapping for Windchill™ prototype ready

Can we map Windchill as a standard network drive?

Can we allow the browsing of all the rich data held within my PDMLink™ system (File content of documents, CAD data, Attachments, Representations…) ?

Can we use navigation criterias to browse the data?

This requirement has been raised several times, and we have now a prototype allowing a fully controlled access to Windchill™ file data. Once installed this component allows Windchill™ to be mounted as if it was a simple network drive, the adminstrator can configure it to show whatever part of the system is required, for example a Product or Library (always respecting access control rules). This component uses the standard WebDav protocol.

This prototype supports mounting on Microsoft Office and Microsoft Windows (Unix, Sparc and others are also supported). Note that this is true access to the file data, unlike the out-of-the-box DTI that only makes this information available via Windows Explorer, which means that the Operating System and any of it’s applications are aware of the files, making it perfect to build integration to third party applications.

For example, you could give your service teams access to all the latest released service manuals held within your PDMLink™ system.

Drive Mapping using WebDav

We are keen to have your feedback on this, and so if you would like to suggest features or requirements that you would have for this type of tool please let us know.


CAD Loader for Windchill™ development started

CAD Loader for Windchill™ development started

We are always listening to our customers requirements, and one of the most frequent ones is the ability of easily load CAD data with controlled cost and risk. Following this, we decided to start the development of a CAD loader which will supports all major CAD tools. We are currently working on AutoCAD (Up to 2013 version) and will update you regarding the progress of the project.We will be using the latest technology to make a clean and fast loader.

CAD Data

We are keen to have your feedback your on this, and so if you would like to suggest features or requirements that you would have for this type of tool please let us know.