Building a Blueprint Using CygNet Designer
The blueprint that describes your system is the foundation on which all Designer functionality rests, so it is important that it accurately describes the complexity of your system’s design. Creating a blueprint for your system is therefore not a trivial task.
See the following subsections and topics for more information:
- Sample Blueprints
- Use the Designer
- Configure Points
- Configure Tables
- Configure Facility Attributes
- Configure Facilities
Sample Blueprints
There are two sample blueprints that come with the Designer. These blueprints describe the data model for our reference CygNet implementation, CygNet for Production. They are located in the Designer\Blueprints folder where Designer is installed:
- Blueprint_CygProd.blu — A blueprint for the basic CygNet for Production model
- Blueprint_CygProd_Sample_Data.blu — A blueprint with additional configuration to match the sample data distributed with CygNet for Production
If your system was based on CygNet for Production, it might be valuable to start with these blueprints rather than starting from scratch. Even if your system uses a different model, hopefully these samples will help.
If you don’t know where to start with your blueprint, load Blueprint_CygProd.blu and review its points, tables, facility attributes, and facilities to see how you might lay out your own system’s model.
Use the Designer
The Designer is intended to be the primary interface for creating and editing blueprints.
Note: Only one blueprint can be loaded into the Designer at any time. If you create a new blueprint or open an existing one, your current blueprint will be unloaded. Any unsaved changes will be lost.
Under the Define section on the navigation menu, your blueprint is broken into these sections:
- Points
- Tables
- Facility Attributes
- Facilities
Import from an Existing System
Each of the following sections allows you to define everything manually. However, with any complex system, you will have many aspects of your blueprint to configure. Therefore we recommend using the available Import options wherever possible. These will allow you to leverage an existing system’s configuration in building your blueprint to make the process faster and more efficient.
More:
Building a Blueprint Using CygNet Designer to Configure Points
Building a Blueprint Using CygNet Designer to Configure Tables
Building a Blueprint Using CygNet Designer to Configure Facility Attributes
Building a Blueprint Using CygNet Designer to Configure Facilities
