Norm,

The easiest way I can think of off hand is to create companies of those
independent business units.  If the organization you're talking about is
large enough it would probably be best to have multiple ITSM
installations on multiple servers, and use DSO to push between the
different companies, still setting each business unit up as a different
company.

Also, I would suggest you set up a test environment for yourself to see
how multi-tenancy works.  I'm currently having an issue with it that
appears to have bypassed multi-tenancy in a way.  I'm able to add a user
as an approver for a change that the user has no permission to see
because they are in different companies.  I think multi-tenancy works
fine for the main modules, but for things like approvals and tasks I
would suggest testing more rigorously if I were you.

Shawn Pierson

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96
CS/SCCE
Sent: Friday, June 29, 2007 1:20 PM
To: arslist@ARSLIST.ORG
Subject: Multitenancy in a Large Enterprise



        **

        Has anyone attempted to implement multitenancy in a large,
complex enterprise? Suppose I have a very large company called Acme
Incorporated, and let's say Acme actually consists of multiple
quasi-independent subsidiaries-Widgets, Sprockets, and Gizmos.



        Let's say Widgets, Sprockets, and Gizmos were each independent
companies that were recently acquired by Acme.  So Acme's structure
looks like this:



        Acme

                Widgets

                Sprockets

                Gizmos



        Now each subsidiary has independent business units-Research,
Development, Testing, and Contracting.  So now Acme looks like this:



        Acme

                Widgets

                        Research

                        Development

                        Testing

                        Contracting

                Sprockets

                        Research

                        Development

                        Testing

                        Contracting

                Gizmos

                        Research

                        Development

                        Testing

                        Contracting



        OK, so far, so good.  Here's the rub-Acme does not want each
independent business unit to be able to see the others' tickets.  In
other words, Widgets' Research unit cannot see tickets assigned to
Widgets' Testing unit and vice versa...unless, that is, Widgets'
Research unit wants to "throw the ball over the fence" to Widget's
Testing.



        According to the ITSM documentation, multitenancy can only be
effected at the company level...so my question is, can multitenancy be
implemented in the way I'm describing without any code modifications?



        Norm



        __20060125_______________________This posting was submitted with
HTML in it___


The information in this e-mail, and any files transmitted with it, is intended 
for the exclusive use of the recipient(s) to which it is addressed and may 
contain confidential, proprietary or privileged information.  If you are not an 
intended recipient, you have received this transmission in error and any use, 
review, dissemination, distribution, printing or copying of this information is 
strictly prohibited.  If you have received this e-mail in error, please notify 
the sender immediately of the erroneous transmission by reply e-mail, 
immediately delete this e-mail and all electronic copies of it from your system 
and destroy any hard copies of it that you may have made. Thank you.

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to