Lubrication Point Manager - Mobile App

Please read the requirements thoroughly - we ask for a number of recommendations in the attached PDF. The purpose of this project is to create a mobile application to provide users with ability to view and edit lubrication point information in a very user-friendly and interactive manner using a mobile app running on iOS. What we’re looking for is a clean, neat modern display of the data described below. In this database we start with assets or installations. An example of an asset/installation type would be a Factory, Ship or Oil Rig. Each asset belongs to an asset type and has it’s own name. Put simply, an asset/installation is anything that has a number of machines that require some form of lubrication. Each asset type would be linked to it’s own image or if undefined it would use a generic image. The developer will be provided with these images and icons. An asset is divided into sections. In a factory a section could be “cooling” for example, or “compressors”. On an oil rig a section could be “air compressors” for example. Each section would be linked to it’s own image or if undefined it would use a generic image. The developer will be provided with these images and icons. A section is then divided into Machines. For example, “Air Compressor”. Once again each machine would be linked to it’s own image or if undefined it would use a generic image. The developer will be provided with these images and icons. A machine is then finally divided into components. For example an air compressor would consist of the engine (e.g. Caterpillar D-3516-B), a shaft with some bearings and the compressor. So the layout is pretty much contained in a tree structure. The mobile application should allow the user to easily and graphically navigate around this structure and duplicate/clone and part of the tree. It should be possible to edit anything in the tree. Once a specific component is selected it should be possible to edit information linked to that specific component. The following details need to be editable: Component identifier (Tag name) Manufacturer (drawn from pre-defined drop-downs) Model (drawn from pre-defined drop-downs) Application (drawn from pre-defined drop-downs) Serial number Current lubricant Future lubricant (drawn from pre-defined drop-downs) Units of measure Quantity of lubricant (pre-populated from lookup table but can be verified and/or altered) Continuity quantity of lubricant (pre-populated from lookup table but can be verified and/or altered) The edits should write the data back to a MSSQL 2012 database