Monday Oct 06, 2008

What PCM actions are supported through SDK?

[Read More]

Wednesday Oct 01, 2008

Installing ACP

Thomas Edison once said "I haven't failed; I have found 10,000 ways that don't work". In this tremendously evolving world where 'Google' is posing extinction to the verb 'search', Intel quad core microprocessors are breaking all speed barriers and HP Oracle Exadata Storage servers breaking the performance bottleneck between database servers and conventional storage, we all look for quick and easy answers to the most ambiguous questions and problems we have ever come across. And I'm sure you are looking for an easy answer to the question, "Now that I have got hold of ACP software, how do I install it?", than waiting for the 10,001th try to figure out how to do it right.[Read More]

Thursday Sep 25, 2008

Who needs iPLM?

[Read More]

Enabling seamless processes between Agile PLM and SAP ERP

An integration between Agile PLM and SAP ERP is an essential part of your infrastructure if you want to support a seamless process between design and validation phase in PLM and manufacturing execution in SAP. Many of you who are using Agile PLM together with SAP already have an integration in place. Deciding what enterprise objects to synchronize between the systems is typically very simple in phase 1 of your implementation. It normally is Parts, Bill of Materials and the Changes, which are stored as Material, Material BOM and Engineering Change Master in the SAP system. There may be some detail discussion on where resides the master, which means where do you enter and modify e.g. a part or part attribute, but that can be resolved very quickly by mapping the objects and attributes of both systems in a spreadsheet and agree where you want maintain what. This sort of "controlled redundancy" allows you then to (normally) create these objects in PLM and push them to SAP once they are "mature" enough or needs processing in SAP. [Read More]

Monday Sep 22, 2008

Storing outbound compliance information in PGC

You obviously know that you can use a Declaration to gather compliance information from your suppliers. Those are inbound Declarations where the data is submitted by Suppliers or content providers. But, did you know you can also use a Declaration for storing "outbound" compliance to be shared with your Customers? In PLM's release, you can make use of the attribute Exclude from Compliance Check in Declaration-Items or Declaration-Mfr Parts or Declaration-Part Groups tabs. This is a list field with values of "Yes" and "No" and the purpose of this field is to use for "outbound" Declarations. Note that this is different from the Exclude from Rollup flag in the cover page of an Item. The Exclude from Rollup field flags the entire Item to be excluded from compliance rollup, while the Exclude from Compliance Check flags just that particular Declaration/Composition to be excluded from compliance rollup. Here are the steps you can follow to create an "outbound" Declaration:[Read More]

Sunday Sep 21, 2008

BI Publisher licensing options for Agile PLM

In Agile PLM 9224 release, we added the Business Intelligence (BI) Publisher reporting framework, which enables our customers to customize their PLM reports. This post is intended to provide more clarity on the BI Publisher restricted and full licensing options for Agile PLM customers. Oracle Business Intelligence Publisher (BI Publisher) is an enterprise reporting solution to author, manage, and deliver all types of highly formatted documents. Developers can create data models against practically any data source and use BI Publisher APIs to build custom applications. End users can easily design report layouts using familiar desktop tools, dramatically reducing the time and cost needed to develop and maintain reports Click on the following URL for details: [Read More]

Where do I find Agile PLM Platform certification matrix?

[Read More]

Thursday Sep 18, 2008

Collaborating with Suppliers

“No bird soars too high if he soars on his own wings.” – William Blake Fellow blogger Laila Herr underscores the significance of collaboration in the PLM process. At Oracle Agile PLM, we have been focused on this aspect from the very beginning (no wonder that one of the pillars of our PLM solution is called "Product Collaboration"). The very popular Cimmetry viewer enables engineers to collaborate within the enterprise, as well as outside of it with suppliers and customers on product design models. At the upcoming Oracle Openworld, I'll be presenting with fellow product manager Shane Goodwin, and a long time Agile PLM customer, Quantum, on our features around securely collaborating with suppliers.[Read More]

Wednesday Sep 17, 2008

CAD and the New Part Request process

One of our goals with the Agile Engineering Collaboration product is to support the process needs of CAD users as simply and unobtrusively as possible. The challenge is to also support the necessary flexibility to accommodate different company's processes without requiring extensive customization. [Read More]

Getting what you want from AutoVue

Have you ever been frustrated trying to bring the right files from Agile into AutoVue for viewing? Starting with Agile PLM release we have been working to improve the usability of the AutoVue integration, especially the ways in which you access files. [Read More]

Tuesday Sep 16, 2008

Where did we place our Agile PLM Software?

Since Agile was purchased by Oracle last year, the download location of our documentation and software has merged into the Oracle system. We are now using Oracle Edelivery, Oracle Technology Network, and Metalink. Continue reading to better understand when we are using the different Oracle locations, including the location for Agile PLM[Read More]

Monday Sep 15, 2008

How do you lock down Item privileges based on the Change Order Status in Agile PLM?

Often our customers are looking for additional means to restrict Read or Modify privileges on an Item based on the status of related Changes. For example, file attachment checkin may need to be allowed for pending revisions of items only as long as the corresponding ECO is in authoring mode ("Pending" status), but not once the ECO gets submitted or routed. Before Agile PLM, achieving the desired business result could be complicated. Now, Agile PLM has some very powerful capabilities to write Criteria against an Item that checks the related Change status. The enhanced functionality around variables such as $CURRENTREV and $LATESTREV can help Agile Administrators write criteria that meet business goals to limit Item Read or Modify privileges.[Read More]

Wednesday Sep 10, 2008

Agile Configuration Propagation - ACP

For a long time we heard from customers, partners and consultants in one voice - "give us a comprehensive configuration export-import solution”. Regardless of the fact that we had selective export and import of configuration in Java Client, we found the plea very compelling and loud enough. Yes, we listened and understood the persuasive reason for a nurtured solution to accomplish the same at a larger scale. We mixed it until no lumps, baked it long enough, packaged it (January 7th ’08) and called it Agile Configuration Propagation aka ACP. [Read More]

Monday Sep 08, 2008

Configuring attributes between Items and Sourcing Projects

Have you come across cases where certain fields that show up in an Item's Page Two doesn't show in a Sourcing Project? That could be related to some of the attributes not been mapped correctly between Product Collaboration and Sourcing Project. In PC's Items & Manufacturer Parts, customers could categorize their data using unlimited number of fields in Page Two. When items and mfr parts are added to a Sourcing Project for costing purposes, not all these fields would be relevant to the sourcing manager and so, the ability to configure what attributes should show up in the Sourcing Project becomes important. PCM supports the "mapping" functionality wherein, you can setup a "mapping" between a field in Item-Page Two tab and a field in Project-Items tab. The purpose of establishing a mapping between 2 fields is to ensure that a field in Project-Items tab displays the same value as in a field in Item-Page Two. For instance, if you have a Last Paid Cost field (or some kind of standard cost) defined in Page Two of an Item in PC, you can map the same cost field into the Standard Cost field in the Sourcing Project to enable the sourcing manager make informed decisions. At a high level, follow the simple steps below if you want to map a specific field from PC to Sourcing Project: 1. Identify the field in Item-Page Two or MfrPart-Page Two that you want to see in the Sourcing Project and make sure it is visible. 2. Identify the field in Sourcing Project-Items tab or Project-MfrParts tab that you want to see the value from PC-Page Two and setup the mapping. 3. Enable the corresponding field in Project-Analysis tab and RFQ-Responses tab and follow consistent naming. Let's look at the process in more detail:[Read More]

Smart URLs - enabling reference to Agile objects from external systems

Are they as smart as they look? Judge for yourself (and let me know what you think too). In Agile 9.2.2 and earlier versions, while the system allowed a user to generate a URL for an object, the generated URL was rather cryptic. For example, here's a sample URL for part P0001: Furthermore, the only way to generate a URL pointing to an Agile object was through Agile. With Agile, any Agile object can be linked to using a URL in the following format: [Read More]

Hear from the community that's pioneering PLM's critical role in transforming supply chains into sustainable value chains that power profitable innovation and competitive advantage.

Subscribe to Oracle Agile PLM Blog by Email


« June 2016