Data validator aids property book conversion.
Development of the Data Validator started in 2000, when LOGSA began working with the Program Manager for the Global Combat Support System--Army (PM GCSS-Army), the Army Combined Arms Support Command (CASCOM), and TRW, Inc. (now Northrop Grumman Electronic Systems), to develop a Web-based property book for the Army. After initial testing and fielding, the system was modified to include Unit Level Logistics System--S4 users. LOGSA currently is working with the PM for Logistics Information Systems, CASCOM, and Northrup Grumman to test software that will convert Defense Property Accounting System users to PBUSE.
Fielding of PBUSE across the Army is a critical support mission performed by LOGSA for the PM GCSS-Army. LOGSA has participated in many system acceptance tests to ensure that functional requirements for data quality, edits, and interfaces to LOGSA systems are accurate and functioning as intended. LOGSA also has partnered with CASCOM on several system deployments to Active Army, Army National Guard, and Army Reserve units in and outside of the continental United States.
The Web-based PBUSE enhances the way today's Army does business. PBUSE not only improves property accountability and data integrity but also eliminates the need for Continuing Balance System-Expanded (CBS--X) reporting and Unique Item Tracking (UIT) system reconciliations. PBUSE fully supports serial number tracking, mobility planning, and national-level redistribution. Here's bow it works.
Before converting to PBUSE, a PBO first must validate critical data in his unit's property book, such as line item numbers, serial numbers, and registration members. To speed up identification and correction of data errors before beginning the conversion process, he accesses the PBUSE Data Validator, on the Web at http://weblog.army.mil.
The PBO then uploads the SPBS-R Property Book Master File, and, as part of the preconversion process, the PBUSE Data Validator systematically identifies discrepancies in UIT, the Army Maintenance Management System Equipment Database, the Readiness Integrated Database, and asset balances.
The PBO must correct discrepancies identified by the PBUSE Data Validator before the unit's data can migrate into the Logistics Integrated Data Base (LIDB) and PBUSE production tables. Until all data integrity issues are resolved, migrating unit identification codes are placed in a "hold" table within LIDB and changes to the unit's authorization and asset posture are not processed. The Data Validator prevents the incorrect identification of assets, which can adversely affect UIT reporting, national-level asset visibility, and the accuracy of chief financial officers' reports. The Data Validator also helps prevent redistribution problems that can occur if assets are identified incorrectly as excess to national-level decisionmakers. Most importantly, it helps ensure that incorrect asset locations registered within the LIDB will not generate reports of shortages that could be passed on to the National Inventory Control Point Class VII Major Item Requisition Validation file. If such shortages are reported, valid requisitions for class VII (major end items) may be rejected, thus lowering unit readiness.
More than 3,000 unit identification codes have been converted from SPBS-R to PBUSE. Feedback from PBOs using LOGSA's Data Validator tool when converting from SPBS--R to PBUSE has been extremely positive. Web-based PBUSE will be fielded in all Active Army, Army National Guard, and Army Reserve units by 30 September 2006.
For more information about the PBUSE Data Validator, contact LOGSA at email@example.com or call (256) 955-7716 or DSN 645-7716.
MARSETTA BEARDEN IS A LOGISTICS MANAGEMENT SPECIALIST IN THE ASSET MANAGEMENT DIVISION OF THE LOGISTICS INFORMATION CENTER AT THE ARMY MATERIEL COMMAND LOGISTICS SUPPORT ACTIVITY AT REDSTONE ARSENAL, ALABAMA. SHE HAS A BACHELOR'S DEGREE IN BUSINESS ADMINISTRATION FROM ALABAMA A&M UNIVERSITY.