Information regarding Solocast Methodology
Three files need to be in place for Solocast to function:
1) A "Clusters" file that describes the cluster mapping.
2) A demo file with specific variables as needed for Solocast
3) A BlockCentroids file that relates to the level to which clusters are coded. Note that this may be the same BC file as that used by Allocate, or it may not. This is typically built by SRC as one of the "base" files used by Allocate and Solocast.
To build the clusters file for Solocast. It requires 4 Tables, typically built in Microsoft Access.
Cluster: A simple mapping between cluster (segment) and the geography key to which it's assigned. This should be sorted on the Geography Key (e.g. BG). The sort should be "forced" by building a query with a sort column specified, or specifying the Geography Key as a primary key field (this latter approach doesn't always work).
ClusterDesc: Metadata describing the cluster. Sort should also be "forced" via query or primary key on the ClusterNum field.
UGCodes: Description of the first higher-level grouping of clusters. Sort should be forced via query or primary key on the UG_Code field.
MFCodes: Description of another grouping of clusters. Sort should be forced via query or primary key on the MG_Code field.
Cluster table:
The main BG or other base Key to cluster table. Use the ini file setting: DemoKeysLevel to specify which level in the demokeys this is pointing to. ClusterNum values must contain Clusters in sequential order. If there is an "Unknown" cluster, and it doesn't follow in sequence (e.g. if you have 60 clusters, 1 thru 60, and the unknown cluster is 99 instead of 61), use the UncodedClusterAlias=N parameter (where N would = 99).
Format:
Fieldnames specified via the ini file settings:
ClusterSourceFile_Key_Field=BG
ClusterSourceFile_Cluster_Field=Cluster
ClusterDesc table:
The cluster Description file. The copyright string should be in the description for cluster # 0.
| ClusterNum |
ClusterDesc |
MF_Code |
UG_Code |
|
This must be a # starting with 0 and incrementing sequentially after that. Cluster # 0 is fictional and should have the copyright in the cluster Desc field |
The description of the cluster. |
The 0 based # of the MF_Code associated with this. All clusters require this. If not used put in a 0 and make sure the MF table has a record 0 with a desc of Not Used or something. |
Same as MF |
Fieldnames specified via the ini file settings:
ClusterDescFile_ClusterNum_Field=ClusterNum
ClusterDescFile_ClusterDesc_Field=ClusterDesc
ClusterDescFile_Group1_Code_Field=UG_Code
ClusterDescFile_Group2_Code_Field=MF_Code
UGCodes table: This name of this table is historical (UGCodes) and doesn't have much relevance.
A description for the first level grouping of clusters. This is required, even if there is no higher level (see discussion under the MF_Code column above)
Fieldnames specified via the ini file settings:
Group1File_Code_Field=UG_Code
Group1File_Desc_Field=UG_Desc
There is also an ini file setting to describe this group (this appears in the Solocast interface):
MF_Codes_Name=Income Stage
MFCodes table: The name of this table is historical (MFCodes) and doesn't have much relevance.
A description for another grouping of the clusters. This is required, even if there is no higher level (see discussion under the MF_Code column above)
Fieldnames specified via the ini file settings:
Group2File_Code_Field=MF_Code
Group2File_Desc_Field=MF_Desc
Theres is also an ini file setting to describe this group (this appears in the Solocast interface):
UG_Codes_Name=Lifestages
Example ClusterBuilderCmd.ini
Cluster_DescSource=C:\CLUSTER_INFO.mdb,SEGMENT_GET
ClusterSource=C:\CLUSTER_INFO.mdb,BG_CLUSTER
MF_CodesSource=C:\CLUSTER_INFO.mdb,UG_CODES
UG_CodesSource=C:\CLUSTER_INFO.mdb,MF_CODES
MF_Codes_Name=Income Stage
UG_Codes_Name=Lifestages
ClusterDescFile_ClusterNum_Field=ClusterNum
ClusterDescFile_ClusterDesc_Field=ClusterDesc
ClusterDescFile_Group1_Code_Field=UG_Code
ClusterDescFile_Group2_Code_Field=MF_Code
Group1File_Code_Field=UG_Code
Group1File_Desc_Field=UG_Desc
Group2File_Code_Field=MF_Code
Group2File_Desc_Field=MF_Desc
ClusterSourceFile_Key_Field=BG
ClusterSourceFile_Cluster_Field=Cluster
demoKeysFileName=c:\SRC_US_04A_DEMOKEYS_A.src
OutputFile=c:\SRC_US_04A_CLUSTERS.src
DemoKeysLevel=0
ClusterSystem=SRC_CLUSTER
UncodedClusterAlias=N
Username=
password=
;End of ClusterBuilderCmd.ini file
How to Build the Cluster.src file
1) Prepare your 4 tables in a Microsoft Access database with queries or primary keys to force the sort order. A sample of the Access database can be found HERE.
2) Prepare your ClusterBuilderCmd.ini file (you can paste the sample above into a text file, and do a save as.
3) Obtain the lastest ClusterBuilderCmd.exe from your SRC representative.
4) From a command line window, navigate to the folder containing the ClusterBuilderCmd.ini file, and run the ClusterBuilderCmd.exe
5) Check the resulting log file in the same location as the ini file for any errors.
Demo file for Solocast:
A demo file needs to be built in conjunction with the .src file for Solocast to function correctly. This demo file must contain up to 5 key variables (it can have fewer, but at minimum must have the Household and Population variables), and the fieldnames MUST be hardcoded as follows :
Households:HH
Population:POP
Adult Population:POP18P
Adult Females:FPOP18P
Adult Males:MPOP18P
The demo file needs to be built for ONLY 2 LEVELS of geography:
1) The base level to which the clusters are defined. For example, in the US, clusters are mapped to Block Groups, so this would be the BG level. In the UK, it might be Postcodes, since segments are mapped to the PostCode level.
Note that this is also the level to which the Solocast BlockCentroids file must be built, as BC Retrieval is used to build most geographic profiles.
2) The license level of geography. This is used for specific functionality within Solocast. Specifically when running a Detail report, and choosing Scaled to Country variables from the Output fields window.
Other than the information above, this is a standard .demo build. Refer to the documentation on building demo files for more information.