Job ID: NC-710444
Remote MS Dynamics 365 Developer with security, and entity experience
Location: Raleigh, NC (NCDEQ-ITS)
Duration: 11 months
Skills
- Create, Deliver and Manage CRM Applications
- Configure Dynamics 365 Setting
- Demonstrated experience configuring (and developing) with the MS Dynamics 365 CRM online platform (2011-current versions preferred)
- Manage Dynamics CRM security
- Manage entity ownership; manage entity properties; understand system and custom entities
Description:
1- Location of Impact (Discussed previously and quoted approximately 2 weeks' worth of design work)
- 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: 1) request impact, 2) permit impacts, 3) request requirement.
- The data in CRM currently is not available at the request requirement level.
2- Requirement Location and Service Area
- 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.
3- Credit Service Area
- Currently, project assets have locations but do not have service areas.
- CRM only stores the project's location.
- The Pooled Credits pools use the projects location to establish the credit pool's de facto service area.
- These credits may be used incorrectly if service areas are not properly defined.
4- Service Area Fee versus Requirement Location
5- Upgrade Refund Functionality
- 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.
6- Credit Releases
- 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.
7- 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.
8- Revenue Upgrade
- Currently the revenue entity captures all revenue for DMS however, it is unconnected and unlinked with customer invoices and vendor refunds.
9- RFP Entity
- 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 market place.
10- Create STIP Entity
- 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.
11- STIP Module Upgrade for Mitigation Targeting
- 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.
12- Mitigation Target Tables
- 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.
13- Sum and Calculated Fields
- 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.
14- Data Validation / Data Cleaning
- Perform Data validation / screening:
15-Reports
- Various reports need to be created to extract data from the system.
16- Training and Project Documentation
- Training and documentation of the system is important as changes to the system have been and are progressing at a rapid pace.
- DMS is requesting some training and documentations on the updates.