|
|
www.johnstark.com |
|
|
|
Reason 41. Everyone knows that departmental empires just want to be separate. Reason 42. We saw EDM/PDM once, and it looked neither useful nor usable to us. Reason 43. EDM/PDM is so simple we are going to build our own system. Reason 44. EDM/PDM is very good, but we can do it a different way. Reason 45. The idea of EDM/PDM is good, but EDM/PDM systems are not really data base systems. Reason 46. EDM/PDM isn't the type of engineering computing system we need. Our engineers really need C++ support. Reason 47. We can't do EDM/PDM because it wasn't included in the 5-year plan. Reason 48. We can't do EDM/PDM because we've used up this year's budget. Reason 49. Our management only lets us buy systems from 3 vendors, and none of them has a good EDM/PDM solution. Reason 50. We would like an EDM/PDM system, but the potential users say they don't want one. Reason 51. We would like to do EDM/PDM, but the others don't want to. Reason 52. We would like to do EDM/PDM, but we don't have the power. Reason 53. We would like to do EDM/PDM, but we don't have any influence. Reason 54. We can't do EDM/PDM, because it isn't in the plan we have to follow. Reason 55. We would like to do EDM/PDM, but we don't have the resources. Reason 56. We would like to do EDM/PDM, but we don't know how to cost-justify it. Reason 57. We would like to do EDM/PDM, but it's a bit too soon. Reason 58. We would have liked to do EDM/PDM, but it's a bit late now. Reason 59. Your ideas on EDM/PDM are good, but we would need to adapt them to our company. |