Getting up and running with RepairData requires knowledge of the
organizational structure, culture, and the short and long-term goals
for the enterprise. A thorough analysis of current business processes
is critical and development of some new processes may be necessary.
Having detailed timelines and milestones will keep everyone focused
and informed on progress of past, current, and upcoming tasks.
Technically, data capture plans; analysis of existing data, and
data cleansing are required before data is input into the new system.
Coordination with various internal departments, external
agencies, suppliers, OEMs, support contractors, and customers will
ensure that the implementation occurs smoothly and effectively.
Identifying the expectations (realistic and unrealistic) of all
users of the data is important to overcome the natural anxieties
associated with new systems and change. There is a natural learning
curve associated with a new information system. Training and experience
is the time proven method of getting beyond the curve.
RepairData has the experienced staff to assist your organization
with the implementation process. The lessons learned from the
implementation of the RepairData products with other Army programs
over the past 14 years can be applied to make your transition easier,
cost effective, and more efficient.
Below are just some of the key implementation tasks that
RepairData can assist your organization in performing:
1. Analyze business processes in place for the primary
users (OEMs, Vendors, Organic Depots, Organic support, and all
program support entities) and do a cross walk of RepairData products
to be used. The analysis includes Maintenance process analysis,
Supply Chain Management process analysis, Configuration Management
analysis, Modification Tracking Process analysis, System Administration
Management, and Automatic Identification Technology (AIT) uses and
processes. A ?concept of operation? briefing that includes timelines
and milestones for implementation is usually the end result of this task.
2. Establish policies or guidelines (data collection, supply
processes, etc.) pertaining to the use of RepairData products in support
of all programs. The business process analysis typically yield the need
to revise or define new guidance for: Data Collection Requirements;
Supply Chain Management processes; Requisition processing procedures
and priorities; Warehouse procedures and inventory requirements;
users responsibilities and data entry requirements; and the System
Administrative Management processes for access requests, access approvals,
user roles, and levels of access.
3. Analyze existing data for usability, prepare usable data
for initial upload, fill ?data gaps?, set legitimate code table fields
(dropdowns, codes, tables, presets) and upload initial data. This process
may need to be repeated for all sites or entities that will input existing
data. Each item number (same as part number) needs to be reviewed to
determine characteristics such as serialized, repairable, configuration
tracked, visibility tracked, system code, stockage levels, re-order
points, part category, warrantee items, kit items, UID items, level
of repair, and primary and secondary repair locations. For items that
are configuration tracked, a design template or tree will be created
to input initial ?as built? and ?as maintained? data. Defining and
adding all the entities or ?contacts? is also an important initial
data input task. All items in RepairData?s relational database require
both an item number and a CAGE code. Each CAGE code for items in
inventory will need to be added to the contact list along with all
warehouses, repair facilities, DODAACs and/or UICs.
4. Coordination with LOGSA may be needed to use the Standard
Army Retail Supply System (SARSS) to interface with your contractor
managed supply system. This usually requires the establishment of a
Memorandum of Agreement between the Program Management Office (PMO)
and LOGSA. Additionally, a non-standard parts catalog in the SARSS
148 character/codes and format must be created and submitted LOGSA
(this will be updated monthly thereafter). Coordination with DAASC
will provide the MILSTRIP/requisition data transfer to the RepairEDI
supply module. An agreement needs to be established between the PMO
and DAASC that specifies requisitions received with the specified
Routing Identifier Code (RIC) will pass electronically to and from
5. Training all personnel that will use the database cannot
be under emphasized. Scheduling and conducting initial and sustainment
training in a timely manner will ensure user acceptance and minimize
frustration and confusion associated with change. RepairData has
developed a Program of Instruction (POI), based on practical exercises
and supplemental training materials geared towards introducing users
to basic program functionality and beyond.