Attachment 2a-Initial TO PWS_Architecture (Revised).pdf

Performance Work Statement (PWS) in Support of the

Deputy Commandant Combat Development & Integration, Capabilities Development Directorate (CDD) for Initial Task Order 1

Operational Architecture Support

1. INTRODUCTION

The CDD supports DC CD&I by developing and integrating capability solutions and enabling an effective Marine

Corps capability to respond to strategic challenges and opportunities. CDD provides resident expertise for capability integration in the areas of: Command and Control, Cyber and Information Warfare, Fires and Maneuver, Force

Protection, Intelligence, Logistics, Corporate Management, and Force Integration. In consideration of overarching national strategic and service guidance and concepts development, the Directorate conducts analysis across the complete spectrum of Doctrine, Organizational, Training, Materiel, Leadership, Personnel, Facilities, and Policy, (DOTMLPF-P).

1.1. Operational Architecture Branch (OABr) is located within the Marine Corps Integration Division (MCID), CDD. The OABr develops engineered architecture views and comprehensive, authoritative data sets that support decision-making within Marine Corps Strategic Planning, Capabilities Planning, Resourcing, and

Solution Development processes. The OABr provides Operational Architecture Description development and validation across the Marine Corps Enterprise in support of the requirements outlined in Marine Corps

Order (MCO) 5230.20, Marine Corps Enterprise Architecture and described in the USMC Architecture

Development Guide (ADG).

1.2. The scope of this task order effort is to provide Department of Defense Architecture Framework (DoDAF)

Integrated Architecture Descriptions. Key support requirements include the development of capabilities-based Operational, Capability and Data and Information views within each Architecture Description, which model As-Is and To-Be (emergent) Marine Corps, Naval, and Joint concepts and capability solutions in support of Mission Engineering, the Joint Capabilities Integration and Development System

(JCIDS) , the Business Capability Acquisition Cycle (BCAC), and DOD information technology interoperability requirements.

1.3. The views that the OABr is responsible for include DoDAF All Views (AV) 1 and 2, Capability Views

(CV) 1 through 6, Operational Views (OV) 1 through 6, and Data and Information Views (DIV) 1 and 2.

In addition, an understanding of the DIV 3, Project Views (PV), Systems Views (SV), Services Views

(SvcV), and Standards Views (StdV) is required to sufficiently model the capability for system development.

2. SUPPORT REQUIREMENTS

This task order directly correlates to CLIN 0001 Technical Support, in the Indefinite Delivery, Indefinite Quantity

(IDIQ) contract; moreover, the following is a list of general requirements:

2.1. WORK LOCATION.

2.1.1. For UNCLASSIFIED-level topics the Contractor performance will primarily be at the company's off base facility(s).

2.1.2. For SECRET-level topics accessed on SECRET Internet Protocol Router Network (SIPRNET), the

Contractor performance will be at 3300 Russell Road (Davis Building) aboard Marine Corps Base

PWS for Initial Task 1 Operational Architecture Support

Quantico, Virginia.

2.1.3. To gain access to MCB, Quantico, registration in the Defense Biometric Identification System

(DBIDS) must be completed as well as possession of a valid form of identification. The DBID registration information and a list of valid forms of identification are found at https://www.quantico.marines.mil/Base-Access/

2.2. TRAVEL REQUIREMENTS. This requirement anticipates only local travel on an occasional basis. Local travel will not be reimbursed.

2.3. MEETING SUPPORT. The Contractor shall provide support for off-site meetings and working groups as necessary to facilitate task execution . Upon Government request, the Contractor, at its location, shall facilitate meetings and Interim Progress Review (IPRs) for 6-12 personnel.

2.4. PERFORMANCE MANAGEMENT. The Contractor shall provide the necessary resources and infrastructure to manage and administer this task order. The selection of teaming partners, subcontractors, facilities, and other business considerations is discretionary on the part of the Contractor, so long as they conform to the labor categories, pricing, and performance terms and conditions that bind the prime. The

Contractor shall establish processes and assign appropriate management and support resources to this task order and interface with CDD’s Contracting Officer’s Representative (COR). This shall include management of staffing actions, subcontractor management, finance, and Government interface with CDD and RCO-NCR staff. At all times, the prime Contractor shall be responsible for the actions of its teaming partners and subcontractors.

2.5. GOVERNMENT RESPONSIBILITIES AND INTERFACE. CDD's designated COR will have technical cognizance over the tasks listed herein. The COR will execute responsibilities related to quality compliance and performance oversight; deliverables acceptance; invoice certification; and coordination of follow-on work efforts. Only the contracting officer will interface with the prime Contractor's representative for payment and administrative issues.

2.6. TECHNICAL PERFORMANCE QUALITY. Site Lead for the contractor team can either be the Prime or a Subcontractor, however, technical cognizance over performance remains with the prime Contractor at all times. The prime Contractor is responsible for all assigned resources, performance quality (e.g., QASP compliance), and deliverables associated with each task order.

2.7. STAFF QUALIFICATIONS. The Contractor shall be responsible for staffing, competency training, guidance, and supervision of personnel performing any resulting task orders. The Contractor shall accomplish the assigned work by employing and utilizing qualified personnel possessing an appropriate combination of education, training, and experience required to respond to the criteria contained herein.

Staff initially assigned shall provide the benchmark for replacement staff qualifications and no dilution of such qualifications, or reduction in performance shall be incurred by the Government as a result of staff reassignment/departure.

2.8. SECURITY CLEARANCE REQUIREMENTS. Some of the work will require access to classified information at the SECRET level. All contractor personnel requiring access to classified information and assigned to this program shall possess a minimum secret clearance. The Prime Contractor and all Sub-contractors (through the Prime Contractor) shall certify in writing to the Government that those personnel supporting this contract are "Qualified United States (U.S.) Contractors" per Department of Defense

(DoD) Directive 5220.22-M Chapter 2 Section 2. Qualified U.S. Contractors are restricted to U.S. citizens, persons admitted lawfully into the United States for permanent residence and are located in the United

States. All personnel identified on the certification and/or supporting this contract shall be in compliance https://www.quantico.marines.mil/Base-Access/ with DoD, Department of the Navy (DON), and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. The contractor must ensure they, and all subcontractors used in the performance of this task order are vetted in the DD254. If new subcontractors are considered for the performance of this task order, the contractor shall ensure that any changes made to the approved DD254 are reviewed and concurred by the

Government.

The Government shall assist the Contractor in gaining access to Government agencies and installations related to the systems in question, as required. The Contractor shall take all necessary steps to assure that contractor and any subcontractor personnel performing under this contract are persons of professional and personal integrity and trust and meet all other requirements stipulated in this PWS. The Contractor shall ensure that the employees are on the approved Government access list prior to entering any access-controlled area. The Contractor shall notify the Government by written notice within twenty-four hours of

Contractor personnel are to be added or removed from the access control list.

The Contractor may be required to access and handle unclassified and classified (up to the Secret level) material at non-government facilities. Security management, inclusive of retention of clearances, are to be considered as part of the Contractor’s indirect base. The Government will not be responsible for getting subcontract companies cleared through any security measures. The Government will sponsor the

Contractor’s access to other Government facilities as required. On an as needed basis, the Government may also provide the Contractor access to Secured Internet Protocol Router Network (SIPRNet) at the

Government facility located at Raymond G. Davis Center, 3300 Russell Road, Quantico, VA 22134. The

Contractor shall safeguard all Government property and information provided in performance of this contract. Contractor employees shall be subject to all MCIA security procedures and any other applicable installation access and security regulations.

2.9. PHYSICAL RESOURCES. The Contractor shall have all necessary equipment, models, tools, software applications, infrastructure (e. g. wired or wireless telephone networks, laptops, etc.), and other resources necessary to execute performance of task orders. No additional charges will be made to the Government to purchase equipment, software, or other tools necessary to perform task orders following their award.

2.10. The use of the current OABr standard modeling software (currently CAMEO Enterprise Architecture) for development and submission of deliverables is mandatory. Contractor is responsible for obtaining software for contractor equipment used for developing unclassified architectural descriptions.

3. SPECIFIC REQUIREMENTS

3.1. General. The Contractor shall be responsible for employment, training, guidance, and supervision of qualified personnel performing under this PWS. The Contractor shall accomplish the assigned services by employing and utilizing qualified personnel possessing an appropriate combination of education, training, and experience to successfully produce the deliverables in this PWS. All personnel must possess the ability to read, write, speak, and understand English. All personnel must be able to travel to attend meetings and conferences, deliver briefings, facilitate discussions, and observe exercises as determined by the Government. All personnel must perform and maintain annual training requirements for computer network and security access, via the Marine Corps Enterprise Network (MCEN). This may include, but not limited to, Annual Cyber training and/or derivative classifier training.

3.2. Special Qualifications. The Contractor must collectively possess comprehensive knowledge of the DoD

Architecture Framework (DoDAF), DODAF Meta-Model, and Marine Corps policy and guidance governing architecture development and use. Knowledge and experience in data modeling is required. The

Contractor must possess knowledge of Marine Corps warfighting concepts, warfighting and business functions, and associated Navy, Joint, and Department of Defense (DOD) organization and capabilities development processes. Contractor personnel shall possess experience in and understanding of military operations and in conducting in-depth research, analysis, and documentation of analytical findings and conclusions. Experience in Joint and Combined operations; inter-agency operations; combat development or defense acquisition; and ability to write clearly and concisely are all value added to the mission.

3.3. The period of performance of this task order is 12 months from the contract award date with four 12-month option periods, not to exceed a total of 60 calendar months. The following deliverables are required to be executed within the period of performance. All deliverables should be provided to either the COR or the designated Government point of contact.

3.4. Number of Recurring Architectures per year

Operational Architecture Type Number of Recurring Architectures per year

Solution Architectural Descriptions 40

Mission Architectural Descriptions 16

Total 56

3.5. Delivery Format Requirements

Deliverable to Government PWS Deliverable Delivery Format

Intake Meeting ONE In-person meeting

Monthly Status Reports TWO MS Word/Excel/PowerPoint

Solution & Mission Architectural

Descriptions THREE CAMEO Enterprise Architecture

Mission Architecture Development FOUR Mission Architectural Descriptions

• 3.5.1 DELIVERABLE ONE. The contractor shall attend an Intake Meeting within ten (10) business days of task order contract award. The Intake Meeting will be organized and scheduled by the Government and will be held at the Government’s site. Government will provide appropriate Government Furnished

Information (GFI), e.g., SharePoint site URLs, Marine Corps Architecture Environment (MCAE), Architecture Development Guide (ADG), and Architecture business process references.

• 3.5.2 DELIVERABLE TWO. The contractor shall provide monthly status reports, due to the COR on the

10th day of the following month for work accomplished from the first (1st) through the final calendar day of the previous month. Contractor shall provide this report in electronic media compatible with conventional MS Office applications. The report shall include the following information, at a minimum:

o Comparison of planned and actual task order performance o Task progress during the past month, plans for the forthcoming month;

o Problems (actual or anticipated) requiring Government action and summary of action required;

o Travel costs, including purpose of trips, duration, and related actions, by task order, summary of trips taken (attach Trip Reports to the MTOPR for the reporting period);

o Total contract staffing by position and assignment;

o Personnel turnover, utilization of subcontractors, and future staffing projections;

o Deliverables (by task) accepted or rejected, inclusive of the final day of the month, as well as the reason for rejection and timeline for resubmission.

• 3.5.3 DELIVERABLE THREE. Solution Architecture Development o The Contractor shall develop and deliver Marine Corps Operational, Capability, Data and Information, and All Viewpoint models needed for assigned solution-level integrated Architectural Descriptions that support requirements documentation (JCIDS, BCAC, etc), Information Support Plan (ISP) documentation. Models will be developed in accordance with DoD, Joint, and Marine Corps policies and guidance pertaining to architecture development in support of solution requirements generation and acquisition. OABr-specified fit-for-purpose architecture models may also be required for some solutions.

o Prior to submission, the Contractor shall perform review of all models and related data for correctness and conformity to the current versions of the Marine Corps Architecture Development Guide (ADG).

The contractor shall develop approximately 40 integrated Architectural Descriptions annually, and participate in development reviews associated to 20-Step Architecture Development Process published in the ADG. The OABr anticipates 1 or 2 QA/QC reviews for each required review step.

• 3.5.4 DELIVERABLE FOUR: Mission Architecture Development o The Contractor shall develop Mission Architectural Descriptions in accordance with DoD and Marine

Corps policy and guidance pertaining to Mission Engineering and Mission Integration Management, in support of requirements generation and Planning, Programming, Budgeting and Execution (PPBE) decisions. The contractor shall develop approximately 14-16 Mission Architectural Descriptions, each describing operations of an Echelon V level organization (e.g., MEU, MLR) performing a mission within a specified Defense Planning Scenario.

o Prior to submission, the Contractor shall perform review of all models and related data for correctness and conformity to the current versions of the Marine Corps Architecture Development Guide (ADG).

The contractor shall develop approximately 40 integrated Architectural Descriptions annually, and participate in development reviews associated to 20-Step Architecture Development Process published in the ADG. The OABr anticipates 1 or 2 QA/QC reviews for each required review step.

4. TECHNICAL PERFORMANCE

Each of the cited task areas illustrate both conventional and unique attributes linked to objectives. The

Contractor shall support the execution of these requirements, ensuring an applied understanding of

Headquarters Marine Corps responsibilities and capabilities within JCA 1 (Force Integration) and JCA 8

(Corporate Management and Support); SharePoint 2013, SharePoint Online and Microsoft Power Platform; and knowledge and information management principles and methods. Core capabilities essential to performance include coordinating/communicating with stakeholders, scheduling and managing meetings and events, accurately capturing meeting records, managing information, and building SharePoint Online pages, lists, and libraries, and Power Platform workflows, forms, and dashboards. To successfully manage CDD information

(efficiently assess information, determine metadata assignment, and make other storage/organization decisions) the contractor will require basic knowledge of PPBE, JCIDS, Marine Corps Total Force Structure and Universal

Needs processes, as well as familiarity with warfighting functions and doctrine.

5. PERFORMANCE REQUIREMENTS SUMMARY (PRS)

Performance Characteristic Required Standard Measurement

Quality of Work Performed:

Provide acceptable or better results through the following:

• Technical accuracy, thoroughness of analysis / findings; and

• Completion and preparation to a professional standard

< 5% rejection rate of all formal deliverables submitted under the performance provisions of the contract; and

<10% rejection rate of draft and first time submissions.

- Reconciled weekly by MCID Leads;

- Reconciled monthly by COR /

Contractor's PM (CPM) and tracked as a

3-mos. moving average.

Responsiveness: Timely response to discrete work requirements emerging at the CDD Division levels, including:

• Timely delivery of deliverables;

• Attendance at required meetings

Initial Response to any requests provided to COR within 24-hrs., strategy provided to COR <48-hrs.

from notification, including:

- Delivery Schedule

- Project Timeline

- Deliverables; and

- Availability of staff.

- Periodic assessment by the COR, MCID

Leads as to the thoroughness of the response;

- Reconciled monthly by COR / CPM and tracked as a 3-mos. moving average.

Management and Administration:

Includes the following measures of performance and compliance:

• Deliverables shall be complete, accurate, and prepared to a professional standard;

• Quality of the Contractor’s overall technical management strategy;

• Ability to identify and preclude problems, or resolve issues; and

• Effectiveness of their use corporate quality practices, resolution of invoice anomalies, WBS compliance, and effectiveness of their overall subcontract management.

Aggregation of subordinated areas assessed using progressively more objective criteria – ratings considered:

Excellent – Exceeded performance expectations and abated, or immediately mitigated known problems;

Acceptable – Met performance expectations and generally responded to problems in a satisfactory manner; and

Unacceptable – Areas of inconsistent performance, prolific problems remain unresolved, and two or more performance areas are noted as substandard.

- Assessment by the COR, MCID Leads.

Performance evaluation at TBD milestones;

- Reconciled monthly by COR / CPM and tracked as a 3-mos. moving average.

WBS stability and forecast use of labor resources to meet quality standards without increasing current performance scope (e.g., change orders <1%)

Consequence of Non-compliance –

- Rejected Invoices/Delayed Payments

- Reduced likelihood of future task order awards under this contract

- Negative CPARs entry

- Contractor Consideration to the

Government.

Solution Architectural Descriptions:

- The content is factually correct, faithfully representing and supporting required information; views are data driven and present information in a way that supports the many stakeholders, processes, and uses of architecture. All architecture data elements and their relationships must be accurately reflected, including relationships to architecture data elements in other viewpoints.

- Required architecture artifacts include, at a minimum, the model and data requirements established by the current version of the United States

Marine Corps Architecture

Development Guide (ADG) and the relationships established by DoDAF.

These viewpoints are exportable to a format that can be entered into the

Service's Architecture Repository and also registered in MARS or Service equivalent; prepared in standard formats; content meets the required standards set forth in the current version of the United States Marine

Corps Architecture Development

Guide (ADG) and applicable reference materials to include the current version of the CJCSI 3170.0 l "Joint

Capabilities and Development

System," and any other future KPP guidance.

- The content conforms to current or emerging doctrine, concepts, capabilities, and development plans.

Views are developed from the same perspective(s), integrated across the entire architecture, and are based on traceable supporting data.

- The operational and capability

Architecture Descriptions answer the questions posed in the requirement.

The architecture is framed in the appropriate operational context. The data in the architecture model is to the required level of granularity to properly address the desired aspect, utilizing appropriate engineering principles, to be ultimately used for the purpose of analysis

100% accuracy of the content is determined accurate by the Capability

Integration Officer or CD&I appointed representative;

100% of the modeled elements, attributes, and relationships are DoDAF

Meta Model (DM2) compliant;

100% of Main Actions for each Step in the current version of the United States

Marine Corps Architecture

Development Guide (ADG) are accomplished;

100% of checklist items for each of the views are accomplished as outlined in the current version of the United States

Marine Corps Architecture

Development Guide (ADG);

100% of the data is traceable to throughout views (with attributes on data fields) and conforms to the current version of the United States

100% of the Key

Performance Parameters listed in the requirements document of the project being modeled are included in the architecture. This may be focused to a particular aspect if requested by the customer and approved by the Chief Operational

Architect;

90% of the architecture projects will meet the threshold and objective time requirements per step as defined in the current version of the United States

100% of the capabilities addressed in the JCIDS or

-Timely delivery of Monthly Reports

-Feedback from government stakeholders, surveys

-100% review of written architecture support products.

-Grammar error-free written documentation.

- Adheres to the timeline outlined in the current version of the United

States Marine Corps Integrated

Architecture Process and Viewpoint

Guide.

- Appropriate measure from the JCIDS or supported DBS document, Marine

Corps Task List (MCTL), Universal

Joint Task List (UJTL), or other appropriate authoritative source are modeled in the architecture that supports the capabilities identified in the JCIDS or supported DBS document and lead to capability based decisions.

supported DBS document and within the scope of the architecture are modeled with measures as attributes residing inside the data, that support capabilities-based decision making. All views are produced in accordance with the current version of the

Marine Corps Integrated

Architecture Process and

Viewpoint Guide.

Marine Corps Mission Threads

Development

- The content is factually correct, faithfully representing and supporting required information.

All views are produced in accordance with the Integrated Architecture

Process and Viewpoint Guide. All operational and other architectural views are produced to accepted

DoDAF 2.02 (current Version) standards.

- Required architecture artifacts include, at a minimum, the model and data requirements established by the current version of the United States

Marine Corps Architecture

Development Guide (ADG) or as directed by the Chief Operational

Architect, and the relationships established by DoDAF. These viewpoints are exportable to a format that can be entered into the Service's

Architecture Repository and also registered in MARS or Service equivalent; prepared in standard formats; content meets the required standards set forth in the current version of the United States Marine

Corps Architecture Development

Guide (ADG) and applicable reference materials to include the current version of the CJCSI 3170.01 "Joint

Capabilities and Development

System," and any other future KPP guidance.

100% accuracy of the content is determined accurate by the Capability

Integration Officer or CD&I appointed representative;

100% of the modeled elements, attributes, and · relationships are DoDAF

Meta Model (DM2) compliant;

100% of Main Actions for each Step in the current version of the United States

Marine Corps Architecture

Development Guide (ADG) are accomplished;

100% of checklist items for each of the views are accomplished as outlined in the current version of the

United States Marine Corps

Architecture Development

Guide (ADG) or as directed by the Chief Operational

Architect;

100% of the data is traceable to throughout views (with attributes on data fields) and conforms to the current version of the United States

Marine Corps Architecture

-Timely delivery of Monthly and

Quarterly Reports

-Feedback from government stakeholders, surveys

-100% review of written architecture support products.

-Grammar error-free written documentation.

- The content conforms to current or emerging doctrine, concepts, capabilities, and development plans.

Views are developed from the same perspective(s), integrated across the entire architecture, and are based on traceable supporting data.

- The operational and capability

Architecture Descriptions answer the questions posed in the requirement.

The architecture is framed in the appropriate operational context. The data in the architecture model is to the required level of granularity to properly address the desired aspect, utilizing appropriate engineering principles, to be ultimately used for the purpose of analysis.

- Adheres to the timeline outlined in the current version of the United

States Marine Corps Integrated

Architecture Process and Viewpoint

Guide or as directed by the Chief

Operational Architect.

- Appropriate measure as directed by the Chief Operational Architect, Marine Corps Task List (MCTL), Universal Joint Task List (UJTL), or other appropriate authoritative source are modeled in the architecture that supports the capabilities identified in the Mission Thread.