Data
      Back to home
      1. Knowledge Base
      2. Amperecloud Platform
      3. Data

      Data Studio Mapping Rule Standards

      Content

      Typical Device Types & Hierarchical Structureopen_in_new_24dp_FILL0_wght400_GRAD0_opsz24

      Internal Identifier Naming Standardsopen_in_new_24dp_FILL0_wght400_GRAD0_opsz24

      Device Name Standardizationopen_in_new_24dp_FILL0_wght400_GRAD0_opsz24

      Status Codesopen_in_new_24dp_FILL0_wght400_GRAD0_opsz24

      Mapping Rule-Setsopen_in_new_24dp_FILL0_wght400_GRAD0_opsz24

      Welcome to the central reference for mapping rule standards in our PV monitoring platform.

      As our system scales across many projects and hardware types, it's critical to define and follow consistent standards — for internal identifiers, device hierarchies, naming conventions, and rule reuse.

      Following these standards ensures:

      • Clean and predictable rule behavior
      • Easier reuse across projects
      • Faster debugging and troubleshooting
      • Accurate simulation and hierarchy visualization
      • Scalable onboarding and maintenance

      Typical Device Types & Hierarchical Structure

      Defines the physical top-down structure for device relationships.

      • Transformer → Inverter → MPP/Combiner → String → Sensor/Input
      • Never place higher-level devices under lower-level ones
      • Skipping levels is allowed
      • Devices are created under the data logger that reads them
      • In 99% of cases: one logger = one transformer (or multiple)

      Internal Identifier Naming Standards

      Internal identifiers define hierarchy and uniqueness.

      • Follow structured formats: TR$1_INV$2_SC$3_STR$4
      • Use numeric suffixes ($1, $2, ...)
      • Case-sensitive and persistent
      • Essential for simulation and reusability

      Device Name Standardization

      Consistent naming in German and English.

      • WR$ = German inverter label, INV$ = English equivalent
      • Names follow the hierarchy format
      • Improves readability without affecting system identifiers

      Status Codes

      Defines how to structure and interpret alarms/faults.

      • Match substrings like STATE, ERROR
      • Define prefix: E1, S1, etc.
      • Source: name or value
      • Type: number or bitmask

      Mapping Rule-Sets

      Collection of reusable, prebuilt rules for common devices.

      • Based on specific logger + device model combos
      • Marked as:
        • ✅ Matching Standard – conforms to all structure rules
        • ✅ Consistent – device streams are reliably structured
      • Use copyRawReadingMappingRule endpoint for setup

      Need More Help?

      If you encountered any difficulties or need further assistance, here are some steps you can take:

      Contact Support:

      • Email: Reach out to our support team by emailing us at support@amperecloud.com. Provide as much detail as possible about the issue you're facing.
      • Fill out a form: Complete our online support form. Please include all relevant information about your request, and our team will get back to you as soon as possible.

      Share Your Feedback

      If this article didn’t meet your needs or if you have suggestions on how we can improve, please let us know by submitting feedback. Your input helps us enhance our resources and support.