Aviation Logistics Management Information System Portal: Project: LCDR Daniel P. Taylor ALMIS

ACMS data ACMS apps Aircraft Computerized Maintenance System (ACMS) is used to manage aircraft maintenance and configuration. The application and the database are at ARSC. The users are spread out among 25 Air Stations, ARSC, and HQ.

ACMS data ACMS apps character interface Data gets into ACMS through a data entry person. Data is transferred from a person to one or more paper forms, and input by a data entry person using a character-based application.

ACMS data ACMS apps limited printers character interface character- based paper reports Reports from ACMS are limited to “canned” character-based reports that can be printed only on certain designated printers.

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information Most units have their own standalone systems into which they feed some the same data that is input into ACMS …

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information … or into which they re-key data from reports generated from ACMS.

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information The Aviation Maintenance Management Information System (AMMIS) is used to manage aircraft supply, inventory, accounting, finance, procurement, depot maintenance, and flight operations. Until Summer 2000, there had been no system interfaces between AMMIS and ACMS

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information There were some interfaces, like the NMC report run from ACMS, then re-keyed into AMMIS for the Abstract of Ops report

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information Do I have the parts I need for the mx coming due? Most of the integration between the two systems happened by people correlating reports from both systems.

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information How many times do I need to input flight time? And there was plenty of redundancy and inconsistency in the two systems from the same data being put into both systems.

So what’s wrong with this picture?

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information X Needed to build interfaces between the two systems and stop running reports from one and then re-entering into the other.

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information X X Needed to eliminate the non value-added data entry where possible and get data straight from the person who has it into the computer.

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information X X Needed to eliminate the redundant data entry.

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information Needed to capture some of the information that hadn’t been captured, like discrepancy and corrective action for unscheduled maintenance.

ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information XX X X Needed to make it easier to get information out of both systems – Right information, right place, right time, right format.

X X ACMS data ACMS apps limited printers character interface character- based paper reports local applications charts, MOEs, information AMMIS data AMMIS apps limited printers character interface character- based paper reports local applications charts, MOEs, information X X Needed to eliminate the multiple data entry into standalone systems created by units because there had been no way to get out much of what had been put in.

What have we done about it?

ALMIS data (AMMIS, ACMS, EAL) AMMIS, ACMS apps Transitioned to a unified architecture with a single physical database and legacy applications on a single machine.

ALMIS data (AMMIS, ACMS, EAL) AMMIS, ACMS apps limited printers character interface character- based paper reports Legacy applications remain. Much of AMMIS will remain, legacy ACMS interface will be gradually replaced by Electronic Aircraft Logbook.

ALMIS data (AMMIS, ACMS, EAL) AMMIS, ACMS apps limited printers character interface character- based paper reports browser apps (EAL, DSS) New, browser based EAL and Decision Support System will use same single database architecture accessed through the ALMIS Portal.

ALMIS data (AMMIS, ACMS, EAL) AMMIS, ACMS apps limited printers character interface character- based paper reports browser apps (EAL, DSS) browser interface: on screen one click charts, MOEs, information EAL interface will be easy enough for user to input logbook data. DSS will provide on screen access to information using OLAP, reporting, ad hoc tools.

ALMIS data (AMMIS, ACMS, EAL) AMMIS, ACMS apps limited printers character interface character- based paper reports browser apps (EAL, DSS) any printer browser interface: on screen one click charts, MOEs, information rich, formatted, schedulable, exportable reports, charts, MOEs, information Browser based system allows for printing to any printer. Reports can be scheduled, exported to MS Excel, ed, or printed.

ALMIS data (AMMIS, ACMS, EAL) AMMIS, ACMS apps limited printers character interface character- based paper reports browser apps (EAL, DSS) any printer browser interface: on screen one click charts, MOEs, information rich, formatted, schedulable, exportable reports, charts, MOEs, information Data can be exported to MS Excel or to CSV format for direct input into or linkage with unit- developed applications, without the non value added data re-keying. local applications charts, MOEs, information

ALMIS data (AMMIS, ACMS, EAL) AMMIS, ACMS apps limited printers character interface character- based paper reports local applications browser apps (EAL, DSS) any printer browser interface: on screen one click charts, MOEs, information rich, formatted, schedulable, exportable reports, charts, MOEs, information charts, MOEs, information