|
|
 |
EnterpriseROR™ FOM Schema
Description...
The dailyVest FOM Schema embodies the internal data structure of the FOM which is built by making
calls to the Client Data Interface and shows the relationships each table and corresponding
data element have to each other. This section describes only the function and purpose
of each table. For more detailed technical documentation,
please contact dailyVest.
FOM Data Schema...
The following current investor/investment data objects are available:
- RKSystem. This object contains information about the recordkeeping system, system or records, account data database, etc., and other important settings.
- Account. A single account or defined contribution plan account held at a financial institution containing one or more individual holdings. One or more individual accounts can exist o comprise a portfolio.
- SubAccount1. A child of the “Account.” Can be used to represent the different sources of money in defined contribution plans such as employer and employee contributions, rollover contributions, etc. It is a sibling of “SubAccount2.”
- SubAccount2. “SubAccount2” is another child of the “Account” and
a sibling of “SubAccount1.” In the defined contribution world, a “SubAccountX” may
contain holdings represented by “Investment Programs” (a.k.a. “IPM”), a self-directed
brokerage account, etc.
- Holding. A position in a security comprised of one or more transactions
which can have a current zero unit balance. A holding is always contained in one
account or sub-account.
- Security. A financial instrument used by the FOM including stock,
bond, mutual fund, option, and cash. The dailyVest FOM maintains a single securities
list referred to by holdings and transactions.
- Transaction. A record of activity in a position in a security (i.e.,
“holding”) such as a purchase, redemption, or reinvestment of dividends. A transaction
is always associated with one holding within one account or sub-account.
- TransType. Indicates the type of transaction and other relevant
information.
- AssetClass. Indicates the most basic, granular level of asset class
for a security such as “domestic stocks,” “international stocks,” “short-term bonds,”
etc. Among other things, an “AssetClass” can also designate a single security which
can act as a proxy for that asset class, as well as a pie slice color associated
with that asset class.
- AssetClassRollup. Indicates a “higher-level” or possibly less granular
level of asset class for a security. For example, the two asset classes “domestic
stocks” and “international stocks” could have an AssetClassRollup with a Name of
“Stocks.”
- AssetClassStyle. Designates one or more asset classes comprising
a single security, and corresponding percentages of each asset class. (For example,
IDSecurity 000004 can be comprised of 50% large-cap stocks and 50% small-cap stocks.)
- ActivityTypes. Used to broadly classify types of transaction activity,
such as Additions, Deductions, Income. Used for displaying summarizing information
in what are commonly referred to as “Account Activity Tables.”
- Price. Indicates the price of a security, usually a closing price.
- Dividend. A dividend and associated date and amount. Used for calculating
investment performance of an non-owned security (not a holding), as in a table of
average annual returns. For example, “1-Year,” “3-Year,” “5-Year,” “Since Inception”
returns.
- InvestmentOption. List containing information about the securities
available for investment within a 401k plan.
- SecurityROR. Used to maintain performance return information about
an investment security and contains applicable attributes. Typically used when displaying
a table returns for investment options.
- RORPeriod. Table containing information about the periods associated
with the SecurityROR data.
- Benchmark. Maintains information about an investment benchmark
which is associated with a security.
- FootNote. In applications where a table of investment options must
be displayed, as in a table of returns, this describes the possible footnotes (or
memos) associated with each investment option (if any).
- ModelPortfolio. The FOM supports model portfolios (zero minimum,
no maximum) which may be represented by pie charts. This object defines essential
information about one or multiple model portfolios.
- ModelPortfolioMember. This object contains information about the
elements (i.e., members or “slices”), each model portfolio declared in the “ModelPortfolio”
object.
Minimal Installation...
In order to deploy a minimal, basic installation of the FOM, the following data (tables) must be sent to the dailyVest Financial Object Model by way of the “Data Connector.”
- RKSystem
- Account
- Holding
- Security
- Transaction
- TransType
- Price
|
