diff --git a/translations.yaml b/translations.yaml index 05a3afbc..f8b206eb 100644 --- a/translations.yaml +++ b/translations.yaml @@ -17,37 +17,23 @@ base_public: header_title: JEDI Cloud login: Log in title_tag: JEDI Cloud -flash: - new_portfolio_member: You have successfully invited {user_name} to the portfolio. - success: Success! - congrats: Congrats! - new_portfolio: You've created a new JEDI portfolio and jump-started your first task order! - portfolio_home: Go to my portfolio home page - next_steps: Review next steps below - deleted_member: Portfolio member deleted - delete_member_success: You have successfully deleted {member_name} from the portfolio. - new_ppoc_title: Primary point of contact updated - new_ppoc_message: You have successfully added {ppoc_name} as the primary point of contact. You are no longer the PPoC. - application: - deleted: You have successfully deleted the {application_name} application. To view the retained activity log, visit the portfolio administration page. common: - hide: Hide - show: Show back: Back cancel: Cancel confirm: Confirm + delete_confirm: 'Please type the word DELETE to confirm:' edit: Edit + hide: Hide manage: manage - cancel: Cancel - save: Save - 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 - delete_confirm: "Please type the word DELETE to confirm:" + security_officer: Security Officer + save: Save + save_and_continue: Save & continue + show: Show + sign: Sign components: modal: close: Close @@ -65,13 +51,32 @@ components: The https:// ensures that you are connecting to the official website and that any information you provide is encrypted and transmitted securely.

title: Here’s how you know +flash: + application: + deleted: 'You have successfully deleted the {application_name} application. To view the retained activity log, visit the portfolio administration page.' + congrats: Congrats! + delete_member_success: 'You have successfully deleted {member_name} from the portfolio.' + deleted_member: Portfolio member deleted + new_portfolio: You've created a new JEDI portfolio and jump-started your first task order! + new_portfolio_member: 'You have successfully invited {user_name} to the portfolio.' + new_ppoc_message: 'You have successfully added {ppoc_name} as the primary point of contact. You are no longer the PPoC.' + new_ppoc_title: Primary point of contact updated + next_steps: Review next steps below + portfolio_home: Go to my portfolio home page + success: Success! 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: + 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 assign_ppoc: - dod_id: "Select new primary point of contact:" + dod_id: 'Select new primary point of contact:' 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. This message will be shared with the person making the JEDI request.. comment_label: Instructions or comments @@ -82,16 +87,20 @@ forms: 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) #1 - custom_clauses_label: Task order custom clauses (optional) - custom_clauses_description: This will put a pause on the CSP access once the contracting officer signs until the CCPO reviews that language to make sure it is legal. + dd_254: + certifying_official: + description: '(Last, First, Middle Initial)' + label: Name of Certifying Official + certifying_official_address: + description: (Include ZIP Code) + label: Address + certifying_official_phone: + description: (Include Area Code) + label: Telephone + certifying_official_title: + label: Title + required_distribution: + label: Required Distribution by the Certifying Official edit_member: portfolio_role_label: Portfolio Role edit_user: @@ -151,19 +160,29 @@ forms: internal_comment: text_description: Add comments or notes for internal CCPO reference and follow-up here. These comments will not be visible to the person making the JEDI request. text_label: CCPO Internal Notes + ko_review: + custom_clauses_description: This will put a pause on the CSP access once the contracting officer signs until the CCPO reviews that language to make sure it is legal. + custom_clauses_label: Task order custom clauses (optional) + end_date_label: Period of performance end date + invalid_date: Must be a date in the future. + loa: 'Line of accounting (LOA) #1' + pdf_description: Upload a PDF of the task order that you entered in your system of record for your organization. + pdf_label: Upload a copy of your task order document + start_date_label: Period of performance start date + to_number: Task order number new_member: - dod_id_label: DoD ID - email_label: Email address - phone_number_label: Phone number (optional) - 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 access: Access Level app_mgmt: App management + dod_id_label: DoD ID + email_label: Email address + first_name_label: First name funding: Funding - reporting: Reporting + last_name_label: Last name + phone_number_label: Phone number (optional) portfolio_mgmt: Portfolio management + 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 + reporting: Reporting 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? @@ -200,120 +219,105 @@ forms: 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: - first_step_title: Basics - basic_intro: The first step of obtaining funding for cloud access is to provide more information about how you intend to use these funds. Before you can submit your task order, you’ll have to complete all sections, but while you’re working on it, you can skip around the form, once you’ve supplied the portfolio name and DoD component. - portfolio_name_label: 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: What do you plan to do on the cloud? Some examples might include migrating an existing application or creating a prototype. You don’t need to include a detailed plan of execution, but should list key requirements. This section will be reviewed by your contracting officer, but won’t be sent to the CCPO.

Not sure how to describe your scope? Read some examples to get some inspiration.

- 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 on-premise data center - cloud: Yes, migrating from another cloud provider - both: Yes, migrating from both an on-premise data center and another cloud provider - 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 (E.g. University or other partner)" - 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 contracting officer 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: | - 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. - 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 contracting officer to Task Order Builder contracting_officer_representative_invite: Invite COR to Task Order Builder security_officer_invite: Invite Security Officer to Task Order Builder + portfolio: + name_label: Portfolio name + name_length_validation_message: Portfolio names can be between 4-100 characters + task_order: + app_migration: + both: 'Yes, migrating from both an on-premise data center and another cloud provider' + cloud: 'Yes, migrating from another cloud provider' + description: Do you plan to migrate one or more existing application(s) to the cloud? + label: App migration + none: Not planning to migrate any applications + not_sure: Not sure + on_premise: 'Yes, migrating from an on-premise data center' + basic_intro: 'The first step of obtaining funding for cloud access is to provide more information about how you intend to use these funds. Before you can submit your task order, you’ll have to complete all sections, but while you’re working on it, you can skip around the form, once you’ve supplied the portfolio name and DoD component.' + clin_01_label: 'CLIN 01 : Unclassified' + clin_02_label: 'CLIN 02: Classified' + clin_03_label: 'CLIN 03: Unclassified' + clin_04_label: 'CLIN 04: Classified' + complexity: + conus: CONUS access + data_analytics: Data analytics + description: Which of these describes how complex your team's use of the cloud will be? Select all that apply. + label: Project complexity + not_sure: Not sure + oconus: OCONUS access + other: Other + storage: Storage + tactical_edge: Tactical edge access + complexity_other_label: Project Complexity Other + cor_invite_label: Invite COR to Task Order Builder + csp_estimate_description: Upload a PDF or screenshot of your usage estimate from the calculator. + csp_estimate_label: Upload a copy of your CSP cost estimate research + defense_component_label: Department of Defense component + dev_team: + civilians: Government civilians + contractor: Contractor + description: Who will be completing the development work for your cloud application(s)? Select all that apply. + label: Development team + military: Military + other: Other (E.g. University or other partner) + dev_team_other_label: Development Team Other + end_date_label: End Date + file_format_not_allowed: Only PDF or PNG files can be uploaded. + first_step_title: Basics + ko_invite_label: Invite contracting officer to Task Order Builder + native_apps: + description: Do you plan to develop any applications natively in the cloud? + label: Native apps + 'no': 'No, not planning to develop natively in the cloud' + not_sure: 'Not sure, unsure if planning to develop natively in the cloud' + 'yes': 'Yes, planning to develop natively in the cloud' + oversight_am_cor_label: I am the Contracting Officer Representative (COR) for this task order + oversight_dod_id_label: DoD ID + oversight_email_label: Email + oversight_first_name_label: First Name + oversight_last_name_label: Last Name + oversight_phone_label: Phone Number + performance_length: + label: Period of performance length + 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. + portfolio_name_label: Portfolio name + scope_description: 'What do you plan to do on the cloud? Some examples might include migrating an existing application or creating a prototype. You don’t need to include a detailed plan of execution, but should list key requirements. This section will be reviewed by your contracting officer, but won’t be sent to the CCPO.

Not sure how to describe your scope? Read some examples to get some inspiration.

' + scope_label: Cloud project scope + skip_invite_description: | + 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. + so_invite_label: Invite Security Officer to Task Order Builder + start_date_label: Start Date + team_experience: + 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' + description: How much experience does your team have with development in the cloud? + label: Team experience + none: No previous experience + planned: Researched or planned a cloud build or migration + unclassified_clin_02_label: 'CLIN 02: Classified (available soon)' + unclassified_clin_04_label: 'CLIN 04: Classified (available soon)' + validators: + is_number_message: Please enter a valid number. + is_required: This field is required. + 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. 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.' + 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?
Information Assurance (IA) training is an important step in cyber awareness. save_details_button: Save Details + ko_review_message: + 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 + title: Steps 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. @@ -325,25 +329,20 @@ fragments: 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, 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 (PPoC) - subtitle: The PPoC has the ability to edit all aspects of a portfolio and is the only one who can manage the PPoC role. - update_btn: Update + alert: + message: Selecting a new PPoC gives that member full access to the portfolio and removes your ability to manage the PPoC role. The rest of your permissions will remain untouched. Please be sure you want to proceed. + title: Warning! assign_user_button_text: Assign Member + confirm_alert: + title: 'Once you assign a new PPoC, you will no longer be able to request portfolio deactivation or manage the PPoC role.' + subtitle: The PPoC has the ability to edit all aspects of a portfolio and is the only one who can manage the PPoC role. + title: Primary point of contact (PPoC) + update_btn: Update update_ppoc_confirmation_title: Confirmation update_ppoc_title: Update primary point of contact - confirm_alert: - title: Once you assign a new PPoC, you will no longer be able to request portfolio deactivation or manage the PPoC role. - alert: - title: Warning! - message: Selecting a new PPoC gives that member full access to the portfolio and removes your ability to manage the PPoC role. The rest of your permissions will remain untouched. Please be sure you want to proceed. login: ccpo_logo_alt_text: Cloud Computing Program Office Logo certificate_selection: @@ -354,6 +353,20 @@ login: login_button: Sign in with CAC title_tag: Sign in | JEDI cloud navigation: + portfolio_navigation: + activity_log: Activity log + add_new_application_label: Add new application + add_new_member_label: Add new member + applications: Applications + breadcrumbs: + admin: Admin + funding: Funding + reports: Reports + budget_report: Budget Report + members: Members + portfolio_admin: Portfolio Administration + portfolio_funding: Funding + portfolio_settings: Portfolio Settings topbar: jedi_cloud_link_text: JEDI logout_link_title: Log out of JEDI cloud @@ -361,20 +374,78 @@ navigation: 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 +portfolios: + admin: + activity_log_title: Activity log + add_member: Add a new member + add_new_member: Add a new member + alert_header: Are you sure you want to delete this member? + alert_message: 'The member will be removed from the portfolio, but their log history will be retained.' + alert_title: Warning! You are about to delete a member from the portfolio. + no_members: There are currently no members in this portfolio. + permissions_info: Learn more about these permissions + portfolio_members_subheading: These members have different levels of access to the portfolio. + portfolio_members_title: Portfolio members + settings_info: Learn more about these settings + applications: + add_application_text: Add a new application + add_environment: Add new environment + app_settings_text: App settings + create_button_text: Create + csp_console_text: CSP console + delete: + alert: + message: You will lose access to this application and all of its reporting and metrics tools. The activity log will be retained. + title: Warning! This action is permanent. + button: Delete application + header: Are you sure you want to delete this application? + environments: + members: Members + name: Name + environments_description: Each environment created within an application is logically separated from one another for easier management and security. + environments_heading: Application environments + existing_application_title: '{application_name} Application Settings' + new_application_title: New Application + settings_heading: Application Settings + team_management: + subheading: Team Management + title: '{application_name} Team Management' + team_settings: + blank_slate: + action_label: Invite a new team member + sub_message: Please contact your JEDI Cloud portfolio administrator to invite new members. + title: There are currently no team members for this application. + environments: Environments + section: + members_count: 'Members ({members_count})' + table: + delete_access: Delete Access + environment_management: Environment Management + environments: Environments + name: Name + team_management: Team Management + title: '{application_name} Team' + subheading: Team Settings + title: '{application_name} Team Settings' + user: User + team_text: Team + update_button_text: Save + index: + empty: + start_button: Start a new JEDI portfolio + title: You have no apps yet + members: + archive_button: Delete member + permissions: + app_mgmt: App management + edit_access: Edit access funding: Funding - reports: Reports + name: Name + portfolio_mgmt: Portfolio management + reporting: Reporting + view_only: View only + task_orders: + available_budget_help_description: The available budget shown includes the available budget of all active task orders requests: _new: new_request: New Request @@ -425,10 +496,10 @@ requests: 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. + no_requests_found: No requests found. pending_ccpo_action: Pending CCPO Action request_submitted_title: Request submitted! requests_in_progress: Requests in progress @@ -466,8 +537,107 @@ requests: task_orders: form: draft_alert_title: Your draft has been saved + invitations: + contracting_officer: + add_button_text: Add / Invite contracting officer + description: You'll need a signature from your contracting officer. You might want to work with your program Financial Manager to get your TO documents moving in the right direction. + edit_title: Edit KO + invite_button_text: Invite KO + title: Contracting officer information + contracting_officer_representative: + add_button_text: Add / Invite COR + description: Your COR may assist in submitting the task order documents within their official system of record. + edit_title: Edit COR + invite_button_text: Invite COR + title: Contracting officer representative (COR) information + dod_id_label: DoD ID + edit_text: A new invitation email will be sent when new information is saved. + resend_btn: Resend + resend_confirmation_message: Are you sure you'd like to resend this invitation? + security_officer: + add_button_text: Add / Invite Security Officer + description: 'Your security officer will need to answer some security configuration questions in order to generate a DD-254 document, then digitally sign.' + edit_title: Edit security officer + invite_button_text: Invite security officer + title: Security officer information + ko_review: + 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 + title: Verify task order information + new: + app_info: + basic_info_title: Basic information + details_description: 'Provide a few more details about the work you will be doing. The CCPO will use this section for reporting purposes, but it won’t be included in the final task order.' + 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.
View JEDI market research memo' + market_research_title: Market research + project_title: Project details + sample_scope: | + Not sure how to describe your scope? Read some examples to get some inspiration. + section_title: Basics + team_title: Your team + funding: + cloud_calculations_paragraph: Enter the results of your cloud usage calculations below. + cloud_calculations_title: Cloud usage calculations + cloud_offerings_paragraph: Infrastructure as a Service (IaaS) and Platform as a Service (PaaS) offerings + cloud_offerings_title: Cloud offerings + 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.' + estimate_usage_title: Estimate your cloud usage + 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.' + performance_period_title: Period of performance + section_title: Funding + support_assistance_paragraph: 'Technical guidance from the cloud service provider, including architecture, configuration of IaaS and PaaS, integration, troubleshooting assistance, and other services.' + support_assistance_title: Cloud support and assistance + total: 'Total task order value:' + get_started: + button: Create a portfolio + intro: 'Your portfolio is where you can organize all your JEDI cloud applications, funding information, and reporting in one place. It’s also where you can begin the process of securing funds for your new cloud project.' + intro2: 'To get started, you’ll need to prepare your first task order, which you’ll then submit separately through your organization’s system of record. There are some important steps you’ll need to complete for any task order, including:' + intro3: 'It should only take about half an hour to complete the task order process from start to finish. Need to know more? You’ll be able to get help at each step along the way. If you’re unable to complete your task order in one session, your work will be saved, and you can continue when you’re ready.' + intro4: 'Not looking to create a whole new portfolio? If you’d like to add a new task order to an existing portfolio, select that portfolio from the list at the left and follow the instructions.' + team_header: 'Before you begin, you’ll need to assemble your team' + title: Let's get started + oversight: + 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. + cor_info_title: Contracting officer representative (COR) information + dod_id_tooltip: The DoD ID is needed to verify the identity of the indicated officer or representative. + ko_info_paragraph: 'Your contracting officer 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.' + ko_info_title: Contracting officer information + section_title: Oversight + skip_ko_label: Skip for now (We'll remind you to enter one later) + 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.' + so_info_title: Security officer information + review: + app_info: Basics + classified_inactive: (Available Soon) + clin_1: 'CLIN #1: Unclassified Cloud' + clin_2: 'CLIN #2: Classified Cloud' + clin_3: 'CLIN #3: Unclassified Cloud' + clin_4: 'CLIN #4: Classified Cloud' + complexity: Project complexity + cor: Contracting Officer Representative (COR) + dod: DoD component + dod_id: 'DoD ID:' + funding: Funding + invited: Invited + ko: Contracting Officer + not_invited: Not yet invited + not_uploaded: Not uploaded + oversight: Oversight + pending_to: Pending TO completion + performance_period: Period of performance + portfolio: Portfolio + reporting: Reporting + scope: Scope (statement of work) + section_title: Review Your Task Order + so: Security Officer + team: Development team + to_value: Task order value + usage_est_link: View usage estimate 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 Federal Acquisition Regulation (FAR). + 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 Federal Acquisition Regulation (FAR).' 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 @@ -475,188 +645,17 @@ task_orders: 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. + so_review: + certification: Certification + title: DD-254 Information view: - whats_next: Here are the remaining steps to get your task order approved. steps: draft: 'Primary Point of Contact ({contact}) completes initial task order form.' - security: 'Security Officer ({security_officer}) completes a Security Requirements Document. Send a reminder' record: 'Contracting Officer ({contracting_officer}) or Contracting Officer Representative ({contracting_officer_representative}) records task order information. Send a reminder' - 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. + 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.' + security: 'Security Officer ({security_officer}) completes a Security Requirements Document. Send a reminder' sign: 'Contracting Officer ({contracting_officer}) verifies funding to unlock cloud services.' - new: - get_started: - title: Let's get started - intro: Your portfolio is where you can organize all your JEDI cloud applications, funding information, and reporting in one place. It’s also where you can begin the process of securing funds for your new cloud project. - intro2: "To get started, you’ll need to prepare your first task order, which you’ll then submit separately through your organization’s system of record. There are some important steps you’ll need to complete for any task order, including:" - intro3: It should only take about half an hour to complete the task order process from start to finish. Need to know more? You’ll be able to get help at each step along the way. If you’re unable to complete your task order in one session, your work will be saved, and you can continue when you’re ready. - intro4: Not looking to create a whole new portfolio? If you’d like to add a new task order to an existing portfolio, select that portfolio from the list at the left and follow the instructions. - team_header: Before you begin, you’ll need to assemble your team - button: Create a portfolio - app_info: - section_title: "Basics" - basic_info_title: Basic information - sample_scope: | - Not sure how to describe your scope? Read some examples to get some inspiration. - project_title: Project details - details_description: Provide a few more details about the work you will be doing. The CCPO will use this section for reporting purposes, but it won’t be included in the final task order. - team_title: 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.
View JEDI market research memo' - 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 information - ko_info_paragraph: Your contracting officer 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 - app_info: Basics - 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 - cor: Contracting Officer Representative (COR) - so: 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 email 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 information - description: You'll need a signature from your contracting officer. 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 contracting officer - 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: 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: Application environments - environments_description: Each environment created within an application is logically separated from one another for easier management and security. - update_button_text: Save - create_button_text: Create - team_settings: - title: '{application_name} Team Settings' - subheading: Team Settings - user: User - environments: Environments - blank_slate: - action_label: Invite a new team member - sub_message: Please contact your JEDI Cloud portfolio administrator to invite new members. - title: There are currently no team members for this application. - section: - title: '{application_name} Team' - members_count: 'Members ({members_count})' - table: - delete_access: Delete Access - environment_management: Environment Management - environments: Environments - name: Name - team_management: Team Management - team_management: - title: '{application_name} Team Management' - subheading: Team Management - environments: - name: Name - members: Members - delete: - button: Delete application - header: Are you sure you want to delete this application? - alert: - title: Warning! This action is permanent. - message: You will lose access to this application and all of its reporting and metrics tools. The activity log will be retained. - add_environment: Add new environment - 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 - add_member: Add a new member - permissions_info: Learn more about these permissions - activity_log_title: Activity log - add_new_member: Add a new member - alert_header: Are you sure you want to delete this member? - alert_title: Warning! You are about to delete a member from the portfolio. - alert_message: The member will be removed from the portfolio, but their log history will be retained. - no_members: There are currently no members in this portfolio. - members: - archive_button: Delete member - permissions: - name: Name - app_mgmt: App management - funding: Funding - reporting: Reporting - portfolio_mgmt: Portfolio management - view_only: View only - edit_access: Edit access + whats_next: Here are the remaining steps to get your task order approved. testing: example_string: Hello World example_with_variables: 'Hello, {name}!'