本文发表在 rolia.net 枫下论坛你说得不错,pre-built ERP 系统的实施和in-house application development采用完全不同的methodology.
per-built ERP应该是一个大致完整的系统,后端的数据库架构,不同数据库之间的connector应该定义完成,中间端的business tier,应该预留用户接口,用户可用所支持的语言API,开发plug-in,或将开发的新模块,在configuration-xml中注册。
In-house application development,是个从底层构建(database architecture design, application middleware framework, system replication, role-based authendication model,etc ), 直到用户端(client type: thin web app, or thick Notes, VB, ).
建立用户界面,数据库,dataflow, 不是什么难点。In-House ERP难的部分,是workflow, 举个例子,Engineering Change Request, one ECR may have one, or tens of ECRs, each ECR will have to pass different stages, PE designer, supervisor, Material Control, MFE, QA, Tooling, Sales Admin, Senior Mgmt, will execute their own approval process at each stage. 这些,并不是复杂的,复杂的是,product assembly, prototype BOM, CAD Drawings, Customer RFQ,每星期都在变,公司的部门,人员,职责。也在变动。这些经常变动的requests, 必须及时地反映在ERP中,否则,生产线,和销售,就要受到影响。生产线一天三班倒,一旦停下来,对公司的销售,利润影响巨大。
IT部门的包袱是沉重的,开句玩笑,IT员工,是从不和Product Engineer一起吃饭的。
我现在所谓的pilot project,就是建立一个小的workflow model,让SAP去实现, 增加number of stages, approval levels and comlexity, 观察,比较,定量分析。为今后系统的开发,确定一个大致的走向。更多精彩文章及讨论,请光临枫下论坛 rolia.net