atst/translations.yaml

# How to use text containing html tags in .html files:
  # In the template add the `safe` filter when referencing the string
  # from the template file. ie:

  # login:
  #   title: A title with <a href="#">a link</a>!

  # `{{ "login.title" | translate | safe }}`
audit_log:
  events:
    default:
      change: '{from} to {to}'
      changes: 'Changes:'
      details: 'Details:'
  header_title: Activity History
base_public:
  header_title: JEDI Cloud
  login: Log in
  title_tag: JEDI Cloud
common:
  back: Back
  edit: Edit
  manage: manage
  save_and_continue: Save & Continue
  sign: Sign
  officer_helpers:
    underscore_to_friendly:
      contracting_officer: Contracting Officer
      security_officer: Security Officer
      contracting_officer_representative: Contracting Officer Representative
components:
  modal:
    close: Close
  usa_header:
    flag_image_alt: U.S. Flag
    official_message: An official website of the United States government
    tooltip:
      message: |
        <p>
          <strong>The .mil means it’s official.</strong><br/>
          Federal government websites often end in .gov or .mil. Before sharing sensitive information, make sure you’re on a federal government site.
        </p><br/>
        <p>
          <strong>The site is secure.</strong><br>
          The <strong>https://</strong> ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.
        </p>
      title: Here’s how you know
footer:
  about_link_text: Joint Enterprise Defense Infrastructure
  browser_support: JEDI Cloud supported on these web browsers
  jedi_help_link_text: Questions? Contact your CCPO Representative
forms:
  ccpo_review:
    comment_description: Provide instructions or notes for additional information that is necessary to approve the request here. The requestor may then re-submit the updated request or initiate contact outside of AT-AT if further discussion is required. <strong>This message will be shared with the person making the JEDI request.</strong>.
    comment_label: Instructions or comments
    email_mao_label: Mission Owner e-mail (optional)
    fname_ccpo_label: First Name (optional)
    fname_mao_label: First Name (optional)
    lname_ccpo_label: Last Name (optional)
    lname_mao_label: Last Name (optional)
    phone_ext_mao_label: Extension (optional)
    phone_mao_label: Mission Owner phone number (optional)
  ko_review:
    start_date_label: Period of Performance Start Date
    end_date_label: Period of Performance End Date
    invalid_date: Must be a date in the future.
    pdf_label: Upload a copy of your Task Order document
    pdf_description: Upload a PDF of the Task Order that you entered in your system of record for your organization.
    to_number: Task Order Number
    loa: Line of Accounting (LOA) &#35;1
    custom_clauses_label: Task Order Custom Clauses (optional)
    custom_clauses_description: This will put a pause on the CSP access once the KO signs until the CCPO reviews that language to make sure it is legal.
  edit_member:
    portfolio_role_label: Portfolio Role
  edit_user:
    citizenship_description: What is your citizenship status?
    date_latest_training_description: |
      To complete the training, you can find it in
      <a class="icon-link" href="https://iatraining.disa.mil/eta/disa_cac2018/launchPage.htm" target="_blank">
        Information Assurance Cyber Awareness Challenge
      </a> website.
    date_latest_training_label: Latest Information Assurance (IA) Training Completion Date
    designation_description: What is your designation within the DoD?
    designation_label: Designation of Person
    email_description: Enter your preferred e-mail address
    email_label: E-mail Address
    first_name_label: First Name
    last_name_label: Last Name
    phone_number_label: Phone Number
    service_branch_description: Which service or organization do you belong to within the DoD?
    service_branch_label: Service Branch or Agency
  exceptions:
    message: Form validation failed.
  financial:
    ba_code_description: 'BA Code is used to identify the purposes, applications, or types of activities financed by the appropriation fund. <br/><em>It should be two digits, followed by an optional letter.</em>'
    ba_code_label: Program Budget Activity (BA) Code
    clin_0001_description: 'Review your task order document, the amounts for each CLIN must match exactly here'
    clin_0001_label: <dl><dt>CLIN 0001</dt> - <dd>Unclassified IaaS and PaaS Amount</dd></dl>
    clin_0003_description: 'Review your task order document, the amounts for each CLIN must match exactly here'
    clin_0003_label: <dl><dt>CLIN 0003</dt> - <dd>Unclassified Cloud Support Package</dd></dl>
    clin_1001_description: 'Review your task order document, the amounts for each CLIN must match exactly here"'
    clin_1001_label: <dl><dt>CLIN 1001</dt> - <dd>Unclassified IaaS and PaaS Amount <br> OPTION PERIOD 1</dd></dl>
    clin_1003_description: 'Review your task order document, the amounts for each CLIN must match exactly here'
    clin_1003_label: <dl><dt>CLIN 1003</dt> - <dd>Unclassified Cloud Support Package <br> OPTION PERIOD 1</dd></dl>
    clin_2001_description: 'Review your task order document, the amounts for each CLIN must match exactly here'
    clin_2001_label: <dl><dt>CLIN 2001</dt> - <dd>Unclassified IaaS and PaaS Amount <br> OPTION PERIOD 2</dd></dl>
    clin_2003_description: 'Review your task order document, the amounts for each CLIN must match exactly here'
    clin_2003_label: <dl><dt>CLIN 2003</dt> - <dd>Unclassified Cloud Support Package <br> OPTION PERIOD 2</dd></dl>
    email_co_label: KO Email
    email_cor_label: COR Email
    expiration_date_description: Please enter the expiration date for the Task Order
    expiration_date_label: Task Order Expiration Date
    fname_co_label: KO First Name
    fname_cor_label: COR First Name
    funding_type_description: What is the source of funding?
    funding_type_other_label: 'If other, please specify'
    lname_co_label: KO Last Name
    lname_cor_label: COR Last Name
    number_description: Include the original Task Order number (including the 000X at the end). Do not include any modification numbers. Note that there may be a lag between approving a task order and when it becomes available in our system.
    number_label: Task Order Number associated with this request
    office_co_label: KO Office
    office_cor_label: COR Office
    pdf_allowed_description: Only PDF documents can be uploaded.
    pdf_label: Upload a copy of your Task Order
    pe_id_description: 'PE numbers help the Department of Defense identify which offices'' budgets are contributing towards this resource use. <br/><em>It should be 7 digits followed by 1-3 letters, and should have a zero as the first and third digits.</em>'
    pe_id_label: Program Element Number
    treasury_code_description: 'Program Treasury Code (or Appropriations Code) identifies resource types. <br/> <em>It should be a four digit or six digit number, optionally prefixed by one or more zeros.</em>'
    treasury_code_label: Program Treasury Code
    uii_ids_description: 'If you have more than one UII, place each one on a new line.'
    uii_ids_label: Unique Item Identifier (UII)s related to your application(s) if you already have them.
  internal_comment:
    text_description: Add comments or notes for internal CCPO reference and follow-up here. <strong>These comments <em>will not</em> be visible to the person making the JEDI request.</strong>
    text_label: CCPO Internal Notes
  new_member:
    dod_id_label: DOD ID
    email_label: Email Address
    first_name_label: First Name
    last_name_label: Last Name
    portfolio_role_description: 'The portfolio role controls whether a member is permitted to organize a portfolio into applications and environments, add members to this portfolio, and view billing information.'
    portfolio_role_label: Portfolio Role
  new_request:
    am_poc_label: I am the Portfolio Owner
    average_daily_traffic_description: What is the average daily traffic you expect the systems under this cloud contract to use?
    average_daily_traffic_gb_description: What is the average daily traffic you expect the systems under this cloud contract to use?
    average_daily_traffic_gb_label: Average Daily Traffic (GB)
    average_daily_traffic_label: Average Daily Traffic (Number of Requests)
    cloud_native_description: Are your software systems being developed cloud native?
    data_transfers_description: How much data is being transferred to the cloud?
    dod_component_description: Identify the DoD component that is requesting access to the JEDI Cloud
    dod_component_label: DoD Component
    dodid_poc_label: DoD ID
    dollar_value_description: What is your total expected budget for this JEDI Cloud Request?
    dollar_value_label: Total Spend
    email_poc_label: Email Address
    engineering_assessment_description: Have you completed an engineering assessment of your systems for cloud readiness?
    estimated_monthly_spend_description: 'Use the <a href="/jedi-csp-calculator" target="_blank" class="icon-link">JEDI CSP Calculator</a> to estimate your <b>monthly</b> cloud resource usage and enter the dollar amount below. Note these estimates are for initial approval only. After the request is approved, you will be asked to provide a valid Task Order number with specific CLIN amounts for cloud services.'
    estimated_monthly_spend_label: Estimated Monthly Spend
    expected_completion_date_description: When do you expect to complete your migration to the JEDI Cloud?
    fname_poc_label: First Name
    jedi_migration_description: Are you using the JEDI Cloud to migrate existing systems?
    jedi_migration_label: JEDI Migration
    jedi_usage_description: Your answer will help us provide tangible examples to DoD leadership how and why commercial cloud resources are accelerating the Department's missions
    jedi_usage_label: JEDI Usage
    lname_poc_label: Last Name
    name_description: This name serves as a reference for your initial request and the associated portfolio that will be created once this request is approved. You may edit this name later.
    name_label: Name Your Request
    name_length_validation_message: Request names must be at least 4 and not more than 100 characters
    num_software_systems_description: Estimate the number of software systems that will be supported by this JEDI Cloud access request
    num_software_systems_label: Number of Software Systems
    number_user_sessions_description: How many user sessions do you expect on these systems each day?
    organization_providing_assistance_description: 'If you are receiving migration assistance, what is the type of organization providing assistance?'
    rationalization_software_systems_description: Have you completed a “rationalization” of your software systems to move to the cloud?
    reviewed_label: I have reviewed this data and it is correct.
    start_date_date_range_validation_message: Must be a date in the future.
    start_date_label: When do you expect to start using the JEDI Cloud (not for billing purposes)?
    technical_support_team_description: Are you working with a technical support team experienced in cloud migrations?
  application:
    description_label: Description
    environment_names_label: Environment Name
    environment_names_required_validation_message: Provide at least one environment name.
    environment_names_unique_validation_message: Environment names must be unique.
    name_label: Name
  task_order:
    portfolio_name_label: Organization Portfolio Name
    portfolio_name_description: The name of your office or organization. You can add multiple applications to your portfolio. Your task orders are used to pay for these applications and their environments.
    scope_label: Cloud Project Scope
    scope_description: Your team's plan for using the cloud, such as migrating an existing application or creating a prototype.
    defense_component_label: Department of Defense Component
    app_migration:
      label: App Migration
      description: Do you plan to migrate one or more existing application(s) to the cloud?
      on_premise: Yes, migrating from an <strong>on-premise data center</strong>
      cloud: Yes, migrating from <strong>another cloud provider</strong>
      both: Yes, migrating from an <strong>on-premise data center</strong> and <strong>another cloud provider</strong>
      none: Not planning to migrate any applications
      not_sure: "Not sure"
    native_apps:
      label: Native Apps
      description: Do you plan to develop any applications natively in the cloud?
      'yes': Yes, planning to develop natively in the cloud
      'no': No, not planning to develop natively in the cloud
      not_sure: Not sure, unsure if planning to develop natively in the cloud
    complexity:
      label: Project Complexity
      description: Which of these describes how complex your team's use of the cloud will be? Select all that apply.
      storage: Storage
      data_analytics: Data Analytics
      conus: CONUS Access
      oconus: OCONUS Access
      tactical_edge: Tactical Edge Access
      not_sure: Not sure
      other: Other
    complexity_other_label: Project Complexity Other
    dev_team:
      label: Development Team
      description: Who will be completing the development work for your cloud application(s)? Select all that apply.
      civilians: Government Civilians
      military: Military
      contractor: Contractor
      other: "Other <em class='description'>(E.g. University or other partner)</em>"
    dev_team_other_label: Development Team Other
    team_experience:
      label: Team Experience
      description: How much experience does your team  have with development in the cloud?
      none: No previous experience
      planned: Researched or planned a cloud build or migration
      built_1: Built or migrated 1-2 applications
      built_3: Built or migrated 3-5 applications
      built_many: Built or migrated many applications, or consulted on several such projects
    performance_length:
      label: Period of Performance length
    start_date_label: Start Date
    end_date_label: End Date
    csp_estimate_label: Upload a copy of your CSP Cost Estimate Research
    csp_estimate_description: Upload a PDF or screenshot of your usage estimate from the calculator.
    file_format_not_allowed: Only PDF or PNG files can be uploaded.
    clin_01_label: 'CLIN 01 : Unclassified'
    clin_02_label: 'CLIN 02: Classified'
    clin_03_label: 'CLIN 03: Unclassified'
    clin_04_label: 'CLIN 04: Classified'
    unclassified_clin_02_label: 'CLIN 02: Classified (available soon)'
    unclassified_clin_04_label: 'CLIN 04: Classified (available soon)'
    oversight_first_name_label: First Name
    oversight_last_name_label: Last Name
    oversight_email_label: Email
    oversight_phone_label: Phone Number
    oversight_dod_id_label: DoD ID
    oversight_am_cor_label: I am the Contracting Officer Representative (COR) for this Task Order
    ko_invite_label: Invite KO to Task Order Builder
    cor_invite_label: Invite COR to Task Order Builder
    so_invite_label: Invite Security Officer to Task Order Builder
    skip_invite_description: |
      <i>An invitation won't actually be sent until you click Done on the Review page. You can skip this for now and invite them later.</i>
  dd_254:
    certifying_official:
      label: Name of Certifying Official
      description: (Last, First, Middle Initial)
    certifying_official_title:
      label: Title
    certifying_official_address:
      label: Address
      description: (Include ZIP Code)
    certifying_official_phone:
      label: Telephone
      description: (Include Area Code)
    required_distribution:
      label: Required Distribution by the Certifying Official
  validators:
    is_number_message: Please enter a valid number.
    list_item_required_message: Please provide at least one.
    list_items_unique_message: Items must be unique
    name_message: 'This field accepts letters, numbers, commas, apostrophes, hyphens, and periods.'
    phone_number_message: Please enter a valid 5 or 10 digit phone number.
    is_required: This field is required.
  portfolio:
    name_label: Portfolio Name
    name_length_validation_message: Portfolio names can be between 4-100 characters
  officers:
    contracting_officer_invite: Invite KO to Task Order Builder
    contracting_officer_representative_invite: Invite COR to Task Order Builder
    security_officer_invite: Invite Security Officer to Task Order Builder
fragments:
  edit_application_form:
    explain: 'AT-AT allows you to create multiple applications within a portfolio. Each application can then be broken down into its own customizable environments.'
    new_application_title: Add a new application
  edit_user_form:
    date_last_training_tooltip: When was the last time you completed the IA training? <br> Information Assurance (IA) training is an important step in cyber awareness.
    save_details_button: Save Details
  pending_ccpo_acceptance_alert:
    learn_more_link_text: Learn more about the JEDI Cloud Task Order and the Financial Verification process.
    paragraph_1: The CCPO will review and respond to your request in 3 business days. You’ll be notified via email or phone. Please note if your request is for over $1M of JEDI cloud resources it will require a manual review by the CCPO.
    paragraph_2: 'While your request is being reviewed, your next step is to create a Task Order (TO) associated with the JEDI Cloud. Please contact a Contracting Officer (KO), Contracting Officer Representative (COR), or a Financial Manager to help with this step.'
  pending_ccpo_approval_modal:
    paragraph_1: The CCPO will review and respond to your Financial Verification submission in 3 business days. You will be notified via email or phone.
    paragraph_2: Once the financial verification is approved you will be invited to create your JEDI Portfolio and set-up your applications. Click here for more details.
  pending_financial_verification:
    learn_more_link_text: Learn more about the JEDI Cloud Task Order and the Financial Verification process.
    paragraph_1: 'The next step is to create a Task Order associated with JEDI Cloud.  Please contact a Contracting Officer (KO), Contracting Officer Representative (COR), or a Financial Manager to help with this step.'
    paragraph_2: 'Once the Task Order has been created, you will be asked to provide details about the task order in the Financial Verification step.'
  ko_review_message:
    title: Steps
    bullet_1: Make sure the information below matches the final task order and is accurate and up-to-date
    bullet_2: Upload your Task Order (TO) document
    bullet_3: Add both the Task Order (TO) and Line(s) of Accounting (LOA) numbers
  portfolio_admin:
    none: Not Selected
  ppoc:
    title: Primary Point of Contact
    subtitle: The PoC has the ability to edit all aspects of a portfolio.
    update_btn: Update Primary PoC
login:
  ccpo_logo_alt_text: Cloud Computing Program Office Logo
  certificate_selection:
    learn_more: Learn more
    message: 'When you are prompted to select a certificate, please select E-mail Certificate from the provided choices.'
    title: Certificate Selection
  h1_title: Access the JEDI Cloud
  login_button: Sign in with CAC
  title_tag: Sign in | JEDI Cloud
navigation:
  topbar:
    jedi_cloud_link_text: JEDI
    logout_link_title: Log out of JEDI Cloud
    named_portfolio: 'Portfolio {portfolio}'
    no_other_active_portfolios: You have no other active JEDI portfolios.
    other_active_portfolios: Other Active Portfolios
    request_portfolio_link_text: Request a new JEDI Portfolio
  portfolio_navigation:
    add_new_member_label: Add New Member
    add_new_application_label: Add New Application
    budget_report: Budget Report
    activity_log: Activity Log
    members: Members
    applications: Applications
    portfolio_funding: Funding
    portfolio_settings: Portfolio Settings
    portfolio_admin: Portfolio Administration
    breadcrumbs:
      admin: Admin
      funding: Funding
      reports: Reports
requests:
  _new:
    new_request: New Request
  approval:
    add_comment: Add a comment
    approve_comments_or_notes_description: Provide any comments or notes regarding the approval of this request. <strong>This message will be shared with the person making the JEDI request.</strong>
    approve_comments_or_notes_label: Approval comments or notes
    authorizing_officials_paragraph: Provide the name of the key officials for both parties that have authorized this request to move forward. <strong>This section is not visible to the person making the request. It is only viewable by CCPO staff.</strong>
    authorizing_officials_title: Authorizing Officials
    ccpo_approval_on_behalf_of: 'CCPO approval on behalf of:'
    ccpo_authorizing_official_title: CCPO Authorizing Official
    ccpo_internal_comments: CCPO Internal Comments
    ccpo_review_activity: CCPO Review Activity
    mission_authorizing_official_title: Mission Authorizing Official
    mission_owner_approval_on_behalf_of: 'Mission Owner approval on behalf of:'
    no_ccpo_approval_request_changes: No CCPO approvals or request changes have been recorded yet.
    no_ccpo_comments: No CCPO comments have been recorded yet.
    ready_for_approval: Ready for approval
    request_revisions: Request revisions
    request_title: 'Request: {displayname}'
    review_request: Review this Request
    revision_instructions_or_notes_label: Revision instructions or notes
    save_notes: Save Notes
  financial_verification:
    contracting_officer_information_title: Contracting Officer (KO) Information
    contracting_officer_representative_information_title: Contracting Officer Representative (COR) Information
    draft_saved: Draft saved
    enter_task_order_manually_link_text: Enter Task Order information manually
    expiration_date_placeholder: Please enter the expiration date for the task order only and do not include options that you may choose to exercise in the future.
    financial_verification_title: Financial Verification
    manually_enter_task_information_description: 'Additional fields are displayed below, where you can manually enter financial information as documented in your Task Order.'
    manually_enter_task_information_help_label: Learn more about the JEDI Cloud Task Order and the Financial Verification process.
    manually_enter_task_information_label: Manually enter Task Order information
    number_placeholder: A Contracting Officer will likely be the best source for this number.
    pending_financial_verification: Pending Financial Verification
    permissions_paragraph: 'In order to get you access to the JEDI Cloud, we will need you to enter the details below that will help us verify and account for your Task Order.'
    request_title: 'Request: {displayname}'
    some_errors_label: There were some errors
    task_order_not_found_eda_description: 'We could not find your Task Order in our system of record, EDA. Please confirm that you have entered it correctly.'
    task_order_not_found_eda_label: Task Order not found in EDA
    uui_ids_placeholder: A Unique Item Identifer is a unique code that helps the Department of Defense track and report on where and how digital assets are stored. <br>Not all applications have an existing UII number assigned.
  index:
    action_required: Action Required
    all_filter: All
    approved_requests: Approved Requests
    filter_by_dod_component: Filter by DOD Component
    filter_by_status: Filter by status
    filter_requests_by_dod_component: Filter requests by DOD component
    filter_requests_by_status_label: Filter requests by status
    financial_verification_submitted_title: Financial Verification submitted!
    no_requests_found: No requests found.
    no_portfolios_action_label: Create a new JEDI Cloud Request
    no_portfolios_label: You currently have no JEDI Cloud portfolios.
    no_portfolios_sub_message: A JEDI Cloud Portfolio is where you manage your applications and control user access to those applications.
    pending_ccpo_action: Pending CCPO Action
    request_submitted_title: Request submitted!
    requests_in_progress: Requests in progress
    search_button_text: Search
    search_by_name: Search requests by name
    try_different_search: Please try a different search.
  review_menu:
    financial_verification_information_link_text: Financial Verification Information
    request_information_link_text: Request Information
  screen-1:
    additional_plan_details_title: Please provide additional details regarding your planned usage.
    approximate_annual_spend_paragraph: |
      <p>
        So this means you are spending approximately
        <span class="label label--info">!{{ annualSpendStr }}</span>
        annually
      </p>
    average_daily_traffic_gb_tooltip: GB uploaded is the gigabyte amount of data traffic that is being transferred to your systems
    average_daily_traffic_tooltip: Requests are the client-to-server network traffic that is being transferred to your systems
    cloud_native_tooltip: 'Cloud native is architecting and designing your application to use all the benefits of the commercial cloud. Specifically, designing applications so that they are decoupled from a physical resource.'
    cloud_readiness_title_text: Cloud Readiness
    dollar_value_tooltip: You may specify a different Total Spend amount to cover other JEDI Cloud services that the JEDI Cloud cost calculator was not able to estimate. Examples may include support packages from the cloud service provider.
    engineering_assessment_tooltip: An engineering assessment is an evaluation to convert your application architecture from on-premises to using the commercial cloud
    estimated_monthly_spend_tooltip: Refer to financial verification step help docs
    financial_usage_title: Financial Usage
    form_instructions: |
      <p>We’d like to know a little about how you plan to use JEDI Cloud services to process your request. Please answer the following questions to the best of your ability. Note that the CCPO does not directly help with migrating systems to JEDI Cloud. These questions are for learning about your cloud readiness and financial usage of the JEDI Cloud; your estimates will not be used for any department level reporting.</p>
      <p><em>All fields are required, unless specified optional.</em></p>
    general_title_text: General
    jedi_migration_tooltip: 'Cloud migration is the process of moving data, applications or other business elements from an organization''s onsite computers/data centers to the cloud, or moving them from one cloud environment to another.'
    jedi_usage_placeholder: Briefly describe how you are expecting to use the JEDI Cloud. e.g. We are migrating XYZ application to the cloud so that...
    num_software_systems_tooltip: 'A software system can be any code that you plan to host on cloud infrastructure. For example, it could be a custom-developed web application, or a large ERP system.'
    questions_title_text: Questions related to JEDI Cloud migration
    rationalization_software_systems_tooltip: Rationalization is the DoD process to determine whether the application should move to the cloud.
task_orders:
  form:
    draft_alert_title: Your draft has been saved
  sign:
    digital_signature_description: I acknowledge that I have read and fully understand the DoD CCPO JEDI agreements and completed all the necessary steps, as detailed in the FAR (Federal Acquisition Regulation).
    digital_signature_label: Digital Signature
    level_of_warrant_description: This is a dollar value indicating that you have permission to sign any Task Order under this max value.
    level_of_warrant_label: Level of Warrant
    task_order_builder_title: Task Order Builder
    title: Sign Task Order
    unlimited_level_of_warrant_description: Unlimited Level of Warrant funds
    verify_warrant_level_paragraph: Verify your level of warrant and provide your digital signature to authorize this Task Order.
  view:
    whats_next: Here are the remaining tasks to get your Task Order approved.
    steps:
      draft: '<strong>Primary Point of contact ({contact})</strong> completes initial Task Order form.'
      security: '<strong>IA Security Officer ({security_officer})</strong> completes a Security Requirements Document. <a href="#">Send a reminder</a>'
      record: '<strong>Contracting Officer ({contracting_officer}) or Contracting Officer Representative ({contracting_officer_representative})</strong> records Task Order information. <a href="#">Send a reminder</a>'
      record_description: Obtain a funding document and file a Task Order in the appropriate system of record. Once this is complete, come back here and record the task order information.
      sign: '<strong>Contracting Officer ({contracting_officer})</strong> verifies funding to unlock cloud services.'
  new:
    app_info:
      section_title: "What You're Making"
      basic_info_title: Basic Information
      sample_scope: |
        Not sure how to describe your scope? <a href="#">Read some examples</a> to get some inspiration.
      project_title: About Your Project
      team_title: About Your Team
      market_research_title: Market Research
      market_research_paragraph: 'The JEDI Cloud Computing Program Office (CCPO) has completed the market research requirements for all related task orders. The Department of Defense CIO has approved this research.<br /><a href="#">View JEDI Market Research Memo</a>'
    funding:
      section_title: Funding
      performance_period_title: Period of Performance
      performance_period_description: Choose the length of time your task order will cover.
      performance_period_paragraph: Be aware that your funds will be lost if you don’t use them. Because of this, we strongly recommend submitting small, short-duration task orders, usually around a three month period. We’ll notify you when your period of performance is nearing its end so you can request your next set of funds with a new task order.
      estimate_usage_title: Estimate Your Cloud Usage
      estimate_usage_description: Calculate how much your cloud usage will cost. A technical representative from your team should help you complete this calculation. These calculations will become your CLINs.
      estimate_usage_paragraph: This is only an estimation tool to help you make an informed evaluation of what you expect to use. While you're tied to the dollar amount you specify in your task order, you're not obligated by the resources you indicate in the calculator.
      cloud_calculations_title: Cloud Usage Calculations
      cloud_calculations_paragraph: Enter the results of your cloud usage calculations below.
      cloud_offerings_title: Cloud Offerings
      cloud_offerings_paragraph: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) offerings
      support_assistance_title: Cloud Support and Assistance
      support_assistance_paragraph: Technical guidance from the cloud service provider, including architecture, configuration of IaaS and PaaS, integration, troubleshooting assistance, and other services.
      total: 'Total Task Order Value:'
    oversight:
      section_title: Oversight
      ko_info_title: Contracting Officer (KO) Information
      ko_info_paragraph: Your KO will need to approve funding for this Task Order by logging into the JEDI Cloud Portal, submitting the Task Order documents within their official system of record, and then finally providing a digital signature. It might be helpful to work with your program's Financial Manager to get your TO documents moving.
      skip_ko_label: "Skip for now (We'll remind you to enter one later)"
      dod_id_tooltip: "The DoD ID is needed to verify the identity of the indicated officer or representative."
      cor_info_title: Contracting Officer Representative (COR) Information
      cor_info_paragraph: Your COR may assist in submitting the Task Order documents within their official system of record. They may also be invited to log in and manage the Task Order entry within the JEDI Cloud portal.
      so_info_title: Security Officer Information
      so_info_paragraph: Your Security Officer will need to answer some security configuration questions in order to generate a DD-254 document, then electronically sign.
    review:
      section_title: Review Your Task Order Info
      app_info: What are you building
      portfolio: Portfolio
      dod: DoD Component
      scope: Scope (Statement of Work)
      reporting: Reporting
      complexity: Project Complexity
      team: Development Team
      funding: Funding
      performance_period: Period of Performance
      usage_est_link: View Usage Estimate
      to_value: Task Order Value
      clin_1: 'CLIN #1: Unclassified Cloud'
      clin_2: 'CLIN #2: Classified Cloud'
      clin_3: 'CLIN #3: Unclassified Cloud'
      clin_4: 'CLIN #4: Classified Cloud'
      classified_inactive: (Available Soon)
      oversight: Oversight
      ko: Contracting Officer (KO)
      cor: Contracting Officer Representative (COR)
      so: IA Security Officer
      dod_id: 'DoD ID:'
      invited: Invited
      not_invited: Not Yet Invited
      not_uploaded: Not Uploaded
      pending_to: Pending TO Completion
  invitations:
    dod_id_label: DoD ID
    edit_text: A new invitation e-mail will be sent when new information is saved.
    resend_btn: Resend
    resend_confirmation_message: Are you sure you'd like to resend this invitation?
    contracting_officer:
      title: Contracting Officer (KO) Information
      description: You'll need a signature from your KO. You might want to work with your program Financial Manager to get your TO documents moving in the right direction.
      add_button_text: Add / Invite KO
      invite_button_text: Invite KO
      edit_title: Edit KO
    contracting_officer_representative:
      title: Contracting Officer Representative (COR) Information
      description: Your COR may assist in submitting the Task Order documents within their official system of record.
      add_button_text: Add / Invite COR
      invite_button_text: Invite COR
      edit_title: Edit COR
    security_officer:
      title: IA Security Officer Information
      description: Your Security Officer will need to answer some security configuration questions in order to generate a DD-254 document, then digitally sign.
      add_button_text: Add / Invite Security Officer
      invite_button_text: Invite Security Officer
      edit_title: Edit Security Officer
  ko_review:
    title: Verify Task Order Information
    message: Grant your team access to the cloud by verifying the Task Order info below.
    review_title: Task Order Builder
    task_order_information: Task Order Information
  so_review:
    title: DD-254 Information
    certification: Certification
portfolios:
  task_orders:
    available_budget_help_description: The available budget shown includes the available budget of all active task orders
  index:
    empty:
      title: You have no apps yet
      start_button: Start a New JEDI Portfolio
  applications:
    add_application_text: Add A New Application
    app_settings_text: App Settings
    team_text: Team
    csp_console_text: CSP Console
    existing_application_title: '{application_name} Application Settings'
    new_application_title: New Application
    settings_heading: Application Settings
    environments_heading: Environments
    environments_description: Each environment created within an application is logically separated from one another for easier management and security.
    update_button_text: Save Changes
    create_button_text: Create Application
    team_management:
      title: '{application_name} Team Management'
      subheading: Team Management
  admin:
    portfolio_members_title: Portfolio Members
    portfolio_members_subheading: These members have different levels of access to the portfolio.
    settings_info: Learn more about these settings
    activity_log_title: Activity Log
  members:
    permissions:
      name: Name
      app_mgmt: App Mgmt
      funding: Funding
      reporting: Reporting
      portfolio_mgmt: Portfolio Mgmt
testing:
  example_string: Hello World
  example_with_variables: 'Hello, {name}!'
  nested:
    example: Hello nested example