Task Order Technical Instructions

 

NAVSEA SeaPort EnhancedPerformance Work Statement (PWS):
SPAWAR 05F - FORCEnet Implementation Processes and Tools Support (NS01)

1.0 PERFORMANCE REQUIREMENTS

The Contractor shall perform the following tasks in accomplishing the requirements of this Task Order (TO). Additionally, the contractor shall provide the necessary timely assistance to meet emergent requirements as requested by the Project Manager, Deputy Project Manager or other properly designated authority.

1.1 FORCEnet Implementation Process (FIP)

1.1.1 Definition: Conceptually, the FORCEnet Implementation Process evaluates program compliance with FORCEnet attributes and identifies FORCEnet implementation contribution of Program of Record Systems. It supports enterprise requirements and programming process such as JCIDS, NCDP and PPBE. In the execution of this task the contractor shall formally define the activities and workflows associated with the FIP and explain how this it adds value to other mandated processes (RDT&E).

1.1.2 Documentation: In the execution of this task the contractor shall produce textual and graphical artifacts that define the FIP. These will be of professional quality formatted with XML for formal electronic staffing, registration and discovery. All documentation will be placed under Configuration Management. Tasking includes incorporation of recommended changes during the vetting process and publishing the approved version as a Navy policy or SPAWAR instruction (RDT&E).

1.1.3 Presentation: In the execution of this task the contractor shall formally socialization of the FIP within the Naval and DoD Enterprise through the creation and presentation of briefings, and training. Materials will be in softcopy, hardcopy and/or interactive formats (O&M,N).

1.2 Naval Net-centric Data Strategy Development

1.2.1 Definition: In the execution of this task the contractor shall define Naval requirements and processes necessary to comply with DoD Net-centric Data Strategy Policy guidance. Tasking involves research into ongoing data strategy efforts within DoD and the development of governance infrastructure related to the establishment of institutional Naval Communities of Interest. It involves identification of the major technical elements of the Strategy to include recommendations on industry / DoD best practices with respect to taxonomy and ontology development, enterprise storage, archiving, replication, Enterprise Content Management, and Knowledge Management. Contractors shall capture the Return on Investment (ROI) metrics associated with data level integration of software programs, databases, applications and services (RDT&E).

1.2.2 Implementation: This task involves establishing a timeline and fielding plan for the implementation of the Naval Net-centric Data Strategy. It consists of Risk and Benefit calculations in the context of new or improved military capability. Return on Investment Calculations and / or Cost Avoidance Calculations will also be required (RDT&E).

1.2.3 Documentation: This task relates to the production of textual and graphical artifacts that define the Naval Net-centric Data Strategy. These will be of professional quality formatted with XML for formal electronic staffing, registration and discovery. All documentation will be placed under Configuration Management. Tasking includes incorporation of recommended changes during the vetting process and publishing the approved version as a Navy policy or SPAWAR instruction (RDT&E).

1.3 FORCEnet Implementation Toolset FIT) Management

1.3.1 Requirements Definition and Management: In the execution of this task the contractor shall capture and manage requirements associated with the development of the software tools necessary to support the FORCEnet Implementation Process. Best practices will be required for the capture, elicitation, archiving and Configuration Management of the all business, user and functional requirements. The contractor shall create a feedback mechanism to permit stakeholders to track their requirements requests (RDT&E).

1.3.2 IPTs and WGs: In the exectution of this task the contractor shall coordinate and/or participate in Integrated Product Teams and Working Groups and government hosted conferences related specifically to the management of FORCEnet Implementation (RDT&E).

1.3.3 Document Courses of Action (COAs): In the execution of this task the contractor shall document all courses of action, options and recommendations from appropriate IPTs and WGs (RDT&E).

1.3.4 Transition COAs to appropriate Project Office (RDT&E).

1.4 FORCEnet Implementation Baseline (RDT&E)

1.4.1 The contractor shall provide information system project management, software requirements management, Concept Development, design, development, test, modification, installation, implementation, quality assurance, training, and documentation to support FORCEnet Implementation Baseline (RDT&E).

1.4.2 Documentation: This task relates to the production of textual and graphical artifacts that conform with the Software Engineering Life Cycle (SELC) guidance provided as Government Furnished Information (GFI) These will be of professional quality formatted with XML for formal electronic staffing, registration and discovery. All documentation will be placed under Configuration Management. Tasking includes incorporation of recommended changes during the vetting process and publishing the approved version as a Navy policy or SPAWAR instruction (O&M,N).

1.5 Classified material: The contractor shall comply with all security regulations and instructions concerning handling and storage of classified material under their control. Government authority will inventory classified material annually with no inventory discrepancies allowed (O&M,N).

1.6 Planning Support: The contractor shall provide technical and planning support for meetings, conferences and working groups. This support shall include coordination of the meetings, drafting meeting agendas, setup and operation of Video Teleconferencing (VTC) equipment and other audio-visual equipment, taking meeting minutes, and finalizing and distributing those minutes as directed within the schedule established by the requestor (O&M,N).

1.7 Meeting and Conference Services: The contractor shall coordinate technical meetings, conferences, and work groups. The arrangements will be made in accordance with the procedures and schedules set by the requestor. For these events, the contractor shall notify the participants, provide agendas, directions, and arrange for appropriate equipment. The arrangements for the above events are to be made within the requester’s timeframe and to their satisfaction. Event reports are due ten (10) working days after the event. These events shall be planned, coordinated and executed with 99% accuracy and in the time required according to the requestor (O&M,N). …

1.8 Project Management

1.8.1 The Contractor shall prepare, maintain, and track project management data including work breakdown structures, schedules, Plans of Action and Milestones (POA&Ms), briefings, and general purpose project data and reports, including evaluation tools to help these efforts. The Contractor shall process this project management data as received, updating project files as necessary for proper ADNS project management, to the satisfaction of the project managers(O&M,N).

1.8.2 The Contractor shall prepare project management analysis reports including status on current projects in response to external or internal questions. Reports shall be prepared and submitted on an ad hoc basis as necessary or as assigned to support the project office (O&M,N).




Performance Work Statement (PWS): C4I Modernization Integrated Data
Data Environment (IDE) Support (NS02)

1.0 PERFORMANCE REQUIREMENTS

The Contractor shall perform the following tasks in accomplishing the requirements of this Task Order (TO). The Contractor shall provide the necessary timely assistance to meet routine and emergent requirements as requested by Government task managers or other properly designated authority. Performance standards (unless otherwise specified):

Performance – Fully coordinated among stakeholders; Timeliness – Meets required deadlines or schedule assigned by requester or Lead, documentation submitted to the proper authority in sufficient time for review and approval; Quality – Properly coordinated efforts, produced in the government-approved format of the requester or Lead, technically and factually correct, accurate, complete and free of grammatical, typographical and spelling errors, meeting intended purpose; Acceptable Quality Level (AQL) – 95% compliance. Monitoring Method: Contractor shall report weekly on accomplishments; client feedback and efforts to remedy or mitigate any problems will be monitored.

1.1. Integrated Data Environment (IDE) System Enhancement Support

1.1.1. Systems enhancement: The Contractor shall provide existing, fielded systems enhancement support to the PEO Director of Modernization to implement, streamline, and automate modernization and installation processes.

1.1.1.1. The Contractor shall assist in the enhancement, documentation, and implementation of enterprise level processes and tools to support all phases of the PEO C4I and Space Advance Planning Process. These efforts will focus specifically on the evolution and maturation of the C4I Advanced Training Suite (CAPS).

1.1.1.2. The Contractor will support development of the CAPS Acquisition Module, initial C4I certification report, and automation of the IT21/Fn cost to completion metric.

1.1.1.3. The Contractor will support migration of the existing Acquisition Support Office (ASO) web site and associated database into the SPIDER/CAPS environment.

1.1.1.4. The Contractor shall provide maintenance and configuration control of the CAPS to include resolution of software trouble reports and minor functionality improvements presented via approved software change requests.

1.1.1.5. All Software/Services developed under this task shall be in accordance with Net-Centric Enterprise Solutions for Interoperability (NESI) mandatory guidance and best practices located at http://nesipublic.spawar.navy.mil.

1.1.1.6. All Software/Services delivered shall be labeled “Unlimited” or “government Purpose Rights”, and shall be deposited (uploaded) in the NESI collaborative site at https://nesi.spawar.navy.mil.

1.1.2. Training Support: The Contractor shall establish and implement a training plan for introducing new functionality provided in production releases of CAPS to all PMWs within PEO C4I and Space. The training plan will support group lecture and individual end user hands on training. The group lectures will provide a CAPS capability overview and present general user functions. The individual end user training will provide a handson session tailored to primary users.