# Project and Project Management Design

**URL:** https://discourse.kitware.com/t/project-and-project-management-design/333
**Category:** Design
**Created:** [November 1, 2019, 4:55pm UTC](https://discourse.kitware.com/t/project-and-project-management-design/333 "2019-11-01T16:55:22Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![johnt](https://discourse.kitware.com/user_avatar/discourse.kitware.com/johnt/32/147_2.png) [@johnt](https://discourse.kitware.com/u/johnt)
#### Post date: [November 1, 2019, 7:29pm UTC](https://discourse.kitware.com/t/project-and-project-management-design/333/2 "2019-11-01T19:29:30Z")

</div>

I think there is an additional project requirement for tracking simulation data that are not smtk resources, the most obvious being simulation input decks and output datasets. This has been suggested as a “simulation asset” class that is somewhere in the PersistentObject class hierarchy. This was previously discussed in the spring ([Proposed Change To PersistentObject](https://discourse.kitware.com/t/proposed-change-to-persistentobject/245)), but I dropped that ball.

A simulation asset class would share at least some of the behaviors of persistent objects, in particular (i) ability for projects to use links to assets, and (ii) the ability to use assets in operations, presumably by assigning them to ReferenceItem instances.

---

_[View the full topic](https://discourse.kitware.com/t/project-and-project-management-design/333)._