Requirements Specification. 5.11.1 This part of the document sets out the Commissioner’s general requirements. No change may be made to the specification without prior arrangement having been obtained in writing from the named Commissioner’s Corporate Procurement Unit.
Requirements Specification. The requirements for the Delivery as specified by the Customer in Appendix 3, including any changes and additions incorporated by the Supplier.
Requirements Specification. Sub-appendices The Tenderer should provide: • The draft Public Engagement Plan in sub-appendix 4.M, “Public Engagement Plan”. Requirement R-10 Construction Interface Procedure.
Requirements Specification. The Requirements Specification is the requirements set out in Appendix 3 Services All the services that the Supplier is obliged to deliver under the Contract.
Requirements Specification. The Tenderer should describe the method for calculation and the validation of the consistency of the data used in the Business Plan with the input data used in the relevant cost calculation sheets in the draft Business model summary sheet. If the Tenderer has obtained third-party validation, the Tenderer should describe the basis and scope of such validation. Sub-appendices The Tenderer should provide: • the draft Business Plan in sub-appendix 4.Q, “Business Plan” • The draft Business model summary sheet in sub-appendix 4.R, “Business model summary sheet” Requirement R-13 Technical Design. Instruction
Requirements Specification. Sub-appendices The Tenderer should provide: • The draft Technical Design in sub-appendix 4.S, “Technical Design” • The draft Total design verification plan in sub-appendix 4.T, “Total design verification plan” Requirement R-14 Test and Commissioning Plan.
Requirements Specification. The Financing Plan shall be a written description of the input data and cost calculations provided in the excel sheet of the Financing model summary sheet, if relevant. The Financing Plan shall provide a description of the expected investments and funding sources. If the Tenderer has obtained third-party validation, the Tenderer should describe the basis and scope of such validation.
Requirements Specification. Technical components are required for a monitoring system, as they describe what should be monitored. To be able to monitor at all, the system must be able to communicate with services to obtain the relevant metrics. Therefore, the DSL must define some way to perform this communication, for instance by describing interfaces, inputs, and outputs. As a technical description of services is not easy to work with, the DSL should take into account the type of users and make sure it is usable by them. Besides describing how to communicate with a service, it should clarify what exactly is being agreed upon. For the scope of this thesis, a textual description should be enough for this. The monitoring process should also be able to define the actual agreements that will be monitored. In Chapter 3, we showed that in the logistics sector, for example, the timing of certain actions needs to be represented. Assuming that this is generally necessary in other domains, the DSL must be able to reason about time, e.g., by using some form of temporal logic. In addition, there must also be a way to describe obligations and permissions, e.g., by using some form of deontic logic. This would allow the DSL to reason about actions that must, might or may not be taken. Together, this should allow components of the monitoring system to reason about most types of agreements. Another observation made, is about frame SLAs, i.e. long term SLAs that offer the ability to concurrently have long-term and short-term agreements. While this could be a valuable extension to an SLA monitoring system, this is considered to be out of scope for the purposes of this thesis, to simplify the system. Some organisational components of an SLA must also be modelled, more specifically, the involved parties and contract validity that are required for the monitoring system. Other organisational components are not required for monitoring, but could still be present in the model. The reporting of monitoring results, for example, is not relevant for the monitoring process, but modelling it in the DSL could facilitate SLA construction. Components such as liability and level of escalation, however, could also easily be described in another language or outside of the system. Legal components are similar, as they are also not required for SLA monitoring. In order to keep the scope of the project manageable, these have not been included in the DSL. Finally, an SLA should contain contact information for the involved p...
Requirements Specification. NOMOS Annex A.2: Requirements Specification - services The Supplier's offer Annex B.1: Supplier’s offer - NOMOS Annex B.2: Supplier’s offer - services Specific NATO Codification and Implementation Annex C.1: Specific NATO codification and implementation information Annex C.2: NATO codification form Outline advance payment guarantee N/A Training programme The Supplier's end-user reservations
Requirements Specification. Under each Programme Milestone, except for Milestone 1.1, four rows have been pre-inserted for Project Milestones, however the number of Project Milestones is to be decided by the Tenderer. Thus the Tenderer can delete pre-inserted rows and insert as many additional Project Milestones as needed under each predefined Programme Milestone, except Programme Milestone 1.1, where no Project Milestones shall be inserted. The Tenderer should note that Appendix 3, Requirements specification, mentions several Project Milestones that should be included in this Appendix, e.g., documentation of the CO2 storage site’s compliance as per R-7 in Appendix 3, Requirements specification. The DEA requires that the Tenderer submits documentation for the entry into all sub-contracts required for the performance of the CCS Activities, e.g., with a CO2 storage supplier, as part of the deliverables in Programme Milestone 1.3 in this Appendix, and therefore not as part of BAFO.
