Expert CRM Development

We are looking for

• Currently, CMR stores the requested impacts from the applicant in the “Request Impacts” entity.
• CRM uses code to create an initial default permit impact location and permit requirement location. Impact location is needed at 3 levels:
• Request impact.
• Permit impacts, and
• Request requirement.
• The data in CRM currently is not available at the request requirement level.

• CRM currently uses requirement location and service area to define where the requirement needs to be mitigated.
• This needs to be refined and new data and fields added.

• Currently, project assets have locations but do not have service areas.
• CRM only stores the project’s location.
• The Pooled Credits pools use the location of the project to establish the credit pool’s de facto service area.
• These credits may be used incorrectly if service areas are not properly defined.
• Service Area Fee versus Requirement Location

• The refund functionality needs to be streamlined. When a refund is issued, either a negative revenue should be generated or a positive expenditure created.
• Neither occurs currently in CRM and a manual entry is made.

• Currently, the credit release function can only be utilized after a credit release has been authorized.
• The proposed credit release, credit release ledger, and debit forms are all maintained in separate Excel ledgers outside of CRM which need to change.
• Cost Allocations to Service Area and mitigation type.
• DMS assigns all program costs including administrative costs to mitigation types and geographic regions.
• Currently, none of this information is stored in CRM or NCAS.
• CRM assigns costs to projects, contracts, and funds/programs.
• On multi credit projects, CRM doesn’t know how much of the costs are assigned to the different mitigation types.
• These costs need to be assigned to a service area and broken down into mitigation types.

• Currently, the revenue entity captures all revenue for DMS however, it is unconnected and unlinked with customer invoices and vendor refunds.

• Currently, RFP data and RFP results are tracked in an Excel spreadsheet.
• The data is needed to assess the need for RFPs to acquire mitigation credits.
• The data is also needed to describe how prices (both awarded and not awarded) have changed in the marketplace.

• The IMS TIP module and data were not migrated from IMS to CRM. CRM has “Projected Impacts” as part of the Request module but there is no data available as the TIP entity was never created.

• When NCDOT submits mitigation orders to DMS, DMS tracks the mitigation order by TIP and categorizes it across three levels: forecasted projection, acceptance data, and permitted requirements.
• Currently, CRM can only provide permitted requirements or unmet permitted requirements for forecasting.
• Accepted data is not in format where it could be used and projection data is not yet stored.

• Mitigation Target tables are highly desired as these values determine snapshot program needs by service area and time.
• To create these, net assets, unmet requirements, and future requirements need to be known. Future requirements may be projection data, acceptance data, or requirements with a future due date.

• CRM currently doesn’t have many sum fields.
• Most of the data is entered in small pieces called lines.
• The user relies on charts to sum up the data.
• Unfortunately, charts only work when views have been added that allow the user to select the chart.

• Perform Data validation/screening.

• Various reports need to be created to extract data from the system.
• Training and Project Documentation.
• Training and documentation of the system are important as changes to the system have been and are progressing at a rapid pace.
• DMS is requesting some training and documentation on the updates.