 send to a friend
GEMI Contact Info:
1155 15th Street, NW
Suite 500
Washington, DC 20005
Phone: 202-296-7449
Fax: 202-296-7442
e-mail: info@gemi.org
http://www.gemi.org
About GEMI
|
|
Cross-functional team
|
Consists of representatives from business functions and system end-users. These functions may include: information systems, manufacturing, operations, marketing, research and development, finance, purchasing, public affairs, investor relations, legal and, of course, health, safety and environmental.
|
|
Current State
|
A description of the current situation in terms of the work processes, HSE-information and MIS performance.
|
|
Data Architecture
|
The overall software configuration and data linkage supporting a particular HSE-MIS application.
|
|
Enterprise Resource Planning
|
or ERP, an industry term for the broad set of activities supported by application software that helps a manufacturer or other business manage the important parts of its business, including product planning, parts purchasing, maintaining inventories, interacting with suppliers, providing customer service, and tracking orders. ERP systems provide an opportunity to support the integration of HSE activities into the business.
|
|
ERP
|
see Enterprise Resource Planning
|
|
Functional Requirements
|
A detailed list of business and user needs that the HSE-MIS should support.
|
|
Future State
|
A description of the desired future state of the redesigned or newly design HSE-MIS requirements for the reengineered work processes.
|
|
Globalization
|
A set of processes leading to the integration of economic, cultural, political, and social systems across geographical boundaries.
|
|
HSE
|
Refers to health, safety and environmental functions and processes.
|
|
HSE Business Plan
|
The HSE plan that identifies the goals, objectives and targets to achieve the HSE vision, mission, policy and business requirements.
|
|
HSE Software Product
|
A commercially developed software product designed to support a specific HSE application or group of HSE applications.
|
|
HSE-MIS
|
Health, Safety and Environment -Management Information Systems. Refers to a set of processes and systems supporting health, safety and environmental (HSE) functions. May be a comprehensive system which encompasses all relevant HSE functions, or a focused system which supports a smaller set of HSE functions.
|
|
HSE-MIS Development Initiative
|
Description of a need identified by the gap analysis.
|
|
Implementation Plan
|
Comprehensive outline of the most appropriate options for implementing initiatives identified and ranked during the Gap Analysis and Prioritization steps.
|
|
Implementation Scenario
|
A detailed view of what is required to implement a specific initiative.
|
|
Information Model
|
A high-level roadmap containing software, hardware, and other information technology requirements for HSE-MIS.
|
|
Integrator
|
Individual or group that ensures that the HSE systems and processes that are developed and implemented fit into overall business functions.
|
|
Internal Rate of Return
|
The rate of discount that makes the net present value (NPV) equal to zero.
|
|
Net Present Value
|
The present value of future cash returns of a project.
|
|
Owner
|
Business unit or function responsible for collecting, using, reporting and maintaining the HSE-MIS information.
|
|
Prototype
|
Smaller version of a system or application that can be validated quickly by the user without construction of an entire system.
|
|
Return on Investment
|
Benefits of a project over a set time period divided by the amount invested in the project.
|
|
Scope Creep
|
A situation where the project requirements are allowed to expand or change once they have been agreed upon and this change affects the project negatively, such as requiring additional unplanned budget or resources.
|
|
Screen Shots
|
Graphic representations of screens the user would see on the finished system. They are built with limited functionality behind the screens and are intended to show high-level functionality with a detailed user interface.
|
|
Source Code
|
Commercially or in-house developed proprietary algorithms, such as macros, that specifically determine how a software program works.
|
|
Sponsorship
|
Business unit or function providing the business resources to support the HSE-MIS solution.
|
|
Stakeholder
|
In this context, stakeholders are involved with or somehow touch HSE processes, either through execution or support.
|
|
Strategic Business Plan
|
A roadmap that competitively differentiates a company's products and services, target markets, customers, competition and resources needed to deliver products successfully to customers.
|
|
Sustainability
|
There are many definitions of sustainability, but a good one for the HSE-MIS context is:
"Sustainable means using methods, systems and materials that won't deplete resources or harm natural cycles" (Rosenbaum, 1993).
|
|
System Architecture
|
The overall hardware/software configuration and database design supporting a particular HSE-MIS application, including internet, intranet and extranet network linkages.
|
|
System Development Life Cycle
|
Series of steps required to conceptualize, design and implement an information management systems project. Steps may include: Analysis, design, build, implementation, operation and maintenance.
|
|
System owner
|
Refers to the functional owner of a computer-based application. The function responsible for granting access, defining requirements and maintaining an application.
|
|
Test Scripts
|
Specific application simulations to beta test a new or modified software application.
|
|
Testing Scenarios
|
Different application circumstances and conditions that validate the software's capabilities to meet the functional requirements.
|
|