Home / SLFD / Principals of operation / DEFENITIONS:

DEFENITIONS:

Defenition EXAMPLES
Event: An action to occur 001 054 001
for example a kiosk being used on site, or cholesterol testing.  A kiosk must be linked to an event when on site.

 

With an event title of:

    1. Solihul
    2. Leicester
With an event title of:

54 (John Ellis House, Derby)

 

With an event title of:

1 (Head Office)

 

Project:

SO / Sales order / Programme

A group of events, joined to a single SO number.

 

SOA00654 SOA00465 SOA00486
The project may be a cluster of events over a couple of weeks, a calendar/financial year, or a 3 year contract. These can be started or finished to suit the business needs.    With a program Title of

Kier Interiors – White van days

**

With a program title of:

Network Rail 2015-2016

Business Unit: The projects are joined to a business unit of the company Options may include:

 

Options may include:

 

Options may include, but may be left blank:
The business unit can be a division, a department, or a separate part of the same company. For some companies this will be left blank.  These will be selected from a predefined group for a company, ensuring consistency, ie a drop down menu, populated from another area of SLFD Kier Construction Ltd

Kier Interiors

Kier Scotland

Infrastructure Projects

Safety Directorate

Digital Railway

Communications

Network operations

Central
Company:

 

A customers company name which links the business units together. KIER Network Rail Advent Underwriting

 

NOTES

  • We have changed to the word Project from Programme, as it seems a better word, and does not get confused with the SLFD program
  • **It may appear unnecessary to use the name of the company or building sector in the titles, but these are also used in the titling of reports.
  • You will be able to search and view at all levels of the above.
  • We will need to adjust the way reports are requested, as we need ‘ad-hoc’ reports as well as project/event ones.  The Ad-hoc may span multiple business units, or just about anything else.  But, they will have to be assigned to a business unit for billing purposes later
  • The company name and business units will be set up in a different part of SLFD, so those entering the SO later on, can only select the options available.
    • This set up will eventually include:
      • Company:  Name /Address1/Address2/Address3/Town/Post Code- (Entered from Admin level)
      • Business Centres:  each one will have: Name /Address1/Address2/Address3/Town/Post Code  (Entered from Admin level)
      • Event:   each event will have:  Name /Address1/Address2/Address3/Town/Post Code  (Entered from User level, and adds to the available lists of venues for this company.)
      • Company contacts:  Sla/Name/Surname/ Job title / Tel / mobile / email – (Entered from User level, and visible at any part of program

 Examples, with explanation:

Kier

There is one company here, Kier.  But, there are many business units below that, such as “Construction” or “Group”.  At the moment, there are also people’s names too (Mark Starling, Ellen Bird etc.).  All of the business units have different SO project numbers.  Some contacts (Tracey Fellows) have multiple SO project numbers.

Under the new system there will be one company, Kier.  There will also be as many business units as required, they should never be named as people, always their department or role.  A business units sits under a company.

As a new job or set of jobs come in from one of your contacts, either a new SO is produced for that business unit, or the events are tacked on to the end of an existing programme as appropriate.

Example:

Company:            Kier

Business Unit:    Kier Construction

Project:       SOA00654

Event:                   1 (Sollihul)

CS Healthcare

There is one company.

There are one or more Business Units (contacts) you arrange events for, each one of those business units has one or more programmes.

Example:

Company:            CS Healthcare

Business Unit:    HMRC

Project:       SOA00548

Event:                   24 (Leicester), 28 (Norwich)

Advent Underwriting

I would ignore Buck Consultants here, it is irrelevant to the delivery of the programme.  The company is ‘Advent’, the business unit is probably ‘Central’, from there I can see at least 2 programmes.  The ‘2015’, and the ‘2016’ programme.

Example:

Company:            Advent Underwriting

Business Unit:    Central

Project:       SOA00486

Event:                   1 (Head Office)

Network Rail

All of the events sit under Network Rail, but there are a lot of business units here.  Some of the business units are regions, but most are departments.  For example, “IP” or “Wales” or “Digital Railway”.

Example:

Company:            Network Rail

Business Unit:    Infrastructure Projects

Project:       SOA00465

Event:                   54 (John Ellis House, Derby)

There is one programme (SOA) here, as it is a finite project.  But, all of the events can be associated with a business unit.  This allows us to separate them in a much clearer way, and makes requesting reports for a subset of events much easier.

Medigold

What is your relationship with Arla?  Do you organise events through Medigold or Arla?  If you deal directly with Arla, I’m not sure Medigold should be mentioned – in the same way Buck Consultants is ignored.

Example:

Company:            Arla

Business Unit:    Central

Project:       SOA00602

Event:                   1 (Leeds)

Sent to Phil, Siobhan,Guy,Verity  1.6.2016  14.47, as discussion, feedback awaited.

Leave a Reply

Your email address will not be published. Required fields are marked *