Executive
Summary
This project is for a
client company Northrop Grumman Corporation (NGC), and specifically for a
division site located at Hill AFB, UT. Northrop Grumman is an aerospace
engineering defense contractor with major military programs such as the F-35 Lightning
II Joint Strike Fighter, the B-2 Spirit stealth bomber, and the Minuteman III
Intercontinental Ballistic Missile (ICBM).
NGC’s Hill AFB site
manages operations for ICBM-related activities at seven main locations
throughout the nation. These locations include engineering offices, testing sites,
and military grounds.
This particular division
of NGC wanted improve the visibility of receiving shipments of orders / purchases. NGC purchases that are shipped to the sites
have a lot of variation; they can be highly technical, expensive pieces of
equipment ordered by engineers, or they can be low-cost commodity items such as
printer cartridges ordered by facilities management.
Currently employees at
the different sites use a clipboard and paper records to track expected
incoming shipments and whether shipments arrive or are lost in transit.
Information such as delivery courier, tracking number, sender, receiver, dates,
location, receiving personnel are recorded for accountability and tracking.
The sponsor of the
project wanted a centralized repository for this information, rather than
multiple documents for each company site, so that there’s better tracking of
whether their expected shipments are actually arriving.
The solution that I
created is an Excel document to be used with a user form interface to be used
as a shipment receiving log. This log sheet also is able to, with the click of
a button, launch the courier’s tracking website to check the status of the
shipment. This file can be posted on NGC’s SharePoint drive, so that purchasers
can input their purchases and warehouse receiving personnel can expect and
track the shipments’ arrival.
This unification of
information is critical for the division because they have had a history of delayed
shipments, lost-in-transit shipments, and instances where the sender claimed to
send the product but did not and NGC was charged for the purchase. Because
there has not been a singular communication channel, these cases existed.
http://files.gove.net/shares/files/15w/jmur2000/Receiving_Logbook.xlsm
No comments:
Post a Comment