Recent Work

• Radius server instance on an Linux/Ubuntu
• CloudTrax network integration
• PHP/MySQL Laravel (dev, staging, production) running on Git branches  utilizing artisan database migrations
• MailChimp API integration

• Client relations
• Store and retrieve data for the accreditation
• Backend Admin and Reporting
• PDF Generation
  
• Digital Signatures
• User\Permissions Matrix

CALEA Information Management & Reporting System (CIMRS) for the Commission on Accreditation for Law Enforcement Agencies, Inc. (CALEA). CIMRS enables CALEA and its clients to store and retrieve data for the accreditation process of four types of programs: 1) Law Enforcement, 2) Campus Security, 3) Training Academy, 4) Communications. Each program is versioned and can potential change from year to year. The project has been successfully completed and is now in a maintenance contract to address any issues or add small new features.

CIMRS has a client relations component that allows certain credentialed users to receive email notifications when data is ready for review. Once reviewed, the client could then enter feedback that would be stored and become part of the accreditation process

CIMRS has a considerable backend administration section. The primary functions are client and user admin, and accreditation program admin. The user admin allows you to assign roles and clients to users. The accreditation admin enables you to create new accreditation programs and versions. There is also an import tool for CSV files that contain program data into CIMRS.  

CIMRS generates numerous PDF reports crucial to the accreditation process. These reports contain compiled statistics as well as pie charts generated from Charts.js. CIMRS also contains a digital signature system.  

Update to the MarketLink Brokerage System (MBS).

• QuickBooks accounting integration
• CodeIgniter framework and Propel ORM migration
• Custom Broker\buyer marketplace
  

The MBS was a major overhaul of an existing CRM system and added many features. Major revisions to the db structure for new features and performance. Large code refactor for CodeIgniter framework and Propel ORM migration.

The MBS system consisted of a custom CRM that allowed clients (farmers) to communicate with brokers who buy their grains. Clients could also track their shipments from associated carriers. The CRM portion consisted of many common client and sales tracking features.

MBS consisted of four main parts: (1) client functionality, (2) broker functionality, (3) carrier functionality, (4) QuickBooks accounting integration. The legacy system had a basic model and authentication system for clients and brokers but this was greatly enhanced and integrated with the new carrier and accounting pieces.

MBS client functions allow an authorized user/farmer to search for brokers to sell their grains to. Clients can also communicate with the brokers and would receive email reminders about new pricing and other news. After selling their grains clients could then search and communicate with carriers who would ship their grains to their destination. Tracking of shipments was also available.

MBS broker functions allow an authorized user/grain broker to post prices and quantities of grains they were looking to buy. Brokers entered their geographical data in to MBS, which allowed clients and brokers to use proximity to decrease shipping costs and prevent spoilage. Brokers can also communicate with clients and carriers.

MBS carrier functionality allow an authorized user/grain shipper to post prices for grain shipments by weight and distance from clients to brokers. Carrier prices are perishable and changed due to the variable price of fuel. Carriers can also communicate with brokers and clients about shipping rates and statuses.

MBS Quickbooks integration allow MBS invoices to by imported into Quickbooks once certain criteria were meet. Both client and carrier invoices were included in the sync. Quickbooks would also update the invoices in MBS once they were marked as paid.