Full stack developer & CTO

Ignite is a truly efficient and multi purpose internal application. It starts with Okta built in authentication connected to Active Directory and the NetSuite ERP system. Utilizing Okta for 2FA and NetSuite for roles and employee information, it is used for multi subsidiary login and separation of data. Ignite is comprised of several microservices to make employees day to day tasks easier. Each microservice is tied into the user roles to control access and features available. These microservices include:

1. Campfire. A social platform for posting company wide messages and attachments. Pulls in latest blog posts from company websites via the API and also includes features to display Instagram posts via the Instagram API.

2. Product E-Catalog. A VCDB & BCI (Vehicle Data) lookup tool that allows employees and external resources to look up available products, based on several applications, using the custom built API. Once an application vehicle is selected, the results are then pulled via the API using a database that is synced in real-time with the NetSuite ERP system. The catalog can also be set to iframe mode, via a query string, to allow external resources and sites to embed the catalog in any website. The catalog features a very simple to use data import form. Supply Chain simply uploads the latest VCDB/BCI file, in the provided excel format, and the API will process the individual worksheets, over 250,000 rows of data, and update the catalog database for all internal and external applications using the API or embedded iframe.

3. Point Of Sale. Ignite has a full featured point of sale system which was developed to make over the counter sales incredibly efficient as opposed to entering all data directly into the ERP system. The average sale was taking anywhere from 5 to10 minutes to complete due to amount of forms required in the ERP system. Ignite consolidates this to one form that quickly provides a receipt to get the customer out the door, while in the background handling all form creation and inventory requirements automatically in NetSuite reducing the workload for the branches. The POS system provides an easy to read dashboard to break down the days transactions and provides quick access to NetSuite to fix any inventory errors that require manual adjustments. The POS system also respects all custom pricing set in NetSuite and allows quick customer creation for new transactions. PDF receipts are dynamically created and the ability to email receipts is available to save paper.

4. Files & Forms. Multi purpose area used for route truck drivers to complete various forms in a mobile friendly application. Also used for internal forms for employees. Some examples are marketing requests and trade show requests. Some forms are powered via Hubspot to allow marketing the control over editing, updating the fields directly in Hubspot, and for tracking and statistics.

5. Reporting. This area allows for custom searches and reports in NetSuite to be shared in the application to be viewed and exported to CSV. Since these are pulled via the API the reports always contain the latest data.

6. Support. This page embeds YouTube and Microsoft Stream videos with tutorials on how to use Ignite. This also includes a quick support request button to quickly and easily report a bug or feature request.

7. Admin Settings. The admin settings features a heads up view of the API connectivity and Quasar upgrade status. If API connectivity fails, the application will trigger an offline mode to make sure no POS transactions are lost. Once connectivity is restored, the data will be nudged to resend to the API. It also features two tabs with additional settings. The general tab allows you to change subsidiaries to trigger changes in the app based on the subsidiary chosen. It also features a complete user selector. The user selector allows you to login as any user on this list for troubleshooting and to get a full view into the users access and role selection. It is very helpful for when you need to make sure you are looking at the same screens a user is seeing. Some additional cache clearing can be triggered as well to reset the Redis cache. The second tab controls internal or third-party API keys. You may create new API keys that may interact with Ignites API, copy existing keys, or mark keys inactive.