samreed-research commited on
Commit
ac24754
·
verified ·
1 Parent(s): 3025a89

Initial release for NeurIPS 2026 E&D submission

Browse files
Files changed (4) hide show
  1. LICENSE +46 -0
  2. README.md +159 -3
  3. billsim_default.pt +3 -0
  4. croissant.json +126 -0
LICENSE ADDED
@@ -0,0 +1,46 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ Creative Commons Attribution 4.0 International (CC BY 4.0)
2
+
3
+ Copyright (c) 2026 Anonymous Authors
4
+
5
+ This dataset and all generated data files in this directory are licensed under
6
+ the Creative Commons Attribution 4.0 International License (CC BY 4.0).
7
+
8
+ You are free to:
9
+
10
+ Share — copy and redistribute the material in any medium or format
11
+ Adapt — remix, transform, and build upon the material for any purpose,
12
+ even commercially.
13
+
14
+ The licensor cannot revoke these freedoms as long as you follow the license
15
+ terms.
16
+
17
+ Under the following terms:
18
+
19
+ Attribution — You must give appropriate credit, provide a link to the
20
+ license, and indicate if changes were made. You may do so in any
21
+ reasonable manner, but not in any way that suggests the licensor
22
+ endorses you or your use.
23
+
24
+ No additional restrictions — You may not apply legal terms or
25
+ technological measures that legally restrict others from doing anything
26
+ the license permits.
27
+
28
+ Notices:
29
+
30
+ You do not have to comply with the license for elements of the material
31
+ in the public domain or where your use is permitted by an applicable
32
+ exception or limitation.
33
+
34
+ No warranties are given. The license may not give you all of the
35
+ permissions necessary for your intended use. For example, other rights
36
+ such as publicity, privacy, or moral rights may limit how you use the
37
+ material.
38
+
39
+ Full license text: https://creativecommons.org/licenses/by/4.0/legalcode
40
+ Human-readable summary: https://creativecommons.org/licenses/by/4.0/
41
+
42
+ To attribute this dataset, please cite:
43
+
44
+ Anonymous Authors. BillSim: A Synthetic Heterogeneous Graph Benchmark
45
+ for Non-Adversarial Anomaly Detection in Usage-Based Billing.
46
+ Submitted to NeurIPS 2026 Evaluations & Datasets Track, 2026.
README.md CHANGED
@@ -1,3 +1,159 @@
1
- ---
2
- license: cc-by-4.0
3
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: cc-by-4.0
3
+ task_categories:
4
+ - graph-ml
5
+ tags:
6
+ - graph-anomaly-detection
7
+ - heterogeneous-graphs
8
+ - non-adversarial-anomalies
9
+ - billing-pipelines
10
+ size_categories:
11
+ - 10K<n<100K
12
+ ---
13
+
14
+ # BillSim — A Synthetic Heterogeneous Graph Benchmark for Non-Adversarial Anomaly Detection in Usage-Based Billing
15
+
16
+ Anonymous Authors
17
+ Submitted to NeurIPS 2026 Evaluations & Datasets Track
18
+ 2026
19
+
20
+ ## Overview
21
+
22
+ BillSim is a fully synthetic heterogeneous graph benchmark for non-adversarial anomaly detection in usage-based billing pipelines. Existing graph anomaly detection benchmarks (Amazon reviews, Bitcoin OTC/Alpha, Yelp, UNSW-NB15, DGraph) model adversarial behaviour: fraud, spam, attacks, intentional concealment. BillSim targets the complementary regime that dominates enterprise systems-of-record: configuration errors, integration drift, and timing mismatches that are economically consequential (revenue leakage, customer overbilling) yet not adversarial.
23
+
24
+ The headline finding the benchmark is built to expose: a 0.374 AUROC gap on peer-comparison anomalies between a hand-coded oracle (0.965) and the best GNN (0.591), localizing the limitation to message-passing aggregation rather than task ill-posedness. In abstract-level shorthand, this is the 0.37 AUROC oracle gap.
25
+
26
+ ## Dataset At A Glance
27
+
28
+ - 63,155 nodes across 11 entity types
29
+ - 108,930 edges across 14 relationship types
30
+ - 6 anomaly types organized by graph reasoning pattern: structural / relational / peer-comparison
31
+ - 5 baselines benchmarked: MLP, GCN, GAT, RGCN, HGT
32
+ - 10 random seeds per configuration
33
+ - 4 anomaly injection rates: 0.01, 0.03, 0.05, 0.10
34
+ - 24 simulated billing months; temporal split for dynamic entities, deterministic 75/25 random split for static entities
35
+
36
+ ## Schema
37
+
38
+ ### Node Types (11)
39
+
40
+ | Type | Count | Features |
41
+ |------|-------|----------|
42
+ | customer | 200 | segment, is_active, num_sub_accounts |
43
+ | contract | 389 | duration_months, payment_terms, status, total_committed_value |
44
+ | sku | 50 | category, base_price, is_active |
45
+ | pricing_rule | 1,111 | rate_type, rate_value, is_current |
46
+ | usage_record | 14,601 | volume, unit_cost |
47
+ | rated_charge | 14,601 | amount |
48
+ | invoice | 3,547 | total_amount, status |
49
+ | line_item | 14,601 | amount |
50
+ | payment | 3,547 | amount, method |
51
+ | ar_record | 3,547 | status, amount |
52
+ | gl_entry | 6,961 | abs_amount |
53
+ | **Total** | **63,155** | |
54
+
55
+ All feature vectors are z-score normalized per node type. Categorical features are integer-encoded. The `gl_entry` feature deliberately omits the sign of the GL amount to prevent revenue/cash leakage into the learning task.
56
+
57
+ ### Edge Types (14)
58
+
59
+ | Edge | Source -> Target | Count |
60
+ |------|------------------|-------|
61
+ | subscribes_to | customer -> contract | 389 |
62
+ | has_sku | contract -> sku | 1,111 |
63
+ | governs | pricing_rule -> sku | 1,111 |
64
+ | applies_to | pricing_rule -> contract | 1,111 |
65
+ | generates_usage | customer -> usage_record | 14,601 |
66
+ | for_sku | usage_record -> sku | 14,601 |
67
+ | rates_to | usage_record -> rated_charge | 14,601 |
68
+ | priced_by | rated_charge -> pricing_rule | 14,601 |
69
+ | billed_on | rated_charge -> line_item | 14,601 |
70
+ | part_of | line_item -> invoice | 14,601 |
71
+ | invoiced_to | invoice -> customer | 3,547 |
72
+ | settles | payment -> invoice | 3,547 |
73
+ | opens_ar | invoice -> ar_record | 3,547 |
74
+ | posts_to | invoice -> gl_entry | 6,961 |
75
+ | **Total** | | **108,930** |
76
+
77
+ The homogeneous view doubles edge count by adding reverse edges.
78
+
79
+ ## Anomaly Taxonomy
80
+
81
+ Six anomaly types are organized into three graph-reasoning categories. The categorization is the analytical contribution of the benchmark: it makes the architectural success and failure modes of GNNs interpretable.
82
+
83
+ | # | Name | Target Node | Category | Mechanism |
84
+ |---|------|-------------|----------|-----------|
85
+ | 1 | Missing Metering | customer | relational | Usage stops while contract remains active |
86
+ | 2 | Orphaned Lines | line_item | relational | Invoice customer differs from charge customer (cross-path violation) |
87
+ | 3 | Pricing Mismatch | rated_charge | structural | Charge amount inconsistent with volume x rate from connected pricing rule |
88
+ | 4 | Stale Discount | pricing_rule | peer-comparison | Rate diverges from peer rules governing the same SKU |
89
+ | 5 | Revenue Recognition | gl_entry | structural | Invoice missing the expected cash GL entry (sibling-count check) |
90
+ | 6 | Premature AR | ar_record | structural | AR record closed despite incomplete payment sum |
91
+
92
+ Labels are provided per node type as a binary `y` (0 = normal, 1 = anomalous) and as `anomaly_type` (0 = normal, 1-6 = the type above). Each node carries at most one anomaly label; no overlap between types.
93
+
94
+ Injection signatures have been audited for feature leakage: per-type Cohen's d remains below 0.2, ensuring detection requires graph structure rather than feature shortcuts.
95
+
96
+ ## Headline Result
97
+
98
+ At injection rate 0.05 across 10 seeds, the V4 result table is:
99
+
100
+ | Type | MLP | GCN | GAT | RGCN | HGT | Oracle | Best GNN | Gap |
101
+ |------|-----|-----|-----|------|-----|--------|----------|-----|
102
+ | Missing Metering | 0.512 | 0.730 | 0.398 | 0.784 | **0.827** | 0.866 | HGT | +0.038 |
103
+ | Pricing Mismatch | 0.684 | 0.571 | 0.867 | **0.980** | 0.979 | 0.881 | RGCN | -0.099 |
104
+ | Orphaned Lines | 0.505 | 0.967 | 0.968 | 0.922 | **0.988** | 1.000 | HGT | +0.012 |
105
+ | **Stale Discount** | 0.560 | 0.571 | 0.476 | **0.591** | 0.540 | **0.965** | RGCN | **+0.374** |
106
+ | Revenue Recognition | 0.509 | 0.965 | 0.928 | 0.497 | **0.987** | 1.000 | HGT | +0.013 |
107
+ | Premature AR | 0.509 | 0.519 | 0.533 | **0.996** | 0.991 | 1.000 | RGCN | +0.004 |
108
+
109
+ The 0.374 oracle-GNN gap on Stale Discount is an order of magnitude larger than any other gap. Because the gap is exposed by a hand-coded peer-comparison oracle that achieves 0.965 AUROC, the limitation is established as architectural — message-passing aggregation cannot represent peer-distribution comparison — rather than the task being ill-posed.
110
+
111
+ ## Data Generation
112
+
113
+ The dataset is fully synthetic. No real billing data was used at any stage. The generation pipeline is a configurable Python module with deterministic NumPy seeding. Default parameters:
114
+
115
+ - Revenue distribution: lognormal contract sizes producing a Pareto-like tail
116
+ - Usage volumes: log-normal (mu = 6.0, sigma = 1.2)
117
+ - Customer arrivals: front-loaded declining Poisson
118
+ - Contract durations: uniform 6-36 months
119
+ - Pricing: uniform 0.01-10.0 base rate with +/-20% per-contract variation
120
+
121
+ All parameters are documented in the configuration module of the released code.
122
+
123
+ ## Train / Test Split
124
+
125
+ - Dynamic entities (usage_record, rated_charge, invoice, line_item, payment, ar_record, gl_entry): temporal split. Months 1-18 -> train, months 19-24 -> test.
126
+ - Static entities (customer, contract, sku, pricing_rule): deterministic 75/25 random split keyed off `(seed + stable_offset(node_type))`. The stable offset is an MD5-derived integer per node type name, ensuring split reproducibility across seeds and node types.
127
+
128
+ ## Preprocessing
129
+
130
+ - All features z-score normalized per column (mean 0, std 1)
131
+ - Categorical features integer-encoded
132
+ - No missing values; no NaN or Inf values (verified by automated integrity check)
133
+ - No out-of-bounds edge indices (verified)
134
+
135
+ ## Intended Uses
136
+
137
+ - Benchmarking GNN methods for non-adversarial anomaly detection on heterogeneous temporal graphs
138
+ - Evaluating which graph reasoning patterns (structural sibling counting, multi-hop relational path matching, relation-specific traversal, peer-distribution comparison) different architectures can or cannot represent
139
+ - Diagnostic studies of message-passing limitations, including ablations against hand-coded oracle ceilings
140
+ - Research on architectural extensions that close the peer-comparison gap
141
+
142
+ ## Not-Intended Uses
143
+
144
+ - Production billing system deployment. The synthetic distributions do not replicate the complexity of real billing data.
145
+ - Training fraud detection models. The anomalies in BillSim are non-adversarial system errors, not adversarial attack patterns. Fraud involves intentional concealment and shifting tactics; billing errors do not.
146
+ - Drawing conclusions about real-customer billing accuracy. The benchmark exists to evaluate model architectures, not to model any specific operator's billing platform.
147
+
148
+ ## Format
149
+
150
+ PyTorch Geometric `HeteroData` objects serialized as `.pt` files, accompanied by Python generation scripts that reproduce the dataset deterministically from any seed and injection rate.
151
+
152
+ ## Licenses
153
+
154
+ - Data: CC-BY-4.0
155
+ - Code: Apache-2.0
156
+
157
+ ## Citation
158
+
159
+ Anonymous Authors. BillSim: A Synthetic Heterogeneous Graph Benchmark for Non-Adversarial Anomaly Detection in Usage-Based Billing. Submitted to NeurIPS 2026 Evaluations & Datasets Track, 2026.
billsim_default.pt ADDED
@@ -0,0 +1,3 @@
 
 
 
 
1
+ version https://git-lfs.github.com/spec/v1
2
+ oid sha256:a1b956386dbf7a73177e768657ae329e2e96496790a9c8ebe0421c5b5cbeb5a6
3
+ size 4285402
croissant.json ADDED
@@ -0,0 +1,126 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "@context": {
3
+ "@language": "en",
4
+ "@vocab": "https://schema.org/",
5
+ "citeAs": "cr:citeAs",
6
+ "column": "cr:column",
7
+ "conformsTo": "dct:conformsTo",
8
+ "cr": "http://mlcommons.org/croissant/",
9
+ "rai": "http://mlcommons.org/croissant/RAI/",
10
+ "data": {"@id": "cr:data", "@type": "@json"},
11
+ "dataType": {"@id": "cr:dataType", "@type": "@vocab"},
12
+ "dct": "http://purl.org/dc/terms/",
13
+ "equivalentProperty": "cr:equivalentProperty",
14
+ "examples": {"@id": "cr:examples", "@type": "@json"},
15
+ "extract": "cr:extract",
16
+ "field": "cr:field",
17
+ "fileProperty": "cr:fileProperty",
18
+ "fileObject": "cr:fileObject",
19
+ "fileSet": "cr:fileSet",
20
+ "format": "cr:format",
21
+ "includes": "cr:includes",
22
+ "isLiveDataset": "cr:isLiveDataset",
23
+ "jsonPath": "cr:jsonPath",
24
+ "key": "cr:key",
25
+ "md5": "cr:md5",
26
+ "parentField": "cr:parentField",
27
+ "path": "cr:path",
28
+ "recordSet": "cr:recordSet",
29
+ "references": "cr:references",
30
+ "regex": "cr:regex",
31
+ "repeated": "cr:repeated",
32
+ "replace": "cr:replace",
33
+ "samplingRate": "cr:samplingRate",
34
+ "sc": "https://schema.org/",
35
+ "separator": "cr:separator",
36
+ "source": "cr:source",
37
+ "subField": "cr:subField",
38
+ "transform": "cr:transform"
39
+ },
40
+ "@type": "sc:Dataset",
41
+ "name": "BillSim",
42
+ "conformsTo": "http://mlcommons.org/croissant/1.0",
43
+ "description": "BillSim is a synthetic heterogeneous graph benchmark for non-adversarial anomaly detection in usage-based billing pipelines. The default dataset contains 63,155 nodes across 11 entity types (customer, contract, sku, pricing_rule, usage_record, rated_charge, invoice, line_item, payment, ar_record, gl_entry) and 108,930 edges across 14 relationship types (subscribes_to, has_sku, governs, applies_to, generates_usage, for_sku, rates_to, priced_by, billed_on, part_of, invoiced_to, settles, opens_ar, posts_to). Six anomaly types are organized into three categories: structural (Pricing Mismatch, Revenue Recognition, Premature AR Closure), relational (Missing Metering, Orphaned Invoice Lines), and peer-comparison (Stale Discount). Five baselines are evaluated (MLP, GCN, GAT, RGCN, HGT) across 10 random seeds and 4 injection rates (0.01, 0.03, 0.05, 0.10). Headline finding: a 0.374 AUROC oracle gap on peer-comparison anomalies between a hand-coded oracle (0.965 AUROC on Stale Discount) and the best message-passing baseline (RGCN at 0.591; HGT at 0.540 is statistically indistinguishable), localizing the limitation to message-passing aggregation rather than task ill-posedness. Distributed as a PyTorch Geometric HeteroData (.pt) tensor plus deterministic Python generation scripts.",
44
+ "citeAs": "Anonymous Authors. BillSim: A Synthetic Heterogeneous Graph Benchmark for Non-Adversarial Anomaly Detection in Usage-Based Billing. Submitted to NeurIPS 2026 Evaluations & Datasets Track, 2026.",
45
+ "license": "https://creativecommons.org/licenses/by/4.0/",
46
+ "url": "[anonymized for double-blind review]",
47
+ "version": "4.0.0",
48
+ "datePublished": "2026-05-06",
49
+ "keywords": [
50
+ "graph anomaly detection",
51
+ "heterogeneous graphs",
52
+ "non-adversarial anomalies",
53
+ "billing pipelines",
54
+ "GNN benchmarks"
55
+ ],
56
+ "creator": {
57
+ "@type": "sc:Person",
58
+ "name": "Anonymous Authors",
59
+ "email": "anon@example.com"
60
+ },
61
+ "rai:dataCollection": "Fully synthetic dataset generated by a deterministic Python pipeline. No real customer, account, transaction, or other financial data was collected, sampled, scraped, or otherwise sourced from any real-world subject or system. Every node, edge, feature, and label is produced by parameterized statistical distributions (Pareto for revenue, log-normal for usage volumes, Poisson for arrivals, uniform for pricing) seeded with a NumPy random state for bit-level reproducibility.",
62
+ "rai:dataCollectionType": "Synthetic data generation",
63
+ "rai:dataPreprocessingProtocol": "Per-node-type z-score normalization (mean 0, std 1) on each numeric feature column. Categorical features (e.g., customer segment, payment terms, SKU category, payment method) are integer-encoded with stable per-process hashing. Train/test split is deterministic per seed: static entity types (customer, contract, pricing_rule, sku) use a 75/25 random split; dynamic entity types (usage_record, rated_charge, invoice, line_item, payment, ar_record, gl_entry) use a temporal split of months 1-18 (train) versus 19-24 (test) over a 24-month simulated horizon. No missing values, no NaN, no Inf, and no out-of-bounds edge indices are present; integrity is verified by an automated check on every regeneration.",
64
+ "rai:dataAnnotationProtocol": "Anomaly labels are generated programmatically at injection time, not annotated by humans. The injector marks each affected node with a binary anomaly indicator (y in {0, 1}) and an integer anomaly type (anomaly_type in {0, 1, 2, 3, 4, 5, 6}). Every node has at most one anomaly type assigned, so the multi-class label set is mutually exclusive across the six anomaly categories.",
65
+ "rai:dataUseCases": "Intended use: benchmarking graph neural network architectures on non-adversarial anomaly detection in heterogeneous temporal graphs, and evaluating which graph-reasoning patterns (structural degree counting, multi-hop path matching, relation-specific traversal, peer comparison) different architectures excel at. Not intended for fraud detection: anomalies in BillSim are operational and configuration errors, not adversarial attack patterns; fraud involves intentional concealment, billing errors do not. Not intended for production billing system deployment: the synthetic distributions deliberately do not replicate real billing data complexity.",
66
+ "rai:dataBiases": "BillSim is fully synthetic and contains no demographic, geographic, or otherwise protected-class attributes. The data generator does not encode race, gender, age, ethnicity, nationality, sexual orientation, religion, disability, or any proxy thereof. Customer entities have only segment (a non-demographic business tier index 0-3) and account-activity attributes. Statistical distributions used to sample synthetic feature values (Pareto revenue, log-normal usage, Poisson arrivals) are documented in billsim/config.py and are intended to reproduce the long-tailed shapes typical of usage-based-billing systems while introducing no demographic bias.",
67
+ "rai:personalSensitiveInformation": "None. All entity identifiers are sequential integers, all features are synthetic numeric or categorical encodings, and no field carries personal, financial, biometric, geolocation, or otherwise sensitive information about any real person or organization.",
68
+ "rai:dataSocialImpact": "Low. The dataset contains no real-world subjects and cannot be used to identify, target, or impact any individual or group. The primary intended impact is methodological: it provides a reproducible benchmark for studying when and why message-passing graph neural networks fail on operational anomaly-detection tasks that require peer-distribution comparison.",
69
+ "rai:dataLimitations": "BillSim covers six anomaly types representative of common operational failure modes in usage-based billing (missed metering, pricing mismatches, orphaned invoice lines, stale discounts, revenue recognition errors, premature AR closure) but is not exhaustive of real-world billing system failure modes. Synthetic distributions approximate but do not replicate the full complexity of production billing data (no tax tiers, no currency mismatches, no retroactive adjustments, no off-cycle events).",
70
+ "rai:dataReleaseMaintenancePlan": "The dataset is released as a single default PyTorch Geometric HeteroData artifact plus the deterministic generation pipeline. Because the generator is deterministic given (seed, injection_rate), the dataset can be regenerated indefinitely without depending on continued hosting of the binary artifact. Issues and contributions are accepted via the anonymous code mirror referenced in the paper.",
71
+ "cr:syntheticData": true,
72
+ "distribution": [
73
+ {
74
+ "@type": "cr:FileObject",
75
+ "@id": "billsim-default-pt",
76
+ "name": "billsim_default.pt",
77
+ "description": "Default pre-generated dataset (seed=42, injection_rate=0.05). PyTorch Geometric HeteroData object with 11 node types, 14 edge types, z-score-normalized features, binary anomaly labels (y), integer anomaly type labels (anomaly_type in 0-6), and temporal train/test masks.",
78
+ "contentUrl": "data/billsim_default.pt",
79
+ "encodingFormat": "application/x-pytorch",
80
+ "md5": "00000000000000000000000000000000"
81
+ }
82
+ ],
83
+ "recordSet": [
84
+ {
85
+ "@type": "cr:RecordSet",
86
+ "@id": "customer",
87
+ "name": "customer",
88
+ "description": "Customer entity records. 200 nodes. The full 11-node-type record set (customer, contract, sku, pricing_rule, usage_record, rated_charge, invoice, line_item, payment, ar_record, gl_entry) is enumerated in docs/datasheet.md and docs/croissant.json in the anonymous code mirror; this RecordSet is included as a representative example of the schema typing.",
89
+ "field": [
90
+ {
91
+ "@type": "cr:Field",
92
+ "@id": "customer/segment",
93
+ "name": "segment",
94
+ "description": "Integer-encoded customer segment (business tier 0-3). Non-demographic.",
95
+ "dataType": "sc:Integer",
96
+ "source": {
97
+ "fileObject": {"@id": "billsim-default-pt"},
98
+ "extract": {"column": "customer.x[:, 0]"}
99
+ }
100
+ },
101
+ {
102
+ "@type": "cr:Field",
103
+ "@id": "customer/is_active",
104
+ "name": "is_active",
105
+ "description": "Boolean indicating whether the customer is currently active (1) or churned (0).",
106
+ "dataType": "sc:Boolean",
107
+ "source": {
108
+ "fileObject": {"@id": "billsim-default-pt"},
109
+ "extract": {"column": "customer.x[:, 1]"}
110
+ }
111
+ },
112
+ {
113
+ "@type": "cr:Field",
114
+ "@id": "customer/num_sub_accounts",
115
+ "name": "num_sub_accounts",
116
+ "description": "Count of sub-accounts associated with this customer.",
117
+ "dataType": "sc:Integer",
118
+ "source": {
119
+ "fileObject": {"@id": "billsim-default-pt"},
120
+ "extract": {"column": "customer.x[:, 2]"}
121
+ }
122
+ }
123
+ ]
124
+ }
125
+ ]
126
+ }