Back to top anchor

Data caveats and definitions

Information on the caveats that apply to the infrastructure pipeline and the detailed data definitions.

Data caveats

The pipeline information needs to be considered in the context of the following caveats:

  • This first prototype of the pipeline contains data from five central government agencies only. Other agencies will be added in future iterations.
  • We have included only those projects that we have assessed as credible and certain (or near certain) in coming to market. Some known or anticipated projects will be included in future iterations when agencies have firmed up their intentions.
  • The data is incomplete because of the absence of specific information on the timing of project phases, and project value.In the absence of specific values, ranges have been used for this iteration.
  • Information on expected or anticipated project phasing, where provided, has been included to the nearest quarter.
  • The pipeline does not represent any ICT-related infrastructure activity.

Data definitions

Infrastructure Pipeline data columns
No Column Name Title and Label Used in the Pipeline Type Description
1 PrimaryKey N/A - not displayed. Text. Constrained to 10 characters. Alphanumeric code assigned to the project by the Infrastructure Transactions Unit. Does not change if the project changes its name and remains essentially the same project in scope. ParentProjectIDs are retired permanently and not re-used if a project is cancelled.
2 DateAddedtoDataRelease N/A - not displayed. Datetime year, month and day in YYYY-MM-DD format. Issue (publication) date of the first quarterly or ad hoc release of Infrastructure Pipeline data in which the project first appeared.
3 ProcuringAgencyOrganisation Procuring agency Text. Enclosed in standard double-quotes as some agency names may include commas; comma is used as the delimiter in the CSV for download. Full legal name of the Crown entity or public service department managing the procurement process for infrastructure projects.
4 ProjectName Project Text. Enclosed in standard double-quotes as some names may include commas; comma is used as the delimiter in the CSV for download. Project name as supplied by the procuring agency. May have been modified slightly by the Infrastructure Transactions Unit to expand on acronyms or abbreviations that may be unfamiliar outside the procuring agency.
5 ProjectShortDescription N/A - displayed without a label on project detail pages. Text. Enclosed in standard double-quotes as some descriptions may include commas; comma is used as the delimiter in the CSV for download. Short paragraph supplied by the procuring agency.
6 ParentProjectID N/A - not displayed. Text. Constrained to 10 characters. If a project or programme of work has sub-projects the PrimaryKey of the parent project will be identified in this column.
7 ProjectStatus Project status Text. Options are: Business Case / Investment Case Development; In Procurement; Under Construction.
8 ProcurementMethod Procurement method Text. Options are: To be determined; Design and construct; Construct only; Public Private Partnership; Other.
9 ProjectRegion Region Text. Regions as defined by local government authorities. The Nationwide option is selected if a project spans multiple regions. Options are: Nationwide; Northland; Auckland; Waikato; Bay of Plenty; Gisborne; Hawkes Bay; Taranakil; Manawatu - Wanganui; Wellington; Marlborough; Tasman; West Coast; Canterbury; Otago; Southland.
10 ProjectSector Sector Text. Sector terms have been chosen by the Infrastructure Transactions Unit. Department of Corrections projects have been incorporated under a broader Justice sector heading.
11 EstimatedProjectValueRange Cost range Text. Options are: < 5 Million; 5 - 25 Million; 25 - 50 Million; 50 - 100 Million; 100 - 250 Million; 250 - 500 Million; 500 Million +.
12 EstimatedQuarterBusinessCaseStart Business case (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency is not yet able to break down the project dates for the three phases.
13 EstimatedQuarterBusinessCaseCompletion Business case (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency is not yet able to break down the project dates for the three phases.
14 EstimatedQuarterProcurementStart Procurement (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency is not yet able to break down the project dates for the three phases.
15 EstimatedQuarterProcurementCompletion Procurement (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency is not yet able to break down the project dates for the three phases.
16 EstimatedQuarterConstructionStart Construction (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency is not yet able to break down the project dates for the three phases.
17 EstimatedQuarterConstructionCompletion Construction (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency is not yet able to break down the project dates for the three phases.
18 EstimatedQuarterProjectRangeStart Phases undetermined (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency has been able to break down the project dates into three phases.
19 EstimatedQuarterProjectRangeCompletion Phases undetermined (est) Text. Format YYYY-Q#. Alphanumeric to allow sorting in year YYYY- then quarter Q# order. Quarters relate to the calendar not fiscal (government financial) year. Q1 is from 1 January to 31 March; Q2 from 1 April to 30 June; Q3 from 1 July to 30 September; and Q4 from 1 October to 31 December. Value will be null (empty) if a procuring agency has been able to break down the project dates into three phases.
20 ProjectInfoURL Project info URL Text. URI or URL supplied by a procuring agency for more information about either a. the specific project, b. the agency's infrastructure and procurement plans or c. the procuring agency.
21 EstimatedProjectValueNote N/A - not displayed. Text. A procuring agency may supply information to explain why a project value fits within a partcular range.
Last updated: 
Thursday, 9 May 2019