Stephen Hawking’s final theory on black holes has been published, and you can read it for free

Stephen Hawking’s final theory on black holes has been published, and you can read it for free

Black Hole Entropy and Soft Hair

https://arxiv.org/abs/1810.01847

 

Advertisements

Writing Statement of Works

Writing Statement of Works

 

A Statement of Work or Proposal is THE most important sales ‘artefacts’ to win any deal and absolutely the most important in terms of Post sales hygiene and successful customer engagement an satisfaction.  Why, because it translate the sales to a legal serviceable contract.

Reference

ICT Architecture Titles by Deliverables

ICT Architecture Titles by Deliverables

 

As a Solutions Architect, I always like to think outcome or deliverables based. So here is a short description of ICT Architecture Titles by Deliverables. There seems to be a lot of confusion around these titles so hope this helps.

These titles vary depending where the nominated titles is allocated inside ICT Supply Chain. (Customer, MSP, Vendor, Solutions Integrator or Distributor) more on this here:- http://www.insidespin.com/channeltopics.php#resellers .

(Loosely based on TOGAF and Zachman)

ICT Architecture Titles and Deliverables

  1. Presales / Sales Engineers (Vendors and SI side only)
    • Competitive Selling
    • Proof of Concepts/Pilots/Health Checks
    • Product Selection / Commercial and Licensing Models
    • Bill of Materials
    • Account Planing
    • Customer Training
  2. Enterprise Architects (Usually only customer side) Quasi CIO level
    • Business Case
    • Strategy/Financial Justifications (ROI, TCO, Net Present Value, RPO/RTOs)
    • Project Managment
    • RFP / RFI Scoping
    • Risk and Governances
    • Technology Roadmaps
    • Reference Architectures
    • Vendor Selection
    • Architecture Practices
    • Sourcing Agreements
    • Service Level Agreements
  3. Solutions Architects/Domain Architects (Infrastructure/Application/Security)(Customer, Vendor or SI)
    • Infrastructure Requirements
    • Responding to RFI/RFPs
    • Statement of Work
    • High Level Design
    • Bill of Materials
    • Services Estimates
  4. Subject Matter Experts (Delivery Focused)
    • Low-Level Design
    • As-Built Documentations
    • Operating Manuals

This is Rule of Thumb only.

Reference

Spaghetti Situations

Spaghetti Situations

 

  • In ‘spaghetti situations’ in which everything is connected to everything, and everything influences everything it is by far not obvious what the best solution is. All people involved have a different idea about what the problem is. And if you ask them, all these people have different ideas about what the solution could;. If you, as engineer, consultant, manager or analyst are in a situation like this, then what to do?
  • In order to solve complex problems its required to define a overall strategy and method that will guide the development of the complex solutions and following a set critical path, budget and timeframe.
  • In order to design and accelerate the implementation of a solution, customers must commit to design decision and any acceptable risks. Multiply components solutions adds to the complexity, through validation and support from vendors is a absolute requirement and they must be invested in the success of the solution
  1. Define Budget
  2. Define Business Requirements
  3. Define Technical Requirements
  4. Define Success Criteria and key metrics
  5. Identify Risks
  6. Solutions Definition
  7. Project initiation
  8. Migration Plan
  9. Operate