Engaging with the V1.3 release of the OSLC PLM Reference model from the release package	30/9/11

The OSLC PLM Reference model at V1.3 has been made available initially in a topcased project archive file with embed html and other files so it can be explored in two ways - via topcased or through the file system and browser.

These notes add some additional detail about the options to engage with the files and content in the release package.

No significant updates. Certain images below show V1.1 – they are equivalent for V1.3

Alternatively you can unzip the archive into a project directory and explore using your browser to launch and explore the navigators.

Option 1. To explore the release package via html through topcased

You can install topcased and proceed with the tips to import into topcased which can be found on the OSLC PLM Reference model wiki.

You will gain a model structure as follows 

You can now launch the initial reference model navigator via opening the index.html from the above navigator tree - there is an option in topcased to select the tool - if navigating you are likely to want to use the browser option, at least at first. Note how topcased remembers your tool choice and so defaults to the last used when using dble click.

Option 2. To explore the release package via html from the filesystem using your browser 

When unzippped the file system structure is as follows (in Windows XP for example

You can now launch the initial reference model navigator via opening the index.html with your browser from the Windows folder view. 

Continuing to navigate the release package 

From launching index.html in your browser from either of the above trees provides a simple menu of options

Alternatively you can navigate directly to the model of interest and use the relevant index.html in the file system structure 
e.g. using Option 2 in the Windows filesystem to locate the straup for the Implementation change model

The html structure and links are relative so you can launch the html in your browser from deeper branches within the trees, however moving beyond the top level branch of each of the three models will result in the SysML block level hot spots becoming inoperative. You can of course navigate via the tree to the appropriate jpgs.

See the additional note on "Whats stored where in the release package filesystem"

Note: This was tested in Windows XP using firefox 4.0

Gray Bachelor 
V0.1	30/9/11