Damara Tern FAQ
Jump to:
Trackables & operations ·
Operation search ·
Add a machine ·
Additional fields ·
Recording more information ·
Sensitive content · Content creation · Contact
What are trackables and operations?
The Damara Tern data model is built around the concepts of operations and trackables, defined as follows:
- Trackable: Any physical or digital component that can be subjected to an operation (such as parts, builds, materials, etc.).
- Operation: Any action performed via the use of a machine (such as print, cure, heat treatment, blue light scan, microscopy analysis, tensile test, etc.) or human interaction (procurement, annotation, registration, manipulation, etc.).
How can I search for operations?
You can search for operations using the filters, which are available on the operations list page or from the home page via Operations → Search.
On the operations list page, a quick filter (shown below) allows you to search for operations by name.
For more detailed queries, use the Advanced search button next to the quick filter. This lets you filter operations using multiple criteria such as operation type, date range, machine, project, and more. The interface also includes toggle filters to quickly narrow results to operations where you are listed as an operator or that are associated with projects you belong to.
How can I add my machine to the system?
Use the contact form to request a new machine.
Please include the following information in your request:
- Machine name
- Manufacturer
- Model
- Serial number
- Procurement date (date of on-site arrival)
- Owner institution
- Location (building, room number)
- Operation type (such as L-PBF, DED, machining, wire EDM, etc.) and/or technology
Once the machine is added, you will be able to start recording operations.
What are operation contextual details and additional fields?
When you create a new operation, Damara Tern records contextual details that describe what was done, when, where, and how. Required details include the date, machine, operator, and any associated projects.
In addition, some operation types or machines support additional fields. These fields let you capture process-specific details that an operator may want to record in order to identify, understand, or reproduce a process. While some of this information may exist in log files or time-series data, collecting it directly in the operation form makes the most relevant details easy to find later.
You can think of additional fields as information you would want to see immediately, search or filter by, or or naturally write down write down when running the process or experiment.
I can create an operation, but I need to record more information to track my process.
Damara Tern supports extended field entry in addition to the default contextual details recorded for operations. If the existing fields are not sufficient for your process, a dedicated entry form can be added to collect additional information for the operation type and/or machine.
You can request an entry form by using the contact form and providing an initial list of the fields you would like to record, along with desired labels and units if relevant.
Keep in mind that additional fields should focus on information that operators will actually use. Capturing only what is meaningful helps keep entry forms clear, usable, and effective.
I can browse content, but I cannot add operations, content, or files.
Content creation permissions depend on user role. Only users labeled as Contributors and Operators can upload files and create new operations.
You can find more information about permissions and access restrictions on the sensitivity and permission documentation page.
If you need permission to create or edit data, please request access from the appropriate project owner or administrator.
How can I set up sensitivity, CUI, and distribution labels?
Damara Tern restricts access to operations and trackables based on CUI markings, DoD distribution markings, project affiliation, and the user's access status.
When an operation or trackable has sensitive markings, it is visible only to users who are allowed to access that content. This usually includes the operator for the operation and the users who belong to the related project, as long as their access status satisfies the content markings. Users who do not meet those requirements will not be able to view the protected content.
By default, sensitivity and marking values are inherited from the project associated with the operation or trackable. These defaults can be updated during creation by using the custom CUI form builder shown below.
For more details about how roles, project membership, and sensitivity markings work together, see the permission system documentation.
Why can I not see sensitive content?
Some data in Damara Tern is access-restricted based on CUI and DoD distribution requirements.
By default, users registered as External Viewers can only access publicly released content. Contributors and Operators may have access to additional internal data, along with collaboration permissions such as uploading files or creating new operations.
Sensitive content is filtered according to the CUI labels and distribution controls applied to the data. It is hidden from users who do not have the required permission level or who do not meet labeling requirements, such as U.S. citizen or foreign national restrictions.
In addition, sensitive content associated with an operation can inherit restrictions from its parent project. Access is limited to users explicitly assigned to the Project, project administrators, and the operators associated with that Operation.
You can find more information about permissions and access restrictions on the sensitivity and permission documentation page.
Still need help?
Please contact us using our contact form.