WHY: To show respect to an officer of the Air Force
WHAT: To perform the required salute WHEN: An officer enters a room or approaches when outdoors. HOW: The hand and wrist are straight [simple];
|
Establish “why” information is exchanged;
Determine “what” information supports the “why”; Define “when” information should be exchanged; and finally Design "how" information should be exchanged. |
WHY: The design / development of products occurs in PLM (in conjunction with CAD) and the production of products occurs in ERP. Therefore, select Product information in PLM have to be entered into ERP for production of those select Products to be executed [simple];
WHAT: All Products that are to be produced need to be passed from PLM to ERP. The Product information that is required by ERP include the Product ID, Product Name, Product Description, Primary Material, etc. [equally simple]; WHEN: Products that achieve a development status of Approved in PLM [again simple]; HOW: Any Product that achieves an Approved status triggers an event in PLM that: |
(1a) reads the Product information;
(1b) forms it into a json message structure that includes the ERP address; and (1c) passes it to the middleware service. |
The middleware service:
|
(2a) reads the json message and ERP address;
(2b) determines what mapping is required to ensure that the PLM based Product information is “understandable” by the ERP API (Application Programming Interface); (2c) transforms the information from PLM to an ERP acceptable format; (2d) transfers the transformed json message structure to the ERP system. |
Systems Integration example: Automating the passing of Supplier data from PLM to ERP when there are only a handful of new Suppliers per calendar quarter. Resulting in overinvesting in a systems integration when compared to manual reentry.
Military example: Saluting the mirror in a room without officers. Resulting in wasted energy; unless you are practicing … |
Systems Integration example: Automating the passing of Product information of all Approved products from PLM to ERP but doing so in a nightly (or worse, weekly) batch run instead of doing so as it occurs. Resulting in a loss on production / time-to-market gains.
Military example: Saluting an officer after s/he passes. Resulting in the officer commanding that the airman “give me 20 pushups”. |
dsg_applies_kiss_to_systems_integration.pdf | |
File Size: | 200 kb |
File Type: |