Home > Case Studies > Luminaire IMS Application
Luminaire IMS
Orders
Luminaire Lighting Corporation is an Edison NJ based company which markets vandal resistant lighting fixtures. At the time when discussions regarding our involvement in a project were initiated, Luminaire utilized an internally developed Inventory System (IMS) as a key component in a suite of applications that were used to manage its supply chain and production.

The original IMS is built upon Ashton Tate’s Dbase platform and has provided over 20 years of service. The program still functioned well overall, but management wanted to enhance the system, and it didn't make sense to invest in a DOS based technology at that point in time. The main shortcoming of the original IMS is that Order Tracking was not tied to Inventory Management in any way. Another shortcoming is that the original system has a limitation of 9999 records due to design tradeoffs made when the system was first implemented.

During discussions between Luminaire's President Ron Lipson, and Impact Informatics principal consultant, Dave Brown, a new IMS was envisioned which would provide a number of benefits including:
  • Tying Order Tracking to Inventory Management will both enhance operating efficiency and give management a sharper tool for decision support activities as compared to the current IMS.
  • In the current system, the operator has to reserve parts on a fixture-by-fixture basis while looking at a print out of an order. The new system will allow all reservations for each of an order’s fixtures to occur when an order is booked. This will be much faster and more accurate then the current system.
  • Having instant knowledge of how the current inventory is to be allocated across customer orders should better enable management to meet strategic goals. For instance a potentially big first-time customer could be accommodated rather then a long-time customer whose need is not critical in the event that both have an order for the same fixtures, and there are not enough parts on hand to cover both orders.
  • The ability to store information on more then 9999 parts or fixtures at a given time will give management a better historical view of fixture/parts movement.
  • All of the search functions in the current IMS require that the user type in the exact part or fixture name to match against. Novice users are not particularly good at this and often need to make several attempts. The new system will utilize SQL’s wildcard operator which will enable a “begins with” style of search. Users will be able to type in the first few characters of the part they are searching for and pick the exact part they’re interested in from the ensuing list of parts.
Parts
  • The new system will implement searching on combined criteria as well. For instance, users should be able to ask for orders shipped between two dates, belonging to a given sales rep. This type of search is not available in the current IMS
After Impact was engaged, about a week was spent gathering an understanding of the original IMS, and conceptualizing how the new system would both deliver all of the old systems functionality, and the desired benefits brought out in the envisioning phase of the project. The deliverables of this phase of the project were both a data dictionary, and a database diagram. The former lists each table in the system, along with that table's role in the system, along with each table's columns. Each column in this document carries both a data type, and a business definition which in turn explains that column's role and meaning in the application. The latter was implemented in SQL Server 2005, and also served to create the system tables. The design represented by this diagram had 24 tables. 3 more were added later in the development process in response to new requirements.

During the development phase of the project, we maintained a test site on the internet. This approach enabled a RAD style of development where small pieces of the project are uploaded at short intervals for testing and feedback. The approach ensured that Luminaire personnel were involved in the design process and that their feedback was incorporated into the design in the early stages. As the project progressed, Ron Lipson. Luminaire's president felt comfortable enough with the progress shown to allow the scope of the project to increase. Most notably, much time was spent developing custom controls, including select and combo controls both of which utilize a fully incremental search.

Production version 1 of the new Luminaire IMS was rolled out on 2/12/2010. The system is comprised of 27 tables, and 128 stored procedures on the database side. The .Net based application is comprised of 41 different .aspx pages, along with a number of shared modules. There are over 40,000 lines of code, counting stored procs, .Net, and javascript code. From production rollout, to the date of this writing, only 6 bugs have been discovered. This represents a defect rate of only .15/KLOC (1000 lines of code), well under the industry average according to this post: StackOverflow.com Article