assignment 4

April 6, 2015 Prepared by: Tim Williams / Warne r Sherman BCM -002 Technical Requirements Product and Environmental Specifications 1 BCM -002 Technical Requirements | 4/6/2015 BCM -002 Technical Requirements Product and Environmental Specifications P u r p o s e o f t h i s D o c u m e n t This document outlines the four step product requirements process described by the international version of Ulrich and Eppinger text in Chapter 6. The objective of this document is to translate the custome r requirements presented in a previous paper into meaningful technical requirements for the product to mee t the required specifications . P r o d u c t S u m m a r y a n d B a c k g r o u n d The Babe l Control Module 002 ( BCM -002 ) is an interlink device that translates APEX proprietary protocols to industry standard protocols. The BCM -002 device h as a form factor that fits into an existing APEX rack. The BCM -002 does not require extensive installation configuration. Customers are currently without support for an estimated 15,000 LCM -1020 series controllers currently in the field. Because of th e closure of Apex Corporation in early 2014 and the fact that the LCM -1020 device uses the proprietary APEX industrial control scheme , it is not currently possible to obtain suitable replacements or upgrades for LCM -1020 modules. As a service provider , WISH will decode the APEX scheme, impellent an APEX to ICS4 conversion routine on a board with the same form factor as an LCM - 1020 module, and provide the appropriate layouts and schedule drawings for use in manufacture of the new BCM -002 modules. Upon completion , the BCM -002 project will be an industrial control board to serve as a communication bridge between the older LCM -1020 system designed by Apex Corporation and the standard Industrial Control Scheme version 4 (ICS4). Based on past experience and a preliminary design, it is expected that an individual module will cost $175 to develo p, with an expected sales cost of $300 , resulting in potential revenue of $125 per module . S t e p 1 : P r e p a r e t h e M e t r i c s Devices of this sort commonly list the following technical specifications:  Power Requirements  Isolation Voltage  Ethernet Connection  Power connection  North American temperature code  IEC temperature code  Temperature, operating  Temperature, surrounding air, max  Temperature, nonoperating  Relative humidity  Certifications  Other environmental considerations (ESD, RF Immunity, etc.) S t e p 2 : C o l l e c t C o m p e t i t i v e B e n c h m a r k i n g I n f o r m a t i o n 2 BCM -002 Technical Requirements | 4/6/2015 Because the requirements of industrial control components are all similar and WiSh has a history with these products, it is not necessary to collect additional information here. Comm on values used by WiSh are detailed in the following table (this is modeled on the specs of the Allen -Bradley 1788EN2DNR EtherNet/IP to DeviceNet Linking Device, available at: (http://literature.rockwellautomation.com/idc/groups/literature/documents/td/1788 -td001_ -en -p.pdf ) Power requirements Input: 24V DC, 150 mA, Class 2/SELV Isolation voltage 30V (continuous), basic insulation type, power to system, Ethernet to system, and APEX to system Ethernet Connection RJ45 connector according to IEC 60603 -7, 2 or 4 pair Category 5e minimum cable according to TIA 568 -B.1 or Category 5 cable according to ISO/IEC 24702. Power connection Power: 0.25…2.5 mm 2 (22…14 AWG) solid or stranded copper wire rated at 105 C (221 F ), or greater, 1.2 mm (3/64 in.) insulation max. North American temperature code T4 IEC temperature code T4 Temperature, operating -25…60 °C ( -13…140 °F) Temperature, surrounding air, max 60 C (140 F) Temperature, nonoperating -40…85 °C ( -40…185 °F) Relative humidity 5…95% noncondensing Certifications c-UL -us; Ethernet/IP (ODVA)  Note that size and weight are generally not explicitly listed for “slotted” equipment that fits into existing racks. S t e p 3 : S e t I d e a l a n d M a r g i n a l l y A c c e p t e d T a r g e t V a l u e s For this step, the example values above were selected as they are very common numbers for these device s. Deviations from these specifications would (potentially) create an issue with the project scope. S t e p 4 : R e f l e c t o n t h e P r o c e s s This includes the following questions:  Are the members of the team “gaming”? No, the specifications for the product are straightforward and achievable. The project team’s primary concerns are whether or not a linking device for the APEX protocol is possible and how much time creating one will require. If a product is possible, then the physical specifications of the produ ct shouldn’t prove to be an issue.  Should more than one product be offered? The hardware for the BCM -002 device should be usable for any Ethernet to Ethernet linking device. However, without a customer willing to pay for the development of the software fo r such a device, it is outside of the WiSh business model to create one.  Are there any missing specifications? It is believed that the specifications are complete. However, these specifications should be revisited after the APEX communications scheme has been decoded.