Abstract: A system and method for operation of an autonomous vehicle (AV) yard truck is provided. A processor facilitates autonomous movement of the AV yard truck, and connection to and disconnection from trailers. A plurality of sensors are interconnected with the processor that sense terrain/objects and assist in automatically connecting/disconnecting trailers. A server, interconnected, wirelessly with the processor, that tracks movement of the truck around and determines locations for trailer connection and disconnection. A door station unlatches/opens rear doors of the trailer when adjacent thereto, securing them in an opened position via clamps, etc. The system computes a height of the trailer, and/or if landing gear of the trailer is on the ground and interoperates with the fifth wheel to change height, and whether docking is safe, allowing a user to take manual control, and optimum charge time(s). Reversing sensors/safety, automated chocking, and intermodal container organization are also provided.

Abstract: A system and method for operation of an autonomous vehicle (AV) yard truck is provided. A processor facilitates autonomous movement of the AV yard truck, and connection to and disconnection from trailers. A plurality of sensors are interconnected with the processor that sense terrain/objects and assist in automatically connecting/disconnecting trailers. A server, interconnected, wirelessly with the processor, that tracks movement of the truck around and determines locations for trailer connection and disconnection. A door station unlatches/opens rear doors of the trailer when adjacent thereto, securing them in an opened position via clamps, etc. The system computes a height of the trailer, and/or if landing gear of the trailer is on the ground and interoperates with the fifth wheel to change height, and whether docking is safe, allowing a user to take manual control, and optimum charge time(s). Reversing sensors/safety, automated chocking, and intermodal container organization are also provided.

Abstract: An approach provides support for automatic fault isolation in a managed services system. A fault indication corresponding to a communications network of a customer is determined. An analysis is performed to determine a root cause of the fault indication using information associated with the determined fault to output an alarm. A determination is made whether the alarm is associated with a maintenance event to update the alarm. Further, a workflow event corresponding to the alarm is created.

Abstract: An approach for supporting automated fault isolation and recovery is provided. An alarm indicative of a fault within a customer network is received. An event within a workflow is created in response to the alarm, wherein a new trouble ticket is generated as part of the workflow. Communication with a trouble management system is performed to correlate the alarm with an existing trouble ticket. The new trouble ticket is associated with the existing trouble ticket.

Abstract: An approach for supporting automated fault isolation is provided. An alarm is received indicating a fault within a customer network that includes one or more network elements. The customer network being monitored by a service provider. A script is retrieved for specifying a dialogue with the network elements for data collection. A command is transmitted to the customer network according to the one script to obtain data from the network elements, wherein the data is utilized to determine the fault. Further, a workflow event corresponding to the alarm is generated, wherein resolution of the fault is automated according to the workflow event.

Abstract: An approach for supporting automated fault isolation and recovery is provided. A notification configuration option is transmitted to a browser interface utilized by a user associated with a customer network that is monitored by a service provider, wherein the user selects the notification configuration option to input notification information. The notification information is received, via the browser interface, from the customer. A notification message is received from a platform configured to create a workflow event in response to an alarm indicative of a fault within the customer network, wherein isolation and recovery of the fault is performed according to the workflow event, the notification message including information about the customer network during the fault isolation and recovery process. The notification message is transmitted in accordance with the stored notification information.

Abstract: An approach for supporting automated fault isolation and recovery is provided. A workflow event corresponding to an alarm indicative of a fault within a customer network is generated. Recovery from the fault is automated according to the workflow event. Alarm information is transmitted to a maintenance management system, wherein the alarm information specifies information about the alarm. A maintenance event information from the maintenance management system is received in response to the transmitted alarm information. Additionally, it is determined whether the alarm is correlated to a maintenance event based on the maintenance event information. Automated handling of the alarm is differentiated based on the correlation.

Abstract: A system and method is described for using a component business model to partition a business into non-overlapping components, and then allocating different components to appropriate organizing strategies, based on attribute values assigned to each component. In the best mode of implementation there are two attributes: whether or not the component differentiates the business within the market place; and whether the component is industry standard or is tailored by the organization. These attributes and their values map the components of the business to a matrix. Based on the combination of attribute values in each cell of the matrix, available organizing strategies are also mapped to the matrix, thereby identifying for each component an appropriate organizing strategy.

Abstract: An approach for supporting automated fault isolation and recovery is provided. A notification configuration option is transmitted to a browser interface utilized by a user associated with a customer network that is monitored by a service provider, wherein the user selects the notification configuration option to input notification information. The notification information is received, via the browser interface, from the customer. A notification message is received from a platform configured to create a workflow event in response to an alarm indicative of a fault within the customer network, wherein isolation and recovery of the fault is performed according to the workflow event, the notification message including information about the customer network during the fault isolation and recovery process. The notification message is transmitted in accordance with the stored notification information.

Abstract: An approach for supporting automated fault isolation and recovery is provided. A notification configuration option is transmitted to a browser interface utilized by a user associated with a customer network that is monitored by a service provider, wherein the user selects the notification configuration option to input notification information. The notification information is received, via the browser interface, from the customer. A notification message is received from a platform configured to create a workflow event in response to an alarm indicative of a fault within the customer network, wherein isolation and recovery of the fault is performed according to the workflow event, the notification message including information about the customer network during the fault isolation and recovery process. The notification message is transmitted in accordance with the stored notification information.

Abstract: The method and system uses the component business model as a framework for locating business activities. Business value drivers are identified, related in an influence model, and structured into a prioritized driver tree. The driver tree is used to determine the relative contributions of leaf drivers to the overall value of the business. Business activities contributing to the leaf drivers are then identified, and the relative contributions of the leaf drivers are allocated to the business activities and then rolled up to the components for display as a heat map overlay on a component map.

Abstract: A method and system are described for using the structure and relationships between components in a component business model of an enterprise to assign components providing monitoring data to a management component. In response to the monitoring data, the management component executes a business rule invoking a service that alters a behavior of the enterprise. The management component contains data rules limiting the information provided by the assigned components, analysis rules defining the interaction between components, and report rules for consolidating recommendations for altering behavior of the enterprise, including decisions to invest in certain aspects of the business, to reengineer certain processes of the business, and to alter operation of certain aspects of the business.

Abstract: A system and method are described for using a Component Business Model (CBM) to transform a business. A CBM map is used to identify components that collaborate to provide a specified capability, and a repository supporting the CBM map is filtered to provide a view of the identified components that highlights how they collaborate. The view is used to identify component features contributing to the specified capability. The specified capability is then enhanced by a transformation strategy that includes re-engineering particular components, identifying a pattern characterizing the collaboration between components and adding a component to perform the collaborative pattern, and/or adding an additional feature to the collaboration and adding component to perform the additional feature. The CBM repository provides exemplar best practices that can be adapted for use in a re-engineered component.

Abstract: A method of combining businesses by creating a target component map based on the business strategy of the resulting company, and using that target map to generate a component map for each constituent company in the combination. The constituent component map describes the current state of each component instantiated in the constituent company. Where there is no overlap between constituent companies with respect to components in the target map, those component instantiations are carried over to the resulting company. Where there is overlap, a comparative analysis is done and a ‘best fit’ component is recommended for inclusion in the resulting company. A transformation plan is developed to build the resulting company from those component instances selected for inclusion, in accordance with the target component map. Where the business strategy for building the resulting company includes a divestiture, the transformation plan provides alignment of the components to be divested in order to optimize the divestiture.