{"text_format":"1","workbook":"xlsx","n_sheets":2,"sheets":["Derived Requirements","Sheet3"],"not_rendered":{"charts":0,"images":0,"macros":0,"external_links":0,"defined_names":1,"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":"Derived Requirements","index":0,"n_rows":97,"n_cols":11,"rows_kept":97,"cut":false,"hidden":false,"merged":[[34,6,37,6],[34,7,37,7],[34,8,37,8],[34,9,37,9],[34,10,37,10],[62,0,74,0],[67,2,69,2],[72,2,74,2],[75,0,95,0],[88,2,91,2],[92,2,95,2],[82,2,87,2],[79,2,81,2],[19,0,38,0],[19,2,23,2],[24,2,28,2],[39,0,61,0],[47,2,61,2],[31,2,32,2],[39,2,46,2],[13,1,18,1],[0,0,0,10],[13,0,18,0],[9,0,12,0],[9,1,12,1],[1,0,1,10],[3,0,3,3],[3,4,7,5],[3,6,7,10],[2,0,2,10],[24,3,28,3],[67,3,69,3],[19,1,38,1],[72,3,74,3],[47,3,61,3],[39,1,61,1],[19,3,23,3],[31,3,32,3],[34,2,37,2],[39,3,46,3],[88,3,91,3],[82,3,87,3],[92,3,95,3],[75,1,95,1],[62,1,74,1],[79,3,81,3],[77,3,78,3],[77,2,78,2],[63,2,64,2],[34,5,37,5],[34,4,37,4],[34,3,37,3],[63,5,64,5],[63,4,64,4],[63,3,64,3]]}
["ARMYHQ2/00279 - VERITAS ENDURING IT SUPPORT"]
["PRICING MATRIX"]
[]
["Name and Address of Contractor",null,null,null,"Ministry Of Defence\n\nVERITAS Enduring IT Support \n",null,"CONTRACT:\n \nARMYHQ2/00279"]
[]
[null,"Techmodal, "]
[null,"27 Queen Square ,Bristol, BS1 4ND "]
[]
["Serial","Key Requirements","Serial","Sub Requirement","Serial"," ","Individual Qty Price  Year 1","Individual Qty Price Year 2","Individual Qty Price Year 3","Individual Qty Price  for option Year 4 ","Individual Qty Price  for option Year 5 "]
[1,"Generic Requirements",1.1000000000000001,"One page Support updates \n(Firm Price)","1.1.1","The Contractor shall liaise closely with the Authority on the delivery of the support solution.               \nThe Contractor shall provide a one page summary to the Authority on the first working day of each month summarising the status of VERITAS Support progress and should include risks and issues to the system"]
[null,null,1.2,"Support Plan \n(Firm Price)","1.2.1","Within 20 working days of the completion of the CAR the Contractor shall produce a annual Support plan and schedule. Further updates shall be provided if mutually agreed by the Authority and the Contractor. "]
[null,null,1.3,"Support Coverage \n(Firm Price)","1.3.1","The Contractor shall undertake the activities and manage the delivery of all elements of VERITAS support and it's releases. As agreed with the Authority."]
[null,null,1.4,"Sustainable Data Feeds\n(Firm Price)","1.4.1","The Contractor will identify and work with Data Owners, Director Info and DE&S to secure sustainable data feeds for all new functionality. New ICDs will be produced by the Contractor and signed by the Data Provider as part of this process."]
[2,"Capability Assessment review (CAR): One off requirement at start of contract.",2.1,"System Review end to end \n(Firm Price)","2.1.1","The Contractor is to familiarise themselves with the live system and all of it components and documentation. Report to the Authority any suggested improvements. "]
[null,null,2.2000000000000002,"Data Analysis Report \n(Firm Price)","2.2.1","The Contractor is to familiarise themselves with the current Interface Control Documents (ICD's) and ICD Log to understand Data Contractors, Points of Contact, Contact Details, and what interfaces require manipulation. Report to the Authority any suggested improvements, and possible reductions in manipulation. "]
[null,null,2.2999999999999998,"Stakeholder Analysis \n(Firm Price)","2.3.1","The Contractor is to produce a detailed stakeholder analysis document based on current VERITAS usage, processes VERITAS enables and application functionality.                                                                                    "]
[null,null,2.4,"Process Review\n(Firm Price)","2.4.1","The system Currently has two Concept of Use (CONUSE) documents one covering Defence Equipment and Support (DE&S) and one covering Army, we require the Contractor to thoroughly review both and adapt them to accommodate the process level for each stakeholder area, from the stakeholder analysis work. (Detailed above)"]
[null,null,2.5,"Training Reviews\n(Firm Price)","2.5.1","The Contractor is to carry out a review of the current Training Plan and Training Need Analysis (TNA) documentation. Updating them to include any missing elements from the stakeholder and process analysis work. (Detailed above)"]
[null,null,2.6,"Forecasting Algorithms Review\n(Firm Price)","2.6.1","Review the multiple Forecasting Algorithms currently within VERITAS, and reports any improvements/refinement required. "]
[3,"Maintaining the system",3.1,"Issues Management \n(Firm Price)","3.1.1","The Contractor shall, in conjunction with the Authority, develop and exploit a robust issues reporting and prioritisation system: Response times:\n-   1  working day to show receipt of issue.\n-   3 working days to provide feedback on issues.\n\nFor incidents and issues forwarded to the Contractor from the Authority: The Contractor shall respond to/update user on issue resolution progress within 1 working day and aim to resolve issues within 5 working days where possible. The Authority should be copied in to all correspondence. "]
[null,null,null,null,"3.1.2","Help Service: The Contractor shall provide a help  service (Phone/email/service desk) to the user community and Authority.  Coverage from 8am-5pm Mon-Fri.  This service desk will provide the following:                                                        1. Direct Feedback to user on issues raised including estimated resolution time and issue tracking reference in accordance with 3.1.1 above.                                                           2. Live issue log                                                    3. Monthly reports n issues resolved to Authority from live issues log.                                            "]
[null,null,null,null,"3.1.3","Contractor identified issues are subject to the same issue resolution process and timescale found and agreed via the Issue resolution prioritisation Review "]
[null,null,null,null,"3.1.4","Issue Communication to users, detailing issue status and issue resolution times. "]
[null,null,null,null,"3.1.5","In agreement with the Authority, the Contractor will seek to understand both external and internal threats to VERITAS and implement appropriate actions to restore system functionality with minimal downtime"]
[null,null,3.2,"Hierarchies Management \n(Firm Price)","3.2.1","Contractor to review the current hierarchies, and suggest improvements, including the investigation of automating hierarchies where possible. "]
[null,null,null,null,"3.2.2","Implement hierarchy review findings, in agreement with the Authority into VERITAS."]
[null,null,null,null,"3.2.3","The Contractor shall update and maintain all hierarchy data owners/Points of Contact (POC) associated to VERITAS. "]
[null,null,null,null,"3.2.4","The Contractor shall maintain all VERITAS associated hierarchies ensuring that there are no unallocated data elements. "]
[null,null,null,null,"3.2.5","The Contractor shall work with Authority staff to train and then pass over the management of data hierarchies. By March 2020. "]
[null,null,3.3,"Base Plan Management (Firm Price)","3.3.1","The Contractor shall provide 1 days assistance to the Authority weekly to ensure Base plans load, run and operate correctly in VERITAS. Specifically the Contractor will be available to work alongside the Bus Imp Team in Andover during the first live  update to any new plan/source set on a new release. The Contractor will be on hand (via telephone/email) to investigate and resolve errors with data feeds, source sets, base plans and hierarchies as a priority during daily, weekly, monthly updates. \n"]
[null,null,3.4,"Forecasting Algorithms Review\n(Firm Price)","3.4.1","Maintain and amend the multiple forecasting algorithms required by the Authority. "]
[null,null,3.5,"Interface Management (Firm Price)","3.5.1","Currently the majority of interfaces go into VERITAS. VERITAS then places them into the Army Data Warehouse (ADW) Database schema. VERITAS then uses the information from ADW. Any new interface will initially need to follow this process until 3.5.3 delivers.  "]
[null,null,null,null,"3.5.2 ","The majority of interfaces follow 3.5.1 with data going into the ADW, but not all, this will need to be reviewed and rectified within the course of this contract with 6 monthly reports on progress being issued to the Authority"]
[null,null,3.6,"Exploitation Management \n(Firm Price)","3.6.1","VERITAS data has to be exploitable by Oracle Business Intelligence Enterprise Edition (OBIEE)  and Power BI Tools to enable internal reports to be run on any element of the VERITAS application. "]
[null,null,3.7,"Interim Training \n(Firm Price)","3.7.1","In the interim whilst the Automated Training Capability (Ref 5.1 below) is being developed the Contractor will provided the following:                                                                                         \n1. Administration training \n2. Classroom Base Training.\n3. Super User Training (The highest level permission in the system) - Internal staff understanding (Covering dashboard manager/creation) of whole system. \n4.     Continual Monthly training at Army and DE&S.                      "]
[]
[]
[]
[null,null,3.8,"BOM Support \n(Firm Price)","3.8.1","Contractor is to support DE&S with the maintenance of the Bill of Materials (BOM) to variant level for all Eqpt, Commodities."]
[4,"Communication",4.0999999999999996,"Meeting Attendance \n(Firm Price)","4.1.1","Governance Meetings: 1 day per Quarter. "]
[null,null,null,null,"4.1.2","Awareness briefs: 2 days per major release, agreed with Authority. Produce Awareness material for the brief. 2 day per release for senior staff. "]
[null,null,null,null,"4.1.3","Development Reviews; 2 days per major release, agreed with Authority. "]
[null,null,null,null,"4.1.4","Requirements meetings : 3 days per major release, agreed with Authority. "]
[null,null,null,null,"4.1.5","User Acceptance Testing: 2 days per major release, agreed with Authority. "]
[null,null,null,null,"4.1.6","Demonstrations: As required (like awareness days but more focused to specific areas and for senior staff."]
[null,null,null,null,"4.1.7","Record of Decisions (ROD):A ROD for any meetings shall be produced and submitted to the Authority by the Contractor within 5 working days."]
[null,null,null,null,"4.1.8","Project/Performance meetings:  A forum to enable the Authority and Contractor to discuss all performance and project related points and issues"]
[null,null,4.2,"Documentation: All documents updated for each release of the system, covering any amendments. \n (Firm Price)","4.2.1","Step by Step Guides: Updates to Step by step guides for each areas of the system for each release. "]
[null,null,null,null,"4.2.2","Administration Guides: Updates to Step by step guide for each areas of the system for each release"]
[null,null,null,null,"4.2.3","System Design Document (SDD): High level design document to give an understanding of the system. "]
[null,null,null,null,"4.2.4","Detailed Design Document (DDD): Detail/Code level design of the system.   "]
[null,null,null,null,"4.2.5","Data Modal: A pictorial version of all the VERITAS database tables and their linkage to one another, updated for each release. "]
[null,null,null,null,"4.2.6","Master Data Assumptions List (MDAL) to be kept updated with any release over life of contract, and cover all business rules in the VERITAS application."]
[null,null,null,null,"4.2.7","Application Files (Source Code): The provision of source code comprising of a set of Data Definition Language (DDL) and Data manipulation language (DML) SQL scripts to install the application in the database through IAS for each release."]
[null,null,null,null,"4.2.8","Requirements Documentation: Format to be agreed with Contractor. "]
[null,null,null,null,"4.2.9","Interface Control Documents (ICD's): Details of format and frequency of data transfer to VERITAS. "]
[null,null,null,null,"4.2.10","Stakeholder Analysis (SA) Document: A list of all stakeholders of the system, and where the work. "]
[null,null,null,null,"4.2.11","Training Needs Analysis: A review carried out to understand the level of training required of users of the system. "]
[null,null,null,null,"4.2.12","Training Material: PowerPoint Slide packs for each area of the system, with context. "]
[null,null,null,null,"4.2.13","Training Plan:  Annually plan of training to be undertaken. "]
[null,null,null,null,"4.2.14","VERITAS System Help Text: Every screen in VERITAS to have page, Chart or Dashboard help text covering every element of the system. "]
[null,null,null,null,"4.2.15","Concept of Use (CONUSE): Explains what each team does and how VERITAS enables those teams. Linked to Process review requirement.  "]
[5,"System Enhancements",5.0999999999999996,"Automated Training Capability \n(Firm Price)","5.1.1","Production of on-line training support system: The Contractor shall develop an Online Training Capability accessible via the defence intranet, to all MOD users. "]
[null,null,5.2,"VERITAS Support of the Command Acquisition Support Plan (CASP) Governance processes.\n(Firm Price)","5.2.1","The Contractor is to ensure that the digitised CASP outputs continue to be effective year on year, for the duration of the contract. Ensuring any changes each year are incorporated and any in In Year updates are also included. This should include any workshops required and any updates to documentation. "]
[]
[null,null,5.3,"Mean Variant Between Failure (MVBF) \n(Firm Price)","5.3.1","Review the MVBF in VERITAS and how it effects VERITAS. Highlight issues with the calculations i.e. static items, suggest and implement resolutions with agreement with the Authority. "]
[null,null,5.4,"Consumable Inventory (Firm Price)","5.4.1","Review the new financial treatment for dealing with consumable inventory from April 18, and incorporates changes into VERITAS to reflect this.  "]
[null,null,5.5,"Continuous Improvement \n(Limit of liability)","5.5.1","The Contractor shall seek continuous improvement to reduce the amount of data manipulation on interfaces into VERITAS: Manual manipulation of data feeds will be kept to an absolute minimum. Where possible data should be fed directly from the source in to VERITAS to enable passthrough to the ADW (Reference 3.5.1,3.5.3) . \n\nAny reformatting of data should be done within VERITAS automatically. If this is not possible then Data Owners should be asked to provide the data in a format suitable for VERITAS.  \n\nVERITAS should be built to accept the format supplied by the Data Owner.\n"]
[null,null,null,null,"5.5.2","The Contractor shall seek continuous improvement to improve the performance of the system."]
[null,null,null,null,"5.5.3","Deliver outputs of the Process Review undertaken in the CAR agreed by the authority.  "]
[null,null,5.6,"Army Recruitment Training Division (ARTD) Review and update.\n(Firm Price)","5.6.1","Review of current ARTD capability in VERITAS  with the aim of removing all middleware and aligning with the core VERITAS capability and interfaces. "]
[null,null,5.7,"Hierarchies Review and Update \n(Firm Price)","5.7.1","Expansion of current Operational Command (Opcom) hierarchies, to cover all Top Level Budget (TLB's) end to end. "]
[null,null,5.8,"Requests for Change (RFC's) - Limit of liability requirement per year","5.8.1","Contractor or User requested/generated changes to the system: Contractor to provide an overview against this entry and provide details of his approach for changes identified by the Contractor and changes identified by the user. "]
[null,null,null,null,"5.8.2","All unfulfilled or not completed RFCs to date by the Authority shall be incorporated by the Contractor as part a release in the initial year. "]
[null,null,null,null,"5.8.3","All documentation is to be updated for any RFC's undertaken."]
[6,"System Release Management",6.1,"Contractors development environment \n(Firm Price)","6.1.1","The Contractor shall establish a remote development environment at their premises  in which VERITAS development can be performed and is able to seamlessly integrate into IAS systems and the ADW infrastructure. \n\nAuthority considers this an essential tool for success of VERITAS. It shall be the responsibility of the Contractor to ensure that all the appropriate processes and documentation are complied to enable full and tested Release of the application into ADW. If the application fails to meet IAS requirements and is excluded from being placed into ADW, then the Contractor shall be responsible for corrective action at no additional cost to MOD."]
[null,null,6.2,"Migration \n(Firm Price)","6.2.1","All work to migrate existing User Plans and Base Plans to a new release of VERITAS will be carried out by the Contractor.  "]
[null,null,6.3,"Releases\n(Firm Price)","6.3.1","We are expecting a minimum of two release a year. (ideally no more than 4) "]
[null,null,null,null,"6.3.2","The Contractor is to work within the following release process of IAS for VERITAS:                          a.  Contractor provided a release plan (minimum period to the release, negotiated and agreed with the Authority)                                                                            b. Contractor delivers code (Ref Serial 4.2.6) to IAS\nc. Contractor notifies Authority who then raise internal action. \nd. Contractor to support IAS carrying out basic testing.\ne. The release is issued to the internal Application Support Team (AST).\nf. Contractor to support AST carrying out a data backup and install onto Pre Prod. \ng. The Authority carries out any User Acceptance Testing (UAT) on Pre-Prod. (Ref Serial 4.1.5)\n(The Contractor will need to run Base plans  on Pre-Prod VERITAS to enable this UAT.)                 h. The Contractor is to resolve as many issues as possible on pre-prod prior to release, all remaining issues will go into a patch following the release. \nI. Contractor to support  AST carrying out a data backup of Production and install."]
[null,null,6.4,"Patches \n(Firm Price)","6.4.1","We expecting a patch after each release to fix any unknown issues arising from a release. "]
[null,null,null,null,"6.4.2","Code issues found throughout the year that can be fixed without a major release "]
[null,null,null,null,"6.4.3","The Authority agrees a patch to reduce risk of a release. "]
[null,null,6.5,"Testing \nFirm Price)","6.5.1","Unit Testing - testing of the individual functions of the application in isolation in the Contractors own environment. "]
[null,null,null,null,"6.5.2","Regression Testing:  the Contractor shall ensure that all existing functionality of the VERITAS application is maintained. Covering the entire capability end to end. "]
[null,null,null,null,"6.5.3","System Testing - pre-handover testing of the application within the IAS development environment. "]
[null,null,null,null,"6.5.4","User Acceptance Testing on Pre-Production environment: testing the system in the ADW in conjunction with IAS for approval by the Authority and stakeholders against the requirements."]
[null,null,null,null,"6.5.5","Live Testing - new functionality and bug fixes will be rigorously tested on the live system by the Contractor to ensure requirements have been met/resolved."]
[null,null,null,null,"6.5.6.","Contractor will spend time with Subject Matter Experts (SME's) at their desks testing all aspects of new functionality and compile lists of issues for resolution into the next release. Once fixed the Contractor will re-test with SMEs on their live system to obtain sign-off."]
[null,null,6.6,"Code Transfer to IAS \n(Firm Price)","6.6.1","System Integration: The Contractor shall liaise closely with IAS to load the application into the ADW development area (Pre Prod) and work through any issues that may arise. Prior to transfer into ADW the Contractor shall mitigate any issues by thoroughly testing the application within their own environment. All testing shall be completed within the IAS development environment before it is moved to live ADW"]
[null,null,null,null,"6.6.2","The Contractor shall provide Application Files & Data Model to IAS prior to installation onto the ADW for Integration testing. \n "]
[null,null,null,null,"6.6.3","The Contractor shall provide a presence in Andover to support IAS staff during testing. The IAS team may require the application to be penetration tested independently; this shall also be supported by the Contractor. "]
[null,null,null,null,"6.6.4","Following the successful completion of Integration testing, the application will be packaged up by IAS staff and passed to the IAS test cell for full testing internally. Testing can take up to 5 working days and needs to be incorporated into any release plans. The Contractor shall fully support IAS staff during this testing period. "]
[null,null,6.7,"Compatibility Management \n(Firm Price)","6.7.1","The Contractor shall ensure that the system remains compatible with changes to browser software. The system needs to be compatible with both IE and Chrome. "]
[null,null,null,null,"6.7.2","The Contractor shall ensure that VERITAS aligned to any Dii/MoDNet/ADW Technical refreshes. Examples such as Apex, Java, Adobe Flash.  (Currently IAS plan for 4 Apex updates per year however, due to the nature of our business and its shifting priorities the normal is for 2 Apex updates per year)"]
[null,null,null,null,"6.7.3","The Contractor shall ensure the system remains compatible with changes to the ADW over time and any upgrades to future version of Apex"]
[null,null,null,null,"6.7.4","The Contractor shall ensure that the system remains compatible with changes to interfaces /data sources over time. "]
[7,"Reporting",7.1,"(Firm Price)","7.1.1","The Contractor will produce Service Delivery and Progress Reports in conjunction with BCMs/SMEs and against the KPI's. (Annex A to SC2) "]

{"sheet":"Sheet3","index":1,"n_rows":0,"n_cols":0,"rows_kept":0,"cut":false,"hidden":false,"merged":[]}