A set of predefined models is available in the SSM procedure for models called structural models in the time series literature. These predefined models can be used to model trend, seasonal, and cyclical patterns in the univariate and multivariate time series. For the most part, the multivariate models are straightforward generalizations of the corresponding univariate models—for example, the multivariate random walk trend described later in this section generalizes the univariate random walk trend that is described in the section Random Walk Trend. All of these models, with the exception of the continuoustime cycle model, are applicable only to the regular data type. The continuoustime cycle model is applicable to all the data types; however, it is available for the univariate case only.
To specify these models, you must first use the STATE statement with the correct TYPE= option. When you specify the TYPE=option, you do not need to specify other options of the STATE statement (for example, the T option, the COV1 option, and the A1 option). However, you must specify the COV option, which describes the covariance of the disturbance term that drives the state equation. Throughout this section, the symmetric matrix specified by using the COV option is denoted by . For TYPE= LL, an additional matrix, specified by using the SLOPECOV suboption, also plays a role; it is denoted by . Subsequently you must specify one or more COMPONENT statements to define the (univariate) components that are based on this state subsection for their inclusion in the MODEL statement. These univariate components exhibit interesting behavior based on the structure of (and , whenever applicable)—for example, imposing rank restrictions on in the multivariate random walk results in these univariate trends moving together. For additional information about these models, see Harvey (1989).
The following example summarizes the steps needed to define a multivariate structural model by using a sequence of STATE and
COMPONENT statements. For a full example, see Example 27.1. Suppose that a threedimensional time series is being studied with response variables y1, y2
, and y3
. Suppose you want to specify the trivariate structural model

where denotes the response series, and , , and denote the trivariate components, trend, cycle, and white noise, respectively. The three components of , the observation noise in the model, are not assumed to be independent. Therefore, you cannot specify them by using three IRREGULAR statements; you must include them in the state specification. The following (incomplete) statements show how to specify this model:
state whiteNoise(3) type=wn ...; component wn1 = whiteNoise[1]; component wn2 = whiteNoise[2]; component wn3 = whiteNoise[3]; state randomWalk(3) type=rw ...; component rw1 = randomWalk[1]; component rw2 = randomWalk[2]; component rw3 = randomWalk[3]; state cycleState(3) type=cycle ...; component c1 = cycleState[1]; component c2 = cycleState[2]; component c3 = cycleState[3]; model y1 = rw1 c1 wn1; model y2 = rw2 c2 wn2; model y3 = rw3 c3 wn3;
The first STATE statement defines whiteNoise
, a state subsection that is needed for defining a threedimensional white noise component. In turn, whiteNoise
is used to define the three univariate white noise components: wn1
, wn2
, and wn3
. The components wn1
, wn2
, and wn3
are correlated—their correlation structure is controlled by the covariance specification of whiteNoise
. The second set of STATE and COMPONENT statements result in three correlated random walk trend components: rw1
, rw2
, and rw3
. Finally, the last set of STATE and COMPONENT statements result in three correlated cycle components: c1
, c2
, and c3
. In the end, the desired multivariate model is defined by including these (univariate) components in the appropriate MODEL
statements.
In the preceding example, it is important to note the relationship between the nominal dimension (denoted by dim throughout this section) that is specified in the STATE statement and the actual dimension of the resulting state subsection.
Note that the three state subsections, whiteNoise
, randomWalk
, and cycleState
, are defined by using the same dim specification: 3. However, the actual dimensions of these state subsections depend on their type; they do not need to equal
this specified dimension. Here, whiteNoise
and randomWalk
do have the same size, 3, as the specified dim. However, the size of cycleState
, which is of TYPE=CYCLE, is . Another important point to note: no matter what the underlying size of the state subsection, the desired univariate components
were obtained by using an identical specification scheme in the COMPONENT statement. This happens because the component specification
style that is based on the element operator—[]—in the COMPONENT statement behaves differently when the TYPE= option is used
to define the state subsection (see the section Multivariate Season for an illustration).
The system matrices for all these models are timeinvariant, with the exception of the continuoustime cycle model. In this section, denotes the subsection of the overall model state , and , , and denote the corresponding blocks of the larger system matrices.
For the multivariate cycle system matrices described in the section Multivariate Cycle, the Kronecker product notation is useful: if is an matrix and is a matrix, then the Kronecker product is an block matrix:

The STATE statement option TYPE=WN specifies white noise of dimension dim—that is, a sequence of zero mean, independent, Gaussian vectors with covariance . The specification of the associated system matrices is trivial: is zero, , and the initial condition is nondiffuse ( and ).
Multivariate white noise is needed to specify the observation equation noise term for the multivariate models for the time
series data. Since the state space formulation for the SSM procedure requires the observation equation noise vector to have
the diagonal form, you need to include the noise vector in the state. The noise term for the th response variable is defined by a component that simply picks the th element of this multivariate white noise. For example, the component wn_i
defined as follows can be used as a noise term in the MODEL statement of the th response variable:
state white(dim) type=wn ...; component wn_3 = white[3];
The STATE statement option TYPE=RW specifies a dimdimensional random walk

where is a sequence of zero mean, independent, Gaussian vectors with covariance . The specification of the associated system matrices is trivial: is a dimdimensional identity matrix, , , and the initial condition is fully diffuse ( and ).
The multivariate random walk is a useful trend model for multivariate time series data. The trend term for the th response variable is defined by a component that simply picks the th () element of . For example, the component rw_i
defined as follows can be used as a trend term in the MODEL statement of the th response variable:
state randomWalk(3) type=rw ...; component rw_2 = randomWalk[2];
The STATE statement option TYPE=LL specifies a (2*dim)dimensional , needed for defining a dimdimensional local linear trend. The first dim elements of correspond to the needed multivariate trend, and the subsequent dim elements are needed to capture the slope vector of this trend. can be defined as

where is a sequence of zero mean, independent, Gaussian vectors with covariance and is a 2*dimdimensional block matrix . The initial condition is fully diffuse ( and ). This is a multivariate generalization of the univariate local linear trend.
The multivariate local linear trend is a useful trend model for multivariate time series data. The trend term for the th response variable is defined by a component that simply picks the th element () of . For example, the component ll_i
defined as follows can be used as a trend term in the MODEL statement of the th response variable:
state localLin(dim) type=ll(slopecov..) ...; component ll_3 = localLin[3];
The STATE statement option TYPE=CYCLE specifies a (2*dim)dimensional , needed for defining a dimdimensional cycle. As in the LL case, the first dim elements of correspond to the needed dimdimensional cycle, and the remaining dim elements contain some auxiliary quantities. The cycle model defined in this subsection requires a regular data type—that is, the CT option is not included. Let denote the damping factor, and let period be the frequency associated with the cycle. The admissible parameter ranges are and period , which implies that . Let , a matrix, and let , a matrix. With this notation, the transition equation associated with is

where is a sequence of zero mean, independent, dimensional Gaussian vectors with covariance . If , the initial condition is fully diffuse ( and ). Otherwise, it is nondiffuse: and .
The multivariate cycle is useful for capturing periodic behavior for multivariate time series data. The cycle term for the
th response variable is defined by a component that simply picks the th element of . For example, the component cycle_i
defined as follows can be used as a cycle term in the MODEL statement of the th response variable:
state cycleState(dim) type=cycle ...; component cycle_2 = cycleState[2];
The STATE statement option TYPE=SEASON(LENGTH=s) specifies a ((s–1)*dim)dimensional , needed for defining a dimdimensional trigonometric season component with season length s. A (multivariate) trigonometric season component, , is a sum of (multivariate) cycles of different frequencies,

where the constituent cycles , called harmonics, have frequencies s. All the harmonics are assumed to be statistically independent, have the same damping factor , and are governed by the disturbances with the same covariance matrix . The number of harmonics, , equals if is even and if it is odd. This means that specifying TYPE=SEASON(LENGTH=s) is equivalent to specifying cycle specifications with correct frequencies, damping factor , and the COV option restricted to the same covariance . The resulting is necessarily ((s–1)*dim)dimensional. When the season length is even, the last harmonic cycle, , has frequency and requires special attention. It is of dimension dim rather than 2*dim because its underlying state equation simplifies to a dimvariate autoregression with autoregression coefficient . As a result of this discussion, it is clear that the system matrices and associated with the ((s–1)*dim)dimensional are blockdiagonal with the blocks corresponding to the harmonics. The initial condition is fully diffuse.
For all the models discussed so far, the first dim elements of provided the needed (multivariate) component. This is not the case for the (multivariate) season component. Extracting the th seasonal component from requires accumulating the contributions from the harmonics that are associated with this th seasonal, which are not organized contiguously in . For example, suppose that dim is 2 and the season length s is 4. In this case is 2, and the bivariate seasonal component is a sum of two independent bivariate cycles, and . The cycle has frequency and its underlying state, say , has dimension . The last harmonic, , has frequency , and therefore its underlying state, say , has dimension 2. The combined state has dimension . In order to extract the first bivariate seasonal component, you must extract the first components of bivariate cycles and , which in turn implies the first elements of and , respectively. Thus, obtaining the first bivariate seasonal component requires extracting the first and the fifth elements of the combined state . Similarly, obtaining the second bivariate seasonal component requires extracting the second and the sixth elements of the combined state . All this can be summarized by the dot product expressions






where and denote the first and second components, respectively, of the bivariate seasonal component. Note that and are univariate seasonal components, each of season length , in their own right. They are correlated components; their correlation structure depends on .
Obtaining the desired components of the multivariate seasonal component is made easy by a special syntax convention of the COMPONENT statement. Continuing with the previous example, the following examples illustrate two equivalent ways of obtaining and . The first set of statements explicitly specify the linear combinations needed for defining and :
state seasonState(2) type=season(length=4) ...; component s_1 =( 1 0 0 0 1 0 ) * seasonState; component s_2 =( 0 1 0 0 0 1 ) * seasonState;
The following simpler specification achieves the same result:
state seasonState(2) type=season(length=4) ...; component s_1 = seasonState[1]; component s_2 = seasonState[2];
In the latter specification, the meaning of the element operator [] changes if the state in question is defined by using the TYPE= option.
You can specify a state vector that follows a multivariate autoregressive, moving average (VARMA) model by using the STATE statement option TYPE=VARMA. The autoregressive and moving average orders can be either 0 or 1 ( and )—that is, only VAR(1), MA(1), and VARMA(1,1) models can be specified. The notation and the state space form of the VARMA model described here is taken from Reinsel (1997), which is a good reference for VARMA modeling.
A dimdimensional vector process follows a zeromean, autoregressive order p, moving average order q (VARMA(p, q)) model if it satisfies the following matrix difference equation:

Here and are dimdimensional square matrices and is a dimdimensional, Gaussian, white noise sequence with covariance matrix . If autoregressive order p is 0, the term that involves is absent; similarly, if the moving average order q is 0, the term that involves is absent. Since AR and MA orders can be at most 1, the subscripts of and can be ignored in this discussion—when applicable, an AR coefficient matrix is denoted by and an MA coefficient matrix is denoted by . The unknown elements of , , and constitute the parameter vector that is associated with a VARMA state. The process defined by the VARMA difference equation is stationary and invertible (Reinsel 1997) if and only if the eigenvalues of and are strictly less than 1 in magnitude. By default, the SSM procedure imposes these stationarity and invertibility restrictions on and . However, you can specify to be an identity matrix, in which case the resulting process is nonstationary.
A VARMA model can be cast into a state space form. The state space form used by the SSM procedure is described in Reinsel (1997, pp 52–53). The system matrices for the supported VARMA models are as follows:
The VAR(1) form is the simplest. In this case, the underlying state is the same as the VAR(1) process . Therefore, and .
Taking equal to the zero matrix if , the VARMA(1,1) and MA(1) cases can be treated together. In this case, the underlying state is 2*dim dimensional and the desired VARMA process corresponds to its first dim elements. Let . Then, in the blocked form,

Unless is restricted to be identity, the underlying state is stationary and the covariance of the initial condition is computed by

where denotes the Kronecker product and the operation on a matrix creates a vector formed by vertically stacking the rows of that matrix. If is restricted to be identity, the initial condition is fully diffuse.
The STATE statement option TYPE=CYCLE(CT) specifies a twodimensional , needed for defining a univariate continuous time cycle. In this case the nominal dimension, dim, must be 1. In particular, becomes onedimensional, which is denoted by . This cycle can be used for any data type. As before, the parameters of the cycle are a damping factor , , and period . Unlike in the discretetime cycle described in the section Multivariate Cycle, the period is not required to be larger than 2. Let , and let denote the difference between successive time points. In this case, the system matrices and that govern depend on . They are:









If , the initial condition is nondiffuse: . For , the initial condition is fully diffuse.
The first element of corresponds to the needed cycle, and the second element is an auxiliary quantity. You can define a cycle term based on this state as follows:
state cycleState(1) type=cycle(CT) ...; component cycle = cycleState[1];
The CT option must be included in the use of TYPE=CYCLE.