# About the Model & Artifact Objects (eTMF & CTMS)

_Model_ and _Artifact_ are standard objects that Vault uses to model the <a class="external-link " href="http://www.tmfrefmodel.com" target="_blank" rel="noopener">TMF Reference Model<i class="fa fa-external-link" aria-hidden="true"></i></a> (TMF RM), a commonly used standard taxonomy for Trial Master File content. The _Model_ object (`model__v`) contains a record for each version of the TMF Reference Model that has been published since 2012. The _Artifact_ object (`hierarchy__v`) contains a record for each zone, section, and artifact in each version of the TMF RM.

Unlike other objects, the object data records for _Model_ and _Artifact_ are non-editable and completely maintained by Veeva. As new versions of the TMF RM become available, Veeva will add new _Model_ and _Artifact_ records to all eTMF Vaults.

You can use these object data records in your Vault's document type configuration to <a href="/en/gr/30260/">map document classifications to individual artifacts</a> in each version of the reference model. An Admin will perform this analysis and mapping exercise during the initial implementation of your eTMF Vault. Over time, you can revisit these mappings when adding new document types or when a new version of the TMF RM is published.

Vault can use these mappings to <a href="/en/gr/4502/">drive auto-filing of documents into binders</a>. Each binder template and each binder is associated with a specific _Model_ record using the binder's _Filing Model_ field. When associated with TMF RM 2.0 or TMF RM 3.0, you can map one _Artifact_ from that version to each section of the binder. Vault uses the combination of _Artifact_ mapping and study fields to auto-file documents into binders.