Agricos concern Lack of standardization in AMR software, so any modification will require rigorous testing AMR has client

nt specific codes which makes having a backup of Agricos codes essential Issues with AMR software Comprehensive testing was not there Compatibility issues with various options offered by AMR Fire fighting/reactive response to software bugs AMRs concern AMR does not want to sacrifice its core competency by sharing its source code Also sharing its source code will lead to loss of its market potential of modifications that will be required in future Agrico Inc is not a software company so external consultants will be hired for modification which increases data vulnerability as well as risk of breach of IPR(Intellectual Property Rights) Recommendation Concerns can be resolved by rights based analysis(regard to the implications for the rights of each stakeholder ) and duty based analysis(effort to identify any fundamental ethical duties which may be involved) AMR issues of privacy (consisting of access, storage, duplication) and ownership (consisting of access, duplication and technology vendor) Agrico Inc Issues of control (consisting of duplication and job redesign) and accuracy (consisting of access and storage) Issues of privacy, ownership and accuracy can be resolved with comprehensive data policy (need to delineate who is responsible for the accuracy to the data, and monitors procedures for updating ) and issue of control can be resolved by IPR policy