Sourced energy and environment context
Assets, production, and emissions records: Dynamics 365 CRM
The Calgary Plan describes a transition from the city's historic energy base and identifies renewable and net-zero energy as an investment area. Translate the operating setting into accounts, contacts, opportunities, cases, work orders, assets, and activities. Require a reason for each custom table or process variation. Energy work can connect physical assets, production, meters, forecasts, maintenance, contracts, markets, safety, emissions calculations, financial postings, and public reporting.
Evidence to request: Use a process-design case and require table, form, automation, security, reporting, and ownership decisions. Name the assets and energy process, source measurements, calculation method, commercial boundary, maintenance window, reconciliation, reporting rule, and approval evidence.
Sourced health, science, and technology context
Research, digital products, and health systems: Dynamics 365 CRM
The Calgary Plan names health, science, and technology among the sectors used to diversify and modernize the city's economy. Define the Dataverse, Power Platform, ERP, identity, and external-service boundaries. Candidates should cover APIs, events, virtual tables, security, retries, and monitoring. These roles may serve research, clinical operations, regulated products, digital services, data platforms, or enterprise functions with different proof and access requirements.
Evidence to request: Review an ERP or external integration with source-of-truth rules, matching, failure handling, replay, and reconciliation. Set the user and outcome, scientific or product stage, data authority, regulated boundary, validation need, deployment target, access model, and acceptance owner.
Sourced aerospace, agribusiness, and inland-port operations context
Production, supply, and distribution networks: Dynamics 365 CRM
Calgary's municipal plan identifies aerospace and agribusiness as investment sectors and states that industrial land supports the city's inland-port role. Set migration and release ownership. Ask how the consultant profiles source data, controls duplicates, tests roles and automation, sequences cutover, and supports users afterward. These operations can join engineering or product records, crops or materials, equipment, quality, suppliers, plants, warehouses, rail and road movement, inventory, and financial settlement.
Evidence to request: Ask for a migration or release the consultant owned, including data quality, role testing, defects, training handoff, and acceptance. Trace the product or shipment from source through production, quality release, storage, transport, customer handoff, exception, accounting, and support ownership.