Short resume (in English/Dutch)
Chief Information Officer richt zich primair op de CIO, of de functionaris die
een vergelijkbare functie heeft bij
een onderneming,
de overheid
of een andere grote organisatie.
Hij is in de Raad van Bestuur of op het directieniveau direct daaronder
verantwoordelijk voor de ICT-strategie.
Secundair richt Chief Information Officer zich op andere functionarissen die
op hetzelfde niveau opereren en in hun werk ook op strategisch niveau met ICT
te maken hebben.
Andere lezers zijn ICT functionarissen die op de niveau's daaronder werkzaam
zijn, bijvoorbeeld directieleden en hoofden van ICT afdelingen.
Tenslotte is Chief Information Officer ook een bron van informatie en
inspiratie voor de "business owner".
juni 2006:
Kees Donker, CIO van IBM Nederland
Lars Gustavsson, CIO van ABN Amro
Bernard van Oranje, oprichter van levi9
Jan Piek, voormalig gevangenisdirecteur Lelystad
Roel Pieper en het CIO Platform Nederland
Ineke Molenaars, directeur ICT van de Universiteit Utrecht
april 2006:
Hans Wanders, CIO Randstad en directeur I-bridge
Chris Verhoef, IT-hoogleraar Vrije Universiteit Amsterdam
Okko Huising, CIO ROC Twente
Peter Mulder, directeur GBO, Ministerie van Justitie
februari 2006:
Jac Braat, voormalig CIO en Supply Chain Manager Philips Lighting
Mario der Weduwen, Manager ICT ANWB
Thor Tielemans, CIO DaimlerChrysler CAC
Math Muijres, voormalig directeur Concern ICT UWV
Martin Vonk, CIO en COO ING Direct
Tom Dijkstra, directeur Informatie Beleid en Projecten Kadaster
november 2005:
Gerard Spans, Vice President en CIO Sara Lee
Jeroen Kuijlen, CIO CZ
Jo van den Hanenburg, CIO DSM
Wim Bentvelzen, directeur ISC RIVIT
Paul Piebinga, directievoorzitter Achmea Active
oktober 2005:
Peter Hagedoorn, CIO Océ
Roel Bakker, CIO Nutreco
Peter Somers, Executive VP en CIO KLM
Daniel Hartert, CIO Philips
Gerard Helmink, CIO Akzo Nobel Chemicals
Petra van Spronsen, ICT-manager Wehkamp
Frank Krom, CIO ING Lease
Peter Hennephof, PSG Ministerie van Sociale Zaken en Werkgelegenheid
Hadi Jassim, CIO Versatel
juni 2005:
Kostas Gerogiannis, CIO NS
Dimitri van Zantvliet, CIO Athlon
Martijn van Dam, Tweede kamer-lid PvdA
Daan Rijsenbrij, hoogleraar Informatiekunde aan de Radboud Universiteit
Nijmegen
Brian Gray, topambtenaar EC
april 2005:
Boudewijn Gerner, CFO Imtech
Randy Mott, CIO Dell
Zsolt Szabo, Tweede Kamer-lid VVD
Jeroen Kuijlen, CIO CZ
Wim Rietveld, CIO Vopak
Peter Vermeij, CIO en PSG Ministerie van Economische Zaken
Ruud Staijen, Chef Dienst Bedrijfsinformatie Politie Amsterdam-Amstelland
Ron Voskuijl, CIO AFM
Achter de wolken...
Web Services: geen diensten maar technologie (november 2002)
De tijd (december 2002)
Het einde van een fallussymbool (januari 2003)
Legacy (februari 2003)
Web bijt TV (maart 2003)
De echte waarde van TCO en ROI (april 2003)
Liefdadigheid (mei 2003)
Meer Met Minder (3) (september 2003)
Customer Lifetime Value
Kwaliteit uit kwantiteit (oktober 2003)
This document describes the installation of the MMBase content management system on a Red Hat Linux distribution, using the Tomcat application server, and integrating it with MySQL and Apache.
The Chiplist; The Processor Portal
Looking for a new computer, and confused by all these different processor flavors? Looking at an old computer, and wondering what it is made off? Or simply being a geek, interested in processors and processor technology?
Whether you are buying a new PC or server, refurbishing an old system, or simply having this itch, The ChipList aims to fulfill your every processor-need.
The ChipList brings you detailed information on the various processors used in PC's and servers. It covers news, market analyses, specifications, overview tables, roadmaps, benchmarks, and system tests.
Matt's FormMail CGI script
is a generic HTML form to e-mail gateway that parses the results of any form
and sends them to the specified users.
Unfortunately, using this script your e-mail addresses will still be published
on your web site (now not in a mailto URI but as a form parameter), and can be
still be harvested by crawlers collecting e-mail addresses for spam.
I've implemented a hash table that converts aliases from the form to e-mail
adresses. In this way all e-mail addresses will be savely hidden in the script
configuration parameters.
Both the
new file (version 1.92)
and a
diff dump
are available.
Aad Offerman and Ad J. van de Goor: An Open Notation for Memory Tests (also available in PostScript format) (presented at the IEEE International Workshop on Memory Technology, Design and Testing, 1997)
Aad Offerman and Ad J. van de Goor: An Open Notation for Memory Tests (also available in PostScript format) (Technical Report No.1-68340-44(1997)07, Delft University of Technology)
This paper contains the description of a language that was intended to be open, and at the same time handle most of the tests used these days. The result might be a little overwhelming.
We have realized that building and building on top of this open notation is not the way to go in the long run, and are thinking about better solutions at the moment. The next step will probably be a language that looks more like a general programming language providing facilities commonly used in memory tests. Furthermore, it is tempting to try to design notations for the specification of faults and for memory architectures at the same time, and make good use of the fact that the three of them are so closely related. However, this only exists in our heads yet, so no paper on this can be provided at the moment.
Ad J. van de Goor, Aad Offerman, and Ivo Schanstra: Towards a Uniform Notation for Memory Tests (also available in PostScript format) (presented at the European Design & Test Conference and Exhibition 96)
In here you can find a predecessor to the language above that is much
more limited (more like an extension to the March test notation) and
thus much more cleaner.
For this language a lex & yacc front-end is
available.
Designing memory tests which are complete and irredundant is hard to do. It is difficult to verify whether a certain test indeed covers all faults it is designed for (verification for completeness), and if it contains elements that can be left out without affecting its completeness (verification for irredundancy).
Therefore, a method is presented to automatically verify the completeness and irredundancy of memory tests. This method includes the definition of a two-dimensional memory model that determines the abstraction level, and the specification of memory characteristics, memory faults, and memory tests.
In the fault specification, a great variety of memory cell array faults and port faults can be specified. There is a strict separation between the behaviour of the fault, and the layout in the memory. Furthermore, the use of natural defaults allows the user to work only at an abstraction level as deep as needed.
To specify memory tests, a new memory test language has been designed. The widely used standard march test language is a natural subset of this memory test language. Furthermore, the memory test language has a much wider applicability than only this specific application; it can be practized for others too.
The presented method has been implemented in the programming language C++ for the UNIX platform and the X Window System grafical user interface. Several interpreters for the memory test language were implemented using the standard UNIX tools lex and yacc.
The complete thesis report (237 pages, in PostScript format).
This package contains a complete PostScript language DSC (Document Structuring Conventions) Version 3.0 framework for black and white documents (.ps), as well as for black and white pictures (.eps). The files can be used to put your own raw PostScript code into, to make them fully PostScript DSC 3.0 conforming. Easier is to write them directly using the files framew.ps for multi page documents and framew.eps for pictures.