Microsoft Access Development

While at Abbott, I built two databases. The first one was another version of a Training Project Management Database that tracked all aspects of the training development process. It introduced the concept of course numbering, and would display the last course code utilized so you know what the next number would be.

The second database was much more complicated as it required the creation of cross tabs in order to create a training matrix. This matrix would display the Manager's name and role with a listing of roles that reported to the manager, along with the required training for each role. This was then exported as a PDF to a Document Management System for storage.

It also tracked the Job Descriptions for each role, which were also exported as a PDF to the Document Management System.

Accenture brought me in to a very big insurance company in my area to build and manage the metrics and reporting for an enterprise-wide eSignature initiative. I created a single reporting database for each business unit to isolate the reporting metrics from each other. It automatically brought in the data from the eSignature vendor, performed several (15 stored procedures) 'cleansing' routines that made the data useful from a metrics perspective.

An additional "Program Level" database was also created that was linked to all of the business unit database that provided overall metrics from a program perspective. Once the system was put into place, it was turned over to an administrative assistant and I was released.

At Clipper, Windpower, I created a multi-user, networked, development tracking system to track all aspects of the development of training and documentation. This includes developer notes, objectives, tasks, course outline, all Analysis results (task, risk, audience, etc.) and reviewer comments and actions.

I also created a student tracking front end system that linked to a MySQL backend in an LMS. It was read only, and primarily used to create professional student transcripts.

Iconma was my first real job as an Access Architect. I was contracted out by a large health insurance company out of Southfield, Michigan, to develop a small budgeting database to automate their semi-annual budgeting cycles. I was onsite for the first week, conducting interviews and providing quick layout demo's that I would build during the evenings, then I completed the work back at home using VPN. This database included User-level access and logging, importing, and exporting.

Just before that project was completed, I was asked to create another database to support the Accounts Receivable department in their collections of closed accounts. I was again onsite for the first week, then came back at the end of this project to demonstrate it to their Leadership team. This one went through a few major changes as personnel changed and thus, requirements changed with them.

A few months after finishing that one, I was asked once again to modify an existing system used by Accounts Payable (payroll), and utilized tables and reports. I was required to update this one to include non-budgeted position tracking, and it needed to be linked to the first database that I had built. This one would provide the initial updates to the first one, just before a new budget cycle would begin to ensure it had the most recent personnel changes. Once again, I flew in for the first week to conduct the interviews, then completed the work from home.

At TekSystems, I developed two systems that import employee data from various sources, compiles the data, then exports them to CSV files that are imported into the HRMS. They are used when a catastrophe occurs and the company needs to add as many as 600 temporary employees into the system. The database reduced the activation time of the catastrophe centers from 48 hours to 30 minutes. 

I then developed a system for tracking the various team efforts in the implementation of a new Unified Communication system to over 40,000 endpoints. It integrated the efforts of 8 teams, each using their own Excel tracking system, and eliminated confusion by using standard terms, locking specific fields, and restricting access to only authorized users. This system reduced the amount of communication involved between teams by 80% and reduced the weekly status meeting from 2 hours to 30 minutes.

Next, I developed a deliverable tracking system that tracks hundreds of attributes for training and documentation, including the relationships between deliverables, the website pages they are accessed from, and all published locations. For example, a user guide might be referenced by job aids and training courses. It might also be published in one physical location, but accessible from multiple web pages.
I also created a development tracking system to track all aspects of the development of training and documentation. This includes developer notes, objectives, course outline, Course Plan, Course Request forms, and reviewer comments and actions.

 At Ciber, I created a development tracking system to track all aspects of the development of training, documentation, communications, and organizational change procedures. This included developer notes, objectives, course outline, Course Plan, Communication Strategy, Organizational Change Strategy, and reviewer comments and actions.