<< Back to Portfolio

The Program Information Management System built for B/E Aerospace, known commonly as ProView, grew out of a need to manage documentation requirements for the delivery of product.  A given program is associated with a significant list of time-sensitive documentation that must be provided in a timely fashion in order to meet customer delivery timeline expectations.

The system does well to handle the basic functionality of Primavera system integration to keep program definitions current and to allow for engineers and others to provide documents against defined requests but the real value in the system to the department is management of performance thresholds to keep an eye on continuous improvement.

Prior to the implementation of a system that both identified requirements within the context of related programs and also captured activity transactions for every step in the process it was an extremely arduous task to identify program delivery risk, or for that matter, even late requirement submissions.  It is now as simple as either running an interactive search or executing a canned report to evaluate trends and to highlight areas needing attention.

Much of the value of the Data Submittals portion of ProView is the real time view of metrics of interest, as depicted in this dashboard.




...that said, the ease-of-use focus was relentless and simple but powerful search and export features were the eventual result.

Once the Data Submittals module was implemented the system grew into several additional modules, including

  • AC21-49 (an electrical documentation compliance standard),
  • Schedule (a simple tool to assist program managers in maintaining dates on the Primavera program schedule),
  • Sales Order Management (standardized sales order change request management for program managers), 
  • Waterfalls (spreadsheet-based sales order status reconciliation and reporting) and 
  • Flammability (flammability engineer workflow management).



The AC21-49 module is concerned with managing the workflow and related documents around EMCD and EMNOC data between internal and external application users.  User interface for search and detail records were kept common to minimize the need to train.



A simple click on a submittal to see its full history was once a hopeful search through the file system coupled with intimate knowledge of the process.

The Sales Order module functions more as a complicated change management workflow system with an interface to replicate in live changes from related enterprise systems.  Because of its underlying data replication feature several screens focus on metrics-related data analysis more so than the change request functionality for which it was originally built.  Still, its core purpose and value add remains the ability for sales order administrators to manage change requests accurately and efficiently as required by program managers.


The Schedule module was designed as a user friendly interface to the Primavera program management application.  Current data can be displayed and conditionally managed by program managers directly through these ProView application screens.  The actual data manipulation must, of course, occur with a communication to the underlying Primavera system which is done through secure use of the application's web services interface layer.

Managing data in a variety of spreadsheet formats and reconciling the contents of each with an ERP system is a task that causes sadness for many.  The time required and the individual attention to detail required to perform such a task reliably led to this additional ProView module.  It allows for the definition of a variety of spreadsheet input/output formats to be created and then automatically manages the reconciliation of the spreadsheet data contents according to a proprietary workflow.  While this is not a system that could easily be applied to any given situation it is the sort of system that could be built to meet the needs of many other semi-structured data reconciliation processes.