EFILM implements DataFrameworks software to manage data pipeline.
How to quantify my environment Obviously, to quantify any one problem it is necessary to first assess the current environment to identify inefficiencies and then evaluate all the relevant data requirements. Current environment When assessing the current environment is often helpful to understand at what level of maturity the organization is at in their approach to data management. An assessment spectrum typically runs from early stages where companies are likely to not be doing a great deal to actually manage data but just keep ‘buying more storage,’ through to very advanced stages which incorporate up to date business schedules and objectives, almost in real time, to make their data decisions. Inefficiencies Inefficiencies show up in a variety of different ways. These usually range from unnecessary operating and capital expenditures through to major impacts on workflow due to data related issues. Quantifying the cost and workflow impact of poor data management will be different for every organization. In many cases organizations just get caught in the vicious cycle of running to fight data related fires and never seem to have time to stop the chaos to actually help themselves improve the situation. Within DataFrameworks is the ability to help quantify and rectify these inefficiencies. Data requirements It is important to have a detailed understanding of the data to effectively quantify its value to the business. One method is to use a simple rule of thumb; the older the data gets the less valuable it is. Alternatively, it is possible to calculate the cost to achieve the resulting data for a particular task or project. Often the most valuable data contains a human “value add” element combined with the source component. Typically these would include interpretations, analysis, seismic surveys etc. Click here for more information.
Quantify Environment - how do I do that ?
Customer inefficiency comments... "Adding more storage capacity is easy; what I need are tools that make this storage and data useful to the business" "Every user has their own idea of what a good directory structure should be. If a user changes from one project to the next, they either take their convoluted structure with them, or have to learn someone else's convoluted structure. Summary: There is no structure to our data !" "How do I find the data I need? searching through unorganized data can be very time consuming and inefficient" Notification that /volume7 is filling up is of little value, I can easily be inundated with notifications which then require further human investigation with complicated file system commands. These notifications often lack the business perspective required to quickly identify the area of concern, for example: Project X, Dept Y is increasing at an abnormal rate, perhaps we should go identify why?" "Users had to know the location of their data. With multiple file systems to choose from, remembering the location of all your different tasks, became very time consuming, and at times impossible. There was an entire team of people hired to help Band-Aid up this issue." "When dealing with backups, I quickly learned that a tape was only as good or useful as the label on it. If the tape had no label or an inaccurate label, I might as well throw it away as it was extremely difficult to determine what was on it, or why it might be important. The same lesson often applies to data files on a file system."