<?xml version="1.0" encoding="UTF-8"?>
<codeBook version="1.2.2" ID="TZA_2013_MCC-KSP_v01_M" xml-lang="en" xmlns="http://www.icpsr.umich.edu/DDI" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.icpsr.umich.edu/DDI http://www.icpsr.umich.edu/DDI/Version1-2-2.xsd">
<docDscr>
  <citation>
    <titlStmt>
      <IDNo>DDI_TZA_2013_MCC-KSP_v01_M</IDNo>
    </titlStmt>
    <prodStmt>
      <producer abbr="MCC" affiliation="" role="Review of Metadata">Millennium Challenge Corporation</producer>
      <prodDate date="2014-04">2014-04</prodDate>
      <software version="v5">NADA</software>
    </prodStmt>
    <verStmt>
      <version>Version 1.0 (April 2014)
Version 2.0 (June 2015). Edited version based on Version 01 (DDI-MCC-TZA-IE-ENERGY-2014-v01) that was done by Millennium Challenge Corporation.</version>
    </verStmt>
  </citation>
</docDscr>
<stdyDscr>
  <citation>
    <titlStmt>
      <titl>Kigoma Solar Power 2013</titl>
      <subTitl/>
      <altTitl>MCC-KSP 2013</altTitl>
      <parTitl/>
      <IDNo>TZA_2013_MCC-KSP_v01_M</IDNo>
    </titlStmt>
    <rspStmt>
      <AuthEnty affiliation="Independent Evaluator">Abel Busalama</AuthEnty>
    </rspStmt>
    <prodStmt>
      <copyright/>
      <software version="5.0" date="2021-04-12">NADA</software>
      <fundAg abbr="MCC" role="">Millennium Challenge Corporation</fundAg>
      <grantNo/>
    </prodStmt>
    <distStmt>
      <contact affiliation="Millennium Challenge Corporation" URI="" email="impact-eval@mcc.gov">Monitoring &amp; Evaluation Division</contact>
      <depDate date=""/>
      <distDate date=""/>
    </distStmt>
    <serStmt>
      <serName>Independent Performance Evaluation</serName>
      <serInfo/>
    </serStmt>
    <verStmt>
      <version date="">Anonymized dataset for public distribution</version>
      <verResp/>
      <notes/>
    </verStmt>
    <biblCit format=""/>
    <notes/>
  </citation>
  <stdyInfo>
    <studyBudget/>
    <subject>
      <keyword vocab="" vocabURI="">Performance Evaluation</keyword>
      <keyword vocab="" vocabURI="">Energy</keyword>
      <keyword vocab="" vocabURI="">Solar Energy</keyword>
    </subject>
    <abstract>The performance evaluation design and implementation will address the following overarching questions across the geography, activity scope and the Project Logic of the Kigoma Solar PV program: 
i. How well was the program implemented? (Including analysis of Project scope, timing, costs, and public perceptions); were the output targets achieved? If not, why? 
ii. What type of challenges were encountered during implementations? 
iii. How well has the solar energy approach addressed the energy needs of the beneficiary population? 
iv. What are the outcomes of the program on solar energy access, use and costs as well as productivity income etc.? 
v. How sustainable are the outcomes? 
vi. What lessons can be learned from the experience of the program? 
vii. Was the project successful in catalyzing investments in the energy sector in Kigoma? If not what conditions will needs to be in place for the pilot to encourage additional investments? 
viii. Are there any unplanned results due to the implementation of the Kigoma Solar project? 

In addition to the above the evaluation design and subsequent data gathering activities will address the following key research questions on outcome, objectives and Compact Goal: 
i. Has the Kigoma Solar Project contributed to an improvement in electricity service coverage across different customer types? 
ii. Has the Kigoma Solar Project contributed to an improvement in the quality of electricity available, across different customer types? 
iii. Has the Kigoma Solar Project contributed to an increase in consumption of electricity, across different customer types? 
iv. Has the Kigoma Solar Project contributed to an increase in investment in economic activities across different customer types? 
v. Has the Kigoma Solar Project contributed to an improvement in human capital accumulation across different customer types? 
vi. Has the Kigoma Solar Project contributed to a reduction in poverty across different customer types, as measured by household income per capital? 

The study is also expected to collect data that will feed into the formulation of the Economic Rate of Return (ERR) model for the Kigoma Solar program. This will include data on the sources of energy used prior to the installation of PV systems and their associated prices and quantities data, energy use and cost after the PV installation, ways and purposes for which the system are being used, and energy sources used in homes in the project area.</abstract>
    <sumDscr>
      <collDate date="2013" event="start" cycle=""/>
      <collDate date="2013" event="end" cycle=""/>
      <nation abbr="TZA">Tanzania</nation>
      <geogCover/>
      <geogUnit/>
      <anlyUnit>Community, School, Health Center, Village Market, Enterprise, Household</anlyUnit>
      <universe/>
      <dataKind>Other</dataKind>
    </sumDscr>
    <!-- qualityStatement - ddi2.5 - complex type
     
     This structure consists of two parts, standardsCompliance and otherQualityStatements. 
     In standardsCompliance list all specific standards complied with during the execution of this 
     study. Note the standard name and producer and how the study complied with the standard. 
     Enter any additional quality statements in otherQualityStatements.
     
     -->
    <qualityStatement>
      <standardsCompliance>
        <standard>
          <standardName/>
          <producer/>
        </standard>
        <complianceDescription/>
      </standardsCompliance>
      <otherQualityStatement/>
    </qualityStatement>
    <notes/>
    <!-- exPostEvaluation ddi2.5
      Use this section to describe evaluation procedures not address in data evaluation processes. 
      These may include issues such as timing of the study, sequencing issues, cost/budget issues, 
      relevance, instituional or legal arrangments etc. of the study. 
      
      The completionDate attribute holds the date the evaluation was completed. 
      The type attribute is an optional type to identify the type of evaluation with or without 
      the use of a controlled vocabulary.
    -->
    <exPostEvaluation completionDate="" type="">
      <evaluationProcess/>
      <outcomes/>
    </exPostEvaluation>
  </stdyInfo>
  <method>
    <dataColl>
      <timeMeth/>
      <!-- collectorTraining - DDI2.5
        
        Collector Training

        Describes the training provided to data collectors including internviewer training, process testing, 
        compliance with standards etc. This is repeatable for language and to capture different aspects of the 
        training process. The type attribute allows specification of the type of training being described.
        
        -->
      <collectorTraining type=""/>
      <frequenc/>
      <sampProc>(a) Stages of sample selection 

The evaluation included institution, business and household surveys. There were three stages of sample selection that were implemented at different levels. The first selection was to adopt the Kigoma Rural and Kasulu districts that are targeted by the program as study areas. The second selection involved sampling of units of observation for the institution, business and household surveys. The third sampling was selection of respondents for fishers, business and households surveys. Sampling of responding units was intervention based. It involved subjects covered by the intervention for the pre-post comparison evaluation method. This was complemented by including communities not covered by the Program as comparison group for assessing baseline status in the additional treatment and comparison groups' evaluation method. However, some facilities were eliminated from the comparison sampling frame because they were too far to get to.  Units of observation were selected based on program beneficiaries and stakeholders provided in the ToR. 

The detailed deployment plan for the program was used as sampling frame. The evaluation used Cluster sampling design with stratification because the communities are clusters while the sources of data are stratified into treated and non-treated. For efficiency purposes, villages with most of the types of the solar PV installations (village market, secondary school, dispensary, health centre, BMU and SACCOS) were purposefully be given priority. This was to ensure all types of installations, conduits and beneficiaries are covered by the evaluation. The selection of comparison of groups' villages and facilities was also done purposefully to ensure that they are located far from the target villages and facilities of the program to the extent that they cannot access services provided by the program. 

The first selection was for villages to be covered. The second stage sampling was also done purposefully based on the distribution of installations in the detailed deployment plan for the program as sampling frame and the above sample selection guide. The selection included Beach Managemetn Units (BMUs) that are also given in the detailed deployment plan for the program. It also included selection of SACCOs based on their list obtained from MCA-T and updates by Cooperative Officers of the two districts. Once an institution was sampled as a unit of observation, the head of the institution such Headmaster/mistress was automatically or purposefully selected/identified because we had already planned to interview the institution. The third stage sampling involved selection of units of respondents for outcome indicators namely fishers/boat owners that purchased PV systems through BMUs, Businesses connected to the PV system of the village market, and businesses and households that purchased the PV systems through SACCOs.  A total of 170 respondents were selected for the various surveys.</sampProc>
      <sampleFrame>
        <sampleFrameName/>
        <custodian/>
        <universe/>
        <frameUnit isPrimary="">
          <unitType numberOfUnits=""/>
        </frameUnit>
        <updateProcedure/>
      </sampleFrame>
      <deviat/>
      <collMode/>
      <resInstru/>
      <!-- instrumentDevelopment - DDI2.5             
        Describe any development work on the data collection instrument. Type attribute allows for the optional use of a defined development type with or without use of a controlled vocabulary.
        -->
      <instrumentDevelopment type=""/>
      <collSitu/>
      <actMin/>
      <ConOps/>
      <weight/>
      <cleanOps/>
    </dataColl>
    <notes/>
    <anlyInfo>
      <respRate/>
      <EstSmpErr/>
      <dataAppr/>
    </anlyInfo>
    <stdyClas/>
    <dataProcessing type=""/>
    <codingInstructions relatedProcesses="" type="">
      <txt/>
      <command formalLanguage=""/>
    </codingInstructions>
  </method>
  <dataAccs>
    <setAvail>
      <accsPlac URI="http://data.mcc.gov/evaluations/index.php/catalog/87">Millennium Challenge Corporation</accsPlac>
      <origArch>Millennium Challenge Corporation
http://data.mcc.gov/evaluations/index.php/catalog/87
Cost: None</origArch>
      <avlStatus/>
      <collSize/>
      <complete/>
      <fileQnty/>
      <notes/>
    </setAvail>
    <useStmt>
      <restrctn/>
      <citReq/>
      <deposReq/>
      <conditions/>
      <disclaimer/>
    </useStmt>
    <notes/>
  </dataAccs>
  <notes/>
</stdyDscr>
<dataDscr>
</dataDscr></codeBook>
