Tags |
|
|
Links |
|
|
Hub You - Understanding the IRM/MRP Analogy
Well, I felt that quality over anything else should lead to success so I made sure everything on my site worked properly and established connections with reputable people to help guide me through this learning experience. Looking at the competition (Orbitz, Travelocity, Cheaptickets,etc), I felt that I would be lucky to scratch even a few sales. Interestingly, when I checked prices I found that I actually compete very well. My confidence grew and so my journey began.(Free Advertising,learning experiences) Ok, well this one is interesting because I've had mixed results from many attempts at growing my business. The first thing I tried was free advertising. I filled out countless classifieds adds over a period of several days and many, many hours. I do not think that was incredibly effective, so I turned to the FFA sites. I submitted to thousands of FFA sites, I found free link sites, free link dumps. Anywhere I could post my link I did, and I still do. This strategy has, if nothing else at leasted boosted my confidence, but produced few visitors to my website.(Continued strategies of Free Advertising) Now I was ready to submit to various search engines. This seemed endless and boring. I submitted by hand to many search engines, indexes, etc, but this job seemed endless because it seems no matter how many search engines I can submit to, I can still find more to submit too....I thought well I must submit to the most popular ones, Yahoo, Google, etc., so I did. This has helped and I've also learned that international search engine submissions are also an excellent avenue to go down.(Free Advertising/
DIFFERENT METHODOLOGIES
The three classes of resources also hints at three different methodologies for developing them:
Enterprise Engineering Methodology (EEM) - primarily concerned with developing business resources and is performed by Enterprise Engineers (Business Analysts)
Information Systems Engineering Methodology (ISEM) - primarily concerned with system resources (Software Engineering is considered a subset of ISEM), Such resources are developed by Systems Engineers and Software Engineers (analysts and programmers).
Data Base Engineering Methodology (DBEM) - primarily concerned with data resources and is performed by Data Engineers and Data Base Administrators.
Although the methodologies will define "who" is primarily responsible for their development, it is quite common for information resources to cross methodology boundaries. For example, during EEM systems and "objects" (logical files) are identified which are later implemented by ISEM and DBEM respectively. During ISEM, application logical files are identified and detailed later in DBEM. In DBEM, physical files for a specific application are designed and delivered to ISEM in Software Engineering. This means resources are initially identified and then refined in ensuing phases of the various methodologies. In this regards, an IRM Repository is used as a "scratchpad" by developers to record the specifications of information resources.
Project Management and Quality Assurance will also find information resource definition helpful in their assignments. The phases of the methodologies dictate which resources must be used and their degree of definition. For example, in ISEM, the need for specific data elements must be identified in Phase 1 (to support an information requirement), either new or established data elements to be re-used. At this time, for new data elements, only its logical definition must be supplied. The physical attributes of the data elements (e.g., length, picture,
When you think about it, without more money then you need for your family, you can barely contribute to society. While there are many ways to contribute to society, money is often needed to make a difference for other people. Money is needed for research. Money is needed for clothes. Money is needed for resources.Money that is needed for her research is crucial in a sense. Not everyone can contribute to the research itself. Money must be provided to do the research as well as to pay the research technicians.Contribute to Society.Often, when we don't create the extra money that we can contribute, we find ourselves feeling, apathetic to causes. Maybe this apathy comes from knowing that when we are capable, we have a responsibility to not only barely meet our own means. We realize it is important to create a way of abundance where we can contribute to society and make a difference for others who may not be as blessed.It's quite common that people who have an abundance of money will contribute to society. They are thankful for what they have and often what they have has been created through business ownership and network marketing companies.A very low percentage of people inherit wealth. Those who inherit wealth will often contribute to society as a matter of principle.What About You?How can you create enough money to have a pleasurable life and still contribute to society at a significant level? Many believe that if you don't have wealth, you were not meant to have wealth. As a result these people do not pursue activities that produce weal
INTRODUCTION
When we introduced the original version of the "PRIDE" methodology in 1971 (which is now referred to as "PRIDE"-ISEM), we were primarily concerned with developing enterprise-wide systems. Over time, it became clear to us that we needed to enhance our approach for developing the corporate data base, hence "PRIDE"-DBEM (Data Base Engineering Methodology) was born. Shortly thereafter, we introduced "PRIDE"-EEM (Enterprise Engineering Methodology) as a means to model the business and formulate an enterprise information strategy. When this was done, the last piece of the puzzle of our philosophy for Information Resource Management (IRM) fell into place. This was completed by the early 1980's.
At the time, most companies were concerned with only controlling the data resources pertaining to their Data Base Management Systems. This was a nice first step, but as it became necessary to share and re-use other resources such as software, it started to become obvious a more global perspective on managing information resources was needed, which is where IRM comes in.
DEFINITION
Information Resource Management is the design, development, implementation, and control over all of the resources needed to produce information. Its intent is to share and re-use resources where appropriate. Sharing represents the interchangeability of resources, thereby promoting the standardization and integration of parts in products. By doing so, development time and costs are reduced by simply re-using parts.
To those of you in manufacturing, this will all sound very familiar as this is the same objective of Materials Resource Planning (MRP) and, as such, IRM can trace its roots to MRP. The intent of both IRM and MRP are the same, the only difference is the types of resources being managed. Whereas MRP is concerned with tangible parts and products, IRM is concerned with resources that are more intangible. Nonetheless, both IRM and MRP are concerned with the collection, storage, and delivery of resources in the most cost effective means possible.
TYPES OF INFORMATION RESOURCES
To understand the resources needed to produce information, we must first understand the fundamental nature of information itself. We define it as "the intelligence or insight required to support the actions and decisions of the business." Further, we provide a simple formula for it:
Information = Data + Processing
This means there are two equal variables for producing information: data (representing the facts and events of the business) and, processing (representing how and when data is to be collected, stored, and retrieved). If the data is correct, but the processing is wrong, the information will be wrong. Conversely, if the data is wrong, but the processing is correct, the information will also be wrong. From this, we can deduce three classes of information resources:
DATA RESOURCES - representing the facts and events of the business, along with how they are stored.
SYSTEM RESOURCES - representing how data is to be processed.
BUSINESS RESOURCES - representing both the consumer of the information as well as the human and machine resources participating in the production of information.
DATA RESOURCES
Data Elements - individual facts and events regarding an enterprise (the basic building block of all data resources). Used to identify, describe and quantify the objects of the business; includes both primary and generated values (e.g., Net-Pay, Percent Completed, etc.).
Records - a collection of one or more data elements. Represents logical and physical storage areas within a file, input transactions, print maps and screen panels (incl. messages), and call arguments between programming modules.
Files - a collection of one or more records. Represents logical and physical storage, both computer and manual.
Data Base - all of the files either within a single application or a given enterprise, both logically and physically.
Inputs - a collection of one of more records used to collect data. Can be implemented by screens, paper, verbal, optical, etc.
Outputs - a collection of one or more records to transmit information
SYSTEM RESOURCES
Systems - a collection of one or more sub-systems. Systems can be implemented manually, in part or in full, or with mechanical support (computers).
Sub-Systems - a collection of one or more procedures within a system. A sub-system is a business process representing a flow of work within a specific time-frame.
Procedures - a collection of one or more operational steps (Administrative) or one or more programs (Computer).
Operational Step - an individual task.
Programs - a set of computer-executable instructions performing a step within a computer procedure. A program may be subdivided into modules if so desired.
Modules - compilable program source code consisting of one or more subroutines written in the same programming language. It is not executable by itself. Modules can call other modules.
BUSINESS RESOURCES
Enterprises - a defined business entity with a specific mission, whether profitable or non-profitable in intent. Enterprises take many forms, such as the conventional commercial venture, whether private or public, a government agency, etc. Enterprises consist of business functions and are implemented by Positions.
Functions - a scope of responsibilities for carrying out a specific portion of the mission of the enterprise, e.g., Marketing, Sales, Manufacturing, etc. Functions are implemented by Positions.
Positions - a prescribed set of duties and responsibilities; another name is "job." Positions implement business functions either in part or in full. Positions are implemented by Human/Machine Resources.
Human/Machine Resources - employees, part-time workers, consultants, computers, equipment, etc. Such resources possess...
Skills - specific knowledge or talent as developed by education and/or experience. Proficiency denotes level of skill.
Information Requirements - specific needs for information in order to perform actions and decisions related to the business of the enterprise
Objectives - a goal for the enterprise to achieve whether strategic, tactical, or mandatory in nature. An objective can be used to call for new development, modify or improve an existing condition (mod/imp), or to maintain or correct something. One or more objectives can be grouped into a project. An objective may relate to one or more information requirements.
Projects - a scope of work consisting of one or more phases. A project is an application of the material and human resources to a specific objective through the execution of a prescribed sequence of events. A project implements one or more objectives.
Many of the relationships between the resources are hierarchical in nature, such as Systems Resources that subscribe to a "Standard System Structure" as specified by "PRIDE." Some also have recursive relationships, such as files-within-files or modules-calling-modules. Yet, others are represented by a network of relationships (too extensive to go into here). All of these relationships ultimately represents a model of the business and provides the ability to perform an "Impact Analysis" whereby we can study the effect the change of one resource may have on another. For example, should we decide to change the length of a data element, we should be able to determine, with great accuracy, all of the other resources affected by the change, thereby providing a "roadmap" for a maintenance project.
The mapping and maintenance of these extensive relationships between information resources is the forte of an "IRM Repository" which acts as a "Bill of Materials" processor (see "Managing Design Complexity" - "PRIDE" Special Subject Bulletin #10) at: http://www.phmainstreet.com/mba/ss050207.pdf
In order to promote sharing and re-usability, resources should be uniquely identified by number and name, along with its prescribed characteristics. Such resource definition ultimately represents the rules of the business and allows us to differentiate resources. Using an automated IRM Repository, tests can be performed to check for redundancy in characteristics and, as such, the use of redundant resources can be avoided.
Also see "Establishing an IRM Repository" at: http://www.phmainstreet.com/mba/pride/spir.htm
DIFFERENT METHODOLOGIES
The three classes of resources also hints at three different methodologies for developing them:
Enterprise Engineering Methodology (EEM) - primarily concerned with developing business resources and is performed by Enterprise Engineers (Business Analysts)
Information Systems Engineering Methodology (ISEM) - primarily concerned with system resources (Software Engineering is considered a subset of ISEM), Such resources are developed by Systems Engineers and Software Engineers (analysts and programmers).
Data Base Engineering Methodology (DBEM) - primarily concerned with data resources and is performed by Data Engineers and Data Base Administrators.
Although the methodologies will define "who" is primarily responsible for their development, it is quite common for information resources to cross methodology boundaries. For example, during EEM systems and "objects" (logical files) are identified which are later implemented by ISEM and DBEM respectively. During ISEM, application logical files are identified and detailed later in DBEM. In DBEM, physical files for a specific application are designed and delivered to ISEM in Software Engineering. This means resources are initially identified and then refined in ensuing phases of the various methodologies. In this regards, an IRM Repository is used as a "scratchpad" by developers to record the specifications of information resources.
Project Management and Quality Assurance will also find information resource definition helpful in their assignments. The phases of the methodologies dictate which resources must be used and their degree of definition. For example, in ISEM, the need for specific data elements must be identified in Phase 1 (to support an information requirement), either new or established data elements to be re-used. At this time, for new data elements, only its logical definition must be supplied. The physical attributes of the data elements (e.g., length, picture,
It’s the law: if you drive a motor vehicle on any public road in the state of Missouri you must have automobile insurance and you must carry proof of that insurance with you each time you drive your vehicle. Failure to do so could result in a serious fine, impounding of your vehicle or even jail time.Driving without insurance simply is not worth the risk. And there’s no need to if you take the time to reduce the cost of your automobile insurance premiums.Start by driving sensibly and within the law. Speeding, reckless driving, drunk or impaired driving all carry severe legal penalties and, just as bad, each of them will cause your automobile insurance rates to go so high that they might very well be unaffordable.If you are in school stay in school and study hard. Getting a “B” average in school can reduce you automobile insurance rates significantly. If you’re 55 or older talk to your insurance agent about enrolling in an approved safe-driving course. Passing such a course can often save you as much as 10% on your automobile insurance premiums.Depending on the age of your automobile you may be able to save money by reducing certain coverage amounts, especially on comprehensive coverage, which pays to have your car repaired after a claim. If your automobile is so old that it has little or no Blue Book value then you may consider dropping comprehensive coverage altogether since your insurance may pay little or nothing in any event.Your deductible may be the biggest area in which you can have a significant impact on the cost of your automobile insurance. The more you are willing to pay for e
TYPES OF INFORMATION RESOURCES
To understand the resources needed to produce information, we must first understand the fundamental nature of information itself. We define it as "the intelligence or insight required to support the actions and decisions of the business." Further, we provide a simple formula for it:
Information = Data + Processing
This means there are two equal variables for producing information: data (representing the facts and events of the business) and, processing (representing how and when data is to be collected, stored, and retrieved). If the data is correct, but the processing is wrong, the information will be wrong. Conversely, if the data is wrong, but the processing is correct, the information will also be wrong. From this, we can deduce three classes of information resources:
DATA RESOURCES - representing the facts and events of the business, along with how they are stored.
SYSTEM RESOURCES - representing how data is to be processed.
BUSINESS RESOURCES - representing both the consumer of the information as well as the human and machine resources participating in the production of information.
DATA RESOURCES
Data Elements - individual facts and events regarding an enterprise (the basic building block of all data resources). Used to identify, describe and quantify the objects of the business; includes both primary and generated values (e.g., Net-Pay, Percent Completed, etc.).
Records - a collection of one or more data elements. Represents logical and physical storage areas within a file, input transactions, print maps and screen panels (incl. messages), and call arguments between programming modules.
Files - a collection of one or more records. Represents logical and physical storage, both computer and manual.
Data Base - all of the files either within a single application or a given enterprise, both logically and physically.
Inputs - a collection of one of more records used to collect data. Can be implemented by screens, paper, verbal, optical, etc.
Outputs - a collection of one or more records to transmit information
SYSTEM RESOURCES
Systems - a collection of one or more sub-systems. Systems can be implemented manually, in part or in full, or with mechanical support (computers).
Sub-Systems - a collection of one or more procedures within a system. A sub-system is a business process representing a flow of work within a specific time-frame.
Procedures - a collection of one or more operational steps (Administrative) or one or more programs (Computer).
Operational Step - an individual task.
Programs - a set of computer-executable instructions performing a step within a computer procedure. A program may be subdivided into modules if so desired.
Modules - compilable program source code consisting of one or more subroutines written in the same programming language. It is not executable by itself. Modules can call other modules.
BUSINESS RESOURCES
Enterprises - a defined business entity with a specific mission, whether profitable or non-profitable in intent. Enterprises take many forms, such as the conventional commercial venture, whether private or public, a government agency, etc. Enterprises consist of business functions and are implemented by Positions.
Functions - a scope of responsibilities for carrying out a specific portion of the mission of the enterprise, e.g., Marketing, Sales, Manufacturing, etc. Functions are implemented by Positions.
Positions - a prescribed set of duties and responsibilities; another name is "job." Positions implement business functions either in part or in full. Positions are implemented by Human/Machine Resources.
Human/Machine Resources - employees, part-time workers, consultants, computers, equipment, etc. Such resources possess...
Skills - specific knowledge or talent as developed by education and/or experience. Proficiency denotes level of skill.
Information Requirements - specific needs for information in order to perform actions and decisions related to the business of the enterprise
Objectives - a goal for the enterprise to achieve whether strategic, tactical, or mandatory in nature. An objective can be used to call for new development, modify or improve an existing condition (mod/imp), or to maintain or correct something. One or more objectives can be grouped into a project. An objective may relate to one or more information requirements.
Projects - a scope of work consisting of one or more phases. A project is an application of the material and human resources to a specific objective through the execution of a prescribed sequence of events. A project implements one or more objectives.
Many of the relationships between the resources are hierarchical in nature, such as Systems Resources that subscribe to a "Standard System Structure" as specified by "PRIDE." Some also have recursive relationships, such as files-within-files or modules-calling-modules. Yet, others are represented by a network of relationships (too extensive to go into here). All of these relationships ultimately represents a model of the business and provides the ability to perform an "Impact Analysis" whereby we can study the effect the change of one resource may have on another. For example, should we decide to change the length of a data element, we should be able to determine, with great accuracy, all of the other resources affected by the change, thereby providing a "roadmap" for a maintenance project.
The mapping and maintenance of these extensive relationships between information resources is the forte of an "IRM Repository" which acts as a "Bill of Materials" processor (see "Managing Design Complexity" - "PRIDE" Special Subject Bulletin #10) at: http://www.phmainstreet.com/mba/ss050207.pdf
In order to promote sharing and re-usability, resources should be uniquely identified by number and name, along with its prescribed characteristics. Such resource definition ultimately represents the rules of the business and allows us to differentiate resources. Using an automated IRM Repository, tests can be performed to check for redundancy in characteristics and, as such, the use of redundant resources can be avoided.
Also see "Establishing an IRM Repository" at: http://www.phmainstreet.com/mba/pride/spir.htm
DIFFERENT METHODOLOGIES
The three classes of resources also hints at three different methodologies for developing them:
Enterprise Engineering Methodology (EEM) - primarily concerned with developing business resources and is performed by Enterprise Engineers (Business Analysts)
Information Systems Engineering Methodology (ISEM) - primarily concerned with system resources (Software Engineering is considered a subset of ISEM), Such resources are developed by Systems Engineers and Software Engineers (analysts and programmers).
Data Base Engineering Methodology (DBEM) - primarily concerned with data resources and is performed by Data Engineers and Data Base Administrators.
Although the methodologies will define "who" is primarily responsible for their development, it is quite common for information resources to cross methodology boundaries. For example, during EEM systems and "objects" (logical files) are identified which are later implemented by ISEM and DBEM respectively. During ISEM, application logical files are identified and detailed later in DBEM. In DBEM, physical files for a specific application are designed and delivered to ISEM in Software Engineering. This means resources are initially identified and then refined in ensuing phases of the various methodologies. In this regards, an IRM Repository is used as a "scratchpad" by developers to record the specifications of information resources.
Project Management and Quality Assurance will also find information resource definition helpful in their assignments. The phases of the methodologies dictate which resources must be used and their degree of definition. For example, in ISEM, the need for specific data elements must be identified in Phase 1 (to support an information requirement), either new or established data elements to be re-used. At this time, for new data elements, only its logical definition must be supplied. The physical attributes of the data elements (e.g., length, picture,
Few things are as devastating as losing your home. Sadly, it's not always inevitable. In many cases the foreclosure could have been avoided with some outside help.You are in a unique position to advise your clients in financial matters. If you know that a client is on the path toward foreclosure, take the time to show them how it can be avoided. First, remind them of some of the hidden difficulties that will arise if foreclosure occurs.1st, Finding a new home. Don't let your clients believe that it will be better to let the foreclosure happen, because after they lose their home, they will still need to find a new place to live. All too often, the price they will need to pay in rent will be almost as high if not higher than their current mortgage payment. Remember: The owner of the property needs to make his mortgage payment, too, so he's going to charge a rental payment that's higher than his mortgage costs.2nd, Deficiency judgment. It's not uncommon that the sale of the home is insufficient to cover the remainder of the mortgage. When the property has been damaged, or market values have dropped, the owner may end up with a bill in the tens of thousands for the difference.Despite what many people think, most lending institutions are not anxious to foreclose. It's a last-ditch effort to recover their money and minimize their losses, and it's an incredible hassle. Most lenders would rather avoid it, if possible. There are multiple sources for help that your client should be aware of, and most lenders will be happy to hear that their client
Outputs - a collection of one or more records to transmit information
SYSTEM RESOURCES
Systems - a collection of one or more sub-systems. Systems can be implemented manually, in part or in full, or with mechanical support (computers).
Sub-Systems - a collection of one or more procedures within a system. A sub-system is a business process representing a flow of work within a specific time-frame.
Procedures - a collection of one or more operational steps (Administrative) or one or more programs (Computer).
Operational Step - an individual task.
Programs - a set of computer-executable instructions performing a step within a computer procedure. A program may be subdivided into modules if so desired.
Modules - compilable program source code consisting of one or more subroutines written in the same programming language. It is not executable by itself. Modules can call other modules.
BUSINESS RESOURCES
Enterprises - a defined business entity with a specific mission, whether profitable or non-profitable in intent. Enterprises take many forms, such as the conventional commercial venture, whether private or public, a government agency, etc. Enterprises consist of business functions and are implemented by Positions.
Functions - a scope of responsibilities for carrying out a specific portion of the mission of the enterprise, e.g., Marketing, Sales, Manufacturing, etc. Functions are implemented by Positions.
Positions - a prescribed set of duties and responsibilities; another name is "job." Positions implement business functions either in part or in full. Positions are implemented by Human/Machine Resources.
Human/Machine Resources - employees, part-time workers, consultants, computers, equipment, etc. Such resources possess...
Skills - specific knowledge or talent as developed by education and/or experience. Proficiency denotes level of skill.
Information Requirements - specific needs for information in order to perform actions and decisions related to the business of the enterprise
Objectives - a goal for the enterprise to achieve whether strategic, tactical, or mandatory in nature. An objective can be used to call for new development, modify or improve an existing condition (mod/imp), or to maintain or correct something. One or more objectives can be grouped into a project. An objective may relate to one or more information requirements.
Projects - a scope of work consisting of one or more phases. A project is an application of the material and human resources to a specific objective through the execution of a prescribed sequence of events. A project implements one or more objectives.
Many of the relationships between the resources are hierarchical in nature, such as Systems Resources that subscribe to a "Standard System Structure" as specified by "PRIDE." Some also have recursive relationships, such as files-within-files or modules-calling-modules. Yet, others are represented by a network of relationships (too extensive to go into here). All of these relationships ultimately represents a model of the business and provides the ability to perform an "Impact Analysis" whereby we can study the effect the change of one resource may have on another. For example, should we decide to change the length of a data element, we should be able to determine, with great accuracy, all of the other resources affected by the change, thereby providing a "roadmap" for a maintenance project.
The mapping and maintenance of these extensive relationships between information resources is the forte of an "IRM Repository" which acts as a "Bill of Materials" processor (see "Managing Design Complexity" - "PRIDE" Special Subject Bulletin #10) at: http://www.phmainstreet.com/mba/ss050207.pdf
In order to promote sharing and re-usability, resources should be uniquely identified by number and name, along with its prescribed characteristics. Such resource definition ultimately represents the rules of the business and allows us to differentiate resources. Using an automated IRM Repository, tests can be performed to check for redundancy in characteristics and, as such, the use of redundant resources can be avoided.
Also see "Establishing an IRM Repository" at: http://www.phmainstreet.com/mba/pride/spir.htm
DIFFERENT METHODOLOGIES
The three classes of resources also hints at three different methodologies for developing them:
Enterprise Engineering Methodology (EEM) - primarily concerned with developing business resources and is performed by Enterprise Engineers (Business Analysts)
Information Systems Engineering Methodology (ISEM) - primarily concerned with system resources (Software Engineering is considered a subset of ISEM), Such resources are developed by Systems Engineers and Software Engineers (analysts and programmers).
Data Base Engineering Methodology (DBEM) - primarily concerned with data resources and is performed by Data Engineers and Data Base Administrators.
Although the methodologies will define "who" is primarily responsible for their development, it is quite common for information resources to cross methodology boundaries. For example, during EEM systems and "objects" (logical files) are identified which are later implemented by ISEM and DBEM respectively. During ISEM, application logical files are identified and detailed later in DBEM. In DBEM, physical files for a specific application are designed and delivered to ISEM in Software Engineering. This means resources are initially identified and then refined in ensuing phases of the various methodologies. In this regards, an IRM Repository is used as a "scratchpad" by developers to record the specifications of information resources.
Project Management and Quality Assurance will also find information resource definition helpful in their assignments. The phases of the methodologies dictate which resources must be used and their degree of definition. For example, in ISEM, the need for specific data elements must be identified in Phase 1 (to support an information requirement), either new or established data elements to be re-used. At this time, for new data elements, only its logical definition must be supplied. The physical attributes of the data elements (e.g., length, picture,
A friend of mine, a responsible sort who had always paid his bills on time, recently fell on hard times. The corporation that had benefited from the diligence and devotion with which he customarily performed his duties day in and day out for 10 years laid off hundreds of employees, and my friend – we’ll call him X – found himself downsized.X had a son and daughter attending UCLA, and the combined income of X and his wife was what had kept the family solvent. With only his wife’s income keeping the family afloat, they were forced to delve into their savings. X, a JPL physicist, had no idea that his shining credentials would actually work against him in the job market. Time and time again he was told that he was overqualified. Weeks stretched into months, and before he knew it, the savings and the nest egg were exhausted. He was still unemployed.Humiliated, X nevertheless called his creditors and explained his situation, expressing his desire to defer payments on his monthly bills until he was back on his feet. For a few creditors he was able to send a nominal monthly fee, but there were some bills he simply could not pay. Many of the creditors he contacted were not sympathetic to X’s plight. He began to receive calls from collection agencies.He received calls off and on throughout the day. He tried explaining his situation, but the collection agency representatives had a single item on their agenda: to get X to pay his bills. X told me that the attitude of his callers ran the gamut: cajoling, patronizing, harsh, mean-spirited. Some of the callers probably crossed the line into harassment. His stress level ros
Projects - a scope of work consisting of one or more phases. A project is an application of the material and human resources to a specific objective through the execution of a prescribed sequence of events. A project implements one or more objectives.
Many of the relationships between the resources are hierarchical in nature, such as Systems Resources that subscribe to a "Standard System Structure" as specified by "PRIDE." Some also have recursive relationships, such as files-within-files or modules-calling-modules. Yet, others are represented by a network of relationships (too extensive to go into here). All of these relationships ultimately represents a model of the business and provides the ability to perform an "Impact Analysis" whereby we can study the effect the change of one resource may have on another. For example, should we decide to change the length of a data element, we should be able to determine, with great accuracy, all of the other resources affected by the change, thereby providing a "roadmap" for a maintenance project.
The mapping and maintenance of these extensive relationships between information resources is the forte of an "IRM Repository" which acts as a "Bill of Materials" processor (see "Managing Design Complexity" - "PRIDE" Special Subject Bulletin #10) at: http://www.phmainstreet.com/mba/ss050207.pdf
In order to promote sharing and re-usability, resources should be uniquely identified by number and name, along with its prescribed characteristics. Such resource definition ultimately represents the rules of the business and allows us to differentiate resources. Using an automated IRM Repository, tests can be performed to check for redundancy in characteristics and, as such, the use of redundant resources can be avoided.
Also see "Establishing an IRM Repository" at: http://www.phmainstreet.com/mba/pride/spir.htm
DIFFERENT METHODOLOGIES
The three classes of resources also hints at three different methodologies for developing them:
Enterprise Engineering Methodology (EEM) - primarily concerned with developing business resources and is performed by Enterprise Engineers (Business Analysts)
Information Systems Engineering Methodology (ISEM) - primarily concerned with system resources (Software Engineering is considered a subset of ISEM), Such resources are developed by Systems Engineers and Software Engineers (analysts and programmers).
Data Base Engineering Methodology (DBEM) - primarily concerned with data resources and is performed by Data Engineers and Data Base Administrators.
Although the methodologies will define "who" is primarily responsible for their development, it is quite common for information resources to cross methodology boundaries. For example, during EEM systems and "objects" (logical files) are identified which are later implemented by ISEM and DBEM respectively. During ISEM, application logical files are identified and detailed later in DBEM. In DBEM, physical files for a specific application are designed and delivered to ISEM in Software Engineering. This means resources are initially identified and then refined in ensuing phases of the various methodologies. In this regards, an IRM Repository is used as a "scratchpad" by developers to record the specifications of information resources.
Project Management and Quality Assurance will also find information resource definition helpful in their assignments. The phases of the methodologies dictate which resources must be used and their degree of definition. For example, in ISEM, the need for specific data elements must be identified in Phase 1 (to support an information requirement), either new or established data elements to be re-used. At this time, for new data elements, only its logical definition must be supplied. The physical attributes of the data elements (e.g., length, picture,
In the highly competitive world of internet marketing it is important to attract highly targeted traffic to your website. This is something that certainly cannot be overemphasized. Sending targeted traffic to your website is the only means of survival in the world of internet marketing. Getting and retaining high search engine ranking can be a very difficult task. Fortunately, there are a host of promotion techniques you can use to drive targeted traffic to your website. One of the best techniques available is article writing.Here is how can article writing can help improve your web traffic. This strategy can help explode your internet marketing business.1. Increases Your Website Link PopularityInstead of trying to establish reciprocal links with other websites, you can by simply submitting an article get hundreds of one way links to your own website. Just do not forget to include one or two links to your site in your resource box. When various other websites pickup and publish your article, you automatically get a link partner. You should try to get as many link partners as possible. Link popularity is one of the factors used by search engines in determining search engine rankings. Make your article especially useful and appealing, so that more websites will be encouraged to publish it.2. Increase Your Exposure By Reaching More PeopleWell written articles should be shared with other people. This can be done by posting your articles on your own website or by you submitting them to article directories, e-zines and other online publishers. Submitting your articles to these sites will give expos
DIFFERENT METHODOLOGIES
The three classes of resources also hints at three different methodologies for developing them:
Enterprise Engineering Methodology (EEM) - primarily concerned with developing business resources and is performed by Enterprise Engineers (Business Analysts)
Information Systems Engineering Methodology (ISEM) - primarily concerned with system resources (Software Engineering is considered a subset of ISEM), Such resources are developed by Systems Engineers and Software Engineers (analysts and programmers).
Data Base Engineering Methodology (DBEM) - primarily concerned with data resources and is performed by Data Engineers and Data Base Administrators.
Although the methodologies will define "who" is primarily responsible for their development, it is quite common for information resources to cross methodology boundaries. For example, during EEM systems and "objects" (logical files) are identified which are later implemented by ISEM and DBEM respectively. During ISEM, application logical files are identified and detailed later in DBEM. In DBEM, physical files for a specific application are designed and delivered to ISEM in Software Engineering. This means resources are initially identified and then refined in ensuing phases of the various methodologies. In this regards, an IRM Repository is used as a "scratchpad" by developers to record the specifications of information resources.
Project Management and Quality Assurance will also find information resource definition helpful in their assignments. The phases of the methodologies dictate which resources must be used and their degree of definition. For example, in ISEM, the need for specific data elements must be identified in Phase 1 (to support an information requirement), either new or established data elements to be re-used. At this time, for new data elements, only its logical definition must be supplied. The physical attributes of the data elements (e.g., length, picture, precision, scale, etc.) do not have to be defined until Phase 3 (prior to Software Engineering). By taking this approach to development, Project Management and Quality Assurance can substantiate completion of the resource definition and the phase of work (it either has been done or it has not). Such analysis of the completion of work is commonly referred to as performing a "status check."
IMPLEMENTATION
As we mentioned in our earlier article, "Managing Design Complexity," sharing and re-using resources doesn't happen by accident. It takes a premeditated effort to do so. This means we have to uniquely identify, describe, and cross-reference each resource.
Is such definition work endless? Hardly. There is a finite number of information resources in an organization. For example, there is probably no more than 500 - 1,000 unique data elements in an enterprise. Once they are documented, they can be shared and re-used over and over again. This is the real payoff of IRM, thus expediting development and simplifying change control.
Year ago there was a problem in India where people were starving to death. To help out, the United States sent seed grain to India for the local populace to plant and harvest. This was a viable long-term strategy to take. Unfortunately, when the sacks of seed were delivered to the docks, the people opened them and ate the seed as opposed to planting it. This remedied their immediate hunger problem, but ruined their long term needs. You cannot harvest a crop if you do not sew the seeds. The same is true in IRM and MRP. To harvest the crop, we must first document our resources. Only then can we realize the benefits of sharing and re-using them.
For more information on our philosophies of Information Resource Management (IRM), please see the "Introduction" section of "PRIDE" at:
HTTP = HTML link (for blogs, profiles,phorums):
<a href="http://www.iadvice.info/article/170081/iadvice-Understanding-the-IRMMRP-Analogy.html">Understanding the IRM/MRP Analogy</a>
BB link (for phorums):
[url=http://www.iadvice.info/article/170081/iadvice-Understanding-the-IRMMRP-Analogy.html]Understanding the IRM/MRP Analogy[/url]
Related Articles:
Training Sales People at a Tire Shop
A Free Corporate Values Assessment
Bookmark it:
|