RFP_AMD_0001.pdf

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER (Type or print)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

1. The purpose of this amendment is as follow s:

a. Provide Goverment responses to all contractor questions.

b. Revise PWS para 6.2.1, 6.3.2, 6.3.3 subtask 3, 12.1 and 12.2, Section L, para 2.1.4 and 2.3, and Section M, para 2.1.2 and 2.1.3 as indicated.

c. See FBO for upload of all questions and answ ers to include Attachment 6 - EPL Worksheet.

2. Date for receipt of offers remains unchanged.

1. CONTRACT ID CODE PAGE OF PAGES

S 1 40

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 05-Feb-2014

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X HC1047-14-R-4006

X 9B. DATED (SEE ITEM 11)

22-Jan-2014

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offer is extended, X is not extended.

Offer must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended by one of the following methods:

(a) By completing Items 8 and 15, and returning 1 copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted;

or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE

CONTRACT ORDER NO. IN ITEM 10A.

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office, appropriation date, etc.) SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(B).

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. DESCRIPTION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

29-Jan-2014

CODE

DISA/CONTRACTS-NCR

P.O. BOX 549

FT. MEADE MD 20755

HC1047 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

HC1047-14-R-4006

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

The following have been modified:

PERFORMANCE WORK STATEMENT

PERFORMANCE WORK STATEMENT (PWS)

As of 5 February 2014

Contract Number: TBD Task Order Number: TBD

1. Contracting Officer Representative (COR):

a. Primary COR:

Name:

Organization:

Department of Defense Activity Address Code (DODAAC):

Address:

Phone No.:

Fax Number:

E-Mail Address:

b. Alternate COR:

Name:

Organization:

DODAAC:

Address:

Phone No.:

Fax Number:

E-Mail Address:

2. Task Order Title: Advanced Enterprise Information Technology and Architecture (AEITA) Support

3. Background The Defense Information Systems Agency (DISA) faces growing challenges in the areas of Technology Management and Information Assurance. The latest DISA Campaign Plan calls for significant improvements in DISA’s abilities to address these critical areas. The DISA Chief Technology Officer (CTO) facilitates the rapid transfer of advanced technology from research and experimentation stages through pilot operations to deployment and full-scale implementation within DISA and Department of Defense (DoD) Defense Information Infrastructure (DII) and mission or enterprise software and platform capabilities. The organization coordinates or facilitates coordination of the rapid insertion of this advanced technology into leading edge pilot services for the joint forces and multi-services command, control, communications, computers, and intelligence (C4I) systems and software. The CTO’s office serves as a vehicle for implementing long-range technology strategy among DISA, Combatant Commanders (COCOM), Services, and coalition and mission partners. The Advanced Enterprise Information Technology and Architecture (AEITA) will address DISA’s technology management challenge in carrying out its research and development mission. The Office of the Chief Technology Officer (OCTO) needs to leverage advanced technology to develop next-generation information assurance architectures and solutions for the Global Information Grid (GIG).

4. Objectives: The objective is to provide the OCTO with technical expertise in the areas of security architectures, assessment of emerging security-related technologies, and planning of security-related technology migration strategies.

5. Scope: This effort will require technology expertise to define the Advanced Enterprise Information Technology and Architecture (AEITA) processes, design and field the AEITA infrastructure, and to provide technical expertise to support technology assessment activities.

The Advanced Enterprise Information Technology and Architecture (AEITA) will address DISA’s technology management challenge in carrying out its research and development mission.

The scope of this PWS is to provide comprehensive support in several areas to include: systems engineering and engineering management; senior level computer science support, program strategy, transformation planning, and technology pilot and demonstration support. The requirement will support CTO, PEO-C2C, and MAE.

6. Performance Requirements:

6.1. Task 1: Management (CTO, PEO-C2C, and MAE)

The contractor shall perform and provide the task management, technical management and program management activities necessary to manage cost, schedule, and performance throughout the life of the contract.

6.1.1 Subtask 1 – Contract Management Plan

The contractor shall prepare and provide a Contract Management Plan describing the technical approach, organizational resources, and management controls to be employed to meet the cost, schedule and performance throughout contract execution. This plan shall include the contractor’s planned billing dates.

Deliverables: Contract Management Plan

6.1.2 Subtask 2 – Monthly Progress Reporting

The contractor shall provide a Monthly Status Report (MSR) and projected requirements of funds, staff-hours, and work completion for evaluation of the contractor’s progress based on the PWS tasks and subtasks. At a minimum, this data shall include: (1) A description of activities and deliverables during the current month for the contract. The descriptions shall include problem definitions and recommendations for program resolutions. More emphasis shall be given to risk management activities; (2) Cumulative planned and cumulative actual hours, cumulative travel and cumulative actual dollars by task; and cumulative actual labor price by subtask; cumulative actual staff hours by subtask and by individual (including location) for the reporting period; (3) Trips, technical visits, and related results for the reporting period; and (4) Planned and actual billing dates. Monthly meetings will be held to review and discuss Interim Progress Review (IPR) Report content; (5) Technical Management – the contractor shall provide engineering support for the technical analysis, technology assessment and evaluation, technology planning and insertion, project planning and technical outreach activities. This shall include transition planning and prototyping and piloting coordination required to ensure relevancy to Warfighter needs and technical and functional soundness.

Deliverables: Monthly Invoice Monthly Status Report Monthly Interim Progress Review (IPR) Report via Power Point Slides Monthly Interim Progress Review (IPR) Meeting Monthly Interim Progress Report

6.2. Task 2: Engineering Support (CTO/TO1)

The contractor shall provide, systems engineering support services to DISA in defining, planning, implementing, and executing the Advanced Enterprise Information and Technology (AEITA) Support.

6.2.1 Subtask 1 – Strategic Technology Analysis, Engineering and Planning The contractor shall provide technical support for targeted and focused technical studies and analyses that support the Agency’s technology strategies and implementations; provide support in the development of the DISA strategic objectives related to technology planning and management, technology and research coordination, and innovation initiatives; provide support to develop and mature the methodologies and processes for technology evaluation, technology strategic planning, and for technology management infrastructure operations; provide the below deliverables to support the CTO in reviewing the effectiveness of the Agency’s technology management processes. The work to be performed under this subtask is at the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables: Technology and Innovation Policy and Process Definition, Evaluation and

Review, and Recommendations Metrics and Definition Analysis

6.2.2 Subtask 2 – Technology Management Framework Engineering The contractor shall provide technical support for planning, hosting and operations of the DISA Technology Information Repository (DTIR), which supports AEITA operations, identification of technical approaches for implementing the DTIR, development and testing support of DTIR solutions conducted by other government and contract organizations, and support of the hosting and operations of the DTIR. The contractor shall also prepare and document DTIR requirements in coordination with the government, monitor use of the DTIR to gather information about its effectiveness and usability, and use the resulting information to feedback into the DTIR development activity.

Deliverables: DTIR Strategic Planning, Requirements Definition, and Design Architecture

Products DTIR Functional Demonstrations

DTIR Innovation Sourcebook DTIR User Guidance

6.2.3 Subtask 3 – Technology Evaluation and Assessment (TS-SCI) The contractor shall support the OCTO by conducting technology evaluations and assessments in coordination with the Contracting Officer’s Representative (COR) in accordance with operational priorities in the DISA Technology Watch List. The contractor shall conduct technical evaluations, experiments, pilots, or assessments in the areas of biometric technologies, command and control technologies, communications and networking technologies, data and data management technologies, engineering and test support technologies, enterprise computing technologies, cloud computing technologies, mobility technologies and information assurance technologies. The contractor shall prepare the related technical evaluation and assessment reports. The work to be performed under this subtask is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables:

Standards based Cloud Initiative Mobility Initiative Evaluation Assessment Report

6.3. Task 3: Technology Piloting and Demonstration Support (CTO/TO2) The contractor shall provide systems engineering support services to define, execute, and transition innovative technologies in conjunction with Technology Piloting and Joint Concept

Technology Demonstrations (JCTD). This includes: technology piloting support; concept demonstration support; and customer service and network optimization.

6.3.1 Subtask 1 – Technology Piloting Support (TS-SCI)

The contractor shall provide expert and technical support to conduct technical studies, data collection, identification, analysis and evaluation of technology pilots. The contractor shall provide evaluation criteria to assess and evaluate cyber security and innovation pilots during technology identification, plan, design, engineering, and implementation. The cyber security pilot technologies may include managing mobile device services with sensors and software and code checking (static and dynamic code checking). The innovation pilot technologies may include data communication between countries, big data, mobile device near field communications, and allowing users to access and retrieve information from various domains and networks. The work to be performed under this subtask is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables: Technical Reports

Reference Materials Network Analysis Findings and Recommendations White Paper Trip Reports and Briefing Charts

6.3.2 Subtask 2 – Concept Demonstration Support

The contractor shall provide expert and technical support to conduct technical studies, data collection, identification, analysis and evaluation of Joint Concept Technology Demonstrations (JCTDs). The contractor shall provide technical support and evaluation criteria to assess and evaluate concept demonstration identification, plan, design, engineering, and implementation. The JCTDs may include social media and creating visualization of data in one application from disparate sources of data. The JCTDs can integrate suite of SOA web-services hosted in DISA enterprise data centers using attributed based access control, common data modeling, data mashups, messaging, and widget frameworks used in exposing and visualizing data based on DoD Net-Centric Data & Services Strategy. The JCTDs require extensive knowledge of net-centric enterprise services, DoD data and services strategy, service oriented architecture concepts, data center architecture and production and infrastructure management, and networks. The work to be performed under this subtask is at the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables: JCTD Concept Briefings

JCTD Management Plans JCTD Technology Transition Plans

Meeting Minutes/Trip Reports

6.3.3 Subtask 3 – Customer Service and Network Optimization

The contractor shall identify, assess, and resolve customer service and network optimization issues with Global Information Grid GIG, Wide Area Network (WAN), and Local Area Network (LAN). The initiatives shall include cloud computing Infrastructure as a Service (IaaS), Platform as a Service (PaaS), Software as a Service (SaaS), data center standardization (latest technologies in compute, storage, and network), network optimization, and service improvement.

Deliverables: Technical Reports Reference Materials Network Analysis Findings and Recommendations White Paper Trip Reports and Briefing Charts

6.4 Task 4 – Program Control Technical Support (PEO-C2C/SE&I) The contractor shall perform program control to include project planning, scheduling, and facilitating meetings. The contractor shall support meeting attendance and provide requisite briefings at meetings, conferences, and working groups as needed with both internal and external organizations. The contractor shall provide management support for the generation, update and maintenance of relevant fiscal year budget briefings and spend plans. The contractor shall provide scheduling support through the preparation and maintenance of an Integrated Master Schedule (IMS). The contractor shall provide support for risk assessment and management activities of all tasked efforts and document them in quarterly risk assessment/status briefs. The contractor shall provide support needed for meetings in support of task activities such as scheduling, meeting agendas, meeting minutes, action items, setting up Defense Connect Online (DCO) sessions, and setting up conference call-in lines. The contractor shall provide administrative support to include Action Information Management System (AIMS) suspense tracking and coordination, administration of relevant Defense Enterprise Portal Service (DEPS) and SharePoint folders and folder content, and similar relevant administrative systems, applications, and repositories.

Deliverables: Briefing Slides Spend Plan Integrated Master Schedule (IMS) Meeting Minutes and Agenda

6.5 Task 5: Systems Engineering and Integration Support (PEO-C2C/SE&I) The contractor shall provide technical support to DISA’s Systems Engineering and Integration Office in the areas of program and administrative management, acquisition strategy and concepts, and systems engineering process refinements. The contractor shall perform a variety of systems engineering activities including planning, preparing, and executing state-of-the-art systems engineering concepts and strategies. The contractor shall provide systems engineering and technical support in a variety of problem areas including the specific problem areas identified in the Subtasks below.

6.5.1 Subtask 1 – Acquisition Strategies and Concepts

The contractor shall provide management assistance focused on future capabilities strategies and concepts relevant to the application of DoDI 5000.02 and Component Acquisition Executive (CAE) Guideline 004 using Agile Development/Agile Testing principles and methods. The contractor shall provide inputs/updates to the DISA Campaign Plan; prepare briefing presentations; and develop Concept Papers/White Papers, Acquisition Strategies, and Concepts of Operation (CONOPS). Activities accomplished in support of this task shall be reported in the

MSR.

Concept Papers Acquisition Strategy

CONOPS

6.5.2 Subtask 2 – Systems Engineering Process Refinement

The contractor shall provide support for the update and refinement of the Systems Engineering (SE) Process based on the practical lessons learned from its successful application to multiple applications and Initiatives. The contractor shall provide advice and assistance in applying the SE Process to relevant capabilities and shall maintain the currency and accuracy of the SE Process briefing slides and any affected templates of that process briefing slide deck. Activities accomplished in support of this task shall be reported in the MSR.

6.6 Task 6: Mission Assurance Systems Engineering Support (MAE) The contractor shall provide technical support to DISA’s Office of the Mission Assurance Executive (MAE) in the areas of networks, platforms, clouds, computing environments, pilots, demonstrations, and services. The types of support may include but are not limited to requirements, architecture, system engineering, design, prototyping, piloting, and implementation with the emphasis on Mission Assurance (MA), Information Assurance (IA), security, and resiliency. The networks include the classified SIPRNet, unclassified NIPRNet, and public Internet. The scope of networks covers Local Area Networks (LAN), Wide Area Networks (WAN), Virtual Private Networks (VPN), Cross-Domain Solutions (CDS), commercial and DoD clouds, and interoperability between different types of networks. The support includes planning of new security architectures, review assessment and piloting of emerging security-related technologies, and planning of security-related technology migration strategies.

6.6.1Subtask.1 – Secure Information Sharing (TS-SCI) The contractor shall provide support in MA, IA, security, and resiliency in the areas of Defense Enterprise Email (DEE), Defense Enterprise SharePoint Service, Active Directory Engineering, Identity Management and Access Control, NIPRNet Systems Engineering, SIPRNet Network Security Engineering, Trusted Network Engineering, Security Research and Development (R&D) Outreach, Secure Information Sharing, Secure Cloud Computing, and Security Process Engineering. The work to be performed under this subtask is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables: Architecture Products such as Microsoft Word documents and PowerPoint drawings, briefings, and relevant email updates

Design Products such as Microsoft Word documents and PowerPoint

IA Data Sharing Specifications Security Technical Implementation Guidelines (STIG)

6.6.2 Subtask 2 – Identity Management and Access Control

The contractor shall provide support in MA, IA, security, and resiliency for the migration from LAN/platform-centric networks and computing environments to WAN/services-centric networks and computing environments.

Deliverables: Architecture Products such as Microsoft Word documents and PowerPoint drawings, briefings, and relevant email updates

6.6.3 Subtask 3 – NIPRNET Systems Engineering (TS-SCI)

The contractor shall support the MAE Office with the DISA’s Defense Enterprise Computing Centers (DECC) efforts in technology refresh, modernization and standardization from the perspectives of MA, IA, security, and resiliency. The contractor shall assist with the DECC modernization and Joint Information Enterprise (JIE) related tasks. The work to be performed under this subtask is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables: Architecture Products such as Microsoft Word documents and PowerPoint

Technical Solutions

6. 6.4Subtask 4 – SIPRNET Network Security Engineering (TS-SCI) The contractor shall provide support to the MA Office in evolving the SIRPNET architecture and services from the perspectives of IA, security, and resiliency. The work to be performed under this subtask is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables: Architecture Products such as Microsoft Word documents and PowerPoint drawings, briefings, and relevant email updates

6.6.5 Subtask 5 – Security Process Engineering (TS-SCI)

The contractor shall provide technical support on specific IA and security tasks, e.g., risk assessment, Continuity of Operations (COOP), contingency planning, firewall design, and/or others as needed. The work to be performed under this subtask is up to the Top Secret level and will require Sensitive Compartmented Information (SCI) access eligibility.

Deliverables: IA Security briefings and email updates

7. Performance Standards:

Performance Standard Acceptable Quality Level

(AQL)

Method of Surveillance

Subtask 6.1.1 Contract Management Plan will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time 100% of the time.

Revisions that occur are minor and are resolved in a satisfactory manner.

Periodic inspection of deliverable products and services.

Subtask 6.1.3 IPR Report will be on time and IAW the PWS

Materials contain required information and are delivered on time 100% of the time.

Revisions that occur are minor and are resolved in a satisfactory manner.

Periodic inspection of deliverable products and services.

Subtask 6.2.1 Technology and innovation Policy and Process Definition, Evaluation and Review, and Recommendations will be on time and IAW the PWS

Reports are delivered on time at least 90% of the time.

Revisions that occur are minor and are resolved in a satisfactory manner.

Quarterly inspection of deliverables.

Subtask 6.2.2 DTIR Functional Demonstrations will be on time and IAW the

PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Quarterly inspection of deliverables.

Subtask 6.2.2 DTIR User Guide will be on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.2.3 DTIR Technology Artifacts/Content Adjudication will be on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.2.3 Technology Evaluation/Assessment Artifacts and Reports will be on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.3.1 Tech Piloting Technical Reports will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.3.1 Tech Piloting Reference Materials will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.3.1 Tech Piloting Network Analysis Findings and White Papers will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.3.1 Tech Piloting Trip Reports and Briefing Charts will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.3.2 JCTD Concept Briefings will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.3.2 JCTD Management Plans will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.3.2 JCTD Technology Transition Plans will be delivered

Materials contain required information and are delivered on time at least 90% of the on time and IAW the

PWS

time. Revisions that occur are minor and are resolved in a satisfactory manner.

Subtask 6.3.2 JCTD Meeting Minutes and Trip Reports will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.6.1 Secure Information Sharing Architecture Products will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6.6.1 Secure Information Sharing Design Products will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6. 6.1 Secure Information Sharing IA Data Sharing Specifications will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6. 6.1 Secure Information Sharing STIG will be delivered on time and IAW the

PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6. 6.2 Identity Management and Access Control Architecture Products will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable

Subtask 6. 6.2 Identity Materials contain required Random inspection of deliverable

Management and Access Control Design Products will be delivered on time and IAW the PWS information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

products and services.

Subtask 6. 6.3 NIPRNET Systems Engineering Architecture Products will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6. 6.3 NIPRNET Systems Engineering Technical Solutions will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6. 6.4 SIPRNET Systems Engineering Architecture Products will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6. 6.4 SIPRNET Systems Engineering Design Products will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

Random inspection of deliverable products and services.

Subtask 6. 6.5 Process Engineering IA Security briefings and email updates will be delivered on time and IAW the PWS

Materials contain required information and are delivered on time at least 90% of the time. Revisions that occur are minor and are resolved in a satisfactory manner.

8. Incentives:

Both positive and negative performance ratings shall be recorded in the Contractor Performance Assessment Reporting System (CPARS). The COR and PM will hold monthly reviews with the contractor to discuss deliverables, cost and schedules. Timely submission of invoices and deliverables are required in order to maintain and continue the work involved with this task. All deliverables will be inspected, tested and evaluated for completeness, functionality and utility.

During each meeting the Contractor will provide detailed analyses of all ongoing, completed, and planned efforts. Based on the review of this information, the Government can then determine how to continue forward with the efforts, evolving requirements, and enabling the Contractor to develop their role on the effort.

9. Place of Performance:

Unclassified work to be accomplished under this PWS shall be done at both the contractor’s facilities and at DISA, Ft. Meade, MD 20755. Work under this PWS that will require Sensitive Compartmented Information (SCI) access shall be performed at DISA, Ft. Meade, MD 20755.

Office space will be provided at DISA’s location for this classified work. The space will be allocated via approved Space Waiver(s) per task(s).

Local travel within the Ft. Meade and within the National Capital Region is required. Travel outside the local area may be required. All travel must be approved, in advance and in writing by the government COR. Site visits may be required to Government and industry facilities in CONUS and in support of various security activities and government or industry working groups or conferences. Travel and reimbursement shall be in accordance with the Joint Travel Regulation and its prevailing rates.

Travel is possible to the CONUS locations shown in the Travel table below.

Travel

Task 6.2 No. of Persons No. of Trips Duration SPAWAR 2-3 4 2-3 Days San Francisco 1 3 2-3 Days Boston 1 1 2-3 Days Task 6.3 No. of Persons No. of Trips Duration Oklahoma City 1 1 3 Days Ogden 1 1 3 Days San Antonio 1 1 3 Days Alabama 1 1 3 Days San Jose 1 2 4 Days Task 6.4 No. of Persons No. of Trips Duration Boston, MA 1 1 5 -7 Days Las Vegas, NV 1 1 5-7 Days Miami, FL 1 1 5-7 Days San Diego, CA 1 1 5-7 Days Charleston, SC 1 1 5-7 Days Task 6. 6 No. of Persons No. of Trips Duration

Optional Optional Optional

Alternate Place of Performance - Contingency Only. Contractor employees may be required to work at home, another approved activity within the local travel area or at the contractor's facility in cases of unforeseen conditions or contingencies (e.g., pandemic conditions, exercises, etc.).

Any equipment such as laptops or phones provided to Contractor personnel shall be returned at the termination of the engagement or at another time mutually agreeable to both parties.

Contracting Officer Representative (COR) approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources. To the extent possible, the contractor shall use best efforts to provide the same level of support as stated in the SOW/PWS. In the event the services are impacted, reduced, compromised, etc., the Contracting Officer or the contractor may request an equitable adjustment.

10. Period of Performance:

The period of performance is one base year, and four one year option periods.

11. Delivery and Payment Schedule:

All days are calendar days, except where otherwise noted. All deliveries shall be made in softcopy to the Defense Enterprise Portal Service (DEPS) repositories as designated by the COR.

The Government reserves the option to request hardcopy deliverables. All deliverables are in contractor format, in coordination with the COR. Standard distribution applies unless otherwise noted.

PWS

Task

Deliverable Title

Format Due Date Distribution/Cop ies

Frequency and

Remarks

6.1.1 Contract

Mgmt. Plan Contractor determined format (approved by

COR)

5 calendar days after contract award date (initial).

One copy to COR and copy to Contracting Officer

Initial – 5 calendar days after contract award.

6.1.2 Monthly

Status Report

(MSR)

Contractor determined format (approved by

COR)

15th of each month.

Uploaded to WAWF and soft copy to COR via

DEPS

Monthly on 15th

6.1.2 IPR Slides Contractor

determined format (approved by

COR)

5 calendar days before Monthly IPR Meeting

One copy to

COR

Monthly

6.1.3 Monthly IPR

Report

Contractor determined format (approved by

COR)

Within one week after end of each month(based on award date) and

One copy to

COR

Monthly (coordinati on with

COR)

coordinated with COR.

6.2.1 Policy and

Process

Contractor determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1 -5 per month

6.2.1 Metrics

Analysis and Definition

Contractor determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1-5 per month

6.2.2 Strategic

Planning, Requirement s Definition, and Design Architecture Products

Contractor determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1 -5 per month

6.2.2 Demonstrati

on

Contractor determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1 -5 per month

6.2.2 Sourcebook Contractor

determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1 - 5 per month

6.2.2 User

Guidance

Contractor determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1 - 5 per month

6.2.3 Evaluation/A

ssessment and Reports

Contractor determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1 -5 per month

6.2.3 Cloud

Initiative

Contractor determined format (approved by

COR)

2 calendar weeks after Government request

One copy to PM and COR

1 -5 per month

6.2.3 Mobility Contractor 2 calendar One copy to PM

Initiative determined format (approved by

COR)

weeks after Government request and COR 1 -5 per month

6.3.1 Technical

Reports

Contractor determined format (approved by

COR & PM)

10 business days after Government request

One copy to PM and COR

1 - 3 per month

6.3.1 Reference

Materials

Contractor determined format (approved by

COR & PM)

10 business days after Government request

One copy to PM and COR

1 - 3 per month

6.3.1 Analysis

Findings and White Paper

Contractor determined format (approved by

COR & PM)

10 business days after Government request

One copy to PM and COR

1 -3 per month

6.3.1 Trip Reports

and Briefing Charts

Contractor determined format (approved by

COR & PM)

5 business days after travel completion

One copy to PM and COR

1 - 3 per month

6.3.2 Concept

Briefings

Contractor determined format (approved by

COR & PM)

10 business days after Government request

One copy to PM and COR

1 - 3 per month

6.3.2 Management

Plans

Contractor determined format (approved by

COR & PM)

10 business days after Government request

One copy to PM and COR

1 - 3 per month

6.3.2 Transition

Plans

Contractor determined format (approved by

COR & PM)

10 business days after Government request

1 - 3 per

6.3.2 Meeting

Minutes/Trip Reports

Contractor determined format (approved by

COR & PM)

5 business days after travel completion

One copy to PM and COR

1 - 3 per

6.3.3 Technical Contractor 10 business One copy to PM 1 - 3 per

Reports determined format (approved by

COR & PM)

days after Government request and COR month

6.3.3 Reference

Materials

Contractor determined format (approved by

COR & PM)

10 business days after Government request

One copy to PM and COR

1 - 3 per month

6.3.3 Analysis

Findings and White Paper

Contractor determined format (approved by

COR & PM)

10 business days after Government request

One copy to PM and COR

1 - 3 per month

6.3.3 Trip Reports

and Briefing Charts

Contractor determined format (approved by

COR & PM)

5 business days after travel completion

One copy to PM and COR

1 - 3 per month

6.4 Briefing

Slides

Format determined by Project Manager (PM)

Draft - 3 calendar days after government request. Final – 3 days prior to briefing.

One copy to PM and COR

1 - 3 per month

6.4.1 Spend Plan Format

determined by Project Manager (PM)

Draft - 3 days after government request Final - 7 days after government request Updates -5 calendar days after government request

One copy to PM and COR

Updates Estimate 1 or 2 per Quarter NTE 6 per Year

6.4 Integrated

Master Schedule

(IMS)

Format determined by Project Manager (PM)

5 calendar days after government request.

Updates - Weekly

Updates - Weekly

6.4 Meeting

Minutes and Agenda

Format determined by Project Manager (PM)

Agenda – two days before meeting.

Meeting Minutes - 5 calendar days after meeting

One copy to PM and COR

Weekly

6.5.1 Briefing

Slides

Format determined by Project Manager (PM)

Draft - 3 calendar days after government request Final – 3 days prior to briefing

One copy to PM and COR

1 – 3 per month

6.5.1 Concept

Papers

Contractor determined format (approved by

COR & PM)

Draft - 7calendar days after government request. Final – 14 calendar days after government request.

One copy to PM and COR

Estimate 1 or 2 per Quarter NTE 6 per Year

6.5.1 Acquisition

Strategy

Contractor determined format (approved by

COR & PM)

Draft - 7 calendar days after government request Final – 14 calendar days after government request.

Updates - 5 calendar days after government request

One copy to PM and COR

Estimate 1 or 2 updates per Quarter NTE 6 per Year

6.5.1 CONOPS Contractor

determined format (approved by

COR & PM)

Draft - 7 calendar days after government request Final – 14

One copy to PM and COR

Estimate 1 or 2 per Quarter NTE 8 per Year calendar days after government

6.5.2 Briefing

Slides

Format determined by Project Manager (PM)

Draft - 3 calendar days after government request Final – 3 days prior to briefing

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.1 Architecture Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.1 Design Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.1 Data Sharing Specification s

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.1 STIGs Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.2 Architecture Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.2 Design Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to

One copy to PM and COR

Estimate 1 per month NTE 3 per schedule.

6. 6.3 Architecture

Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.3 Design Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.4 Architecture Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6. 6.4 Design Products

Contractor determined format (approved by

COR & PM)

10 calendar days before due date.

Final – according to schedule.

One copy to PM and COR

Estimate 1 per month NTE 3 per month

6.7.5

IA Security briefings and email updates

Contractor determined format (approved by

COR & PM)

Daily and weekly consulting with Government

One copy to PM and COR

Estimate 1 per week NTE 5 per week

11.1 Payment Schedule.

The Contractor is authorized to invoice monthly for these severable services. In the case of cost reimbursement CLINs, the amount shall be all allowable costs. In the case of fixed-price CLINs, that amount shall be the monthly unit price. Payment (and the application of the Prompt Payment Act) will depend upon delivery and acceptance of the deliverables set forth above, as well as delivery and acceptance of the severable services performed each month.

12. Security:

The work to be performed and products to be delivered under this contract shall be accomplished in accordance with the Contract Security Classification Specification, DD Form 254, pertaining to this contract. The contract shall conscientiously follow the security guidance provided in the

DD form 254, the Classification Guide, and other guidance that may be established in writing by the Contracting Officer’s Representative (COR).

12.1. Security Clearance

This section shall be considered a supplement to Block 13 of the Government provided DD 254, Contract Classification and Specification.

All personnel require security clearance at the TOP SECRET level. All individuals will be U.S.

citizens. The Contractor shall follow the standards established in DOD 5200.2-R, DOD Personnel Security Program. All unclassified portions of such data and information shall be defined as sensitive information and be protected under Public Law 100-225.

12.2. Security Clearance and Information Technology (IT) Level Security Clearance and Information Technology (IT) Level. All personnel performing on this contract must be U.S. citizens. There is one level of personnel security requirements under this contract:

IT-I (privileged level systems access) requires a final Top Secret security clearance and final

IT-I eligibility when performance starts. Immediately upon hire at least one information engineer will require Sensitive Compartmented Information (SCI) access eligibility adjudicated by the Defense Intelligence Agency (DIA) to perform their duties. SCI Processing for SCI eligibility will be coordinated with the supporting Government Security Manager and will begin immediately upon start of duty performance under this contract.

The contractor's project manager requires a final Top Secret security clearance and final IT-I eligibility when performance starts. The remaining contractor personnel require a final Top Secret security clearance and IT-I eligibility when performance starts.

12.3. Investigation Requirements

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

12.3.1. Clearances

Contract employees that are not immediately eligible for at least interim IT-1 systems access will be permitted to begin work with interim IT-II systems access at the discretion of the Government, pending eligibility for IT-1. 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-1 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-1 systems access by DISA Security.

Advance NAC results or a previous DoD investigation is required for interim IT-1 consideration. If the employee is not able to obtain an interim IT-1 clearance within 100 days they will not be eligible for continued employment with the agency.

12.4. 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 Top 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. Obtaining Clearance

The contractor is responsible for obtaining personnel security clearance. The contractor will assure that individuals assigned to this contract have completed the required actions to obtain prerequisite security clearance. The contractor will forward a Visit Authorization Letter (VAL) on all their employees to:

DISA Security Division ATTN: Programs and Oversight Branch, MP61 P.O. Box 549 Ft. Meade, MD 20755-0549

12.6. Removal of Contractor Personnel

Should the contractor decide to replace personnel assigned to this effort whose actions conflict with the interest of the Government, regardless of prior clearance or adjudication status, the Contractor shall, with COR/Alt. COR approval, within five days, assign other qualified personnel to fill those positions.

12.7. Security Procedures.

All contractor personnel working on or managing this effort shall strictly adhere to DISA and DoD security regulations and procedures and shall comply with local security requirements as established by the facility being supported or visited in conjunction with this PWS.

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

(GFI):

13.1 Government Furnished Equipment

During the performance of this requirement, DISA will provide the use of standard office furnishings/equipment and administrative facilities at the DISA location at Fort Meade, MD for contractor personnel assigned to this requirement. This includes desks, telephones, PCs, access to DISANET. All assigned personnel shall be eligible to use the furnishings/equipment.

13.2 Government Furnished Information

GFI will include programmatic documents, budget information/cost estimates and other documentation as required. Contractors will be given access to DKO/Shared drives/DISANet, etc. DISA will provide information and documentation concerning existing models, systems, computer programs, and procedures required in the accomplishment of the tasks above. The DOD and DISA Web Style Guides are available on the DISA internal home page at www.datahouse.disa.mil. The contractor is expected to have knowledge of pertinent Federal, DoD, and DISA standards, policies, procedures, and directives. Updates to this document will be provided as needed.

14. Other Pertinent Information or Special Considerations:

A. Identification of Potential Conflicts of Interest (COI):

The contractor shall identify any potential conflicts of interest and deliver a mitigation plan to address them as part of the proposal. The contractor and any subcontractors are hereby placed on notice that they may be precluded from participating in future federal contract competitions for the planning, furnishing, development, or…