PSA, Inc. is excited to announce that Donald Nagel, GS&S PLM Engineering Functional Skills Manager, from The Boeing Company will be presenting Managing Hardware Engineering Changes Throughout The Product Process With CMPRO on Tuesday, May 22 at 10:45. 

The detailed agenda with dates and times is now available. View it here.

Register today at www.regonline.com/cmpro2012.

The agenda is now finalized!

The Fundamentals User Track, led by John Cope and Gary Gunter, will include:

• Browser Prep, Connecting, Navigation, and Searching
• Working with Workflow Docs
• Document Repository
• Drawing Repository
• Messaging and Polling, User Defined Groups
• Share Spaces
• Software Repository
• Inventory

The Reviews feature in CMPRO provides a process in which participants can offer formal and detailed assessment of a workflow record. Any workflow enabled document type such as documents, drawings, or software that are controlled by change documents (i.e. DOCCN, DCN, or SOFTCN) can be evaluated using the Review tool.

Reviews can influence whether a workflow item continues forward in the route, or is returned for correction of the issue(s) raised. When an issue is raised as part of a submitted Review response, resolution of the issue becomes a necessary part of bringing that Review to completion.

Review and response data can be compiled as summary reports in tabular and graphical formats, and can also be included when printing workflow documentation via standard printing options. Reviews can be accessed from the workflow document’s detail screen by using the Reviews link in the Additional Data section of the left pane.

Review Process in CMPRO

A Review in CMPRO goes through the following process:

• Creating the review
• Getting responses (responding to the review)
• Working the responses
• Completing or Canceling the review

Creating a Review

If the workflow document does not already have a review in progress, the Create Review icon is available for selection in the Additional Data section of the workflow record’s detail screen. Optionally, once the Reviews link is clicked, the Reviews screen is displayed, and the Create Review link can be selected to create a new review.

Rules about creating a Review:

• Only one active review is allowed against a workflow document. A new review cannot be created while an existing review is open (i.e. neither completed nor canceled).
• A review can only be created for workflow documents that have not been canceled or released. Not even an administrator can create a review on a workflow document that has been previously canceled or released.
• The individual creating a review must either be an administrator or the owner of the workflow document for which the review is created.

Note: Once created, a Review may be reassigned to a Review Lead. This individual does not have to be an administrator or the owner of the workflow record to fully conduct all aspects of the review.

Select either the Create icon or the link to access the Review Create screen. Fill out the required fields (with a yellow background). Reviewers can be copied from a previous review with the List link next to the Copy Reviewers from field.

After the fields are completed, select the Create Review button to display the Review Detail screen. From this screen, Reviewers can be added individually or from User Defined Groups (UDG).

Select Reviewers from a UDG with the Add Reviewers from UDGs link. A list of groups will be displayed with links (when clicked, displays the members of the group) and check boxes to add a group(s). After groups have been selected using the check boxes, click on the Add Reviewer(s) button at the bottom of the screen.

Once the Reviewers have been added, the numbers in the Response Summary section of the Review Detail screen will be updated.

The numbers in this section represent:

• Reviewers – The numbers shown here are represented by the letters T:N:H, where T is the total number of reviewers; N is the number of reviewers who have not selected a response for any response record (a single reviewer can have multiple responses); and H is the number of reviewers who have selected a response for at least one response record.
• Responses - The numbers shown here are represented by the letters T:P:G, where T is the total number of response records for all reviewers; P is the number of response records with a response Selection Pending (no response); and G is the number of response records that have been selected and saved (i.e. submitted).
• Resolutions – The numbers shown here are represented by the letters T:P:F, where T is the total number of all response records that represent issues or which are provisional acceptances; P is the number of response records where the response value is Issue Identified or Provisionally Accepted and where the resolved and verification dates are both blank; and F is the number of response records where the response value is Issue Identified or Provisionally Accepted and where the resolved and verification dates are both filled in.

After individuals selected to participate as reviewers have been notified via e-mail, responses are collected. The Review is considered In-Review.

Responding to Reviews

In addition to the e-mail notification, there is a My Reviews widget on the Home screen that provides status for the reviews a user is currently participating in. The My Reviews screen displays the Response Pending (RP) and Response Given (RG) for reviews participated in and the RP and RG for reviews in which a user is acting as Review Lead.

Select the appropriate Review Number to access the Review Detail screen. In the Response Summary section of the screen, information is included describing your participation in the review, including whether or not you have provided a response. A link is also available to provide or edit a response.

The link provided to view your response displays the Review Response Detail screen. This screen includes the following fields:

• Response – A response must be selected from the drop-down list that includes the values of Accepted, Waived, Rejected, Issue Identified, or Provisionally Accepted. If a value of Issue Identified is selected, the Issue Type, Issue Origin, Issue Category, and Issue Location fields become visible and must be completed. The values in the drop-down list fields are determined by site administrators and are designed to add specific details to the issue identified.
• Remarks – An open text field used to give remarks on the review.  This field is required if the selected Response is Rejected or Provisionally Accepted.
• Review Time Spent (Hours) – An open number field for the reviewer to document the time it took (in hours) to review the document. Depending on the site, this field may be required.
• Multiple Occurrences – This Yes/No field indicates whether or not an issue occurs multiple times in the item being reviewed. The Remarks section should be used to provide supporting details.

Note: If an administrator is viewing the screen an additional option of Not Provided is given in the Response field. This is used to reset a response entry.

After the information in the fields is provided and the changes saved, select the Submit this Response link next to the Submitted By / Date field.

Note: Changes may be saved without the response being submitted (submitting the response provides e-mail notification to the record’s owner and/or the Review Lead). Also note that the same reviewer can later submit additional responses.

As the responses are submitted, the Response Summary section of the Review Detail screen automatically updates to reflect the responses.

Optionally Review Responses can be reassigned to other users by the associated review lead, the current owner of the workflow document for which a review was created, or an administrative user.  To reassign a Review Response click on the Reassign link next to the Reviewer field. This action is recorded in the system log of the associated review.

Click on the Reassign link to display a pop-up window to select the next reviewer.

The Review Lead can work the responses at any time during the review process, although it’s common to wait until all reviewers have provided a response.

Working the Responses

A workflow record can move forward on a route when a Review is still open. This is possible even when issues have been identified. As long as the workflow document is not canceled or released, the Review will remain open. At any time, the Review Lead, document owner, or administrator may select the Work Responses to place a Review into the IN-WORK phase, allowing existing responses to be resolved and verified, as required. During this phase of the review, reviewers can no longer update existing responses or create new ones.

View the responses with the Review All Responses link in the Review Options or Response Summary section of the Review Detail screen. Select the View link next to the response to be worked.

The Review Response Detail screen is displayed, where the owner can assign the response to another user for resolution, and also indicate whether or not the response has been Validated (Yes/No) or Discussed (Yes/No). Additional text can be added in the Resolution field to describe the details of the resolution, if necessary. After the changes are saved, the issue can be marked resolved by the Mark Resolved link in the Resolved By / Date field.

After the response is marked Resolved, the Resolution Verification section will be active on the screen where the time spent on verification can be reported.

After hours are entered and changes are saved, the Mark Verified link becomes active. Click on the Mark Verified link to finish the Work Responses process.

Finishing Reviews

Once all issues have been resolved and verified, the review can be completed using the Complete Review button in the Review Control section of the Review Detail screen.  A review can also be canceled at any time using the Cancel Review button in the same section.

Note: A review can only be completed or canceled by: an administrator, the owner of the workflow document for which the review was created, or the Review Lead.

To complete the review, a reason for the Final Decision must be selected from the drop-down list.  This can be either Accepted (the item being reviewed is acceptable to act on or use) or Rejected (the item being reviewed is not acceptable to act on or use).  There is also a text box available to provide Final Review Comments.

The status will be displayed in the Review Control section of the Review Detail screen.

Searching Review Responses

The Review Response Search screen allows users to search, view, and export information about review responses. This assists reviewers in finding out what issues (or other feedback) may have been identified by others during a review process, and helps prevent duplication of effort. The Review Response Search screen can be accessed from the Review Detail, Review Response Detail, and the Review Response screens.

Printing and Reporting Reviews

Review and review response data is now a part of the workflow document printing options, allowing the charts and specific response data to be included in the printing package. To print all or part of a workflow document’s data access the Print link in the Additional Options section in the left pane of the detail screen.

Check the boxes next to the information to be printed and select the Print button.

The information will be delivered in a PDF through the Internet browser.

A reporting option for reviews is the Review screen, displaying a summary of the review data. This screen can be accessed through the Reviews link in the Additional Data section in the left pane of the workflow document screen.

Conclusion

Reviews offer a formalized process for reviewing workflow documents and repository items (documents, drawings, and released software) in CMPRO. This is another feature added on to the functionality of CMPRO to allow users to be more effective through collaboration.

For more complete coverage of the details involved in the creation and management of a Review in CMPRO, please refer to the Reviews topic in the online User’s Guide.

• Reviews
• Checklists
• Contracts and Contract Tasks
• Process Workflow Engine Routing

As the features and modules are covered, the list will contain links so that you can easily navigate content.

If there are any additional modules that you would like to see included in this series, please contact us with your request.

• The Enterprise Change Management (ECM) approach as defined by the Institute of Configuration Management (ICM).
• The Department of Defense (DoD) Change Management (DCM) approach as utilized by many U.S. military programs (this process was previously formalized as MIL-STD-973).

CMPRO provides processes and electronic forms to accommodate both the ECM and DCM approach to configuration status accounting.

The Enterprise Change Management (ECM) Approach

The ECM approach is based on the guidance and practices set forth by ICM. Product baselines are used to provide overall monitoring and status of the changes that are tied to a particular product. CMPRO uses the following workflow-enabled electronic forms to facilitate ECM:

• Enterprise Problem Report (E-PR) and Enterprise Software Problem Report (E-SPR) – accommodates identifying, reporting on, and analyzing potential issues.
• Enterprise Change Request (E-CR) – provides a way for changes to formally be requested and evaluated from a cost, scope, and feasibility perspective.
• Enterprise Change Notice (E-CN) – provides a way for approved changes to be scheduled and implemented.

Enterprise Change Management forms flow and feed data in this order: E-PR/E-SPR > E-CR > E-CN. For a simple change, problem reports (either engineering or software) and change requests can be skipped with only an E-CN being used to implement the change.  In more complex situations, one or more E-PRs (problem report) can generate one or more E-CRs; and one or more E-CRs can generate one or more E-CNs (change notices). The number of change documents required depends on the nature of the changes and how they need to be reviewed and managed.

Enterprise Problem Report (E-PR/E-SPR)

The E-PR is used to document a reported problem. This form provides supporting information and assists in determining if a problem exists that may require a change. CMPRO workflow is used to route the E-PR to the appropriate reviewers. The Enterprise Software Problem Report (E-SPR) is available to track software-specific problem reports and contains fields that pertain specifically to software issues.

Both the E-PR and the E-SPR are located in the Hardware Configuration Management section of the Menu.

The E-PR Detail screen provides several fields to document a problem:

• Remarks – use this section to enter any general remarks that may be helpful in determining the course of action.
• Application Environment – use this section to describe how this item or product is used and why this problem affects the application of the item or product.
• Sequence of Events Leading Up to the Problem – this area should provide a step-by-step process that was followed, resulting in the issue that is being reported.  This detail will be used by technical support to try to replicate the issue and to determine the proper course of action.
• Recommended Solution – provided by either the helpdesk resource or by technical support.  The recommendation is provided as input to help determine a course of action with regards to the problem being reported.

The Associated E-CR(s) w/ E-CN(s) section in the right pane of the E-PR Detail screen displays the change request and change notice associated with the problem report.

Enterprise Change Request (E-CR)

The Enterprise Change Request (E-CR) form is used to gather data and route the proposed change for review and comment. The ultimate goal of the E-CR is to obtain a business case approval for the change request, either as a fast track change or by approval from a Change Review Board (CRB).

An E-CR is similar to the DoD Engineering Change Proposal (ECP) and its related process except that the E-CR is a one-page preliminary ECP.  However, where the ECP attempts to contain and manage data within a single seven-page form, the E-CR if approved generates one or more E-CNs, depending on the scope of the change.

Impact Matrix

The Impact Matrix is an important part of any E-CR because it provides a list of the parts, drawings, documents, and software that are potentially impacted by the change. The View Matrix link in the left pane of the E-CR Detail screen displays the E-CR Impact Matrix.

The E-CR Impact Matrix screen provides a method for identifying the elements that are impacted by the change  (including new and deleted items). Only the components affected by the change are listed. For example, if only one part is affected on a parts list, then items included on the Impact Matrix are:

• The changing part and superseding part if applicable.
• The drawing containing the parts list.
• Any associated documents or software release records from the appropriate baseline.
• Any new parts, drawings, documents, or software releases.

The Build Matrix from Baseline link in the left pane of the E-CR Detail screen starts the process of building an E-CR Impact Matrix from a Product Baseline.

After selecting items to include in the impact matrix, the Build Impact Matrix link displays the E-CR Impact Matrix screen.

Enterprise Change Notice (E-CN)

The Enterprise Change Notice (E-CN) provides the authority to schedule, revise, and release documents..  E-PRs and/or E-CRs usually precede an E-CN, but are not required. E-PRs and E-CRs may be omitted if the change is simple or needs to be implemented quickly (commonly referred to as a “fast track” change).

When an E-CN is created from one or more E-CRs, items from the impact matrices are copied and merged into the Document Change Schedule.  An approved and released E-CN provides the authorization to create and revise the items listed in the Document Change Schedule.  Components listed on the E-CR Impact Matrix have scheduled dates listed in the right pane of the E-CN Detail screen in the Document Change Schedule section.

A typical E-CN process includes a Change Implementation Board (CIB) that plans the implementation of the approved changes tied to the E-CN. Part of the implementation planning process involves providing a date in the Effective Date field for all changes. Once the Effective Date and Required By Date fields are identified, the document revision work can be planned.

The Effective Date field is critical when building a product baseline in CMPRO. When a product baseline is produced with the Product Baseline module, CMPRO builds it—based on the part structure from the released parts list—using the Effective Date. The Product Baseline captures the parts, drawings, and associated documents required in the product structure. Learn more about the Product Baseline module in the Baseline newsletter.

Enterprise Reports

The Enterprise Reports screen facilitates early detection of schedule problems. The data is linked by contract / task number which, together with the product baseline, determines the required by date that all engineering should be released by.

To find the Enterprise Reports link search for “enterprise” in the Menu. The Enterprise Reports screen provides reporting options for:

• E-CR Advanced Options Report –parameters can be set for E-CN No, Disposition Status, Originator, Priority, CN Date, and/or Release Date.
• E-CR Under Review – parameters can be set for Contract, Task, System, and/or Subsystem.
• E-CR Rejected – parameters can be set for Contract, Task, System and/or Subsystem.
• E-CR Approved – parameters can be set for Contract, Task, System and/or Subsystem.
• E-CN Advanced Options Report – parameters can be set for E-CN No, Disposition Status, Originator, Priority, CN Date, and/or Release Date.
• E-CN Contract / Task – parameters can be set for Contract, Task, System, and/or Subsystem.
• E-CN Currently Pending – parameters can be set for Contract, Task, System, and/or Subsystem.
• Document Scheduled by Contract / Task – parameters can be set for Contract and/or Task.
• Document Schedule Statistics – parameters can be set for Contract, Task, and Date Range –Start Date and/or Date Range – End Date.
• E-CN In-Progress – parameters can be set for Contract, Task, System and/or Subsystem.
• E-CN Dashboard – parameters can be set for Product Baseline.

The Department of Defense (DoD) Change Management (DCM) Approach

The DoD Change Management (DCM) approach is based on the standard previously formalized as MIL-STD-973, which is still widely used in the DoD today. DCM is available in CMPRO, with a few enhancements, using the following workflow-enabled electronic forms:

• Issue Report (IR) – a CMPRO-specific DCM enhancement provides a way for potential issues to be identified, reported, and analyzed.
• Advance Change Study Notice (ACSN) – supports the formal study of potential changes.
• Engineering Change Proposal (ECP) – provides a way for changes to be formally requested and evaluated from a cost, scope, and feasibility perspective.
• Implementation Directive (ID) – a CMPRO-specific DCM enhancement, facilitates the scheduling and implementation of approved ECPs.

Note: For U.S. Navy customers in the SPAWAR organization, the full SPAWAR Enterprise Change Report (SPAWAR ECR) is available for online automation. The SPAWAR ECR replaces the ECP-centric change process for SPAWAR customers.

Note: For U.S. Navy customers, the Configuration Item (APL) module supports tracking Allowance Parts Lists (APL) information as it pertains to Engineering Baselines in CMPRO.

The forms for the DCM approach in CMPRO support the pages and functionality required by the DoD and include features to aid in package creation, tracking, printing and status reporting. Additionally, full reporting on all of the form fields and related data elements are provided.

Engineering Change Proposal (ECP)

The ECP Detail screen fits the functionality of an engineering change proposal as originally specified by MIL-STD-973.

 SPAWAR ECR

The SPAWAR ECR Detail screen supports the specifications of the PEO C4I Lifecycle Configuration Control Implementation Manual (LCCMIM). The SPAWAR ECR function includes the full CMPRO workflow functionality and integration with the Repositories and Baseline modules.

Waivers / Deviations

The WD Detail screen provides the Waiver / Deviation functionality as originally specified by MIL-STD-973.

System Technical Data List

The System Technical Data List module provides a method to search, view, and report on the current documentation list for a selected system. All repository documents, workflow documents, and other pertinent data records are included in the report.

Workflow and Change Management

Part of the strength of CMPRO’s Product Lifecycle Management process is in its workflow and collaborative environment.  Electronic forms are routed through users and teams; gathering electronic approvals, comments, and supporting files, as required by the specific review and approval processes.

The following graph illustrates the process a typical E-CR follows.

Conclusion

Configuration Status Accounting with CMPRO accommodates the Enterprise Change Management and DoD Change Management approaches and integrates with the PLM process partly through metrics and statuses displayed on the Disposition and Program Dashboards.

Using CMPRO for PLM is accomplished with integrated modules that provide the means for various departments and workgroups to function together more effectively.

This newsletter concludes the How to Use CMPRO for PLM newsletter series:

• Contracts and Contract Tasks
• Projects and Tasks
• Drawings, Documents and Software Release Repositories
• Baselines
• Product Definitions – Part Trees / BOMs
• Inventory
• Work Orders & Work Instructions
• Non-Conformance
• Requisitions
• As-Built
• Configuration Status Accounting (CSA)

For more information on how to implement any the above functionalities at your site, please contact your CMPRO Systems Analyst.

CMPROficiency+ 2012 will be held May 22 – 24, 2012 in Panama City Beach, FL. This event provides attendees with valuable information on how to proficiently use CMPRO for Product Lifecycle Management (PLM) and Configuration Management (CM), including all the associated processes that CMPRO helps automate and manage. The format for this training event includes a “full group” session for new CMPRO topics, a CMPRO Lab, and multi-track sessions for administrators, fundamental users, and advanced users…read more.

As multiple quantities of an end-item are built and deployed, it is critical to have a method for tracking the location of those end-items, and the final configuration at the time of deployment. The As-Built module offers insight into the original configuration and any changes that were made to that configuration over time.

As-Built Baselines are used to create Bill of Material (BOM) templates for product-based applications. Those templates are used in the process of fabricating the product.

Some modules interact with the As-Built module for generating and maintaining kit templates that are built to satisfy customer orders.

As-Built Module

The As-Built module tracks end-items by location (platform and physical placement).  Other important information available through the As-Built module includes:

• Part validation
• Drawing information necessary to build the end-item
• Cost to manufacture
• Warranty information
• Tracking number/UID
• Prescribed elements required to create an end-item
• Actual components installed on the end-item
• Where the end-item is used
• Current and historical location information for the end-item
• Calibration history
• Repair Order history

Note: A Platform represents where a product (system) can be deployed. Examples of platforms include: ships, planes, buildings and sites.

Note: A location includes the platform and the physical place in or on a platform where a product (system) is located.  Examples of locations include: deck, wing, cabinet, closet, and main warehouse.

To view an As-Built item, click on the As-Built link in the Menu.

Conduct the search by entering the appropriate parameters to limit the results and then click on the desired link to display the As Built Part Detail screen.

Among other useful data fields included on the screen, the As-Built part’s current location and platform, location history, serial number, and components can be viewed. The As-Built Options section in the left pane of the screen contains links to edit the location information and other details of the part.

To change the location of an As-Built item click on the Change Location link in the As-Built Options section in the left pane of the screen. The As-Built Change Location screen will appear where the platform, location, owner and/or status can be changed. Use the List link next to the fields to be changed to pick from a validated list of values.

Once the location field has been changed, the end-item’s location history is included on the As-Built Detail screen.

The components of an As-Built end-item can be viewed on the As-Built Detail screen in the Components section or by clicking on the End Item Component List link in the As-Built Options section of the Detail screen’s left pane.

The Where Used Search link in the As-Built Options section in the left pane opens the As-Built Where Used Search screen. Enter the parameters for the search to display where the part is used across all the parts list information stored in CMPRO. To view a list of the end items the part is used on, click on the View link under the End Item(s) Where Used column.

As-Built Baseline

An As-Built Baseline provides a means to record the part numbers and serial numbers for a configuration that will be manufactured repetitively. The As-Built Baseline tracks components that are critical to the end-item, so minor consumables such as washers, nuts and screws are not listed in the baseline.

Creating an As-Built Baseline

Create an As-Built Baseline by starting with the top-level assembly. After the top-level assembly is added to the baseline, subordinate parts can be added and related to the top-level part.

To create the top-level assembly, click the Create As-Built Baseline link either from the Menu or As-Built Baseline Search screen.

The Create As-Built Baseline screen will be displayed. All fields with a yellow background are required.

Enter all of the required information:

1. Baseline No – User defined baseline number. This number is listed on every component of the baseline for identification purposes.
2. Part No - The top-level assembly part number can be found by using the links to the right of the field.
3. Part Nomen – A descriptive name for the part.
4. Control Group – Used to define who has access to the baseline and what actions individual users within that group can perform.
5. Qty – The quantity of this part that is used to build the As-Built assembly.
6. Proprietary Group – Controls who is able to see a record. Only individuals assigned to the same proprietary group to which the record is assigned will be able to view it or work with it in any way.
7. Click the Create As-Built Baseline button to continue.

On the As-Built Baseline screen subordinate parts that are critical to the end item should be added and associated to the top-level assembly.

Copying an As-Built Baseline

An As-Built Baseline can be copied and used as a starting point for a new baseline. Start this process by accessing the existing baseline to be copied by performing an As-Built Baseline Search.

On the As-Built Baseline screen select the Copy As-Built Baseline link.

Enter information in the required fields of the Copy As-Built Baseline screen.

Note: Either the Baseline No or the Part No must be different than the baseline that is being copied.

After all of the yellow fields are completed click on the Copy As-Built Baseline button and the new baseline will open.

Editing an As-Built Baseline

The individual components of an As-Built Baseline can be edited to reflect information specific to that item, for example the serial number. To edit any record in an As-Built Baseline, click the Edit link to the left of the part number to be edited.

The As-Built Baseline Detail screen for that part entry will be displayed where the part information can be edited.

Deleting All or Part of an As-Built Baseline

An As-Built Baseline and all subordinate parts can be deleted by selecting the Delete As-Built Baseline link. Individual subordinate parts can be deleted from an As-Built Baseline by selecting the check box next to the Part No and clicking the Save and Delete button.

Conclusion

The As-Built module in CMPRO extends the PLM process by providing the tools necessary to ensure accurate assembly of As-Built end items and the means to track those items once they have been deployed.

In This Issue

CMPROficiency+ 2012 Date and Location Announced

CMPROficiency+ 2012 will be held at the Edgewater Beach Resort in Panama City Beach, Florida May 22 – 24. This year’s layout for the user event includes three tracks for different user types: Administrators, Advanced, and Fundamental users…read more.

PSA, Inc. Presented at the Configuration Management Process Improvement Center (CMPIC) Conference – CM Trends 2011

Professional Systems Associates, Inc. exhibited its product lifecycle management tool and presented PLM Process Automation at the CM Trends Conference in Orlando, Florida. The CM Trends conference is geared to share configuration management practices, tools and processes to configuration management professionals…read more.

PSA at the 24th Annual CMII Conference

Product lifecycle management (PLM) tool CMPRO was exhibited and discussed at the Institute of Configuration Management’s (ICM) 24th Annual Conference in Las Vegas, NV October 3-4, 2011…read more.

Thank you for your interest in CMPRO. If you would like to receive a paper copy of this newsletter please contact us with your mailing information.

Download PDF Version of Newsletter

Requisitions

Requisitions support multiple line items and use the standard CMPRO workflow. When line items have the Link to Inventory set to “Yes”, the line item is linked with the Inventory module, and additional functionality is activated.

Note: The Inv. Req. Multi Detail screen will limit the creation of line items based on the budget entered on the Project Task.

Note: Inventory Functions and Permissions apply. Users must have Inventory Permissions, be in the Inventory Subgroup of the record being received, and must have the functions to be able to use the Inventory module.

Creating a Requisition

Note: Inventory Requisitions are workflow documents. In order to create an Inventory Requisition, the user must have permission to create on at least one workflow route that is assigned to Req. Master.

Click on the Inv. Req. Multi Create link in the Inventory and Production Management section of the Menu to create a Requisition.

The Inv. Req. Multi Create screen contains several required fields (with a yellow background) that need to be populated before the requisition is created.

The required fields for creating a requisition in CMPRO are:

1. Enter any Description for the requisition. This field can be used to identify the reason this requisition is being opened or to indicate what this requisition is supporting.
2. In the Req. Del Date enter the date by which the items need to be received.
3. Choose the Default Subgroup for when items are received. This refers to the inventory subgroup (as described in the Inventory Module newsletter).
4. The Req. Status indicates the current status of the requisition. Available statuses are:
   • Draft (the default value)
   • B/O (back ordered)
   • Cancel (cancels the requisition)
   • Com (complete) The Req. Status will automatically change to this value when all items have been received.
   • Ord (ordered)
5. The Requisitioner and Phone fields are automatically populated with the user’s information that is creating the requisition.
6. The Priority field is assigned to rank the urgency of this requisition in relation to other requisitions that are in process.
7. Select the Folder from the drop down list of values. This alias points to a location on a server where any attached electronic files will be stored.
8. Select the Proprietary Group from the drop down list of values. Proprietary Group helps control who is able to see a record, only individuals assigned to the same proprietary group to which the record is assigned will be able to view it or work with it in any way.
9. Select the Workflow Route from the drop down list of values. The route chosen will determine the signatures necessary for the Requisition to be approved.

When all of the required fields are completed, click on Create Req. Multi to display the Req. Multi Detail screen. From this screen add line items to the requisition by clicking on the Add Line Item link in the Link Options section on the left side of the screen or the Line Items section on the right side of the screen.

Click on the Add Line Items link to display the Req. Multi Line Item Create screen. Enter the information in the fields (yellow fields are required) to create a line item.

Inventory Requisitions can be created for items that are listed in the Part Master, the Inventory Master or the Product Definition Master (PDM). Once the item being purchased is selected, the pertinent information is retrieved and populated on the requisition.

After entering the quantity to purchase, the line item total cost is automatically calculated.

The Inventory Requisition Line Item can be tied out to the drawing that uses the part by entering the drawing and revision information in the fields Ref Dwg Number; Ref Dwg Rev and Ref Dwg Type.

Link the line item to a Project and Task in CMPRO by entering the Charge Number and Contract Task Number on the Req. Multi Line Item Create screen. If the Charge Number is used, CMPRO will compare the Line Total to the remaining balance on the Task. If there are insufficient funds for the item a warning message will appear informing the user of such. CMPRO will not save and add the item to the requisition unless sufficient funds are available on the charge number that is listed.

Work Order BOM lines can be referenced to the line item using the ID number that was entered on the Work Order Bill of Materials.

Receiving Requisition Items

Receive requisition items by accessing the Inv. Req. Multi Receive screen from the requisition by using the Receive Items link in the Link Options section in the left pane or from the Menu using the Inv. Req. Multi Receive link. The advantage of entering from the requisition is that the items being received will automatically be linked to the requisition.

To receive items complete the steps on the Inv. Req. Multi Receive screen and click on the Receive button.

Work Orders

Work Orders in CMPRO can be used to create Requisitions from the Buy List of the Work Order. View the Buy List from the Work Order Detail screen by clicking on the Order Status link in the Part BOM section of the screen.

Create Requisitions by checking the boxes next to the items and clicking on the Create Requisition from Line Items link to open the Multi Req. Line Item Create screen. The Requisition can then be created following the steps above.

Conclusion

The Requisition functionality in CMPRO links the Inventory module to the Contracts and Tasks, Projects and Tasks, Product Definitions – Part Trees, Work Orders & Work Instructions and Non-Conformance Modules. This assists in the product lifecycle management (PLM) process by linking all of the information about an Inventory item to the line item it affects.