IT Baseline Protection Manual - The Information Warfare Site

Safeguard Catalogue - Organisation Remarks
____________________________________________________________________ .........................................
S 2.90 Checking delivery
Initiation responsibility: Head of IT Section, Head of organisation
Implementation responsibility: Procurer
Following receipt of a delivery, the following must be checked using the
documents available,
- Whether the delivery was ordered,
- For whom it is intended,
- Whether there are any signs of damage in transit,
- Whether it is complete, i.e. whether all the components ordered are there
and/or whether all the components included within the scope of supply of
the product in accordance with the product specification are there.
The results of these checks must be documented in a goods inwards register,
together with:
- Product name and version,
- Type of product, e.g. word processing,
- Scope of supply, i.e. description of the individual components including
number and form of delivery (book, diskette, CD-ROM, ...),
- Date of delivery,
- Type of delivery,
- Who took delivery of it,
- Place where it is kept and
- Person to whom it was passed on.
The delivered products must be passed on to the IT Department to enable
functional tests and subsequent formal approval, installation and configuration
to be carried out.
If the products are only being used or made available temporarily, e.g. for test
purposes, as a minimum requirement the serial numbers and other productspecific
identifying characteristics must be noted down in appropriate
inventory lists. If the delivered products are scheduled to remain permanently,
they must be marked with clear identifying characteristics (e.g. grouped
consecutive inventory numbers). Following this, they must be included in an
inventory list. This must give information on:
- Identifying characteristics,
- Procurement sources, delivery times,
- Whereabouts,
- Approval date,
- Installation date and peculiar configuration features and
- maintenance contracts, maintenance intervals.
____________________________________________________________________ .........................................
IT-Baseline Protection Manual: Oktober 2000