<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="https://wiki.calax.com/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>Calax.com - Reference Data - nr</title>
        <description></description>
        <link>https://wiki.calax.com/</link>
        <lastBuildDate>Wed, 22 Jul 2026 21:14:55 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>https://wiki.calax.com/lib/exe/fetch.php?media=wiki:dokuwiki.svg</url>
            <title>Calax.com - Reference Data</title>
            <link>https://wiki.calax.com/</link>
        </image>
        <item>
            <title>access_points</title>
            <link>https://wiki.calax.com/doku.php?id=nr:access_points</link>
            <description>Access Points

Description

Access Points holds the information on the access points to any asset that Infrastructure Management control.
This includes characteristics of each access point such as:

	*  Times of access 
	*  Suitability of access for various weight limits</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>acronyms</title>
            <link>https://wiki.calax.com/doku.php?id=nr:acronyms</link>
            <description>Information Management (IM) Acronyms

This section holds any acronyms associated with the IM function.
AcronymFull TermUsageADD-LiteAsset Data Dictionary LiteTerminology used for Assets in the engineering side of the businessAKBS Asset Knowledge Business Support</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>comments</title>
            <link>https://wiki.calax.com/doku.php?id=nr:comments</link>
            <description>This page contains miscellaneous comments and thoughts that don&#039;t fit in any of the other pages.

Culture

	*  Currently heavily paper based for non-operatives
		*  Fax delivery to depots is common
		*  Often problems with document versioning and expiry</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>dw</title>
            <link>https://wiki.calax.com/doku.php?id=nr:dw</link>
            <description>Data Warehousing

	*   ETL thoughts 
	*   Data warehousing thoughts</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>etl</title>
            <link>https://wiki.calax.com/doku.php?id=nr:etl</link>
            <description></description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>im</title>
            <link>https://wiki.calax.com/doku.php?id=nr:im</link>
            <description>Image Management

Description

Image Management (IM) at NR is exactly as it sounds.  It is the storage and re-distribution of maintenance imagery. 

Current Situation

Image management is done very much on an ad-hoc basis, often with the images held in a substantial number of MS Access databases floating around the company.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>odm</title>
            <link>https://wiki.calax.com/doku.php?id=nr:odm</link>
            <description>ODM

Current Situation

ODM stands for Operational Data Management.  At NR this breaks down into a number of key areas for Infrastructure Maintenance:

	*  Data management for various safety and hazard registers (see specifics for more details.
	*  A level of image management (this is a future requirement)</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>organisation</title>
            <link>https://wiki.calax.com/doku.php?id=nr:organisation</link>
            <description>Overview

Key Stakeholders

The key stakeholders for network rail are:

	*  Department of Transport
		*  Determines the level of public expenditure for the railway in England and Wales
		*  Defines the strategy for the railway in England and Wales

	*</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>specifics</title>
            <link>https://wiki.calax.com/doku.php?id=nr:specifics</link>
            <description>Specific Systems Details

	*   Access Points 
	*   Hazard Directories</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>staff</title>
            <link>https://wiki.calax.com/doku.php?id=nr:staff</link>
            <description>Project / Programme Staff
NameRoleGraham MeePMO - also used as a PM where necessaryLee FellBA Lead - Runs the BA team which is likely to growKevin ConnollyHeads IS delivery Brian LeonardFinancial controller for the pipeline workMatthew Quazai-TigheLinks in to Strategy</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>start</title>
            <link>https://wiki.calax.com/doku.php?id=nr:start</link>
            <description>General Notes on Network Rail

	*  Stakeholders and Organisational Structure
	*  Direct Contact Staff
	*  Acronyms in Use
	*  Terms of Reference &amp; Work Pieces
	*  Strategies, Policies and Directions 
	*   General Thoughts
	*   Data Warehouse</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>strategies</title>
            <link>https://wiki.calax.com/doku.php?id=nr:strategies</link>
            <description>Strategies, Policies and Direction

Current

Architecture Vision

Presentation Principles

Application Principles

	*  J2EE for reasonable size applications
	*  Oracle Application Express for small applications

Middleware Principles

Data Principles</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
        <item>
            <title>tor</title>
            <link>https://wiki.calax.com/doku.php?id=nr:tor</link>
            <description>There are four pieces of work in the TOR. These are:

	*  Support for ongoing BAU
	*  Help recruit replacement
	*  Operational Data Management
	*  image Management</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Sun, 06 Jan 2013 20:54:14 +0000</pubDate>
        </item>
    </channel>
</rss>
