Turn Off Tabs
Serena Orchestrated Ops 4.0 Readme
This readme file contains information about this release. Last updated on 2013-01-07.

Contents

About this Release

Welcome to Serena Orchestrated Ops 4.0. Refer to the What's New? tab for a complete list of new features in this release.

Please note the following important information:

  • On-premise customers: Before you install Serena Orchestrated Ops, you must install and configure SBM 10.1.1.4 or later as described in the SBM Installation and Configuration Guide.
  • Serena Orchestrated Ops 4.0 is available in English only.
  • This readme pertains to both the on-demand and on-premise versions of Serena Orchestrated Ops 4.0.
  • Internet Explorer 7.0 is no longer supported with Serena Orchestrated Ops.

Packaging Changes

Serena Orchestrated Ops is now used to refer to the collection of solutions that manage your IT services. (Previously, Serena Service Manager was used.) The following solutions, which can be used independently or in combination, are included in Serena Orchestrated Ops:

  • Serena Request Center
  • Serena Demand Manager
  • Serena Service Manager

New Installations of Serena Orchestrated Ops

If this is a new on-premise installation, download Serena Business Manager 10.1.1.4 or later from http://www.serena.com/support and then follow the instructions in the SBM Installation and Configuration Guide to install and configure Serena Business Manager. After you have verified that Serena Business Manager is installed successfully, download Serena Orchestrated Ops 4.0 from http://www.serena.com/support and follow the instructions in the Serena Orchestrated Ops Installation and Configuration Guide.

For on-demand customers, see the Serena Orchestrated Ops On-Demand Installation and Configuration Guide for information on setting up Serena Orchestrated Ops in your current environment.

Upgrades from Previous Versions

The Serena Orchestrated Ops upgrade process consists of two phases: the installation upgrade (on-premise only) and the solutions upgrade.
  • Installation Upgrade

    In the installation upgrade phase, you install and configure the latest versions of the framework files for Serena Request Center, Serena Demand Center, and features such as service level agreements (SLA). The solutions that you have implemented from previous releases are supported with the upgraded framework files.

  • Solutions Upgrade

    In the solutions upgrade phase, you import new solution files and merge changes into your current solutions. Before attempting this upgrade, review the list of changes to determine the benefit of upgrading your solutions.

Note: Upgrades of Serena Demand Manager to version 4.0 are not supported. The SDM - Project Proposal and SDM - Voting applications that were included with version 3.5 have been replaced by the SDM - Demand Plan app in SOO 4.0. To use the new process app, import the Serena Demand Manager 4.0 solution, and then promote the SDM - Demand Plan process app.

For upgrade instructions, refer to the Serena Orchestrated Ops Upgrade Guide.

Serena Orchestrated Ops Installer Components

The Serena Orchestrated Ops installer delivers three components:

  • Solution Files – Solution files are process app snapshots and blueprints that contain the latest changes and updates for the Serena Orchestrated Ops process workflows and data models.
    The following solutions are delivered by the Serena Orchestrated Ops installer:
    • Serena Demand Center:
      • SDM - Demand Plan
    • Serena Request Center:
      • SRC - Starter Pack Forms - IT
      • SRC - Knowledge Management
      • SRC - Service Request
    • Serena Service Manager:
      • SSM - Change Management
      • SSM - Configuration Management System
      • SSM - Problem Management
      • SSM - Incident Management
  • Framework Files – The SOO framework files augment your underlying SBM installation and enable certain features in the SOO process apps. The framework files include new templates, images, and code that are backward compatible with your existing installation.
  • Service Level Agreement (SLA) Files – SLAs define the level of service that an organization commits to its customers. SLAs contain performance metrics that correspond to these commitments.

Third-party Tools

For third-party software information, refer to:

What's New?

The following features and changes are new in Serena Orchestrated Ops.

Serena Demand Manager

Significant improvements have been made to Serena Demand Manager:

Demand Plan Process App

Serena Demand Manager brings governance to your planning process through the Demand Plan process app. Analysis, approvals, and reviews are now tightly integrated with Serena Demand Center, allowing participants in your planning process to collaborate on demand item analysis and other activities from plan creation to completion, all with full audit capabilities provided by Serena Business Manager.

Serena Demand Center Improvements
  • Demand Center takes advantage of the Resource Management features introduced in Serena Business Manager 10.1.1.4. Team capacity is now calculated based on SBM calendars, shared team allotments and assignments, and estimates for individual demand items in a plan.

    On the Resources tab in Demand Center, you can now view each team's capacity breakdown by plan, as well as its allocations, members, skills, job functions, and team leader.

  • Demand items can now be analyzed by multiple planning participants to determine the validity, size, and scope of individual items. After analysis, items can be added to a plan, sent to a backlog, or rejected.
  • Plans can now be organized into portfolios, which allow for better organization and monitoring.
  • Graphical roll-up views are now available for demand items and plans.

    For demand items, you can quickly see how many items have been analyzed and how many are in progress. This roll-up view is available for all demand views or for those in a specific category.

    For plans, the master view enables Demand Center users to see top initiatives across all plan. The portfolio roll-up view enables users to see a time line of all plans or those that are in planning, in-flight, or completed.

  • Large demand items assigned to a plan can be "split" into smaller items, enabling you to spread components of work across plans or send pieces to the backlog. This feature requires configuration to your demand item applications. For details, refer to the Serena Orchestrated Ops Implementation Guide.
  • If an incoming demand item is too large to deliver as part of a plan, planners can now propose a new plan based on a specific demand item that is in analysis. The proposed plan is submitted into the Demand Plan project and follows the approval process. Once the plan is visible in Demand Center, the demand item on which the plan is based is automatically assigned to the plan.
  • Items assigned to plans can be returned to analysis as needed.
Demand Item Improvements
  • Demand items are now automatically "paused" while they are in a planning phase, such as analysis or waiting for plan approval. This ensures that items are part of an approved plan before work begins. Paused items cannot be transitioned or closed when they are paused, but they can be updated so that pertinent information is captured. Once a plan has been approved, its demand items are "unpaused" and work can continue.
  • To optimize the "pause" feature, you can add the new Pause Status system field to your demand item applications. You can then create reports and notifications to enable users to monitor the status of demand items as they are paused or "unpaused" by Demand Manager.
  • The Demand Widget can now be added to custom state forms in your demand item applications. The widget displays analysis and planning information, such as assigned plan and allocated resource teams, scoring, and resource and asset estimates.

Customizing the Demand Plan Process App

Each of the states and transitions in the Demand Plan workflow coordinate with plan life-cycle actions in Demand Center. Customizing the workflow is possible, but use caution when doing so. Before beginning this advanced customization, read the instructions in S139262 in the Knowledgebase at serena.com.

Deprecated Features

The Project Proposals and Voting process apps that were included with Serena Orchestrated Ops 3.5 are no longer available. Upgrades for these process apps are not supported.

Serena Request Center

  • The Knowledge Management application now supports Smart Search functionality. Smart Search provides sophisticated search handling by recognizing keywords, phrases, synonyms, wild cards, and returning related knowledge base items.
    • Use SBM Configurator to configure settings related to the location of Smart Search index files, expected search usage for your system, and the database polling interval (how often the service should poll the database to learn about new search strings).
    • The entire knowledge base article is now indexed for searching, so in Request Center, a search can return any word in the content, title, and summary fields. If you anticipate that users will search using a different word, you can type it in the Keywords field in the article to include it in a search.
    • In the SBM User Workspace, the Details tab (formerly called the Overview tab) now includes the Summary field and the optional Keywords field. References to the obsolete keyword generator script and the jQuery plugin have been removed from forms.
    Note: To implement this feature as part of an upgrade from a previous version of SOO, you must follow the steps described in the Serena Orchestrated Ops On-Premise Upgrade Guide to upgrade the following process apps:
    • SRC - Knowledge Management
  • A "service" configuration item (CI) can now be created in the Configuration Management System (CMS). A service CI is the highest level of CI, but it is visible throughout the CI hierarchy down to the individual request. This allows service data to be accurately and efficiently captured and reported. After an administrator links a service CI to a service request in Serena Request Center, all requests submitted into that service request from Request Center are associated with that service CI.

    An administrator can also use SBM Application Administrator to link a service CI to a service request at the project level. This service CI will be set by default for all requests submitted from the SBM User Workspace and for all requests submitted from Request Center to service requests not already linked to a service CI as described above.

    Note: To implement this feature as part of an upgrade from a previous version of SOO, you must follow the steps described in the Serena Orchestrated Ops On-Premise Upgrade Guide to upgrade the following process apps:
    • SRC - Service Request
    • SSM - Configuration Management System

Solution Improvements

  • Configuration Management System changes:
    • The Relationship Explorer for configuration items (CIs) in the Configuration Management System (CMS) application has been enhanced and includes new navigational features, including the ability to view details of items in the graph in a popup window, show or hide the type of relationship between items, and open the graph in a separate window.
    • Constraints can now be defined to prevent relationships that do not make sense, such as "Server runs on Software," from being created. An administrator can select which parent and child CI types are allowed for each relationship type. Validation checks ensure that the constraints are enforced when a relationship is submitted or updated.
    • Each CI category is now represented by an icon, which is displayed in the Relationship Explorer and stored in the CI Categories auxiliary table. By default, certain icons are associated with the default categories and a computer icon is associated with new categories. You can change an icon by selecting another image stored in a provided library or by entering a URL to an image stored somewhere else.
    Note: To implement these features as part of an upgrade from a previous version of SOO, you must follow the steps described in the Serena Orchestrated Ops On-Premise Upgrade Guide to upgrade the following process app:
    • SSM - Configuration Management System
  • The new "SOO_OLA_default.htm" template is now available for e-mail notifications associated with Service Level Agreement (SLA) actions. It includes text that informs users that an item is being monitored by an SLA or OLA and has reached a level of risk or violation.
    Note: To implement this feature as part of an upgrade from a previous version of SOO, for existing actions, select this template on the Edit Notification page in SBM Application Administrator.
  • The group queues feature was expanded to include the following:
    • Problem Management now supports group queues and has an Investigation Queue state.
    • The Change Management submit form has a Change Management Team Multi-User field; the selected users become the secondary owners of the new Classification Queue state.
    • Operation Level Agreements (OLAs) are now defined for each "queue" state. The OLAs are configured to have notification e-mails sent to users after a certain threshold is reached.
    • A new "Worklist Dashboard" with three reports was added to the Incident Management, Change Management, Service Request, and Problem Management applications.
    Note: To implement these features as part of an upgrade from a previous version of SOO, you must follow the steps described in the Serena Orchestrated Ops On-Premise Upgrade Guide to upgrade the cited process apps.
  • Additional SOO-specific conditions and actions are now available for custom form actions.
    Note: To implement this feature as part of an upgrade from a previous version of SOO, you must follow the steps described in the Serena Orchestrated Ops On-Premise Upgrade Guide to upgrade the applicable process apps.
  • Change Management has been integrated with Demand Manager and can be used as a demand item application out of the box.
    Note: To implement this feature as part of an upgrade from a previous version of SOO, you must follow the steps described in the Serena Orchestrated Ops On-Premise Upgrade Guide to upgrade the following process app:
    • SSM - Change Management
  • The "Any [item] is submitted" notification changed such that the submitter of an item will not get a notification when the item is submitted. The new "[Item] submitted which affects me" notification is sent to the affected user and any additional contacts when an item is submitted.
    Note: To implement this change as part of an upgrade from a previous version of SOO, you must follow the steps described in the Serena Orchestrated Ops On-Premise Upgrade Guide to upgrade the following process apps:
    • SSM - Change Management
    • SSM - Configuration Management System
    • SSM - Incident Management
    • SSM - Problem Management

Terminology Changes

  • A "service" is now called a "service request," and a "service request" is now called a "request."

Documentation Changes

  • The new Serena Demand Manager User's Guide provides guidance to Serena Demand Center users. This guide is available on the Documentation Center.
  • The Serena Service Manager ITIL Guide was renamed to Serena Service Manager Concepts Guide.

Known Issues

Serena Demand Manager

  • The DP - Move plan to review when review date is reached notification in the SDM – Demand Plan process app that automatically transitions your demand plan to the review state once the review date is reached is lost after you promote the app for the first time. To restore the notification, follow the steps described in solution S139246.
  • Only resource teams that do not have child teams can be assigned to plans in Serena Demand Center. To work around this problem, do not establish a team hierarchy when creating resource teams in SBM Application Administrator.
  • Team name changes made in SBM Application Administrator may not be reflected in Demand Center for teams that are already assigned to plans. This problem also occurs if you delete a team. The plan capacity is correctly updated to reflect deleted teams, however.
  • The list of plan items in Master Plan view on the Demand Center Plans tab may change after users sort by rank, cost, or name. This typically occurs when the date range of plans selected for the Master Plan view extends beyond the selected date range and duration for the view.
  • Users who are assigned to the Demand Plan Reviewers role can be selected as plan reviewer, but may receive privilege errors when they attempt to view a plan in Demand Center. To work around this problem, assign the "View All Items" privilege to users with this role. You can also modify the role in SBM Composer and deploy your changes.
  • Serena Demand Center users may receive a message stating they do not have appropriate privileges to complete actions in Demand Center. This error typically occurs if you add or update role assignments for users who are currently logged in to Demand Center. To work around this problem, users should refresh their browser windows.
  • Demand Center incorrectly allows users to add Listing reports based on auxiliary tables to demand views. This may result in empty rows in the demand view. To work around this problem, edit the demand view and remove the report based on an auxiliary table.

Miscellaneous Issues

  • Prior to starting JBoss after the upgrade is finished, you must delete the XmlSchema-1.4.7.jar file from the sdf.war\WEB-INF\lib directory in order to successfully use SOO 4.0. You can delete this .jar file before or after the upgrade. This applies to upgrades from any prior version of SOO.

Issues for On-demand Systems

  • Customized notification e-mail templates provided with Serena solutions may not be available. Contact support for a resolution to this problem.