 |
Major Projects |
|
|
| Project Name |
Start Year |
Duration |
| SAP Implementation Service Organization |
2007 |
30 months |
| Objective |
Team |
| Move the service organization for USA and Canada from legacy systems to SAP. |
SAP team of IT, consultants and functional users. |
| My Role |
Result |
Project manager
My areas of responsibility are for PP/MM modules,
ABAP development manager for internal resources,
security and liaison with our outsourcer for
Basis support. Also did configuration as needed.
Project is utilizing Solution Manager for project
documentation.
Initially used a third party warehouse as our
distribution center for which I set up the SAP
XI system as interface for transactions between
SAP and third party. Later the warehouse was
brought in house and I installed third party
software to interface between SAP and FedEx
Ship Manager server.
|
Went live July 2009.
Key issue(s): Managing multiple projects and
roles at the same time, integration issues with
CRM, and compressed time schedule for reconditioning
business project.
|
|
|
|
| Project Name |
Start Year |
Duration |
| SAP Implementation Bethlehem Plant |
2006 |
12 |
| Objective |
Team |
| Convert Bethlehem product reconditioning
plant from Oracle to SAP ERP system. |
SAP team of IT, consultants and functional users. |
| My Role |
Result |
| Project manager
Project manager
My areas of responsibility are for PP/MM modules,
ABAP development manager for internal resources,
security and liaison with our outsourcer for
Basis support. Also did configuration as needed.
|
Completed with go live of January 2008.
Key issue(s): Managing multiple projects and
roles at the same time (also involved in start
of Service Organization move to SAP), compressed
time schedule for reconditioning business project
while they also tried to manage urgent business
issues.
|
|
| Project Name |
Start Year |
Duration |
| SAP Implementation Durham Mfg |
2004 |
14 months |
| Objective |
Team |
| Convert from Oracle Applications
to SAP utilizing configuration from German parent
company. [SD, MM, PP, FICO, QM] |
SAP team of IT and functional users. |
| My Role |
Result |
| Project manager
My areas of responsibility are for PP/MM/WM/SD modules, ABAP development, security and liaison with our outsourcer for Basis support.
Also did configuration and some light ABAP programming. |
Went live January 2, 2006.
Key issue(s): Initial issue in starting the project
was gaining support from the business to
provide full time functional business team members
to the team. Functional team member time allocation
increased and the functional team members took ownership of their roles in the project which contributed greatly to the successful implementation. |
|
|
|
| Project Name |
Start Year |
Duration |
| Web Site Upgrade/Redesign |
2003 |
5 months |
| Objective |
Team |
| Redesign and upgrade company public
web site |
One Sr. Analyst and myself. |
| My Role |
Result |
| Project manager, Analyst and programmer |
Changed the development language and architecture
of the web site to support dynamic content and
improved productivity for on going maintenance.
Key issue(s): My group had been trimmed to just
two people (from 4) with the work load same
as before. With our business relying on marketing
and selling product on the website, we needed
a way for fresh content to be readily implemented
in an efficient manner. We redesigned the site
and moved to Cold Fusion development environment.
This enabled us to provide marketing and sales
with interfaces to dynamically change text and
graphic content on their own. All course and
schedule information came from our SQL database.
This methodology was then extended to become
the basis for a redesign of our in-house course
scheduling system.
|
|
| Project Name |
Start Year |
Duration |
| Accounting System Upgrade |
2002 |
5 months |
| Objective |
Team |
| The business systems were supported
by a sister company. Management wanted to save
cost and improve productivity by bringing support
in house. |
One accountant and myself. |
| My Role |
Result |
| Project manager, DBA, System Analyst and programmer |
Project went live in two main phases of
AP then AR. Company now running on new system.
Key issue(s): Due to resource constraints I
was the only IT person working on the project.
Also, the accounting representative was part
of a layoff during the last phase of the project.
Due to budget issues I was only able to use
Epicor consulting for about 1/3 of the time
projected. Required me to quickly gain in depth
understanding of the system. |
|
| Project Name |
Start Year |
Duration |
| Enterprise Reporting - Sales |
2002 |
3 months |
| Objective |
Team |
| Develop Sales Management enterprise
reporting system to company president's specifications. |
Myself, Sr. Analyst, Sr. Programmer |
| My Role |
Result |
| Manager, System Analyst and programmer |
Sales opportunity forecasting and management
of the sales group was an issue for the company.
My team worked with the president to develop
and Salesforce.com type of in-house system to
collect sales opportunities and manage the stages.
We then developed a management reporting system
to combine sales opportunities from this system,
invoiced sales from an event management system
(technical training - public and private), and
sales from the internal project/consulting side
of the business. The reports where developed
using Microsoft SQL and Crystal Enterprise Reporting.
We also developed a web front end to deliver
the reports which contained features such as
security groups and individual assignment, folder
structure for report listing, entry of selection
parameters for reports to filter or sort by
requestor, and web management of the report
delivery system for ease of additions or changes
to the reports to be delivered. For a couple
of the more dynamic reports, a 'dashboard' version
was created so they could get real time updates
and trends for data such as public class sales.
Key issue(s): As with most management reporting
systems this one required multiple levels of
consolidation, different points of view and
as we developed it management changed their
requirements quite frequently. The key to the
success of the system was the database we built
and the process to populate the database. It
was able to keep up with the ever changing requirements
with very little changes to its structure.
Key issue(s): Due to resource constraints I
was the only IT person working on the project.
Also, the accounting representative was part
of a layoff during the last phase of the project.
Due to budget issues I was only able to use
Epicor consulting for about 1/3 of the time
projected. Required me to quickly gain in depth
understanding of the system. |
| Project Name |
Start Year |
Duration |
| Business System Support |
2001 |
3 months |
| Objective |
Team |
| The business systems were
supported by a sister company. Management
wanted to save cost and improve productivity
by bringing support in house. |
Four developers from the sister company. |
| My Role |
Result |
| Project manager for transfer of knowledge. |
Finished the project on time. Compiled
documentation of business systems and
my team assumed support.
Key issue(s): During the knowledge transfer
we were also rolling out a new design
of our public web site. |
|
| Project Name |
Start Year |
Duration |
| SAP Implementation |
1998 |
16 months |
| Objective |
Team |
Implement SAP (SD, IM,
PP, FI) for the Commercial Steering division.
Included integration of EDI (ASN, PO,
Releases, Invoice) and bar coding for
shipping process.
|
Team was comprised of two manager
level internal employees for each SAP
module implemented and an internal IT
team of two for data conversion. Consultant
team members for each module, ABAP programmers,
EDI consultant and training assistance.
My division team worked in conjunction
with another division's team for the first
8 months. |
| My Role |
Result |
| Project manager for my division. I
worked closely with the other division's
project manager and an overall corporate
group project manager.
I also designed the training methodology
and change management process for my division. |
Implemented SAP in division headquarters
and three plants at the same time.
Key issue(s): This project had many issues.
Some of the more critical included: Sponsor
and division manager both left company
soon after start of project. We were to
implement same configuration of SAP as
our sister division, which had a very
different business model. Time frame was
very short to implement SAP in two divisions
(multiple plants in each division). It
was implemented in time frame given, but
more issues had to be addressed at cut-over
The business environment was at an all
time high which made it hard to get full
time team members and users involved in
required project activities. |
|
| Project Name |
Start Year |
Duration |
| QS-9000 Certification |
1996 |
24 months |
| Objective |
Team |
| Attain QS-9000 certification
for division headquarters and each of the
three plants. |
Team was comprised of coordinators/managers
for each plant and a project team for
each location. Each location team was
6-10 members each. |
| My Role |
Result |
| Project manager for my division. In
addition to project manager duties I also
selected, modified, installed, trained
and maintained a Notes system to aid with
the QS-9000 documentation and process
requirements. Also wrote and updated policies
and procedures for the division, conducted
QS-9000 training, became certified quality
auditor. In conjunction with the site
project manager, managed actual audits
by independent auditors. |
Each facility passed the audit the
first time.
Key issue(s): One of our locations was
behind in activities to bring them in
compliance with the audit. The project
manager (who was also the quality manager)
resigned 2 months before the scheduled
audit. The other facilities passed the
audit first time on time and I was able
to get a 2 month extension and assumed
full management of this facility. We did
pass the audit. |
|
| Project Name |
Start Year |
Duration |
| Tiger Team |
1994 |
4 months |
| Objective |
Team |
| A plant was having some critical
systemic issues. The tiger team was to review,
analyze, recommend and implement necessary
changes. |
Team was comprised of 4 people from
areas of purchasing, engineering and IT. |
| My Role |
Result |
| I was a team member and handled areas
such as plant strategic plan organization
and communication, quality systems and
plant communication.
After the team was dissolved, I stayed
on with the plant to implement recommended
changes. |
This was probably the best team I
have ever had the privilege to be a member.
Through our efforts many systems were
changes, attitudes improved and customer
perception became more positive.
Key issue(s): Biggest hurdle was the
existing plant management. They were not
real excited about the "help"
of an outside team. We did finally win
them over and gained their cooperation
and input. We also served as "psychologist"
for many employees who were concerned
about many issues but did not feel anyone
would listen. |
|
| Project Name |
Start Year |
Duration |
| Preventive Maintenance System |
1994 |
6 months |
| Objective |
Team |
| Select new preventive maintenance
system to meet needs of three plants. |
Team was comprised of maintenance
managers from each plant. |
| My Role |
Result |
| First objective was to select a new
system to replace an outdated preventive
maintenance system. I directed the team
in compiling requirements, software selection
process, negotiation with software suppliers,
and creation of implementation plan. |
We were able to select a package which
met the needs of each location.
Key issue(s): No real issues in this
project. Everything went well and all
were happy with the selection. |
|
| Project Name |
Start Year |
Duration |
| Traceability System |
1993 |
6 months |
| Objective |
Team |
| Design and implementation
of traceability system for Steering Gears. |
Team was comprised of IT and plant
quality and manufacturing engineers. |
| My Role |
Result |
| Initially I worked with an MES software/hardware
supplier. At first it looked like a good
solution, but as we moved further along
they were not able to come up with a design
to meet our needs. The team then designed,
developed and implemented our own system. |
New system was designed and programmed
internally. Implementation went very well
and met the needs of the plant. The system
utilized wireless barcode readers to populate
a SQL database. Barcodes were laser etched
on metal components to be traced.Key issue(s):
Difficult system requirements and utilization
of some new technology. |
|
| Project Name |
Start Year |
Duration |
| Integration of new plant |
1987 |
12 months |
| Objective |
Team |
| The division acquired a new
plant and needed to integrate their existing
business systems into the division standard
systems. |
Team was comprised of the plant staff
managers. Each particular area (such as
materials management, accounting, etc.)
also had an integration team. |
| My Role |
Result |
| I was the technical project manager
and worked with another individual as
overall project manager. I had responsibility
for understanding their current system
and designing a strategy for integration.
Both of us had responsibility for training,
process changes, and change management
for the integration. |
We were able to complete the integration
on time with acceptance by the plant.
Key issue(s): First issue was need for
a change in strategy suggested by upper
management. Initial thought was to do
a gradual integration with "bridges"
between their old system and the new.
In my opinion this was not the best strategy.
Needed to present new strategy and gain
acceptance. The materials manager resigned
about third of the way through the project.
Biggest hurdle was to gain acceptance
of new system. Key to our success was
full understanding of current situation
and pros and cons of the new systems.
A key issue for myself, was that I also
still had management responsibility for
the division analyst and programming group. |
|
| Project Name |
Start Year |
Duration |
| Conversion of CAD/CAM system |
1986 |
9 months |
| Objective |
Team |
| Convert 2D mainframe CAD system
to UNIX based 3D system. |
Team was comprised of product and
manufacturing engineering managers from
each of the 4 facilities. |
| My Role |
Result |
| Worked in tandem with the division's
Advanced Engineering Manager to manage
selection, conversion and implementation
of a new CAD/CAM system. |
We were able to complete the selection,
conversion of drawings and implementation
of the new system on time and within budget.
Key issue(s): The new system presents
a very big change for the division. Biggest
tasks for the IT group were drawing conversion,
selection and support of new hardware. |
|
| Project Name |
Start Year |
Duration |
| ERP Implementation |
1984 |
24 months |
| Objective |
Team |
| Selection and implementation
of new ERP system for all locations (3)
of the division. |
Team was comprised of project managers
for each location, location teams and
IT team. Software consultants were utilized
as needed. |
| My Role |
Result |
| I was the technical and training project
manager. There was an overall project
manager for the division. |
The project had a huge impact on the
division and each plant. Every manufacturing
system was affected. The implementation
was very successful and the system served
the needs for 10 years.
Key issue(s): A project of this magnitude
has many issues. The overall project manager
changed and the second manager resigned
shortly after implementation. There were
several major software issues with the
product selected. We eventually took control
of the software and my team modified it
to meet our needs and expectations. As
part of the implementation, IT was required
to change mainframe system from UNIVAC
to IBM. The cut over to the new system
was done for all locations at the same
time. |
|
| Project Name |
Start Year |
Duration |
| Other Software Development Projects |
1985-1988 |
varied |
| Objective |
Team |
| This is a set of software
development projects. All were mainframe
systems utilizing COBOL, Easytrieve, IDMS
database and CICS or ADS/O for online. |
Team was comprised of IT analysts
and programmers along with a representative
user group. |
| My Role |
Projects |
| Project manager, system designer and
in many cases programmer. |
- Manufacturing scheduling
- Process Planning/Tooling
- Master Production Scheduling
- Inventory
- Purchasing
- Customer information system
|
|
|
|
|
|