Skip to main content

Asset Valuer Pro - Information Gaps Summary

Overview

This document consolidates all identified information gaps in our business process documentation that require input from the business unit. Addressing these gaps will increase confidence in our documentation and ensure it accurately reflects current business processes.

Priority Information Gaps

High Priority Gaps (Critical for Accurate Documentation)

  1. Process Ownership

    • Which specific departments/roles own each business process?
    • What are the handoff points between different teams?
  2. Decision Criteria

    • What specific criteria are used at key decision points?
    • What thresholds or guidelines inform these decisions?
  3. Approval Workflows

    • What formal approval processes exist for each key process?
    • Who has authorization at each approval stage?
  4. Integration Details

    • How do client systems integrate with AVP exports?
    • What specific formats are required for different client systems?
  5. Performance Metrics

    • How is success measured for each process?
    • What KPIs are tracked to evaluate process performance?

Process-Specific Information Gaps

File Setup and Configuration Process

  1. User Roles and Permissions

    • What specific roles exist in the system?
    • What permissions does each role have?
    • How are roles assigned and managed?
  2. Asset Hierarchy Decisions

    • What business rules govern the asset hierarchy structure?
    • How are decisions made about asset classification?
    • Are there industry or regulatory standards that inform these decisions?
  3. Assumption Management

    • What is the process for developing and validating assumptions?
    • How frequently are assumptions reviewed and updated?
    • How are assumption changes documented and tracked?

Data Collection Process

  1. Field Inspection Protocols

    • What protocols govern field inspections?
    • What training do field inspectors receive?
    • How are special cases or unusual assets handled?
  2. Sampling Methodology

    • What sampling methodology is used for infrastructure validation?
    • How is sample size determined?
    • What process ensures sample representativeness?
  3. Data Validation Rules

    • What specific validation rules are applied to collected data?
    • How are validation failures handled?
    • What remediation processes exist for data quality issues?

Calculation and Reporting Process

  1. Calculation Rules and Algorithms

    • What specific algorithms are used for different valuation types?
    • How are calculations validated for accuracy?
    • How are exceptions or outliers handled?
  2. Report Customization

    • What report customization options are available?
    • How are client-specific reporting requirements incorporated?
    • What are the standard report formats and contents?
  3. Client Review Process

    • What is the formal process for client review of results?
    • How are client feedback and change requests managed?
    • What constitutes final client acceptance?

Post-Valuation Process

  1. Audit Support Procedures

    • What specific procedures support the audit process?
    • What documentation must be maintained for audit purposes?
    • How are audit questions and concerns addressed?
  2. Archiving Policies

    • What are the detailed archiving policies and procedures?
    • How long are different types of data retained?
    • What access controls exist for archived data?
  3. Client System Integration

    • What are the specific formats and procedures for client system integration?
    • How are data mapping issues resolved?
    • Who is responsible for ensuring successful integration?

Cross-Cutting Information Gaps

  1. Exception Handling

    • How are exceptions handled in each process?
    • What escalation procedures exist?
    • How are recurring issues addressed?
  2. Manual Workarounds

    • What manual workarounds exist for system limitations?
    • How are these workarounds documented and communicated?
    • Are there plans to address these with system enhancements?
  3. Training and Knowledge Transfer

    • How are users trained on each process?
    • What documentation exists for training purposes?
    • How is knowledge transferred to new team members?
  4. Process Improvement

    • What process exists for continuous improvement?
    • How are improvement suggestions collected and evaluated?
    • How are process changes communicated and implemented?

Technical-Business Gap Areas

  1. Technical Implementation of Business Rules

    • How are business rules implemented in the codebase?
    • Where are calculation formulas documented?
    • How are changes to business rules reflected in the code?
  2. Data Model Alignment

    • How do database entities align with business concepts?
    • What business meaning is attached to technical fields?
    • How are relationships between business entities represented?
  3. Integration Architecture

    • How does the mobile app integrate with the main system?
    • What API endpoints support business processes?
    • How are data synchronization conflicts resolved?

Next Steps for Gap Resolution

  1. Schedule focused review sessions with the business unit to address:

    • Process ownership and responsibilities
    • Decision criteria and approval workflows
    • Performance metrics and success criteria
  2. Arrange technical workshops to clarify:

    • Technical implementation of business rules
    • Integration architecture
    • Data model alignment with business concepts
  3. Document responses and update process documentation accordingly

  4. Create a feedback loop for ongoing refinement of process documentation