HC1047-14-R-4003_Omnibus__1-23-2014.docx

HC1047-14-R-4003

Section SF 1449 - CONTINUATION SHEET

Months

Project Mgmt & Documentation Support

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 1 and all subtask.

FOB: Destination

NET AMT

Months

Certification & Accreditation Support

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 2 and all subtask.

NET AMT

Cost

Software Integration

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 3 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

Operations Support

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 4 and all subtask.

NET AMT

Cost

Software Development

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 5 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

Community Management Support

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 6 and all subtask.

NET AMT

Months

Business Ops Support

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 7.

NET AMT

Cost

Travel

COST

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Tasks

ESTIMATED COST

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 1 and all subtask.

NET AMT

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 2 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 3 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 4 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 5 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 6.

NET AMT

Cost

COST

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 7

ESTIMATED COST

Cost

COST

ESTIMATED COST

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 1 and all subtask.

NET AMT

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 2 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 3 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 4 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 5 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 6 and all subtask.

NET AMT

Months

FFP

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Tasks.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 1 and all subtask.

NET AMT

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 2 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 3 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 4 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 5 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 6 and all subtask.

NET AMT

Months

FFP

NET AMT

Cost

CPFF

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 1 and all subtask.

NET AMT

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 2 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 3 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 4 and all subtask.

NET AMT

Cost

CPFF

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 5 and all subtask.

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

Months

FFP

IAW PWS dated 11 Dec 13, provide the necessary personnel needed to support PWS Task 6 and all subtask.

NET AMT

Months

FFP

NET AMT

Cost

CPFF

ESTIMATED COST

FIXED FEE

TOTAL EST COST + FEE

PWS - 23OCT2013

Forge.mil Omnibus Support Performance Work Statement (PWS)

17 December 2013

1. Contractor Officer Representative (CORs).

1.1. Primary COR.

Name

Organization

DODAAC

Address

Phone Number

Fax Number

E-Mail Address

1.2. Alternate COR.

Name

Organization

DODAAC

Address

Phone Number

Fax Number

E-Mail Address

2. Task Order Title. Forge.mil Omnibus Support

3. Background.

The Defense Information System Agency (DISA) Forge.mil Program Management Office (PMO) requires Software Development Life Cycle (SDLC) support. SDLC includes, but is not limited to planning, implementing, testing, documenting, deploying, and maintaining the software applications that comprise the Forge.mil service. This effort will require project management expertise as well as technical expertise in the areas of application lifecycle management systems (ALM), software engineering, DoD security architectures, planning security-related technology risk migration strategies, integration assessments into emerging IT technologies, business operation, and community management support. Detailed information concerning the requirements and task is contained in subsequent sections.

Forge.mil is a family of cloud-based enterprise services using cloud computing capabilities to provide hardware and software-as-a-service infrastructure to accelerate design, development, test, deployment, and sharing of applications, program source code, and other software development artifacts (such as IA and test documentation), and to improve the reliability of software, systems, and services implemented on the Global Information Grid (GIG). Forge.mil services comprise four distinct production systems available to the Department of Defense (DoD) community, and one currently being deployed into production:

Current Systems:

1. www.forge.mil: This site is the only forge.mil site with no access restrictions. Anyone with access to NIPRNet or the internet can view www.forge.mil. Its purpose is to educate the viewing public about the forge.mil program and service offerings, and to provide a link for users to register for forge.mil. Unauthorized users attempting to access the other forge.mil services are redirected to this site.

1. Forge.mil Community: Social networking-like collaboration site for software developers and other DoD IT capability providers. Supports self-organizing behavior to facilitate communications and collaboration across projects. Supports technical and functional groupings and provides a rich content management capability.

1. SoftwareForge: A collection of tools providing a full-featured application lifecycle management system support distributed, collaborative development within projects and reuse of open source and DoD community source software across the enterprise. Its intent is to promote early and continuous collaboration among developers, material providers, testers, operators, and other users throughout the software/application development life-cycle.

1. ProjectForge: ProjectForge provides the same capabilities as SoftwareForge, but for programs and/or projects that are not doing DoD community source development and/or need to restrict access to specific project members. While SoftwareForge comes free to all DoD affiliated users, ProjectForge is a fee for service capability.

System in process of production deployment:

1. milCloud: The newest addition to the Forge.mil family of services, milCloud provides for the automated provisioning of virtual environments within a variety of cloud environments, automated system build and deployment with a limited number of integrated test tools, and automated deployment of simulator test systems. milCloud itself is a system/service independent of other Forge.mil services and will be available to Forge.mil and Forge.mil users, as well as non-Forge.mil users.

In production, Forge.mil is deployed on approximately 10 virtual machines on the unclassified network for the www.forge.mil, Software.forge.mil, Project.Forge.mil, and Community.forge.mil applications and databases; and 5 virtual machines on the classified network for the www.forge.mil, Software.forge.mil, and Project.Forge.mil applications and databases; All applications run on top of Red Hat Enterprise Linux. All management and administration of the Forge.mil server and communications hardware and operating systems is a 24 X 7 X 365 service performed by DISA as part of hosting the systems in DISA DECCs.

In pre-production (currently DISA’s RACE environment) a full complement of Forge.mil application stack is deployed.

When milCloud is deployed to production, it will be hosted on approximately 11 more virtual machines on the unclassified network; it runs on top of Red Hat Enterprise Linux having a single Windows 2008 server; and management its hardware and operating systems is a 24 X 7 X 365 service performed by DISA as part of hosting the systems in DISA DECCs.

The installation and/or maintenance updates for Forge.mil application stack in the production operational environments (unclassified and classified) occurs monthly or more frequently and is performed as an Authorized Service Interruption (ASI) in the off-hours, normally from Friday after Close Of Business (COB) until complete. Normal Forge.mil management and operations are an 8 X 5 function, however as previously stated, when outages occur designated on-call personnel may be required to work during off-hour periods to perform emergency maintenance for RTS conditions.

The Forge.mil engineering team is using automation tools such as Puppet for provisioning, configuring, and integrating the Forge.mil application stack, over the number of test environments needed to perform all required tests (e.g. integration, functional, acceptance, performance, security, load, regression) on the Forge.mil application stack prior to deployment to the operational systems. The number of environments required shall be determined jointly by the Forge.mil PMO and the contractor. The test environments shall be maintained at the same level of rigor as the pre-production and production operating environments.

When milCloud is deployed to production, in the same manner as stated above, for the test environments needed to support milCloud. As milCloud utilizes cloud resources on the “back-end” the contractor must be able to support integration with such capabilities. For purposes of this requirement assume the cloud will be VMWARE based.

The engineering development team will jointly work with the Forge.mil PMO and milCloud development team to include the use of common open-source or COTS test tools used for web-service validation, functional, performance, code analysis, and other purposes.

The operational support and engineering team will jointly serve as the Tier 2 and 3 Service Desk function on an 8 X 5 basis, with a designated on-call administrator during off-hours. On-call administrators may be required to perform emergency maintenance for Return To Service (RTS) conditions during off-hour periods. DISA will provide the 24 X 7 X 365 Tier 1 Service Desk function.

The Forge.mil program has always operated using the Agile Software Engineering methodology at a 2 week/iteration pace. Forge.mil follows endorses Agile project management and other Agile concepts and incorporates them into processes and procedures. The Forge.mil team has multiple “scrum masters” and continues to incorporate Agile concepts, processes, and procedures into our program. The contractor shall be familiar with Agile Software Engineering and adopt Agile concepts, processes, and procedures in all contract areas.

4. Objectives.

The overall objective of this requirement is to develop, integrate, test, sustain, maintain the entire Forge.mil ecosystem and infrastructure, business support, and community management support under one consolidated effort. Work accomplished under this effort will provide Forge.mil with the ability to continue to provide services in full life-cycle activities such as integration, certification, operational support (e.g., user assistance, performance reporting, and maintenance), system upgrades, and day-to-day operations. The life-cycle management support includes applying security patches, maintenance, provisioning, testing, and operational management (e.g., trouble ticketing, performance reporting, and service desk support). This also includes exploration and evaluation of new emergent Operational Support Systems (OSS), assessment, procurement, Certification & Accreditation (C&A) support, and system administration and support necessary for limited operational capability (LOC) support for Forge.mil. The community and business support area consists of training Forge.mil customers, marketing, and business support internal and external stakeholders of the Forge program.

5. Scope.

The work needed under this requirement is to provide support services and assistance to the Forge.mil application engineering effort and the Program Management Office (PMO). The Forge.mil environments and components include, but are not limited to; the test, integration, pre-production, and production environments of the DISA Headquarters (HQ) Lab at Ft. Meade, MD; the DISA Rapid Access Computing Environment (RACE) Test & Evaluation (T&E) environments at Defense Enterprise Computing Center (DECC) Oklahoma and the production/operational forge.mil environments at DECC Montgomery, DECC Oklahoma City (OKC), as well as the shared COOP environments at DECC St. Louis and other DISA DECCs as necessary.

The overall scope also includes full engineering life-cycle support in the areas of information assurance, community management for users and prospective users of the Forge.mil suite of services, Forge.mil business office support, software development, integration, testing, certification, operational support (e.g., user assistance, performance reporting, and maintenance), system upgrades, and day-to-day operations of all environments related to Forge.mil. The life-cycle management support includes applying security patches, maintenance, provisioning, testing, and operational management (e.g., trouble ticketing, performance reporting, and service desk support).

6. Performance Requirements

6.1 Task 1 - Project Management & Documentation Support

The contractor shall provide project management & documentation support for the Forge.mil operating environments in support of the Forge PMO. The contractor shall perform the following activities:

1. Creating engineering documents as required;

1. Keeping all engineering documents up to date;

1. Ensuring the engineering team follows the Agile method;

1. Providing support to end-users by monitoring, performing triage, and responding to trouble tickets or other means of reporting;

1. Maintaining statistics of number of users using Forge.mil that will provide management information for user growth and will support out year budget projections;

1. Managing all incident reports (internal and external) to closure;

1. Defining and implement customer communication plans to ensure status is appropriately updated;

1. Define, implementing, and monitoring that means to measure customer satisfaction;

1. Participating in the planning and delivery of community webinars;

1. Creating and maintaining user stories that involve the purpose of monitoring a task in Forge.mil;

1. Maintaining configuration control and management of the operating environments in accordance with the policies laid out in the DISA Small Project Documents;

1. Providing Subject Matter Experts (SME) on Forge.mil engineering, IA, Integration and Testing, and Operations matters from both technical and functional perspectives, and supporting stakeholders;

1. Preparing, as requested, customer outreach briefs, plans, Forge.mil software demos, and other documentation supporting the Forge.mil’s mission;

1. Providing Monthly Status Reports (MSR) to Forge.mil management that includes accomplishment, progress, plans for next month, issues/concerns, and financial status (current work plan, work breakdown structure, burn rate planned);

1. Ensuring all teams formed in this requirement provide guidance/recommendations to the PMO, CMT and CCB that can adversely impact schedule or performance;

1. Leading the Forge.mil daily standup (DSU) calls (currently held at 9:00 AM eastern but subject to change), as well as being an active participant;

1. Leading the bi-weekly iteration Planning and User Acceptance Test (UAT) meetings (using both Defense Connect Online and conference calling) normally held on alternating Fridays following the DSU as well as being an active participant;

1. Leading the bi-weekly iteration kickoff meetings normally held on alternating Mondays following the DSU as well as being an active participant; and

1. Provide technical and functional activities at the contract level needed for the Program Management of this PWS. This effort includes productivity and management methods such as quality assurance, progress/status reporting, schedule, risk identification/handling/mitigation strategy, and program reviews.

1. Coordinating and leading the quarterly Release Planning meetings held either in a physical location or virtually via DCO and conference call, as well as being an active participant and documenting the meeting.

1. Provide support and assist with reducing program costs of design, development, test, deployment, and certification through automation, centralization, and virtualization of hardware and services;

Deliverables:

Kick Off Meeting Project Management Plans Prepare and maintain a master Plan of Actions and Milestones (POA&M) for TestForge.mil test and operations and activities.

In Process Reviews (IPR) Briefs, plans, demos, and other documentation supporting the Forge.mil project office.

Monthly Status Report (MSR) Daily Stand-up QPR/IPR Iteration Plan Slide Iteration Planning Meeting notes Configuration Control Board Meeting notes

6.2 Task 2 - Certification & Accreditation Support

The contractor shall provide certification and accreditation by means of IA support over the Forge.mil environments in support of the Forge PMO. The activities in this task involve access to sensitive information. Therefore, a minimum of Top Secret personnel is needed. The contractor shall perform the following activities:

1. Assure the security posture of the application system;

1. Maintain and track status of Information Assurance Vulnerability Assessment (IAVA) or other open findings in Operating System (OS) and application level of components; prepare and submit Plan Of Action & Milestone (POA&Ms) as required and manage open findings to closure;

1. Work with Forge stakeholders to apply and maintain the necessary IA posture of Forge.mil environments as specified by DoD policy, security checklists, Security Readiness Reviews (SRRs), and Security Technical Implementation Guides (STIGS);

1. Ensure current and new Forge components meet the DoD IA criteria and requirements for performance and dependability;

1. Support Forge.mil services in maintaining a security risk assessment throughout the performance of this requirement;

1. Support the DoD Certification and Accreditation process as described in DIACAP and be responsible for reporting, tracking, and correcting services based on Joint Task Force-Global Network Operations (JTF-GNO) Communication Tasking Orders (CTOs) and IAVA advisories using DoD standard tools, including the Vulnerability Management System (VMS) and other relevant IA information systems up-to-date;

1. Support the DoD Certification and Accreditation process as described in DIACAP and be responsible for ensuring required IA artifacts are present in eMASS; Support the maintenance and revision of documentation needed for the C&A process;

1. Provide knowledge and expertise in the following areas: Service-Oriented Architecture (SOA) and net-centric design; software design and development; database management; network design and management; web application architectures; hardware configuration and installation; systems integration; testing; DoD DIACAP certification; and technology integration.

1. Provide support to enable cross-component collaboration and integration using an open computing model to support system development and certification and accreditation;

Deliverables:

IA & CA Tracking Report IAVA Review Report VMS Tracking & eMASS update Generate and maintain C&A documentation

6.3 Task 3 – Software integration, test and validation support The contractor shall support the Forge’s engineering team in providing software integration, test and validation support of the Forge.mil environments in addition to supporting Forge PMO and team members. The activities in this task involve access to DISA DECC data systems. A minimum of final Top Secret security clearance and IT-I (privileged level systems access) is required when performance starts. The contractor shall perform the following activities:

1. Provide support to the program’s software development, integration and test, production deployment, operations, and certification processes throughout the Software Development Life Cycle (SDLC);

1. Provide support and assistance with the continued development and fielding of all automation that provides provisioning, test, and deployment of the Forge.mil services;

1. Work with all other Forge.mil groups to successfully develop, build, test, and deploy the forge.mil services into the various production environments on a daily, weekly, or monthly basis (currently Forge.mil deploys to production on a monthly basis, and the forge.mil teams are modifying deployment processes to increase the frequency of production deployments);

1. Provide an independent verification and validation view-point on the Forge application system’s functionality, performance, and security, and the Forge continuous integration and delivery platform’s functionality and integrity of function;

1. Define, implement, and maintain test plans and procedures for testing and validating critical systems components;

1. Define test and implementation test-cases for inclusion during integration and pre-deployment test cycles necessary to validate existing automated test processes;

1. Maximize utilization of software engineering test cases by auditing the development process and independently confirming their veracity;

1. Monitor test artifacts produced within the Forge continuous integration environment, recommending improvements and/or identify gaps in test cases;

1. Provide troubleshoot support to the engineering teams specific to the testing of components in the Forge.mil environments;

1. Work with Forge stakeholders to resolve site specific issues concerning installation, configuration, network connectivity, and Information Assurance items related to the operating environments;

1. Test the viability of various applications and pilot them in test environments in support of future Forge.mil components and capabilities;

1. Work with Forge stakeholders to enhance and increase the capability of the Forge development and test environments to support a more robust virtualized and automated architecture;

1. Execute performance tests, functional tests, and security scans prior to major deployment to the production environment;

1. Implement, in concert with Forge.mil Engineering, automation necessary to (i) continuously monitor and report on the state of the application pre-production and production environments; (ii) deploy OS and/or application level updates ‘on demand;’ (iii) establish system baseline at a known revision level, (iv) work harmoniously with the Forge continuous integration environment;

1. Establish and maintain the forge.mil product lines’ Configuration Management (CM) Control Items (CI) and baselines;

1. Provide support in the automation of Forge.mil components across project partners to promote the utilization of continuous integration and deployment;

1. Ensure a seamless integration between collaborative development components and other components or systems that may be provided by partner organizations of DISA in the Forge software; and

1. Install, manage, and operate the Forge.mil application stack residing on the test, pre-production and production operating environments.

Deliverables:

User Artifacts, Technical Reports, use cases, source codes, software scripts, and user support documentations, IA support documentations, environment System Architecture Iteration Test Plan Iteration Test Report Site specific issues/incident After Action Report Monthly Drop Readiness Assessment Reports to IAM

6.4 Task 4 – Operations Support

The contractor shall provide operations support to ensure the quality and dependability of the Forge.mil infrastructure in support of the Forge PMO. The activities in this task involve access to DISA DECC data systems. A minimum of final Top Secret security clearance and IT-I (privileged level systems access) is required when performance starts. The contractor shall perform the following activities:

All operations and maintenance of current pre-production (development and testing environment) and production systems (Rapid Access Computing Environment, NIPR, SIPR);

1. Implement and maintain the configuration management system;

1. Apply application level updates to any affected system (monthly maintenance);

1. Monitor production systems – remediate run-time issues, assure security posture of production system;

1. Define, maintain, and implement operational processes germane to the application system and relevant environments;

1. Provide support to assist those programs and projects relying on Forge.mil services to integrate Forge.mil into their native IT processes and existing tools;

1. Provide operational support to Commercial Of The Shelf (COTS) vendors in support of isolating or determining reported problems;

1. Provide guidance/recommendations to the Forge.mil PMO, Community Management Team (CMT) and Configuration Control Board (CCB) on readiness to deploy changes to production that can impact schedule or performance;

1. Serve as both as a CCB member and CCB Secretariat roles; and

1. Perform as a Forge stakeholder with engineering design, development, and integration for the Forge.mil environments.

1. Provide all applications administration and management support for the operations of the production Forge.mil services hosted on NIPRNet including http://www.forge.mil, https://community.forge.mil, https://software.forge.mil, and https://project.forge.mil, as well as milCloud services and other forge.mil services developed for deployment and hosting on NIPRNet as they become available;

1. Provide all applications administration and management support for the operations of Forge.mil services hosted on SIPRNet including software.forge.smil.mil and other forge.mil services developed for deployment and hosted on SIPRNet as they become available, as well as milCloud services and other forge.mil services developed for deployment and hosting on NIPRNet as they become available;

Deliverables:

POA&M Technology products enhancement Support the development, implementation, and maintenance of integrated product

6.5 Task 5 – Software Development for the Collaboration and Community product line

The contractor shall support the engineering task to develop and deliver the system that will enable the Forge.mil Collaborative Development Environment. This task provides an open, Service Oriented Architecture (SOA) based collaboration platform based on CollabNet software to support the Forge.mil community and the development of open source and community source software within the DoD. This platform shall be designed to be operated in a DoD computing center and to meet DoD IA requirements. The activities in this task involve access to DECC data system. A minimum of final Top Secret security clearance and IT-I (privileged level systems access) is required when performance starts. The contractor shall perform the following activities:

1. Providing additional capabilities to the Collaborative Development Environment’s core platform. This additional capability shall include SubVersion, CollabNet TeamForge Enterprise, and Cubit services as enabled by the existing CollabNet software;

1. Design and develop new features and enhance existing features of Forge.mil Family of Services, with a particular focus on features requiring expertise in security;

1. Evaluate the current Forge.mil code and develop technical solutions to help mitigate any security vulnerabilities.

1. Providing software development, engineering solutions and support for Community Forge using open source and community source software;

1. Providing software development, engineering solutions and support for the forge.mil public interface website (www.forge.mil) using open source and community source;

1. Providing development, engineering solutions and support for the froge.mil Single Sign-on (SSO) authentication and authorization for all forge.mil environments using the open source and COTS solutions;

1. Providing additional engineering support in response to this increase capability and new feature enhancement requests. The contractor shall help to define road map, design, and implement new enhancement features and capacity to support the project new demand and growth in both quality and quantity;

1. Delivering the Forge.mil Collaborative Development Environment to support distributed development of open source and community source software within the DoD network environment (i.e., NIPRNet and SIPRNet);

1. Providing open interfaces and product extensions to enable integration with other commercial and government tools that support the software development process. The Forge.mil Developer Network will make use of CollabNet’s open and pluggable SOA Based integration framework to connect these federated user tool environments into the DECC hosted CollabNet infrastructure; and

1. As part of the planning and ramp up of the Forge.mil Developer Network, the contractor shall work with the community to identify and build integrations to commonly used software development lifecycle tools and environments into the DECC hosted infrastructure.

Deliverables:

Assess engineering solution for IA security posture

6.6 Task 6 – Community Management Support

The contractor shall support the creation and growth of a collaborative community of stakeholders who both benefit from and contribute to the Forge.mil Collaborative Development Environment. Working in tandem with DISA, the contractor shall ensure that activities such as governance, public relations and outreach, community recruitment, training and support, and ongoing process development will take place in an institutionalized fashion and contribute to the successful adoption of, satisfaction with, and overall growth of Forge.mil:

1. Support services necessary to on-ramp new customers and partners in the Forge.mil collaborative environment, ensure stakeholder alignment, establish success metrics, and develop a community governance approach to maintaining and evolving the Forge.mil community;

1. Develop a site content strategy and go-to-market strategy that aligns with the DISA and Forge.mil stakeholder objectives and support the launch of the Forge.mil capability;

1. Ensure the brand integration of the Collaborative Development Environment with the other components of Forge.mil;

1. Provide user training and partner training to ensure successful recruitment and retention of community membership, and facilitate real-time feedback to help evolve and maintain the Forge.mil capability;

1. Take part in the weekly Community Management Team meeting.

1. Provide support to maintain the integrity and operational availability of the Forge.mil operating environments in support of the Forge.mil program office and the end users.

1. Work with current and prospective users of the Forge.mil suite of services to improve DoD community adoption, user satisfaction, and overall utilization;

Deliverables:

COTS required list with expected costs COTS required products for deployment Community Support plan Training & Webinar briefing slides

6.7 Task 7 – Business Operation Support

The contractor shall provide support to Forge.mil project coordinators in the planning, operations, and outreach activities necessary to the program. Specific tasks include:

1. Maintaining and executing the community support processes

1. Maintaining and supporting the execution of the Forge.mil communications plan

1. Write technical articles topics such as open source software development, Forge.mil capabilities and features,

1. Ensure the technical accuracy of Forge.mil’s web presence on the Forge.mil web sites as well as community outreach sites such as Wikipedia, Intellipedia, and DoDTechipedia.

1. Prepare and make presentations on behalf of the Forge program to cloud computing initiatives and other technical focus areas as identified.

1. Supporting the user community for the Forge.mil suite of services

2. Inform new projects on the Forge.mil capabilities.

2. Help on-board new projects into Forge.mil’s CollabNet SourceForge Enterprise (CSFE) tool and Subversion repository.

2. Perform as a site administrator of Forge.mil’s CSFE tool and support Forge.mil Tier 1 and Tier 2 support processes.

2. Develop memoranda and support agreements to institutionalize partnerships and clarify relationships and expectations.

2. Make maximum use of online resources (e.g. wikis, portals, hosted collaboration tools) to increase the rate of knowledge sharing within communities and strengthen DISA technical partnerships.

2. Ensure Forge.mil community growth and evolution through education and outreach.

The contractor shall be required to maintain and provide upgrades to the existing Forge.mil ecosystem. This includes providing open interfaces and product extensions to enable integration with other commercial and government tools that support the software development process. Acceptable purchases for the categories listed in this section are as follows:

The contractor shall provide product maintenance and technical refreshes for existing software and hardware products.

The contractor shall purchase additional COTS support or products as specified and approved in the POA&M that’s required to support Forge.mil.

The contractor shall obtain training from COTS product vendors and/or consulting services in support of this requirement.

The contractor shall provide support at various conferences where Forge.mil is required to provide booths and demonstrations to the conference attendees. The contractor shall provide conference items as part of the conference, which shall be governed, and guidance provided by COR or Alt COR. The contractor shall support Forge.mil conference requirements by providing additional space at customer conferences, rental or purchase of electrical equipment, storage units, media furniture, and marketing accessories. As required by the COR.

All purchases will need to be approved by COR or ALT COR.

Deliverables:

Forge.mil Product End Items. This includes successful and operational upgrade features compatible with the current Forge platform that is in DISA DECCs environments System build documentation Documented plan for upgrades, bug fixes and plan successfully delivered Business support plan

7. Performance Standards.

Task 6.4 - Provide a small window of uninterrupted System Access during maintenance activities and upgrades

8. INCENTIVES. Both positive and negative performance will be documented in past performance reports/databases, as appropriate. Meeting or exceeding the Acceptable Quality Level is considered positive performance. Failure to meet the AQL is considered negative performance.

9. PLACE OF PERFORMANCE.

Work will be performed at DISA headquarters (Fort Meade, MD). The contractor shall be required to travel to support Forge.mil within CONUS. The government estimates a total of 10 trips with 4 people for 5 days for planning purposes. For estimating purposes, it is anticipated that travel may be necessary from DISA HQ for the following purposes: Forge stakeholders meetings, Conference attendance, meetings with DISA DECC personnel, and meetings with vendors at their facilities.

The COR/ALT COR must expressly approve travel. Specific travel requirements shall be coordinated with the COR/ALT COR and shall be in accordance with the Federal Acquisition Regulation (FAR) Subpart 31.205-46 requirements and limitations. Reimbursement for travel expenses shall be made in accordance with the Federal Travel Regulations.

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. COR/ALT COR approval is required. Contractor shall prepare all deliverables and other contract documentation utilizing contractor resources.

10. PERIOD OF PERFORMANCE.

The period of performance is for one year from contract award with four (4) one year option periods.

11. Delivery Schedule.

Minimum of 4 – Master POA&M and 3 revisions

Bi-Weekly iteration planning, and User Acceptance Test

Weekly

Initial - 90 days after contract award

Updates - Monthly

Updates - Monthly

Updates - Monthly

Updates Monthly– 30 days after requested

Final: 360 calendar days after contract award

Final – 360 calendar days after award (or do you want a few days to review before contract ends?)

Updates Quarterly

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR ,Alternate COR and Deputy PM.

12. Security Requirements: This section shall be considered a supplement to block 13 of the Government provided DD 254, Contract Classification Specification. The following security requirements shall apply to this effort.

12.1 Facility Security Clearance. The work to be performed under this contract is up to the Top Secret level and may require Sensitive Compartmented Information (SCI) access eligibility for some personnel. Therefore the company must have a final Top Secret Facility Clearance (FCL) from the Defense Security Service (DSS) Facility Clearance Branch (FCB).

12.2 Security Clearance and Information Technology (IT) Level. All personnel performing on this contract will be U.S. citizens. There is two levels of personnel security requirements under this contract covering 8 types of tasks:

12.2.1 The following positions require a minimum of final Top Secret security clearance and IT-I (privileged level systems access) eligibility when performance starts. The incumbents 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.

Task Area 2 – Certification & Accreditation Support Task Area 3 – Software Integration, Test and Validation Support Task Area 4 – Operations Support Task Area 5 – Software Development for Collaboration and Community Product Line

12.2.2…