Tags |
|
|
Links |
|
|
Member You - Understanding the IRM/MRP Analogy
Public speaking is among the five most feared activities human beings encounter.The majority of us fear it worse than anything else. Yet, the mastery of public speaking is an important tool in our business skill set.It’s never too early (or too late) to learn to speak in public. Every one needs to start somewhere. The best strategy is to look for non-threatening opportunities with familiar surroundings, friends and colleagues. Plan your speaking gigs in stages starting out with a small comfortable group then increasing the number of members in the audience and finally tackle the prominence of the engagement.Become a member of the leadership team where you need to give reports or host meetings. In these instances, you will have prepared material in front of you. Practice with the material as if you were giving the speech. Don't just read the material; live it and convey it with feeling. When you begin with an audience, remember to make eye contact. Watch how people are receiving your information. Do they look bored? Adjust your inflection accordingly.Do you participate in a professional association, social club or sport that hosts regular meetings? Ask to make a short presentation. If this is too daunting volunteer to introduce another speaker. This will get you in front of an audience but the spotlight won't be on you because you are not the primary focus. It will help you to feel comfortable with a stage, a mike, and an audience. If you are comfortable with jumping right in, ask to be the keynote. Plan for it to be informal so that you get the experience of speaking
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 th
Why Thermal Binders Instead of Comb Binders?Thermal Binders vs. Comb Binders– Integrity & StrengthLet’s start with the pages themselves. With comb binders, the page’s integrity is compromised by the holes you have to punch. Even if you order them pre-punched, that part of the paper has only half the strength of the rest of the page. If you expect your documents to last for any length of time, then thermal binders are the way to go. The pages are held with a simple strip of glue and nothing more.Unibind’s thermal binders are unique, in that they use a patented resign that doesn’t even require you to score the page ends. It’s truly the strongest thermal binding system today. And each of the spines has a strip of steel in them to strengthen the folder’s form.Thermal Binders vs. Comb Binders– TimeIt takes time to punch holes in your pages…the ones necessary for comb binders. If you have three or more documents to bind, this time can add up fast. Especially if you run a copy center and have to pay someone to do it. Thermal binders don't require holes, so you won't waste any time at all.On top of all that, you have to line the documents up twice…once to punch the holes and once to insert the combs. And that’s only if you have equipment that will punch a large stack at once. If you’re using the cheaper comb binders, you can only punch holes in a small stack…so binding one single document can take up to fifteen minutes.Thermal binders eliminate this step entirely. You just line the sheets up and put them in the folder. Once you lay the folder in the binder, it does the rest f
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 the
Mobil oil change businesses need to sign up fleet customers in order to make money. It is very hard to make high profits on service operations in a Mobile oil change business if you are constantly doing personal cars only.However, when doing fleet oil change services all the vehicles are lined up in a row and therefore you can make more money faster and most of the vehicles are the same type and therefore use the same oil filters. This cuts down on inventory and speeds up the service and therefore such efficiencies mean greater profits.The easiest way to sell fleet oil change services is by telephone and the best place to get lists of customers is to go to business directories to find them. It is also a good idea to co-brand with another local company that does other Fleet services such as tires, signage or mobile fleet watching to get phone lists and contact names to call.When calling fleet oil change customers on the telephone is important to have a prepared two sentence speech explaining what you do. For instance you might say; we do fleet oil changing services, while all your vehicles are parked in a row and they're not being used and then we conveniently bill you once a month, are you interested?Why is important to keep it so simple? Because when you are a cold calling customers of this type they are generally very busy and do not have time to talk. But because they are so busy this is one reason why they need your service so much. I hope you will consider this when doing telephone sales for fleet oil change services in the future. Please consider all this in 2006.
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 th
Do you have a home business success strategy in place to propel your business through each phase? Although there are more and more people that are striving for owning and running their own home based business, very few of them are finding the success that they need because they simply do not have the right strategies in place to help that to happen. Yet, if you are planning to start your own home business, there is no reason why you can’t have these exact things for your own success.What To Take Into ConsiderationWhen it comes to developing your own home business success strategies, it is important for you to determine what your specific target audience is. Who are you selling to? Then, you will be gearing your products, your websites, and your marketing to these individuals. You will spend countless days organizing and developing the best possible product for them as well with their needs in mind.To develop your strategy, take into consideration these aspects.Develop a website domain name that is catchy, unique and easy to remember so that customers can find you without having to write down your website address. Register it.Design an effective website that is geared towards your target audience. It should be a website that propels people into action, one that is not overwhelmingly full of ads and marketing gimmicks and it should be kept up to date. IN addition, you may want to feature a mailing list to send weekly or monthly newsletters to those that sign up.Make sure that ordering your product or service (or business) is easy for the client to do. You should have this automated
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 th
For most people the idea of asset vs. liability is a blur. It often becomes more confusing when you go to your banker. When you go to the bank to get a loan, your banker asks you to list your assets as collateral to insure you can pay back the money they are about to lend you. What is most commonly listed.... house, car, jewelry...This is the single most significant idea that keeps the middle class from becoming wealthy. They purchase long term debt items such as cars and jewelry as their earned income increases, by allowing you to list items that do not bring any kind of revenue into your cash flow your banker is contributing to the chance you are going to default. It is this idea that generates many other problems with a person’s cash flow.Those that are financially literate understand that an asset is something that puts money into your pocket each month, regardless if you work or not. Such as properly managed rental property or managed businesses.A liability is something that takes money out of your pocket every month, weather you work or not. This is anything with monthly payments but usually a house, car, or other luxury.If you get a raise and spend that extra money on something that locks you into an agreement to pay X amount of dollars for X amount of years, then you really have fallen into the middle class trap. By not investing your money into assets you have agreed to continue working for money.Now that you understand the differences between these two concepts you should re-evaluate your current financial status. Do you indeed have assets or do you have a long term debt obligation for
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 th
For anyone who has ever read articles I have written or asked me for helpful tips for getting their business up and going, you know that I truly believe that networking is one of the most important aspects to building a successful business. The spoken word has an awesome power for any entrepreneur.Networking, in relation to running your business, is not just attending events that allow you to meet new contacts and exchange business cards. Networking is any time you talk about your business. Whether you are at a social event and you get the chance to bring up the wonders of being a small business owner or you bump into an old college friend and you swap stories about what has happened in your lives since you last saw each other, anytime you get to tell someone about your business, that is networking and you should jump at the chance.Even when you chat on the email discussion lists that you belong to and use your signature line, that is networking. There are so many opportunities to network every day.But (and I am sure some of you can relate to this) the hardest part of networking can be “what do I say?” How do you let them know the great aspects of your business without over doing it or sounding full of yourself?Well, there are many contributing factors when it comes to saying just the right thing at just the right time, factors that will influence how well you impress others and whether you leave a positive lasting effect. First and foremost, what are the circumstances of your encounter? Are you at an organized networking event or are you chatting with a friend? More often than not, your attitude and p
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, 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.memberyou.net/article/170081/memberyou-Understanding-the-IRMMRP-Analogy.html">Understanding the IRM/MRP Analogy</a>
BB link (for phorums):
[url=http://www.memberyou.net/article/170081/memberyou-Understanding-the-IRMMRP-Analogy.html]Understanding the IRM/MRP Analogy[/url]
Related Articles:
Lists - Be More Organised to Help Your Career - It Helps you to Prioritize
Home Loans For First Time Buyers With Bad Credit
Why 95% of MLM or Network Marketing People Fail with Their Home Based Business
Bookmark it:
|