THIS PAPER OFFERS SEVERAL REASONS WHY CASE IS NOT BEING READILY ADOPTED INTO MANUFACTURING SOFTWARE DEVELOPMENT. THOSE REASONS ARE: THE BACKGROUNDS OF THE DEVELOPERS ARE SPECIALIZED IN THE APPLICATION AREAS AND NOT SOFTWARE ENGINEERING; ORGANIZATIONS AND DEVELOPERS ARE NOT AWARE OF AVAILABILITY AND PERCEIVE MANUFACTURING AS DIFFERENT THAN OTHER INDUSTRIES; THE ORGANIZATIONS ARE INHIBITED FROM USING CASE BY NUMEROUS FACTORS; AND THE MARKETPLACE IS FRAGMENTED AND NEEDS INDUSTRY-WIDE COORDINATION AND FOCUS. THIS PAPER OUTLINES FOUR AREAS OF WORK THAT CAN HELP MANUFACTURING SOFTWARE DEVELOPERS GAIN INSIGHTS INTO WHAT TOOLS AND METHODS ARE AVAILABLE, WHICH ARE APPROPRIATE AND WHEN, AND HELP SUPPLIERS BETTER UNDERSTAND AND BETTER MEET THE NEEDS OF MANUFACTURING SOFTWARE DEVELOPERS. THE FOUR AREAS ARE: DETERMINING THE BEST CURRENT PRACTICES POSSIBLE FOR DEVELOPMENT TODAY; DETERMINING HOW TO SU