<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>eProcess Development &#187; Case Studies</title>
	<atom:link href="http://eprocessdevelopment.wordpress.com/category/case-studies/feed/" rel="self" type="application/rss+xml" />
	<link>http://eprocessdevelopment.wordpress.com</link>
	<description></description>
	<lastBuildDate>Tue, 22 Apr 2008 03:09:41 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<cloud domain='eprocessdevelopment.wordpress.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
<image>
		<url>http://www.gravatar.com/blavatar/0550bd6911efef15d34b00feec8cff6d?s=96&#038;d=http://s.wordpress.com/i/buttonw-com.png</url>
		<title>eProcess Development &#187; Case Studies</title>
		<link>http://eprocessdevelopment.wordpress.com</link>
	</image>
			<item>
		<title>Ls Hospital</title>
		<link>http://eprocessdevelopment.wordpress.com/2008/02/18/ls-hospital/</link>
		<comments>http://eprocessdevelopment.wordpress.com/2008/02/18/ls-hospital/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 14:57:03 +0000</pubDate>
		<dc:creator>eprocessdevelopment</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://eprocessdevelopment.wordpress.com/?p=29</guid>
		<description><![CDATA[by Kurt Rodenhizer, MS, MBA
 
LS Hospital has over 10,000 employees or volunteers working for the organization. One of the logistics that is not often considered is the allocation of parking space for this population. The parking lot security system requires employees to scan a card for access to a parking lot and this means the [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=29&subd=eprocessdevelopment&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p><i>by Kurt Rodenhizer, MS, MBA</i><br />
<b> </b><br />
LS Hospital has over 10,000 employees or volunteers working for the organization. One of the logistics that is not often considered is the allocation of parking space for this population. The parking lot security system requires employees to scan a card for access to a parking lot and this means the person&#8217;s name and scan code number must be managed. <span id="more-29"></span></p>
<p><b>Challenges: </b><br />
Because of frequent change in the employee population, managing the database used to store names, employee numbers, working shifts, rotation dates and vehicle details has not been an easy task. An MS Access database was being used by one staff person to manage the information and then communicate details to the parking administration department. It was important to have the information on parking assignments available on demand and also to allow new employee to apply for their parking assignments when they found it convenient (vs getting parking assignments only when the staff person handling the database was available).</p>
<p><b>Diagnosis: </b><br />
It was decided that the database would be most functional if the information was made available online and ePD was contracted to build the Web version of the database. The system would have to provide an employee parking application form and the form design would have to change depending on the type of employee applying for the lot allocation. There would have to be a way for administrators to search, view and edit the records and since lot assignments varied by employee type, a login system would have to be implemented.</p>
<p><b>Solutions</b></p>
<p><b>Login Page:</b><br />
Handling the variations in the application form used for different employee types was done by using a drop down menu on the parking home page. No names or passwords are required.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_ls1.jpg" height="430" width="496" /></p>
<p><b>Application Form:</b><br />
The application form was used to collect needed details such as name, location, rotation dates, shift times, and vehicle identification details. Drop down fields and radio buttons were used whenever possible to make the application process as efficient as possible and to prevent the entry of inappropriate data.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_ls2.jpg" height="720" width="500" /></p>
<p><b>Administration Form:</b><br />
Parking Administrators were given a weblink to a form that allows for the search of records by name, plate number, date of application and , employee type. The table section lists all filtered employee and allows access to the full record, editing of the information and record deletion.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_ls3.jpg" height="471" width="500" /></p>
<p><b>Results:</b><br />
1. The custom Web site database was created in four days.<br />
2. The database handles parking lot allocation for over 10,000 employees and is available to anyone when needed.<br />
3. The admin options include record location, editing and deletion.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/eprocessdevelopment.wordpress.com/29/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/eprocessdevelopment.wordpress.com/29/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eprocessdevelopment.wordpress.com/29/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eprocessdevelopment.wordpress.com/29/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eprocessdevelopment.wordpress.com/29/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eprocessdevelopment.wordpress.com/29/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eprocessdevelopment.wordpress.com/29/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eprocessdevelopment.wordpress.com/29/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eprocessdevelopment.wordpress.com/29/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eprocessdevelopment.wordpress.com/29/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eprocessdevelopment.wordpress.com/29/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eprocessdevelopment.wordpress.com/29/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=29&subd=eprocessdevelopment&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://eprocessdevelopment.wordpress.com/2008/02/18/ls-hospital/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/096b2908d5891e124e838ff6bfdd44da?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">eprocessdevelopment</media:title>
		</media:content>

		<media:content url="http://www.eprocessdevelopment.com/images/case_ls1.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_ls2.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_ls3.jpg" medium="image" />
	</item>
		<item>
		<title>MedLeads</title>
		<link>http://eprocessdevelopment.wordpress.com/2008/02/18/medleads/</link>
		<comments>http://eprocessdevelopment.wordpress.com/2008/02/18/medleads/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 14:53:32 +0000</pubDate>
		<dc:creator>eprocessdevelopment</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://eprocessdevelopment.wordpress.com/?p=28</guid>
		<description><![CDATA[ by Kurt Rodenhizer, MS, MBA
MedLeads is a professional communications company that generates sales leads for its clients by calling potential customers, interviewing key contacts and collecting essential information. For each client, online calling forms (surveys) are created and used to collect the data requested by their clients. MedLeads uses a team of trained specialist [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=28&subd=eprocessdevelopment&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p> <i>by Kurt Rodenhizer, MS, MBA</i></p>
<p><a href="http://eprocessdevelopment.files.wordpress.com/2008/02/logo_medleads.jpg" title="medleads"><img src="http://eprocessdevelopment.files.wordpress.com/2008/02/logo_medleads.thumbnail.jpg" alt="medleads" style="float:left;" /></a>MedLeads is a professional communications company that generates sales leads for its clients by calling potential customers, interviewing key contacts and collecting essential information. For each client, online calling forms (surveys) are created and used to collect the data requested by their clients. MedLeads uses a team of trained specialist to conduct the customer interviews.</p>
<p><b>Challenges: </b><br />
With multiple clients being serviced concurrently, MedLeads was finding if difficult to manage all the data and present the information to their clients in a professional manner. In addition, <span id="more-28"></span>since the MedLeads staff were living all over the country, it was quite difficult to manage the files of information that had to be emailed or faxed to the MedLeads&#8217; offices for processing and report generation.</p>
<p><b>Diagnosis: </b><br />
MedLeads had an online database but they needed a more sophisticated system for data management and the the decision was made to upgrade to a new online database that could do a better job of managing all aspects of the business. The results of a portion of this project can be reviewed via the MedLeads website (also developed by ePD). For details and to evaluate the &#8220;Real Time Reporting&#8221; demo, visit www.MedLeads.com</p>
<p><b>Solutions</b></p>
<p><b>Online database development:</b><br />
ePD was contracted to create the online database and the first step in the system architecture was to create a series of Web-based tables (MySQL) that would store essential information such as organization names, contacts, call log history and interview data.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_med1.jpg" height="195" width="399" /><br />
<i>Online forms are used to locate and edit all organization and contact information</i></p>
<p><b>Calling Form Development &#8211; Header area</b><br />
Once the database tables were set up, ePD created a header that would be placed at the top of each &#8220;calling form.&#8221; This was done so the caller had all associated details (e.g. names, number of beds at the hospital, contract groups, etc) in front of them while they were interviewing the customer. The header area is a shared area used in all client calling forms.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_med2.jpg" height="186" width="499" /></p>
<p><b>Calling Form Development &#8211; Survey area</b><br />
For each client, a separate calling form is used and they can all be selected using a drop down selection field or by assigning a client to a specific caller as specified in the easily edited user table</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_med3.jpg" height="290" width="467" /><br />
<i>Fields in the calling form use check boxes, drop downs, radio buttons, text fields and memo fields<br />
to allow for the most efficient data collection process possible.</i></p>
<p><b>To Do Table Section:</b><br />
The system used to organize all calling forms and store them in various stages of project completion is called the To Do Table Section. When a calling form is loaded and targeted for a specific customer call, the project can be found in the &#8220;Pending&#8221; section. When a call is first place, the calling log history begins and the calling form sits in the &#8220;In-Process&#8221; section until the callers clicks on complete at the bottom of the form. The other two sections where the project can be located includes &#8220;Awaiting Approval&#8221; and &#8220;Rework.&#8221;</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_med4.jpg" height="124" width="500" /><br />
<i>The image above illustrates the &#8220;Rework&#8221; section of the To Do Table and it is used to send a calling<br />
form back to the caller for modifications.</i></p>
<p><b>Reports:</b><br />
All collected calling form data is stored in the Report section where the records can be viewed by the MedLeads clients. The records are color coded to point out which leads are &#8220;Urgent,&#8221; &#8220;Rep Requested,&#8221; &#8220;News and Updates Requested&#8221; or &#8220;No Action Required.&#8221; When a lead is generated that requires a sales representative&#8217;s attention, an automatic email is sent to the person responsible for that territory.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_med5.jpg" height="318" width="498" /><br />
<i>The Report section of the database actually presents 5 different reports formats and allows for record<br />
location by account number, territory and lead urgency.</i></p>
<p><b>Customer Communications:</b><br />
During a lead interview, a customer may be asked if they are interested in receiving some type of product information from the client. If so, check box can be marked that signals the database that a specific customer letter will be sent automatically. A log of all customer communications is retained for the client and presented as one of the reports.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_med6.jpg" height="227" width="399" /><br />
<i>Letters can be designed in the standard format as shown or as a newsletter.<br />
Dissemination of the material can be targeted to an individual or distribution list.</i></p>
<p><b>Results:</b><br />
1. An online database that manages multiple calling forms (surveys) and reports for MedLeads clients was built in 6 weeks.<br />
2. The system is efficient in that it shares the same table for organizations and contacts<br />
3. The To Do Table section allows multiple MedLeads calling specialists to find their projects (sorted by date and time of next call), collect information and send the project on for administration approval.<br />
4. The reports allow the clients to log in and see the results online as information is collected.<br />
5. The built in communications system automatically sends customer letters and online literature on demand. The sales reps for the MedLeads clients are sent emails when information comes in that they should be aware of.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/eprocessdevelopment.wordpress.com/28/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/eprocessdevelopment.wordpress.com/28/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eprocessdevelopment.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eprocessdevelopment.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eprocessdevelopment.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eprocessdevelopment.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eprocessdevelopment.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eprocessdevelopment.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eprocessdevelopment.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eprocessdevelopment.wordpress.com/28/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eprocessdevelopment.wordpress.com/28/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eprocessdevelopment.wordpress.com/28/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=28&subd=eprocessdevelopment&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://eprocessdevelopment.wordpress.com/2008/02/18/medleads/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/096b2908d5891e124e838ff6bfdd44da?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">eprocessdevelopment</media:title>
		</media:content>

		<media:content url="http://eprocessdevelopment.files.wordpress.com/2008/02/logo_medleads.thumbnail.jpg" medium="image">
			<media:title type="html">medleads</media:title>
		</media:content>

		<media:content url="http://www.eprocessdevelopment.com/images/case_med1.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_med2.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_med3.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_med4.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_med5.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_med6.jpg" medium="image" />
	</item>
		<item>
		<title>Dräger catalog</title>
		<link>http://eprocessdevelopment.wordpress.com/2008/02/18/drager-catalog/</link>
		<comments>http://eprocessdevelopment.wordpress.com/2008/02/18/drager-catalog/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 14:48:16 +0000</pubDate>
		<dc:creator>eprocessdevelopment</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://eprocessdevelopment.wordpress.com/?p=27</guid>
		<description><![CDATA[by Kurt Rodenhizer, MS, MBA

Dräger Medical provides hospitals with medical systems designed to optimize clinical processes. They have several offices throughout the world and there are over 900 parts in their product catalog.
Challenges: 
Dräger&#8217;s parts as described in the product catalog change frequently and it is difficult to keep the customers and product specialists up-to-do-date [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=27&subd=eprocessdevelopment&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p><i>by Kurt Rodenhizer, MS, MBA</i></p>
<p><a href="http://eprocessdevelopment.files.wordpress.com/2008/02/744px-drager_logosvg.png" title="744px-drager_logosvg.png"><img src="http://eprocessdevelopment.files.wordpress.com/2008/02/744px-drager_logosvg.thumbnail.png" alt="744px-drager_logosvg.png" style="float:left;" /></a></p>
<p>Dräger Medical provides hospitals with medical systems designed to optimize clinical processes. They have several offices throughout the world and there are over 900 parts in their product catalog.</p>
<p><b>Challenges: </b><br />
Dräger&#8217;s parts as described in the product catalog change frequently and it is difficult to keep the customers and product specialists up-to-do-date with the most recent information. Another problem is that following a joint venture agreement with Siemens Medical, there were several sections of the product <span id="more-27"></span>catalog in different publication programs including MS Publisher, Quark Express and Adobe PageMaker. The objective was to consolidate all versions of the catalog into one and to investigate ways to more quickly publish product update information.</p>
<p><b>Solutions</b><br />
<b><br />
Consolidating data into one master record:</b><br />
ePD was contracted to work on the project and the recommendation was that all the parts and their descriptions be loaded into a database so the editing can be done from one source. After the part numbers, description and images were updated, a software code would be used to export the data into the preferred publication software.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_cata1.jpg" height="269" width="447" /><br />
<i>A customized data entry form was created to assist in data entry and the master database<br />
was placed in a network folder so that multiple people could work with the same file.</i></p>
<p><b>Automatic generation of the product catalog on demand:</b><br />
The software protocol written to export the data into the publication software&#8217;s customized style sheet (template) allows Dräger to upgrade their product catalog on demand and as easily as executing a mail merge.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_cata2.jpg" height="355" width="449" /><br />
<i>All the text and images used for the catalog comes from one master database and once the<br />
export protocol has been written, catalogs can be update on demand.</i></p>
<p><b>Results:</b><br />
1. The text from several segments of the product catalog were collected into a master database it was edited by product specialists.<br />
2. A style sheet was created in the publication software so the text and images from the database would generate the product catalog automatically and whenever needed.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/eprocessdevelopment.wordpress.com/27/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/eprocessdevelopment.wordpress.com/27/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eprocessdevelopment.wordpress.com/27/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eprocessdevelopment.wordpress.com/27/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eprocessdevelopment.wordpress.com/27/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eprocessdevelopment.wordpress.com/27/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eprocessdevelopment.wordpress.com/27/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eprocessdevelopment.wordpress.com/27/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eprocessdevelopment.wordpress.com/27/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eprocessdevelopment.wordpress.com/27/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eprocessdevelopment.wordpress.com/27/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eprocessdevelopment.wordpress.com/27/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=27&subd=eprocessdevelopment&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://eprocessdevelopment.wordpress.com/2008/02/18/drager-catalog/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/096b2908d5891e124e838ff6bfdd44da?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">eprocessdevelopment</media:title>
		</media:content>

		<media:content url="http://eprocessdevelopment.files.wordpress.com/2008/02/744px-drager_logosvg.thumbnail.png" medium="image">
			<media:title type="html">744px-drager_logosvg.png</media:title>
		</media:content>

		<media:content url="http://www.eprocessdevelopment.com/images/case_cata1.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_cata2.jpg" medium="image" />
	</item>
		<item>
		<title>Dräger Flow Sheets</title>
		<link>http://eprocessdevelopment.wordpress.com/2008/02/18/drager-flow-sheets/</link>
		<comments>http://eprocessdevelopment.wordpress.com/2008/02/18/drager-flow-sheets/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 14:44:52 +0000</pubDate>
		<dc:creator>eprocessdevelopment</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://eprocessdevelopment.wordpress.com/?p=26</guid>
		<description><![CDATA[by Kurt Rodenhizer, MS, MBA
Dräger Medical provides hospitals with medical systems designed to optimize clinical processes. The company uses “flow sheets” to provide their sales force with part numbers and order information. The flow sheets help Dräger sales reps understand the complex configuration requirements for over 900 parts. 

Dräger sales reps use flow sheets as [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=26&subd=eprocessdevelopment&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p><i>by Kurt Rodenhizer, MS, MBA</i></p>
<p><a href="http://eprocessdevelopment.files.wordpress.com/2008/02/744px-drager_logosvg.png" title="744px-drager_logosvg.png"><img src="http://eprocessdevelopment.files.wordpress.com/2008/02/744px-drager_logosvg.thumbnail.png" style="float:left;" alt="744px-drager_logosvg.png" /></a>Dräger Medical provides hospitals with medical systems designed to optimize clinical processes. The company uses “flow sheets” to provide their sales force with part numbers and order information. The flow sheets help Dräger sales reps understand the complex configuration requirements for over 900 parts. <span id="more-26"></span></p>
<p><img width="499" src="http://www.eprocessdevelopment.com/images/case_flow1.jpg" height="244" /><br />
<i>Dräger sales reps use flow sheets as shown above to follow system configuration guidelines</i></p>
<p><b>Challenges:</b><br />
The flow sheets were difficult to edit. Since changes in part numbers occurred frequently, flow sheet management required a full-time outside specialist. Dräger wanted to bring flow sheet management in-house, and they needed to do it quickly. The company had just embarked on a joint venture with Siemens that made Dräger responsible for a new line of monitors and as a result, numerous part configurations had changed. There were nine separate flow sheets that needed to be updated so the sales force could create accurate order configurations for their patient monitoring systems.</p>
<p><b>Diagnosis: </b><br />
Dräger needed one place to house all product information that would be easily accessible to a number of people working in different parts of the office. They also wanted a solution that would work well with Visio, a software program the company had recently begun to use and support. Finally, Dräger needed a solution that they would be able to support and troubleshoot in-house.</p>
<p><b>Solutions</b></p>
<p><b>Consolidation of data:</b><br />
ePD developed an Access database to hold all product information. The database was placed on the company network, making it accessible to different people throughout the company.</p>
<p><img width="499" src="http://www.eprocessdevelopment.com/images/case_flow2.jpg" height="400" /><br />
<i>A customized data entry form was created to assist in data entry and the master database was placed<br />
in a network folder so that multiple people could use the same information.</i></p>
<p><b>Automatic updates of data:</b><br />
ePD then created an automated process for updating the product information in the Access database with up-to-date information from the company’s SAP system.</p>
<p><b>Linking Visio to the master database:</b><br />
The next step was to link Visio flow sheet templates to the Access database allowing the Visio drawings to be automatically populated with data (similar to a mail merge).</p>
<p><img width="499" src="http://www.eprocessdevelopment.com/images/case_flow3.jpg" height="240" /><br />
<i>All the text used in the flow sheets comes from the database, eliminating re-typing.</i></p>
<p><b>Inserting images and order quantity boxes:</b><br />
Finally, ePD developed programming codes that would integrate all product images and order quantity boxes into the database</p>
<p><img width="499" src="http://www.eprocessdevelopment.com/images/case_flow4.jpg" height="152" /><br />
<i>Placement of all images and order quantity boxes are done automatically</i></p>
<p><b>Training the staff on the new software:</b><br />
ePD conducted an in-house training for all staff members who need access to product information.</p>
<p><b>Results:</b><br />
1. All nine flow sheets were submitted for final review in eight weeks, 50% less time than previously required to generate the flow sheets.<br />
2. All of the order management staff and product managers are now using one database to add, remove and edit part numbers and part descriptions.<br />
3. Since one centralized database has replaced four separate databases, naming protocol for the parts has been streamlined (for example: SW Option, Delta SW Option or Option, SW).<br />
4. Dräger staff has produced three additional flow sheets in-house.<br />
5. Dräger is now using the master database to automatically generate an online and offline product catalog. The system also allows the order management system to be presented online and to generate automatic customer quotes. (click here for demo)</p>
<p><b>Customer Quotations:</b><br />
“ePD helped us overcome significant obstructions in organizing our data. They helped us save an estimated two months of work and helped us reach our goals. At the time, we did not have the database and Visio skills needed to complete the project, but we are now able to quickly create new order configurations and upgrade flow sheets in-house.”<br />
-Anders Brograde, Product Manager, Dräger Medical Systems</p>
<p>&#8220;ePD was excellent to work with. They understood our needs, and provided us with a product that was done right and done well. They had the expertise to ensure the project met our immediate objectives and the foresight to point how we can use the data for other projects. Money well spent, and time well saved.&#8221;<br />
-Dina LaTulippe, Senior Product Manager, Dräger Medical Systems.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/eprocessdevelopment.wordpress.com/26/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/eprocessdevelopment.wordpress.com/26/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eprocessdevelopment.wordpress.com/26/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eprocessdevelopment.wordpress.com/26/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eprocessdevelopment.wordpress.com/26/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eprocessdevelopment.wordpress.com/26/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eprocessdevelopment.wordpress.com/26/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eprocessdevelopment.wordpress.com/26/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eprocessdevelopment.wordpress.com/26/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eprocessdevelopment.wordpress.com/26/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eprocessdevelopment.wordpress.com/26/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eprocessdevelopment.wordpress.com/26/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=26&subd=eprocessdevelopment&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://eprocessdevelopment.wordpress.com/2008/02/18/drager-flow-sheets/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/096b2908d5891e124e838ff6bfdd44da?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">eprocessdevelopment</media:title>
		</media:content>

		<media:content url="http://eprocessdevelopment.files.wordpress.com/2008/02/744px-drager_logosvg.thumbnail.png" medium="image">
			<media:title type="html">744px-drager_logosvg.png</media:title>
		</media:content>

		<media:content url="http://www.eprocessdevelopment.com/images/case_flow1.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_flow2.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_flow3.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_flow4.jpg" medium="image" />
	</item>
		<item>
		<title>BM Medical</title>
		<link>http://eprocessdevelopment.wordpress.com/2008/02/18/bm-medical/</link>
		<comments>http://eprocessdevelopment.wordpress.com/2008/02/18/bm-medical/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 14:39:56 +0000</pubDate>
		<dc:creator>eprocessdevelopment</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://eprocessdevelopment.wordpress.com/?p=25</guid>
		<description><![CDATA[by Kurt Rodenhizer, MS, MBA

BM Medical provides temperature regulation equipment and disposables to Anesthesia Departments throughout the world.

Challenges: 
BM Medical was using multiple files to manage contact information and to generate sales reports. The method for data entry left room for error and there was no relationship between customer contact information and sales made to [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=25&subd=eprocessdevelopment&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p><i>by Kurt Rodenhizer, MS, MBA</i><br />
<b></b><br />
BM Medical provides temperature regulation equipment and disposables to Anesthesia Departments throughout the world.<br />
<span id="more-25"></span></p>
<p><b>Challenges: </b><br />
BM Medical was using multiple files to manage contact information and to generate sales reports. The method for data entry left room for error and there was no relationship between customer contact information and sales made to the respective hospitals. In addition, the sales activity reports per region required the integration of multiple files into one and this was not being done as efficiently as the company had wanted..</p>
<p><b>Diagnosis: </b><br />
Data on customers such as organization numbers, address, phone numbers, etc. was not associated to the sales data that was being entered by customer service.</p>
<p><b>Solutions</b></p>
<p><b>Table Architecture:</b><br />
The first objective was to collect all the data from multiple files and create the minimum number of tables needed to develop the database. The table below is the organization table. Organization ID&#8217;s were assigned and regions were linked to the Sale rep regional tables. the link to the regional tables were important since sales quotas are based on sales made per region.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_bm1.jpg" height="210" width="450" /></p>
<p><b>Product Table:</b><br />
A product table was created so data did not have to be entered into the sales files. This table and others were used to create forms with drop down fields and check boxes to eliminate data entry error and spelling inconsistencies.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_bm2.jpg" height="291" width="434" /></p>
<p><b>Report Generation:</b><br />
Because all information has been stored in linked tables, hundreds of reports are possible in multiple formats.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_bm3.jpg" height="338" width="449" /></p>
<p><b>Results:</b><br />
1. The custom database was created in three days.<br />
2. All data has been linked via assigned id numbers (database table relationships were resolved)<br />
3. The establishment of database relationships allows for hundreds of report options which are all automatically updated as new data is entered into the system.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/eprocessdevelopment.wordpress.com/25/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/eprocessdevelopment.wordpress.com/25/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eprocessdevelopment.wordpress.com/25/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eprocessdevelopment.wordpress.com/25/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eprocessdevelopment.wordpress.com/25/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eprocessdevelopment.wordpress.com/25/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eprocessdevelopment.wordpress.com/25/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eprocessdevelopment.wordpress.com/25/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eprocessdevelopment.wordpress.com/25/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eprocessdevelopment.wordpress.com/25/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eprocessdevelopment.wordpress.com/25/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eprocessdevelopment.wordpress.com/25/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=25&subd=eprocessdevelopment&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://eprocessdevelopment.wordpress.com/2008/02/18/bm-medical/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/096b2908d5891e124e838ff6bfdd44da?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">eprocessdevelopment</media:title>
		</media:content>

		<media:content url="http://www.eprocessdevelopment.com/images/case_bm1.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_bm2.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_bm3.jpg" medium="image" />
	</item>
		<item>
		<title>AX Medical</title>
		<link>http://eprocessdevelopment.wordpress.com/2008/02/18/ax-medical/</link>
		<comments>http://eprocessdevelopment.wordpress.com/2008/02/18/ax-medical/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 14:36:30 +0000</pubDate>
		<dc:creator>eprocessdevelopment</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://eprocessdevelopment.wordpress.com/?p=24</guid>
		<description><![CDATA[by Kurt Rodenhizer, MS, MBA
 
AX Medical is a company that specializes in the engineering and development of medical devices. Their customers are mainly medical manufacturers who outsource to AX for design engineering contracts.
Challenges: 
AX has several offices throughout the US, and their customer contact information had become a collection of files from several sources. The [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=24&subd=eprocessdevelopment&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p><i>by Kurt Rodenhizer, MS, MBA</i><br />
<b> </b><br />
AX Medical is a company that specializes in the engineering and development of medical devices. Their customers are mainly medical manufacturers who outsource to AX for design engineering contracts.<span id="more-24"></span></p>
<p><b>Challenges: </b><br />
AX has several offices throughout the US, and their customer contact information had become a collection of files from several sources. The objective was to create one master database for all their contacts, remove duplications and then start making updates to one data source.</p>
<p><b>Diagnosis: </b><br />
ePD was contracted to manage the creation of an offline database (built in MS Access). The objective was to create a database that would allow for the effective categorization, search and edit capabilities for all key contacts and to produce numerous variations of print ready reports on demand.</p>
<p><b>Solutions</b></p>
<p><b>Master Table</b><br />
ePD collected all the records into one table, removed double entries and assigned customer numbers to each client office. The number of records was reduced from 30,000 to 9,000 following the data scrubbing.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_ax1.jpg" height="159" width="450" /></p>
<p><b>Standardization Process:</b><br />
Data scrubbing included standardizing the way information is presented in the database (e.g. VP vs. Vice-President; First Street vs 1st Street). This tedious work was essential so the filters (search and queries) set for department, job titles, office locations, etc., would work reliably.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_ax2.jpg" height="259" width="450" /></p>
<p><b>Master Form:</b><br />
Once the tables were ready, a master form was organized to allow for record location and editing. A linked sub-table was used to provide details on all contacts working for a specific client office. Drop downs and checkboxes were inserted whenever possible to reduce the time associated with data entry and editing.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_ax3.jpg" height="340" width="450" /></p>
<p><b>Filter-based Reports:</b><br />
Numerous report templates were set up and a software code was used to display in the print ready reports, only what was filtered (queried) from the &#8220;filter&#8221; page. For example and as shown in the image below, a filter was applied for key accounts, and then by sub-division. The report shows only the filtered data. On a subsequent filter, the user can select contacts in just the purchasing departments and in a specific territories.</p>
<p><img src="http://www.eprocessdevelopment.com/images/case_ax4.jpg" height="216" width="450" /></p>
<p><b>Results:</b><br />
1. The custom database was completed in five days including the data processing.<br />
2. The database allows for hundreds of filtering or query options (e.g. by job title, department, territory, sales volume, etc)<br />
3. Whatever is filtered remains in queue as the user clicks on the templated reports<i> (allows for hundreds of report options without needing to design hundreds of reports)  </i></p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/eprocessdevelopment.wordpress.com/24/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/eprocessdevelopment.wordpress.com/24/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eprocessdevelopment.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eprocessdevelopment.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eprocessdevelopment.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eprocessdevelopment.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eprocessdevelopment.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eprocessdevelopment.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eprocessdevelopment.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eprocessdevelopment.wordpress.com/24/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eprocessdevelopment.wordpress.com/24/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eprocessdevelopment.wordpress.com/24/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=24&subd=eprocessdevelopment&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://eprocessdevelopment.wordpress.com/2008/02/18/ax-medical/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/096b2908d5891e124e838ff6bfdd44da?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">eprocessdevelopment</media:title>
		</media:content>

		<media:content url="http://www.eprocessdevelopment.com/images/case_ax1.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_ax2.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_ax3.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_ax4.jpg" medium="image" />
	</item>
		<item>
		<title>Aronson &amp; Novicki</title>
		<link>http://eprocessdevelopment.wordpress.com/2008/02/18/aronson-novicki/</link>
		<comments>http://eprocessdevelopment.wordpress.com/2008/02/18/aronson-novicki/#comments</comments>
		<pubDate>Mon, 18 Feb 2008 14:31:52 +0000</pubDate>
		<dc:creator>eprocessdevelopment</dc:creator>
				<category><![CDATA[Case Studies]]></category>

		<guid isPermaLink="false">http://eprocessdevelopment.wordpress.com/?p=23</guid>
		<description><![CDATA[by Kurt Rodenhizer, MS, MBA

Aronson &#38; Novicki is a title examination company with over 300 clients. The company’s work predominately entails organizing client files, compiling details for new work order, researching titles, completing invoices and matching contact information to billing statements.
Challenges: 
A&#38;N needed to improve their file management system and reduce their dependence on paper [...]<img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=23&subd=eprocessdevelopment&ref=&feed=1" />]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p><i>by Kurt Rodenhizer, MS, MBA</i></p>
<p><a href="http://eprocessdevelopment.files.wordpress.com/2008/02/web_aronson.jpg" title="web_aronson.jpg"><img src="http://eprocessdevelopment.files.wordpress.com/2008/02/web_aronson.thumbnail.jpg" alt="web_aronson.jpg" style="float:left;" /></a></p>
<p>Aronson &amp; Novicki is a title examination company with over 300 clients. The company’s work predominately entails organizing client files, compiling details for new work order, researching titles, completing invoices and matching contact information to billing statements.</p>
<p><b>Challenges: </b><br />
A&amp;N needed to improve their file management system and reduce their dependence on paper files. They wanted to electronically generat to-do lists and associated reports. <span id="more-23"></span>Work order, billing details and invoices were being created by hand and then re-entered into a limited database. If work orders, invoices and billing data were not carefully collected at the end of each day, important data was lost and the collections process incomplete. In addition, the competition was beginning to use email to contact their clients and a website to accept work order forms and review billing statements.</p>
<p><b>Diagnosis: </b><br />
In order to streamline business processes and ensure collections, A&amp;N needed to develop an automated electronic process. The first step was to create a customized database that would allow the company to operate their entire business from one master form. The database would also allow invoices and mailing labels to be printed on a pre-determined schedule.</p>
<p><b>Solutions</b><br />
<b><br />
Master Form:</b><br />
Allows the user to scroll through each client’s history and review contact information, payment history, outstanding invoices and the results of their title exam.</p>
<p><img width="591" src="http://www.eprocessdevelopment.com/images/case_aranson1.jpg" height="358" /></p>
<p><b>Automated Search:</b><br />
The database allows A&amp;N staff members to search for specific client details and run custom reports, such as address lists formatted to print on mailing labels, pending jobs, payments received and payments due.</p>
<p><img width="355" src="http://www.eprocessdevelopment.com/images/case_aranson2.jpg" height="194" /></p>
<p><b>Customer Reporting:</b><br />
A&amp;N can now use the information stored in the database to create several reports. This Pending Jobs Report once had to be filled out by hand. Now it can be printed with the click of a button and used as the daily To-Do list.</p>
<p><img width="532" src="http://www.eprocessdevelopment.com/images/case_aranson3.jpg" height="321" /></p>
<p><b>Automation:</b><br />
A&amp;N can now automate the production of its customer invoices, FedX packing slips and mailing labels</p>
<p><b>Results:</b><br />
1. The custom database was created in three days.<br />
2. The database saves approximately 10 hours of work per week.<br />
3. Daily task lists are now automatically generated.<br />
4. Automating the accounts receivable processes is expected to improve revenue.</p>
<p><b>Customer Quotation:</b><br />
“ePD reviewed our business processes and managed to convert most of our hard-copy material into a database that put us one click away from all work orders, invoices, contact information, project lists, collection data and sales summaries. The electronic process has translated to the effective reduction of 10 hours per week.”<br />
-Carl Aronson, Aronson and Novicki Title Examiners, LLC</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/eprocessdevelopment.wordpress.com/23/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/eprocessdevelopment.wordpress.com/23/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/eprocessdevelopment.wordpress.com/23/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/eprocessdevelopment.wordpress.com/23/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/eprocessdevelopment.wordpress.com/23/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/eprocessdevelopment.wordpress.com/23/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/eprocessdevelopment.wordpress.com/23/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/eprocessdevelopment.wordpress.com/23/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/eprocessdevelopment.wordpress.com/23/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/eprocessdevelopment.wordpress.com/23/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/eprocessdevelopment.wordpress.com/23/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/eprocessdevelopment.wordpress.com/23/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=eprocessdevelopment.wordpress.com&blog=2773791&post=23&subd=eprocessdevelopment&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://eprocessdevelopment.wordpress.com/2008/02/18/aronson-novicki/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
	
		<media:content url="http://0.gravatar.com/avatar/096b2908d5891e124e838ff6bfdd44da?s=96&#38;d=identicon&#38;r=G" medium="image">
			<media:title type="html">eprocessdevelopment</media:title>
		</media:content>

		<media:content url="http://eprocessdevelopment.files.wordpress.com/2008/02/web_aronson.thumbnail.jpg" medium="image">
			<media:title type="html">web_aronson.jpg</media:title>
		</media:content>

		<media:content url="http://www.eprocessdevelopment.com/images/case_aranson1.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_aranson2.jpg" medium="image" />

		<media:content url="http://www.eprocessdevelopment.com/images/case_aranson3.jpg" medium="image" />
	</item>
	</channel>
</rss>