1. PEPGreen Bikes International FSPPresentationFinal Presentationwww.greenbikes.manishabraham.com

2. FSP Page - 2Green Bikes International TeamProject LeaderManish AbrahamEngineering ManagerMuna AbdulrahmanDesign EngineerAbraham De OchoaDesign EngineerMahdi Baghban PouraslSystems ManagerHaydee CapcoNina Asadi MoghadasSystems EngineerCristian GideaSystems EngineerShakh Alauddin 3. FSPThe Flow of the PresentationPage - 3 4. FSP Page - 4The Flow of the Presentation 5. FSPDevelopment process(Conceptual design)Page - 5 6. FSPOverall Project PlanPage - 6 7. FSPStakeholder RequirementsPage - 7The E-bike shall be profitable after 100 units.The E-bike shall be made of at least 50% recycledmaterials.The E-bike shall run for at least 60 km on a fullcharge.The E-bike should be energy-autonomous. 8. FSPStakeholder RequirementsThe E-bike should be able to last at least 800charge cycles.The E-bikes initial aesthetic design shall have atleast 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 sportyfeeling for the user.Page - 8 9. FSPInitial Design ConceptsPage - 9 10. FSPConceptual DesignPage - 10 11. FSPDevelopment Processfor the ConceptualDesignPage - 11 12. FSPConceptual Data ModelPage - 12 13. FSPNomenclatureNaming convention of system elementsAll files/entry names were named starting with GBfollowed by the element nameAll the levels were defined with L, numbered andseparated with _.E.g. GB_FC_L1.... (with levels)Page - 13 14. FSP Page - 14Functions GB_FC_System Definition GB_SDStakeholder Requirements GB_SH _System Requirements GB_SR_Requirements Set GB_RS_Derived Requirements GB_DR_System Definition GB_SD_SD Procedure GB_PROC_SD Physical GB_PHYSD Hardware GB_HWSD Software GB_SWSD Interface GB_IFBaseline Functions GB_BL_FCNomenclature 15. FSPFunctions GB_FC_Baseline SD Ordinal GB_BL_ODBaselines Documents GB_BL_DOCBaseline Parts GB_BL_PARBaseline Hardware GB_BL_HWBaseline Software GB_BL_SWBaseline Collector GB_BL_COLLECTORPart Master Parts GB_PARCAD Files GB_CAD_Project Management GB_PM_Derived Requirements GB_DR_PDF Files GB_PDF_Office Document File GB_DOX_Page - 15Nomenclature 16. FSPSystem 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 andrequirementsFollow consistent nomenclature rulesReview and release itemsPage - 16 17. FSPFunctional DecompositionPage - 17 18. FSP Page - 18Creating Functions andDefining Functional Structure 19. FSPRequirements DefinitionPage - 19Functional BreakdownPhysical RequirementsRequirement ManagementStakeholdersRequirementsFunctionalBreakdownSystemRequirementDerivedRequirements 20. FSP Page - 20System RequirementsInside CIM db 21. FSPRequirements Set:Page - 21 22. FSP Page - 22Linking Functions toRequirements 23. FSPSystem BreakdownPage - 23 24. FSPSystem Definition(inside CIM Database)ObjectsSystem Definition OrdinalSystem Definition ProcedureSystem Definition PhysicalSystem Definition HardwareSystem Definition SoftwareSystem Definition InterfacesInformationNomenclature, Acronym, DescriptionProject, Maturity, other descriptionsPage - 24 25. FSPSystem Definition OrdinalEach system element is created and defined in CIMdatabase.This will be the foundation for the detailed structuredview of the system.Top level generic nomenclature and information.Clear illustration and representation of the systemGives the user a complete overview of the system forassessment and review.Page - 25 26. FSPSystem Definition OrdinalTasksSD-00000 - Data SheetEnter information of each system element intoits own SD datasheet in CIM databaseSD-00001 SD Structure OrdinalSystem Architecture- Define/Link relationshipsand levels of the systemFather-child relationshipsTop-down StructurePage - 26 27. FSPSystem Definition OrdinalTasksSD-00001 - System Definition to Requirement SetLink to system requirement setsSD-00001 - FilesLink filesFor easy access to related and relevant filesPage - 27 28. FSPSystem Definition ProcedureCollector of documentsRules, standards, generic documents which are usually notdirectly related to the productFor convenient referenceTaskCreate SD Procedure entries and upload related filesRevisioning (Indexing/Issues)ResultSD Procedures - SDPR-00002Page - 28 29. FSPSystem Definition PhysicalAbstract definition of the physical componentsProvides the engineering department a systemdefinition view of physical parts as reference whendefining or creating specific partsTaskCreate general non-specific physical components of thesystem in CIM databaseLink to (specific) partsResultSD PartsPage - 29 30. FSPSystem Definition Physical(example)Page - 30Reference in CIM database: SD physical---right click on item---SD physical to Part 31. FSPSystem Definition HardwareRefers exclusively to all computer hardware related tothe system (product).TaskCreate and define SD Hardware entries in the databaseResultSD HardwarePage - 31 32. FSPSystem Definition SoftwareRefers exclusively to all computer software related tothe system (product).TaskCreate and define SD Software entries in thedatabaseResultSD SoftwarePage - 32 33. FSPSystem Definition InterfacesDefines horizontal relationships between system andgives the user a clear view of physical interfaces froma system view.TaskCreate and define InterfacesInterfaces between systemsResultSD InterfacesPage - 33 34. FSP Page - 34Physical Interface of Parts 35. FSPSystem Definition OrdinalRelationshipsTasksSD-00000 - SD Ordinal to SD ProcedureLink system elements to related SD ProcedureSD-00001 - SD Ordinal to SD PhysicalLink system elements to related SD PhysicalelementsPage - 35 36. FSPSystem Definition OrdinalRelationshipsTasksSD-00008 - SD Ordinal to SD HardwareLink system elements to SD Hardware of thesystemSD-00008 - SD Ordinal to SD SoftwareLink system elements to SD Software of thesystemPage - 36 37. FSPSystem EngineeringGenerating the Structure ViewIntegration of all information entered into the databaseStructured view of the whole systemView all links and relationships with one clickPage - 37 38. FSP Page - 38Structure View ResultSD-00000 - System Definition -System definition all relationshipsSD-00002/1SDPH-000063/1 39. FSPBill of MaterialsTwo types:Engineering Bill Of Materials (E-BOM)Manufacturing Bill Of Materials (M-BOM)The E-BOM and M-BOM contain the product knowledgeof how to build and how to manufacture a product. Theyare presented as assembly trees that represent ahierarchical structure for the assemblies, subassembliesand parts that make up the product, whether purchasedor manufactured.Page - 39 40. FSPE-BOM vs. M-BOME-BOMDefines and manages the components and structure of the productbeing manufactured.Contains the list of items, parts, components, sub-assemblies andassemblies in the product designed by engineering.Represents only the physical product being engineered, not thepackaging or manufacturing consumables.M-BOMContains details of the parts and assemblies required to build acomplete and shippable product. (eg: Kits, Structures, Assemblyprocessesetc.).Reflects the manufacturing process, represents physical product,packaging and included documentation (CAD files, PDF,etc.).Page - 40 41. FSPE-BOM vs. M-BOM example 1Page - 41ProductComponent B1Component B2Component CComponent DProductComponent B1Component B2Component CAssembly A(E-BOM) (M-BOM) 42. FSPE-BOM vs. M-BOM example1.1Page - 42Part Number Part Name000045 Head Tube000046 Handle Bar000049 Phone Holder... 43. FSPWhy is it important to havethe two views?Page - 43E-BOM M-BOMSupports better purchasing decisions,manufacturing process and logisticschoicesThe information from the M-BOM feedsthe business systems used to orderparts and build the productExtra and unnecessary changes in themanufacturing process can be avoidedSupports the successful management ofmanufacturing resourcesDisruptive last minute changes can beavoided with an accurate E-BOMbecause all the details including parts,items, components and quantities arecorrectly noted.Enables the final transition fromproduct concept to a concrete,touchable objectSmoother hand-off to manufacturing Saves time in assembly process 44. FSP Page - 44Conceptual Design E-BOM andE-BOME-BOMM-BOM 45. FSPParts and BOMs in CIM-DatabasePage - 45 46. FSPParts and BOMs in CIMDatabase cont.Page - 46PartNumberPart Name000007 Rim000061 Tire000014 Spokes000015 ValveReference in CIM database: Part Master---Double click on the part---select BOM tab in the pop up menu 47. FSPLinking Parts to CAD documentsPage - 47 48. FSPShort Assembly VideoPage - 48 49. FSPBaselinesPage - 49A snapshot of system defining objects at a certainpoint in time.A stable reference for future work.Captured state of the project for use in assessingand analyzing the system and its components. 50. FSP Page - 50Baseline MasterCollects createdbaselines to captureprogress points withinthe systemdevelopment life cycle.For convenientreference andtraceabilityBaseline Master (Collector)Baseline SD OrdinalBaseline FunctionsBaseline DocumentsBaseline SD PhysicalBaseline HardwareBaseline Software 51. FSPSD StructureOrdinalFunctionsSystem EngineeringRelationships (CIM Database)Page - 51StakeholdersRequirementsSystemRequirements DerivedRequirementsSDProceduresSDInterfacesSD SoftwareSDHardwareSD PhysicalM-BomE-BomRequirementSetSD OrdinalBaselineCollectorFunctionalStructureFunctionsSD StructureOrdinalFilesPartsBaselineDocumentsBaselineSD OrdinalBaselineFunctionsBaselineHardware BaselineSoftwareBaselineSD Physical 52. FSPManageability of all product-related documents andfilesAccessibility of parts, documents and changesTraceability of product dataChange ManagementPage - 52Benefits of PLM/PDM Solutions 53. FSPKEY EXPERIENCESGREEN BIKESINTERNATIONALPage - 53 54. Page - 54 55. FSPFew Thoughts about the ProcessPage - 55 56. Page - 56 57. FSPFew Thoughts about team workPage - 57 58. FSPFew Aha ExperiencesIt was surprising and interesting to learn on the way how simpledetails of the product get related at some point of the process.Something the system engineering is Aha experience. Becausewe know but we can not remember, when someone reminds thiswe remember.Many things worked on Trial and Error.Page - 58 59. Page - 59 60. FSP Page - 60 61. FSPThank you for your attention!Page - 61