SOLIDWORKS Manage: Understanding the Data Model SOLIDWORKS® Manage

 

Best Practice Information

Domain and Role/Product

<a class="s6m-tag-link sm-link" data-predicate="ds6w:what" data-tag-value="SOLIDWORKS Manage" data-type="internal" contenteditable="false">SOLIDWORKS Manage</a>

What's Covered? - Jump to each section using the Contents List in the top right!

  • Preface
  • The SOLIDWORKS Manage Data Model
  • Major Object Types by Module
  • Considerations for Microsoft SQL Server Installation

 

Revision History

Rev #DateDescription
1.0Oct 2020Document created.
2.0Nov 2022

Document updated for current release.

Added a new chapter to cover the considerations for Microsoft SQL Server installation

2.1Feb 2025Document validated for current release
    3.0Nov 2026Document formatted for 3DSwym
<strong>Note</strong>
<i>All SolidPractices are written as guidelines. It is a strong recommendation to use these documents only after properly evaluating your requirements. Distribution of this document is limited to Dassault Systèmes SolidWorks employees, VARs, and customers that are on active subscription. You may not post this document on blogs or any internal or external forums without prior written authorization from Dassault Systèmes SolidWorks Corporation.</i>
<i>This document was updated using version SOLIDWORKS 2025 SP1.0. If you have questions or need assistance in understanding the content, please get in touch with your designated reseller.</i>
<strong>Acknowledgments</strong>
<i>This document was authored by </i><a href="https://www.goengineer.com/" rel="nofollow"><i>GoEngineer</i></a><i> and reviewed by Dassault Systèmes SolidWorks Corporation.</i>

 

Preface

The best implementations of SOLIDWORKS Manage rely on careful upfront planning and good design intent. In the same way that good design intent makes a SOLIDWORKS CAD model more robust and parametrically scalable, so too does a configurable data management system like SOLIDWORKS Manage benefit with respect to scalability and long-term flexibility given proper planning and good design intent ahead of the setup and configuration. The idea is that the most successful implementations of SOLIDWORKS Manage are geared to support business use cases. These cases are built with an appreciation of the basic tenants of the software in a manner that fully utilize the software strengths, while working around limitations imposed by selecting certain configuration approaches. Therefore, a key factor for success with SOLIDWORKS Manage is to begin by understanding the data model in general. Thereafter, when considering a specific use case, it is possible to approach the implementation, and the imposed requirements thereof with an optimal design plan that works with the system rather than against it.

SOLIDWORKS Manage is a forgiving system in that you can change most settings and configuration options over time to refine and optimize the behavior of the software. However, there are certain key decisions regarding foundational structures (therefore inherently created early in the planning and implementation process) that do become permanent and difficult or impossible to alter later once the system is live and in use. It is with this cautionary note that the scope of this document is to review the overall data model of SOLIDWORKS Manage with an eye toward how the various structures of the software might relate to one another, and how you can best use and assemble them to the greatest effect.

<strong>Your Feedback Requested</strong>
We would like to hear your feedback and suggestions for new topics. After reviewing this document, please take a few minutes to fill out a <a href="https://www.surveymonkey.com/r/SolidPractices" rel="nofollow">brief survey</a>. Your feedback will help us create the content that directly addresses your challenges.

The SOLIDWORKS Manage Data Model

Every SOLIDWORKS Manage environment is a composite of many configured substructures. When taken in total, these structures define an applied data model around which it is possible to plan and build uniquely tailored implementations of SOLIDWORKS Manage. Each of these structures, by design, have their own unique behavioral and functional characteristics. You can configure and apply these characteristics very narrowly, or use them in combination with one another in novel ways to tackle a variety of data management challenges. For the purpose of this article, the scope of the discussion focuses on defining the SOLIDWORKS Manage data model as users and administrators from the perspective of the front-end graphical user interface (GUI) experience. The intention is to review and break down the SOLIDWORKS Manage data model as it applies to the practical day-to-day use of the system. This document is a resource to assist new and prospective customers by describing the software in a way that promotes well-informed decision making throughout the planning, setup, and configuration of the system. It is not the purpose of this document to discuss the data model from the standpoint of the data model in the Microsoft® SQL Server® database as it relates to the underlying tables and relationships with one another. Rather, the intent is to focus on the structures and their relationships as rendered on the front-end of the system, and as experienced through the applied use of SOLIDWORKS Manage by users and administrators.

While the intent is not to focus on the data model of the database, it is crucial to know that the SOLIDWORKS Manage database is in many ways one of its greatest assets and strengths. The database behind SOLIDWORKS Manage represents a purposeful, well-considered design intent on the part of the SOLIDWORKS Manage software development team, who have clearly placed a deliberative emphasis on having the database structure reflect the structures in the GUI as much as possible. This is to such a degree that one’s expectations and assumptions about the database (based on interacting with the GUI) align (more often than one would think) with the actual relational structures in the database. This is for example nowhere more in evidence then with respect to the objects in SOLIDWORKS Manage that appear in the GUI and their corollary array of database tables (dbo.OBJ…). From the front end of the system, objects are the key structures that manage all of the records and fields within the system. In many respects, they look and act like a spreadsheet or a table of data in the GUI, and one might expect (or hope) that there is a discrete database table provisioned for each of these objects anytime they are created in the system. This simple one-to-one relationship established between objects in the software and tables in the database, is not a requirement that SQL Server imposes. Instead, it is a choice by the development team to mirror the software design with the database design. The result is that writing queries for SOLIDWORKS Manage either for use internally, directly through various SQL query enabled features (such as link to third-party fields, reports, dashboards, etc.), or through any external means generally available to an open SQL Server data source, is usually a straight forward and simple affair. It is not always the case, but queries for data from a single object within SOLIDWORKS Manage frequently do not require joins within their SELECT clause. This is because most of the data for a given object exists in a single table. This emphasis on good design intent behind the SOLIDWORKS Manage database is evident even in small touches on the front end of the system. For example, every item property field and BOM field alike, defined within the administrative settings of an object always provides its own database ID for reference. Therefore, there is never any effort involved with finding the object.

This is all to say that the SOLIDWORKS Manage database maintains an efficient and well-ordered database that meets a user’s expectation and assumptions about the location of any particular data in the database tables. The SOLIDWORKS Manage development team have clearly developed a very functional system that is also approachable as a practical matter. Ultimately, this benefits everyone by encouraging and enabling the use of the database in a more direct fashion, in ways that greatly enhance the overall capabilities of the system.

  1. Environment

Envisioning the overall hierarchy of SOLIDWORKS Manage should begin by considering the entire system. In aggregate, there is no specific name or commonly accepted term for this system. Therefore, for the purpose of this discussion, the document refers to the system as an ‘environment’. For example, the configuration of an entire SOLIDWORKS Manage environment.

The information storage architecture for a single SOLIDWORKS Manage environment from the server side of the system is very straightforward. There is a single SQL Server database (not counting database replication scenarios for multisite deployment, or connected PDM vault databases) along with an accompanying Windows® file directory for the management of the SOLIDWORKS Manage file stores by its File Server service, which runs through Internet Information Services (IIS). It is possible to set up multiple SOLIDWORKS Manage environments that run concurrently, either from the same server, or from separate servers (usually for sandbox or testing environments). However, there is no ability to share data between separate SOLIDWORKS Manage environments from a practical standpoint, because they are intended as siloed data sets at that level.

An environment from the standpoint of navigating the GUI as well as from a feature and function standpoint is comprised of modules. Modules are then in turn broken down into at least one or multiple structures known as objects. The objects are the real workhorses of the system. They collectively contain and manage all of the individual records or items within the system. Objects may also (optionally) be configured to contain one or multiple sub objects known as special objects that each in turn contain their own collection of subitems within. The subitems within a special object relate to a specific parent item from the primary object in a many-to-one relationship. Each parent item can reference from zero to many subitems, however each sub item must be created from and associated to a single parent item on a strictly one-to-one basis. Therefore, there is a rigid parent/child relationship established between a given parent item and any number of subitems created from it.

 

  1. Modules

A variety of different modules are available for and included with the SOLIDWORKS Manage software. You cannot create or remove modules, however you can deactivate, expose, or hide modules for users based on their access rights. SOLIDWORKS Manage modules are not available for purchase separately as add-ons because all available modules are built in to every SOLIDWORKS Manage environment. There are six primary modules in the SOLIDWORKS Manage environment. These are:

Documents & Records, Processes, Projects & Cases, Reports, Relationships, and Resources.

Modules

These modules are used to define and manage special types (classes) of objects within the context of each module. Most modules are flexible with respect to the number or types of objects that they may contain, but a few of them are essentially hardcoded and come with predefined objects. Therefore, depending on the module, it may either support and encourage the creation and configuration of new objects, or conversely offer a predefined set number of dedicated objects. Within the flexible group of modules are Documents & Records, Processes, Projects & Cases, and Reports. These modules allow for the building and configuration of an effectively unlimited number of objects. Within the fewer hardcoded variety of modules are the Relationships and Resources modules that each come with a prescribed set of objects. With these modules, although their objects are configurable by adding custom fields, tabs, permissions, etc., you cannot create new objects or remove built-in objects from the environment.

In addition to the six primary modules, there are also three additional structures within every SOLIDWORKS Manage environment.

You might consider these structures as single purpose (dedicated) modules or objects in their own right, or perhaps simply as a floating collection of objects that are not defined within the confines of any specific module. These floating objects are Dashboards, Timesheets, and Tasks.

With respect to similar competitive software systems in the marketplace, SOLIDWORKS Manage is unusual in its approach to modularity in two key respects. The first is simply that Dassault Systèmes does not monetize SOLIDWORKS Manage modules individually from a licensing perspective. That is, you cannot purchase the modules separately. This speaks more about the approach to the market of SOLIDWORKS Manage as a complete solution, rather than a loose affiliation of modular components that are available for consumption, which is a common marketing strategy that similar systems use. The second aspect that sets SOLIDWORKS Manage apart from its competition is the overall uniformity and compatibility of the modules in general. Competitive platforms often offer various modules that differ from one another at a fundamental level. Sometimes this is readily apparent in the GUIs and administrative settings. At other times, the differences manifest at a deeper level, despite superficial similarities. This is often because developers write modules (as the name implies) at different times by different development teams, and maybe even through third-party acquisitions. Therefore, they might lack a cohesive form factor when it comes to the look and feel of the module, and from the actual use and administration as well. With SOLIDWORKS Manage however, this is not an issue because all of its modules and the accompanying objects and features come standard with the software. These components are built together explicitly using a common code base to natively integrate with one another. This contributes greatly to ease of use for both users and Administrators alike.

  1. Sections

Sections are simple structures that serve two functions. The first is to organize the objects within a module, and the second is to control the visibility of those objects. It is often the case within several of the SOLIDWORKS Manage modules, and particularly so with the Documents & Records, and Processes modules, that sections tend to accumulate and manage a large number of objects over time. Instead of displaying a flat list of objects in the GUI, sections organize a collection of objects in essentially the same way that Windows uses file folders. In addition to simply grouping objects, sections are also useful as a convenient way to limit visibility rights to an entire section and all the objects within as a collection. In practice, sections are commonly used to group objects according to the functional or departmental theme of an organization. For example, Quality Processes or Engineering Records etc. In addition, sections are also useful to group objects based on visibility rights or restrictions. For example, one might use a section to conceal a group of restricted objects that contain sensitive data. This delineates access to certain classes of objects at the section level rather than on a per-object basis.

The SOLIDWORKS Manage GUI focused on the Documents and Records Module

 

  1. Objects

Objects are the primary structures within SOLIDWORKS Manage that occupy the most time building and configuring an environment. SOLIDWORKS Manage is fundamentally a collection of configured objects (organized within modules) that are used to manage all of the records held within the system. When setting up and configuring SOLIDWORKS Manage, it soon becomes apparent that the various object types available throughout the available modules are all similar to each other in terms of both their GUIs as well as their administrative settings. The modules clearly all share a common code base with respect to the majority of their core features and functions. This means that regardless of the type of object that one is dealing with (Document, Record, Process, or Project etc.), they are all by-and-large configured in the same way and share most of the same core settings and features (Permissions, Fields, BOMs etc.). This is a strategic advantage for anyone who implements or administers a SOLIDWORKS Manage environment because it means that the skill set and training required to manage any of the various object types in a SOLIDWORKS Manage environment is largely the same. It is this thematic consistency that shortens the learning curve dramatically, which translates to rapid productivity and competence gains when implementing, administering, and using the software.

That said, the various types of objects within SOLIDWORKS Manage intentionally differentiate from each other in subtle but important ways. The different classes of objects are all equipped with their own unique functional capabilities that align with respect to the modules with which they are bound. In turn, these unique capabilities help to determine the specific business applications that might be best suited for an object to be configured and employed to manage.

For example, Process objects defined within the Processes module are equipped with workflow routing capability. Although this is not the only object type to employ workflow, Process objects workflows additionally have the unique ability to affect and have an effect on items from other objects and modules within the system that are associated to a process record. In contrast, a Project object within the Projects & Cases module, while not able to employ workflow, is in a similar way uniquely equipped with its own array of special features such as Gantt-chart functions that contain time-lines, phases, and milestones (among other special traits) necessary for performing project management functions.

The type of object chosen for use in a given situation therefore depends largely on the business application being addressed, such that an object’s applied function (as configured) is dependent on both the type of records to be managed, as well the functional capabilities of a given object type that are available for use by records created within the object.

  1. Items

The base record structure in SOLIDWORKS Manage is the item. In this context, the terms item and record are largely synonymous and generally refer to non-file-based records managed within a SOLIDWORKS Manage object. In effect, SOLIDWORKS Manage is an item-centric data management system that is primarily concerned with items in the sense of items within its database tables. This is in contrast to product data management (PDM) systems file or document-centric based such as SOLIDWORKS PDM that may also maintain a database that essentially contains a collection of items. However, the major emphasis for SOLIDWORKS PDM, especially with respect to its GUI, is on the management of tangible documents.

SOLIDWORKS Manage in contrast does not actually directly manage files themselves as a fundamental record type. Instead, the files are subordinate to items as attachments thereof. Therefore, understand the data model more clearly; it is important to define item management specifically in terms of the SOLIDWORKS Manage approach to the discipline.

  1. Defining terms

One possible way to define item management as a discipline is as a measure of whether a given software leans toward being more item-centric or more document-centric. This is always on a spectrum, and not a hard and fast line that can be drawn. The most straightforward way to approach the subject is as a function of which is emphasized from the front end of the system when interacting with the GUI. Again, SOLIDWORKS PDM is a great example of this idea. An item or record is not created within the SOLIDWORKS PDM database until a file is added in Windows File Explorer. Whereas with SOLIDWORKS Manage, you cannot add a file directly within the GUI until first creating an item from which to support the file as an attachment. Therefore, an item in SOLIDWORKS Manage is a prerequisite necessary to support file management.

For most object types in SOLIDWORKS Manage, files are neither required nor even necessary to create an item. All items in SOLIDWORKS Manage are generally capable of managing files to one degree or another. However, adding files to an item as an attachment is generally optional, and in some instance may not be allowed based on user rights. Even for items created within a SOLIDWORKS Manage Document object (which is the closest that SOLIDWORKS Manage gets to document management as a pure discipline), it is clear that the item record is still the dominant record in terms of the overall balance between the item and its primary file attachment. Meaning that within SOLIDWORKS Manage, even for items whose sole purpose is to manage a document, the item is still clearly a primary element.

Another approach to understanding the discipline of item management, and specifically how SOLIDWORKS Manage treats items within its data model, is by defining item management not in terms of the records themselves, but in terms of the relationships established between them. In other words, to define an item-centric system such as SOLIDWORKS Manage as a system in which the major focus is not merely establishing and managing items alone, but rather to facilitate the creation of myriad relationships in and amongst the items. The measuring stick then becomes how well, and on how many diverse and useful ways a system permits its records to link with one another. A less item-centric system such as SOLIDWORKS PDM will have relatively fewer methods to interrelate records with one another. Whereas a more item-centric system such as SOLIDWORKS Manage is more centrally focused on creating an ecosystem of links and relationships amongst all of the items it manages. In effect then, an item-centric system like SOLIDWORKS Manage is designed expressly to manifest its relational database within the context of the software GUI, to allow users to leverage the database to create and manipulate these relationships. No item exists within a vacuum. In the end, the point of managing items is not the management of the individual records themselves, but rather the benefits that come from weaving the records together in an effort to solve real-world challenges surrounding the management of complex data.

SOLIDWORKS Manage offers many ways for users to create relationships amongst items. It is all of these capabilities taken in total that represent one of the true core competencies of the software. To name just a few of the wide variety of methods that SOLIDWORKS Manage uses to create such links and relationships: there are parent/child structures in bills of materials (BOMs), or a unique process record hierarchy called a Sub-process. There are subitems from Special Objects that act like items within items. SOLIDWORKS Manage processes use an affected item relationship to influence and manipulate the lifecycle of associated items via the workflow. In addition, virtually every item type within SOLIDWORKS Manage supports a simple cross-reference form of relationship that is useful for everything from requirements management applications, to simply demonstrating associativity with one another. Project records are tied to their deliverables, and project tasks can in turn have their own attachments with items separate from the project record. Even at the very granular level of a single property field within a given item, an individual object field can be linked directly to other items (as a field) that in turn enables both the lookup capability for other item data, as well as field-by-field Where Used relationships. This is all to say that within SOLIDWORKS Manage, item management is defined not as an end in itself, but rather the as means to an end to foster a wide variety of relationships in and amongst the items being managed.

  1. Managing items

When taking a broader view of SOLIDWORKS Manage, it becomes apparent that it is indeed an item-centric system, and that regardless of whether the item in question is a Record, Document, Process, Project, or Task (etc.), they are all simply different types of items. Therefore, objects that contain and control items are structures primarily concerned with the business of item management. While this becomes evident after using SOLIDWORKS Manage for any period of time, it is worth using this notion to reframe the conversation to begin discussion about objects as a type of vault for the management of item records. This is because each object individually defines every aspect and characteristic of their internally managed table of item records. This is true on an absolute basis with regard to the capabilities inherent to a given object. It is also true from the relative perspective of the allowed features and functions available for use on a given item, with respect to a user’s permissions within an object. This has important implications about how many objects are created and used, and for what purposes. Once created, items are locked within each object permanently and cannot be moved or transported between objects. In simplified terms: one needs to consider carefully whether it might be better for example to use a larger number of separate objects to segregate the variety of record types being managed within separate object tables, or to define a fewer number of objects, or even a single object capable of managing a variety of item types internally. A single object might use classifications or folders, or both, to sort and segregate different classes of items while still managing the items within a single object. So typically, while SOLIDWORKS Manage is neither configured exclusively as a collection of single-purpose objects (each managing a few item types per object) or as a single monolithic object managing every type of record item, this is the backdrop to an implementation as a spectrum of choices to make. Any given situation warrants balancing requirements more to one side than the other.

These questions and choices are central, and later become irrevocable once the system is live and in use. There is no correct answer to the questions because the choice depends on the use case business requirements and security concerns.

  1. Common traits

SOLIDWORKS Manage uses the item record across the various modules and objects. Largely, all items share a common set of features or traits as a basic feature-set. The might also have special capabilities to adapt them for use to a specific application such as process or project management. As with most things in SOLIDWORKS Manage, these features are governed by the objects within the system as to which items are present, and which are allowed based on permissions. An exhaustive list of all features that items have in common would be very long. However, a few features warrant specific mention to establish a picture of the basic capabilities of items throughout the system:

 

Significant traits and features common to most item types in SOLIDWORKS Manage

 

  • Items: The base record structure in SOLIDWORKS Manage is the item. The terms item and record are largely synonymous and generally refer to non-file-based records managed within a SOLIDWORKS Manage object
  • Properties: Items have configurable properties for which one can create and manager various types of both system-level fields and custom fields, and attributes.
  • Related Files/File Attachments: Items are capable of managing direct file attachments not as a reference to another record in the system, but in a direct sense such that an item might manage one or many files that exist in the system only to supplement a specific item.
  • BOM: Items can represent and directly manage a BOM as a form of a special parent/child relationship amongst a group of related items. Regardless of whether an item is from an object within the Documents and Records module that is specifically meant to manage BOMs, or is a Process or Project item for example, all items can make use of the SOLIDWORKS Manage BOM functionality. In other words, a Project can have a BOM structure as easily as can a dedicated BOM record. In addition, SOLIDWORKS Manage has the capability to extract and shows the BOM of a SOLIDWORKS Assembly file. A pre-condition for that, is that the components files are present in SOLIDWORKS Manage environment.
  • Special Objects: Nearly all objects can define Special Objects that relate to a table of subitems. Therefore, every primary item might relate to its own family of children or subitems.
  • References: Simple references used as cross-references can be enabled between items throughout the system between any number of objects.
  • Tasks: Tasks are items within a separate module or object in their own right. All non-task or regular items throughout the system have a special reference type that allows them to have a Used On and Where Used relationship between tasks and items. In this relationship, regular items reference tasks, and tasks reference the items to which they relate. The Task items are used for assigning activities to one or more Users, known as Resources, inside Projects and Processes.
  • Reports: Reports in SOLIDWORKS Manage come in two forms. The first is a type of global reporting capability that compiles data from across modules and their objects and respective item tables. This style of reporting is in fact its own module within SOLIDWORKS Manage, and the Reports are items in their own right. However, it is the second type of reporting that is shared in common across all items. This report type is defined within an object to report on specific items within that object. This report type more narrowly focuses on reporting data from a specific item, and is typically used for forms in the sense of a report as a printable version of an electronic item record. This type of report is common throughout SOLIDWORKS Manage objects and are therefore accessible by all items within the SOLIDWORKS Manage environment.

Major Object Types by Module

This section provides information about the major objects that are used and managed within SOLIDWORKS Manage. The emphasis is to review the primary characteristics of each object that differentiate them from one another and to consider their applicability for a given situation.

  1. Documents and Records Module:

The Documents & Records module is at the heart of SOLIDWORKS Manage. This module contains all of the principle items and BOM records that are the focus for the rest of the structures throughout the system. For example, Processes, Projects, and Reports. This module is the central focus around which everything else has been built to support.

While the term record is generally synonymous with the term item in the system as a whole, the term does have a specific nuanced meaning within the Documents & Records module in particular. The term Record (capital R) as a proper noun in this context is used to differentiate between two distinct types of items based on the two primary object types available in this module: the Record object type and the Document object type. Each of these objects (despite their names) fundamentally manage items. Their relationship and capabilities with respect to file management are the key differentiating factor.

  1. Document objects

The Document object is designed to manage items whose primary characteristic is that they require a primary file attachment. This means that every item created within this object type requires a single file type attachment. This implies that the item directly represents the file and vice-versa. In other words, the sole purpose that the item exists in the system is to manage the primary file attachment. SOLIDWORKS Manage uses this object type for the management of file-based records for document and source control records management.

When initially creating a Document object, you must declare an object as either revision controlled, or as not revision controlled. This setting becomes permanent, meaning you cannot change it later. This creates two distinct variants of Document objects. A revision controlled object means that the object is enabled to track and record the revision and version history created subsequent to all of the check-in and release operations that happen over time. For not revision controlled objects, the nuance is not that such records cannot have revisions. Contrary to expectations perhaps, items within a not revision controlled object can in fact receive revisions and can also be released in terms of lifecycle status. It is rather that they do not maintain a history record of the revision changes. The crux of the decision is not as one might expect: To Revision or Not To Revision… Instead, it is whether keeping a record of the revision history is important or not.

  1. Record objects

The Record object type is meant to manage items in the most classic sense of the term, as in a database-derived record that has properties and attributes and that does not require any relationship with a Windows file record. From a technical standpoint, every object type in SOLIDWORKS Manage fundamentally contains and manages item records. However, items managed within a Record object are the purest expression of this concept. For example, compared to items from Projects, Processes, or Document objects, a Record object has no agenda beyond the core business of item management, that is, managing attributes and the relationships between themselves and other items in the system. The Record object differs from its sibling Document object in that it is not capable of (or burdened with, depending on one’s perspective) managing a primary file record. Like all items throughout SOLIDWORKS Manage, the items within a Record object, can each manage an array of file attachments (as reference documents) but these are always meant to be supplementary file attachments that are not central to the item itself in contrast the primary file of a Document object.

Like the Document object type, a Record object must also have a classification of either being revision controlled or not revision controlled, and thus like Document Objects there are two distinct variants of Record Objects based on this setting.

  1. PDM objects

The PDM object type is a hybrid of the Document object that is in most respects the same as the regular type of SOLIDWORKS Manage Document object, in that items for this object each require a primary file attachment. However, this object type specially integrates or synchronizes with a SOLIDWORKS PDM Professional vault. The PDM object is therefore a hybrid object type in the sense that it bridges the SOLIDWORKS Manage and SOLIDWORKS PDM Professional systems and manages elements from both systems. The item record managed by a PDM object is an artifact managed within the SOLIDWORKS Manage database. Whereas, the primary file attachment is not managed by the SOLIDWORKS Manage file server (as are the file attachments from all other item types in SOLIDWORKS Manage. Instead, the primary file attachment is managed within the associated SOLIDWORKS PDM vault. The primary file is managed by a regular or non-PDM Document object on the backend by the SOLIDWORKS Manage file manager. Whereas, the primary files attached to items within a PDM object are files from the SOLIDWORKS PDM vault. This relationship comes with several implications and complications, the foremost of which is that these files are managed by two separate but integrated systems, two databases, two systems of permissions, lifecycles, attributes, etc. Therefore, effective management and configuration the PDM object type in SOLIDWORKS Manage is necessarily more complicated than for a regular type of Document object.

SOLIDWORKS PDM by itself is light on item-like features, because its focus is more purely that of a file management system for CAD source control. Because of that, another way of thinking about a PDM object is essentially as a framework to facilitate formal item management of files in a SOLIDWORKS PDM vault. SOLIDWORKS Manage adds a true item record capability layer on top of the classic PDM system such that within SOLIDWORKS Manage, it is actually the item that represents the PDM file within SOLIDWORKS Manage. Making use of any PDM record in SOLIDWORKS Manage (for example within a BOM or a Process record), does not actually directly make use of the file from PDM, but rather the item created by SOLIDWORKS Manage to manage and represent the file within this system.

  1. Processes Module

The Processes module is a dedicated module that manages only a single type of object with the primary role of the focused management of process and workflow for affected items.

 

  1. Process objects

It is important to define a couple of terms in context with references in this document. First, understand that the terms process and workflow are not synonymous with each other. In SOLIDWORKS Manage, a process is a type of item record (such as ECO, CAPA, NCMR, etc.) that one defines by creating a specific object in which to manage these record types. By contrast, a workflow is the decision tree or route as one might imagine as a flowchart diagram. A Process item follows a workflow to collect approvals and come to a determination. Therefore, a process in SOLIDWORKS Manage is actually an item, and a workflow is the path that Process record follows from a defined start point, through various stages, and ultimately to a conclusion. In this respect, do not confuse the term workflow with the term lifecycle in the context of SOLIDWORKS Manage, in that processes are workflow-ed, which means that they have a defined start and end; and once a Process record finishes its workflow, that process is complete and never again cycles to begin a new workflow route. In SOLIDWORKS Manage, it is predominately items from the Documents and Records module that are subject to a lifecycle. In fact, the primary function of a process item is to change the lifecycles of attached references known as affected items. Revision and Lifecycle are the two primary attributes that are affected in this sense by process records. In contrast to workflow stages, lifecycle statuses (as the name implies) are cyclical and repeat over time. Whereas, a workflow as followed by a Process record is a one-time operation. If a new decision is needed, a new unique Process record is created and routed through the workflow on its own. Process objects as a class of object in SOLIDWORKS Manage have two distinct capabilities that set them apart from most other objects in the system. These being: workflow and affected items.

Workflow: Every Process object defines a specific workflow route that all items managed by that object must follow. In other words, workflow in SOLIDWORKS Manage is specific to each Process object as it defines a single allowable route or flowchart per object. SOLIDWORKS Manage might therefore have a theoretically unlimited capacity to define different workflows. However, the limiting factor is that it allows only one workflow map per object. All items within a given object table are limited to using a given map as defined by its parent object. Of course, workflow maps may be used dynamically according to conditional logic, as in a single flow diagram with multiple allowed routes. However, it is still the same overall map used by every item within a given object.

Affected Items: Though it is not a unique ability that Process objects can define and manage workflow routing (see Cases in the next section), this second defining characteristic is a distinct capability of the Processes module and the Process objects within. These objects have a unique reference type used for what is commonly referred to as Affected Items management. This special reference type allows a Process item to manage a unique type of relationship with other external items throughout the system in the manner of a hierarchical parent and child relationship that allows a Process item to directly act upon and affect changes upon items attached in this manner. In general, item types within SOLIDWORKS Manage have a sort of generic ability to create references amongst themselves in the sense of a cross-reference (Reference) feature within SOLIDWORKS Manage for the purpose of linking and showing associativity. However, an item cannot use these reference types affect or have an effect on another item directly. On the other hand, Process objects are uniquely equipped to do just this, and use this capability primarily for Change Management types of applications where it is necessary for a Process item record (such as ECRs, ECOs, ECNs, etc.) to revision and/or drive lifecycle changes down to all of their affected items.

  1. Projects & Cases Module

This module reflects the names of its two respective types of objects: Projects and Cases. This paring is a bit of an odd marriage of two very different object types. Projects are an object type that manages Project records (items). This object type is typically used for such applications as Engineering Project Management (Gantt charts, resource utilization, etc.). Whereas, Cases on the other hand are a type of process object (with workflow capability) that share more in common with objects from the Processes module than with its sibling Project object.

  1. Project Objects

The Project object is the central toolset within SOLIDWORKS Manage that enables the software to deliver Project Portfolio Management (PPM) as a business application. Each Project object manages within a collection of Project records (items) that in addition to sharing the core capabilities common to all SOLIDWORKS Manage items are equipped with an array of features to facilitate project management. This incorporates all of the usual features that one expects from a project management tool, a few of which include: Gantt charts and timelines and their accompanying phases, milestones, predecessors, critical-path calculations, etc. Project items importantly also have different means at their disposal with which to track time and measure resource utilization, such as Tasks and Time Sheets that are unique to this object type.

 

 

It is possible to create one or multiple Project objects to manage different project types and templates. Instead of keeping all project records in one basket so-to-speak, creating and managing multiple Project objects can be an effective way to segregate different project types. This is very useful if the various project types have for example different custom attributes, or require different collections of project Gantt templates, etc. Each object can internally manage and make use of its own collection of predefined project templates to initiate projects (similar to a typical project management system like Microsoft Project®). However, the use of multiple objects by SOLIDWORKS Manage allows for a greater range of project-type differences to define between the projects from separate objects. For example, distinct Project objects may be used to organize and support projects for different engineering disciplines, departments, or products, or they can be based on data access and permissions issues. As an example, imagine configuring one Project object to support Engineering Project Management with a focus on New Product Development. Now imagine configuring another Project object to manage Sustaining Engineering and a third Project object to manage project management of Equipment and Facilities, etc.

It is immediately evident that the SOLIDWORKS Manage project management capabilities represent a collection of solid project management tools. However, where the application sets itself apart from other project management systems and becomes a compelling platform from which to practice PPM is in some respects not directly attributable to the specific features and functions of the Project object type itself, but rather to three main capabilities that are ubiquitous throughout the environment across all modules:

Data Analytics: The first of these features of the SOLIDWORKS Manage environment that when combined with the project management-specific tools make this such a compelling platform are the data analytics tools available for dashboarding and reporting. These tools are typically used as a business intelligence suite across all areas of the system. However, the tools are essential components for project management to manage a portfolio of projects effectively, in that the data analytics tools facilitate the aggregation and reporting of data across multiple Projects and Project objects. In other words, if a company only has one project to manage, then data analytics is likely of little or no concern. However when managing multiple projects (in parallel), then reporting and dashboarding become a crucial capability. Like all objects within SOLIDWORKS Manage, Project objects benefit from the same array of reporting tools. This includes both object-specific reports defined within an object to manage their own (internal) set of reports, as well as more global reports and dashboards that can report data across separate modules and collections of objects, and against the multitude of items within these objects. Therefore, it is the reporting and dashboarding capabilities that allow Project Managers (PMs) to examine virtually any aspect of SOLIDWORKS Manage (and especially including its project records) that round out SOLIDWORKS Manage as a true PPM. Project Management and Data Analytics work hand-in-hand as inseparable aspects of the same endeavor.

SCRUM: The second compelling aspect of the SOLIDWORKS Manage project management tools is that they are designed for use in a decentralized SCRUM type of manner where system users are equipped and encouraged to report their own progress (via assigned tasks and/or time sheets etc.). As with many similar tools where only the PMs have access to the software, SOLIDWORKS Manage does not leave the management of project status updates solely to the PMs. In other words, SOLIDWORKS Manage lessens the PM’s burden of having to constantly track people down and figure out the status of particular project or phase in terms of the planned schedule.

Centralized data model: This is the third aspect of project management that distinguishes SOLIDWORKS Manage from other project management systems (especially projects that relate to the development of new products). SOLIDWORKS Manage Project records are managed as items within the same database as all of the other documentation and source control data that relates to the actual product deliverables (CAD data, Documents, BOMs, Process and Change management records, etc.). What this means is that SOLIDWORKS Manage does not practice project management in the abstract as some systems do, in a sense pretending to manage projects. It is rather the case with SOLIDWORKS Manage, that the projects and all resources and deliverables can be connected to the projects as tangible records. These being the records and project deliverables that constitute much of what any given project is supposed to manage. Instead of being maintained in disparate and unconnected software systems such as network drives, desktops, or paper hard copy, etc., SOLIDWORKS Manage enables a more interconnected project management experience. Dassault Systèmes SolidWorks Corporation refers to SOLIDWORKS Manage officially as a Distributed Data Management system, not because it manages data in a distributed fashion, but because it collects and centrally manages data typically stored in a distributed fashion by companies throughout various data management systems and filing cabinets.

  1. Case objects

Despite being paired in the same module, Case objects and Project objects do not share any special features of note in common except capacity planning. As the name implies though, Case objects are meant for use in Case management, not Project management. Cases are fundamentally a type of process record. The closest comparison within the SOLIDWORKS Manage environment for a Case object is therefore in fact a Process object within the Processes module. Cases and processes are analogous to one another in much the same way as are Record and Document objects, in that they are nearly identical except in one very fundamental respect. With Records and Documents, it is the ability or requirement of the Document object to require their items to manage primary file attachments that set the two object types apart. With Cases and Processes, both are equipped with the ability to define workflow routing for their item records. This allows management of all the typical sorts of workflow responsibilities, such as defining stages and approvals, making decisions, and so on. The area in which these two object types differ is in the ability (or lack thereof) to manage affected items. A Case is essentially a type of process record that lacks the ability (unique to Process objects) to attach items from other objects as a special reference type that gives SOLIDWORKS Manage processes the ability to affect and have an effect on referenced Items. Cases, in other words, apply workflow essentially only for themselves and cannot directly affect other items throughout the system. The Case workflow route is meant exclusively for managing the Case record itself and is therefore incapable of affecting other items in the ways that a Process record can. Cases have normal references in the sense of a cross-reference or an attribute-based link to items elsewhere in the system. This is common to items throughout SOLIDWORKS Manage. However, Cases are crucially unable to affect change upon these references. This fundamentally sets them apart from Processes.

As an example of a Case vs. a Process applied in a practical sense, consider the Return Merchandise Authorization or RMA. This is a common business record that companies commonly manage in such systems. This type of record is used to track customer requests to return products, so as to begin to document an issue for warranty and quality control purposes, as well as to determine workflow and decide whether to authorize and therefore accept returned goods from a customer. Often times an RMA could easily be managed within SOLIDWORKS Manage as either a Case or a Process object. Therefore, the question would arise as to which of these objects would be the better use for this application? Both objects can facilitate a workflow determination. Both objects can have references to companies and customer contact records, part numbers, BOMs etc. In addition, both objects can link in various ways to the data and parameters held within SOLIDWORKS Manage related to the goods pending authorization. So which object type would be the better choice for an RMA? In this situation, the decision would likely come down to whether the design intent for the RMA is to merely reference applicable product records in the system, or whether the intent is for the RMA to affect the object directly. For example, change a lifecycle status, update properties or attributes, and other actions. This is likely the sole factor that might determine the best use case for using Cases vs. Processes in a given application.

Considerations For Microsoft SQL Server installation

Whereas SOLIDWORKS Manage is implemented along with SOLIDWORKS PDM Professional for managing the files as Items inside SOLIWORKS Manage, it is important to remember that both databases (SOLIDWORKS Manage and SOLIDWORKS PDM Professional) needs to be on the same SQL Server instance.

In addition, it is necessary taking in account the fact that both databases (SOLIDWORKS Manage and SOLIDWORKS PDM Professional) can increase their size easily due to the database settings and their usage. This means that a Database Server that is hosting one or both databases could compromise the usage of the SOLIDWORKS Products if few resources in terms of drive’s space are available on the Database Server itself.

Therefore, it is strongly recommend reading the SOLIDPractices - SQL Server Performance whereas a new Microsoft SQL Server installation is planned or it is needed reviewing the current SQL Server Configuration.

<i>We hope that you find this document informational and useful and request that you leave a </i><a href="https://www.surveymonkey.com/r/SolidPractices" rel="nofollow"><i>brief feedback</i></a><i> about the topics that you want us to cover in the next revision of this document. Click </i><a href="https://my.solidworks.com/support/solidpractices" rel="nofollow"><i>here</i></a><i> for a complete list of SolidPractices documents available from DS SOLIDWORKS Corp.</i>
Comments 0