0 Replies Latest reply on Aug 8, 2013 1:44 PM by Andrew Knott

    AO Time Estimates

      Share This:

      A Fortune 500 company is looking to implement AO in their environment and has these question for the AO experts that have implemented AO in an enterpris setting.  We are lking for input on a number of AO tasks, any input would be appreciated.

       

       

       

      For each item, please provide us your best guess regarding

       

       

      • How many calendar days to complete
      • How much effort in man hours. 

       

       

         Make any assumption you think is necessary to answer the question.  Please don’t over work this exercise.  Your first instinct is probably the level of analysis we need.

       

       

      1. A form is being developed (service request definition) that requires one approval.  Once approved, it will call Atrium Orchestrator to add an ID into an Active Directory group.   The automation should update the Work Order with success or failure + some sort of status text.  The task ends when it works in production.

       

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

      2. An existing Atrium Orchestrator workflow has been created, and there is a decision made to create a SRD which will serve as a front end for this workflow.  (Using OCP should not be considered as an option.)   The SRD has one free text field, plus three pull down lists that users can use to select their options.  The data from those pull down lists all exists in CMDB.  The task ends when it works in production.

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

      3. Same as example #2, but two of the pull down lists require new data to be replicated into the CMDB.  One of the data sources can be
      referenced using straight SQL.  The other data source is a Microsoft SharePoint list and can be referenced via a .Net based web service.  The task ends when it works in production.

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

      4. An existing Atrium Orchestrator workflow which interacts with several systems using a command line interface.  The target system changes and the command line needs to be updated.  Unfortunately, the workflow has to be updated, as opposed to just updating a configuration item.  The task is to make an adjustment to the command which is run by BAO, plus restructure the workflow so future updates could be made with just a configuration change.  The task ends when it works in production.

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

      5. Build an SRD, which upon approval, triggers an action to be taken in Bladelogic Network Automation.  The SRD would pass at least
      one argument.  For example, the name of the switch upon which the action should be taken.  The task ends when it works in production.

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

      6. Take a functional BAO workflow, then do the following

        • promote it to a distinct acceptance grid
        • evaluate it, then promote it to a distinct production grid
        • validate that it works in the production grid

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

      7. Take a functional SRD

        • promote it to a distinct acceptance environment
        • evaluate it, then promote it to a distinct production environment
        • validate that it works in the production  environment

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

       

       

      8. Our company agrees to provide support for a third party which has its own instance of Remedy.  There is an agreement to bi-directionally replicate Remedy data between the two instances.  Data mapping is fairly straightforward.   The task is considered complete when you have validated that the replication works in the production environment.

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes:

       

       

      9. We decide to pull data from a managed Dell FTP site into our CMDB to update information about the server hardware.  Data mapping is straightforward.

       

      Calendar Days Best Case:

      Calendar Days Worst Case:

      Work Effort Hours Best Case:

      Work Effort Hours Worst Case:

      Notes: