Importing and Exporting Incidents
HOPEX LDCUse Excel data exchange wizards to import and export incidents.
For more details, see chapter "Excel Import/Export Wizards" in the HOPEX Common Features guide.The list of information exported in the standard model delivered with HOPEX LDC is as follows:
• Incident Name
• Description is a comment describing the incident
• Declarant: name of the incident creator
• Declarant entity:
• Declaration date
• Detection date
• Occurrence date
• Near-miss:
A near-miss is an incident that could have caused important financial losses or harm to persons, property or the environment.• Nature: you may enter the financial nature of the incident.
• Impact of the incident on environment elements
• Priority characterizing described incident relative importance
• Currency
• Gross loss is obtained by a macro
• Recoveries is obtained by a macro
• Provision: the amount is obtained by a macro.
• entity concerned by the incident
An entity can be internal or external to the enterprise: an entity represents an organizational element of enterprise structure such as a management, department, or job function. It is defined at a level depending on the degree of detail to be provided on the organization (see org-unit type). Example: financial management, sales management, marketing department, account manager. An external entity represents an organization that exchanges flows with the enterprise, Example: customer, supplier, government office.• business lines concerned by the incident
A business line is a high level classification of main enterprise activities. It corresponds for example to major product segments or to distribution channels. It enables classification of enterprise processes, organizational units or applications that serve a specific product and/or specific market. Regulation frameworks of certain industries impose their own business lines.• risk types to be associated with the incident
A risk type defines a risk typology standardized within the context of an organization.• business processes and organizational processes concerned by the incident
A business process represents a system that offers products or services to an internal or external client of the company or organization. At the higher levels, a business process represents a structure and a categorization of the business. It can be broken down into other processes. The link with organizational processes will describe the real implementation of the business process in the organization. A business process can also be detailed by a functional view.An organizational process describes how to implement all or part of the process required to make a product or handle a flow.• products impacted by the incident
A product represents commodities offered for sale, either goods or merchandise produced as the result of manufacturing, or a service, ie. work done by one person or group that benefits another.• applications impacted by the incident
An application is a set of software tools coherent from a software development viewpoint.• requirements expected related to incident management
A requirement is a need or expectation explicitly expressed, imposed as a constraint to be met within the context of a project. This project can be a certification project or an organizational project or an information system project.