The OMD Sync Settings page is available from the Synchronize Module located on the Main Admin page.

Central currently supports both OMD NetVision and iManager (referred to as NetVision the rest of this page) applications compatible with OMD single or multi meter versions.

The OMD Sync Settings page lists the Main Dealer and each sub-dealer account (defined as an account with a dealer user assigned as the primary contact) as a separate row in the account grid.  This allows you to configure each with a different OMD server connection settings and/or push/pull frequencies.  Placing a check in the appropriate Select row, performs a 2-way sync with all child accounts.  All sub-dealer accounts by default inherit the OMD server connection settings configured for the Main Dealer, unless otherwise specified.

During an OMD PULL; defined as the extraction of data from OMD NetVision, the following information is extracted and imported into Central:

1)  Accounts; OMD accounts and account locations that have devices assigned to them

2)  Devices; OMD devices which are assigned to an imported account

2)  Contract Data; OMD contract data which is assigned to an imported device

The accounts imported from OMD are compared to those which already exist in Central. Accounts are mapped based on identical OMD account names and by cross referencing the device serial numbers and equipment id's.  The remaining OMD accounts which are not mapped are referred to as OMD Orphans.  Using the OMD Orphans page, accounts may be mapped to unlike names, or selected individually thereby creating new Central accounts.

Optionally, you can combine the Central Meter Validation results, allowing the meters extracted using Onsite, WebAudit or Viewer to be pre-approved by either the end-user or dealer employee prior to a PUSH; defined as the submission of data to OMD NetVision.  This process helps to reduce DSO (Day-Sales-Outstanding) by providing accurate and timely billing.

If FMAudit Central is offline and misses multiple syncs, then it only performs the last scheduled sync when it comes back online.

OMD Server Connection Settings
Minimally, the Main Dealer account requires the server connection settings to be specified.  To view another sub-dealer account and/or modify these settings, select the sub-dealer account from the Dealer Account drop-down list.  Modifying the OMD Server Connection Settings and selecting the Save Connection Settings button, applies those settings to the current sub-dealer account and all child accounts, no longer inheriting the settings from the Main Dealer.

NetVision URL
The Central OMD NetVision URL value is the same URL used to access and log into NetVision.

NetVision Service URL
The Central OMD NetVision Service URL value (sometimes referred to as the Transoft Driver or H2O URL) is used by the OMD application to receive data for meters being pushed by applications such as Central.

If Central is hosted internally: defined as Central being hosted on the same local network as OMD;

use the internal LAN IP or server name, i.e. http://internal_server_name_or_ip:8080/twaa/servlet/twaaserver.  By default the NetVision Service URL is installed using port 8080.

If Central is hosted externally: defined as Central being hosted on and outside server which is not on the same local network as OMD

your network administrator will need configure your router and/or DNS appropriately (contact FMAudit's implementation team for assistance), i.e. http://omd.dealerwebsite.com:8080/twaa/servlet/twaaserver/. 

Source Tag
This option is currently not required.

OMD Meters
Depending on your OMD version, the OMD Sync may be set to support synchronization and submission of meters to either a single or multi meter OMD application.  For a single meter OMD application that has more than one serial record created to reflect multiple meters, i.e. appending a suffix or prefix to the serial number, the Central OMD Sync will detect the mappings and list the results.

Authentication
The OMD iManager/NetVision application requires a NetVision User ID (composed of a User name and Password) for access past the login page.  A NetVision User ID is created via the NetVision Control record utility (not to be confused with an OMD Vision login).

The User/Pass values entered into the Central OMD Sync must match the NetVision User ID.  A single NetVision User ID allows you to associate a maximum of 1,000 accounts in the OMD application, therefore additional NetVision User ID's must be assigned via the NetVision Control record utility, with the corresponding User/Pass combinations added to the Central OMD Sync settings.

Contact OMD and request a copy of the REQL83 program that is used to assign all of the accounts within a range to a NetVision User ID, then increment the User names, i.e.:

User1 / Pass1 = OMD Accounts 1 to 999

User2 / Pass2 = OMD Accounts 1,000 to 1,999

User3 / Pass3 = OMD Accounts 2,000 to 2,999

and so on...

Meter Name Mapping
FMAudit products use static meter names, therefore the OMD Sync allows you to specify the associated OMD meter names.  When using multi meter OMD applications, it is the OMD Meter Label (maximum length 20 characters) that is matched to (not to be confused with Meter Code or Meter Description).  For OMD single meter applications the main device serial record serial number and model combination are used to identify the primary meter and the appropriate serial number prefix, suffix or increment is detected and used for synchronization of simulated meters.  Fields are left blank for any meters which are not specified and used by the OMD application.

Map accounts by name
With this option checked, accounts with like names to those in Central will be automatically mapped and selected for synchronization.  Accounts which are not mapped, are referred to as OMD Orphan accounts.  These accounts may be manually mapped via the OMD Orphans page.  In the case where an audit is performed on an end-users WAN (Wide Area Network) therefore containing results from multiple branch offices, and the associated OMD accounts are split, multiple OMD accounts may be combined and mapped to a single Central account.  The account names are separated with a semi-colon ";".

Map accounts by EquipID's and S/N's
With this option selected, OMD accounts; even with different names, are automatically mapped to the appropriate Central accounts.  Devices are auto-mapped based on a Serial Number or Equipment ID.  These devices may be manually mapped or edited via the ERP Equip ID column located on the Device Management Views page.

Create accounts using OMD orphans
With this option selected, a Central account will be created automatically for each OMD orphan account, based on the information extracted from OMD.  To individually select which OMD accounts to create in Central, deselect this option and refer to the OMD Orphans page.

Managed Devices
Devices which are automatically mapped via a Serial Number or Equipment ID are flagged in Central as Managed Devices, unless this option is set to Manual.

Push and Pull Frequencies
Separate push and pull frequencies may be configured as appropriate, i.e. Pull new accounts and devices from OMD every 1 week, and Push meters from Central every 1 day.  These settings apply to all child accounts.  Each push will submit the updated meters since the last interval, i.e. previous day.

We recommend overriding the global Push frequency, and Push the meters on a per-account basis 1 day before the meters are due for billing.  Refer to the Account Settings page for more information.

Send results via email
With this option checked, a summary email will be sent to the selected contact upon completion of a push or pull from OMD NetVision.

Following are some of the explanations of the messages returned by NetVision:

Meter Code not found for label: COLOR METER; it's a B/W device and therefore has no Color Meter

Meter Code not found for label: TOTAL METER; it's a color device but only B/W and Color Meters are configured in OMD, not a Total Meter

No Cycle Model; device is not defined in OMD under a contract, however it may exist in OMD because it's billed hourly for service

No Model/Serial Number; the device may be part of a new order (or reassigned/repurposed device) which is delivered and installed, but it may be several days or longer before the device is added to a contract in OMD

The date is less then the last meter date 02/05/08; a meter from a previous date cannot overwrite a manually entered meter with a newer date