Skip to main content
Skip table of contents

Operations Manual

About this Manual

This manual provides comprehensive guidelines and step-by-step instructions for working with HaloCAD solutions (Monitor and Protect). For installation and configuration instructions, please refer to the "Installation Manual" shipped with the product package.

How does it Work?

At a high level, HaloCAD workflow involves the following steps: 

Windchill_How Does it work-.png

HaloCAD for Windchill

  1. Step 1: File check-out/check-in

    1. A user creates a new CAD / Office document or opens an existing workspace object from the embedded browser.

    2. Applies, check-out (download), or check-in (upload).

  2. Step 2: File transfer through PLM HaloCAD component
    HaloCAD for Windchill collects the metadata and retrieves the action derivation from the HaloENGINE. File processing is based on the following parameters:

    1. If HaloENGINE Service=Local, send the file directly to the (local) HaloENGINE Service for file handling either in “File path” or “Stream”.

    2. If HaloENGINE Service=Remote, the metadata and label information from the HaloENGINE is sent to the remote HaloENGINE Service for file processing

  3. Step 3: Encryption/decryption
    According to the metadata collected, the action is executed in the file.

    1. The file will not be processed if any inappropriate action is present or no action is available. It will be downloaded without any changes.

    2. If a suitable action with a label is found, the file is sent to the HaloENGINE in local mode or to the HaloENGINE Service in remote mode to further file processing. Note: In the check-in case, the label is removed, and then the decrypted file is stored in Windchill PLM.

    3. HaloCAD prevents file downloads if a block action rule in HaloENGINE is properly configured.

  4. Step 4: Processed file sent to the user
    The file is encrypted with the derived label and returned to the user through HaloCAD for Windchill.

  5. Step 5: Monitor log
    The event is captured by the HaloCAD component and forwarded to the monitor log of the HaloENGINE.

How to Protect a CAD File?

This section describes how to protect Creo and office files via PLM. Note: We recommend referring to the "Operations Manual of HaloCAD Add-on for Creo" to know more about standalone HaloCAD protection scenarios.

Fulfill the Requirements

  1. HaloCAD for Windchill needs to be installed and set up.

  2. HaloENGINE Service must be installed and configured.

  3. HaloENGINE must be installed and configured. 

  4. The Classification Engine must be configured.  For illustration purposes, a simple classification profile is explained here.

    1. Step 1: Enter a name for the profile.

      Sample Profile.png

      Sample profile

    2. Step 2: Configure classification properties and their values.

      Classification Schema Configuration.png

      Classification properties

    3. Step 3: Create classification rules based on metadata types. Note: If you want to use your metadata, specify it on the Custom Metadata page of the HaloENGINE admin portal. Please refer to the Custom Metadata section of the HaloENGINE Installation and Configuration manual.

      Classification rules Windchill.png

      Rules

    4. Step 4: Create an action rule to label and block.

      Action Rules Windchill.png

      Action rule for labeling

      Action Rules Windchill_Block.png

      Action rule for blocking

    5. Step 5: Assign Systems to the profile.

      Assign Systems Windchill.png

      Assign Systems

  5. HaloCAD add-on must be installed.

Download a Protected File

Follow the instructions below to protect CAD files via PLM:

  1. Go to Windchill Workspace, download a file via Export from Workspace/Open in Creo.

  2. Alternatively, from Windchill Commonspace, download a file using the Check out and Download option.
    Results: The downloaded file is labeled as defined in the HaloENGINE. The encryption settings from the label are enforced and remain with the file wherever it is stored.  

    What to do next:

    1. If you are an authorized user, you can modify the label and save the file.

    2. If you wish to view the audit log, you can view the export event in the HaloENGINE audit log.

Blocking a File Download

  1. Go to Windchill Workspace and download a file using Export from Workspace/Open in Creo.

  2. You can also download a file by using the Check out and Download option in Windchill Commonspace.

    Results:

    1. The action rule for block configured in HaloENGINE prevents file download. As a result, no file download occurs.

    2. Refer to the monitor log for further information.

Common Scenarios 

This section presents some common scenarios for illustrative purposes and is meant to provide general guidelines.

How to Open a Protected CAD File? 

Prerequisite: Before opening the protected file, make sure the HaloCAD Add-on for Creo is installed.

  1. Click on the protected file.

  2. The first time when you try to open a labeled file, HaloCAD will prompt you about the Microsoft Sign-In Assistant.

  3. Click OK when prompted, "Microsoft Sign-In Assistant will be invoked and the user credentials will be cached."

  4. Follow the on-screen prompts to complete the authentication process.
    Results:

    1. On successful confirmation, the file will open.

    2. Users could experience different access results for the same document based on the policy settings. For more details, refer to the "Operations Manual of HaloCAD Add-on for Creo".

Example 1: Application ID as the Owner of the File  

The following figure shows an example of an Application ID that is used to initialize HaloENGINE Service. This Application ID will be the owner of the document by default, however, a static email or a user who logs in to Windchill can also be an owner of the downloaded file if specified in HaloENGINE. Please refer to examples 2 and 3.  

EX1_Application ID as the Owner of the File.png

Application ID as the Owner of the File

Example 2: Static Email as the Owner of the File

The following figure shows an example of an email address configured in the HaloENGINE. This email address will be the owner of the exported document. 

EX2_Static Email as the Owner of the File.png

Static Email as the Owner of the File

Example 3: User as the Owner of the File

The following figure shows an example of a PLM logged-in user who has become the owner of the document. In order to achieve this, the Owner configuration must be set to "user" on the HaloENGINE Admin portal. The exported document will have the email address of the currently logged-in user as its owner.

In case, the user who logged in to Windchill PLM Server does not have an email ID, then the Application ID (which is used to initialize HaloENGINE Service) will be the owner of the document.

EX3_User as the Owner of the File.png

User as the Owner of the File

Example 4: File Upload and Download 

The following is an example of an upload and download sequence in Windchill PLM integrated with HaloCAD. Note: Non-office files are also supported (e.g., .txt and .PDF). For illustration purposes, an Excel file is used here.

  1. Open the Creo Parametric application and enter the user credentials of the PLM server.

  2. Navigate to your Windchill Commonspace.

  3. Click the New Document option, the New document screen will appear.

  4. Select the product type as Document and select the protected file using the Browse option. [Please note, in this example, the file (Bill Of Materials.xlsx) which is going to be uploaded is already protected with the HaloCAD INTERNAL label].

  5. Click the Finish button.
    Results:

    1. The file is uploaded to the Windchill.

    2. During the upload/check-in sequence, the original label HaloCAD_INTERNAL is removed, and the decrypted file is stored (checked-in) in Windchill PLM.

    3. The upload/checked-in event is logged in the HaloENGINE.

  6. Check-out sequence: From the list, select the previously uploaded file and click the option - Download PDF or Download Text File or Download Unknown buttons available in the workspace.
    Results:

    1. The file is downloaded to the default location.

    2. During the download/check-out sequence, the file is exported from Windchill with a new label HCAD Confidential which is defined in the Classification Engine.

    3. The download/check-out event is logged in the HaloENGINE.

  7. The below figure shows the difference between the uploaded file into Windchill and the downloaded file from Windchill.

    Upload_Download sequence.png

    File upload and download Sequence

Customer Support

Please be ready with the below-listed information before contacting our team to help you with the issue you are experiencing. The data that you provide will help us serve you better.

  1. Full contact details.

  2. HaloCAD component and HaloENGINE build version.

  3. Date, time, and description of the error (if possible, provide screenshots).

  4. What (if any) third-party products (software or other) were used in conjunction with our product?

  5. Any other information necessary to reproduce the error.

Secude offers help and support through

  1. Technical support email: support@secude.com
    If you choose the email option to contact us, please provide your company details with a detailed description of the issue and attach the log file (if any). Our representative will respond to your email inquiry.

  2. Phone support: Call +41 41 510 70 70  to talk to our representative to diagnose and resolve the technical problem.

Other resources

Please visit https://secude.com to know about upcoming events, press releases, and to download whitepapers.

Documentation Feedback

Secude understands the importance of technical content when attempting to gain product knowledge and strives to continuously improve product documentation to ensure that users receive the information they want. To provide feedback on the documentation, please send an email to documentation@secude.com. Please include the following details in your feedback:

  1. Product name and version

  2. Documentation topic

  3. Details of the suggestion or error

The technical documentation team will consider your feedback and address it in future documentation updates.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.