OpenNet File Management System Offers Enhanced Data Mapping, Data Plugging

OpenNet File Management System's fall 2003 release brought enhancements to the data-mapping and data-plugging features. Schools may want to consider these features as a way to keep their loan-processing file formats current.

Data Mapping
Data mapping converts one version of a file to another file version. For example, with data mapping, CommonLine 96 converts to CommonLine Release 5, or a proprietary format can convert to the latest CommonLine format.

Data mapping is implemented on a broad basis to ensure file systems are compatible.

What changed in the fall 2003 release
OpenNet File Management System now maps CommonLine 4 disbursement rosters to CommonLine 5 disbursement roster format.

Example:

1. A lender creates a CommonLine 4 Disbursement Roster file for a school.
2. The lender sends the file to OpenNet File Management System.
3. OpenNet moves the file to the OpenNet File Management System engine for processing.
4. OpenNet File Management System maps the CommonLine 4 file to a CommonLine 5 file.
5. OpenNet File Management System routes the CommonLine 5 file to the school.

Data Plugging
Data plugging adds data to a file or changes data within a file to make the file compliant with the common file system. For example, specific data that was not collected by a lender or financial-aid-management system may be added to the incoming file format.

Unlike data mapping, data plugging is implemented on a case by case basis at the request of the customer.

What changed in the fall 2003 release
Users now can view in OpenNet File Management System the data at each stage, both before and after plugging. The "File Summary" screen shows both the transmitted data in an "original file" section and the converted data in a "mapped original file" section. This lessens confusion for users because they can see exactly what data changed in the plugging process.

Example:

1. A lender creates an electronic file containing loan records for a school. The file contains a lender-specific code tracking code.
2. The lender sends the file to OpenNet File Management System.
3. OpenNet plugs the lender-specific data into the common file format.
4. OpenNet moves the file to the OpenNet File Management System engine for processing.
5. OpenNet File Management System prepares a response file for the lender by converting the common response file to the lender-specific format.
6. OpenNet File Management System routes the file to the lender.

To learn if data mapping and data plugging are right for your school's loan processing systems, contact your USA Funds^® Services account executive.