HC1047-14-R-4021.doc

Section B - Supplies or Services and Prices

Task 1 - Contract Management

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 - Contract Management in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

*** THIS CLIN SHALL BE BILLED / PAID MONTHLY IN ARREARS ***

FOB: Destination

NET AMT

Task 2 - Systems Engineering Support

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 - Systems Engineering Support in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

NET AMT

Cost

Travel

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014. Travel shall be in accordance with FAR Subpart 31.205-46.

Base Year Period of Performance (TBD, 2014 -- TBD, 2015)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 - Contract Management in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 1 Period of Performance (TBD, 2015 -- TBD, 2016)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 - Systems Engineering Support in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 1 Period of Performance (TBD, 2015 -- TBD, 2016)

NET AMT

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year 1 Period of Performance (TBD, 2015 -- TBD, 2016)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 - Contract Management in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 2 Period of Performance (TBD, 2016 -- TBD, 2017)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 - Systems Engineering Support in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 2 Period of Performance (TBD, 2016 -- TBD, 2017)

NET AMT

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year 2 Period of Performance (TBD, 2016 -- TBD, 2017)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 - Contract Management in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 3 Period of Performance (TBD, 2017 -- TBD, 2018)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 - Systems Engineering Support in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 3 Period of Performance (TBD, 2017 -- TBD, 2018)

NET AMT

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year 3 Period of Performance (TBD, 2017 -- TBD, 2018)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 - Contract Management in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 4 Period of Performance (TBD, 2018 -- TBD, 2019)

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 - Systems Engineering Support in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Option Year 4 Period of Performance (TBD, 2018 -- TBD, 2019)

NET AMT

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014. Travel shall be in accordance with FAR Subpart 31.205-46.

Option Year 4 Period of Performance (TBD, 2018 -- TBD, 2019)

ESTIMATED COST

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 1 - Contract Management in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Period of Performance (TBD, 2019 -- TBD, 2020)

This optional 6 month extension of services is pre-priced in accordance with FAR 52.217-8.

NET AMT

FFP

The Contractor shall provide firm fixed-price labor to complete the requirements of Task 2 - Systems Engineering Support in accordance with the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014 and the Contractor's proposal dated TBD.

Period of Performance (TBD, 2019 -- TBD, 2020)

This optional 6 month extension of services is pre-priced in accordance with FAR 52.217-8.

NET AMT

Cost

COST

Travel Costs. All Travel must be pre-approved by the COR identified in clause 52.204-9000 prior to the Contractor incurring the cost in support of the Performance Work Statement entitled, "Joint Command and Control (C2) Architecture Support" dated 21 February 2014. Travel shall be in accordance with FAR Subpart 31.205-46.

Period of Performance (TBD, 2019 -- TBD, 2020)

This optional 6 month extension of services is pre-priced in accordance with FAR 52.217-8.

ESTIMATED COST

Section C - Descriptions and Specifications

SECTION C

PERFORMANCE WORK STATEMENT (PWS)

21 February 2014

Contract Number:

Task Order Number:

1. Contracting Officer Representative (COR).

a. Primary COR.

Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone Number:

E-Mail Address:

b. Alternate COR.

Organization:

DODAAC:

Address:

Phone Number:

E-Mail Address:

2. Contract Title. Joint Command and Control (C2) Architecture Support

3. Background. The Joint C2 will be a federated set of C2 programs that will form a joint system that allows seamless integration of information for the Chairman, Joint Chiefs of Staff (CJCS), the Combatant Commanders (COCOMs), and the Military Services providing joint and multinational operations into the 21st century. The system supports the President, Vice President, Secretary of Defense, CJCS, COCOMs, and Services by providing synchronized operations from dispersed locations and provides joint Command, Control, Communications, Computers, and Intelligence (C4I) to support the entire force projection cycle. It provides responsive command and control, the capability to assess the level of success, and retain flexibility to re-engage with precision by allowing the Joint Task Force (JTF) commander the ability to maintain dominant battlefield awareness through a fused, integrated, near real-time picture of the battle space.

4. Objectives: The objective of this contract is to provide support to the Program Executive Office for Command and Control Capabilities (PEO-C2C) in the accomplishment of Joint C2 Architecture development activities. Specifically, this includes support for Joint C2 standards, Joint C2 architecture compliance assessment, multi-party engineering activities, and Joint C2 architecture repository and analysis.

5. Scope. The scope of this contract is to support the systems engineering activities associated with the Joint C2 Architecture. This effort will support the Office of the Technical Director within PEO-C2C. This contract provides systems engineering support focused on the Joint C2 Family of Programs (FoP) transition and compliance with the Joint C2 Architecture.

6 Performance Requirements.

6.1 Contract Management. (O&M)

6.1.1 Contract Management. The contractor shall perform contract management activities to include planning, controlling, and implementing the requirements as defined in this Performance Work Statement (PWS). The contractor shall perform the planning activities associated with the project to include approach, project schedule, milestones, required reviews and list of deliverables. The contractor shall perform risk management activities to include risk identification and a description of any activities that may reduce or eliminate risk. The contractor shall document the approach to executing the Joint C2 Architecture Support requirements in a Contract Management Plan. The plan shall include specific methods and procedures (technical and managerial) that will be employed over the course of this contract.

Deliverable: Contract Management Plan

6.1.2 Monthly Status Reporting. The contractor shall provide a monthly status report to include cost, schedule and technical accomplishments. The contractor shall provide a monthly financial summary including travel costs. Schedule information shall include planned deliverables, planned technical reviews/meetings, and planned travel. The contractor shall document the technical accomplishments for each task to include identified risk and recommended risk mitigation.

Deliverable: Monthly Status Report

6.1.3 Meeting Support. The contractor shall provide support needed for meetings in support of task activities such as scheduling, documenting meeting minutes, and setting up conference lines. The contractor shall support virtual meeting attendance via Defense Connect Online (DCO) for various working groups to include: Joint C2 Plan Build Workshop, Joint C2 Architecture Core Team (ACT), Joint C2 Program Manager, Chief Engineer Steering Group (PMCESG) and PEO-C2C Technical Director staff meetings. The contractor shall provide audio teleconference capability to support weekly Technical Director Staff meetings and weekly Architecture Core Team meetings. The contractor shall attend eight (8) meetings per month.

Deliverable: Meeting Minutes

6.2 Systems Engineering Support. (O&M)

6.2.1 Joint C2 Standards Support. The contractor shall provide technical support for enhancements to the Joint C2 Reference Architecture Technical Positions in accordance with the Department of Defense (DoD) Information Technology Standards Registry (DISR). The contractor shall identify those mandated, emerging, and critical standards in order to facilitate interoperability across Joint C2 capabilities. The contractor shall update the online Joint C2 Standards Profile on the GTG-Federation Portal based on the Joint C2 Reference Architecture & DISR releases. Estimate three (3) releases per year. The contractor shall support meeting attendance via Defense Connect Online (DCO) and provide technical standards support to the Joint C2 Architecture Core Team (ACT). The contractor shall develop technical standard change requests to DISR on behalf of the C2 community and monitor the status of the change request throughout the DISR review process. The contractor can plan to develop two (2) technical standard change requests per year.

Deliverables: Technical Report - Joint C2 Standards Profile/Technical Positions

6.2.2 Joint C2 Architecture Compliance Assessment Support. The contractor shall lead and provide engineering support for Joint C2 architecture compliance assessments. The contractor shall assist the Joint C2 community programs in their annual assessment of compliance with the Joint C2 Reference Architecture and the DoD Information Enterprise Architecture (DIEA) to include the principles, rules and technical positions. The contractor shall attend Joint C2 Plan Build Workshop(s) and Joint C2 program preliminary and critical design reviews. The contractor shall review technical design documentation and program artifacts such as architecture self assessments and Department of Defense Architecture Framework (DoDAF) views. The contractor shall prepare technical report(s) documenting the status and progress of the Joint C2 community as a whole toward architecture compliance. In this report the contractor shall provide analysis of trends, identification of potential areas of concern and recommendations for the Joint C2 portfolio. The contractor shall plan to provide detailed direct support to seven (7) Joint C2 Programs/Projects and provide occasional consultation (infrequent technical guidance related to the self assessment assertions and process) to up to twenty (20) others. Compliance assessment activities shall be closely coordinated with the activities supported in subtask 6.2.3, Joint C2 Architecture Repository and Analysis. The contractor shall brief the results of the Joint C2 Architecture Compliance Assessment including the Fit for Purpose DoDAF views developed under Task 6.2.3 to the Joint C2 Architecture Core Team (ACT).

Deliverables: Briefing Materials – Joint C2 Community Architecture Compliance Assessment

6.2.3 Joint C2 Architecture Repository and Analysis. The contractor shall develop and maintain a Joint C2 Architecture Repository on Intelink which will document the evolution of Joint C2 capabilities implemented by the Joint C2 Family of Programs. The Architecture Artifacts Repository will contain community provided DoDAF models in addition to links to Joint C2 architecture models from documents such as the Joint C2 Capability Development Document, Joint C2 Capability Definition Packages/Capability Packages, and Joint C2 Capability Modules. All tier 1 and 2 systems of the Joint C2 community that provide documentation must be included in this task. The purpose of the Joint C2 Architecture Repository is to provide a comprehensive shared view of the Joint C2 community portfolio architecture. The contractor shall analyze current and proposed architectures and develop Systems Modeling Language (SySML) compliant selected Fit for Purpose (FFP) DODAF 2.0 views and associated Data Management (DM2) elements, including high-level services & interface dependency views (e.g., SvcV-1 & SvcV-3 ) representing the Joint C2 portfolio.

Deliverables: Joint C2 Architecture Repository – Intelink

Briefing Materials, Fit For Purpose DoDAF Models

6.2.4 Joint C2 Multi-Party Engineering Activities. The contractor shall provide engineering expertise to define and support a Joint C2 Multi-Party Engineering process. The Joint C2 Multi-Party engineering effort shall analyze high priority Joint C2 focus areas. The contractor shall conduct an architectural analysis to include: dependency analysis, identification of risk, and potential gaps or duplications. The contractor shall provide recommendations for the refinement of community multi-party engineering processes and solution architectures (i.e. software, data, and information assurance). Recommendations for the refinement of information assurance architectures must be in compliance with the DoD Information Assurance Certification and Accreditation Process (DIACAP). The contractor shall participate in a joint engineering team consisting of both Government and contractor representatives. As team members, the contractor shall analyze alternatives and produce a recommended design and implementation approach with associated DoDAF SvcV-1 and SvcV-3 artifacts for each Joint C2 focus area. The solution implementation guidance will include rules and technical positions that are required in accordance with the Joint C2 Reference Architecture. The contractor shall plan to support multi-party engineering activities for three (3) high priority Joint C2 focus area.

Deliverables: Technical Report - Solution Implementation Guidance

6.2.5 Joint C2 Architecture Development Support. The contractor shall provide engineering support for Joint C2 Architecture development. This includes setting up and customizing collaborative tools (i.e. Intelink/SharePoint, DoDAF tools) for developing requirements and artifacts associated with the Joint C2 Architecture. The contractor shall maintain the Architecture Core Team (ACT) site on Intelink SharePoint and manage the DISA DEPS Technical Director’s site. The contractor shall maintain the Joint C2 Compliance and Interoperability Assessment site on Intelink/SharePoint. The Joint C2 Compliance and Interoperability Assessment site shall provide the capability & tools to support the Joint C2 community program architecture self assessment in accordance with the Joint C2 Reference Architecture and approved Joint C2 Solution Implementation Guidance.

Deliverables: Technical Report – Joint C2 Architecture Development Support

7. Performance Standards.

8. Incentives. The Government will positively and/or negatively review the contractor’s performance based on the success or failure in meeting quality assurance surveillance plan objectives. The contractor is incentivized to earn favorable Government reviews to support continuation of JC2 requirements and support contract awards with other Government agencies seeking DISA’s input on the contractor’s past performance and the Contract Performance Assessment Reporting System (CPARS). Failure to meet the acceptable quality levels may result in an unsatisfactory past performance report by the Government.

9. Place of Performance. Work will be performed at the contractor’s site. Local travel between the contractor facility and DISA Ft. Meade is required. The number of local trips is two (2) trips per month. Long distance travel will be required and is described below:

Washington, DC

Suffolk, VA

Specific travel requirements shall be coordinated with the Contracting Officer’s Representative (COR) and shall be in accordance with Federal Acquisition Regulation (FAR) 31.205-46 requirements and limitations. Reimbursement for travel expenses shall be made in accordance with the Federal Travel Regulations. Local travel will be reimbursed.

10. Period of Performance. The period of performance is for a base period of 365 calendar days after contract award with four (4) 12-month option periods, to be exercised at the discretion of the Government. If required and in coordination by the COR, the contractor shall continue performance in emergency or mission essential conditions.

11. Delivery Schedule.

Final – 30 Days after award

30 Days after Government request - Final

FINAL - 30 Days after Government request

* Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer and contracting specialist.

1 copy of the transmittal letter with the deliverable to the Primary COR.

12.0 Security. Work under this PWS will be at the Secret level.

12.1 Security Requirements.

The security classification guidance needed for this classified effort is identified below. If any difficulty is encountered in applying this guidance or if any other contributing factor indicates a need for changes in this guidance, the contractor is authorized and encouraged to provide recommended changes to challenge the guidance or the classification assigned to any information or material furnished or generated under this contract; and to submit any questions for interpretation of this guidance to the official identified below. Pending final decision, the information involved shall be handled and protected at the highest level of classification assigned or recommended.

12.2 Facility Security Clearance.

The work to be performed under this contract is Secret. The contractor must have a final Secret Facility Clearance (FCL) from the Defense Industrial Security Clearance Office (DISCO).

12.3 Security Clearance and Information Technology (IT) Level.

All personnel performing on this contract will be U.S. citizens with level IT-I.

12.4 Investigation Requirements.

All personnel requiring Secret eligibility under this task order must undergo a favorably adjudicated Single Scope Background Investigation (SSBI) as a minimum investigation. The SSBI will be maintained current within 10-years and requests for Special Background Periodic Review (SBPR) will be initiated 6-months prior to the 10-year anniversary date of the previous SSBI or SBPR.

12.4.1 Contract employees that are not immediately eligible for at least interim IT-I systems access will be permitted to begin work with interim IT-II systems access at the discretion of the Government, pending eligibility for IT-I. Before being permitted to begin work under this arrangement, the individual contractor employee must be submitted by the company for an SSBI (investigation) that is reflected in the DoD JPAS database and granted interim IT-II systems access approval by DISA Personnel Security. The employee will not be granted any privileged access until interim or final IT-I systems access is granted by DISA Personnel Security. The contract company must submit the request for SSBI as soon as a job offer is tendered to an employee. Advance NAC results will be requested by the contract company to facilitate expeditious consideration for interim IT-I systems access by DISA Security. Advance NAC results or a previous DoD investigation are required for interim IT-I consideration. If the employee is not able to obtain an interim IT-I clearance within 90 days they will not be eligible for continued employment with the agency.

12.5 Adjudication for IT Access.

Adjudication of investigations for granting of interim or final IT-I access will be accomplished through DISA Security. An exception to this is that individual contractor employees with an SSBI or SBPR (within a 5-year scope) that is favorably adjudicated for a Secret security clearance by any of the Department of Defense adjudication facilities (DISCO, DIA, ACCF, AFCAF, NAVCAF, WHSCAF) will be automatically accepted for final IT-I access.

12.5.1 Interim IT Access.

Pending completion of a SSBI (for IT-I) and final adjudication for security clearance, contractor employees may be granted interim authorization to perform duties designated as IT-I. The interim authority for IT sensitive positions is the DISA Personnel Security Office.

12.5.2 Following are the requirements, which must be met prior to granting of interim IT-I authorization:

· The request for SSBI (E-QIP or Word Fillable SF 86 and fingerprint cards) must be submitted by the contractor Facility Security Officer (FSO) through the Defense Security Service (DSS) to the Office of Personnel Management (OPM) and the Department of Defense (DoD) Personnel Security Data Base (JPAS) must reflect that the investigation is open. A copy of the E-QIP or SF 86 forms must be submitted to the DISA Field Security Office, Security Manager (SM). The SM will forward the forms along with a written request for interim IT-I authorization to DISA Personnel Security for approval.

· The National Agency Check (NAC) portion of the SSBI or a previous valid NCLC/DNACI/NAC or ENTNAC must be completed and favorably adjudicated before interim IT-I access will be granted. An interim security clearance of Secret should be requested by the company FSO for those contractor employees without a previous investigation.

12.6 Visit Authorization Letters.

The Contractor will forward a Visit Authorization Letter (VAL) to the Contracting Officer’s Representative at the following address for all employees prior to the beginning of each period of performance and as new contractor employees are assigned to the task order:

Cindy Hopkins

Defense Information Systems Agency

6914 Cooper Avenue

PEO-C2C/CCTD

Fort Meade, MD 20755

The VAL shall be on company letterhead or pre-fabricated form and contain the following information:

· Contract number with start and end dates

· Company point of contact (POC) and telephone number

· Government Task Monitor name and telephone number

· Complete legal name of employee(s)

· Social Security Number

· Security Clearance level, date granted, and

· Adjudication facility name, i.e. DISCO

· Type of personnel security investigation (PSI) pending or completed

· Date PSI completed

Should the contractor have security related questions they should be coordinated through the COR to appropriate security personnel.

Security Contacts. DISA Security Personnel can be contacted for security related questions as follows:

For Industrial Security related issues:

Terry Scott, phone: (301) 225-1229

Defense Information Systems Agency

ATTN: MPS61, Industrial Security

Command Building

6910 Cooper Ave.

Fort Meade, MD 20755-7088

For Personnel Security related issues to include interim IT access requests:

Primary: Richard Young, phone: (301) 225-1237

Alternate: Vernon Rhodes, phone: (301) 225-1532

Defense Information Systems Agency

ATTN: MPS62, Personnel Security

Command Building

6910 Cooper Ave.

Fort Meade, MD 20755-7088

12.7 Information Security and Other Miscellaneous Requirements.

12.7.1 Contractor personnel must comply with local security requirements for entry and exit control for personnel and property at the Government facility.

12.7.2 Contractor employees will be required to comply with all Government security regulations and requirements. Initial and periodic security training and briefings will be provided by Government security personnel. Failure to comply with security requirements can be cause for termination of employment.

12.7.3 The Contractor shall not divulge any information about DoD files, data processing activities or functions, user identifications, passwords or any other knowledge that may be gained, to anyone who is not authorized to have access to such information. The Contractor shall observe and comply with the security provisions in effect at the DoD facility. Identification shall be worn and displayed as required.

12.7.4 DISA retains the right to request removal of contractor personnel regardless of prior clearance or adjudication status, whose actions, while assigned to this task order, clearly conflict with the interest of the Government.

12.7.5 Contractor personnel will generate or handle documents that contain for official use only (FOUO) information at Government facilities. Contractor shall have access to, generate, and handle classified material only at Government facilities. All contractor deliverables shall be marked at a minimum FOUO, unless otherwise directed by the Government. The contractor shall comply with the provisions of the DoD Industrial Security Manual for handling classified material and producing deliverables. The contractor shall comply with DISA Instruction 630-230-19.

12.7.6 The Contractor shall ensure that personnel accessing information systems have the proper and current information assurance certification to perform information assurance functions in accordance with DoD 8570.01-M, Information Assurance Workforce Improvement Program. The Contractor shall meet the applicable information assurance certification requirements, including:

(1) DoD-approved information assurance workforce certifications appropriate for each category and level as listed in the current version of DoD 8570.01-M; and

(2) Appropriate operating system certification for information assurance technical positions as required by DoD 8570.01-M.

Upon request by the Government, the Contractor shall provide documentation supporting the information assurance certification status of personnel performing information assurance functions.

Contractor personnel who do not have proper and current certifications shall be denied access to DoD information systems for the purpose of performing information assurance functions.

13. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI).

The following documents are provided as GFI:

Joint C2 Reference Architecture v3.0, 27 January 2014

DoD Reference Architecture Description, 18 June 2010

Joint Command and Control (C2) Capability Development Document, v1.4, 9 April 2013

DoD Information Assurance Certification and Accreditation Process (DIACAP), 28 Nov 2007

Documents will be provided upon request after award and in support of the work to be performed

14. Other Pertinent Information or Special Considerations.

a. Identification of Potential Conflicts of Interest (COI). The contractor shall identify any potential organizational conflicts of interest (COI). An “organizational COI” is a situation where because of other relationships or activities a person/company is unable or potentially unable to render impartial assistance or advice to the Government or cannot objectively perform contract work or has an unfair competitive advantage.

b. Identification of Non-Disclosure Requirements. This contract does not require a Non-Disclosure Agreement. The contractor will not have any access to sensitive or proprietary information.

c. Key Personnel - Key Personnel changes and substitutions shall be in accordance with DARS Clause 52.237-9000. Key personnel assigned to the subject contract shall be identified by labor category and name. The COR will review resumes of proposed personnel to ensure skill set qualifications are met for the tasks defined in this PWS. For the purposes of this effort, the following positions are considered key personnel:

· Project Manager

· Principal Systems Architect

d. Removal or replacement of key personnel requires contractor notification to the COR or Alternate COR. Notification shall include justification (including proposed substitutions) in sufficient detail to permit evaluation of the impact on the PWS. The Contracting Officer shall be included on all correspondence.

15. Section 508 Accessibility Standards. The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable (if box is checked) to this acquisition.

Technical Standards

FORMCHECKBOX

1194.21 - Software Applications and Operating Systems

FORMCHECKBOX

1194.22 - Web Based Intranet and Internet Information and Applications

FORMCHECKBOX

1194.23 - Telecommunications Products

FORMCHECKBOX

1194.24 - Video and Multimedia Products

FORMCHECKBOX

1194.25 - Self-Contained, Closed Products

FORMCHECKBOX

1194.26 - Desktop and Portable Computers

FORMCHECKBOX

1194.41 - Information, Documentation and Support

The Technical Standards above facilitate the assurance that the maximum technical standards are provided to the Offerors. Functional Performance Criteria is the minimally acceptable standards to ensure Section 508 compliance. This block is checked to ensure that the minimally acceptable electronic and information technology (E&IT) products are proposed.

Functional Performance Criteria

FORMCHECKBOX

1194.31 - Functional Performance Criteria

SECTION C

QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

1. Contract or Task Order Title: Joint Command and Control (C2) Architecture

2. Work Requirements:

· Task 1. Contract Management

· Task 2: Systems Engineering Support

· Task 2.1: Joint C2 Standards Support

· Task 2.2: Joint C2 Architecture Compliance Assessment Support

· Task 2.3: Joint C2 Architecture Repository and Analysis

· Task 2.4: Joint C2 Multi-Party Engineering Activities

· Task 2.5: Joint C2 Architecture Development Support

3. Primary Method of Surveillance:

· Task 1. Contract Management – 100% Inspection

· Task 2: Systems Engineering Support – 100% Inspection

· Task 2.1: Joint C2 Standards Support

· Task 2.2: Joint C2 Architecture Compliance Assessment Support

· Task 2.3: Joint C2 Architecture Repository and Analysis

· Task 2.4: Joint C2 Multi-Party Engineering Activities

· Task 2.5: Joint C2 Architecture Development Support

4. Scope of Performance:

The contractor shall provide services and deliverables in accordance with the Performance Work Statement (PWS).

· The contractor will provide contract management activities to include project planning, scheduling and meeting facilitation. The contract reference is Paragraph 6.1.1.

· The contractor will provide a monthly status report to include cost, schedule and performance metrics as well as Earned Value Management (EVM) data. The contract reference is Paragraph 6.1.2.

· The contractor will provide support needed for meetings associated with task activities such as scheduling, meeting minutes, action items and setting up conference lines. The contractor shall support meeting attendance at various working groups and other relevant meetings with both internal and external organizations. The contractor shall provide audio teleconference capability to support weekly Technical Director Staff meetings and weekly Architecture Core Team meetings. The contract reference is Paragraph 6.1.3.

· The contractor will identify those mandated, emerging, and critical standards in order to facilitate interoperability across Joint C2 capabilities. The contractor shall update the online Joint C2 Standards Profile on the GTG-Federation Portal based on the Joint C2 Reference Architecture & DISR releases. The contractor shall develop change requests to DISR on behalf of the C2 community as needed. The contract reference is Paragraph 6.2.1.

· The contractor will lead and provide engineering support for Joint C2 architecture compliance assessments. The contractor shall assist the Joint C2 community Tier 1 programs in their annual assessment of compliance with the Joint C2 Reference Architecture and the DoD Information Enterprise Architecture (DIEA) to include the principles, rules and technical positions. The contractor shall attend Joint C2 technical interchange meetings. The contractor shall review technical design documentation and program artifacts such as architecture self assessments, and Department of Defense Architecture Framework (DoDAF) views. The contractor shall prepare technical report(s) documenting the status and progress of the Joint C2 community as a whole toward architecture compliance. In this report the contractor shall provide analysis of trends, identification of potential areas of concern and recommendations for the Joint C2 portfolio. The contract reference is Paragraph 6.2.2.

· The contractor will develop and maintain a Joint C2 Architecture Repository on Intelink which will document the evolution of Joint C2 capabilities implemented by the Joint C2 Family of Programs. The Architecture Artifacts Repository will contain community provided DoDAF models in addition to links to Joint C2 architecture models from the Joint C2 CDD, Capability Definition Packages/Capability Packages, and Capability Modules. All tier 1 and 2 systems of the Joint C2 community that provide documentation must be included in this task. The contractor shall analyze current and proposed architectures and develop selected Fit for Purpose (FFP) DODAF 2.0 views and associated Data Management (DM2) elements, including high-level services & interface dependency views (e.g., SvcV-1 & SvcV-3 ) representing the Joint C2 portfolio. The contract reference is Paragraph 6.2.3.

· The contractor shall provide engineering expertise to define and support a Joint C2 Multi-Party Engineering process. The Joint C2 Multi-Party engineering effort shall analyze high priority Joint C2 focus areas. The contractor shall conduct an architectural analysis to include: dependency analysis, identification of risk, and potential gaps or duplications. The contractor shall provide recommendations for the refinement of community multi-party engineering processes and solution architectures (i.e. software, data, and information assurance). Recommendations for the refinement of information assurance architectures must be in compliance with the DoD Information Assurance Certification and Accreditation Process (DIACAP). The contractor shall participate in a joint engineering team consisting of both Government and contractor representatives. As team members, the contractor shall analyze alternatives and produce a recommended design and implementation approach with associated DoDAF SvcV-1 and SvcV-3 artifacts for each Joint C2 focus area. The solution implementation guidance will include rules and technical positions that are required in accordance with the Joint C2 Reference Architecture. The contractor shall plan to support multi-party engineering activities for three (3) high priority Joint C2 focus area.The contract reference is Paragraph 6.2.4.

· The contractor shall provide engineering support for Joint C2 Architecture development. This includes setting up and customizing collaborative tools (i.e. Intelink/SharePoint, DoDAF tools) for developing requirements and artifacts associated with the Joint C2 Architecture. The contractor shall maintain the Architecture Core Team (ACT) site on Intelink SharePoint and manage the DISA DEPS Technical Director’s site. The contractor shall maintain the Joint C2 Compliance and Interoperability Assessment site on Intelink/SharePoint. The Joint C2 Compliance and Interoperability Assessment site shall provide the capability & tools to support the Joint C2 community program architecture self assessment in accordance with the Joint C2 Reference Architecture and approved Joint C2 Solution Implementation Guidance. The contract reference is Paragraph 6.2.5.

5. Performance Standards:

6. Mandatory or regulatory compliance items:

The contractor shall provide initial proof of compliance with regulatory and compliance items contained in the contract. The Contracting Officer’s Representative (COR) and the contracting officer (KO) will evaluate the initial submission. The COR and KO will conduct ad hoc reviews of the contractor’s compliance throughout the remainder of the contract.

The contractor will monitor compliance as required by FAR 52.222-50, Combating Trafficking in Persons, and report any issues to the Contracting Officer.

7. Acceptable Quality Level (AQL):

The AQL for this project is 95% due to the critical to Joint C2 capability development.

8. Evaluation Method:

The COR will perform 100% inspection of the deliverable product and services. When problems are identified, the COR will document the time of verbal notification to the contractor. The COR will confirm the date and time of problem resolution in the record.

9. Incentives (Positive and/or Negative):

The Government will positively and/or negatively review the contractor’s performance based on the success or failure in meeting quality assurance surveillance plan objectives. The contractor is incentivized to earn favorable Government reviews to support continuation of JC2 requirements and support contract awards with other Government agencies seeking DISA’s input on the contractor’s past performance and the Contract Performance Assessment Reporting System (CPARS). Failure to meet the acceptable quality levels may result in an unsatisfactory past performance report by the Government.

Section D - Packaging and Marking

SECTION D

N/A

Section E - Inspection and Acceptance

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLAUSES INCORPORATED BY REFERENCE

Section F - Deliveries or Performance

SECTION F

F.1.

DELIVERY ADDRESSES AND POINTS OF CONTACT.

Delivery addresses and the Points of Contact shall be identified upon contract award.

F.2.

PERIOD OF PERFORMANCE.

Period of performance under this Contract shall be from date of award for a one-year base period and four (4), one (1) year option periods (if exercised) with an additional six (6) month extension of services option (if exercised) in accordance with FAR 52.217-8.

DELIVERY INFORMATION

Section G - Contract Administration Data

SECTION G

G.1. CONTRACT MANAGEMENT.

Notwithstanding the Contractor’s responsibility for total management during the performance of this contract, the administration of the contract requires maximum coordination between the Government and the Contractors. The following individuals will be the Government points of contact during the performance of the contract. See Clause 52.204-9000 for contact information.

a. Contracting Officer (KO).

(1) Contract Administration. All contract administration will be handled by the DITCO-NCR / PL62 Contracting Officer. Communications pertaining to contractual administrative matters shall be addressed to the KO and Specialist(s). No changes in or deviations from the scope of work shall be effected without a written modification to the contract executed by the KO authorizing such changes.

(2) Designation of Representatives. The KO may designate individuals to act as Contracting Officer Representative’s (COR) under the contract. CORs may provide technical guidance in direction of the work, but they will not be authorized to change any of the terms and conditions of the contract. CORs will be designated by a letter of appointment from the KO.

b. Contracting Officer’s Representative (COR). CORs are responsible for defining requirements, funding the work to be performed, monitoring and evaluating the Contractor’s performance, providing technical support to the KO on Contracting issues, and providing acceptance and rejection information to the Accounting and Finance Section for all invoice processing.

(1) At contract award, or at other times when required throughout the contract’s period of performance, the CORs will be designated on authority of the KO, to monitor and coordinate all technical aspects and assist in the administration of the contract.