Scribd
Upload
27 views

Example Two

The document summarizes internal strengths, opportunities, weaknesses, and threats for an organization. Key strengths include automation of manual work, diverse team skills, and established on-call mechanisms. Opportunities include improved reporting, inventory management, and dashboards. Weaknesses involve lack of monitoring, version management, and inconsistent operational readiness. Threats include resource constraints, split documentation, and explosive growth without additional help.

Uploaded by

api-289267628
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
27 views

Example Two

The document summarizes internal strengths, opportunities, weaknesses, and threats for an organization. Key strengths include automation of manual work, diverse team skills, and established on-call mechanisms. Opportunities include improved reporting, inventory management, and dashboards. Weaknesses involve lack of monitoring, version management, and inconsistent operational readiness. Threats include resource constraints, split documentation, and explosive growth without additional help.

Uploaded by

api-289267628
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Internal

External

Strengths
Direction accepted and supported for automation and repeatability for
manual work. Accomplishments in this area continue.

Opportunities
Automated Refreshes, Windows 2008 rollout, alignment to quarterly
releases for improvements

Commitment to standardize work tracking.


The team contains members with diverse skill sets.

Increased ability to report on what worked occurred, how well we


are doing meeting targets, and where we are spending our
operational time.
Rehosting

All database technology has various levels of support at least 2-deep


across the team.
On-call mechanisms established and working for DBA, Web, and SA team.

Basis for inventory management is in place. Improvements in


CMDB underway
Service Level Agreement work being done at management level.

Dashboards underway with measurements indicating performance on key


performance indicators.
Foundation for easy reference of operational procedures has started with
the wiki.
Patching processes are strong.

WAS console access now being controlled as part of build.

Consistent change processes are followed across all teams.

Managed State improvements have been accepted and are


underway

Weaknesses
Monitoring does not exist or is undependable for middleware and database
technology, and has not been expanded for operating system metrics.
Some monitoring has been built in-house and must be maintained
manually.
No real ability to track or manage software versions or baselines to our
builds. We do not have a unified, aligned way to track releases or
baselines.
Operational Readiness and managed status is very manual, sometimes
inconsistent, and is not followed by all technology teams

Threats
Vacation schedule mandates for associates.

Location of documentation is varied


Architecture and engineering level engagement for SOA related middleware
technologies is non existent.

Cost-containment.
Split

Server security policies

Middleware, Backup, and Linux do not have official 2-deep resource


knowledge. SQL Server pipeline is too long.
ghost hunts relating to our supported technologies.
Inability to track system capacity on database or middleware
servers.

On-call rotation for middleware and backup areas.

Upcoming DR LAB
Version Management underway

The capacity of resources, or skill sets, conflict with the ability to


provision improvements.
Inconsistent change procedures not accounting for Infrastructure
processes.

Explosive growth of additional environments with no resource help


or improvements in manageability.
Rehosting

You might also like