The process of using a company's resources in the most efficient way possible.

These resources can include tangible resources such as goods and equipment, financial resources, and labor resources such as employees. Resource management can include ideas such as making sure one has enough physical resources for one's business, but not an overabundance so that products won't get used, or making sure that people are assigned to tasksthat will keep them busy and not have too much downtime. The concept of "Data Management" arose in the 1980s as technology moved from sequential processing (first cards, then tape) to random access processing. Since it was now technically possible to store a single fact in a single place and access that using random access disk, those suggesting that "Data Management" was more important than "Process Management" used arguments such as "a customer's home address is stored in 75 (or some other large number) places in our computer systems." During this period, random access processing was not competitively fast, so those suggesting "Process Management" was more important than "Data Management" used batch processing time as their primary argument. As applications moved more and more into real-time, interactive applications, it became obvious to most practitioners that both management processes were important. If the data was not well defined, the data would be mis-used in applications. If the process wasn't well defined, it was impossible to meet user needs.

The official definition provided by DAMA International, the professional organization for those in the data management profession, is: "Data Resource Management is the development and execution of architectures, policies, practices and procedures that properly manage the full data lifecycle needs of an enterprise." This definition is fairly broad and encompasses a number of professions which may not have direct technical contact with lower-level aspects of data management, such as relational database management. In modern management usage, one can easily discern a trend away from the term 'data' in composite expressions to the term information or even knowledge when talking in non-technical context. Thus there exists not only data management, but

also information management and knowledge management. This is a fairly detrimental tendency in that it obscures the fact that is usually always plain, traditional data that is managed or somehow processed on second looks. The extremely relevant distinction between data and derived values can be seen in the information ladder. While data can exist as such, 'information' and 'knowledge' are always in the "eye" (or rather the brain) of the beholder and can only be measured in relative units. Capacity determines how much work the resources can do. In Project Server, capacity is defined for each resource. Individual resources are often aggregated into groups based on location, skill, job function, organizational affiliation, or other attribute for resource management planning and reporting. Utilization describes how the resources are deployed and allocated. Utilization can be divided into planned (what is scheduled for the future) and actual (what happened in the past). Resources are utilized when they are assigned to work on projects. Capacity is often expressed in hours per week. For example, Scott works 9 A.M. to 5 P.M. Monday through Friday for a total of 8 hours of work capacity per day, or 40 hours per week, as determined by his working time calendar.

Base capacity (also known as baseline capacity) is a new concept of maximum work capacity and is only used for RM reports on Project Server. Microsoft Office Project Professional 2007 and project managers in general do not use base capacity. For example, a company has the following holidays: January 3, May 30, July 4, September 5, November 24-25, and December 23-26. The holidays reduce a resource's capacity to the base capacity. Actual capacity is base capacity minus personal time off. For example, Brad is taking two weeks off in July. Project Professional uses the actual capacity combined with the availability contour to determine when a resource is available. Remaining availability is actual capacity minus utilization. Availability contour is the representation of times a resource is available to do work. Project Server always stores timephased data in a contour. Work is the time expended on a task, as recorded by timesheets.

Effort is the progress toward task completion, as specified by status updates. If work and effort are equal, then the term is work.

Resource Management Data

There are many things that you can do with the PSI to integrate resource RM data with other applications, and some things that you cannot do RM data in Project Server can be grouped into several logical areas, as follows:

Enterprise resource pool is the list of resources managed by Project Server, and defines the capacity of those resources. Calendars and resource capacity refers to every resource that has an associated calendar where working time can be uniquely specified. Resource utilization summary data contains one entry per project (or nonproject work category) for each enterprise resource and describes how much time the resource is committed to the project. Project assignments provide task-level detail on what work a resource is assigned to on each project. Timesheets and status updates represent work and effort, respectively. Non-project time data keeps track of demands other than task assignments on a resource's time, such as vacation, training, sick time, and so forth. Resource plans capture high-level resource requirements for projects when detailed (such as task-level) plans with tasks and assignments are not available. Resource custom fields contain the enterprise custom field values associated with each resource.

Enterprise Resource Pool The enterprise resource pool maintains the list of resources managed by Project Server. Figure 1. Resource Sheet view

The core resource data includes the resource attributes shown in the Resource Sheet view in Project Professional (Figure 1), and in the resource cost rate tables on the Costs tab in the Resource Information dialog box (Figure 2). Figure 2. Cost rate tables in the Resource Information dialog box

Enterprise resource data includes the availability contour, visible on the General tab of the Resource Information dialog box (Figure 3). The availability contour, along with the resource's calendar, defines that resource's capacity to perform work. Figure 3. Availability contour

The Project Server Resource Web service includes the Resource class with PSI methods for editing enterprise resources. The methods that use the ResourceDataSet parameter include CreateResources and UpdateResources. Figure 4 shows the main entities that represent enterprise resources in the ResourceDataSet. Figure 4. Entity-relationship diagram for the ResourceDataSet

Following are the five main tables that contain resource information in the ResourceDataSet.

ResourcesDataTable contains the intrinsic resource attributes that are visible in the Resource Sheet view in Project Professional. The attributes include resource name, type, enterprise ID, and so forth. ResourceCustomFieldsDataTable contains the values associated with each resource for enterprise custom fields that are defined in Project Server. ResourceRatesDataTable contains the rate table information (shown in Figure 2). Each row in the table corresponds to one line in the rate table grid of the Resource Information dialog box. ResourceAvailabilitiesDataTable contains the availability contour (shown in Figure 3). Each row in the table corresponds to one line in the resource availability grid. CalendarExceptionsDataTable contains the specific exceptions to working time for a resource. For example, Aaron is normally available 9 A.M. to 5 P.M., but March 6 through March 17 he is available 8 A.M. to 12 noon only on Tuesdays and Thursdays.

Calendars and Resource Capacity

Every enterprise resource has an associated calendar that defines the resource's hours of work as well as working and non-working days. Project Server creates the resource calendar when the resource is added. The resource calendar has the same GUID (the CAL_UID property in CalendarsRow) as the resource. You can update calendar data from the Resource Information dialog box in Project Professional. Click Change Working Time on the General tab to see the Change Working Time dialog box (Figure 5). For more information, see Calendar Exceptions and Effective Work Weeks. Figure 5. Calendar exceptions

Calendars define the hours of work or shifts for each day of the week (Sunday through Saturday) and also show which days of the week are working and which are non-working days. You can define calendar exceptions that override the normal working/non-working time for specific dates or ranges of dates. For example, if Monday to Friday are normally working days, a calendar exception can declare a specific Friday as a non-working day to reflect a company holiday. Calendar exceptions apply to a specific date or date range. They can specify certain dates to be working or non-working days or change the hours of work (shift information) for specific working days. The resource dataset contains the list of calendar exceptions but does not expose the default shift information for each day of the week. Figure 6 shows relationships of the following DataTable and DataRow objects in the ResourceDataSet and CalendarDataSet:

ResourcesDataTable

ResourcesRow CalendarExceptionsDataTable (resource-specific exceptions in the ResourceDataSet) CalendarsDataTable CalendarsRow (specific resource calendars and base calendars) CalendarExceptionsDataTable (base exceptions in the CalendarDataSet)

Figure 6. Entity-relationship diagram for resource calendars

Resource calendars are based on one of the enterprise calendars defined in the system. By default, the resource inherits the hours of work and work days along with the list of calendar exceptions (such as holidays) that are defined in the base calendar. You can override any base calendar item for an individual resource using the Change Working Timedialog box. A resource's capacity is determined by the hours of work defined in their calendar combined with the units defined in their availability contour. If the resource's hours of work are defined as 9-5 M-F (in other words, 8 hours/day, 5 days/week) at 100% availability, then their capacity is 40 hours per week. If the calendar defines their hours of work as 9-5 M,W,F (that is, 8 hours/day, 3 days/week) and the availability contour defines their maximum units as 50%, then their capacity would be 12 hours per week. the idea of resource base capacity in addition to actual capacity. Base capacity is calculated using the specified base calendar for the resource and reflects the normal hours of work for the organization as well as company-wide holidays. Actual capacity is calculated using the resource calendar and includes the unique resource calendar exceptions in addition to those in the base calendar. A resource calendar inherits the shift definitions and any exceptions in the enterprise calendar on which the resource calendar is based. Resource Utilization Summary Summary-level resource utilization data is useful for medium-term and long-term planning and high-level decision making. Data structures, called summary resource assignments(SRAs), maintain the data. The SRAs store the time-phased

commitment of a resource for each project to which the resource is assigned. There is one SRA per resource per project. The summary resource assignments are operational data. The Project Professional Resource Usage view (Figure 7) shows an open project with the summary resource usage values for tasks in the project and also the total usage of the resource for other projects. Figure 7. Summary resource assignments in the Resource Usage view

SRAs also supply resource utilization data for the Resource Availability page in Project Web Access (Figure 8). For more information about resource availability, see How to: Calculate Resource Availability in OLAP Cubes. Figure 8. Resource Availability page in Project Web Access

Summary resource assignments are created from the following data:

Project plans: roll-up of all the detailed assignments in the project for each resource Resource plans: time-phased data entered by the user Timesheets: time-phased administrative (non-project) working-time entered by the timesheet user

Together, these data sources can capture all the time commitments for the resources managed in the system and provide an accurate picture of how the resources are being utilized for both project and non-project work. When a project has both a resource plan and detailed assignments, double-counting of resource utilization is avoided through a user-specified option on the resource plan (Figure 9) indicating which should be used to calculate the SRA shown in the usage view, availability graph, and reports.

Figure 9. Resource Plan in Project Web Access

As with normal assignments, the work recorded in the summary resource assignments is time-phased and is divided into actual and remaining work. Actual work can only be entered for assignments in project plans or in timesheets, but not for resource plans.

Project Assignments Assignment-level data is useful for day-to-day operational decision making. Assignments are created when resources are assigned to tasks in a project plan. They represent the association between the task and the resource and, in the case of work resources, are used to track how much work is scheduled to be performed on the task by the resource and how much work has already been done. Figure 10 shows relationships of the following DataTable objects in the ProjectDataSet:

Assignment Data Table Project Resource Data Table Project Data Table Task Data Table

Figure 10. Entity-relationship diagram for assignments

When a project is published, the assignments are visible in Project Web Access. Team members (resources) can report progress in their Task Center page (My Work) and resource managers can see a summary of assignments in the View Assignments page. To see resource assignments (if you have permission to do so), click Resource Center in the Quick Launch, select one or more resources on the Resource Center page, and then click View Assignments in the Actions dropdown menu or tab. All the assignments for a resource in a project are rolled up to create summary resource assignments that keep track of the total amount of work planned (or done) by the resource on that project.

Timesheets and Status Updates Timesheets are a new feature in Project Server 2007. Timesheets and status updates both allow the capture of time-phased actual work data from users and resources. Timesheets can stand alone. That is, an organization can use only the timesheet feature of Project Server or can choose to use timesheet data for project management and status updates. Resources need to provide data only for one of the systems. If resources use timesheets, the data can be imported to status updates for project rescheduling. To enable project time entry by timesheet only, the Project Server administrator must configure Project Server to use timesheets and status in a synchronized mode. On the Server Settings page, click Task Settings and Display under the Time and Task Management section. On the Task Settings and Display page, select Time entry by Timesheet only, users will sync to update tasks. Users still have to synchronize the tasks grid with the timesheet and submit to the project manager before the update affects project scheduling. The timesheet allows entry of both project work and non-project time and provides a vehicle for capturing accurate and comprehensive resource utilization data. The timesheet allows actual work for projects to be entered at the detailed task/assignment level or at the project level, depending on the needs of the organization. By default, timesheet data does not affect project scheduling. Timesheets are intended to provide accurate time accounting data that can be used in audit reports and for integration with external accounting applications. The Project Server TimeSheet Web service includes the TimeSheet class with methods for developing timesheet and line-of-business (LOB) integration applications. The TimeSheet Web service includes the following DataSet classes:

TimesheetDataSet is the primary timesheet DataSet and includes the Actions, Actuals, Audits, CustomFields, Headers, and Lines tables TimesheetListDataSet ResourceDataSet duplicates the ResourceDataSet in the Resource Web service, so that timesheet applications need to use only the TimeSheet Web service

In addition to methods and datasets in the TimeSheet Web service, the Admin class includes several methods along with the following DataSet classes in the Admin Web service for managing timesheet audits and reporting periods:

TimesheetAuditExportDataSet TimesheetLineClassDataSet UnsubmittedTimesheetDataSet

Status updates work essentially the same way in Project Server 2007 as they did in Project Server 2003. Status updates capture actual work at the task and assignment levels and are intended primarily as a vehicle for team members to report progress to the project manager. When the project manager accepts a status update, he or she can reschedule the project plan. The project manager does not have to open the project in Project Professional 2007 to reschedule it because Project Server includes a server-side scheduling engine. The Project Server Statusing Web service includes the Statusing class with methods for managing assignments and status updates. The Statusing Web service includes the following DataSet classes:

AssnHistoryDataSet DelegationDataSet ImportTimesheetDataSet ScheduleDataSet StatusApprovalDataSet StatusingAssignmentsDataSet StatusingDataSet StatusingTimephasedActualsDataSet StatusTransactionDataSet ProjectDataSet duplicates the ProjectDataSet in the Project Web service

Non-Project Time Non-project time, like project assignments, is fine-grained data useful for day-today operational planning and decision making. Non-project time can include administrative time or non-working time.

Administrative time in Project Server 2002 was implemented as calendar exceptions. Project Server 2003 introduced Admin projects, but scheduling and approval did not work correctly for Admin projects. Project Server 2007 includes three types of non-project time by default:

Working administrative time Non-working administrative time Unverified timesheet lines

Project Server administrators can create other categories of non-project time, for example training time. Project Server 2007 keeps track of resource time commitments and utilization for non-project work such as training or support activities and for non-working time such as vacations. To create or edit new types of administrative time, on the Server Settings page, click Administrative Time under the Time and Task Management section. Following are the default types of administrative time.

Administrative time (working) Sick time (non-working) Vacation time (non-working)

Timesheets capture non-project time and classify it into the categories defined by the system administrator. With the appropriate Project Server setting, resources can add timesheet lines for future time as well as past time, and include non-project time such as vacations for future planning. Timesheets are normally closed to changes after the timesheet approver accepts the timesheet. Future time periods should be kept open, in case of changes. You can also indicate specific non-working time on a resource's calendar by using a calendar exception. Calendar exceptions and future non-working time on timesheets prevent work from being scheduled on the non-working days or time periods. Non-project work is reflected in summary resource assignments. Projects allow both non-project work and project work to be scheduled so you can see where resource overallocations exist.

Resource Plans Resource plans provide a vehicle for capturing high-level resource requirements for projects and for non-project requirements, such as support and maintenance activities. Resource plans are useful because resources are not bothered with unapproved assignments just to enable planning, such as in the following scenarios:

Initial project planning of resource needs. Planning a project by phase. Resources see only assignments for the currently approved phases; resource plans capture the rest of the project.

Resource utilization views and reports can include resource plans as well as project assignments and non-project timesheet entries. Resource plans allow project and resource managers to express resource requirements in terms of the number of people or full-time equivalents (FTEs) over a period of time. For example, the statement, "We need three analysts for four months," is useful in the early stages of project planning. Later stages can use fine-grained time requirements that derive from project plans and timesheets after resources are assigned to tasks. Project Server uses resource plan data to create summary resource assignments which are used by the other parts of the system that consume resource utilization data.

Resource Custom Fields The ResourceCustomFieldsDataTable stores the enterprise custom field values associated with each resource. Each row in the table represents one value of one custom field for one resource. A row contains the GUID of the resource to which the custom field belongs as well as the GUID of the custom field definition in the CustomFieldsDataTable. Figure 11. Entity-relationship diagram for resource custom fields

For custom fields that have an associated lookup table, the row also contains the GUID of the corresponding lookup table value in the property MD_PROP_UID. You can see theResourceCustomFieldsRow properties also include the field type enumeration and columns for the resource custom field types. The ResourceCustomFieldsRow has columns only for Date, Duration, Flag, Number, and Text. Additional custom fields that apply to resources include Start and Finish, which are specific date custom fields, and outline code custom fields such as RBS. For more information, see Local and Enterprise Custom Fields. Multivalue fields can have multiple rows for the same resource and custom field combination. If the row associated with a custom field is absent from the table for a particular resource, its value is assumed to be null.

Resource Management Data in Project Server Databases The Project Server architecture includes four separate databases. For a diagram of the architecture and databases, see Project Server Architecture.

The Draft database stores the working copy of projects and resource plans while they are being edited and updated. The Published database contains the versions of the projects and resource plans that are visible to other Project Server users. The Published database also stores the enterprise resource pool, summary resource utilization data, and all other resource-related data as well as enterprise calendars, custom fields, look-up tables, and data required by Project Web Access features and functions. The Reporting database contains a denormalized, report-friendly copy of the data in the Published database. The Archive database stores copies of projects that are explicitly archived. The Archive database is not used by any of the resource management features in Project Server.

Project and resource plans are updated first in the Draft database, and then the updates are propagated to the Published database in response to an explicit publish operation. Generally a user publishes a project after she is finished making changes and wants to make those changes visible to other users. All updates to projects and resource planswhether they originate from Project Professional or Project Web Access, or from calls to PSI methods in other applicationsare made in the Draft database first. Changes made to the Published database are automatically propagated to the Reporting database. Changes include projects and resource plans that have been published as well as changes to entities such as resources and calendars that Project Server stores in the Published database. Benefits realized by engaging DRM for services include:

Increased Customer Focus - Enables the customer to focus on their core business instead of their Database Management Software architecture. Experienced Database Administration (DBA) Team - Provides knowledgeable, professional, and experienced staff. Cost Savings - Provides cost savings from shared DBA services as well as a possibility of shared licensing.

Around the Clock Database Administrator Support - Provides 24x7x365 support. Full Range of Database Administrator Services - Provides a full range of database administration functions and services.

The common services provided by DRM include installation of databases (and their Database Management Systems [DBMS]), configuration, troubleshooting, backups, disaster recovery preparation and other general maintenance functions such as implementation of DBMS version updates. DRM provides support for Dotcom/DB, Oracle and MS SQL Server database environments. DRM also provides assistance with Lotus Domino, TIBCO Business Works, Business Objects, data analysis and data design.

Some of the many services provided by DSG include:

System Administration Server Virtualization Data Storage Enterprise Backups Disaster Recovery System Monitoring Terminal Services

Tier 3 User Administration.

Objectives 1. Describe basic file organization concepts and the problems of managing data resources in a traditional file environment. 2. Describe how a database management system organizes information and compare the principal database models. 3. Apply important database design principles. 4. Evaluate new database trends. 5. Identify the challenges posed by data resource management and management solutions.

Technical Support is comprised of five teams: 1. The Network Team - This team is responsible for the mainframe communication products such as VTAM, TCPIP, CA-Spool, HOD, PKZip 2. The Performance Management and Automation Team - This team is responsible for the mainframe automation products and monitoring products such as Netview, TMON, the Control Product Suite, Panvalet, Easytrieve, Sysview and Oracle. 3. The Database Team - This team is responsible for the mainframe Database transaction managers such as Datacom, IMS & CICS and supports the associated data base tools, utilities, and performance related products. 4. The MVS Team - This team is responsible for the Operating System software such as z/OS, and all its associated products such as SMP/E, RMF, JES2 HCM, TSO, SDSF, REXX, and many more. 5. The Storage Team - This team is responsible for managing the placement, the copying, the restoring and the organizing of our customers and the Operating systems data onto DASD (Direct Access Storage Device), Physical Tape, and Virtual Tape using tools such as SMS, HSM, FDR, ABR, and Upstream.

his team is responsible for development and support of applications including but not limited to STARS, Email (Exchange and Webmail), LDAP, content management for websites, and custom web applications. Matt DeClue leads this dynamic team of highly skilled and technically diverse individuals. In addition to his leadership role, Matt provides strategic direction for the technology infrastructure utilized to support APPS service offerings, establishes best practices and procedures, and oversees day-to-day operations within the group. Team Responsibilities Include (but not limited to):

Work assignments Staffing levels Project management & oversight Change control review & approval Development of procedures for project acceptance Change control & application architecture Problem escalation

Web/Application Services:

Initial design/build (New) Enhancement/Add-on (Existing) Website Design (Static pages to fully interactive) Technology Migration (EOL to Current) On-going web/application development and support (even if we didn't build your website/application) Integration with other State of Arizona systems and third-party systems including email, HRIS & AFIS Integration with the State of Arizona payment portal (credit card/debit card) for direct deposit into agency accounts with updates to AFIS Integration with mobile devices such as Blackberry devices, laptops & pocket PC's Development for specific devices such as Blackberry devices and Windows Mobile phones Domain Name Services (Statewide DNS) Site Certificates - SSL 128bit Web Content Management (CMS)

Development in a variety of languages such as: classic ASP 3.0, ASP.Net, C# 3.0, Java/Javascript, VBScript Applications hosting on Windows/Unix platforms Website hosting on IIS/Apache platforms Microsoft Exchange (POP3 email) Web/Application integration with your email provider

Other Services

Project Management Business Analyst Technical Consultation/Documentation

A New Direction for Data Resource Management

What is the future for data resource management? Considering the past practices and the current data resource situation in most public and private sector organizations, is a new direction needed for developing and managing the data resource? Is a new orientation toward improved data resource quality and increased business support needed? Data administration has not been an effective way to manage an organization's data resource.. People have tried to administer the data with an orientation toward the data, rather than towards support of the business. Many organizations have been, and still are, oriented toward the technology aspect of information technology by trying every new technology that comes along hoping that it will help them administer the data and provide better business support. They are looking for that elusive silver bullet and are sacrificing future business support for current needs. A new direction is needed that focuses on managing data as a critical resource of the organization to directly support its business activities. The data resource must be managed with the same intensity and formality that other critical resources are managed. Organizations must emphasize the information aspect of information technology, determine the data needed to support the business, and then use appropriate technology to build and maintain a high-quality data resource that provides that support. In other words, organizations must manage data as a resource rather than administer the data. Business Information Demand A new direction for formal data resource management begins with an understanding of an organization's demand for information to support their business activities. Thebusiness information demand is an organization's continuously increasing, constantly changing need for current, accurate, integrated information, often on short or very short notice, to support its business activities. It is an extremely dynamic demand for information to support the business. The result of past data resource management practices is rapidly increasing quantities of disparate data. Disparate data are data that are essentially not alike, or are distinctly different in kind, quality, or character. They are unequal and cannot be readily integrated. They are low-quality, defective, discordant, ambiguous,

heterogeneous data. The data resource is in a state of disarray that does not, and cannot, adequately support and organization's dynamic need for information. Disparate data cause a dilemma for most organizations. The business needs integrated data to meet the business information demand, yet disparate data are being created faster than they have ever been created before. There is no end in sight for a resolution to this dilemma with the current orientation. In fact, the current orientation will lead to increased quantities of disparate data and decreased support for the business because the data resource naturally drifts toward disparity of it is not properly managed. The sooner organizations make a conscious effort to alter the natural drift away from disparity, the easier it will be to achieve a high-quality data resource that supports the business information demand. The surprising thing is that most people will not object to formal data resource management. Most people really want a higher quality data resource, are enthused about improving data resource quality, and want to share data. The problem is that they just do not know how to go about those tasks without impacting business operations. Data Resource Quality Data resource quality is a measure of how well the organization's data resource supports the current and the future business information demand of the organization. The data resource cannot support just the current business information demand while sacrificing the future business information demand. It must support both the current and the future business information demand. The ultimate data resource quality is stability across changing business needs and changing technology. This stability across change is the ideal that provides the foundation organizations need to become an intelligent learning organization--an iorganization. A high-quality data resource can only be achieved by developing a comparate data resource where the data are alike in kind, quality, and character, and are without defect. They are concordant, homogeneous, nearly flawless, nearly perfect, highquality data. The data are easily identified and thoroughly understood, readily accessed and shared, and utilized to their fullest potential. Common Data Architecture A comparate data resource must be developed within a single, organization-wide common data architecture. A data architecture is the science and method of designing and constructing a data resource that is business driven, based on realworld objects and events as perceived by the organization, and implemented into

appropriate operating environments. It is the overall structure of a data resource that provides a consistent foundation across organizational boundaries to provide easily identifiable, readily available, high-quality data to support the business information demand. The common data architecture is a formal, comprehensive data architecture that provides a common context within which all data at an organization's disposal are understood and integrated. It is subject oriented, meaning that it is built from data subjects that represent business objects and business events in the real world that are of interest to the organization and about which data are captured and maintained. The common data architecture contains concepts, principles, and techniques for developing and maintaining formal data names, comprehensive data definitions, proper data structures, precise data integrity rules, and robust data documentation. Documentation about the data resource is often referred to as meta-data, which is commonly defined as data about the data. This term has been misused and abused to the point that its real definition is unclear. An increased emphasis on meta-data only promotes the concept that they are something different from the business data that must be designed and managed independent of the business data. The term data resource data helps people understand the importance of thoroughly documenting the data resource. Data resource data are any data that document the data resource and help people understand, manage, and use that data resource to support the business information demand. Data resource data are a major segment of the organization's data resource that are designed, developed, managed, stored, retrieved, and used the same as any other segment of the data resource. They support the business of managing the organization's data resource just like human resource data support the business of managing the organization's human resource.

A New Direction The traditional orientation to building an organization's data resource is to develop data models independent of an organization-wide data architecture. In many organizations, only 10% to 15% of their data resource has ever been modeled and portions of the data resource have been modeled multiple times with different tools and techniques. Many data models are oriented toward developing the database rather than understanding the business. This from-below, brute force physical approach leads to increased data disparity. A new data resource management direction emphasizes the development of an integrated data resource within one organization-wide, subject oriented common data architecture. A data model is developed using a subset of the data resource data for a specific business activity for a specific audience. The concept is the same as any other segment of the data resource, such as affirmative action, where specific data are extracted from the data resource and presented to the affirmative action audience in a form that is useful to them for performing their business activity. The specific data model techniques and notations are simply an option for presenting a data model to a specific audience. Data model are not developed independent of the common data architecture. There are no more conflicting data models or data model disparity because all data models are developed within the context of the common data architecture. Conclusion The future of data resource management depends on a change in direction from administering the data to managing data as critical resource of the organization. This new data resource management direction emphasizes development of a highquality, integrated, comparate data resource within a common data architecture that is stable across changing business needs and changing technology. It emphasizes formal data resource management that focuses on the information aspect of information technology to support both the current and the future business information demand of an intelligent learning organization. The future of data resource management depends on development of an integrated comparate data resource within a common data architecture that improves data understanding and promotes data sharing. It requires a self-perpetuating cycle where improved data resource quality increases data sharing, increased data sharing improves data resource quality, and so on. Organizations that change their direction toward formal data resource management, establish a common data

architecture, maintain robust data resource data, and manage data as a critical resource to support current and future business information needs will be the organizations that survive. Those that don't will fail to be fully successful due to information deprivation.

A PROJECT REPORT Of Management information system

PUNJAB TECHNICAL UNIVERSITY JALANDHAR ACADEMIC SESSION (2010-2012)

In partial fulfilment of the requirement for the award of Degree of Masters in Business Administration (MBA) Submitted to S. Sachleen Singh Assistant Lecturer of Mgt. & IT CTIMIT Submitted by Anmol kumar