Variable Insurance Product (VIP) Data Sets

Contents

1          Overview                                  1

2          Scope                                       2

3          Organization                             2

4          File Formats                              4

5          Table Definitions                      4

5.1   SUB (Submissions)                   5

5.2   SCN (Series Class Name)          7

5.3   TAG (Tags)                               8

5.4   NUM (Numbers)                        8

5.5   TXT (Plain Text)                        9

 

Figure 1. Data relationships                  4

Figure 2. Fields in the SUB data set       5

Figure 3. Fields in the SCN data set      7

Figure 4. Fields in the TAG data set       8

Figure 5. Fields in the NUM data set      8

Figure 6. Fields in the TXT data set       9

 

1         Overview

The following data sets provide information extracted from eXtensible Business Reporting Language (XBRL) submissions filed with the Commission in a flattened data format to assist users in more easily consuming the data for analysis. The data is sourced from selected information found in Forms N-3, N-4 and N-6 XBRL submissions to the Commission.  Filers prepare these submissions using the Variable Insurance Product Taxonomy and Taxonomy Guide, which are available and periodically updated at https://xbrl.sec.gov/vip/.

Certain additional fields used in the Commission's Electronic Data Gathering, Analysis, and Retrieval (EDGAR) system are also included to help in supporting the use of the data.  The information has been taken directly from submissions created by each registrant, and the data is "as filed" by the registrant.  The data sets will be updated monthly.  

DISCLAIMER: The VIP Data Sets contain information derived from structured data filed with the Commission by individual registrants as well as Commission-generated filing identifiers. Because the data sets are derived from information provided by individual registrants, we cannot guarantee the accuracy of the data sets. In addition, it is possible inaccuracies, or other errors were introduced into the data sets during the process of extracting the data and compiling the data sets. Finally, the data sets do not reflect all available information, including certain metadata associated with Commission filings. The data sets are intended to assist the public in analyzing data contained in Commission filings; however, they are not a substitute for such filings. Investors should review the full Commission filings before making any investment decision.

The data extracted from the XBRL submissions is organized into data sets containing information about submissions, numbers, taxonomy tags, and more.  Each data set consists of rows and fields and is provided as a tab-delimited TXT format file.  The data sets are as follows:

·         SUB – Submission data set; this includes one record for each XBRL submission. The set includes fields of information pertinent to the submission and the filing entity.

·         SCN – Series Class Name data set; includes the series and class identifiers for each submission.

·         TAG – Tag data set; includes defining information about each tag.  Information includes tag descriptions (documentation labels), taxonomy version information and other tag attributes.

·         NUM – Number data set; this includes one row for each distinct amount tagged in the submission.

·         TXT – Text data set; this is the plain text of all the non-numeric tagged items in the submission.

2         Scope

The scope of the data in the VIP data sets consists of:

·         Numeric data and non-numeric "plain text" data from XBRL submissions;

·         XBRL submissions that include a Variable Insurance Product (VIP) taxonomy element;

·         Submitted from February 2023 through the "Data Cutoff Date" inclusive.

All data values are "as filed."

3         Organization

Note that this data set represents "as filed" EDGAR document submissions containing multiple reporting periods (including amendments of prior submissions). Data in this submitted form may contain redundancies, inconsistencies, and discrepancies relative to other publication formats. Each data set is accompanied by a metadata file conforming to the W3C specification for tabular data (https://www.w3.org/TR/2015/REC-tabular-data-model-20151217/ ) that encodes the following information about the data sets and their relationships to each other.

1.    SUB identifies all the EDGAR submissions in the data set, with each row having the unique (primary) key adsh, a 20-character EDGAR Accession Number with dashes in positions 11 and 14.

2.    SCN is a data set that provides the series and class (contract) names and identifiers for each submission.  These fields comprise a unique compound key:

1)    adsh - EDGAR accession number

2)    seriesid - 10-character series identifier.

3)    classid - 10-character class identifier.

3.    TAG is a data set of all tags used in the submissions, both standard and custom.  These fields comprise a unique compound key:

1)    tag – tag used by the filer

2)    version – if a standard tag, the taxonomy of origin, otherwise equal to adsh.

4.    NUM is a data set of all numeric XBRL facts presented in the submission. These fields comprise a unique compound key:

1)    adsh - EDGAR accession number

2)    tag - tag used by the filer

3)    version – if a standard tag, the taxonomy of origin, otherwise equal to adsh.

4)    ddate - document date

5)    uom - unit of measure

6)    segments – XBRL tags used to represent axis and member reporting

 

5.    TXT is a data set that contains the plain (no HTML) text of each non-numeric XBRL fact.  These fields comprise a unique compound key:

1)    adsh - EDGAR accession number

2)    tag – tag used by the filer

3)    version – if a standard tag, the taxonomy of origin, otherwise equal to adsh

4)    ddate - period end date

5)    segments – XBRL tags used to represent axis and member reporting


 

The relationship of the data sets is as shown in Figure 1. The Accession Number (adsh) found in the NUM and TXT data set can be used to retrieve information about the submission in SUB.  Each row of data in NUM or TXT was tagged by the filer using a tag. Information about the tag used can be found in TAG.  Each row of data in NUM or TXT appears on one or more lines detailed in LAB.

Figure 1. Data relationships

Data set

Fields referencing other datasets

Referenced dataset

Referenced fields

NUM

adsh

SUB

adsh

tag, version

TAG

tag, version

 

adsh, contract

SCN

adsh, classId

TXT

adsh

SUB

adsh

tag, version

TAG

tag, version

 

adsh, contract

SCN

adsh, classId

 

4         File Formats

Each of the data sets is provided in a single encoding, as follows:

Tab Separated Value (.tsv): utf-8, tab-delimited, \n- terminated lines, with the first line containing the field names in lowercase.

5         Table Definitions

The fields in the figures below provide the following information: field name, description, source, data format, maximum field size, an indication of whether the field may be NULL (yes or no), and key.  

The Source field (SUB only) has two possible values:

·         EDGAR indicates that the source of the data is the filer's EDGAR submission header.

·         XBRL indicates that the source of the data is the filer's XBRL submission.

The Key field indicates whether the field is part of a unique index on the data.  There are two possible values for this field:

·         "*" – Indicates the field is part of the unique key for the row.

·         Empty (nothing in field) – the field is not part of the unique compound key.


 

5.1       SUB (Submissions)

The submissions data set contains summary information about an entire EDGAR submission. Some fields were sourced directly from EDGAR submission information, while other fields of data were sourced from the XBRL submission. Note: EDGAR derived fields represent the most recent EDGAR assignment as of a given filing's submission date and do not necessarily represent the most current assignments.   

Figure 2. Fields in the SUB data set

Field Name

Field Description

Source

Format

Max Size

May be NULL

Key

adsh

Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.

EDGAR

ALPHANUMERIC (nnnnnnnnnn-nn-nnnnnn)

20

No

*

cik

Central Index Key (CIK). Ten-digit number assigned by the Commission to each registrant that submits filings.

EDGAR

NUMERIC

10

No

 

name

Name of registrant. This corresponds to the name of the legal entity as recorded in EDGAR as of the filing date.

EDGAR

ALPHANUMERIC

150

No

 

countryba

The ISO 3166-1 country of the registrant's business address.

EDGAR

ALPHANUMERIC

2

Yes

 

stprba

The state or province of the registrant's business address if field countryba is US or CA.

EDGAR

ALPHANUMERIC

2

Yes

 

cityba

The city of the registrant's business address.

EDGAR

ALPHANUMERIC

30

Yes

 

zipba

The zip code of the registrant's business address.

EDGAR

ALPHANUMERIC

10

Yes

 

bas1

The first line of the street of the registrant's business address.

EDGAR

ALPHANUMERIC

40

Yes

 

bas2

The second line of the street of the registrant's business address.

EDGAR

ALPHANUMERIC

40

Yes

 

baph

The phone number of the registrant's business address.

EDGAR

ALPHANUMERIC

20

Yes

 

countryma

The ISO 3166-1 country of the registrant's mailing address.

EDGAR

ALPHANUMERIC

2

Yes

 

stprma

The state or province of the registrant's mailing address if field countryma is US or CA.

EDGAR

ALPHANUMERIC

2

Yes

 

cityma

The city of the registrant's mailing address.

EDGAR

ALPHANUMERIC

30

Yes

 

zipma

The zip code of the registrant's mailing address.

EDGAR

ALPHANUMERIC

10

Yes

 

mas1

The first line of the street of the registrant's mailing address.

EDGAR

ALPHANUMERIC

40

Yes

 

mas2

The second line of the street of the registrant's mailing address.

EDGAR

ALPHANUMERIC

40

Yes

 

countryinc

The ISO 3166-1 country of incorporation for the registrant.

EDGAR

ALPHANUMERIC

2

Yes

 

stprinc

The state or province of incorporation for the registrant, if countryinc is US or CA, otherwise NULL.

EDGAR

ALPHANUMERIC

2

Yes

 

ein

Employee Identification Number, 9-digit identification number assigned by the Internal Revenue Service to business entities operating in the United States.

EDGAR

NUMERIC

10

Yes

 

former

Most recent former name of the registrant, if any.

EDGAR

ALPHANUMERIC

150

Yes

 

changed

Date of change from the former name, if any.

EDGAR

DATE (yyyymmdd)

8

Yes

 

form

The submission type of the registrant's filing.

EDGAR

ALPHANUMERIC

20

No

 

filed

The date of the registrant's filing with the Commission.

EDGAR

DATE (yyyymmdd)

8

No

 

accepted

The acceptance date and time of the registrant's filing with the Commission.

EDGAR

DATETIME (yyyy‑mm‑dd hh:mm:ss)

19

No

 

instance

The name of the submitted XBRL Instance Document type data file.

EDGAR

ALPHANUMERIC (example: abcd‑yyyymmdd.xml)

40

No

 

docEndDate

Document end date

XBRL

DATE (yyyy-mm-dd)

10

Yes

doctype

Document type: N-3, N-4, N-6

XBRL

ALPHANUMERIC

3

No

 

 

Note: To access the complete submission files for a given filing, please see the Commission EDGAR website.  The Commission website folder https://www.sec.gov/Archives/edgar/data/{cik}/{accession}/ will always contain all the data sets for a given submission.  To assemble the folder address to any filing referenced in the SUB data set, simply substitute {cik} with the cik field and replace {accession} with the adsh field (after removing the dash character).  The following sample SQL Query provides an example of how to generate a list of addresses for filings contained in the SUB data set:

·         select name,form,period, 'https://www.sec.gov/Archives/edgar/data/' + ltrim(str(cik,10))+'/' + replace(adsh,'-','')+'/'+instance as url from sub order by period desc, name

 

5.2       SCN (Series Class Name)

The SCN data set contains the series and class (contract) identifiers and names for each submission.  The source for the table is the EDGAR submission header.

Figure 3. Fields in the SCN data set

Field Name

Field Description

Field Type (format)

Max Size

May be NULL

Key

adsh

Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.

ALPHANUMERIC

20

No

*

seriesid

10-character series identifier.

ALPHANUMERIC

10

No

*

seriesName

Series name.

ALPHANUMERIC

150

No

 

classid

10-character class (contract) identifier.

ALPHANUMERIC

10

No

 *

className

Class (contract) name.

ALPHANUMERIC

150

No

 

5.3       TAG (Tags)

The TAG data set contains the standard taxonomy tags and the custom taxonomy tags defined in the submissions.  The source is the "as filed" XBRL filer submissions.  The standard tags are derived from taxonomies in https://www.sec.gov/data-research/standard-taxonomies as of the date of the original submission. 

Figure 4. Fields in the TAG data set

Field Name

Field Description

Field Type

Max Size

May be NULL

Key

tag

The unique identifier (name) for a tag in a specific taxonomy release.

ALPHANUMERIC

256

No

*

version

For a standard tag, an identifier for the taxonomy; otherwise the accession number where the tag was defined.

ALPHANUMERIC

20

No

*

custom

1 if tag is custom (version=adsh), 0 if it is standard. Note: This flag is technically redundant with the version and adsh fields.

BOOLEAN (1 if true and 0 if false)

1

No

 

abstract

1 if the tag is not used to represent a fact.

BOOLEAN (1 if true and 0 if false)

1

No

 

datatype

If abstract=1, then NULL, otherwise the data type (e.g., monetary) for the tag.

ALPHANUMERIC

20

Yes

 

iord

If abstract=1, then NULL; otherwise, "I" if the value is a point in time, or "D" if the value is a duration.

ALPHANUMERIC

1

Yes

 

tlabel

If a standard tag, then the label text provided by the taxonomy, otherwise the text provided by the filer.  A tag which had neither would have a NULL value here.

ALPHANUMERIC

512

Yes

 

doc

The detailed definition for the tag. If a standard tag, then the text provided by the taxonomy, otherwise the text assigned by the filer.  Some tags have neither, in which case this field is NULL.

ALPHANUMERIC

Yes

 

 

5.4       NUM (Numbers)

The NUM data set contains numeric data, one row per data point. The source for the table is the "as filed" XBRL filer submissions.

Figure 5. Fields in the NUM data set

Field Name

Field Description

Field Type (format)

Max Size

May be NULL

Key

adsh

Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.

ALPHANUMERIC

20

No

*

tag

The unique identifier (name) for a tag in a specific taxonomy release.

ALPHANUMERIC

256

No

*

version

For a standard tag, an identifier for the taxonomy; otherwise, the accession number where the tag was defined.

ALPHANUMERIC

20

No

*

ddate

The end date for the data value, rounded to the nearest month end.

DATE (yyyymmdd)

8

No

*

uom

The unit of measure for the value.

ALPHANUMERIC

20

No

*

segments

Tags used to represent axis and member reporting. Axis tags are on the left of the equal sign (=) and members on the right. Delimited by a semicolon. The version of tag is in parenthesis with custom tags having the adsh.

ALPHANUMERIC

1024

No

*

value

The value. This is not scaled, it is as found in the Interactive Data file but is rounded to four digits to the right of the decimal point.

NUMERIC

16

Yes

 

footnote

The plain text of any superscripted footnotes on the value, if any.

ALPHANUMERIC

512

Yes

 

footlen

Number of bytes in the plain text of the footnote; zero if no footnote.

NUMERIC

4

No

 

dimn

Small integer representing the number of dimensions.  Note that this value is a function of the dimension segments.

NUMERIC

1

No

 

contract

Contract to which the fact applies.

ALPHANUMERIC

256

No

 

5.5       TXT (Plain Text)

The TXT data set contains non-numeric data, one row per data point. The source for the table is the "as filed" XBRL filer submissions.

Figure 6. Fields in the TXT data set

Field Name

Field Description

Field Type (format)

Max Size

May be NULL

Key

adsh

Accession Number. The 20-character string formed from the 18-digit number assigned by the Commission to each EDGAR submission.

ALPHANUMERIC

20

No

*

tag

The unique identifier (name) for a tag in a specific taxonomy release.

ALPHANUMERIC

256

No

*

version

For a standard tag, an identifier for the taxonomy; otherwise, the accession number where the tag was defined. 

ALPHANUMERIC

20

No

*

ddate

The end date for the data value, rounded to the nearest month end.

DATE (yyyymmdd)

8

No

*

segments

Tags used to represent axis and member reporting. Axis tags are on the left of the equal sign (=) and members on the right. Delimited by a semicolon. The version of tag is in parenthesis with custom tags having the adsh.

ALPHANUMERIC

1024

No

*

dimn

Small integer representing the number of dimensions, useful for sorting.  Note that this value is function of the dimension segments.

NUMERIC

1

Yes

 

txtlen

The original length of the whitespace normalized value.

NUMERIC(4,0)

4

Yes

 

footnote

The plain text of any superscripted footnotes on the value, as shown on the page or if there is no footnote, then this field will be blank.

ALPHANUMERIC

512

Yes

 

footlen

Number of bytes in the plain text of the footnote.

NUMERIC(4,0)

4

Yes

 

value

The value, with all whitespace normalized, that is, all sequences of line feeds, carriage returns, tabs, non-breaking spaces, and spaces having been collapsed to a single space, and no leading or trailing spaces.  Escaped XML that appears in EDGAR "Text Block" tags is processed to remove all mark-up (comments, processing instructions, elements, attributes).  The value is truncated to a maximum number of bytes.  The resulting text is not intended for end user display but only for text analysis applications. 

ALPHANUMERIC

Yes

 

contract

Contract to which the fact applies.

ALPHANUMERIC

256

No