Junkshon FAQ's

Here you will find responses to some of the most frequently asked questions.  Should you have a question not covered below please contact our support team on support@junkshon.com or your assigned Junkshon contact 

What Security controls are implemented on Junkshon Platform?

All information is encrypted at REST and in transit, the application layer has Role Based Access Controls (RBAC) and the database layer is secured in a separate security domain with least privilege access controls. The database is also encrypted. We will also be using an instance of our platform that is based in the UK. So, no data is moving outside of the UK borders.

Junkshon's InfoSec documentation can be accessed here

 
Do I need to deploy an agent to get the data to upload?

NO, We do not request that you deploy an agent to capture the data as we understand there may be concern in deploying tools.  Junkshon Platform can work with the data extracted from any discovery tool you already have implemented if this is the case or from any other system extracts you may have running.

Some data sources can include:

Asset Management Systems

Configuration Management Systems

ITSM/Service Management Systems

System Extracts such as vSphere as an example

Other sources can include:

Daily check lists managed by engineering teams

Database extracts

 
What types of Data do I need to include in my file to upload?

The list of data types/categories that can be uploaded are as follows:

  • Server Name

  • Environment/Network Domain - e.g. Dev, Test, Prod

  • Operating System

  • Operating System Version

  • CPU

  • Memory (with the metric noted - e.g.GiB)

  • DataCentre Location

  • Utilisation - CPU

  • Utilisation - Memory

  • IP Address

  • Applications on the server

  • Databases on the server

  • Allocated Storage (with the metric noted - e.g.GiB)

  • Used Storage (with the metric noted - e.g.GiB)

  • Business Unit/Owner

  • Server Type - e.g. Virtual, Physical

When data is processed the Primary Key will be set by the server name on Junkshon Platform.

 
 
 
 
 
 
 
 
How much time do I (the customer) need to allocate from my teams during a Cloud Strategy Engagement?
Data Discovery and Upload:

 

The first 5-10 days of the assignment is allocated to collecting data.  Effort required should not exceed 2-3 hours of time from the technical team during this phase.  The team do not need to make any changes to the data in order to load the files, the mapping and cleaning (where needed) is all taken care of by Junkshon Platform.

 

Typical Customer Roles involved:

 

  • Service Management Manager

  • Asset Manager

  • System Admin e.g. vSphere or Cloud Admin

The Junkshon team are able to offer support and guidance on the types of data to collect and load if required.

 

Application Deep Dives:

 

45 min to 1hr session per service/application (4 applications targeted), typically a survey is sent to the application owners for them to complete on-line and then a short 45min to 1hr call for any clarifications.

 

Typical Customer Roles involved:

 

  • Application Architect, e.g. system architect or enterprise architect

  • Application SME, e.g. application operations engineer, application specialist, database admin

 

Migration Readiness Assessment (MRA):

 

Typical approach is for a half day workshop to work assess and score a different assessment domain covering:

 

  • Business Objectives

  • People & Organisation

  • Operating Model

  • Applications & Infrastructure

  • Security & Compliance

  • Operations

 

At the end of the assessment phase a maturity assessment report is produced along with action plan for improving scores.

 

Operational Sourcing Workshop:

 

Typical approach is a half day workshop session to assess and define the to-be operating model functional components. Typical areas of coverage include:

 

  • Customers

    • who are they?

    • how do they differ?

    • what is important to them?

  • Operating Models

    • what are they?

    • how do they differ?

    • which are most appropriate for my portfolio of customers and workloads?

  • Product-Based Delivery

    • what is a product?

    • how is it different than a project?

    • what are the benefits?

  • Products
    what products should i build? which should be built first?

  • Product Teams

    • who is on them?

    • what roles do they play?

    • what are their responsibilities?

    • what culture do they have?

  • Product Teams | Platform

    • how do my product teams work together to enable cloud adoption?

  • Product Teams | Application

    • what does a modern, iterative learning culture look like?

  • Org and Team Interaction Models

    • how do my product teams work together to enable cloud adoption?

  • Training & Enablement

    • what skills does my organisation already have?

    • what skills need to be developed?

    • how do I start?

  • Transition

    • how do I think big but start small?

    • how do I deliver results quickly, learn, and expand?

 

 

Business Case Review:

 

1-2 hrs typically two iterations of the business case model.

 

Typical Customer Roles involved:

 

  • Finance or Business Operations

  • Programme Director

  • Owner of the application / infrastructure portfolio

 

Report Review:  

 

1-2 hrs typically two iterations of the report review.

 

Typical Customer Roles involved:

 

  • Finance or Business Operations

  • Programme Director

  • Owner of the application / infrastructure portfolio