{"text_format":"1","workbook":"xlsx","n_sheets":1,"sheets":["Score Card"],"not_rendered":{"charts":0,"images":1,"macros":1,"external_links":0,"defined_names":0,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Score Card","index":0,"n_rows":46,"n_cols":11,"rows_kept":46,"cut":false,"hidden":false,"merged":[[9,9,10,9],[9,10,10,10],[28,8,30,8],[28,9,30,9],[28,10,30,10],[23,8,26,8],[23,9,26,9],[23,10,26,10],[16,9,17,9],[16,10,17,10],[12,9,14,9],[12,10,14,10],[28,0,30,0],[28,1,30,1],[28,2,30,2],[28,7,30,7],[23,0,26,0],[23,1,26,1],[23,2,26,2],[23,7,26,7],[28,3,30,3],[28,5,30,5],[28,4,30,4],[23,4,26,4],[23,3,26,3],[23,5,26,5],[16,0,17,0],[16,1,17,1],[16,2,17,2],[16,7,17,7],[16,8,17,8],[16,3,17,3],[16,5,17,5],[16,4,17,4],[12,0,14,0],[12,1,14,1],[12,2,14,2],[12,7,14,7],[12,8,14,8],[12,3,14,3],[12,5,14,5],[12,4,14,4],[9,0,10,0],[9,1,10,1],[9,2,10,2],[9,7,10,7],[9,8,10,8],[9,5,10,5],[9,4,10,4],[9,3,10,3],[2,0,7,0],[2,1,7,1],[2,2,7,2],[2,7,7,7],[2,8,7,8],[2,4,7,4],[2,5,7,5],[2,9,7,9],[2,10,7,10],[2,3,7,3],[0,3,0,4],[0,7,0,8],[0,9,0,10]]}
[null,null,null,"Columns D & E should be hidden"]
["Domains","Description","Notes","Weighting","Score Numerical","Score",null,"Non-Existent/Basic","Emerging","Practising","Leading"]
["Cloud Financial Management","Implementing Cloud Financial Management enables organizations to realize business value and financial success as they optimize their cost and usage and scale on AWS.\n\nDefining roles and responsibilities forms the foundation of any cloud optimisation efforts in your organisation.\n\nDefine a strategy to communicate objectives, metrics, and obstacles, ensuring alignment among all stakeholders.",null,0.4,{"$f":"_xlfn.SWITCH(F3,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"There is no alignment between finance and technology regarding cloud costs.\n\nThere are no budgets or reporting.","There is a finance role responsible for cloud closts, but no techical role assigned.\n\nWhile cost data is available it is not regularly reviewed.","Finance and technology roles for cloud cost reporting and optimisation are in place, with some alignment.\n\nCost Explorer or similar tool used to report on costs, and tagging is in place.","There is a strong allignment between the tech & finance regarding cloud costs, with regular meetings to analyze the cost efficiency of workloads and to promote cost aware culture.\n\nCost reports including Cost and Usage  files are regularly analysed.\n\nBudgets are configured and tracked."]
[]
[]
[]
[]
[]
[]
["Governing Usage","AWS has defined best practises for each pillar of the Well-Architected Framework, following these will help produce stable and efficient systems.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  ",null,0.4,{"$f":"_xlfn.SWITCH(F10,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"There is little or no evidence of attempts to follow AWS best practise.\n\nRoles and Groups are not used to delegate permissions appropriately.\n\nThere is no tracking or auditing of project resources","Some familiarity with AWS Best Practises, with policies implemented in relation to atleast 2 best practises.\n\nProject resources and tracked and mesaured, but there is a lack of auditing.","AWS Best Practises relating to cost-optimisation are well understood, and generally implemented and followed.\n\nProjects resources are tracked, measured and audited.\n\nAll workloads have cost and usage goals defined.","AWS Best Practises are well understood and used to shape policy relating to cost-optimisation efforts. These policies are fully implemented and followed by all teams.\n\nProjects resources are tracked, measured and audited. All resources are wrapped up at the close of a project. \n\nGroups are effectively used to delegate appropriate permissions to the right users."]
[]
[]
["Monitoring Usage and Cost","Gaining a granular understanding of your costs and usage enables the team to take actions to improve cost optimisation.  Creating models and forecasts of future spend, usage and features reduces wastage, and enables you to align cost and usage to your organisations objectives.",null,0.3,{"$f":"_xlfn.SWITCH(F13,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"AWS Cost & Usage, Cost Explorer and Cloud Watch have not been customised to the customers needs.\n\nNo tagging schema is in place.\n\nNo metrics have been defined for workloads.","AWS Cost & Usage and Cost Explorer are used, however they are not customised to provide detailed infromation.\n\nA tagging schema is in development,or it is usedbut not regularly reviewed to ensure the right data is being tracked.\n\nWhile each workload can be correlated to a business out come, performance metrics have not been defined.","AWS Cost & Usage and Cost Explorer are both used to provide a detailed breakdown of utlisation and spend.\n\nA tagging schema has been implented and is regularly reviewed.\n\nAll workloads have a defined metric that measures performance in relation to business ourcome., ","AWS Cost and Usage Reports and Cost Explorer are configured to provide detailed cost and usage information which also relate to business outcomes.\n\nHave implemented a complete tagging chema, which surfaces the data needed to meet KPIs and allocate costs within the organisation.\n\nAll workloads have a defined metric that measures performance in relation to business ourcomes, and is regularly reviewed."]
[]
[]
[]
["Decommissioning Resources","Implement change control and resource management from project inception to end-of-life. This ensures you shut down or terminate unused resources to reduce waste and unecessary spend.",null,0.7,{"$f":"_xlfn.SWITCH(F17,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"There is no process for tracking resources and decommissioning them at the end of their useful lifetime.","Resources are often decommissioned at the end of their lifecycle, however there may be some delay in doing so. There is no method for tracking resources currently in place.","Customer has defined, and usually follows a set method for tracking resources and their associations with systems over their lifetime.","Customer has defined and is following a method for tracking resources and their associations with systems over their lifetime. From this they are able to identify, or anticipate redundancy, and decommission resources in a timely manner to avoid unecessary costs."]
[]
[]
["Current Services and Resource Implementation","Maintain a high-level overview of the AWS platform in terms of services used, size, regions and cost. Compare against current documentation of the platform already in place.",null,0.2,{"$f":"_xlfn.SWITCH(F20,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"Applications have been migrated or installed without any redesign to optimise for running in the cloud. Database design is monolithic.","Load balancers are being used to direct traffic to multiple targets for the same applications. The targets are monolithic and single-tenant in design.\n\nContainers and/or microservices are not utilised to lower operating costs.","Web and Application load balancers are being used where applicable. \n\nContainers and/or Microservices are being used or application architecture is in the process of being modified to support them in the near future.","The application is fully architected to use containers and microservices to run workloads and database services only when needed\n.\nWeb and Application load balancers are being used where applicable.\n\nEvidence of evolutionary architecture leading to Serverless application and database support.\n\nAll DBs and EC2 instances are running in the lowest cost forms."]
[]
["Use of Pricing Models","If the spend is large eoungh, commit a sensible amount to AWS to achieve a discounted rate across all services. Allow room for cost reductions and future negotiation.",null,0.15,{"$f":"_xlfn.SWITCH(F22,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"All workloads are running On-Demand.\n\nNo consideration given to spot instances as an option for workloads.","Some Savings Plans and Reserved Instances have been purchased, but are not optimised.\n\nSpot instances have previously been considered, but a decision has been made not to use them.","A central purchasing and management policy for Savings Plans and Reserved Instances is in place and delivering acceptable Effective Savings Rates of 30%+.\n\nApplications are able to support Spot to some extent. Usually considers and uses spot instances where appropriate.","A central purchasing and management policy for Savings Plans and Reserved Instances is fully automated and delivering class-leading Effective Savings Rates of 40%+.\n\n Applications are well architected and  fully able to take advantage of Spot. Automation ensures that Spot is always used when possible."]
[]
["Rightsizing","Carry out regular utilisation reviews of compute, storage and database resources to ensure sizing and cost is appropriate to the workload and that the workload is still required.  \n\nEnsure that the lowest cost instance type is used which is still compatible with the workload, including burstable instane types.",null,null,{"$f":"_xlfn.SWITCH(F24,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"No rightisizing activities, and no strategy for burstable instance types.","Rightsizing is intermittently carried out on some but not all AWS services, however there is a lack of process or strategy.","Regularly carries out rightsizing on all EC2, EBS and RDS instances, including using burstable instances wherever possible. \n\nWorking on application compatibility to support emerging CPU architecture instance types.","Regularly carries out rightsizing on all EC2, EBS and RDS instances, using tools to aid the process.EC2 Instances are rightsized on both CPU and RAM usage and uses burstable instace types wherever possible.\n\nApplications are designed to support lower cost CPU architecture instance types."]
[]
[]
[]
[]
["Data Transfer Charges\n","Ensure that the platform and applications are architected to reduce data transfer charges between workloads, especially taking into account regional transfers.",null,null,{"$f":"_xlfn.SWITCH(F29,\"Non-Existent/Basic\",0,\"Emerging\",1,\"Practising\",2,\"Leading\",3)","v":0},"Non-existent/Basic",null,"No analysis or monitoring of data transfer charges.","Data transfer charges are monitored and reported on.","Data transfer charges are monitored and then analysed for each workload and it's components to identify opportunities for cost savings.\n\nAnomalies leading to higher costs are quickly identified and rectified.","Performs data transfer modelling of each workload and it's components, based on organisational requirements. \n\nWorkloads are  architected to minimise data transfer charges, and utilise relevant services such as a CDN or caching layers.\n\nAnomalies leading to higher costs are quickly identified and rectified."]
[]
[]
[]
[]
[null,null,"Overall Score:",null,{"$f":"(E3*E38)+(E10*E39)+(E13*E40)+(E17*E41)+(E20*E42)+(E22*E43)+(E24*E44)+(E29*E45)","v":0},{"$f":"_xlfn.SWITCH(ROUND(E34,0),0,\"Non-Existent/Basic\",1,\"Emerging\",2,\"Practising\",3,\"Leading\")","v":"Non-Existent/Basic"}]
["Copyright 2021 Tecflair Limited. All Rights Reserved."]
["The material in this document is copyright Tecflair Limited 2021 and must not be reproduced or sent to anyone other than the person to which it was delivered by Tecflair without prior permission."]
[null,null,null,"Domain","Weighting"]
[null,null,null,"Cloud Financial Management",0.2]
[null,null,null,"Governing Usage",0.17499999999999999]
[null,null,null,"Monitoring Usage and Cost",0.125]
[null,null,null,"Decomissioning Resources",5.5E-2]
[null,null,null,"Current Services and Resource Implementation",0.125]
[null,null,null,"Use of Pricing Models",0.2]
[null,null,null,"Rightsizing",0.1]
[null,null,null,"Data Transfer Charges",0.02]
[null,null,null,"Total",{"$f":"SUM(E38:E45)","v":1}]