Skip to main content
Cartegraph Campus

Build an Asset

You must have a Cartegraph OMS advanced feature extension to access this feature.

When your organization wants to build an asset that is not provided as a standard asset in Cartegraph this is the process you need to follow. Throughout this document, Courts, like tennis and basketball is used as an example, and the guidelines and instructions are true for any asset.

Cartegraph recommends completing each step of the process for maximum gain from. If all the steps are completed, inefficiencies and costly system adjustments are avoided. Also you can get an idea of how long it will take to go through this process.

NOTE: If your organization is on the Standard edition this option is not available to you.

Process Requirements:

  • Knowledge of how the asset is used in your organization
  • Who in your organization works with the asset
  • Cartegraph Administration rights
  • Access to your organization's GIS system (if applicable)
  • Familiarity with the CartegraphAsset Administration
  • Familiarity with the Cartegraph Library Manager
  • Familiarity with the Cartegraph Layout Manager
  • Familiarity with Cartegraph Role Administration

Areas of Consideration:

Development of Process and Procedures related to:

  • Overall Operations and Standard Operating Process & Procedures
  • Data capture
  • Data entry
  • Data retrieval
  • Unique work flow scenarios

Configuration Phases:

  • Needs assessment
  • Gather asset information
  • Generate asset
  • Configuration asset

Needs Assessment

This research and analysis reveals how the asset is used by your organization and what data needs to be managed in Cartegraph.

This assessment needs to cover

  • What to track
  • Why your organization needs this data
  • Reporting needs

This gives you an understanding of your needs and whether creating an asset is the best approach.

Where to Begin

Review and document what you know about this asset's role in your organization.

  • How does your organization currently work with this asset?
  • Why do you want to track this asset?
  • When will you use this information?
  • How will you use this information?
  • Is there an existing data source to create start up data, like Activities, Issues, Departments, Condition Categories, etc.?

If your analysis reveals this asset is a good fit for Cartegraph, continue with more research and documentation.

What's Next

Research and document the following as appropriate for the asset:

  • What are the inventory requirements?
  • What are the maintenance requirements?
  • Define GIS needs
  • Is the asset already in your GIS system?
  • Will the GIS data need to be normalized before integration into Cartegraph.
  • What are the required fields for data input process and requirements?
  • What are the Required data field to be captured and tracked in the database?
  • Who collects the information?
  • How is the information collected?
  • How does this information work with the following types of management:
    • Requests
    • Work
    • Asset
    • Maintenance
    • GIS
  • Are there Report needs beyond summary and detail?

Gather Asset Information

There are several areas where you need to collect information to add fields, libraries, create relationships, screen layout, and security. Refer to the information you gathered in the Needs Assessment phase.

  • Determine who will use it and define Role security.
  • List the departments that will work with this asset.
  • List the Container/Component and/or Linked Asset relationships needed.
  • List the Activities apply to this asset.
  • List relevant Request Issues
  • List of additional Condition Categories and associated curves.
  • Does the data stored in ArcGIS need to be normalized?

Build Asset

You must have administrator rights to access this feature.

For instruction see Install a Custom Asset.

Configure Asset

  1. Add libraries and fields to an asset.
  2. Configure library and field settings.
  3. Create Container/Component and/or Linked Asset relationships.
  4. Publish.
  5. Build layouts.
  6. Setup security. Do this last so that no one has access to the asset until you are ready to release to the entire organization.

 

  • Was this article helpful?