As we discussed in last post, after requirements captured by all cross functional teams in the organization, it is very important to develop As-Is process documentation.As-Is process is working methodology of an organization at present without any new system implementaion. Once As-Is process document is ready, submit it to management team for review. Management team should review the As-Is process document and reviewed process should be used to create To-Be process with respect to captured information by the organization and PLM tools offerings. It is very important to prepare first level To-Be process document before starting project and organization people and PLM service vendor both should again review To-be process together. To-Be process documents should include the future PLM system technical scope which will be implementing after mutual agreement between both organization and PLM service vendor.
To-Be process is a document which should clearly indicates what and all PLM functionalities will be implemented as per organization requirements, if some of requirements are not able to implement at present chosen PLM software then those functionalities should be clearly mentioned with proper workarounds or customized ways to get it done to match organization’s requirements. And To-Be process document is overview of scope of work document before elaborating the technical scope document of whole PLM implementation project.
Simple Example:
As-Is process:
a. At present Engineers are generating Part Numbers manually in excel sheet and later entering Part Numbers from excel sheet to CAD model and Drawing manually.
To-Be process:
a. Automatic Part Number Generation module will be built in out of the box PLM system offering as per Number Logic.
b. And engineers will use this function to generate Part Number directly in CAD tool and later assign to new CAD Model and same way another Part Number will be generated for respective drawing automatically.
c. In case of complicated Part Number generation and other reference variable Part Number logic, customization needs to be done and same will be evaluated later.
Some the PLM vendors prepares whole Project Plan before proceeding to requirements phase and some vendors develops Project Resource and Time plan after To-Be process signed-off by the organization team. Both the way is suitable as per their internal process. We developed Project Plan before and after To-be process sign-off again we changed some the Project Plan in our Project.
Next post we can discuss how the technical configuration plan can be preparation and how we can start PLM software configuration.
Bye for now,
Anil Kumar J R
No comments:
Post a Comment