FUJ00086866 - Email chain between Mik Peach, Simon Ajina, David Johns and others RE: CS Requirements (SSC) Solution Compliance Review - Meeting 29/10/08 Action 36.

Evidence on official site

FUJ00086866
FUJ00086866

~ ; Cooke David}
Parker Steve (PostOfficeAccount){
=ADMINGROUP1/CN=RECIPIENTS)

Sent: Wed 1/14/2009 3:46:03 PM (UTC)

Subject: RE: CS Requirements (SSC) Solution Compliance Review - Meeting 29/10/08 Action 36 (CS-BR-825)
Simon,

No.

The agreed wording from the meeting - "A lightweight process to introduce new applications to the installed base on the SAS servers.
This should not require a CP and be achievable within a week."

Has been converted to "Installation of new SSC diagnostic applications requiring an install on the SAS server (e.g. .msi file or setup.exe) would
need to follow due process." leaving it open, at any time, for someone to claim that the CP process is the "due process" - this is precisely
what we are trying to avoid. We have argued the case, and have achieved agreement in meetings, why is it proving so difficult to word
the compliance statement to the equivalent of what has already been agreed ?

You can do one of two things .Either use the wording which has already been agreed in the meeting as above OR change the wording
of the second paragraph to the following "SSC scripts , bespoke diagnostic code and new SSC diagnostic applications requiring an install on

the SAS server can be uploaded to the SSC area on the SAS servers using FTP or SSH session, subject to CS operational procedures. Such
updates would be lost in the event of the SAS server being rebuilt. "

Regards
Mik
From: Ajina Simon
Sent: 14 January 2009 10:22
To: Peach Mik
Ce: Johns David DL; Cooke David; Welsh Graham; Parker Steve (PostOfficeAccount)
Subject: RE: CS Requirements (SSC) Solution Compliance Review - Meeting 29/10/08 Action 36 (CS-BR-825)
Mik

Thanks for your feedback. The compliance text has now been revised and is given below for your approval

Remote desktop server shall be provided on
SSC Servers.

Note: remote desktops on SSC Servers to be
provided to mitigate against data loss
through network malfunctions.

The SSC perform a lot of data processing
tasks on an ad hoc basis that is sensitive to
interruption. By providing the remote desktop
server on the SSC platform we can mitigate
against data loss by ensuring that tasks are
managed locally and not through another
client connection.

RDP, SSH & FTP access from the SSC Workstations HNG-X VM will be
permitted to the SSC servers directly. Further access is provided to the
SSC servers via RDP through the SAS Secure Access Servers (SSN
Platform) giving SQL Client, Perfmon, Events, JDBC & http(s) access as
well as the SSH & FTP access. The RDP route through the SAS also gives
access to other systems.

SSC scripts and bespoke diagnostic code can be uploaded to the SSC
area on the SAS servers using FTP or SSH session, subject to CS
operational procedures. Such updates would be lost in the event of the
SAS server being rebuilt. Installation of new SSC diagnostic applications
requiring an install on the SAS server (e.g. .msi file or setup.exe) would
need to follow due process.

Regards

Simon Ajina FIAP FBCS C.Eng CITP

Principal Consultant - Service Decomposition & Business Analysis

Application Solution Development - Business Requirements Practice, Application Services

FUJITSU

E-mail: simon.ajinal
http//uk.fujitsu.com

Web:

‘kshire, RG

FUJ00086866
FUJ00086866

wh Please consider the environment - do you really need to print this email?
Fujitsu Services Limited, Registered in England no 96056, Registered Office: 22 Baker Street, London, W1U 38W

This e-mail is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu Services does not
guarantee that this e-mail has not been intercepted and amended or that it is virus-free.

From: Peach Mik

Sent: 08 January 2009 12:22

To: Ajina Simon

Cc: Johns David DL; Cooke David; Welsh Graham; Parker Steve (PostOfficeAccount)

Subject: RE: CS Requirements (SSC) Solution Compliance Review - Meeting 29/10/08 Action 36 (CS-BR-825)

Simon,
OK as far as it goes, but is does not capture all that was agreed at the meeting attended by Steve Parker on this subject.

Following wording copied from original AGREED minutes of the meeting:

To archive this we need:

3) A lightweight process and systems to add scripts and other bespoke code to the SAS servers.
In order to be usable this needs to be a direct transfer mechanism so that scripts can be added

to the SAS server within a few minutes.

4) A lightweight process to introduce new applications to the installed base on the SAS servers.
This should not require a CP and be achievable within a week.

Without this, the new process whereby all tools are on the SAS WILL NOT WORK. Therefore this part is essential, has been
agreed, and must be included

Regards
Mik

From: — Ajina Simon
Sent: 08 January 2009 10:43

To: Peach Mik

Cc: Johns David DL; Cooke David; Welsh Graham; Parker Steve (PostOfficeAccount)

Subject: RE: CS Requirements (SSC) Solution Compliance Review - Meeting 29/10/08 Action 36 (CS-BR-825)

Mik
Further to the earlier email, I now have the information from Jim Sweeting on what has been agreed and the compliance

statement has been updated to reflect that. I have switched the SI RAG Status to Green from Amber. New compliance text in
red. Please confirm this is OK

access from the SSC Worl stations ING- x MM will be
SSC Servers. permitted to the SSC servers directly. Further access is provided to the
SSC servers via RDP through the SAS Secure Access Servers (SSN
Note: remote desktops on SSC Servers to be I Platform) giving SQL Client, Perfmon, Events, JDBC & http(s) access as

provided to mitigate against data loss well as the SSH & FTP access. The RDP route through the SAS also gives
through network malfunctions. access to other systems.

The SSC perform a lot of data processing R te ti C. ilbe-permitted -but t-be-via the SA
tasks on an ad hoc basis that is sensitive to Se A Ss ALE

interruption. By providing the remote desktop
server on the SSC platform we can mitigate
against data loss by ensuring that tasks are
managed locally and not through another
client connection

Regards

Simon Ajina FIAP FBCS C.Eng CITP
Principal Consultant - Service Decomposition & Business Analysis
Application Solution Development - Business Requirements Practice, Application Services
FUJ00086866

FUJ00086866
FUJITSU
Lovelace.Road..Rracknell. Berkshire, RG12 8SN
@ Tel! Internally
4 Mob: {_ /GR

aii
Web: _ httpy//uk.fujitsu.com

wh Please consider the environment - do you really need to print this email?

This e-mail is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu Services does not
guarantee that this e-mail has not been intercepted and amended or that it is virus-free.

From: Ajina Simon

Sent: 13 November 2008 19:07

To: Peach Mik; Parker Steve (PostOfficeAccount)

Cc: Efstathiou Mike; Philip Steven

Subject: FW: CS Requirements (SSC) Solution Compliance Review - Meeting Action 36 (CS-BR-825)

Mik / Steve

Following from the action from the compliance discussions on the 29" October, Shahid Latif is the technical lead person to
discuss the solution and the SI compliance position for CS-BR-825.

Regards

Simon Ajina FIAP FBCS C.Eng CITP
Principal Consultant - Service Decomposition & Business Analysis
Application Solution Development - Business Requirements Practice, Application Services

FUJITSU

Berkshire _RG12.8SN

Internally G RO {

ly,

E-mail: simon.aiing,

Web: _http/uk fujitsu.com

ws Please consider the environment - do you really need to print this email?

Fujitsu ored Office: 2:

ker Street, London, W1U 3BW

ervices Limited, Registered in England no 96056, Regis

This e-mail is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu Services does not
guarantee that this e-mail has not been intercepted and amended or that it is virus-free.

From: Bowen Ian

Sent: 13 November 2008 17:44

To: Ajina Simon

Cc: Efstathiou Mike; Latif Shahid

Subject: RE: CS Requirements (SSC) Solution Compliance Review - Meeting Action 36 (CS-BR-825)

I thought that the attached compliance was what was agreed with Jim Sweeting.

Steve Parker can discuss this with Shahid Latif, who still does the design for SSN.

I’m also happy to discuss.

Shahid - can you get to the bottom of what Steve wants and we'll go from there - thanks

lan

From: Ajina Simon

Sent: 10 November 2008 12:54

To: Bowen Ian

Cc: Efstathiou Mike

Subject: CS Requirements (SSC) Solution Compliance Review - Meeting Action 36 (CS-BR-825)
lan

An action from the recent review with the SSC.

FUJ00086866
FUJ00086866

825 who can lead discussion with Steve Parker on
requirement.

36 CS-BR- Green => Amber. Need to identify an architect owner

this

The compliance text we put together for CS-BR-825 was questioned by the SSC and the feedback in the meeting was that the

example I was giving related to the Out of Hour laptop connection rather than a

connection from an SSC office workstation.

The action we took was to identify someone within SAS/SSN Architecture & Design to discuss the compliance position with the

SSC (their contact being Steve Parker).

Could you let me know who that would be ? Would this be you? someone else?

SA 29/10/08 Full Reqs Remote desktop server shall be
Compliance Review with Mik provided on SSC Servers.

Peach. SSC do not understand
relevance of compliance text Note: remote desktops on SSC Servers
example. SSC believe that to be provided to mitigate against data
relates to out of hour support loss through network malfunctions.
from home. Discuss with SSN
design (through lan Bowen). The SSC perform a lot of data

Change to Amber. SSC processing tasks on an ad hoc basis
contact for this is Steve Parker I that is sensitive to interruption. By
providing the remote desktop server on
the SSC platform we can mitigate
against data loss by ensuring that
tasks are managed locally and not
through another client connection.

Remote access to SSC servers will be
permitted but must be via the SAS Secure
Access Server (SSN Platform),

e.g. On Corporate FJS LAN using Remote
Desktop Protocol (RDP) to SAS (SSN) over
Secure Socket Layer (SSL), and then on the
RMGA Campus using Remote Desktop
Protocol (RDP) from SAS (SSN to the SSC
server).

Regards

Simon Ajina FIAP FBCS C.Eng CITP
Principal Consultant - Service Decomposition & Business Analysis
Application Solution Development - Business Requirements Practice, Application Services

FUJITSU
Lovelace Road, Bracknell, Berkshire, RG12 8SN

or Internally! 1
internally); GRO

E-mi rz
Web: _http://uk fujitsu.c

ss Please consider the environment - do you really need to print this email?

Fujitsu Services Limited, Registered in England no 96056, Registered Office: 22 Baker Street, London, W1U 3BW

This e-mail is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu Services does not

guarantee that this e-mail has not been intercepted and amended or that it is virus-free.