Scripts and PXs for Agile PLM

If two application suites have comparable feature sets, then an easier-to-use, more intuitive user interface often determines which suite gains a larger share of the market. Users strongly favor software that improves access to commonly-used features, and minimizes the number of steps required to accomplish each task. Agile PLM’s highly polished user interface is held in high esteem in the enterprise software industry, and has been influential in many organizations’ adoption of Agile PLM instead of alternative PLM solutions.

On the other hand, though, it's been said that “graphical user interfaces make easy tasks easy, while command line interfaces make difficult tasks possible.” In other words, there are times when a GUI just isn’t the right tool for the job. This is especially obvious when the task to perform is repetitive and requires hardly any thought to accomplish. Adjusting the part numbers for an entire series of components in Agile can be accomplished via the GUI, but would probably take too many person-hours to be a feasible option. The same task, however, could easily be accomplished by a script containing fewer than ten lines of code. Such a script could probably rename millions of records in mere minutes, and complete the task without a single error. The same cannot be said for a team of fifty people using a perfect GUI.

BOM validation is another great reason to use scripts and PXs. Each company’s products and components are unique, which makes it very difficult to design a one-size fits- all solution that detects user error during data entry. However, if the data objects in a specific Agile space are known, scripts and PXs can produce effective BOM validation solutions.

A considerable number of the actions performed by users of software like Agile PLM have only slight variations. Component X from one supplier might be needed for product A, while component Y from another supplier might be needed for product B. Variations in an assembly process might call for input from different change approvers. When there are a small set of conditions that determine the course of action that needs to be taken, scripts and PXs can be used to automate decision making processes that are otherwise largely redundant.

The Agile SDK can be used for a number of file manipulation jobs. You might want to use a BOM template to generate duplicate BOMs, for example. Files can be imported from and exported to a number of file types, including Microsoft Word and Excel files. The SDK can also facilitate Agile PLM’s integration with other software applications that your business uses, so that manually copying data between programs is avoided whenever possible.

The SDK for Agile PLM 9.3 is an extremely powerful tool for crafting custom scripts and process extensions (PXs). A Groovy script can be used to whip up simple process automation similar to the example above. For more complex customizations, the Java APIs for Agile are a better option. The SDK can automate repetitive UI tasks, making them lightning-quick, and also produce UIs that conform more closely to way your business operates.

Here’s an example of the latter scenario. Suppose your organization does business with a number of component suppliers whom you’d like to provide accurate, up-to-date inventory information from your agile implementation. One possible solution might involve assigning an Agile login to the supplier, and customizing that login’s permissions according to the supplier’s needs. However, I think you will agree that this option is risky and impairs the effectiveness of an organization’s IT security policy.

A much better solution uses web services and the Java APIs to provide your suppliers with an information portal that resides outside the Agile server, and only shows them the data they need, presented in virtually any visual format that web browsers support. Now here’s a solution that is more secure than granting suppliers direct access to your Agile server, and also much more convenient than manually emailing each supplier!

As organizations using Agile become more familiar with the Agile SDK and the tremendous flexibility and power that it offers, scripts and PXs have begun to proliferate. Once companies begin to leverage Agile scripts and PXs in ways that approximate their business processes, they typically achieve greater operational efficiency. Personnel that had to manually perform repetitive tasks can now spend more time on jobs that truly require human judgment or creativity.

Despite the obvious advantages described thus far, some businesses, such as medical device manufacturers, are reluctant to utilize scripts and PXs because of industry requirements like FDA validation. However, in our work, we have estimated that the long-term gains in efficiency afforded by deploying a PX nearly always outweigh its onetime validation costs by a healthy margin.

Scripts and PXs are a great way to integrate business applications, reduce rates of error, automate builds and approval processes, improve inter-business communication without compromising security, and much more.Enterprises have much to gain from exploring the Agile SDK, and determining ways that it can mature your Agile PLM implementation from “great for any firm” to “perfect for us”.