What’s New With Arbortext for S1000D
Arbortext for S1000D 4.4 offers new integrations with Windchill PDMLink, product usability improvements and a workflow API.
Arbortext for S1000D 4.4, scheduled for release in March 2011, offers several product usability improvements including the ability to produce a parts list using Windchill BOM data, Windchill-driven compilation, a new workflow API for integration with PLM workflows, and additional compliancy with the S1000D and S2000M standards. Here is a high level overview of all of the updates you can look forward to in Arbortext for S1000D 4.4:
Arbortext for S1000D and Windchill-driven compilation for Parts Lists
The new Windchill-driven compilation capability in Arbortext Parts Catalog Manager & Arbortext Provisioning Manager software allows users to select parts directly from Windchill design or manufacturing data and repurpose that information for use in either an S1000D parts list or an S2000M deliverable. Additionally, by creating a link between the design source and a parts list, customers can very quickly determine the impact of a design change on the associated publications by using the new design change impact report. This capability will improve the accuracy and reduce the time for planning and updating technical information.
Key features:Capability to interrogate product hierarchy within Windchill
- The main Windchill-driven compilation view gives visibility to the source of the design data, not tied to a single source of data, this can be design, manufacturing or service information.
- Allowing an up to the minute representation of the component build.
- The method in which the data is extracted, allows the user to identify the hierarchical structure of the components, with the added advantage of when viewing the data will see immediately when any of the components status as changed
- The Windchill-driven compilation view indicates which components have been used in the compilation window or previously linked to the illustrated parts catalog (IPC)
- Parts associated with a design change.
- These trigger events produce a list of assemblies affected by the design change.
- The change event and the subsequent impact information can be used to initiate a change workflow.
- Establishing a link between design data and its “as supported” parts list enables the derivation of potential required changes to other publication objects.
- Modules are ultimately used in a publication. Once the modules are known then it is easy to derive which publications contain the affected modules.
Deliver workflow API for integration with PLM workflows
In the 4.4 release, any workflow engine capable of calling an API can be used to control a data module’s status and there are features in the API aimed at getting information from the CSDB for status reporting to help track the progress of technical information development.
- Manage a modules status throughout its lifecycle
- Integrating a workflow engine allows the engine to set the status of a module when it reaches a particular decision/event in the workflow
- Control module authoring status using custom workflow
- Manage module production and QA using existing business practice
- Monitor Module Status
- Listed are the potential primary status’ within the CSDB. It is not expected that these values will be added to. However, the CSDB has a tertiary status for each module that is not currently used.
- PROPOSED – Request to include DM in CSDB from LSA/Provisioning Manager
- PENDING – In CSDB but no work carried out
- WIP – Module in process of being authored
- QA REQUIRED – Module in QA
- REWORK REQUIRED – DM Failed QA
- ISSUED – DM Passed QA
- DELIVERED – DM included in Publication of sent via interchange
- CSDB workflow and status change
- Module status changes can initiate multiple backend processes.
- For example, setting the status to ISSUED requires the update of verification information, the changing of the issue number and resetting the in-work value.
- Capabilities include creation, up issuing, QA cycle management and issuing of data modules.
Improve compliancy with S1000D / S2000M standard
- Multiple Reason for Update (RFU) Support
- Support Material Item Category Code in SNS Structure Libraries
- Introducing templates for common structures and copy/paste with PDME
- Improved search with IETP
- Entity Where Used – support for Slave Modules in addition to Master Modules
- Support for PCT Applicability
- User interface enhancements for Arbortext Provisioning Manager for S1000D
- Improved Container Data Module Support
- Support for other standards and customizations of S1000D
- Authoring Tool Interface
- Make it customization of Arbortext Editor rather than stand alone plug-in
- Use Arbortext Editor and IsoView/Draw integration for hotspot insertion into modules
- Link to new CSDB API for improved analysis reporting (BREX/Ref DM checks)
- Support for Arbortext Editor 6.0 in Arbortext for S1000D 4.4 M010 release