Vortragsthema

Green Bikes International FSP Presentation Final Presentation greenbikes.manishabraham.comPEPFSP

Page - 2Green Bikes International Team

FSPThe Flow of the Presentation Page - 3

FSP3Page - 4The Flow of the Presentation

FSPDevelopment process (Conceptual design)Page - 5

FSPOverall Project Plan

Page - 6FSP

Stakeholder Requirements Page - 7The E-bike shall be profitable after 100 units. The E-bike shall be made of at least 50% recycled materials.The E-bike shall run for at least 60 km on a full charge.The E-bike should be energy-autonomous.

FSPStakeholder Requirements The E-bike should be able to last at least 800 charge cycles.The E-bike's initial aesthetic design shall have at least a 50% approval rate from a focus group.The E-bike should be a silent bike.The E-bike should bring about a young and sporty feeling for the user.

Page - 8FSPInitial Design Concepts

Page - 9

FSPConceptual Design

Page - 10

FSPDevelopment Process for the Conceptual DesignPage - 11FSPConceptual Data ModelPage - 12

FSPNomenclatureNaming convention of system elementsAll files/entry names were named starting with GB followed by the element nameAll the levels were defined with L, numbered and separated with _.

E.g. GB_FC_L1.... (with levels)

Page - 13FSPPage - 14FunctionsGB_FC_System DefinitionGB_SDStakeholder RequirementsGB_SH _ System RequirementsGB_SR_Requirements SetGB_RS_Derived RequirementsGB_DR_System DefinitionGB_SD_SD Procedure GB_PROC_SD Physical GB_PHYSD Hardware GB_HWSD Software GB_SWSD Interface GB_IFBaseline FunctionsGB_BL_FCNomenclatureFSPFunctionsGB_FC_Baseline SD OrdinalGB_BL_ODBaselines DocumentsGB_BL_DOCBaseline Parts GB_BL_PARBaseline HardwareGB_BL_HWBaseline SoftwareGB_BL_SWBaseline CollectorGB_BL_COLLECTORPart Master PartsGB_PARCAD FilesGB_CAD_Project ManagementGB_PM_Derived RequirementsGB_DR_PDF FilesGB_PDF_Office Document FileGB_DOX_Page - 15NomenclatureFSPSystem EngineeringFunctional DecompositionRequirements DefinitionSystem BreakdownGeneric breakdown of the product from a system point of view.Decomposition of the product with no specific solution in mindPhysical InterfacesGeneral GuidelinesNeeds to be consistent with defined functions and requirementsFollow consistent nomenclature rulesReview and release itemsPage - 16FSPFunctional Decomposition Page - 17

FSPPage - 18

Creating Functions and Defining Functional StructureFSPRequirements DefinitionPage - 19Functional BreakdownPhysical RequirementsRequirement ManagementStakeholders RequirementsFunctional BreakdownSystem RequirementDerived RequirementsFSPPage - 20System Requirements

Inside CIM dbFSPRequirements Set:Page - 21

FSPPage - 22

Linking Functions to RequirementsFSPSystem Breakdown

Page - 23FSPSystem Definition (inside CIM Database)ObjectsSystem Definition OrdinalSystem Definition ProcedureSystem Definition PhysicalSystem Definition HardwareSystem Definition SoftwareSystem Definition InterfacesInformation Nomenclature, Acronym, DescriptionProject, Maturity, other descriptionsPage - 24FSPSystem Definition OrdinalEach system element is created and defined in CIM database.This will be the foundation for the detailed structured view of the system.Top level generic nomenclature and information.Clear illustration and representation of the systemGives the user a complete overview of the system for assessment and review.

Page - 25FSPSystem Definition OrdinalTasksSD-00000 - Data SheetEnter information of each system element into its own SD datasheet in CIM databaseSD-00001 SD Structure OrdinalSystem Architecture- Define/Link relationships and levels of the system Father-child relationshipsTop-down StructurePage - 26FSPSystem Definition OrdinalTasks SD-00001 - System Definition to Requirement SetLink to system requirement setsSD-00001 - FilesLink filesFor easy access to related and relevant files

Page - 27FSPSystem Definition ProcedureCollector of documentsRules, standards, generic documents which are usually not directly related to the productFor convenient reference TaskCreate SD Procedure entries and upload related filesRevisioning (Indexing/Issues)ResultSD Procedures - SDPR-00002

Page - 28FSPSystem Definition PhysicalAbstract definition of the physical components Provides the engineering department a system definition view of physical parts as reference when defining or creating specific partsTaskCreate general non-specific physical components of the system in CIM databaseLink to (specific) partsResultSD PartsPage - 29FSPSystem Definition Physical (example)

Page - 30

Reference in CIM database: SD physical---right click on item---SD physical to Part FSPSystem Definition HardwareRefers exclusively to all computer hardware related to the system (product).

TaskCreate and define SD Hardware entries in the databaseResultSD HardwarePage - 31FSPSystem Definition SoftwareRefers exclusively to all computer software related to the system (product).

TaskCreate and define SD Software entries in the databaseResultSD Software

Page - 32FSPSystem Definition InterfacesDefines horizontal relationships between system and gives the user a clear view of physical interfaces from a system view. TaskCreate and define InterfacesInterfaces between systems ResultSD Interfaces

Page - 33FSP

Page - 34Physical Interface of Parts

FSPSystem Definition Ordinal RelationshipsTasks SD-00000 - SD Ordinal to SD ProcedureLink system elements to related SD Procedure SD-00001 - SD Ordinal to SD PhysicalLink system elements to related SD Physical elements

Page - 35FSPSystem Definition Ordinal RelationshipsTasks SD-00008 - SD Ordinal to SD HardwareLink system elements to SD Hardware of the systemSD-00008 - SD Ordinal to SD SoftwareLink system elements to SD Software of the system

Page - 36FSPSystem EngineeringGenerating the Structure View

Integration of all information entered into the databaseStructured view of the whole systemView all links and relationships with one click

Page - 37FSP

Page - 38Structure View ResultSD-00000 - System Definition - System definition all relationshipsSD-00002/1SDPH-000063/1FSPBill of Materials Two types:Engineering Bill Of Materials (E-BOM)Manufacturing Bill Of Materials (M-BOM)

The E-BOM and M-BOM contain the product knowledge of how to build and how to manufacture a product. They are presented as assembly trees that represent a hierarchical structure for the assemblies, subassemblies and parts that make up the product, whether purchased or manufactured.

Page - 39FSPE-BOM vs. M-BOME-BOMDefines and manages the components and structure of the product being manufactured.Contains the list of items, parts, components, sub-assemblies and assemblies in the product designed by engineering.Represents only the physical product being engineered, not the packaging or manufacturing consumables. M-BOMContains details of the parts and assemblies required to build a complete and shippable product. (eg: Kits, Structures, Assembly processesetc.).Reflects the manufacturing process, represents physical product, packaging and included documentation (CAD files, PDF,etc.).

Page - 40FSPE-BOM vs. M-BOM example 1Page - 41Product Component B1Component B2Component CComponent DProduct Component B1Component B2Component CAssembly A(E-BOM)(M-BOM)

FSPE-BOM vs. M-BOM example 1.1Page - 42

Part Number Part Name 000045Head Tube 000046Handle Bar 000049Phone Holder ... FSPWhy is it important to have the two views?Page - 43E-BOMM-BOM Supports better purchasing decisions, manufacturing process and logistics choicesThe information from the M-BOM feeds the business systems used to order parts and build the productExtra and unnecessary changes in the manufacturing process can be avoidedSupports the successful management of manufacturing resourcesDisruptive last minute changes can be avoided with an accurate E-BOM because all the details including parts, items, components and quantities are correctly noted. Enables the final transition from product concept to a concrete, touchable objectSmoother hand-off to manufacturing Saves time in assembly process FSP

Page - 44Conceptual Design E-BOM and E-BOM

E-BOMM-BOMFSPParts and BOMs in CIM-Database

Page - 45FSPParts and BOMs in CIM Database cont.

Page - 46Part Number Part Name 000007Rim000061Tire000014Spokes000015ValveReference in CIM database: Part Master---Double click on the part---select BOM tab in the pop up menu FSPLinking Parts to CAD documents Page - 47

FSPShort Assembly Video

Page - 48FSPBaselinesPage - 49A snapshot of system defining objects at a certain point in time.A stable reference for future work.Captured state of the project for use in assessing and analyzing the system and its components.

FSPHave you explained configration item somewhere?Is it only functional and physical?Page - 50Baseline MasterCollects created baselines to capture progress points within the system development life cycle.For convenient reference and traceability

FSPSD Structure OrdinalFunctionsSystem Engineering Relationships (CIM Database)Page - 51Stakeholders RequirementsSystem RequirementsDerived RequirementsSD ProceduresSD InterfacesSD SoftwareSD HardwareSD PhysicalM-BomE-BomRequirementSetSD OrdinalBaseline CollectorFunctionalStructureFunctionsSD Structure OrdinalFilesPartsBaseline DocumentsBaseline SD OrdinalBaselineFunctionsBaselineHardwareBaselineSoftwareBaseline SD PhysicalFSP51Manageability of all product-related documents and files Accessibility of parts, documents and changesTraceability of product dataChange Management

Page - 52Benefits of PLM/PDM SolutionsFSP

KEY EXPERIENCES GREEN BIKES INTERNATIONAL Page - 53FSPPage - 54ComplicatedDetailedFUNConfusionStepsTeam WorkExperienceChallengingPROCESS

FSPFew Thoughts about the ProcessIt was a nice experience to deal with all the steps that a team faces when creating a product. Even though our product is not a complex product, the process is very important and at some point it gets complex, because the team had to deal with every small detail of the bicycle.

It was an interesting experience having an overall view of how to handle a product in its entire concept phase within a PLM environment. At first I felt the tasks were too time-consuming especially the database build-up phase. But once this was done, it was more fun exploring the system, seeing how all things are interconnected and related. But it also gave me an idea to how more complicated these systems are in a real working environment. And that is a bit intimidating.Page - 55FSPPage - 56TEAM WORKINDIVIDUAL RESPONSIBILITIESDIFFERENT OPINIONSDYNAMICCOLLABRATIONPARTICIPATIONeveryoneacceptanceExciting SOCIALequalityFSPFew Thoughts about team workIt was always a nice experience to have a committed team in which everyone had their own responsibilities.

It doesn't matter what nationalities the other members have, in the end it's all about teamwork. the more different views, the better the result.

Team work was really interesting and effective. It made the work dynamic. Sometimes absence of some team member did not effect the overall work.

Sometimes it was difficult to manage meetings and difficult to agree or arrive at a decision as a team because every one has a different opinion and wants their solution/idea to be used.Page - 57FSP

Few Aha Experiences It was surprising and interesting to learn on the way how simple details of the product get related at some point of the process.

Something the system engineering is Aha experience. Because we know but we can not remember, when someone reminds this we remember.

Many things worked on Trial and Error. Page - 58FSPPage - 59OVERALL PLM EXPERIENCE

OrganizationCooperationComplexChallengingOrganizedInterestingProductiveComplicatedTask Oriented FSPPage - 60Feel free to ask Questions

FSP

Thank you for your attention!

Page - 61FSP