Here's an excerpt from helpful article
Let's examine this concept in the context of packages stored in the .dtsx
format in the file system, which implies that they are part of the legacy
Package Deployment Model (we will deal with the implications of Project
Deployment Model on dtexec.exe operations in an upcoming article), starting with
the property paths of the variables (refer to
one of our earlier
articles for more information on the subject of
SSIS
variables). In order to reference a variable via the property path notation,
you need to provide its scope, namespace, and name. As a general rule (in the
case of the Package Deployment Model), the notation always starts with the
\Package prefix. The backslash character ('\') is a container separator, period
('.') designates collections (such as Properties and Variables), while members
of these collections are identified by their index, enclosed in square brackets
([]). The index is formed by specifying a unique characteristic of a collection
member, which can be either its name (in the case of Properties) or (when
dealing with Variables, where duplicates are allowed) also their namespace, with
the double colon (::) as the separator.
In order to become more accustomed to this syntax, let's consider a sample
package that contains a single Data Flow Task with its default name and two user
variables. Var1 has the package-wide scope while the visibility of Var2 is
limited to the Data Flow Task only. With these settings in place, you can
reference our variables in the following manner:
\Package.Variables[User::Var1].Properties[Value]
\Package\Data Flow Task.Variables[User::Var2].Properties[Value]
http://www.databasejournal.com/features/mssql/SSIS-2012-using-dtexec.exe-to-run-file-system-based-packages.html