<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://au.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Tools &amp; Automation</title>
 <link>http://au.sys-con.com/</link>
 <description>Latest articles from Tools &amp; Automation</description>
 <language>en</language>
 <copyright>Copyright 2012 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Sat, 18 Feb 2012 05:15:19 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>How MRP and Production Planning and Scheduling Software Differ</title>
 <link>http://au.sys-con.com/node/2086052</link>
 <description>Without a doubt, one of the most difficult stages of manufacturing production is the planning stage. Minor errors in predicting demand or planning materials can lead to costly mistakes such as producing too much or carrying excess inventory. To drive out waste and produce at the most efficient levels, manufacturers increasingly rely on information technology during the planning stages. Two of the most popular planning applications on the market today are material requirements planning (MRP) software and production planning and scheduling software.
While it’s generally understood that both of these applications are broadly about manufacturing planning, there remains considerable confusion about what each application is actually capable of doing. I recently decided to break down their capabilities as part of my work over at the Software Advice Manufacturing Blog. I thought it would be worth sharing the knowledge here. &lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/2086052&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 30 Dec 2011 15:30:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/2086052</guid>
</item>
<item>
 <title>Tips for Making the Right Decision for Your Organization</title>
 <link>http://au.sys-con.com/node/2069792</link>
 <description>Executing change management and version control for applications like Oracle E-Business Suite can be a daunting challenge, especially when you’re talking about upgrading Oracle E-Business 11i to version 12, commonly called “R12.” Your choices to achieve this change include a traditional upgrade to EBS R12, or reimplementation, a rip-and-replace of the current version with R12.
Each approach has its own unique set of advantages and disadvantages, and the path you take to R12 also can depend on whether your organization has EBS 11i, or an older version. In the long run, upgrading is less expensive, but carries a higher technical risk. Reimplementation, which rebuilds your existing Oracle E-Business Suite based on existing data, presents lower risk and requires less technical effort by an experienced DBA, but is more expensive. An EBS R12 upgrade can be challenging and complex, but, with knowledge of a few key fundamentals, you will survive, regardless of whether you’re perspective is technical or functional.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/2069792&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 18 Nov 2011 06:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/2069792</guid>
</item>
<item>
 <title>Choosing the Best Testing Tools to Increase Project Productivity</title>
 <link>http://au.sys-con.com/node/164547</link>
 <description>The primary mission of information technology is to improve business processes and increase profits. Companies are constantly rethinking and struggling with how to use IT to a competitive advantage, reduce IT operating and maintenance costs, and reduce the total cost of ownership... all while attempting to deliver increased value.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/164547&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 27 Dec 2005 15:15:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/164547</guid>
</item>
<item>
 <title>Building a Portal Using Web Services</title>
 <link>http://au.sys-con.com/node/47275</link>
 <description>The combination of portal technology, service-oriented architecture (SOA), and Web services provides customers with a powerful approach to developing, assembling, and deploying portal-based composite applications. Recent improvements in composite application development tools, coupled with a maturing portal market and a set of standards, provide customers with increased flexibility, promoting the reuse and repurposing of existing investments.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/47275&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 02 Dec 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/47275</guid>
</item>
<item>
 <title>Beyond SOA Platforms and Tools</title>
 <link>http://au.sys-con.com/node/47276</link>
 <description>Software reuse process and infrastructure are key enablers for SOA success. Software engineering spent the better part of the 20th century stubbornly resisting standard engineering disciplines. Project introspection and peripheral management activities accepted by all other engineering fields as mandatory have frequently been avoided by many software development organizations.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/47276&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 02 Dec 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/47276</guid>
</item>
<item>
 <title>Delivering, Administrating, &amp; Tracking Distributed Web Services</title>
 <link>http://au.sys-con.com/node/47280</link>
 <description>Companies that adopted and deployed early implementations of Web services primarily focused on three fundamental areas: These early implementations were driven by a need for greater efficiency in integrating systems, data and business processes, and in development.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/47280&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 02 Dec 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/47280</guid>
</item>
<item>
 <title>Sleeping with the Enemy</title>
 <link>http://au.sys-con.com/node/45516</link>
 <description>People often assume that .NET and J2EE are locked in some kind of life and death struggle. In fact, they can co-exist very well as I proved on a recent project. Both .NET and J2EE are based on open standards; these are Web Services Definition Language (WSDL) and Simple Object Access Protocol (SOAP), both of which are built on Extensible Markup Language (XML).&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/45516&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 02 Jul 2004 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/45516</guid>
</item>
<item>
 <title>Deploy Web Services - Double Your Servers?</title>
 <link>http://au.sys-con.com/node/43568</link>
 <description>The recent explosive growth of transactional information and applications over the Web has led to a very real concern for IT managers - how to address the processing bottleneck in Web and application servers. For service-oriented architectures (SOAs) that use XML to bridge the transfer of information across disparate technologies, this processing bottleneck may hinder the deployment and adoption of XML standards and Web services.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/43568&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 05 Feb 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/43568</guid>
</item>
<item>
 <title>Web Services - They&#039;re Here, but We&#039;re Not There (Yet)</title>
 <link>http://au.sys-con.com/node/43571</link>
 <description>Web services have been touted as a really &#039;big thing&#039; in the software industry the last couple of years, and that is for good reason: they promise technical interoperability between platforms from different vendors, an hitherto unheard-of thing in an industry plagued by proprietary non-compatible solutions.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/43571&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 05 Feb 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/43571</guid>
</item>
<item>
 <title>Wrapping the Perfect Web Services Package</title>
 <link>http://au.sys-con.com/node/43572</link>
 <description>Web services have been touted as a really &#039;big thing&#039; in the software industry the last couple of years, and for good reason: they promise technical interoperability between platforms from different vendors, an hitherto unheard-of thing in an industry plagued by proprietary non-compatible solutions.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/43572&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 05 Feb 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/43572</guid>
</item>
<item>
 <title>Building the Foundation for a New Breed of Enterprise Applications</title>
 <link>http://au.sys-con.com/node/43573</link>
 <description>More than ever, midsized businesses face the challenge of operating in a global economy, where nothing stands still. Product life cycles that once might have been measured in terms of years, are now measured in months or even weeks. From development to service, successful companies are leveraging process improvement and technology to continually reduce time to market and improve operating efficiencies.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/43573&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 05 Feb 2004 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/43573</guid>
</item>
<item>
 <title>The Tools Landscape</title>
 <link>http://au.sys-con.com/node/39575</link>
 <description>Web services products have matured rapidly over the past 12 months, to the point where it&#039;s become acceptable to utilize the technology in major projects. However, though improving, the currently available toolkits can&#039;t be considered complete.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/39575&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 23 Sep 2002 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/39575</guid>
</item>
<item>
 <title>Web Services Orchestration</title>
 <link>http://au.sys-con.com/node/39573</link>
 <description>In the past decade &#039;workflow&#039; has become one of the most overloaded  terms in the software industry. Almost every application is tagged as  &#039;based on workflow.&#039; While this doesn&#039;t always mean a lot, there is  good reason for it; it involves recognition among software architects  that the business process is the application.&lt;p&gt;&lt;a href=&quot;http://au.sys-con.com/node/39573&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 23 Sep 2002 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://au.sys-con.com/node/39573</guid>
</item>
</channel>
</rss>

