Scribd
Upload
18 views

Requirement Document For Requirement Module

The customer currently manages requirements and progress information using Excel, which has security issues and inability to track revisions. They need a solution using Siemens Teamcenter that allows importing requirements, controlling access, differentiating customer and derived requirements, adding feasibility checks and documents, and generating reports while managing the requirements and approval workflows.

Uploaded by

Subha Sree
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
18 views

Requirement Document For Requirement Module

The customer currently manages requirements and progress information using Excel, which has security issues and inability to track revisions. They need a solution using Siemens Teamcenter that allows importing requirements, controlling access, differentiating customer and derived requirements, adding feasibility checks and documents, and generating reports while managing the requirements and approval workflows.

Uploaded by

Subha Sree
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Current process in customer site:

Customer at present manages the customer and derived requirements at Excel application.

Changes in customer Requirements are managed via mail and excel

Progress information about each requirement is managed in excel reporting

<Add some more>

Pain points:
Below is the list of non-exhaustive pain points at customer site.

 Security issue: Other groups’ users can edit other groups information.
 Unable to manage revisions of each requirement.
 Unable to avoid duplicate information about requirements.
 Unable to compare requirements

<Add some more>

Expected Solution:
Customer currently at TC 13.2 and AWC 5.2 with Teamcenter Integration

Following are the non-exhaustive list of requirements from customer.

 Able to convert OR(PDF/Printouts) as Structure in AWC


 Able to edit the requirements in Word or Excel directly from AWC.
 Access should be controlled between Program Manager, Project Manager and Designer
 Able to differentiate customer requirement and Derived Requirements.
 Provision for feasibility check and upload of documents
 One approval workflow for review of all information like feasibility
 Create “Feasible Study” workflow
 Workflow should be initiated on Created Customer Requirement
 Should be able to create derived requirements separately. Provision to use existing
requirement specification.
 Different requirements should be managed with different objects and they should be visible
in different colors and Naming patterns
 Different requirements should be managed and they should be visible for different groups
 Should be able to generate report on requirement along with attached objects like
documents, design etc.…
 Direct queries needed for searching based on type of requirements and feasibility
information
 Should create a Form for capturing feasibility information and comments by users
 Should create a Relation “HasfeasibilityInfo”
 Form should be attached to the requirement under “HasfeasibilityInfo” relation
 Create 3 groups: Program Manager, Project manager, Structures
 Create 2 roles: Engineer, Designer
 Add 2 users to each role
Custom Object: Customer Requirement

Naming Rule: CREQ - NNNNN


Properties:
Form:

Structure Feasibility
Program manager Feasibility
Project manager Feasibility

Structure Comments
Program Manager comments
Project manager comments

Customer Requirement:

Overall Feasibility

Lov:
Feasible:
Yes
No

Overall Feasibility:
Yes
No

BOM Structure:
Requirement Specification
Customer Requirement 1
Customer Requirement 2

Customer Requirement
Customer Requirement 1
Customer Requirement 2

Create a preference to control the allowed child types for above structure formations
<Add some more>

You might also like