Copernicus Marine - User ¿ Support à la gestion des produits Copernicus Marine

• Thank you for your responses. I noted some inconsistency between the them though and was hoping that you could clarify them:
  
  In the response from 23 Feb 2024 17:07 you state that:
  major release: ~50-70 PUMs (plus associated docs)
  minor release: ~ 25 PUMs
  
  whereas in the response from 23 Feb 2024 17:00, you state:
  major release: 90 Word documents, between 25 and 130 pages long
  minor release: about half (i.e., 45 PUMs)
  
  So with the first option it would be between 100 and 120 PUMs total (1 major and 2 minor releases) and with the second option it would be 180 PUMs. Sorry to be insisting, but considering that this is likely to be the task requiring the most person-hours by far, it is important to know these numbers as accurately as possible to allow for some realistic personnel planning and budgeting. Thank you.
  

  23 février 2024 17:32 (heure de Paris)

  • Réponse:
    Bonjour, les chiffres que je vous ai donnés, des documents de 90 mots, correspondent à l'exemple de la release majeure de novembre 2023, pour vous donner un ordre de grandeur, c'était une release très conséquente.
    Habituellement, c'est ce que nous prévoyons pour la version majeure de 2024, nous attendons entre 50 et 70 PUM à réviser, ces documents font toujours entre 25 et 130 pages.
    Espérons que cela rendra les choses plus claires.//The figures I've given you, 90 word documents, correspond to the example of the November 2023 major release, to give you an order of magnitude - this was a very substantial release.
    Usually, this is what we project for the major version of 2024, we expect between 50 and 70 PUMs to be revised, these documents are always between 25 and 130 pages long.
    Hopefully this will make things clearer. Best regards,

    26 février 2024 12:17 (heure de Paris)

  Lire les réponses ou Masquer les réponses
• Hello, I would have a general question regarding the distribution of work and pay.
  Based on the due dates for the referencing (T+4m) and release reports (T + 8m), is it fair to assume that most of the referencing (Task 2) and PUM review work (Task 1) will limited to the first 4 and 8 months, respectively?
  
  If so, then based on our estimate of the associated work these tasks, we obtain a considerable mismatch between the amounts being paid and the amount of work being performed (left image in the attached model). From about month 6 onward, payments would considerably lag behind the amount of work performed. In practice, this represents a problem for us, as we of course need to pay our people in accordance with the amount of work they perform.
  
  Would it be possible to adjust the percentages attached to some deliverables? For instance, considering that Task 1 represents a large chunk of work, the corresponding report seems underpaid with just 15%. Could this be increased to 25 or 30% (in exchange for reducing the final report payment from 20 to 5% - right panel in attached image).
  
  Or perhaps our estimates of the amounts and distribution of workload are wrong. To help with this, could you maybe provide some more details, e.g.:
  1) How many major/minor releases will fall within the 16 month period and what are their approximate dates?
  2) How many PUMs per major/minor release?
  Thank you.
  
  

  21 février 2024 18:48 (heure de Paris)

  (PNG, 88 Ko) Fichier joint à la question : Télécharger

  • Réponse:
    Bonjour,
    L'échéancier de paiement ne sera pas modifié.
    Le livrable D4 sera livré pour la version majeure.
    Le livrable D3 est prévu après la version mineure, qui sera plus légère en termes de revue documentaire, permettant de consacrer plus de temps sur ce livrable.
    1) Il y aurait 1 version mineure en juin 2024, 1 version majeure en novembre 2024 et 1 version mineure au premier semestre 2025.
    2) • Version mineure : 25 PUM
    • Sortie majeure en 2024 entre 50 et 70 PUM
    //
    The payment schedule will not be changed.
    Deliverable D4 will be delivered for the major release.
    Deliverable D3 is scheduled after the minor release, which will be lighter in terms of document review, allowing more time to be spent on this deliverable.
    1) There would be 1 minor release in June 2024, 1 major release in November 2024 and 1 minor release in the first semester of 2025.
    2) • Minor release : 25 PUM
    • Major release in 2024 between 50 and 70 PUMs
    Best regards,

    23 février 2024 17:07 (heure de Paris)

  Lire les réponses ou Masquer les réponses
• Hello, the SOW states that there is to be 1 major release of PUMs per year and 2 minor releases. As these releases constitute a large portion of the overall workload, can you state
  1) how many major and minor releases will fall within the 16 month contract period (the workload will vary considerably depending on whether it is just 1 or 2 major releases)?
  2) how many PUMs do you expect per major and minor release?
  3) how many documents do you expect per each of Specification Review, Design Review, and Acceptance review?
  4) And can you define what you mean by "review"? I.e., are these just compliance checks (adherence to standard format, nomenclature, etc.) or also English corrections?
  Thank you.

  21 février 2024 14:01 (heure de Paris)

  • Réponse:
    Réponse : Bonjour, Les réponses aux questions se trouvent dans le document joint. // The answers to the questions can be found in the attached document. Best regards,

    23 février 2024 17:00 (heure de Paris)

    (PDF, 92 Ko) Fichier joint à la réponse : Télécharger

  Lire les réponses ou Masquer les réponses
• Hi, I would have a couple more questions:
  1) Document validation. What does this involve exactly? Just compliance checks or also English language editing/correction? Roughly how many documents need to be validated? If language editing/correction is required, how big are these documents approximately (page numbers or word count)?
  2) Several tasks seems to require inside knowledge of MOi processes and font-end or back-end tools and interfaces used to interact with MFCs and TACs. E.g., "Prepare the delivery of the documents following the process established by the team in charge of Copernicus Marine Technical Coordination", "Use the tools available to track statistics on downloads of data", or "An API solution proposed ... compatible with Mercator Ocean tools". It is difficult to write a detailed technical proposal without knowing what those processes and tools are exactly. So I guess my actual question is, how detailed to you expect the technical proposal to be considering that several tasks require knowledge of internal processes, tools, and procedures that a normal outside applicant has no a priori knowledge of? Is it sufficient to simply state that we will follow your internal procedures and use the available tools?
  3) Task 4. Could you clarify a language issue in the English text: What is meant by "coordinate the interface" or "ensure a smooth interface"? Do you perhaps mean "interaction" instead" of "interface"?
  4) Deliverable 3, API: Do you expect the contractor to do any coding? I.e., should the contractor actively work on implementing the DataCite API on your website or what exactly is expected here?
  5) Workload. Can you give some indication of the expected workload (either in terms of person-hours per week or full time equivalents). Thank you.

  14 février 2024 11:47 (heure de Paris)

  • Réponse:
    Bonjour, Les réponses aux questions se trouvent dans le document joint. // The answers to the questions can be found in the attached document. Best regards,
    

    23 février 2024 17:00 (heure de Paris)

    (PDF, 93 Ko) Fichier joint à la réponse : Télécharger

  Lire les réponses ou Masquer les réponses
• Dear Madam/Sir,
  
  In the frame of tender ?Copernicus Marine ? Support with Copernicus Marine product management?, we would kindly request clarification regarding the following two topics:
  
  1) Financial proposal:
  The document "Tender Regulations" states that "Each candidate must detail the amount of his offer, based in particular on the payment schedule". However, we have not found further instructions regarding the payment schedule and how the amount of the offer is to be presented.
  Looking at the document "Act of engagement", we see that one of the fields to be filled out is: "Amount of the public contract. On the basis of its offer, to carry out the services requested at the price indicated below: Amount before tax."
  Could you please confirm whether the financial offer should only include a total price for the whole set of tasks of the contract or whether payment will be done under the basis of daily rates and the amount of effort required to carry out the different tasks?
  2) Technical proposal:
  Could you please confirm whether there is a maximum number of pages for the technical proposal document?
  
  Thank you In advance for your attention.
  
  Best regards,
  

  13 février 2024 07:49 (heure de Paris)

  • Réponse:
    Bonjour, 1) L'échéancier se trouve à l'article 5.3.1 du document CCAP. Nous vous demandons également de détailler le montant de votre offre, afin de comprendre la façon dont vous l'avez construit.
    2) Cet appel d'offres ne comporte pas de limitation du nombre de page, vous êtes libres d'organiser votre réponse. // The schedule can be found in section 5.3.1 of the SCC document. We also ask you to detail the amount of your offer, in order to understand how you constructed it.
    2) This call for tenders has no limitation on the number of pages, you are free to organize your answer. Best regards,

    15 février 2024 18:32 (heure de Paris)

  Lire les réponses ou Masquer les réponses
• Hello, I would have a question regarding the 3rd bullet point under deliverable D3, where it states that the report shall contain "An API solution proposed by datacite Fabrica". This is a little confusing. If the API is delivered by DataCite, what is the exact role of the contractor here? E.g., is the contractor expected to suggest how this API could be integrated with an existing web platform at MOI? Some clarification would be helpful. Thank you.

  8 février 2024 11:21 (heure de Paris)

  • Réponse:
    Bonjour, Oui exactement, suggérez comment cette API pourrait être intégrée aux outils existants déjà en place chez Mercator Océan pour attribuer et mettre à jour automatiquement les DOI. // Yes exactly, suggest how this API could be integrated with existing tools already in place at Mercator Ocean to automatically assign and update DOIs. Best regards,

    8 février 2024 14:33 (heure de Paris)

  Lire les réponses ou Masquer les réponses

Il y a 0 question(s) en attente